Download - Bussiness Content

SAP® BW BCT List for BI Content 3.3 Add-On

Release/Version: SAP BW 3.1 Content / BI Content 3.3 Add-On

Author: Marianne Kollmann

SAP Business Information Warehouse 3.1 Content / BI Content 3.3 Add-On

BW Business Content List

Version Status Date 1.1 Final 03/11/2003

SAP AG assumes no responsibility for errors or omissions in these materials.

These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third party Web pages.

© 2002 SAP AG Neurottstr. 16 D-69190 Walldorf

Title: SAP BI Content 3.3 Add-On – Business Content List File: BWBCTLIST33ADDON_v2.doc Date: 11/3/2003

of 74

SAP® BW BCT List for BI Content 3.3 Add-On 1 Customer Relationship Management................................................. 4 1.1 Marketing .......................................................................................................... 4 1.1.1 Round offs and performance improvements of ELM ........................................ 4 1.2 CRM Sales........................................................................................................ 6 1.2.1 Business Content for CRM Activity Management Analysis .............................. 6 1.2.2 Business Content for CRM Opportunity Management Analysis ....................... 6 1.2.3 Business Content for CRM Territory Management Analysis............................. 7 2 Human Capital Management............................................................... 8 2.1 Enterprise Compensation Management ........................................................... 8 2.2 People-Centric User Interface: Role “HR Executive” ........................................ 9 2.3 Pension Fund.................................................................................................. 10 3 Product Lifecycle Management ........................................................ 12 3.1 Environment, Health and Safety Issues.......................................................... 12 3.2 Extraction of (central) master data attributes and Ids from MDM ................... 13 3.3 Evaluation of Stability Study Data from mySAP PLM Quality Management ... 14 4 Financials ........................................................................................... 17 4.1 Asset Finance and Leasing ............................................................................ 17 4.2 Credit Management ........................................................................................ 18 4.3 Flexible Real Estate Management (RE-FX) in SAP BW................................. 20 4.4 Extraction of Budget Line Items...................................................................... 23 5 Supplier Relationship Management ................................................. 25 5.1 Contract Reporting.......................................................................................... 25 5.2 Global Spend Analysis – Integration of FI Data.............................................. 26 5.3 Vendor Evaluation .......................................................................................... 27 5.4 Bidding Engine Reporting ............................................................................... 28 5.5 Reporting for Supplier Self Service................................................................. 30 6 Manufacturing.................................................................................... 31 6.1 Sales Scheduling Agreement Processing....................................................... 31 7 Small and Midsize Business............................................................. 34 7.1 SAP Business One – SAP BW Integration ..................................................... 34 8 SAP Master Data Management (SAP MDM)..................................... 36 8.1 Extraction of (central) master data attributes and Ids from MDM'................... 36 9 Industry Units..................................................................................... 38 9.1 Financial Services........................................................................................... 38 9.1.1 Bank Analyzer Basel II BW Business Content................................................ 38 9.1.2 Bank Analyzer IAS BW Business Content...................................................... 41 9.1.3 Core Banking Mortgage Loans ....................................................................... 42 9.1.4 Transaction Banking ....................................................................................... 44 9.1.5 Claims............................................................................................................. 46


Title: SAP BI Content 3.2 Add-On –Business Content List File: BWBCTLIST33ADDON_v2.doc Date: 11/3/2003

of 74

SAP® BW BCT List for BI Content 3.3 Add-On 9.2 High Tech ....................................................................................................... 48 9.2.1 CRM Channel Sales Management Analytics.................................................. 48 9.3 Media .............................................................................................................. 50 9.3.1 Enhancement of Intellectual Property Management to SAP BW.................... 50 9.4 Pharma ........................................................................................................... 53 9.4.1 Pharmaceutical Call Sample BW Business Content....................................... 53 9.5 Consumer Products ........................................................................................ 56 9.5.1 Store Audits .................................................................................................... 56 9.6 Retail............................................................................................................... 57 9.6.1 CRM Workforce Management Retail – Operational Reporting....................... 57 9.6.2 SAP POS Data Management ......................................................................... 61 9.6.3 Global Trade Management ............................................................................. 62 9.7 Utilities ............................................................................................................ 65 9.7.1 Round-Off BI Content for KAM Portal Utilities ................................................ 65 9.8 Engineering, Construction & Operations ........................................................ 65 9.8.1 Business Content for Project Risk Management for Contractors (PRC)......... 65 9.9 Oil & Gas ........................................................................................................ 67 9.9.1 Business Content for Joint Venture Accounting (JVA) ................................... 67 9.10 Public Sector................................................................................................... 68 9.10.1 Grants Management – Grantee organizations................................................ 68 9.10.2 Federal Government BW Reporting ............................................................... 72



of 74


1 Customer Relationship Management 1.1 Marketing

1.1.1 Round offs and performance improvements of ELM

Abstract of the Business Solution

External List Management (ELM) is the process of procuring, managing, using, and reporting on acquired addresses.

Acquired addresses can be:

Business partner addresses (for example, the name of an organization or the name of a private individual, the postal code, city, and street)

Business partner relationship data (for example, person A is the contact person for organization B)

The entire External List Management scenario runs in SAP BW and SAP CRM.

The address lists used in External List Management can be acquired from external providers of marketing data. Customers can decide which data they want, how many data records an address list should contain and which format the data is to be provided.

Description of the (new) BW Business Content

SAP delivers a predefined scenario that is ready-to-go so you can put the solution to work right away. The scenario contains pre-configured packages based on business scenarios. The SAP Business Information Warehouse part contains:

Extractors for transferring data from CRM to SAP Business Information Warehouse

Predefined Data Models, including

1 ODS object, collecting data about created outbound contacts

2 InfoCubes, collecting the contact counter and COPA data

Multi Provider, joining the contact and COPA data

InfoSet, providing data for the queries

The BW scenario of ELM offers an operational and an analytical part. The operational functionality covers the upload of address data into BW and their selection via Segment Builder in CRM. For the analytical part predefined queries are delivered, which provide information about the number of duplicates in the loaded address list, the number of won business partners as well the revenue of the address list used in campaigns.



of 74

SAP® BW BCT List for BI Content 3.3 Add-On Main business benefit / main question answered with the (improved/enhanced) solution

External List Management adds solid, bottom-line business value because it:

Allows the processing of marketing addresses in an easy way

Increases market share, revenues and profits

Increases the number of customers resulting from the gaining of new business partners via campaigns

The main benefit of integrating SAP ELM (External List Management) into SAP BW is the closed loop analysis that allows a comparison of costs and revenues of acquired addresses.

Business scenarios (how the solution can be used)

External List Management covers the upload of address data into BW, selection of the data via Segment Builder in CRM, transfer of the addresses and creation of business partners in CRM, contacting the business partners assigned to a target group via campaigns, collection of the reaction of the contacted business partners, creation of sales orders, collection of campaign and sales data in COPA and the transfer of all information to the data warehouse where it is analyzed.

SAP BWCRM SERVER SAP R/3

System updates contact information

Analyze

System provides contact data

System provides sales order data

System provides activity data

System provides profitability data

Upload list in SAP BW

Select business partners for target group

Create target group



of 74

SAP® BW BCT List for BI Content 3.3 Add-On 1.2 CRM Sales

1.2.1 Business Content for CRM Activity Management Analysis


mySAP CRM Activity Management enables sales representatives and managers to allocate resources for daily sales tasks effectively so that sales professionals can close their sales deals as quickly as possible.


CRM Activity Management Analysis provides analyses for monitoring the quantity and success rate of activities undertaken by the sales team. It includes a success/failure analysis, open activities per customer, active/passive analysis, intensity of customer care, and distribution of activities across organizational units.

BI Content 3.3 Add-On contains the following enhanced business content:

Inclusion of Interaction Objects in Activity Analyses

The interaction object is a simplified activity used to represent e-mails or other forms of communication that are mass-generated for marketing campaigns. You can now decide whether to include these objects in activity analyses, enabling you to view every form of contact that has been made in conjunction with a certain customer or marketing campaign, or to create specific analyses for following the progress of your marketing campaigns. The addition of interaction objects provides you with the opportunity for monitoring your sales cycle from marketing through to sales.

Main business benefit / main question answered with the (improved/enhanced) solution

Business Content for analyzing items in Activity Management enables you to better relate the pre-sales effort of your sales team with the products that are actually involved. It provides an accurate picture of whether your sales strategy is being implemented in the field.

1.2.2 Business Content for CRM Opportunity Management Analysis


Opportunity Management provides sales professionals with a 360° view of their sales opportunities by providing complete visibility of the opportunity’s history, milestones, progress and key decision-makers.



of 74

SAP® BW BCT List for BI Content 3.3 Add-On Description of the (new) BW Business Content

Opportunity Management Analysis comprises a specific set of analyses that look at opportunities in detail. These enable you to monitor expected revenues, the opportunity pipeline, progress towards opportunity completion, and opportunity success. The information can be fed back into the sales cycle by using the results to discover which customers to target in subsequent marketing campaigns, for example.

BI Content 3.3 Add-On contains the following enhancement to existing Business Content for Opportunity Management:

Opportunity Monitor Timeline Analysis

The timeline analysis enables you to navigate from a selected opportunity in the Opportunity Monitor to a chronological overview of all documents, such as activities and quotations, related to this opportunity. This query is applicable for the portal roles Sales Manager and Sales Representative.

1.2.3 Business Content for CRM Territory Management Analysis


mySAP CRM Territory Management enables you to structure and organize your sales market by dividing it into territories according to criteria of your choice, such as size, region or product line.


CRM Territory Management Analysis enables you to analyze your sales figures, including revenues, sales volumes, planned figures, by territory. You can run reports, such as:

Comparison of Planned and Actual Sales Figures by Territory

Number of Activities by Territory

Number of Samples Given by Territory

BI Content 3.3 Add-On contains analyses for tracking sales document revenues according to territory. They enable you to compare the net billed value against the net value of orders per territory and also inform you which sales orders have not been completed and what are the reasons for not being able to complete them.


Business Content for Territory Management enables you to analyze sales data, including revenue-related figures, according to territory. It thus provides sales managers with an overview of which territories are successful or not.



of 74


2 Human Capital Management 2.1 Enterprise Compensation Management Abstract of the Business Solution

The primary task of mySAP HR Enterprise Compensation Management is to help business owners and managers build effective employee compensation programs and support a company’s entire compensation management process.

mySAP HR Enterprise Compensation Management covers all parts belonging to this compensation process: job pricing, budgeting, compensation administration and long-term incentives. And even more, with numerous integration points, SAP is able to support your fully-integrated compensation management process with a truly end-to-end solution.

Using the compensation management capabilities of mySAP Human Resources supports you in defining and streamlining a strategic compensation policy throughout your enterprise. A fundamental advantage is that the system offers all vital parts belonging to a complete compensation management system such as salary benchmarking to its full extent, budgeting, compensation reviews including variable pay (e.g. bonuses) of all kinds and long-term incentive plans – not to mention integration which is in place wherever required by a business point of view such as the direct interaction with goals setting and the achievement thereof to be able to manage and pay by performance.

SAP delivers tools to you to put your compensation strategy into practice that provides the key in motivating employees to support your business goals and improve your company’s bottom line.


The BW Business Content for mySAP HR Enterprise Compensation Management comprises

Extractors for transferring data from mySAP HR Enterprise Compensation Management (PA-EC) to SAP Business Information Warehouse


8 ODS objects, collecting data about compensation processes, compensation budgets, employee pay categories, composite market data, raw market data, job matching, salary structure of jobs as well as active and planned salary structures

5 InfoSets, providing data on compensation processes, compensation budgets, Comparison of Market Data and Employee Payment, Salary Survey Market Data and Job Matching as well as Comparison of Salary Structure Against Market

1 InfoCube, enabling the evaluation of LTI awards

24 predefined standard queries



of 74

SAP® BW BCT List for BI Content 3.3 Add-On Main business benefit / main question answered with the (improved/enhanced) solution

Increased visibility of all information around the compensation management process at your enterprise

Compensation Specialists can monitor and steer the compensation process better, based on the information from the SAP BW

Compensation Specialists can come up with a more fair, transparent and competitive compensation and pay strategy based on data and comparison capabilities coming from the SAP BW

Analytical reporting capabilities complete mySAP HR Enterprise Compensation Management and make it a mature compensation management solution. The main benefit of integrating mySAP HR Enterprise Compensation Management with SAP BW are the powerful analysis options provided by SAP BW. Status monitoring of the ongoing compensation management process support compensation professionals.

2.2 People-Centric User Interface: Role “HR Executive” Abstract of the Business Solution

Currently, there is no business software specifically designed to support the critical business needs of the HR Executive. In today’s competitive business environment, it is vital to be able to prove the value of human capital to the overall revenue and performance of an organization using the measurable goals of the business as a whole. This proof is, however, difficult to obtain. Using metrics and the integration capabilities of the SAP application suite (such as HCM, BI, SEM, and FI among others) in the Enterprise Portal, the HR Executive is equipped with the right information to establish the strategy, structure, systems, and staffing that will drive human capital transformation. Since it relates to overall business strategies, the information delivered in the HR Executive role can help any executive to drive human capital. The information supplied to the HR Executive is in aggregated form and can be broken down in detail as required.


Key Figures

The most important HR-related key figures and Key Performance Indicators (KPIs) are provided for the HR Executive on the overview page in the Enterprise Portal. They can be selected from the Key Figure Catalog. The HR Executive can simply click on a key figure to obtain detailed information and can navigate in the query with ease.

Key Figure Catalog

The Key Figure Catalog contains all pre-defined key figures. The catalog is grouped into categories from a business point of view. Customers can enhance the catalog and thereby tailor it to suit their requirements. Key figures for the Key Figure Watchlist are selected from this catalog.



of 74

SAP® BW BCT List for BI Content 3.3 Add-On Key Figure Monitor

Key figures from queries with pre-defined exception values appear in the Key Figure Monitor on the Enterprise Portal page for the HR Executive. The level at which the exception value is exceeded is indicated using traffic lights.

Combined Analyses (enhanced Cockpits)

The Combined Analyses iView provides you with a list of cockpits, which are a summary of multiple queries, starting with a graphical overview. The HR Executive can use this iView to compare key figures, for example to analyze the headcount. In the standard system, each cockpit in the Combined Analyses iView contains four graphics on one screen. SAP delivers two cockpits that have a uniform look and feel: Overtime and Illness, and Headcount.


This content is specially designed for use in the Enterprise Portal by an HR Executive or by the head of an HR Department.

The most important analytical HR key figures are provided on one Enterprise Portal page.

Key Figures with pre-defined exception values are provided and visualized using traffic lights.

More detailed information can be accessed with a mouse-click.

Navigation in the queries is very easy.

Navigation in time is possible.


This solution covers the information needs of an HR Executive regarding HR-related Key Figures and KPIs. The information is provided initially on an aggregated (company) level, with the option to drill down to more detailed evaluation levels, such as organizational unit, cost center, employee subgroup, and even to employee level.

The solution integrates these analytical information requirements with application services (such as HR services) and generic services designed for the HR Executive, provided by the Enterprise Portal.

2.3 Pension Fund Abstract of the Business Solution

The SAP HR Pension Fund supports you in administering an enterprise’s pension fund. The flexibility of the solution enables you to map, manage, and monitor all the business processes required.



of 74

SAP® BW BCT List for BI Content 3.3 Add-On Description of the new BW Business Content

SAP delivers predefined scenarios that can be used for the following purposes:

Determination of insured persons’ age structure in a pension fund

Overview of pension entitlements

Overview of insured persons’ credits

The SAP Business Information Warehouse element in these predefined scenarios contains:

Extractors for transferring data from SAP HR Pension Fund to SAP BIW

Predefined Data Models, which include

5 ODS objects, containing data on: master data of the insured persons, chosen pension products and linked values accounts events (exclusively for Dutch Pension Funds) calculated data

2 InfoCubes, enabling evaluation of account data and calculated data

3 InfoSets, enabling evaluation of the insured persons’ data according to the organizational assignment


The new BW Business Content mainly supports the pension fund administration business area. It enhances operation efficiency by enabling administrators to perform evaluations for all insured persons within a pension fund.

The integration of HR SAP Pension Fund with other SAP Business Suites such as mySAP Financials, mySAP Human Resources Payroll, and mySAP HR Personnel Administration, represents one of the main business benefits. To be able to make full use of this advantage, a BW interface has been developed. Its business content will be delivered for the first time with the following Plug-In Releases:

R/3 – PI 2002.1 (Support Package 2)

R/3 PI – 2003.1



of 74


3 Product Lifecycle Management

3.1 Environment, Health and Safety Issues Abstract of the Business Solution

mySAP Product Lifecycle Management (mySAP PLM) addresses a range of environment, health, and safety issues in the module EH&S. As well as enabling the customer to manage risk and comply with government regulations, the solution integrates a variety of environment, health, and safety functions:

Product safety

Hazardous materials management

Dangerous goods management

Industrial hygiene and safety management

Occupational health

Waste management

The EH&S BW interface supports companies in evaluating results from different EH&S modules, in particular “Dangerous goods management”, “Product safety” and “Industrial Hygiene and Safety”.


SAP delivers predefined content that is ready-to-go so you can put the solution to work right away. This content contains:

Extractors for transferring data from EH&S to SAP Business Information Warehouse

Predefined Data Models, including:

4 ODS objects, collecting data about expected and unplanned events, groups of expected events and the event handler

5 InfoCubes, enabling the evaluation of notification and execution behavior

The Content delivered covers the extraction of EH&S substance data with values and phrases, accidents and “Hazardous Substance Inventory” data.


The target group for reporting is product safety specialists, industrial hygiene and safety specialists, and dangerous goods specialists.

The main benefit of integrating SAP PLM EH&S into SAP BW is the increased visibility of EH&S throughout a company’s processes, and the support of EH&S data for monitoring


Title: SAP BI Content 3.3 Add-On – Business Content List File: BWBCTLIST33ADDON_v2.doc Date: 11/3/2003

of 74


and auditing purposes.


The BW connection to EH&S supports the easy and reliable creation of:

Accident statistics

Hazardous Substance Inventory

Inventory lists for fire department

based on the corresponding data maintained in R/3.

3.2 Extraction of (central) master data attributes and Ids from MDM


SAP Master Data Management (SAP MDM) improves the accuracy of the enterprise-wide master data, getting rid of redundancies and inconsistencies. You can match multiple occurrences of the same object across the system landscape and store them as ID mapping data.


The new business content enables you to extract the ID mapping data and the master data to the SAP Business Information Warehouse (SAP BW). In particular, the ID mapping data and the master data can be used there to fill the consolidated product, customer and vendor InfoObjects. These correspond directly to the SAP MDM master data objects product and business partner and allow you to carry out consolidated and company-wide evaluations.


With the enhanced business content solution the DataSources provided by SAP MDM 2.0 become fully operational allowing the extraction of the ID mapping and the master data from the SAP MDM master data server into SAP BW. This simplifies the work of the system administrator responsible for the update of the consolidated InfoObjects. Instead of having to extract the corresponding data from all the different application systems, a unified upload from the SAP MDM master data server is possible.


The SAP MDM scenario you are using (Content Consolidation, Master Data



of 74


Harmonization, or Central Master Data Management) determines how you extract data from SAP MDM to SAP BW.

The new business content applies to the scenarios 2 or 3 (Master Data Harmonization, or Central Master Data Management). In these scenarios both the ID mapping data and the master data can be extracted from DataSources on the SAP MDM master data server to SAP BW. The new SAP MDM BI content provides the InfoSources as well as the transfer and update rules required to update the consolidated InfoObjects.

Remark: In scenario 1 (Content Consolidation), no master data is stored on the master data server in SAP MDM. However, the ID mapping data is available and can be extracted directly from SAP CI DataSources in SAP MDM to SAP BW. There, you can transfer the ID mapping data to the consolidated InfoObjects. In SAP BW, you can use mySAP Supplier Relationship Management (SAP SRM) BI content, which is available from SAP BW 3.1/BI Content 3.2 Add-On.

3.3 Evaluation of Stability Study Data from mySAP PLM Quality Management


With SAP R/3 Enterprise, Ext. 1.10, customers can plan and perform stability studies with the quality management application of the mySAP PLM solution. The handling of stability studies is an essential business process especially in the process industry (Pharmaceuticals, Chemicals, Food & Beverages) to determine the shelf life of products under defined conditions over a fixed period of time.

The new delivered business content enables the customer to run evaluations on stability studies using SAP BW and thus significantly enhances the reporting capabilities of this new QM process. For example, the evaluation and comparison of study data according to common standards now becomes possible, enabling the customer to analyze test results, realizing trends and make decisions on further progress.

The new business content is an essential contribution to SAP ´s capability on data handling in the Research & Development (R&D) environment, where stability studies are often used.


SAP delivers two new info cubes for evaluating stability studies from SAP R/3. The extractors in the SAP R/3 plug-in were enhanced accordingly.

0QM_C12: Stability Study: Inspection results (general): This cube allows the evaluation of



of 74


data from all closed inspection characteristics, especially qualitative characteristics together with their attributive codes. Only test results from inspection lots of inspection origin 16 (stability studies) are extracted into this cube.

0QM_C13: Stability Study: Inspection results (quantitative data): This cube allows the evaluation of data from all closed quantitative inspection characteristics (numeric results). Only test results from inspection lots of inspection origin 16 (stability studies) are extracted into this cube.


So far, the reporting capabilities for stability studies in SAP R/3 were limited. Additionally, the existing business content in SAP BW was not sufficient to evaluate stability studies, because new data fields were created in SAP R/3, which were not extracted to SAP BW. Furthermore, the connection between inspection lots, physical samples and notifications as central object of the stability study did not exist.

The evaluation of stability studies with SAP BW is now possible and covers all essential requirements for the handling of study-related inspection data (e.g. list display of all test results for one packaging material at one selected storage condition across several studies).

During development of the business content, valuable input was provided by a customer from the pharmaceutical industry.

The new business content is very valuable because

all stability study data can easily be evaluated

the evaluation takes place in a user-friendly and easy-to-use interface, which is especially important for people working in an analytical laboratory

the evaluation reports can be tailored to customer needs

the results of several studies can be compared

the data can be handled in a controlled environment, which is especially important for regulated industries such as the Pharmaceutical industry


Stability studies are planned and periodical tests at fixed points in time were performed using the quality management capabilities in SAP R/3. The user would like to have – at any time – an overview about his study results according to several selection criteria.

With this new business content in SAP BW, this is now possible.

For example, the solution allows the evaluation of all inspection lots for one stability study



of 74


or the comparison of samples for one storage condition across several studies.

It also enables the comparison of results from two different characteristics over a certain period of time. e.g. in a graphical display.

The results are presented in MS Excel workbooks, which can be send around or embedded into other reports.

Availability: SAP R/3 Enterprise: PLM Extension 2.00 SAP Plug-In: Release 2004.1 SAP BW: Content 3.3



of 74


4 Financials

4.1 Asset Finance and Leasing Abstract of the Business Solution

SAP Asset Finance and Leasing is a complete end-to-end solution for companies leasing out or financing mobile assets. It supports the whole offer and contract management, including pricing and financial mathematics, as well as all back office related activities like revenue accounting, asset management and general ledger handling.

The solution is completed by offering an aggregated view of all transactional data related to financing in BW. This includes the identification of critical lease portfolios and profitability tracking. Additionally operational reports help with estimating profitability in the organization (like order cycle times).


The BW Content for SAP Asset Finance and Leasing provides predefined scenarios showing how to combine information from lease contract management with accounting information about a leasing contract, in one common report. The scenario contains:

Extractors for transferring data from contracts, assets, lease accounting and accounts compatible with BW

Predefined ODS objects combining this data so as to be able to run integrated reports


SAP Asset Finance and Leasing adds business value because:

It offers an integrated view of all leasing contracts from the customer, as well as the internal, perspective

It allows you to control lease portfolios and the respective profitability online

It helps reduce the transactional costs related to the lease offer and contract management

It allows you to review the lease portfolio from a strategic point of view while also taking into account new legal requirements.


Lease portfolio analysis:

One of the main tasks within lease analysis is to constantly check the profitability and structure of the lease portfolio. Legal changes or unforeseen developments in the residual



of 74


values of leased objects can strongly influence the profitability of the leasing company. Therefore it is essential to have a clear picture of this at any point in time. This information can also be used to derive future strategic decisions and strategies.

4.2 Credit Management Abstract of the Business Solution

Using effective credit management, companies can reduce the balance of arrears (Days Sales Outstanding) and prevent the possibility of non-payment for a delivery that has already been made. The prerequisites for a company-wide credit policy are the integration of credit management in all distribution channels, automated real-time decisions, and access to internal and external credit information.

The SAP Credit Management component provides companies that have a large customer base with the opportunity to monitor the total liability of their customers, using appropriate credit lines. A decisive advantage of this is a centralized and company-wide management of credit lines. This means that different distribution channels use the same data to check creditworthiness and utilization. This eliminates the risk of customers exceeding the credit limit granted to them by using different distribution channels, without this being recognized by the credit department.

In the age of Web business, in which business processes take place at "Web" speed, it is very important to be able to classify new customers or check creditworthiness in real time. Therefore, Credit Management has corresponding interfaces to external credit information providers so that the user can get an independent assessment of his or her customers from professional service providers in real-time. In addition, the customers can be assessed according to your own internal company valuation rules, whereby companies can take their internal credit guidelines into account.

Extensive analyses enables the user to identify customer groups with a low risk and good response time, and therefore plan targeted sales and marketing campaigns for low-risk customers. In addition, companies can use relevant analyses to compare the structure of their customers, with regard to creditworthiness, with that of other companies or with the industry average.

A Credit Rules Engine automates the process for the new assignment and adjustment of credit lines using derivation rules.

The Credit Management system also has analyses that can be used to monitor the performance of a credit department or individual credit clerks with respect to the effectiveness of credit decisions. This enables companies to establish to what extent the



of 74


Credit Management Department was able to prevent non-payment through credit decisions in the past, or to what extent strategic specifications could be implemented. Constant monitoring of performance prevents credit departments from rejecting sales orders due to credit decision criteria that are too severe, where the credit risk would actually be acceptable for the company.


Credit Management BW Content aims to support decisions on the credit rating of business partners by providing analytic information such as internal rating, risk class, credit limits and scores. The BW Content that is available for SAP Credit Management includes:

Extractors for transferring data from SAP Credit Management to SAP Business Information Warehouse


3 ODS objects, collecting data about customer credit master data, credit limit, mass updates

2 InfoCube, enabling the analysis of credit master data by period and the analysis of the simulation of credit scoring for each customer

Predefined Queries help you to analyze the risk structure of your customer base, the result of simulated scoring & limit rules, the credit history of a customer and to monitor the overall credit risk to your company.


Main target groups of Credit Management BW Content are credit managers whose task is to supervise and judge their customers’ credit rating. In addition, the same BW Content is used to inform sales managers and AR accountants about a customer’s standing.

Controlling credit risk via real-time credit allocation and ongoing monitoring

Online credit rating check to enable fast credit decisions

Reducing effective DSO by reducing payment delays and bad debt

Increasing revenues with risk-free accounts (decreased rate of credit refusals)

Reducing transaction costs by automating the credit application process

Improving customer relationships by concentrating service on profitable customers

Linking dunning & dispute information to the credit decision process

The main benefit of integrating SAP Credit Management into SAP BW is the availability of vast amounts of information that can be included for the scoring and valuation of customers. Therefore you can combine information from sales, logistic and financial departments to evaluate the creditworthiness of your customer. Once the scoring for a



of 74


customer is calculated, this information is needed in many other departments where the creditworthiness of a customer also plays a role (e.g. sales). As the customer’s score is available in the BW, it can easily be used in other queries. In this way, information from the credit management department is used to enhance your analysis functions.

Business scenario: Scoring for existing customers

The scoring of customers is a very important step in credit management processes. Customer scoring is necessary, especially if you want to monitor the credit exposure of your customers. Usually you use information from the payment behavior, sales history, or dunning history to calculate the scoring for existing customers. You can use predefined queries to simulate the scoring of your customer base with new scoring models and to compare the results with the existing models. With this feature you are able to develop new scoring models, which provide better results in terms of identifying high-risk customers.

4.3 Flexible Real Estate Management (RE-FX) in SAP BW Abstract of the Business Solution

The main goal of Flexible Real Estate Management is the effective and efficient management of real estate and investment portfolios.

Real estate is typically the second largest use of corporate capital and cash flow, and the second largest expense on balance sheet. Flexible Real Estate Management (RE-FX) enables the maximization of value for this very significant corporate investment through a complete solution to support every stage of real estate management.

The new release of SAP Real Estate Management (RE-FX), which is based on SAPNet Weaver technology, offers greater management flexibility and highly visible control of rental space and contracts. Closely integrated with financial accounting and product lifecycle management, this innovative solution lets you manage your properties as efficiently as possible while increasing your cachet with customers.

In addition, Flexible Real Estate Management delivers integrated tools that improve decision-making capabilities and enable a more effective management of your real estate portfolio.



of 74

d025525

This needs to be repaired!



Flexible Real Estate Management in SAP BW allows access to real-time data on all of the strategically important aspects of your enterprise, equipping you with the tools to simulate and plan future development for your real estate portfolio.

The BW Content for Flexible Real Estate Management provides predefined scenarios enabling the analysis of real estate objects, contracts and vacancies, as well as costs and revenues. For BI Content 3.3 Add-On, this comprises of:

Extractors for transferring data from SAP Flexible Real Estate Management (RE-FX) to SAP Business Information Warehouse (SAP BW).

Info Cubes for occupancy, vacancy, measurements, cost and revenues, conditions, cash flows

Predefined Queries/Workbooks to help you analyze real estate costs and revenues, portfolio performance, measurements, contract and partner performance, notice dates, as well as vacancy frequency and duration.


Flexible Real Estate Management offers all the functionality you need to manage every phase of the real estate portfolio life-cycle.

By integrating the relevant data from the SAP application suite (RE-FX, FI, CO, PLM, AA, PS) with SAP BW the real estate manager is provided with the right information to establish the best direction for strategy and structure, in order to drive optimum portfolio performance. Real Estate managers can monitor and manage the real estate process better, based on the information in SAP BW. It enhances operational efficiency by enabling users to perform evaluations on all areas of the real estate portfolio.

The solution adds business value because:

It provides an integrated view of all real estate management processes. Results are displayed for both internal rent (corporate use) and for objects rented from and to third parties (Commercial Use).

It allows you to control and monitor the performance of rental objects, contracts and business partners.

It helps reduce transactional costs related to lease and contract management

It provides accurate information on real estate costs and revenues contributing to overall company success.

The main benefit of integrating SAP Flexible Real Estate Management in SAP BW is the increased visibility of real estate management in company processes. It allows you to streamline business processes by integrating the real estate management software solution into the company’s corporate software solution. In doing this, it allows for the identification and realisation of how effective real estate management can influence



of 74


business decisions, and how much it contributes to the company balance sheet.


Main target groups of Flexible Real Estate Management BW Content are real estate managers whose task it is to manage the real estate portfolio efficiently, making decisions about location, portfolio size (buy, sale, lease-back), contracts (lease-in/-outs, services, own-use) and portfolio performance. The real estate manager is also interested in the costs and revenues (profitability) generated by the real estate portfolio.

The solution covers the information needs of a real estate manager, independent of whether he/she is managing the company’s own real estate (corporate use), or whether the real estate is being managed on behalf of another company (commercial use).

Information is delivered to the Real Estate Manager on an aggregated level at first glance, with the possibilities to drill-down to more detailed evaluations such as real estate object, contract, business partner and location.

Flexible Real Estate Management content in BW supports the easy and reliable analysis of:

Object and Contract Performance

Business Partner Performance

Important Dates (notice)

Vacancy (frequency and duration)

Cash Flows

Costs and Revenues

based on the corresponding data maintained in R/3.



of 74


4.4 Extraction of Budget Line Items Abstract of the Business Solution

Controlling provides you with information for management decision-making. It facilitates coordination, monitoring, and optimization of all processes in an organization. This involves recording both the consumption of production factors and the services provided by an organization.

The Overhead Cost Controlling component (CO-OM) enables you to plan, allocate, control, and monitor overhead costs. It is an important preparation for reliable and comprehensive profitability analysis, as well as for a precise product costing and project controlling.

On the corresponding account assignment objects, Budget Management answers the question whether budget requirements can be met. The budgets incurred are assigned to business objects such as orders or projects.


SAP delivers predefined, ready-to-go scenarios so that you can put the solution to work right away. Each scenario contains preconfigured packages based on business scenarios. The SAP Business Information Warehouse part in these visibility scenarios contains:

Extractors for transferring data from CO-OM to SAP Business Information Warehouse

Predefined data models, including ODS objects, InfoCubes, queries and workbooks for analysis of costs on cost centers, internal orders and projects.

With BI Content 3.3 Add-On this functionality has been significantly enhanced with respect to operational line item reporting capabilities.

BI Content 3.3 Add-On provides new DataSources for budget line items on orders and WBS elements.

Both the existing DataSources for actual, plan and commitment line items on orders and WBS elements, as well as the new budget DataSources provide delta extraction capabilities for releases SAP R/3 4.0B up to SAP R/3 Enterprise.


Line item reporting for budgets provides a deeper understanding of the origin of planned costs and expected costs, thus delivering crucial controlling information especially for project management.

In particular a detailed view on aggregated budget data is possible now drilling down to the



of 74


respective line items.

The R/3 delta mechanism for budgets leads to a significant reduction in loading times, allows for shorter extraction intervals and thus a more up-to-date analysis of budgets.



of 74


5 Supplier Relationship Management

5.1 Contract Reporting Abstract of the Business Solution

Contract Management is a crucial piece in both processes operational procurement as well as strategic sourcing. In fact, it serves as the connection point between the two. Therefore, contract analysis is also crucial in both processes. For strategic sourcing, contract reporting analyzes expiring contracts in terms of time as well as target quantity/volume. Oftentimes one, centrally negotiated outline agreement is replicated as local contracts into several execution systems. Call-offs are always recorded in the local systems. For strategic sourcing purposes, it is necessary to be able to track how the local call-off volumes relate to the central outline agreement.

For operational procurement, contracts are the source of supply that is assigned to operational demands. Purchasing professionals analyze contracts in terms of utilization in order to allocate the demand in accordance with the purchasing guidelines and objectives e.g. equal distribution across multiple vendors or single sourcing, in order maximize the bonus.



of 74


The new contract functionality in SRM 3.0 is the ability to create a central outline agreement and replicate it to several execution systems (those can be Enterprise Buyer and R/3 Materials Management). With BI Content 3.3 Add-On, reporting complements this functionality by enabling reporting on contract including the relation between a central outline agreement and the local contracts.

When an outline agreement is replicated to an execution system, the contract references the central outline agreement ID. For reporting, contract and call-off data is extracted to BW from the local execution systems as well as from the central EBP, hosting the outline agreement. The contracts carry the central ID as an attribute into BW, where it can be used as mapping and as filter. The new content includes one new DataSource, additions to existing DataSources and one new ODS with several queries attached.

Reports to the following areas will be available:

One will be an overview of the call-offs to a master agreement, broken down by the related local contracts. The displayed figures will be the local contracts to a master agreement, the position numbers of the local contracts, the call-offs to the local contracts, with the total call-offs to the master in the result line.

Another report will show the values / quantities that were processed over master agreements only. This can be done using the contract type or by only displaying the


contracts marked as master agreement.

One report will show details for single contracts, showing the combination of contract, vendor, product category and the end of the validity period, with the corresponding target and call off value. (equivalent to report on old ODS)

There will be a report displaying the expiring contracts, also showing the target values and the call offs for those contracts that are expiring within the following months, so that an action can be taken to reach the target value within the contract time frame.


The new content extends the contract analysis functionality beyond system-by-system reporting, to make transparent contract utilization across the entire enterprise. This way, global spend analysis and sourcing opportunity identification can be conducted based on contracts. Opportunity identification determines the scope and savings potential of a strategic sourcing project and therefore directly impacts the bottom line. Only continuous opportunity identification delivers sustainable savings in repeated sourcing cycles.

5.2 Global Spend Analysis – Integration of FI Data Abstract of the Business Solution

The purpose of Global Spend Analysis is to be able to analyze corporate spend in a heterogeneous system environment. In the past releases, spend analysis was based on data, originating in procurement systems. Some spend categories, e.g. utility expenses, p-card purchases, rent, etc. are typically not channeled through a procurement system, and thus are often not available for spend analysis. In the new release all spend is captured by extracting and analyzing FI data in terms of purchasing volume.


In this release, data is extracted from R/3 FI into BW and analyzed in terms of spending. Only spending-relevant information from general ledger accounts is extracted, using FI extractors, which are generated based on customers FI configuration. This allows for the enhancement of the extracted FI data with purchasing information not available in FI (e.g. material group). The pre-delivered business content will include a dedicated ODS and one InfoCube. The data model also includes the generic InfoObjects for vendor and material group, which makes the analysis comparable with the spend analysis based on procurement data as it appears in the previous releases.



of 74



The solution benefits mainly the strategic sourcing professional in his/her efforts to aggregate spend across a heterogeneous system landscape with multiple buying channels. The capture of all spend enables the best possible aggregation of purchasing volume to be leveraged in sourcing efforts such as contract negotiations. The complete spend visibility also allows for precise identification of sourcing opportunities and informed decision making.


Global spend analysis is mainly utilized in the strategic sourcing process. Opportunity identification determines the scope and savings potential of a strategic sourcing project and therefore directly impacts the bottom line. Only continuous opportunity identification delivers sustainable savings in repeated sourcing cycles.

5.3 Vendor Evaluation Abstract of the Business Solution

The evaluation of buy-side business partners, in terms of delivery performance, is a crucial part of the strategic purchasing efforts. Supplier evaluation drives decisions about the future relationship with a supplier, and helps optimizing the supplier portfolio. One might extend more business to a supplier with good performance, or collaborate with that supplier to improve supply chain processes. If performance is low, less business to, or exit of, that supplier might be appropriate.

An additional application for supplier evaluation is the supplier selection in the operational procurement process. In the case of multiple comparable suppliers, past performance might be the indicator of who gets selected as source of supply for a operational demand.

In order to make performance measurable, SRM business content offers two ways of capturing performance data. Firstly purchasing documents, such as purchase orders, goods receipt and invoices are collected and interpreted. Secondly, end users of the e-procurement component are confronted with web surveys, collecting soft-facts about a supplier in the context of the specific procurement process step, e.g. questions about the packaging quality in the goods receipt procedure. Both, procurement data and Web survey information is interpreted in BW and contributes to a supplier evaluation solution.



of 74



Initial supplier evaluation functionality has been released in previous SRM/BW releases, however, the following functionality has been expended in the release:

Choosing suppliers in the supplier evaluation report and return them to Enterprise Buyer. BW front end will support, in several reports, the selection of suppliers as source of supply and the transfer of the selected suppliers to supplier list and Bidding Engine and possibly the sourcing cockpit.

Verification tool to display the calculation algorithm for supplier’s score for improved supplier evaluation visibility (verification by the purchasing professional). This includes queries in order to display how individual criteria are weighed on each level of aggregation.

Statistical reporting on weighting and usage of criteria

Improved customizing functionality for weighting an grouping of supplier-score-calculation-algorithm


As described above, supplier evaluation fulfils multiple purposes. Used strategically, it helps optimising the supplier portfolio and minimizing supply risks. Also opportunities for process improvements can be identified.

In an operative context, supplier evaluation helps allocating purchasing volume to viable and well performing suppliers, minimizing the supply risk and improving the relationship with strategic suppliers.

The verification tool for supplier scoring enables a continuous process improvement process, as the user has visibility into underlying logic and can trigger improvements


Supplier evaluation is mainly applicable to the purchasing professional, who is maintaining supplier relationships or allocating sources of supply to operational demand based on supplier performance.

5.4 Bidding Engine Reporting Abstract of the Business Solution

Bidding Engine is the component within mySAP SRM that fulfills RFI and RFQ processes. The purchaser invites bidders to bid and after all bids are placed, analyzes the results and determines the winner(s). The awarded suppliers are recorded as such in the Bidding Engine and the resulting document can be a contract or purchase order. Business



of 74


Warehouse contains bid analysis capabilities that support the purchaser in determining a winner as well as analyze the bidding behavior of bidders for future process improvements.


New business content revolves around the following areas:

Supplier evaluation report as source for bid invitation list (requires SRM 3.0 service pack 3)

The selection of suppliers to receive a bid invitation will also be possible in BW (in addition to external catalogs and internal master data, as it was possible in previous releases). The report is enhanced with checkboxes for supplier selection and the transfer of all necessary supplier data will be realized via Open Partner Interface (OPI).

Additional functionality within reports to enhance usability

Download to Excel button available in all reports pertaining to Bidding Engine

Button for currency conversion in bid analysis reports

Integration of supplier evaluation reports with bidder comparison reports, in order to relate delivery performance to bidding behavior.

Highlight best and worst bid to make the range visible.

Suppliers that have been invited and did not respond can now be included in the analysis of bidding behaviors (percentage response to invitation and average response time).

Report to indicate how many bid invitations and responses per product category have been placed

Enhanced reporting on dynamic attributes

Availability of comment fields in BW (initiator and bidder) for dynamic attributes

Calculation with dynamic attributes possible (e.g. currency conversion, reporting by dates, etc.)


Supplier evaluation as source for bid invitation list: Past performance and bidding behaviour of suppliers impact the decision which suppliers to invite to a bidding event. The integration of supplier evaluation and bidder selection streamlines the selection process and improves selection decisions.

Enhanced bid analysis optimises the award-decision and streamlines the decision process. The inclusion of dynamic attributes in this process, presents a comprehensive view of all aspects of a bid, which in turn enables an optimally informed award-decision.

Comprehensive bidding statistics support the supplier selection process and assembly of



of 74


bid invitation lists.


This scenario is applicable to the initiators and decision makers in a bidding event with SRM Bidding Engine

5.5 Reporting for Supplier Self Service Abstract of the Business Solution

Supplier Self Service (SUS) is the supplier-facing application of the SRM procurement solution. Reporting on SUS processes includes actual status of orders and invoices, procurement volumes, contracts and performance evaluation information.


Business content enhancements for BI Content 3.3 Add-On are following the SUS enhancement of enabling the SUS – MM procurement scenario

Web templates with modified authorization concept that restricts vendors to only see their own data, based on the login ID (only with SUS 2.0 service pack 2). The web templates also serve as basis for easy navigation between different reports.

New query to get visibility into consignment stock levels in R/3 MM

Reporting on performance of service providers, including performance indicators such as quality of service, timeliness of service and compliance.

Reporting supports a 1:n connection scenario (one SUS to many buying applications)


With the integration of MM processes into the SUS reporting, the SRM reporting functionality is extended to stockable materials. Suppliers are enabled to get an improved overview of current business with their customers and thus empowered to re-act and pro-act quickly. This minimizes expediting and error tracking and leaves more time available to process improvements.


This scenario is applicable to customers exchanging procurement documents between Enterprise Buyer and SUS as well as R/3 MM and SUS.



of 74


6 Manufacturing

6.1 Sales Scheduling Agreement Processing Abstract of the Business Solution

The main goal of Collaborative Management of Delivery Schedules (CMDS) is to enable and improve collaboration between the supplier and its customers beyond company boundaries. The flexibility of the solution enables it to map, manage, and monitor all customer demand for a certain product or a set of them and match it with the stock or production of the products. It uses active alerts to make users aware of situations, and thus improves response times to exceptional situations. This, in turn, means a better service for the customer.

In addition, Supply Chain Management with CMDS supports companies in evaluating results using data warehouse systems such as SAP Business Information Warehouse, for example to obtain detailed information about how reliable customer demands were confirmed, in order to improve customer satisfaction.


SAP delivers predefined scenarios that are ready-to-go so you can put the solution to work right away. Each scenario contains pre-configured packages based on business scenarios. The SAP Business Information Warehouse part in these visibility scenarios contains:

Extractors for transferring data from SCM to SAP Business Information Warehouse


7 ODS objects, collecting data about Schedule Lines for Sales Scheduling Agreements, Sales Scheduling Agreement Items, Deliveries as well as Sales orders

2 Info Cubes, enabling the tracking of the Service Levels and Fulfillment rates

Process Chains

In the SAP Business Information Warehouse (SAP BW) you can evaluate data on sales scheduling agreement items that are planned in SAP APO.

As well as sales scheduling agreements planned in APO (APO sales scheduling agreements), sales orders from SAP R/3 can also be included in the evaluation.

For example, you can evaluate in the CMDS environment

How reliably customer requirements were confirmed, in other words, whether they were confirmed fully or partially?

How reliably deliveries were made for customer requirements, in other words, © 2002 SAP AG Neurottstr. 16 D-69190 Walldorf


of 74


whether deliveries were made on time for confirmed customer requirements?


Collaborative Management of Delivery Schedule adds solid, bottom-line business value because it:

Improves service levels and reduces inventory levels thanks to tight cooperation between customer facing and production facing users.

Increases market share, revenues, and profits, with the ability to respond quickly in volatile markets.

Increases customer loyalty resulting from improved service, and the ability to provide customers with accurate updates and commitments.

Reduces costs as a result of the ability to deploy resources where they can most effectively handle demand.

Enhances operating efficiency, from workload leveling and focusing on the exceptions rather than the routine.

The main benefit of integrating CMDS into SAP BW is the increased accuracy of the scheduling call released to production with all its dependant benefits.

Business scenarios (how the solution can be used) The following slide shows the process how the solution can be used.



of 74




of 74


7 Small and Midsize Business

7.1 SAP Business One – SAP BW Integration Abstract of the Business Solution

The SAP Business One – SAP BW Integration enables BW users within the headquarters of a company to analyze subsidiaries using SAP Business One. Data from SAP Business One systems can be uploaded to SAP BW. The relevant Reporting Areas include Sales, Purchasing, and Financials. The data is comparable to SAP R/3 data. So the data format and the logical meaning of the key figures and characteristics are the same. There is no financial consolidation of the different subsidiaries.


SAP delivers pre-configured packages to analyze SAP Business One data within SAP BW. These are listed below:

Sales:

3 ODS objects collecting Order, Invoice, and Delivery data

1 InfoCube to analyze the Sales data from SAP Business One Systems

1 MultiCube to compare the SAP Business One data with SAP R/3 data

Queries for the Sales Area enabling Subsidiary Comparison and Trend Analysis

Purchasing

3 ODS objects collecting Purchase order, Goods receipt/ Goods return, and Invoice/ Credit memo

1 InfoCube to analyze the purchasing data from SAP Business One Systems

1 MultiCube to compare the SAP Business One purchasing data with SAP R/3 purchasing data

Queries for the Purchasing Org. Comparison, Purchasing activity analysis, Vendor evaluation, and Price trends over the last three months

Financials

3 ODS objects respectively collecting General Ledger Transaction Figures, General Ledger Line Items, and Profit Center Transaction Data

2 InfoCubes to analyze the General Ledger Transaction Data and Profit Center Transaction Data

1 MultiCube to integrate General Ledger Transaction Data

Queries for Financial Analysis enabling Balance Sheet reports, Profit Center Reports, and Profit and Loss statements



of 74



The main benefit of the SAP Business One – SAP BW Integration is the possibility to analyze data from subsidiaries using SAP Business One as well as subsidiaries using SAP R/3 and to compare this data.


The data can be analyzed for the areas Sales, Purchasing, and Financials:

Sales:

The company has many subsidiaries and a headquarters. A sales manager wants to get an overview of the sales data of all subsidiaries. After analyzing this data various actions may take place, for example, changes in the plan, advertisement in special regions, or personnel changes.

Purchasing:

The company has many subsidiaries and a headquarters. Each subsidiary has its own purchase organization to process the procurement procedure, to include purchase orders, goods receipts, and invoice verification. The material master and vendor information is shared between subsidiaries and headquarter. A purchase manager located in the headquarters would like to analyze the purchase information from all subsidiaries, for example, subsidiary comparison of purchase value, quantity, and value variance between purchase order, goods receipt, and invoice receipt per material; price trends over the last three months per material, fulfillment delivery rate per vendor, vendor comparison, and so on. Afterwards, various actions may take place, such as negotiating a contract for central purchases to lower cost, changes in purchase budget, vendor relocation, and so on.

Financials:

The company has many subsidiaries and a headquarters. A financial manager wants to have an overview of the financial data of all subsidiaries, for example, the balance sheet, the P/L statement, the profit center analysis.



of 74


8 SAP Master Data Management (SAP MDM)

8.1 Extraction of (central) master data attributes and Ids from MDM' Abstract of the Business Solution

SAP Master Data Management (SAP MDM) improves the accuracy of the enterprise-wide master data, getting rid of redundancies and inconsistencies. You can match multiple occurrences of the same object across the system landscape and store them as ID mapping data.


The new business content enables you to extract the ID mapping data and the master data to the SAP Business Information Warehouse (SAP BW). In particular, the ID mapping data and the master data can be used there to fill the consolidated product, customer and vendor InfoObjects. These correspond directly to the SAP MDM master data objects product and business partner and allow you to carry out consolidated and company-wide evaluations.


With the enhanced business content solution the DataSources provided by SAP MDM 2.0 become fully operational allowing the extraction of the ID mapping and the master data from the SAP MDM master data server into SAP BW. This simplifies the work of the system administrator responsible for the update of the consolidated InfoObjects. Instead of having to extract the corresponding data from all the different application systems, a unified upload from the SAP MDM master data server is possible.


The SAP MDM scenario you are using (Content Consolidation, Master Data Harmonization, or Central Master Data Management) determines how you extract data from SAP MDM to SAP BW.

The new business content applies to the scenarios 2 or 3 (Master Data Harmonization, or Central Master Data Management). In these scenarios both the ID mapping data and the master data can be extracted from DataSources on the SAP MDM master data server to SAP BW. The new SAP MDM BI content provides the InfoSources as well as the transfer and update rules required to update the consolidated InfoObjects.

Remark: In scenario 1 (Content Consolidation), no master data is stored on the master data server in SAP MDM. However, the ID mapping data is available and can be extracted



of 74


directly from SAP CI DataSources in SAP MDM to SAP BW. There, you can transfer the ID mapping data to the consolidated InfoObjects. In SAP BW, you can use mySAP Supplier Relationship Management (SAP SRM) BI content, which is available from SAP BW 3.1/BI Content 3.2 Add-On.



of 74


9 Industry Units

9.1 Financial Services

9.1.1 Bank Analyzer Basel II BW Business Content


With “Bank Analyzer”, IBU Financial Services offers a new suite of analytical applications tailored to match the banking industry’s need for an integrated back office solution. Bank Analyzer consists of a common data layer – the Financial Database – which provides multiple analyzers with data.

Some of the challenges the banking industry faces today are the new risk calculation, risk controlling and disclosure practices as demanded by the Basel II consolidation paper. The Bank Analyzer helps banks overcome these challenges, with business content providing the reports demanded by pillar 3 (Disclosure and Reporting) of the consolidation paper.

The overall scenario includes the new features:

OLTP extractor configuration and generation to flexibly combine and transfer results of the Basel II calculation process (Result Data Base), the Historical Data Base (HDB) and the Financial Data Base (FDB) to the SAP Business Information Warehouse

complete data staging process including InfoSource and update rules

ODS-based line item reporting

MultiProvider-based analytical reporting

ready-to-run queries satisfying the disclosure specifications of the SAP Basel II Solution 2.1


SAP delivers ready-to-run reports including the complete data model for reporting and the staging process, the latter supported by the OLTP extractor shipped with the Bank Analyzer 2.1 system.

The following reports are provided:

1. Distribution of Credit Items 2. Geographic Distribution 3. Distribution by Sector/Counterparty Category 4. Maturity Distribution 5. Portfolio Report 6. LGD Results 7. EAD Results



of 74


8. Risk Mitigation Effects 9. Non-Performing Credit Items 10. Value Adjustments, Revenues, Depreciation

They are based on the MultiProvider 0BADRMC01. The MultiProvider offers the above-mentioned disclosure reports and can also support internal analytical reporting.

The scenario is rounded off by the ODS-object 0BADRDS01, which may be used for both detailed line item reporting on financial transaction level and as a possible source for drill-down navigation. The ODS-object contains the necessary information to allow for drill-through scenarios to the Bank Analyzer OLTP system.

The BW Business Content may be seen as integral part of the full Basel II disclosure and reporting process, which originates in the Bank Analyzer OLTP system: The extractor reads in, merges and transports results from the calculation process (RDB), the Historical Data Base (HDB) and the Financial Data Base (FDB) of the Bank Analyzer. The data can be staged using the pre-defined InfoSource.


The Bank Analyzer Basel II disclosure and reporting business content has been set up following the Basel II regulations (pillar 3).

The business content shortens implementation time and effort of the BW reporting considerably by providing ready-to-run queries, a fully developed data model and close integration with the Bank Analyzer OLTP processes.

Reports on high aggregation level satisfy the disclosure and reporting requirements determined by management and supervisory authorities.

The business content can easily be enhanced to meet extended requirements for internal reporting using freely definable drill-down paths.

The Bank Analyzer Basel II solution including the data extraction process can be extended with freely definable customer reporting criteria and key figures.

Business scenarios

The following Basel II process shows the data flow for Disclosure and Reporting in the SAP Bank Analyzer Core and SAP BW:



of 74


BW

SERVER

Transfer RulesTransfer RulesTransfer RulesTransfer Rules TransferTransferTransferTransfer

Operational Data StoreOperational Data Store

UpdateUpdateUpdateUpdate

OLAP Processor

PSA PSAInfoSources

Operational SystemsOperational SystemsOperational Systems

HDB FDBNon SAPRDB

Reports

Input Layer

Data Extraction

Bank Analyzer Core

Bank Analyzer calculates key figures relevant for Basel II and stores pre-calculated and historic results in the Historical Data Base (HDB). The calculation results and the historical data may be merged and transferred to the SAP Business Information Warehouse, where they can be analysed on financial transaction level or higher.

Example

The following example illustrates the report Geographic Distribution of Credit Items.

The underlying transaction includes a loan with an annual repayment amounting to EUR 1 million to a company headquartered in Germany, which was valued on 06/01/2003.

Step 1: The transaction data for the loan is entered, processed and stored in the bank’s own operational systems.

Step 2: The necessary transaction data (for example: exposure, collaterals, guarantees and maturity) for the loan is transferred to the FDB.



of 74


Step 3: The costing objects for the loan are determined during the costing process, which reads the input data (Step 2) from the FDB. The results - EAD (exposure at default), LGD (loss given default), PD (probability of default) and others - are stored in the Result Data Base (RDB).

Step 4: The calculation results (Step 3) may be merged with other information in the data extraction process and analysed in the Business Information Warehouse.

9.1.2 Bank Analyzer IAS BW Business Content


With “Bank Analyzer”, IBU Financial Services offers a new suite of analytical applications tailored to match the banking industry’s need for an integrated back office solution. Bank Analyzer consists of a common data layer – the Financial Database – which provides multiple analyzers with data.

One of these analyzers is Balance Analyzer - Balance Analyzer provides financial statements, including profit and loss statements and notes, in accordance with the International Accounting Standards (IAS) for the financial transactions and instruments of a bank.

The results from Balance Analyzer are reported using SAP Business Information Warehouse (BW). The data model can be modified and extended to a large degree to meet the bank’s individual requirements. This reflects the high level of flexibility required by a modern financial reporting process. Bank Analyzer IAS Business Content demonstrates independently of a special data model the reporting possibilities offered by BW. It is therefore used in the early implementation phase to support the financial and technical experts in the implementation team by providing examples that cover:

Financial reporting using queries with two structures

Comparison of results from different fiscal periods using calculated key figures and variables

Segment reporting using drill down and free characteristics

Sender query for drill-through navigation to details of individual transactions and instruments in the OLTP


Bank Analyzer IAS Business Content has been set up to support implementation projects in the early phase by offering alternative data modeling approaches for financial reporting in SAP Business Information Warehouse.



of 74


Although data extraction can be carried out easily using the Balance Analyzer data extractor in the standard way, the option of modeling formatted financial reporting, comparing fiscal periods, and using drill-through scenarios has been used to give the implementation project a running start.

IAS Business Content contains:

One MultiProvider that supports balance sheet reports and profit and loss reports.

Four queries to demonstrate financial reporting using two structures, comparison of fiscal periods, and drill-through scenarios


The main benefit of integrating SAP IAS into SAP BW is the increased transparency throughout a company’s financial reporting processes. In addition to standard financial statement items, P&L, and notes, it allows you to monitor the creation of all keyfigures along the financial reporting process.

The aim of Bank Analyzer IAS Business Content is to facilitate the implementation of IAS reporting. It offers modeling alternatives to all members of the implementation team, thus providing the decision makers with management reporting capabilities.

Quick and complete overview of all relevant financial statement items, resulting from a consistent valuation process.

Segment reporting

Full audit trail

Using the BW technology to combine these results with other data for further reporting and analysis.


The following analytical applications are supported:

Operative financial reporting process, which covers the entire process from transaction data, its valuation in accordance with IAS and visualization of the results in BW. Further detailed analysis can be carried out, including tracing the origin of the data in the OLTP system.

9.1.3 Core Banking Mortgage Loans


The loan-management features in mySAP Banking CML (Core Banking Mortgage Loans)



of 74


support both medium- and long-term loans for real estate and other investment financing.

The Loans Management component offers functions for mapping the complete loan process for loans given and loans taken, from entering data on a potential contract right through to contract disbursement and the data transfer to Financial Accounting. It incorporates complex collateral management functions, support for decision-making and a range of options for tailoring your contracts.

These features provide the flexibility required for configuring the most individualized and sophisticated loan arrangements.

Loans Management is fully integrated in SAP Treasury, allowing you to measure the effects of loan activities on your liquidity or interest rate risk directly. Cross-application functions, such as SAP Business Partner Management or the Information System provide you with a comprehensive overview of the business relationships maintained with your loan partner.


In addition to the Query and Drilldown reporting options, CML offers a link to the Business Data Warehouse.

SAP delivers for the SAP Business Information Warehouse

Enhanced Extractors for transferring master data and flow information to the SAP Business Information Warehouse


2 ODS objects:

3 InfoCubes

5 predefined example-reports


The CML Business Content developed for SAP BW is designed primarily for use in strategic Management reporting for loans.

SAP CML delivers predefined reports as an example to the customer, e.g.

Position Lists

Position Overview

Position Evaluations Discount/Premium – Accrual/Deferral

Commitment

Balance Lists



of 74


Open Positions List for Contract

Flow Reporting

Due Date Lists Planned Flows / Posted Flows

9.1.4 Transaction Banking


Account Management is a central SAP application within the area of transaction banking, and is responsible for the management and processing of statutory reporting figures. It provides information on the receivables and payables between a bank and third parties. The accounts, balances and payment items are managed in the Account Management system. The currencies of the balances and turnover items are strictly separated, that is, no conversion takes place. The positions form the basis for external financial reporting, meaning the contract and turnover data stored here represents the data basis for creation of the balance sheet. One key processing function of the Account Management system involves the interest settlement and charges calculation for the accounts.

In addition, Account Management supports banks in evaluating results – using data warehouse systems such as SAP Business Information Warehouse, for example – to obtain information on operational data of transaction banking and to generate lists.


SAP delivers predefined scenarios (visibility scenarios) that are ready-to-go so you can put the solution to work right away. Each scenario contains pre-configured packages based on business scenarios. The SAP Business Information Warehouse part in these visibility scenarios contains:

Extractors for transferring data from Account Management to the SAP Business Information Warehouse

Master data of: Business partner, bank master data, contract, current account, card account, conditions, product, posting lock, transaction types, account closure, card cancelation …

Dynamic data: Payment item data, item counter


App. 175 InfoObjects, collecting data about products, accounts, cards, bank, business partner, addresses, conditions….

Appr. 30 Key figures, for example, limits of accounts, limits of cards, extra amount, item counter, credit balance, debit balance, condition amount …

appr. 12 ODS objects, collecting data about card master data, cards of



of 74


accounts, payment item, contract limit, current account master data

1 InfoCube, enabling the accumulation of account balances

1 Infoset, enabling an overview of products and linked cards

Process Chains

Predefined Queries are delivered, which provide information on the number of current and card accounts depending on the product type, information on balances and the account overview of an account holder.


The Account Management system, with its standard query customizing, offers a general statistical analysis of the accounts managed, their number and the way they are used. The information supports employees in account processing, marketing and product development in analyzing the quality and progress of their product portfolio.

The main benefit of integrating SAP Account Management into SAP BW is:

Most of the AM data is transferred into SAP BW.

Banks can flexibly define additional queries using the complete database in SAP BW.

The possibilities of querying data in SAP BW enable a reduction in traffic in the operational system and enhancement of performance.


Due to the large volumes of data in the Transaction Banking application and the fact that it is near-time-enabled, performance issues are extremely critical. To ease the load on the posting machine, all the operational reporting data was removed, and loaded into the BW system.

Numerous extractors are available with which all the reporting-relevant data can be transferred to the BW system and stored in InfoProviders. This results in a database that is available as basis for the most important evaluations in operational banking. For the implementation of the queries, which can differ from bank to bank, you can use the queries supplied with the TRBK Content as orientation. These provide examples of how you can implement evaluations, not only for accounts, cards and business partners, but also for various product statistics.



of 74


9.1.5 Claims


The business content of Claims Management contains information relevant to a claim, such as coverages (subclaim), claim items, payments, reserves, coverage referrals, claim activities, diagnosis and procurements (item grouping). Information is provided down to item level, this being the greatest level of details. Users can then merge and aggregate this information to suit their own requirements.

As of Release BI Content 3.3 Add-On, the BW Business Content of the Claims Management component (FS-CM) provides a technical merge of ODS objects according to business criteria. This merge releases the relational data structures from the source system. They are transferred 1:1 to the BW and are now merged on the data platform.

The reduction in the number of data pools also means that the Business Content is more clearly arranged on the data platform level, which is especially important for an enterprise-wide data warehouse. At this level the data is still kept at single record level.


SAP delivers predefined scenarios (visibility scenarios) that are ready-to-go so you can put the solution to work right away. Each scenario contains pre-configured packages based on business scenarios. The SAP Business Information Warehouse part in these visibility scenarios contains:

Extractors for transferring data from Claims Management to SAP Business Information Warehouse

Dynamic Data: 9 Extractors (claim, subclaim, claim items, payments, reserves, coverage referrals, claim activities, diagnosis and procurements)

Master Data: App. 75 Extractors for texts and app. 10 Extractors for attributes for above mass data extractors.


App. 10 ODS objects, contain data relevant to a claim (claim, subclaim, claim items, payment header, payment item, reserves, coverage referrals, claim activities, diagnosis and procurement)

3 InfoCube, enabling the evaluation of claims data, payment data and reserve data

Predefined Queries are delivered, which provides information about the number of claims by organizational Unit or loss location (region) in a certain period, the payment amounts by benefit type or by loss incident type as well as the Amount of open reserves per Insurance line of business



of 74



The main benefit of integrating SAP Claims Management into SAP BW is the availability of claims data in BW, that means the most important Claims data are transferred into SAP BW.

A further great benefit is the delta capability of the claims extractors, because of the huge data volume at insurance companies.

Insurance companies can flexibly design queries using the most of the database in BW.



of 74


Calculation of the liability rate is a scenario, that is used e.g. for indicating the workload of the individual organizational units or evaluate the number of claims per region for comparison liability rates between different regions.

Payment analysis is a further scenario, that can be used to figure out payment amounts per benefit types, coverage types, internal claim types or loss incident types. It can be distinguished whether they are indicated as losses or expenses.

Scenarios for the next releases are:

Fraud Scenario - One of the biggest problems faced by Insurance Companies today is identifying claims which are fraudulent. The impact of these claims on an insurance company are significant and even a small reduction would have a noticeable impact on profitability. By using the various characteristics available within the BW Claims Content it is possible to identify trends which may lead to instances of fraud.

Activity Profitability Scenario – A common problem held by most insurance companies is trying to reduce the Combined Ratio. The most easily controlled component of the combined ratio is the Cost Component, i.e. how much money is spent supporting claims activities. Three of these activities are Subrogation, Salvage and Litigation:

Subrogation – By capturing all of the activities that take place around subrogation, and insurance company can quickly identify the costs associated with this process. Further analysis gives the ability to determine if amount received via subrogation offsets the costs thus defining whether subrogation is profitable. An insurance company can then, by using this information, identify which claims are worthwhile subrogation targets.

Salvage - By capturing all of the activities that take place around salvage, and insurance company can quickly identify the costs associated with this process. Further analysis gives the ability to determine if amount received via salvage offsets the costs thus defining whether salvage is profitable. An insurance company can then, by using this information, identify which claims are worthwhile salvage targets.


Litigation - By capturing all of the activities that take place around litigation, and insurance company can quickly identify the costs associated with this process. Further analysis gives the ability to determine if amount received via litigation offsets the costs thus defining whether litigation is profitable. An insurance company can then, by using this information, identify which claims are worthwhile litigation targets.

Activity Benchmarks – As the claims process increasing becomes an outsourced activity for insurance companies, it is vital that they ensure that their customers are being treated correctly. To do this insurance companies often have contractual agreements with the outsourcers, which dictate activities, such as time limits that an activity must be accomplished within. BW Claims Content contains information that will allow an insurance company, as well as the outsourcer, to track these agreements and ensure that customers are treated with the utmost care.

9.2 High Tech

9.2.1 CRM Channel Sales Management Analytics


SAP for High Tech – CRM Channel Sales Management is designed specifically for high tech companies. The SAP solution further enables semiconductor, component manufacturer and OEM companies to work with and leverage their channel partners – helping these organizations to better market to, sell to, and service their customers.

Based on mySAP CRM, the Channel Sales Management solution enables high tech organizations to maximize their return on investment in the sales channel by increasing revenue, supporting sales representatives and partners, and minimizing sales channel costs.

Manufacturing companies that use channel partners to sell their products (as subcomponents of an OEM product) can use the solution’s design registration functionality for enabling these partners to identify specific opportunities where their product designs are matched and registered with the OEM.

With robust integration to facilitate cross-enterprise communication and collaboration, the solution helps High Tech companies enhance and strengthen critical partner relationships by providing the right information at the right time to authorized users within all levels of the organization - thus leading to higher sales revenues.

SAP delivers a powerful Channel Sales Management solution that you need to improve the organization’s bottom line.



of 74



SAP delivers predefined scenarios that are ready-to-go so you can put the solution to work right away. The SAP Business Information Warehouse contains:

Extractors for transferring data from CRM Channel Sales Management to SAP Business Information Warehouse


Three ODS objects, collecting resale data and design registration header as well as item data.

Two Info-Cubes and one Consolidated Info-Cube, enabling detailed analysis on reported resale, on projects, assemblies & design registrations as well as on linking resale data to design registration data.

The predefined scenario covers the receipt of resale information as well as creation of Design Registrations and transferring the data to the data warehouse, where it is analyzed.

For this, also predefined Queries are delivered, which provide information on

Query #1 Top 100 End Customers

Query #2 Transactional Analysis - Manufacturer's Calendar

Query #3 End Customer Analysis

Query #4 Customer Industry Analysis

Query #5 Cumulative and Current Month Resales Figures

Query #6 Incoming Resales figures for design registration

Query #7 Summary Matrix of Design Wins

Query #8 Summary report of Projects, Assemblies and Design registrations

Query #9 Design Registration Win/Loss analysis

Query #10 Design Win Analysis

Query #11 Resale Ranking - Product Movement

Query #12 Top 100 Profitable Products


SAP for High Tech – Channel Sales Management adds solid, bottom line business value because it:

Increases business opportunities and market share –Timely capturing and accurate tracking of new business opportunities help enhance revenue share, building new success and competitive advantage.

Enhanced value to your customers – Because the solution enables your partners to better market, sell, and service your products, your end customers receive added value that generates greater satisfaction.

Reduced channel support costs – The channel management capabilities of SAP



of 74


for High Tech help companies reduce costs across all sales support activities. Administrative costs can be cut using the solution’s proactive claims payments and auto-approving design registration. In addition, organizations can reduce stock rotation and price protection claims using the solution’s perpetual channel inventory tracking capability.

Improved channel partner relationships – The solution helps to improve relationships with channel partners because it makes it easier for your partners to work with you, which will encourage them to do more business with you.

The main benefits of integrating Channel Sales Management into SAP BW are

It provides with the tools to stay on top of the future market demand because it helps analyzing the current opportunity pipeline.

The increased visibility into your sales channels as well as better knowing your end-customer market. Based on standard key performance indicators (KPIs) it allows you to analyze product, region or partner performance.

It integrates resale and design registration information and helps measuring the performance of products and partners.

You can reward your channel partners for their design work in a timely and accurate manner.


Demand Creation and Design Registration (Opportunity Management) is one of the main areas of Channel Sales Management, which allows channel partners and internal sales personnel to register for design win opportunities.

SAP provides tools to analyze the current opportunity pipeline as well as perform win/loss analysis to help improve the win rate of future design registrations.

Another main area of Channel Sales Management is Resale Tracking, which provides the ability to capture and receive resale (POS) data from channel partners using EDI, XML, or Web-based interfaces and update the Channel Inventory information.

SAP provides tools to analyze product, region, and partner performance thus allowing organizations to link resale information back to Design Registrations.

9.3 Media

9.3.1 Enhancement of Intellectual Property Management to SAP BW


The Business Content for SAP for Media Intellectual Property Management (IPM), which is available with BI Content 3.3 Add-On, can be used to manage the entire IPM business



of 74


process in BW.

The BW Business Content available for IPM can be used as soon as it has been installed and there are no restrictions to its usage.

The Business Content for IPM focuses on the following areas:

License acquisition

License sales and license usage confirmations

License revenues (incoming royalties)

License settlement (outgoing royalties) and outgoing royalties data collector

Master data (interlinkages, hierarchical attributes, title hierarchy)


The following components have been added to the Business Content for IPM in BI Content 3.3 Add-On:

License acquisition – Acquisition of an IP uses the license acquisition contract.

BW makes a distinction between license acquisition contracts and the acquisition of services. The following are available in BW for evaluation of license acquisitions:

Extraction: 2 DataSources

License acquisition contract billing items

License acquisition rights-relevant items

Data model:

2 ODS objects

• ODS License acquisition contract billing data • ODS License acquisition rights-relevant data

4 InfoCubes for evaluating the license acquisition contract

• InfoCube ODS License acquisition contract billing data • InfoCube ODS License acquisition contract rights-relevant data • InfoCube Service contract billing data • InfoCube Service contract rights-relevant data

Outgoing Royalties - Outgoing Royalties are payments that the licensee makes to the licensor:

As a result of license exploitation (controlled by the license sales contract) in which the licensor has a proportional interest.

As a result of license acquisition (controlled by the license acquisition contract) from a licensor.

The following are available in BW for evaluation of outgoing royalties:



of 74


Extraction:

1 DataSource

• Outgoing royalties items

Data model:

1 ODS object

• Outgoing royalties items

2 InfoCubes

• Outgoing royalties for settlement data on the license acquisition contract

• Outgoing royalties for settlement data on the service contract

Outgoing Royalties Data Collector – The data collector is used to collect all settlement data as a preliminary level for outgoing royalties. The following are available in BW for evaluation of Outgoing Royalties (OR) Data Collector Royalties:

Extraction:

1 DataSource

OR Data Collector

Data model:

2 ODS objects

• OR Data Collector – Raw lines • OR Data Collector – Derived lines

2 InfoCubes

• OR DataCollector – Raw lines • OR Data Collector – Derived lines


The analysis options in the BW Business Content enable all business processes associated with IPM to be represented in a transparent format.

Decisions and measures to optimize the business strategy employed and safeguard future success can be derived by analyzing the data available on the license acquisition contract, license sales contract with license usage confirmations and the incoming royalties, billing and settlement data.


The SAP for Media Intellectual Property Management (IPM) business scenario is a comprehensive solution whose functions cover the entire value creation chain for an Intellectual Property. This includes the acquisition and creation of Intellectual Property,



of 74


development of new media products, sale of licenses and rights through to management of license revenues and royalties. IPM also contains functions for maintaining business relationships with rights owners, licensors and licensees, actors or authors of Intellectual Property.

All evaluations of business transactions and the rights owned in IPM are performed using BW.

9.4 Pharma

9.4.1 Pharmaceutical Call Sample BW Business Content


The main goal of the BW Pharmaceutical Call Sample Detail Business Content is to enable and improve efficient analysis within SAP BW for the pharmaceutical industry (especially for the US).

Pharmaceutical companies relay on external market research services to gauge their products' activity and performance (i.e., the number of prescriptions written for the product, who prescribed them, etc.) because they cannot estimate directly the effectiveness of their Sales Force through their own Sales. Thus, Sales representatives (sales reps) of pharmaceutical companies influence the prescribers but do not sell to prescribers. Therefore, they cannot know certainly whether their drugs are finally prescribed or not by the visited doctor. Once a drug is prescribed, the patient has to buy the drug in order to generate a turnover for the pharmaceutical company.

External data for analysis purposes

External data are for this reason determinant. There are several data providers in the market. The biggest, which is present in 60 countries worldwide, is IMS Health. All bigger pharmaceutical companies buy IMS data. For this reason, SAP has first of all integrated the following IMS products in the standard BW (BW 3.0B):

1) The DDD IMS data

2) The Xponent standard IMS US structure for the prescriber data: it delivers the exact information about what was prescribed by every single physician.

The external data from IMS is large and is frequently updated. This data provides the greatest value when compared and analysed against the effort invested in promoting the product to the physicians. This analysis is crucial for sales planning



of 74


and market research; firms use it for various purposes including sales representative compensation, doctor targeting and sales force alignment.

CRM data for analysis purposes –the CSD information

The effort invested by the pharmaceutical company is captured first of all in CRM by the Sales reps after their visits to doctors' offices primarily using three measures sales Call, product Sample and Detail (CSD) information, normally referred to as SFA information.

A sales call represents a rep visit to a doctor.

A product sample represents the number of sample product packs the doctor received.

A product detail represents an interaction with the doctor about a specific product. Often for a single call, there will be several "details" as the rep promotes various products in his portfolio.

The CSD information has to be then transmitted to BW in order to be there analysed with the external IMS data.

From the CRM data base perspective, the following CRM information domains are involved in order to deliver from CRM to BW qualitative information easily usable for the future analysis:

1. Organizational Management

2. Data Distribution

3. Additional Pharma fields with Business Partner

4. Sample Management

5. Data Cleansing

6. Activity – Product Correlation

7. Free Goods.

Tasks of this new BI Content 3.3 Add-On pharmaceutical Call Sample Detail Business Content:

It provides all the needed information from the IMS data and the CRM data (territories, activities, samples) within BW 3.3 standard in order to run efficient Call, Sample, Detail (CSD) reporting.

These new standard effective CSD reportings will enable pharmaceutical companies to have an optimal understanding about their physician profiling and segmentation for each Sales rep territory. They can, for example, determine which physicians place the most or the fewest prescriptions and the causes for these differences.

With this vision, they can then optimize the value and profitability of their direct sales force and of their other sales channels – such as their interaction centers or their Internet



of 74


services.

Moreover, they can support the effort of their sales force by designing adapted market-driven programs such as discounts, campaigns, promotions, special offers, and advertising and target specific groups of customers with clinical information, time-limited offers, or incentives.


Prerequisite for an efficient pharmaceutical analysis in BW:

New specific extractor for the pharmaceutical Business Partner Fields from SAP CRM to SAP Business Information Warehouse

As a prerequisite, the pharmaceutical company needs to have a very detailed CRM data in order to compare it efficiently to the external data from IMS. The analysed business partners (which are in the ethical business the physicians), who are visited by the field force, are not the recipients of goods, or parties placing orders. To this extent, clinics or doctors cannot be distinguished on the basis of the account groups but need to be distinguished with other specific criteria. Those criteria are the specific pharmaceutical business partner fields implemented in CRM 4.0 such as the group and subgroup fields, the main & additional qualifications fields, the function and position fields, the market segmentation fields (Bricks, Nanobricks).

Therefore, it is now possible in BI Content 3.3 Add-On to extract the new SAP CRM 4.0 pharmaceutical specific fields of a business partner and do analysis for physicians based on this pharmaceutical specific classification information.

The new BI Content 3.3 Add-On pharmaceutical Call Sample Detail Business Content:


New pharma-specific InfoProviders (ODS objects and InfoCubes), containing data about the Sales Analysis for territories and activities based on IMS data

New queries, providing information about:

Single sales development: development of sales (at the detail level of the Sales Rep‘s territory)

Market volume: Development of market volumes (at the detail level of the Sales Rep‘s territory)

Market Share: Development of market share (at the detail level of the Sales Rep‘s territory)

Sales and Samples: Sales development vs. amount of distributed samples of prescribers for last 3 months



of 74


Sales and Visits: Sales development vs. prescribers calls for last 3 months

Top n prescribers: Shows the Sales Revenue top n prescribers of the last month (at the detail level of the Sales Rep‘s territory)

These reporting possibilities are bundled in one role for the Sales Representative for the US market.


The BI Content 3.3 Add-On Pharmaceutical Call Sample Detail Business Content adds a solid, bottom-line business value specially for the US market because it:

Reduces BW implementation costs for the pharmaceutical company by using this pre-configured new pharmaceutical BW content.

Increases visibility of the company market share, revenues, and profits in connection to their sales activities, with the ability to respond quickly in volatile markets.

Reduces costs as a result of the ability to deploy resources where they can most effectively handle demand. The optimal market visibility allows to realign the Sales force to new territory in order to improve its global performance.

The main benefit of integrating the SAP CRM data (such as Sample Sales Detail, activities and territory data) and the IMS data into SAP BW is to give to the pharmaceutical company a ready-to-go solution to allow an optimal visibility of the company’s performance and Sales efficiency in its market.

In addition to standard key performance indicators (KPIs) it allows the pharmaceutical company to estimate at the product line level or at the product level the quality of the interaction of the Sales Force and the prescribers. This can result in new practical measures to improve this interaction (such as realignment, new guide lines for giving samples away…).

9.5 Consumer Products

9.5.1 Store Audits


Store audits are based on visit reports. In visit reports, field sales representatives enter data about products in stores, for example, shelf-edge prices, out-of-stocks, and facings. You can use these visit reports to analyze how your products are being positioned on the market and to check if retailers are adhering to agreements.



of 74



An extraction of activity items from SAP CRM is available with BI Content 3.2 Add-On. CP visit reports is just another name for activity items. Consequently, based on the existing extraction process, CP Industry Store Audits contain

an ODS to take care for corrections made to visit reports

an InfoCube enabling the analysis of store audits, and

four queries to check and compare in-store conditions, in particular distribution and out-of-stocks.


Store audits are a main source of information for the account manager to check the customer's compliance. Furthermore, the reason for a decline in market share can be traced back to customer out-of-stocks and a low distribution level if this was really causing the decline. It's also instrumental to get competitive information at the point of sale to the consumer.


The solution can be used in an analysis of a market share decline or of a low promotional performance. Such an analytical scenario is not part of the BI Content 3.3 Add-On delivery.

9.6 Retail

9.6.1 CRM Workforce Management Retail – Operational Reporting


The strategic objective of this project is to build a new set of business functions into the WFM CRM product that will provide preliminary functionality for the Retail QSR market. The solution will allow for central planning (forecasting), scheduling (optimization of employee resources), and operational reporting at the location level. The scope of the project will be constrained by the 4.0 CRM release schedule.

Retail WFM performs the complex process of creating optimum employee schedules by utilizing business variables entered during implementation and actual data captured throughout the day.

The "optimization engine" at the heart of Retail WFM finds the best possible floor schedule while balancing such weighted variables as staffing needs, employee skills, payroll requirements, employee availabilities, workplace rules and performance standards. The result is that scheduling is transformed from a necessary but tedious, clerical function, into an analytical, cost-effective, business



of 74


management process that is visible at all levels of the enterprise.

The solution will be built in an open fashion allowing for integration to other systems.

The functional areas of the proposed application are:

System Configuration and Maintenance

Forecasting

Schedule Creation and Maintenance

Employee Data Maintenance

Reporting/Analytics


Extractors for transferring data from CRM/WFM to SAP Business Information Warehouse

Enhancement of existing Content:

• Schedule Details Extractor (delta extractor) • Indicator Details Extractor (delta extractor) • Workload Details Extractor (delta extractor)

New Content:

• WFM Org Configuration Extractor • Actual Scheduling Details Extractor (delta extractor) • Master Data Extractors (e.g. Employee Attributes, Employee

Type, etc.)


Enhancement of existing Content:

• 3 ODS objects: (Schedule Details, Indicator Details and Workload Details) collecting raw transactional schedule, indicator and workload data from CRM/WFM

• 3 InfoCubes: (WorkArea Details, WorkArea Total, Employee Details) enabling the evaluation of all kinds of KPIs (e.g. total schedule hours, overtime hours, total actual sales, etc.), and also weekly schedule, daily coverage, indicator value and workload value

New Content:

• 2 ODS objects: (Schedule Actual and WFM Org Attributes) collecting raw transactional actual data imported from a third-party Time Management system, and WFM Org Attributes data

• 1 InfoCube: (WFM Org Daily Total) enabling the evaluation of Org Daily KPIs (e.g. benefit pay)

• 3 Virtual Cubes: (Weekly Schedule, Daily Coverage and Volume Indicator) enabling real time evaluation of schedule, coverage and indicator value

• 1 MultiCube: specifically for KPI report



of 74


Process Chains:

7 predefined Queries: 3 Queries are used for real-time reports, the other 4 Queries are used for KPI reports

6 predefined Crystal Reports: 3 real-time reports which provide real-time information on Weekly Schedule, Daily Coverage and Volume Indicator; 3 KPI reports which provide close-to-real-time KPIs of Sales, Schedule vs. Actual Statistics and other statistics.


Issues facing retailers and QSRs include the need for a scheduling solution that enables the control of multiple locations from a central location. The ability to efficiently and effectively control labor costs, while simultaneously maintaining and/or increasing service levels, gives companies significant market advantage. Considering this, and the number of sites and employees being impacted within an organization, these companies are looking for solutions that will enable them to leverage web technology to accomplish the following objectives:

Monitor and impact compliance levels across the enterprise easily

Modify configurations based on changing business needs

Reduce costs associated with roll out and the training of new applications

Control operations and maintenance centrally

Allow management to control scheduling

Visibility and control at store level provide the information necessary to make “real time” business decisions, which result in cost savings and/or increased sales performance. This also allows for standard business practices to be implemented across the enterprise. Performance can then be monitored and addressed for all locations in a timely manner.


Operational Reporting is one of the application areas in CRM Work Force Management. SAP will provide a means of delivering 6 operational reports, for which the Business Content in SAP BW will be developed.

This scenario covers the Locations/Corporations operating process from generating a sales/volume forecast, to creating a schedule, to configuring and running operational reports. The following graphic shows the business partners involved and their role in the scenario:



of 74


Vendor

SAP CRMWFM RetailApplication SAP BW

Generate Forecast Submit for Review

Generate Demand Plan

ManagerReviews Completed

Schedule

ManagerMaintainsSchedule

Manager configures,views or prints

reports based onrole assigned.

Operational Report

Manager Accesses

Calculation Status

Manage EmployeeInformation and

Updates

WFMCalculation Server

Return completedschedule

Return calculationstatus information

UtilizeBusiness Partner

Configure IMG and Master Data

Submit/ Load Volume Data Inputs

Load new

Business Partners

IC Administrator monitors schedule

calculationprocessing

Submit for Calculation or for

Re-calculation

Select Schedule Weekto be Created



of 74

SAP® Preliminary BW BCT List for BI Content 3.3 Add-On

9.6.2 SAP POS Data Management


SAP POS Data Management is a stand alone, R/3 independent point solution that offers comprehensive point of sale data management, from the cash register to the retail application. The solution enables customers to run sales analytics based on POS sales information in various ways in a stand alone SAP BW. This approach allows you to load POS data directly into an SAP BW without being forced to process it first in the merchandise management system and then transfer it to BW. The POS inbound processing engine is an encapsulated application residing on the BW platform that carries out all POS related processing steps.

The solution is thought to be a basis component that can easily be integrated in future reporting and analytical scenarios. It can also be complemented with other areas of reporting within SAP BW containing, for example, stock or cost/revenue information to create combined reporting views, as required by either the demand side or the supply side. SAP POS Data Management can also be useful for enterprises that have to deal with POS data of their customers, such as CPG manufacturers that process Retail POS data for trade promotion management and category management, or convenience stores or service station operations that need to process POS data from their franchisees.

Description of the (new) BW Business Content SAP POS Data Management consists of: 1) POS Inbound Processing Engine: A fully encapsulated POS inbound application

residing on BW, processing and distribution of all POS information to follow on systems through various internal and external interfaces.

2) POS Analytics: The POS content is a new set of reporting features including extractors,

InfoSources, cubes and queries for the analysis of products, stores, customers, as e.g.

Comparable/non-comparable store reporting

Reason code reporting, e.g. for returns reasons

Event reporting allows long-term comparison of sales-events (e.g. promotions, themes, campaigns, etc..) over time

Price and margin information even when used as stand alone solution (moving average concept)

Retail calendar provides the ability to report using fiscal year variants

Ready-to-run example Web-reports with enhanced performance

Loss prevention


Title: SAP BI Content 3.3 Add-On – Preliminary Business Content List File: BWBCTLIST33ADDON_v2.doc Date: 11/3/2003

of 74


Main business benefit/main question answered with the (improved/enhanced) solution

The aim of SAP POS Data Management is to reduce the total cost of ownership for retailers, by offering advanced interface options that accept all major messages coming from the POS.

It will improve the performance of the whole POS inbound processing and simultaneously reduce the system load on the retailer's merchandise management system.

The new solution provides a number of significant benefits:

Stand alone and out of the box POS inbound engine and reporting content

New architecture with enhanced performance

Decrease system load on merchandise management platform by performing sales audit on a separate system, better compression, redirecting traffic

Flexible data distribution

Simplification of inbound interfaces by providing one interface that covers all major POS inbound business cases

Support of Industry Standards for POS inbound

Lean processing when no error occurs during POS inbound, data is provided to follow on processes directly

Compatibility with all existing SAP POS inbound message types in order to secure the investment in existing converter technology

Automatic check rules & automatic error correction will liberate users from many manual tasks

Expandable and modular solution

9.6.3 Global Trade Management


The Business Content for Global Trade Management can be used to evaluate trading contracts as logistics documents, on the basis of statistical characteristics. The content enables the user to monitor the business volume on different levels.


Within BW release 3.2 the infrastructure was created, to connect the Global Trade Management application to BW. In the first step the extractor and tree ODS objects was created to store the trading contract data on document level in BW.

“SAP delivers predefined scenarios (visibility scenarios) that are ready-to-go so you can put the solution to work right away. Each scenario contains pre-configured packages based on business scenarios. The SAP Business Information Warehouse part in these visibility



of 74


scenarios contains for BW release 3.3

Extractors for transferring data from GTM to SAP Business Information Warehouse


3 ODS objects, collecting data about trading contracts

3 InfoCubes, enabling the evaluation of the turnover and GTM

1 Multicube, enabling side independent analyzis

The visibility scenario covers the GTM process from creating trading contracts (purchase, sales and both sided) to transferring the data to the data warehouse, where it is analyzed. For this, also predefined Queries are delivered, which provides information about the actual turnover on different organization levels in different time periods.


The main benefit of integrating SAP GTM into SAP BW is the increased visibility throughout a company’s actual business situation. Comparing the business volume on a detailed level enables the user to monitor and react to actual business requirements.


Trading contracts are the logistical documents in GTM. In the first scenario SAP focused on this document, to give the company the possibility to monitor their business on this level.

The content gives information about the business to the management on a high level and allows traders to drill down on a very detailed level (document level) for managing and monitoring the daily workload.

For this a drill from multiprovider to infocube and ODS Object is provided.

The following picture gives an overview about the cotent.



of 74


Infosource/ Extractor for Schedule lines ( 2LIS_46_SCL) ODS objects

Infocubes

Multiprovider



of 74


9.7 Utilities

9.7.1 Round-Off BI Content for KAM Portal Utilities


The integration of BI Content for planning and analyzing utility service quotations into the KAM portal for the key account manager (KAM) utilities is enhanced.

In particular, Web templates for the comparison of planned and actual key figures of utility service contracts are provided.

Furthermore, analysis of consumptions, revenues, cost and contribution margins based on master agreements for cross-contract billing is enabled.


With the new content, SAP provides

1 Extractor for the hierarchy of contracts related to master agreements. The hierarchy is extracted from the IS-U-contract database as a result of replication from CRM.

Web templates for the analytics part of the KAM portal.

The new hierarchy is part of the BW info object for IS-U-contracts. Therefore, all relevant ODS objects and InfoCubes of the sales (CRM) info area are enhanced by that info object.


The enhancements of the BW content support:

Key account managers in planning and analyzing the profitability of their non-residential customers (pure portal-based approach)

Sales controllers in monitoring the master agreements of their key accounts

9.8 Engineering, Construction & Operations

9.8.1 Business Content for Project Risk Management for Contractors (PRC)


This application provides functions to help you administrate and analyze projects and organizational units according to balance sheet key figures. Consequently it supports enterprise management and controlling particularly for constructions in progress and plant



of 74


engineering and construction. These are often controlled locally, in other words, there are several lines of business, business areas and subsidiaries. Projects are frequently carried out by several subsidiaries or departments. Balance sheet key figures from the projects are an important information and controlling instrument for these organization units.

The joint venture represents an artificial level on which project key figures are collected. The joint ventures are displayed via the joint venture.

The project-oriented enterprise structure aims to structurally represent the organizational units in such a way that it is possible to assign projects to them. This enables detailed and concise reporting of balance sheet key figures from projects on the different aggregation levels of the enterprise structure.


The SAP Business Information Warehouse part in this scenario contains:

Extractors for transferring data from R/3 Enterprise Extension 2.0 to Business Information Warehouse


3 ODS objects, collecting data about JVA line items (for delta upload, 1 for plan and 1 for actual data) and equity shares of the ventures 2 InfoCubes, enabling the evaluation either on summary items or on line items from JVA

The BW Business Content covers the reporting of project balance sheet key figures from a single project to each level of the organizational unit of the company’s ORG chart transferring the data to the data warehouse, where it is analyzed. For this, predefined queries are also delivered, which provide information about the most common key figures for the financial part of a project risk management.


With Project Risk Management for Contractors (PRC) customers are able to report balance sheet key figures from a single project to each level of the ORG chart. Main benefits for customers are

Decreased financial risk on each project thanks to a greater set of key figures that can be reported for each project

Better visibility into operations and increasing accountability across the enterprise as financial data can be managed on any organizational level down to projects and sub-project level, creating,

Increased accuracy and new opportunities for group reporting for project centric enterprises.



of 74



The scenario can be used for group reporting based on a time-dependant, flexible organizational structure delivering balance sheet key figures on each level of the ORG chart.

9.9 Oil & Gas

9.9.1 Business Content for Joint Venture Accounting (JVA)


BW Business Content for JVA helps you to administrate and analyze operated and non-operated joint ventures, including:

1. JV reporting in BW - balance sheets and P&L statements by venture allow you to analyze profitability of, and standing in, each joint venture.

2. Lease Operating Statements - enables companies to analyze results based on cus-tomer-defined hierarchies. Additionally BW reporting will facilitate unit cost calcula-tions such as per BOE cost used by customers for relative comparisons.

3. Project reporting by Joint Venture - enables companies to analyze each of their pro-jects at a finer level of detail when subdivided by venture, and also allows companies to separately analyze only that project data which are belonging to joint ventures.

4. Venture analysis - inclusion of JV Master Data allows companies to carry out analy-sis and comparisons of their ventures, such as equity percentages, projects etc.

5. Billing reporting and analysis - timely and full collection of funds from JV partners is key to maintaining good cash flows. BW-reporting will enable companies to carry out this and other analyses.


The SAP Business Information Warehouse content for JVA contains:

Master Data and Transaction Data Extractors for transferring data from R/3 Enter-prise Extension 2.0 to Business Information Warehouse which form the basis to en-able customers to develop their own information structures, such as InfoCubes and ODS Objects.

Characteristics and common key figures for analyzing joint ventures



of 74



JVA customers gain better reporting and analytical flexibility with the BW Content for JVA, as compared to the Report Writer reports available in R/3. The main benefit for the customer is better visibility into jointventure operations and new opportunities for venture re-porting with the additional reporting flexibility that allows individual customers to customize their reports and enable customer and/or venture -specific data analysis.


The BW Content delivered provides the basis for customer-specific scenarios, where cus-tomers can set up individual JV reports that are specific to their business operations.

9.10 Public Sector

9.10.1 Grants Management – Grantee organizations


SAP Grants Management – Grantee (GM) enables customers to plan, budget, execute and report on any external source of monies received in the form of grants or other financial instruments (i.e. contracts, cooperative agreement, etc.). These grants and financial instruments are binding agreements between sponsors and grantee organizations and subject to the sponsor’s terms and conditions. The GM functionality allows grantee organizations to comply with all of the grant’s terms and conditions and also allows the grantee organization to control and report based on an individual sponsor requirement(s) as well as the grantee organization’s own fiscal year and currency.

GM provides functionality to cover both pre-award and post-award business processes:

Pre-Award (prior to receiving a grant)

Master Data Creation

Sponsor -> SAP Business Partner

Grant (Draft, Proposal and Application)

Grant Master approval with Workflow

Budget Planning: Proposal and Application

Budget Planning approval with Workflow

Post-Award (after receiving a grant)

Master Data



of 74


Grant Award with Workflow

Budget Awarded Grant

Possible Integration with FM Budget and Control System

Execution and Compliance with Grant Rules

Consume Budget on Grant

Posting Control Based on Sponsor Rules

Overhead Calculation and Posting

Cost Sharing Requirements

Billing

Resource Related Billing (RRB), Milestones, Installment/Periodic, Manual A/R

Reporting

Closeout


SAP delivers the Grants Management – Grantee (GM) Business Information Warehouse content with detailed and aggregated activity information. Extractors are available for master data and transaction data. Master data consists of text and attributes for the following objects: Sponsor, Grant, Fund, Sponsored Program and Sponsored Class. Transaction data consists of line items, totals, budget items and the grant’s status.

The transactional data extraction process provides the ability to setup BW reporting based on the detailed transaction information or at a higher level or both. Using the detail transaction data extraction on line items and budget items enables BW to link GM information with other BW reporting modules (for example Funds Management).

In addition to the transactional data reporting, GM BW reporting offers reports for Grant status (lifecycle statues and network (i.e. user defined) statuses, and Grant responsibility reports.

Below is a list of the available BW content for GM:

Extractor: Totals, Line items, Budget items, Status items, Responsibility items, GM dimensions.

Operation Data Storage (ODS): Line item, Budget item, responsibility item.

Infocube: Aggregated Key Figures, Detail Activity, Budget Activity, Status Network and Responsibilities.

Reports: Grant overview, Grant Sponsor, Budget vs. Actual/Commitments, Budget Detail, Activity Detail, Lifecycle status (representing the grant business process), Responsibility status (i.e. responsible person/s).



of 74



The Grants Management – Grantee (GM) solution with its reporting data in the SAP business data warehouse is required for all grantee organizations to satisfy sponsor and grantee organization/internal reporting requirements. This information is then available for flexible reporting and used in conjunction with Crystal report.


The business scenarios can be categorized into pre-award and post-award business scenarios. In both all business transactions involving the Grant are recorded in the GM ledgers and controlled by the settings in the GM master data. Pre-award scenarios such as:

Monitoring the number Grant proposals, applications and awards by responsible person or organizational unit

Tracking the success rate by responsible person or organization unit

Evaluating the outstanding grant proposals and/or applications for a responsible person or organization unit

Grant proposals or applications with cost sharing requirements

Monitoring value (i.e. budget) of grant proposals or applications

Post award scenarios such as:

Grant award budget to actual/commitments comparisons

Grant award budgets by responsible persons or organizational unit

Comparison of budget proposed, submitted to the sponsor and actual funded amount of a grant

Identifying the grant awards terminating within 30, 60 or 90 days

Budget, actuals and commitments in sponsor report formats using Crystal reports

The GM architecture (see slide below) supports the GM business processes (see slide below), thus allowing grantee organizations to administer and analyze grant pre-award and post-award business process to meet both sponsor and internal reporting requirements.



of 74




of 74


9.10.2 Federal Government BW Reporting

General Information Abstract of the Business Solution

The Federal Government application ontop of Funds Management implements the financial transaction demanded from the US Federal Government. Specific organizational processes are defined and verified through a JFMIP certification process. The requirements are available on websites like www.jfmip.gov , www.whitehouse.com/omb (budgeting) and http://www.fms.treas.gov (treasury).

The Federal Government implementation predefines the financial processes for budgeting, accounts payable and receivable processes. It defines the communication between agencies, OMB (budget and reporting agency) and Treasury (spending and reporting agency).

Reports built out of the BW Federal Government content help to monitor the activities and provide in-house as well as external reporting. The reports are cross-functional covering FI, CO and FM information and have in detail as well as summarized data available.


SAP delivers the Federal Government Business Information Warehouse content with detailed and aggregated activity information. All Federal Government financial transactions would be available and can be visualized with the trial balance report.

Line item and totals extractors transfer the data from the Federal Government transaction tables into SAP Business Information Warehouse

One ODS will be fed from the line item extractor. This allows merging information with ODS from other modules (for example purchasing) to detail the information even more.

2 Infocubes show the financial detail and by organizational layer aggregated activities.

The trial balance report displays the activities in a defined format.


The Federal Government solution with its reporting data in the SAP business data warehouse is required for US federal government agencies. With its solution, all financial transactions are captured and combined with the Federal Government attributes. This information is then available for flexible reporting.



of 74

http://www.jfmip.gov/

http://www.whitehouse.com/omb

http://www.fms.treas.gov/



This solution is the overall solution for all US Federal Government financial processes. To highlight one process particularly would be the budgetary accounting flow:

When an agency receives budget authority and begins to use those budgetary resources, the funding progresses through various statuses. These statuses are tracked through specific budgetary accounts. The following provides examples of some of the various budgetary statuses:

Appropriation – from Congress

Budget Authority

• “Discretionary” (provided in appropriations) or “Mandatory” (controlled by laws other than appropriations)

• ”Definite” (law specifies an amount) or “Indefinite” (law does not specify an amount)

Apportionment – from OMB

Method to further limit spending by quarters (Category A) or by programs (Category B)

Budget Authority cannot be alloted until apportionment by OMB

Allotment – within the agency

Transfer of budget authority to be available for use

Commitment – within the agency

Internal reservation of funds / budget authority

Undelivered Orders – within the agency

This is a firm/binding/legal requirement to fund a specific purpose – contract signed. As a result, these are also called obligations.

Delivered Orders – within the agency

All the way through this process BW makes financial reporting available to visualize the budgetary status, account balances and fund status.



of 74




of 74

ã SAP AG 2003, Title of Presentation, Speaker Name / 3

Budgetary Accounting -- Flow

Appropriation

Apportionment

Allotment Commitment UndeliveredOrders

DeliveredOrders

Page: 20 [SAP1]This needs to be repaired!