Scribd
Upload
298 views1 page

Sbcmont1 and Se16n CD Data

This document discusses ways to manage tables that store MIME documents and change documents created during import/export processes in SAP systems. It describes how to deactivate storage of MIME data to avoid growth of the SBCMCONT1 table by using transaction SOST or report RSCONN06. It also explains that change documents created during table entries changed via transaction SE16N are stored in tables SE16N_CD_KEY and SE16N_CD_DATA, and can be displayed and deleted using reports like RKSE16N_CD and RKSE16N_CD_DISPLAY. Reorganization via report RSBCS_REORG or deletion using RSBCS_DELETE_MIME can manage the SBCMCONT1 table

Uploaded by

AlexFluido
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
298 views1 page

Sbcmont1 and Se16n CD Data

This document discusses ways to manage tables that store MIME documents and change documents created during import/export processes in SAP systems. It describes how to deactivate storage of MIME data to avoid growth of the SBCMCONT1 table by using transaction SOST or report RSCONN06. It also explains that change documents created during table entries changed via transaction SE16N are stored in tables SE16N_CD_KEY and SE16N_CD_DATA, and can be displayed and deleted using reports like RKSE16N_CD and RKSE16N_CD_DISPLAY. Reorganization via report RSBCS_REORG or deletion using RSBCS_DELETE_MIME can manage the SBCMCONT1 table

Uploaded by

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

SBCMCONT1: Table for Document Contents (Import / Export)

This table contains the converted MIME documents that are created during shipping
or receipt via SMTP.
These documents are required for analysis purposes only. This table is often
growing on SAP SRM systems
due to the intensive usage of sending documents (mails, faxes) to internal but also
to external recipients.
5.1.22.1 Avoidance
Check whether the MIME data is required. If this is not the case, you can
deactivate the data storage in the
database. To do this, call transaction SOST and choose Utilities  MIME Settings
from the menu
(alternatively, you can use report RSCONN06 to do this).
5.1.22.2 Summarization
Cannot be used
5.1.22.3 Deletion
A reorganization via report RSBCS_REORG is possible. At this, MIME data will also
be deleted. An explicit
deletion of the MIME data is possible via report RSBCS_DELETE_MIME.
See also SAP note:
 1253870 (SAP Basis 620 – 711): Table SBCMCONT1 is large
5.1.22.4 Archiving
Cannot be used
5.1.23 SE16N_CD_DATA, SE16N_CD_KEY: Table Display – Change Documents
While changing table entries via transaction SE16N, table change documents will be
written. They will be
saved in tables SE16N_CD_KEY (header information) and SE16N_CD_DATA (item
information).
5.1.23.1 Avoidance
Please check if all those changes really have to be done within transaction SE16N
or if is possible to use
other business transactions alternatively to do those changes. Please check if you
can restrict the number of
users that are authorized to perform those changes.
It is not possible to switch off the creation of those table change documents.
5.1.23.2 Deletion
In releases up to SAP ERP 6.0 EHP 5 the table change documents can be displayed and
deleted with
reports:
 RKSE16N_CD
 RKSE16N_CD_SHOW_DELETE
With SAP ERP 6.0 EHP 5, both display reports became obsolete. Instead, report
RKSE16N_CD_DISPLAY
should be used.
See also SAP notes:
 1263844 (SAP R/3 470 -604): CO-OM tools: SE16N: Deleting change documents
 1275614 (SAP R/3 470 -604): CO-OM tools: SE16N: Deleting change documents in
background

You might also like