Skip to main content

[SAP WM] 3259682 - Error L3344 during creation of transfer order from transfer requirement

3259682 - Error L3344 during creation of transfer order from transfer requirement

Cause

The function module checks to see if the action is allowable in background processing. Check in LT04 foreground for the Transfer Requirement which user input is required. For example, most commonly if there is a QM pop-up box, this can be the reason why background processing is not allowed. In that case it is not allowable by your QM-WM configuration

Resolution

  1. Please check your QM-WM config (tcode SE16-> V_T325) if you have an entry there for warehouse. 
  2. The entry should be set to allow background processing in 'Foreground/Background control for inspection sample dialog' (T325-DUNKL). 
  3. In order for that configuration to be read during background processing of the TR, it can be paired with the 'storage type search' configuration. 
  4. Maintain that by going to transaction SE16 -> V_T334T. Here, you could edit the relevant entry and set the value for 'QM Control' (T334T-QMSTE value). 
  5. This should link up the configurations correctly and help to avoid the error being raised in function L_TO_CREATE_TR. 
  6. Please ensure to also check with your configuration expert that any changes meet your requirements.

Comments

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

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