Issue due to missing value update indicator.

[Former Member]

While configuring new plant , value update indicator for one
material type was missed out.
Now goods receipts have been posted in the plant also the materials
have been moved out using sales order .

Now we corrected the configuration in  our testing client.
Value update indicator has been set for the material type.
But, due to stock postings done earlier with missing value update
indicator, table MBEW has not updated with stock and value.
Other stock tables MARD and MCHB are updated.

Now after value update indicator set in testing client, when we are posting goods
issue against delivery we are getting error 'valuated stok becomes negative:*-->see long text'.
Please suggest if there is way to update the MBEW table for stock
already existing in plant .
We will not be able to implement the value update indicator in GNP
with the error occuring since it will directly affect sales

Sampada V Desale

[JL23 · Accepted solution]

you know that you created an inconsistency in your system.

if you switc on valuation update while you have stock, this does not mean that the existing stock becomes valuated. this portion is foreever unvaluated. but each action made after the config change is valuated, hence you get the error when you touch the unvaluated portion of your stock.

There is only one way out of this. Deactivate the value updation again. remove all unvaluated stock, switch valuation update on again, reenter the previously removed stock.

It is certainly a very worse situation, and you should stop posting any movement to this plant immediately to avoid making the situation even worse.

You have to compare the quantity from MBEW table with total of quantity from MARD table per material, the difference is the non-valuated stock. this part has to be removed with e.g. 562, but only after you removed the value update again.

[Former Member · Accepted solution]

Thank you Jurgen.

But,a ll the materials are  excisable.

what will be the impact on excise if i remove the stock and uplaod it again??

Please suggest.

Sampada Desale

[ajitkumar · Accepted solution]

Is the GR thru Purchase order or Production / process order?

are you taking any cenvat credits?

if it is trading, are you passing on the excise cenvat to your buyers?

[JL23 · Accepted solution]

Sorry, I cannot answer that question as I am not familiar with excise. But it would really wonder me if  it did not allow to correct  incorrect entries

[Former Member · Accepted solution]

It is finished goods.

we are availng cenvat credit.

GR is posted against STO

[ajitkumar · Accepted solution]

Hve you utilized the credit or passed on the credit if there is trade?

for the 102 movement type document, you can create j1iS to create equivalent commitments,, like we do when an excisable material is stock transferred.

pl do a test in your test server, check the excise gls whether it meet your requirements

if not, you may have to rectify using J1ih,, excise JV.

[Former Member]

Thank you everyone for the reply.

It was really helpful.

I am following below steps to resolve the issue

1. Remove stock using MI10.

2. Implement the tick to update value

3. Upload the stock using MI10.

We are using customised report to display invoices with remaining qty in  RG23D (based on table-J_1IEXCDTL)

Excise details are updated propely.

[former_member192897]

You said its a Trading material that means you cannot take the credit. Excise value will load on the Material. You can pass on the excise to the customer.

And you said you are removing the goods using PID..That means you must create an Excise invoice in J1IJ and remove the excise and once you are done the correction and Repost the Stock and Update RG23D register again...

[Former Member]

Dear all ,

Thank u for the reply.

But as I said material has been sent out of the plant.

So it is not possible to reverse the documents.

Sampada Desale

[former_member192897]

Check the SAP notes 0000032236  and 00935755.

[Former Member]

Hii,

You will have to reverse all the transactions and create them all again in order to correct this.

Thanks

Lokesh

[former_member192897]

Reverse all the transactions and redo again once you have corrected the config. Give a try in dev server and revert back in case of any further issues.