Business Information Warehouse Release Notes BW-BCT Business Content and Extractors
Release SAP BI Content 3.2 Add-on
Copyright Copyright(c) 2003 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
2
Copyright Copyright(c) 2003 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
2
BW-BCT Business Content and Extractors 5 1. Analytical Applications 5 Dun&Bradstreet Supplier Analytics Scenario 5 D&B Delivery analysis for SAP BW 5 Dun & Bradstreet Customer Analytics for SAP BW 6 Dun & Bradstreet Marketing Universe for SAP BW 6 2. Customer Relationship Management 7 Channel Management (New) 7 Analyzing Activity Items (New) 8 Customer Migration Analysis: Business Content 8 Data Mining Workbench: Enhancements 11 External List Management (New) 12 Business Content for External List Management (New) 13 Business-Partner Related Key Figures (New) 16 Analysis of Installed Base Master Data (New) 16 Commission Recipient and Business Partner Mapping Mechanism Changed. 17 Lead Time Analysis for Service Orders (New) 18 Generic Extractor for CRM Marketing Attributes (new) 18 Enhancements to SAP CRM Marketing Planning Content 19 Business Content for Marketing Optimization (new) 20 Analysis of Competitor Products in Opportunities (New) 20 Opportunity Hierarchies in Business Warehouse (New) 21 Analysis of Planning Accuracy (New) 22 Integration of Products in SAP BW (Enhanced) 23 Increased Flexibility in Response Prediction Modeling (new) 24 Analysis of Service Plan Simulation Data (New) 24 InfoCube for Strategic Service Planning (New) 25 Analysis of Service Quotation Data (New) 26 Territory Management Analytics (New) 26 Changes in CRM IC WFM Content for BW 3.2 27 Warranty Analysis (New) 28 SAP Media: Intellectual Property Management (New) 29 Interactive Scripting Evaluation for the IC WebClient 33 3. Supplier Relationship Management 33 Integration of SAP of SAP Content Integrator into SAP BW 33 Project Success of an Enterprise Buyer Implementation (New) 34 New Functions for Vendor Evaluation in SRM 34 4. Supply Chain Management 35 Business Content SCM Inventory Management 35 5. Product Lifecycle Management 35 Line Item Reporting for Commitments and Actual Data (Enhanced) 35 Business Content for cProjects (Enhanced) 36 Business Content for Workforce Management Core (New) 36
SAP AG
3
Evaluation of Dangerous Goods Shipments (New) 37 6. Financials 38 DataSource 0EC_PCA_3 for Line Item Delta Extraction 38 Business Content for Dispute Management 38 Generic FI-SL Line Item Extractors for Transporting the Delta Upload to the SAP BW System 39 Financial Statement and Profit & Loss Statement 39 Delta Extractors FI-AP/AR/GL 40 Master Data for Orders and WBS Elements (Enhanced) 41 Crystal Reports for Formatted Financial Statements 42 7. Human Capital Management 42 Business Content for the SAP Learning Solution (New) 42 Business Content for Objective Setting and Appraisals (New) 43 Business Content for Budget Planning and Position Control (Enhanced) 45 Key figures MTTR and MTBR for plant maintenance and customer service. 46 8. Industry Solutions 46 Apparel and Footwear 46 Business Content for SAP Apparel and Footwear (SAP AFS) 46 Automotive 47 Business Content for Warranty Processing in Discrete Industries (New) 47 Banking 48 Link from CML to SAP BW 48 Insurance 48 New Extractors in FS-CM 48 Healthcare 49 Enhancements to Business Content SAP Healthcare 49 Media 49 SAP Media: Changes to Business Content for Advertising Management 49 Retail 50 NEW ODS OBJECTS FOR UPDATING AGENCY DOCUMENTS 50 SAP Retail Merchandise and Assortment Planning 50 Utilities 52 Quotation Planning and Analysis for the Utilities Industry 52 EDM Analyses in the Utilities Industry 53 Collection Agencies in Contract Accounts Receivable and Payable 54 Installment Plan in Contract Accounts Receivable and Payable 54 Sales Statistics with Tax Amounts in the Utilities Industry 55 Beverage 55 SAP Beverage Business Content 55 9. Cross-Application Components 56 BW Integration in the Business Partner (Extended) 56 10. External Sources 58 SAP BW Business Content for Oracle Receivables (New) 58
SAP AG
4
BW-BCT Business Content and Extractors 1. Analytical Applications Dun&Bradstreet Supplier Analytics Scenario Use The existing D&B scenario Supplier Analytics (previously: Vendor/Customer Analytics ) has been enhanced in this release. You can now update the D&B data from the Supplier Analytics Import file (#1784 file#) with the help of a flexible InfoSource in InfoObjects 0DBDUNS_NUM, 0VENDOR, 0BPARTNER, and 0GN_VENDOR. Furthermore, the data is written from the 1784 file into an ODS object so that you can compare information from D&B with internal business data. The data comparison is enabled by a multiprovider (0SRM_DBM1). This unifies data from the 0BBP_C01 InfoCube and from the 0DB_VCDS1 ODS object. Based on a multiprovider, a new query can be displayed, for example, with the vendor dependencies for individual companies (#dependency ratio#). Among other things, the query is placed across from the internal business sales volume (from 0BBP_c01) for the total vendor sales (0DB_VCDS1). In addition to the data from the 1784 file, new attributes and key figures from D&B are integrated into the scenario, which ar e of most importance in US-American markets. New import files from D&B exist for this, as well as flexible InfoSources for updating master data into the existing model.
Effects on Existing Data You can continue to use the existing D&B scenario in the old form. If you want to use the enhancement, you have to reproduce the 1784 file for the ne w, flexible InfoSource. If you want to use a scenario with the 0BPARTNER object, you have to use a new export program included in SAP BW 3.20 BW 3.20 in order to create the BW export BW export file.
D&B Delivery analysis for SAP BW Use The existing D&B scenario Vendor Analysis (previously: Vendor/Customer Analytics ) has been enhanced in this release. You can now update D&B data from the Supplier Analytics import file ("1784-file") into the InfoObjects 0DBDUNS_NUM, 0VENDOR, 0BPARTNER, 0BPARTNER, und 0GN_VENDOR using a flexible InfoSource. The system also writes data from the 1784 file into a ODS object enabling D&B information to be compared with company internal data. This comparison of data is made possible with a MultiProvider (0SRM_DBM1). (0SRM_DBM1). This combines data from InfoCube 0BBP_C01 and ODS object 0DB_VCDS1. A new query is based on the MultiProvider, using which vendor depedency ratios can be displayed for your own company. The query compares the company internal purchase volume (from 0BBP_C01) with the total revenue of the vendor (from 0DB_VCDS1). In addition to the data from the 1784 file, new D&B attributes and key figures have been integrated into this scenario. These are mostly relevant to a US context. Related to this, new D&B import files and flexible InfoSource exist to update master data into the existing model.
Effects on Existing Data You can continue to use the existing D&B scenario in its older form. If you want to use the enhancement, you need to map the 1784 file to a new flexible InfoSource. If you want to use a scenario with the object 0BPARTNER, you need to use a new export program which is contained in SAP BW 3.20, BW 3.20, in order to create the BW -export BW -export file.
SAP AG
5
Dun & Bradstreet Customer Analytics for SAP BW Use The existing D&B scenario Customer Analytics (previously Vendor/ Customer Analytics) has been expanded in this release. You can now update D&B data with the help of a flexible InfoSource in InfoObjects 0DBDUNS_NUM and 0CUSTOMER. Four new queries are based on InfoProvider 0SD_C03 that combine customer information with group structure information. The following Business Content is available in BW Release 3.2 Content:
New roles:
Dun & Bradstreet Customer Analysis (SAP_BW_DB_CUSTOMER_ANALYSIS)
New queries: o
D&B Duplicate Vendors per one D-U-N-S Number (0SD_C03_DB_Q0002)
o
D&B Invoiced Amount per Customer with Family Tree (0SD_C03_DB_Q0001)
o
D&B Customer Revenue Analysis (0SD_C03_DB_Q0003)
o
D&B Customer Details (0SD_C03_DB_Q0010)
New InfoSource: o
D&B Import File: Attributes (0DBDUNS_IMPORT_ATTR)
Effects on Existing Data You can continue to use the existing scenario in its old form. If you want to use the expanded version, map Vendor/Customer Analytics Import File (1784-file) on to the new flexible InfoSource.
Dun & Bradstreet Marketing Universe for SAP BW Use The upload process for D&B data is simplified considerably by using process chains. In BW release 3.2 Content five process chains in total are delivered for D&B Marketing Universe Scenario: o
0DB_INIT_P01: D&B Marketing Initial Data Load Uploading the initially delivered D&B data (master data)
o
0DB_FULL_P02: D&B Marketing Full Master Data Load Uploading repeatedly delivered D&B data (master data)
o
0DB_FULL_P04: D&B Marketing Full Transactional Data Load Uploading repeatedly delivered D&B data (transaction data)
o
0DB_FULL_P03: D&B Marketing Additional Data Load Uploading additional contact information
o
0DB_FULL_P05: D&B Marketing Meta Chain Full Data Load Meta chain: 0DB_FULL_P02 + 0DB_FULL_P04
SAP AG
6
2. Customer Relationship Management Channel Management (New) Use As of the release BW 3.2 Content, the following enhancements and new content to the business content for Partner and Channel Analytics are implemented.
User-specific Data in Queries Variables now filter data in queries according to a user's role (Channel Manager, Partner Manager or Partner Employee), so that users only see information relevant for their purpose.
Enhanced business content objects to allow partner-specific analysis •
•
•
•
InfoObject 0BPARTNER with the following navigational attributes: o
Partner Type
o
Partner Program
InfoCubes that have been enhanced with the InfoObject Sales Partner (0CRM_SALESP) o
CRM Lead Management (0MKTG_C01)
o
Opportunities (0CRM_C04)
o
Quotations for Sales Orders (0CSAL_C05)
InfoCubes that have been enhanced with the InfoObject Transaction Number (0CRM_OBJ_ID) o
CRM Lead Management (0MKTG_C01)
o
Opportunities (0CRM_C04)
BW extractors and InfoSources affected by these enhancements have been enhanced accordingly.
Newly created business content objects •
InfoCube Sales Orders for Hosted Order Management Scenarios (0HOM_C03)
•
Queries, views and templates in the following areas: o
Lead Management
o
Sales (Quotations for Sales Orders, Sales Orders, Sales Orders for Hosted Order Management Scenarios)
o
Contracts
o
Sales Planning
This provides the Channel Management roles (Channel Manager, Partner Manager or Partner Employee) with the most important key performance indicators covering the relationship between a Brand Owner and its Channel Partners.
See also For information about Opportunities, Quotations, Sales Order and Sales Planning, see the SAP Library for the SAP Business Information Warehouse under Business Warehouse -> Business Content -> Customer Relationship Management -> Sales.
SAP AG
7
For information about Lead Management, see the SAP Library for the SAP Business Information Warehouse under Business Warehouse -> Business Content -> Customer Relationship Management -> Marketing .
Analyzing Activity Items (New) Use As of Business Warehouse Release 3.2 you can analyze the items in activities. Items have been added to activities in mySAP Customer Relationship Management (Release 4.0) so that you can record the distribution of samples or describe the product placement of articles in activity journals, for example. New Business Content has been created so that the items are also contained in activity analyses such as: •
Pre-Sales Investment per Customer (number of activities and items per activity partner)
•
Number of Samples Given in Current Calendar Year
•
Number of Samples per Contact Person and Batch
The following objects have been created for Release 3.2: •
DataSource: Activity Items (technical name: 0CRM_SALES_ACT_I)
•
InfoSource: Activity Items (technical name: 0CRM_SALES_ACT_I)
•
ODS: Activity Items (technical name: 0CRM_ACTI)
•
InfoCube: Activity Items (technical name: 0CRM_C08)
Relevant characteristics and key figures have also been created. Item information is also extracted to objects for the activity header so that you can evaluate information about iObjects and business agreements.
Effects on Existing Data The following InfoObjects have been enhanced with a key figure for the nu mber of items per activity: •
DataSource: Activity (technical name: 0CRM_SALES_ACT_1)
•
InfoSource: Activity in Flat Structure for ODS (technical name: 0CRM_SALES_ACT_1)
•
InfoCube: Activity (technical name: 0CSAL_C01)
•
ODS: Activity (technical name: 0SAL_DS01)
If you use fields for consumer products in the activity journal from the CI_ACT_REP_ADD_FIELDS Include in the CRM system, you can add the relevant characteristics to the ODS and InfoCube so that the information can be analyzed in the BW system. Note that you must create your own key figures for the consumer product information.
See also For more information about the Business Warehouse Content for Activity Management, see the SAP Library under Business Information Warehouse -> Business Content -> Customer Relationship Management -> Cross-Application Performance Analyses -> Activities. For more information about Activity Management in CRM, see the SAP Library under Customer Relationship Management -> Enterprise Sales -> Activity Management.
Customer Migration Analysis: Business Content Use
SAP AG
8
As of SAP BW 3.2, Customer Migration Analysis is provided as part of business content. This enables you to measure the customer migration. You can use Customer Migration Analysis for the following types of analysis: Clustering Analysis comparison: You can measure the migration of customers between different clusters by comparing the results of various clustering analysis executions. Decision Tree Analysis comparison: Similar to clustering analysis, you can measure the customer migration by comparing the Predicted Value of the decision tree results. ABC Classification: You can compare the results of ABC Classification and measure the migration of customers between the A, B and C classes. You can also compare the results of different types of analyses. For example, you can compare the results of ABC Classification and Clustering , to know how many customers of Class A belong to Cluster 1. You can generate the DataSources as part of Customer Migration Analysis within the Data Mining Workbench for transfer of transactional data. The following InfoObjects are new: Techncial Name Description 0DM_CLUSNC
Cluster Number
0DM_CLUSNC2 2nd best Cluster Number 0DM_CLUSMIH Min Inter Cluster Hops 0DM_CLUSMI
Max Iteration
0DM_CLUSMDV Max Distinct Values 0DM_SCORVAL Score 0DM_PREDVAL Predicted Value 0DM_PREDCF
Confidence
0DM_PREDSP
Support in Training
0DM_PREDVT
Value in Training
0DM_TCOUNT
Total Count
All the InfoSources are for transactional data. Since DataSources will be generated in the Data Mining Workbench, you must create the transfer rules, that is, do the mapping manually. The following InfoSources are new: Technical Name
Description
0CRM_ABC_BPART_1
CRM ABC Classification
0CRM_CLUS_BPART_1 CRM Clustering 0CRM_TREE_BPART_1 CRM Decision Tree 0DM_ABC_CUST_1
ABC Classification
0DM_CLUS_CUST_1
Clustering
0DM_TREE_CUST_1
Decision Tree
The following ODS objects are new: Technical Name Description 0CRMADS01
CRM ABC Classification Results
0CRMCDS01
CRM Clustering Results
0CRMTDS01
CRM Decision Tree Results
0DMADS01
ABC Classification Results
0DMCDS01
Clustering Results
0DMTDS01
Decision Tree Results
The following InfoCubes are new: Technical Name Description 0CRMACC01
CRM ABC Classification Counts
0CRMCCC01
CRM Clustering Counts
0CRMTCC01
CRM Decision Tree Counts
SAP AG
9
0DMACC01
ABC Classification Counts
0DMCCC01
Clustering Counts
0DMTCC01
Decision Tree Counts
The following MultiProviders are new: Technical Name Description 0CRMAMC01
CRM ABC Classification and Counts
0CRMCMC01
CRM Clustering and Counts
0CRMTMC01
CRM Decision Tree and Counts
0DMACM01
ABC Classification and Counts
0DMCCM01
Clustering and Counts
0DMTCM01
Decision Tree and Counts
The following InfoSets are new: For comparing results of the same type of analysis Technical Name Description 0CRMAIS01
CRM ABC Migration Analysis
0CRMCIS01
CRM Clustering Migration
0CRMTIS01
CRM Decision Tree Migration
0DMAIS01
ABC Migration Analysis
0DMCIS01
Clustering Migration
0DMTIS01
Decision Tree Migration
For comparing results of the different types of analyses Technical Name Description 0CRACIS01
Comparing CRM ABC Classification and CRM Clustering
0CRATIS01
Comparing CRM ABC Classification and CRM Decision Tree
0CRCTIS01
Comparing CRM Clustering and CRM Decision Tree
0DMACIS01
Comparing ABC Classification and Clustering
0DMATIS01
Comparing ABC Classification and Decision Tree
0DMCTIS01
Comparing Clustering and Decision Tree
The following Reports are new: For comparing results of same type of analysis Technical Name
Description
0CRMAIS01_Q0001
CRM ABC Migration Analysis
0CRMCIS01_Q0001
CRM Clustering Migration Analysis
0CRMTIS01_Q0001
CRM Decision Tree Migration Analysis
0CRMAMC01_Q0001 CRM ABC Deviation analysis relative to second ABC Classification 0CRMAMC01_Q0002 CRM ABC Deviation analysis relative to first ABC Classification 0CRMCMC01_Q0001 CRM Clustering Deviation analysis relative to second Clustering analysis 0CRMCMC01_Q0002 CRM Clustering Deviation analysis relative to first Cluster 0CRMTMC01_Q0001 CRM Decision Tree Deviation analysis relative to second Decision Tree analysis 0CRMTMC01_Q0002 CRM Decision Tree Deviation analysis relative to first Decision Tree analysis
SAP AG
10
0DMAIS01_Q0001
ABC Migration Analysis
0DMCIS01_Q0001
Clustering Migration Analysis
0DMTIS01_Q0001
Decision Tree Migration Analysis
0DMAMC01_Q0001
ABC Deviation analysis relative to second ABC Classification
0DMAMC01_Q0002
ABC Deviation analysis relative to first ABC Classification
0DMCMC01_Q0001
Clustering Deviation analysis relative to second Clustering
0DMCMC01_Q0002
Clustering Deviation analysis relative to first Clustering
0DMTMC01_Q0001
Decision Tree Deviation analysis relative to second Decision Tree analysis
0DMTMC01_Q0002
Decision Tree Deviation analysis relative to first Decision Tree analysis
For comparing results of the different types of analyses Technical Name
Description
0CRACIS01_Q0001
Comparing CRM ABC Classification and CRM Clustering
0CRATIS01_Q0001
Comparing CRM ABC Classification and CRM Decision Tree
0CRCTIS01_Q0001
Comparing CRM Clustering and CRM Decision Tree
0DMACIS01_Q0001
Comparing ABC Classification and Clustering
0DMATIS01_Q0001
Comparing ABC Classification and Decision Tree
0DMTIS01_Q0001
Comparing Clustering and Decision Tree
0CRMAMC01_Q0003 Deviation of CRM ABC Classification from CRM Clustering 0CRMAMC01_Q0004 Deviation of CRM ABC Classification from CRM Decision Tree 0CRMCMC01_Q0003 Deviation CRM Clustering from CRM ABC Classification 0CRMCMC01_Q0004 Deviation of CRM Clustering from CRM Decision Tree 0CRMTMC01_Q0003 Deviation of CRM Decision Tree from CRM ABC Classification 0CRMTMC01_Q0004 Deviation of CRM Decision Tree from CRM Clustering Analysis 0DMAMC01_Q0003
Deviation of ABC Classification from Clustering
0DMAMC01_Q0004
Deviation of ABC Classification from Decision Tree
0DMCMC01_Q0003
Deviation of Clustering from ABC Classification
0DMCMC01_Q0004
Deviation of Clustering from Decision Tree
0DMTMC01_Q0003
Deviation of Decision Tree from ABC Classification
0DMTMC01_Q0004
Deviation of Decision Tree from Clustering
See also For more information, see Business Content -> Customer Relationship Management -> Data Mining and Business Content -> Customer Relationship Management ->Customer Analyses in the SAP Library.
Data Mining Workbench: Enhancements Use As of SAP BW 3.2, the navigation tree for the Data Mining Workbench has been restructured. The Scoring method is classified under Approximation and ABC Classification under Further Analyses . The following enhancements have been made to the various data mining methods: Association Analysis You can specify more than one field as type Transaction while performing Association Analysis. ABC Classification
SAP AG
11
•
You can now perform ABC classification on each value or a combination of values of the grouping attribute. For example, you can classify customers into A, B and C classes within each region.
•
You can also assign compound characteristics as the key or grouping attribute.
•
The ABC classification output charts have also been enhanced.
Clustering •
The clustering method has been enhanced to handle unspecified ranges. There are two new Transformation Types for handling unspecified ranges, that is, Discretize and Multiply by specified weights.
•
The clustering results screen has been enhanced to display Intra Cluster Attribute Value Distribution Index and Inter and Intra-Cluster Distances Information with additional clustering attributes such as Maximum Distance, Minimum Distance and Average Distance of each cluster.
Scoring •
You can perform What If Prediction for Scoring.
•
Enhancements have been made to provide better visualization for the scoring output.
•
You can view detailed statistical information and distribution by using the Other Statistics and the Score Distribution options respectively.
For Decision Tree and Clustering , you can display the mining results in PMML format and export them to a local file.
See also For further information, see Business Content -> Customer Relationship Management -> Data Mining in the SAP Library.
External List Management (New) Use External List Management is the process of procuring, managing, implementing and evaluating acquired addresses that are used to win ne w customers. The scenario External List Management runs in SAP BW and SAP CRM. The address lists used in External List Management can be obtained from external providers of marketing data (for example, Schober, Claritas, Dun & Bradstreet). The customer can specify the data he wants, how many data records should be contained in address list and the format in which the data should be delivered. Address data can be bought or rented and a contractual agreement determines how often and for how long the data can be used for marketing activities. You can access the user interface of External List Managment using transaction elm. The scenario consists of the following steps: 1. Loading the address list The data provider delivers the address data, for example, by e-mail, on a CD in ASCII format, or as a csv file. BW provides a user interface where you can enter the file path, the origin of the data, the gross number of data records, the costs and permitted or recommended number of usages and duration of usages and where you can trigger further process steps. Before uploading, the data records must be mapped. During mapping, the system administrator assigns a target structure to the source structures of the address file. 2. Checking the address list After the upload, the data can be checked to ensure that postal details are correct and that duplicates are identified. 3. Execution of marketing campaings with obtained addresses This step takes place in the CRM System. The list formatted in the BW System can be considered as a completed target group and can be loaded into the CRM System, or it can be proces sed further in the Segment Builder. To import lists from BW into CRM, the list type in Customizing in both systems must be identified in the same way under Define List Type. Campaigns can then be
SAP AG
12
carried out using the created target groups. Before the marketing activities are carried out, you need to check that the business partners obtained may actually be contacted, that is, whether the permitted number of uses or the permitted end-of-use date has been exceeded. If a customer is contacted after this check, this can be recorded by a contact counter. 4. Reporting Reporting can be carried out after all marketing activities have been concluded. This can include a range of aspects regarding the quality of address data (for example, how many duplicates the list contains, how many addresses could not be contacted due to incorrect address data) and the success of the marketing activities (how many addresses were won as customers, how many contacts were necessary to win the customer) and so on. For more information on this, see the Business Content Release Information for External List Management. 5. Deleting Data Once you have exceeded the usage duration agreed in the contract, or after carrying out the maximum number of activities agreed, the details of the business partners who were not successfully contacted must be deleted. The definition of a successful contact is usually set down in the contractual agreement.
Effects on Customizing You can maintain settings for External List Management in Customizing under Business Information Warehouse -> Settings for Business Content -> Customer Relationship Management -> External List Management .
See also For more information, see the documentation in the SAP Library under Business Content -> Customer Relationship Management -> Marketing -> External List Management .
Business Content for External List Management (New) Use Release SAP BW 3.2 Content provides the following Business Content for External List Management: Multi Provider •
External List Management (0 MKTG_MC1)
Web Templates •
Sales Success (0TPL_MKTG_MC01_Q0001_V01)
•
Successful Contacts (0TPL_MKTG_MC01_Q0002_V01)
•
Quality Address List (0TPL_MKTG_MC01_Q0003_V01)
•
Data Package Success (0TPL_MKTG_MC01_Q0004_V01)
Queries •
Sales Success (0MKTG_MC1_Q0001)
•
Successful Contacts (0MKTG_MC1_Q0002)
•
Quality Address List (0MKTG_MC1_Q0003)
•
Data Package Success (0MKTG_MC1_Q0004)
Info Cubes •
Business Partner List (0MKTG_C03)
ODS Objects •
Contact Counter (0ELM_CC)
SAP AG
13
Key Figures •
Address List - Gross Number (0ELM_NOGROS)
•
Address List - Costs (0ELM_COSTS)
•
Activity Counter (0ELM_NUMCON)
•
Counter (0ELM_COUNT)
Calculated Key Figures •
Successfully Contacted BP in % (0MKTG_C03_CK001)
•
Won Customers in % (0MKTG_C03_CK002)
•
Average Revenue/Won Customers (0MKTG_C03_CK003)
•
Number of Contacts/Won Customers (0MKTG_C03_CK004)
•
Average Costs/Won Customers (0MKTG_C03_CK005)
•
Average Profit/Won Customers (0MKTG_C03_CK006)
•
Incorrect Postal Addresses in % (0MKTG_C03_CK007)
•
Duplicates in % (0MKTG_C03_CK008)
Restriced Key Figures •
Successfully Contacted BP (0MKTG_C03_RK001)
•
Won Customers (0MKTG_C03_RK002)
•
Incorrect Postal Address (0MKTG_C03_RK003)
•
Number of Duplicates (0MKTG_C03_RK004)
Characteristics •
Address List Type (0ELM_TYPE)
•
Address List - Provider (0ELM_ORIGIN)
•
Form of Address Key (0ELM_PERS_T)
•
Form of Address Key - Company (0ELM_ORG_TK)
•
Address List Description (0ELM_LISTID)
•
Duplicate (0ELM_DUPLIC)
•
ELM GUID (Address Data Record ID) (0ELM_GUID_I)
•
ELM GUID (Address List ID) (0ELM_GUID_H)
•
Recommended End-of-Use Date (Address List) (0ELM_VDATE)
•
Successfully Contacted Business Partners (0ELM_SUCOAC)
•
Permitted End-of-Use Date (Address List) (0ELM_UDATE)
SAP AG
14
•
Fax (Number) (Person) (0ELM_FAXEXT)
•
Fax (Number) ( 0FAX_EXTENS)
•
Fax Number (Code and Extension) (0ELM_FAXNR)
•
Function Description of Partner (0ELM_FCTN)
•
External Business Partner (0ELM_BP_EXT)
•
Won Business Partners (0ELM_WONCUS)
•
Organization Establishment Date (0ELM_OFDATE)
•
Address List Deletion Indicator in CRM (0ELM_DEL_L)
•
Business Partner Deletion Indicator in CRM (0ELM_DEL)
•
Maximum Number of Contacts (0ELM_MUSAGE)
•
Pager Number (0ELM_PAGER)
•
Incorrect Postal Addresses (0ELM_INCADR)
•
Telephone (Number, Person) (0ELM_TELEXT)
•
Telephone Number (Code+Extension) (0ELM_TELNR)
•
URL, e.g. Homepage or ftp Address (0ELM_ORGURL)
•
Agreed End-of-Use Date (Address Data Record) (0ELM_MUDATE)
Process Chain •
Delta Upload of Address List and Ext. BP for ELM (ELM_DELTA_P02)
•
Initial Upload of Address List and Ext. BP for ELM (ELM_INIT_P01)
Data Sources •
CRM External List Management of Header Data (Administration) (0CRM_ELM_ATTR)
•
CRM External List Management of Item Data (BP List) (0CRM_ELM_I)
•
CRM External List Management of External Business Partners (0CRM_ELM_BP_EXT)
•
CRM External List Management of Contact Counters (0CRM_ELM_CC)
•
CRM External List Management of Text Lists (0CRM_ELM_H_TEXT)
•
CRM External List Management of Provider Texts (0CRM_ELM_ORIGIN_TEXT)
•
CRM External List Management of Type Texts (0CRM_ELM_TYPE_TEXT)
Additional Content Objects User Interface of ELM (Transaction elm)
See also For additional information, refer to the release information External List Management (new) and the SAP library under Business Content -> Customer Relationship Management -> Marketing -> Business Scenarios -> External List Management .
SAP AG
15
Business-Partner Related Key Figures (New) Use Business Warehouse Release 3.2 contains a new Operational Data Store (ODS) for business partnerrelated key figures. This can be used to evaluate activity and sales order information in summarized form for a specific business partner. It has been designed particularly for use with the business partner fact sheet in mySAP Customer Relationship Management in order to improve the performance when calling data from the Business Warehouse system to the fact sheet.
,Effects on Existing Data The Business Partner Related Key Figures ODS (technical name: 0CRMBPKPI) is new for Release 3.2. The following Business Content has been changed: •
InfoSource: Activity in Flat Structure for ODS (technical name: 0CRM_SALES_ACT_1)
•
InfoSource: Sales Order Items (technical name: 0CRM_SALES_ORDER_I)
Effects on Data Transfer The data is taken from the following ODSs: •
Activity ODS (technical name: 0SAL_DS01) This provides information such as number of closed activities and details of the next planned activity.
•
Sales ODS (technical name: 0CRM_SALO)
This provides information such as number of open sales order items as well as items blocked for delivery and billing. The system transfers this to the business partner fact s heet in the CRM system for the Quick Info info block.
Effects on System Administration The standard settings for the Quick Info info block in the business partner fact sheet have been changed so that they call up the information from the new ODS.
See also For more information about the business partner fact sheet, see the SAP Library for Customer Relationship Management under Master Data -> Business Partners -> Business Partner Cockpit and Fact Sheet.
Analysis of Installed Base Master Data (New) Use As of the 3.2 Content release of SAP BW, master data for installed bases (IBases) can be extracted from SAP Customer Relationship Management (CRM). This enables you to analyze IBases from the point of view of their components and their attributes. For example, you could determine the number of occurrences of a particular product or individual object within the IBases for which your service organization is responsible. The following Business Content is available for the extraction and analysis of IBase master data in the 3.2 Content release of SAP BW:
New DataSources in mySAP CRM Release 4.0 CRM IBase Master Data
0CRM_SRV_IBASE_ATTR
GUID of Installed Base/Component 0CRM_IBAKEY_TXT
SAP AG
16
New InfoSources CRM Service - IBase Master Data
0CRM_SERVICE_IBASE_ATTR
GUID of Installed Base/Component 0CRM_IBAKEY
New Characteristics CRM IBase
0CRM_IBASE
IBase Business Partner
0CRM_IBPART
GUID of Installed Base/Component
0CRM_IBAKEY
Component No Longer Valid
0CRM_IBDEL
Top-Level Component of Installed Base
0CRM_COMPRT
Higher-Level Component
0CRM_COMPPA
Characteristic: Installed Base/Component 0CRM_IBFLAG Installed Base/Component Created By
0CRM_IBCRBY
Text Component
0CRM_IBTEXT
Component is Installed Base
0CRM_COMPIB
New ODS Object Installed Bases and Components 0CRM_IBCO
New Queries Installed Base Analysis by Location
0CRM_IBCO_Q0101
Analysis of Products in Installed Bases
0CRM_IBCO_Q0102
Analysis of Individual Objects in IBase Components 0CRM_IBCO_Q0103 Note The characteristic Vehicle (0AUVEHICLE) is predefined in the standard Business Content as an example of how an individual object can be represented. Characteristics representing vehicle attributes are also provided, and are linked to the Vehicle characteristic. The characteristics are included in the ODS object Installed Bases and Components , and are included in the definition of the query Analysis of Individual Objects in IBase Components.
Effects on Customizing In SAP CRM, you control the extraction of IBases and their components to SAP BW by defining: •
Whether data is extracted
•
The level of data extracted (according to the IBase hierarchy)
This enables you to restrict the volume of data extracted to a minimum, thereby ensuring optimum system performance when you run extraction and analyses. You make this setting in the SAP Implementation Guide in the step: Integration with Other mySAP.com Components -> Business Information Warehouse -> Settings for Application-Specific DataSources (CRM) -> Settings for the Extraction of CRM Objects -> Set Up Extraction for Installed Base.
Commission Recipient and Business Partner Mapping Mechanism Changed. Use
SAP AG
17
The mapping and retrieval of the Business Partner (BuPa) to the Commission Recipient (0CRM_CRBP) has been changed. This will not impact the end user and is only a change in the back system processes.
Lead Time Analysis for Service Orders (New) Use As of the 3.2 Content release of SAP BW, you can analyze the lead time for service orders created in SAP Customer Relationship Management (CRM), for example, by determining how long it takes on average for orders to be completed within your service organization. Service lead time is calculated as the time between creation of a service o rder and the setting of the order status to "Completed". As a key figure, it can give you an indication of the efficiency of your internal processes, and is an important factor that can influence customer satisfaction. The following Business Content is available for the determination and analysis of service lead times:
New Key Figure Lead Time of Service Orders 0CRMLEADTIM
New Unit Unit - Lead Time of Service Orders 0CRMLTUNIT The above key figure and unit have been added to the following: DataSource in mySAP CRM Release 4.0 CRM Service - Order Header Data 0CRM_SRV_PROCESS_H InfoSource CRM Service - Orders (Header Data) 0CRM_SERVICE_PROCESS_H InfoCube Service Orders and Confirmations (Header Data) 0CSRV_C01 ODS Object Service Orders (Header Data) 0CRM_PROH
New Query Lead Time of Service Orders 0CSRV_C01_Q0103 Note The calculated lead times can be inaccurate if you use service plans in SAP CRM. This is due to the fact that service plans generate service orders based on defined intervals, and the creation date of the order can therefore be in advance of the actual start of s ervice.
Generic Extractor for CRM Marketing Attributes (new) Use SAP CRM 4.0 provides you with two generic DataSources that enable you to extract CRM marketing attributes and the related texts into SAP BW.
Effects on Data Transfer It is no longer necessary to generate DataSources specifically for the attribute values in profiles in SAP CRM.
See also For more information, see the documentation on these DataSources in the SAP Library under Business Content -> Customer Relationship Management -> Marketing -> DataSources.
SAP AG
18
Enhancements to SAP CRM Marketing Planning Content Use The planning content in SAP BW for SAP CRM Marketing has been enhanced to allow the campaign manager more flexibility and functionality for monitoring his marketing plans and campaigns and comparing plan versus actual data. New objects have been developed for use with SAP CRM 4.0 to allow monitoring and s uccess measurement in marketing planning. There are 3 new queries: •
Marketing Success Measurement (Plan vs Actual) 0CRM_MC05_Q0012
•
Marketing Top Down Planning (Plan vs Actual) 0CRM_MC05_Q0014
•
Marketing Costs (Plan vs Actual) 0CRM_MC05_Q0013
There are 4 new web templates: •
0TPL_CRM_MC05_Q0014_V01
•
0TPL_CRM_MC05_Q0014_V02
•
0TPL_CRM_MC05_Q0013_V01
•
0TPL_CRM_MC05_Q0012_V01
There are three new characteristics: •
0DUEDATE
•
0BP_GRP1
•
0BP_GRP2
The following have been added to InfoCube 0CRM_C01 Characteristics: •
0PROD_CAT_A
•
0PROD_CAT_B:
•
0DUEDATE
•
0BPARTNER
•
0BP_GRP
•
0CRM_PROD
•
0CRM_SALORG
•
0DISTR_CHAIN
•
0DIVISION
•
0PROD_CATEG
•
0BP_GRP1 and 0BP_GRP2 will also be added. They are new and will refer to 0BP_GRP
SAP AG
19
•
0CRM_MKTELE
•
0CRM_VERSION
Key Figure: •
0KEYFG_FLAG
Product Groups: •
0CRM_PRGRP1
•
0CRM_PRGRP2
•
0CRM_PRGRP3
•
0CRM_PRGRP4
•
0CRM_PRGRP5
See also You can find more information in the SAP Library documentation under Business Content -> Customer Relationship Management -> Marketing
Business Content for Marketing Optimization (new) Use With SAP CRM 4.0, there is now an option in the new campaign automation functionality for optimizing a campaign on the basis of data in SAP BW. For this, you use the ODS object Direkt Marketing Optimization (0CRM_ODMO) in SAP BW. This object is filled directly from SAP CRM.
See also For more information, see the documentation on this ODS object in the SAP Library under Business Content -> Customer Relationship Management -> Marketing -> ODS Objects.
Analysis of Competitor Products in Opportunities (New) Use As of Business Warehouse Release 3.2, you can analyze the competitor products that have been listed in opportunities in Customer Relationship Management. You can compare which products are in direct competition with your own products and whether you have won an opportunity against or lost to your competitor. You can also include product values so that you can analyze how much expected revenue you have won or lost. An example of this type of analysis is delivered in the standard system and is called Win/Loss Analysis of Competitor Products (technical name: 0CRM_C04_Q019).
Effects on Existing Data The following Business Content objects have been enhanced with the characteristics for the vendor (parent) product (0CRM_PAR), the competitor product (0CRM_CMPP) and the item type usage ( 0CRM_ITTU): •
DataSource: Opportunity Item (0CRM_OPPT_I)
•
InfoSource: Opportunity Item (0CRM_OPPT_I)
•
InfoCube: CRM Opportunity (0CRM_C04)
SAP AG
20
•
ODS: Opportunity (0CRM_OPPI)
If you have created your own queries and implement Customer Relationship Management Release 4.0 but you do not want to see the competitor product information, you need to filter the queries by leaving the value for the competitor product characteristic (0CRM_CMPP) empty. This filter has been implemented in the standard queries delivered in the Business Warehouse system.
Effects on Data Transfer If you wish to see the product values correctly for the competitor product, you must enter these values in the opportunity in the CRM system.
See also For more information about Business Content for CRM opportunities, see the SAP Library for Business Information Warehouse under Business Content -> Customer Relationship Managment -> Sales -> CRM Sales -> Opportunities. For more information about opportunities in CRM, see the SAP Library for Customer Relationship Management under Enterprise Sales -> Opportunity Management .
Opportunity Hierarchies in Business Warehouse (New) Use As of Business Warehouse Content 3.2 you can extract opportunity hierarchy data from mySAP Customer Relationship Management to the BW s ystem. In the CRM system, it is possible to link related opportunities with each other by using master and subopportunities, either by linking the opportunity header to another opportunity header, or from an opportunity item ito the header of another opportunity. This information is extracted to the BW system so that you c an drill down from a master opportunity to linked sub-opportunities in your opportunity analyses.
Effects on Existing Data The DataSource, InfoSource and InfoCube for the Opportunity Header have been enhanced with the following characteristics: •
Master Opportunity GUID (0CRM_MOPPG)
•
Master Opportunity Item GUID (0CRM_MOPPIG)
The DataSource, InfoSource and InfoCube for the Opportunity Item have been enhanced with the following characteristics: •
Master Opportunity GUID (0CRM_MOPPG)
•
Master Opportunity Item GUID (0CRM_MOPPIG)
•
Sub-Opportunity GUID (0CRM_SOPPG)
The system only fills these fields with the relevant IDs if sub-opportunities exist.
Effects on Data Transfer If you analyse opportunities at item level, reporting will be accurate as the items that are linked to subopportunities are only counted once in the sub-opportunity, and not in their master opportunity. However, if you wish to analyse opportunities at header level, you need to decide whether you wish to ignore or include the master opportunity data. You can do this with the Master Opportunity Flag characteristic (technical name: 0CRM_MSTOPP).
See also
SAP AG
21
For information about Business Content for opportunities, see the SAP Library for the SAP Business Information Warehouse under Business Warehouse -> Business Content -> Customer Relationship Management -> Sales. For information about CRM Opportunity Management, see the SAP Library for SAP Customer Relationship Management under Enterprise Sales -> Opportunity Management.
Analysis of Planning Accuracy (New) Use As of the 3.2 Content release of SAP BW, you can determine how closely the spare parts quantities and service durations in service orders within SAP Customer Relationship Management (CRM) match the actual quantities and durations confirmed. This gives you an indication of the accuracy of your operational planning in the short term, and enables you to adjust your product master data for spare parts and services to enable more accurate planning. You can determine planning accuracy for the following: •
Spare parts quantities
•
Service quantities (planning accuracy influences revenue)
•
Service duration (planning accuracy influences resource planning)
The following Business Content is available for the determination of planning accuracy:
New Key Figures Estimated Duration 0CRM_ORDTIM Confirmed Duration 0CRM_CNFTIM
New Units Unit - Estimated Duration 0CRM_ORDTUN Unit - Confirmed Duration 0CRM_CNFTUN •
The key figure and unit for estimated duration have been added to the following: DataSource in SAP CRM Release 4.0 CRM Service - Order Item Data (0CRM_SRV_PROCESS_I) InfoSource CRM Service - Orders (Item Data) (0CRM_SERVICE_PROCESS_I) ODS Object Service Orders (Item Data) (0CRM_PROI)
•
The key figure and unit for confirmed duration have been added to the following: DataSource in SAP CRM Release 4.0 CRM Service - Confirmation Item Data (0CRM_SRV_CONFIRM_I) InfoSource CRM Service - Confirmations (Item Data) (0CRM_SERVICE_CONFIRM_I) ODS Object Confirmations (Item Data) (0CRM_CNFI)
•
All of the key figures and units listed above have been added to the following: InfoCube Service Orders and Confirmations (Item Data) (0CRM_PRI)
New Query Planning Accuracy 0CRM_PRI_Q0106
SAP AG
22
Planning accuracy as a key figure is calculated as the planned quantity/duration from the service order as a quota of the quantity/duration actually confirmed: A value of 1 indicates perfect planning A value of less than 1 indicates an underestimation A value of more than 1 indicates an overestimation Note Data is aggregated according to product (material product for spare parts and service product for services), therefore you cannot determine planning accuracy on service order level.
Integration of Products in SAP BW (Enhanced) Use Enhancements to the Products business content were necessary due to developments made in the Products component in CRM 4.0: •
Decoupling of the Products component Products now consists of a central part and a CRM part. This has meant that some of the DataSources used for BW extraction have become obsolete, either because they have been made available in the central part under a new name or because some of the product attributes belong to the central part and others to the CRM enhancements. The DataSource 0CRM_PROD_ATTR has therefore been replaced by the two DataSources 0COM_PRODUCT_ATTR and 0CRM_PRODUCT_ATTR. DataSources that have become obsolete due to the decoupling are indicated as such in the system. The long texts indicate which DataSources should be used in future. Note that obsolete objects will not be maintained any longer and will be deleted in the foreseeable future. Obsolete
New
0CRM_GTIN_TYPE_TEXT
0COM_GTIN_TYPE_TEXT
0CRM_OBJECT_FAMILY_TEXT
0COM_OBJECT_FAMILY_TEXT
0CRM_PROD_ATTR
0COM_PRODUCT_ATTR/0CRM_PRODUCT_ATTR
0CRM_PROD_HIER
0COM_PRODUCT_HIER
0CRM_PROD_STAPROSYS0_TEXT 0COM_PRODUCT_STAPROSYS0_TEXT 0CRM_PROD_STAPROSYS1_TEXT 0COM_PRODUCT_STAPROSYS1_TEXT
•
0CRM_PROD_TEXT
0COM_PRODUCT_TEXT
0CRM_PROD_TYPE_TEXT
0COM_PRODUCT_TYPE_TEXT
Competitor Products CRM Release 4.0 allows information to be maintained on competitor products. Essential information is recorded by creating relationships to accounts, competitors, and your o wn products. To import this information into the Business Information Warehouse, three new DataSources were created, three ODS objects as the data target, and three InfoSources:
SAP AG
o
Accounts - DataSource 0CRM_IL_BPCMPT_ATTR - InfoSource 0CRM_IL_BPCMPT_ATTR - ODS object 0CRM_PRCU
o
Own products - DataSource 0CRM_IL_COMPET_ATTR - InfoSource 0CRM_IL_COMPET_ATTR - ODS object 0CRM_PRPR
o
Competitors - DataSource 0CRM_IL_PRCMPT_ATTR - InfoSource 0CRM_IL_PRCMPT_ATTR - ODS object 0CM_PRVD
23
Effects on Data Transfer To set up your system for using the new DataSources, proceed as follows: 1. Perform a delta initialization for the new data sources so that a delta is logged. Initialization without data transfer is sufficient. 2. Load the delta for the old DataSource. 3. Delete the DataSource assignment. Only by following this procedure can you avoid repeating a full update and still ensure that there is no loss of data.
Increased Flexibility in Response Prediction Modeling (new) Use By using response prediction models to analyze historic data in SAP BW, you can predict the responses and thereby the success of future campaigns. Alongside RFM Analysis, there is another more flexible option for defining response ra te models with Release SAP BW 3.2 Content. Besides using RFM response rate models, you can use the Business Add-In RSAN_RESPONSE_MODEL to make user-defined response rate models available, the prediction functions of which you program yourself.
See also For more information, see the SAP Library under Business Content -> Analytical Applications -> Customer Relationship Management -> Response Prediction Modeling.
Analysis of Service Plan Simulation Data (New) Use As of the 3.2 Content release of SAP BW, you can extract results of service plan simulations performed in SAP Customer Relationship Management (CRM). The service plan simulation function enables you to forecast the service orders within a particular timeframe, based on existing service plans. It enables you to predict future service volumes and resource requirements, and to perform operational planning based on information such as the planned dates for future service events, and planned order revenue. By extracting the results of service plan simulations to SAP BW, you can aggregate data and analyze it using different views. On the basis of the simulation results extracted to SAP BW, you can for example, determine the volume and monetary value of expected service orders, and the number of individual products, such as spare parts, that are required to fulfill those orders. This supports your operational planning by enabling you to plan your resources more accurately. You can also compare actual and forecasted data over a longer period of time to determine the accuracy of simulated data. The following Business Content is available for the storage and analysis of service plan simulation data:
New DataSources in mySAP CRM Release 4.0 CRM Service - Data from Planned Orders
0CRM_SRV_PRO_PLAN
Service Plan Names - DataSource for Texts 0CRM_SRVPLN_TEXT
New InfoSources CRM Service - Service Orders from Service Plan Simulation 0CRM_SERVICE_PROCESS_PLAN GUID CRM Service Plan
0CRM_SRVPLN
New Characteristics Service Plan Simulation Date
SAP AG
0CRM_FOCAAT
24
Planned Date of Service Order
0CRM_PLANAT
Characteristic: Simulation Header/Item 0CRM_FOCAFL Service Plan - Counter for Orders
0CRM_PLANCT
Time Stamp of Service Plan Simulation 0CRM_FOCATS Service Plan -Time Stamp ID
0CRM_PLANID
Service Order Valid
0CRM_FOCVAL
GUID CRM Service Plan
0CRM_SRVPLN
New InfoCube Orders from Service Plan Simulation 0CRM_FOCS
New ODS Objects Orders from Service Plan Simulation 0CRM_FOCA Service Plan - Time Stamp ID
0CRM_FOID
New Queries Determine ID of Last Service Plan Simulation
0CRM_FOID_Q0001
Resource Requirements and Service Volume
0CRM_FOCS_Q0001
Resource Requirements and Service Volume (Order Level) 0CRM_FOCS_Q0002 Comparison of Service Plan Simulations
0CRM_FOCS_Q0003
Note Since any number of service plan simulations can be performed for the same service plan within the same time period, duplication of data in queries is prevented as follows: Simulation results are stored in two separate ODS objects: •
Service Plan - Time Stamp ID This ODS object stores a record of the latest simulation performed per service plan, using a unique ID consisting of a combination of the service plan ID and a time stamp (the service plan ID is the key field in the database).
•
Orders from Service Plan Simulation
This ODS object stores transaction data records, each with the same unique ID as above. Before you use the queries Resource Requirements and Service Volume or Resource Requirements and Service Volume (Order Level), you need to execute the query Determine ID of Last Service Plan Simulation. This query reads the unique ID of the latest simulation performed for each service plan. You need to leave this query open when executing either of the resource requirements queries. When you execute either of the resource requirements queries, these compare the unique IDs in the ODS object for transaction data with the unique IDs determined by the query Determine ID of Last Service Plan Simulation. They display data only for those data records with identical IDs; the other data records are old records and are not displayed.
InfoCube for Strategic Service Planning (New) Use As of the 3.2 Content release of SAP BW, strategic service planning in SAP Strategic Enterprise (SEM) is supported by the transactional InfoCube Strategic Service Planning (0CSRVPLAN). Strategic service planning is supported in SAP SEM as of Release 3.5 in conjunction witn SAP BW Release 3.2. It enables you perform top-down and bottom-up planning of sales and profit.
SAP AG
25
Analysis of Service Quotation Data (New) Use As of the 3.2 Content release of SAP BW, service quotation data can be extracted from SAP Customer Relationship Management (CRM). Service quotations enable service providers to provide a no-obligation estimate of costs for services to a customer before the actual service order or service contract is created. A quotation comprises a list of services and parts to be delivered to the customer, stating prices as well as dates and terms of service delivery. By analyzing quotation data, you can, for example, determine the quotation success rate and the total number of quotations for your service organization. The following Business Content is available for the extraction and analysis of s ervice quotation data:
New Characteristics Status: Occurrence of Quotation Items 0CRM_STAQUO Status: Occurrence of Inquiry Items
0CRM_STAINQ
Start of Quotation Validity
0CRM_QUVALF
The above characteristics and the existing characteristic End of Quotation Validity (0CRM_VALIDT) have been added to the following: DataSource in SAP CRM Release 4.0 CRM Service - Order Header Data 0CRM_SRV_PROCESS_H InfoSource CRM Service - Orders (Header Data) 0CRM_SERVICE_PROCESS_H The new characteristic Start of Quotation Validity (0CRM_QUVALF) and the existing characteristic Status Expired (Quotation) (0CRM_STQEXP) have been added to the following: DataSource in mySAP CRM Release 4.0 CRM Service - Order Item Data 0CRM_SRV_PROCESS_I InfoSource CRM Service - Orders (Item Data) 0CRM_SERVICE_PROCESS_I
New ODS Objects Service Quotations (Header Data) 0CRM_QUTH Service Quotations (Item Data)
0CRM_QUTI
Note No predefined queries for service quotation analysis are provided in this SAP BW release.
Territory Management Analytics (New) Use As of Business Warehouse Release 3.2 you can analyze territory management data that you have created and used in mySAP Customer Relationship Management. This enables you to run reports on sales data according to territories, such as: •
Pre-Sales Investment per Customer by Territory
•
Number of Samples Given per Territory
•
Sales Orders per Territory
You can also use territory attributes in sales planning so that you can create analyses such as Comparison of Planned/Actual Sales Figures per Territory . To enable the extraction of territory master data and the territory hierarchy, the following Business Content has been developed:
SAP AG
26
DataSources in the CRM system: •
Territory (0CRM_TR_ATTR) Contains the territory master data
•
Territory Texts (0CRM_TR_TEXT) Contains the territory descriptions
•
Territory Hierarchy (0CRM_TR_HIER) Contains territory hierarchies
•
Territory Level Texts (0CRM_TRLV_TEXT) Extracts textual descriptions of territory levels in the CRM system
•
Territory Attribute Set (0CRM_TRAS_ATTR) Extracts the attributes used by the customer to define the territories, independently of the territory master data
•
Territory Person Responsible (0CRM_TRPR_ATTR)
Extracts the territorities that have been assigned to an employee responsible InfoSources in the BW system: •
Territory (0CRM_TR) Contains data from the Territory, Territory Texts and Territory Hierarchy DataSources
•
Territory Attribute Set (0CRM_TRAS_ATTR) Contains data from the Territory Attribute Set DataSource
•
Territory Person Responsible (0CRM_TRPR_ATTR) Contains data from the Territory Person Responsible DataSource
Effects on Existing Data In order to enable you to analyze existing sales information (such as sales orders, activities, or opportunities) according to territory, the standard DataSources, Online Data Stores, InfoSources, Info and MultiCubes have been enhanced with the attribute for the territory ID. The technical name of the characteristic for the territory is 0CRM_TR
See also For more information about the Business Content for Territory Management, see the SAP Library for the SAP Business Information Warehouse under Business Warehouse -> Business Content -> Customer Relationship Management -> Sales. For more information about Territory Management, see the SAP Library for Customer Relationship Management under Enterprise Sales -> Territory Management .
Changes in CRM IC WFM Content for BW 3.2 Use There have been material changes to the available content for IC WFM according to changes to the CRM (OLTP) Data Model. Among the changes are: •
Removel of Agent references in all content, the term Employee replaces usage
•
Concept of Agent Groups removed from Reports
•
Concept of Department and Location is replaced by CRM O rganizational Unit
SAP AG
27
•
Indicator and Workload Information is now available in the InfoCubes (but no in a formal report at this time)
•
Rule Violations are now referred to as Schedule Exceptions
•
Activities are now referred to as Scheduled Events
•
Promised Hours are now referred to as Set Shifts
•
Agents are now referred to as Employees
Effects on Existing Data This content is only valid for CRM 4.0 and higher!
Effects on Data Transfer Master Data extractors have been added for Time Intervals, Workload, and the Indicator concepts added to the BW Data Model. A process chain is also provided for easier management of Master Data. Transacational extractors are all delta enabled.
Warranty Analysis (New) Use As of the 3.2 Content release of SAP BW, you can extract warranty data from SAP Customer Relationship Management (CRM). Warranties are supported as of SAP CRM Release 4.0 and are managed as products. You can therefore perform the same controlling analyses for warranties in SAP BW as are already available for products, using the same Business Content. These analyses include profitability and cost-of-sales analyses. With this release of SAP BW, you can extract data representing the following relationships from SAP CRM: •
Warranties and installed base (IBase) components
•
Warranties and individual objects
•
Warranties and products
This information enables you to determine the number of IBase components, individual objects, and products for which a warranty is valid.
New DataSources in SAP CRM Release 4.0 Warranties for Installed Base Component 0CRM_IL_IBCWTY_ATTR Warranties for Individual Object
0CRM_IL_IOBWTY_ATTR
Warranties for Products
0CRM_IL_PRDWTY_ATTR
New InfoSources Relationship Between Warranty and IBase Component 0CRM_IL_IBCWTY_ATTR Relationship Between Warranty and Individual Object
0CRM_IL_IOBWTY_ATTR
Relationship Between Warranty and Product
0CRM_IL_PRDWTY_ATTR
New Characteristics Start of Warranty (Time Stamp)
0CRM_WTYBEG
Date Rule for Start of Warranty
0CRM_WTYBDR
SAP AG
28
End of Warranty (Time Stamp)
0CRM_WTYEND
Date Rule for End of Warranty
0CRM_WTYEDR
Product (Warranty)
0CRM_PRODWY
Product: Object Family (Warranty) 0CRM_OBJFWY Product ID (Warranty)
0CRM_PRIDWY
Product Type (Warranty)
0CRM_PTYPWY
New ODS Objects Relationship Between Warranty and IBase Component 0CRM_IBWY Relationship Between Warranty and Individual Object
0CRM_IOWY
Relationship Between Warranty and Product
0CRM_PRWY
SAP Media: Intellectual Property Management (New) Use The mySAP Media Intellectual Property Management solution (shipped with SAP CRM 4.0) can be used to represent the acquisition of rights to Intellectual Properties (IPs), management of the IP rights owned, which are acquired or generated and the sale of Intellectual Properties in your media company. The Business Content for Intellectual Property Management in SAP BW Release 3.20 provides you with the following functions for reporting: •
DataSource, Data targets and queries for the license sales contract
•
DataSource, Data targets and queries for license usage confirmations
•
DataSource, Data targets and queries for incoming royalties (license revenues)
•
DataSources, InfoObjects and data targets for representing various master data and master data relationships (e.g. interlinkage relationships to the IP, hierarchical attributes for IP rights dimensions)
License sales contract A right to an IP is sold using a license sales contract. Billing items in the license sales contract are represented for evaluation in SAP BW. Available rights dimensions (maximum of six), define the rights characteristics for a right to be exploited in a license sales contract item. Any combinations of (admissible) rights characteristics can be recorded for an item. Recording these types of combinations requires the contract value to be distributed between the actual characteristics available, so that a unique statement can be made on the value within an item. The same applies if s everal IPs are recorded for an item. A revenue plan is available in the CRM System for both cases, which specifies the distribution rate for item values. Distribution of values according to the revenue plan is based on the evaluation in SAP BW. Data targets for the license sales contract •
InfoCube: 0IPM_C01 License sales contract
•
ODS Object: 0IPM_DS01 License sales contract (billing item)
•
MultiCube: 0IPM_MC01 Incoming royalties and license sales contract
The InfoCube on the license sales contract (0IPM_C01) contains all items in a license sales contract and their characteristics by IP and rights dimensions and additional attributes (e.g validity range). Meaningful statements on the value of a contract can only be made using the items for which revenue distribution has been performed. These items are represented using a revenue object , whose attributes (rights characteristics and IP) reflect the actual rights characteristics in the respective item. Values for which revenue distribution has been performed from the license usage confirmation (see license usage confirmation section) are available for evaluation of the InfoCube. The net item value can be used for items that are not relevant to confirmation (pro rata license fees, single payments). Confirmation values in
SAP AG
29
the license sales contract are PP values (confirmed data refers to a current period). The net value of the billed item must be used to evaluate the net value of confirmation items for which revenue distribution has been performed, since the net contract value only contains ITD values (confirmed data is c umulated over all periods) for technical reasons. The ITD value is converted to a PP value using the difference calculation for billing where it can then be evaluated in a meaningful way. The Incoming Royalties and License Sales Contract (0IPM_MC01) MultiCube, which connects key figures and characteristics from the license sales contract and incoming royalties, is available for collective evaluation of the billed net value and the values confirmed in the contract. The License sales contract (billing item) (0IPM_DS01) ODS object is mandatory as a result of the After Image/Delete (AIMD) delta procedure for updating item data in the delta mode. In addition to update of the License sales contract (0IPM_C01), master data for the revenue object and the license sales contract is also updated from the License sales contract (billing item) ODS object (0IPM_DS01). License sales contract InfoSource and DataSource •
DataSource: 0IPM_SALES_CONTR_I IPM license sales contract (billing item)
•
InfoSource: 0IPM_SALES_CONTR_I IPM license sales contract (billing item)
The License sales contract (billing item) DataSource (0IPM_SALES_CONTR_I) contains all billing items in a license sales contract for which revenue distribution has been performed. Customizing settings for adding your own partner functions, date types and cumulation rules (confirmation values) to the license sales contract are available for the DataSource in the SAP CRM System under: Customer Relationship Management -> Industries -> Media: Intellectual Property Management -> Business Information Warehouse -> Settings for Date Types, Cumulation Rules and Partner Functions. These settings can be used to connect these enhancements to SAP BW quickly in a flexible manner. License usage confirmation Confirmations are used to report the actual data, which a licensee exploits (e.g sales volumes, advertising costs, audience figures), for a license sales contract to the licensor. This information is used to check the exploitation success of a rights sale and forms the basis for calculating license fees according to the contract type. Data targets for license usage confirmation •
InfoCube 0IPM_C03 License usage confirmation (item)
•
ODS object 0IPM_DS03 ,License usage confirmation (item)
The License usage confirmations InfoCube (0IPM_C03) can be used to perform a detailed analysis of the confirmation data for a license sales item from the license sales contract (if confirmation relevant item = billing request item). Note the following here: The license sales contract and the license usage confirmation can have different rights characteristics, since confirmation can take place at a more detailed level than that defined in the license sales contract. Example: The license sales contract was signed for the Europe region. However, confirmations are made at the level of the individual country, such as Germany, England, France etc. SAP BW represents the IPM-specific Customizing settings for confirmations. However, values to be confirmed can be made available according to your requirements using the Customizing settings for Intellectual Property Management. Individual enhancements also require the corresponding objects to be post-edited in SAP BW. Two different procedures for handling values are available for confirmations. The confirmed data either refers to a current period (PP, per period), or it is cumulated across all periods (ITD, inception to date) from the start of the contract validity period to the current point in time. Both procedures are supported by the License usage confirmations (item) InfoCube (0IPM_C03), in which separate key figures are created according to the procedure used. Note the following: Key figures of the ITD type cannot be handled in a cumulative way during the evaluation. Since confirmations are made in a specific way for a billing request item in the license sales c ontract, revenue-dependent distribution of confirmation values is not required. The License usage confirmation (item) (0IPM_DS03) ODS object is mandatory as a result of the After Image/Delete (AIMD) delta procedure for updating item data in the delta mode. The License usage confirmation (item) InfoCube (0IPM_C03) is updated from the License usage confirmation (item) ODS object (0IPM_DS03) License usage confirmation InfoSource and DataSource
SAP AG
30
•
DataSource: 0IPM_CONFIRM_I IPM License usage confirmation (item)
•
InfoSource: 0IPM_CONFIRM_I IPM License usage confirmation (item)
The IPM License usage confirmation (item) DataSource (0IPM_CONFIRM_I) contains all items in a license usage confirmation. Customizing settings for adding your own partner functions, date types and cumulation rules (confirmation values) to the confirmation document are available for the DataSource in the SAP CRM System under: Customer Relationship Management -> Media: Intellectual Property Management -> Business Information Warehouse -> Settings for Date Types, Cumulation Rules and Partner Functions . These settings can be used to connect these enhancements to SAP BW quickly in a flexible manner. Incoming royalties (billing documents) Incoming royalties are license revenues, which the licensor receives as a result of their license sale (controlled by the license sales contract) from the licensee, in return for transferring the usage of an IP for a defined period. As is the case for the license sales contract, various IP characteristics and/or several IPs, which require revenue distribution to be performed for the billed value, can be recorded for a billing item. Incoming royalties data targets •
InfoCube: 0IPM_C02 Incoming royalties (billing items)
•
ODS-Objekt: 0IPM_DS02 Incoming royalties (billing items)
•
MultiCube: 0IPM_MC01 Incoming royalties and license sales contract
The Incoming Royalties (billing items) InfoCube (0IPM_C02) contains all billed items in the license sales contract and enables the billed net value, for which revenue distribution has been p erformed, to be evaluated by various characteristics, such as the IP and rights dimensions and by additional attributes. As is the case in the license sales contract, the revenue objects is used to split revenues. The Incoming royalties and license sales contract MultiCube (0IPM_MC01), which connects key figures and characteristics from the license sales contract and incoming royalties, is available for collective evaluation of the billed net value and the values confirmed in the contract. Attributes in the license sales contract, which are not found in the billing document, are made available using navigation attributes for a master data object in the license sales contract. The Incoming royalties (billing items) ODS object (0IPM_DS02) is mandatory as a result of the After Image/Delete (AIMD) delta procedure for updating item data in the delta mode. The Incoming royalties (billing items) InfoCube (0IPM_C02) is updated from the Incoming royalties (billing items ODS object (0IPM_DS02). Incoming royalties InfoSource and DataSource •
DataSource: 0IPM_BEA_IPMI_I IPM Incoming royalties (billing items)
•
InfoSource: 0IPM_BEA_IPMI_I IPM Incoming royalties (billing items)
Extraction of billing items by the IPM Incoming royalties (billing items) DataSource (0IPM_BEA_IPMI_I) makes all billing items for incoming royalties (IPMI Billing Engine Application IPMI) available (revenue distribution has been performed for these items). No Customizing settings are available for the DataSource. IPM master data Interlinkages Interlinkages provide detailed information on the product, since they enable a relationship to be made between various product components. They are used to determine all materials or IPs, which have been recorded for an additional IP. Example of IP package part interlinkage: Interlinkages can be used to represent individual episodes and scales for a TV series. DataSources for representing Interlinkages •
0IPM_IL_IPACC_ATTR IP part
•
0IPM_IL_IPMAT_ATTR IP related material
•
0IPM_IL_IPPAC_ATTR IP package part
•
0IPM_IL_IPTTL_ATTR IP title
•
0IPM_IL_IPUCO_ATTR IP underlying component
SAP AG
31
The interlinkage for the relationship with partners, for which the 0CRM_IL_PRDBP_ATTR DataSource is available, is also used for the partner relationship. Revenue object The revenue object (InfoObject 0IPM_REVOBJ) adopts all actual rights characteristics that appear and/or several IPs recorded for a rights item. The rights characteristics and IP are managed as attributes for the revenue object, which can also be updated from the transaction data for the 0IPM_SALES_CONTR_I InfoSource (using ODS 0IPM_DS01). Attributes in the revenue object are defined as navigation attributes and made available as such in the InfoCubes for the license sales contract, incoming royalties and the collective Multicube for the license sales contract and incoming royalties. Master data for an item in the license sales contract Master data for this item (InfoObject 0IPM_ITMEX) can be used to represent attributes in the license sales contract for the billing document, which are not found in this document. Attributes in the revenue object are made available as navigation attributes in the InfoCube for incoming royalties and the collective Multicube for the license sales contract and incoming royalties. Attributes are updated using the 0IPM_SALES_CONTR_I InfoSource (from ODS 0IPM_DS01) when the transaction data is loaded. Hierarchical attributes for IP rights dimensions Any hierarchical attributes can be assigned to the IP rights dimensions in the IPM Customizing settings to define the rights characteristics. To make these available for the evaluation, hierarchy DataSources are provided, which determine the associated hierarchy for a dimension dynamically according to the Customizing settings. The same dynamic procedure applies for attribute texts for the IP rights dimensions DataSources for the IP rights dimensions hierarchies •
0IPM_RDIM01_HIER IP rights dimension 1
•
0IPM_RDIM02_HIER IP rights dimension 2
•
0IPM_RDIM03_HIER IP rights dimension 3
•
0IPM_RDIM04_HIER IP rights dimension 4
•
0IPM_RDIM05_HIER IP rights dimension 5
•
0IPM_RDIM06_HIER IP rights dimension 6
DataSources for extracting descriptions of hierarchical attributes •
0IPM_RDIM01_TEXT IP rights dimension 1
•
0IPM_RDIM02_TEXT IP rights dimension 2
•
0IPM_RDIM03_TEXT IP rights dimension 3
•
0IPM_RDIM04_TEXT IP rights dimension 4
•
0IPM_RDIM05_TEXT IP rights dimension 5
•
0IPM_RDIM06_TEXT IP rights dimension 6
The description of InfoObjects for IP rights dimensions (0IPM_DIM01 - 0IPMDIM06) is based on the IPM Customizing settings for dimensions 1-3. These should be adjusted as required in SAP BW according to the way in which the rights dimensions are used: •
0IPM_RDIM01 IP rights dimension (language)
•
0IPM_RDIM02 IP rights dimension (market)
•
0IPM_RDIM03 IP rights dimension (territory)
SAP AG
32
Interactive Scripting Evaluation for the IC WebClient Use You can use this function to evaluate customer responses to questions in interactive scripts. This function has been available for the Interaction Center (IC) WinClient since BW 2.1, support package 8. We are expanding this function to be available in the new IC WebClient. This function works together with mySAP CRM to track button clicks made by agents as they work through interactive scripts in the Interaction Center (IC) WebClient. When customers answer a question, agents choose a button to indicate the answer. This function records these button clicks. You can use this recorded information to display: •
An overview of all executed scripts
•
A particular script by questions and answers
•
A list of business partners who gave particular ans wers
•
A particular time period
In some cases, we created separate InfoObjects for the IC WebClient. In these cas es, both InfoObjects have the same title, with the client name following in parentheses. Example Interactive Script (IC WinClient) Interactive Script (IC WebClient)
3. Supplier Relationship Management Integration of SAP Content Integrator into SAP BW Use SAP Content Integrator (SAP CI) primarily serves to identify concurrent objects with different keys in a complex system connection, for example for several R/3 systems with SAP Enterprise Buyer , SAP BW ,and external systems. The information about identical or semantically-similar objects are stored by SAP CI in the form of key mappings (connections to the respective key). The mappings are available for SAP BW by extraction and are integrated into the existing master data model, especially into the consolidated InfoObjects. With SAP CI 2.0, the object partners (vendors) and product categories are available for key mapping. In doing so, a consolidated view within SAP Supplier Relationship Management - Global Spend Analysis , for example, is given for the company tasks for each vendor and also if vendors have different keys in different purchasing systems. Such an evaluation can be the basis for additional savings, for example, by renegotiating prices. In addition to key mapping, SAP CI supports the assignment of a standard category to a local product number. This is likewise transferred by extractor into SAP BW . The assignment of a standard category is preferred for key mapping in these cases in which similar categories cannot be uniquely assigned (for example, based on the level of detail of categorization).
Effects on Existing Data The master data non-cumulative is enhanced with information for specifying real objects (vendor, category), which is indicated with different keys. No changes ar e successful for transaction data.
Effects on Data Transfer Extract the group information from SAP CI in addition to the master and transaction data into SAP BW .
Effects on System Administration Add SAP CI as an additional source system to SAP BW .
SAP AG
33
See also You can find further information about integrating the SAP Content Integrator into the SAP BW in the SAP Help Portal under the Internet address help.sap.com -> mySAP.com Cross-Industry Solutions -> mySAP Business Intelligence -> SAP Business Information Warehouse -> Business Content -> Supplier Relationship Management -> Content Integrator.
Project Success of an Enterprise Buyer Implementation (New) Use The procurement controller (new role SAP_BW_SRM_PROC_CONTROLLER) can use a ne w report to judge how successful an Enterprise Buyer im plementation was and to what extent the technical scenarios are used. The report compares the number of purchase order transactions per scenario (standalone scenario, classic scenario, extended classic scenario, and pure R/3 scenario) over a certain period of time. To this end, a new Info Object 0SR_SCENA (Technical Scenario) has been incorporated in ODS object 0BBP_PO. This is able to determine the technical scenario during update of purchase order records from the source systems (Enterprise Buyer and R/3 MM).
Effects on Existing Data To use the report, you have to load the purchase order data from the different ordering systems (Enterprise Buyer, R/3 MM) again via INIT.
Effects on Customizing The system can only successfully identify the technical scenario, if you have defined the number ranges for purchase orders and purchase requisitions in Enterprise Buyer in the Implementation Guide (IMG) of the BW system. See Control Table for EBP Project Success.
New Functions for Vendor Evaluation in SRM Use Vendor evaluation has been extended to include the components Grouping of Criteria and Weighting of Groups/Criteria. To this end, the new InfoCube Weighting of Evaluations ( 0SR_VE_C1) has been defined, as have new Web Cockpits and Queries for evaluation of valuation data. These support the Sourcing, Vendor List , and Strategic Purchasing processes. With Grouping of Criteria, you assign criteria that are defined within a questionnaire for vendor evaluation to groups. You always carry out grouping with regard to a certain Enterprise Buyer system. Weighting of Groups/Criteria is based on the defined grouping. Here, you assign a weighting for each group and each criteria. Before you assign a weighting, you need to select the source system, the purchasing organization, the location, the product category, and the product. You can also enter an asterisk (*) as generic value.
Effects on Customizing To update the weighted valuations in the InfoCube 0SR_VE_C1, you have to carry out the following activities in the Implementation Guide (IMG) of the BW system: •
Vendor Evaluation: Carry out Grouping
•
Vendor Evaluation: Carry out Weighting
SAP AG
34
4. Supply Chain Management Business Content SCM Inventory Management Use The following list provides an overview of the new Business Content. •
•
New Queries o
0IC_C03_Q0001: Receipt and Issue Consignment Stock at Customer This query provides a stock overview of the value of the consignment stock at customer, broken down according to receipts and issues, as well as the consignment quantity at customer, listed as receipt quantity and issue quantity. The following evaluation levels are predefined: value, material, and calendar month. This query replaces objects 0IC_C01_Q0012 and 0IC_C01_Q0014.
o
0IC_C03_Q0017: Inventory Turnover This query provides information on how often the average valuated stock is used up. Calculation base:Total issue value / Valuated stock w ith aggregation average. This query replaces object 0IC_C01_Q0001.
o
0IC_C03_Q0018: Material Range of Coverage You can use this query to display, based on the stock value and issue value, how many days in the future the current s tock will be sufficient for covering stock issues. This query replaces the objects 0IC_C01_Q0002 to 0IC_C01_Q0007.
New MultiCubes o
0IC_MC03: Material Range of Coverage WIP This MultiCube contrasts the stock key figures with the values of half- finished products from production, in order to determine the material range of coverage WIP (WIP= work in process).
o
Associated Query 0IC_MC03_Q0001: Material Range of Coverage WIP You can use this query to display, based on the issue value, how many days in the future the current stock of half-finished products (WIP) will be sufficient for covering stock issues.
See also For more information, see the Knowledge Warehouse on SAP BW 3.2 Content.
5. Product Lifecycle Management Line Item Reporting for Commitments and Actual Data (Enhanced) Use As of SAP BW Release 3.20 content and Plug-In 2003.1 you can use DataSources for commitments line items for the following objects in SAP R/3 releases 4.0B to 4.70: Cost centers
0CO_OM_CCA_10
Orders
0CO_OM_OPA_7
WBS elements
0CO_OM_WBS_7
Networks
0CO_OM_NTW_3
Network activities
0CO_OM_NWA_3
SAP AG
35
Network activity elements 0CO_OM_NAE_3 Maintenance orders
0PM_OM_OPA_3
The commitments extractors can work with deltas starting from the SAP R/3 Enterprise 4.70 Release onwards. ODS objects for line item reporting are delivered for all commitment DataSources and for actual data. It is not possible, however, to update data in the existing InfoCubes and to define queries for these objects in the current release. If required, you can realize this in a customer project.
See also For more information, see SAP Note 590562.
Business Content for cProjects (Enhanced) Use As of SAP BW Release 3.2 you can use the following Business Content enhancements for cProjects: Replication of cProjects Data in the SAP R/3 Project System With the new report 0CPR_C03_Q0001: Replication: Planned/Actual you can evaluate data that was replicated from cProjects into the SAP Project System (PS) together with PS data. To enable this, the existing InfoSources (type attribute) of PS objects are enhanced to include the corresponding cProjects InfoObjects. You can now select queries using cProjects project definitions and find and display the replicated SAP R/3 projects for project definitions. You can also assign costs to cProjects projects using the projects in PS. SAP R/3 Accounting Integration with cProjects In cProjects you have the option of assigning a c Projects project definition to an internal order in SAP R/3. In this way a project in cProjects can carry costs using an internal or der. The new InfoSource 0GECCO_ORDER_ATTR provides information using the connection to a project in cProjects as an additional attribute of the internal order master data. You can use the following new reports for evaluating: 0CPR_C03_Q0002: Internal orders (created in cProjects): Planned/Actual 0CPR_C03_Q0003: Internal orders (created in cProjects): Overall Plan/Actual/Commitments 0CPR_C03_Q0004: Internal orders (created in cProjects): Budget/Actual/Commitments Delta Management for Transaction Data As of SAP BW content Release 3.2 you can use a delta update. For more information, see the documentation on DataSources. Delta Management for Master Data (Attributes and Texts) As of SAP BW content Release 3.2 you can use a delta update for DataSources of type ATTR TEXT. In these DataSources only changed master data is updated, and not deleted master data. For more information, see the documentation on DataSources.
Business Content for Workforce Management Core (New) Use As of SAP BW Release 3.2, you can evaluate data from Workforce Management Core (WFM Core) in the SAP Business Information Warehouse (SAP BW). WFM Core is a planning service that you can use to manage assignments of personnel resources to workforce requirements. You can use the following new reports to represent an employee's availability, working time, and free capacity: •
0WFM_C01_Q0001: Employees' Availability
•
0WFM_C03_Q0001: Availability with Assigned Projects
SAP AG
36
•
0WFM_C01_Q0002: Availability in Detail
The following new objects have been created: DataSources •
0WFM_BOOKING_TYPE_TEXT: Extraction of Booking Type Text
•
0WFM_CAPACITY: Extraction of Gross and Net Availability
•
0WFM_WORKTIME: Extraction of WFM Working Time
•
0WFM_ASSIGNMENTS: Extraction of WFM Assignments
InfoSources Transaction data: •
0WFM_WORKTIME: Working Time
•
0WFM_ASSIGNMENTS: Assignments
•
0WFM_CAPACITY: Availability Gross/Net
Master data: •
0WFM_BOOKTP: Booking Type
•
0WFM_EXT_ID: WFM Resource ID
InfoCubes •
0WFM_C01: WFM Availability of All Employees
•
0WFM_C02: WFM Assignments cProjects
•
0WFM_C03: WFM Availability with Assigned Projects
Evaluation of Dangerous Goods Shipments (New) Use By extending the Delivery Data of Shipment Stages InfoCube (0LES_C13) in the SAP application component Transportation (LE-TRA), you can now also evaluate shipments that contain dangerous goods data. This means that you can answer the following question, for example: What quantity of dangerous goods class 3 was transported by road in the year 2002? The InfoCube was extended to include the following characteristics that originate in Dangerous Goods Management (EHS-DGP): •
Identification Number
•
Identification Number Type
•
Dangerous Goods Regulation
•
Dangerous Goods Mode of Transport Category
•
Dangerous Goods Class
•
Packing Group
•
Not Dangerous Goods Full Transport
SAP AG
37
•
Validity Area
This extension applies from SAP BW 3.0B.
Requirements To be able to fill the InfoCube 0LES_C13 with dangerous goods data, you will require either a Release of SAP Environment, Health and Safety (SAP EH&S) or SAP R/3. You can use the function from the following Releases: •
Release 2.7B of SAP EH&S
•
SAP R/3 Enterprise Extension 1.10 from Plug-In 2001.1
Further notes The corresponding InfoSource is Shipment Delivery Item Data per Stage (2LIS_08TRTLP). For data extraction, the DataSource Shipment Delivery Item Data per Stage (2LIS_08TRTLP) is used with the extractor MCEX_BW_LO_API. The characteristics are filled from the following fields: Characteristic Field 0EHS_DGNU
DGNU
0EHS_TKUI
TKUI
0EHS_LWDG
LWDG
0EHS_MOT
MOT
0EHS_DGCL
DGCL
OEHS_PGRO
PGRO
0EHS_DGNHM DGNHM 0EHS_RVLID
RVLID
6. Financials DataSource 0EC_PCA_3 for Line Item Delta Extraction Use As of SAP BW 3.20 Content-Release / PI 2003.1, a new DataSource 0EC_PCA_3 is provided that can be used to upload GL PCA line items. As with the generic FISL line item extractors, changes to the DataSource 0EC_PCA_3 can be evaluated without carrying out lengthy evaluation runs.
Business Content for Dispute Management Use In SAP BW 3.2, you can use various tools and info providers to create reports for processes and functions for Dispute Management which is part of Financial Supply Chain Management. You can create reports about the master data of Dispute Management using numerous characteristics from different dimensions and the elementary key figures of Dispute Management, such as the original amount, the current amount, paid amount, and so on. You can also create reports about the process integration data with the underlying Accounts Receivable Account system. Of particular interest are the evaluations that contain Dispute Management data and Accounts Receivable data in equal quantities. Different info sets enable seamless integration of the data.
SAP AG
38
In addition to standard queries, that contain the open dispute cases sorted on a time basis, you can also use master data tables, info sets, and operational data stores (ODS) to create reports. The modular definition of the extraction interfaces and info sources also enable you to model your own info providers simply, using the methods of the flexible master data update.
Generic FI-SL Line Item Extractors for Transporting the Delta Upload to the SAP BW System Use As of SAP BW 3.20 Content Release / PI 2003.1, you can in addition to the existing totals records generate line item extractors for your FISL ledgers for data extraction to the SAP BW system. The transaction data can be displayed at totals record l evel as both actual and plan data, while at the line item level it can be displayed as actual data only. Generate Transfer Structure for Totals Tables In addition to generating the transfer structure that you use to transfer transaction data from your ledgers to the BW, this activity also gives you the opportunity to choose whether to generate the extract structure for totals records (actual/plan data) and/or line items (actual data) Define and Assign DataSource In addition to generating the totals record DataSource for an FI-SL ledger, you c an now create DataSources for FI-SL line items. Notes: If you have implemented PlugIn 2003, you can also use the generic FI-SL line item extractors for earlier SAP BW releases. To implement the FI-SL line items extractors, however, you must be using at least R/3 Release 4.0. In principle, a Delta upload can be carr ied out for the line item DataSource. As of Release SAP R/3 470, Delta uploads can also be carried out for the totals record DataSource. A Delta upload can also be c arried out for totals records from earlier than Release SAP R/3 470. For further information, see note 328197.
Effects on Existing Data SAP provides 0EC_PCA_3 as a new DataSource for SAP BW 3.20 Content-Release / PI 2003.1. This DataSource is only relevant for EC-PCA (Profit Center Accounting). For FI-SL ledgers, you can generate any number of DataSources. These DataSources are generated with the transactions BW01 (generate e xtract structure for FI-SL table) and BW03 (assign DataSource to a ledger ) using the naming convention 3FI_SL_xx_SI, with xx representing the ledger.
Financial Statement and Profit & Loss Statement Use From SAP BW 3.20 Content-Release, the balance sheet and profit & loss statement can be depicted in the Business Information Warehouse (BW) on the basis of SAP BW Release 3.0B. This is displayed in accordance with any financial statement /P&L structure extracted from the SAP R/3 system. In particular, the system performs both balance-specific assignment of accounts (balance sheet contra items) and calculation of retained earnings (profit / loss). The query results correspond to the following evaluations in the SAP R/3 s ystem: •
Report RFBILA00 (output with ALV Tree Control)
•
Drilldown reports 0SAPBLNCE-* (report type: financial statement analysis)
The financial statement and P&L statement can be reported either according to period accounting or cost-ofsales accounting. Period accounting: Using the query financial statement and P&L: actual/actual comparison (0FIGL_VC1_Q0001)
SAP AG
39
This query is based on the virtual InfoCube General Ledger: Financial statement and P&L (0FIGL_VC1). The virtual InfoCube itself contains no data. When the query is executed, the system reads the data from the existing Basis Cube General Ledger: Transaction figures (0FIGL_C01). Cost-of-sales accounting: Using the query financial statement and P&L (cost-of-sales accounting): actual/actual comparison (0FIGL_VC2_Q0001) This query is based on the virtual InfoCube Cost-of-sales Ledger: Financial statement and P&L (0FIGL_VC2). The virtual InfoCube itself contains no data. When the query is executed, the system reads the data from the new Basis Cube Cost-of-sales Ledger: Transaction figures (0FIGL_C02). Note: It is necessary to use queries based on virtual InfoCubes in order to be able to report the data according to the above-mentioned financial statement/P&L structures.
Delta Extractors FI-AP/AR/GL Use After the initial selection, only data changes that have taken place since the most recent extraction are transferred. This improves system performance for the following: •
Data extraction of FI-AP/AR/BL transaction figures
•
Customer payment history
Transaction figures are also extracted for special general ledger transactions and credit management data. The extractors allow separate init and delta loads. All DataSources therefore have their own selection parameters. The init selections are stored and checked with the relevant DataSources. The delta method is carried out using a time stamp procedure. In addition to registering changes to transaction figures, the system also registers creation or deletion of data in the change table. The following is a list of new transaction figure extractors for which a delta method can be used: •
0FI_AR_6
•
0FI_AR_7
•
0FI_AP_6
•
0FI_AP_7
•
0FI_GL_6
•
0FI_GL_7
The following is a list of new credit management data extractors for which a delta method can be used: •
0FI_AR_8
•
0FI_AR_9
•
0FI_AR_10
The following master data extractors allow full upload: •
0COMP_CODE_CCA_PERM (Customizing tables)
•
0CRED_GROUP (texts for credit groups)
Effects on Existing Data The delta extractors replace these existing full upload extractors: •
0FI_AR_1
SAP AG
40
•
0FI_AR_5
•
0FI_AP_1
•
0FI_GL_1
•
0FI_GL_2
Master Data for Orders and WBS Elements (Enhanced) Use As of SAP BW Release 3.20 the following InfoObjects are changed over to the flexible master data update: Appropriation request 0APPR_REQU Order
0COORDER
WBS Element
0WBS_ELEMT
The InfoObjects above are enhanced to include additional attributes: Approval year
0APPR_YEAR
Program definition
0PROG_DEF_S
Investment program position 0PROG_POS Here it is possible to extract assignment information about investment program positions in addition to the old attributes, using the following DataSources: Program assignment of appropriation request 0IM_FA_IP_7 Program assignment of orders
0IM_FA_IP_8
Program assignment of WBS elements
0IM_FA_IP_9
In this way you can use the investment program position as a navigation attribute for all existing InfoCubes for these InfoObjects so that cross-project and cross-order evaluations are possible in the hierarchy of the investment program for all key figures available for these InfoCubes. Previously you could evaluate only key figures on the program level defined in the InfoCube 0IMFA_1. Now you can use a variety of key figures on the program level. For example: •
Dates (PS)
•
Payments (PS)
•
Statistic key figure (PS; CO-OM)
•
Progress values (PS)
Note the following limitations: •
You can use the new solution only for the program assignments in one single approval year.
•
An evaluation for a percentage breakdown of the assignment of WBS elements and orders o
According to various investment program positions
o
According to budget type
Or appropriation requests o
According to investment reason
o
According to requesting organizational units
is possible only by using the InfoCube 0IMFA_1.
SAP AG
41
Crystal Reports for Formatted Financial Statements Use As of the 3.2 Content release of SAP BW, SAP delivers the following crystal reports in conjuction with the underliying BW queries for consolidated financial statements used in SEM-BCS. These crystal reports conform with the general layout requirements of financial statements and act as good examples for customers to create their own formatted reports. Crystal Reorts : 6KJIDB0DKEG71H9G9Z1IR468I Balance Sheet Current Year C2R257DL4WCKEG7O27Z73705U Balance Sheet with 2 Year Comparison 9LMMD1MVTL817FRN6LG6AQKFW Balance Sheet with 5 Year Comparison 9HYGOFC4AQBM8FGJWUEKTF9PU Asset History Sheet BOL8U6V4705BLFJOBE1VNBTA4 Income Statement with Two Year Comparison BW Queries: 0BCS_V11_Q051_CR Balance Sheet Current Year 0BCS_V11_Q052_CR Balance Sheet with 2 Year Comparison 0BCS_V11_Q053_CR Balance Sheet with 5 Year Comparison 0BCS_VC11_Q014 Asset History Sheet 0BCS_VC11_Q054_CR Income Statement with Two Year Comparison
7. Human Capital Management Business Content for the SAP Learning Solution (New) Use Business Content is now available in the SAP Business Information Warehouse (SAP BW) for Release LSO 200 of the SAP Learning Solution. On the technical side, there are two new InfoCubes available: •
Training Management (0LSO_C01) This InfoCube contains all of the transaction data for participation bookings and cancellations transferred from the source system. Data is provided for the InfoCube by the Info Sources Participation (0HR_LSO_1) and Cancellation (0HR_LSO_2). The InfoCube contains the general key figures Number of Cancellations (0CANCEL_NO), Number of Participants (0BOOKING_NO), Cancellation Fee (0CANCELFEE), Participation Fee (0BOOKINGFEE), Course Duration in Hours (0TRAINHOURS), Course Duration in Days (0TRAINDAYS), and Course Costs (0TRAINCOSTS). In addition, calculated key figures (e.g average cancellation fee) and restricted key figures, that is, key figures that depend upon certain characteristics (e.g. billed participation fees, number of internal participants) are delivered. The time dimensions available for evaluations are calendar day, calendar year, calendar year/quarter, and calendar year/month. Several structures are delivered with the InfoCube that contain key figures in combination with certain calculation rules. These structures provide you with swift, easy access to frequently used evaluation structures (such as comparison previous year/current year) including details of the absolute and percentage difference of the results. In the update rules, several fields are read from master data tables and written to the InfoCube as characteristics. This requires that the master data is loaded and activated before the InfoSources.
•
Resource Reservation (0LSO_C02) This InfoCube contains transaction data about resources that is transmitted from the source system. The Resource Reservation InfoSource (0HR_LSO_3) provides the data for the InfoCube. The InfoCube contains the general key figures Reservation Period in Days (0RODAYS), Reservation Period in Hours (0ROHOURS) and Resource Costs (0ROCOSTS). A structure is delivered with the InfoCube. Structures contain key figures in combination with calculation rules. They give you easy access to frequently used evaluation structures (as in this
SAP AG
42
case Comparison Previous Year/ Current Year) with details of the absolute and percentage difference in the results. The time dimensions available for evaluations are calendar day, calendar year, calendar year/quarter, and calendar year/month. The role Training Manager is the strategic business partner of the human resources manager and the line manager. He or she has an e xtensive knowledge and expertise in the area of training and is in a position to align corporate training and education to the strategic goals of the enterprise. The training manager is responsible for planning activities and the overall coordination of training activities in the enterprise. Reporting for training data is of great significance in this context. The role Employee Manager has personnel managerial responsibility for employees. As a manager, he or she is responsible for the further training and education of the employees, among other duties. The manager should use the reporting facilities available to monitor and keep track of the training and education of the employees in his or her area of responsibility. Note Only the active plan version is included for data extraction from SAP R/3 to the BW System. The DataSources for providing Business Content for the SAP Learning Solution are available as of Release LSO 200 .
See also For more information, refer to the documentation for SAP BW 3.2 Content under Business Content -> Personnel Management -> SAP Learning Solution.
Business Content for Objective Setting and Appraisals (New) Use The following Business Content is now available in the SAP Business Information Warehouse (SAP BW) for the mySAP HR solution Objective Setting and Appraisals, which was newly developed with SAP R/3 Enterprise HR Extension 1.10. •
Objective Setting and Appraisals: Status The query available for status management Status Overview of Appraisal Documents (0PAH_IS02_Q0001) allows you to determine the processing percentage of objective setting and appraisals documents for a particular organizational unit for instance.
•
Objective Setting and Appraisals: Averages The queries available for determining averages allow you to determine the average appraisal values, analyze the target and actual values of a specific template, or display the average values as a time series. The following queries are available for this purpose:
•
o
Appraisal Average for Overall Appraisal (0PAH_IS01_Q0001)
o
Appraisal Average for Criterion (0PAH_IS01_Q0002)
o
Average of All Aspects for Overall Criterion (0PAH_IS01_Q0003)
o
Average of All Aspects for Criterion (0PAH_IS01_Q0004)
o
Time Series for Appraisals (0PAH_IS01_Q0005)
Objective Setting and Appraisals: Distribution The queries available for distribution values allow you to analyze the distribution of appraisal values and target and actual values in relation to a particular template you have selected. The following queries are available for this purpose: Appraisal Distribution for Overall Appraisal ((0PAH_IS01_Q0006) Appraisal Distribtuion for Criterion (0PAH_IS01_Q0007) Appraisal Distribution for Criterion (Point Scale) (0PAH_IS01_Q0008)
•
The data you can report on is stored in the following InfoProviders (ODS objects and InfoSets):
SAP AG
43
•
Appraiser per Document (0PAH_DS01)
•
Appraisee per Document (0PAH_DS02)
•
Appraisals (0PAH_DS03)
•
Appaisee Employees per Document (0PAH_DS04)
•
Appraisals and Appraisees (0PAH_IS01)
•
Appraisals per Employee (0PAH_IS02)
•
The role of Personnel Development Manager has been brought into alignment with the new functions and contains additional reports for the status, average values, and distribution of Objective Setting and Appraisals.
•
The following new DataSources are available: o
Appraiser per Document (0HR_PA_HAP_01)
o
Appraisee per Document (0HR_PA_HAP_02)
o
Appraisals (0HR_PA_HAP_03)
o
Appraisal Document Attributes (0HAP_ID_ATTR)
o
Appraisal Document (0HAP_ID_TEXT)
o
Template (0HAP_VA_TEXT)
o
Criteria Group (0HAP_VB_TEXT)
o
Criterion (0HAP_VC_TEXT)
o
Row (0HAP_ROW_ID_TEXT)
o
Status of Appraisal D ocument (0HAP_STATUS_TEXT)
o
Substatus of Appraisal Document (0HAP_SUBSTA_TEXT)
o
Value (0HAP_VALUE_TEXT_WERT
o
Value List (0HAP_V_LIST_TEXT)
Further notes When data is extracted from the R/3 System and transferred to the BW system, only the active plan version is taken into account. The DataSources for supplying Business Content are available for Objective Setting and Appraisals as of SAP R/3 Enterprise HR Extension 2.0 .
See also For more information, see the documentation on SAP BW 3.20, under Business Content -> Human Resources -> Objective Setting and Appraisals.
SAP AG
44
Business Content for Budget Planning and Position Control (Enhanced) Use As of SAP Business Information Warehouse (SAP BW) Content 3.2, you can also transfer personnel cost savings and overruns of personnel costs from Budget Planning and Position Control (PBC) to the Business Information Warehouse (SAP BW). In addition, it is possible to perform a commitments/actuals comparison of the commitment data from Budget Planning and Position Control (PBC) with the actual data from Payroll per person.
New DataSources in SAP R/3 Personnel Cost Savings (0PSM_PBC_02)
New Objects in SAP BW 3.2 Content •
Multi Provider Commitments/Actuals Comparison (0PSM_MP01) This Multi Provider is used in the area of Budget Planning and Position Control (PBC) to compare the commitments data with the actual data for accounted person. The data necessary for this is read from the Commitment Line Items Budget Planning and Position Control (0PSM_C40) and Revision Info on Postings for Budget Planning and Position Control (0PY_PPC02 ) InfoCubes.
New Characteristics in SAP BW 3.2 Content •
Number of Commitment Run (0PSM_RUNID)
•
Start Date of Commitment Run (0PSM_SDATE)
•
Start Time of Commitment Run (0PSM_STIME)
•
Logical System of Source Document (0PSM_AWSYS)
•
Reference Key (0PSM_AWKEY)
•
Reference Document Position (0PSM_AWPOS)
•
Reference Procedure (0PSM_AWTYP)
New Key Figures in SAP BW 3.2 Content •
Personnel Cost Savings: Open Amount (0PSM_OPENAM) In this key figure, the open amount of a personnel cost saving that has not yet been transferred to the budget is saved. This amount corresponds to the amount in the funds block in Funds Management .
New Queries in SAP BW 3.2 Content •
Personnel Cost Savings/Overruns (FM View) (0PSM_C40_Q0006) Displays the personnel cost savings or overruns in FM account assignment
•
Personnel Cost Savings/Overruns (FM View) (0PSM_C40_Q0007) Displays the personnel cost savings or overruns with FI assignment
•
Personnel Cost Savings/Overruns (CO View) (0PSM_C40_Q0008) Display the personnel cost savings or overruns with the CO assignment
SAP AG
45
•
Commitments/Actual Comparison (PBC) (FM View) (0PSM_MP01_Q0001) Displays Commitment/Actual comparison per employee with Funds Management assignment
•
Commitments/Actual Comparison (PBC) (CO View) (0PSM_MP01_Q0002) Display Commitment/Actual comparison for each employee with CO assignment.
Key figures MTTR and MTBR for plant maintenance and customer service. Use From SAP BW 3.2, the key figures MTTR (Mean time to repair) and MTBR (Mean time between repair) are available. The following objects are affected by this: •
The extract structures MC17I00NTF and MC18I00NTF and the communication structure MCQMELB of the Data Source 2LIS_17_I0NOTIF (maintenance notification) and 2LIS_18_IONOTIF (service notification) were enhanced by adding the following fields: o
AUSVN - Start of malfunction date
o
AUSTV - Start of malfunction time
o
AUSBS - End of malfunction date
o
AUZTB - End of malfunction time
•
The Data Source 0EQUIPMENT_ATTR was enhanced by adding the field INBDT (equipment startup date).
•
The Data Source 0FUNCT_LOC_ATTR was enhanced by adding the field DATAB (functional location start-up date).
There are also two new ODS objects, as well as a new Query: •
0PM_DS01 (Outage times)
•
0PM_DS02 (MTTR/MTBR)
•
0PM_DS02_Q0001 (MTTR/MTBR)
Effects on System Administration To get the key figures into the ODS objects and into the Query, you must plan the info packages on the process chains 0PM_INIT_P01 and 0PM_DELTA_P02 in the areas of plant maintenance and c ustomer service. You must also activate and execute the chains.
8. Industry Solutions Apparel and Footwear Business Content for SAP Apparel and Footwear (SAP AFS) Use
SAP AG
46
As of SAP BW 3.2, there is an extended Business Content for SAP AFS. The extended Business Content is primarily used to supply data to the Business Package for Resellers (Apparel and Footwear). For more information, see the Business Package for Resellers documentation (Apparel and Footwear). The main focus of the extension is reporting on document level in SD. The Business Content for this AFS Business Package has been extended by key figures, characteristics, queries, Web templates, and ODS objects. The following ODS objects have been created for SAP AFS: •
AFS sales orders (0AFSD_DS1)
•
AFS contracts (quantity contracts) (0AFSD_DS2)
•
AFS invoicing (0AFSD_DS3)
As of SAP BW 3.2, the role AFS: Reseller is also available.
Automotive Business Content for Warranty Processing in Discrete Industries (New) Use As of SAP BW 3.2 Content, you can evaluate data from Warranty Processing (IS-A-WTY) in the SAP Business Information Warehouse (SAP BW). Warranty Processing, a component in the mySAP Automotive solution, is targeted at manufacturers and importers of complex products as well as their suppliers. Although developed as part of the mySAP Automotive solution, it can be used throughout all the discrete industries to easily handle a large number of warranty claims and, as far as possible, automatically. The queries delivered by SAP concentrate on listing the top N claimants, the top N labor operations, the total number of objects recalled, and the failure frequency of claimed materials. The objects of the content are located in the new Warranty Processing info area. InfoProvider 0AU_WTY contains the following: •
InfoCube Completed Claims 0AU_WTYG1
•
Master data
•
o
Recall Number 0AU_RCL
o
Vehicle GUID 0AU_WVHGUID
ODS objects o
Warranty Claim Header 0AU_WTYH
o
Warranty Claim Version 0AU_WTYV
o
Warranty Claim Items 0AU_WTYI
o
Warranty-Related Counters and Limits 0AU_WTYM
o
Warranty Version and Item Measurement Documents 0AU_WTYMP.
See also The DataSources for the Warranty Processing Business Content are available as of DIMP 4.71. For more information, see the SAP Library documentation for SAP BW 3.20 under Business Content -> Industry Solutions -> Automotive.
SAP AG
47
Banking Link from CML to SAP BW Use Core Banking Mortgage Loans (FS CML) offers a link to the SAP Business Data Warehouse, providing additional reporting options to the Queries and Drilldown reporting tools contained in CML. Business Content has been developed for these reports, taking account of the operational and strategic management reporting in the loans area. The Business Content supplied forms a basic framework and allows you to include your important master data and all flow data in the reports. Delta mechanisms are also provided for the upload. These are particularly relevant for objects with large volumes of data that can affect runtime. They contain delta management for the loan master data and the flow data. Typical target groups: •
Clerks/ administrators
•
Planning and controlling employees working in the company's own credit control area.
•
Employees responsible for strategic management decisions
Insurance New Extractors in FS-CM Use As from Insurance Release 4.71, the following additional transaction data extractors are available for integration with the BW system (Business Information Warehouse). They mainly deliver specific information on health insurance to the BW system: •
0ISCM_ACTIVITY_01 Enables extraction of data fields in the Activities application table (ICLACTIVITY), which contains information on the claim activities. To enable calculation of lead times with activities (history times), historicized activity data (ICSACTIVITY) is extracted to the BW system with this extractor.
•
0ISCM_DIAGNOSIS_01 Enables extraction of data fields in the Diagnoses application table (ICLDIAGNOSIS), which contains information on the diagnosis.
•
0ISCM_PROCURE_01
Enables extraction of data fields in the Procurement application table (ICLPROCURE), which contains information on the claim item groupings. The claim item groupings are a technical construction with attributes for procurement documents (such as request, prescription, approval, cost estimate, invoice). The master data required for these transaction data extractors in the form of texts and attributes is also provided as master data extractors.
SAP AG
48
Healthcare Enhancements to Business Content SAP Healthcare Use The following InfoCubes have been remodeled for this release: •
Case-Related Costs (0HC_C26)
•
Organizational Unit-Related Costs (0HC_C27)
To ensure that you are also able to use the delta extraction from Controlling for case-based orders when Healthcare information is subsequently modified, the InfoObject Case (0HC_PATCASE) is now available to you as a master data InfoProvider . This means that information from different ODS objects that had to be updated in the InfoCube Case-Related Costs in earlier releases can now be saved directly as master data attributes for the case (for example, DRG, MDC, admitting and discharging department). As of this release, the InfoObject Material (0MATERIAL) is available to you in the InfoCube Case-Related Costs and in the InfoCube Organizational Unit-Related Costs. This InfoObject is also defined as a master data InfoProvider. This means that you can now also use the Healthcare-specific attributes of the material here, as was already the case in the SCM Content. The redesign of the above mentioned InfoCubes made necessary a redesign of the respective queries. As a consequence, characteristics have been removed from the queries and have been turned into navigation attributes (for example, DRG). A number of new queries have been made available to you in this release. These include the query Material Analyses with Case Reference. The patient name is now transferred in relation to the institution. The name format corresponds to the format you defined in SAP Patient Management.
Media SAP Media: Changes to Business Content for Advertising Management Use In SAP BW 3.2 , the following changes are available with the SAP Media Business Content for the Advertising Management component: •
InfoCube Billing Document (0MEMAMC01) Correction to the billing quantity relevant for update: The plus or minus sign is only inverted in the update rule, for example, when reversing a billing document, for quantity analysis. Previously, the plus/minus sign was sometimes interpreted incorrectly in exceptional cases, that is to s ay, when the gross value of the billing document was 0. This meant that the cumulation of the quantities was also displayed incorrectly in the evaluation. This correction only applies to the way in which the billing quantity is displayed. For further information on the corrections to the billing quantity relevant for update, see the OSS note 588743.
•
ODS objekt Billing Datasets (0MEMAMO08) and InfoCube Schedule Line/Ad Spec (Ads Only) (0MEMAMC03) Correction to update rules for reversed order objects: Reversals for the order (billing datasets and schedule lines/ad specs) are transferred preceded by a plus sign to SAP BW . Until now, the plus/minus sign was not inverted but instead, the reversed order objects were excluded from the query by filtering the reversal indicator. In some cases, this procedure led to an incorrect cumulation of the key figures being analyzed. For this reason, the inversion of the plus/minus sign has been integrated in the update rule for the InfoCube. If a reversal indicator is selected for an order object, the order record is now displayed with a minus sign.
SAP AG
49
You can use the ODS object 0MEMAMO08 for evaluations, but the object is principally designed to format the data for the InfoCube Billing Datasets (Ads Only) 0MEMAMC02 so that the correction of the update rule now means the reversed order objects are now also updated in this InfoCube according to their plus/minus signs. The filter criterion for reversed order objects has also been removed from the following queries to reflect the change: o
0MEMAMC02_Q0001: Ad orders: billing datasets (IS-M < 4.63)
o
0MEMAMC02_Q0002: Ad orders: billing datasets
o
0MEMAMC02_Q0003: Campaign ad orders: billing datasets
o
0MEMAMC03_Q0001: Ad orders: schedule lines/ad specs (IS-M < 4.63)
o
0MEMAMC03_Q0002: Ad orders: schedule lines/ad specs
o
0MEMAMC15_Q0001: Value-oriented complaint ratio
For further information on the corrections to the update rules for reversed order objects, see the OSS note 572954. •
DataSource M/AM Order: Schedule Line/Ad Spec (0ME_ISM_AM_ORDER_2) The DataSource M/AM Order: Schedule Line/Ad Spec did not return a reversal indicator for reversed order objects during delta extraction. For this reason, filtering of reversed order objects in the evaluations for the InfoCube Schedule Line/Ad Spec (Ads Only) 0MEMAMC03 was not performed correctly and led to incorrect results being displayed in the query. For further information on the corrections made to delta extraction for reversed order objects, see the OSS note 584823.
Retail NEW ODS OBJECTS FOR UPDATING AGENCY DOCUMENTS Use There are now two ODS objects available, which enable you to update all single documents and all list documents in Agency Business at document level. You can use the ODS objects as follows: •
You can create InfoCubes in which you update the data from the ODS objects. Reorganize the ODS objects at regular intervals.
•
You can structure a reporting at document level. You can cr eate a link between the list document level and the single document level. InfoSource 2LIS_45_LST has been extended to include field WBELN_LF for this. The corresponding InfoObject 0AB_DOCLF represents the document number of the single document.
Effects on System Administration You require PlugIn 2003.1 in the OLTP system, as the list extractor MC045W_0LST has been extended to include field WBELN_LF.
SAP Retail Merchandise and Assortment Planning Use
SAP AG
50
SAP Retail Merchandise and Assortment Planning (MAP) is a complete set of tools for planning in retail environment, for both fashion and basic merchandise. For fashion, planning is usually top-down to the merchandise category level and bottom-up from the assortment planning level, while for basics the plan is driven by forecast and replenishment considerations. This BW content is intended to be used as a basis for merchandise and assortment planning within Strategic Enterprise Management (SEM), but may also be used independently of SEM for reporting on actual and historical data. The major building blocks of MAP are: •
Strategic Planning (including channel performance planning and financial data such as balanced scorecards and margins)
•
Merchandise Planning (including open-to-buy planning, sales, margin, and inventory planning by merchandise category)
•
Assortment Planning (including creation of new styles and assortments)
•
Location Planning (including open-to-ship planning, plan/actual comparisons and exception reporting)
•
Slow Seller Management (including markdown planning)
The following reports are available: •
•
•
For the Merchandise Planner , who needs information about departments and merchandise categories so as to target the ones that contribute the greatest amount to sales and profits o
Cross Category Analysis and Assessment
o
Sales Scorecard
o
Inventory Scorecard
o
Productivity Scorecard
o
Sales Exceptions
o
Sales and Markdown Shares
o
Comparison Merchandise/Rollout Plans
For the Location Planner , who needs a true picture of growth and comparable sales in order to estimate the effect of opening or closing stores will have on total company sales and profit projections o
Regional Analysis
o
Location Scorecard
o
Location Inventory Scorecard
o
Location Productivity Scorecard
o
Comparable Sales Analysis
For the Assortment Planner , who needs visibility into fashion products by color, fabric, themes or other attributes, and an analysis of past history d ata for basics
SAP AG
o
Assortment Analysis and Assessment
o
Sales Coverage of Products
o
Plan Analysis for Fashion
51
•
o
Fashion Sales Scorecard
o
Basics Sales Scorecard
o
Fashion Inventory Scorecard
o
Basics Inventory Scorecard
o
Productivity Scorecard for Fashion
o
Productivity Scorecard for Basics
o
Sales and Receipts Exceptions
o
Top N% Sellers
For the VP of Planning , who needs to evaluate performance metrics that span the entire organization and then assess them by sales channels and division o
Comparison Location/Merchandise/Strategic Plans
o
Comparison Rollout/Style Plans
Effects on Data Transfer •
Sales information is obtained from POS receipts via the POS DataMart. It includes regular sales, promotional sales, and temporary markdowns. All necessary information is provided for gross margin calculations, including a moving average cost and retail.
•
For customers that have R/3 Enterprise, inventory and purchasing information is obtained via DataSources and InfoSources that are fed by R/3 Enterprise. It is also possible to use flat files from external inventory and purchasing solutions and assign them to the InfoSources; this allows you to upload inventory and purchasing information into the MAP InfoCubes.
Utilities Quotation Planning and Analysis for the Utilities Industry Use This content allows you to plan utility quotations for commercial and industrial customers in CRM. The planning key figures can be compared with the actual key figures in IS-U if contracts were created for the quotations. A prerequisite for this function is that you have the IS-U/CRM Integration component for Commercial and Industrial Customers (as of CRM 4.0). The planning key figures are u pdated when utility quotations are calculated for commercial and industrial customers. This calculation is part of the Key Account Manager portal for Utilities. The planning key figures are updated in the corresponding BW InfoCube using component SEM-BPS (Strategic Enterprise Management - Business Planning and Simulation). However, the KAM portal interface is used instead of the SEM-BPS interface. It is important to differentiate between actual billed key figures and actual forecasted key figures. The first is based on IS-U sales statistics while the latter is extracted from a mass simulation in BW. It is possible to perform a simulation for the future so that the whole quotation period is covered. InfoProviders are available for clearing costs and rates of different cost types. These InfoProviders serve as a basis for calculating and updating accrued costs with the help of the planning functions of SEM-BPS. MultiProviders that allow contribution margin accounting at contract or point of delivery level are provided for the purpose of analyzing different data sources. The full functionality is restricted to commercial and industrial contracts that are defined in IS-U and in CRM by means of the IS-U item type.
SAP AG
52
Effects on Existing Data You define commercial and industrial contracts in IS-U by allocating update group SNRES (C&I customer) to their rate categories in update group determination. If contracts already exist for which another update group has been found, you must change your Customizing settings and if necessary also change the customerdefined transfer and update rules for the BW sales statistics that referred to the old update group.
Effects on Data Transfer Secondary cost rates previously stored in customer-defined tables can now be transferred to the relevant InfoProvider in the BW system by means of an SEM-BPS planning area or a PC file. If accrued costs were previously calculated in CO-PA, you can no w use the corresponding SEM-BPS functions as an alternative or as an addition.
Effects on System Administration Before you can use the analysis functions you must first load data from CRM and IS-U to BW. If you want to prepare data for further anaylsis, you must first close any open requests for transactional InfoCubes.
See also For more information read the documentation for IS-U/CRM Integration for Release CRM 4.0.
EDM Analyses in the Utilities Industry Use It is now possible to analyze data from Energy Data Management (EDM) in SAP BW. This mainly concerns the point of delivery and its attributes, the allocation of the point of delivery to the installation, and the profile values, which can be visualized in SAP BW by means of remote query. The point of delivery master data can be used in SAP BW for master data reporting. A predefined InfoSet query links the point of delivery to the business partner. You can use this InfoSet Query to determine all points of delivery that belong to a business partner or a business partner's contracts, for example. Also available is a RemoteCube that uses the Remote Extractor to provide you with the selected profile values from IS-U. You can display the profile values in graphical form using front end tools Excel or Web Application Designer. Do not save the profile values in BW as this creates duplicate data. The advantage of this function is that you can use the SAP BW front end and display the profile data in the portal without using programming resources. You primarily use the InfoSet Query and the RemoteCube to display the profile data of a business partner in graphical form. All of the points of delivery for the business partner are selected in SAP BW.
Effects on Existing Data This function does not affect existing data.
Effects on Data Transfer The initial download of the point of delivery master data can only be made via the full stock. As it is not possible to restrict the selection, ensure that you have planned a sufficient amount of time. The changes are then processed as delta and transfered via delta do wnload to BW. Ensure that any updates to the points of delivery are made using the function modules provided by SAP otherwise correct delta processing is not guaranteed. Note that the DataSources are only available as of IS-U/CCS Release 4.71.
Effects on System Administration The attributes in the InfoSet that are used for the join condition need to be given a secondary index in order to improve the performance of the analyses.
Effects on Customizing
SAP AG
53
Activate the DataSources in IS-U/CCS and replicate them in SAP BW.
See also For further information read the online documentation for BW 3.20, in particular the sections on InfoSets and Queries.
Collection Agencies in Contract Accounts Receivable and Payable Use This content answers questions on the duration of activities and on the sum of collected and uncollected amounts. The collection data is cumulated and stored in an InfoCube so that you can evalute the services of the collection agency. The data in the delta queue of the s ource system is configured by means of a mass activity.
Effects on Existing Data The data is loaded to a new InfoProvider. This does not affect existing data.
Effects on Data Transfer An InfoPackage is provided for the initial load as well as for the delta load. The initial load InfoPackage is executed just once and is used for initialization without having to load any data. Once you have done this, you have to start the collection agency mass activity in order to generate the data that is to be loaded into the BW system. You then execute the delta load InfoPackage to transfer the data to the BW system.
See also For more information read the online documentation on BW 3.20 for Contract Accounts Receivable and Payable.
Installment Plan in Contract Accounts Receivable and Payable Use This content answers questions on the number of installment plans, expected repayments from installment plans, average installments per installment plan, and so on. The item data and header data is stored in two different ODS objects so that you can s ubsequently analyze the installment plans. A third ODS object contains this data in compressed form for each installment plan separated according to cleared and open items. The data in the delta queue of the s ource system is configured by means of a mass activity.
Effects on Existing Data The data is loaded to a new InfoProvider. This does not affect existing data.
Effects on Data Transfer An InfoPackage is provided for the initial load as well as for the delta load. The initial load InfoPackage is executed just once and is used for initialization without having to load any data. Once you have done this, you have to start the collection agency mass activity in order to generate the data that is to be loaded into the BW system. You then execute the delta load InfoPackage to transfer the data to the BW system.
See also For more information read the online documentation on BW 3.20 for Contract Accounts Receivable and Payable.
SAP AG
54
Sales Statistics with Tax Amounts in the Utilities Industry Use Tax amounts are now also available in addition to the net amounts. The tax amounts are divided amongst consumption months according to the net amounts and loaded to the sales statistics InfoCube. Up to now, you could only evaluate the net amounts of characteristics (such as rate category, rate, and statistics group). Now you can also evaluate the corresponding tax amounts.
Effects on Existing Data It is not possible to determine tax amounts for data that has already been loaded. If you need these amounts you have to carry out a new full upload.
Effects on Data Transfer The corresponding DataSources 0UC_SALES_STATS_01 (sales statistics) and 0UC_SALES_STATS_02 (IS-U sales statistics) contain this new functionality as of IS-U/CCS Release 4.71. Read the OSS notes for the BW-BCT-ISU-ST component.
Effects on Customizing Copy DataSources 0UC_SALES_STATS_01 and 0UC_SALES_STATS_02 from the content and replicate them in SAP BW.
See also For more information read the online documentation for BW 3.20.
Beverage SAP Beverage Business Content Use Development in the SAP Beverage Business Content covers the following SAP Beverage components o
SAP Beverage Telephone Sales
o
SAP Beverage Sales Returns
o
SAP Beverage Empties Management
The Beverage Content has been created under 0Industries with the following structure of InfoAreas and application components New InfoAreas o
Beverage (0BV)
o
Sales Returns (0BV _LO_SR)
o
Empties Management (0BV_LO_EM)
o
Telephone Sales (0BV_CAS_TS)
New application components
SAP AG
o
Beverage (0IS_BV)
o
Telephone Sales (0IS_BV_TS)
55
o
Sales Returns (0IS_BV_SR)
o
Empties Management (0IS_BV_EM)
In the Telephone Sales component sales activities and the resulting sales are being analyzed. The evaluations are based on the InfoCube "SAP Beverage Telephone Sales Overview" (0BVTS_C01) . In the loading process all records are loaded in the standard - irrespective of the status of the sales activity and the material type of the materials that are maintained. For further information on the sales activity status, please refer to "Effects on Data Transfer". The Business Content for the SAP Beverage component Telephone Sales can, for example, be activated through the role "Beverage Telephone Sales" (SAP_BW_BV_CAS_TS). The SAP Beverage component Sales Returns makes it possible to evaluate the values and quantities of the analysis results. The evaluations are based on the InfoCube "Analysis Sales Returns" (0BVSR_C01). The SAP Beverage component Empties Management makes it possible to evaluate the empties acc ount of the customer. The evaluations are based on the InfoCube "SAP Beverage Empties Evaluation" (0BVEM_C01). The Business Content for the SAP Beverage components Sales Returns and Empties Management can, for example, be activated through the role "Beverage Logistics" (SAP_BW_BV_LO.
Effects on Data Transfer The generic extractors that were developed for the transaction data support the Delta loading process. SAP Beverage Telephone Sales has been precustomized in such a way that all sales activities are loaded. In order to filter sales activities with specific statuses the delivered start routines can be configured customer-specifically in the update rules of the ODS-objects "Sales Document CAS-Sales Activity" (0BVTSDS01) and "Telephone Sales Sales Activity/Order" (0BVTSDS02). The Business Content for Telephone Sales has been precustomized in such a way that the order items are updated for all material types. In order to suppress updating s pecific material types the delivered start routine can be configured customer-specifically in the update rules of the ODS-objects "Telephone Sales Sales Activity/Order" (0BVTSDS02), too. For further information on updating, please refer to SAP Library Business Content -> Beverage.
9. Cross-Application Components BW Integration in the Business Partner (Extended) Use DataSources in the PI_BASIS The DataSources for the central part of the business partner (BP), which are available as of PI_BASIS 2002_2_620 in all SAP Systems with Basis Release 6.20, are now used generally used in the Business Content. In this way all the DataSources that exist redundantly in the CRM Enterprise und Enterprise Buyer professional edition for the central BP data become obsolete. The description for these DataSources was changed to "obsolete" and a reference to the PI_BASIS DataSource that should be used in future has been inserted. Note Note that these DataSources are no longer supported and that they will be deleted within the foreseeable future. The objects in question are listed below: DataSource Description 0BBP_BPART_ATTR Obsolete: Use 0BPARTNER_ATTR
SAP AG
56
0BBP_BPART_TEXT Obsolete: Use 0BPARTNER_TEXT 0BBP_BPCCARD_ATTR Obsolete: Use 0BP_CCARD_ATTR 0BBP_BPDEFADDR_ATTR Obsolete: Use 0BP_DEF_ADDRESS_ATTR 0BBP_BPTYPE_TEXT Obsolete: Use 0BPTYPE_TEXT 0BBP_BP_BANK_ATTR Obsolete: Use 0BP_BANK_ATTR 0BBP_BP_ID_ATTR Obsolete: Use 0BP_ID_ATTR 0BBP_BP_ID_TYPE_TEXT Obsolete: Use 0BP_ID_TYPE_TEXT 0BBP_BP_IND_CODE_TEXT Obsolete: Use 0BP_IND_CODE_TEXT 0BBP_BP_IND_SECTOR_ATTR Obsolete: Use 0BP_IND_SECTOR_ATTR 0BBP_BP_IS_ATTR Obsolete: Use 0BP_IS_ATTR 0BBP_BP_STATUS_ATTR Obsolete: Use 0BP_STATUS_ATTR 0BBP_BP_TAXCAT_TEXT Obsolete: Use 0BP_TAXCAT_TEXT 0BBP_BP_TAXNUMB_ATTR Obsolete: Use 0BP_TAXNUMB_ATTR 0BBP_BP_UNAME_ATTR Obsolete: Use 0BP_UNAME_ORGUNIT_ATTR 0BBP_CITYCODE_TEXT Obsolete: Use 0CAM_CITYCODE_TEXT 0BBP_CITYPCODE_TEXT Obsolete: Use 0CAM_CITYPCODE_TEXT 0BBP_IND_NUMSYS_TEXT Obsolete: Use 0IND_NUMSYS_TEXT 0BBP_IND_SECTOR_HIER Obsolete: Use 0IND_SECTOR_HIER 0BBP_PROD_STAPROSYS0_TEXT Obsolete: Use 0COM_PRODUCT_STAPROSYS0_TEXT 0BBP_PROD_STAPROSYS1_TEXT Obsolete: Use 0COM_PRODUCT_STAPROSYS1_TEXT 0BBP_STREETCODE_TEXT Obsolete: Use 0CAM_STREETCODE_TEXT 0CRM_BANKKEY_TEXT Obsolete: Use 0BANKKEY_TEXT 0CRM_BPACTITLE_TEXT Obsolete: Use 0BP_ACTITLE_TEXT 0CRM_BPART_ATTR Obsolete: Use 0BPARTNER_ATTR 0CRM_BPART_TEXT Obsolete: Use 0BPARTNER_TEXT 0CRM_BPCCARD_ATTR Obsolete: Use 0BP_CCARD_ATTR 0CRM_BPCONTACT_TEXT Obsolete: Use 0BP_CONTACT_TEXT 0CRM_BPDEFADDR_ATTR Obsolete: Use 0BP_DEF_ADDRESS_ATTR 0CRM_BPGROUP_TEXT Obsolete: Use 0BP_GROUP_TEXT 0CRM_BPGRPTYPE_TEXT Obsolete: Use 0BP_GRPTYPE_TEXT 0CRM_BPMARST_TEXT Obsolete: Use 0BP_MARST_TEXT 0CRM_BPTITLESPPL_TEXT Obsolete: Use 0BP_TITLESPPL_TEXT 0CRM_BPTYPE_TEXT Obsolete: Use 0BPTYPE_TEXT 0CRM_BP_BANK_ATTR Obsolete: Use 0BP_BANK_ATTR 0CRM_BP_CAT_TEXT Obsolete: Use 0BP_CAT_TEXT 0CRM_BP_ID_ATTR Obsolete: Use 0BP_ID_ATTR 0CRM_BP_ID_TYPE_TEXT Obsolete: Use 0BP_ID_TYPE_TEXT 0CRM_BP_IND_CODE_TEXT Obsolete: Use 0BP_IND_CODE_TEXT 0CRM_BP_IND_SECTOR_ATTR Obsolete: Use 0BP_IND_SECTOR_ATTR 0CRM_BP_IS_ATTR Obsolete: Use 0BP_IS_ATTR 0CRM_BP_RELATIONS_ATTR Obsolete: Use 0BP_RELATIONS_ATTR 0CRM_BP_RELDIR_TEXT Obsolete: Use 0BP_RELDIR_TEXT 0CRM_BP_RELTYPES_TEXT Obsolete: Use 0BP_RELTYPES_TEXT 0CRM_BP_REL_AUTH_TEXT Obsolete: Use 0BP_REL_AUTH_TEXT 0CRM_BP_REL_DEPMNT_TEXT Obsolete: Use 0BP_REL_DEPMNT_TEXT 0CRM_BP_REL_FUNC_TEXT Obsolete: Use 0BP_REL_FUNC_TEXT 0CRM_BP_REL_VIP_TEXT Obsolete: Use 0BP_REL_VIP_TEXT 0CRM_BP_STABUPSYS0_TEXT Obsolete: Use 0BP_STABUPSYS0_TEXT 0CRM_BP_STABUPSYS1_TEXT Obsolete: Use 0BP_STABUPSYS1_TEXT 0CRM_BP_STABUPSYS2_TEXT Obsolete: Use 0BP_STABUPSYS0_TEXT 0CRM_BP_STATUS_ATTR Obsolete: Use 0BP_STATUS_ATTR 0CRM_BP_TAXCAT_TEXT Obsolete: Use 0BP_TAXCAT_TEXT 0CRM_BP_TAXNUMB_ATTR Obsolete: Use 0BP_TAXNUMB_ATTR 0CRM_BP_UNAME_ATTR Obsolete: Use 0BP_UNAME_ORGUNIT_ATTR
SAP AG
57
0CRM_CCARDTYPE_TEXT Obsolete: Use 0CCARDTYPE_TEXT 0CRM_CITYCODE_TEXT Obsolete: Use 0CAM_CITYCODE_TEXT 0CRM_CITYPCODE_TEXT Obsolete: Use 0CAM_CITYPCODE_TEXT 0CRM_IND_NUMSYS_TEXT Obsolete: Use 0IND_NUMSYS_TEXT 0CRM_IND_SECTOR_HIER Obsolete: Use 0IND_SECTOR_HIER 0CRM_LEGALFORM_TEXT Obsolete: Use 0LEGALFORM_TEXT 0CRM_STREETCODE_TEXT Obsolete: Use 0CAM_STREETCODE_TEXT Formatted Address The address is now available in formatted form, in addition to the address attributes for the BP (0BPARTNER) and the BP relationships (0BPRELATION) that already exist. The following attributes were added for this purpose: o 0ADDR_SHORT: Short form of the address with name/city o 0ADDR_SH_S: Short form of the address with name/street/city o 0ADDR_LINE0: Address line 0 o 0ADDR_LINE1: Address line 1 o 0ADDR_LINE2: Address line 2 o 0ADDR_LINE3: Address line 3 o 0ADDR_LINE4: Address line 4 o 0ADDR_LINE5: Address line 5 o 0ADDR_LINE6: Address line 6 o 0ADDR_LINE7: Address line 7 o 0ADDR_LINE8: Address line 8 o 0ADDR_LINE9: Address line 9 Effects on Data Transfer Proceed with conversion to the new DataSources as follows: 1. First carry out a delta initialization for the new DataSource so that a delta is logged here. An initialization without data transfer is sufficient. 2. Load the delta for the old DataSource. 3. Delete the DataSource assignment. In this way you do not need to carry out a full update, and you nevertheless do not lose any data.
10. External Sources SAP BW Business Content for Oracle Receivables (New) Use In the Oracle Receivables application, you can create and manage transactional data (invoices, credit memos, payments, and so on) for Accounts Receivable Accounting. Using Ascential DataStage, this transactional data is extracted from the Oracle OLTP system into SAP BW. You can now analyze the Accounts Receivable data in SAP BW on the basis of pre-defined Business Content. The aim is to control more effectively payment transactions between your company and your customers. The Accounts Receivable Accounting employee or Credit Manager can use BW analysis tools to react very early to delayed payments from customers. And in s o doing, minimize the financial losses for your company. SAP returns the most useful reports (that is BW Queries) for Accounts Receivable Accounting based on data that has been extracted from the Oracle Receivables application: •
Ageing lists: Days overdue analysis, net due data analysis
•
Customer balance lists
•
Days of Sales Outstanding (DSO) analysis
Effects on Data Transfer
SAP AG
58
