‎2008 Feb 21 7:11 AM
‎2008 Feb 21 7:22 AM
Hi,
SAP is a transaction-oriented system. Between an order and cash on different ends of the financial chain, there are a number of steps. SAP establishes the horizontal chain, but does not take account of the controls that have to be carried out (vertically) across this chain. Runbook is the complement to SAP: it makes data from SAP provable and quicker to process for the Period-End Closing.
Runbook is the integrated and guaranteed SAP solution that carries out all operational controls within your objectives for risk management. It has a highly safe control mechanism and records all risk-related decisions at every operational level. Moreover, Runbook provides extensive possibilities for tracking & tracing, which you can use to constantly improve your system for risk management.
Runbook offers a cockpit style status overview and monitoring capabilities. With an integrated authorization concept to view, change and manage transactions and activities. It is user-focused and management-driven software. Runbook never runs away with your business, but ensures that you can run your business in a controlled way.
Runbook also provides the evidence of which matters have been dealt with at the various management levels. The checks are made up of main elements (business divisions, business processes) and secondary elements (impact on financial reports, type of control, risk area, significance and internal control objectives).
External Audit / IC Annual Report
Runbook provides a detailed manual for the operational internal control scenarios, with a description of the duties of the controller and the responsible person. Every scenario is intended for a specific part of the business process. Frequently used SAP transactions can be saved and executed from the Runbook menu in your SAP screen.
IC Evaluation / Overview of controls
Runbook also provides the possibility of evaluating controls. This is done on the basis of the control definition. For example, impact on the financial reporting, type of control, control definition(s).
Effectiveness of internal controls
Control results assessment based on strengths and weaknesses can be performed within the Runbook, as well as the reporting of current risks (i.e. control result multiplied by significance factor). By setting objectives, registering results and reporting control results, continual business process improvements can be achieved.
Monitoring Control Activities
Controls are monitored based on execution logging and control result registration. A history log provides evidence of control execution including date/time and operator.
Operational control activities
Each control is set up as a next step in the control process and offers direct access to transaction/report execution. After the execution the control close (with compulsory registration) forms the starting point for the control results of the workflow process.
RUNBOOK Business Model integration
Risk management implementation in the Runbook comprises seven steps:
1. Select organizational units relevant for Internal Control result registration and sign-off, starting with the most significant business units and departments (e.g. Sales).
2. Select business process and sub processes relevant for Internal Control result registration and sign-off.
3. Detailed documentation of risks per sub process. (e.g. based on Failure Mode Effect & Analysis template).
4. Mapping of risk impact on financial accounts (e.g. general ledger account groups).
5. Selection of SAP transactions, programs and configuration settings used for Internal Control analysis and result registration.
6. Setup of Runbook step with assignment of checker, SAP transaction, program, batch job or operational procedure.
7. Setup of Internal Control template to be configured upon customer demand.
Thanks And
please reward points if helpful
‎2008 Feb 21 7:22 AM
Hi,
SAP is a transaction-oriented system. Between an order and cash on different ends of the financial chain, there are a number of steps. SAP establishes the horizontal chain, but does not take account of the controls that have to be carried out (vertically) across this chain. Runbook is the complement to SAP: it makes data from SAP provable and quicker to process for the Period-End Closing.
Runbook is the integrated and guaranteed SAP solution that carries out all operational controls within your objectives for risk management. It has a highly safe control mechanism and records all risk-related decisions at every operational level. Moreover, Runbook provides extensive possibilities for tracking & tracing, which you can use to constantly improve your system for risk management.
Runbook offers a cockpit style status overview and monitoring capabilities. With an integrated authorization concept to view, change and manage transactions and activities. It is user-focused and management-driven software. Runbook never runs away with your business, but ensures that you can run your business in a controlled way.
Runbook also provides the evidence of which matters have been dealt with at the various management levels. The checks are made up of main elements (business divisions, business processes) and secondary elements (impact on financial reports, type of control, risk area, significance and internal control objectives).
External Audit / IC Annual Report
Runbook provides a detailed manual for the operational internal control scenarios, with a description of the duties of the controller and the responsible person. Every scenario is intended for a specific part of the business process. Frequently used SAP transactions can be saved and executed from the Runbook menu in your SAP screen.
IC Evaluation / Overview of controls
Runbook also provides the possibility of evaluating controls. This is done on the basis of the control definition. For example, impact on the financial reporting, type of control, control definition(s).
Effectiveness of internal controls
Control results assessment based on strengths and weaknesses can be performed within the Runbook, as well as the reporting of current risks (i.e. control result multiplied by significance factor). By setting objectives, registering results and reporting control results, continual business process improvements can be achieved.
Monitoring Control Activities
Controls are monitored based on execution logging and control result registration. A history log provides evidence of control execution including date/time and operator.
Operational control activities
Each control is set up as a next step in the control process and offers direct access to transaction/report execution. After the execution the control close (with compulsory registration) forms the starting point for the control results of the workflow process.
RUNBOOK Business Model integration
Risk management implementation in the Runbook comprises seven steps:
1. Select organizational units relevant for Internal Control result registration and sign-off, starting with the most significant business units and departments (e.g. Sales).
2. Select business process and sub processes relevant for Internal Control result registration and sign-off.
3. Detailed documentation of risks per sub process. (e.g. based on Failure Mode Effect & Analysis template).
4. Mapping of risk impact on financial accounts (e.g. general ledger account groups).
5. Selection of SAP transactions, programs and configuration settings used for Internal Control analysis and result registration.
6. Setup of Runbook step with assignment of checker, SAP transaction, program, batch job or operational procedure.
7. Setup of Internal Control template to be configured upon customer demand.
Thanks And
please reward points if helpful
‎2008 Feb 21 7:23 AM
hii
here id a pdf on runbook
follow the link\
https://websmp202.sap-ag.de/~sapidp/011000358700009390382004E/files/Proxyon_Runbook.pdf
do reward if helpful