中学生怎样遵守规则:FAQ: SAP BI Some configuers and solutions

 

Why DTP and not IP in SAP BI 7.0

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0ada4bf-e963-2d10-aa89-abb9eeae7723?QuickLink=index&overridelayout=trueReading Master Data
In your transformation, you want to assign the CUSTOMER field of the DataSource to the 0COUNTRY InfoObject in your target. To do so, you assign the 0CUSTOMER InfoObject to the CUSTOMER field in the rule details so that the attribute 0COUNTRY in 0CUSTOMER can be read.To be able to specify time dependence for reading master data, assign the CALDAY field to the 0COUNTRY rule as an additional input field. The CALDAY field of the DataSource also needs an assigned InfoObject.Assign 0CALDAY to it so that 0CALDAY's properties can be read. Then enter a time.Transaction Key SPRO > Material Management > Purchasing > Conditions >define price determination process > Define transcation key
SBIW-> Settings for Application-Specific DataSources (PI) -> Logistics -> Settings: Inventory Controlling -> Transaction Key Maintenance for SAP BW.
Transaction Key Maintenance for SAP BW
In this operation, you can transform key figures in the transaction key for a suitable transfer control of the logistics movement data in SAP BW.
This transformation is made for each area and LIS application.
Example:
Control for Purchasing in CP.
At this level you can assign transaction keys for the individual business transactions.
Settings:
Application components: MM,
Application: 02 (Purchasing)
Transaction key: 1 (PO for external vendors)

Further notes
Transaction key identification (name range for the SAP transaction key: 001-499) only takes place as long as an industry sector was defined.
Customer-specific transaction key can be created (customer name range: 500-999).
These transaction keys must exist in the relevant customer exits for the relevant LIS applications.
what is Process Key Process key are normally used when Implementing the MM Scenarios. Process key is used to interpret document information from r/3 to bw.

The extractors presented here represent, in principle, structures that collect document-specific information from the logistics application Purchasing and transfer it to the SAP BW.

Many key figures are yielded from the application. These must be transferred to the SAP BW with the help of the extractors. SAP ensures that document information is interpreted in advance with the help of a 'process key' so that key figures, which describe and measure the particular processes, can be more easily derived for customers.

how to
to activate : transaction Transaction MCB_ in r/3

sample in purchasing
Here is a list of the values that process key - BWVORG can assume, according with the purchasing item type, processed document and purchasing order type:
1 - For non return items:

a) Document type: Purchasing order

- Normal purchasing order - BWVORG = 001

- Stock transport order - BWVORG = 011

- Cross company order - BWVORG = 021
b) Document type: Goods receipt

- Normal purchasing order - BWVORG = 002

- Stock transport order - BWVORG = 012

- Cross company order - BWVORG = 022
c) Document type: Invoice receipt

- Normal purchasing order - BWVORG = 003

- Stock transport order - BWVORG = 013

- Cross company order - BWVORG = 023
d) Document type: Scheduling agreement

- Normal scheduling agreement - BWVORG = 004

- Stock transport agreement - BWVORG = 014

- Cross company agreement - BWVORG = 024
e) Document type: Contract

- Normal contract - BWVORG = 008

- Cross company contract - BWVORG = 028
f) Document type: Request of quotation

- Request of quotation - BWVORG = 009

- Quotation - BWVORG = 040

2 - For return items:
a) Document type: Purchasing order

- Normal purchasing order - BWVORG = 005

- Stock transport order - BWVORG = 015

- Cross company order - BWVORG = 025
b) Document type: Goods receipt

- Normal purchasing order - BWVORG = 006

- Stock transport order - BWVORG = 016

- Cross company order - BWVORG = 026
c) Document type: Invoice receipt

- Normal purchasing order - BWVORG = 007

- Stock transport order - BWVORG = 017

- Cross company order - BWVORG = 027
d) Document type: Scheduling agreement

- Normal scheduling agreement - BWVORG = 041

- Stock transport agreement - BWVORG = 051

- Cross company agreement - BWVORG = 061

Can also please refer to the link which gives some more idea:
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/process-key-for-vendor-return-in-purchasing-118683
The implementation of your SAP System covers the following phases:
The implementation of your SAP System covers the following phases:

1. Project PreparationIn this phase you plan your project and lay the foundations for successful implementation. It is at this stage that you make the strategic decisions crucial to your project:

• Define your project goals and objectives
• Clarify the scope of your implementation
• Define your project schedule, budget plan, and implementation sequence
• Establish the project organization and relevant committees and assign resources

2. Business Blueprint
   In this phase you create a blueprint using the Question & Answer database (Q&Adb), which documents your enterprise’s requirements and establishes how your business processes and organizational structure are to be represented in the SAP System. You also refine the original project goals and objectives and revise the overall project schedule in this phase.
3. RealizationIn this phase, you configure the requirements contained in the Business Blueprint. Baseline configuration (major scope) is followed by final configuration (remaining scope), which can consist of up to four cycles. Other key focal areas of this phase are conducting integration tests and drawing up end user documentation.
4. Final Preparation
   In this phase you complete your preparations, including testing, end user training, system management, and cutover activities. You also need to resolve all open issues in this phase. At this stage you need to ensure that all the prerequisites for your system to go live have been fulfilled.
5. Go Live & SupportIn this phase you move from a pre-production environment to the live system. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.

Standard Data Store Object

Types of DSO

• Standard Data Store Object (Ref. Fig. A)
• Data Store Object with Direct Update (Transactional ODS using 3.x)
• Write Optimized Data Store - BI 7.0
o Contains only active data table used to manage huge data loads

Motivation for DSO

• Consolidation & Cleansing
o A further motivation is the need for a place where data can be consolidated and cleansed. This is important when we upload data from completely different Source Systems.
o After consolidation and cleansing, data can be uploaded to Info Cubes.
• To store data on document level
• Overwrite capability of characteristics
o Not possible to overwrite data in Info Cube as whenever data is added to Info Cube, this data is aggregated. So data can be overwritten in DSO and this provides a significant capability to BW.
• Reporting
o Direct on document level data
o Drilldown from Info cube to document level
Architecture of Standard ODS / DSO (7.x)

"ODS Objects consist of three tables as shown in the architecture" - Source: SAP Docs
Fig.A - ODS Object Structure

The Transition: ODS Objects (3.X) to DSO (BI 7.0)

The ODS consists of consolidated data from several Info Sources on a detailed (document) level, in order to support the document analysis. In the context of the DSO, the PSA makes up the first level and the DSO table makes up the second level of the DSO. Therefore, the first level consists of the transaction data from the source system, and the second level consists of the consolidated data and data from several source systems and Info Sources. You can run this analysis directly on the contents of the table, or run it from an Info Cube query into a query by means of a drilldown.
Fig. B. Sample schema for Reporting using ODS Objects (using Update Rules & Transfer Rules) * Note: UR refers to Update Rules
Prior to existence of DSO, decisions on granularity were based solely on data in Info Cube. Now Info Cube can be less granular with data held for a longer period of time versus the DSO which can be very granular but hold data for a shorter period of time. Data from the ODS can be updated into appropriate Info Cubes or other ODS Objects. Reporting on ODS can be done with the OLAP processor or directly with an ODS query.
In this Fig. B, data from Data Source A and Data Source B is uploaded to a PSA. The PSA (Persistent Staging Area) corresponds to DSO. From the PSA we have the possibility, via transfer rules, to upload data to DSO. The DSO is represented here as one layer, but depending on the business scenario, BI DSO can be structured with multiple levels.
Thus, the ODS objects offer data that are subject oriented, consolidated and integrated with respect to same process on different source systems. After data has been stored, or while the data is updated in the ODS, we have option of making technical changes as well as data changes. In the ODS, data is stored in a de-normalized data structure.

Structure of ODS

While transferring data from PSA to ODS objects, rules (Transfer Rules) can be applied to clean records and transform them to company-wide standards for characteristic values. If it is meaningful at this stage, business logic may also be applied (Update Rules).

Sample Scenario for a Standard DSO

Consider an example involving a Standard DSO in SAP BI 7.0.Let's check flat file records, the key fields are customer and material and we have a duplicate record (Check Rec.2). The 'Unique Data Records ‘option is unchecked which means it can expect duplicate records.
Figure C. Explains how records are captured in a DSO (Refer selected options below)
After update rule, Record 2 in PSA is overwritten as it has got same keys. It's overwritten with most recent record. The key here is [M1000 | Customer A].
If we note the monitor entries, 3 records are transferred to update rules & two records are loaded in to Active Queue table. This is because we haven't activated request yet & that duplicate record for key in DSO gets overwritten.
Note: Activation Queue can also be expressed as 'New Data' table
The key figures will have the overwrite option by default, additionally we have the summation option to suit certain scenarios and the characteristics will overwrite always.

Naming Conventions

• Tech. Name of New data / Activation queue table is always for customer objects - /bic 140 and for SAP objects - /bio140.
• Name of active data table /BIC/A100 and /BI0 for SAP.
• Name of change log table - The technical name is always /BIC/.Once we activate we will have two records in DSO's Active Data table. The Active Data table always has contains the semantic key (E.g. Customer & Material for instance)

Change Log

The Change Log table has 2 entries with the image N (stands for ‘New'). The technical key (REQID, DATAPACKETID, RECORDNUMBER) will be part of change log table. (Refer Fig. D)
Fig. D - Data is loaded to CL & ADT (Pl. refer Fig. A for more details)
Introducing a few changes, we get the following result as in Fig. E.
Fig. E - Changes Introduced from the Flat file is reflected on PSA to ADT & PSA to CL

Detailed Study on Change Logs

We will check Change log table to see how the deltas are handled. The records are from first request that is uniquely identified by technical key (Request Number, Data packet number, Partition value of PSA and Data record number). With the second request the change log table puts the before and after Image for the relevant records.

Fig. F - Study on the Change Log on how the Deltas are handled
In this example Customer and Material has the before image with record mode "X". And also note that all key figures will be having "-" sign if we opted to overwrite option & characteristics will be overwritten always.
A new record (last row in the Fig. F) is added is with the status "N" as it's a new record.
Fig. G - Final Change Log Output

Record modes

Fig.H - Types of Record modes The record mode(s) that a particular data source uses for the delta mechanism largely depends on the type of the extractor. Ref. OSS notes 399739 for more details.

Work Scenario

Let's go through a sample real time scenario. In this example we will take the Master data object Customer, Material with a few attributes for the demonstration purpose. Here we define a ODS / DSO as below where material and customer is a key and the corresponding attributes as data fields.• ODS / DSO definition
• Definition of the transformation
• Flat file Loading
• Monitoring the Entries
• Monitoring Activation Queue
• Monitoring PSA data for comparison
• Checking Active Data Table
• Monitoring Change Log Table
• Displaying data in suitable Info provider (E.g. Flat File to PSA to DSO to Info Cube)
PSA Function modules RSAR_PSA_CLEANUP_DIRECTORY PSA Directory CleanUp Program
RSAR_PSA_PARTITION_CHECK Report RSAR_PSA_PARTITION_CHECK
RSAR_PSA_REQUEST_CHECK Analysis of PSA request (Transfer method: PSA only)
RSBKFIND_DTP_WITHOUT_PSA Find and Correct DTPs Without PSA
RSPSADEL1 Delete PSA
RSSM_REPAIR_PSADELETE Repair Incorrect PSA References in PSADELETE
RSSTATMAN_CHECK_CONVERT_PSA Check and Conversion of PSA Status Management to NW 04s
RSSM_CHECK_PSA_IS_CHANGELOG PSA/Change Log check Function Module
RSSM_DELETE_ODS_PSA_TABS Function Module for deleting old data in PSA
RSSM_DELETE_PLANNED_PSADELJOBS Function Module to delete PSA jobs
RSSM_FILL_REQ_FOR_PSADEL Function Module to fill request for PSA Deletion
RSDS_DATASOURCE_ALL_PSA_GET Function Module to get PSA table for all data sources.
RSAR_CHANGELOG_NAME_GET Get the name of change log table Function Module
RSCRT_GET_METADATA_CHANGELOG Function module to get meta data of change logs
RSBX_CHANGELOG_GET_DATA Function Module to get change log dataAbove is the list of most of the very useful PSA programs/Function modules which might solve our multiple problems.
Explore Data Sources http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1059f439-1017-2d10-2f88-cfe27b48170b?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/507a76c6-cb53-2e10-3ab0-d2655a7559bf?QuickLink=index&overridelayout=trueFollowing are the different function modules for datasource. RSDS_DATASOURCE_3X_DELETE
RSDS_DATASOURCE_ADMISSIBLE
RSDS_DATASOURCE_ALL_PSA_GET
RSDS_DATASOURCE_COLLECTION_ACT
RSDS_DATASOURCE_COLLECTION_DEL
RSDS_DATASOURCE_COL_ACT_DEL
RSDS_DATASOURCE_DELETE
RSDS_DATASOURCE_EXC_GET
RSDS_DATASOURCE_EXC_SET
RSDS_DATASOURCE_F4
RSDS_DATASOURCE_FROM_SH_GET
RSDS_DATASOURCE_HEADER_GET
RSDS_DATASOURCE_MIGRATE
RSDS_DATASOURCE_OLDNEW
RSDS_DATASOURCE_PSEUDO_D_DEL
RSDS_DATASOURCE_PSEUDO_D_LOOP
RSDS_DATASOURCE_PSEUDO_D_WRITE
RSDS_DATASOURCE_PSEUDO_IMPACT
RSDS_DATASOURCE_REPLICATE
RSDS_DATASOURCE_REPL_SAVE
RSDS_DATASOURCE_SAVE
RSDS_DATASOURCE_SEL_FIELDS_GET
RSDS_DATASOURCE_SH_DELETE
RSDS_DATASOURCE_SH_SAVE
Programs for Activating BW Objects in a Productive System

Communication Structures :

RS_COMSTRU_ACTIVATE_ALL

DataSources:

RSDS_DATASOURCE_ACTIVATE_ALL (for 7.X DataSources)
This report reactivates only A versions of DataSources according to the selection.

RS_TRANSTRU_ACTIVATE_ALL (for 3.X DataSources - same report for Transfer Rules)

Data Transfer Processes (DTP):

RSBKDTPREPAIR

Data Store Objects (DSO/ODS):

RSDG_ODSO_ACTIVATE (single object only - no mass activation)
During activation the M version will be read.
The flag "Clean Up DDIC Structures" deletes old generated tables. This was necessary only in previous releases.

InfoCubes:

RSDG_CUBE_ACTIVATE
If the A version is activated it will not effect the M version. If the M version is activated it will overwrite the A version with the M.

InfoObjects:

RSDG_IOBJ_ACTIVATE (single object only - no mass activation)
In the expert mode the processing lock can be swithed off, however it is not suggested to use.

InfoSets:

RSQ_ISET_MASS_OPERATIONS

MultiProviders:

RSDG_MPRO_ACTIVATE

Transfer Rules / Transfer Structures:

RS_TRANSTRU_ACTIVATE_ALL
If the option "Lock" is flaged during activation the object is locked. If only inactive transferstructure should be activated the flag "Only Inactive" can be checked.

Transformations:

RSDG_TRFN_ACTIVATE
In case you need to reactivate an already active transformation you need to put the parameter Object status (OBJSTAT) as 'ACT' for the that particular Transformation (TRAN_ID). DTP's containing transformation of source - / target type 'InfoSource' also will be re-activated.
This is a new program, which is delivered and corrected by the following SAP Notes: 1408161 - Program for transformation activation. 1434801 - Automatic Adjustment of Transformation for ISET. 1471117 - SP25:RSDG_TRFN_ACTIVATE skips if M version has OBJSTAT 'INA'. 1493850 - Consulting: Transformations inactive after system copy. 1507043 - RSDG_TRFN_ACTIVATE: Enhancements.

Update Rules:

RSAU_UPDR_REACTIVATE_ALL
This report reactivates only already active update rules. The possibility of changing this behavior has been revised a few times, and the decision was to keep it activating only the already active versions. The reason is Update Rules should always be checked when they get deactivated. Blindly reactivating them may cause inconsistencies.
1516916 - RSAU_UPDR_REACTIVATE_ALL doesn't activate inactive upd. Rule.

Performance Tuning in SAP BI 7.0

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6071ed5f-1057-2e10-deb6-d3426fec0219?QuickLink=index&overridelayout=true
Aggregation of Key Figures http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/801822f7-d053-2e10-78bc-fb8c3e203284?QuickLink=index&overridelayout=true

Process Chains in SAP BI

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/101bed70-f13d-2e10-e7ad-d5c9dabf4485?QuickLink=index&overridelayout=true
Data Source Replication and Activation of Transfer Structure http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/507a76c6-cb53-2e10-3ab0-d2655a7559bf?QuickLink=index&overridelayout=true
Role and Scope of ABAP in SAP BI http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0c8aa6b-7d42-2e10-f499-cefacc488e3d?QuickLink=index&overridelayout=trueUpdate Types IN SAP BIhttp://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0db2280-8242-2e10-b6a5-86a46d0feb25?QuickLink=index&overridelayout=true
Business Content in SAP BI http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?QuickLink=index&overridelayout=true
Standard DSO http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d9ab26-7a66-2e10-36bb-deea308c7020?QuickLink=index&overridelayout=true
BEx Query Designer: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/703f5fd4-8c84-2e10-9592-815d9802a10c?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0de5857-8c84-2e10-08b4-c92b99d90065?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20587d3e-8c84-2e10-828d-d05dd3b79765?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0ef2b84-8c84-2e10-2080-f674a87552b5?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/403986c0-8c84-2e10-17a6-88b5af5c6e97?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e018cba1-8c84-2e10-9fa9-de5c7021ea35?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0ef2b84-8c84-2e10-2080-f674a87552b5?QuickLink=index&overridelayout=true
Replacement Path http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80461c9f-fa4a-2e10-88be-e2219a016f09?QuickLink=index&overridelayout=true
Direct Update DSO http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e09289b7-7a66-2e10-1c83-bed127c635f0?QuickLink=index&overridelayout=true
Write-Optimized DSO http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/101ba999-7a66-2e10-5899-8b5bec800d67?QuickLink=index&overridelayout=true
Remodeling http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a07c3ba4-b853-2e10-4990-fd287ed1c5f7?QuickLink=index&overridelayout=true
Repartitioning http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20148ed3-b553-2e10-a99e-b0793764a752?QuickLink=index&overridelayout=true
Aggregates in SAP BI http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/908d2964-0a62-2e10-7baa-db86115cdbd9?QuickLink=index&overridelayout=true
All about Compression & Reverse Posting? http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
Scheduling of Process Chains at Custom Intervals Using Function Modules and Events http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8068a6b6-40e3-2c10-22ab-d52c5ab48f90?QuickLink=index&overridelayout=true
Trigger an Event Using Program and then Trigger a Process Chain by Event http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4027834a-81e5-2c10-1692-866e137fe2a3?QuickLink=index&overridelayout=true
Record Mode Concept in Delta Management http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5080c337-81e5-2c10-97af-8929424f3a4b?QuickLink=index&overridelayout=true
Elimination The Elimination Tab is used to restrict or eliminate the values a the Key Figures based on the Characteristics specified for elimination.

You have 2 options.
(1) Elimination of All Characteristic pairs.
(2) Elimination of Each Characteristic pairs.

For (1), the value of the key figure is only eliminated when the elimination condition is met for all characteristic pairs.

For (2), the value of the key figure is eliminated as long as the elimination condition is met for a characteristic pair.

Example:
The best example of elimination is in hierarchies,
You have 2 Characteristics, say "Delivering Plant" and "Receiving Plant".
When "Delivering Plant" is enabled with a Hierarchy (Not Restricted) and the "Receiving Plant" is avaialble in the hierarchy and is restricted with a Filter.

The KF corresponding to these charactersitic will be eliminated ONLY if the value of the "Receiving Plant" is available in the Hierarchy node and the "Delivering Plant" chararcteristic value is available in the filter for the "Receiving Plant".

In simpe words, if you want the value of the KF not to be repeated twice for the same characteristics in the Hierarchy, you can go for this option.
========================================================================================

Use

You can use this function to eliminate the internal business volume when executing a BEx query. In other words, the effect of this function is that revenues made between two cost centers in an organization are no longer displayed.

Prerequisites

You have an InfoProvider that includes two characteristics (sender and receiver) that contain the same reference (and, thus, contain the same master data) and are on the same level within the hierarchy.Note that you can only create aggregates for InfoCubes which contain both characteristics (sender and recipient).

Functions

To eliminate internal business volume in an InfoProvider, you have to create a key figure with a reference. You then include these in the InfoProvider. The value is kept here after the elimination during the query, but is not included in the fact table for the InfoCube (or in the ODS object).

Creating the reference key figure

When creating a key figure, select Key Figure with Reference. In the InfoObject maintenance you have an additional tab page, Elimination.Enter one or more characteristic pairs here regarding the key figure to be eliminated. In doing so, always choose a “sending characteristic” and a “receiving characteristic”. A typical example for such a pair of characteristics is Sending Cost Center and Receiving Cost Center. The characteristics of such a pair must have the same reference characteristic. You can also enter the names of the navigation attributes here.You can display permitted characteristics for an elimination characteristic by using the input help.If have specified several characteristic pairs, you still have to specify one of the following by using the selection buttons:· all characteristic pairs need to be eliminated - then the key figure value is only eliminated if the elimination condition is fulfilled for all characteristic pairs (AND relationship)· each individual characteristic pair needs to be eliminated - then the key figure value is already eliminated as soon as the elimination condition for one of the characteristic pairs is fulfilled (OR relationship)

Example

The profit center Production Accessories (UK) has $50.00 of internal revenue from profit center Internal Service (DE). This amount needs to be eliminated.
In the following example, different options are shown for different cases, including using these example hierarchies to display a profit center hierarchy and a country hierarchy.

Query example 1:

You create a referenced key figure, Profit Center Sales. For your characteristic pair, you choose Profit Center (0PROFIT_CTR) andPartner Profit Center (0PART_PRCTR). In the query you use the profit center hierarchy. The (internal business volume) amount of $50, which Production Accessories received internally, is eliminated for this profit center for the next highest level.

Query example 2:

You create a referenced key figure, Country Sales. As your characteristic pair, you choose Country (0COUNTRY) and Partner Country(0PCOUNTRY). In the query, you use the country hierarchy. The (internal business volume) amount for Europe and the country is eliminated, because the amount of $50 was counted from Germany to the UK.

Query example 3 (elimination with regard to all characteristic pairs):

You create a referenced key figure, Sales After Elimination, that includes the characteristic pairs· Country (0COUNTRY) and Partner Country (0PCOUNTRY)· Profit Center (0PROFIT_CTR) and Partner Profit Center (0PART_PRCTR). Choose the option Elimination with Regard to All Characteristic Pairs. In the query, use the hierarchies displayed above for country and profit center. The sales are then eliminated for the nodes for which both elimination conditions are fulfilled. In this example, the sales are eliminated on the node level, Europe. This is because the profit cente,r as well as both countries DE and UK, are appended underneath, between which the sales are eliminated.

Query example 4 (elimination with regard to each individual characteristic pair):

You create a referenced key figure, Sales After Elimination, that includes the characteristic pairs· Country (0COUNTRY) and Partner Country (0PCOUNTRY)· Profit Center (0PROFIT_CTR) and Partner Profit Center (0PART_PRCTR). Choose the option Elimination with Regard to Each Individual Characteristic Pair. In the query, use the hierarchies displayed above for country and profit center. Then all sales are eliminated that were sent either between Country and Partner Country or between Profit Center and Partner Profit Center. In this example, the sales are already eliminated from the node level, because the condition already applies for the profit center. The country was not considered for this node.