Skip to Content

VL01NO - Default Shipping Condition

We are configuring a returns scenario without reference to any sales order based on a returns outbound delivery without reference. In order to accept the goods receiving point (different to the standard shipping point) in the same plant, a reference order type was configured that includes a different Shipping Condition to that in the customer master. This order type is then assigned to the returns delivery type.

However, when we run the scenario it is still determining the Shipping Condition from the customer and generating an error when we enter the plant in the delivery item.

I checked the copy control between the reference order type and the delivery type and it uses standard copy routine 301 for the Header Data transfer. So I placed a break-point againts likp-vsbed = xkomdlgn-vsbed but the routine does not appear to get executed when I create a delivery.

I have searched many posts and also OSS and not found anything related to this. It is a standard scenario for most organisations so I can only assume I have got something wrong.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 12, 2017 at 07:23 PM

    Hey Hows its possible to have a return of something; but with no referencing document;

    If you still want it in that way; then its not a return anymore. (return itself means i have sent something ; which is I am getting back so it will always have a referencing document ).

    Add comment
    10|10000 characters needed characters exceeded

    • We send serialized returnable packaging out with finished products against Sales Schedule Agreements. This is consigned to the customer via a 621 movement. Periodically they get returned either based on a shipping notification received via EDI or manual creation of the returns delivery. We do this on a 622 movement, which is why it is a return. We don't need to reference the Sales Schedule.

      The goods receipt is then transacted via an RF transaction. Even if we did reference the Sales Schedule, this would not solve the problem.