SAP SOLUTIONS FOR GOVERNANCE, RISK, AND COMPLIANCE How-To Guide How to Configure Set Column Fields for Reporting Display for Process Control 2.5 SAP GRC Regional Implementation Group Applicable Releases: SAP GRC Process Control 2.5 IT Practice / Topic Area: GRC GRC / Process Control IT Scenario / Capability: GRC / Process Control October 2008
19
Embed
How to Configure Set Column Fields for Reporting Display ... · This activity is used to enhance the report columns in a Process Control report. 3.1 Configure Set Column Fields for
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP SOLUTIONS FOR GOVERNANCE,RISK, AND COMPLIANCE
How-To Guide
How to Configure Set Column Fieldsfor Reporting Display for ProcessControl 2.5
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered
trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented andimplemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world.
All other product and service names mentioned are thetrademarks of their respective companies. Data contained
in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAPGroup 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 suchproducts and services, if any. Nothing herein should be
construed as constituting an additional warranty.
These materials are provided “as is” without a warranty of
any kind, either express or implied, including but notlimited to, the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the
information, text, graphics, links or other items contained
within these materials. SAP has no control over theinformation that you may access through the use of hot
links contained in these materials and does not endorse
your use of third party web pages nor provide any warranty
whatsoever relating to third party web pages.
SAP NetWeaver “How-to” Guides are intended to simplify
the product implementation. While specific product
features and procedures typically are explained in a
practical business context, it is not implied that thosefeatures and procedures are the only approach in solving a
specific business problem using SAP NetWeaver. Should
you wish to receive additional information, clarification or
support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”)
included in this documentation are only examples and are
not intended to be used in a productive system
environment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.
SAP does not warrant the correctness and completeness of
the Code given herein, and SAP shall not be liable for
errors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally or
grossly negligent.
Disclaimer
Some components of this product are based on Java™. Anycode change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not be
modified or altered in any way.
Document HistoryDocument Version Description
1.10 Update after external review
1.00 Document created
Typographic ConventionsType Style Description
Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.
Cross-references to otherdocumentation
Example text Emphasized words orphrases in body text, graphictitles, and table titles
Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.
Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.
<Exampletext>
Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.
EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.
IconsIcon Description
Caution
Note or Important
Example
Recommendation or Tip
Table of Contents
1. Business Scenario and Background Information ..........................................................1
4. Comments and Feedback ............................................................................................. 14
1. Business Scenario and BackgroundInformation
SAP GRC Process Control is a solution for internal controls management that enables members ofaudit and internal controls teams to gain better visibility into key business processes and ensure ahigh level of reliability in financial statement reporting.
Report Center is a central repository providing users with summary and detailed reports. Reports canbe personalized by user or for the entire company by adding, removing or changing the order ofpredefined fields (columns).
In this documentation, we will discuss in details concerning how to configure IMG setting of “SetColumn Fields for Reporting Display”.
2. PrerequisitesPC 2.5 has successfully installed and the Report Work Center displays the summary and detailedreports.
3. Step-by-Step ProcedureThis activity is used to enhance the report columns in a Process Control report.
3.1 Configure Set Column Fields for ReportingDisplay
A group of columns in a report is called a field group. For each Process Control report, there is apre-defined field group that you can customize at the system level. Each Process Control report ismapped to a report type. Before you can customize a report, you need to know the report type.
1. Log on to Process Control 2.5 system.
2. Execute Transaction SM30. And Enter “GRPCREPORT” for Table/View.
3. Click on Display button.
4. Note down the key for the report that you want to set the columned fields. For example, the keyfor “Organization and Process Structure Report” is H1A.
Note: If you do not see the key, click on “Customize Local Layout (ALT + F12)” and selectOptions.
On the Expert tab, check “Show Keys in all Dropdown Lists”. Click OK. Redisplay the table viewagain, you will see the key.
5. Go to the IMG by executing transaction code SPRO -> SAP Reference IMG.
6. Expand the node of GRC Process Control -> Reporting.
7. Execute Set Column Fields for Reporting Display. The Determine Work Area window will show.
8. Enter the technical key in the Work Area, such as “*H1A*” and click on F4 dropdown. Select theField Group.
Click on green check. The Field Group Overview page will display.
9. Click on icon to change to edit mode.
10. Click the “Import S Table Entries (or CLT + F12)” . The table is automatically populated withconfigurable attributes for the field group.
11. The field in column “n. List” is not checked will display as default.
12. Before making the change, log on to NWBC and access the Report Center to check the defaultdisplay.
13. Click on “Organization and Process Structure link. Note: We are using this report as anexample.
14. Click on Go button. The report will show with two field columns.
15. Go back to the Field Group View and uncheck the “PROCESS_T” and save.
16. Run the same report again from NWBC. The report will show the Subprocess field.
3.2 Adjust the field display order...
1. You could adjust the position of the field columns; for example, put the Subprocess field inbetween the Owner and Significance field.
2. Take a look at the position of the field first. The position of PROCESS_T is 17. The position ofRESP_PERS_T is 46. And the position 49 is not being used.
3. Highlight the row of PROCSS_T.
4. Click on copy as (F6) button.
5. Change the Screen Position from 17 to 49 and hit enter.
6. There will be two PROCESS_T field.
7. Highlight Position 17 row and delete it.
8. Save.
9. Re-run the report from NWBC. The field position will be updated.
3.3 Q&A...
1. After the customization, if customer upgrade to next SP, say from PC 2.5 SP4 to SP5, what isthe impact? Will all IMG configuration preserved or they have to redo the configuration?
[Answer] Changes made in Set Column Fields for Reporting Display are in "customernamespace" so they are not affected by SP implementation.
2. Is there any way to display the text of the Field Name by viewing the Field Group table?
[Answer] Unfortunately not, in IMG you will see always only the fields name not a text.
3. Will the user level personalization higher than the global system level personalization?
[Answer] Yes, the "user level personalization" from reporting selection screen has priority overthe "system level personalization" described in this document.
4. Is there other way to find the field group besides using the key?
[Answer] The field group in IMG has "hard coded" prefix "GRPC_REPORT_DATA_". Customercan use this to find and display the field group.
4. Comments and FeedbackBoth comments and feedback are very welcome. Please send them to: