cancel
Showing results for 
Search instead for 
Did you mean: 

STOs with split valuation by batches

Former Member
0 Kudos

I have split valuation by batches activated.

The system forces me enter a batch number(valuation type) when i am creating the STO.

It does not make sense, as the batch is really known at the time of shipping.

wE have reviewed all the relevant oss notes , nothing seems to work.

i appreciate if anyone has valuable inputs on this.

best regards

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello,

Note 66953 explains that during the creating of stock transport orders,

you must enter the receiving 'valuation type' (not the batch number).

The valuation type in a stock transport order is always mandatory in accordance with the following: (w/o OMF4 configuration of either ME21 or ME27 or ME21N)

The first step after posting the stock transfer PO is the goods issue.

In this step, the user is only able to type in the issuing valuation type. But the system also needs the receiving valuation type to post the value correctly.

This information can only be taken from the PO

item. So the valuation type in stock transfer orders is mandatory.

As you have pointed out other valuation types are proposed eventhough they are deactivated. This is normal.

In contrast, the first step after posting normal POs is NOT the goods issue, but the goods receipt. So the receiving valuation type can be typed in and you need not specify the valuation type in the PO item.

For normal POs the valuation type field 'required' can be configured using the field selection reference keys in transaction OMF4 (e.g. ME21 NBF), thereby making the field a required entry. However, a similar

customizing for field reference keys ME27, UBF is not effective.

Note 216904 describes the correction only for standard PO´s (w/o item category 'U').

Also, your description 2 describes the standard system

when creating PO's with split batch valuation and note 66953 addresses this.

I hope this information helped you!

Regards

David Merino

Former Member
0 Kudos

hello david,

i guess this is an SAP bug, i would need to work with SAP to get this fixed.

for other valuation categories , it makes sense to make val type mandatory in the PO,but for val category "x",

it does not make sense.

0 Kudos

Hello Srinivas,

Please review SAP Note No. 212532. It should solve the problem in case you use batches.

Symptom

When entering a stock transfer order with SD delivery, the valuation

type is a required entry even though at this point in the business

process the batches to be transferred are not yet known.

Hence, the valuation type for the goods movement is still not known as

well for separately valuated batches.

Reason and Prerequisites

This is not contained in the standard system.

****************************CAUTION******************************

This note may only be implemented in consultation with LO-BM

development. For this, you must create an OSS message under component

LO-BM-AI.

This Note changes the standardized type of evaluation for separately

evaluated batches in the event of a stock transfer. As a result of this,

the analysis reports in accordance with Note 32236 can no longer be

applied provided that there is stock in transit (goods in stock

transfer).

You must note in the OSS report relating to a suspected inconsistency in

the area of the inventory management that this modification Note has

been implemented.

Furthermore, the elimination of inconsistencies is liable for costs and

NOT part of the general maintenance with quantities or values for

materials that use this business process.

Moreover, you have to check after the import of a Support Package

whether all modifications of this note are still available completely.

The partial removal of these modifications may lead to inconsistencies.

***************************CAUTION**********************

I hope this information helps you!

Regards

David Merino

Former Member
0 Kudos

hello David,

this answer was very helpful for me.It could save us a RICEF.

As a coincidence, now SD is in scope for this project, we plan to use deliveries for STOs, so this note will help us.

best regards,

srinivas