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

Performing Required Tasks for the Communications PIP

The tasks in this topic are required if you are using the Communications PIP.

Enabling Dynamic Pricing

Customers with the 'Dynamic Pricer' license must undertake the steps mentioned in the document to enable the execution of 'Dynamic Pricing Procedure'.

To leverage the dynamic pricing procedure, customers have to perform following changes to the existing repository.

The Siebel pricing module is available in multiple licensing modes and each mode is associated with either the 'Basic Pricing Procedure' or the 'Dynamic Pricing Procedure'.

Basic Pricing Procedure

Note the following information about this procedure:

• This procedure mimics the basic Siebel Pricer functionality that was available in Siebel version 7.7 applications.
• Basic Siebel Pricer functionality includes list price, volume discounts, and service pricing.
• It leverages the variable maps that do not contain the XA child variable maps.

Dynamic Pricing Procedure

Note the following information about this procedure:

• This procedure provides the complete pricing capabilities such as attribute pricing, promotions, aggregate discounts, and so forth.
• It leverages the variable maps that contain the XA child variable maps.
• It is available only to those customers that have the 'Dynamic Pricer' license.

To enable dynamic pricing

1. If you are running Siebel applications version 8.1.1 or above, then navigate to the Administration - Pricing screen, then Price Lists view, click the menu button, and select Enable Dynamic Pricing.
2. If you are running Siebel applications versions earlier than 8.1.1, then you must manually modify the signals.

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.

Configuring the Email Notification for the Product Class and Attribute Query Feature

Users to whom emails must be sent must be added to the user list.

To add or change the email addresses for the user list

1. Navigate to the Administration - User screen, then the Users view.
2. Add user name and user ID.
3. Add the email address in the contact information of the child applet.
4. Navigate to the Administration - Group screen, then the User Lists view.
5. Query for the SCE Users user list. If it does not appear, then create it.
6. Add the users created in the user list.

Add Changed User List

The user list created above is passed in the run-time events. Use the following procedure to add the changed user list.

To change the BO/BC/Field name to extract the email addresses

1. Navigate to the Administration - Run Time Events screen, then the Action Sets view.
2. Query for the EmailNotify action set.
3. Query for the 'GetEmailAddr' action in the child applet.

   The following is the business service context syntax:

   "Parent BC Record Name";"Field Name in Child BC";"BO Name";"Parent BC";"Child BC"

   For instance:

   "SCE Users";"Email Address";"Account";"Account";"Contact"

   or

   "SCE Users";"EMail Addr";"User List";"User List";"User"

   The following three run-time events use the action set described above.

Edit or Configure Templates

Four communications templates are used to send email messages. The Attribute Defn and Product Class templates are already configured. Use the following procedure to configure or edit other templates.

To edit or configure email template text

1. Create a Notepad file called Attribute_Template.txt and add the following values:
   • Attribute Name: [Name]
   • Description: [Description]
   • Type: [Type]
   • Object Number: [Object Number]
   • XRef Class Name: [XRef Class Name]
2. Create a Notepad file called Class_Template.txt and add the following values:
   • Class Name: [Name]
   • Description: [Description]
   • Type: [Type]
   • Object Number: [Object Number]
3. Create a Notepad file called attr_email_notification_template.txt and add the following values:

   Attribute Version Details
   ========================
   _____________________________________________________
   | Effective Start Date : [Required Start Date]
   |
   | Effective End Date : [Required End Date]
   |
   | VOD Version Number : [Version]
   ______________________________________________________

4. Create a Notepad file called class_email_notification_template.txt and add the following values:

   Product Class Version Details
   =============================
   _____________________________________________________
   | Effective Start Date : [Required Start Date]
   |
   | Effective End Date : [Required End Date]
   |
   | VOD Version Number : [Version]
   ______________________________________________________

5. Navigate to the Administration - Communication screen, All Templates, and then the Template Items view.
6. Query for Workspace Attribute Defn Template, and complete the following steps:
   1. In the Template Items view, attach the Attribute_Template.txt file created in Step 1 in the template item.
   2. Select ISS Joint Workspace VOD Pick BusComp from Iteration Child Business Component.
   3. Select the Substitute Values and Message Body check boxes, and save the template Item.
7. Query for Workspace Product Class Defn Template, and complete the following steps:
   1. In the Template Items view, attach the Class_Template.txt file created in Step 2 in the template item.
   2. Select ISS Joint Workspace VOD Pick BusComp from the Iteration Child Business Component.
   3. Select the Substitute Values and Message Body check boxes, and save the template Item.
8. Query for Attribute Defn Template, and complete the following steps:
   1. In the Template Items view, attach the attr_email_notification_template.txt file created in Step 3 in the template item.
   2. Select SWI Attribute Versions BusComp (Notify) from the Iteration Child Business Component.
   3. Select the Substitute Values and Message Body check boxes, and save the template item.
9. Query for Product Class Template, and complete the following steps:
   1. In the Template Items view, attach the class_email_notification_template.txt file created in Step 4 in the template item.
   2. Select SWI Attribute Versions BusComp (Notify) from the Iteration Child Business Component.
   3. Select the Substitute Values and Message Body check boxes, and save the template item.

      The communication template names are added in the user properties of the business components in the following table.

      Business Component	User Property	Template Name
      ISS Joint Workspace BusComp	PackageNameList|Attribute Definition	Workspace Attribute Defn Template
      ISS Joint Workspace BusComp	PackageNameList|Product Class Definition	Workspace Product Class Defn Template
      Attribute VOD BusComp	PackageNameList	Attribute Defn Template
      ISS Class VOD BusComp	PackageNameList	Product Class Template

Add SMTP Server Name, From Email Address, and POP Server Details

The SMTP Server name, From Email Address, and POP server details are added in the Communication profile. Use the following procedure to add the SMTP server name, From Email Address, and POP server details.

To change the SMTP Server name, From Email Address, and POP server details

1. Navigate to the Administration - Communications screen, then the Communications Drivers and Profiles view.
2. Query for the Internet SMTP/POP3 Server communication driver, and if it does not exist, then create it, using the following values:
   • Name: Internet SMTP/IMAP Server
   • Channel Type: Email
   • Channel String: POP3SMTP
   • Library Name: sscmmail
   • Outbound: Yes
3. Query for Default SMTP in child applet. If it does not exist, then create it.
4. Change the SMTP and POP Server details in the grandchild applet, using the following values:
   • From Address: siebel.product.admin@demohost.siebel.com
   • POP3 Account Name: support
   • POP3 Account Password: support
   • POP3 Server: demohost.siebel.com
   • SMTP Server: rgmamersmtp.oraclecorp.com

The communication profile is added in the user properties of the business components in the following table.

Set Up Time-Based Offering Feature

Use the following procedure to set up the time-based offering feature

To set up the Time-Based Offering feature

1. Create Product Master Data by completing the following steps:
   1. Create the following attributes:
      • Duration (Number. Enumerated, values 1, 2,3, ... 31)
      • DurationUnitOfMeasure (Text. Enumerated values: Days, Months, Years)
      • DurationValidityStart (Text. Enumerated Values: Original Start, Now, Original End)
   2. Create a class with the above three attributes.

      NOTE:  The Class attributes names and the attribute definition names must be identical.

   3. For the TBO Discount products synced from Oracle Communications Billing and Revenue Management, change the Structure type to Customizable and the Product Type to Time Based Offer, and associate the above TBO class to this product.
2. Create Job to Inactive Assets by completing the following steps:
   1. Navigate to Server Management, and then Jobs, and create a new Job as follows:
      • Select Component as Workflow Process Batch Manager.
      • Select Repeating as Y.
      • Select Requested Server as the Siebel Server.
      • Select Repeat Unit as Days.
      • Select Repeat Interval as 1.
      • Select Repeat From as Scheduled Start.
   2. Navigate to Job Parameters and create a new parameters.
   3. Select Name as Workflow Process Name and specify the Value of SWI Asset Status Update.
   4. Select Name as Search Specification and specify the Value if necessary.
3. Create Revision Data Maps by completing the following steps:
   1. Navigate to Administration - Application, then the Data Map Administration view.
   2. In Data Map Object, query for Name of Revise Order or ReviseQuote.
   3. In Data Map Component, query for Name of Line Item.
   4. In Data Map Field, add the fields to be copied during revision (such as Service End Date, Service Start Date, and Due Date).
4. Configure the business service.

   The business service name must be specified as the value for the Business Service Query Access List server component parameter.

   For example, if the server component is eCommunications Object Manager (ENU), then go to its parameters and query for Name of Business Service Query Access List and add Value of CMU External Integration Service. Then, the server component can be restarted to take effect after the change in the component parameter value.