How To Fix VR543 - Orders due for shipping are restricted by delivery block (see long text)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: VR - Output for SD Reporting

  • Message number: 543

  • Message text: Orders due for shipping are restricted by delivery block (see long text)

  • Show details Hide details
  • What causes this issue?

    You want to select orders that are due for shipping so that you can
    create deliveries and you only want to display those order items that
    have been blocked for delivery.

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    System Response

    The system only displays those order items in the list of orders due
    for shipping that meet your selection criteria and which have a
    shipping due date index.
    Certain business processes set delivery blocks and
    <DS:TRAN.OVB9>prevent</> the shipping due date index from being written
    (for example, a credit block). Therefore, they do not appear in the
    overview of orders due for shipping, although you have explicitly
    included the delivery block in the selection criteria.
    Orders with a delivery block in the order header normally never write a
    shipping due date index. They can only be delivered if you create a
    delivery online (transaction <DS:TRAN.VL01>VL01</>) and then, only if
    the delivery block in the order header has not been
    <DS:TRAN.OVLX>assigned</> to the delivery type that is used for
    delivering the order.
    If you have configured Customizing for table <DS:TRAN.OVLS>TVLS</> so
    that the delivery block is valid for the order, you can set the
    delivery block manually in the order header or it can be determined
    from the customer master.
    You can see an overview of orders blocked for delivery in transaction
    <DS:TRAN.V.14>V.14</>, or by going to the Sales menu.
    Regardless of the delivery blocks in the order header, when you create
    a delivery, the system also checks whether the ship-to party has been
    blocked for delivery by checking whether a delivery block exists in the
    ship-to party's customer master record that is assigned to the delivery
    type of the current delivery. This check can only take place if the
    order can be delivered at all, in other words, if there is no delivery
    block in the order header (and the delivery block is not copied from
    the ship-to party's customer master record to the order header, see
    above).
    General
    =======
    If the delivery block for an order or customer has been assigned to a
    delivery type, this can prevent you from creating a delivery (see
    below)
    If the delivery block is not assigned to a delivery type, you are
    normally permitted to create the delivery, but it then prevents certain
    subsequent functions, such as posting goods issue or picking.
    Delivery due list block (VL04/VL10):
    Transaction <DS:TRAN.OVLS>VL04</> also displays the shipping due date
    index of blocked orders in the delivery due list, for which the
    delivery block is not valid for the delivery due list (VL04) and
    highlights them in red.
    In an extended shipping due list, the delivery blocks in the order
    items are displayed as specified in the selection screen and output in
    the list. You can use a filter at item and schedule line level.
    Blocking a ship-to party after order entry:
    ===========================================
    Actual situation:
    If a ship-to party is blocked for delivery, the delivery block in the
    customer master record only affects the delivery of orders without a
    delivery block, if the delivery block has been configured in
    Customizing so that it is not automatically copied from the customer
    master record to the order when you create the delivery (tvls-speau =
    'X').
    Advantage:
    1. You can create a delivery manually by removing the delivery block
    that was automatically copied to the order, even if the customer is
    still blocked for delivery when you create the delivery.
    2. Orders that were entered before the ship-to party was blocked can
    still be delivered if the delivery block is copied from the customer to
    the orders.
    3. If you set the delivery block in the customer master record after
    you have created the order, it only prevents you from creating a
    delivery if the block is copied from the customer to the order.
    Disadvantage:
    You cannot block a customer by copying to the order or immediately
    prevent deliveries from being created for this ship-to party.

    How to fix this error?

    Choose the delivery blocks you require.

    Procedure for System Administrators

    <DS:TRAN.OVB9>Prevent</> shipping due index from being written
    <DS:TRAN.OVLX>Assign</> delivery block to delivery type
    <DS:TRAN.OVLS>Assign</> business processes for which the delivery block
    should be valid.
    Modification note:
    The SAP standard display of the extended shipping due index also
    displays schedule lines blocked for delivery, even if the open delivery
    quantity is 0. You can use a customer modification in the list profile
    to prevent this by setting the show_0_quan_blocked field to 'N'
    <DS:REPO.RV56SH08>MAIN(RVV50R1T)</>.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message VR543 - Orders due for shipping are restricted by delivery block (see long text) ?




    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker