Multiple Characteristics for same material based on Plant

[Former Member]

Hi all,

The wrong characteristics are used whne creating the planned order because we have the same material in two plants with different chracteristics. The wrong characteristics are used because the plant is not used to determine the characteristics to be used.

Does anybody have an idea on how to rectify the problem?

I have researched in OSS notes and have found nothing. I am still searching in hope to find soemthing.

Help would be greatly appreciated.

Regards!

Curtis

[Former Member]

Hi all,

I found that the MD02 transaction creates the correct "plnord" components when not based on a delivery.

If there's a delivery with an item category ULN there's no problem it creates the components correctly.

But if delivery line item category ZNLN there's a problem because it does not get the correct components.

I looked at both item categories ZNLN and ULN. There's some differences. So I changed the config so that ZNLN

is the same as ULN. Re-tested but I get the wrong components.

Any suggestions?

Regards!

Curtis

[Ritz]

Dear Curtis,

i didnt understand the baisc of your problem.

classes and characterstic are created at client level, but when you assign them to material and create BOM its referance to exact Plant.

when you have created BOM and configuration profile at plant level the resultant configuration will result in the material list from the super BOM specific to that plant, if you are saying that materials selected are from another plant how is it possible do you have same lower level materials present in both the plants...?

same thing apply to sales order as every line item refer to specific plant so selection of material from secondary plant is out of question.

another thing is Item category is responsilbe for configuration possible or not , it never interfare in selection of component.

hope you understand my point.

It will be lot better if you explain in more detail whats happening including the master data settings.

hope it will help you.

Regards

Ritesh

[Former Member]

Hi Ritesh,

Thank you for your response.

We use Super BOM with object dependency.

Same material in two plants.

When we have a delivery STO we get the problem because it does not use the correct

material characteristics of the production plant but it uses the characteristics of the receiving plant.

If there's no delivery STO and only P.Req it works fine.

If we enter into the incorrect plnord with MD12 and go to EDIT-->EXPLODE BOM the correct

components are updated for the correct components.

If we save all is good now.

We do not want to do the reediting to have the correct data.

Any ideas?

Best regards!

Curtis

[Ritz]

Curtis,

I think i got clue for your problem.

just explain me what do you mean by * delivery STO * ...?

and If there's no delivery STO and only P.Req it works fine. explanantion of bolded line.

Clue is , if you are creating order in one plant and want the production do be done at another plant , during MRP the BOM is first exploring at first plant and selected the materials from that plant , if same component list is attached to the plan order at second plant which will do the actual production , but the plan order contain wrong components , when you do the re editing of that plan order , configuration run at that plant level and as per dependencies written in configiration profile it will pick the right materials.

Hope i am clear now, if its so revert back.

Hope it helps you.

regards

Ritesh

[Former Member]

Ritesh,

"Delivery STO" is Stock transfert order.

"P.Req" is Purchase request.

So, if the MRP runs for a purchase request we get the correct components.

if the MRP runs for a stock transfert order the MRP does not find the BOM configuration

of the receiving plant and does not refer to the BOM of the production plant.

Regards!

Curtis

[Former Member]

Ritesh,

If I was not clear before this is the scenario.

I have plant 1020 material 12345

Plant 1020 is the production plant for material 12345

The material 12345 exists in plant 1070.

The material 12345 in plant 1070 has no MRP.

Plant 1020 material 12345 config in MM03

MRP1 --> MRP Type = PD

MRP1 --> MRP Controller = G03

MRP3 --> Planning material = PLAN_1020_GR03

MRP3 --> Planning plant = 1020

Plant 1070 material 12345 config in MM03

MRP1 --> MRP Type = P3

MRP1 --> MRP Controller = 017

MRP3 --> Planning material = empty

MRP3 --> Planning plant = empty

The BOM in cs11 for plant 1020 material 12345

has 3 components

Comp#1

Comp#2

Comp#3

The Dependency is code

TABLE TB_1020_SUPERBOM (PP_nuance_interne = $ROOT.PP_nuance_interne,

PP_dim_billette_bom = $ROOT.PP_dim_billette_bom,

PP_CODE_LONG_BILL = $ROOT.PP_CODE_LONG_BILL,

pp_component_bom =$self.pp_component_bom).

The dependency is not found because it is looking for it in the plant 1070 and not the plant 1020.

When the MRP runs for a Delivery type stock transfer order I get

CONFIG_1020_BILLET <---- This is the BOM item component field in CS11 in the Basic data tab

Comp#2

Comp#3

instead of

Comp#1

Comp#2

Comp#3

Hope this explains better m'I situation.

Regards!

Curtis

[Ritz]

Curtis Marchand,

i have again few question.

if in plant 1070 there is no MRP how you are planning and producing materuial there.....?

as per my understanding , when ever you create order for configurable material system ask you to configure it and based upon your selection of values BOM is configured for that order, if your case as you are creating proposal in 1020 BOM is being created in the same plant. and it will have components from plant 1020 only.

now you please check the BOM of your header material in plant 1020 and 1070 for the components

Comp#1

Comp#2

Comp#3

what selection conditions are written.

i guess as in plant 1070 Comp#1 is not present in BOM thast why there is difference in production order.

Check and revert back.

Hope it helps you.

regards

Ritesh

[Former Member]

Ritesh,

Thank you for your support on this subject. It's very appriciated.

No the plant 1070 does not have a BOM so there's no COMP#1

The problem is that the MRP run's and cannot find the BOM for plant 1070 so it returns comp#1 not found.

This appens only when there's a Stock transfer order for production in 1020 to be shipped to plant 1070.

Regards!

Curtis

[Former Member]

Hi all,

In MD04 if there's an MRP element of type "Delvry" the incorrect characteristics are used.

In MD04 if there's no MRP element of type "Delvry" the correct characteristics are used.

The problem only occurs when there's a delivery.

The funny thing is that the configuration is ok but the components list is not correct if there's an MRP element type Delvry.

Regards!

Curtis

[Former Member]

More information on the case:

Planned order does not use the characteristics from the good plant.

We have the same material in 2 plants using variant configuration that are

different from one plant to the other.

Material 20001685 in plant 1020

Same material in plant 1070 ( requestor plant )

In MD04 plant 1020

We use object dependent to retrieve the component from a VC table using characteristics. In the present case, it looks that when the planned order is created to cover a delivery requirement, it does not use the characteristics of the production plant to retrieve the component but the characteristics from the receiving plant. The result of this is that the component cannot be retrieved and have a wrong material number that is carried out to the production order when converted.

Regards!

Curtis

[Former Member]

Hi

If we use different charectertics for same material in two plants, the easiest way is to create two different class with varying characterstics and use this class in the BOM Seperately.

Since the class and characterstic are at client level and plant independent you can have different characteristics for material with same class

Krishna

[Ritz]

Curtis,

The only solution available is you need to change process and adopt convention to identify charactersyics and classes valid for specific plant.

as this data is at Client level you cant distigvish them at planty leevl other then you can create them with diffeent name and discription which denote the plant in name or discription for example CHARA_1020 or CHARA_1070.

Characterstic and class group can also be used for this purpose.

Check and revert back.

Regards

Ritesh

[Former Member]

Could you give more details on the issue?

Class and chracteritics are defined in Client level as per my understanding unless you are maintainig the classification at BOM level.

regards

Ratan