You are on page 1of 4

Central Process Catalog

PDF download from SAP Help Portal:
Created on August 28, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see for additional trademark information and notices.

Table of content

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 4

Table of content 1 Central Process Catalog 1. Page 2 of 4 .2 Documenting Controls Centrally PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.1 P-CO-R Assignment 1.

You then assign one or more risks (R) to the combination of process and control objective. any changes made centrally to those process steps automatically apply to the organizational unit. you enter the objectives of the controls contained in the process and the risks that could prevent the control objectives from being achieved. Page 3 of 4 . All rights reserved.1 P-CO-R Assignment Use In the central process catalog. you select a control objective category that has been created in Customizing for MIC. Prerequisites In Customizing for MIC under Edit Attributes ® Attributes with Dependent Attributes . A process step can be defined in the central process catalog as a control. The central process catalog is compiled by the power user or by the person assigned to the role containing the task Edit Central Process Catalog (EDITCPCAT) . and are directly or indirectly related either to financial reporting (to satisfy the requirements of section 404 of the Sarbanes-Oxley Act) or to disclosure controls and procedures (to satisfy the requirements of section 302). to represent the processes necessary for section 404. you assign account groups to any process that influences them. Processes are located at the lowest level of the process group hierarchy. A risk is a potential event that adversely impacts the desired outcome of a control objective. Use The central process catalog simplifies the tasks of the individual organizational units and in so doing reduces the costs of an SOA project. A process can be a subnode of any number of different process groups. you specify general control attributes as well as the central attributes for the process step (see Documenting Controls Centrally).!--a11y--> 1 Central Process Catalog Definition The central process catalog contains processes and process steps that are created centrally in the corporate group. central attributes are made for a process as well as for the process steps (such as the transaction type for a process or whether the process is industry-specific). All objects defined in the central process catalog and all assignments are time-dependent. Integration You can define values for the transaction type in Customizing for MIC under Edit Attribute Values . The control objective category determines PUBLIC © 2014 SAP SE or an SAP affiliate company. Structure The central process catalog contains processes that are arranged in a process group hierarchy. The individual organizational units of the organizational hierarchy can accept the processes and their respective process steps unchanged by referencing them as they are in the central process catalog. Any additional attributes that are required need to be added subsequently by the individual organizational unit copying that process. Features For each control objective. you define the objectives of the process steps defined as controls in that process. By doing so. you specify the following assignments for a process: · Assignment of control objectives and risks (P-CO-R assignment) With the P-CO-R assignment. In the central process catalog. Besides the attributes. approx. Each process consists of process steps that are organized in a specific sequence. · Assignment of account groups The SOA requires companies to document processes that have a significant impact on financial statements. If the organizational unit references the process steps of a process. You can choose from all account groups that were defined as significant for the corporate group in the account group hierarchy. you assign one or more control objectives (CO) to a process (P). or they can copy them and adjust them to suit that particular organizational unit. 10 process groups each with 5 to 10 processes are required. For this reason. In such cases. !--a11y--> 1. the power user has created control objective categories and one or more control types for each control object category. Experience at corporate groups has so far shown that.

This means that the validity period of a control objective must fall within that of the process. you select the appropriate control type.P-CO-R tab page. · All settings for the process to which the control belongs have been made in the central process catalog (for example. you have access to the account groups and FS assertions that were assigned to the corresponding process in the central process catalog. For the assignment. · You have authorization for the task Edit General Control Attributes in Central Process Catalog . Features Documenting a control involves defining various attributes and assignments. In the Control . PUBLIC © 2014 SAP SE or an SAP affiliate company. Example Process: Order processing Control objective: Only authorized transactions are posted Risk: The transaction is not reviewed conscientiously !--a11y--> 1. Furthermore. All rights reserved. For the assignment. the central attributes serve as default settings that simplify work for the organizational units.which control types an organizational unit can later enter as an attribute for a control when accepting processes and documenting controls. control objective. minimal. The validity periods of the process. These central control attributes can be changed by organizational units that have copied the process with the control. In this case. The following are examples of general control attributes: · · · · · · · · Control Significance Nature of Control Control Purpose Control Automation Control Trigger Assessment Attributes Test Attributes Control Relevance In the Control .Accounts tab page. you assign FS assertions from account groups to the control. you assign one or more risks to the control. the assignment to a control objective and to a risk). once the PCO-R-C assignment has been made. this control then has to be documented centrally using control attributes in a different Web application. you select the assertions that are relevant for the control. From these. Moreover. For each risk. · The task is scheduled (see Scheduling Tasks). Page 4 of 4 . and the validity period of the risk must fall within that of the control objective. you can specify what would be the qualitative impact of the risk (such as negligible. · All attributes for the process step to which the control corresponds have been defined in the central process catalog. You can define the possible values in Customizing under Edit Attribute Values . and risk must be compatible.2 Documenting Controls Centrally Use When a process step has been defined as a control in the central process catalog. you specify which condition could cause the risk to come into play and which consequence this could have. you have access to all risks that are assigned in the PCO-R (Process – Control Objective – Risk) structure to the relevant process in the central process catalog (see P-CO-R Assignment ). immense). Prerequisites · The values that the control attributes can take have been defined in Customizing for MIC under Edit Attribute Values .