Last updated on SEPTEMBER 02, 2016
Applies to:Oracle Payments - Version 12.0.6 to 12.0.6 [Release 12.0]
Information in this document applies to any platform.
Checked for relevance on 15-Jul-2013.
Oracle iPayment - Version: 12.0.6 to 12.0.6
<Bug:7388882> and <Bug:6898689> address the issue of user not able to open Text output for Format Payment Instructions program when default output type [in concurrent program definition] is not Text.
The initial approach of using Output Post Processor in the <Bug:6898689> had Out of memory issues for the very large payment instructions. Hence, new approach of having multiple concurrent program definitions for different output type is used in the fix in <Bug:7388882>.
The <Bug:6898689> fix used to create file(s) with extensions ETEXT/PDF/XML to hold the output in APPLCSF/OUT directory.
With the <bug:7388882> fix, it has now reverted back to the standard directory/output file name as APPLCSF/OUT/o<request_id>.OUT.
In the new approach, we have come up with two concurrent program definitions 'Format Payment Instructions' and 'Format Payment Instructions for text output' with output type PDF and Text respectively to resolve view output issue. These concurrent programs use exactly same logic but produce output in the type as per their output type definition. The selection of the concurrent program during execution is done internally depending upon output type requirement.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms