Transaction Automation

deprecated topic

Transaction BDLS

  • Purpose: Conversion of logical system names
  • Automation type: ABAP program
  • Procedure: Process Definition: SCP_BDLS

If the conversion of logical system names fails, no new conversion can be started. The corresponding error message looks like this:

Copy 
Message no. B1668
Diagnosis
While a conversion is running, you cannot start any further processes for the test run. Depending on the size of the dataset in the system, this process can last a long time.

In this case, there are old log entries in tables BDLSHDR, BDLSPOS, and BDLSLOG. These entries can be deleted by running the ABAP program RBDLSMAP_RESET. This ABAP program requires no variants.

Run ABAP program RBDLSMAP with a (temporary) variant.

These are the recommended values for the variant:

Parameter Name Value
Old Logical System Name

New Logical System Name <new name>
Client independent X
Test run X
Check existence of new names in tables X
Number of Entries per Commit 100
Tables to be Converted [CP *]

Check the spool list for errors and then rerun the ABAP program RBDLSMAP with a (temporary) variant with a blank value of the parameter Test run.

Test runs can be started in parallel, the actual conversion needs to happen sequentially.

Transaction BD54

  • Purpose: Maintenance of logical systems

Display Logical Systems

  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_BD54_Get_Logical_Systems

Delete Logical Systems

  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_BD54_Delete_Logical_System

Transaction BD64

  • Purpose: Display Distribution Model
  • Automation type: BDC
  • Procedure:

Transaction BD97

  • Purpose: Assign RFC destinations for synchronous method calls
  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_BD97

Transaction DB02

  • Purpose: Space Overview
  • Automation type: RFC scripting
  • Procedure: Normally the information shown in this transaction can be retrieved from the CCMS monitoring tree. This can be done by either configuring Redwood Server to synchronize the CCMS monitoring tree (XAL) or by direct calls of the XAL BAPIs.

Transaction DB13

  • Purpose: DBA planning calendar
  • Automation type: ABAP program
  • Procedure: The implementation depends on what exactly you want to do. Contact Redwood if you need help determining what needs to be done in database calendar planning.

Transaction OAC0

  • Purpose: Display Content Repositories: Overview
  • **Automation type: ** Export/Import
  • Procedure: Process Definition: SCP_Configure

Configure the refresh scenario such that Content Repository data is preserved.

Transaction LC10

  • Purpose: LiveCache: Initial Screen
  • **Automation type: ** BDC
  • Procedure:

Transaction OSS1

  • Purpose: OSS connection
  • Automation type: ABAP program
  • Procedure: Run ABAP program RSEFA910 with a (temporary) variant.

Transaction PFCG

  • Purpose: Profile generator
  • Automation type: Export/Import
  • Procedure: Process Definition SCP_Configure

Configure the refresh scenario such that User Master data is preserved.

Transaction RZ03

  • Purpose: Application server statuses and alerts
  • Automation type: ABAP program
  • Procedure: Run ABAP program RSRZLST1 and check the spool list.

Transaction RZ04

  • Purpose: Maintain operation modes and instances
  • Automation type: ABAP, RFC Scripting
  • Procedure: Process Definitions SCP_RZ04_xxx

These Process Definitions provide means to maintain operation modes and instances

Transaction RZ10

  • Purpose: Edit profiles
  • Automation type: OS / RFC Scripting
  • Procedure: Process Definitions SCP_RZ10_Add_Profile_Parameter, SCP_RZ10_Import_Profiles_All_Active_Servers, and SCP_RZ10_Update_Profile

Transaction RZ12

  • Purpose: RFC server group maintenance
  • Automation type: RFC Scripting
  • Procedure: Process Definitions SCP_RZ12_xxx Run the Process Definition SCP_RZ12_Save_RFC_Server_Groups before and SCP_RZ12_Restore_RFC_Server_Groups after the refresh

Transaction RZ20

  • Purpose: Get or maintain CCMS monitors

Get CCMS monitor values

  • Automation type: XAL or RFC scripting
  • Procedure: Redwood Server can import CCMS monitors into its own monitoring tree by using the XAL interface.

Alternatively it is possible to call the XAL BAPIs from RFC scripting

Create Database Monitor Tree

  • Automation type: ABAP program
  • Procedure: Run ABAP program RSDBMON0 with a (temporary) variant

Process Definition: SCP_RZ20_Create_Monitor_Tree

Transaction RZ21

  • Purpose: Monitoring: Properties and Methods
  • Automation type: BDC
  • Procedure:

Transaction SALE

  • Purpose: Display IMG
  • Automation type: BDC
  • Procedure:

Transaction SCC3

  • Purpose: Client copy / Transport log analysis
  • Automation type: RFC scripting
  • Procedure: Read table CCCFLOW

Transaction SCC4

  • Purpose: Client configuration

Display Clients

  • Automation type: RFC scripting
  • Procedure: Read table T000

Normally the user needs the S_ADMI_FCD authorization to read this table.

Change the Modifiable Flag

  • Automation type: BDC
  • Procedure: Process Definition: SCP_SCC4

Delete Logical System from a Client

  • Automation type: RFC scripting

Process Definition: SCP_BD54_Delete_Logical_System

Transaction SCC5

  • Purpose: Delete client
  • Automation type: ABAP program
  • Procedure: Run ABAP program SAPMSCC1 with a (temporary) variant.

Transaction SCC8

  • Purpose: Client Export
  • Automation type: BDC
  • Procedure: Chain definition: SCP_SCC8

Run ABAP program RSCLXCOP with a (temporary) variant.

  • Tables:
    • CCPROF - Client copy profiles
    • CCPROFSR - Source entries for profiles
    • CCPROCTAB - Parallel Client Copy Processes
    • CCCFLOW - Client Copy Control Flow

Transaction SCC9

  • Purpose: Client copy
  • Automation type: ABAP report
  • Procedure: Submit the ABAP report RSCLXCOP with a (temporary) variant.

Transaction SCOT

  • Purpose: SAPConnect Administration

  • Tables:

  • SXADDRTYPE

  • SXSERV

  • SXROUTE

  • SXNODES

Disable / enable nodes

  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_SCOT_SAPConnect_Nodes

Display Jobs

  • Automation type: RFC scripting
  • Procedure: Select jobs with the ABAP program name RSCONN01 in the step

Transaction SCUL

  • Purpose: Log Display for Central User Administration
  • Automation type: ABAP Program
  • Procedure: RSUSRLOG

Transaction SDCCN

  • Purpose: Service Data Control Center
  • Automation type: ABAP Program
  • Procedure: Process Definitions SCP_SDCCN_xxx

Transaction SE06

  • Purpose: Post-installation actions for transport organizer
  • Automation type: BDC
  • Procedure: Process Definition: SCP_SE06

Transaction SE14

  • Purpose: ABAP Dictionary: Database Utility
  • Automation type: BDC
  • Procedure:

Transaction SE16N

  • Purpose: General Table Display
  • Automation type: None
  • Procedure: In general, this transaction cannot be automated, since this is the entry point into general SAP table maintenance. Changing values in specific tables can be automated though. The preferred way of doing this is via export/import. For this add the SAP table to the Redwood Server table SCP_CTS_CUSTOM_TABLES and make sure that export/import is enabled via SCP_Configure

Transaction SE80

  • Purpose: Object Navigator
  • Automation type: None
  • Procedure: In general, this transaction cannot be automated, since this is a general entry point into ABAP code navigation and manual execution. The actual steps needed for your system copy procedure will depend on what you do in the object navigator.

Transaction SE38

Purpose: ABAP Editor: Initial Screen

  • Automation type: ABAP program
  • Procedure: Run the ABAP program via SAP_AbapRun with a (temporary) variant

Transaction SE84

Purpose: Object Navigator

  • Automation type: None
  • Procedure: In general, this transaction cannot be automated, since this is a general entry point into ABAP code navigation and manual execution.

See transaction SE80 for more details.

Transaction SECSTORE

  • Purpose: Secure storage administration
  • Automation type: Export/Import
  • Procedure: SCP_Configure with RFC and STRUST

Transaction SGEN

  • Purpose: SAP Load generator
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SGEN

Transaction SICF

  • Purpose: Maintain Services
  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_SICF_ShowServices shows all available services along with their status. This can be used in a subsequent process to notify the user if important services are not properly configured.

The actual service configuration will remain a manual task for now.

Transaction SICK

  • Purpose: SAP Initial Consistency Check
  • Automation type: ABAP
  • Procedure: Run ABAP program RSICC000. Check the spool list of the job for possible errors.

Process Definition: SCP_SICK

Transaction SM02

  • Purpose: System messages
  • Automation type: BDC
  • Procedure: Process Definition SCP_SM02

Transaction SM12

  • Purpose: Delete Lock Entries
  • Automation type: BDC
  • Procedure: Process Definition SCP_SM12_Delete_All_Locks

This Process Definition deletes all locks, which is good enough when performing a system copy.

Transaction SM13

  • Purpose: Update Requests
  • Automation type: ABAP
  • Procedure: Process Definition SCP_RSM13002

Transaction SM37

  • Purpose: Display SAP batch jobs
  • Automation type: RFC scripting
  • Procedure: Select jobs using standard RFC scripting methods

Process Definition SCP_SM37_Deactivate_Jobs can be used to remove all SAP jobs in status Released, Ready or Active from scheduling.

Transaction SM21

  • Purpose: System Log
  • Automation type: Standard Process Definition
  • Procedure: Run Process Definition SAP_GetSyslog

Transaction SM28

  • Purpose: Installation check
  • Automation type: ABAP program
  • Procedure: SCP_SICK

Transaction SM50

  • Purpose: Process Overview
  • Automation type: ABAP program or RFC scripting
  • Procedure: Process Definition SCP_SM50 ABAP program: Run ABAP program RSMON000_ALV. Check the spool list of the job. RFC scripting: function module TH_WPINFO

Transaction SM51

  • Purpose: SAP Server Overview
  • Automation type: ABAP program or RFC scripting
  • Procedure: Process Definition SM51

ABAP program: Run ABAP program RSM51000. Check the spool list of the job.

RFC scripting: Function modules TH_SERVER_LIST

Transaction SM54

  • Purpose: Maintain CPIC destinations and SNC options
  • Automation type: RFC Scripting
  • Procedure: Process Definition SCP_SM54 to show the entries in table TXCOM

Transaction SM55

  • Purpose: Maintain entries in the THOST table
  • Automation type: Export/Import
  • Procedure: Process Definition: SCP_Configure

Configure the refresh scenario such that THOST table is preserved.

Transaction SM58

  • Purpose: RFC error log maintenance

Check the Asynchronous RFC Error Log

  • Purpose: RFC error log maintenance
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SM58_Show_tRFC_Logs

Run ABAP program RSARFCRD with a (temporary) variant and check the spool list of the job.

Delete old RFC calls

  • Purpose: Delete stale RFC calls
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SM58_Delete_Stale_tRFC_Calls

Run ABAP program RSARFC01 with a (temporary) variant.

Transaction SM59

  • Purpose: Configuration of connections

Check the Application Servers

  • Purpose: check the configuration of the application servers
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SM59_Check_App_Servers

Run ABAP program RSWKTHRU and check the spool list of the job for errors.

Maintain RFC coneections

  • Automation type: Export/Import
  • Procedure: Process Definition: SCP_Configure

Configure the refresh scenario such that RFC connections are preserved.

Check RFC traces

  • Purpose: check the RFC traces for errors
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SM59_Check_RFC_Traces

Run ABAP program RSRFCTRC and check the spool list of the job for errors.

Delete RFC traces

  • Purpose: delete old RFC traces
  • Automation type: RFC scripting
  • Procedure: Call function module RFC_TRACE_DELETE via RFC scripting.

Show RFC destinations

  • Purpose: show available RFC destinations
  • Automation type: RFC Scripting
  • Procedure: Process Definition SCP_SM59_Show_RFC_Destinations

Create or Modify Destination

  • Purpose: create a new or modify an existing destination
  • Automation type: RFC scripting & Redwood transports
  • Procedure: TCPIP destination type and Process Definition SCP_SM59_Modify_RFC_Destination_TCPIP

Delete Destination

  • Purpose: delete an existing destination

  • Automation type: RFC scripting & Redwood transports

  • Procedure: Process Definition SCP_SM59_Delete_RFC_Destination

Transaction SM61

  • Purpose: Display control object list

  • Automation type: RFC scripting

  • Procedure: Process Definition SCP_SM61

Transaction SM63

  • Purpose: Maintain operation modes
  • Automation type: Export/Import
  • Procedure: SCP_Configure with OPERATION_MODES

Transaction SM65

  • Purpose: Analysis Tool – Background Processing
  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_SM65

TEMSE:

Call function module RSTS_SELF_TEST via RFC scripting

User authorization check:

Call function module AUTHORITY_CHECK for following authorization objects (as specified in the function module BPT_USER_PRIVILEGE_CHECK ):

Copy 
    S_BTCH_ADM: BTCADMIN=Y
    S_BTCH_JOB: JOBGROUP=*, JOBACTION=EWCH
    S_ADMI_FCD: S_ADMI_FCD=STOR
    S_BTCH_JOB: JOBGROUP=*, JOBACTION=DELE
    S_BTCH_JOB: JOBGROUP=*, JOBACTION=PROT
    S_BTCH_JOB: JOBGROUP=*, JOBACTION=RELE
    S_BTCH_JOB: JOBGROUP=*, JOBACTION=SHOW

SAPCPIC:

Use RFC scripting

Read table T000 to get all defined clients

For each defined client read table USR02 and check that the user SAPCPIC is defined

Batch consistency check:

Use RFC scripting to read various tables and compare their contents. Please refer to function module BPT_CONSISTENCY_CHECK for more details.

Transaction SMICM

  • Purpose: ICM Monitor
  • Automation type: RFC scripting
  • Procedure

Process Definition SCP_SMICM_Check_Service

Transaction SMLG

  • Purpose: Maintain logon groups
  • Automation type: BDC

Show Logon Groups

  • Procedure: Process Definitions ~SCP_SMLG_xxx_

Run SCP_SMLG_Save_Logon_Groups before and SCP_SMLG_Restore_Logon_Groups after the refresh

Transaction SMQ1

  • Purpose: qRFC Monitor / Outbound Queues
  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_SMQ1

Transaction SMQ2

  • Purpose: qRFC Monitor / Inbound Queues
  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_SMQ2

Transaction SMQR

  • Purpose: qRFC Monitor / QIN scheduler
  • Automation type: RFC scripting
  • Procedure: Process Definition SCP_SMQR_qRFC_Monitor_QIN

Transaction SMQS

  • Purpose: qRFC Monitor / QOUT scheduler
  • Automation type: RFC scripting
  • Procedure: Process Definitions SCP_SMQS_qRFC_Monitor_QOUT and SCP_SMQS_QOUT_Change_AS_Group_Name

Transaction SNRO

  • Purpose: Number Range Object Maintenance
  • Automation type: Export/Import
  • Procedure: SCP_Configure with SNUM

Transaction SNUM

  • Purpose: Number Range Object Maintenance
  • Automation type: Export/import
  • Procedure: SCP_Configure with SNUM

Transaction SP12

  • Purpose: TemSe consistency check
  • Automation type: ABAP program
  • Procedure: Process Definitions SCP_SP12_xxx

Run ABAP program RSTS0020. Check the spool list of the job for errors. Check the spool list of the job for errors.

The inconsistencies in TemSe can be deleted by running the ABAP program RSTS0030 with a (temporary) variant with values from the previous step.

Note: TemSe may by design contain temporary inconsistencies which must not be deleted. As such, do not perform the described TemSe consistency check in a live SAP system.

Transaction SPAD

  • Purpose: Spool administration

Process Definitions SCP_SPAD_xxx

Installation Check

  • Purpose: check whether the spool system is installed and configured
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SPAD_Installation_Check

Run ABAP program RSPO0055. Check the spool list of the job for errors.

Delete old Spool Requests

  • Purpose: delete old spool requests
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SPAD_Delete_Old_Spool_Requests

Run ABAP program RSPO0041 with a (temporary) variant.

These are the recommended values for the variant:

Parameter Name Value
Client *
Requests past expiration date X
Minimum age in days

Log instead of dialog boxes? X
COMMIT all ... Spool requests 50

Alternatively run ABAP program RSPO1041 with a (temporary) variant

Delete old Joblogs

  • Purpose: delete old joblogs
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SPAD_Delete_Orphaned_Joblogs

Run ABAP program RSTS0024 with a (temporary) variant.

Consistency Check

  • Purpose: check the consistency of the spool system
  • Automation type: ABAP program
  • Procedure: Process Definition SCP_SPAD_Consistency_Check

Run ABAP program RSPO0043 with a (temporary) variant. Check the spool list of the job for errors.

These are the recommended values for the variant:

Parameter Name Value
Release locks after .. minutes 10

Alternatively run ABAP program RSPO1043 with a (temporary) variant

Transaction SPRO

  • Purpose: Customizing: Execute Project
  • Automation type: BDC
  • Procedure:

Transaction ST11

  • Purpose: Error Log Files
  • Automation type: BDC
  • Procedure:

Transaction ST22

  • Purpose: ABAP Runtime Error
  • Automation type: ABAP program
  • Procedure:

Process Definition SCP_ST22

Transaction STMS

  • Purpose: Transport management system
  • Automation type: Export/Import
  • Procedure:

SCP_Configure with STMS (and STMS_QA)

Transaction STRUST

  • Purpose:
  • Automation type: Export/Import
  • Procedure:

SCP_Configure with STRUST

Transaction STRUSTSSO2

  • Purpose:
  • Automation type: export/import
  • Procedure: SCP_Configure with STRUST and RFC

Transaction SU01

  • Purpose: Maintain users
  • Automation type: RFC-enabled function modules

Lock User

  • Procedure:

Process Definitions SCP_SU01_Control_User, SCP_SU01_Control_Users, and SCP_SU01_Change_User_Password User master can be exported and reimported. SCP_Configure with USER

Transaction SU10

  • Purpose: Mass changes users
  • Automation type: RFC scripting

Lock/Unlock Users

  • Procedure:

See SU01

Transaction SLICENSE

  • Purpose:
  • Automation type: Export/Import
  • Procedure: SCP_Configure with LICENSE

Also add process SCP_Change_SAP_SID as the first step of post-processing if the target SID is different from the source SID (which is normally the case). This is already done in the default template.

Transaction SWU3

  • Purpose: Automatic Workflow Customizing
  • Automation type: BDC
  • Procedure: Process Definition SCP_SWU3

Transaction UNIX

  • Purpose:
  • Automation type: BDC
  • Procedure:

Transaction WE19

  • Purpose: Test Tool for IDOC Processing
  • Automation type: ABAP Program
  • Procedure:
    • RSQOWKMA

Transaction WE20

  • Purpose: Partner profiles
  • Automation type: ABAP Program
  • Procedure: Process Definition SCP_WE20_Activate_Partner_Profiles

Transaction WE21

  • Purpose: Ports in IDoc processing
  • Automation type: RFC scripting
  • Procedure: Process Definitions SCP_WE21_xxx

ABAP Program automation

  • ABAP Program: RBDAPP01
    • Purpose: Inbound Processing of Idocs Ready for Transfer
    • Procedure:
  • ABAP Program: RBDMANI2
    • Purpose: Manual Processing of Idocs: Post Idocs Not Yet Posted
    • Procedure:
  • ABAP Program: RSADRCK2
    • Purpose: User without address
    • Procedure:
  • ABAP Program: RSADRCK1
    • Purpose: Address management check report
    • Procedure:
  • ABAP Program: RSCCUSND
    • Purpose: CUA: Distribution of the User Master Records
    • Procedure:
  • **ABAP Program: RSBTONEJOB **
    • Purpose: CUA: Message Processing I
    • Procedure:
  • ABAP Program: RSEOUT00
    • Purpose: Test Outbound Processing
    • Procedure:
  • ABAP Program: RBDMANIN
    • Purpose: Reposting of IDocs (ALE)
    • Procedure:
  • **ABAP Program: RS_TRANSTRU_ACTIVATE_ALL **
    • Purpose: activate all active transfer structures for a source system
    • Procedure:

Table truncation

SAP tables can be truncated using

  • DB vendor tools
  • JDBC
  • Control file for R3trans

Following tables have to be truncated:

  • ALCONSEG
  • ALSYSTEMS
  • DBSNP
  • DBSTATHORA
  • DBSTAIHORA
  • DBSTATIORA
  • DBSTATTORA
  • MONI
  • OSMON
  • PAHI
  • SDBAD
  • SDBAH
  • SDBAP
  • SDBAR
  • DDLOG
  • TLOCK
  • TPFHT
  • TPFET

There are more candidates for truncation:

  • CRMRFCPAR
  • CRMPRLS
  • RFCATTRIB
  • RFCCHECK
  • DBCON
  • RFCDES
  • RFCDESSECU
  • RFCDOC
  • RFCTRUST
  • RFCSYSACL
  • RSECACHK
  • RSECACTB
  • RSECTAB
  • RZLLITAB
  • INSTVERS
  • TBLSYSDEST
  • TPFET
  • TPFHT
  • TPFID

DB vendor tools / JDBC

Once the DB is copied over, the tables can be truncated using the standard DB tools provided by the database vendor. Alternatively we could use JDBC to access the database.