Transaction MB1B - 309 Movement Backdate Posting Give Error Message ? Message No. M7021

[TSG]

Hi All ,

I try to do the movement 309 to previous month (Posting date 30th Jan) by using MB1B transaction. But system generate error message.

I checked previous month batch quantity by using t-code MB5B, but it have sufficient unrestricted quantity . MB5B Selection Screen and Out put.

output.

I debug the message and it will checked the MCHB table filed CVMLA values is grater than

the entered . in my case CVMLA values is 0 , because that is the reason it will give error message. .

Please any one have idea to resolve this error.

[TSG]

Dear Jürgen L,

Also I try to post them in 31st January , it also getting same error. at that time MB5B Selection screen and out put

for material 2000324,

Output

MB51 for As at date 07 FEB 2018 Total also 46

But MCHB Table MCHB table filed CVMLA value is 0.

system will check the CVMLA value is grater than 0.

system MB51 and MMBE batch stock are given same quantity 46.

Please do you have any idea why this MCHB table CVMLA value become 0. it should be 46. ?

[JL23]

MB5B is my most hated transaction, since there were hundreds of OSS notes with program fixes and this is still going on, I don't trust any number in this transaction. Post what I asked for.

IF you have today 46 and MCHB record has zero for the previous month, then it is obvious that those 46 must have been posted in the current month only, or had another stock status like quality or blocked in your previous month.

MB51 allows all users to add a column with the CPU date and time to the detailed report, and this helps together with document date and posting date to know the period the movement belongs.

And if you post the full movements then also explain what eventually used non-standard-movement types are used for.

[JL23]

Posting into previous periods just checks the period end stock. And my January ends on the 31st, while you showed the MB5B stock of the January 30. SAP does not at all look at daily stocks, they are not stored anywhere. SAP only checks if there is enough stock to issue from.

you cannot issue something on the January 30 if you have already issued this stock on the 31st and brought the total to zero. Your movement would make the movement from the 31st illogical, and the stock minus.

[former_member183424]

Be sure that you have stock as on date as well. System checks stock availability on the date which you are posting goods movement and the stock availability on current date. Let me give you an example:

Suppose you have done a goods receipt (mvt type - 101) on date 01.01.2018 for qty 10.

Then you have done a goods issue (mvt type - 201) on date 01.02.2018 for qty 10 and today's date is 06.02.2018.

Now if you check the stock availability as on date 31.01.2018 from MB5B, then you will be able to see the stock. But you can't post goods issue on any date.

[JL23]

MB5B is a calculated statistic, this logic is not performed when you post a movement and get above error.

SAP just checks what quantity you have in MCHB record for the given combination.

And as it is zero it is obvious that your result from MB5B is incorrect or had a wrong selection. Just use MB51 enter material number and batch number and execute, you should then see all movements from its initial receipt until today. And if this does not sum up to the current stock in MMBE then you have somehow an inconsistency.