Read RI_31C_en.pdf text version

Business Information Warehouse Release Notes

BW-BCT Business Content and Extractors

Release 3.1 Content

______________________________________________________________ __

Copyright

Copyright(c) 1995 SAP AG. All rights reserved. Neither this document nor any part of it may be copied or reproduced in any form or by any means or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change without notice. SAP is a registered trademark of SAP AG. All other products which are mentioned in this documentation are registered or not registered trademarks of their respective companies.

SAP AG Table of Contents R/3 System ______________________________________________________________

__

1.1 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.1.6 1.1.7 1.1.8 1.1.9 1.1.10 1.1.11 1.1.12 1.1.13 1.1.14 1.1.15 1.1.16 1.1.17 1.1.18 1.1.19 1.1.20 1.1.21 1.1.22 1.1.23

BW-BCT Business Content and Extractors Business Content for Asset/Liability Management Moving the extractors into PI_BASIS Business Content for Parallele Position Management in CFM-TM Customer Loyalty Marketing Category Management Consumer Products Enhancements in the Area "Controlling" Business Content for cProjects (New) BW Content for mySAP CRM (Release 3.0 and above) Changes to BW Content in CRM Sales for the Personalization Variable Changes to BW Content for CRM Sales to Enable Alerts Changes to BW Content for CRM Sales: Top Five N Queries Personalization Variables for Roles in BW and Enterprise Portal (CRM) UI-Verbesserung der Customer-Lifetime-Value-Analyse (geändert) Integration of Installed Base Data in Service Analytics (New) Changes to BW Content in CRM Marketing for the Personalization Variabl Web Content für Kundenzufriedenheitsund -loyalitätsanalyse (erw.) Business Content for Service Analytics (Enhanced) Customer Analyses in Service Analytics (New) Web Templates for Service Analytics in the Enterprise Portal (New) Separation of extractors for InfoSources 0FI_*_4 Tax reporting for advance return for tax on sales Claims Management System (FS-CM): Extended Business Content SAP CRM: Intellectual Property

1 1 2 3 3 4 5 6 7 7 8 9 9 11 11 12 13 13 14 15 15 16 17

______________________________________________________________ __

SAP AG 16.10.2002 iii

R/3 System Table of Contents SAP AG ______________________________________________________________

__

1.1.24 1.1.25 1.1.26 1.1.27 1.1.28 1.1.29 1.1.30 1.1.31 1.1.32 1.1.33 1.1.34 1.1.35 1.1.36 1.1.37 1.1.38 1.1.39 1.1.40 1.1.41 1.1.42

Management (IPM) New Features in SAP Media unbilled Revenue Reporting with SAP BW and SEM-BPS Business Content for Personnel Cost Planning and Simulation (New) Organizational Management (PA-OS): Enhanced Business Content Personnel Administration (PA-PA): Enhanced Business Content Business Content for Positon Budgeting and Control (new) Profit Center Analytics Retail Content of SAP Project System (Enhanced) Extractors and Business Content SCM Event Management Extractors and Business Content SCM Inventory Management Changes in the area of Supply Chain Performance Management Evaluation of Bidding Engine Bid Invitations and Bids SRM: BW Reporting with SUS-MM Coupling (changed) Trade Promotion Management: Business Content Global Spend Analysis (Changed) SRM: Consolidated Info Objects in the E-Procurement Content SRM: Vendor Evaluation in mySAP Supplier Relationship Management

21 25 30 31 31 32 33 34 35 35 36 39 40 41 43 43 43 44 44 45

______________________________________________________________ __

iv 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

1.1 BW-BCT

Business Content and Extractors

1.1.1 Business Content for Asset/Liability Management

Use With the current release, ALM is fully integrated into the BW. Sample info cubes and queries are delivered, flexible reporting of ALM data is enabled. Template structures provided in the BW system in the form of Cubes, Queries and Reports can be used directly, or the given formats can be copied and extended in order to produce any type of report needed. BW can report on the current and future position of assets and liabilities of a financial institution. This is done via a three-step process: 1. Core ALM Data Extractors - In order to extract data from the ALM system, it is possible to generate various Datasources once the ALM system itself has been configured to a customer's individual requirements. Transaction, hierarchy, and master data Datasources are all supported and allow for the quick and efficient extraction of ALM information. 2. ALM BW Data Warehouse - Cubes are set up in the BW system by defining Characteristics and Key figures. Using three sample cubes as a template, multidimensional data for business-driven Volume, Profitability, and Cash Flows within the banking organization can be easily set up. 3. Reporting - Once data is moved from ALM into its appropriate cube, customers are able to set up reports based on pre-made templates. Gap reporting samples for the US are given to allow for the creation of standard government reporting needs, and users are free to further create a wide range of reports to handle the needs of any large financial institution.

&DATA TRANSFER& &SYSTEM ADMINISTRATION Effects on Customizing Customizing for the extraction of ALM data is done in the banking add-on system. The appropriate customizing transactions can be accessed directly by entering the transaction codes mentioned in each of the following sections.

The different customizing activities are: 1. Create Datasource (transaction ANA_STRUCT_GEN_ALM) In this activity you create a new Datasource. Since it is impossible to deliver a Datasource that is tailored precisely to all the specific requirements that customers have for analyzing data, the procedure applied here, differs from that applied in other applications.

______________________________________________________________ __

SAP AG 16.10.2002 1

R/3 System ______________________________________________________________

__

2. Create Characteristic Hierarchy Datasource (transaction SEM_CHAR_HIER) In this activity, a Hierarchy Datasource is created with which to analyze data from any part of the system that uses Characteristic Hierarchies. The Datasource is generated, but before generation can begin, the generator has to be supplied with the particular characteristic for that you wish to create a hierarchy. 3. Create Characteristic Master Data Text Datasource (transaction SEM_CHAR_TEXT) In this activity, a Text Master Data for any Characteristic within an Analysis Structure is created. The Datasource is generated, but before generation can begin, the generator needs to be supplied with the particular characteristic for that you wish to create a text extractor.

In addition, the following activities have to be executed in the SAP BW: 'Activate Business Content', 'Metadata Upload', 'Mapping Datasource and Infosource Fields', 'Extract Master Data', 'Initializing the Delta Procedure for Transaction Data', 'Regular Extraction of Transaction Data'.

1.1.2 Moving the extractors into PI_BASIS

Use For Plug-In 2002.2, the extractors are no longer a component of the Plug-In for the SAP business partner for Basis release 6.20, but rather are a component of PI_BASIS. This does not affect usability. However, as of PI_BASIS 2003.1, the respective DataSources become obsolete with this in CRM and EBP. Example Until now, the DataSource 0CRM_BPART_ATTR has to be used in CRM for extracting the business partner master record, because the DataSource 0BPARTNER_ATTR contained in the Plug-In was not available in CRM systems. By moving it, it is possible to work in all SAP systems with DataSource 0BPARTNER_ATTR. This is valid for Release PI 2003.1, R/3 4.70, and CRM 4.0.

New delta methods

The delta methods for some business partner extractors were changed from 'Delta Using ALE Change Pointer' to 'Delta Using Delta Queue'. This is valid for the following DataSources: o o o 0BPARTNER_TEXT: Business partner texts 0BP_DEF_ADDRESS_ATTR: Business partner standard address 0BP_RELATIONS_ATTR: Business partner relationships

In order not to lose any delta information, the following steps have to be executed for each DataSource before the activation, meaning before the transfer to the new version: 1. 2. 3. Execute the delta upload for all connected BW systems. This is necessary, because after the Content activation, you can no longer access the old deta records, and these would be lost. Transfer the DataSource directly thereafter (transaction RSA5). Replicate the new version in all connected BW systems.

______________________________________________________________ __

2 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

4.

Execute a delta initialization. In doing so, note the following: a) An initialization without transferring data is technically sufficient. If you should be concerned that delta information was lost during the conversion of the DataSource (by the business partner data changed in the meantime), you can also excute a delta initialization with a data transfer. The named DataSources are zero-downtime-capable in the new version. This means that directly after starting the delta initialization, the delta is logged in the source system. It does not initially begin with the completion of the initialization.

b)

Zero-Downtime

A zero-downtime delta initialization was enabled for the following DataSources: o o o 0BP_ID_ATTR: External ID numbers for the business partner 0BP_IS_ATTR: Business Partner Industries 0BP_STATUS_ATTR: Business Partner Status

1.1.3 Business Content for Parallele Position Management in CFM-TM

Use With this release, parallel position management in the CFM Transaction Manager (CFM-TM) was linked to the SAP Business Information Warehouse (SAP BW). InfoCubes, ODS Objects, DataSources, InfoSources and InfoObjects are provided, which you can use as a basis for defining queries for position- and position trend reporting.

1.1.4 Customer Loyalty Marketing

Use Business Content for "Customer Loyalty Marketing" is a solution which allows retail firms to analyze and carry out customer segmentation and marketing campaigns in SAP CRM, based on POS data. These campaigns are aimed at customers who are known to the retailer through their use of a customer card. Business Content for "Customer Loyalty Marketing" provides structures which enable individual customers to be identified and their data to be combined with POS data. This data provides the basis for customer segmentation. In the first step, the buying behavior of "familiar customers" is examined on the basis of their shopping baskets. This examination results in customer segmentation based on buying behavior. Combining sociodemographic customer data from SAP CRM and sales data from SAP BW allows you to carry out extensive and flexible customer segmentation, using the Segment Builder in SAP CRM Marketing. In the second step you can design and execute sales promotions in SAP CRM, for example, for special

______________________________________________________________ __

SAP AG 16.10.2002 3

R/3 System ______________________________________________________________

__

customer groups or target groups.

1.1.5 Category Management Consumer Products

Use The business process category management (CM) for manufacturers is a highly anticipated collaborative business process and will be performed within 3 mySAP.com standard solutions: BW for CM-related reporting and analysis, SEM for business process-related planning activities, and finally the Enterprise Portal as the framework for doing the collaborative business process. BW as one part of the entire solution comprehends the following main features/functionalities and business content: o o Creating and maintaining multiple distribution channel independent hierarchies, consumer decision trees (CDTs) Pre-configured business content (including content from market-data providers and point-of-sale (POS) systems)

Consumer Decision Tree (CDT) At the heart of the category management solution is the consumer decision tree (CDT), a sophisticated and flexible model of shopper behavior information. You use the CDT to define categories to analyze, plan and execute strategies and tactics in a consumer-centric approach. SAP BW allows you to create, handle, and analyse multiple CDTs, providing you and your collaboration partners with knowledge and flexibility throughout all the stages of category management. Business Content BW comprehends the following business content, e.g.: o o o o o Sales analyses Consumer analyses Pricing analyses Sociodemographic analyses CDT / hierarchy / product / brand / SKU analyses

Effects on Data Transfer POS Data Upload Before you upload the POS data in your BW system, you must define the hierarchy ID of the CDT, if you want to upload the POS data. In the field 0CM_HIEID of the transfer rules you can define the hierarchy ID as a constant. Using the CDT, you have to define a constant hierarchie ID for the field 0CM_HIEID. If you want to upload POS data to more than one CDT version, you must define own transfer rules with a

______________________________________________________________ __

4 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

corresponding hierarchie ID as a constant for each CDT version. In the update rules for basic InfoCubes you can define a constant value (e.g. #000#) for the characteristics 0VERSION (Version). You should use versions to compare actual and planning data in one single query. Syndicated Data Upload Before you upload the syndicated data (market data) you must maintain the DB table CMCPMBD. This table contains the required information about competitor, country and region. For sociodemographical panel data (information about the consumer) we added four consumer profiles characteristics to specify the consumer. This DataSource is for uploading AC Nielsen data only. If you want to upload syndicated data from other data providers you have to specify a modified upload logic as an extra DataSource (modified).

1.1.6 Enhancements in the Area "Controlling"

Use Commitment Line Item Reports In Release SAP BW 3.1 Content, three new DataSources are available for commitment line items: o o o 0CO_OM_WBS_7 WBS Elements: Commitment Line Items 0CO_OM_OPA_7 Internal Orders: Commitment Line Items 0CO_OM_CCA_10 Cost Centers: Commitment Line Items

Generation of Users and Profiles for Cost Center Reporting

For Release SAP BW 3.1 Content, new objects and functions have been added to provide the following features: o o The users for those responsible for areas and cost centers in the standard hierarchy of a controlling area can be loaded from the SAP R/3 System into the SAP BW System. The users and authorization profiles are generated at the click of a button in the BW system for those responsible, displaying the reporting authorizations for the respective cost centers of the area of responsibility belonging to the user. Due to the generated authorization profiles, automatically personalized queries can be called up for these users, depending on their area of responsibility.

o

Further Enhancement of the DataSources 0COORDER_TEXT and 0COORDER_ATTR In Release SAP BW 3.1 Content, the DataSources 0COORDER_TEXT and 0COORDER_ATTR were improved as follows: o o You can perform a delta extraction You now support both selections using the controlling area and the order type

______________________________________________________________ __

SAP AG 16.10.2002 5

R/3 System ______________________________________________________________

__

o

If the parameter 0COORDER_ATTR_TEXT ORGSYSONLY in the table BWOM_SETTINGS is set to X, only order master data with an original in this system is extracted (relevant for ALE distributed order master data in OLTP).

Flexible Definition of Report Lines for Cost Elements in Queries BW report line hierarchies can now be created for cost center reports by using cost elements (0COSTELMNT) with which the values can be directed into different lines depending on the debit/credit indicator (0DB_CR_IND).

1.1.7 Business Content for cProjects (New)

Use From SAP BW 3.1 Content on, you can evaluate data from cProjects in the SAP Information Warehouse (SAP BW). With the Content delivered for this purpose you have the option of evaluating master data and transaction data from cProjects. The reports delivered by SAP concentrate on the evaluation of the planned work and timeframe for cProjects objects as well the work and timeframe for resources assigned to the objects. The objects of the content are located in the new cProjects(0CPR) InfoArea. They contain the following: New role SAP_BW_0ROLE_0050: Project leader in cProjects Neue reports There are a BEx Query and a Web Report available for each report: o o o o o o 0CPR_C01_Q0001 / 0TPL_CPR_C01_Q0001: Tasks Assignments of Project Roles 0CPR_C01_Q0002 / 0TPL_CPR_C01_Q0002: Project Role Assignment 0CPR_C01_Q0003 / 0TPL_CPR_C01_Q0003: Assignment of Tasks Project Role Assignment 0CPR_C02_Q0001 / 0TPL_CPR_C02_Q0001: Project Dates and Work 0CPR_C04_Q0001 / 0TPL_CPR_C04_Q0001: Utilization of Project Roles 0CPR_IS01_Q0001 / 0TPL_CPR_IS01_Q0001: Document Assignment

New InfoCubes o o o 0CPR_C01: Assignments with Work 0CPR_C02: Planning: Dates and Work 0CPR_C04: Dates, Planned Work, Assignments

Neue ODS Objects o o o 0CPR_O01: Assignment of Role to Application Object 0CPR_O02: Assignment of Role to Business Partner 0CPR_O03: Dates and Work of Application Objects and Roles

______________________________________________________________ __

6 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o o

0CPR_O04: Assignment of Documents 0CPR_O05: Assignment of Objects

1.1.8 BW Content for mySAP CRM (Release 3.0 and above)

Use Some areas of business content have been developed for Customer Relationship Management and can be seen in the Administrator Workbench for CRM. However this business content cannot be used in conjunction with CRM Releases 3.0 or 3.1. It forms the preparation for integrating certain business processs that will be delivered in a later CRM release. Do not activate this content as it is currently not supported by SAP. The following areas are affected: o Marketing o External List Management Marketing and Campaign Analysis -> Optimization of Direct Marketing

Sales - CRM Sales Master Data -> Territory Attributes and Person Responsible All InfoObjects named 0CRM_TR*

o

Service - Installed Base Data

1.1.9 Changes to BW Content in CRM Sales for the Personalization Variable

Use The following objects have been changed for Release 3.1 in order to accomodate the variables: o o o 0P_USER (user name) 0P_USSYS (system name of user) CRMOM (organizational hierarchy node)

(see thePersonalization Variable for Roles in BW and Enterprise Portal release note: o Cross-Performance Analyses o Lead Funnel Analysis (0CSALMC02_Q001) Sales Pipeline Analysis (0CSALMC02_Q007) Activities, Opportunities and Sales: Numbers and Volumes (0CSALMC01_Q001) My Team's Planned Activities (0CSAL_C01_Q0013)

Opportunities

______________________________________________________________ __

SAP AG 16.10.2002 7

R/3 System ______________________________________________________________

__

o

Opportunity Funnel Analysis (0CSALMC02_Q005) Opportunity Pipeline Analysis (0CRM_C04_Q011) Sales Volume Forecast (0CRM_C04_Q014) Completed Opportunities acc. to Status (0CRM_C04_Q012) Win/Loss Analysis (0CRM_C04_Q010) Top Five Opportunities (0CRM_C04_Q013)

Sales Orders and Quotations Quotation Funnel Analysis (0CSALMC02_Q007) Incoming Orders -Last 12 Months (0CSAL_C03_Q0003) Quotation Success Rate (0CSAL_C05_Q0003) Open Quotations per Region (0CSAL_C05_Q0004) Top Five Sold-To Parties -Quotations (0CSAL_C05_Q0005)

o

Sales Contracts Top Five Sales Contracts (0CSAL_C04_Q0007) Open Sales Contracts (0CSAL_C04_Q0008)

1.1.10 Changes to BW Content for CRM Sales to Enable Alerts

Use Exceptions have been defined for the following queries so that they can be used to create alerts: o o o Pipeline Anaylsis per Phase (0CRM_C04_Q011) Alert is triggered if the expected sales revenue of an opportunity decreases by a certain value Completed Opportunities Acc. to Status (0CRM_C04_Q012) Alert is triggered if the number of lost opportunities is greater than the defined expected number Quotation Success Rate (0CSAL_C05_Q0003) Alert is triggered if the rate at which quotations are converted to sales orders decreases by a certain percentage Open Sales Orders (0CRM_C03_Q002) Alert is triggered if the open sales volume decreases by a certain amount My Cancelled Contracts (0CSAL_C04_Q0002) Alert is triggered if the number of cancelled contract items exceeds a certain figure

o o

Effects on System Administration In each of the exceptions, you can define the threshhold value at which the alert should be triggered.

______________________________________________________________ __

8 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

In order to enable the exception to trigger a complete alert process, for example, an e-mail in an employee's inbox, or an Alert iView in the mySAP Enterprise Portal, you also need to make the necessary settings in the Reporting Agent. See also For more information about the exceptions in each query, see the query documentation under Business Information Warehouse -> Business Content -> Customer Relationship Management -> Cross-Application Performance Analyses or Sales. For more information about defining alerts, see the documentation in the Business Information Warehouse -> Administrator Workbench -> Reporting Agent.

1.1.11 Changes to BW Content for CRM Sales: Top Five N Queries

Use The following queries enable you to evaluate the top five most valuable documents for a particular sales organization: o o Top Five Opportunities (0CRM_C04_Q013) Top Five Quotations (0CSAL_C05_Q0005)

Changes have been made to each of these queries and additional queries have been created so that they run correctly. o Top Five Opportunities A query has been created (0CRM_C04_Q013_1) that filters the top five opportunities according to the expected revenue. The original query was modified to include this query, which provides the filter variables for a replacement variable for the Transaction Number characteristic (0CRM_OBJ_ID). Top Five Quotations This query has been renamed to Top Five Sold-To Parties (Quotations) because the query actually displays the sold-to parties with the highest cumulated quotation values. A new query has also been created to display the top five quotations (that is quotations with the highest values). It will remain named Top Five Quotations but will have a new technical name 0CSAL_C05_Q0106. Another query has been created to filter the top five quotations according to their value. This query provides the filter values for a replacement variable for the query 0CSAL_C05_Q0106. It runs in the background and has the technical name 0CSAL_C05_Q0106_1.

o

1.1.12 Personalization Variables for Roles in BW and Enterprise Portal (CRM)

Use The content for CRM contains several queries that are appropriate for use by both managerial roles (such as the Sales Manager) as well as representative roles (such as the Sales Representative). As these roles

______________________________________________________________ __

SAP AG 16.10.2002 9

R/3 System ______________________________________________________________

__

view the same data but with a different focus, the data can now be filtered with the use of variables. o Manager In order to restrict data so that the manager only sees data for the node in the organizational hierarchy to which s/he has been assigned, the following change has been made: The 0CRMOM variable (user's node in the organizational hierarchy) has been added to the 0CRMSA_OG_R characteristic (responsible sales organization). This is suitable for managerial roles such as the Sales or Service Manager, for example, who need to analyze data for their organizational units. Representative The following variables have been created in order to restrict the data to documents in which the user, who has logged onto the system, is named as the "employee responsible": 0P_USER This is the variable for the user name and has been added to the navigation attribute 0BP_RESPPER_0USER_NAME (user name). 0P_USSYS This is the variable for the user's system and has been added to the navigation attribute 0BP_RESPPER_0USER_SYST (user's system name). This is suitable for all roles, but is particularly designed for standard employees, such as call center agents, sales or service representatives. Once this variable has been assigned to the Sales Representative role, for example, users who are assigned to this role will see their query data only. Effects on Existing Data These variables have been designed for the following SAP Enterprise Portal roles: o o o o o o o o o o o Sales Manager (SAP_PCC_SALES_MANAGER) Sales Representative (SAP_PCC_SALES_REP) Service Manager (SAP_PCC_SERVICE_MANAGER) Service Representative (SAP_PCC_SERVICE REP) Campaign Manager (SAP_PCC_CAMPAIGN_MANAGER) Customer (SAP_PCC_CUSTOMER_ADVANCED) Interaction Center Agent (SAP_PCC_IC_AGENT) Interaction Center Manager (SAP_PCC_IC_MANAGER) Lead Manager (SAP_PCC_LEAD_MANAGER) Lead Qualifier (SAP_PCC_LEAD_QUALIFIER) Lead Qualifier (external) (SAP_PCC_LEAD_QUALIFIER_EXTERN)

o

Please note, however, that you must also assign this variable to any other Business Warehouse roles that you are using, for example, the Sales Performance Analysis roles (SAP_BW_SALES_PERF_ANALYSIS_PR/LG/ CU/FI) in order to be able to view the queries correctly. Effects on System Administration To assign the variables to the relevant roles, go the SAP menu and choose Tools -> Administration ->

______________________________________________________________ __

10 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

User Maintenance -> Role Administration -> Roles. Select the role that you want to change and choose the Personalization tab. Double-click on the CRM_ROLE_VARIABLE_SETTING personalization object and add the variables 0CRMOM and 0P_USER. You must also assign a priority to the variables so that the system knows which one to call up first for each role. Ensure that the users are named identically in all the relevant systems, that is, Business Warehouse, Customer Relationship Management and the Enterprise Portal. See also For more information about the variables and how they work for the Portal roles, see the CRM People-Centric Administration Guide in the documentation for the Enterprise Portal. For more information about which sales queries have been changed to accomodate these variables, see the Changes to BW Content in CRM Sales for the Personalization Variablerelease note.

1.1.13 UI-Verbesserung der Customer-Lifetime-Value-Analyse (geändert)

Use In SAP BW 3.1 Content wurde die Bedienungsfreundlichkeit der analytischen Applikation Customer-Lifetime-Value-Analyse verbessert, zum Beispiel die grafische Darstellung und die Navigation bei der CLTV-Modellierung.

1.1.14 Integration of Installed Base Data in Service Analytics (New)

Use As of the 3.1 Content release of SAP BW, Business Content is available in the Administrator Workbench to support the extraction of installed base (IBase) data from the CRM system. This content is not compatible with mySAP CRM Releases 3.0 and 3.1. It can only be used with Release 4.0 or above. IBase information contained in service process and confirmation documents (headers and items) is extracted from the CRM system. This enables you to analyze transaction data with a breakdown by IBase and IBase attributes. For example, you can determine costs, revenues, or order values for a particular IBase component. The following Business Content has been created to support the extraction of IBase data: New InfoSources: CRM IBase Transaction Data 0CRM_SERVICE_IBASE_TRANS Number of Installed Base (Texts) 0CRM_IBNUMB Installed Base Category (Texts) 0CRM_IBTYPE Object Type of Component Usage (Texts) 0CRM_COMOTY Object Type for Reference Object in Subject Set (Texts) 0CRM_REFOTY_TXT Authorization Group for Installed Base (Texts) 0CRM_IBAUTG_TXT New DataSources in mySAP CRM Release 4.0:

______________________________________________________________ __

SAP AG 16.10.2002 11

R/3 System ______________________________________________________________

__

CRM IBase Transaction Data 0CRM_SRV_IBASE_TRAN Number of Installed Base (Texts) 0CRM_IBNUMB_TXT Installed Base Category (Texts) 0CRM_IBTYPE_TXT Object Type of Component Usage(Texts) 0CRM_COMOTY_TXT Object Type for Reference Object in Subject Set (Texts) 0CRM_REFOTY_TXT Authorization Group for Installed Base (Texts) 0CRM_IBAUTG_TXT New Characteristic GUID of Document for Reference Object/Subject Set (0CRM_SRVGUI) This InfoObject is included in the following InfoProviders, enabling you to analyze data by reference object (product, individual object, or IBase component): ODS Objects CRM Service - Processes (Header Data) CRM Service - Processes (Item Data) CRM Service - Confirmations (Header Data) CRM Service - Confirmations (Item Data) 0CRM_PROH 0CRM_PROI 0CRM_CNFH 0CRM_CNFI

InfoCubes CRM Service - Processes and Confirmations (Header Data) 0CSRV_C01 CRM Service - Processes and Confirmations (Item Data) 0CRM_PRI Enhanced Queries In the following queries, the InfoObjects IBase Number (0CRM_SRVGUI__0CRM_IBNUMB) and Component Number (0CRM_SRVGUI__0CRM_COMPNR) are available as free characteristics, enabling you to break down data by installed base and installed base component: o o All queries with technical names beginning with 0CRM_PRI (queries based on the InfoCube CRM Service - Processes and Confirmations (Item Data) 0CRM_PRI) All queries with technical names beginning with 0CSRV_C01 (queries based on the InfoCube CRM Service - Processes and Confirmations (Header Data) 0CSRV_C01)

1.1.15 Changes to BW Content in CRM Marketing for the Personalization Variabl

Use The following objects have been changed for Release 3.1 in order to accomodate the variables 0P_USER and CRMOM (see the Personalization Variable for Roles in BW and Enterprise Portal release note): o Lead Management Channel Analysis (0MKTG_C01_Q0001) Efficiency Reporting (0MKTG_C01_Q0002) Original Qualification Level Reporting (0MKTG_C01_Q0003) History Reporting (0MKTG_C01_Q0004)

______________________________________________________________ __

12 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

-

Lost Leads (0MKTG_C01_Q0005)

1.1.16 Web Content für Kundenzufriedenheits- und -loyalitätsanalyse (erw.)

Use Mit SAP BW 3.1 Content steht Ihnen zur analytischen Applikation Kundenzufriedenheit- und -loyalität umfangreicherer Business Content zum Web Publishing zur Verfügung, zusammengefasst im Web Template 0TPL_COCKPIT_SATISFACTION.

1.1.17 Business Content for Service Analytics (Enhanced)

Use As of the 3.1 Content release of SAP BW, the following enhancements are implemented: User-Specific Data in Queries Variables now filter data in queries according to the user's role (Service Manager or Service Representative) so that users only see information relevant for their purposes. For further information on the new variables provided in the CRM Business Content and the Enterprise Portal, see Personalization Variables for Roles in BW and Enterprise Portal (CRM). The variables have been implemented in all queries except: Service Processes: Current Situation 0CRM_PROH_Q002 Overall Customer Status 0CRM_MRO2_Q0001 Active/Non-Active Customers 0CRM_MRO2_Q0002 Customer Order History 0CRM_HIS2_Q0001 The following queries only use the variables for the role Service Representative: My Service Contracts 0CSAL_C07_Q0001 Open Service Contracts 0CSAL_C07_Q0003 New Characteristic Service Profile (0CRM_SRVSWI) This new InfoObject is included in the following InfoProviders, enabling you to analyze data by service profiles in contracts: CRM Service - Contracts (Item Data) 0CSAL_C07 (InfoCube) CRM Service - Overall Controlling (Item Data)0CSRVMC02 (MultiProvider) CRM Service - Overall Controlling 0CSRVMC05 (MultiProvider) Characteristics Country (0CRM_SOLDTO__0COUNTRY) and Region (0CRM_SOLDTO__0REGION) These InfoObjects are included in the following MultiProviders, enabling you to analyze data by country and region: CRM Service - Overall Controlling (Header Data) 0CSRVMC01

______________________________________________________________ __

SAP AG 16.10.2002 13

R/3 System ______________________________________________________________

__

CRM Service - Overall Controlling (Item Data)0CSRVMC02 CRM Service - Contract, Process/Confirmation, Complaint, (Header) 0CSRVMC03 CRM Service - Processes and Confirmations with Complaints 0CSRVMC04 CRM Service - Overall Controlling 0CSRVMC05 Characteristic Sales Quantity (0CRM_SALQTY) This InfoObject is included in the following objects, enabling the sales quantity to be extracted from service process and confirmation items: CRM Service - Processes (Item Data) 0CRM_SERVICE_PROCESS_I (InfoSource) CRM Service - Confirmations (Item Data) 0CRM_SERVICE_CONFIRM_I (InfoSource) CRM Service - Processes (Item Data) 0CRM_PROI (ODS object) CRM Service - Confirmations (Item Data) 0CRM_CNFI (ODS object) CRM Service - Processes and Confirmations (Item Data) 0CRM_PRI (InfoCube)

1.1.18 Customer Analyses in Service Analytics (New)

Use As of the 3.1 Content release of SAP BW, additional information on customer numbers is available for reporting, and new queries are available for analyzing customer value. Customers and customer activities can be counted, based on an aggregation of service process, confirmation, and contract documents by customer. This enables the following key figures to be calculated, for example: o o o Number of active/non-active customers Number of customer activities Average order value per customer

Prior to this release, it was possible to break down transaction data by customer (sold-to-party), however, customer numbers could not be determined. New ODS objects CRM Service - Customer Order History 0CRM_HIS1 CRM Service - Customer's Most Recent Order 0CRM_MRO1 New InfoCubes The above ODS objects update the following new InfoCubes, respectively: CRM Service - Customer Order History 0CRM_HIS2 CRM Service - Customer's Most Recent Order 0CRM_MRO2 New Queries The following new queries have been designed specifically for customer analyses: Customer Order History 0CRM_HIS2_Q0001 Overall Customer Status 0CRM_MRO2_Q0001

______________________________________________________________ __

14 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

Active/Non-Active Customers

0CRM_MRO2_Q0002

1.1.19 Web Templates for Service Analytics in the Enterprise Portal (New)

Use New Web templates have been created for use in the Enterprise Portal by the roles Service Manager and Service Representative. The technical names of the new templates begin as follows: o o o o o o o o 0TPL_0CRM_PRI_Q010* 0TPL_0CSAL_C07_Q010* 0TPL_0CSAL_C09_Q010* 0TPL_0CSRV_C01_Q010* 0TPL_0CSRVMC02_Q010* 0TPL_0CSRVMC03_Q010* 0TPL_0CSRVMC04_Q010* 0TPL_0CSRVMC05_Q010*

Effects on System Administration To implement the new Web templates, you need to activate the following BW roles: o o o o o Note With this release, you should use the new Web templates instead of the previously valid templates, since the old templates will be deleted in the next BW release. For information about the correspondence between the old and new templates, see customer note 543753. Service Performance Analysis: Financial Perspective (SAP_BW_SERV_PERF_ANALYSIS_FI) Service Performance Analysis: Customer Perspective (SAP_BW_SERV_PERF_ANALYSIS_CU) Service Performance Analysis: Internal Process Perspective (SAP_BW_SERV_PERF_ANALYSIS_PR) Service Performance Analysis: Learning and Growth Perspective (SAP_BW_SERV_PERF_ANALYSIS_LG) CRM Service Technical Content (SAP_BW_SERV_TECH_CONTENT)

1.1.20 Separation of extractors for InfoSources 0FI_*_4

Use As of PlugIn 2002.2 and BW Content Release 3.10, selections according to company code and fiscal year/period are also possible for DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4. In this way, data requests in the delta init mode are possible. The selections for data requests in the delta init mode are

______________________________________________________________ __

SAP AG 16.10.2002 15

R/3 System ______________________________________________________________

__

administered separately per DataSource. If you require a consistent extraction, then the same init selection criteria regarding company code and fiscal year/period have to be selected. In addition, the strict coupling of DataSources has been removed. This means that now 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 can be loaded in a user-defined sequence. Additionally, DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 can now be used separately without 0FI_GL_4. The DataSources can then be used independently of eachother. However, as soon as DataSource 0FI_GL_4 is loaded, it is the leading DataSource regarding time limitations, for example maximum time (CPU date), until extraction takes place. For this reason, a data request should first take place in the Delta mode OFI_GL_4 when there is a transition from data requested in the delta init mode to pure delta mode. A consistent extraction of FI data takes place regarding time limits as a result of the coupling of DataSources. Functional consistency must be ensured via the init selection criteria. See also See SAP Note 551044 for more information on the subject of preinstallation, setup transition from the old to the new logic (if OFI_*_4 extractors have already been used), and so on.

1.1.21 Tax reporting for advance return for tax on sales

Use As of SAP BW 3.10 Content, data extraction for reporting sales tax is available via the delta method in the SAP Business Information Warehouse (SAP BW). Here, tax data is selected consistently with general ledger line items. The selected data is output in SAP BW. Within SAP BW, you can then create advance returns for tax on sales according to the requirements of the most important countries. In addition to this, you can also create a combined message for all EU member states. DataSource OFI_TX_4 with the extractor BWFID_GET_FITAX_ITEM ensures consistent delta dataset in the OLTP system. Extraction takes place primarily from tables BKPF and BSET. Data is also extracted from tables BSEG, T001, T007A, T007L, T007S, TRVOR, LFA1 and KNA1. The coupled delta extractions in the time stamp procedure provide a consistent transfer of data from the document header table and from the tax data table. The BKPF-CPUDT field makes precise determination of the delta dataset in the new document. New objects in SAP BW: o o o o DataSource: Extractor: ODS-Object for tax data: Queries: Advance return for tax on sales general (0FITX_O01_Q0001) Advance return for tax on sales Italy, Spain (0FITX_O01_Q0004) Combined message general (0FITX_O01_Q0002) 0FI_TAX_4 BWFI_GET_FITAX_ITEM 0FITX_O03

______________________________________________________________ __

16 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o

Key figures: Deductible part of tax amount (0DEDUCT) Gross amount currency of declaration (0TAX_GRO_RC) Non-deductible tax amount (0NONDED_AMT) Tax base amount for combined message (0TAXBASE_EC) Tax base amount in currency of declaration (0TAX_BAS_RC) Tax base amount in transaction currency (0TAX_BAS_TC) Tax amount in currency of declaration (0TAX_AMT_RC)

o

Characteristics: Description of tax group (0DESC_TAXGR) EU code (0EUCODE) General ledger account tax (0TX_ACCOUNT) Indicator for subcontraction (0IND_SUBCON) Indicator triangular business within the EU (0TRIANGULAR) Reporting country (2 digit) (0R_COUNTRY) Non-deductible (0NONDEDUCT) Tax type (0VATTAXTYPE) Tax group (0TAXGROUP) Tax reporting organization (0VAT_REPORG) Sales tax ID (0VAT_REG_NO)

1.1.22 Claims Management System (FS-CM): Extended Business Content

Use As from SAP BW 3.1 Content, the FS-CM business content also includes the healthcare line of insurance. In addition to information onproperty and casualty insurance, the business content now provides specific information on health insurance, such as o o o Activity management Diagnoses made Claim item groupings

The information is transferred to the SAP Business Information Warehouse (SAP BW) at single record level. You can aggregate the information there and adapt it according to your own requirements. The DataSources for transaction data are extracted in ODS objects at single record level. As the delta

______________________________________________________________ __

SAP AG 16.10.2002 17

R/3 System ______________________________________________________________

__

procedure is used with the AIMD method, this procedure is obligatory. The following ODS objects are new: Technical name 0ISCMDS10 0ISCMDS09 0ISCMDS11 The following info objects are new: Technical name 0IS_ACTNUM 0IS_ACTIVIT 0IS_DUETIME 0IS_XDONE 0IS_PRIORIT 0IS_SUBACTU 0IS_RESUBTI 0IS_ACTCOUN 0IS_WORKTIM 0IS_MESSAGE 0IS_XTASK 0IS_PATIENT 0IS_DIAGNO 0IS_PCATID 0IS_PDIAGID 0IS_SCATID 0IS_SDIAGID 0IS_ENDDATE 0IS_PDOCCAT 0IS_DIAGSRC 0IS_DIAGTYP 0IS_LOCALI 0IS_SEVCODE 0IS_MORPHO 0IS_EXCORIA 0IS_GUARANT 0IS_DEPARTM 0IS_INJURED 0IS_DIAGCOU 0IS_INCDCOU 0IS_DIAGGID Title Sequence number of the activity Claims Management activity Due time Task completed Claims Management priority of activity grouping Activity used to process the task Resubmission of an activity (grouping) Number of activities Processing time in days Claims Management activity or prompting message Flag: Is this a task? Damaged object in the form of an injured person Sequence diagnosis number within a case ID of a diagnosis catalog Primary diagnosis ID of a diagnosis catalog Secondary diagnosis End date Procurement document category Diagnosis source ID Diagnosis type Localization of a diagnosis Severity of a diagnosis Morphology Excoriation Diagnostic certainty Department Injured person Number of diagnoses Number of referral diagnoses Diagnosis group Title Claim activities Diagnoses made Claim item grouping

______________________________________________________________ __

18 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

0IS_DIAGCAT 0IS_TREATTY 0IS_XNEURO 0IS_XACCID 0IS_SEX 0IS_AGETO 0IS_AGEFROM 0IS_PROCMNT 0IS_PDOCTYP 0IS_ISSDATE 0IS_RECDATE 0IS_DATEFR home healthcare 0IS_DATETO home healthcare 0IS_ACQDATE 0IS_INVTYPE 0IS_XFINISH 0IS_PROCREF 0IS_INVOICR 0IS_HEALTH 0IS_APPRAIS 0IS_PRESCDO 0IS_ITEMCOU 0IS_DISCOUN 0IS_DUEDATE 0IS_DUETIME 0IS_RESUBDA 0IS_RESUBTI The following InfoSources are new: Technical name 0IS_IS_CM_ACTIVITY_01 0IS_IS_CM_DIAGNOSIS_01 0IS_IS_CM_PROCURE_01 0IS_ACTIVIT 0IS_TREATTY 0IS_SUBACTU 0IS_DIAGGID 0IS_PCATID

Diagnosis category Treatment type Indicates whether this is a neurological diagnosis Suspected accident Indicates whether the diagnosis is gender-specific Age up to which the diagnosis can be made Age from which the diagnosis can be made ID of a procurement document Procurement document type Date created Date received Start date of approval period for medical devices / End date of approval period for medical devices / Date entered Invoice type Complete / approved ID of a procurement document Invoicing party Service provider Appraiser Prescriber Number of claim items Discount on invoice amount Due date Due time Resubmission date Resubmission time

Title Claim activities Diagnoses made Claim item grouping Claims Management activity Treatment type Activity used to process the task Diagnosis group ID of a diagnosis catalog

______________________________________________________________ __

SAP AG 16.10.2002 19

R/3 System ______________________________________________________________

__

0IS_PDIAGID 0IS_PDOCCAT 0IS_DIAGTYP 0IS_DIAGCAT 0IS_LOCALI 0IS_SEVCODE 0IS_MORPHO 0IS_EXCORIA 0IS_GUARANT 0IS_DEPARTM 0IS_SEX 0IS_XNEURO 0IS_XACCID 0IS_XFINISH The following DataSources are new: Technical name 0ISCM_ACTIVITY_01 0ISCM_DIAGNOSIS_01 0ISCM_PROCURE_01 DataSource 0ISCM_ACTIVITY_ATTR 0ISCM_ACTIVITY_TEXT 0ISCM_TREATTYP_TEXT 0ISCM_DIAGGROUPID_TEXT 0ISCM_DIAGCAT_TEXT 0ISCM_SUBACTIVITYUSED_TEXT DataSource 0ISCM_DIAGNOSISCATALOGID_TEXT DataSource 0ISCM_DIAGNOSISCATALOG_ATTR 0ISCM_DIAGNOSISCATALOG_TEXT 0ISCM_PDOCCAT_TEXT DataSource 0ISCM_DIAGTYPE_TEXT 0ISCM_LOCALIZATION_TEXT DataSource 0ISCM_SEVCODE_TEXT DataSource 0ISCM_MORPHOLOGIE_TEXT 0ISCM_EXCORIATION_TEXT

Primary diagnosis catalog Procurement document category Diagnosis type Diagnosis category Localization of a diagnosis Severity of a diagnosis Morphology Excoriation Diagnostic certainty Department Flag: Gender-specific diagnosis Flag: Neurological diagnosis Flag: Suspected accident Complete / approved

Title Claims Management: Claim activities DataSource Claims Management: Diagnoses made DataSource Claims Management: Claim item grouping Claims Management: Activity DataSource Claims Management: Activity DataSource Claims Management: Treatment type DataSource Claims Management: Diagnosis group DataSource Claims Management: Diagnosis category DataSource Claims Management: Activity used to process task Claims Management: ID of a diagnosis catalog Claims Management: Diagnosis catalog DataSource Claims Management: Diagnosis catalog DataSource Claims Management: Procurement document category Claims Management: Diagnosis type DataSource Claims Management: Localization of diagnosis Claims Management: Severity of diagnosis Claims Management: Morphology DataSource Claims Management: Excoriation DataSource

______________________________________________________________ __

20 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

0ISCM_GUARANTEE_TEXT 0ISCM_DEPARTMENT_TEXT 0ISCM_SEX_TEXT Gender-specific diagnosis 0ISCM_XNEURO_TEXT diagnosis 0ISCM_XACCIDENT_TEXT accident The following extractors are new: Technical name ICL_BW_EXTRACT_ACTIVITY_GET ICL_BW_EXTRACT_DIAGNOSIS_GET ICL_BW_EXTRACT_PROCURE_GET DataSource

Claims Management: Diagnostic certainty DataSource Claims Management: Department DataSource Claims Management: DataSource flag: Claims Management: DataSource flag: Neurological Claims Management: DataSource flag: Suspected

Title Claims Management: DataSource for activities Claims Management: Diagnoses made DataSource Claims Management: Claim item grouping

1.1.23 SAP CRM: Intellectual Property Management (IPM)

Use The Intellectual Property Management (IPM) component has been connected to the SAP Business Information Warehouse (SAP BW) for the first time in the SAP BW 3.1 Content release. Since the IPM component itself will first be available with SAP CRM 4.0, you will not be able to make operational use of the scenarios supplied with the Business Content until the corresponding SAP CRM Release is available. This should correspond with the next SAP BW Release. Development Focus Standard CRM Content has been used where possible to connect IPM to SAP BW. One-order documents from CRM to which IPM-specific extensions have been added have been used here. The resulting license acquisition and license sales contracts mean that the sale and acquisition of Intellectual Properties (IPs) can be represented using CRM contracts. This provides the SAP BW connection with access to standard CRM extractors. The same applies to the IP product that uses the CRM product and the use of the Billing Engine (BE) by Billing Engine Applications (BEA) in IPM. Development in SAP BW 3.1 Content focuses on the connection of IP product master data and the license sales contract. Features of Intellectual Property Management The Intellectual Property Management (IPM) component covers the acquisition of rights to Intellectual Properties, (known as: IPs), management of IP rights owned that have been acquired or generated and IP sales. The IPM business process is represented by the following sub-areas in the CRM System: o o License acquisition contract IP master data (using the CRM product with the IPM-specific product type 04)

______________________________________________________________ __

SAP AG 16.10.2002 21

R/3 System ______________________________________________________________

__

o o

License sales contract in CRM Incoming revenues and license fees due are managed using separate Billing Engine Applications.

Acquisition of an Intellectual Property (IP) takes place using a license acquisition contract, which transfers the IP from the licensor to the licensee permanently or for a defined period. IPs acquired with their specific characteristics (defined within the license acquisition contract) represent the owned and represented rights. These rights are represented using the product master data. IP rights can be sold to a third party from the rights owned that are currently available. The license sales contract regulates the way in which a right is granted. This contract issues a right to an IP from the rights inventory to a subsequent licensee. A right to an IP (IPR) has specific characteristics that control its usage, granting and validity period in the context of these characteristics. Characteristics are defined using rights components, known as dimensions. Six dimensions that can de defined to meet user requirements are available for an IP. The validity period is controlled using three time intervals: o o o The period within which the licensee owns the rights (rights owned) The date to which the right has been released by the licensor for exploitation by the licensee (rights released) The date on which restrictions to the usage of the right apply (rights restricted, e.g. blocked periods).

Settlement data is distinguished as incoming royalties and outgoing royalties. o o Incoming royalties are revenues that are obtained by the sale of IPs. Outgoing royalties are paid to the licensor in return for usage of the rights to an IP.

Outgoing royalties can be created from incoming royalties. This occurs if the seller of an IP is not the original owner. In this scenario, the seller has a license contract for the IP, meaning that they have received license revenue for the exploitation of the right (such as the airing) and must pay a share of this revenue to the original licensor. A separate Billing Engine Application is available for the settlement of outgoing and incoming royalties. A preliminary level for the billing due list provides an additional highly detailed level of individual records on rights exploitation within the settlement periods. This can be used to make precise statements about individual exploitation of the rights to an IP within the existing rights characteristics for each business partner. Information from incoming royalties and other components that are involved in the exploitation of the rights (such as the SD order) is entered in this preliminary level before it is transferred to billing. Name Space, InfoAreas, ApplicationAreas and Application Components The 0IPM<...> name space is used for IPM-specific objects in BW. IPM objects are structured using the following areas: BW InfoAreas o 0CRM Customer Relationship Management 0IPM Intellectual Property Management

InfoObject Catalog o 0IPM_CHA01 IPM: Characteristics

______________________________________________________________ __

22 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

-

0IPM_KYF01 IPM: Key Figures

BW Application Areas o 0CRM Customer Relationship Management 0CRM_IPM Intellectual Property Management - 0CRM_IPM-IO Master Data for Intellectual Property Management

CRM Application Components o 0CRM Customer Relationship Management Roles The following roles are supplied: o o SAP_BW_IPM collective role for IPM, used to combine all single roles used by IPM as a package. SAP_BW_IPM_ANALYST single role, used to include reports for shipment 0CRM_IPM Intellectual Property Management - 0CRM_IPM-IO Master Data for Intellectual Property Management

Additional roles may require user-specific adjustments to be made. IPM Master Data IP Product A separate product type (Intellectual Property Product 04) to which IPM-specific product enhancements have been made is available in CRM for the IP. However, the standard CRM product can be used for the connection to SAP BW. No separate IPM attributes are currently managed in the SAP BW product master data (refer to the following section). However, to provide future flexibility for IPM-specific attributes, a separate InfoObject 0IPM_PROD Intellectual Property Product has been created for the IP. This characteristic contains all relevant information from the standard Product (0CRM_PROD) object and is easily adjustable to incorporate requirements that are specific to IPM without modifying the standard object. The 0IPM_PROD InfoObject has also been defined as a data target. This means that data in DataSources for the CRM product can be updated flexibly in BW using update rules. A restriction to product type 04 is made during the update. Special Features of IP Product Attributes - Rights Dimensions and Time Intervals The IP is represented by a rights cube with six dimensions that are used to classify each individual IP uniquely. A dimension can be a classifying dimension or a royalty dimension. Classifying dimensions can represent the market, geographical structures or language. An example of a royalty dimension is the price group. Royalty dimensions are only defined using the contract and are not therefore relevant to the product. Dimensions are used to distinguish rights characteristics precisely. Dimensions in conjunction with the product key (product GUID) make up a comprehensive composite key for a unique rights characteristic. This means that it is not possible to represent the structure of the actual IP using the master data alone, since the key containing the attributes would be 166 characters long and an InfoObject only allows a maximum of 60 characters. An ODS object is therefore used to represent IP characteristics from the IP master data:

______________________________________________________________ __

SAP AG 16.10.2002 23

R/3 System ______________________________________________________________

__

o

0IPM_DS05 IP Rights Owned

Since Customizing settings can be made to define dimensions to meet user requirements, dummy dimensions are supplied. This means that you can only use general placeholders (dimensions 1-6) for representation in SAP BW. It may be necessary to subsequently modify the names in BW manually depending on the individual settings that have been made. Time restrictions to a rights characteristic can be made using the validity interval of the rights owned, or the release intervals or release restrictions owned by the licensor. The ODS object for the IPM rights owned and represented is also used to represent time intervals. Data targets for the IP product master data and the IP rights owned are made available for evaluations of the product master data: o o Master data target 0IPM_PROD Intellectual Property Product ODS object 0IPM_DS05 IP Rights Owned

Interlinkages for the IP Product Interlinkages provide detailed information on the product and are therefore used to display all materials or additional IPs that have been recorded for an IP. Example: A specific television series is represented as a superordinate IP. The individual programs and series levels are represented as interlinkages. At present, no standard procedure has been defined for transferring interlinkages to SAP BW. Interlinkages in the IP product are represented using an ODS object for IPM. During the IP evaluation, the report-report interface can be used to access detailed information on the interlinkages with the object that has been assigned for the query of the IP master data. Available interlinkages: o o o o IPACC IP parts IPMAT IP Assigned materials IPUCO IP Underlying IP components IPPAC IPs in a package

ODS object used to represent interlinkages: o 0IPM_DS06 Intellectual Property Product (Interlinkages)

Business Partner Master Data The SAP business partner 0BPARTNER in conjunction with a referencing InfoObject is used to represent the IPM business partner. There are no current requirements for separate business partner attributes. CRM objects (0BPRELATION) are also used to represent business partner relationships. The SAP business partner is used to represent the following: o o The licensor as the seller of a license: InfoObject 0IPM_LICNSR The licensee as the purchaser of a license: InfoObject 0IPM_LICNSE

License Sales Contract The CRM sales contract is used during the sale of rights to an IP. Individual rights characteristics for the

______________________________________________________________ __

24 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

IP are sold in an item in the sales contract for a defined time interval. The IP rights owned (IP master data) are checked during this process. Rights can only be sold if they are available during the sales period. The validity period of a license sold in a license sales contract is controlled using the Valid from and Valid to time intervals. The system checks the validity period of the rights owned, the release periods and release restrictions, and the exclusivity of the available right. Data Targets, InfoCubes and ODS Object for the License Sales Contract An InfoCube and an ODS object are available for the IPM sales contract. The ODS object is mandatory as an input layer for the item data update in delta mode. Since CRM DataSources use the After Image/Delete (AIMD) delta procedure, the Before Image must be provided from the ODS object for the update. o o InfoCube: 0IPM_C01 License Sales Contract ODS Object: 0IPM_DS01 License Sales Contract (Item)

The InfoCube for IPM rights sales is used as a primary data target for evaluations. It provides all items in a license sales contract and their characteristics according to the existing rights dimensions and their validity period. The InfoCube for the sales contract is therefore a flexible tool for detailed division of the rights to an IP sold according to the relevant characteristic attributes and additional contract characteristics. InfoSources and DataSources for the License Sales Contract The following DataSource is used to prepare the data: o DataSource: 0IPM_SALES_CONTR_I License Sales Contract (Item)

This DataSource, like the CRM sales contract, provides all contract data and IPM-specific fields in the sales contract. InfoSources: 0IPM_SALES_CONTR_I License Sales Contract (Item)

1.1.24 New Features in SAP Media

Use Development of the SAP BW 3.1 Content focuses on the following functions in the industry-specific component Media Sales and Distribution (IS-M/SD). o Document data and detailed item data has been added to the order data. This allows you to perform analyses on the exact structure of an individual subscription, which was not previously possible to this degree of detail. Further improvements have been made to the address data and promotion data on an order. It is also now possible to perform evaluations on renewals.

o o

The following developments have been central to the industry-specific component Advertising Management (IS-M/AM): o Recording order complaints

______________________________________________________________ __

SAP AG 16.10.2002 25

R/3 System ______________________________________________________________

__

o o

Setting up data targets to improve evaluations of the sales agent data for an order In addition, a new and more comprehensive InfoCube is now available for evaluating the billing dataset.

As in each Release, all areas have been generally reworked in order to integrate technical improvements. The delivery now also contains InfoPackages, which contributes to a further reduction in the time required to go live with Business Content for media in implementation projects. New Roles The new composite role Media Company integrates all the single roles in Media Content, which simplifies the transfer of Business Content. o SAP_BW_MEDIA Composite role Media Company, together with the following single roles: SAP_BW_ADVERT_SALES_MAN SAP_BW_CIRCULATION_SALES_MAN 1SAP_BW_ADVERT_SALS_REP SAP_BW_ME_PLM_ANALYST

New InfoAreas and Application Components The InfoArea and the application components have been subdivided to improve the structure of Media Product Sales and Distribution, previously listed under Media Sales and Distribution: InfoArea o 0ME Media Company 0ME_MPS Media Product Sales and Distribution

Application Components o 0IS_ME Media Company 0IS_ME_MPS Media Product Sales and Distribution - 0IS_ME_MPS-IO Media Product Sales and Distribution Master Data

Improvements in Media Sales and Distribution (IS-M/SD) New InfoCubes New InfoCubes for use in analyzing order documents: 0MEMSDC07 Subscription Order Items 0MEMSDC08 Subscription Addresses 0MEMSDC09 Subscription Promotion Data 0MEMSDC10 Subscription Payment Data

You can use these InfoCubes, for example, to find answers to the following questions: o o o How many terminations have already been received for the next half year? Which promotional gift leads to how many new subscriptions? How many subscriptions that are still live were taken out in a period in the past?

______________________________________________________________ __

26 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o

How many new subscriptions have already been received for a future period?

Special Features of Time Updating in the InfoCubes Time updating has been initialized for all new InfoCubes in Media Sales and Distribution, since their validity period depends on the interval for the order item in question. The valid interval for an item is recorded separately in the master data and made available in the InfoCubes by means of navigation attributes. The validity period of the subscription is specified in the master data on the external item and the validity period for the item is specified in the master data on the internal item. Special Features of Characteristics of the Order Item in the InfoCubes All the characteristics of the order item are made available as navigation attributes. The link between the characteristic evaluation and the validity periods reflects an exact image of all the items in an order and their changes for a current period, a period in the past and a period in the future. o InfoCube 0MEMSDC07 Subscription Order Items The InfoCube Subscription Order Items is used to perform a detailed evaluation of the order items in a subscription. The InfoCube has been kept very simple and only gives access to the document and the internal and external item number. All other characteristics of the item are provided by the navigation attributes of the order item, for example the publication, the edition and the item type. See also: Special Features of Characteristics of the Order Item in the InfoCubes Special Features of Time Updating in the InfoCubes InfoCube 0MEMSDC08 Subscription Addresses The InfoCube Subscription Addresses is used to perform an evaluation of the address data on a subscription. Addresses recorded for a subscription item can differ from those recorded in the business partner master data. Please note that a business partners address must always be analyzed together with the business partner role, since the address data for the payer, ship-to party and bill-to party are always recorded for each subscription. See also: Special Features of Time Updating in the InfoCubes InfoCube 0MEMSDC09 Subscription Promotion Data You can use the InfoCube Subscription Promotion Data to evaluate promotional data on a subscription, so as to reach conclusions on the effectiveness of promotional activities. In addition to the order data, data on the campaign framework and sales agent is provided. See also: Special Features of Time Updating in the InfoCubes InfoCube 0MEMSDC10 Subscription Payment Data The InfoCube Subscription Payment Data provides information that is used to evaluate renewals. You can use the InfoCube to evaluate information on the end of the period covered by the payment amount and the number of deliveries and use the results to control monitoring of order renewal. See also: Special Features of Time Updating in the InfoCubes

o

o

o

New InfoSources and DataSources in Media Sales and Distribution New InfoSources for retrieving order document data: 0ME_ISM_SD_ORD_ADDR M/SD Subscription Addresses

______________________________________________________________ __

SAP AG 16.10.2002 27

R/3 System ______________________________________________________________

__

-

0ME_ISM_SD_ORD_ITEM M/SD Subscription Order Items 0ME_ISM_SD_ORD_PROM M/SD Subscription Promotion Data 0ME_ISM_SD_ORD_CYCL M/SD Subscription Payment Data

New DataSources for extracting order document data: 0ME_ISM_SD_ORD_ADDR IS-M/SD: Address Data for Subscription Order 0ME_ISM_SD_ORD_ITEM IS-M/SD: Subscription Order Data 0ME_ISM_SD_ORD_PROM IS-M/SD: Subscription Promotion Data 0ME_ISM_SD_ORD_ACC IS-M/SD: Liability Account 0ME_ISM_SD_ORD_REM IS-M/SD: Renewal Payment

The DataSources IS-M/SD: Liability Account and IS-M/SD: Renewal Account are both mapped on the InfoSource M/SD Subscription Payment Data. DataSources for master data attributes of internal and external items: Please note that the attributes must also be updated, in particular the validity periods of the external and internal order items. Data is entered in the internal item using the DataSource IS-M/SD: Subscription Order Data. A separate DataSource is used to extract the external item. 0ME_ISM_SD_ORD_ITEX IS-M/SD: External Subscription Order Item

Changes to Existing InfoObjects in Media Sales and Distribution The InfoObject 0ME_ISSUE Issue is modified according to the domain definition in IS-M/SD. The field length is extended from 8 to 10 characters and conversion type alpha is activated. If you already use the Content for media companies and plan to adopt new objects for M/SD from the Content, it is advisable to check whether these objects contain the InfoObject 0ME_ISSUE Issue. All objects (InfoCubes and master data objects) that already contain data are critical for converting the tables. Since the conversion type is also changed during implementation, you must delete all the data in the relevant InfoCubes and master data tables in order to avoid errors during transfer from the Business Content. If you do not want to use alpha conversion, you can retain the data in the data objects and activate them manually in postediting, removing alpha conversion from the InfoObject before you do so. Improvements in Advertising Management (M/AM) New InfoCubes, MultiCubes and ODS Objects in Advertising Management New data targets for evaluating complaints in Advertising Management: 0MEMAMC13 Complaints (Billing Datasets Only) (InfoCube) 0MEMAMC14 Complaints (InfoCube) 0MEMAMMC4 Complaints and Billing Dataset (MultiCube) 0MEMAMO08 Billing Dataset (ODS object)

New InfoCube for evaluating the billing dataset: 0MEMAMC15 Billing Dataset (InfoCube)

______________________________________________________________ __

28 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

New InfoCube for sales agent assignment to the order data: 0MEMAMC16 Sales Agent (Order)

Modified InfoCubes The 0MEMAMC02 Billing Dataset (Ads Only) InfoCube has been changed. The update is now performed from the new Billing Dataset ODS object. This means that data can be prepared centrally from a single location. Consolidated data is then available to any number of data targets. Deletion of Data Targets The Contact Partner Relationship (IS-M < 4.63) 0MEMAMC09 and Contact Person Relationship 0MEMAMC10 InfoCubes have been deleted from the existing Business Content. Both InfoCubes have been flagged for deletion as of Release 30B. o InfoCube 0MEMAMC13 Complaints (Billing Dataset Only) The Complaints (Billing Dataset Only) InfoCube only contains complaints that have been entered at billing dataset level. Information from the order billing dataset has been added to the complaint data. This means that queries that relate to the order for which the complaint has been made, such as the initial booking unit or color scheme can be dealt with in addition to those that relate exclusively to the complaint data. Note: Since a complaint in the Advertising Management component can be entered at any order level (header, item, schedule line, billing dataset...), it is only feasible to access the data for which a complaint has been made at the lowest level (business level of the billing dataset) in this InfoCube. Any complaints that are made at other document levels are disregarded here. To enable complaints to be evaluated meaningfully in conjunction with the billing dataset, the leading date in the time dimension is the service creation date for the order. o InfoCube 0MEMAMC14 Complaints The Complaints InfoCube is used to evaluate complaints from all document levels in the order. It is only possible to evaluate information that is entirely complaint-related, such as complaint reasons, business partners who have made the complaints or the total number of complaints here. The complaint date is used as the leading date in this time dimension. MultiCube 0MEMAMMC4 Complaints and Billing Dataset The Complaints and Billing Dataset MultiCube in conjunction with the Complaints (Billing Dataset Only) and Billing Dataset InfoCubes can be used to obtain an overall view of the order and its complaints. This enables complaint ratios to be created: The total number of orders is placed in relationship with the number of complaints. Value-based complaint rations that take the corresponding item categories (credit memos) into account can be created here. The service creation date is the leading date in this time dimension. InfoCube 0MEMAMC15 Billing Dataset The Billing Dataset InfoCube is intended to completely replace Billing Dataset (Ads Only) (0MEMAMC02) InfoCube, since it was only possible to evaluate ad orders in this InfoCube. The new InfoCube covers this shortfall. All item types in an ad order are now available. When evaluating quantity information, you must ensure that you restrict your selection to a specific item type, since mixed units (such as column mm, pieces) can occur. o OD Object 0MEMAMO08 Billing Dataset

o

o

______________________________________________________________ __

SAP AG 16.10.2002 29

R/3 System ______________________________________________________________

__

The new Billing Dataset ODS object is used as an input layer for data from the billing dataset. The objective here is to prepare extracted documents uniquely (such as leading sign reversal in cancelled documents) and then update this information in the associated data targets. o InfoCube 0MEMAMC16 Sales Agent (Order) The Sales Agent (Order) InfoCube is used to evaluate sales agent assignments to the billing dataset. All orders and the sales agents involved in these orders (or vice versa) can be evaluated. This means that the data target for the existing M/AM Order: Sales Agent InfoSource is also available.

New InfoSources and DataSources in Advertising Management New InfoSource for complaints: 0ME_ISM_AM_COMPL_1 M/AM Complaints

New DataSource for complaints: 0ME_ISM_AM_COMPL_1 IS-M/AM: Complaints

1.1.25 unbilled Revenue Reporting with SAP BW and SEM-BPS

Use You can now use a new InfoCube to map unbilled revenue reporting. This InfoCude is filled with current data from the sales statistics, as well as extrapolated values from IS-U/CCS. You can compare the real and extrapolated data with the energy feeding volume in SEM-BPS (Strategic Enterprise Management Business Planning and Simulation) and then adjust the data if required. The real and extrapolated data are saved in difference versions and are available for reporting purposes over long periods of time. You can use preconfigured queries to determine the unbilled amount or corrected value of the previous year for further clearing in FI. In addition, you can use a new MultiCube that enables you to compare the unbilled revenue reporting data and the real data from the sales statistics. This especially relevant if you want to forecast the revenue reporting and check the forecast data during the course of the year. You can use unbilled revenue reporting in SAP BW as a replacement for accrual calculation in CO-PA. (profitability analysis). The advantages of unbilled revenue reporting are optimal modeling of data in SAP BW, better system performance during modification and analysis of the data and a variety of archiving options. In addition, process chains are provided that support you during updates and extractions in the InfoCubes, You are still free to make you of unbilled revenue reporting in CO-PA. Effects on Existing Data Note that the unbilled revenue reporting InfoCube is based on an existing modeling method for the sales statistics. If you have changed the Sales Statistics InfoCube in you system then you need to make a manual comparison and manual adjustments. Effects on System Administration If you activate the unbilled revenue reporting InfoCube, we recommend that you also activate the

______________________________________________________________ __

30 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

corresponding process chains and queries. You may also have to modify the Sales Statistics InfoCube and generate its dependent objects. Effects on Customizing Make sure you read the update rules provided. We also recommend you read the Unbilled Revenue Reporting cookbook before beginning. See also For more information, see the documentation on the SAP BW Content for Release 310 and the Unbilled Revenue Reporting cookbook.

1.1.26 Business Content for Personnel Cost Planning and Simulation (New)

Use New Business Content is now available in the SAP Business Information Warehouse (SAP BW) for Personnel Cost Planning and Simulation developed for SAP R/3 Enterprise HR Extension 1.10. Two new InfoCubes and one MultiProvider are available. o Personnel Cost Plans (0PACP_C01) This InfoCube provides personnel cost data in relation to a cost unit (organizational unit or account assignment object) with the relevant account assignment. Planned Personnel Costs Per Cost Object (0PACP_C02) This InfoCube contains cost data on cost objects Employee, Position, Job and Organizational Unit, irrespective of their organizational assignment for different valuation scenarios. Plan/Actual Comparison of Personnel Costs (0PAC_MC01) This MultiProvider is composed of InfoCubes Personnel Cost Plans (0PACP_C01) and Auditing Information on Postings Relevant to Accounting (0PY_PPC01).

o

o

The role Personnel Cost Planner is used in the existing Personnel Cost Planning application where it contains additional reports for plan analyses, cost objects, and plan-actual comparisons. Note When extracting data from the R/3 system into the BW system, only active plan versions are taken into account. DataSources for supplying Business Content to Personnel Cost Planning and Simulation are available as of SAP R/3 Enterprise Extension 2.0. See also For more information, see the documentation on SAP BW 3.1 Content under Business Content -> Human Resources -> Personnel Cost Planning and Simulation.

______________________________________________________________ __

SAP AG 16.10.2002 31

R/3 System ______________________________________________________________

__

1.1.27 Organizational Management (PA-OS): Enhanced Business Content

Use As of SAP BW 3.1 Content, new fields for transferring data from Organizational Management (PA-OS) to the SAP Business Information Warehouse (BW) are available for the DataSource 0ORGUNIT_ATTR (Organizational Unit). Enhanced DataSource DataSource 0ORGUNIT_ATTR has the following additional fields: o o o o o See also For more information, see the documentation on SAP BW 3.1 Content under Business Content -> Human Resources -> Organizational Management -> DataSources -> Organizational Unit (Attributes). BUKRS - Company Code GSBER - Business Area WERKS - Plant PERSA - Personnel Area BTRTL - Personnel Subarea

1.1.28 Personnel Administration (PA-PA): Enhanced Business Content

Use As of SAP BW 3.1 Content, enhanced Business Content is available in the SAP Business Information Warehouse (BW) for the Personnel Administration components (PA-PA). Enhanced DataSources The following DataSources were enhanced by the field SNAME, which contains the sortable name of the employee or person: o o 0EMPLOYEE_ATTR (Employee) 0PERSON_ATTR (Person)

New DataSources The following DataSources were newly created to extract data from the Education infotype (0022): o o o o o 0EMPLOYEE_0022_ATTR (Employee - Education) This DataSource delivers attributes for the InfoSource 0EMPLOYEE. 0BRNCHSTDY_TEXT (Branch of Study) 0CERTIFIC_TEXT (Certificate) 0EDUCATION_TEXT (Education) 0EDUC_EST_TEXT (Educational Establishment)

______________________________________________________________ __

32 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

These new text DataSources deliver texts for the new DataSource 0EMPLOYEE_0022_ATTR. New InfoSources Accordingly, the following new InfoSources were created for BW: o o o o o 0EMPLOYEE_EDUCATION (Employee - Education) 0BRNCHSTDY (Branch of Study) 0CERTIFIC (Certificate) 0EDUCATION (Education) 0EDUC_EST (Educational Establishment)

New ODS Object 0PA_DS04 (Employee - Education) See also For more information, see the documentation on SAP BW 3.1 Content under Business Content -> Human Resources -> Personnel Administration.

1.1.29 Business Content for Positon Budgeting and Control (new)

Use As of SAP BW 3.1 Content, you can transfer commitment documents from Position Budgeting and Control to the SAP Business Information Warehouse (SAP BW). This process is for funds precommitments or funds commitment documents that were created during a run for automatic commitment creation for personnel and positions. New Data Sources in SAP R/3 o Commitment line items of Position Budgeting and Control (0PSM_PBC_01)

New Objects in SAP BW o Info Cube commitment documents Position Budgeting and Control (0PSM_C40) This cube is used in the area Position Budgeting and Control to make available information from commitment creation per person/position or account assignment. It contains the funds precommitments and commitments created during an automatic commitment creation run. Feature: Earmarked Fund Category (0PSM_ENCT) This feature contains the information on whether the document created is a funds precommitment or a funds commitment. Feature: Dependent Earmarked Fund Category (0PSM_ENCT_R) This feature is derived from the feature earmarked fund category and contains information on the commitment document category for the dependent object. Feature: Item Number (0PSM_POSNR) This feature provides information on the item in the commitment document. Feature: Dependent Item Number (0PSM_PSNR_R)

o

o

o o

______________________________________________________________ __

SAP AG 16.10.2002 33

R/3 System ______________________________________________________________

__

This feature is derived from the feature item number and provides information on the item of the dependent object in the dependent document. o Feature: Dependent Employee (0PSM_EMPL_R) This feature is derived from the feature employee (0EMPLOYEE) and contains the ID of the dependent employee. Feature: Dependent Position (0PSM_HRPO_R) This feature is derived from the characteristic position (0HRPOSITION) and contains the ID of the dependent position. ODS Object Commitment Document Position Budgeting and Control (0PSM_O40) Query documents of Position Budgeting and Control (Funds Management view) (0PSM_C40_Q0001) Display of commitment document of Position Budgeting and Control with the Funds Management account assignment. You can display the financing of the dependent object or the commitment/actual in Former Budgeting or in Budget Control System (BCS) using Goto Query documents of Position Budgeting and Control (FI View) (0PSM_C40_Q0003) Commitment document display of Position Budgeting and Control with the FI account assignment. It is also possible to display the financing of the dependent object or the commitment/actual in Former Budgeting or in Budget Control System using Goto. Query documents of Position Budgeting and Control (CO view) (0PSM_C40_Q0004) Commitment document display of Position Budgeting and Control with the CO account assignment. It is also possible to display the financing of the dependent object or the commitment/actual in Former Budgeting or in Budget Control System using Goto Display query financing of dependent object (0PSM_C40_Q0002) This query should only be used for navigation and displays the dependent object.

o

o o

o

o

o

1.1.30 Profit Center Analytics Retail

Use Business Content for "Profit Center Analytics Retail" is a solution which allows retail firms to calculate how profitable stores and their individual departments are. The subject of analyis is basically the store which is defined as both a cost center and a profit center in Business Content for "Profit Center Analytics Retail". This allows you, for example, to calculate the profitability of a store, or to compare monthly store statistics. You also have access to statistical key figures (for example, sales per employee). You can use hierarchies to carry out analyses beyond the store level (for example, at regional or distribution chain level). Business Content for "Profit Center Analytics Retail" provides you with the following: o o o Reports calculating short-term success: Reporting of actual data and plan data from a store InfoCubes which form the basis for Financial Store Planning functionalities SAP R/3 FI / CO store data is collected in the Retail Ledger (SAP R/3).

______________________________________________________________ __

34 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

1.1.31 Content of SAP Project System (Enhanced)

Use From SAP BW 3.1 Content on there are two additional Web reports for multi-project analysis in the content of the SAP Project System. With these reports you can create evaluations using multiple projects and get an overview of the current costs and dates. o The report 0TPL_PS_C05_Q0001 (Overview Report - Projects) gives you an an overview of the current cost situation in multiple projects. Furthermore, basic dates, planned and actual work are displayed. The report 0TPL_PS_C04_Q0010 (Project Overview - Chronological Cost Development) gives you an overview of the cost development for multiple projects. The costs are broken down by cost element.

o

1.1.32

Use SAP BW 3.1 Content includes enhanced options for transferring information from Payroll to the SAP Business Information Warehouse (SAP BW). This information consists of data that is created when payroll results are evaluated to facilitate posting to Accounting. You can always transfer this data as of SAP BW 3.0B. This release note provides an overview of the objects that have been added to SAP BW 3.1 Content and are supported as of SAP R/3 Plug-In 2002.2. New DataSources in SAP R/3 Plug-In 2002.2 o o o o Symbolic Account (0SYMB_ACCNT_TEXT) Symbolic Account (0SYMB_ACCNT_ATTR) Type of Symbolic Account (0PY_KTTYP_TEXT) Employee Grouping (0EEGR_ACCNT_TEXT)

New and changed objects in SAP BW o InfoCube Index Information on Postings Relevant to Cost Accounting (0PY_PPC01) This InfoCube is used in Personnel Cost Planning and Simulation to make posting information that is relevant to cost accounting available on the level of personnel numbers. It contains actual data, which you can compare with the appropriate planning data. Characteristic Symbolic Account: CO/FM-Relevant (0PY_COINFO) This characteristic belongs to a symbolic account's master data and contains information on which account assignment types of SAP R/3 symbolic accounts are flagged as relevant to cost accounting. In the standard system, these account assignment types are for postings to expense accounts (C, CN, and R). The system uses this characteristic to determine a line item's relevance to cost accounting. Characteristic Type of Symbolic Account (0PY_KTTYP)

o

o

______________________________________________________________ __

SAP AG 16.10.2002 35

R/3 System ______________________________________________________________

__

This characteristic contains information on the transaction (such as HRC or HRF) which, from a business perspective, characterizes the posting. o Characteristic Account Determination: Dependent on Employee Grouping (0EEGR_RELV) This characteristic belongs to a symbolic account's master data and contains information on whether an SAP R/3 posting was performed dependent on the feature Employee Grouping for Account Determination (PPMOD). Characteristic Employee Grouping for Account Determination (0EEGR_ACCNT) This characteristic has been supplemented by the texts that you define in SAP R/3 for the return values of the feature Employee Grouping for Account Determination (PPMOD). ODS object Posting Documents and Posting Index Combined (0PY_PP_C3) The key fields and characteristics have been adjusted and the update rules have been corrected. Query Auditing Information and Payroll Data (Per In-Period) (0PY_PP_C1_Q001) The symbolic account has been included as a free characteristic.

o

o o

Further notes Content objects whose titles include the term "posting index" have been renamed for SAP BW 3.1 Content. The term "posting index" has been replaced by the term "auditing information" to ensure that terminology in SAP R/3 and SAP BW is consistent. In SAP R/3, the term "posting index" is used to mean the contents of tables PPOIX and PPOPX. When posting documents are created for posting data to Accounting, SAP R/3 uses these tables to store detailed, employee-specific information that is not transferred to Accounting but must nevertheless be available for auditing purposes. This is auditing information from the user's perspective. A support package of SAP R/3 Plug-In 2002.2 changes the name of the DataSource whose technical name is 0HR_PY_PP_1 from "Posting Index" to "Auditing Information". See also For more information, access the documentation on SAP BW 3.1 Content and choose Human Resources -> Payroll.

1.1.33 Extractors and Business Content SCM Event Management

Use The following list provides an overview of the new extractors as well as the new Business Content for SCM Event Management in the SAP Business Information Warehouse (SAP BW) as of SAP BW 3.1 Content. Extractors o o o /SAPTRX/BWTFSEH: Extraction Structure for Event Handler Header Data /SAPTRX/BWTFSEE: Extraction Structure for Events (Planned and Unplanned) /SAPTRX/BWTFSEG: Extraction Structure for Groups of Expected Events

______________________________________________________________ __

36 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

Business Content o DataSources o 0SCEM_1: SCEM - Event Handler Header Data 0SCEM_2: SCEM - Events (Expected and Unplanned) 0SCEM_3: SCEM - Groups of Expected Events

InfoSources 0SCEM_1: SCEM - Event Handler Header Data 0SCEM_2: SCEM - Events (Expected and Unplanned) 0SCEM_3: SCEM - Groups of Expected Events

o

InfoCube 0EM_C01: SCEM - Notification- and Execution Processes

o

ODS Objects 0EM_DS01: SCEM - ODS Event Handler Header Data 0EM_DS02: SCEM - ODS Events (Expected and Unplanned) 0EM_DS03: SCEM - ODS Groups of Expected Events

o

Queries 0EM_C01_Q0001: Execute Events CARRARRIV and CUSTARRIV 0EM_C01_Q0002: Execute Event PLANTDEPT 0EM_C01_Q0003: Reporting Events CUSTARRIV and CARRARRIV 0EM_C01_Q0004: Reporting Event PLANTDEPT 0EM_C01_Q0005: Execute Shipment

o

Characteristics (Catalog 0SCEM_CHA01) 0CARRIER: Carrier 0DEL_PRIO: Delivery Priority 0UNLD_POINT: Unloading Point 0REASON_CD: Code ID for Status Reason 0EVENT_CD: Internal Event Code 0EVENT_GRP: Group of Internal Event Codes 0EXEV_GRP: Group of Expected Events (BW) 0EH_GUID: UUID in X-Form (Binary) 0EH_TYPE: Event Handler Type 0EM_BW_PROF: SCEM: BW Profile 0INFOTYPE: SCEM: BW Infotype

______________________________________________________________ __

SAP AG 16.10.2002 37

R/3 System ______________________________________________________________

__

o

0SRVPROV_CD: Service Provider Code ID 0SRVPROV_CS: Service Provider Code Set 0LOC_CD1: Location Code ID, Part 1 0LOC_CD2: Location Code ID, Part 2 0LOC_CS: Location Code Set 0AO_ID: Application Object 0AO_TYPE: Application Object Type 0APPSYS: Name of Application System 0TRKID_CS: Code Set for Tracking ID 0TRKID_CD: Tracking ID 0EH_ACT_DAT: Event Handler Activation Date

Key Figures (Catalog 0SCEM_KYF01) 0NR_CARRARV: Number of Arrivals Carrier 0NR_CUSTARV: Number of Arrivals at Customer 0NR_PLANTDP: Number of Departures from Plant 0EVT_DELAY: Event Delay (Duration) 0NR_EVT_DEL: Number of Delayed Events 0EVT_LT_12: Number of Events Delayed 0 - 12 Hrs 0EVT_12_24: Number of Events Delayed 12 - 24 Hrs 0EVT_24_36: Number of Events Delayed 24 - 36 Hrs 0EVT_36_48: Number of Events Delayed 36 - 48 Hrs 0EVT_48_96: Number of Events Delayed 48 - 96 Hrs 0EVT_MT_96: Number of Events Delayed > 96 Hrs 0RC_CTR_ACC: Number of Status Reasons 'Accident' 0RC_CTR_WTH: Number of Status Reasons 'Weather' 0RC_CTR_MBR: Number of Status Reasons 'Mechanical' 0RC_CTR_CRL: Number of Status Reasons 'Carrier Delayed' 0RC_CTR_GTO: Number of Status Reasons 'Door Occupied' 0RC_CTR_PKL: Number of Status Reasons 'Picking Delayed' 0RC_CTR_NO: Number Without Status Reason 0MSG_DELAY: Event Message Delay (Duration) 0NR_MSG_DEL: Number of Delayed Event Messages 0MSG_LT_12: Number of Event Messages Delayed 0 - 12 Hrs

______________________________________________________________ __

38 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o

0MSG_12_24: Number of Event Messages Delayed 12 - 24 Hrs 0MSG_24_36: Number of Event Messages Delayed 24 - 36 Hrs 0MSG_36_48: Number of Event Messages Delayed 36 - 48 Hrs 0MSG_48_96: Number of Event Messages Delayed 48 - 96 Hrs 0MSG_MT_96: Number of Event Messages Delayed > 96 Hrs 0EVT_ACTDUR: Actual Duration Shipment 0EVT_PLNDUR: Planned Duration Shipment 0EVT_DURLTE: Delayed Duration Shipment 0NR_DUR_DEL: Number of Delayed Shipments 0EVDR_LT_12: Number of Shipments Delayed 0 - 12 Hrs 0EVDR_12_24: Number of Shipments Delayed 12 - 24 Hrs 0EVDR_24_36: Number of Shipments Delayed 24 - 36 Hrs 0EVDR_36_48: Number of Shipments Delayed 36 - 48 Hrs 0EVDR_48_96: Number of Shipments Delayed 48 - 96 Hrs 0EVDR_MT_96: Number of Shipments Delayed > 96 Hrs

Calculated Key Figures 0EM_C01_CK007: Average Event Delay (Time) 0EM_C01_CK008: Average Event Message Delay (Time) 0EM_C01_CK009: Average Shipment Duration Delay (Time)

See also For more information, see the Knowledge Warehouse for SAP BW 3.1 Content.

1.1.34 Extractors and Business Content SCM Inventory Management

Use The SAP Business Information Warehouse (SAP BW) contains the following changes in the area SCM Performance Management: Inventory Management as of SAP BW 3.1 Content: A new DataSource 2LIS_03_BX has been delivered which, along with the previous functions, allows you to calculate the valuated customer order stock and the valuated project stock in BW. Until now, the stock was extracted via the LIS DataSource 2LIS_40_S278, but valuated customer order stock and valuated project stock could not be determined separately on a value basis. The DataSource 2LIS_03_BX replaces the function of the DataSource 2LIS_40_S278 and enhances it with the function described above. However, because the DataSource 2LIS_40_S278 is still required in its entirety by mySAP Retail, it is still being delivered for the time being. This DataSource will no longer be delivered in a future Release

______________________________________________________________ __

SAP AG 16.10.2002 39

R/3 System ______________________________________________________________

__

and will then no longer be maintained. In BW, the DataSource 2LIS_03_BX can only be implemented as of Release BW 3.10 and higher. This DataSource cannot be implemented in the Content for mySAP Retail. The InfoCube 0IC_C03 can therefore be filled via the DataSource 2LIS_40_S278 or via the new DataSource 2LIS_03_BX; parallel usage is not possible. If you require valuated customer order stock or valuated project stock for your reports, we recommend that you activate the update rules for the InfoSource 2LIS_03_BX and set up the stock data using this source. New Queries The following new queries are delivered with the new DataSource: o o o o See also For more information, see the Knowledge Warehouse for SAP BW 3.1 Content. 0IC_C03_Q0013: Stock Overview 0IC_C03_Q0014: Quantity of Valuated Project Stock 0IC_C03_Q0015: Valuated Stock 0IC_C03_Q0016: Quantity of Valuated Customer Order Stock

1.1.35 Changes in the area of Supply Chain Performance Management

Use The business content for Release 3.1 has been enhanced in the following areas: o Information regarding backorders In the area of delivery services for the applications sales, procurment and production, it is now possible to evaluate information on backorders in BW. The new InfoCube Request Schedule Lines in Backorder Processing (0PUR_C10) is available for information on quantities and values in backlog, and on period patterns and classifications. The new ODS object Delivery Schedule Lines in Purchase Order Processing(0PUR_DS03), and the new Query Request Schedule Lines in Backorder Processing (0PUR_C10_Q0001) are also available. Process chains In Release BW 3.1 Content, process chains were delivered in the areas of Sales (SD), Procurement (MM) and Production (PP). Both process chains for each application area (initial and delta) make it possible to fill and activate all ODS and InfoCube objects according to a specific sequence as a result of their unique start. The following process chains are included: SD Initial: 0SD_DLV_INIT_P01 SD Delta: 0SD_DLV_DELTA_P02 MM Initial: 0MMPUR_DLV_INIT_P01 MM Delta: 0MMPUR_DLV_DELTA_P02

o

______________________________________________________________ __

40 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o

PP Initial: 0PP_DELTA_P01 PP Delta: 0PP_INIT_P01

Production In the area of production it will be possible to analyze value information as of Release 3.10. This means, for example, key figures Value of Product Quantities or Scrap Value can be displayed. These key figures will be calculated in quantities (in Logistics) multiplied by the standard material price. For this reason, such key figures are an estimated value, rather than an exact amount. These key figures are not relevant for controllers, but for logistics managers, or planners.

1.1.36

&Short text&

Risk Management (SEM-CPM-RMS): New Business Content

Use The role "SEM Risk Controller in BW" is provided with this release. As a SEM Risk Controller in SAP Business Information Warehouse (SAP BW), you create reports for Risk Management. You also use the two reports named below. These reports contain basic data about risk effects and the target values for measures contained in the target systems for Risk Management. These reports help you to make informed decisions about which risk activities to take. The scope of supply also includes the characteristics, measures, InfoSources, DataSources and InfoCubes required for the reports. The data required is extracted from SEM Strategy Management and Performance Measurement (SEM-CPM). New Role o SAP_BW_SEM_RISK_CONTROLLER (SEM Risk Controller in BW)

New Queries o o 0SEM_C07_Q001 (Aggregated Effects of Risks on a Measure) 0SEM_C07_Q002 (Effects of a Risk on a Measure in Target Systems)

New InfoCube o 0SEM_C07 (Risk Management)

New DataSources o o o o o 0SEM_SC_TEXT (Scorecard: Text) 0SEM_SC1_HIER (Scorecard: Hierarchy (IDOC)) 0SEM_ACTIV_ATTR (Risk Activity: Master Data) 0SEM_ACTIV_TEXT (Risk Activity: Text) 0SEM_INIT_TEXT (Initiative: Master)

______________________________________________________________ __

SAP AG 16.10.2002 41

R/3 System ______________________________________________________________

__

o o o o o o o o o o

0SEM_VF_TEXT (Value Field: Text) 0SEM_OBJ_TEXT (Objective: Master) 0SEM_RISKID_TEXT (Risk ID: Text) 0SEM_STRAT_TEXT (Strategy: Master) 0SEM_PERS_TEXT (Perspective: Master) 0SEM_ACTFLG_TEXT (Use of Risk Activities) 0SEM_MEAS_TEXT (Measure: Master) 0SEM_C07_2_TRAN (Measure Status and Risk Status) 0SEM_C07_TRAN (Risk Values) 0SEM_C07_1_TRAN (Measure Targets)

New InfoSources o o o o Risk Management Master Data 0SEM_RISK_1 (Risk Values) 0SEM_RISK_2 (Target Values for Measures) 0SEM_RISK_3 (Status)

New Measures o o o o o o o o o 0SEM_BSCSCR (BSC Score) 0SEM_BSCSTS (BSC Status) 0SEM_ACTBDG (Budget for Risk Activity) 0SEM_RQUANT (Risk Effect (Quantity)) 0SEM_RAMNT (Risk Effect (Amount)) 0SEM_RSKSCR (Risk Score) 0SEM_RSKSTS (Risk Status) 0SEM_TGAMNT (Target Value (Amount)) 0SEM_TGAMNT (Target Value (Quantity))

New Characteristics o o o o o o o 0SEM_ACTFLG (Expectation Value With/Without Risk Activity) 0SEM_PERS (Perspective ID) 0SEM_MEASID (Measure ID) 0SEM_STRAT (Strategy ID) 0SEM_RISKID (Risk ID) 0SEM_OBJ (Objective ID) 0SEM_VF (Value Field ID)

______________________________________________________________ __

42 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o o o o

0SEM_ACTIV (Risk Activity) 0SEM_RACTFR (Risk Activity - Valid from) 0SEM_RACTFR (Risk Activity - Valid to) 0SEM_TARPER (Target Period)

Effects on Data Transfer For BW data extraction, you must have closed the relevant periods in your corresponding SEM-CPM system (see documentation for Balanced Scorecard Monitor): This makes the risk-relevant data available for BW extraction. You then create InfoPackages for the following InfoSources, and start the data download: o o o o Risk Management Master Data Status Risk values Target values for risks

You have then extracted all risk-relevant master data and transaction data to your SAP BW.

1.1.37 Evaluation of Bidding Engine Bid Invitations and Bids

Use The evaluations support the bid invitation process of the Bidding Engine. Existing reports have been extended and new reports have been added. You can use the evaluations to analyze the bid invitations according to different criteria (such as creation date, status and category), and you can compare the bids submitted for a particular bid invitation. For each bidder, you can display how many bids he has submitted per category in a specific time period.

1.1.38 SRM: BW Reporting with SUS-MM Coupling (changed)

Use Up to now, in the Supplier Self-Services (SUS) component, you could only display data from an Enterprise Buyer System in the SAP BW Content reports that were provided. From Release 3.1C, it is now also possible to analyze data that has been extracted from a SAP MM System into SAP BW. To enable this, the existing SUS reports have been modified. In addition, three SUS reports are provided that can only be used in the SUS-EBP scenario.

______________________________________________________________ __

SAP AG 16.10.2002 43

R/3 System ______________________________________________________________

__

1.1.39 Trade Promotion Management: Business Content

Use The mySAP Business Warehouse now also provides Business Content for the Trade Promotion Management (TPM) Busines Scenario. This Business Scenario provides you with an integrated solution for Trade Promotions and combines all activities to do with the planning, marketing, and sales of your product in one unified process. This lets you plan, coordinate, and process all activities required within the Business Scenario centrally. You can run reports for current and future planning based on historical data and on data from external data providers. The new Busines Content supports the TPM process in the SAP systems SEM, CRM, and R/3. Plan data is captured from SEM and CRM Marketing Planner, and actual data from CO-PA. The new Business Content includes the following areas: o Monitoring & Reporting: You can regularly monitor the success of a Trade Promotion and take corrective action if necessary. You can also check whether the sales expenditures are within the budget. Results Analysis: You can analyze which Trade Promotion tactics achieve optimum results for which sales channels, customers, and products. Forecast: You can forecast the Return on Investment (ROI) or increase in sales as the result of a particular Trade Promotion.

o o

1.1.40 Global Spend Analysis (Changed)

Use Global Spend Analysis is now available in the MarketSet environment. The documents to be evaluated are sent via the MarketSet connector, transformed into the XML format of the SAP Business Information Warehouse (SAP BW XML format), and written to the BW Delta Queue. Effects on Customizing There are no special Customizing transactions. However, several steps are necessary for a successful configuration. These are described in the Configuration Guide for the Global Spend Analysis scenario. See also SAPNet: Keyword "Global Spend"

1.1.41 SRM: Consolidated Info Objects in the E-Procurement Content

Use Consolidated InfoObjects for

______________________________________________________________ __

44 16.10.2002 SAP AG

R/3 System ______________________________________________________________ __

o o o

Products (0PROCUCT) Categories (0GN_CAT_PUR) Partners (0GN_VENDOR)

are grouped in data targets (ODS objects and InfoCubes) and in some queries in the E-Procurement content. The model of the consolidated InfoObjects exists since BW 3.0B. It allows you to group together different, local, source system dependent representations of objects, for example 0MATERIAL and 0BBP_PROD for the product. This function is particularly useful if a complex E-Procurement landscape is used, for example, if several R/3 systems are connected to an Enterprise Buyer system. With the consolidated Info Objects, you can, for example, measure your business volume per vendor straight away, regardless of the system from which the data originates. See also SAP Help Portal (help.sap.com) under mySAP.com Cross-Industry Solutions -> mySAP Business Intelligence -> Business Information Warehouse -> Business Content -> Cross-Application Master Data -> Consolidated InfoObjects for BP, Product, and Product Category.

1.1.42 SRM: Vendor Evaluation in mySAP Supplier Relationship Management

Use mySAP Supplier Relationship Management (mySAP SRM) is the cross-industry solution that helps you optimize your vendor relationships. It is based on the functions of mySAP E-Procurement. mySAP SRM offers more than E-Procurement, since it supports companies during the whole procurement cycle in strategic/operational sourcing of supply, connection of vendors, and procurement too. Vendor evaluation in mySAP SRM is called from SAP Enterprise Buyer (SAP EB). From BW3.0B, timeliness and quantity reliability evaluations are available that are based on document data from Enterprise Buyer and from R/3 Materials Management. With SAP EB 4.0, manual entry of valuation data is also possible using the survey tool WebSurvey. Using Web Survey (delivered with ABA 6.20 SP 08/SAP EB 4.0) different manual evaluation criteria, for example, timeliness and quantity reliability for certain events, for example, goods receipt and invoice receipt, is compiled, assessed, and extracted to the SAP Business Information Warehouse (SAP BW). In BW, the criteria are updated to an ODS object on the basis of document data. The following evaluation possibilities are available in the Sourcing Cockpit and the Vendor List of SAP EB: o o Evaluation criteria with assessment per vendor and event Evaluation criteria with assessment per vendor and document

Vendors can display their own assessment scores in SAP Supplier Self-Services (SAP SUS). Vendor evaluation in mySAP SRM supports vendor selection and management and is the basis for the

______________________________________________________________ __

SAP AG 16.10.2002 45

R/3 System ______________________________________________________________

__

communication with vendors. Evaluation can also occur on other levels than that of vendors. For example, it can occur on product or product category level. Vendor evaluation is supplied with data in the standard system from SRM 3.0 (EB 4.0) onwards. Up until then, the survey tool can be connected on project basis.

______________________________________________________________ __

46 16.10.2002 SAP AG

Information

50 pages

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

7582


You might also be interested in

BETA
Data Modeling in SAP NetWeaver BW
SAP BI Consultant - Tim Webb - Resume