Preprocessor Creates Two Operation_sequence ID's For The Same Op Seq Number

(Doc ID 2166675.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Data Collections

ACTUAL BEHAVIOR
---------------
Legacy Collections using ODBC - Pre-processor creates two operation_sequence_id's for the same Operation Sequence Number.

Routing has one operation, 10, with two parallel resource sequences. 1st resource is for Resource AAAAA second sequence is for Resource BBBBB.

Prior to Pre-processor running there are two operation 10 for the same routing in msc_st_operation_resources. After the Pre-processor runs there are two operation 10's with different operation sequence id. When viewed in the ASCP workbench there are two operations 10. When you drill down to resource we see one one operation has the resource AAAAA, and the other operation drill down to resource has the BBBBB resource.


EXPECTED BEHAVIOR
-----------------------
Expect one Operation with two operations to be loaded.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup Routing
2. Load information into Staging tables
3. Run Legacy Collections
4. Observe results


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms