SRDC - EBS Receivables: Receipts

Workbench (Doc ID 1682452.1)

To
Bottom

Applies To
Product:

Oracle Receivables - All Versions

What is being collected and why?

This document is tagged as a Service Request Data Collection (SRDC)
document, this means that it has been designed to provide you with the
instructions to:

Collect files to be uploaded, depending on your Receipt workbench

issue

Action Plan
To troubleshoot various issues, within the Receipt Workbench, different
files are required for specific issues.
Please review the list below to identify your type of issue, and the list of
files required. Then next to each file is a value in parentheses, look for
Instructions on how to get that type of file in the Instructions section
below:
Files required
1. For issues with Receipt Create or Receipt Write-off:

Receipt Data Diagnostic (FILE1)

Screen Shot (FILE13) showing the error/issue

AR Setup Diagnostics (FILE2)

2. For issues with Receipt Application or Receipt Reversal:

Transaction Data Diagnostic (FILE3) of the transaction the receipt is

applied to

Screen Shot (FILE13) showing the error/issue

Receipt Data Diagnostic (FILE1)

AR Setup Diagnostics (FILE2)

3. For issues with Receipt Batches:

Receipt Batch Data Diagnostic (FILE4)

Receipt Data Diagnostic (FILE1)

AR Setup Diagnostics (FILE2)

4. For issues with AP/AR Netting Agreement:

AP/AR Netting Setup Diagnostic (FILE5)

AR Setup Diagnostics (FILE2)

Report Output (FILE8)

Concurrent Process Log File (FILE9)

5. For issues with AutoReceipts/AutoRemittances:

Receipt Data Diagnostic (FILE1)

AR Setup Diagnostics (FILE2)

Report Output (FILE8)

Concurrent Process Log File (FILE9) and the FND Debug log (FILE7)

6. For issues with Receipt SEPA or Receipt Workbench Setup:

AR Setup Diagnostic(FILE2)

RDA/ACT Diagnostic or Apps Check Output (FILE6)

Instructions to get files:

FILE1: Receipt Data Diagnostic (pick the note appropriate for your release)

Note 215969.1 11i Oracle Receivables Receipt Data Data Collection

Test

Note 431367.1 R12.0.[3-4] Oracle Receivables Receipt Data Setup

Test

Note 732201.1 R12.0.6+ Oracle Receivables Receipt Data Setup

Test

FILE2: AR Setup Diagnostic (pick the note appropriate for your release)

Note 202260.1 11i : Oracle Receivables General Setup Test

Note 419051.1 R12.0.[3-4] : Oracle Receivables General Setup Test

Note 732193.1 R12.0.6+ : Oracle Receivables General Setup Test

FILE3: Transaction Data Diagnostic (pick the note appropriate for your
release)

Note 223834.1 11i Oracle Receivables Transaction Data Data

Collection Test

Note 431370.1 R12.0.[3-4] Oracle Receivables Transaction Data

Setup Test

Note 732203.1 R12.0.6+ Oracle Receivables Transaction Data Setup

Test

FILE4: Receipt Batch Data Diagnostic (pick the note appropriate for your
release)

Note 311204.1 11i Oracle Receivables Receipt Batch Data Data

Collection Test

Note 471593.1 R12.0.[3-4] Oracle Receivables Receipt Batch Data

Data Collection Test

Note 732200.1 R12.0.6+ Oracle Receivables Receipt Batch Data

Data Collection Test

FILE5: AP/AR Netting Setup Diagnostic (pick the note appropriate for your
release)

Note 437145.1 R12.0.[3-4] : Financials Common Modules APAR

Netting Data Setup Test

Note 732129.1 R12.0.6+ : Financials Common Modules APAR Netting

Data Setup Test

FILE6: RDA/ACT diagnostic *OR* Apps Check output

To gather information regarding file versions for forms, PL/SQL packages,
reports and more, we need one of the following files. This will help us
identify if you need to apply patches to obtain code fixes to address your
issue.

RDA/ACT
Please upload the output of RDA/ACT Data Collection diagnostic. Run
it for Application Short Name = AR. The APPS Username and
Password are OPTIONAL. Use the note applicable to your release
from the list below:
o Note 183274.1 11i : Applications DBA RDA Data Collection Test
o Note 420427.1 R12.0.[3-4] : All RDA Data Collection Test
o Note 732091.1 R12.0.6+ : All RDA Data Collection Test

OR Apps Check:
1) Log into the Application
2) Responsibility: Order Management
3) Navigation: Report, Request > Run Requests
4) Submit a Single Request for Name = Diagnostics: Apps Check
5) Run with Parameter 1 = Receivables
6) Upload the output generated

FILE7: FND Debug Log

The FND debug log will show the path taken by the code. This will help in
troubleshooting the issue. Please do the following steps:
a. Setup FND Debug Profiles
Responsibility: System Administrator
Navigation: System > Profiles
- Set the following profile options:
FND: Debug Log Enabled = 'Yes'
FND: Debug Log Level = Statement
FND: Debug Log module = %
AR: Enable Debug Message Output = Yes
- Save your changes
b. Retrieve maximum log sequence before reproducing issue by running
the following SQL statement:

SELECT MAX(log_sequence) before_seq

FROM fnd_log_messages;
c. Reproduce the error
Using minimal keystrokes, continue with the duplication step(s) to
replicate error. Click 'Ok' to close any error message box.
d. Retrieve maximum log sequence after reproducing issue by running
the following SQL statement:
SELECT MAX(log_sequence) after_seq
FROM fnd_log_messages;
e. Retrieve debug messages and export to a spreadsheet
SELECT *
FROM fnd_log_messages
WHERE log_sequence BETWEEN &before_seq AND &after_seq
ORDER BY log_sequence;
f. Upload the spreadsheet
FILE8: Concurrent Program Output
If the concurrent process yielded output, please upload the report that
illustrates the issue you are encountering.
FILE9: Concurrent Request Logfile
Please upload the concurrent request logfile generated by the concurrent
process.
FILE10: API Code
Upload the complete code/script you are using to call the API.
FILE11: API Output
If your code/script using the API yielded output, please upload it.
FILE12: API Debug Log
Upload the Debug Log generated by the API code, using Note 784317.1
FILE13: Screen Shot
Reproduce the issue you get in the form and capture the screenshot
showing the error and upload it.