JDE Publish Plan Results - ItemCode Is Wrong In PurchaseOrderInbound.xml (Doc ID 2116243.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Value Chain Planning Integration Base Pack - Version 11.1 and later
Information in this document applies to any platform.

Symptoms

VCP 12.2.4.1 with PIP 11.5

The PurchaseOrderInbound.xml has the long item name instead of short item name as required.

This is working in one instance - DEV
This is not working in latest instance - UAT

Our understanding of the flow is as follows:

When you release planned order - we insert into msc_po_requisitions_interface
Then we call to code in MSC_A2A_XML_WF.LEGACY_RELEASE /
This calls out for Req release to use mapping in
MSC_REQUISITNO_OAG71_OUT.xgm

-- this code I cannot interpret - I expect it to create some XML file - I believe this is PurchasePlan.xml

Next step is run Publish Planning Results - shortname MSCE1PPR
This calls to MSC_E1APS_DEMCL.PUB_PPR / MSCE1DMB.pls

This executes call to ODI and runs
  1041 /* Executing PurchasePlan ODI Scenarios */
  1042 IF p_purchase_plan = MSC_UTIL.SYS_YES THEN
  1043 scenario_name:='LOADAPSPURCHASEPLANDATATOE1PKG';
  1044 ret_value1 :=CALL_ODIEXE(scenario_name ,scenario_version ,scenario_param ,odi_url);
  1045 END IF;
AND others depending on setups

This appears to create PurchaseOrderInbound.xml
and then ODI appears to update values per earlier update to populate CHAR4 from msc_local_id_item

Customer stated that ODI has the following:

SOURCE COMMAND
select (SELECT char4 FROM msc_local_id_item mli WHERE mli.char1 = #E1TOAPSPROJECT.PVN_SR_INSTANCE_ID AND mli.entity_name = 'SR_INVENTORY_ITEM_ID' AND mli.instance_id = #E1TOAPSPROJECT.PVN_SR_INSTANCE_ID AND mli.char5 IS NOT NULL AND mli.char4 IS NOT NULL AND rownum < 2 ) as c4, (SELECT char5 FROM msc_local_id_item mli WHERE mli.char1 = #E1TOAPSPROJECT.PVN_SR_INSTANCE_ID AND mli.entity_name = 'SR_INVENTORY_ITEM_ID' AND mli.instance_id = #E1TOAPSPROJECT.PVN_SR_INSTANCE_ID AND mli.char5 IS NOT NULL AND mli.char4 IS NOT NULL AND rownum < 2 ) as C5 from dual

TARGET COMMAND
UPDATE PURCHASEPLANDETAIL pp SET ITEMCODE = :C4 WHERE (1=1) and pp.ITEMCODE = :C5

-- this is clearly getting CHAR4 which is short item name and is consistent and properly populated in both instances as we can see in file - SUPPORT_REVIEW_Msc_System_items-msc_local_id_item.xls

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