Skip to Content

Req.class/Check mode issue

Hi Experts,

I have created the custom "Requirement Class" in ECC. The availability check search methods in APO is based on the MRP type.

This setting has been made in the transaction ' Determination Of Requirement Types Using Transaction'

The issue is - in APO the check mode changes when the user changes the 'Requirement Strategy'  from strategy 10 (make to stock) to 40 (planning with finally assembly) in Material Master MRP screen.

ECC-For strategy 10 (make to stock) the default Req.class is 030 and It has assigned to 'Define Strategy' in PP

ECC-For strategy 40 (planning with final assembly) the default Req.class is 050 and it has assigned to 'Define Strategy' in PP

In this case the issue is - when I CIFF the materials at first from ECC to APO, The check modes are appearing in APO as standards -030 & 050. These are all copying from standards.

I need to go for all the hundreds of material then I need to change my custom CHECK MODE -K10 for all the thousands of materials.

Even If I change the check mode K10 manually for all the thousands of material at first time in APO then if the user goes to ECC material master data and changes any strategy from 10 to 40 or 40 to 10 then in APO check mode again populates the standard as maintained in the PP Define strategy.

APO check mode will not populate by default custom req.class K10.

My question is- Is there any enhancement/BADI available in CIF- no change happen in check mode in APO even if the material strategy changes in ECC frequently.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 14, 2015 at 06:59 AM

    Hi Prasnop,

    There are two ways to resolve this,

    One is to maintain configuration and assign custom requirement type to your Strategy 40 and 10 resp

    The Custom Requirement Type can be maintained as below

    You can maintain K10 Requirement Class to your custom Requirement Type.

    This Requirement Class is eventually transferred to APO as Checkmode.


    You can use the below user Exist to suppress the default Check mode getting cifed used during ATP check


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Prasnop,

      I would still suggest you to look at an option to achieve your requirement without using the ABAP development route.

      I see that you mentioned that for Standard product Availability Check is happening in ECC and for Critical product AV check is happening in APO GATP.

      Why don't you setup the check instruction of Standard (With Check mode) 050 - A in GATP with same as K10 - A, So that your X0 Critical material will perform required SETUP in APO box, While your Standard product will still 050 Requirement class details stored in ECC. ( Note unless your have activated IMOD for ATP Customizing we can maintain different setting for Requirement class in ECC  and Check instruction in GATP)

      If you still want to go ahead with the Customized check mode determination way then you have to do below changes.

      Note , the logic here is to suppress the standard Check mode determined during ATP check and replace it with your Custom Check mode based on certain criteria that you may define ( For Eg. X0)

      You need to maintain this detail in a Z Table in ECC side and read it every time in this include. If order item going under ATP check have same parameters maintained in the custom Table then you replace the standard Check mode that was being passed with your custom one.

      Note you have to take that this replacement is done only for your specific order items.

      the Advantage of this logic is that this is a dynamic Check mode determination and subsequent IMODs or master data changes related Check mode either in ECC and APO will not affect the final Check mode used eventually by the GATP.

      Note: You have to implement similar logic in other places too, for example for STO there is a different user Exit and during Order Save there is a different one ( EXIT_SAPLCSLS_002)

      I hope this helps in defining your own logic.