Scribd
Upload
106 views3 pages

E 20250317 (SNote)

The document addresses errors occurring during the creation of SAPoffice objects, specifically runtime errors related to duplicate records and database issues. It outlines a resolution process involving the execution of specific programs to correct inconsistencies in SAPoffice number ranges and customizing settings. Additionally, it references relevant SAP notes for further guidance on resolving these issues.

Uploaded by

Nepalsingh Bhayal Rajputh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
106 views3 pages

E 20250317 (SNote)

The document addresses errors occurring during the creation of SAPoffice objects, specifically runtime errors related to duplicate records and database issues. It outlines a resolution process involving the execution of specific programs to correct inconsistencies in SAPoffice number ranges and customizing settings. Additionally, it references relevant SAP notes for further guidance on resolving these issues.

Uploaded by

Nepalsingh Bhayal Rajputh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SAP Knowledge Base Article

1915614 - Dump or error message occurs while SAPoffice object (user, folder, document,
attachment) should be created
Component: BC-SRV-COM (Basis Components > Basis Services/Communication Interfaces > Communication Services:
Mail, Fax, SMS, Telephony), Version: 17, Released On: 30.12.2024

Symptom
While executing any kind of process which creates new SAPoffice object (folder, user, document, etc.) following errors occur:
Dump:
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
ABAP Program SAPFSSO6
...
Termination occurred in the ABAP program "SAPFSSO6" - in "SOFD_INSARR".
...
Source code Extract:
>>>>> INSERT SOFD FROM TABLE SOFD_ARRAY.
...

Dump:
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
ABAP Program CL_BCS_DOCUMENT_DB============CP
...
Termination occurred in the ABAP program "CL_BCS_DOCUMENT_DB============CP" -
in "PERSIST".
...

Dump:
Runtime Errors DBSQL_DUPLICATE_KEY_ERROR
Except. CX_SY_OPEN_SQL_DB
ABAP Program CL_BCS_DOCUMENT_DB
...
The termination occurred in ABAP program "CL_BCS_DOCUMENT_DB============CP",
in "PERSIST".
...
>>>>> insert sood from table lt_sood.
...

Error message:
Transaction Canceled SO 013 ( object_insert )
...

Error message:
Database error for <object_insert> <>
...
Error message:
Database error for <attach_insert> <>

Error message:
Error trying to create office for user
...

Error message:
The attachment has not been created
Message no. SGOS_MSG042
...

Error message:
No note was created
Message no. SGOS_MSG040

No mails are created (for example after a client copy)

Environment
As of SAP Basis Release 640
SAPoffice
Generic Object Services (Services for Object)

Cause
Inconsistency in SAPoffice number range objects.

Resolution
1. Call transaction SE38
2. Execute two programs:
1. RSSOPRRP without test mode to correct possible inconsistency in SAPoffice profile. For more info read SAP Note 834221.
2. RSBCS_NUMBER_RANGE (from SAP Note 1125583) without test mode to correct SAPoffice number range inconsistencies
Remarks:
Executing program in test mode shows the SAPoffice number range objects with status, where inconsistency is
highlighted with "red light"
"Number Range not in Use": Also make sure that certain number range objects should not have "Number Range not in
Use" as description for current year. This shows which number range objects are not in use. However for SAPoffice usage
some of these objects should have description "OK", which means number range object is correctly set in transaction
SNRO for actual year.
Example number range objects which should have description
"OK": SO_OBJ_ALI, SO_OBJ_BCS, SO_OBJ_EXT, SO_OBJ_FOL, SO_OBJ_RAW, SO_OBJ_SCR, SO_OBJ_USR, SO_O
3. Check the customizing settings regarding content repositories:
1. Go to transaction SKPR08 and check whether customer own new category is set for class SOFFPHIO. If yes, check this new
category in transaction OACT.
2. In transaction OACT search for this new category and check the content repository linked to it.
3. Check whether this content repository exist in transaction OAC0. If it is a logical repository, check whether a content
repository exist (in transaction OAC0) based on the symbolic repository of the logical repository.

For more info read SAP Note 530792

4. If issue still exist after executing these reports, implement SAP Note 2066358

See Also
3425357 - BCS: When you create a document, the runtime error DBSQL_DUPLICATE_KEY_ERROR occurs.

Keywords
Meldungsnr. SO013, Laufzeitfehler, Kurzdump, Nummerkreis, Datenbank-Fehler bei <object_insert>, Include FSSO6E01, GOS, number
range, RSBCS_NUMBER_RANGE, RSSOPRRP, SKPR08, SOFFPHIO, OACT, OAC0

Attributes
Key Value

Other Basis Components > Basis Services/Communication Interfaces > Generic Business Tools > Object links (BC-SRV-GBT-OBL)
Components

Other Basis Components > Basis Services/Communication Interfaces > Generic Business Tools > Generic Object Services (BC-SRV-
Components GBT-GOS)

Products
Products

SAP NetWeaver all versions

This document refers to


SAP Note/KBA Component Title

834221 BC-SRV-COM SAPoffice: Restore profile - report RSSOPRRP

530792 BC-SRV-GBT-GOS Storing documents in the generic object services

2066358 BC-FES-GUI Upload of front-end files is not possible - FILE_OPEN_DIALOG return table contains a blank entry

1125583 BC-SRV-COM BCS: Report to correct number range objects


This document is referenced by
SAP Note/KBA Component Title

2266569 How to update SAP Office number range objects SO_OBJ*

2593051 BC-SRV-COM SU01: Dump OBJECTS_OBJREF_NOT_ASSIGNED occurs when creating/deleting user

You might also like