Hi ,
I have a recent issue which was related to data exchange task id being reused .
Elaborating the issue in our process which is related to Utilities Business when we create a New connection contract for electricity from SAP CRM we create a service notification which is then linked to the contract created.
when the status of the service notification changes a BADI is triggered which contains the logic to call the COMEV and then the COMPR which send the SO out to the market in form of idoc.
Ideally every date exchange task id should be unique because it is stored in Edextask table which has the datextaskid as the primary key.
In my case two new connection contract have been created for the same BP(Multi site. I.E: Like a Building which contains different premise) within a difference of 2 mins and two different service notification linked to two different contracts.
for the first one the datex task id is unique which leads us to idoc which was created for sending the details out to the Distributors.
for the second one the datex task id is reused(with the first one) which leads us to but obvious previous Idoc.
I am saying reused because the standard code which creates the datex task id would never generate a duplicate one bcoz of primary key concept.
I have debugged the scenario and tried changing the datextask id to previous one when it was generated.
Later when it goes ahead for saving in the table Edextask it gives an error.
Does anyone has been in this situation before?
Please help.
Regards,
Sumit