EDI CDMO: ECE_CDMO_HEADER_V Deriving PARTY_NUMBER Instead of ACCOUNT_NUMBER
(Doc ID 1908231.1)
Last updated on FEBRUARY 18, 2019
Oracle EDI Gateway - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Receivables EDI/XML Gateway
The OUT: Credit/Debit Memo(812) is not getting the BILL_TO_CUSTOMER_NUMBER, SHIP_TO_CUSTOMER_NUMBER, or SOLD_TO_CUSTOMER_NUMBER in lines 1010, 1110 and 1210 pos. 141.
This extract program is using view ECE_CDMO_HEADER_V, which is getting the information from the HZ_PARTIES.party_number table, instead of HZ_CUST_ACCOUNTS.account_number.
In 11i, the information is derived from RA_CUSTOMERS view.
In R12, the customer number is stored in the table HZ_CUST_ACCOUNTS, in the account_number column.
Steps to Reproduce:
1. Review the ECE_CDMO_HEADER_V
CREATE OR REPLACE force VIEW ECE_CDMO_HEADER_V as
SELECT 'EDI' communication_method,
pt1.party_number bill_to_customer_number, -- should be ca1.account_number
pt2.party_number ship_to_customer_number, -- should be ca2.account_number
pt3.party_number sold_to_customer_number, -- should be ca3.account_number
FROM hz_parties pt1,
WHERE rct1.complete_flag = 'Y'
AND rct1.printing_pending = 'Y'
AND rct1.printing_option = 'PRI'
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
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.