Transferring Schedule Object After a Service Transfer (Doc ID 2643801.1)

Last updated on MARCH 05, 2020

Applies to:

Symptoms

After a service transfer from Account A to Account B,  the /schedule objected associated with the service is still pointing to the Account A, while it is expected that the /schedule object associated with the service should now point to the Account B since the service was transferred from Account A to Account B.

Steps to Reproduce:

1. Log in Pricing Center and configure a Plan with more than one service and associate each service with a unique balance group.
         * when transferring services from one account to another, the service's Balance Group should not belong to Account's Balance Group
2. Log in Customer Center and create Account A and Account B.
3. Purchase the Plan created above for Account A and configure the service with validity END dates in the future i.e. purchase_end_t , usage_end_t, cycle_end_t;
4. A deferred action will be created for Account A under the services tab.
5. Log in Developer Center and see that /schedule object is getting created for this deferred action with SYS_DESCR as "Telco delayed activation/deactivation" with when_t as PURCHASE_END_T;
         0 PIN_FLD_POID POID [0] 0.0.0.1 /schedule 351039 1
         0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 348255 0 - the schedule object assigned to the Account A;
6. The Service is transferred from Account to Account B with opcode PCM_OP_SUBSCRIPTION_TRANSFER_SUBSCRIPTION.
      Input Flist:
         0 PIN_FLD_POID POID [0] 0.0.0.1 /service/telco/gsm/telephony 350271 0 - transferred service
         0 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 352926 0 - billinfo for the Account B
         0 PIN_FLD_FROM_OBJ POID [0] 0.0.0.1 /account 348255 0 - Account A
         0 PIN_FLD_PROGRAM_NAME STR [0] "test"
         0 PIN_FLD_TO_OBJ POID [0] 0.0.0.1 /account 352414 0 - Account B
7. Log in Developer Center and see that the /schedule objected created previously for Account A is still assigned to the Account A even though the service was transferred to Account B.
        0 PIN_FLD_POID POID [0] 0.0.0.1 /schedule 351039 1
        0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 348255 0 - the schedule object is still assigned to the Account A;

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.