Solution : https://service.sap.com/sap/support/notes/131904 (SAP Service marketplace login required)
Summary :
When utilizing BOM explosion for component assignment in SAP networks and orders, users may encounter several issues, such as RESB table update terminations and arbitrary account assignment changes for new components. These problems occur due to the RESB table's design, which limits components to 9999 per network or order. Once this threshold is exceeded, existing RESB records are overwritten, leading to errors. SAP recommends using Transaction SE91 to create message 262, developing a new function module via SE37 to handle RSPOS checks, and implementing specific program changes. It's crucial to integrate related corrections from Notes 98893, 365954, and 119697.
Key words :
free rspos import parameter reference field rsnum_imp resb-rsnum rspos_imp resb-rspos export parameter reference field rspos_exp resb-rspos exception no_more_free_space 3, reservation number rsnum valid, function group cobc development class, short text check rspos, -digit numerator rspos, existing resb records, resb table occurs, resb table, rspos 9999, co_bc_check_rspos function module
Related Notes :
| 452656 | Termination with Message_Type_X when transferring components |
| 365954 | Note 131904 does not work with Note 98893 |
| 335447 | CN22/CN33: Termination with CN263 |
| 335409 | CN22/CN33: Termination CN263 when adding components |
| 132150 | Networks with some thousand components |
| 119697 | CO02, CO03: Performance reading the components |
| 98893 | CO02: SAPSQL_ARRAY_INSERT_DUPREC in table RESB |