Intercompany Troubleshooting Guide For Mandatory Intercompany Relation Or Transaction Flow Not Defined Between These Two Operating Units
(Doc ID 436957.1)
Last updated on JANUARY 23, 2018
Applies to:
Oracle Inventory Management - Version 11.5.10 to 11.5.10 [Release 11.5]Information in this document applies to any platform.
Symptoms
Create Intercompany AP Invoices completed with warning.
Warning
APP-INV-05700: Warning: Mandatory Intercompany Relation or Transaction Flow not defined between these two operating units:
Cause: The selling and shipping operating unit belong to different legal entities but the intercompany relation or the transaction flow has not been defined.
Action: Use the Define Intercompany Transaction Flow form to define the transaction flow and intercompany relation between these two operating units.
Warning: Invoice creation aborted
End of Processing Invoice ID:
Transaction ID: Status: FAILURE
Sometimes includes error message:
Call inv_workflow.call_generate_cogs l_gl_ccid is 0
Message Dictionary couldn't open the ORA-20002: 3135: 'Wf_Item_Activity_Status.
Set_Error(error_process)' is not permitted in synchronous processes.
application message file.
Message Dictionary Error- A file pathname could not be constructed for the application ORA-20002: 3135: 'Wf_Item_Activity_Status.
Set_Error(error_process)' is not permitted in synchronous processes.
This error often indicates that the Application Basepath (e.g. FND_TOP) or
Subdirectory (APPLMSG) environment variables do not have a valid value.
Warning: Invoice creation aborted
End of Processing Invoice Line ID: 8834
Invoice Line ID: 8834 Status: FAILURE
(Please See Note 215460.1 for alternative solutions)
Steps
Navigate to Inventory > Reports > Intercompany invoicing > Create Intercompany AP Invoices
Run the report and receive the warning.
The AP Invoices are not created.
Cause
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
| Symptoms |
| Cause |
| Solution |
| A. Check Setups |
| B. Check Inventory (INV) Debug |
| C. Patching |
| References |