Engineering Change Order (ECO) Implementation Fails For Items With Unreleased Standard Jobs
Last updated on JULY 14, 2017
Applies to:Oracle Work in Process - Version 12.0.4 to 12.1.3 [Release 12 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 06-May-2013***
Find Engineering Change Order (ECO) Implementation fails for items with unreleased standard jobs.
ENCACNC module: Engineering Change Order Implementation(1)
Calling PL/SQL API for processing discrete records
wilmlx.ppc: wip_massload_pub.massLoadJobs API returned unsuccessful status
No eRecord generated for oracle.apps.bom.billUpdate. This is normal. Please check your rules or
bERES_Flag_for_Routing=FALSE, then, NO ERES event for Routing.
Ackn check: parent_record_id=0, eco_failed_flag=1
Normal end of acknowledgement part
APP-FND-01388: Cannot read value for profile option RPM_CONC_PROCESS_ID in routine &ROUTINE.
The issue can be reproduced at will with the following steps:
1. Create new item with revision control flag.
2. Assign to INV ORG
3. Create and implement ECO in ORG to create BOM
4. Create future job on item.
5. Create new item version in org.
6. Create an ECO to change the item current BOM.
7. Implementation fails.
Expect that BOM would be changed and job updated.
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