How To Fix M7359 - Movement type &1 is only possible with ref. to a delivery

M7359 - Overview

• Message type: E = Error

• Message class: M7 - Inventory Management and Physical Inventory

• Message number: 359

• Message text: Movement type &1 is only possible with ref. to a delivery

What causes this issue?

When you entered a goods movement, the system found that the movement
type entered <DS:CHAP.SIMG_OLMB_BWA_605>605</> requires a
<DS:GLOS.3526BEB2AFAB52B9E10000009B38F974>delivery</> via Shipping. You
therefore have to reference a delivery.
Possible causes:
You entered the movement type <ZH>605</> manually. However, the system
automatically creates this movement type for goods movements with
reference to a delivery.
The function module MB_CREATE_GOODS_MOVEMENT is incorrectly called up
by the system.

How to fix this error?

INCLUDE NA_EINGABE_PRUEFEN OBJECT DOKU ID TX LANGUAGE EN
INCLUDE NA_SYSTEMVERWALTUNG OBJECT DOKU ID TX LANGUAGE EN

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message M7359 - Movement type &1 is only possible with ref. to a delivery ?

  The SAP error message M7359 indicates that a specific movement type (denoted by &1) can only be executed in reference to a delivery. This error typically occurs when you attempt to perform a goods movement (such as goods receipt or goods issue) using a movement type that is restricted to being linked to a delivery document, but you have not provided a delivery reference.
  
  Cause:
  
  Incorrect Movement Type: The movement type you are trying to use is configured to require a delivery reference, but you are not providing one.
  Missing Delivery Document: You may be trying to perform a movement without having a corresponding delivery document created.
  
  Configuration Issues: The movement type may be incorrectly configured in the system, leading to this restriction.
  
  
  Solution:
  
  
  Check Movement Type: Verify the movement type you are using. You can do this by checking the movement type configuration in the SAP system (Transaction code: OMJJ). Ensure that you are using