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 FEBRUARY 03, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 126.96.36.199 and later
Information in this document applies to any platform.
188.8.131.52.1 in Production and Test
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.
Collect trading partners via Legacy load
Some Id would be assigned per design
This data gets carried over to APCC and we are seeing some unassigned operating units in reports due to this OPERATING_UNIT being null.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|