3/26/25, 5:05 AM

Application Server Infrastructure

Generated on: 2025-03-26 05:05:29 GMT+0000

Support Content | 1.0

Public

Original content: https://help.sap.com/docs/SUPPORT_CONTENT/si?locale=en-US&state=PRODUCTION&version=1.0

Warning

This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.

For more information, please visit https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit SAP Help Portal. 1
 3/26/25, 5:05 AM

BC-SRV-COM Communication Services - SAPconnect - Mail, Fax, SMS, Telephony

NEW BC-SRV-COM WIKI AVAIBLE

Please visit the new BC-SRV-COM Wiki as it is the more updated and maintained one: Sapconnect Interface Informations
Guide

Purpose:

Welcome to the BC-SRV-COM WIKI, the starting point for topics around SAPconnect and communication services. This area also
covers SAPftp and SAPhttp.

Overview:
SAPconnect provides a standard interface for external communication, which supports sending using telecommunication services,
such as FAX, pager (SMS), Internet and X.400, as well as sending to printers and between several SAP Systems. This Wiki hopes to
help you understand how this process works and assist with many of the configuration issues and errors you may encounter.

Section 1

Here are the following pages available:

COMMIT WORK - SO672 - Still no entry in queue

Communication Services Common Issues (BC-SRV-COM)

Delete Private User Folder in SAP

How to capture the MIME data

How to create traces in SAPconnect issues to get more information

How to define a job for sending messages via SAPconnect

How to reduce the size of table SOFFCONT1

SAPConnect Administration (SCOT) change log

SAPoffice objects disappear from shared folder

How to configure SAP to send external mails

SCOT - SAPconnect Administration

Secure File Transfer Protocol - SFTP

SOST - Send Request Overview

TCodes for SAPoffice

This is custom documentation. For more information, please visit SAP Help Portal. 2
 3/26/25, 5:05 AM
Transaction SCOT - New layout (SOADM)

Transaction SO12 Private Office settings

Transaction SO15 and SO23 - Distribution lists

Transaction SO16 Shared Office Settings

Type 'SAPFTP_SERVERS' is unknown

Related Content:

Related documents:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/d925bf4b8a11d1894c0000e8323c4f/frameset.htm

Related SAP Notes & KBAs

SAP note 455140 - Configuration of e-mail, fax, paging or SMS using SMTP

SAP KBA 1639935: How to capture the SAPconnect trace

SAP KBA 1641800: How to delete 'Has links to GOS/Document not sent' documents from the Hidden folder.

SAP KBA 1827878: Status of messages not updated in SOST

SAP KBA 1861133: The address to which a DSN is sent

COMMIT_WORK - SO672 - Still no entry in queue

Purpose:
This Wiki is to explain why a COMMIT WORK is required in the sending application when sending messages from the SAP system.

Overview:

When an COMMIT WORK is missing in the sending application, this can lead to messages failing in transaction SOST. In this Wiki I
will be going through the errors this leads to and also how to resolve the issue. Error related to an missing COMMIT
WORK are usually seen in custom programs.

Section 1:

Messages will be seen in the send queue in SOST with status 'SO672 - Still no entry in queue'. This message points towards to a
lack of an explicit COMMIT WORK in the sending application.

This is custom documentation. For more information, please visit SAP Help Portal. 3
 3/26/25, 5:05 AM

Section 2:

To view these mails you will have to select the option 'Still Not Entered in Queue' through the 'Further' button in transaction SOST,
please see below:

Section 3:

The first step here is to check if there is an COMMIT WORK is present in the sending program. It is necessary to execute the
COMMIT WORK after the call of the send interface to save the persistent objects.

Section 4:

A common mistake is to call the COMMIT WORK during the program, the 'COMMIT_WORK' = 'X' should be set AFTER the send
function.

Related Content

Related Notes:

SAP KBA 1895298 - SO672 - Still no entry in queue

SAP note 489286 - External send error after upgrade to 6.10 or higher

SAP note 717265 - Sending in PERFORM-ON-COMMIT as of Release 6.10

SAP note 1041227 - Object pool: Persistent objects are not saved

This is custom documentation. For more information, please visit SAP Help Portal. 4
 3/26/25, 5:05 AM

Communication Services Common Issues(BC-SRV-COM)

1. After system copy or client copy while creating new objects(user, folder, documents), dump
SAPSQL_ARRAY_INSERT_DUPREC occurs.

A) Run report RSBCS_NUMBER_RANGE

2. Internal error: SO_OBJECT_MIME_GET Exception: 0, No MIME Document Received. Error Code: MNA_DOC.

A) SCOT-> define corresponding codepage for SMTP node.

3. Internal Error: SO_OBJECT_MIME_GET Exception: 0, No MIME Document Received. Error Code: MIME_BCS or Error Code:
SENDER_BCS.

A) SCOT-> Setting->set default domain.

4. Internal Error: SO_OBJECT_MIME_GET Exception: 0 , No Send Order Exists -> Termination

A) No 'COMMIT WORK', refer to note 429427.

5. Cannot display full recipient mail address.

A) The recipient field length in SCOT is 35 characters, it's a restriction, but it's only a display problem, should not affact mail
sending.

6. The scheduled job to send emails out seems to hang and the emails are not sent out successfully.

A) STOP the send job in SM37. Make sure that this job is not running and then delete the lock in table SXDISP (transaction SM12).
Regarding the details please refer to note 855545.

7. Error in job SAPCONNECT INT SEND, GETWA_NOT_ASSIGNED .

A) The jobs terminates with GETWA_NOT_ASSIGNED in CREATE_PACKAGE

In this case you should check the variant of the send job and check if the standard settings are working correct:

Maximum Package Size 1.000

Minimum Package Size 20

Maximum No. of Send Requests 20.000

Timeout Factor f. Send Request 2

Timeout Offset for aRFC 100

CommitAfter 1

8. Sending mails from SAP system to an external mail address through SMTP node, following error status can be seen
in transaction SOST for some send requests:

XS802
XS812
XS806
XS829

A) Contact the mail server administrator to check the relay settings of the mail server. refer to note 1496168.
This is custom documentation. For more information, please visit SAP Help Portal. 5
 3/26/25, 5:05 AM
are working.

9. Using sapftp the following error can be seen : "User xxx has no access authorization for computer xxx"

Please check note 1605054. According to this note the table SAPFTP_SERVERS must be maintained to be able to use sapftp. (FTP
Server whitelist) Maintain this table and check whether error still occurs.

10. Read Receipt is allways set for outbound email. Read notification is allways ask while open the email which was received
from sap system.

Please read the KBA 2161462 How does Read Receipt work in SAPConnect?

Delete Private User Folder in SAP

Purpose
This purpose of this wiki is to tell you how to delete the private folder of a SAP user.

Overview
There are reports available to delete this information.

Section 1
Execute transaction code SE38. Fill in the field with RSSO_DELETE_PRIVATE and click execute. Then choose the appropriate
selections for your needs and execute to delete the data.

Section 2

If you use report RSSO_DELETE_PRIVATE, report RSSODLOLD is no longer necessary. All of its functions are included in report
RSSO_DELETE_PRIVATE and it also contains enhanced selection criteria for the selection of documents.

Related Content

Related Notes:

SAP note 922671 Deleting folder entries

Distribution list in the Hidden folder

Purpose
The purpose of this page is to describe an unique scenario that was encountered with the SAPoffcce hidden folder.

Overview

This is custom documentation. For more information, please visit SAP Help Portal. 6
 3/26/25, 5:05 AM
In certain circumstances, when documents are sent, they are stored in hidden folders. These folders cannot be accessed from the
Business Workplace (or transctions SO15/SO23).

Section 1

Due to this the contents of the hidden folder cannot be deleted and so some SAPoffice tables grow quite large, which can cause
performance issues. The SAPoffice re-organization report RSBCS_REORG does not delete any entries by itself.

Section 2
The SAPoffice hidden folder contents are flagged for deletion with report RSSODFRE and the actual deletion is carried out by
report RSBCS_REORG..

Section 3
We had an unusal incident where some documents in the hidden folder were distribution lists. Normally distribution lists are either
located in a private folder (private distribution lists) or in a
shared folder (shared distribution lists). So as no distribution lists are usually located in the hidden folder the report RSSODFRE
does not flag them for deletion. To resolve this issue a report must be written which will move all distribution lists from the hidden
folder to a new created folder in the shared folder area.

Related Content

Related Documents
SAPconnect

Related SAP Notes/KBAs

SAP Note 567975: Hidden folder: Reorganization

__________________________________________________________________________________________________________

Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.

How to capture the MIME data

Purpose

The purpose of this Wiki is to give steps on how to capture the MIME data of a message sent via SMTP from the SAP system

Overview

The following will explain the details of why MIME data is useful and also outline the steps required to capture the MIME data of a
message in SAP.

Section 1
MIME (Multipurpose Internet Mail Extensions) data of a document can very useful for analysis purposes and also some customers
may want to have the MIME data always available (this may cause problems in the system if mass emails are sent from the system
in question). Basically it allows many pieces of different data types to be sent in one message (e.g. a picture, Word doc and Excel

This is custom documentation. For more information, please visit SAP Help Portal. 7
 3/26/25, 5:05 AM
doc) and it then tells the recipient's email client what format the data is in so they can know how to display all parts of the
message.

Section 2
In the SAP system the report RSCONN06 can be used to switch on/off the saving of the MIME data of outbound/inbound e-mails.

Section 3

Now when a e-mail is sent from the SAP system the MIME data will be saved. To view the MIME data of an outbound mail goto:

Transaction SOST -> highlight the mail in question -> right mouse click on the send request -> select menu entry "Disply MIME
representation" -> MIME data will be seen

Section 4
To view the MIME data of an Inbound mail:

Transaction SOIN -> highlight the mail in question -> Click on the MIME icon on the right

Related Content

Related Notes
SAP Note 706328: MIME version: No additional information available

SAP Note 845449: MIME: Only message headers should be saved

SAP Note 1045882: MIME format is not displayed

SAP Note 1666970: MIME document not stored for incoming message

How to create traces in SAPconnect issues to get more information

How to create traces in SAPconnect issues to get more information

Introduction
1. SAPconnect trace
2. ICM Trace
3. MIME Representation
4. SXDUMP Trace
5. Telnet Test

Introduction

While using SAPconnect interface to send or receive send requests (faxing, mailing, etc.), problems can occur due to
-Software bug
-Wrong configuration
-Interaction with other external communication partners (like fax or mail servers).

To get more information about the problem and to identify the location of the possible cause some useful tracing options are
available in SAP.
Take into account, that these tracing methods are helpful if the send request reached the outbound (transaction SOST) or inbound
(transaction SOIN) queue.

List of most common scenarios and advised tracing options:

This is custom documentation. For more information, please visit SAP Help Portal. 8
 3/26/25, 5:05 AM
-Outgoing send request through SMTP node not sent: check point 1, 2
-Outgoing send request through SMTP node sent with incorrect attributes/content: check point 2, 3
-Outgoing send request through RFC node not sent: check point 1
-Outgoing send request through RFC node sent with incorrect attributes/content: check point 1, 4
-Incoming send request through SMTP not received: check point 5
-Incoming send request through SMTP received with incorrect attributes/content: check point 3

Top

1. SAPconnect trace

It can be activated for outgoing and incoming send requests also:

-Transaction SCOT
-Menu: Utilities > Trace Settings (in SAP Basis version 700 and higher)
OR
Menu: Utilities > Trace > Internal Trace (in SAP Basis Versions lower than 700)

For more info to create sapconnect trace read the sap note 194926.

After activating the trace reproduce the steps which led to the problem or resend the incorrect send request with button "Repeat
send" in transaction SOST.

Trace can be checked for outgoing send requests as follows:

-Transaction SOST
-Select the appropriate send request
-Push button "Trace"
-Double click on the line "Trace ID"

Trace can be checked for incoming send requests as follows:

-Transaction SOIN
-Select the appropriate send request
-Push button "Trace"
-Double click on the line "Trace ID"

Display the list containing all sapconnect traces:

-Transaction SCOT
-Menu: Utilities > Trace Selection (in SAP Basis version 700 and higher)
OR
Menu: Utilities > Trace > Internal Trace >> Button "Display"

Sending SAPconnect trace to the SAP:

- When you display the trace click on the "Local File(CTRL + Shift + F8)" button
- Save the trace in TXT format
- Send the TXT file

Top

2. ICM Trace

If send request goes through SMTP service, the ICM trace can also help to identify the problem.

Steps for creating ICM Trace:

-Transaction SMICM

This is custom documentation. For more information, please visit SAP Help Portal. 9
 3/26/25, 5:05 AM
-Menu: Goto > Trace File > Reset (deleting the trace to have the most current trace)
-Menu: Goto > Trace Level > Set
-New Trace Level: 3
-Button "Change"
-For outgoing mail: create a new send request (mail, fax, sms) and send it or resend (button "Repeat Send") an existing, failed send
request from transaction SOST.
In any case use the button "Start send proc. for selection" in tr. SOST for manually executing the send process on the appication
server, where the icm trace was activated (icm trace is application server dependent)
-For incoming mail: from mail client (Outlook, Lotus Notes, etc.) send a mail into SAP System
OR send a test mail via telnet test into SAP System as of point 5 (Telnet test, SAP Note 607108).

Keep in mind, that this trace can increase rapidly. So after activating the trace reproduce the error immediately. Afterwards set the
trace level back to 1 (default value).
See this page for instructions for the ICM trace analysis.

Sending ICM Trace to the SAP:

- When you display the trace in Tr. SMICM->Goto->Trace file->Display All(Shift + F5) click on the "Local File(Shift + F9)" button
- Save the trace in TXT format
- Send the TXT file

Top

3. MIME Representation

Using SMTP node, send request attributes/content can be checked with MIME representation.

Activate MIME creation as follows:

-Transaction SE38
-Execute report RSCONN06
-Set checkbox "Always Save" based on the situation (incoming or outgoing send request)

Afterwards create a new send request and send it to the recipient.

(either from SAP to an external recipient or from outside to an SAP system)

Displaying MIME representation for outgoing send request:

-Transaction SOST
-Click right mouse button on the newly created send request
-Choose "Display MIME Representation"
Displaying MIME representation for incoming send request:
-Transaction SOIN
-In last column "MIME exist" click on the icon "Display MIME"

Sending MIME representation about incoming or outgoing send request to SAP:

- When you display MIME click on the "Save as local file" button and save the MIME in TXT format
- Send the TXT file

Top

4. SXDUMP Trace

For checking documents sent through RFC node, create the SXDUMP traces as of sap note 320503.

This is custom documentation. For more information, please visit SAP Help Portal. 10
 3/26/25, 5:05 AM
Important informations regarding SXDUMP:
-Create SXDUMP node in transaction SCOT with same settings/attributes, as the original node
-For SXDUMP node set a specific recipient address in address area, so that the send request with this recipient goes through the
SXDUMP node
-Create an RFC destination in transaction SM59, which calls sxdump.exe on frontend
-Send process should be started manually from transaction SOST by the user, who installed sxdump.exe file on own PC. SXDUMP
files will be created on this PC with the configured target file types, like TXT, PDF, etc.

Top

5. Telnet Test

For problems receiving send requests in SAP system through SMTP node, the telnet test is a useful method to check whether or
not the SAP system is able to receive mails.
For telnet test check sap note 607108.
If the telnet test is successfull, the system is correctly configured to receive mails.

Top

How to define a job for sending messages via SAPconnect

Purpose

This wiki is to give the steps to create a job to send messages from the SAP system.

Overview

If a job is not defined to send messages from the SAP system then they will stay in a Waiting status in the Send queue in
transaction SOST. These messages also could be sent manually from SOST.

Section 1

The following will define a background send job that will send all messages types (e.g. e-mail/fax/etc) from the SAP system:

Please goto SM36 ->

Job Wizard ->

Job Name "SAPCONNECT_SEND" ->

Job Class "C" ->

ABAP Program ->

ABAP Program "RSCONN01" ->

Varient "SAP&CONNECTALL" ->

Release immediately ->

Periodic Job "Flagged" ->

None of the above "flagged" ->

This is custom documentation. For more information, please visit SAP Help Portal. 11
 3/26/25, 5:05 AM
Other Periods ->

5 Minutes (This is the maximum run time for this program) ->

Complete

Related Content

Related documents

Send Processes

How to reduce the size of table SOFFCONT1

Purpose

The table SOFFCONT1 can often become quite large in the system and needs to be reduced. The following wiki will provide means
to do so.

Overview
The table SOFFCONT1 is the database table used by SAPoffice and KPRO to store content related to storage category SOFFDB,
that contains the attachments from all messages that are sent from SAP (fax, email etc..) and this is why it will become quite
large. Storage in table SOFFCONT1 is only the fall back solution, when no content server is present. Please see note 530792 for
more information.

Section 1

There are 2 ways to reduce SOFFCONT1. You can use the re-organization process or use a content server

Section 2

The Re-organzation Process: Use the re-organization report to delete entries in SOFFCONT1 that are no longer referenced by any
User/folder, etc. For the re-organization report please see note 966854 or 922565 depending on your release and note 988057 for
information on the re-organization process.

Section 3

Use of an Content Server: To use an content server to store entries from the table set a new storage category for SOFFDB in
transaction SKPR08 pointing to the external content server you want to use. Now all new documents will be stored in the content
server and existing documents in the system will remain in SOFFCONT1. You can use the report RSIRPIRL from note 389366
to physically move the existing documents in SOFFCONT1 to the content server. However this is only an optional step as
the Knowledge Provider still knows whether a document is stored in SOFFCONT1 or on the external content server and can access
documents from both.

Related Content

Related Notes

SAP note 530792 : Storing documents in the generic object services

SAP note 966854 : Reorganization - New report

SAP note 922565 : Reorganisation - New report (4.6C)

This is custom documentation. For more information, please visit SAP Help Portal. 12
 3/26/25, 5:05 AM
SAP note 988057 : Reorganization - Information

SAP note 389366 : Relocation of documents

SAP KBA 1634908: Reduce the size of table SOFFCONT1

SAP to send external mails

How to configure SAP to send mails.

After reading lots of threads related to this subject I found that most of the issues can be resolved by reviewing a few simple steps.

First you need to read the basic configuration found in the SMTP guide available in help.sap.com, If after that you still have trouble
here is a few tips.

1. Always check that the port (usually port 25) is open and you can reach your SMTP server. You can do this by simply telnet
the port if the port fail to reply please contact your network team.

1. Open a command prompt

2. Telnet <SMTP host> <port>

2. Check that the IP Address of you SAP Server is maintained on the SMTP Relay Agent of your SMTP Server. Basically SMTP
server require authentication by adding the IP Address of your server in the SMTP Relay Agent all the requests coming from
your SAP system will be "trusted".
3. Make sure that the E-mail Address and the Communication Method are maintained in SU01, this is a basic requirement to
send an e-mail and without it your mail simply won't be sent.
4. Please add your tips here....

Also please refer to following SAP Notes,

Note 455140 - Configuration of e-mail, fax, paging or SMS using SMTP
Note 455127 - E-mail (SMTP) in different SAP releases

SAPConnect Administration (SCOT) change log

Purpose

The purpose of this page is to clarify the understanding about the logged changes on SAPConnect Administration, more
specifically on SCOT transaction.

Overview

The SAPConnect Administration (SCOT) provides a standard interface for configuring the components to external
communications and sometimes you need to view the change that was made on this configuration for some reason.

On this document we cover a section with a brief introduction about SAPConnect and other about the logged changes on SCOT.

SAPConnect Administration (SCOT)

On SAPConnect Administration – SCOT t-code – you can modify or set up the components for external communication between
SAP and external systems/services.

For instance, you can configure your SMTP, FAX, SMS and other components of external communications.

For doing this configuration you need to have the “Sap Office Admin” right on your user.

Logged changes on SCOT

This is custom documentation. For more information, please visit SAP Help Portal. 13
 3/26/25, 5:05 AM
If someone did some changes on the configuration of SCOT and you need view a log about this changes and determine who did
what, you need to know that:

There is only the information about the last change on this configuration;
The transaction SCOT hasn’t a change log;
The user who did it has the “Sap Office Admin” right.

You can view the last change on the configuration doing this way:

1. Call scot transaction;

2. Expand the group what you want to view;
3. Double click on the service component;
4. In the opened new screen you can see the “Last changed by” field.

Related Content

Related Documents
BC-SRV-COM Communication Services - SAPconnect - Mail, Fax, SMS, Telephony

Related Notes
SAP Note 455140 : Configuration of e-mail, fax, paging or SMS using

SAPoffice objects disappear from shared folder

Purpose

This content was created to give more background information in relation to disappearing sapoffice objects in shared folders.

Overview
This is custom documentation. For more information, please visit SAP Help Portal. 14
 3/26/25, 5:05 AM
There is no known software error which results deleting SAPoffice objects from shared folders. Content of shared folders
(underlying shared folders, shared distribution lists, SAPoffice documents in shared folders) are usually manually deleted by
SAPoffice user. The following sections will show in detail how to restrict users from deleting SAPoffice objects from shared folders,
to check how and by whom the objects were deleted, how to recover/restore deleted documents.

How to "protect" objects from deletion in shared folders

User with SAPoffice Administrator authorization (S_OC_ROLE = ADMINISTRATOR or S_OC_ROLE = *) can change/delete any
SAPoffice objects in shared folders independently of the folder access authorizations. More information about the SAPoffice
authorizations can be found in following SAP Notes:

552127 - FAQ: SAPoffice - Authorizations

124025 - SAPoffice: Authorization in the shared folders

One way to protect documents in shared folders (like shared distribution lists) from deletion is to create a subfolder under the
shared folder and give authorization to this folder in "Attributes" service of the folder. You can give here general authorizations and
selected authorizations for users as well.
Be aware, that users with sapoffice administration authorization (sapoffice administrators) can change and delete any documents
from any folder under shared folders independently of this folder authorization. Therefore SAPoffice administrator authorization
should not be set for the users in general.

Logging/tracing deletion of SAPoffice documents

To be able to log such deletions in SAPoffice area for future deletions, you can activate the delete log. After the sapoffice document
is deleted, you can analyze the delete log to check, how and by whom the deletion was made. (Unfortunately if delete log is not
active, it is not possible to determine the circumstances of the deletion)

In this log you can find following informations:

-User who carried out the deletion
-Transaction from where the deletion was carried out
-Informations about the deleted SAPoffice object: folder ID, object ID

To activate the log and to have a detailed description about the log, check SAP Note

766112 - SAPoffice: Folders or documents disappear

In release ECC6.0 the log can simply be activated as follows:

-Transaction SO16 >> Tab "Document org."
-Set checkbox "Log Deletion of SAPoffice Documents"
-Schedule background job >> schedule periodically (every day)

To evaluate the log, go to transaction SLG1, enter following values:

Object: SO
Subobject: DELETE

Example for a log entry:

...
Document was deleted from folder FOL32000000009215 RAW35000000013845 Test
SUPPORT SBWP SAPMSSO0 SO_OBJECT_DELETE
...

-Folder ID: FOL32000000009215

-SAPoffice document ID: RAW35000000013845 (For distribution list, ID is DLI...)
-SAPoffice document Title: Test

This is custom documentation. For more information, please visit SAP Help Portal. 15
 3/26/25, 5:05 AM
-User name: SUPPORT
-Transaction: SBWP
-Used function module to delete the object: SO_OBJECT_DELETE

These informations lead us to the conclusion, that user SUPPORT deleted the document "Test" in transaction SBWP from the
appropriate folder.

Top

Recover deleted documents

First of all recovering deleted documents is only possible if no reorganization was executed (Report RSBCS_REORG) after the
SAPoffice objects were deleted from shared folders (and from shared trash folder also). If deleted documents can be still found in
shared trash, they can be simply removed to the original folder.

Unfortunately followings can not be recovered:

-Distribution lists
-Folders
-Folder structures

Deleted documents can be put back into shared folders with report RSSODELUNDO. This report creates the X_REPAIR folder
under shared folders and all deleted documents will be placed under this folder.

For more information read SAP Note:

887884 - SBWP: Recovering deleted documents

Top

Restore deleted documents

In case a backup system is available, the restoring option can also be used to bring back the deleted SAPoffice objects. For this
purpose the report RSBCS_RESTORE and RSBCS_RESTORE_GOS can be used. See SAP Notes:

1061985 - Restoring documents and folders from backup System

1726715 - Restore GOS documents from the backup system

Important informations before using restore report:

-Source system is a complete backup system of the target system
-Report supposes that relevant folder idendifications (ID) are the same in source and target system. This has to be checked first
before using the report. Folder IDs are stored in table SOFD.

Regarding distribution lists also consider SAP Note:

1642856 - RSBCS_RESTORE does not transfer distribution lists

Unfortunately during the restore step, it could happen that distribution lists will be inconsistently copied. To delete these
inconsistent distribution lists use report RSSO_DLI_CONSISTENT from the following SAP Note:

1363566 - Distribution lists cannot be opened via SBWP

Top

This is custom documentation. For more information, please visit SAP Help Portal. 16
 3/26/25, 5:05 AM

Transport of SAPoffice Documents

Transport of SAPoffice documents from other systems is not supported.

Top

Related Content

Related Documents

Related Notes

SCOT - SAPconnect Administration

SOST - Send Request Overview

Secure File Transfer Protocol - SFTP

Purpose:
This page is to explain how to accomplish Secure File Transfer Protocol (SFTP) in the SAP system.

Overivew:
In SAP, Secure File Transfer Protocol (SFTP) can be achieved using SSH (Secure Socket Shell)

Section 1:
SAP does not have any standard recomendation for achiving Secure File Transfer Protocol (SFTP) using SAPFTP/SAPFTPA. At
present all the communications done by SAPFTP are in clear text. The SAP R/3 system encrypts the password and sends it to
SAPFTP. Then this password is decrypted by SAPFTP, and this password information is sent via FTP in clear text to the FTP server.

Section 2:

SAPFTP is a simple FTP client that can be setup to use SSH (Secure Socket Shell). Now there are various vendors who provide
SSH (Secure Socket Shell) and the configuration of SSH (Secure Socket Shell) completely depends on the SSH (Secure Socket
Shell) vendor you choose. SAP has no recommendations on the configuration of the SSH (Secure Socket Shell).

Section 3:

The flow of the data goes as follows:

1. Firstly the SSH (client local/daemon local) is configured as per the Vendors instructions.
2. The SSH client is installed to the client system while the SSH daemon is installed to the FTP server.
3. The data is sent from SAPFTP to the local port of the SSH client and this makes the data secure (encrypts the data).
4. Then the SSH client sends this data to the SSH server daemon which decrypts the data and forwards the data to the FTP
server.

Section 4:
SSH can be configured for both Active and Passive mode of FTP communication.

Related Content

Related Notes:

This is custom documentation. For more information, please visit SAP Help Portal. 17
 3/26/25, 5:05 AM
SAP note 795131 - FAQ: How to make Secure FTP communication with SAPFTP

TCodes for SAPoffice

SO01 - SAPoffice: Inbox

SO02 - SAPoffice: Outbox

SO03 - SAPoffice: Private Folders
SO04 - SAPoffice: Shared Folders
SO05 - SAPoffice: Private Trash
SO06 - SAPoffice: Substitutionon/off
SO07 - SAPoffice: Resubmission
SO10 - SAPscript: Standard Texts
SO12 - SAPoffice: User Master
SO13 - SAPoffice: Substitute
SO15 - SAPoffice: DistributionLists
SO16 - SAPoffice: Profile
SO17 - SAPoffice: Delete Shared Trash
SO18 - SAPoffice: Shared Trash
SO19 - SAPoffice: Default Documents
SO21 - Maintain PC Work Directory
SO22 - SAPoffice: Delete PC Temp. Files
SO23 - SAPoffice: DistributionLists
SO24 - SAPoffice: Maintenance of default PC
SO28 - Maintain SOGR
SO30 - SAPoffice: Reorg.
SO31 - Reorganization (daily)
SO36 - Create Automatic Forwarding
SO38 - SAPoffice: Synchr. of Folder Auths.
SO40 - SAPoffice: Cust. LayoutSet MAIL
SO41 - SAPoffice: Cust. LayoutSet TELEFAX
SO42 - SAPoffice: Cust.Layout Set TELEFAX_K
SO43 - SAPoffice: Cust.Layout Set TELEFAX_M
SO44 - SAPoffice: Cust. LayoutSet TELEX
SO70 - Hypertext: Display/Maint. Structure
SO71 - Test plan management
SO72 - Maintain Hypertext Module
SO73 - Import graphic into SAPfind
SO80 - SAPfind: Free Text Retrieval Dialog
SO81 - SAPfind: Free Text Indexing (Test)
SO82 - SAPfind: Free Text Retrieval Batch
SO95 - Pregenerated Search Queries - Selec.
SO99 - Put Information System
SOA0 - ArchiveLink Workflow document types
SOBJ - Attribute Maintenance Objects
SOLE - OLE Applications
SOLI - Load OLE type info
SOPE - Exclude Document Classes
SOTD - SAPoffice: Maintain Object Types
SOY1 - SAPoffice: Mass Maint. Users
SOY2 - SAPoffice: Statistics data collect.
SOY3 - SAPoffice: Statistics Evaluation
SOY4 - SAPoffice: Access overview
SOY5 - SAPoffice: Inbox overview

This is custom documentation. For more information, please visit SAP Help Portal. 18
 3/26/25, 5:05 AM
SOY6 - SAPoffice: Document overview
SOY7 - SAPoffice: Folder overview
SOY8 - SAPoffice: Mass Archiving
SOY9 - SAPoffice: Inbox Reorg.
SOYA - SAPoffice: Change folder owner

Transaction SCOT - New layout (SOADM)

Purpose:
This page is to describe the changes in transaction 'SCOT - Business Communication Administration' in release 730.

Overview:
Since release 730 the format, look and functionaility of transaction SCOT has changed dramatically. It is now a very convenient
transaction for Business Communication Services as it provides one area where settings can be maintained, jobs scheduled,
reports run and other parameters related to Business Communication Services set. In release 720 a similar transaction is available
through SOADM however you cannot access the same transaction using SCOT.

Section 1:

Under the heading Business Communication Administration you can view each sections present in SCOT and also a breif
description of each section, they are as follow:

1. Administration - Overview of the most important transactions for administering Business Communication Services (BCS).
2. Settings - This area will allow the User to maintain/change the settings for the SBWP (Business workplace) and external
communication.
3. Maintenance - This area contains reports that can be used to check the Business Communication Services data and
correct inconsistencies.
4. Statistics - This area relates to the database tables related to Business Communication Services.
5. Re-organization - This area relates to the re-organization of Business Communication Services data
6. Delete Data - This area relates methods of deleting data that is no longer required.
7. Service Functions - This area relates to functions that are usually used by SAP support to analyze the system

Section 2:

The Administration section allows you to access the traditional view of SCOT and also transactions SOST (Outbound Send
Requests) and SOIN (Inbound Send Requests). In the SCOT traditional view you can see view and access the nodes maintained for
each communication method (e.g. E-Mail, Fax, SMS, etc.). Also you can view the number of different send request statuses for each
communication method (e.g. failed, successful, etc.)

in SOST and SOIN you can view the Outbound and Inbound Send requests in the system, from here you can check SAPconnect
trace and the MIME document of these Send requests which can help in troubleshooting errors in transmission. There are many
other selection options available in each screen.

Section 3:
This is custom documentation. For more information, please visit SAP Help Portal. 19
 3/26/25, 5:05 AM
The Settings section contains 3 areas, Outbound messages, Inbound message and Business Workplace. Under each you can
configure the settings for that area.

For Outbound messages there are the areas SMTP node, Settings, Send Jobs & Disclosures. In the SMTP node section you can
view and maintain all the setting of a SMTP node for a communication type.

Under the settings area first tab you can set various parameters in relation to outbound message such as Default Domain, Code
page, Size restrictions, Re-send attempts and if the first body part of a mail should be of type Text. The second tab controls
whether status requests and read confirmations are requested. In the Analysis tab you can turn on the SAPconnect trace and
whether MIME document are saved. The final tab can control whether e-mails are signed or encrypted.

The Send job area allows you to view/edit send jobs already maintained in the system, a send job must be regularly scheduled to
send waiting messages from the SAP system and can be created for a particular communication method or for all communication
methods.

Under disclosures area you can maintain disclosures depending on sender, these are details placed before or in a document that
contain information regarding contact data, etc.

For Inbound messages there are the areas Settings, Inbound processing and Inbound distribution.

This is custom documentation. For more information, please visit SAP Help Portal. 20
 3/26/25, 5:05 AM

Under the settings area first tab you can set various parameters in relation to Inbound message such as format of an inbound mail
and whether status requests and read confirmations are sent. The second tab controls statuses in relation to inbound mail. In
the Analysis tab as for ountbound mail you can turn on the SAPconnect trace and whether MIME document are saved. The button
Inbound distribution allows you to mintain settings as in transaction SO28.

For Business Workplace there are the areas Settings and Forwarding and Mail System Group. These two tabs allows the same
parameters to be set as in transaction SO16.

Section 4:
The Maintenance section contains various reports in relation to Profile settings, Users, Recipients, Address data,
Folders/documents, Number range objects. The following reports are available to be run in this section: (more detailed description
of each report is available in the relavent note for each report or in SCOT itself)

RSSOPRRP - Checks the consistency of the BCS Profile Settings

RSBCS_NUMBER_RANGE - Checks the consistency of the BCS number range objects
RSSOUSCO - Checks the consistency between SAP users, SAPoffice users, and address data.
RSSOUSFD - Checks the consistency of the private folders of a user
RSBCS_IFREC - Checks for recipient/sender records that have been created but not assigned to a send request, if they
exist they are deleted.
RSSO_DLI_CONSISTENT - Checks the consistency of BCS distribution lists
RSSO_DEL_EMPTY_FOLID - Checks the consistency between folder definition and folder assignment
RSSORE_SOC3_SOOD - Checks the consistency between documents and document content
RSSOADRDUP - Checks for duplicate addresses that were created when sending, then deletes them if they exist to improve
outbound/inbound transmission performance

Section 5:
This is custom documentation. For more information, please visit SAP Help Portal. 21
 3/26/25, 5:05 AM
The Statistics section contains methods for analyzing BCS data. There are 3 areas 'Determine BCS data', 'BCS data overview' and
'Private folder overview'

Under 'Determine BCS data' you can run a report (RSBCS_START_STATISTIC) that will determine the amount of BCS data in the
system, you can check for any large increase in data by using this option at a regular interval.

The 'BCS data overview' section shows the information that is gathered in the above area. You can check the number
of BCS documents that exist and other activites in the system. Again in the 'Private folder overview' area you can use the
information gathered using 'Determine BCS data' to check users with very large numbers of documents and documents that are in
the dark folder.

Section 6:
The Reorganization section contains options to Reorganize the BCS data, MIME documents and BCS users.

Under 'Reorganization of Business Communication Services data' you can start report RSBCS_REORG which will
delete documents with send requests or documents that are not part of a send request that they are no longer used in accordance

This is custom documentation. For more information, please visit SAP Help Portal. 22
 3/26/25, 5:05 AM
with the settings under "Reorganization Mode" (more details in SAP note 988057). In this section there are options to run
the report in dialog or in the background or as a job. More details on this report and this process are contained in SAP KBA
1641830.

Under 'Reorganization of MIME documents' you can run report RSBCS_DELETE_MIME in the same manner as the report above.
This report will delete MIME documents which are saved (if the option is set) when messages are sent and received via SMTP in
the system. They are saved into table SBCMCONT1 and are deleted by report RSBCS_REORG however with this method you can
delete the MIME documents without having to run RSBCS_REORG.

Under 'Reorganization of BCS users' you can run report RSBCS_USER_DELETE, this report deletes a BCS user whose SAP user
has already been deleted. When an SAP user is deleted in user management, the relevant BCS user is not deleted directly, but only
flagged as 'deleted', so this is why the report is required.

Section 7:
Under the 'Delete Data' section there are many functions to delete data in a targeted manner using different BCS reports. These
reports are as follows and again more more detailed information about each report is available in the relavent note for each report
or in SCOT itself. PLEASE NOTE: You cannot usually restore data that you delete using these functions. Therefore, check whether
the data is still required by users or applications before deleting it.

RSSO_DELETE_PRIVATE - Can delete documents from Private folders

RSSODFRE - Can delete documents from the 'Dark folder'
RSBCS_SREQ_RELEASE - Deletes documents with the status "Send Request Not Yet Released" that cannot be deleted by
report RSBCS_REORG
RSBCS_DELETE_QUEUE - Deletes messages that have status "Waiting" in SOST, these messages should not be sent from
the system
RSBCS_ADDRESS_REFERENCE - Deletes references to business partner or contact person addresses that cannot be
deleted due to this reference
RSBCS_ADRVP - Deletes address references to direct addresses that are no longer used, thus improving performance
when sending or receiving e-mails
RSBCS_SREQ_UNLINK - Deletes documents with the status "Link to Application" that cannot be deleted by report
RSBCS_REORG

Section 8:
Under the Service Functions section there are other service functions that are mostly used by SAP Support to analyze the BCS
runtime and/or data.

This is custom documentation. For more information, please visit SAP Help Portal. 23
 3/26/25, 5:05 AM

Related Content

Related documents

SAPconnect documentation

Transaction SO12 Private Office settings

Purpose
This wiki is to describe what settings are available in transaction SO12.

Overview
Transaction SO12 shows the SAPoffice settings for your User, you can view the SAPoffice administration information of another
User with the button Other User at the bottom of screen. Also from the bottom of the screen a new SAP User can be created with
the Create button and the address details of your User can be seen with the Address button.

Section 1
Document Tab:

Here are the settings for your User when creating a document, with option Change options after sending you can choose if a
document can be changed after being sent. Document types entered under Default document types will be available for creation in
the SAP Business Workplace.

This is custom documentation. For more information, please visit SAP Help Portal. 24
 3/26/25, 5:05 AM

Under Other settings for documents there are 4 options:

1. If the Confirmation prompt for deletion option is selected then when a document is deleted from the SAP Business
Workplace you will receive a pop-up in which you must confirm or cancel the deletion. This option will prevent a document being
deleted accidentally.

2. The Start PC application in R/3 window option controls if PC applications are embedded in the SAP window. The advantage of
this option is that you can edit PC documents in the SAP window and you no longer need to switch between different
windows. Also all functions and menu areas of the PC application and of the business workplace are available. Please note this
setting only has an effect for PC applications which support OLE.

3. The Resubmission on workdays only option controls whether resubmissions only take place on working days. So if you select
this field then you do not receive resubmissions on weekends or bank holidays. This means that you avoid reading important time
critical information late because you received the resubmission on a non-working day. In order for the system to proceed
according to the correct calendar, select the factory calendar that corresponds to your region in the field factory calendar.

4. The Factory calendar option allows you to specify the factory calendar that corresponds to your region.

The Number of days after which a document is deleted from trash option sets the number of days a document will stay in your
thrash before being deleted automatically. Deletion takes place when a User logs on to the SAP Business Workplace for the first

This is custom documentation. For more information, please visit SAP Help Portal. 25
 3/26/25, 5:05 AM
time each day. If no value has been entered, the trash is not deleted automatically. Deletion is then done manually in the
SAP Business Workplace.

Section 2
Send/Print Tab:

Here you can define pre-settings for sending:

Send automatic reply externally option is used so you can choose if the automatic reply is to be sent to internet addresses outside
the SAP system.

Move document to outbox option means that a document will be copied to the outbox when sent. A user can then receive more
information about these documents, e.g. whether a recipient has viewed the document.

Pre-settings for printing:

Change print param option controls whether or not a pop-up box appears where you can change the print parameters before the
printing of a document.

Include document header option controls whether the printing of the document header is included.

Include note option controls whether the printing of notes is included.

Include recipient list option controls whether the printing of recipient lists is included.

Section 3
Substitute Tab:

Here you can assign a substitute for your user when you do not have access to your SAP account. You can assign your substitute to
have authorization to your inbox/outbox and also your private/shared folders. Please note that only 1 substitute can be specified
for a particular period

This is custom documentation. For more information, please visit SAP Help Portal. 26
 3/26/25, 5:05 AM

The SUBSTIT field shows which user is the substitute for your user, FRM field shows when the substitution starts, TO field shows
when the substitution ends and ACTV. field shows if the substitution is currently active. The Details button shows the current
settings for the substitution and also changes to the substitution settings can be made here.

Section 4
Automatic Forwarding Tab:

Here you can set an address and communication method so that all documents sent to your user address will be forwarded to this
chosen address for a certain time period. You can also choose if these documents will be placed in your inbox.

This is custom documentation. For more information, please visit SAP Help Portal. 27
 3/26/25, 5:05 AM

Section 5
Automatic Reply Tab:

Here you can define an automatic reply that will be sent to all Internet mail addresses who contact your user. You can set
the time period the reply will be sent and also the title and message body of the reply.

This is custom documentation. For more information, please visit SAP Help Portal. 28
 3/26/25, 5:05 AM

Section 6
Admin Info Tab:

Here you can view the SAPoffice administration information for your user (this is the same information you will see for another
user if you choose the Other User button at the bottom of screen). You can view the username, address name and number, who
created and last changed the user, last access by the user to their business workplace and also what authorizations the user has in
regard to creation, sending and archiving. Please note no changes can be made here, although the Address Management button
will bring you to the address details of the User (this screen can also be seen with the Address button at the bottom of the screen).

This is custom documentation. For more information, please visit SAP Help Portal. 29
 3/26/25, 5:05 AM

Related Content
The Business Workplace

Transaction SO15 and SO23 - Distribution lists

Purpose
This wiki is to discuss Distribution lists transactions and common issues.

Overview
Transactions SO15 and SO23 are used for maintenance of Distribution lists in the SAP system.

Section 1
SO15 / SO23: The transactions for creating, maintaining and deleting Distribution lists are SO15 and SO23. Both transactions will
bring you to the same screen. Here you can view both Private and Shared distribution lists. You can search for distribution lists at

This is custom documentation. For more information, please visit SAP Help Portal. 30
 3/26/25, 5:05 AM
the top of the screen. The search options possible are Type (Share or Private), Name, Title and 'Entry in DL'. For 'Entry in DL' you
can choose from internal user, addresses and internal users, distribution list, external addresses and organizational users. To check
the consistency of a distribution list the following report, RSSO_DLI_CONSISTENT, from note 1176031 can be used.

Section 2
Distribution lists vanish / disappear: A common issue with distribution lists is that they vanish/disappear from the SAP system.
Usually when distribution lists disappear they have been deleted accidently by some User. The first step is to check if these
distribution lists are still in the Trash Bin? Unfortunately once a distribution list has been deleted from the Trash Bin it cannot be
recovered. There are no standard SAP programs or reports that will delete a distribution list. To prevent distribution list deletions in
future you should change the authorizations of users as per note 124025.

What you should also do is activate the deletion log for of SAPoffice folders and documents under the 'Document Org' tab in
transaction SO16 (more details in note 766112). Then in transaction SLG1 you can view the details of who, how and
where SAPoffice folders and documents are deleted. However if the log was not in operation when the deletion occured you will not
be able to find out which user deleted the distribution lists, only future deletions will be logged.

Check also wiki page SAPoffice objects disappear from shared folder.

Transaction SO16 Shared Office Settings

Purpose

This wiki is to describe the settings available in transaction SO16

Overview

Transaction SO16 shows the shared SAPoffice settings that are applicable to all SAP users. Also with the Shared Thrash button at
the top of the screen you can access Txn SO18, from which allows you to view the shared thrash and also choose and delete
individual entries.

Section 1
This is custom documentation. For more information, please visit SAP Help Portal. 31
 3/26/25, 5:05 AM
User Tab:

Here the pre-settings that all newly created users are assigned with can be maintained.

1. Documents are copied to the outbox when sent. Select this option if documents are to be copied to the outbox when sent.

2. Switch confirmation prompt on or off when deleting. When a document is deleted you receive a pop-up in which you must
confirm or cancel the deletion. This prevents a user from deleting documents accidentally.

3. RE on workdays only. This controls whether resubmissions only take place on working days. So if you select this field then you
do not receive resubmissions on weekends or bank holidays.

4. Factory Calendar. This allows you to specify the factory calendar that corresponds to your region.

These settings can then be changed by the user in their private office settings in transaction SO12.

The settings under User Notifications are for all users. If the option No notification of unviewed mails at logon is not set then when
a user logons to the SAP system they will receive a pop-up box informing them if they have any unviewed mails in their inbox. The
option Execution of express messages in new session, if set, means that the inbox is displayed in a new session window.

Section 2
Document Org. Tab:

This is custom documentation. For more information, please visit SAP Help Portal. 32
 3/26/25, 5:05 AM
Here you can maintain the settings in relation to expiry, export and deletion of documents.

Expiration

1. Presetting: Document Expiration. Here you set the amount of days after which a document will be deleted.

2. Expiration of Documents in Outbox. Here you can set the amount of days after which a document will be automatically deleted
from the outbox. Also you can set a job to do this deletion with the schedule background job (green check) button that comes after
the field. The Expiration also for unread documents option below allows you to set it so unviewed documents will also be deleted
from the outbox.

Export

The option Warning at export, if document is larger than allows you to choose the size of documents, so that when users are
creating or changing a document they will receive a pop-up that informs them about the size of the document, the pop-up will give
the option of cancelling the function or downloading the document first. This is used because calling large documents can affect
performance on the system.

Log deletion

Here you can turn on the deletion log so that when a folder or document is deleted from the Business Workplace information about
the deletion is logged (who, how, where, etc). The log is turned on with option Log deletion of SAPoffice documents. More details
on this process are contained in note 766112.

With option Schedule Job for Generating/Deleting Log Files you can define a job that will generate and delete these deletion log
files.

Section 3
Send Tab:

This is custom documentation. For more information, please visit SAP Help Portal. 33
 3/26/25, 5:05 AM
Here you can maintain settings in relation to sending for all users in the system.

1. No sending between SAP users. This option controls if internal sending is allowed in the system, i.e. sending from one user to
another.

2. External sending only using address management. This option controls whether direct external sending is allowed. If selected
then users can only send documents externally to people from the address management.

3. No external sending using address management. This option controls whether sending to an external address recipient is
allowed. If this option is selected with option 2 then users will not be able to send externally in the system.

4. No external sending of confidential documents. If this option is selected then confidential documents cannot be sent to external
addresses in this system.

Please note if all three fields (options 2 -> 4) under send restrictions are selected then the send function is deactivated in the
whole of SAPoffice.

Section 4
Addressing Tab:

This is custom documentation. For more information, please visit SAP Help Portal. 34
 3/26/25, 5:05 AM
When an SAP user's address is changed it can be buffered, ie. placed into the address buffer of an application server. This is done
to improve performance. When a address is placed in the buffer it will not be effective until it is deleted from the address buffer.
The Reset Buffer after allows you to set the number of hours after the address buffer is deleted, then the address change will take
place. You can manually reset the buffer with the Reset Buffer button. If you do not want the buffer to ever be deleted
automatically, enter 9999, or if you want to switch the buffer off enter 0000.

The Addresses from LDAP service option should be selected if a connection has been set up to an LDAP directory service. The
LDAP directory service can then be accessed from the user interface and so SAP users in a mail system group can access the
addresses of non-SAP users. The LDAP settings button shows the current setting in relation to the LDAP.

If Organizational Units option checked the HR organization is connected and documents can be sent to HR organization units.

If the SAP business objects option is selected then it is possible to send to objects from the Business Object Repository

Section 5
Mail Sy.Grp Tab:

Under mail system group you can configure it so all messages are sent to another SAP system or to the home address of users.

The No mail system group option means the system is not part of a mail system group and so messages will be sent normally. If
there are problems with E-mails not appearing in the Send Queue in transaction SOST then check the settings here.

The Forward mails to (SAP SID / client) option means that all the messages received in this SAP system are forwarded to the SAP
system that is specified in the SAP System ID and Client field defined underneath. This applies to all internal and external
messages.

The option Send to home addresses of users means that messages sent to a user in the system will be forwarded to that user's
home addresses. A user's home address is specified in address management. In this case the messages will be forwarded to the
home address that is specified for the standard communication method of the user.

Related Content

Related Documents
SAPhelp - A Mail System Group Between SAP Systems and an External Mail System

Type 'SAPFTP_SERVERS' is unknown

This is custom documentation. For more information, please visit SAP Help Portal. 35
 3/26/25, 5:05 AM

Purpose

This wiki deals with the SYNTAX_ERROR dump Type 'SAPFTP_SERVERS' is unknown. This dump comes because the table
'SAPFTP_SERVERS' does not exist in the system in question.

Overview

This dump is usually encountered when you are attempting to implement note 1692988, note 1605054 is a prerequisite that must
be implemented before note 1692988 and contains steps to create table 'SAPFTP_SERVERS'

Section 1
To resolve this dump the table SAPFTP_SERVERS must be created manually as per the steps in note 1605054, (please note that
the package should be SFTP and that the correction instructions attached to this note should be implemented before the manual
configuration)

Related Notes

SAP note 1692988: Directory traversal in SFTP modules

SAP note 1605054: Restriction in access to FTP Servers & usage of test reports

This is custom documentation. For more information, please visit SAP Help Portal. 36