Administration Guide for Oracle Billing Insight > Command Center Jobs and Configuration Parameters > Billing Jobs >

DefUsrAcctRelationship Job

The DefUsrAcctRelationship job lets you add or remove user-account relationships in Oracle Billing Insight (Consumer Edition only). The job processes a pipe-delimited TXT input file with a list of user IDs and the associated billing system ID and billing account, and a flag stating whether this user should be added to or deleted from the account.

If a user has multiple accounts, then the input file will have multiple rows for the same user. For details about the input file format for the DefUsrAcctRelationship job, see Implementation Guide for Oracle Billing Insight.

The DefUsrAcctRelationship job first verifies that the user and billing account exist in the Oracle Billing Insight database.

If the user-account relationship record is flagged to be removed, then the job checks whether user is associated with any other billing accounts. If the user is associated with more than one billing account, then the association is removed along with any recurring payments. If the user is associated with only one billing account, then the user is not removed. Once you confirm that you want to remove these users, you can delete B2C users and associated activities in batch mode using a SQL script at the command line. For more information about deleting users in batch mode, see Deleting B2C Users in Batch Mode.

After processing, the DefUsrAcctRelationship job sends an email notification to the email addresses specified in the job configuration indicating the number of successful, failed, and warning entries. The job also sends a list of bad billing accounts in an email to the email addresses specified in the job configuration.

Problems with User-Account Records That Generate Bad Entries

The DefUsrAcctRelationship job logs the bad entries, including all errors and warnings, in a log named as the input file name with the extension _Bad, and it places the file in the output directory. The following issues with user-account records are identified as bad entries:

• Error. The entry does not conform to the file specification.
• Error. The user ID does not exist in the Oracle Billing Insight database or is not a B2C user ID.
• Error. The account does not exist in the Oracle Billing Insight database or is not a B2C account, and includes billing ID validation.
• Warning. The user-account relationship is flagged to be added but already exists in the Oracle Billing Insight database.
• Warning. The user-account relationship is flagged to be removed but does not exist in the Oracle Billing Insight database.
• Warning. The user-account relationship is flagged to be removed but the user has only one account.

The DefUsrAcctRelationship job also records entries that do not conform to the file specification in the LOGS database table, and records all other types of bad entries in EDX_UMF_USERACCT_LOAD_EXCEPN database table.

Parameters for Configuring the DefUserAcctRelationshipTask

Table 20 displays the configuration parameters for the DefUserAcctRelationship task.