/SAPSLL/IF_EX_ECC_INBOUND~CUSTOMS_RELEASE Not Executed (ACE)

[dean_hinson2]

Hello,

Scenario, successful filing with ACE. The BADI finds message I1560 with CUCRS of 'A' and updates the Customs Release information. Customer realizes a mistake. Makes correction, send new M0410.

However, correction is wrong and message I1560 contains CUCRS of 'R'. The expectation is that the BADI is executed again, so that the Customs Release Information ids cleared. But it is not.

Is this a bug?

Regards, Dean.

[former_member215181]

Hi Dean,

I guess the developers would say that it's a feature, not a fault. As far as I can see, there's no functionality in the system for "unreleasing" a Customs Declaration. The logic for determining the release may be somewhat complex, depending on the country and message, but it either sets the release or it doesn't - there's no way to reverse the release if already set.

In my humble opinion, the US Customs logic is incorrect, or perhaps rather poor. In many other countries, with your example, the amendment would fail, but that failure would leave the Declaration in its existing (released) state. To amend the Declaration, you would have to send a valid message with valid data.

Does that help?

Regards,
Dave

[dean_hinson2]

Hello Dave,

My customer thinks that the original release status should be reset if an amendment fails. I see both sides. The amendment is not valid until accepted and when accepted the release status would be updated. I guess the question is what is the status of a filing in ACE if an amendment fails.

I will see if my customer can finds out.

Regards, Dean.