Controls

DataSource Transactional Data 0EHSM_HSS_RAS_03

Use

You can use this DataSource to extract controls that have been entered for a risk from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). The DataSource extracts the data from the following nodes of the following business objects:

  • Business object EHHSS_RISK

    • ROOT

    • REVISION

    • CONTROL

  • Business object EHHSS_AGENT/EHFND_CHEMICAL

    • ROOT (only the ID field)

  • Business object EHHSS_RISK_ASSESSMENT

    • ROOT (only the fields KEY and ID)

  • Business object EHFND_LOCATION

    • ROOT (only the ID field)

  • Business object EHHSS_JOB

    • ROOT (only the ID field)

The DataSource extracts data only for those risks for which a control has been entered.

Technical Data

Application Component SAP EHS Management (EHS-MGM-RAS)
Exchange Available as of Release Component Extension 2.0 for SAP EHS Management
Shipment SAP NetWeaver 7.0 BI Content Add-On 7 SP02
Content Versions EHM200, EHM300
RemoteCube-Capable No
Delta-Capable Yes
Extraction from Archives No
Verifiable No

Prerequisites

  • You have configured the DataSource in Customizing in the source system under Start of the navigation pathSAP EHS Management Next navigation step Foundation for EHS Management Next navigation step Analytical Reporting Next navigation step Configure ExtractorsEnd of the navigation path.

  • The BAdI implementation BADI_EHFND_FW_BI_BOPF_OBJ_LIST must be an active default implementation of the BAdI BADI_EHFND_FW_BI_OBJ_LIST. For more information, see Customizing in the source system under Start of the navigation pathSAP EHS Management Next navigation step Foundation for EHS Management Next navigation step Analytical Reporting Next navigation step BAdI: Determination of Objects to ExtractEnd of the navigation path.

  • The BAdI implementation BADI_EHFND_FW_BI_BOPF_EXTRACT must be an active default implementation of the BAdI BADI_EHFND_FW_BI_EXTRACTOR. For more information, see Customizing in the source system under Start of the navigation pathSAP EHS Management Next navigation step Foundation for EHS Management Next navigation step Analytical Reporting Next navigation step BAdI: Extraction of One ObjectEnd of the navigation path.

Data Modeling

Delta Update

The delta update used for this DataSource is AIED (After-Images with Deletion Indicator by Extractor). The deciding field for the update is BW_DELTATIMESTMP.

Fields of Origin for the Extraction Structure

Fields in the Extraction Structure Description of the Field in the Extraction Structure Table of Origin Field in the Table of Origin
ID Risk ID - -
RISK_ROOT_KEY_REF Risk Key - -
HAZARD Hazard - -
HAZ_CAT Hazard Category - -
RAS_ROOT_KEY_REF Risk Assessment Key - -
RAS_ID Risk Assessment ID - -
RAS_TYPE Risk Assessment Type - -
LOCATION_ID Location ID - -
OPERATION_STATUS Operational Status - -
AGENT_ID Agent ID - -
AGENT_KEY_REF Agent Key - -
JOB_ID Job ID - -
SPLIT_DATE Revision Date - -
STATUS Risk Status - -
CONTROL_KEY_REF Internal key of control instance - -
CONTROL Control - -
RESP_NAME Control Responsible Person - -
IMPL_STATUS Control Implementation Status - -
EFFECTIVN_CODE Control Effectiveness - -
HAZARD_CODE Control Hazard - -
PROPOSAL_IND Control Is Proposed - -
CNTRL_TYPE Control Type - -
CNTRL_SUBTYPE Control Subtype - -
GOAL_TARGET_CODE Target - -
GOAL_OBJECT_CODE Objective - -
GOAL_CTRL_EFFECT Desired Effect of Control - -
EFFECT_DET_DATE Control Effectiveness Evaluation Date - -
EFFECT_DET_CODE Source of Evaluation Results - -
NUM_UNACC_RISKS Number of Unacceptable Risks - -
NUM_INADEQ_CTRL Number of Inadequate Controls - -
BW_RECORDNUMBER Serial number of record since one risk can have multiple records Generated (by extractor) -
BW_RECORDMODE Record mode that allows flagging records for deletion in BW Generated (by extractor) -
BW_DELTATIMESTAMP Time stamp for delta load Input for extractor -

Extractor Logic

The extractor extracts only the most recent revision of a risk. The actual extractor logic is implemented as a BOPF determination of the transient node BI_CONTROLS of the business object EHHSS_RISK. The business object EHHSS_RISK saves references to the following business objects:

  • EHHSS_RISK_ASSESSMENT

  • EHFND_LOCATION

  • EHHSS_AGENT

  • EHFND_CHEMICAL

  • EHHSS_JOB

These references consist of internal keys (GUIDs). Except for agents, the extractor does not extract these internal keys. Instead, the extractor translates these keys into the ID of the corresponding business object instance. Because the agent IDs are not necessarily unique (depending on how the number range objects are maintained in Customizing), the extractor also extracts internal keys for agents.

The hazard category is not saved in the business object EHHSS_RISK directly. The extractor determines the hazard category from the customizing table EHHSSC_HAZARD.

The system determines the value for the CONTROL field in the following way:

  • If the PROPOSAL_IND field is false, the system fills the field with the value in the CONTROL_CODE field. In this case, the control’s name is the text of the control InfoObject.

  • If the PROPOSAL_IND field is true, the system fills the field with the title (PROPOSED_TITLE) that the user proposed for the new control.

The system determines the value for the CNTRL_TYPE field in the following way:

  • If the PROPOSAL_IND field is false, the system fills the field with the value in the TYPE field of the control catalog. The system determined the control catalog from the control BO instance that the system determined via the CONTROL_CODE field.

  • If the PROPOSAL_IND field is true, the system fills the field with the type (PROPOSED_TYPE) that the user proposed for the new control.

  • The control type gets the control priority from configuration as a three-digit prefix. This allows the system to sort the controls by priority.

The system determines the value for the CNTRL_SUBTYPE field in the following way:

  • If the PROPOSAL_IND field is false, the system fills the field with the value in the SUBJECT field of the control catalog. The system determined the control catalog from the control BO instance that the system determined via the CONTROL_CODE field.

  • If the PROPOSAL_IND field is true, the system fills the field with the type (PROPOSED_SUBJECT) that the user proposed for the new control.

The system determines the value for the RESP_NAME according to the ID in the RESP_ID field. The system extracts the last name and first name separated by a comma (last name, first name).

Verification of Key Figures

You can verify the key figures in the following way:

Key Figure

Verification

NUM_UNACC_RISKS

Counts the number of inherent risks, initial risks, and residual risks with evaluation Unacceptable in the most recent revision of the respective risk.

NUM_INADEQ_CTRL

Counts the number of controls with effectiveness Inadequate in the most recent revision of the respective risk.

Unsychronized Backup Recovery in BI System

The DataSource does not use an own time stamp management. The DataSource uses the generic delta functionality.