My Oracle Support Banner

Incorrect payment_grouping_number When Payment Process Request Includes Credit Memos (Doc ID 1614813.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Oracle Payables - Version 12.0.6 and later
Oracle Payments - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.


Two checks generated for same supplier.

PPR generated two document numbers due to Pre-grouping of the invoices. Invoices are pre-grouped and assigned a group number if the batch includes any ‘Credit Memo’/’Interest invoice’. When user initially built the PPR, credit memo was included and it caused the grouping of all the invoices included that time. Later when user included the invoices again, they were assigned a different group number and hence separate document number got generated for each group.

According to Doc 1384297.1:
Exception when applying Grouping within a PPR:
When credit or debit memos are selected in the Payment Process Request (PPR), then document grouping is done by the Payables application (AP) instead of the Payments module (IBY).

When a PPR contains memos, Payables will pre-group the "Documents Payable" (the selected invoices and memos) by stamping them with a payment grouping number (IBY_DOCS_PAYABLE_ALL.PAYMENT_GROUPING_NUMBER).

When the payments Build Payments program detects that the Documents Payable are pre-grouped by Payables, it will ignore all the user-defined grouping rules defined in the Payment Process Profile, and apply only the pre-defined grouping rules.

Adding new invoices manually should not create a new Document group and should be added to pre-grouped invoices.

The issue can be reproduced at will with the following steps:
1. Submit PPR
2. Add Invoices to the PPR Manually




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.