Skip to Content
0

CK11N - Special Procurement - Stock Transfer - Updates both the plants

Dec 13, 2016 at 06:18 AM

146

avatar image

Hello,

We have a Special Procurement Stock Transfer issue, wherein Costing Run executed for one plant ESPL updates the values in another plant - BEPL. Below is the setup:

OMD9 Config

Plant ESPL

Special Procurement Type: A1 - Stock Transfer source BEPL->dest ESPL

Procurement Type: F

Special Procurement: U

Plant: BEPL

Costing Variant > Transfer Control > Cross- Plant

Strategy Sequence = 4 Period Based Transfer.

The Valuation Variant is not plant specific.

Material Master for plant ESPL : MRP2 and Costing 1 updated with A1 in Special Procurement Field.

This is not happening with all the plants. This looks to be wierd because Costing Variant Settings are not plant specific so if the problem happens it should happen for all the plants and not to specific plants. Is there something additional I have missed checking in the configuration? Kindly advise.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Bhaskar Basam Dec 14, 2016 at 06:10 AM
0

Have you created spl proc key for all your plants ?

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Yes Bhaskar, SPK is created for all the plants. Please let me know if there is anything more I need to check in the configuration.

0
Ratnakar Venkat Dec 15, 2016 at 12:12 AM
0
Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hello Ratnakar,

The system always is recalculating at source plant (BEPL), when they execute for destination plant (ESPL) - despite of just taking already released cost estimate from source plant (BEPL). \

For ex. executing CK11N in source plant BEPL - Costed, Marked and Released on Dec 21, 2016.

when executing CK11N in destination plant (ESPL) on Dec 22, 2106, the system is recalculating and saving the new cost estimate in source plant (BEPL) for the same date dec 22, 2016 - despite of just taking already released cost estimate (executed on Dec 21, 2016) from source plant (BEPL). Can you please advise?

0

In other words, the user do not want the system to calculate a new cost for material that already has a released cost estimate.

0

Below is the Transfer Control Setup

capture.png (8.2 kB)
0
Johannes Gierse
Dec 28, 2016 at 03:06 PM
0

Dear Sagar,

if you want to transfer the released standard cost estimate then you have to use the transfer strategy 'Current standard cost estimate'.
(Period-based transfer only considers cost estimate of the same costing variant/version/date).


Best regards,
Johannes

Share
10 |10000 characters needed characters left characters exceeded