cancel
Showing results for 
Search instead for 
Did you mean: 

BOM w/ ECM is recursive

0 Kudos

Hi all,

I created a BOM "A" with ECM number (CS01) and set 2 materials with subitem; "B" and "C".

I deleted "B" (CS02) one of those materials (w/ ECM also) because was wrong.

After that I created a BOM with ECM number for the material "B" and try to set the material "A" as a component. The system says that the BOM is recursive.

If I haven't deleted the material "B" from the BOM "A", it will be the perfect scenario of recursiveness. But the detail is that I deleted "B" from BOM "A" before creating the "B" BOM.

In STPO table, the material "B" still is considered as a component.

Does anybody know this issue? Do I have to open a ticket for SAP to treat BOM w/ ECM and recursiveness.

PS.: I've tested the same scenario without ECM and it worked perfectly (without recursiveness).

Regards,

Caio Gama.

A          after:    A

---B                    --C

---C

B

---A (error: bom is recursive)

Accepted Solutions (1)

Accepted Solutions (1)

sjeevan
Active Contributor
0 Kudos

Check the dates of your ECN you used.

If you deleted something with ECN does not physically get deleted from the table, it's just becomes invalid after the "valid from" date of ECN. If you delete a component without ECN then it gets deleted from STPO table and other related tables.

0 Kudos

Jeevan,

I understood well what you said. And it makes sense.

But in that case, that I've already deleted, or turned it invalid with ECM. There's a way that I can go back e make the component disappear from STPO and others?

I tried to change the BOM without ECM, but the material don't appear again in the BOM.

Regards,

Caio Gama.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Caio,

Did you use the same ECN to create and delete the BOM items? or different ECNs?

Are the valid dates of the ECN different?

Regards,

Senthil

0 Kudos

Hi Senthil, I used the same ECN to create both BOMs and delete the item from the first one.

The dates are from 01.01.1900 til 31.12.9999.

We use ECN because we work with ships and each ECN is for a different ship.

Thanks,

Caio Gama.

sjeevan
Active Contributor
0 Kudos

Please check the note 42891 - Recursiveness Check  point 2.

For reasons of performance, the system does not make any fine distinctions during the recursiveness check in the BOM explosion.

  1. BOM items of a bill of material are treated as being assigned to all variants of a variant BOM or as being assigned to all configured materials of a configured bill of material.

2. The effectivity (date / parameter effectivity) is not taken into account.

3. The plant is not taken into account.

4. The usage is not taken into account.

And I don't think you can make the deleted component B (with ECN)  re-appear in the BOM of A, so that you can delete it again without ECN.  Even if you add the component with ECN with same item number it's gonna change the STLKN (item ID in CS03) and STLPOZ values in STPO table. Basically system just looks at the table STPO_V01 for any entries.

I would suggest you to just check the box Recurs. allowed. to overcome this error.

(or)

You can make the deleted item appear again but it's by changing table values.

1. Go to SE16N in change mode (&sap_edit)

2. Enter STPO and execute for that bom number and delete the field values AEDAT and AENAM (note down the STLKN for that component)

3. Go to STAS enter bom number and STLKN for that component, you will see two entries one with LKENZ = X, just delete that line only keep the other one. (Normally STASZ of that line is higher than the one with LKENZ = blank).(When you delete a component with change number, system system will just adds a line to STAS with same STLKN but LKENZ = X)

4. Now go to CS02 without change number, your item B will appear, just delete the line item, it will get deleted permanently from table STPO and STAS and STPO_V01.

5. Delete the entry from STPO_V01 for the STLNR and STLKN combination from step 2

Try this first in your QAS and then do it in production.