Inbound Web Service History

Oracle Revenue Management and Billing enables you to track the response sent through an inbound web service to the external system using the Inbound Web Service History feature. To enable the Inbound Web Service History feature, you need to do the following:

  • Define an outbound message type with the following specifications:

    • Outbound Message Business Object - Web Service History (C1-WebServiceHistory)

    • Priority - Priority 10 -- Highest

  • Define an external system and associate the above outbound message type (where the outbound message business object is set to Web Service History) with the external system using the following specifications:

    • Processing Method - Batch

    • Batch Control - F1-FLUSH

  • Create an algorithm using the C1-IWSHIST algorithm type and attach it to the Web Service History system event in the installation options.

    Note: You need to specify the above outbound message type (where the outbound message business object is set to Web Service History) in the Outbound Message Type parameter of the C1-IWSHIST algorithm.

If the Inbound Web Service History feature is enabled, the system creates an outbound message using the outbound message type specified in the C1-IWSHIST algorithm when the response is sent through an inbound web service. The details of the outbound message, request (in the XML format), and response (in the XML format) are stored in the F1_​OUTMSG table. In addition, it creates a history record in the C1_​IWS_​HIST table. The inbound web service history record indicates the following:

  • Outbound message which is created for the external system, external transaction ID, and/or external source ID combination

  • Business service due to which the outbound message is created

  • Entity on which the action is performed through the business service

The entity type is stored along with the entity corresponding to the record in the C1_​IWS_​HIST table. At present, the following entity types are added in the RMB_​ENTITY_​TYPE_​FLG lookup field:

  • Account

  • Adjustment

  • Bill

  • Contract Type

  • Contract

  • Membership

  • Payment

If you want to use the Inbound Web Service History feature for any custom inbound web service, you need to ensure that the respective entity type is added in the RMB_​ENTITY_​TYPE_​FLG lookup field.

Note: If the external system is received in the request, the system verifies whether the specified external system matches the external system which is associated with the outbound message type specified in the C1-IWSHIST algorithm. If the specified external system does not match the external system associated with the outbound message type, an error occurs while processing the request. Note that the external system validation happens when the Inbound Web Service History feature is enabled.