Search
Related topics are listed below.
CHaRM Integration Requirements
CHaRM Integration Requirements
The ActiveControl ChaRM integration is fairly unique in its setup, in that the integration is primarily based at a transport level and not a ticket/business task level as is the case of most other ActiveControl integrations with 3rd-Party ITSM systems. The following…
Why use both ActiveControl and ChaRM?
CHaRM Integration Requirements » Why use both ActiveControl and ChaRM?
The customer for whom the ActiveControl / ChaRM integration was originally developed had a few contributing reasons for wanting to run both tools in parallel: 1) They had previously had some ChaRM Retrofit overwriting Project change resulting in a loss of work. This…
Architecture of ActiveControl
Architecture of ActiveControl
The architecture of ActiveControl can be broken down into several core components: 1) a Domain Controller 2) other participating satellite SAP systems. 3) Access methods – consisting of a Windows GUI client software, Web UI and SAPGUI screens. 4) Integration…
Table: /BTI/TE_INT_SYST
Core Configuration » Table: /BTI/TE_INT_SYST
/BTI/TE_INT_SYST is a standard configuration table as part of the Integration Framework, and is required for the ChaRM integration. Field Explanation EXTSYS_NO Integration System Number, this is a unique numerical identifier of the system…
Table: /BTI/TE_TVARV
Core Configuration » Table: /BTI/TE_TVARV
/BTI/TE_TVARV is a standard configuration table used for storing various configuration variables and parameters for other functionalities within ActiveControl. Field Explanation of Field Variable Name This is where the variable/parameter…
Table: /BTI/TE_INT_MAPP
Core Configuration » Table: /BTI/TE_INT_MAPP
/BTI/TE_INT_MAP is a standard configuration table as part of the Integration Framework. It is used to define the mapping between ActiveControl fields values and their equivalent in the 3rd Party System – at a Business Task level. Field Explanation of…
Table: /BTI/TE_INT_FMAP
Core Configuration » Table: /BTI/TE_INT_FMAP
/BTI/TE_INT_FMAP is a standard configuration table as part of the Integration Framework. This table is used in the ChaRM integration to map ChaRM custom fields to ActiveControl standard / custom fields. Field Explanation of Field …
Core Configuration
Core Configuration
This section details the core configuration steps that are required to setup the ActiveControl/ChaRM integration. The Integration configuration is maintained through the SAP standard SM30/31 transactions where table entries can be created and updated. …
Table: /BTI/TE_FORM_CON
Core Configuration » Table: /BTI/TE_FORM_CON
/BTI/TE_FORM_CON is a new configuration table as part of the Integration Framework, that is used to map the relevant ActiveControl and ChaRM fields at Transport Level. Field Explanation of Field EXTSYS_NO Integration system number [from…
Introduction
Introduction
ActiveControl include an Integration Framework to allow easy bi-directional communication with other ITSM tools. This Integration Framework can be utilised to manage outbound interactions with external systems (including queuing, re-sends, error processing and…
Table: /BTI/TE_INT_LOC
Core Configuration » Table: /BTI/TE_INT_LOC
This can be used in newer versions of ActiveControl to trigger an approval in ActiveControl based on a ChaRM status move. Example Customer Configuration The below illustrates some example configuration of /BTI/TE_INT_LOC table at a customer implementation of the…
User Exit (Transport Form [Group] Mismatching)
Optional Configuration » User Exit (Transport Form [Group] Mismatching)
An optional User Exit was created for a Basis Technologies customer where there Transport Form Groups did not match the corresponding field values in ChaRM. The reason for the Group mismatch was that this customer had subdivided their Transport Form groups out per…
New Project Creation
Other Information » New Project Creation
Whenever a new ChaRM projects gets created for which you want Business Tasks to be created against the CRs, then this needs to be added to project mapping /BTI/TE_INT_CONV. If the project does not exist in this Conversation table, then it will NOT be picked up by…
Table: /BTI/TE_CONTROL
Core Configuration » Table: /BTI/TE_CONTROL
An entry must be maintained in standard /BTI/TE_CONTROL table in the ActiveControl Domain Controller for the system user that moves the CR from one status to another status in ChaRM. *Note that this is not a requirement for a standard ActiveControl. implementation,…
Table: /BTI/TE_INT_CONV
Core Configuration » Table: /BTI/TE_INT_CONV
The integration framework can also take into account value conversions. For instance where a value in ActiveControl could equal one thing maybe its corresponding value in an external system could be different although they both mean the same thing. BTI/TE_INT_CONV is…
Domain Controller downtime
Other Information » Domain Controller downtime
If the ActiveControl Domain Controller is unavailable due to Solution Manager being unavailable, the ChaRM is also unavailable. This means there is no risk of Business Tasks not getting created, and it is simply a case of running the /BTI/TE_INTEF_POLL_CHARM program…
Program: /BTI/TE_INTEG_POLL_CHARM
Core Configuration » Program: /BTI/TE_INTEG_POLL_CHARM
/BTI/TE_INTEG_POLL_CHARM is what polls ChaRM to see what new Change Documents created (or updates made to any field), and creates the Transport Forms for any new Transports against those CDs. The program needs to be scheduled to run every 5-10 minutes in the…