Reconnection Short Dump

[Former Member]

Hi,

We are facing an issue, where reconnection of a DiscDoc is giving a short dump in PRD.

Based on our initial analysis we observed that the unreversed reconnection entries in DiscActivity table in EC86 transaction is the reason behind short dump while reconnection.But we are unable to reverse the existing entries and also to do fresh reconnection.

Please help.

Regards,

Thanu.

[ivor_martin · Accepted solution]

Hi Thanu,

Please let me know the current Status of the Disconnection Document (e.g. is it 21, 22, 30,... ?).

Depending on your status, I might be able to help.

Additional questions:

Are you using the ''Generate Reconnection Order'' feature? If so, please ensure that the Order code you are triggering does in fact exist - sometimes you will get a short dump if the Document cannot find the linked order code.

I will await your response.

Ivor martin

[Former Member]

Hi,

Thank You for your response.

The current status of the disconnect doc is 21(disconnection carried out).

By order code I guess you are talking about notification code.The one we use is Dunning Reconnection. which is already existing.

But there is Reconnection entry which is not reversed.

Pls let me know if you have any more questions.

Regards,

Thanu.