Device Disassociation From Service Makes TELCO_FEATURES And Service Status To Deactivation In Service Order
Last updated on APRIL 16, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
The dissassociation of a device from a service makes the TELCO_FEATURES and Service Status to (D)eactivation in SO (Service Order).
When an account has two devices (/device/num) with Brandband service (the service is having telco features). One device (/device/num) is disassociated from that service using CUST_UPDATE_SERVICES opcode. This is setting all the PIN_FLD_TELCO_FEATURES and service status to "D" in service order. After processing the service order these features are removed from the service.
The issue can be reproduced at will with the following steps:
- Create an account with the service having some provisioning tags and devices. This will create PIN_FLD_TELCO_FEATURES for the service.
- Disassociate the device from that service using PCM_OP_CUST_UPDATE_SERVICES
TELCO_FEATURES and service tag is set to D(eprovisioning)
Provisioning tag elements/telco features and service should not get D(eprovisioning). Only device status should be deprovision.
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