R12 Can not assign Document Sequence for Debit Memo created From RTS transaction
(Doc ID 842107.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Payables - Version 12.0.0 to 12.0.6 [Release 12.0]Information in this document applies to any platform.
This problem can occur on any platform.
APXINWKB.fmb
apcrtdmb.pls
Symptoms
Unable to Assign Document Sequence for Debit Memo Invoice Created from RTS (Return To Supplier) transaction
EXPECTED BEHAVIOR
Expect that Sequence Number to be populated.
STEPS TO REPRODUCE:
The issue can be reproduced at will with the following steps:
Define Document Sequence
Assign Document Sequence for Debit Memo Invoices with method as NULL
Generate Debit Memo via RTS process
BUSINESS IMPACT:
The issue has the following business impact:
Due to this issue, users cannot get sequence number on debit memo, hence can not track these invoices with voucher number
.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |