sales order stock not able to use for delivery

[adwait_bachuwar]

Hi,

I am facing a issue for special stock of material.

During cut over activity some documents are created in system. One of them was a sales order and then stock was also uploaded for the sales order.

In our business special stock was required and hence stock was uploaded using 561E.

Now in between we had archived these material documents (561E). As an effect in MMBE we are able to see special stock for material but if we click on it no sales order number is displayed. The sales order is still active. At warehouse report that is MB52 sales order number is displayed.

Now when we are trying to do delivery for this sales order system is giving error message that "sales order stock does not exists" M7 184.

I am not able to do any type of movement with this stock.

I tried to correct this stock inconsistency using transaction MB5K and there were no records.

Please guide me how to get rid of this issue.

Thanks and Regards,

Adwait Bachuwar

[Former Member · Accepted solution]

Hi,

Could you explain why the material document of 561 E was archived?

Are you able to transfer the stock from sales order stock to own through MB1B 411E.

[adwait_bachuwar · Accepted solution]

Hi,

Yes definitely. In our system we archive all material documents which are 2 years older. In that process these 561E document got archived. I am still not sure why system did not give any error while doing that.

And for your second question no i am not able to transfer this stock. I am getting error that this stock for this sales order does not exist.

Thanks and Regards,

Adwait Bachuwar

[Former Member · Accepted solution]

Hi,

Do refer the below OSS Note, whether it can help you.

202345 - Transfer posting of sales order stock without sales doc.

Or better raise a request to SAP.

[adwait_bachuwar · Accepted solution]

Hi Mallinath,

I have already checked this note but in this one sales order is archived while in our case sales order is still active.

[JL23 · Accepted solution]

You can even archive material documents the day after its creation, there is no defined dependency.

And your error is certainly not caused by an archived material document.

I just wonder a bit why a sales order stock is lying for 2 years in your system, this is usually short term stock, goods issued very soon after its production, as it is specially produced for one sales order.

I am not in a SAP system today as we have a public holiday to double check the values from your screen shots with my system.

Right now I somehow feel that there is something wrong with the special stock number seen in your MB52 screenshot, there is a space between the / the the first zero

Also I do not see any batch number and special stock number in MMBE screen

Can you add a screenshot from your sales order, does it really have this number which is seen in the special stock field?

[adwait_bachuwar · Accepted solution]

Hi Jurgen,

Here is the screen shot of my sales order.

Yes the material is there and the sales order is also active.

Thanks and Regards,

Adwait Bachuwar

[JL23 · Accepted solution]

Is that a single problem or do you have the same problem for the other items in this order?

Do you have other sales order stock from your migration, do you have there the same issue?

[adwait_bachuwar · Accepted solution]

No we are not having issue with other items. All items are delivered only this one is to be delivered in system physically its already delivered.

[JL23 · Accepted solution]

Okay, let us try to look at it from a technical point of view.

use SE16, choose from menu Settings > user parameter

make sure you display it as SE16 standard list

do not activate the conversion exit.

Now execute it for table MSKA

Next do it for table VBAP

Compare the fields VBELN and POSNR, and CHARG if they are 100% equal.

[JL23 · Accepted solution]

I wonder why your MMBE does not show the batch number  in the hierarchy on the left.

[adwait_bachuwar · Accepted solution]

The fields in the tables MSKA and VBAP are matching except for CHARG.

Yes one point i forgot to mention that for this material batch mgmt is not active but in initial stock upload its been added.

[JL23 · Accepted solution]

This is an inconsistency.

And adding the MSKA with batch number is usually not possible if normal upload methods are used. This can only happen if direct table inserts are made with own programs.

You can only fix this error by doing direct table updates again.

There is no regular way to get around this.

[Former Member · Accepted solution]

Is this in production environment?

does some one updated entries in table.

If batch is not active you cannot put a batch number.

[adwait_bachuwar · Accepted solution]

Yes this is production system. So we have to do this by table update....Something i would not prefer.

[adwait_bachuwar]

Hi,

This is to guide everyone that which solution is used in order to get this issue resolved.

As per Jurgen's suggestion i have to make changes in MSKA table. I have removed this entry in the table and added this stock in MARD table so that we can utilize the stock and make delivery. As MARD table is updated the stock lies in unrestricted stock and could be used for any transaction.

[PhanikumarV]

Sorry if i interrupt when Legends talk...

can you please confirm-- for this item category YTA with special stock indicator is there or not

and activate the automatic batch determination in VOV7.

Then can you please Re-run the Availability at sales order level for this item..

Note: i saw the flag of schedule lines is active means not confirmed or more than one schedule lines.

So this error is expected..

If allocated sales order number and current sales order number differs--then we need to do this in other ways than normal.

Pl correct me if any...

Phanikumar

[JL23]

It is not about sales order number and availability, it is about having batch number in the stock record without having batch management activated for this material. This is just an inconsistency which cannot be repaired without direct table updates

[Lakshmipathi]

Try runing the correction report SDRQCR21

G. Lakshmipathi

[JL23]

No, this report cannot remove a batch number from table MSKA