My Oracle Support Banner

WS: 47: P470412 Creates Incorrect Journal Entries for 2nd Purchase Order When 1st PO has MACT = Blank & 2nd PO has Multiple detail lines with Subledger/Subledger Type & P4316 Multiple Accounts MACT = 1 (Doc ID 2649891.1)

Last updated on MARCH 19, 2020

Applies to:

JD Edwards World EDI - Version A9.3 and later
Information in this document applies to any platform.


This issue occurs after adding code change for Bug 29803511: MULTIPLE ACCOUNTS USED FOR ONLY LINE 1 WHEN VOUCHER CREATED VIA P470412 to a A9.3 environment.

When processing 2 purchase orders at the same time where order 1 has a single J line type line with MACT = blank and the second order has 3 J line type detail lines with each line having MACT = 1 and for each line the P4316 - Multiple Accounts lists 12 accounts splitting out the total amount of the line, the vouchers are created but for the order with multiple accounts, the journal entries are only partially split out. They do not split out to each and every account listed in the P4316 for each line.

Steps required to produce these results in an A9.3 environment where bug 29803511 has been added.
1. Create a J line type purchase order with a single J line type containing a Subledger and Subledger Type. MACT = blank
2. Create a second J line type purchase order with 3 lines where each line contains a Subledger and Subledger Type. MACT = 1 for each line. Each line has 12 multiple accounts as seen in P4316 and the total amount is split between these 12 lines.
3. Both orders are selected for processing by P470412 (2 way match).
4. Vouchers are created for both orders, but the journal entries for the multiple account PO are only split out to a portion of the multiple accounts rather than splitting out completely.


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.