Subcontracting: Interlock Manager Issues - see debug message "No subcontracting relationship exists between the OEM and the MP" AND also solved PO Not Picked Up For Processing (Doc ID 2184261.1)

Last updated on MARCH 08, 2017

Applies to:

Goal

Qn1:Subcontracting: Interlock Manager not kicking off the worker program . We are running the program in production after go-live

The Subcontracting process completely stop as Replenishment PO and Replenishment SO not created , Which impacting $

Uploaded all the screen shot of setup and fnd log , program log , setup Diagnostics, Apps Diagnostics

FND LOG messages in the ZIP file shows it is failing in the initial validation phase

MODULE LOG_LEVEL MESSAGE_TEXT
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Validate_OSA_Item: OSA flag is 1
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Validate_OSA_Item: Component flag is
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Get_OEM_Tp_Org: Start
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Get_OEM_Tp_Org: p_organization_id:104: p_vendor_id:2113: p_vendor_site_id:3567
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Get_OEM_Tp_OrgTP Org:
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Get_OEM_Tp_Org: Exit
JMF_SUBCONTRACT_ORDERS_PVT 2 >> Validate_OSA_Item mp org id -
jmf.plsql.JMF_SHIKYU_GRP.Get_Subcontracting_Type.invoked 2 Entry
jmf.plsql.JMF_SHIKYU_GRP.Get_Subcontracting_Type.invoked 2 Before the query: subcontracting_type = ""

>>> jmf.plsql.JMF_SHIKYU_GRP.Get_Subcontracting_Type.no_data_found 4 No subcontracting relationship exists between the OEM and the MP

 
Qn2:We have solved several issues in the Post go-live  - In the case of PO 2017 we did not see this PO/Item picked up by the Interlock Manager and processed.

Even for a failure in the interlock manager when trying to process a PO, we expect that line will exist in the table JMF_SUBCONTRACT_ORDERS after it attempts to process and the INTERLOCK_STATUS = E or N

Solution