Skip to Content
author's profile photo Former Member
Former Member

Freight Vendor Specification during Inbound Delivery

Hi MM Gurus,

In MIGO, Goods Receipt Against PO, there is an option to specify the Freight Vendor if the relevant config is done at Condition type level.

However, in our Business, we are doing the Goods receipt using Inbound Delivery in VL31N/VL32N transactions. In VL31N/32N, is there a way to specify the Freight Vendor?

Our requirement is: To Enter a single Freight Invoice, for Multiple Bill of Ladings, for which the Material Vendors are different and freight Vendor is same. However, during creation of PO, we don't know who is going to be the freight Vendor. Also, partial PO receipts can be from different Freight vendors. So, we should have the ability to enter a single Freight Invoice (for a single Frieght vendor) with Multiple BOLs specified during inbound Deliveries. Material vendors can be different for different Inbound deliveries.

Please suggest a suitable solution. The requirement is very genuine. SAP provides the solution in MIGO, whether it has the solution when we do GR via Inbound Deliveries.

Thanks & Regards,


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 04:32 AM


    Change of Frieght Vendor while doing GR, is controled by THE FIELDS, Condition Category and Change of Vendor While GR in the Condition Type...this is for your Information....

    Now, for your requirement.....Goto VL31N and create the Inbound delivery and do the GR in MIGO, against this Inbound Delivery, instead of your PO( ie. As ref. document) and in MIGO screen, Item details, in Frieght Vendor can change the vendor ...

    Reward if useful



    Message was edited by:

    baskaran srinivasan

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 04:49 AM


    In M/06 while defining condition type for freight, select 2 Entry always possible for Vendor in GR. This will help you in two ways:

    If you don't maintain exclusively with a different freight vendor in the PO, it defaults to material supplier. However, while processing the gR, you can change the supplier. This feature activates a separate TAB in MIGO, Freight supplier. In this tab, you can change vendor.

    By maintaining shipping notification (or inbound delivery), you can process GR in MIGO with reference to Inbound Delivery. Still, you can process Freight Vendor conditions in GR with the above configuration done.


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Gopala,

      Please refer this notes : 199703



      As of Release 4.5A, it is possible to post the goods receipt for a shipping notification or for an inbound delivery not only using Transaction MB0A 'Goods receipt - Purchase order unknown', but also using Transaction VL32/VL32N 'Change shipping notification'.

      If, from an organizational point of view, there are no clear rules as to when you use Transactions VL32/VL32N/VL09, or when you use Transactions MB0A/MBST/MIGO to post goods receipts, the following problems might occur:

      Goods movement status and document flow of the inbound delivery:

      Goods movement status and document flow are not updated by Transaction MB0A. This is not possible for partial goods receipt postings from Transaction MB0A in particular, since Transaction VL32/VL32N always posts the goods receipt at the same time for all document items. Transaction VL32/VL32N does not post partial goods receipts. The goods movement status of the inbound delivery cannot be set to 'C' (= completed) due to the missing document flow.

      Check the inbound delivery before GR posting:

      Furthermore, when the goods receipt is posted using Transaction MB0A/MIGO, the system does not check whether the inbound delivery is in an appropriately consistent status and whether, for example, it has been put away completely before the goods receipt (Warehouse Management).


      If Transactions MB0A/MIGO are mixed with Transactions VL32/VL32N, you might have to take unintended duplicate goods receipt postings into account (for example, if the overdelivery tolerance has been set accordingly).

      GR posting and cancellation:

      If goods receipt postings from Transaction VL32/VL32N are cancelled using Transaction MBST, this can also cause document inconsistencies, since the delivery document flow is not updated in this case either.

      Furthermore, valuation problems occur with respect to shipment costs if the inbound deliveries are assigned to a shipment. (EKBZ)

      Assignment and reallocation of quantities reduced for planning purposes (DABMG):

      If goods receipts are posted with Transaction VL32/VL32N, you must make sure that GR assignment is activated in MM Customizing (in combination with the confirmation control key stored in the purchasing document) for the inbound delivery (Transaction OMGZ).

      If this is not the case, the status in the shipping notification might be contradictory to the current stock/requirements situation:

      For example, an inbound delivery might have status 'Completed' but at the same time it might still be displayed as a receipt element in the MRP list. In this case, you can no longer delete or change the inbound delivery.

      Return deliveries to the vendor

      You can create a return delivery to the vendor in Transaction MBRL (MIGO, with Return delivery as the material document) by setting the 'Create delivery' indicator (movement type 122). If the changes contained in Notes 491785 (Customizing+Coding) and 359247 (Customizing) are complete in your system, then all updates for VL32/VL32N are undone. Alternatively, you can create a new delivery using a returns item in the purchase order (Movement type 161). Other terms

      Inbound delivery, shipping notification, goods receipt, MB0A, VL32, VL32N, VL09, cancellation, MBST, DABMG, WBSTK, WBSTA, VBFA, GR, MIGO, MB01, inventory management, MBxx, mix, merge

      Reason and Prerequisites

      Cause: You switch transactions during the collection process ('Goods Receipt for Inbound Delivery' and 'Goods Receipt - Purchase Order unknown') or you switch transactions when reversing a goods receipt posting.


      Both functions for posting the goods receipt of an inbound delivery are planned in such a way that you can determine in advance which one is used to execute a business process. In the organizational processes, ensure that there is no switch between Transactions MB0A/MIGO and VL32/VL32N.

      The same principle applies for IDocs that use the source code of the corresponding transaction.

      When executing a business process, the transactions for posting the goods receipt may not be mixed up under any circumstances.

      If you maintained the movement types in Customizing for the item categories of the inbound delivery, the inbound delivery is automatically relevant for goods receipt posting using Transaction VL32/VL32N.

      In this case, the goods receipt must be executed using Transaction VL32, since Transaction MB0A does not update the document flow of the inbound delivery when the goods receipt is posted and as a result, the goods movement status cannot be changed to 'GR posted'. If you want to post the goods receipt using Transaction MB0A, you must not have maintained any movement types in the item category of the delivery item (View: V_TVLP, Transaction SM30) or set 'GR assignment' to initial in the confirmation control key.

      If you want to use Transaction VL32/VL32N for the goods receipt for the inbound delivery, you also have to set field 'GR assignment' = 'X' in addition to field 'Goods receipt relevancy' = 'X' in Ordering Customizing under 'Confirmation sequence'.

      Cancellation of goods receipts:

      Note that goods receipts that have been posted using Transaction VL32/VL32N can only be cancelled using Transaction VL09. Similarly, if you post using Transaction MB0A, these postings must be cancelled using Transaction MBST.

      Header Data

      Release Status: Released for Customer

      Released on: 28.11.2005 13:10:16

      Priority: Recommendations/additional info

      Category: Consulting

      Primary Component: LE-SHP-DL-LA Inbound Delivery

      Secondary Components: MM-IM-GR Goods Receipt

      LE-SHP-GI Goods Issue

      May be there could be some config.. I will try to check..

      Thanks & Regards,


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.