Type Match in Customer Independent requirement

[former_member183783]

Hi:

We change our business from MTO to MTS for VC materials..then we use CIR(customer independent requirement)to trigger production..But seems VC material is not replace by variant in MD81? It works fine in VA01(sales order creation)...

Do I need to make some enhancement or MD81 doesn't support type matching?thanks..

[Rachel_Tang · Accepted solution]

Try to debug in MD81 when you come out from the configuration screen and set BP at:

Main Program     SAPFV45S

Source code of   FV45SFCO_CONFIGURATION_TYPE_MA

FORM CONFIGURATION_TYPE_MATCHING

...

  IF VBAP-CUOBJ NE *VBAP-CUOBJ.        "Hinzufügen Pos

    CHECK NOT TVAP-LTYPA IS INITIAL. <<<<<<<<

  ELSE.

...

Here, you can find the value of TVAP-PSTYV(sales document item category), then goto customizing:

Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item -> Define Item Categories

(Transaction VOV7)

Find the corresponding item category in the customizing and maintain the following data in the segment "Bill of Material/Configuration":

Config. Strategy

Mat. Variant Action

ATP material variant

Structure scope

Application

Then tick on the indicator "Variant Matching", after this try to create the CIR in MD81 again.

Regards,

Rachel

[former_member183783 · Accepted solution]

Hi,Rachel:

Great!!! It works perfectly...Thanks very much!

[Ritz · Accepted solution]

Hi Monst,

its good that you got solution.

but can you explain , if the varient matching was not activated earlier , how it was working for sales order?

Its the same setting needed for relacing material varient in sales order.

Thanks

Ritesh

[Rachel_Tang · Accepted solution]

Different item category.

[former_member183783]

hi,any hints ?

[Ritz]

Monst Yang,

can you explain , what do you mean by change from MTO to MTS?

is it just you stop creating sales order for product and want to achive same using CIR?

with this change have you also changed strategy group at material level?

as if its make to stock whay do you want to go against CIR , why not use strategy like 56.

the whole philosophy behind keeping MV and changing it during sales order creation is based upon qick reaction to customer requirement with available stock of MV.

but if you process is MTS , i better suggest change over to "BOM characterstic planning " strategy 56 use MD61 for planning.

check and revert back.

Hope it will help you.

Thanks

Ritesh

[former_member183783]

Hi,Ritesh:

I know your concern...Doesn't CIR should work as the same as sales order?It works as expected in sales order and the variant replace VC material in sales order,though the strategy group is not the same..

The reason is that,we use VC for our products and some of stable configure become variant.We need to use MTS to get better customer satifaction..That's why we use CIR...

Btw,the stategy group of VC is 56..I just create variants using 40 strategy..and these variant could replace VC in sales order while it doesn't in CIR..(That's what I mean by saying"changing MTO to MTS"）

[Ritz]

The reason is that,we use VC for our products and some of stable configure become variant.We need to use MTS to get better customer satifaction..That's why we use CIR...

once the configuration got stable , create a MV out of it and plan this MV as MTS product.

if customer create a sales order with KMAT and he choose the values corresponding to your MV , the replace ment will be done in sales order.

I still didnt understand why CIR's needed, if you are assuming CIR is one way to creating sales order then please check the programs this both transaction useses, VA01 & MD81, you will understand every function of VA01 cant be part of MD81.

Also as you said its 56 at header level then you are already in MTS , so whats this change

it means that you are creating PIR using MD61 for KMAT and then again creating CIR using MD81 expecting here MV will replace KMAT.

please check below defination for strategy 56 by SAP.

http://help.sap.com/saphelp_erp60_sp/helpdata/en/cb/7f9b7043b711d189410000e829fbbd/frameset.htm

take all this into account and revert back.

Hope it will help you.

Please mark threads helpfull , if it helps you.

Thanks

Ritesh

[former_member183783]

Hi,Ritesh:

56 is still the same as MTO..no sales order,planned  order is not allowed to convert to production...

Most of the configure can have Variant and we can plan MV and produciton /sales it..while the rest of configure still need to use VC ,since they are not required frequently...For these part ,we create CIR to produce first ..That's why we need CIR...

Seems the only way is to spend much time to read the code in MD81 now......

[Ritz]

Monst Yang,

are you creating PIR for KMAT's ?

which in turn non convertable plan orders for KMAT, and generating requirement for lower level assemblies.

when you will create sales order for this KMAT it will cvonsume PIR's you have created while planning, if here your KMAT's are replaced by MV , then the PIR's you planned will remain open then whats the use of such planning?

Strategy 56 is mainly used where we need to plan sub assemblies in advance to quickly react for cutomer requirement whihc sounds very similar to the MV concept , here you are trying to combine 2 very differnt business process and making it more complex with expectations of relacing KMAT's in CIR.

I suggest , better go with VC , create MV's for stable configuration, plan them using MD61.

or 

Use 56 , create PIR for KMATs , planned order by MRP , sales order which consumes this PIR.

and  use MD61 for MV's if at all required.

please mark threads helpfull , if it helps you.

Thanks

Ritesh