Inbound Processing Failing With Custom Procedure
Last updated on NOVEMBER 17, 2015
Applies to:Oracle XML Gateway - Version 12.2.3 to 12.2.3 [Release 12.2]
Information in this document applies to any platform.
When using a custom procedure to pass data to the XML gateway, in this case i(but may apply to other product groups) the records are sent to AP interface. Upon further review the following key columns required for invoice processing are blank:
These columns are derived by the gateway using the trading partner code used to post data to the interface tables.
It looks like these columns are not mapped in the gateway, but instead it is a problem with Oracle Software.
These values are derived columns,based on the tp_header_id.
Seems the tp_header_id is being set in the global variable ECX_UTILS.G_snd_tp_id in the package ecx_inbound_trig.validate_message.
The procedure using global parameter ecx_utils.g_snd_tp_id which will be set just before starting of xml processing or raising an event
to process xml in java. This is fine with earlier (plsql) as complete processing is in single session. But when processing in java, there are chances
that java processing will be triggered on another session and the vales to this parameter are not available.
On Oracle Applications 12.2.3,
Inbound processing is failing with a custom procedure.
The issue is that the XML Gateway process completes and loads data into the AP interface tables, but the VENDOR_SITE_ID and ORG_ID are not populated in the AP interface tables. When the Payables Open Interface Import runs, the XML invoices are not selected for import because of the missing data.
The VENDOR_SITE_ID and ORG_ID should populate in the AP Interface tables and the invoices should then be selected by the Payables Open Interface Import to import to the AP base tables.
The issue can be reproduced at will with the following steps:
1. Set up the XML Invoice process in OSN.
2. Submit the XML Gateway Process.
3. Check the AP interface tables and see that VENDOR_SITE_ID and ORG_ID are missing.
4. Submit Payables Open Interface Import and see that the invoices do not import.
The issue has the following business impact:
Due to this issue, users cannot import XML Gateway invoices in R12.2.+.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms