Solution : https://service.sap.com/sap/support/notes/140573 (SAP Service marketplace login required)
Summary :
The SAP Note addresses an issue where a recursive check fails to identify the responsible component, causing system termination with error "Maximum low-level code 999 reached". Applies to TCodes CS01, CS02, and programs SAPLCSRC, ZZDIS500. Caused by a programming error when joint production is activated. The solution replaces Note 128379 and involves implementing an Advance Correction from Release 4.6A, executing series of reports (ZZDIS502 to ZZDIS504) to generate and process a file of bills of material, updating and checking low-level codes, and manually correcting BOMs flagged as problematic. Enhancements in reporting processes include gap analysis and adjustment strategies for migrating systems.
Key words :
report zzdis503 corrects incorrect low-level codes, maximum low-level code 999 reached, recursion/low-level code reason, correctly assigned low-level codes, low-level codes assigned, existing low-level code ', proposed low-level code ', low-level code sequence, typical low-level codes, low-level codes disst > '900'
Related Notes :
| 720762 | Serialization of the BOM update/low-level code |
| 672577 | Initializing STPO-REKRI |
| 562360 | EWB calculates too large low-level codes |
| 544489 | FAQ Recursiveness check / low-level code assignment |
| 526841 | EWB: Create variant: Recursiveness is not recognized |
| 484640 | Update termination 29281: Maximum low-level code 999 reached |
| 309076 | Removing Note 128379 |
| 186216 | Incorrect low-level codes in table MDVM |
| 169358 | Incorrect low-level code: Error in CK11 |
| 68792 | Collective note for low-level code / recursiveness |
| 42511 | BOM: Error in low-level code assignment |