Siebel Communications Guide > Defining Billing Profile Workflows for Siebel Communications > Workflow to View Content in the Billing Profile Portal >

SIA External Integration Process Workflow

This workflow retrieves and displays data from a billing application. This data consists of information about top-up requests, current account balances, and usage activity for an account. This workflow displays the content in the Billing Profile portal. This content includes balance group, usage that is not billed, bill, and bill payment information.

This workflow is called in the following situations:

• When the user clicks the Name field of a billing profile in the Billing Profile list of the Account Summary view.
• When the user accesses or navigates to the following views in the billing profile portal:
  • Balance Group
  • Unbilled Usage
  • Bills
  • Payments

This workflow is not called from within the Adjustments view.

Figure 34 shows the SIA External Integration Process workflow.

Figure 34. SIA External Integration Process

Workflow Description. This workflow performs the following actions:

1. Get Custom Attributes. Reads the enterprise details, such as the Siebel Enterprise Server name, language, and locale.
2. Set Custom Attributes. Sets the enterprise details as part of the request message.
3. Proxy Business Service. This step performs the following work:
   1. Calls the appropriate proxy business service as determined by the input that is passed to the business service.
   2. Calls the WSDL file on the integration server to get the response in Siebel Message format. In Oracle Application Integration Architecture 2.5, the workflow passes the Proxy BS Fault input argument for customized fault handling. If there is a fault, then the business service returns the fault code, a summary, and a detail in the output argument.

      NOTE:  You must create the proxy business services that this workflow calls. Also, for the virtual business components (VBCs) that use these services, you must configure the user properties.

4. UpdateVBCRec. Retrieves the data from the Siebel message and stores the data in the property set.

Associated Business Service Methods. The following table shows the steps in this workflow that call business service methods.

The business service names depend on the Name tags in the WSDL file that you generate when you create the proxy business services.