Change of Lifecycle State for Subscription Service Doesn't Sync Lifecycle State for Member Services (Doc ID 2147448.1)

Last updated on AUGUST 07, 2024

Applies to:

Symptoms

If the life PIN_FLD_LIFECYCLE_STATE of a member service is changed first and thereafter if PIN_FLD_LIFECYCLE_STATE of subscription service is changed, the final PIN_FLD_LIFECYCLE_STATE are not in sync. Incorrect provisioning order xml are generated.
 
STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Create a account with a subscription service(/service/telco/gsm/certus_subs) and two member services(/service/telco/sbd, /service/telco/gsm/certus_voice). Initial PIN_FLD_LIFECYCLE_STATE is set to 200 in all services as part of account creation.

2) Change the lifecycle state of the member service to 240 by invoking PCM_OP_CUST_UPDATE_SERVICES with the below flist:

Result:
a) This creates two provisioning order xml one each for member service (/service/telco/sbd) and subscription service (/service/telco/gsm/certus_subs).
b) It changes member service (service/telco/sbd) PIN_FLD_LIFECYCLE_STATE to 200 (from 240 which was done in step 2) and subscription service PIN_FLD_LIFECYCLE_STATE to 240.

Expectation:
a) Should generate two provisioning order xml, one each for the subscription service (/service/telco/gsm/certus_subs) and member service (/service/telco/gsm/certus_voice).
b) There should be no provisioning order xml for member services which are already in state 240. eg in this case, there should have been no provisioning order xml for member service (/service/telco/sbd) which was already in state 240 (done in step 2).
c) The PIN_FLD_LIFECYCLE_STATE should be 240 for all services.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.