Solution : https://service.sap.com/sap/support/notes/672577 (SAP Service marketplace login required)
Summary :
In an SAP system, when updating Bills of Material (BOM), certain items may be auto-identified as recursive, triggering the STPO-REKRI flag to 'X'. This indicator becomes non-editable through maintenance transactions, even if the recursive condition is resolved, preventing modification. Recognizing types vary across transactions: in CS series, recursiveness must be flagged allowed via STPO-REKRS for creation, while CEWB doesn't check until post-save, possibly leading to irreversible BOM entries. The BAPI_MATERIAL_BOM_GROUP_CREATE function similarly postpones checks until commit. Remedial scripts are provided for analysis and resolution, including manipulation of recursive flags and, if applicable, re-calculation of BOM low-level codes.
Key words :
stlty stlnr stlkn stpoz postp posnr idnrk rekri rekrsitems, system automatically sets indicator stpo-rekri = 'x', system automatically sets indicator stpo-rekri, zzdis501 -> zzdis501zzdis502 -> zz_rekri_datazzdis503 -> zz_rekri_resetzzdis504 -> zz_rekri_analysewhile, initialize indicator stpo-rekri = 'x', initialize indicator stpo-rekri subsequently, message 'maximum low-level code 999, function module bapi_material_bom_group_create behaves similarly, initializing stpo-rekricreate report zz_rekri_reset, stpo-rekri initializationstart report zz_rekri_analyse
Related Notes :
| 140573 | Low-level code 999 for joint production |
| 68792 | Collective note for low-level code / recursiveness |