Release 12 Issues in Statement Printing and AR Customer Balance Statement Letter
(Doc ID 565507.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Receivables - Version 12.0.4 and later
Information in this document applies to any platform.
Report:ARXSGPO.RDF - Print Statements
Executable:ARXSGP - Statement Generation Program
Following is a brief history of the changes done regarding Statement Printing in Release 12.
In the original offering of Oracle Receivables Release 12.0.3, the Statement Print Program (ARXSGPO) was seeded to provide output in TEXT format.
Towards the end of 2007, a European localization for Hungary containing the AR Customer Balance Statement letter was released. This letter is used to confirm the balance position with the customers. It is an extension of the Customer Balance Statement letter to show any Unapplied and On-Account receipts of customers in a separate section as on the date of printing the statement in addition to the existing standard information. It is launched using the Print Statement Program.
The patch providing a new printing template for the AR Customer Balance Statement Letter was released via <Patch 6319005>. This patch listed <Patch 6435000>: ORACLE E-BUSINESS SUITE 12.0.4 RELEASE UPDATE PACK (RUP4) as a pre-requisite.
When 12.0.4 (RUP4) <Patch 6435000> was released, many customers who applied it started reporting issues wherein the Statement Print program was failing. Issues stemmed from any of the following:
- Logic in Statement Generation attempts to print AR Customer Balance Statement Letter, but the output is in XML format instead of a format that can be read by customers. This is due to missing templates required to provide proper output.
- You had previously modified the concurrent process to use your own custom template and that has been overridden by applying the RUP4 patch.
- You do not require European localizations and yet AR Customer Balance Statement Letter was being invoked.
- You require European localizations but AR Customer Balance Statement Letter was not being invoked.
Application of RUP4 <Patch 6435000>
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?|