2014 Oct 08 3:28 PM
Hi Experts,
What is the expected standard behavior when you create a disconnection document thru a dunning activity, but there is already an existing disconnection document, lets say with status 20? or with status 30?
Thanks in advance,
Mario.
2014 Oct 10 7:21 AM
Hi Mario,
For status 20
When a disconnection document is created the object gets a disconnection status (I mean table entry is done relevant to this object), in a way its kind of locked with this document number. Now when I create another disconnection document for the same object then the system would take into account the lock status and thus if its a 1:1 scenario then you would have no other object to disconnect.
For status 30
The object is already released (reconnected) so disconnection can happen again.
Hope this helps.
Cheers,
Rakesh..
sapisurdg.wordpress.com
2014 Oct 10 7:21 AM
Hi Mario,
For status 20
When a disconnection document is created the object gets a disconnection status (I mean table entry is done relevant to this object), in a way its kind of locked with this document number. Now when I create another disconnection document for the same object then the system would take into account the lock status and thus if its a 1:1 scenario then you would have no other object to disconnect.
For status 30
The object is already released (reconnected) so disconnection can happen again.
Hope this helps.
Cheers,
Rakesh..
sapisurdg.wordpress.com
2014 Oct 10 2:11 PM
Hi Rakesh,
Thanks for the input, what would you say is the best way to determine if the customer is disconnected? by checking the status of the disconnection documents? or any other tip?
Thanks,
Mario
2014 Oct 10 2:59 PM
Hi Mario,
Yes, that would be quick and easy.
Table EDISCDOC would help with the Ref Object key and the status sorted to get the latest entry.
Cheers,
Rakesh..
sapisurdg.wordpress.com