|
Implementation Guide for Oracle Self-Service E-Billing > Customizing the Payment Consolidator Integration Module > Creating Customized Payment Consolidation Templates >
Template Attributes
Attributes in the template XML files describe the format of each type of record, such as position, length and so on. Each element in a template file corresponds with one of the payment consolidator's data elements. For example, the element <recordType .. /> represents the record type and the element <ConsolidatorID .. /> represents the consolidator ID. The name of element can have any value but it should be meaningful so that it can be easily understood. Table 101 shows the attribute names you can use in the template XML files.
Table 101. Attributes Used in the Payment Consolidator Templates
|
|
|
pos |
int |
The data element start position in the data file. |
len |
int |
The fixed data element value length. |
fmt |
N: number AN: String date: dateFormat timestamp: timestampFormattime:timeFormat |
The type of date and time element and the format. Some payment consolidators require a maximum of 12 numbers before the decimal and two numbers after the decimal, without a decimal point: $$$$$$$$$$$$cc. |
fract |
A digital number. |
The number of digits after decimal point if the fmt attribute is N. |
required |
Y - Yes or N - No |
Indicates whether the field is mandatory. If the attribute is Y, then when parsed or generating a file, the job checks whether the value is not null. If it is null, then this record fails to parse. If the field value could be all spaces, then you must set the required attribute to N. Otherwise, mandatory field checking will fail as all spaces are treated as a null value. |
target |
The invoked statement enclosed between the percentage sign (%), such as: %detailRecord.getConsolidatorID()% |
Used only in template files for the input data file. When parsing this attribute, the template engine invokes the corresponding method or gets the value of the property for certain Java objects (you can get the Java object from the template context by name). |
|
