System behavior change about the recheck indicator (ITREC) of outbound delivery.

In this blog post, I would like to share some information about the recheck indicator (/SAPSLL/CUIT-ITREC) in customs document of outbound delivery.

The recheck indicator controls whether the customs document is relevant for rechecking or not.

“X” means relevant for rechecking.

” ” means not relevant for rechecking.

Old system behavior:

When posting goods issue for the delivery document, the recheck indicator is automatically changed from “X” to ” “. Means, the PGI doesn’t trigger the rechecking in GTS and it makes the customs document not relevant for rechecking any longer.

Generally speaking, the old behavior makes sense. But it is not always correct. Because the original legal control check for the delivery is based on the planned GI date. If the actual GI date is different from the planned GI date in delivery, the original legal control check is not valid any more. In this case, it is necessary to execute a new legal control check.

New system behavior:

Over the last few couple of years, several enhancements were made in outbound process in order to maximize the legal control check in goods issue posting, the logic is enhanced to force GTS performing a new compliance check if below condition are met:

1. 1> The good issue posting directly happening without the creation of outbound delivery
2. 2> The planning good issue date, or actual goods issue date is updated during good issue posting

In other words, when posting GI, the recheck indicator is not automatically changed from “X” to ” “. System will keep the value “X” and execute recheck during PGI.

After that, it is necessary to re-transfer the delivery to update the recheck indicator (to exclude these document already GI’ed from further checks in GTS). This is achieved by using the mechanism of follow on function.

After PGI, a new entry for the delivery will be added into table /sapsll/objssf as below:

It is needed to execute report /SAPSLL/SD0B_OBJSSF_PROCESS regularly in ERP side in order to flag the ‘recheck indicator’ in false for these documents, in another word, to complete the process in GTS side.

This is the new behavior. The logic is stricter comparing to the old behavior.

When is the behavior switched?

The new system behavior is delivered to SAP customers along with note 1941063.

The note is contained in the following support packages.

Note 1941063 is contained in my system, but I prefer the old behavior. What should I do?

This function can be disabled in ‘control setting of document transfer’ in ERP side:

If you don’t see this flag, please implement note 2249473 and 2236356 and then check again.

Best regards,

Hualin Zhang