Siebel Order Management Infrastructure Guide > Variable Maps > Using Variable Maps >

Defining the Variable Map Used by a PSP Procedure


PSP procedures use variable maps to define the objects acted upon. You specify the variable maps used by a PSP procedure in the Parameters list of the Administration - Order Management screen, then Signals view.

NOTE:  Certain methods of the Context Service business service include variable map arguments for these definitions. See Variable Map Methods of the Context Service Business Service.

The PSP procedure is independent of the calling context. Most PSP signals invoke the PSP Driver Workflow Process (shown in Figure 13), which is a generic controller workflow. The controller workflow uses variable maps to construct inputs for the PSP procedure. Those variable maps are defined in the signal that invokes the controller workflow.

Signal parameters define the scope of line items retrieved by the variable map, and they define the variable maps used to retrieve Context and Row Set data. Figure 12 shows example signal parameters.

Figure 12. Signal Parameters for Variable Maps
Click for full size image

Example of Variable Map Methods in Use

Figure 13 shows the PSP Driver Workflow Process, which is a generic example of a controller workflow. PSP Driver Workflow Process uses variable maps to retrieve data that is then synchronized back to the database.

Figure 13. PSP Driver Workflow Process
Click for full size image

As shown in Figure 13, the PSP Driver Workflow Process steps perform as follows:

  • Get Context Row Set. Calls the Context Service business service method GetRowSetData to retrieve header-level information using the Context variable map (Variable Map - Context).
  • Get Row Set. Calls the Context Service business service method GetRowSetData to retrieve row-level information using the Row Set variable map (Variable Map - Row Set) and to scope input arguments.
  • Dispatch Service. Calls the sub workflow process defined in the calling signal and passes in the input argument.
  • Set Pricing Data. Sets pricing date based on whether it is for scenario testing.
    • Set system time stamp if it is not for scenario testing: {Context.Effective Pricing Date} = TimeStamp()
    • Set Active JWS Test DT if it is for scenario testing: {Context.Effective Pricing Date} = GetProfileAttr("Active JWS Test DT")
  • Sync Row Set. Calls the Context Service business service method SyncRowSetData to write any updates back to the database (for example, updates to prices).

To define the variable map used by a PSP procedure

  1. Navigate to the Administration - Order Management screen, then Signals view.
  2. In the Signals list, select the signal that will invoke the PSP procedure.
  3. In the Versions list, click the Work Space hyperlink to access the Actions list.
  4. In the Actions list, enter the name of the controller workflow in the Service Name field.

    NOTE:  Most PSP signals invoke the generic PSP Driver Workflow Process.

  5. In the Parameters list (scroll down, if necessary), enter parameters for the signal, as follows:
    • Using Scope arguments and values, define the scope of line items retrieved by the variable map.
    • Using Variable Map parameters, define the variable maps used to retrieve Context and Row Set data.
Siebel Order Management Infrastructure Guide Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.