Legacy Load Does Not Populate Operating Unit In MSC_TRADING_PARTNERS - APCC Reports Will Not Work Correctly Without This Data (Doc ID 1643632.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

12.1.3.9.1 in Production and Test

PROBLEM
-------------
We are trying to load the Organization using the TradingPartner template for self service legacy load. The file contains the place-holder for Operating Unit Name corresponding to the Organization. After loading the data using legacy load I am expecting in table MSC_TRADING_PARTNERS, the columns OPERATING_UNIT_NAME and OPERATING_UNIT to be updated corresponding to each Organization.

The OPERATING_UNIT_NAME is getting updated from the value per TradingPartner template but the OPERATING_UNIT is NOT getting updates (is NULL)
OPERATING_UNIT is expected to be the internal id corresponding to the OPERATING_UNIT_NAME.
This field is not getting updated by the legacy load.


STEPS
--------
Collect trading partners via Legacy load

EXPECTED BEHAVIOR
----------------------------
Some Id would be assigned per design

BUSINESS IMPACT
----------------------
This data gets carried over to APCC and we are seeing some unassigned operating units in reports due to this OPERATING_UNIT being null.

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