SAP ABAP IMG Activity MIC_XI (XI Message Interfaces for MIC)
Hierarchy
☛ FINBASIS (Software Component) Fin. Basis
   ⤷ FIN-CGV-MIC (Application Component) Management of Internal Controls
     ⤷ FOPC_CUSTOMIZING (Package) Customizing
IMG Activity
ID MIC_XI XI Message Interfaces for MIC  
Transaction Code S_SE3_50000264   (empty) 
Created on 20050510    
Customizing Attributes MIC_XI   XI Message Interfaces for MIC 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name MIC_XI    

Use

In this IMG activity, you find information on the Process Integration Content (XI Content), which is available for MIC. You configure this XI Content on the Integration Server in the Integration Builder delivered with SAP NetWeaver.

You can use the MIC XI Content for the following processes:

  • Uploading master data (for example, from objects in the central process catalog, controls of an organizational unit) from an external system
  • Uploading test logs or notifications from an external system in which automated or semi-automated control tests are performed

For more information about these processes, see the documentation in the SAP Library for MIC under XI Content for MIC.

For general information about process integration with SAP NetWeaver, see the documentation in the SAP Library for SAP NetWeaver under Key Areas of SAP NetWeaver -> Process Integration.

Features

MIC is connected to the Integration Builder by means of several message interfaces. The message interfaces are available in naming space http://sap.com/xi/MICSOA and are based on the following message types :

  • InternalControlLogNotification: Transfer of test logs relating to a control for a test timeframe. In the case of a semi-automated control, the tester assigned receives a workflow task whenever a test log is uploaded. In the case of an automated control, a workflow task is only generated once an issue has been created. This workflow task is forwarded to the person with the task Receive Issues from Effectiveness Test (RECE-EFISO). Prerequisites:
    • The process step is identified as a control.
    • The To Be Tested indicator is activated for the control.
    • The control is released for (semi-)automated tests (attribute Test Automation). Automation is used for the assignment of the testers
    • The transfer is made in the test timeframe of the relevant organizational unit.
    • The control is scheduled to be tested.
  • InternalControlControlCatalogRequest: Querying the test timeframes and the available controls. In particular, it is possible to select controls that are released for (semi-)automated testing and for which test logs can be transferred via message type InternalControlLogNotification. When the prerequisites for the transfer of test logs are fulfilled, the element IsOpenForAutomatedLogIndicator contains the value TRUE in the answer field (interface InternalControlControlCatalogResponse). If the prerequisites are not fulfilled, the element contains the value FALSE.
  • InternalControlTesterNotification: Notification of testers for (semi-)automated controls. The notifications can only be transferred in the same timeframe as the relevant organizational unit. In the case of semi-automated controls, the tester for the corresponding semi-automated test receives the notification. In the case of automated controls, the person who processes the issues for the control (with task RECE-EFISO) receives the notification.
  • InternalControlControlCatalogNotification: Creation of central objects such as process group, process, process step, control objective, management control, management control group, and account group. Furthermore, controls can be created for the organizational unit. In the case of controls that have been copied, the ID of the assigned process for the organizational unit and the ID of the organizational unit must be specified. In the case of referenced controls, the ID of the corresponding central control and the ID of the organization unit must be specified. In both cases, the subordinate central process must be assigned to the organizational unit.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG MIC_XI 0 XS40000002 Management of Internal Controls 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050510 
SAP Release Created in 600