14.11.2012 Page 1 of 4

SAP Note 178631 - SDCC - Service Data Control Center -Vers. 2.3 3.0D-3.1I,4.6

Note Language: English Version: 135 Validity: Valid Since24.03.2004

Summary

SymptomYou want to activate the Service Data Control Center (SDCC) during thepreparation of a pending EarlyWatch, GoingLive Check session, or similar.

Other termsRFC download, EarlyWatch, GoingLive Check, service, EarlyWatch Alert

Reason and PrerequisitesFor the planned execution of a service session, you want to providestatistical data on the use of the R/3 System. For this you want toimplement the Service Data Control Center (SDCC) including the RFCdownload.

Solution

CAUTION: BEFORE CALLING SDCC PLEASE DO REFER TO NOTES712757(Basis Release 3.x) AND 713674 (Basis Release 4.6A):A SERVICE DEFINITION REFRESH MUST NO LONGER BE CARRIEDOUT!

1. Copy the files specified here

o for R/3 Releases <= 3.1I and R/3 Release 4.6A

o Transport SAPKVSD009 (files KVSD009.SAP and RVSD009.SAP)

o (size: about 8.0 MB)

- or alternatively, the file packed with CAR

- SAPKVSD009.CAR (size: about 3.0 MB)

from the directory "/general/R3server/abap/note.0178631" on sapserv3to your system. The files also exist as packed .CAR files (to reducetransmission times and costs). Use ftp in binary mode to download thefiles. For the transport*.CAR file, refer to Note 29372 forinformation on how to unpack the file.

Copy the SAPKVSD009.CAR file into the "directory /usr/sap/trans" andunpack it using the SAP tool CAR as described in Note 29372 using thecommand "car -xvf SAPKVSD009.CAR". The unpacked transport files areautomatically assigned to the correct subdirectories (/cofiles,/data).

Note: Copy only the above files. Any of the other files in the

14.11.2012 Page 2 of 4

SAP Note 178631 - SDCC - Service Data Control Center -Vers. 2.3 3.0D-3.1I,4.6

directory are usually bug fixes for old SDCC versions and must onlybe implemented for a particular reason (see below).

2. Copy file RVSD009.SAP into the "data" directory of your transportdirectory ("/usr/sap/trans\" or "\usr\sap\trans\"). Copy fileRVSD009.SAP to the "cofiles" directory of the transport directory.

3. In directory "\usr\sap\trans\bin" or "/usr/sap/trans/bin" execute thefollowing commands:

o For R/3 Releases <= 3.1I and R/3 Release 4.6A: tp addtobuffer SAPKVSD009 <SID>

4. If these commands were successfully executed, start the followingcommand from the above "bin" directory:

o For R/3 Releases <= 3.1I and R/3 Release 4.6A: tp import SAPKVSD009 <SID> u168

If you want to overwrite an already existing imported version ofSDCC in a system with a new transport, then work in unconditionalmode: tp import SAPKVSD009 <SID> u168

5. Check the logs of the transport request for errors.

Possible errors:

o During the import:

- ABAP SAPLBDL7: Syntax error in line "000031""Field 'BAMVIEWSTR'unknown

If the application monitor does not exist in your system yet(Note 69455), there will be a generation error in functiongroup BDL7 (ABAP SAPLBDL7: Syntax error in line "000031" "Field'BAMVIEWSTR' unknown"). This error can be ignored.

- Transport error 8, inconsistency DD <-> DB (for example, fortable BDLMSGLOG)

If you import the same transport again after an upgrade, theremay be an inconsistency between the Data Dictionary and thedatabase objects. Even regenerating the object from the DataDictionary does not resolve the inconsistency. In this case,run report RTCCTABG, if available (with the incorrect tablename as input). If this report does not exist on your system,refer to Note 211492.

- Transport error 8 (particularly on BW Systems)Field JOBSTATUS: Data element or domain is not active or doesnot exist

Nametab for table BDLDYNSESS cannot be generated. Import the

14.11.2012 Page 3 of 4

SAP Note 178631 - SDCC - Service Data Control Center -Vers. 2.3 3.0D-3.1I,4.6

correction transport SAPKVSD05C using the same procedure as youused for the main transport SAPKVSD009. Do not forget to usethe unconditionals to ensure that this correction overwritesthe relevant section of the main import.

- The following can be ignored:

E- ABAP BDLVIEW3, Include BDLVINCL : Syntax error in line000006

E- INCLUDE report 'BDLV0001' not found.

The SDCC functionality is not affected.

o Conne_Import_Wrong_Comp_Length in program BDLATRUN

- Check if there is an entry in table BDL_CLUSTL. If an entry ispresent, delete it using Transaction SE16.

Header Data

Release Status: Released for CustomerReleased on: 23.03.2004 14:45:54Master Language: EnglishPriority: Recommendations/additional infoCategory: Special developmentPrimary Component: SV-SMG-SDD Service Data Download

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 30 30D 31I

SAP_APPL 46 46A 46A

Related Notes

Number Short Text

1108861 Add. info. on upgrading to SAP CRM 5.0 SR3 ABAP

1088904 Add. info. on upgrading to SAP ECC 6.0 SR3 ABAP

781680 SDCC/ SDCCN - Problems with function modules

597323 TCC basis tools in releases EARLIER than Release 4.0B!

389742 ST14 monitor for CRM/EBP 2.0B-2.0C

314672 System measurement: Data transfer by SDCC

312834 ABAP dump TSV_NEW_PAGE_ALLOC_FAILED in SAPLBDL3

216952 Service Data Control Center (SDCC) - FAQ

211492 Inconsistency between ABAP Dictionary <-> database

203536 DBIF_..._INVALID_CURSOR in SDCC message log / dump

14.11.2012 Page 4 of 4

SAP Note 178631 - SDCC - Service Data Control Center -Vers. 2.3 3.0D-3.1I,4.6

Number Short Text

197886 Upgrade: messages in CHK_POSTUP: BDL*, STSL*, BAM*, SQLR*

195539 Transports for SQL statement analysis service

187939 SAP Servicetools Update (RTCCTOOL)

116095 Solution Tools Plug-In (TCC Basis Tools and Trace Tools)

29372 Unpacking .car archives

Attributes

Attribute Value

Transaction codes DICTIONARY

Transaction codes HIER

Transaction codes MODE

Transaction codes SDCC

Transaction codes SE16

Transaction codes SESS

Transaction codes SM51