Update Service Order Did Not Work when Service Is Closed with Status Flag 0 (Doc ID 1558905.1)

Last updated on JULY 28, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.0]
Information in this document applies to any platform.

Symptoms

On :  BRM 7.3.1.0.0 version

The PCM_OP_PROV_UPDATE_SVC_ORDER opcode behaved unexpectedly when service status changed to closed with status flag 0 using PCM_OP_CUST_UPDATE_SERVICES opcode.

STEPS
---------
1. Create an account with multiple services
2. Change status of service A to 10103 with status flag 4 using PCM_OP_CUST_UPDATE_SERVICES opcode
3. Update service order event using PCM_OP_PROV_UPDATE_SVC_ORDER opcode
4. Change status of service B to 10103 with status flag 0 using PCM_OP_CUST_UPDATE_SERVICES opcode
5. Update service order event using PCM_OP_PROV_UPDATE_SVC_ORDER opcode

In step 3, PCM_OP_CUST_POL_VALID_STATUS called with input status value as 10103; but in step 5, PCM_OP_CUST_POL_VALID_STATUS called with input status value as 10100.

EXPECTED BEHAVIOR
-----------------------
Since the service status changed to 10103 in step 5, PCM_OP_CUST_POL_VALID_STATUS opcode input should have status value as 10103 instead of 10100.

 

Changes

 

Cause

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