Solution : https://service.sap.com/sap/support/notes/20434 (SAP Service marketplace login required)
Summary :
SAP Note clarifies the issue of update terminations flagged by "SAPSQL_ARRAY_INSERT_DUPREC" during the creation of new master data such as orders or projects, primarily due to inconsistencies between general object number management tables (e.g., ONR00, ONRKS) and specific application master data. The remedy includes avoiding isolated transports of these tables; instead, they should be transported as part of broader groups. Utilizing the RBONRRP1 program with specified procedures (starting in SA38, checking inconsistencies, and corrective actions) is suggested to resolve existing inconsistencies. Future recurrence should be checked post-correction by periodic re-execution of RBONRRP1.
Key words :
additional key words general object number, display error message kb 420, general object number management, object number management, display line items, object types v1, 'test run' parameter, affected object type, object type vb, incorrect client copy
Related Notes :
| 308670 | Creating funds centers: SAPSQL_ARRAY_INSERT_DUPREC |
| 301898 | CJB1: KD022 "Object number PRxx does not exist" |
| 201798 | ONR00 entries f.relationships frm versn not deleted |
| 160884 | Report for the deletion of project versions |
| 150465 | Archiving: SD_VBAK - archiving ONR00 ONRVB |
| 69831 | RBONRRP1:Mode of operation for sales orders (VB,VK) |
| 60523 | Classification data is not archived/BS503 |
| 31863 | Plan.interface for RKP2: Update termination |
| 27691 | Termination when copying planning data |
| 10217 | Object numbers missing in index tables |