GRC TABLES

  Let's dive into some of the tables available for SAP GRC.

GRACFUNC - Function

GRACFUNCT - Function Description Translations

GRACFUNCACT - Function Action Relationship

GRACFUNCPRM - Function Action Permission relationship

GRACSODRISKFUNC - SOD Risk Function Relationship

GRACRULESET - Rule Set

GRACRULESETT - Rule Set Description

GRACORGRULE - Organization Rules

GRACACTRULE - SOD Action Rule Detail

GRACSODRISKT - SOD Risk Description

GRACSODRISK - SOD Risk

GRACSODRISKOWN - SOD Risk Owner

GRACMITROLE - Role mitigating control assignment

GRACMITUSER - User mitigating control assignment

GRACCRPROFILE - Critical Profile Rule

GRACCRROLE - Critical Role Rule

GRACBPROC - Business Process

GRACBPROT - Business Process Description

GRACMGRISKD - Risk Analysis Management Sum data for Batch Risk Analysis.

HRP5320 - Defined mitigation controls

GRACUSERPRMVL - User Permission Violation Table

GRACFFLOG - Details related to Firefighter ID Log On Information

GRACFFREPMAPP - FFLOG and Repository Mapping for Firefighters

GRACACTUSAGE - Action Usage

GRACAUDITLOG - Security Audit Log table

GRACSYSTEMLOG - System Security Log table

GRACCHANGELOG - Data Change Log table

GRACREASONCOD - Master table for Reason Codes

GRACREASONSYS - Reason Code and System assignments

GRACFFCTRL - Maintain assignment of FF ID or Role to Controllers

GRACFFOBJECT - Maintain SPM Firefighter ID and Role details

GRACFFUSER - Maintain SPM Firefighter Assignment to FF ID/Roles

GRACROLE - Role

GRACROLEAPPRVR - Role Approver

GRACROLESTATUS - Role Status Table

GRACROLETYPE - Role Type Table

GRACMTH - GRC Methodology

GRACMTHT - GRC ERM Methodology Text

GRACREQ - Request Header

GRACREQPROVITEM - Line Items Associated with Request

GRACREQUSER - User Associated with Request

GRACEUPCONFIG - End User Personalization Fields

GRFNMWCNPATH - MSMP Path

GRFNMWCNROUTE - MSMP Route Mapping

GRFNMWCNSDEF - MSMP Stage Definition

GRFNMWRTAPPR - Current approver of Access Request (GRFNMWRTSTAPPR only during runtime)

SWWUSERWI - Task ID assigned to users

HRUS_D2 - Delegation table

Security Fiori important Tables , T-codes and Queries

  Important T-codes:

/UI2/FLPD_CUST - Launchpad Designer (can add/remove catalogue/group/Tile/TM  -Browser view)

/UI2/FLPCM_CUST - FLP content manager (ADD/Remove Tiles from catalogue) (maintain catalogue present in role)  (SAP GUI view)

/UI2/FLPCAT -Fiori catalogue maintenance

/UI2/FLPCA- Launchpad content aggregator (roles vs catalogue)

SCTS_HTA - Transport HANA Studio role changes (add security package and execute)

Important Tables :

USOBHASH - Table Service name(Field: Object name) vs HASH value(Field: Name)

AGR_BUFFI - Catalogue vs Role, Group vs Role , Hash Value Vs Role

HANADB SQL Queries -

1) To get details of error GUID code

call sys.get_insufficient_privilege_error_details('GUID' , ? )

2) AGR_USERS -

select grantee, role_name from granted_roles;

select * from granted_roles;

select * from granted_roles where role_name like '%SECURITY_Y%'

select grantee, role_name from granted_roles where  grantee in ('Gitesh') and role_name <> 'PUBLIC';

3)USR02

Select * from users;

4)To find Roles having access to Root package/particular package-

Select Grantee from Granted_privileges where OBJECT_NAME= '.REPO_PACKAGE_ROOT'

Project plan for conversion from ECC to S4Hana

 Let's dive deeper into each phase of the ECC to SAP S/4HANA migration project plan:

Phase 1: Planning (Weeks 1-4)

- Define project scope, goals, and timeline

- Identify stakeholders and their roles

- Develop a detailed project schedule

- Establish a budget and resource plan

- Define project governance and decision-making processes

Phase 2: Assessment and Preparation (Weeks 5-12)

- Analyze current ECC system landscape and identify:

    - Customization and integration points

    - Data quality and cleansing requirements

    - Business process and workflow changes

- Develop a data migration strategy

- Set up a test environment for S/4HANA

- Install and configure S/4HANA sandbox system

Phase 3: System Setup and Configuration (Weeks 13-20)

- Install and configure S/4HANA production system

- Set up organizational structures and master data

- Configure business processes and workflows

- Integrate with other systems (e.g., CRM, SCM)

- Develop customizations (if necessary)

Phase 4: Data Migration (Weeks 21-28)

- Migrate data from ECC to S/4HANA using:

    - SAP Data Migration Cockpit

    - SAP LT Replication Server

    - Other tools and methods

- Validate data quality and integrity

- Perform data reconciliation

Phase 5: Testing and Quality Assurance (Weeks 29-36)

- Develop test cases and scenarios

- Perform:

    - Unit testing

    - Integration testing

    - System testing

    - User acceptance testing (UAT)

- Identify and fix defects

Phase 6: Deployment and Go-Live (Weeks 37-40)

- Finalize deployment preparations

- Execute go-live activities

- Provide post-go-live support

Phase 7: Hypercare and Optimization (Weeks 41-52)

- Provide hypercare support

- Monitor system performance

- Identify optimization opportunities

- Implement post-go-live enhancements

Additionally, consider the following best practices:

- Engage stakeholders and end-users throughout the project

- Develop a comprehensive training plan

- Establish a change management process

- Monitor and report on project progress

- Identify and mitigate risks