Thursday, May 21, 2015
.
In this post, let us see an example with conditional display. i.e. the contents are displayed based on the filter condition.
Input XML:
Etext Template:
Output:
Oracle Documentation for Reference:
Display Condition Command
The display condition command specifies when the enclosed record or data field group should be displayed. The command parameter is a Boolean expression. When it evaluates to true, the record or data field group is displayed. Otherwise the record or data field group is skipped.
The display condition command can be used with either a record or a group of data fields. When used with a record, the display condition command must follow the new record command. When used with a group of data fields, the display condition command must follow a data field row. In this case, the display condition will apply to the rest of the fields through the end of the record.
Consecutive display condition commands are merged as AND conditions. The merged display conditions apply to the same enclosed record or data field group.
Further Reading: http://docs.oracle.com/cd/E10091_01/doc/bip.1013/b40017/T421739T481436.htm
Thursday, May 21, 2015 0
In this post, we will see an example template displaying both ascending and descending sorting,
XML Input:
EText Template:
Output:
Oracle Documentation for Reference:
Sort Ascending and Sort Descending Commands
Use the sort ascending and sort descending commands to sort the instances of a level. Enter the elements you wish to sort by in a comma-separated list. This is an optional command. When used, it must come right after the (first) level command and it applies to all records of the level, even if the records are specified in multiple tables.
Further Reading: http://docs.oracle.com/cd/E10091_01/doc/bip.1013/b40017/T421739T481436.htm
Wednesday, May 20, 2015
In this post, let us see an example with CONCATENATION COMMAND
XML Input:
ETEXT Template
Output:
From Oracle Documentation
Define Concatenation Command
Use the define concatenation command to concatenate child-level extract elements for use in parent-level fields. For example, use this command to concatenate invoice number and due date for all the invoices belonging to a payment for use in a payment-level field.
The define concatenation command has three subcommands: base level, element, and delimiter.
Base Level Subcommand
The base level subcommand specifies the child level for the operation. For each parent-level instance, the concatenation operation loops through the child-level instances to generate the concatenated string.
Item Subcommand
The item subcommand specifies the operation used to generate each item. An item is a child-level expression that will be concatenated together to generate the concatenation string.
Delimiter Subcommand
The delimiter subcommand specifies the delimiter to separate the concatenated items in the string.
Wednesday, May 20, 2015 0
In this Example, let us see, how to define and use Sequences in ETEXT Template.
Input XML
Expected Output
Etext Template
From Oracle Documentation
Define Sequence Command
The define sequence command define a sequence that can be used in conjunction with the SEQUENCE_NUMBER function to index either the generated EFT records or the extract instances (the database records). The EFT records are the physical records defined in the template. The database records are the records from the extract. To avoid confusion, the term "record" will always refer to the EFT record. The database record will be referred to as an extract element instance or level.The define sequence command has four subcommands: reset at level, increment basis, start at, and maximum:
Reset at Level
The reset at level subcommand defines where the sequence resets its starting number. It is a mandatory subcommand. For example, to number the payments in a batch, define the reset at level as Batch. To continue numbering across batches, define the reset level as RequestHeader.In some cases the sequence is reset outside the template. For example, a periodic sequence may be defined to reset by date. In these cases, the PERIODIC_SEQUENCE keyword is used for the reset at level. The system saves the last sequence number used for a payment file to the database. Outside events control resetting the sequence in the database. For the next payment file run, the sequence number is extracted from the database for the start at number (see start at subcommand).
Increment Basis
The increment basis subcommand specifies if the sequence should be incremented based on record or extract instances. The allowed parameters for this subcommand are RECORD and LEVEL.Enter RECORD to increment the sequence for every record.
Enter LEVEL to increment the sequence for every new instance of a level.
Note that for levels with multiple records, if you use the level-based increment all the records in the level will have the same sequence number. The record-based increment will assign each record in the level a new sequence number.
For level-based increments, the sequence number can be used in the fields of one level only. For example, suppose an extract has a hierarchy of batch > payment > invoice and you define the increment basis by level sequence, with reset at the batch level. You can use the sequence in either the payment or invoice level fields, but not both. You cannot have sequential numbering across hierarchical levels.
However, this rule does not apply to increment basis by record sequences. Records can be sequenced across levels.
For both increment basis by level and by record sequences, the level of the sequence is implicit based on where the sequence is defined.
For detail understanding, http://docs.oracle.com/cd/E10091_01/doc/bip.1013/b40017/T421739T481436.htm
I recently implemented an interface where I have to generate a custom comma seperated payment file. As you know, standard oracle payment program generates only XML output. Hence, I prepared an Etext template for generating the CSV output.
I found the Etxt templates are relatively simple and easy to understand. I have started this series to share my knowledge in the form of examples. Further, I copy pasted the details from Oracle Documentation for easier reference.
First let us see, how to generate a simple comma separated file as output.
Input XML:
Expected Output:
ETEXT/RTF Template:
