Administration Guide for Oracle Billing Insight > Loading Billing Data Into Oracle Billing Insight >

Setting Global Variables and Email Passwords for ODI Processes

You must set global variables for use as defaults with the the Oracle Data Integrator (ODI) data loading processes. If necessary, you can override global variables at run time.

You specify the global variables to use in the following ODI load scenarios:

• Postpay
• Master
• Unbilled
• Prepay

You must also set global variables with email notification parameters and passwords for use by ODI to send notification of processing status for the following events:

• Load failed
• File failed
• Load successful

NOTE:  Verify that you have installed ODI using the Standalone option, required for running ODI processes in parallel.

To set the global variables and email passwords in Oracle Data Integrator

1. Log in to Oracle Data Integrator as the repository owner.
2. On the Designer tab, expand Global Objects, and then expand Global Variables.
3. For each of the following global variables, select the variable and replace the Default Value shown on the Definition view with your own value. Click Save after specifying each variable.

   Global Variable	Description	Scenarios Where Used
   01_FileName_Pattern	The file name pattern for identifying input file names.	LOADPOSTPAYFILE LOADMASTERFILE LOADPREPAYFILE LOADUNBILLEDFILE
   02_Input_Path	The full directory path where the data input file to be loaded to Oracle Billing Insight is located.	LOADPOSTPAYFILE LOADMASTERFILE LOADPREPAYFILE LOADUNBILLEDFILE
   03_Reject_Path	The full directory path where you want Oracle Billing Insight to place an input file that the loading process rejects.	LOADPOSTPAYFILE LOADMASTERFILE LOADPREPAYFILE LOADUNBILLEDFILE
   04_Output_Path	The full directory path where you want Oracle Billing Insight to place the input file for processing.	LOADPOSTPAYFILE LOADMASTERFILE LOADPREPAYFILE LOADUNBILLEDFILE
   05_Publish	Indicates whether to automatically publish the data into production or use the manual publishing option. The value can be Y or N in single quotation marks.	LOADPOSTPAYFILE
   06_Auto_Reject	Indicates whether to automatically reject the current bill if the load fails and clear the data from the associated staging tables. To automatically reject the load, specify Y. If the load fails, then the data load log will show the discrepancy between the number of records inserted in the staging table and production fact tables. If a failure occurs when using this option, then you will no longer be able to reference the data in the staging tables. If you specify N to suppress this feature, you can reference the staging table data if a failure occurs. After successfully determining the cause of the failure, you must manually reject the data load file before processing the next file. No other files can be loaded until the current run data is either published or rejected.	LOADPOSTPAYFILE LOADMASTERFILE LOADPREPAYFILE LOADUNBILLEDFILE
   08_Email_ToAddress	The email address to receive processing notifications generated by ODI.	Automatic notification after all scenarios
   09_Email_FromAddress	The email address to appear in the From field on email notifications generated by ODI.	Automatic notification after all scenarios
   10_Email_CCAddress	An email address to copy on any notifications sent by ODI.	Automatic notification after all scenarios
   11_Email_SMTPPort	The number of the authenticated SMTP listener port to use for sending email notifications from ODI. The default is 465.	Automatic notification after all scenarios
   12_Email_SMTPServer	The name of the SMTP server to use for sending email notifications from ODI.	Automatic notification after all scenarios
   14_Validate_GroupKey	Indicates whether to validate the associations between the company or account data and group keys. To perform key validation, specify Y. To bypass key validation, specify N. The default is N.	LOADPOSTPAYFILE

4. Set the ODI notification passwords:
   1. Expand Projects, BillingInsight, Data Load Processes, and then expand Packages.
   2. Select the LoadFailed package. In the window on the right, click the transformation icon, which appears as an envelope with an arrow.
   3. On the Properties window, click the General tab, and enter the password for authentication, which is the password of the sender's (from) email account.
   4. Save the changes.
5. Regenerate the notification scenarios to incorporate the global email parameter defaults and passwords:
   1. Expand Projects, BillingInsight, Data Load Processes, and then expand Packages.
   2. Expand the LoadFailed package, expand Scenarios, right-click on LOADFAILED Version 001, and then select Regenerate. On the Regenerate Scenario dialog, click OK. On the Scenario Variables dialog, click OK.
   3. Repeat Step a for the following packages:
      • FileFailed (FILEFAILED Version 001 scenario)
      • LoadSuccessful (LOADSUCCESSFUL Version 001 scenario)
6. Regenerate the load scenarios to incorporate the global parameter defaults:
   1. Expand Projects, BillingInsight, Data Load Processes, and then expand Packages.
   2. Expand the LoadPostPayFile package, expand Scenarios, right-click on the LOADPOSTPAYFILE Version 001 scenario, and then select Regenerate. On the Regenerate Scenario dialog, click OK. On the Scenario Variables dialog, click OK.
   3. Check the following global parameters to use as startup parameters for the LOADPOSTPAYFILE scenario:
      • 01_FileName_Pattern
      • 02_Input_Path
      • 03_Reject_Path
      • 04_Output_Path
      • 05_Publish
      • 06_Auto_Reject
      • 14_Validate_GroupKey
   4. Click OK.
   5. Repeat Step b through Step d for each of the following scenarios:
      • LoadMasterFile (LOADMASTERFILE Version 001 scenario)
      • LoadPrePayFile (LOADPREPAYFILE Version 001 scenario)
      • LoadUnbilledFile(LOADUNBILLEDFILE Version 001 scenario)

        In Step c, set the following global variables only:

      • 01_FileName_Pattern
      • 02_Input_Path
      • 03_Reject_Path
      • 04_Output_Path
      • 06_Auto_Reject