Standard
SAP BI Financial Content
BI 7 Content Package 5
Prepared by
:
Source: SAP AG (Jan 2011)
1
Table of Contents
1. Overhead Cost Controling (OM) ......................................................................................................................................... 3
2. General Ledger Accounting (GL) ........................................................................................................................................ 4
3. Accounts Receivables (AR) ................................................................................................................................................. 5
4. Accounts Payables (AP) ...................................................................................................................................................... 6
5. Funds Management (FM) ................................................................................................................................................... 6
6. Asset Accounting (AA) ........................................................................................................................................................ 7
7. Travel Management (TV).................................................................................................................................................... 8
8. Contract Accounting - Receivable and Payable (CA) (excl. Dunning data)......................................................................... 9
9. Lease Management (L) ..................................................................................................................................................... 13
10. Transactions and Depreciations ..................................................................................................................................... 13
11. Investment Mangement (IM) ......................................................................................................................................... 14
12. Cost and Profitability (COPA) ......................................................................................................................................... 15
13. Closing Cockpit (LC) ........................................................................................................................................................ 15
14. Consolidation (CS) .......................................................................................................................................................... 15
15. Profit Center Accounting (PCA) ...................................................................................................................................... 16
16. Management of Internal Controls (MIC)........................................................................................................................ 16
17. SAP Financial Supply Chain Management (BD-COL-CR-DM).......................................................................................... 17
18. Joint Venture Accounting (JVA) ...................................................................................................................................... 20
19. Financial Web Cockpits .................................................................................................................................................. 20
20. Financial Masterdata Management (FI-MDM) ............................................................................................................. 23
21. Controlling (CO)............................................................................................................................................................... 23
2
Financial DataStores
1. Overhead Cost Controling (OM)
1. 1 CO-OM-OPA: Actual - Line Items - ODS
Technical name: 0OPA_O06
This ODS object is used for the delta process of the DataSource Orders: Actual Cost Line Items (0CO_OM_OPA_6). The
DataSource works in what is called the after-image process. That is, it supplies the new state of the selected internal
order line items from the OLTP. The ODS object calculates the change (delta) against the state extracted earlier. It
contains the line item information for the internal orders that were loaded from the source system(s) using the
InfoSource Internal Orders: Actual Costs Through Delta Extraction (0CO_OM_OPA_6).
1.2 CO-OM-OPA: Commitments - Line Items - ODS
Technical name: 0OPA_O07
This ODS object is used for the delta process of the DataSource Orders: Commitment Line Items (0CO_OM_OPA_7). The
DataSource works in what is called the after-image process. That is, it supplies the new state of the selected
commitment line items from the OLTP. The ODS object calculates the change (delta) against the state extracted earlier.
It contains the line item information for the commitments that were posted on internal orders and that were loaded
from the source system(s) using the InfoSource Orders: Commitment Line Items (0CO_OM_OPA_7).
1.3 CO-OM-OPA: Budget - Line Items - ODS
Technical name: 0OPA_O08
This ODS object is used for the delta process of the DataSource Orders: Budget Line Items (0CO_OM_OPA_8). The
DataSource works in what is called the after-image process. That is, it supplies the new state of the selected budget line
items from the OLTP. The ODS object calculates the change (delta) against the state extracted earlier. It contains the line
item information for the budgets that were loaded from the source system(s) using the InfoSource Orders: Budget Line
Items (0CO_OM_OPA_8).
1.4 CO-OM: Costs and Allocations (Delta Extraction) - InfoCube
Technical name: 0COOM_C02
This InfoCube contains all costs and quantities on cost centers, internal orders, WBS elements, networks, network
activities, and network activity elements that were downloaded from the source systems using delta extraction. The
InfoCube also contains the partner information for the allocation relationships. Before you make entries in this
InfoCube, you need to load the master data for orders, WBS elements, networks and network activities. If you do not do
so, the system cannot determine the responsible cost center or enter it in 0COSTCENTER. You can also use this InfoCube
to access your own fields.
3
2. General Ledger Accounting (GL)
2.1 General Ledger (New): Transaction Figures - InfoCube
Technical name: 0FIGL_C10
This InfoCube contains all the transaction data (transactions figures) from the leading ledger in new General Ledger
Accounting that was loaded from the integrated source system(s).
2.2 General Ledger (New): Transaction Figures, Remote - RemoteCube
Technical name: 0FIGL_R10
This InfoCube contains all the transaction data (transactions figures) from the leading ledger in new General Ledger
Accounting that was loaded from the integrated OLTP system(s). You can use this RemoteCube to select current data in
real time. It is not necessary for the data to be replicated in InfoProviders. The data is read directly from the OLTP
system by means of a BAPI.
2.3 General Ledger (New): Financial Statement
Technical name: 0FIGL_V10
- VirtualCube
This InfoCube is a virtual cube providing services only. This means that the InfoCube itself does not contain any data.
Queries based on this InfoCube are filled with data using the implemented services, which take the data from the
InfoCube General Ledger (New): Transaction Figures (0FIGL_C10). In the case of queries used to display the financial
statement using a financial statement version, these services calculate the result (profit/loss) and ensure that the
accounts assigned in the financial statement on the basis of the balance (contra items) are displayed correctly.
2.4 General Ledger (New): Financial Statement, Remote -VirtualCube
Technical name: 0FIGL_V11
This InfoCube is a virtual InfoCube providing services only. This means that the InfoCube itself does not contain any data.
Queries based on this InfoCube are filled with data using the implemented services, which take the data from the
4
InfoCube General Ledger (New): Transaction Figures, Remote (0FIGL_R10). In the case of queries used to display the
financial statement using a financial statement version, these services calculate the result (profit/loss) and ensure that
the accounts assigned in the financial statement on the basis of the balance (contra items) are displayed correctly. You
can use this InfoCube to select current data in real time. It is not necessary for the data to be replicated in InfoProviders.
The data is read directly from the OLTP system by means of a BAPI.
2.5 General Ledger (New): Transaction Figures - ODS
Technical name: 0FIGL_O10
This DataStore object is required for the delta process of the DataSource General Ledger: Balances, Leading Ledger
(0FI_GL_10). It contains all the totals records (transaction figures) from new General Ledger Accounting that were
uploaded from the connected source system(s) using the InfoSource General Ledger (New): Transaction Figures . The
DataSource works in the after image process. This means that it always delivers the totals records with the latest status
from the OLTP system. In the DataStore object, the difference (or delta) from the previously extracted total is calculated.
2.6 General Ledger Accounting (New): Line Items - ODS
DataStore object: 0FIGL_O14
This DataStore object is required by the delta method of the DataSource General Ledger Accounting (New): Line Items of
the Leading Ledger(0FI_GL_14). It contains all line items that have been extracted from the source system(s). The
DataSource works in the after image process. This means that it always delivers new and changed line items with the
latest status from the OLTP system.
3. Accounts Receivables (AR)
3.1 Accounts Receivable: Line Items - InfoCube
Technical Name: 0FIAR_C03
This InfoCube contains all the Accounts Receivable line items that were loaded from the integrated source system(s).
3.2 Accounts Receivable: Payment History - InfoCube
Technical Name: FIAR_C05
InfoCube 0FIAR_C05 contains the payment history (payment volume and days in arrears) of customers per company
code and fiscal year period. The data comes from table KNB4 in the R/3 source system.
3.3 Accounts Receivable: Transaction Data - InfoCube
Technical name: 0FIAR_C02
This InfoCube contains all accounts receivable data (transaction figures) that was downloaded from the connected
source system(s).
3.4 Accounts Receivable: Line Items - ODS
Technical name: 0FIAR_O03
The ODS object Accounts Receivable: Line Items contains all line items transferred from the source system(s) using the
InfoSource Accounts Receivable Line Items (0FI_AR_3). All fields in the InfoSource are transferred to the ODS object.
3.5 Accounts receivable: Transaction Figures - ODS
DataStore object: 0FIAR_O06
This DataStore object contains accounts receivable transaction figures.
3.6 Accounts Receivable: Special G/L Trans. Figs w. Delta Extraction - ODS
DataStore object: 0FIAR_O07
This DataStore object contains accounts receivable special G/L transaction figures.
5
3.7 Credit Management: Central Data with Delta Extraction - ODS
DataStore object: 0FIAR_O08
This DataStore object contains Credit Management central data.
3.8 Credit Management: Control Area Data with Delta Extraction - ODS
DataStore object: 0FIAR_O09
This DataStore object contains Credit Management control area data.
3.9 Accounts Receivable: Payment History with Delta Extraction - ODS
DataStore object: 0FIAR_O10
This DataStore object contains the most current payment history data, with a maximum of 16 data records for each
customer. Note: The time characteristics are calendar month and calendar year, not fiscal period and fiscal year.
4. Accounts Payables (AP)
4.1 Accounts Payable: Line Items - InfoCube
Technical Name: 0FIAP_C03
This InfoCube contains all the Accounts Payable line items that were loaded from the integrated source system(s).
4.2 Accounts Payable: Transaction Data - InfoCube
Technical name: 0FIAP_C02
This InfoCube contains all accounts payable data (transaction figures) that was downloaded from the connected source
system(s).
4.3 Accounts Payable: Line Items - ODS
Technical Name: 0FIAP_O03
The ODS object Accounts Payable: Line Items contains all line items transferred from the source system(s) using the
InfoSource Accounts Payable Line Items (0FI_AP_3). All fields in the InfoSource are transferred to the ODS object.
4.4 Accounts Payable: Transaction Figures - ODS
Technical name: 0FIAP_O06
This ODS Object contains all transaction figures determined from the source system(s) using the InfoSource Accounts
Payable: Transaction Figures Using Delta Procedure (0FI_AP_6). All fields of the InfoSource are transferred to the ODS
Object.
4.5 FI-AP Special General Ledger Transaction Figures - ODS
Technical name: 0FIAP_O07
This ODS Object contains all special general ledger transaction figures determined from the source system(s) using the
InfoSource Accounts Payable: Special General Ledger Transaction Figures Using Delta Procedure(0FI_AP_7). All fields of
the InfoSource are transferred to the ODS Object.
5. Funds Management (FM)
5.1 Commitment/Actuals and Budget in Funds Management (FI-FM) - InfoCube
Technical Name: 0FIFM_C01
The InfoCube Commitments/Actuals and Budget in Funds Management (FI-FM) (0FIFM_C01) contains all the transaction
data transferred to the source system(s), for the budget (overall budget, annual budget, periodic budget) and for the
assigned funds, as well as commitments/actuals postings. The data in the InfoCube is provided using the InfoSources
Budget in Funds Management (0FI_FM_1) and Commitments and Actuals in Funds Management (0FI_FM_2). The values
are represented as revenues and expenditures here, unlike other InfoCubes in the area of Financial Accounting and
Controlling, where costs and revenues are represented. All the queries belonging to this InfoCube are therefore assigned
to the two user roles Budget Planner and Budget Manager. The InfoCube includes the general key figures Amount
6
(0AMOUNT) for the budget and Amount (long) (0AMOUNT_17) for commitments and actuals. Restricted key figures are
also provided. Restricted key figures are derived from the two key figures by filtering several InfoCube characteristics.
The amounts are differentiated by the restricted characteristics, such as Budget category (payment budget or
commitment budget), Value type in Funds Management (Budget, Releases, Assigned Funds and Commitments/Actuals).
You can aggregate all the values of this InfoCube for an FM area hierarchically because they always refer to a Funds
Management account assignment (combination of commitment item, funds center and fund). This means that on the
highest node of the hierarchy the total of its own values and of the values of all subordinate nodes is displayed. You can
use the Posting period, Fiscal year, Fiscal year/ Period, and Fiscal year variant as time dimensions in your evaluations.
The fiscal year variant is necessary to differentiate fiscal years with different periods.
5.2 CO Line Items in Funds Management (FI-FM) - ODS
Technical Name: 0FIFM_O33
The CO Line Items in Funds Management (FI-FM) ODS object contains all line items for CO postings in Funds
Management that have been transferred from the source system(s) using the CO Line Items in Funds Management
(0FI_FM_33) InfoSource. All the fields of the InfoSource are copied unchanged to the ODS object. The key part consists
of fields that ensure the uniqueness of line items from the OLTP table Actuals Line Items Table for Funds Management
FMIA. ODS object data can be updated in the InfoCube Commitments/Actuals and Budget in Funds Management (FIFM).(0PU_C01) No InfoSets are currently provided for this ODS object. For this reason, the ODS object is not assigned to
any user role. However, functionally the data belongs to the Budget Supervisor role.
5.3 FI Line Items in Funds Management (FI-FM) - ODS
Technical Name: 0FIFM_O32
The CO Line Items in Funds Management (FI-FM) ODS object contains all line items for CO postings in Funds
Management that have been transferred from the source system(s) using the CO Line Items in Funds Management
(0FI_FM_33) InfoSource. All the fields of the InfoSource are copied unchanged to the ODS object. The key part consists
of the primary key for the OLTP table Funds Management Line Items Table FMIFIIT. ODS object data can be updated in
the InfoCube Commitments/Actuals and Budget in Funds Management (FI-FM)(FIFM_C01). No InfoSets are currently
provided for this ODS object. For this reason, the ODS object is not assigned to any user role. However, functionally the
data belongs to the Budget Supervisor role.
5.4 Commitments Line Items in Funds Management (FI-FM) - ODS
Technical Name: 0FIFM_O31
The Commitments Line Items in Funds Management (FI-FM) ODS object contains all line items for commitments and
funds transfers in Funds Management that have been transferred from the source system(s) using the Commitments
Line Items in Funds Management (0FI_FM_31) InfoSource. All the fields of the InfoSource are copied unchanged to the
ODS object. The key part consists of the primary key for the OLTP table Funds Management commitment documents
FMIOI. ODS object data can be updated in the InfoCube Commitments/Actuals and Budget in Funds Management (FIFM)(FIFM_C01).
6. Asset Accounting (AA)
6.1 FI-AA - Annual Values Posted Depreciation - InfoCube
Technical Name: 0FIAA_C02
This InfoCube contains all of the period values uploaded from the source system(s) for Asset Accounting on the basis of
posted depreciation. NOTE: If you try to total across a number different depreciation areas, this could lead to incorrect
results in the query. Check if a report that totals the values of several depreciation areas is really necessary.
Every time you upload data, the system adds it to the existing values. You should, therefore delete existing values where
necessary, before repeating uploading.
6.2 FI-AA - Annual Values Planned Depreciation - InfoCube
7
Technical Name: 0FIAA_C01
This InfoCube contains all of the annual values uploaded from the source system(s) for Asset Accounting on the basis of
planned depreciation. Note: If you try to total across a number different depreciation areas, this could lead to incorrect
results in the query. Check if a report that totals the values of several depreciation areas is really necessary. Every time
you upload data, the system adds it to the existing values. You should, therefore delete existing values where necessary,
before repeating uploading.
6.3 FI-AA - Transactions - InfoCube
Technical Name: 0FIAA_C03
This InfoCube contains all line items uploaded from the source system(s) from Asset Accounting. If you try to total across
a number different depreciation areas, this could lead to incorrect results in the query. Check if a report that totals the
values of several depreciation areas is really necessary. Every time you upload data, the system adds it to the existing
values. You should, therefore delete existing values where necessary, before repeating uploading.
6.4 FI-AA - Annual Values and Transactions - InfoCube
Technical Name: 0FIAA_C04
This InfoCube contains all of the annual values uploaded from the source system(s) on the basis of planned depreciation
and line items. This InfoCube is designed for the asset history sheet. It includes the planned depreciation from InfoCube
0FIAA_C01 and the line items from InfoCube 0FIAA_C03.
6.5 FI-AA - Transactions (Delta) - ODS
DataStore object: 0FIA_DS11
This object contains all transactions and annual value information for an asset. Data for the object is provided by the FIAA - Transactions InfoSource (0FIAA_C11). However, only transactions for assets are available for reports, since they are
the only transactions transferred to the summarized transactions (delta) InfoCube (0FIAA_C11).
6.6 FI-AA - Annual Values (Delta) - ODS
DataStore object: 0FIA_DS12
This object contains the annual values for an asset. These annual values are calculated using the annual value
information from the transactions (delta) DataStore object (0FIA_DS11).
6.7 FI-AA Period Values (Delta) - ODS
DataStore object: 0FIA_DS13
This object contains the periodic values for an asset. Its structure is similar to that of annual values (Delta) DataStore
object (0FIA_DS12). However, the values are based on individual periods and not on the whole fiscal year. The object is
first updated from the transactions (Delta) DataStore object (0FIA_DS11), then it is provided with data from the posted
depreciations (period values) InfoSource (0FI_AA_12). When updating from a DataStore object, the values are calculated
based on the period from the transactions and annual values, while the depreciation values are extracted directly from
the source system.
7. Travel Management (TV)
7.1 Travel Planning: Booking Data - InfoCube
Technical name: 0FITV_C02
The InfoCube Travel Planning: Booking Data contains all the transaction data transferred from the source system (OLAP
system) to the BW system for travel plans created using the R/3 component Travel Planning. You can use the Calendar
Day, Calendar Year/Month, Calendar Year/Quarter, and Calendar Year as time dimensions in your evaluations. You can
evaluate these key figures according to various attributes:
 Personal data of the traveler (such as nationality, gender, and language)
 Organizational data (such as personnel area, employee group, and organizational unit)
 General trip data (such as trip country, trip type, trip provision variant)
8
 Travel service provider (such as hotel code, car rental company, flight cabin class)
 The update rules specify how the time characteristics are to be determined for the key figures. All indicators
with the trip end date are to be updated.
7.2 Travel Expenses: Totals and Receipts - InfoCube
Technical name: 0FITV_C01
The InfoCube Travel Expenses: Totals and Receipts contains all the transaction data transferred from the source system
(OLAP system) to the BW system for travel expense reports created using the R/3 component Travel Expenses. You can
use the Calendar Day, Calendar Year/Month, Calendar Year/Quarter, and Calendar Year as time dimensions in your
evaluations. You can evaluate these key figures according to various attributes:
 Personal data of the traveler (such as nationality, gender, and language)
 Organizational data (such as personnel area, employee group, and organizational unit)
 General trip data (such as beginning and end date of a trip, trip type, trip provision variant)
 Travel expense status and attributes of the travel expense receipts
8. Contract Accounting - Receivable and Payable (CA) (excl. Dunning data)
8.1 FI-CA: Cleared Items - InfoCube
Technical name: 0FC_C06
This InfoCube contains information about cleared items determined at a certain interval by the mass activity. If you want
to compare different intervals from different analyses, the intervals must contain comparable periods (for example,
monthly) and must be determined periodically. You can select the evaluation Calendar day, Calendar year/week,
Calendar year/month and Calendar year. The system determines the value from the posting date. You can evaluate the
key figures Cleared items and Number of document items contained in the InfoCube according to different attributes:
Company code, Business area,Division,Clearing reason,Dunning procedure/dunning level,Regional characteristics
,Clearing grid,Due date. The characteristic 0FCFLAGPOMO, which is contained in the InfoCube, is generated in the
transfer rules and is necessary in the DSO analysis (Day Sales Outstanding).
8.2 FI-CA- DSO Analysis - InfoCube
Technical name: 0FC_MC01
This MultiCube merges information on open items determined on the key date using the mass activity, and settled items
determined for the interval using the mass activity. The DSO (Day Sales Outstanding) is calculated for monthly periods.
For this reason it is necessary that intervals for settled items are at least one month long, and that the end of an interval
matches the corresponding key date for determining open items. Example: For the DSO calculation for the month of
April, you must select the interval 04.01.04 - 04.30.04 for the extraction of settled items, and the key date 04.30.04 for
the extraction of open items. You can select the evaluation Calendar day, Calendar year/week, Calendar year/month and
Calendar year. The system determines the value from the posting date. DSO is calculated as follows: DSO = Balance /
Periodic business volume * 30. The balance is composed of all open items on the key date, and the periodic business
volume is composed of all revenue posted in the period.
8.3 FI-CA - Invoicing Data - InfoCube
InfoCube: 0FC_C10
The InfoCube is used as a data source for the virtual InfoProvider Invoicing Data (0FC_MC02), which, in turn, forms the
basis for the Invoicing Data Analysis (0FC_MC02_Q0001). is used to analyze sales volumes resulting from invoicing data.
8.4 FI-CA: Open Items (Historical) - InfoCube
InfoCube: 0FC_C01
This InfoCube contains information about the open items determined on a key date by the mass activity. The noncumulative value is managed according to key dates and must be determined at periodic intervals (for example, once a
month) if it is to provide useful information about the individual analysis periods. You can select the evaluation Calendar
9
year / month. The system determines the value from the key date. You can evaluate the key figures Open Items and
Number of Document Items contained in the InfoCube according to different attributes: Company code, Business area,
Division, Dunning procedure, Regional characteristics
8.5 FI-CA: Collection Agencies - InfoCube
InfoCube: 0FC_C03
This InfoCube allows you to assess collection agencies by analyzing the delivered receivables and the responses that
were generated as a result. You can use the transaction date or the submission date of the receivable to obtain more
time-based details. You can analyze the data from various aspects such as the process duration, the receivables sold, or
the submission status of the collection items. For example, you can compare the percentage rates of the receivables
collected by the various agencies within a month.
8.6 FI-CA Open Items - InfoCube
InfoCube: 0FC_C07
This InfoCube contains information about the open items determined on a key date by the mass activity. The noncumulative value is managed according to key dates and must be determined at periodic intervals (for example, once a
month) if it is to provide useful information about the individual analysis periods. You can select the evaluation Calendar
day, Calendar year/week, Calendar year/month and Calendar year. The system determines the value from the posting
date. You can evaluate the key figures Open Items and Number of Document Items contained in the InfoCube according
to different attributes: Company code,,Business area,Division,Dunning procedure/dunning level,Regional characteristics,
Clearing grid,Due date,Collection item. The characteristic 0FCFLAGPOMO, which is contained in the InfoCube, is
generated in the transfer rules and is necessary in the DSO analysis (Day Sales Outstanding).
8.7 FI-CA: Installment Plan Header and Item Data - InfoCube
InfoCube: 0FC_C04
This InfoCube allows you to analyze the open and cleared installment plan items. You can use the end or start date of
the installment plan, the due date for net payment, or the clearing date to obtain more time-based details. You can
analyze the data from various aspects, in particular according to the attributes of the installment plan items. For
example, you can call up a structured display of the sum of the expected monthly installment payments by installment
plan category.
8.8 FI-CA: Installment Plan Header Data - InfoCube
InfoCube: 0FC_C05
This InfoCube allows you to analyze installment plans. You can use the start date, the end date, or the deactivation date
of the installment plan to obtain more time-based details. You can analyze the data from various aspects, in particular
according to the attributes of the installment plan header data. For example, you can display how many installment
plans were created in each month and the amount of each installment.
8.9 FI-CA: Revenue Distribution - InfoCube
InfoCube: 0FC_C018
Contains information about the revenue distribution by the report program. You can evaluate the key figures;
distributed amount, posted distribution amount, number of initial distribution and number of posted distribution which
are contained in the InfoCube according to different attributes: Basic information, Application period.
8.10 FI-CA: Cleared Items (Delta method) - InfoCube
InfoCube: : 0FC_C09
This InfoCube contains information on cleared items at the time of the last delta extraction. The data corresponds with
the current status in the ERP system. This InfoCube is the basis of the data for the MultiProvider 0FC_MC09 and
0FC_MC10. Perform evaluations of cleared items using this MultiProvider.
8.11 FI-CA: Open Items (Delta Method) - InfoCube
10
InfoCube: 0FC_C08
This InfoCube contains information on open items at the time of the last delta extraction. The data corresponds with the
current status in the ERP system. This InfoCube is the basis of the data for the MultiProvider 0FC_MC08 and 0FC_MC10.
Perform evaluations of open items using this MultiProvider.
8.12 FI-CA: Returns - InfoCube
InfoCube: 0FC_C20
This InfoCube contains information about returns by the report program. You can evaluate the key figures return
amount, return charge and number of returns with reference to different attributes: Company Information, Date,
Business Partner, Return Data. Note: There is a transformation which transfers data from DSO 0FC_DS20 to InfoCube
0FC_C20. The rule type for InfoObjects 0CALYEAR, 0CALMONTH and 0CALDAY is Time Characteristic; for InfoObjects
0FC_BTRB, 0fc_RLGB, 0FC_BTRV and 0FC_RETNO the rule type is Formula. For the other InfoObjects it is Direct
Assignment. You can load Risk Class (0CDM_RISC) data from DataSource 0FSCM_CM_1, and load Region (0REGION) data
from DataSource 0BP_DEF_ADDRESS_ATTR with your own Customizing.
8.13 FI-CA: Payments - InfoCube
InfoCube: 0FC_C21
This InfoCube contains information about the payments by the mass activity program. You can evaluate the key figures
payment amount from different attributes: Organization data, Payment data, Date, Basic data. Note: Relative to Data
Modeling: There is a transformation which transfers data from DataStore Object 0FC_DS21 to InfoCube 0FC_C21. The
rule type for InfoObject 0CALYEAR, 0CALMONTH and0CALDAY is Time Characteristic; for the other InfoObjects, it is
Direct Assignment.
8.14 FI-CA: Payments - ODS
DataStore object: 0FC_DS21
This DataStore object contains payments data from FI-CA. A transformation transfers data from DataSource 0FC_PAY to
DataStore object 0FC_DS21. The rule type for InfoObject 0LOGSYS is Constant, and the rule type for the other
InfoObjects is Direct Assignment.
8.15 FI-CA Returns - ODS
DataStore object: 0FC_DS20
This DataStore object contains the returns data from FI-CA. Data is transferred from DataSource 0FC_RET to 0FC_DS20.
The rule type for InfoObject 0LOGSYS is Constant and the rule type for the other InfoObjects is Direct Assignment.
8.16 FI-CA: Returns Lot - ODS
DataStore object: 0FC_DS22
This DataStore object contains the returns lot data from FI-CA.. A transformation transfers data from DSO0FC_DS20 to
DSO0FC_DS22 directly. The rule type for the InfoObjects is Direct Assignment.
8.17 FI-CA: Cleared Items (delta method) - ODS
DataStore object: 0FC_DS07
This DataStore object contains all cleared items. The object data is provided using DataStore object 0FC_DS05.
8.18 FI-CA: Invoicing Data - ODS
DataStore object: 0FC_DS13
This DataStore object (DSO) contains data from invoicing. Since large volumes of data have to be processed, it is defined
as write-optimized. It is not as a result of the data loaded that the records are unique, but through the use of a technical
key. This means that more than one record can be returned if you use the semantic key. You can carry out reporting by
using InfoSets. The DSO is used for the following purposes: Technical integration of source data. Consistent data
storage Update the info cubes Invoicing Data (0FC_C10) and Sales Revenue Analysis (0TE_C08)
11
8.19 FI-CA: Open Items - ODS
DataStore object: 0FC_DS01
This data store object allows you to analyze open, due, and overdue items. Since the dataset transferred to BW is
determined by key date, all analyses must be carried out by key date. As a chronological analysis period, you can group
the open items by due date periods. The drilldown can take place according to business partner attributes, regional
structure data, company code, business area, division or dunning procedure. In order to restrict the dataset to the
necessary level of detail, we recommend, for example, that you only transfer business partner data of company
customers to BW since it only makes sense to analyze this data in great detail. The data for this data store object is
determined in OLTP by a mass activity (by key date) and loaded in the data store object using generic extraction. The
DataSource is not capable of producing delta figures. This means that you must manually delete the legacy data in the
data store object.
8.20 FI-CA: Open Items (Delta Method) - ODS
DataStore object: 0FC_DS06
This DataStore object contains all open items. The object data is provided using DataStore object 0FC_DS06.
8.21 FI-CA: Case Management - ODS
Technical name: 0FCCMDS01
The ODS object contains the data for the current clarification cases from the Enhanced Message Management
application (EMMA) in FI-CA. You can also delete clarification cases in this application. These are also no longer available
in this ODS object after the delta load.
8.22 FI-CA: Business Partner Items - ODS
DataStore object: 0FC_DS05
This object contains all business partner items. Data of the object is provided using InfoSource 0FC_BP_ITEMS. The
structure of the DataStore object matches the communication structure of the InfoSource.
8.23 FI-CA: Installment Plan Header and Item Data - ODS
DataStore object: 0FC_DS02
This data store object is used to complete the installment plan item data with data from the installment plan header and
update it for reporting in InfoCube 0FC_C04. The completion of the item data with the header data occurs in the start
routine of the update rules. Therefore, the header data must be loaded before the item data can be loaded. Even
though the separate update of the header data from data store object 0FC_DS03 ensures that the data is consistent, it is
updated a second time with the latest header data.
8.24 FI-CA: Installment Plan Header Data - ODS
DataStore object: 0FC_DS03
This data store object is used to complete the item data in the 0FC_DS02 ODS object with data from the installment plan
header for reporting and update it in InfoCube 0FC_C05. Therefore, the header data must be loaded before the item
data can be loaded Updating header data in the 0FC_DS02 data store object in its transfer rules and from the 0FC_DS03
data store object ensures that the data is consistent. Data is updated twice in another load sequence. It is first updated
with the old header data and the second time with the up-to-date version.
8.25 FI-CA: Contract Account - Partner-Dependent Attributes - ODS
DataStore object: 0FCIODS02
This DataStore object (DSO) contains the business partner-specific attributes of the contract account and can be used for
master data reporting using an InfoSet. The DSO is used for the following purposes: Technical integration of source data
Consistent data storage. Update InfoObject 0FC_ACCNTBP. Caution: Please note that you must activate the data
manually or using a process chain before update to the data targets.
12
8.26 FI-CA: Contract Account - Partner-Independent Attributes - ODS
DataStore object: 0FCIODS01
This DataStore object (DSO) contains the business partner-independent attributes of the contract account and can be
used for master data reporting using an InfoSet. The DSO is used for the following purposes: Technical integration of
source data, Consistent data storage. Update InfoObject Contract Account Number (0CACONT_ACC). Caution: Please
note that you must activate the data manually or using a process chain before update to the data targets.
8.27 FI-CA: Work Items: Data - ODS
DataStore object: 0FC_DS23
This DSO contains the Work Items data from FI-CA. There is a transformation which transfers data from DataSource
0FC_WLI to DataStore object 0FC_DS23. The rule type for InfoObject 0LOGSYS is Constant, and the rule type for the
other InfoObjects is Direct Assignment.
9. Lease Management (L)
9.1 Lease Accounting Key Figures - InfoCube
Technical name: 0FIL_C01
The system provides the summarized accrual, asset, and customer posting data for a lease item for reporting in InfoCube
0FIL_C01.
9.2 Lease Header - ODS
Technical name: 0FIL_DS01
The system uses ODS object 0FIL_DS01 to save the header data of the lease, as extracted from the LAM accounting
system.
9.3 Lease Items - ODS
Technical name: 0FIL_DS02
The system uses ODS object 0FIL_DS02 to save the item data of the lease, as extracted from the LAM accounting system.
9.4 Asset Master Records for Lease - ODS
Technical name: 0FIL_DS03
The system uses ODS object 0FIL_DS03 to save the link between lease item and fixed asset, as extracted from the LAM
accounting system.
9.5 Lease Accounting Key Figures - ODS
Technical name: 0FIL_DS04
The system uses ODS object 0FIL_DS04 to merge the accrual, asset, and customer posting data to form a lease item, and
supplements it with the corresponding lease data. Key Fields: The key consists primarily of the lease (external allocation
indicator, contract header/item) and a time-based accrual (posting period, clearing date of customer document). The
data type controls whether or not the posting period involves accumulated or non-accumulated data.
9.6 Costing Results from the Accrual Engine - ODS
Technical name: 0ACE_DS01
The system uses ODS object 0ACE_DS01 to save the planned accrual values for a lease item, as extracted from the LAM
accounting system. Key Fields: The system saves the data with the technical accrual object as a key; the corresponding
lease item is contained in the data part. The key is converted to the lease item in the later course of the update.
10. Transactions and Depreciations
10.1 Transactions and Depreciation (Direct) - RemoteCube
InfoCube: 0FIAA_R20
13
This InfoCube: Reads data from the source system during runtime using direct access. Is one component of
MultiProvider 0FIAA_M20
10.2 Transactions and Depreciation (Replicated) - infoCube
InfoCube: 0FIAA_C20
This InfoCube: Physically stores the data extracted from the source system in the BI system. Is one component of
MultiProvider 0FIAA_M20
11. Investment Mangement (IM)
11.1 Corporate IM: Transaction Data (Direct) – RemoteCube
InfoCube: 0IMFA_R10
This InfoCube provides IM transaction data to MultiProvider 0IMFA_M10. It reads data directly from the back end.
11.2 Corporate IM: Transaction Data (Direct) II - InfoCube
InfoCube: 0IMFA_C10
This InfoCube provides IM transaction data, reading data from the BW system. You must replicate data in the BW system
in advance. This InfoCube is connected to DataStore Object Corporate IM: Status Selection Profile (0IMFA_D10).
11.3 IM-FA: Assigned Plan and Budget - InfoCube
Technical name: 0IMFA_1
The 0IMFA_1 InfoCube is a central, cross-system, optimized database used for analysis. These analyses assist decisionmaking in company-wide planning, and for investment projects. The queries provided by SAP, numerous predefined
templates, and restricted key figures all enable the quick and easy definition of flexible analyses that provide the
information you require. The 0IMFA_1 InfoCube contains the plan, budget and assigned values of investment programs
and the objects assigned to them. The objects assigned to investment programs are appropriation requests and
measures (that is, orders and projects).
11.4 Corporate IM: Group Shares - InfoCube
Technical Name: 0IMFA_C04
The InfoCube 0IMFA_C04 is part of the data model for Corporate Investment Management. It contains the Consolidation
dimensions on the investments. The Customizing information about the group shares in the individual companies is
loaded into the PSA via InfoSource 0IM_FA_IP_6 IM-FA: Group Shares (IM) . (As of SAP R/3 Release 4.5B the group
shares in the companies can be maintained in IM Information System Customizing. Organizations not using SAP R/3 can
also load the information from an Excel file.) This information allows you to evaluate the investments from the
Consolidation viewpoint. The system determines the values per company, using the group shares (percentages) of the
affected companies as the basis. The companies affected by an investment are determined by the organizational
assignment in the master data of the investment program positions. InfoCube 0IMFA_C04 is updated using DataMart
80IMFA_1.
11.5 Corporate IM: Operative Data - InfoCube
Technical name: 0IMFA_C03
InfoCube 0IMFA_C02 is part of the data model for Corporate Investment Management. It contains the operative data for
planning and cost controlling of the investments at group level. The data for the InfoCube is supplied via a Data Mart
from InfoCube 0IMFA_1, which is designed for local investment control at the company level. Data from the different
local BW systems of the individual companies can be brought together.
11.6 Corporate IM: Strategic Planning/Operative Data - InfoCube
Technical Name: 0IMFA_C02
InfoCube 0IMFA_C02 is part of the data model for Corporate Investment Management. MultiCube 0IMFA_C02 consists
of the cubes 0SEM_C05 SEM-BPS Investment Planning and 0IMFA_C03 Corporate IM: Operative Data. The queries on
14
this InfoCube can be used to compare the planning details entered in SEM-BPS and the operative data from the OLTP
Systems.
11.7 Corporate IM: Status Selection Profile - ODS
DataStore object: 0IMFA_D10
This DataStore object reads data from DataSource 0IM_STATSEL_REPOBJ_ATTR. There is no delta update for this
DataStore object.
12. Cost and Profitability (COPA)
12.1 Profitability Analysis (S_GO), Direct - Remote Cube
InfoCube: 0COPA_R10
This InfoCube reads Profitability Analysis transaction data directly from the back end and provides the information to
MultiProvider 0COPA_M10.
12.2 Profitability Analysis (S_GO), Direct II - InfoCube
InfoCube: 0COPA_C10
This InfoCube reads replicated Profitability Analysis transaction data in the BW system and provides the information to
MultiProvider 0COPA_M10.
13. Closing Cockpit (LC)
13.1 Closing Status (Direct) - RemoteCube
InfoCube: 0CLC_R1
This InfoCube provides data on closing tasks' planned date/time, actual date/time, and status — based on the data
transfer process for direct access.
13.2 Closing Status (Replicated) - InfoCube
InfoCube: 0CLC_C1
This InfoCube contains replicated data on closing tasks' planned date/time, actual date/time, and status.
14. Consolidation (CS)
14.1 Transaction Data, Consolidation - InfoCube
Technical Name: 0ECCS_C01
This InfoCube contains all the transaction data uploaded from the source system(s) for consolidation. The data is present
both in the form of period balances and non-cumulative values. The transaction data in Consolidation is dependent on a
consolidation group hierarchy. Since this itself is time-dependent, the characteristics 0CS_HDATFR (Hierarchy from) and
0CS_HDATTO (Hierarchy to) must be transferred to the filter together with the variables belonging to it 0P_CSHF
(Hierarchy from (SAP Exit)) or 0P_CSHT (Hierarchy to (SAP Exit)). These variables are derived from the query key date
and replaced using a SAP Exit. Only this way can you guarantee that the correct data is displayed. Furthermore, a
variable 0P_CSDAT is defined for the query key date. If this variable is not used, the current date is automatically used as
the query key date. Both the validity interval for a consolidation group hierarchy (that may be used) and the two
variables mentioned above are derived from the query key date. To use a restricting consolidation group hierarchy, you
should use the variables 0H_CG or 0N_CG/0N_CG1/0N_CG2 for the hierarchy name or hierarchy node. The content of
these variables is the same, but they have different texts. The hierarchy's validity date remains free and is automatically
replaced by the query key date. When using cumulative key figures, you should ensure that the fiscal year/period is
defined exactly. This is because of the aggregation behavior. You therefore eliminate any implicit cumulation with regard
to time. This would lead to incorrect results. The cumulative key figures are not automatically available for all periods. If,
15
in OLTP EC-CS system, consolidation frequencies are defined for all consolidation groups in all versions and dimensions,
then the cumulative results are available for the most detailed closing periods. Otherwise the cumulative values for all
periods are transferred into the Cube.
14.2 Changes in Investments, Consolidation - InfoCube
Technical Name: 0ECCS_C03
This InfoCube contains all the reported data of consolidation related to the investment and changes in investments, that
is uploaded by the source system(s). The data reflects transaction figures. You enter the reported data of changes in
investments via additional financial data.
14.3 Changes in Investee Equity, Consolidation - InfoCube
Technical Name: 0ECCS_C04
This InfoCube contains all the reported data of consolidation related to the equity and the changes in investee equity,
that is uploaded by the source system(s). The data represents the transaction figures of the financial items. You enter
the changes in investee equity via additional financial data.
15. Profit Center Accounting (PCA)
15.1 Transaction Data (Profit Centers) - InfoCube
Technical Name: 0PCA_C01
This InfoCube contains all of the period totals for profit and loss accounts and balance sheet accounts from Profit Center
Accounting (PCA), which were loaded from the affiliated source system(s).
15.2 Statistical Key Figures (Profit Center) - InfoCube
Technical Name: 0PCA_C02
This InfoCube contains all statistical key figures from Profit Center Accounting (PCA), which are loaded from the affiliated
source system(s).
16. Management of Internal Controls (MIC)
16.1 Assignment: Process - Control Objective - Risk - Control - ODS
DataStore object: 0MIC_DS01
The assignments made in MIC between process, control objective, risk, and control (P-CO-R-C assignment) are stored in
this DataStore object. Delta update is not supported for this DataStore object.
16.2 Assignment: Process - Account Group - FS Assertion - Control - ODS
DataStore object: 0MIC_DS02
The assignment made in MIC between process, account group, FS assertion, and control is stored in this DataStore
object. Caution: This DataStore object is based on the obsolete DataSource Assignment: Process – Account Group – FS
Assertion – Control (0CGVMIC_6). To be able to use the DataStore object for the new DataSource Assignment: OrgUnit –
Account Group – FS Assertion – Control (0CGVMIC_13) as well, you need to make adjustments to it. For more
information, see SAP Note 835351..
16.3 Status of Sign-Off for Organizational Unit - ODS
DataStore object: 0MIC_DS03
This DataStore object contains information about for which organizational units MIC sign-off has been performed and
for which organizational units it has not been performed.
16.4 Issues - ODS
DataStore object: 0MIC_DS04
16
This DataStore object contains information about all issues that were reported during the various assessments and tests
in MIC. Delta update is not supported for this DataStore object.
16.5 Remediation Plans - ODS
DataStore object: 0MIC_DS05
This DataStore object contains information about the remediation plans relating to issues that were reported during the
various assessments and tests in MIC. Delta update is not supported for this DataStore object.
17. SAP Financial Supply Chain Management (BD-COL-CR-DM)
Within SAP Financial Supply Chain Management, you currently have access to BI Content for the following application
components:
 SAP Biller Direct (FIN-FSCM-BD)
 SAP Collections Management (FIN-FSCM-COL)
 SAP Credit Management (FIN-FSCM-CR)
 SAP Dispute Management (FIN-FSCM-DM)
17.1. Biller Direct: Biller Direct Event Log - ODS
DataStore object: 0BD_DS01
The DSO contains the logged events that a user has created in a transaction in SAP Biller Direct. This DataStore Object is
available to you if you have imported SAP ERP 6.0 Enhancement Package 2.
17.2 Collections Management : Worklist Item - InfoCube
InfoCube: 0CLM_C01
This InfoCube creates a view of the worklist items that your collection specialists process using the component SAP
Collections Management. For each worklist item, this includes the following information: Number of customer contacts.
Amount promised for payment. Disputed amount. The InfoCube is used in the MultiProvider Worklist Item (0CLM_MC1).
You can also use it to generate reports that refer to worklists and collection specialists.
17.3 Collections Management : Customer Contact - InfoCube
InfoCube: 0CLM_C02
This InfoCube creates a view of the customer contacts that your collection specialists have entered in the system using
the component SAP Collections Management. For each customer contact, this includes the following information:
Details of customer contact, Details of dispute cases, Details of promises to pay, Number of Resubmissions. The
InfoCube is used in the MultiProvider Customer Contact (0CLM_MC2). You can also use it as InfoProvider for creating
queries that refer to customer contacts.
17.4 Collections Management : Worklist Item - ODS
DataStore object: 0CLM_DS01
This DataStore Object is used to consolidate the worklist items before they are uploaded to the InfoCube Worklist Item
(0CLM_C01) for further evaluation. It permits the deletion of data before the upload.
17.5 Collections Management : Customer Contact
DataStore object: 0CLM_DS02
This DataStore Object is used to consolidate the customer contacts before they are uploaded to the InfoCube Customer
Contact (0CLM_C02) for further evaluation. You can also use the DataStore Object as InfoProvider in query definitions.
The system transfers the data records of the DataSource Customer Contact (0CLM_CCT) to this DataStore Object on a
one-to-one basis.
17.6 Collections Management : Business Partner in Collections Management
DataStore object: 0CLM_DS03
17
This DataStore Object contains the following data: Collections Management master data, Assignment history of the
organizational data of Collections Management to the business partner. This includes the collection segment, the
collection group, and the collection specialist. The DataStore Object is used to integrate the data of Collections
Management with the data of Accounts Receivable Accounting (FI-AR). It is used as basis for the following InfoSets:
Receivables Linked to Collections Management Organizational Structures (0CLM_IS01). Merge of Invoice and Promise to
Pay (0CLM_IS02). Invoices Linked to Collections Management Organizational Structures (0CLM_IS03)
17.7 Collections Management : Promise to Pay
DataStore object: 0CLM_DS04
This DataStore Object is used to consolidate the promises to pay before they are uploaded to the InfoSet Merge of
Invoice and Promise to Pay (0CLM_IS03). You can also use the DataStore Object as InfoProvider in query definitions. The
system transfers the data records of the DataSource Promise to Pay (0CLM_P2P) to this DataStore Object.
17.8 Collections Management : Invoice Status - ODS
DataStore object: 0CLM_DS05
This DataStore Object contains the transaction data of the invoice that was optimized for SAP Collections Management.
This optimized invoice considers all line items in Accounts Receivable Accounting that are assigned to an invoice item. In
addition to the invoice item itself, this includes the following assigned transactions: Credit memos, Incoming payments
and Clearing transactions
17.9 Collections Management : Customer in Collections Management - ODS
DataStore object: 0CLM_DS06
This DataStore Object contains the mapping between the business partner and the customer. It is used to integrate the
data of Collections Management with the data of Acounts Receivable Accounting (FI-AR) and is used as basis for the
following InfoSets: Receivables Linked to Collections Management Organizational Structures (0CLM_IS01). Merge of
Invoice and Promise to Pay (0CLM_IS02). Invoices Linked to Collections Management Organizational Structures
(0CLM_IS03)
17.10 Collections Management : Open Items in Collections Management - ODS
DataStore object: 0CLM_DS07
This DataStore object contains all of the open items that are transferred for each business partner from Accounts
Receivable Accounting (FI-AR) to Collections Management. This involves a reduced number of fields, such as the
company code, the open item reference, the invoice reference, the amount, and the currency. The DataStore object is
used to integrate the data of Collections Management with the data of Accounts Receivable Accounting (FI-AR). It is
used as the basis for the Receivables Linked to Collections Management Organizational Structures (incl. Head Office Branch Office Relationships) (0CLM_IS04) InfoSet. Note: This DataSource object is only available if you have imported
SAP Enhancement Package 4 for SAP ERP 6.0. It relates to the following business functions: FSCM Functions 2
(FIN_FSCM_CCD_2). FSCM Integration 2 (FIN_FSCM_CCD_INTEGRATION)
17.11 Credit Management: Credit Profile - InfoCube
Technical name: 0CDM_C01
The InfoCube creates snapshots for credit profiles of business partners in SAP Credit Management. The main key figure
here is the Credit Limit at credit segment level. The header level characteristics Risk Class and Score are portrayed as
navigation attributes for the master record Business Partner.
17.12 Credit Management: Credit Profile - ODS
Technical name: 0CDM_DS03
The ODS object is the second highest level in the InfoProvider chain of the Credit Profile analysis scenario that ends with
the InfoCube Credit Profile. The ODS object consolidates the data of the InfoCube, but can also be used as an
independent InfoProvider in query definitions. The uniqueness of the data records in this ODS object can be used to
count data records, as, for example, in the query Profile Analysis: Risk Class.
18
17.13 Credit Management: Credit Profile (Periods) - ODS
Technical name: 0CDM_DS02
The ODS object is the second level in the InfoProvider chain of the Credit Profile analysis scenario that ends with the
InfoCube Credit Profile. The analysis scenario data is retained in this ODS object at month level. The aggregation over
periods is achieved via the update in the ODS object Credit Profile and in the InfoCube Credit Profile.
17.14 Credit Management: Credit Profile (Days) - ODS
Technical name: 0CDM_DS01
The ODS object is the second highest level in the InfoProvider chain of the Credit Profile analysis scenario that ends with
the InfoCube Credit Profile. The analysis scenario data is retained in this ODS object at time level. The aggregation at
month level is achieved via the update in the ODS object Credit Profile (Periods).
17.15 Credit Risk: Total Liability - Remote - RemoteCube
Technical name: 0CDM_VC0
See Credit Risk. You can use this RemoteCube to access the liability data of the source system directly and thus analyze
the current status. The Liability Data (0FSCM_CM_4) InfoSource is the data basis for this cube.
17.16 Credit Risk: Liability - InfoCube
Technical name: 0CDM_C2
See Credit Risk. You use this InfoCube to analyze the liability data of business partners. The liability data is displayed
broken down by credit segments and various different liability categories. You can include the liability data of lower level
business partners in the analysis. The country keys, the region of the business partner, and the risk class are portrayed as
navigation attributes.
17.17 Credit Risk: Total Liability - ODS
Technical name: 0CDM_DS04
See Credit Risk. The ODS object is the consolidation level for the liability data of the Credit Risk analysis process and is
updated in the Liability InfoCube.
17.18 Rating Analysis: New Rating Analysis and Simulation Analysis - InfoCube
Technical name: 0CDM_C1
The InfoCube analyzes collective runs for new ratings or simulation in SAP Credit Management that are created by
extracts. Using the characteristic Before/After Indicator enables a flexible query definition that you can use, in particular,
for displaying the evaluations as graphics. As an alternative, for simple queries you can use the ODS object Collective
Processing Runs.
17.19 Rating Analysis: Collective Processing Runs - ODS
Technical name: 0CDM_DS00
The ODS object is the consolidation level of the New Rating Analysis and Simulation Analysis analysis scenario and is
updated in the InfoCube New Rating Analysis and Simulation Analysis. The ODS object can also be used as InfoProvider
for query definition due to its unique data record update, as, for example, in the query New Rating Analysis and
Simulation Analysis.
17.20 Rating Analysis: Business Partner Rating: Score - ODS
Technical name: 0CDM_DS05
See Business Partner Rating. The results of the example analysis process Score are updated in the transactional ODS
object. The analysis process is part of the analysis scenario Business Partner Rating.
17.21 Dispute Management: Accounts Receivable Process Integration - ODS
Technical Name: 0DPM_O01
19
This ODS object contains the transaction data that results from the process integration of SAP Dispute Management with
Accounts Receivable. This transaction data defines the connection between the dispute cases and the line items of
Accounts Receivable.
18. Joint Venture Accounting (JVA)
18.1 PRC Summary Items - InfoCube
Technical Name: 0PRC_C01
The PRC Summary Items InfoCube contains total records from table JVTO1.
18.2 PRC Line Items - InfoCube
Technical Name: 0PRC_C02
The PRC Line Items InfoCube contains line items from table JVSO1 and JVPO1.
18.3 Joint Venture Summary Records - InfoCube
Technical Name: 0JVA_C01
This InfoCube contains total records from table JVTO1.
18.4 Joint Venture Billing Ledger - InfoCube
Technical Name: 0JVA_C02
This InfoCube contains total records from table JVTO2.
18.5 PRC Line Items Actual (Delta) - ODS
Technical Name: 0PRC_DS01
This ODS object contains actual line items from table JVSO1.
18.6 PRC Line Items Plan (Delta) - ODS
Technical Name: 0PRC_DS02
This OD object contains plan line items from table JVPO1.
18.7 PRC Equity Shares - ODS
Technical Name: 0PRC_DS03
This ODS object contains information about partner shares for joint ventures.
19. Financial Web Cockpits
19.1 Web Cockpit: My Profit Center – Current Situation
This Web Cockpit is designed for companies whose operational managers are responsible for both cost centers and
profit centers. It is an example Cockpit that is intended to be modified and enhanced by company-specific reports. This
Cockpit can be modified to provide the same functionality as the Cockpit My Cost Centers – Current Situation. An
example report is provided for the travel expenses budget with queries from travel management. If personalization is
active, the reports are filtered automatically by the profit center for which the manager is responsible (provided it was
specified in the personalization settings). This Web Cockpit can be used as a central self-service point, either alone or in
conjunction with our other Web Cockpits in CO. Reports can be sent to thousands of addressees on this new distribution
path. The expense and trouble of distributing reports as hard copies is no longer necessary. This lowers costs and
enables current information to be accessed more quickly. Managers can access the reports through a standard web
browser – no special software is needed.
19.2 Web Cockpit: My Orders – Current Situation
20
The cost center manager uses this Web Cockpit for a quick overview of the current costs on his or her internal orders.
The initial screen displays the internal orders assigned to the cost center manager’s cost centers through the responsible
cost center field in the order master data. It shows the actual costs and the planned costs of the last closed period, and
the variances. The five orders with the largest plan-actual variances are displayed in a graphic. Selecting an order brings
you to a detailed report. This is a hierarchical cost element report. When the overview report is initially executed, it
displays cumulative data for your cost centers. You can restrict the report to the internal orders of an individual cost
center by selecting the cost center from the selection list in the report header. If personalization is active, the reports
are filtered automatically by the cost centers for which the manager is responsible (provided these were specified in the
personalization settings). You can choose between the display time frames last period, last four quarters, and current
year.
19.3 Web Cockpit: My Orders - Budget
The cost center manager uses this Web Cockpit to determine how much of the budget on his or her internal orders has
been used up (depleted). This Web Cockpit displays the following information for the orders of the selected cost centers
for the current year or for the entire life of the orders: budget, actual costs, commitment, allotted, and available budget.
The upper part of the graphic shows the percentage budget depletion for the orders. Budget overruns are highlighted in
the graphic. If personalization is active, the reports are filtered automatically by the cost centers for which the manager
is responsible (provided these were specified in the personalization settings). When the report is initially executed, it
displays cumulative data for all your cost centers. You can restrict the report to the internal orders of an individual cost
center by selecting the cost center from the selection list in the report header. You can switch between the time periods
total and in current year. This Web Cockpit can be used as a central self-service point, either alone or in conjunction with
our other Web Cockpits in CO. Reports can be sent to thousands of addressees on this new distribution path.
19.4 Web Cockpit: My Cost Centers – Current Situation
The cost center manager uses this Web Cockpit for a quick overview of the current costs on his or her cost centers. This
Web Cockpit contains five reports for the cost center manager that provide information on the current plan-actual
situation of the cost centers. If personalization is active, the reports are filtered automatically by the cost centers for
which the manager is responsible (provided these were specified in the personalization settings). The initial screen
shows a cost element report with a graphic. It displays the actual and planned costs of the last period, the variances, and
the statistical key figures for the time frame. The report first displays cumulative data for your cost centers. You can
restrict the report to an individual cost center by selecting the cost center from the selection list in the report header.
Selecting a filter value in this way is only possible in the initial report. You can navigate to detailed reports on travel
expenses, personnel costs, depreciation, and purchase orders using the navigation bar at the top of the report. The filter
for cost centers is taken from the initial report.
19.5 Web Cockpit: My Cost Centers - Planning
The cost center manager uses this Web Cockpit to follow current cost center planning. This Web Cockpit contains three
reports on cost center planning for the cost center manager. If personalization is active, the reports are filtered
automatically by the cost centers for which the manager is responsible (provided these were specified in the
personalization settings). The initial screen shows a cost element report with a graphic. This report contains the actual
and planned costs of the previous year, the variances, and the planned costs of the current year plus any changes in
plan. The report first displays cumulative data for your cost centers. You can restrict the report to an individual cost
center by selecting the cost center from the selection list in the report header. Selecting a filter value in this way is only
possible in the initial report. From the navigation bar at the top of the report, you can navigate to detailed reports on
the planning for activity types and statistical key figures. The filter for cost centers is taken from the initial report.
19.6 Web Cockpit: My Projects – Budget
The cost center manager uses this Web Cockpit to determine how much of the budget on his or her overhead cost
projects has been used up (depleted). This Web Cockpit contains reports for the cost center manager that provide
information on the current budget situation of the projects. If personalization is active, the reports are filtered
automatically by the cost centers for which the manager is responsible (provided these were specified in the
21
personalization settings). The initial screen shows a plan/actual report with a graphic. It shows the actual costs and
planned costs of the last period, and the variances. The report first displays cumulative data for your cost centers. You
can restrict the report to an individual cost center by selecting the cost center from the selection list in the report
header. Selecting a filter value in this way is only possible in the initial report.
19.7 Web Cockpit: My Projects - Plan/Actual
The cost center manager uses this Web Cockpit for a quick overview of the current costs on his or her overhead projects.
This Web Cockpit contains three reports for the cost center manager that provide information on the current plan-actual
situation of the projects. If personalization is active, the reports are filtered automatically by the cost centers for which
the manager is responsible (provided these were specified in the personalization settings). The initial screen shows a
plan/actual report with a graphic. It shows the actual costs and planned costs of the last period, and the variances. The
report first displays cumulative data for your cost centers. You can restrict the report to an individual cost center by
selecting the cost center from the selection list in the report header. Selecting a filter value in this way is only possible in
the initial report.
22
20. Financial Masterdata Management (FI-MDM)
This InfoArea provides Business Intelligence (BI) Content you can use to display the master data that has been processed
in the data model provided by SAP. The reports give you an overview of the state of the master data as per a specific
point in time. You can use them to make preparations for creating financial reports and for external audits. The reports
always pertain to one edition. Note: To use this Content, you need to have implemented SAP enhancement package 4
for SAP ERP 6.0 and activated the business function Master Data Management for Financials: Charts of Accounts. The
queries directly access InfoSets. The hierarchy-bearing characteristics (Account (0FMD_ACCNT), Financial Statement
Item (0FMD_FRSITM), and Group Account (0FMD_FSITM)) are extracted via the InfoPackage from the source system and
written as a hierarchy in the BI system.
21. Controlling (CO)
Structure of Controlling: Controlling is divided into Overhead Cost Controlling and Product Cost Controlling.
A. Overhead Cost Controlling
CO-OM-CCA: Cost Center Accounting
CO-OM-OPA: Overhead Orders
CO-OM-WBS: Overhead Projects
CO-OM-ABC: Activity-Based Costing
B. Product Cost Controlling
CO-PC: Product Cost Planning
CO-PC: Actual Costing / Material Ledger / Inventory Valuation
22.1 Cost Center Accounting CO-OM-CCA: Costs and Allocations - InfoCube
Technical name: 0CCA_C11
Full costs on cost centers (plan, target, actual, etc.) Information on the origin of the costs (allocation partner such as
material number, cost center, etc.) No breakdown into fixed and variable costs, or into fixed and variable costs by
activity type
22.2 Cost Center Accounting - CO-OM-CCA: Costs and Allocations (by Activity Type) - InfoCube
Technical name: 0CCA_C02
Costs broken down into cost components, or costs by activity type (fixed and variable costs)
23
22.3 Cost Center Accounting - CO-OM-CCA: Activity Type Quantities and Prices - InfoCube
Technical name:0CCA_C04
Activity quantities (plan, actual, target, scheduled activity, capacity) Activity prices (plan and actual)
22.4 Cost Center Accounting - CO-OM-CCA: Statistical Key Figures - InfoCube
Technical name: 0CCA_C03
Statistical key figures on cost centers (plan, actual)
22.5 CO-OM-CCA: Actual - Line Items - ODS
Technical name: 0CCA_O09
You can define line item queries on this ODS object. You can also use this ODS object to extract current data to BW
without the safety margin of 2 hours using the DataSource Cost Centers: Actual Costs - Line Items (Delta)
(0CO_OM_CCA_9), as described in Note 553561.
22.6 CO-OM-CCA: Commitments - Line Items - ODS
Technical name: 0CCA_O10
This ODS object is used for the delta process of the DataSource Cost Centers: Commitment Line Items
(0CO_OM_CCA_10). The DataSource works in what is called the after-image process. That is, it supplies the new state of
the selected commitment line items from the OLTP. The ODS object calculates the change (delta) against the state
extracted earlier. It contains the line item information for the commitments that were posted on cost centers and that
were loaded from the source system(s) using the InfoSource Cost Centers: Commitment Line Items (0CO_OM_CCA_10).
22.7 Overhead Orders - CO-OM-OPA: Costs and Allocations - InfoCube
Technical name: 0OPA_C11
Full costs on internal orders (plan, target, actual, etc.). Information on the origin of the costs (allocation partner such as
order, cost center, etc.)
22.8 Overhead Orders - CO-OM-OPA: Statistical Key Figures - InfoCube
Technical name: 0OPA_C02
Statistical key figures on internal orders (plan, actual)
22.9 Overhead Projects - CO-OM-WBS: Costs and Allocations - InfoCube
Technical name: 0WBS_C11
Full costs on overhead projects (plan, target, actual, etc.). Information on the origin of the costs (allocation partner such
as material number, cost center, etc.). Fixed/variable split (breakdown) of the costs (if executed previously in R/3)
22.10 Overhead Projects - CO-OM-WBS: Statistical Key Figures - InfoCube
Technical name: 0WBS_C02
Statistical key figures on overhead projects (plan, actual)
22.11 Activity-Based Costing- CO-OM-ABC: Costs and Allocations - InfoCube
Technical name: 0ABC_C06
Full costs on business processes (plan, target, actual, etc.) Information on the origin of the costs (allocation partner such
as material number, cost center, etc.)
22.12 Activity-Based Costing- CO-OM-ABC: Process Quantities and Prices - InfoCube
Technical name: 0ABC_C05
Business process quantities (plan, actual, target, scheduled quantities, capacity) Business process prices (plan, actual)
22.13 Activity-Based Costing- CO-OM-ABC: Statistical Key Figures - InfoCube
24
Technical name: 0ABC_C02
Statistical key figures on business processes (plan, actual)
22.14 CO-PC: Product Cost Planning – All Cost Estimates - InfoCube
Technical name: 0COPC_C08
All cost estimates saved in R/3, for costing variant, costing date, and so on (all statuses, costing purposes, etc.)
22.15 CO-PC: Product Cost Planning – Released Cost Estimates- InfoCube
Technical name: 0COPC_C09
All released cost estimates that changed the standard price for materials when they were released – by material and
period
22.16 Inventory Valuation - Material Prices and Inventory Values - InfoCube
Technical name: 0COPC_C04
Inventory values. Material prices (standard price, moving average price, balance sheet valuation prices)
Including sales order stocks, project stocks, valuation types
22.17 Actual Costing/Material Ledger - CO-PC: Actual Costing/Material Ledger – Costs - InfoCube
Technical name: 0COPC_C03
Inventory valuation in multiple currencies and valuation views. Valuation of procurement, consumption, and inventory
at actual cost
22.18 CO-PC: Actual Costing/Material Ledger – Cost Component Split - InfoCube
Technical name: 0COPC_C07
Information on the cost component split. Valuation of procurement, consumption, and inventory at actual cost
22.19 CO-PC: Cost Object Controlling - InfoCube
Technical name: 0PC_C01
Costs on cost collectors in production: production orders, process orders, run schedule headers, product cost collectors,
and so on (plan costs, actual costs, target costs, settled costs, variances, results analysis data, etc.)
25