How Do I Setup Autocreate Final Assembly Orders Fails (WICDOL) To Run Without a Sales Order Number Parameter Or Organization Parameter?
(Doc ID 1950040.1)
Last updated on JULY 15, 2024
Applies to:
Oracle Work in Process - Version 11.5.9 to 12.2.4 [Release 11.5 to 12.2]Information in this document applies to any platform.
When you leave the Sales Order Number and Organization parameter empty (null), the following occurs:
WICDOL module: AutoCreate Final Assembly Orders
fails with the following:
....
Return status from CTO_WIP_WRAPPER.get_order_lines:1
Group_Id from CTO_WIP_WRAPPER.get_order_lines: 13583
Calling wip_massload_pub.massLoadJobs with group Id: 13583
Returned from wip_massload_pub.massLoadJobs:
Failed in wip_massload_pub.massLoadJobs.
Failed in wip_massload_pub.massLoadJobs returned with status retCode:E
This error is caused by leaving the Default Discrete Class null in an Organization's Work In Process (WIP) parameters.
Leaving the Sales Order Number and Organization parameter empty (null) causes the AutoCreate Final Assembly Orders (WICDOL) concurrent request to run for every organization. So, every organization has to have WIP parameters defined even though the organization may not be a WIP organization.
Goal
You want WICDOL module: AutoCreate Final Assembly Orders to run successfully with periodic resubmission with no no Sales Order Number parameter and/or Organization Parameter specified
Solution
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
| Goal |
| Solution |
| References |