The following configuration and set-up is deemed optional within an overall implementation ActiveControl, and will depend more on an individual SAP customer’s SAP landscape and desired processes.
General Configuration
| Activity | Details | Useful Knowledge Articles |
|---|---|---|
| Rules Engine: Testers | Create Tester Rules for the required scenarios, via the Rules Engine | Link |
| Transport of Copies | Configure any required Transport of Copies via /BTI/TE_TOCONFIG and /BTI/TE_VAUTOCON tables. | Link |
| Transport auto-naming convention | SAP transport short description can be automatically generated, via /BTI/TE_TR_DESC. | Link |
| Create Document Categories | Create the relevant Document Categories via /BTI/TE_ATT_CAT. | Link |
| Documentation Links | Define any customer documentation to be accessible via the ActiveControl Web Platform via /BTI/TE_HLP_LINK. | Link |
| Project Phases | Use SM31 to update table /BTI/TE_PHASE in the Domain Controller to reflect the project phases that your organisation may want to reflect within the ActiveControl Web UI. | Link |
| Switch on ActiveControl Backout | a) Within the target configuration in the Web Platform, enable the “Automatically create backup transport requests” for all required systems. NB Most organisations switch on Backout for Production systems only. b) Create a virtual system called BAK needs to be created in TMS within the transport domain of the intended systems where you will run Backout. c) set the STMS parameter tadirdeletions = “True” in each of the intended systems where you will run Backout. |
Link1 Link2 |
Multi-Track (N+n) Configuration
ActiveControl includes Merge and other functionality to help keep multi-track SAP landscapes synchronised and consistent.
| Activity | Details | Useful Knowledge Articles |
|---|---|---|
| Merge | Configure Merge Targets within ActiveControl as per your requirements. | Link |
| ShiftLeft: Conflict Analysis (0005) | Within the Targets and Transport Paths tab, open all Merge Target Systems and in the Analysis Types tab, switch on ‘Conflict Analysis’ and make it mandatory. | |
| In-Line Conflict Active Functions (SAP GUI) | Switch on the Inline Conflict Analysis related active functions via /BTI/TE_ACTIVE in the Domain Controller. | |
| In-Line Conflict Analysis (SAP GUI) | Use SM31 to update table /BTI/TE_INLINE in the Domain Controller to configure which systems should be checked for parallel development activity. For example, if systems ECD and EPD are parallel development systems, “Active” entries should be created here for ECD -> EPD and EPD -> ECD. |
|
| In-Line Conflict Analysis Systems (Web Platform) | In the Target configuration, ensure that you have entered a client number in the “Before Importing, check whether….” text box for the target. This is required so that ActiveControl knows what client to connect to for the analysis. |
System Specific Setup
Some additional configuration is required if you have specific types of SAP systems such as BW or non-ABAP systems, or if you want to manage BTP changes via ActiveControl
Please refer to the ActiveControl Administration Guide and online Knowledge Articles for full details of what is required, depending on your individual requirements.
Post your comment on this topic.