This chapter covers the following topics:
Oracle Subcontracting, works effectively if you closely follow the setup steps described in Chapter 2 of this guide. If you set up subcontracting incorrectly, then some of the subcontracting concurrent programs will not process the data and the execution process will not function properly. You must correct an erroneus data setup and rerun the processes.
Use the checkpoints provided in this chapter to verify whether concurrent programs are not processing the data.
You can classify Interlock Manager process steps into three sets:
Creating WIP jobs in the MP organization. During this process, you can view subcontracting orders on the workbench. If WIP jobs are not created, then the subcontracting order is not visible on the Subcontracting Workbench.
Create replenishment Sales orders. You can view replenishment orders on the Subcontracting Workbench.
Allocate replenishment orders in accordance with subcontracting order requirements.
The Interlock Manager concurrent request executes all steps at once if the data is correctly set up. If the setup is not complete, then Interlock Manager may execute only a few steps or it may not execute any steps. Review the setup and make the necessary corrections.
Problem at Step 1: WIP Jobs Are Not Created in the MP Organization
Any of the following issues can cause this problem. Verify and correct the setup.
The profile MO: Default Operating Unit is not set to the operating unit of the OEM organization
The profile MO: Security is not set
Inventory Periods are not opened in the MP organization
WIP Parameters are not defined for the MP organization
Customer and supplier relationships are not defined in the OEM and MP organizations
Check the validity of BOM and components in the MP organization
Check and ensure that routing does not exist in the MP organization
Ensure that OEM and MP organizations are not Process, WMS, or EAM enabled organizations
Check that components and assemblies are defined in the OEM and MP organizations as outsourced assemblies and are pre-positioned or synchronized components respectively. If this is the problem, then you must cancel the current PO and create a new PO with the same details.
Problem at Step 2: Interlock Is Not Creating Replenishment Orders
Shipping networks are not defined for the OEM and MP
No valid price exists for the components
Document sequence is not defined for the Order Management transaction type associated in the shipping networks of OEM to the MP
Profile sequential numbering is not set as Partially Used or Always used
Problem at Step 3: Replenishment Sales Orders are Not Allocated
In the case of synchronized components if the replenishment sales order is created, it will always be allocated, so this issue might not arise. In the case of prepositioned components, which would be a common problem, allocations are made to the existing replenishment sales orders.
For Chargeable Subcontracting, the sales price of the replenishment sales order is different than the component price of the subcontracting order (you can see both the prices on the workbench).
Replenishment sales order shipment date is earlier than the requirement date of the component.
If auto receive is not receiving the components in the MP organization after shipping the components in the OEM organization, then these problems could occur:
Replenishment sales order ship date plus shipment lead-time defined in the shipping networks between OEM to the MP is less than the current date (date at which the Auto Receive Components concurrent request is run).
Purchasing periods are not open.
If the Process Receiving Transactions concurrent request does not complete WIP jobs in the MP organization, then subcontracting order components may not be fully allocated.