cancel
Showing results for 
Search instead for 
Did you mean: 

Planned order and Dep. Requirement (link is broken)

former_member789186
Discoverer
0 Kudos
291

Hello all,

We have the following scenario:

1. "MAT_TOP" is sold in plant 1111

2. "MAT_TOP" has procurement of "production in another plant" (plant 2222)

3. On plant 2222, "MAT_TOP" has "ASSEMBLY_01" as its component, this has procurement STO from plant 3333

4. On plant 3333, "ASSEMBLY_01" is produced internally and has "ASSEMBLY_02" as its component, this has procurement direct production

5. The "ASSEMBLY_02" has "ASSEMBLY_03" as its component and this has also procurement direct production

Below the scenario explanation in a more "visual way".


Problem now is:

1. We are still at the beginning of the production process, we only have a planned order for MAT_TOP on plant 1111 (there are no production or purchase orders across all plants, for the components yet).

2. If, for whatever reason, we want to run MD50 for the sales order, system plans the whole structure, passing through 2222 and 3333 plants --> correct

2.1 MD50 is ran with planning mode 3 and scheduling 2

3. Problem happens for the ASSEMBLY_03, system deletes the existing link between dep.req and planned order, planned order (old) is not properly deleted and the dep.req is correctly assigned to a planned order of the ASSEMBLY_02 material

I have found 2 SAP notes which somehow relate to this problem, but none offers a solution for our problem.

633119 - Dependent requirements without parent planned order

2047547 - MD04, MD05: Dependent requirement without planned order

Does any of you have any idea what else could be checked?

Any idea might be helpful, thank you.

BR,

Estevao.

Accepted Solutions (1)

Accepted Solutions (1)

former_member789186
Discoverer
0 Kudos

Topic solved - problem was with the value on "individual or collective requirements" (MRP4).

Material had 2 (collective), but in this case had to have 1.

Now on planning the sales order via MD50, the planned orders for the component ASSEMBLY_03 are being correctly deleted and created, with its assignments.

Answers (0)