on 03-30-2015 1:13 PM
Hi Experts,
According to Stefan Kiene statements, when we have CONTEND date assigned to contract and that date is fulfilled, system should deactivate such contract automatically. We’ve checked that issue and unfortunately, in our case it doesn’t work. We have a contract in our system which has CONTEND date set on 18.03.2015 and it still remains active:
We can see, that the CONTEND date is assigned:
Could you please support us with your expert knowledge? Are there any additional steps which have to be maintained in order to get contract deactivation automatically? We know, that in case of unlocking contracts there is a program which unlock contracts with expired lock date. Maybe there is similar program for expired contract deactivation? I’ve contacted with OSS and I received a response that there should be an action that make inactive the contract, a cancellation made from the UI or in case the contract has a scheduled cancellation it should be activated.
Could you please clarify which statements are correct if you have some free time? We would be very thankful.
With regards,
Mateusz
Hi Mateusz,
setting the contend date in the contract triggers the scheduling of deactivation steps of the ODI. These steps will then be picked up by report CRM_ISX_MSG_START_PLANNED.
Of course such steps will only triggered if the distribution schema contains steps assigned to the deactivation categories (P5/P6).
Once the contend date is set, the steps should be shown in the view Fulfillment steps.
In general, the report CRM_ISX_MSG_START_PLANNED should be scheduled as a job, e.g. for nightly run.
Regards, Carsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.