Skip to Content

Restriction during MFBF posting without standard costing run

Hi Expert,

How to restricted on posting of MFBF with out standard cost estimate. we are using both costing preliminary cost estimate (KKF6N) and standard costing (CK11N). when person has missed standard cost run estimate then during posting it will show any error for standard costing (CK11N).

Kindly suggest.

Best regards,

Santosh Sharma

Add comment
10|10000 characters needed characters exceeded

  • to get responses, please change your tag to something more appropriate e.g. FIN controlling

  • Hello,

    No need to go for enhancement. Please go to OSP2, REM profile, setting can be done in backflushing under cost accounting tab, you need to activate "Post activity according to Standard cost". Settings this would put a check on MFBF confirmation posting without standard cost release.

    Best regards

    Shailesh Mishra

  • Get RSS Feed

3 Answers

  • Dec 05, 2016 at 02:01 PM

    You need to build a enhancement at t-code MFBF. When you execute MFBF t-code, the system should check the stnd cost estimate for the given material in KEKO and KEPH. You need get help with with your CO person to develop enahacement.

    Regards

    Bhaskar

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 12, 2016 at 07:53 AM

    Thanks, Bhaskar

    I need to implement enhancement on KEKO table, in this table there is showing flag for standard costing release periodically in filed FREIG.

    Regards,

    Santosh Sharma

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 09, 2017 at 09:10 AM

    No need of enhancement. Requirement can be mapped through customization settings.

    Go to t code OPS2, for backflushing under cost accounting tab, activate 1) Post activities according to standard cost estimate.

    Settings this, materials must have released standard cost estimate else error will get triggered.

    Best regards

    Shailesh Mishra

    Add comment
    10|10000 characters needed characters exceeded