Skip to main content

delayed during TO confirmation and delivery status issue

At times, Business will face delay during transfer order confirmation and this might be occurred due to the handling units or data reasons and this might lead to inconvenience for business users.

SAP Support team suggested to enabled delayed delivery update functionality to fix this issue and below is the path to be followed :

Warehouse Management under Interfaces -> Shipping -> Shipping Control -> Shipping Control per Warehouse Number in the field Delayed Delivery Update.

In some rare cases, this update might impact on the transfer order confirmation, where status of the delivery will not updated even though picking is completed.

This need to be fixed by executing LX47.

Thank you.

Comments

  1. pavithra dass29 April 2019 at 05:44

    Hi,
    I must appreciate you for providing such a valuable content for us. This is one amazing piece of article. Helped a lot in increasing my knowledge.
    German Classes in Chennai
    German Language Classes in Chennai
    German Courses in Chennai
    German Language Course in Chennai
    AWS Training in Chennai
    Big Data Analytics Courses in Chennai
    Blue Prism Training in Chennai
    German classes in Tnagar

    ReplyDelete
  2. sap mm training28 January 2020 at 23:06

    Thanks for your information
    SAP FICO training in Chennai

    ReplyDelete
  3. Warehousing Express1 March 2020 at 05:06

    If you want to rent a warehouse for logistics storage then warehousing express is the best Warehouse service provider India. We offer top class logistics storage facility with tracking system. You can rent a warehouse for your logistics at affordable prices all over India.

    ReplyDelete
  4. BraxtonBayer13 December 2021 at 02:56

    I do accept as true with all of the ideas you have presented in your post. They are really convincing and can definitely work. Still, the posts are too brief for starters. May just you please extend them a little from subsequent time? Thank you for the post. conex for sale


    ReplyDelete

Post a Comment

Popular posts from this blog

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more