My Oracle Support Banner

R12.1 - Record Print Status Error, Receiving APP-FND-01728: An assignment does not exist for these parameters. (Doc ID 1188174.1)

Last updated on NOVEMBER 24, 2021

Applies to:

Oracle Payables - Version 12.1.1 and later
Information in this document applies to any platform.


We have the Sequential Numbering profile option set to Partially Used for AP, since the business requires its use in some circumstances, such as on Standard invoice creation.  However, that setup seems to be causing the Record Print Status step to fail when processing check batches, with rows like the following displayed in the concurrent request log file:
IBY_DISBURSE_UI_API_PUB_PKG.mark_all_pmts_complete: Exception occured when marking payments complete for payment instruction 10361
IBY_DISBURSE_UI_API_PUB_PKG.mark_all_pmts_complete: SQLCODE: -20001
IBY_DISBURSE_UI_API_PUB_PKG.mark_all_pmts_complete: SQLERRM: ORA-20001: APP-FND-01728: An assignment does not exist for these parameters. Cause: An attempt was made to find a sequence for this document flexfield. The profile option says Sequential Numbering is only partially used. Action: None is necessary unless you expected this document flexfield to have a sequence defined.
Exceptions posted by this request: Concurrent Request for "Record Print Status" has completed with error.

The business does not require the use of Sequential numbering for payment batches. What can we do to avoid the Record Print Status failure, short of disabling the Sequential Numbering profile option in AP?


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
 Still Have Questions?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.