All deliveries attached to a shipment do not goods issue

[dominic_tomasetto]

Has anyone seen an issue in 5.0 where some deliveries attached to a shipment do not PGI? This problem occurs intermittently and seems to have no pattern. These are shipments that contain a large number of deliveries (55+) with many line items. An activity profile is triggering PGI from VT02N when the Shipment Start button is pressed. The PGI appears successful as no error is produced and there are no entries in the system or app log. However, in some cases we find that some of the deliveries attached to the shipment did not PGI.

Any help would be greatly appreciated.

[Shiva_Ram · Accepted solution]

Hi,

It looks the error log is not displayed for the deliveries that are not PGI'ed. Check the SAP notes 636681. The description is below;

Summary

Symptom

When you set a shipment status which triggers the goods issue for the deliveries of the shipment, the system does not display an error message if the goods issue posting was not successful.

For example the system displays message VW171 'Status 'Shipment completion' set in shipment &'.

After saving, the system displays message VW489 'Posting goods issue for delivery &'.

After you completed the transaction, the goods issue for the delivery is not posted, the shipment status is not set, but the system, however, does not display an error message which refers to that.

Other terms

VT02N, VT11, SAPMV56A, RV56ABST

Activity profile, goods issue

Reason and Prerequisites

Prerequisite

• For a shipment status (for example 'Shipment completion'), you created an activity profile in the Customizing, with which the goods issue is supposed to be posted directly 'Carry out goods issue posting during save'(Transaction 0VTL).

• The shipment contains at least one delivery for which the goods issue cannot be posted. For example, the picking is not yet completed.

• The corresponding status, which triggers the goods issue, is set for the shipment.

Cause

Error messages, which result from posting the goods issue of deliveries, are generally not displayed directly. If the goods issue cannot be posted for a delivery, the process is nevertheless continued and the shipment is saved, too. Only the status which triggers the goods issue posting is reset.

Solution

If you want to display information on the success of the activities, you can control this in the Customizing of the activity profile (Transaction 0VTL or Transaction SE38 by maintaining the variant for report RV56ABST). Three options are available in the 'Issue log during save of shipment' frame.

Select the second or third option:

• Issue log if errors or warnings occur

• Always issue log after save

Then, after the shipment is saved, the system displays a log in which you can find the messages for the error causes by expanding the individual rows.

Note:

The messages are only issued in the log in case of a direct goods issue posting, that is if you selected

• 'Carry out goods issue posting during save'

in the activity profile.

Header Data

Release Status: Released for Customer

Released on: 07-01-2003 19:56:59

Priority: Correction with low priority

Category: Consulting

Primary Component: LE-TRA-TP-PR Shipment Processing transactions

Affected Releases

Release-Independent

Related Notes

740989 - FAQ: Activity Profiles in Transportation.

[dominic_tomasetto]

Shiva,

Thanks for the information this is very helpful. The logging was already turned on in the variant for warnings and errors but I will active for all activity to see if these deliveries are somehow being skipped as opposed to failing PGI. Iu2019ll bump you up to full points if I can then identify the pattern.

The u2018Save Logu2019 (Display using transaction VT05) was not checked. Do you happen to know if that is the only way the log would be saved for access by VT05? To further explain, the u2018issue log if errors or warning occuru2019 radio button was clicked however the u2018Save Logu2019 (Display using transaction VT05) was not checked. Does that mean even if I had errors I would not see the log in VT05?

Best regards,

Dom