Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
0 BI
Content Add-On 4
–New Developments
(Version November 2008)
This section provides an overview of new and changed functions in Release SAP NetWeaver 7.0 BI Content Add-On 4. This information
is provided in release notes
1-(43)
3 Financials: ................................................................................................................................................................................ 7
3.1 Financial Supply Chain Management..................................................................................... 7
3.2 Reporting Financials 2 (EhP4) ................................................................................................ 9
3.3 RE-FX - Enhancements of BI Extraction ................................................................................ 9
3.4 Public Sector Collections and Disbursement...................................................................... 12
3.5 Payment History in SAP Contract Accounting.................................................................... 13
3.6 Returns in SAP Contract Accounting................................................................................... 15
3.7 Collections Management in Contract Accounting .............................................................. 16
3.8 Revenue Distribution in SAP Contract Accounting............................................................ 18
2-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, the following BI Content is available for ITSM:
InfoCubes (Existing)
CRM Service - Orders and Confirmations (Header Data) (0CSRV_C01)
Problem (0SRQ_C11)
1.1.5 Characteristics
Urgency (0CRM_URGENC)
Impact (0CRM_IMPACT)
Risk (0CRM_RISK)
3-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, the following new objects are available for chat interactions:
1.2.3 Queries
Average Speed of Answer for Chat – 0CRM_CTI1_QCHAT_ASA
This query provides information about the average time chat requests are waiting in queue before agents accept them.
This query provides information about the average handling time of chat interactions from accepting to ending a chat.
4-(43)
This query provides information about the number of chat interactions per time period (calendar year, month, week, day, and
hour).
As of SAP NetWeaver 7.0 BI Content Add-On 4, the following objects are available for business process push items:
1.3.3 Queries
Number of Rejected Items for Push – 0CRM_CTI1_QPUSH_REJ
This query provides information about the number of pushed business process items that agents reject.
This query provides information about the average time business process items that are pushed are waiting in queue before
agents accept them.
This query provides information about the average handling time of business process items that are pushed.
This query provides information about the percentage of pushed business process items that are distributed within and
outside the service level target.
This query provides information about the average number of transfers of business process push items of a particular type.
5-(43)
As of SAP NetWeaver7.0 BI Content Add-On 4, new BI Content is available for SAP Supply Network Collaboration (SAP SNC). The goal
of the extractors is to provide a user with relevant data about the SAP SNC application, which he or she can use for further analysis. You
can use the extractor in the scenarios where a customer is not running a SAP ERP system. You can use the information that you obtain
from the extractor to develop on-boarding relevant information.
As of SAP NetWeaver 7.0 BI Content Add-On 4, the following new and enhanced BI Content is available for Service Parts Execution:
New BI Content
Queries
Service Loss Reason: Overdue Schedule (0SPL_DS39_Q0002)
Unlike the existing query Service Loss Due to Supplier Late/Overdue (0SPL_DS39_Q0001), here the characteristic Order Type
(0SPL_ORDTYP) is a selection parameter and is not restricted to inbound deliveries, purchase orders, and scheduling agreement
releases. In this query, the order type can also be a subcontract order or a refurbishment order, for example.
Overview of Service Loss Reason: Overdue Schedule Line (0SPL_C33_Q0002)
Unlike the existing query Overview of Service Loss Reason: Supplier Overdue/Late (0SPL_C33_Q0001), here the characteristic
Order Type (0SPL_ORDTYP) is a selection parameter and is not restricted to inbound deliveries, purchase orders, and scheduling
agreement releases. In this query, the order type can also be a subcontract order or a refurbishment order, for example.
Characteristics
Purchase Order Type (0SPL_POODTY)
6-(43)
3 Financials:
3.1 Financial Supply Chain Management
As of SAP NetWeaver 7.0 BI Content Add-On 4 BI content is available to you if you take into consideration the head office - branch office
relationships of your customers in the collection of receivables area. The new objects take into account the fact that the open items in
Collections Management can be managed at the branch office, but in Accounts Receivable Accounting (FI-AR) can be managed at the
head office.
3.1.2 Recommendation
You can use the new evaluations even if you have not activated taking into account the head office - branch office relationships of your
customers for SAP Collections Management. The procedure is particularly recommended if you have not yet used the existing analog
evaluations.
You can only use the new BI content if you have imported SAP Enhancement Package 4 for SAP ERP 6.0. It relates to the following
business functions:
7-(43)
Analysis Scenarios
Analysis of Receivables in Connection with SAP Collections Management (incl. Head Office - Branch Office Relationships)
Analysis of Invoices and Promises to Pay (incl. Head Office - Branch Office Relationships)
Querys
Due Date Analysis (incl. Head Office - Branch Office Relationship) (0CLM_IS04_Q0001)
Statistics for Promises to Pay (incl. Head Office - Branch Office Relationship) (0CLM_IS05_Q0002)
Details of Promises to Pay (incl. Head Office - Branch Office Relationship) (0CLM_IS05_Q0001)
InfoSets
Receivables Linked to Collections Management Organizational Structures (incl. Head Office - Branch Office Relationships)
(0CLM_IS04)
Merge of Invoice and Promise to Pay (incl. Head Office - Branch Office Relationships) (0CLM_IS05)
Invoices Linked to Collections Management Organizational Structures (incl. Head Office - Branch Office Relationships)
(0CLM_IS06)
DataStore Objects
Open Items in Collections Management (0CLM_DS07)
Characteristics
Customer Number of the Head Office (0HD_DEBITOR)
DataSources
Open Items in Collections Management (0CLM_COLL_ITEM)
Enhanced BI Content
The DataSource Invoice Status (0CLM_INVOICE) has been enhanced with the Customer Number 1
(COLL_DEBITOR) field.
8-(43)
For additional information on the individual BI objects, see the documentation in InfoArea Collections Management
(0FSCM_CLM).
You can find additional information about the new application function in release note FIN_FSCM_CCD_2: Head Office/Branch Office
Relationships (New) (FSCM_604_CCD_2_HOB) in the Collections Management system.
As of SAP NetWeaver 7.0 BI Content Add-on 4 and SAP enhancement package 4 for SAP ERP 6.0, you can use the new Reporting
Financials (EhP4) Info Area. This InfoArea provides you with business intelligence content for analysis of the following areas:
To use the provided business intelligence content, you must have activated theReporting Financials 2 business function.
For a list of all new objects and accompanying documentation, in Knowledge Warehouse see BI Content —> Financials —> Reporting
Financials 2 (EhP4).
As of SAP ECC 6.0, Enterprise Extension Financials, Enhancement Package 4 (EA-FIN 604) and SAP Enhancement Package 4 with
activated business function Real Estate 2, you can use enhanced functions and new objects for extracting data of Flexible Real
Estate Management to Business Intelligence:
9-(43)
Contract: Profit center, business area, cost center, partner (and roles)
For the characteristic Occupancy (object 0REOCCUP) there are new values: Reserved and Intended for Rent. The value
Reserved is used when the object is assigned to a contract for which there is a renewal option, or when the rental object is
assigned to a contract offer. The value Intended for Rent is used when the object is assigned to a lease-out that is not yet
active.
The vacancy reason was added to the master data for rental objects (DataSource 0RENTOBJECT_ATTR).
3.3.3 New DataSources for extracting master data and transaction data
for the architectural view:
o Master Data of Architectural Objects (0ARCHOBJECT_ATTR, 0ARCHOBJECT_TEXT)
o Hierarchy of Architectural Objects (0ARCHOBJECT_HIER)
o Architectural Function (0ARCHFUN_ATTR, 0ARCHFUNC_TEXT)
o Texts for attributes of architectural objects (Type of Relationship (0ARCHRELSHP_TEXT), Architectural
Object Type (0ARCHTYPE_TEXT),Common Usage, (0ARCHUSAGE_TEXT))
o Relationship Between Architectural View and Usage View (0REFX_11)
Gets the proportion of measurement amounts used in the assignment of a usage object to an
architectural object.
o Measurements of Architectural Objects (0REFX_12)
o Differing Measurements (0REFX_13)
Returns the differing measurements that were defined in a real estate contract (contract measurements)
o Occupancy (View by Period) (0REFX_14)
Returns the occupancy of rental objects by period. For the time period you specify using the selection
criteria, the system extracts the number of days the object is occupied and vacant (including the
vacancy reason) for each month.
o Assignment of Business Partner to RE Objects (0REFX_BPOBJASSIGN)
Gets the business partners and their roles that are assigned to a real estate object.
o Deleted Real Estate Objects (0REOBJECT_DEL_ATTR)
Gets all real estate objects deleted without being archived. You can use this information to designate
the master data of these objects accordingly in BI.
3.3.5 InfoCubes:
• Assignment Between Architectural View and Usage View (0REFX_C11)
• Measurements of Architectural Object (0REFX_C12)
• Contract Measurements (0REFX_C13)
• Occupancy (View by Period) (0REFX_C14)
3.3.7 MultiProviders:
o Conditions and Measurements (0REFXMP01)
This MultiProvider contains the following objects:
10-(43)
Queries:
• Architectural Object (0ARCHOBJECT_Q0001)
• Architectural Object (Hierarchy) (0ARCHOBJECT_Q0002)
• Measurements of Architectural Object (0REFXMP02_Q0006)
• Architecture – Assignment Report (0REFXMP02_Q0005)
• Usage Objects – Assignment Report (0REFXMP02_Q0004)
• Usage Object Measurements (0REFXMP02_Q0001)
• Contract Measurement (0REFXMP02_Q0002)
• Contract Measurement for Object(0REFXMP02_Q0003)
• Partner for Contract (0REFXMP03_Q0001)
• Conditions Overview (0REFXMP01_Q0001)
• Vacancy Overview (0REFX_C014_Q0001)
11-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, SAP delivers the following new BI-content for reporting in the Public Sector Collections
and Disbursement (PSCD) and Tax and Revenue Management (TRM) area.
3.4.2 Characteristics
Technical Name Description
0FC_ACCTLEG Contract account number in legacy system
0FC_CORDP Correspondence dunning process
0FC_CMGRP Collection Management: Master data group
3.4.3 Queries
Technical Name Description
0BPARTNER_Q0001 Business partner attribute
0FC_IS01_Q0001 Business partner payment
0FC_IS02_Q0001 Business partner identification (ID)
0BP_REL_Q0001 Business partner relationship
0FC_IS03_Q0001 Contract account attribute
12-(43)
As of SAP NetWeaver 7.0 BI Content Add-on 4, you can use the following new functions for business content in the area of Payments in
Contract Accounts Receivable and Payable dunning history:
13-(43)
14-(43)
As of SAP NetWeaver 7.0 BI Content Add-on 4, you can use the following new functions for business content for Contract Accounts
Receivable and Payable dunning history:
15-(43)
As of SAP Netweaver 7.0, BI Content Add-on 4, the following new functions for business content for Collection Management in Contract
Accounts Receivable and Payable are available.
All objects and supporting documentation can be found In Knowledge Warehouse under BI Content —> Financials —> Financial
Accounting —> Contract Accounts Receivable and Payable.
For Collections Management BI content documentation relevant to Interaction Analytics in the CRM area, go to BI Content —> Customer
Relatioinship Management —> CRM Analytics —> Interaction Channel Analytics —> Interaction Center Analytics —> Collections
Management.
16-(43)
As of SAP Netweaver 7.0, BI Content Add-on 4, you can now extract all revenue distribution and aggregated distribution group, both real
and statistical, for Revenue Distribution used in Business Intelligence (BI). You can run the extraction as full upload, delta initialization
with or without data, and delta update. For more information and accompanying documentation, in Knowledge Warehouse see BI
Content —> Financials —> Financial Accounting —> Contract Accounts Receivable and Payable. The following new functions are
available:
18-(43)
19-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, new DataSources are available to the new role of course administrator for reporting
purposes for course appraisals as part of SAP Learning Solution. New extractors for master data, transaction data, and texts have also
been provided.
The BI Content already available in the Goal Setting and Appraisals component (PA-PD-PM) for analzying employee appraisals and
monitoring appraisal processes has been enhanced and can also be used for reporting course appraisals.
0LSO_APP_VA_TEXT (forms)
• 0HAP_DOC_ID_TEXT (document)
• 0HAP_STATUS_TEXT (status)
• 0HAP_SUBSTA_TEXT (substatus)
• 0HAP_VALUE_TEXT (values)
• 0HAP_VB_TEXT (criteria groups)
• 0HAP_VC_TEXT (criteria)
• 0HAP_V_LIST_TEXT (value lists)
20-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4/SAP ERP 6.0 SPS13, the following new BI Content is available for Concurrent
Employment for the InfoArea Personnel Administration (0PAPA):
The Number of Leavers - Person ID key figure (0LEAVERS) was added to the Organizational Unit feature (0ORGUNIT) as a
time-dependent attribute.
In the Number of Leavers (CE) query (0PA_MP03_Q0003) the 0PA_MP03_CK005 key figure was replaced by the
0LEAVERS key figure in the columns.
The enhancements mentioned above are also available in SAP NetWeaver 7.0 BI Content Add-On 3 SP10. For more information, see
SAP Note 1167706.
21-(43)
From SAP NetWeaver 7.0 BI Content Add-On 4 you can reconcile data from different systems. You can also use different queries to
display the results of the reconciliation process. You can use the objects listed below to reconcile the data in operational and analytical
systems, such as Account Management (FS-AM) and the Source Data Layer (SDL) in Bank Analyzer (FS-BA).
Note that you can use these DataSources only for banking services from SAP 7.0 onwards.
5.1.3 Queries
• Reconciliation Details (BACM/SDL Flows) (0OA1_MP01_Q0001)
• Mismatches (Object ID) by Reconciliation Key (0OA1_VP01_Q0001)
• Reconciliation Details (BACM/SDL Balances) (0OA2_MP01_Q0001)
• Reconciliation Details by Sender/Receiver (BACM/SDL Balances) (0OA2_MP01_Q0002)
• Verification of Mismatches (BACM/SDL Balances) (0OA2_VP01_Q0001)
• Reconciliation of Mismatches (Template Query) (0RC_MP01_Q0002)
• Reconciliation of Mismatches (BACM/SDL Balances) (0RC_MP01_Q0004)
• Reconciliation Details (Template Query) (0TP_MP01_Q0001)
• Reconciliation Details by Sender/Receiver (Template) (0TP_MP01_Q0002)
• Reconciliation by Sender/Receiver (BACM/SDL Flows) (0OA1_MP01_Q0002)
• Overview of Reconciliation Hub Mismatches (0RC_MP01_Q0001)
• Reconciliation of Mismatches (BACM/SDL Flows) (0RC_MP01_Q0003)
5.1.4 MultiProviders
• Flows (Details, Aggregated) (0OA1_MP01)
• Balances (Details) (0OA2_MP01)
• Mismatches (Overview) (0RC_MP01)
• Reconciliation: Details (0TP_MP01)
5.1.5 InfoSets
• Mismatches at Aggregated Level (0OA1_IS01)
• Mismatch Balances (Details) (0OA2_IS01)
• Reconciliation: Mismatches (0TP_IS01)
5.1.6 InfoCubes
• Reconciliation: Details (0TP_C01)
• Reconciliation: Mismatches (0TP_C02)
• Open Mismatches (0TP_C03)
• Details (Aggregated) (0OA1_C01)
• Mismatches at Aggregated Level (0OA1_C02)
• Open Mismatches (Details) (0OA1_C03)
• Mismatches at Object ID Level (0OA1_VP01)
22-(43)
5.1.8 InfoSources
• BACM Items (Aggregated) (0BA_RC_OA1_01)
• SDL Items (Aggregated) (0BA_RC_OA1_02)
• BACM Items (Object ID) (0BA_RC_OA1_03)
• SDL Items (Object ID) (0BA_RC_OA1_04)
• BACM Close (Aggregated) (0BA_RC_OA1_05)
• SDL Close (Aggregated) (0BA_RC_OA1_06)
• BACM Close (Object ID) (0BA_RC_OA1_07)
• SDL Close (Object ID) (0BA_RC_OA1_08)
• BACM Balances (0BA_RC_OA2_01)
• SDL Balances (0BA_RC_OA2_02)
• Verification of BACM Details for Balances (0BA_RC_OA2_03)
• Verification of SDL Details for Balances (0BA_RC_OA2_04)
• Sender Details (0BA_RC_TP_01)
• Receiver Details (0BA_RC_TP_02)
5.1.9 Characteristics:
• Debit/Credit Sign (0BA_DCSIGN)
• Reconciliation Key (Application) (0BA_RCAPP)
• Reconciliation Date (0BA_RCDATE)
• Reconciliation Key: ID (0BA_RCKEY)
• Reconciliation Object ID (0BA_RCOBJ1)
• System-Specific Object ID (0BA_RCOBJ2)
• Pair ID (0BA_RCPAIR)
• Business System (Source System) (0BA_RCSBS)
• Sender/Receiver Indicator (0BA_RCSR)
• Reconciliation Key: Source System (0BA_RCSRC)
• Status (0BA_STATUS)
23-(43)
As of SAP Netweaver 7.0 BI Content Add-On 4 SP01, the field length of the 0TB_COGROUP (condition group) characteristic has been
lengthened from 4 to 10 places.
• /BI0/PTB_COGROUP
• /BI0/STB_COGROUP
• /BI0/PBT_COND
If you have used this characteristic in your own development, you also need to make appropriate adjustments, especially in the relevant
queries
As of SAP Netweaver 7.0 BI Content Add-On 4 SP01, the Position Number of a Condition (0TB_COPONO) and Variable for Condition
Position (0TB_COPOVA) fields are read in the update rule from InfoSource Condition Master Data (0TB_AM_CN_13) into
characteristic Individual Condition (0TB_COND) by means of a new start routine. These fields are part of the compounding of the
0TB_COND characteristic. However, their texts are not supplied from the source system.
The business content has been enhanced to include financial reporting of payments and reserves.
As well as being able to evaluate current data, you can now evaluate point-in-time data for selected subject areas. Point-in-time data
contains the values of characteristics and key figures for a specific change time at the end of a key date. You can choose this key date
freely. Reporting is based on the multiprovider 0ISCMMP02. Sample queries are available for this multiprovider.
24-(43)
6 Industries – Media
6.1 BI Content for Intellectual Property Management (Enhanced)
6.1.1 Technical Data
Product Version SAP NetWeaver 7.0 BI Content Add-On 4
Area Media
Country Relevance Valid for all countries
As of SAP Netweaver 7.0 BI Content Add-On 4, the query Multiple Payees (0IPM_C09_Q0017) is available in the Business
Intelligence (BI) Content for Intellectual Property Management. This query analyzes billing documents with the assigned billing category
payee document (0IPM_BLLCAT = G).
25-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, SAP delivers the following new BI-content for reporting in the Public Sector Collections
and Disbursement (PSCD) and Tax and Revenue Management (TRM) area.
7.1.2 Characteristics
Technical Name Description
0FC_ACCTLEG Contract account number in legacy system
0FC_CORDP Correspondence dunning process
0FC_CMGRP Collection Management: Master data group
7.1.3 Queries
Technical Name Description
0BPARTNER_Q0001 Business partner attribute
0FC_IS01_Q0001 Business partner payment
0FC_IS02_Q0001 Business partner identification (ID)
0BP_REL_Q0001 Business partner relationship
0FC_IS03_Q0001 Contract account attribute
26-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, Merchandise and Assortment Planning (MAP) has a new Pre-Season Strategic and
Merchandise Planning function that uses SAP BI Integrated Planning (IP) as the planning framework. The planning queries are delivered
via the web-based BI BEx Web Application Designer. In this release, SAP MAP provides the two sets of strategic merchandise planning
based on the two accounting methods: Retail Method of Accounting (RMA) and Cost Method of Accounting (CMA).
Each accounting method includes a different set of planning templates as described below.
• Strategic Planning
o Distribution Chain Plan
o Division Plan
• Merchandise Planning
o Sales Plan
o Markdown Plan
o Inventory/Receipts Plan
o Gross Margin Plan
• Store Planning
o Sales Plan
o Markdown Plan
o Inventory/Receipts Plan
o Gross Margin Plan
• Reconciliation Planning
o Comparison Plan
• Cost Method of Accounting (CMA)
• Strategic Planning
o Distribution Chain Plan
o Division Plan
• Merchandise Planning
o Sales Plan
o Inventory/Receipts Plan
o Gross Margin Plan
• Store Planning
o Sales Plan
o Inventory/Receipts Plan
o Gross Margin Plan
• Reconciliation Planning
o Comparison Plan
The existing InfoCubes in SAP MAP are reused in addition to the new key figures, multiproviders and IP objects such as the aggregation
levels and planning sequences. (See the SAP Library for details).
Limitations
The current BI IP Planning Framework does not support the inverse formula calculation and the aggregation/disaggregation of the
percentage and average values. With this technical limitation, the current release does not support the input of any percentage key
figures or average key figures. These kinds of key figures are only calculated. For the same reason, no AUR (Average Unit of
Retail) planning templates are included. For the inventory plan, the system only calculates the BOP (Beginning of Period) and EOP
(End of Period) based on the receipts/issues amount entered. In a future release, IP-based MAP will be enhanced using the new
features of the NetWeaver calculation engine to address these issues.
Aggregated long-term forecasting: IP-based MAP Planning does not support aggregated long-term forecasting, which is based on
the older BPS (Business Process and Simulation) planning. However, this current release provides the sales forecast using the IP
forecast planning function. In a future release, MAP will be integrated into SAP Demand Forecasting.
27-(43)
New Transactions:
New Customizing:
As of SAP NetWeaver 7.0 BI Content Add-On 4, you can use the Master Data Planning (MAP-MDP) application to create and update
planning article (article placeholders) to include attributes such as color and size within an assortment plan. To perform planning
activities in MDP, you can use the standard maintenance views provided with the application (see below), or you can create your own
maintenance views via a series of customizing screens.
The standard maintenance views delivered with the system are included in group 0RMP_DEMO and are as follows:
The standard maintenance views are used in the Retail Purchasing Plan Integration Sample application.
These DataSources provide information about the characteristics entered in the Retail classification (using transaction
WRFCHVALTYPE). Extracted data can be filtered by characteristic type (color, main size, secondary size).
These DataSources provide information about the characteristic values entered in the Retail classification (using transaction
WRFCHVALTYPE). Extracted data can be filtered by characteristic type (color, main size, secondary size).
28-(43)
These DataSources provide information about the Quota Scale header for the characteristic entered in the Retail
classification (using transaction WRFCHVALTYPE). Extracted data can be filtered by characteristic type (color, main size,
secondary size).
• List all existing maintenance views and customize the selected view (UPARM_CUSTOM)
• Customize a single maintenance view (UPARM_CUSTOM_SINGLE)
• Define groups and add maintenance views to groups (UPARM_CUSTOM_GROUP)
• Validate field entries and access Search help (F4-help) from customizing screens
• Set a release status from a maintenance view
• Define attributes of specific selection criteria to be displayed in the maintenance views
• Set the Copy behavior of each column
• Add child views to a maintenance view.
A child view can be launched from a customized button in the toolbar. A child view uses the row selected in the
parent maintenance view as the context to initialize its selection criteria.
The MDP Web Dynpro application (maintenance views) includes the following enhancements:
New customizing transaction (UPARI_RPP) that can be used to define a query, plan version, and key figures that are
used by the Retail Purchasing Plan message.
Use this BAdI to implement a flexible lock on the MDP Web Dynpro views depending on the selection criteria
values (BADI_UPARM_VIEW_LOCK)
Use this BAdI to implement a flexible authority check on the MDP Web Dynpro views depending on the selection
criteria values (BADI_UPARM_BLOCK_MAINTENANCE)
BAdIs are available to customize the behavior and display of the results of the Search help (F4-help) in the MDP
Web Dynpro maintenance views (BADI_UPARM_SEARCH_HELP_RESULT and
BADI_UPARM_SEARCH_HELP_SELECT)
29-(43)
As of SAP NetWeaver 7.0 BI Content Add-On 4, there is a new Retail Purchasing Plan Integration Sample – a web template
demonstrating the integration of the BI Merchandise Assortment Planning (MAP) with the ERP Operational Assortment Planning and
Control (OAPC). You use this web template to plan your purchasing on one of the following levels:
Cluster (assortment)
Option (color)
Size
To access the Retail Purchasing Plan Integration Sample web template, choose SAP menu Retail Purchasing Plan Integration
Sample Retail Purchasing Plan – Integration Planning Content (transaction UPARP_RPP) . The web template is linked to the
standard Master Data Planning (MAP-MDP) views delivered with the system. This allows you to both plan and create all the necessary
master data (create styles, colors, sizes and assign the newly created color and sizes to the styles) from a single application. For
example, you can create a new style and color and, as part of your planning activities, assign (plan) sizes and the new color to the new
style.
You can also use the Packsize/Quota Scale per Color pushbutton to open a view where you can maintain the pack size and quota scale
for each of the sizes of each style/color mix.
The assortment plan data is saved in InfoCube 0RMP_C27 and can be transferred to the OAPC (ERP) via the Retail Purchasing Plan
message of the Release Workbench (transaction UPARI_REL).
SAP has already supplied RMA for Release BI 7.03 SP08 and SP09.
30-(43)
• Document and audit trail, based on the RMA period reports for the material group hierarchy and article hierarchy
• Enhancement of the analyses based on an alternative calendar
• Support for special POS scenarios (delayed sales posting and delayed customer returns)
• Valuation of the cost of returns to vendor, according to the RMA cost quotient
• Archiving of period-end closing documents in BI
• Provision of the RMA results to Trade BI applications
For more information, see the help.portal.com under SAP for Industries SAP for Retail BI Content Industry Solutions Trade
Industries Retail Trade Supply Chain Analytics Stock Ledger Analytics Retail Method of Accounting (RMA) .
31-(43)
As of SAP NetWeaver 7.0 BI Content Add-on 4, the following business content is available for the Process Control function. This is a
cumulative list.
9.1.3 Roles
• SAP GRC Governance, Risk Compliance Role
• SAP GRC Process Control 2.5 Role
• SAP GRC Process Control 2.5 - Role for Queries Activation
• SAP GRC Process Control Events Role
9.1.5 Queries
• Authorizations for Organization Units Today
• Control Testing Evaluations History
• Control Testing Evaluations History Overall
• Evaluation Details
• Evaluations Summary
• Event Summary Report
• Failed Design Assessments for CO-Risks
• Failed Design Assessments for Key Accounts
• Failed Self Assessments for CO-Risks
• Failed Self Assessments for Key Accounts
• Failed Testings for CO-Risks
• Failed Testings for Key Accounts
• Global Heat Map
• Global Heat Map for Events
• Global Heat Map for Events: Region
• Ineffective Controls for CO-Risks
• Ineffective Controls for Key Accounts
32-(43)
9.1.6 Variables
• GPC Account Group
• GPC FS Assertion
• GRC PC Control Evaluation Type
• GRC PC Control Objective
• GRC PC Org. Unit
• GRC PC Org. Units
• GRC PC Orgunit Authorizations - Current
• GRC PC Orgunit Authorizations in Timeframe
• GRC PC Process
• GRC PC Risk
• GRC PC Subprocess
• GRC PC Timeframe Interval
• GRC PC Timeframe Interval Begin Date (Exit)
• GRC PC Timeframe Interval End Date (Exit)
• SAPExit Variable - Timeframe Begin Date from OP_GPCTF
• SAPExit Variable - Timeframe End Date from OP_GPCTF
• Timeframe
9.1.7 MultiProviders
• Control Evaluation Details Multiprovider
• Evaluation Details for Account Groups/Assertions
• Evaluation Details for Control Objectives/Risks
• Org. Units Level Authorizations
9.1.8 InfoCubes
• Control Evaluation Details
• Orgunit Level Authorizations
9.1.9 InfoSets
• Evaluation Details for Account Groups/Assertions
• Evaluation Details for Control Objectives/Risks
9.1.11 KeyFigures
• Adequate
• Counter
• Deficient
• Deficient and Significantly Deficient
• Generic Issue Counter
• Generic Open Issue Counter
• Generic Remediation Plan Counter
• Issues Rate
• Number of Control Design Issues
• Number of Effectiveness Test Issues
• Number of Entity Level Control Assessment Issues
• Number of Issues
• Number of Open Control Design Issues
• Number of Open Control Self-Assessment Issues
• Number of Open Effectiveness Test Issues
• Number of Open Entity Level Control Assessment Issues
• Number of Open Subprocess Design Issues
• Number of Remediation Plans
• Number of Remediation Plans for Control Design Assessment Issues
33-(43)
9.1.12 Characteristics
• Account Group
• Assessment
• Boolean Flag Text
• Case Category
• Case ID
• Case Type
• Central Process
• Central Subprocess
• Control
• Control Design Assessment
• Control Design Evaluation Type
• Control Design Processor
• Control Design Rating
• Control Design Status
• Control Effectiveness Test Evaluation Type
• Control Effectiveness Test Processor
• Control Effectiveness Test Rating
• Control Effectiveness Test Status
• Control Effectiveness Testing
• Control Objective
• Control Objective Category
• Control Origin
• Control Owner
• Control Self Assessment
• Control Self Assessment Evaluation Type
• Control Self Assessment Processor
• Control Self Assessment Rating
• Control Self Assessment Status
• Control Type in CO-R Assignment
• Date of Event
• Due Date
• Entity Level Control
• Entity Level Control Assessment
• Entity Level Control Assessment Processor
• Entity Level Control Assessment Rating
• Entity Level Control Assessment Status
• Entity Level Control Evaluation Type
• Entity Level Control Group
• Entity Level Control Owner
• Entity Object ID
• Entity Object Type
• Evaluation Date
• Evaluation Status
• Evaluation Type
• Evaluator
• FS Assertions
• Issue
• Issue Priority
• Organization Unit
• Organization Unit Owner
• Organization Unit Sign-Off Relevance
• Parent Assessment
• Parent Testing
• Process
• Process Control Event
• Process Control Event Location Code
• Process Control Event Sender
• Process Control Event Type
• Process Control User
• Process Owner
• Risk
• Significance of the Account Group
• Status
• Subprocess
34-(43)
9.1.14 DataSources
• Account Group Attributes
• Account Group Hierarchy
• Account Group Texts
• Assessment Attribute
• Assessment Texts
• Boolean Flag Text
• Case Category CaseType
• Central Process Texts
• Central Process/Subprocess Hierarchy
• Central Subprocess Texts
• Control Object Attributes
• Control Objective Category
• Control Objective Texts
• Control Type in CO-R Assignment
• Control Type Texts Entity Level
• Control Group Hierarchy
• Entity Object Type
• Evaluation Type
• FS Assertions
• GRC PC User Texts
• Issue Attributes
• Issues Priority Texts
• Issue Texts
• Org. Unit Attributes
• Org. Unit Texts
• Organization Hierarchy
• PC Control
• PC Control Texts
• PC Entity Level Control Attributes
• PC Entity Level Control Group Texts
• PC Entity Level Control Texts
• PC Event Attributes
• PC Event Sender Text
• PC Event Type Texts
• PC Subprocess-Account-Assertion_Control Assignment
• PC Subprocess-Control Objective-Risk-Control Assignment
• Process Attributes
• Process Control Authorizations
• Process Texts
• Rating Texts
• Remediation Plan Attibutes
• Remediation Plan Texts
35-(43)
36-(43)
In addition to the following release notes text, there are now two SAP Notes for GRC Access Control which collect a set of SAP Notes
related to the NetWeaver BI Content for Access Control (CUP and RAR):
You can periodically check the two notes, as more new notes may be created at any time and would then be referenced under these two
SAP Notes.
First, a business content update for the Risk Analysis and Remediation area is included.
Second, is the business content update for the Compliant User Provisioning area.
Third, are the notes on business content for the Risk Analysis and Remediation capability.
Fourth, the notes on business content for the Compliant User Provisioning capability are listed.
Minor changes:
37-(43)
• InfoObject 0GCC_USRGRP now allows lowercase letters. Following are the RAR InfoObjects which now allow
lowercase letters: 0GCC_USRGRP,0GCC_OBJID,0GCC_ROLE,
0GCC_PROFIL,0GCC_PRMVAL,0GCC_PRMOBJ,0GCC_USER,0GCC_PRMVFR,0GCC_PRM
VTO,0GCC_APPRVR,0GCC_DEPT,0GCC_MONID.
• Replacement of 3.x InfoPackages User Change Log Entries, Role Change Log Entries and Profile Change Log Entries
for Export DataSource 80GCC_URP with DTPs pushing the data from DSO 0GCC_URPC to DSOs
0GCC_UPDH,0GCC_RPDH and 0GCC_PPDH.
• Process Chain 0GAE_TRANSACTION_AR modified to delete PSAs for non-write optimized DSOs to improve the
performance of the archive extracts.
• Process Chain 0GAE_ARCH_TO_CUBE modified to delete contents of DSO 0GAE_HDR and InfoCube
0GAE_C01 after data physically archived off the source system.
• Chain was also moved up the processing stream as described below.
• Language conversion enhancement for DSO 0GAE_D03.
• Conversion from external CUP language code format to internal SAP one character language code format was corrected for
language dependent text objects. See note 1229932.
Extraction technology is based on UD Connect in order to provide straightforward, database independent extracts from a J2EE source
system such as CC.
In the following sections are descriptions and explanations for some of these areas.
Permission Violations data comes from table VIRSA_CC_PRMVL provided via DataSources 0GCC_PRMVL_USER_VIOLS,
0GCC_PRMVL_ROLE_VIOLS and 0GCC_PRMVL_PROF_VIOLS filtered in InfoPackages by GENOBJTP = 1, 2 or 3,
respectively. Full extract InfoPackages are delivered to provide the initial load of this data. After the initial full loads, the recurring pseudo
delta procedure (described below) should be performed.
38-(43)
The Permission Violations delta procedure is driven by the RUNDATE field in source system tables VIRSA_CC_PRMVL and
VIRSA_CC_GENOBJ. VIRSA_CC_GENOBJ is a change log table representing changed users, roles and profiles (including
permissions changes) with a date stamp.
In the example of User Permission Violations processing, after the initial full extract the delta InfoPackage ABAP Routine selection
criteria will select records from VIRSA_CC_PRMVL which have been changed since the previous successful BI extract using the
RUNDATE value. In CC, if the permissions for a user have changed, all of their violations records will be deleted and replaced with the
new values and all records will contain the new Run Date. Therefore, BI needs to extract all of these records and replace the existing
current violations in the DSO and InfoCube with these new values. The extract dates are stored in table GRCCC_EXTRACTS
and managed by programs RS_BCT_GRC_CC_ADD_EXTR_DATE and RS_BCT_GRC_CC_ACT_EXTR_DATE as
executed in the process chains.
The extract date recorded in this table and used for the InfoPackage selection range is the current date minus one. This will help to
prevent missing newly added records in the system (although, it is highly recommended that extracts occur when the CC system is
quiet). Prior to loading the new values, the current records in BI for the changed users need to be extracted from the current DSO and
loaded into the History DSO. This is done by executing an InfoPackage against the User/Role/Profile Change Log DSO filtered by
0GCC_OBJTYP=1 (for the User example).
These values are then used by the start routine for the History DSO to pull in the violation records associated with these users
from the Current DSO. This will create a history of the permission violation changes by user by run date.
Additionally, prior to loading the newly extracted source system records via the DTP, the previous values for the changed users need to
be deleted from the current DSO and InfoCube. In order to do this, the programs RS_BCT_GRC_CC_DEL_DSO_DATA
and RS_BCT_GRC_CC_DEL_CUBE_DATA are used. These programs use as input the values of changed users from the
User/Role/Profile Change Log DSO to delete the associated records from the current User Permission Violations DSO and InfoCube.
Then, the DTP can be executed to load the new user permission violation values for the changed users to either replace the previous
violation values or to add a new user’s violations.
Aggregates are not provided with the delivered InfoCubes, since they should be built on the specific needs of the customer based on
their reporting requirements. Note, however, that the use of aggregates will cause the selective deletion program mentioned above to run
significantly longer as the aggregates will be recalculated. So, the tradeoff will be quicker extracts via the pseudo delta versus longer
loads in providing faster query results using aggregates.
The Management Report - Summary Total extract performs a complete refresh of this DSO in order to enable the monthly delta of the
other Management Report areas. For the extracts from tables where the history is maintained in CC, an InfoPackage selection criteria
extracts on records based on the YEARMONTH belonging to the latest month processed for Management Reporting based on the
highest 0CALMONTH value in the Summary Total DSO.
For the Risk Detail extract (which is based on a table which is fully refreshed in CC), a start routine is used to determine the
0CALMONTH which will be recorded in the DSO based on the latest 0CALMONTH value in the Summary Total DSO (since the date
is not recorded in the CC table for Risk Detail or Critical Action).
9.2.10 Mitigations
No historical tracking is recorded in BI for mitigations. InfoCubes with full refreshes are used to store the information.
This information will be stored in a current InfoCube but, additionally, an Alert Header DSO is used support the pseudo delta
procedure described in the next paragraph. The Alert Detail table is extracted in a pseudo delta mode by using a start routine
39-(43)
If, for example, the user wants to report on the Risk long descriptions while performing Role Permission Violations analysis, an InfoSet
needs to be set up between the Role Permission Violations InfoCube and the Risk Long Description DSO. Then, when a user is
reporting on the Role Permission Violations InfoCube, a jump-to can be executed to run a query off the InfoSet based on the selection
criteria from the Role Permission Violation query and the user supplied language key showing the language dependent long descriptions
of the risks.
For Critical Roles the handling is slightly different since the key for a Critical Role is 68 characters (more than the allowable maximum of
60 for an InfoObject) and the values are stored in a DSO. However, the matching to the values in the 0GCC_EXID DSO is the
same.
In order to report by these long IDs, a query should filter on the attribute 0GCC_PRTFLG of 0GCC_VSYS where the value =Y
(indicating that the Actual System is a portals system) and displays the attributes 0GCC_LNGID1 - 0GCC_LNGID5. This
concept is demonstrated in the delivered queries 0GCC_RPV_Q0002 for Role long IDs and 0GCC_CRVI_Q0001 for Critical
Roles long IDs.
However, one recommendation is to activate the objects below in the following order:
Role SAP_BW_GRC_CC_ROLE and all associated queries (0GCC*), selecting Only Necessary.
Reporting role SAP_BW_GRC_CC_ROLE has been provided as part of BI CC Business Content and can be used to activate all
delivered queries. However, since queries have not been delivered for each and every InfoProvider, the role should not be activated for
the purpose of an all-encompassing business content activation method.
Be sure to deselect any DataSources, Transfer Rules, and so forth, associated with delivered BI-HR InfoObjects, such as
0EMPLOYEE, 0COUNTRY, 0COMP_CODE, etc.
These InfoObjects are included in the BI CC model in order to provide reporting by these user attributes, but their associated
source system related objects, if desire, should be activated from the proper R/3 source system in a separate BC activation
step.
Prior to activating DSO 0GCC_URP, you first need to activate the 3.x Export DataSource 80GCC_URP
using In Dataflow Before and Afterwards and choosing the Myself Source System. This will activate the DataSource as well
as the associated Communication Structure, Transfer Structure and Transfer Rules. Then you can activate the 0GCC_URP
DSO using In Dataflow Before and Afterwards.
First, the initial full load of the Permission Violations and Management data needs to be processed. This is initiated by the Process Chain
GRC CC (Risk Analysis & Remed)Perm Viols/Mgmt Initial Load, which in turn will call GRC
CC (Risk Analysis and Remediation)Initial Master Data and GRC CC(Risk
Analysis and Remediation)Mgmt Rpts Initial Extr.
The loading of the Permission Violations data could take a very long time using UD Connec, perhaps up to several days.
The initial full load of the CC data is not intended to set the customer up for reporting, but simply to accomplish the potentially enormous
Permissions Violations full load and to initialize the Management Reporting extracts.
The strategy is to immediately follow up the initial, one time full load with the recurring extract GRC
CC (Risk Analysis
and Remediation)Start Recurring Extr. This will fully populate all supporting data as well as the other areas of
reporting such as Critical Violations, Rules, Alerts, Mitigations, and so forth, as well as the delta loads for the Permission Violations and
Management Reporting.
The customer will likely want to set the Start variant to a periodic setting.
Customers may choose to create their own process chains but the supplied steps are necessary for accurate delta processing and for
enabling master data attribute lookups. Extracts are designed to be run while the CC system is quiet since delta queues are not
provided. Otherwise, inconsistent data in BI can occur.
9.2.19 InfoAreas
SAP GRC Compliant User Provisioning (CUP) (0GRC_AE)
41-(43)
9.2.21 Queries
• Access Requests (0GAE_MP02_Q0001)
• Service Levels (0GAE_MP02_Q0002)
• User Provisioning (0GAE_MP02_Q0003)
• Role Provisioning (0GAE_MP02_Q0004)
• Risk Violations (0GAE_MP02_Q0005)
• SOD Review (0GAE_MP02_Q0006)
• User Access Review (0GAE_MP02_Q0007)
9.2.22 InfoCubes
• Request Header (0GAE_C01)
• Risk Violations (0GAE_C02)
• SOD Review (0GAE_C03)
• User Access Review (0GAE_C04)
• Access Requests and Service Levels (0GAE_C05)
• Role Provisioning (0GAE_C06)
• User Provisioning (0GAE_C07)
• Archived data not available in Source system (0GAE_C08)
9.2.23 MultiProviders
• Request Header - Current & Archived (0GAE_MP01)
• AE CUP Reporting (0GAE_MP02)
9.2.28 KeyFigures
• Counter (0GAE_COUNT)
• Extra Counter 1 (0GAE_COUNT1)
• Extra Counter 2 (0GAE_COUNT2)
• Role Usage (0GAE_RLUSGE)
• Usage Count (0GAE_USGCNT)
43-(43)