Skip to main content

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).

Comments

  1. simran sahu29 April 2023 at 01:01

    This is the very nice post you shared, I like the post, thanks for sharing..@
    Packers and Movers Kharghar Sector 35!

    ReplyDelete
  2. tttanu45413 June 2023 at 02:36

    This is a very nice post you shared, I like the post, thanks for sharing.

    Movers and Packers in Kharar

    ReplyDelete
  3. JIO PACKER AND MOVER26 March 2024 at 04:28


    great post.

    Packers and Movers Kharghar Sector 11

    ReplyDelete
  4. JIO PACKER AND MOVER23 May 2024 at 02:58

    wonderful post

    Packers and Movers Kharghar Sector 19

    ReplyDelete

Post a Comment

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more

[SAP EWM] Adding custom fields for /SCWM/PACK Screen

If business want to add a custom field to the /SCWM/PACK screen and the requirement is that once business enter value here system will check against the weight in the material master  Step 1 : Structure /SCWM/S_PACK_VIEW_HUHDR need to be appended with the new custom field Step 2 : Then use screen enhancement /SCWM/UI_PACKING /SCWM/EX_WRKC_CHECK_BFR_HU_CMP to include logic specific to validation and updation of the table
Post a Comment
Read more