Ansicht
Dokumentation

SIMG_XXLEIDWDSPLOCK - Allow Splits and Activate Lock During Goods Issue Posting

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

You can use this activity to define for clients that subsequent delivery splits are allowed in decentralized WM systems. This activity also lets you define whether the deliveries that were split should be locked during goods issue posting.

Verification of outbound deliveries that are split in decentralized WM systems is only possible if the outbound delivery is not packed in the central SAP S/4HANA system. You can accomplish this by selecting the same checkbox in the SAP S/4HANA system. (The above link leads to the activity in the IMG, but has no effect in the SAP S/4HANA system, since you carry out the activity in the WM system. You must log on to the SAP S/4HANA system.)

When goods issue is posted for an outbound delivery that was involved in a split (either a delivery that was created during a subsequent outbound-delivery split or a delivery from which other deliveries were split), the central system creates a verification and another delivery which is used as a reference for other goods issue posting.

If a delivery created during the split is posted to goods issue and the original delivery has not yet been posted to goods issue, the system uses the original delivery as the reference delivery and the delivery created during the split is created in the central system.

If goods issue has already been posted for the original delivery, the system selects the delivery that was split from the original delivery using the least number of splits as the reference delivery. This delivery must not have already been posted as goods issue itself, however. If several deliveries are eligible to become the reference delivery, the system takes the delivery that has the lowest number.

In order to make sure that the "not yet posted to GI" condition is met, the system also locks the reference delivery (in addition to the delivery that is to be posted to goods issue).

Therefore, the reference delivery cannot be processed. For example, it is no longer possible to confirm transfer orders for this delivery.

If this situation occurs often and severely limits your productivity, you can deactivate this lock in this activity. If you deactivate it, however, you must be extra careful not to post outbound deliveries to goods issue in parallel.

This only affects outbound deliveries and returns.

The subsequent outbound-delivery split is not normally allowed and the lock is normally always activated.

You must only permit subsequent outbound-delivery splits if you actually use them.

Leave the lock indicator activated initially. If you notice that this lock process creates workflow problems, deactivate it. If you deactivate this lock, we recommend that goods issue be posted by only one person, to avoid parallel processing.

BAL Application Log Documentation   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 2991 Date: 20240523 Time: 183110     sap01-206 ( 74 ms )