Siebel Communications Guide > Overview of Siebel Communications > Configuring Communications, Order-to-Cash, and Master Data Management Integration >

Performing Required Tasks for the Order to Cash PIP

The tasks in this topic are required if you are using the Order to Cash PIP.

Disabling Asset-Based Ordering

Use the following procedure to disable Asset-Based Ordering.

To disable Asset-Based Ordering

1. Log in to the Siebel application, and navigate to the Administration - Server Configuration screen, Servers, then the Parameters view.
2. Query for the corresponding object manager for the application (such as htimObjMgr_enu for application HTIM).
3. Query for the Order Management - Enable Asset Based Ordering parameter in the parameter list for the component, and set the value to False.
4. Restart the Siebel Server.

Running EIM Data Migration

This topic describes how to run the EIM jobs for implementing the O2C PIP.

Data Migration Sequence

Execute the entities in the following table in sequence to maintain the data integrity. This table includes the pre-and post EIM activities, which must be carried out manually.

Before you begin the EIM import, note the following points:

• Make sure that the Siebel Server is running.
• Make sure that the Siebel EIM component is online and is running properly. (Navigate to the Administration - Server Configuration or Administration - Server Management screen.)
• To avoid data loss, do not restart the Siebel Server while the EIM job is running.
• After you have completed the data load for one country, make backup copies of the EIM log files, for status verification. These log files are located in the siebsrvr/logs directory.

Checking EIM Component Availability

Use the following procedure to check EIM component availability.

To check EIM component availability

1. Navigate to the Administration - Server Management screen, Servers, and then the Component Groups view. Make sure that the component group Enterprise Application Integration is active and online.
2. Make sure that the Enterprise Integration Manager component within the Workflow Management component group is also active and online.
3. Navigate to the Administration - Server Configuration screen, Enterprise, Component Groups, and then the Components Group Assignments view.
4. Make sure that the Enterprise Application Integration Component Group is enabled.

Setting Up Organizations

Use the following procedure to set up organizations.

To set up organizations

1. Navigate to the Administration - Group screen, then the Organizations view.
2. Create the required organizations.

   NOTE:  Enter information into the Organization Name field but leave the Site field blank.

Setting Up Inventory Locations

Use the following procedure to set up inventory locations.

To set up inventory locations

1. Navigate to the Administration - Data screen, then the Inventory Locations view.
2. Create inventory locations.

   NOTE:  Make sure that the inventory location is associated with the correct location.

Executing the EIM Job

Use the following procedure to execute the EIM job.

To execute the EIM job

1. Place the respective IFB file on the server computer using the Siebsrvr/Admin file path, as shown in the following example.

2. Make sure that the SESSION SQL statement of the [UPDATE ACCOUNT NUMBER] section of the Customer Ifb file is modified to reflect the working instance:

   UPDATE ORA19111.EIM_ACCOUNT SET OU_NUM = T_ORG_EXT__RID WHERE IF_ROW_BATCH_NUM=100

   where ORA19111 is the working instance.

   Also, consider the same for the [UPDATE INTEGRATION ID] section of the Pricelist.ifb file:

   SESSION SQL = "UPDATE ORA19111.EIM_PRI_LST SET PL_INTEGRATION_ID = NULL WHERE PL_INTEGRATION_ID IS NOT NULL"

   For Pricelist.ifb, comment the second process using a terminate symbol (so that it becomes inactive and only the first process is executed) as follows:

   [IMPORT ALL PRICELISTS]

   TYPE = SHELL

   INCLUDE = "IMPORT PRICELIST"

   ;INCLUDE = "UPDATE INTEGRATION ID"

   After EIM imports all of the pricelist data and the Integration Id is populated, the administrator needs to run another ODI API to populate the cross-reference database. Then, the administrator needs to run EIM again to nullify integ_id. The format of the IFB file for the second run follows:

   [IMPORT ALL PRICELISTS]

   TYPE = SHELL

   ;INCLUDE = "IMPORT PRICELIST"

   INCLUDE = "UPDATE INTEGRATION ID"

   All the job parameters must remain the same for both of the runs.

3. Log in to the application with administrator credentials to be able to access the Server Management screen.
4. Navigate to the Administration - Server Management screen, then the Jobs view.
5. Create a new record, and select Enterprise Integration Mgr in the Component/Job field.
6. In the Job Parameters applet, fill in the following parameters:
   • Configuration file = .Ifb File name
   • Error Flags = 1
   • SQL Trace Flags = 8
   • Trace Flags = 1
7. After passing parameters, click Submit Job.
8. In the Jobs view, for each job that you have executed, make sure that the Status column displays Success for the jobs that you have executed.
9. Check the status in the EIM table by executing the SQL statements that follow. In each case, make sure that the status is IMPORTED.

Products

Product Header:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Product Details:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PROD_INT1

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Product-Inventory Locations:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRODINVLOC

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Pricelists

In this case since the same set of records are processed twice by the two separate sections of the IFB file: one meant for importing the Pricelist Records and other meant for updating the Integration Id to NULL, you get the DUP_REC_EXISTS status in the EIM tables.

SELECT COUNT(*),IF_ROW_STAT FROM EIM_PRI_LST

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Customers

Address:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_ADDR_PER

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Account:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_ACCOUNT

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Account Details:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_FN_ACCNT1

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Customer:

SELECT COUNT(*),IF_ROW_STAT FROM EIM_CONTACT

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT

Assets

There are two sections in the IFB file: For Importing Assets and For Updating the Parent Assets.

Hence the status shows DUP_REC_EXISTS

SELECT COUNT(*),IF_ROW_STAT,IF_ROW_BATCH_NUM FROM EIM_ASSET

WHERE IF_ROW_BATCH_NUM = '100'

GROUP BY IF_ROW_STAT,IF_ROW_BATCH_NUM

Checking the EIM Log File

Use the following procedure to check the EIM log file.

To check the EIM log file

1. From the Jobs view in the Administration - Server Management screen, navigate to the Tasks View in the same screen.
2. Get the task number from the Task field.
3. Navigate to the Siebsrvr\log directory, and query for the log file using the task number. The log file contains details about every level of processing and information about any errors.

Configuring Oracle Configurator

Use the following procedure to apply the run changes for the configuration to the database. The runtime configuration changes must be done before you can launch Oracle Configurator.

To apply runtime Siebel configuration changes

1. Login to eCommunications/HTIM application from a Web browser.
2. Navigate to the Administration - Business Process screen, then Repository workflow process, and complete the following steps:
   1. In the top applet Query for the workflows imported above and activate them.
   2. Make sure they are in active state by querying in the bottom applet.
3. Navigate to the Administration Runtime Events screen, then the Events view, click the menu button, and select Reload Runtime Events.
4. Navigate to the Administration - Integration screen, then the WI Symbolic URL List view, and complete the following steps:
   1. From the Show drop-down list, select Host Administration.
   2. Add a new host entry with the following values:
      • Host Name: Oracle EBIZ host name:port number, for example, qapache.us.oracle.com:3710
      • Virtual Name: OracleConfigurator
   3. Select Symbolic URL Administration and add new record in the top applet with the following values:
      • Name: OracleCfgURL (Note: This symbolic name is very important because server side business component code relies on this name)
      • URL: http://OracleConfigurator/OA_HTML/CfgSebl.jsp
      • Choose the host name: for example qapache.us.oracle.com:3710
      • Fixup Name: Default
      • SSO Disposition: IFRAME
   4. In the bottom applet, add arguments to the URL as follows:

      Create a new record with the following values:

      • Name: InitMessage
      • Req Arg: checked
      • Argument Type: Profile Attribute
      • Argument Value: CZInitMessage
      • Append as argument: checked

        Add another new record with the following values:

      • Name: PostRequest
      • Required Arg: Checked
      • Argument Type: Command
      • Argument Value: PostRequest
      • Append as argument: Not-Checked

        Complete the following two steps to set up the SSO login into Oracle Applications. The SSO login is the preferred style to access Oracle Applications. If the SSO login is not set up, then the Siebel end user must know and enter Oracle login credentials at the login page.

   5. For the next two arguments enter the values for Argument Value as specified. UserLoginId and UserLoginPassword are function names used by Siebel SSO. These functions look up the Oracle login credentials for the current Siebel User. Putting anything else in requires that you log in to an Oracle Applications for Configurator session.
   6. Continue to add arguments to the same URL with the following values:
      • Name: username
      • Required Arg: Checked
      • Argument Type: Command
      • Argument Value: UserLoginId
      • Append as argument: Checked
   7. Add the final argument with the following values:
      • Name: password
      • Required Arg: Checked
      • Argument Type: Command
      • Argument Value: UserLoginPassword
      • Append as argument: Checked
   8. Select SSO Systems Admin List and add a record in the top applet with the following values:
      • System Name: OracleConfigSSO
      • Symbolic URL Name: OracleCfgURL
      • Description: Logs in to the Oracle Configurator
   9. In the bottom applet SSO System Users add records for the Siebel users who invoke Oracle Configurator. The Siebel usernames are paired with Oracle login credentials. An example follows:
      • Siebel Login Name: sadmin
      • Login Name: operations
      • Password: welcome
5. Navigate to the Administration - Server Configuration screen, Servers, and then the Components view. Select the eCommunications Object Manager (ENU) component and select the Order Management - Enable Asset Based Ordering parameter and set this value to False to call Oracle Configurator instead calling Siebel Configurator.

   Select the HTIM Object Manager (ENU) component and select the Order Management - Enable Asset Based Ordering parameter and set this value to False to call Oracle Configurator instead of calling Siebel Configurator.

   The following workflows must be activated for Configurator to work:

   • Account - New Quote
   • Account - New Order
   • Goto*
   • PSP*
   • Product Compatibility*
   • Product Eligibility*
   • Product Reco*
   • *Pric*
   • Compatibility Multiple Popup Workflow
   • Config*
   • Check*

     These workflows are not workflows that were introduced as part of Oracle Configurator integration, but are existing ones.

Adding Siebel Custom Applications to Oracle Applications

Several custom Oracle Applications must be created to allow models to be accessed from Siebel. These custom applications are used during the publication phase of Oracle Configurator Model development cycle.

To add Siebel Custom Applications to Oracle Applications

1. Log in to Oracle Applications with credentials that have the Sys Administrator privilege.
2. Choose Application, then Register.

   Forms starts up, and the form page appears. If not, then navigate to the form.

3. Create three new entries each with four values as follows:
   • Siebel Quote Integration |SEBLQ | DUMMY_TOP | Provides integration between Siebel Quote and Oracle Configurator
   • Siebel Order Entry Integration | SEBLO | DUMMY_TOP | Provides integration between Siebel Order Entry and Oracle Configurator
   • Siebel Agreement Integration | SEBLA | DUMMY_TOP | Provides integration between Siebel Agreement and Oracle Configurator

     The new applications now must be added to Oracle Configurator Publication Applicability list.

4. Change responsibility to Configurator Administrator.
5. Choose Application to Publication Applicability List and add the applications.

   This step runs a concurrent program. After the program runs, these new applications are available during model publication.

See the Oracle documentation for Configurator for the entire process of developing models for calling applications.

Copy Config Web Service Setup

Use the following procedure to copy the Config Web Service setup.

To copy the Config Web Service setup

1. Log in to the eCommunications/HTIM application from a browser.
2. Navigate to the Administration- Web Services screen, then the Outbound Web Services view.
3. Query for the ESB_ConfiguratorCopyConfigEbizAdapter_Service Web service.
4. Query for ConfiguratorUserLangSiebelAdapter.

   NOTE:  The preceding steps apply to seed data. Perform them when exporting the seed data.

5. Change the IP Address on the Service Ports (middle applet) for each of the above Web Services.

Copy Config Data Map Setup

Use the following procedure to copy the Config Data Map setup.

To copy the Config Data Map setup

1. Log in to eCommunications/HTIM application from a browser and navigate to the Administration - Application screen, then the Data Map Administration view.
2. For the following Data Maps, add three columns (External Configurator Reference 1, External Configurator Reference 2, and External Configurator Reference 3) to both the Source and the Destination Column in Data Map Field section for the Data Map Component specified in the parenthesis:
   • AutoAgreement (Data Map Component:Line Item)
   • AutoAgreeFromOrder (Data Map Component Name:Line Items)
   • CopyOrder (Data Map Component Name:Line Item)
   • CopyQuote (Data Map Component Name:Line Item)
   • OrderToTemplate (Data Map Component Name:Line Item)
   • QuoteToSalesOrder (Data Map Component Name:Line Item)
   • QuoteToServiceOrder (Data Map Component Name:Line Item)
   • QuoteToTemplate (Data Map Component Name:Line Item)
   • ReviseAgreement (Data Map Component Name:Line Item)
   • ReviseOrder (Data Map Component Name:Line Item)
   • ReviseQuote (Data Map Component Name:Line Item)
   • TemplateToOrder (Data Map Component Name:Line Item)
   • TemplateToQuote (Data Map Component Name:Line Item)

DoCompression Parameter Setup

Use the following procedure to complete the DoCompression parameter setup.

To complete the DoCompression parameter setup

1. Stop the Siebel Server.
2. Back up the file, for example, eapps.cfg.

   NOTE:  The folder D:\19924 has been suggested here, but if you have installed the application someplace else, then make sure that you refer to the eapps.cfg file in your installation.

3. Edit the file, for example, eapps.cfg using a text editor.

   CAUTION:  Do not use Wordpad because incorrect characters are added to the file.

4. Reset the DoCompression parameter in the [defaults] section to FALSE.
5. Restart the computer.

   NOTE:  Restarting the Siebel Server is not sufficient.

Applying Changes for the Signal

Use the following procedure to apply changes for the signal.

To apply changes for the signal

1. Navigate to the Administration - Order Management screen, then the Signals view.
2. By locking the signal and clicking the Workspace, change the following signal sequences and release the signal.

   For the CalculateShippingAndTax signal, modify the sequence records in the following table.

For the CreditCardAuthentication signal, modify the sequence records in the following table.

For the RunCreditCheck signal, modify the sequence records in the following table.

For the ATPInquire signal, modify the sequence records in the following table.

For the ATPInquireAll signal, modify the sequence records in the following table.

For the Customize signal, modify the sequence records in the following table.

For the QuotesAndOrdersValidate signal, modify the sequence records in the following table.

Fixing State Model for Quote Status

To make Quote Status work, you can extend the related State Model activation date.

To fix the state model for Quote Status

1. Navigate to the Administration - Application screen, then State Models view and search for TNT SHM Quote Status.
2. Extend its activation date until 2020 (leave day and month as sysdate).

Other Order to Cash Configuration Steps

Use the following procedure to complete other order to cash configuration steps.

To complete other order to cash configuration steps

1. Inactivate the field map by completing the following steps:
   1. Navigate to the Administration - Application screen, then the Data Map Administration view and query for a Data Map Object of ReviseOrder, a Data Map Component of Header, and a Data Map Field of Back Office Process Status.
   2. Inactive this field map by selecting the Inactive check box.
2. Restart the Siebel Server.
3. Launch the Siebel Communications application.