Implementation Guide for Oracle Billing Insight > Customizing the Payment Consolidator Integration Module >

Creating Customized Payment Consolidation Templates

A set of custom template files is required for each type of input and output file processed or generated by the payment consolidation jobs in the Command Center. The payment consolidator jobs use the templates to parse the data input files received from a particular payment consolidator (either batch or real-time) and to structure the output files provided to the consolidator.

You must customize the sample templates provided with Oracle Billing Insight to accommodate your consolidator's requirements. The two sets of preconfigured sample files closely describe the structure of common payment consolidator formats.

Each type of input and output file that a payment consolidator uses requires a set of custom XML templates that includes:

• A file structure XML template. The file structured XML template defines the structure of the individual records in the input or output file and maps to each of the individual record XML template files designed for each record.
• An XML template file for each record type in the file. Custom template XML files are required for each type of record, including the file header, file tail, detail record, and batch header and tail records if supported by the consolidator. Record XML template files are used to parse input file records or generate output file records.

This task is step in Process of Implementing a Payment Consolidator.

To create customized payment consolidator templates

1. Review the sample XML templates provided with Oracle Billing Insight to determine which ones most closely match the input and output data files required by your payment consolidator. For information about the sample template files provided with Oracle Billing Insight, see Sample Payment Consolidation Template Files. If your consolidator supports batch processing, then use the batch input file templates.

   The default input and output data file formats that the API is preconfigured to use are described in Default File Formats for Payment Consolidation. For samples of how a payment consolidator's data file elements can map to Oracle Billing Insight, see the following topics:

   • Data Element Mappings - Example A
   • Data Element Mappings - Example B
2. Using the closest matching set of files (or copies), edit the content for your consolidator's specifications. See to the following topics as needed for information about the content and format of template XML files:
   • The File Structure XML Template
   • The Record XML Templates
   • Template Attributes
   • Template Variables
   • Adding a New Java Object Instance or Static Class
   • Adding Cartridge Property Keys
3. Place the templates in the template directory for the payment consolidator that you configured for the consolidator in the Command Center.