Automatic Receipts Gives Extension Invalid For Payer, Or Non-Existant
(Doc ID 1272743.1)
Last updated on JULY 03, 2019
Applies to:
Oracle Payments - Version 12.0.6 to 12.1.3 [Release 12.0 to 12.1]Information in this document applies to any platform.
Symptoms
Automatic Receipts Creation request fails with the following error:
Detect receipts with Auth failure
Debug log displays:
iby.plsql.IBY_FNDCPT_TRXN_PUBCopy_Transaction_Extension extension invalid for payer, or non-existant
fnd.plsql.FND_FILE.PUT_LINE extension invalid for payer, or non-existant
iby.plsql.IBY_FNDCPT_COMMON.Prepare_Result(5 ARG) Enter
fnd.plsql.FND_FILE.PUT_LINE Enter
iby.plsql.IBY_FNDCPT_COMMON.Prepare_Result(7 ARG) Enter
fnd.plsql.FND_FILE.PUT_LINE Enter
iby.plsql.IBY_FNDCPT_COMMON.Prepare_Result(7 ARG) Exit
fnd.plsql.FND_FILE.PUT_LINE Exit
iby.plsql.IBY_FNDCPT_COMMON.Prepare_Result(5 ARG) Exit
fnd.plsql.FND_FILE.PUT_LINE Exit
ar.plsql.l_doc_seq_status x_return_status :<E>
ar.plsql.l_doc_seq_status x_msg_count :<1>
ar.plsql.l_doc_seq_status x_msg #1 = <Transaction extension does not exist.>
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |