210 likes | 226 Views
Studio Maintenance Training October 20, 2003. Sets/Hierarchies and Reporting. Agenda. Sets and Hierarchies Sets/Hierarchies and Reporting Examples of Sets/Hierarchies Process for Maintaining Sets/Hierarchies SAP Transactions Sets/Hierarchies Security Next Steps. Sets and Hierarchies.
E N D
Studio Maintenance Training October 20, 2003 Sets/Hierarchies and Reporting
Agenda • Sets and Hierarchies • Sets/Hierarchies and Reporting • Examples of Sets/Hierarchies • Process for Maintaining Sets/Hierarchies • SAP Transactions • Sets/Hierarchies Security • Next Steps
Sets and Hierarchies • Sets are groups of SAP values or value intervals • Studio requirements include: • The ability to report and analyze information based on user defined groupings of SAP objects • User defined groupings will contain various nodes (parent-child levels) • User defined groupings may also be combinations of multiple objects and MPM attributes (ie: P&L Structure) • G/L Accounts, MPM Product, Product Type, Distribution Channels, Profit/Cost Center, Destination Geography, Document Type
Sets and Hierarchies • See handout for listing of custom hierarchies created for reporting T:\6-Wave 4\Sites\Studio\Reporting\Sets_Hierarchies\Hierarchy Listing 90903 • The following SAP transactions may be used to view sets/hierarchies: • GS03 – Display Sets • KAH3 – Display Cost Element Group • KDH3 – Display Account Group • KSH3 – Display Cost Center Group • KCH3 – Display Profit Center Group
Sets and Hierarchies • Go to “Extras > Check and help functions” in the menu bar • System generated reviews of sets/hierarchies include: • Check Completeness – Available for G/L accounts, profit center, cost center only. Reviews set/hierarchy for completeness and notifies of any missing values • Ambiguity Check – Available on all sets/hierarchies. Reviews set/hierarchy for any duplicate values.
Sets/Hierarchies and Reporting • Sets and hierarchies are required by the Studio for accurate and efficient reporting and analysis • Reporting requirements include: • A reporting and analysis solution to view data elements by user defined groupings • Flexibility to manipulate several user defined groupings into multi-dimensional views • Drill down/across functionality to analyze data efficiently
MPM Product Hierarchy by Destination Geography Hierarchy (BW)
Process for Maintaining Sets/Hierarchies • Regular and timely review of existing hierarchies • New SAP objects • Deleted or changed SAP objects • Studio Sustainment and business unit responsibility • Possible automated notification • Communication of changes to business units • Business unit requests for changes or creation of new hierarchies • Communication/initiation process • Timing of request and turn around (R3 and BW) • Impact of changes to other business units • Communication of changes to business units
Process for Maintaining Sets/Hierarchies • Other Key Issues • P&L roll-up for the Studio is a fixed structure that ties GL accounts and cost centers • Reclassifying GL Accounts/Cost Center combinations between existing nodes can be made by Studio Sustainment • Adding, changing, deleting nodes within the P&L structure requires development work by the BW team • Sets/hierarchies should be a complete representation of SAP objects • Ensure that the sets/hierarchies contain all SAP objects • Create a grouping for any unused SAP object to achieve completeness • Allows end users to quickly audit the hierarchy and/or check for any incorrect postings
SAP Transactions • Adding, deleting, changing sets/hierarchies can be done directly in R3 or via Excel upload to R3 • Sets/hierarchies are created and reviewed in R3, then extracted into BW • Maintaining Studio sets/hierarchies will be restricted with security access granted to certain individuals
SAP Transactions – R3 • To Add, Delete, Change sets/hierarchies directly in R3 use the following transactions: • GS02 – Change Sets • KAH2 – Change Cost Element Group • KDH2 – Change Account Group • KSH2 – Change Cost Center Group • KCH2 – Change Profit Center Group • You can find BPPs in Cyberdocs for these transactions – just use the T-Code for your search criteria in Cyberdocs. • DEMO – Change cost center group SSE_ALL
SAP Transactions – Excel Upload • Excel upload file may also be used to load sets/hierarchies into R3 • All hierarchies except for account hierarchies can be created by the Studio Sustainment group. • The following hierarchies can be uploaded via load program: • Cost Center Groups • Profit Center Groups • MPM Product Groups • Destination Geography Groups • Product Type Groups
SAP Transactions – Excel Upload • BPPs and standardized load templates are currently being developed. Will provide when completed. • Note that the hierarchy load program needs to be customized for different objects to be loaded via excel (i.e. current load program is not configured to load any type of hierarchies) • DEMO – Excel Load of Cost Center Hierarchy and a Destination Geography Hierarchy
SAP Transactions – Excel Upload • T-code: SE38 – ABAP Editor • 2 Programs: ZCOI_RGSIMPH1 – Cost Center and Profit Center groups ZCOI_RGSIMPH1_Dynamic – MPM Product, Dest. Geo & Product Type
SAP Transactions – BW Extract • Process for extract sets/hierarchies in R3 to BW includes: • Currently all hierarchies already extracted to BW are scheduled to refresh from R3 on weekly. • FRIDAYS - Account, Profit Center & Cost Center Hierarchies • SATURDAYS – Product, Product Type, Dest. Geo, Distr’n Channel and Doc Type Sets
SAP Transactions – BW Extract • A workflow process is currently being put in place to address the following (no ETA): • Need for “demand” hierarchy extract outside of the weekly schedule • Need to extract new R3 hierarchies to BW • In the interim, all new hierarchies requiring extracts to BW require an RFS • For “demand” extracts of existing hierarchies, communicate to Jeff Wong and he will work with the extraction team to have this done – please note an ~2 day turn around.
Sets and Hierarchies Security • Set and Hierarchies are secured the following ways in R3: • Account, Cost Center & Profit Center Groups are secured by using a standard naming convention implemented by the PTC team. • Sets such as MPM Product Hierarchies, Destination Geography Hierarchies and Product Type Hierarchies are secured using authorization groups. • DEMO – Authorization Group on Sets
Next Steps • Document complete process for maintaining sets/hierarchies • Possible naming convention for Studio sets/hierarchies • Communicate process to business units • Ensure business units are comfortable with existing sets/hierarchies