BI content

1-(43) SAP NetWeaver 7.0 BI Content Add-On 4 –New Developments

SAP NetWeaver 7.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


Table of Content

1 Customer Relationship Management: ........................................................................................ 3

1.1 BI Content for IT Service Management .................................................................................. 3 1.2 BI Content for SAP CRM Interaction Center Chat Interactions ........................................... 4 1.3 BI Content for SAP CRM Interaction Center Business Process Push................................ 5

2 Supply Chain Management:......................................................................................................... 6

2.1 SAP Supply Network Collaboration........................................................................................ 6 2.2 Service Parts Execution........................................................................................................... 6

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

4 Human Resources ...................................................................................................................... 20

4.1 DataSources for Course Appraisals..................................................................................... 20 4.2 BI Content for Personnel Administration for Concurrent Employment (Enhanced)....... 21

5 Industries / Financial Services .................................................................................................. 22

5.1 - Reconciliation of Data from Different Systems................................................................. 22 5.2 Field Length of the Condition Group (0TB_COGROUP) Characteristic (Changed)......... 24 5.3 Update Rule: Individual Condition (Changed)..................................................................... 24 5.4 Business Content for SAP Claims Management (Enhanced)............................................ 24

6 Industries – Media....................................................................................................................... 25 6.1 BI Content for Intellectual Property Management (Enhanced).......................................... 25

7 Industries Public Sector............................................................................................................ 26 7.1 Collections and Disbursement.............................................................................................. 26

8 Industries –Trade Industries...................................................................................................... 27 8.1 MAP Pre-Season Strategic Merchandise Planning............................................................. 27 8.2 MAP Master Data Planning Application (Enhanced) .......................................................... 28 8.3 Retail Purchasing Plan Integration Sample......................................................................... 30 8.4 Retail Method of Accounting (RMA) (enhanced)................................................................. 30

9 SAP Governance, Risk, and Compliance (GRC)...................................................................... 32

9.1 SAP GRC Process Control .................................................................................................... 32 9.2 SAP GRC Access Control...................................................................................................... 37 Variables ..................................................................................................Error! Bookmark not defined.


1 Customer Relationship Management:

1.1 BI Content for IT Service Management 1.1.1 Technical Data

Product Version SAP NetWeaver 7.0 BI Content Add-On 4 Area IT service management (ITSM)

Country Relevance Valid for all countries

As of SAP NetWeaver 7.0 BI Content Add-On 4, the following BI Content is available for ITSM:

1.1.2 DataStore Objects (Existing)

CRM Service - Orders (Header Data) (0CRM_PROH)

1.1.3 DataStore Objects (New)

Service Request Standard (0SRQ_DS10)

Problem Standard (0SRQ_DS11)

InfoCubes (Existing)

CRM Service - Orders and Confirmations (Header Data) (0CSRV_C01)

1.1.4 InfoCubes (New)

Service Request (0SRQ_C10)

Problem (0SRQ_C11)

1.1.5 Characteristics

Urgency (0CRM_URGENC)

Impact (0CRM_IMPACT)

Risk (0CRM_RISK)

Change Category (0CRM_CHGCAT)

Problem Category (0CRM_PRBCAT)

Multilevel Categorization - Category GUID Catalog Type C (0CRMCCCAT_C)

Multilevel Categorization - Category GUID Catalog Type D (0CRMCCCAT_D)

Multilevel Categorization - Category GUID Catalog Type E (0CRMCCCAT_E)

Multilevel Categorization - Category GUID Catalog Type T (0CRMCCCAT_T)

Multilevel Categorization - Category GUID Catalog Type W (0CRMCCCAT_W)


Recommended Priority (0CRM_PRIO_R)

1.1.6 Key Figures

Number of Service Requests (0CRM_INCI_N)

Number of Service Requests Linked to Problem (0CRM_INCI_T)

Number of Locked Service Requests Linked to Problem (0CRM_INCI_L)

No. of Service Requests In Process with Prev. Status Completed (0CRM_INCI_C)

Number of Problems (0CRM_PROB_N)

No. of Problems In Process with Previous Status Completed (0CRM_PROB_C)

Number of Service Requests Linked to Request for Change (0CRM_RFC_IN)

Number of Requests for Change (0CRM_RFC_N)

Number of RfCs In Process with Previous Status Completed (0CRM_RFC_C)

Number of Problems Linked to Request for Change (0CRM_RFC_PR)

1.2 BI Content for SAP CRM Interaction Center Chat Interactions

1.2.1 Technical Data Product Version SAP NetWeaver 7.0 BI Content Add-On 4

Area SAP Customer Relationship Management (SAP CRM) Interaction Center (IC) Country Relevance Valid for all countries

As of SAP NetWeaver 7.0 BI Content Add-On 4, the following new objects are available for chat interactions:

1.2.2 Web Templates

Abandonment Rate for Chat – 0TPL_0CRM_CTI1_QCHAT_ABRT_V01

Average Handling Time for Chat – 0TPL_0CRM_CTI1_CHAHT_V01

Average Speed of Answer for Chat – 0TPL_0CRM_CTI1_QCHAT_ASA_V01

Volume of Chat Connections – 0TPL_0CRM_CTI1_CHVOL_V01

Service Level for Chat – 0TPL_0CRM_CTI1_QCHAT_SL_V01

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.

Average Handling Time for Chat – 0CRM_CTI1_QCHAT_AHT

This query provides information about the average handling time of chat interactions from accepting to ending a chat.


Volume of Chat Connections – 0CRM_CTI1_QCHAT_VOL

This query provides information about the number of chat interactions per time period (calendar year, month, week, day, and hour).

1.3 BI Content for SAP CRM Interaction Center Business Process Push


Area SAP Customer Relationship Management (SAP CRM) Interaction Center (IC) Country Relevance Valid for all countries

As of SAP NetWeaver 7.0 BI Content Add-On 4, the following objects are available for business process push items:

1.3.2 Web Templates

Number of Rejected Items for Push – 0TPL_0CRM_CTI1_QPUSH_REJ_V01

Average Handling Time for Push – 0TPL_0CRM_CTI1_QPUSH_AHT_V01

Average Speed of Answer for Push – 0TPL_0CRM_CTI1_QPUSH_ASA_V01

Number of Transfers for Push – 0TPL_0CRM_CTI2_QPUSH_TRF_V01

Service Level for Push – 0TPL_0CRM_CTI1_QPUSH_SL_V01

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.

Average Speed of Answer for Push – 0CRM_CTI1_QPUSH_ASA

This query provides information about the average time business process items that are pushed are waiting in queue before agents accept them.

Average Handling Time for Push – 0CRM_CTI1_QPUSH_AHT

This query provides information about the average handling time of business process items that are pushed.

Service Level for Push – 0CRM_CTI1_QPUSH_SL

This query provides information about the percentage of pushed business process items that are distributed within and outside the service level target.

Number of Transfers for Push – 0CRM_CTI2_QPUSH_TRF

This query provides information about the average number of transfers of business process push items of a particular type.


2 Supply Chain Management:

2.1 SAP Supply Network Collaboration


Area SAP Supply Network Collaboration (SAP SNC) 7.0 Country Relevance Valid for all countries

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.

2.1.2 New data sources

Extractor for Advanced Shipping Notifications 0ICH_ASN_INT_1

Extractor for Invoices 0ICH_INV_INT_1

Extractor for Purchase Orders 0ICH_PO_INT_1

Extractor for SMI Time Series 0ICH_SMI_TS_INT_1

Extractor for Scheduling Agreement Releases 0ICH_REL_INT_1

Extractor for Work Order Phase Lead Time 0ICH_WO_PHLD_INT_1

Extractor for Inventory 0ICH_INV_INT_

2.2 Service Parts Execution


Area Service Parts Execution


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)


Purchase Order Item (0SPL_POITTY) Category of Stock/Receipt/Requirement/Forecast (0SPL_ATPCAT) Enhanced BI Content As of SAP NetWeaver 7.0 BI Content Add-On 4, the following existing BI Content objects contain the new characteristics Purchase Order Type (0SPL_POODTY) and Purchase Order Item (0SPL_POITTY): DataSource Purchase Order (0SPL_PO_DATA_1) DataStore object Purchase Order Data (0SPL_DS03) Query SDPR Details About Purchase Orders (Month) (0SPL_DS03_Q001) Query SDPR Details About Purchase Orders (Week) (0SPL_DS03_Q004) Query Supplier View: SDPR Details About Purchase Orders (Month) (0SPL_DS03_Q005) Query Supplier View: SDPR Details About Purchase Orders (Week) (0SPL_DS03_Q006) As of SAP NetWeaver 7.0 BI Content Add-On 4, the following existing BI Content objects contain the new characteristic Category of Stock/Receipt/Requirement/Forecast (0SPL_ATPCAT): DataSource Service Fill Monitor Orders (0SPL_SFA_SRVFILL_1) DataStore object Service Fill Details (0SPL_DS31) DataStore object Service Fill - Requested Schedule Lines for T0 (0SPL_DS33) DataStore object Service Fill Details About T1 (0SPL_DS34) DataStore object Service Fill Details About T2 (0SPL_DS35) DataStore object Service Fill - Requested Schedule Lines for T1 (0SPL_DS36) DataStore object Service Fill - Requested Schedule Lines for T2 (0SPL_DS37) InfoCube Service Fill Reporting (0SPL_C31) MultiProvider Service Fill Details MultiProvider (0SPL_MC31) Renamed BI Content objects Object Type Technical Name Previous Name New Name

DataSource 0SPL_SFA_SRVFSUPPL_1 Service Loss Due to Supplier Delay Service Loss Due to Overdue Schedule

InfoSource 0SPL_SFA_SRVFSUPPL_1 Service Loss Due to Supplier Late/Overdue

Service Loss Reason: Overdue Schedule

DataStore Object 0SPL_DS39 Service Loss Due to Late or Overdue

Supplier Service Loss Due to Overdue Schedule

InfoCube 0SPL_C33 Service Loss Due to Late or Overdue Supplier

Service Loss Due to Overdue Schedule

3 Financials:

3.1 Financial Supply Chain Management

-Considering Head Office/Branch Office Relationships


Area SAP Collections Management (FIN-FSCM-COL) Country Relevance Valid for all countries

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:


FSCM Functions 2 (FIN_FSCM_CCD_2)

FSCM Integration 2 (FIN_FSCM_CCD_INTEGRATION)

From a technical view, you can use the following objects:

3.1.3 New BI Content

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)

Receivables Grid (incl. Head Office - Branch Office Relationship) (0CLM_IS06_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)

Customer Number in Collections Management(0CLM_DEBITR)

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.


3.1.4 Effects on Existing Data

If you activate taking into consideration the head office - branch office relationships in Customizing, then you have to delete the existing data in DataStore object Invoice Status (0CLM_DS05), and carry out an initial data transfer in the corresponding company code of the changed DataSource Invoice Status (0CLM_INVOICE) and DataSource Invoices with Promises to Pay (0CLM_P2P_INVOICE) to the BI system. This also applies to deactivating this function.

3.1.5 Effects on Data Transfer

You have to activate the new and changed DataSource in the relevant system before using them.

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.

3.2 Reporting Financials 2 (EhP4)

3.2.1 Technical Data Product Version SAP NetWeaver 7.0 BI Content Add-on 4

Area Financials


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:

• Asset Accounting (FI-AA) • Investment Management (IM-FA) • Profitability Analysis (CO-PA) • Closing (FI-GL)

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).

3.3 RE-FX - Enhancements of BI Extraction


Area Flexible Real Estate Management Country Relevance Valid for all countries

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:

3.3.2 Enhanced functions for extraction of master data attributes for usage objects

Occupancy (OCCUP field) for the objects Business Entity, Building, Land and Rental Object is no longer provided just for the key date of the extraction, but over the entire validity period. In addition, the following master data attributes are provided on a time-dependent basis:

http://help.sap.com/saphelp_nw70/helpdata/en/4c/db1da3f171488a806515e38f971f73/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/4c/db1da3f171488a806515e38f971f73/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/6a/cd7dbd74694af3ac13b3c24a10def4/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/a6/2c69f315254bc694083ede61b264ed/frameset.htm


• Business Entity: Profit center, business area • Building: Profit center, business area • Land: Profit center, business area • Rental Object: Profit center, business area, cost center

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.4 DataSource for the Vacancy Reason (0VACREAS_TEXT)

There is already an InfoObject available in BI Content for the vacancy reason (0VACREASON) of classic Real Estate Management. This InfoObject cannot include the vacancy reasons defined in Flexible Real Estate Management in certain cases, because the data type is not the same as the data type used in Flexible Real Estate Management. Therefore, there is a new DataSource with the correct data type.

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.6 DataStore Objects:

• Business Partners for Real Estate Objects (0REFXDS02) • Deleted Real Estate Objects (0REFXDS03)

3.3.7 MultiProviders:

o Conditions and Measurements (0REFXMP01) This MultiProvider contains the following objects:


Conditions (0REFX_C01) Measurements (0REFX_C02)

o Measurements (Arch. and Usage View) (0REFXMP02) This MultiProvider contains the following objects: Measurements (0REFX_C02) Measurements of Architectural Object (0REFX_C12) Contract Measurements (0REFX_C13) Assignment Between Architectural View and Usage View (0REFX_C11) Real Estate Object (0REOBJECT) Assigned Real Estate Object (0RETRGOBJ)

o Partner and Contract (0REFXMP03) This MultiProvider contains the following objects: Business Partners for Real Estate Objects (0REFXDS02) Contract (0RECONTRACT)

o Workbooks for the existing role Real Estate Manager (SAP_BW_REFX_RE_MANAGER): Contract Measurements for Object(ZTF3DEMFG7NMNHOJND81R2AFV) Contract Measurements (U0IBQDF75Q1L21SE81E8BKU5A) Usage Object Measurements (GTXCUJLZOKTS29HNJCLEXMFBO) Vacancy Overview (00Z7XO1GC4W80FX6K2D9ZGQFH) Partner for Contract (1ONUM9PHZP6TJSUDEJZ3030FX) Conditions Overview (U4F17W253FE6ENINLVK2MQIYM)

o Workbooks for the new role Real Estate Manager for Architectural Objects (SAP_BW_REFX_RE_ARCHITECTUR):

Measurements of Architectural Object (Q5GF8K28W3CC78UOFV057VT99) Architecture – Assignment Report (MBJVPAZNC8K5IPDJPX6U61Y3W) Usage Objects – Assignment Report (H115D4XIQSHPN3O9P4NDVDOLV) Architectural Object (Hierarchy) (ZKJWWCV2BXEGRONKNIKRDXEEV) Architectural Object (1WOGKW791IO3DB23U1B605XER)

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)


3.4 Public Sector Collections and Disbursement


Area Public Sector Collections and Disbursement / Tax and Revenue Management Country Relevance Valid for all countries

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.


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

3.4.4 Info Sets for Dunning History

Technical Name Description 0FC_IS01 Business partner payment 0FC_IS02 Business partner identification (ID) 0FC_IS03 Contract account attribute


3.5 Payment History in SAP Contract Accounting


Area FI-CA Country Relevance Valid for all countries

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:

3.5.2 DataSources for Payment History: Technical Name Description 0FC_PAY Payments 0FC_SRCTP_TEXT Source Type 0FC_PAYTP_TEXT Payment Type 0FC_RSTAS_TEXT Reverse Status 0FC_CJM_TEXT Cash Journal 0FC_PAYDIR_TEXT Payment Direction

3.5.3 Characteristics for Payment History: Technical Name Description 0FC_SRCTP Source Type for Payments 0FC_PAYIT Payment Identifier 0FC_SUBNO Sequence Number 0FC_PAYTP Payment Type for Payments 0FC_PAYDIR Payment Direction 0FC_XCLAR Duration of Clarification Activity 0FC_RSTAS Reverse Status 0FC_TIMESTAMP Time Stamp for BI Delta Extraction 0FC_OFFIC Branch in Cash Journal

3.5.4 KeyFigures for Payment History: Technical Name Description 0FC_BETRW Payment Document Amount

3.5.5 DataStore Objects for Payment History: Technical Name Description 0FC_DS21 Payments

3.5.6 Queries for Payment History: Technical Name Description 0FC_MP21_Q0001 Payments

3.5.7 InfoCubes for Payment History: Technical Name Description 0FC_C21 Payments

3.5.8 MultiProviders for Payment History: Technical Name Description 0FC_MP21 Payments


3.5.9 Process Chain for Payment History: Technical Name Description 0FC_PAY_INIT_P01 Delta-init for Payments 0FC_PAY_DELTA_P02 Delta-upload for Payments


3.6 Returns in SAP Contract Accounting


Area FI-CA Country Relevance Valid for all countries

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:

3.6.2 Data sources for Payment Returns: Object Type Technical Name Description DataSource 0FC_RET Returns DataSource 0FC_RLGRD_TEXT Return Reason Text DataSource 0FC_RLDIR_TEXT Return Direction Text

3.6.3 Characteristics for Payment Returns: Technical Name Description 0FC_RLBEL Number of the Return Document 0FC_KEYR1 Returns Lot 0FC_POSRA Item Number in a return Lot 0FC_RELGRD Return Reason 0FC_STODT Reversal Document Posting Date 0FC_XSTOR Document Has Been Reversed 0FC_RLDIR Return Direction 0FC_STBLG Number of Reverse/Reset Document

3.6.4 Key Figures for Payment Returns: Technical Name Description 0FC_BETRWR Partial Amount of Return 0FC_BETRR Return Amount 0FC_BTRB1 Charge Amount from Bank 1 0FC_BTRB2 Charge Amount from Bank 2 0FC_BTRB Charge Amount from Bank 0FC_STBB1 Tax Amount: Bank Charge 1 0FC_STBB2 Tax Amount: Bank Charge 2 0FC_BTRV1 Return Charge 1 0FC_BTRV2 Return Charge 2 0FC_BTRV Return Charges 0FC_STBV1 Tax Amount: Return Charges 1 0FC_STBV2 Tax Amount: Return Charges 2 0FC_RLGB1 Graduated Charge 1 0FC_RLGB2 Graduated Charge 2 0FC_RLGB Graduated Charges 0FC_RETNO Number of Returns

3.6.5 DataStore Objects for Payment Returns: Technical Name Description 0FC_DS20 Returns 0FC_DS22 Returns Lot


3.6.6 Queries For Payment returns: Technical Name Description 0FC_MP20_Q0001 Returns

3.6.7 InfoCubes for Payment Returns: Technical Name Description 0FC_C20 Returns

3.6.8 MultiProviders for Payment returns: Technical Name Description 0FC_MP20 Returns

3.6.9 Process Chain for Payment Returns: Technical Name Description 0FC_RET_INIT_P01 Delta-init for Returns 0FC_RET_DELTA_P02 Delta-upload for returns

3.7 Collections Management in Contract Accounting

3.7.1 Technical Data Product Version SAP Netweaver 7.0, BI Content Add-on 4

Area Contract Accounts Receivable and Payable Country Relevance Valid for all countries

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.

3.7.2 DataSources for Collections Management: Technical Name Description 0FC_WLI Work Items 0CRM_CIC_BDC_WLI IC Event Log BDC 0FC_CRMTP_TEXT Type for CRM Query 0FC_ASGTYP_TEXT Work Item: Assignment Category 0FC_ASGRES_TEXT Work Item: Assignment Reason 0FC_WLICAT_TEXT Work Item: Category 0FC_SUCCDES_TEXT Work Item: Collection Result 0FC_ORIG_TEXT Work Item: Origin 0FC_STAT_TEXT Work Item: Status 0FC_SUBSTAT_TEXT Work Item: Substatus

3.7.3 Characteristics for Collections Management: Technical Name Description 0FC_WLIGUID Work Item: Identification 0FC_ORIG Work Item: Origin 0FC_ORIGKEY Work Item: Key of Origin


0FC_WLICAT Work Item: Category 0FC_AENAM Last Changed By 0FC_XSTOR Document Has Been Reversed 0FC_XMAND Work Item: Mandatory 0FC_SCORE Ranking 0FC_STAT Work Item: Status 0FC_SUBSTAT Work Item: Substatus 0FC_SUCCDES Work Item: Collection Result 0FC_ASGTYP Work Item: Assignment Category 0FC_ASGRES Work Item: Assignment Reason 0FC_WLIDENT Worklist: Identification 0FC_CONTACT Collections Contact Person 0FC_XCLCASE Enforcement Work Item 0CIC_EVTYP Type for CRM Query 0FC_STDATE Work item: Date of Resubmission 0FC_ENDDATE Work Item: Date of Resubmission

3.7.4 KeyFigures for Collections Management: Technical Name Description 0FC_WLIDUR Duration of Work Item Processed in Seconds 0CIC_ICDU Duration of CIC Interaction 0FC_TYPDU Duration of Different Type 0CIC_EVNUM Number of Different Type

3.7.5 DataStore Objects for Collections Management: Technical Name Description 0FC_DS23 Work Items 0FC_DS24 Dunning Header and Work Items 0CIC_DS42 IC Analysis (FICA): Event Log BDC Wok Item 0CIC_DS43 IC Interaction and Activities 0CIC_DS44 IC Analytics: Event and Event Parameter 0CIC_DS45 Interaction and Event (Inbound) 0FC_DS25 Interaction and Work Item (Outbound)

3.7.6 Queries for Collections Management: Technical Name Description 0FC_MP24_Q0001 Dunning Header and Work Items 0CIC_MP45_Q0001 Interaction and Event (Inbound) 0FC_MP25_Q0001 Interaction and Work Item (Outbound)

3.7.7 InfoCubes for Collections Management: Technical Name Description 0FC_C24 Dunning Header and Work Items 0CIC_C45 Interaction and Event (Inbound) 0FC_C25 CRM and ERP — Dunning and Work Items (Outbound)

3.7.8 MultiProviders for Collections Management: Technical Name Description 0FC_MP24 Dunning Header and Work Items 0CIC_MP45 Interaction and Event (Inbound) 0FC_MP25 Interaction and Work Item (Outbound)

3.7.9 Process Chain for Collections Management: Technical Name Description 0FC_CM_INIT_P01 Delta Initialization for Collections Management 0FC_CM_DELTA_P01 Delta Update for Collections Management


3.8 Revenue Distribution in SAP Contract Accounting

3.8.1 Technical Data Product Version SAP Netweaver 7.0, BI Content Add-on 4

Area Contract Accounts Receivable and Payable Country Relevance Valid for all countries

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:

3.8.2 Data sources for Revenue Distribution: Technical Name Description 0FC_RDI Revenue Distribution 0FC_AUGRD_TEXT Text for Clearing Reason 0FC_PERSLK_TEXT Text for Revenue Distribution Application

3.8.3 InfoSources for Revenue Distribution: Technical Name Description 0FC_RDI Revenue Distribution

3.8.4 DataStore Objects for Revenue Distribution: Technical Name Description 0FC_DS18 Revenue Distribution and Aggregated Distribution

3.8.5 IInfoCubes for Revenue Distribution: Technical Name Description 0FC_C018 Revenue Distribution

3.8.6 MultiProvider for Revenue Distribution: Technical Name Description 0FC_MP18 Revenue Distribution

3.8.7 Queries for Revenue Distribution: Technical Name Description 0FC_MP18_Q0001 Initial Distribution 0FC_MP18_Q0002 Posted Distribution

3.8.8 KeyFigures for Revenue Distribution: Technical Name Description 0FC_PAMOUNT Partial Amount in Transaction Currency with +/- Sign 0FC_TAMOUNT Total Amount in Transaction Currency with +/- Sign 0FC_BETRWDI Distributed Amount in Transaction Currency with +/- Sign 0FC_ITEMNO Number of Initial Distribution 0FC_ITEMNOP Number of Posted Distribution 0FC_BETRWP Posted Distribution Amount in Transaction Currency with +/- Sign


3.8.9 Characteristics for Revenue Distribution: Technical Name Description 0FC_FINRE Contract Account of Final Recipient 0FC_CORRECT Revenue Distribution: Correction Record 0FC_PERSL Revenue Distribution: Application Period 0FC_VALPER Validation Period 0FC_XAGGR Aggregated Posting of Revenue Distribution 0FC_DISPER Distribution Period 0FC_DISPERR Distribution Period Reversal 0FC_DISGRP Group for Aggregated Revenue Distribution 0FC_GPARTDI Final Recipient Business Partner Number 0FC_VKONTDI Final Recipient Contract Account Number 0FC_VTREFDI Final Recipient Contract 0FC_SUBAPDI Final Recipient Subapplication 0FC_XBLNR Reference Document Number 0FC_XDETDOC Individual Document Posting for Revenue Distribution 0FC_XNEGP Negative posting for Revenue Distribution 0FC_DISTYP Category of Revenue Distribution 0FC_CPUDT Day On Which Accounting Document Was Entered 0FC_AUGDT Clearing Date 0FC_OPBELD Distribution Document Number


4 Human Resources

4.1 DataSources for Course Appraisals


Area SAP Learning Solution Country Relevance Valid for all countries

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.

4.1.2 New Datasources

0HR_LSO_4 (course appraisal)

0LSO_APP_DOC_ATTR (document data)

0LSO_APP_ROW_ID_TEXT (row number)

0LSO_APP_VA_TEXT (forms)


The DataSources must be activated before they are used in a system for the first time. Furthermore, Business Content for SAP Learning Solution and the following DataSources from BI Content of the Goal Settings and Appraisals component must also be activated:

• 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)


4.2 BI Content for Personnel Administration for Concurrent Employment (Enhanced)


Area Concurrent Employment (PA-CE) Country Relevance Valid for all countries

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):

Number of Leavers - Person ID key figure (0LEAVERS)

Number of Leavers for Organizational Unit DataSource (0ORGUNIT_ATTR_LEAVER_NOS)

The following BI Content was changed:

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.

http://service.sap.com/%7Eform/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1167706&_NLANG=en&_NVERS=0


5 Industries / Financial Services

5.1 - Reconciliation of Data from Different Systems


Area banking services from SAP Country Relevance Valid for all countries

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.2 New Objects:

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)

http://help.sap.com/saphelp_nw70/helpdata/en/34/ce4b00fe2d4fea9044930b2409c580/content.htm


• Mismatch Balances (0OA2_C01) • Open Mismatch Balances (0OA2_C02) • Detail Balances (Direct Access) (0OA2_VP01)

5.1.7 DataStore Objects

• BACM Flows (Aggregated) ( 0OA1_DS01) • SDL Flows (Aggregated, Write-Optimized) (0OA1_DS02) • BACM Balances (Write-Optimized) (0OA2_DS01) • SDL Balances (Write-Optimized) (0OA2_DS02) • Balances (Details) (0OA2_DS03) • Sender Details (Write-Optimized) (0TP_DS01) • Receiver Details (Write-Optimized) (0TP_DS02)

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)

5.1.10 Key Figures

• Amount (0BA_RCAM) • Receiver Amount (0BA_RCAMR) • Sender Amount (0BA_RCAMS) • Variance Amount (0BA_RCAMV) • Counter (0BA_RCCT) • Receiver Counter (0BA_RCCTR) • Sender Counter (0BA_RCCTS)

Variance Counter (0BA_RCCTV)


5.2 Field Length of the Condition Group (0TB_COGROUP) Characteristic (Changed)

5.2.1 Technical Data Product Version SAP Netweaver 7.0 BI Content Add-On 4 SP01

Area Transaction Banking Country Relevance Valid for all countries

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.


After importing the BI Content, you need to adjust the following tables to the new field length:

• /BI0/PTB_COGROUP • /BI0/STB_COGROUP • /BI0/PBT_COND

Transaction SE14 is available to help you do this.

Afterwards, activate the Condition Group 0TB_COGROUP characteristic.

If you have used this characteristic in your own development, you also need to make appropriate adjustments, especially in the relevant queries

5.3 Update Rule: Individual Condition (Changed)

5.3.1 Technical Data Product Version SAP Netweaver 7.0 BI Content Add-On 4 SP01

Area Transaction Banking Country Relevance Valid for all countries

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.

5.4 Business Content for SAP Claims Management (Enhanced)


Area SAP Claims Management Country Relevance Valid for all countries

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.


The following DataStore objects have been enhanced with additional info objects:

• 0ISCMDS01 Claim data • 0ISCMDS02 Subclaim data • 0ISCMDS03 Payment data (item) • 0ISCMDS26 Subrogation/recovery (header) • 0ISCMDS27 Subrogation/recovery item

The downward data flow has been adjusted

6 Industries – Media

6.1 BI Content for Intellectual Property Management (Enhanced)


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).


The following BI Content objects have been enhanced for multiple payees:

• InfoProvider Outgoing Royalties (Billing Items) (0IPM_DS15) • InfoProvider Outgoing Royalties to the License Acquisition Contract (0IPM_C09) • InfoProvider Outgoing Royalties to the Service Contract (0IPM_C10) • MultiProvider Overall View of Business Scenarios (0IPM_MC02) • BI presentation role IPM Analyst for Media Companies (SAP_BW_IPM_ANALYST)


The data flow has been enhanced.

6.1.4 Effects on Configuration

To use the multiple payees function for IPM, you must make the settings listed in Customizing for Customer Relationship Management under Industry-Specific Solutions Media Intellectual Property Management Transactions Configure Settings for Multiple Payees .



7 Industries Public Sector

7.1 Collections and Disbursement

7.1.1 Technical Data

Product Version SAP NetWeaver 7.0 BI Content Add-On 4 Area Public Sector Collections and Disbursement / Tax and Revenue Management


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

7.1.4 Info Sets for Dunning History Technical Name Description

0FC_IS01 Business partner payment 0FC_IS02 Business partner identification (ID) 0FC_IS03 Contract account attribute


8 Industries –Trade Industries

8.1 MAP Pre-Season Strategic Merchandise Planning


Area Merchandise and Assortment Planning Country Relevance Valid for all countries

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.

8.1.2 Planning Templates

Retail Method of Accounting (RMA)

• 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.



New Retail Analytic Menu : UPAR_IP

New Transactions:

• UPARP_RMA_STRA: RMA Strategic Planning • UPARP_RMA_MERC: RMA Merchandise Planning • UPARP_RMA_STOR: RMA Store Planning • UPARP_RMA_RECO: RMA Reconciliation Planning • UPARP_CMA_STRA: CMA Strategic Planning • UPARP_CMA_MERC: CMA Merchandise Planning • UPARP_CMA_STOR: CMA Store Planning • UPARP_CMA_RECO: CMA Reconciliation Planning • UPARP_HIER_T: Report that generates a time hierarchy used in the queries • UPARP_HIER_S : Report that generates a store hierarchy used in the queries

New Customizing:

• IMG Activity BW_BCT_RT_MAP_2 Comparability Indicator Settings for Stores • IMG Activity BW_BCT_RT_MAP_3 General Settings

8.2 MAP Master Data Planning Application (Enhanced)



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:

View Type View Name Description 0RMP_V1_STYLE_M Create new style per hierarchy node and material category 0RMP_V2_COLOR_M Create new color per merchandise group 0RMP_V4_PSQS_M Maintain pack size and quota scale per style/color

Tabular

0RMP_V5_SIZE_M Create new size per merchandise group 0RMP_V3_STYCO_A Assign color to style per merchandise group

Assignment 0RMP_V6_STYSZ_A Assign size per merchandise group

The standard maintenance views are used in the Retail Purchasing Plan Integration Sample application.


0RT_CHARACTERISTIC_ATTR and 0RT_CHARACTERISTIC_TEXT (new in EA-RETAIL EHP4)

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).

0RF_CHARVAL_ATTR and 0RF_CHARVAL_TEXT

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).

http://help.sap.com/saphelp_nw70/helpdata/en/f2/f35d3cf39f4b1b904d3cf49243522f/content.htm


0RT_QUOSCL_ATTR and 0RT_QUOSCL_TEXT

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).

8.2.3 Effects on System Administration

The MDP maintenance view customizing application includes enhancements that allow you to:

• 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:

• Selection criteria can be initialized at runtime when launching the application • Results can be displayed automatically when the application is started • Selection criteria now support standard ranges of values • Search help (F4-help) is now available in the selection criteria section and in the results table (columns). The

Search help (F4-help) detects relevant attributes in selection criteria and results table, and lists all the valid inputs.

• Multiple-row copy • Select and deselect all rows • Multiple assignment to rows and/or columns

The MAP Release Workbench includes the following enhancement:

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.

New BAdIs are also available:

Locking mechanism BAdI

Use this BAdI to implement a flexible lock on the MDP Web Dynpro views depending on the selection criteria values (BADI_UPARM_VIEW_LOCK)

Authorization mechanism BAdI

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)

MDP maintenance views Search help (F4-help)

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)

8.3 Retail Purchasing Plan Integration Sample



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).

8.4 Retail Method of Accounting (RMA) (enhanced)


Area Country Relevance Valid for all countries

SAP has already supplied RMA for Release BI 7.03 SP08 and SP09.

Several functional enhancements are available. These are described below.

Note that you must only use RMA in certain countries.


The implementation of SAP ERP and SAP BI is a prerequisite for using RMA. In SAP ERP the valuation at cost (CMA) must be active and the inventory must be initialized correspondingly. The valuation according to RMA is carried out as follows: at the end of each posting period the inventory values according to RMA are recalculated and the differences are posted to special correction accounts in FI. To ensure correct consideration of sales at the cash desk in the RMA, you also require SAP Point of Sale Demand Management (POS DM) in order to transfer the sales directly from the POS to SAP BI.



The following important functional enhancements are supplied with BI 7.04 SP01:

• 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) .



9 SAP Governance, Risk, and Compliance (GRC)

9.1 SAP GRC Process Control

9.1.1 Technical Data Product Version SAP Netweaver 7.0 BI Content Add-on 4

Area SAP GRC Process Control Country Relevance Valid for all countries

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.2 Analysis Scenario

• Control Testing Evaluations • History Heat Map Analysis • Ineffective Controls for Control Objective/Risks • Ineffective Controls for Key Accounts

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.4 Web Template

• Web Template: Control Testing Evaluations History for Org. Unit • Web Template: Control Testing Evaluations History Overall • Web Template: Event Summary Report • Web Template: Failed Design Assessments for CO-Risks • Web Template: Failed Design Assessments for Key Accounts • Web Template: Failed Self Assessments for CO-Risks • Web Template: Failed Self Assessments for Key Accounts • Web Template: Failed Testings for CO-Risks • Web Template: Failed Testings for Key Accounts • Web Template: Global Heat Map • Web Template: Global Heat Map for Events • Web Template: Global Heat Map for Events: Region • Web Template: Ineffective Controls for Control Objective Risks • Web Template: Ineffective Controls for Key Accounts

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


• Organization Unit Level Authorizations

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


• 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


• PC Subprocess-Account Group-Assertion-Control Assignments • PC Subprocess-Control Objective-Risk-Control Assignments • Process Controls Authorizations

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


• Number of Remediation Plans for Control Self Assessment Issues • Number of Remediation Plans for Effectiveness Test Issues • Number of Remediation Plans for Entity Level Control Assess. • Number of Remediation Plans for Subprocess Design Issues • Number of Self Assessment Issues • Number of Subprocess Design Issues • Percentage Deficiency • Significantly Deficient


• 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


• Subprocess Design Assessment • Subprocess Design Assessment Evaluation Type • Subprocess Design Assessment Processor • Subprocess Design Assessment Rating • Subprocess Design Assessment Status • Subprocess Owner • Superordinate Issue • Testing • Time of Event • Timeframe • Timeframe End Date • Timeframe Start Date • Year

9.1.13 Process Chains

• GRC PC Events: Delete All Data • GRC PC Events: Load Data – Full • GRC PC: Delete All Data (Master/Transactional/Hier. Data • GRC PC: Load and Process Hierarchies (for one Timeframe) • GRC PC: Load Attributes – Master Data Texts • GRC PC: Load Entities – Master Data Attributes • GRC PC: Load Entities – Master Data Texts • GRC PC: Loan Transactional Data • GRC PC: Process Attributes (PSA) – Master Data Texts • GRC PC: Process Entities (PSA) – Master Data Attributes • GRC PC: Process Entities (PSA) – Master Data Texts • GRC PC: Process Transactional Data (PSA)

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


• Risk Attributes • Risk Texts • Statuses Texts • Subprocess Attributes • Subprocess Texts • Testing Attributes • Testing Texts • Timeframe Attributes • Timeframes Hierarchy • Timeframe Texts


9.2 SAP GRC Access Control

9.2.1 Technical Data Product Version SAP Netweaver 7.0 BI Content Add-on 4

Area

There are two areas in the SAP GRC Access Control product:

Risk Analysis and Remediation (formerly CC).

Compliant User Provisioning (formerly AE). Country Relevance Valid for all countries

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):

1260280 for NW BI 7.04 for Access Control

1260279 for NW BI 7.03 for Access Control

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.

The present release note content is organized as follows.

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.

9.2.2 Updates to Business Content for Risk Analysis and Remediation

Enhancements in BI Content 7.04 SP00

9.2.3 New Content:

• Additional Rules (Function-Action Relationships, Function-Permission Relationships and Critical Action Rule Detail) • Process Chain GCC_RULES modified to incorporate additional rules • Long Portal IDs handling for Action, Role, Permissions Field, Permissions Object, Permissions Value and Critical Role • Process Chain GCC_LONG_IDS created handle Long Portal IDs • Query 0GCC_CRVI_Q0001 created to support Critical Role violations analysis with Long Portal IDs • Query 0GCC_RPV_Q0002 created to support Role Permission Risk violation analysis with Long Portal IDs.

Minor changes:

• Renaming of some objects to assimilate to new product name. • Adjusted Process Chains for linear processing due to UD Connect performance issues.

9.2.4 Issues existing in BI Content 7.04 SP00

• Removal of direct DDIC references to conform to SAP Best Practice standards. • Apply note 1170897: Permission Violations Delta Deletion Programs.


9.2.5 Enhancements in BI Content 7.04 SP01

Minor changes:

• 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_PRMVTO,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.

9.2.6 Updates to Business Content for Compliant User Provisioning

Issues existing in BI Content 7.04 SP00

• Language conversion enhancement for DSO 0GAE_D03 • Apply note 1229932: Duplicate data records in CUP language dependent text DTPs

Enhancements in BI Content 7.04 SP01

• 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.

9.2.7 Notes on Business Content for Risk Analysis and Remediation

The SAP Business Information Warehouse-Risk Analysis & Remediation (BI-RAR) Business Content 7.04 SP 01 for SAP GRC Access Control provides DataSources, InfoProviders, necessary transformations, required pseudo delta functionality, history storage, long descriptions, supporting master data, process chains and some representative queries for the following primary areas of CC:

• Permission Violations (User, Role, Profile) • Management Reporting (Summary Total, Business Process, Risk, Risk Detail and Alerts) • Mitigations (User, User Organization Rule, Role, Profile and HR Object) • Alerts (Header and Detail • Critical Violations (Action, Role and Profile • Rules (Critical Role, Critical Profile, Function-Permission, Risk-Function, Risk-Owner, Risk-Permission, Risk-Rule Set,

Supplementary)

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.

9.2.8 Permission Violations Delta Processing

Permission Violations are categorized by User, Role and Profile Permission Violations. Since the volume of data for these sources can be extremely large and they are not generally combined in reports, they are stored in separate InfoProviders in BI BC. Separate InfoProviders for current and historical data have been provided due to data volume, InfoProvider maintenance and delta processing. Configuration for supplying the historical data from the history DSO to the history cube has not been provided but the customer may choose to implement this if they plan to perform involved analysis on the historical data. MultiCubes have not been delivered with BI BC, but customers may choose to create them for reporting concurrently on current and historical data.

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.


Due to the volume of violations data and the need for storing historical changes, a delta capability is provided. However, neither a delta queue nor reverse postings are provided by the source system. And due to the limited flexibility of data selection when using UD Connect, a pseudo delta procedure is required.

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.

9.2.9 Management Reporting

There are two types of tables in CC for Management Reporting. One type of table keeps the history as changes occur by refreshing only the current month. The other type of table is fully refreshed each time CC processes Management Reporting.

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.

9.2.11 Alert Header and Detail

The table in CC storing the Alert Header data is an ongoing file that will be extracted in delta mode from BI using an InfoPackage selection criteria based on records with RUNDATE since the latest BI extract date.

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


that eliminates any incoming records which are not part of the most recently extracted header records. This is performed by looking up these values as recorded in the Alert Header DSO.

9.2.12 Critical Violations

No historical tracking is recorded in CC or BI for critical violations. InfoCubes with full refreshes are used to store the information.

9.2.13 Rules Delta Processing

Full extracts and DSO refreshes are performed in order to maintain an accurate snapshot of the current rules and relationship data. Additionally, the history of changes to these rules and relationships is stored in historical DSOs by using the Risk-Function Change Log DSO and a start routine which filters out all of the records from the incoming full extract that are not in the change log DSO.

The history of changes is maintained for the following Rules DSOs: Risk-Rule Set, Risk-Owner, Risk-Function and Function-Permission. All other Rules will only have the current values refreshed in the Current DSO via a full extract.

9.2.14 Long Descriptions

Many descriptive fields in CC contain more than 60 characters. This causes a problem in BI since the maximum length of any object is 60 characters. And, since most of these descriptive fields in CC are language dependent, the following method was designed to store and report on these long descriptions. InfoObjects containing source fields with language dependent descriptions from CC have a DSO created for storing this information. The key to the DSO is the InfoObject and the Language value. The long descriptive fields are extracted from CC and broken up into 60 character pieces and stored in separate InfoObjects within these DSOs for each language that is maintained.

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.

9.2.15 Portals Long IDs

Portals Long ID configuration enables BI to report on the extended IDs (up to 300 characters) which are enabled in a portals system. As of 7.04 SP00, this has been configured in BI for Roles, Critical Roles, Actions and Permission Objects, Fields and Values. The sequence number and associated long IDs are extracted from table VIRSA_CC_EXTOBJ and stored in DSO 0GCC_EXID. When BI master data extracts are performed from the RAR tables for Roles, Actions and Permission Objects, Fields and Values, the long IDs are determined from this DSO and are populated in attributes of the associated InfoObjects.

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.

9.2.16 Business Content Activation

Business Content activation may be done in several standard ways of the installer’s choice. Be sure to choose the proper UD Connect Source System and the Myself Source System when activating.

However, one recommendation is to activate the objects below in the following order:

InfoObject Catalogs 0GCC_*, selectingOnly Necessary.

3.x InfoSource 80GCC_URP, selecting In Dataflow Before and Afterwards.


InfoProviders associated with InfoAreas 0GCC_*, selecting In Flow Before.

Process Chains (GCC*), selecting Only Necessary.

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.

There are two things of which to be aware:

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.


There are two strings of data loading which are necessary to make your CC reporting operational in BI.

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.18 Notes on Business Content for Compliant User Provisioning

As of SAP Netweaver 7.0 BI Content Add-on 4, updated business content is available for the Compliant User Provisioning area. It is described in the following sections.

9.2.19 InfoAreas

SAP GRC Compliant User Provisioning (CUP) (0GRC_AE)

GRC CUP MASTER DATA (0GAE_MD)


9.2.20 Roles

• SAP GRC Compliant User Provisioning (CUP) Queries SAP_BW_GRC_AE_ROLE

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)


• Request Header - Current & Archived (0GAE_MP01) • AE CUP Reporting (0GAE_MP02)


Process Chains must be run in the following order:

• GRC CUP: Master Data Attributes (0GAE_MD) • GRC CUP: Master Data Text (0GAE_TEXT) • Process chain updated as of BI 7.03 post-SP09 to incorporate new DSO 0GAE_D03 replacing DSO 0GAE_LOC

(see note 1170899). • GRC CUP: Load of Archived REQ to be unavailable in Source Sys. (0GAE_ARCH_TO_CUBE) • Run this, here, only for occasions when source data is archived off the source system. • Process chain updated as of BI 7.04 SP01 to delete existing contents of DSO 0GAE_HDR and InfoCube 0GAE_C01 • GRC CUP: Transaction, incl. long texts (Init/Full 0GAE_TRANSACTION) • GRC CUP: Archived, from Source System (0GAE_TRANSACTION_AR Transaction Full) • Process chain updated as of BI 7.04 SP01 to incorporate deletion of all non-archived PSAs to avoid the reloading data • GRC CUP: Analytical layer General process chain (0GAE_ANALYTICAL_GENERAL) • IOBJ 0GAE_REQNO updated here from DSO 0GAE_HDR to enable Master Data updates performed in

Transformations of InfoCubes 0GAE_C02 (Risk Violations), 0GAE_C06 (Role Provisioning), 0GAE_C03 (SOD Review), 0GAE_C04 (User Access Review) and 0GAE_C07 (User Provisioning)


• Application Log (0GAE_APLG) • Business Process Locale (0GAE_BUPL) • Business Sub Process Locale (0GAE_BSPL) • Company Locale (0GAE_COML) • Connector Locale (0GAE_CNTL) • Custom Field (0GAE_CMFD) • Custom Field Locale (0GAE_CMFL) • Custom Field Value (0GAE_CTVL ) • Custom Field Value Locale (0GAE_CFVL) • Employee Locale (0GAE_EMPL)


• Employee Type (0GAE_EMTP) • Function Area Locale (0GAE_FNAL) • Locale Mapping (0GAE_D03) • This DSO is a replacement as of BI 7.03 post-SP09 for DSO 0GAE_LOC (see note 1170899). • Message (0GAE_MSG) • Message Parameters (0GAE_MSGP) • Request Application (0GAE_APL) • Request Attachment (0GAE_ATCH) • Request Attachment - Archive (0GAE_ARAT) • Request Custom Fields (0GAE_CSFL) • Request Header (0GAE_HDR) • Request Header 1 (0GAE_HDR1) • Request History (0GAE_HST • Request History - Archive (0GAE_ARHS) • Request Mitigation (0GAE_MTGN) • Request Organizational Role (0GAE_ORGR) • Request PD Profile Role (0GAE_PDRL) • Request Review Coordinator (0GAE_RVCR) • Request Role Profile (0GAE_RLPR) • Request Segregation of Duties Custom Field (0GAE_SODC) • Request Segregation of Duties Function (0GAE_SODF) • Request Segregation of Duties - Risk (0GAE_SOD) • Request Type Locale (0GAE_TYPL) • Request User Access Review (0GAE_UARW) • Request Users (0GAE_USER) • Request Work Flow Transactions (0GAE_WTRN) • Request Workflow History (0GAE_WHST) • Role Approver (0GAE_RLAP) • Role Details (0GAE_RLDT) • Role Details Locale (0GAE_RDTL) • Role Provisioning (0GAE_D02) • User Access Review - Role (0GAE_UARO) • User Access Review - Role W-O (0GAE_UARR) • User Provisioning Overview (0GAE_D01) • User Sequence (0GAE_USSQ)

9.2.26 Master Data Attribute & Text

The text start routines of the following objects were modified as of BI 7.03 post-SP09 to reflect the new DSO 0GAE_D03 as a replacement for DSO 0GAE_LOC See note 1170899.

• Business Process (0GAE_BUSPRC) • Business Sub Process (0GAE_BUSUPR) • Company (0GAE_COMPID) • Field Name (0GAE_FLDNAM) • Functional Area (0GAE_FNAREA) • Request Type (0GAE_REQTYP) • Role Profile Name (0GAE_RLPRLN) • Role Type (0GAE_RLTYP) • System (0GAE_SYSTEM)

9.2.27 Master Data Attribute

• Request Number (0GAE_REQNO) • Request Priority (0GAE_RQPRIY)

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)

• Violation Count (0GAE_VIOCNT)

BI content

Documents

Transcript of BI content