1. Communications Guide
  2. Running EIM Data Migration for Comms

Running EIM Data Migration for Comms

This topic defines the detailed steps to run the EIM jobs for Siebel applications as a part of the Creating and Updating Credit Alerts for Collection Flows functionality. The ODI interface is triggered to transport the required data for creating and updating Credit Alerts from Oracle Communications Billing and Revenue Management into the Siebel EIM tables. EIM scripts are then executed to load the data into the SFA base tables.

Before you begin your import, note the following:

  • Make sure that the Siebel Server is up and running.

  • Make sure that the Siebel EIM component is online and running properly. Navigate to the Administration - Server Configuration and Administration - Server Management screens.

  • To avoid data loss, do not restart the Siebel Server while the EIM job is running.

  • After you have completed loading data for one country, make a backup copy of the EIM log files for status verification. (These log files are located under siebsrvr/logs.)

Use the following procedure to execute the EIM job to create and update credit alerts.

To execute the EIM job to create and update credit alerts

  1. Run the EIM job with the ProcessAlertsAndBillingProf.ifb configuration file.

  2. Verify that the EIM job is successful.

    Note: If the Order-to-Cash PIP is enabled, then the Asset-Based Ordering parameter for the corresponding object manager for the application has to be set to False.

This topic describes the integration user setup process. A new flag has been introduced to identify an integration user (needed while integration testing). This user credential needs to be configured (on the Oracle Application Integration Architecture side) for the Siebel Inbound Web services call from the Oracle Application Integration Architecture side to avoid the boomerang effect.