We’ll start with an introduction to asset accounting and learn about the tables and the standard DataSources, then you’ll learn about controlling application data extraction and about the various SAP-delivered DataSources in controlling applications.

Asset Accounting

The asset accounting (AA) area is used for managing fixed assets in an organization within an SAP system. In SAP ERP, the following tables are important for asset management:

• ANEK: Document Header Asset Posting
• ANEP: Asset Line items
• ANEA: Asset Line items for Proportional Values
• ANLC: Asset Value fields
• ANLP: Asset Periodic Values

The important DataSources that are used in asset accounting are as follows (if you use these DataSources for extraction scenarios, make sure you follow the below sequence when extracting from SAP BW/4HANA):

• 0FI_GL_4: General ledger line items (if required)
• 0ASSET_ATTR_TEXT: Master data for asset subnumber
• 0ASSET_AFAB_ATTR: Depreciation area
• 0FI_AA_11: FI-AA transactions with line-item details; data based on tables ANLC, ANEP, and ANEA
• 0FI_AA_12: Posted depreciation; contains periodic values based on table ANLP (this is a very stable DataSource)

If you want to use the /IMO dataflow, then SAP delivers a composite provider (/IMO/V_FIAA01). If you install that with the dataflow before beginning the asset accounting process, you’ll get all the required aDSOs for 0FI_AA_11 and 0FI_AA_12, as shown in this figure.

For SAP BW data loading, the process is like other FI-based data loads. The first step is to activate the DataSource in Transaction RSA5 in SAP S/4HANA, then log onto SAP BW/4HANA and replicate the relevant DataSource there and activate it. The next step is to create an aDSO based on the DataSource. Then create the transformation and DTP. Start the data load by executing the DTP using the right and down arrows. which will initialize the deltas in BWOM2_TIMEST. The LAST_TS flag will be set to X and the next delta will get the TS_HIGH values as the lower time of the new delta run.

Controlling Application–Based Extraction

FI deals with external reporting, while controlling (CO) applications help businesses analyze and deal with internal reporting. This includes managing and configuring the master data that covers cost and profit centers, and it deals with cost elements and functional areas. Its main advantage is planning: you can determine variances by comparing actual versus planned data to help your organization control the business flow. Because there are many applications in this area, we’ll focus on the relevant information from an SAP BW perspective. Controlling DataSources can be categorized into the following groups:

• CO-OM: Overhead cost controlling—69+ DataSources in SAP S/4HANA
• CO-PA: Profitability analysis—14 DataSources
• CO-PC: Product cost controlling

CO-OM is further split into the following groups:

• 0CO_OM_CCA* for cost center–based costs and allocations, activities, and so on
• 0CO_OM_OPA* for order-based costs and allocations, activities, and so on
• 0CO_OM_NAE*, NTW*, and NWA* for network activity elements
• 0CO_OM_WBS* for work breakdown structures like budget or overall plan cost 

Controlling DataSources: Some of the important DataSources are as follows:

• 0CO_OM_CCA_9—actual costs line items
• 0CO_OM_CCA_10—commitment line items
• 0CO_OM_CCA_30—statistical key figures
• 0CO_OM_CCA_40—actual line items
• 0CO_OM_OPA_40—actual line items
• 0CO_OM_OPA_1_D—plan totals
• 0CO_OM_WBS_6—actual line items
• 0CO_OM_WBS_7—commitment line items
• 0CO_PC_10—product cost analysis
• 0CO_PC_PCP_20—product cost estimates
• 0CO_PCP_30—product cost estimates itemization
• 0CO_OM_NAE_2—actual line items
• 0CO_OM_NTW_2—actual line items
• 0CO_OM_NWA_2—actual line items

Most of the DataSources in CO use tables like COEP (CO Objects Line Items), COSP, and COSS. Note that if you’re using SAP S/4HANA, most of these are not required—but if you extract the data from SAP ERP, then you need to use these extractors.