Implementation Guide for Oracle Billing Insight > Load Input File Specifications and Data Mapping >

File Formats for Batch Provisioning Data

This topic shows the file and record formats for batch provisioning data. The input file must be pipe-delimited. The file name must use the pattern PROV_BILLING_YYYYMMDDHHMISS.DAT, where YYYYMMDDHHMISS is the time when the file is generated.

The ProvisioningData batch job processes one file at a time, oldest file first. File processing order is critical, as an object created in the first file must be processed before it can be updated in the second, otherwise the second file will fail.

Each provisioning input file consists of the following:

• A file header (record type 00)
• One or more of the following record types, depending on the file type:
  • Company. Record type 10.
  • Account. Record type 20.
  • Service. Record type 30.

Each record has start date, end date, and delete date, which indicate when the object was created, canceled, and deleted. Each of these dates must be a value in the past.

The bill cycle end date is valid only when the file is extracted from the billing file. Also, when the file is extracted from the billing file, the billing cycle end date is not null in file header, and the start date and end date of record will both be null.

The date format is MM/DD/YYYY. The primary contact username and email must both have either a value or no value.

Follow these guidelines when creating batch provisioning input files:

• Create a pipe-delimited file with the content and the format described in Implementation Guide for Oracle Billing Insight.
• Use the following naming format for the provisioning input file you generate: PROV_BILLING_YYYYMMDDHHMISS.DAT
• Add objects records to the input file in the following sequence:
  1. Companies
  2. Accounts
  3. Service Agreements
• Add a row in the input file for each object with a minimum of the following information:
  • ID
  • Start date attributes
  • End date attributes
• The start and end dates indicate when the object was created and expired. Use the dates to indicate the following actions:
  • Add, or create. Make the start date not null.
  • Delete. Make the delete date not null.
  • Expire. Make the end date not null (to expire the object).
  • Update. Make both the start and end dates null. Note that provisioning objects are not versioned.
• You can use multiple input files, however, it is critical to date and load them in chronological order. The ProvisioningData job processes the file with the oldest modified date and time first, so date the files accordingly to sequence the proper load order. If you do not date the files properly, subsequent input files will fail due to missing objects.

  The ProvisioningData job processes the input file one row at a time.

Table 163 shows the file format for batch provisioning file header.

Table 164 shows the file format for the company record in the batch provisioning file.

Table 165 shows the file format for the account record in the batch provisioning file.

Table 166 shows the file format for the service record in the batch provisioning file.