My Oracle Support Banner

R12 AP: How To Setup Periodic Sequences For Use In eText Templates (Doc ID 1999286.1)

Last updated on JUNE 28, 2018

Applies to:

Oracle Payments - Version 12.0.0 to 12.2.3 [Release 12.0 to 12.2]
Information in this document applies to any platform.

Goal

This document will describe how to configure the minimum setups necessary to allow an eText payment template to use periodic sequences.

This may be necessary if you encounter the following error the following errors in the "Format Payment Instructions with Text Output" concurrent request log (line numbers may vary by patch level).

java.lang.NumberFormatException: For input string: "null"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:59)
	at java.lang.Integer.parseInt(Integer.java:458)
	...
Error: an error occurred during formatting. Please verify the template is valid.
oracle.apps.iby.exception.PSException: Internal Error to Payment Server: For input string: "null"
	at oracle.apps.iby.engine.ExtractFormatter.applyFormat(ExtractFormatter.java:150)
	...

These errors can point to a lack of starting value for defined periodic sequences.  This can be confirmed if the payment instruction XML extract does not supply any payment sequence information.  See the example below:

<OutboundPaymentInstruction>
    <PaymentInstructionInfo>
        ...
        <PaymentSequence>
            <SequenceName/>
            <LastValue/>
        </PaymentSequence>
        <PaymentSequence>
            <SequenceName/>
            <LastValue/>
        </PaymentSequence>
        <PaymentSequence>
            <SequenceName/>
            <LastValue/>
        </PaymentSequence>
        ...

Reference R12: AP: How to See the Entire XML Output for a Payment Instruction Without Using the "Extract Identity" Template (Doc ID 1275796.1)

Once the setup is complete, the sequence names and values will be populated in the extract.  This should allow eText output to be successfully generated by templates that require the periodic sequences.

 

The screen shots below show a sample setup using the seeded US NACHA CCDP Format.  The associated template file (IBYDE_N2US_en.rtf) defines the following sequences:

 

Only the US_NACHA_CCDP_DAILY_SEQ sequence is defined as a periodic sequence requiring setup.  This is to ensure that the sequence is tracked and reset outside of individual payment instructions.  The PaymentsSeq sequence will automatically reset for each payment instruction.

The current value of the periodic sequence is obtained via the SEQUENCE_NUMBER() function call. Below is the screenshot from the same seeded template:

IMPORTANT:
Defining a periodic sequence and failing to reference it via the SEQUENCE_NUMBER() function will also result in the error: java.lang.NumberFormatException: For input string: "null"
This call is necessary to perform initialization of the sequence during formatting so that it can be incremented upon completion using the setup steps below. Custom templates should have at least one call for each periodic sequence defined.

Solution

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
Goal
Solution
 Create the New Payment System
 Create the Payment System Account
 Create the Payment Process Profile
  Configure the Sequence(s)
 Configure the Sequence(s) Reset Schedule
 Create test payments
 Standard Patching Process
 Patch Wizard
 Have more questions?
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.