Action Code Dependency in Process Integration Pack with AIA and BRM (Doc ID 1361954.1)

Last updated on JULY 05, 2013

Applies to:

Oracle Communications Order and Service Management - Version 7.0.2 to 7.0.3 [Release 7.0.0]
Information in this document applies to any platform.
***Checked for relevance on 05-July-2013***

Goal

Using PIP OTA 2.5 we noticed this behavior: the same product specification ( example: Mobile.Subscription) on one Order line item, if it is executed with the action code "ADD", it is executing the following functions:
1) sync customer
2) initiate billing
3) provisioning
4) fulfill billing

If it is executed with the action code "Delete", it is executing the following functions:

1) provisioning
2) fulfill billing

This is the behavior observed out of the box. Is it possible to know what is the functional reason behind this behavior and is it possible in the code to modify this behavior. For example; force the product spec in "delete" to also perform Sync customer.


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms