Master Data Transfer from the Source Data Layer (SDL)

Use

When transferring master data from the SDL, the system determines the master data for the accounting objects (AOs) from the SDL. A master data transfer only has to be carried out if new data has been delivered since the last master data transfer (for the legal entity), or changes have been made to the data, affecting the balance master data. (Particularly, therefore, if new AOs are to be created from the new SDL data.)

The system finds the keys (IDs) of the SDL primary objects that are relevant for the AOs and determines their assignment to the AOs. If necessary, the system generates new AOs. In this step, the master data for the AOs (product type and defining characteristics) is thus updated or generated.

The master data transfer is a subprocess within the financial reporting preprocess .

The master data transferred from the SDL is used in both Accounting and Balance Processing.

Prerequisites

In the Implementation Guide for Balance Analyzer , you have defined which InfoSets are to be used to transfer data. These InfoSets comprise an Operational Data Store Object (ODS) for the relevant SDL primary objects (position, account, financial transaction) and possibly one or more ODS’s for the relevancy indicator.

The InfoSet must contain the relevant fields, as described in the SAP Implementation Guide under Bank Analyzer → Analytics → Accounting: Merge Scenario → Balance Analyzer → After Generation → Basic Settings → Master Data Transfer from the SDL → Assign InfoSets to Product Types

This graphic is explained in the accompanying text.

If you want to use the same InfoSet for several product types, you must specify selection criteria so that you do not load the data from the Source Data Layer into the Balance Analyzer twice. You can use the selection criteria to make sure that not all of the data records for the InfoSet are transferred to Balance Analyzer.

This graphic is explained in the accompanying text.

Let us assume that you want to use the same InfoSet for the BOND and STOCK product types. In this case, it would be sensible to use the characteristic Product Type Determination , which is filled using the instrument type attribute of the financial instrument.

If necessary, make settings in Balance Analyzer for characteristic mapping for the defining characteristics from the SDL. You need to enter only those defining characteristics that have a different characteristic name in the SDL than in Balance Analyzer.

This graphic is explained in the accompanying text.

ODS objects are used in the Business Information Warehouse (BW) to store data in flat structures. In the IAS solution, ODS objects are used to maintain index tables and Analyzer relevancy indicators for SDL primary objects. They are the basis for searching for data in the SDL.

In the Implementation Guide (IMG), choose Bank Analyzer → Accounting → Accounting: Merge Scenario → Balance Analyzer → After Generation → Basic Settings → Transfer Master Data from the SDL → Map Defining Characteristics with Different Names. For more information, see the relevant IMG documentation.

If you need, for example, additional characteristics in the relationship table for processing splitting rules for splitting from the SDL, then you must have entered these in the Implementation Guide (IMG) by choosing Bank Analyzer → Analytics → Accounting: Merge Scenario → Balance Analyzer → Before Generation → Objects → Balance Object → Edit Assignment and Splitting Rules

If you want to split the balance objects from the Source Data Layer you must take advantage of the option to save additional characteristics in the relationship table. When the balances are transferred, the individual SDL positions can also be assigned by the system to the corresponding balance objects for split balance objects. In both cases, you must specify the additional defining characteristics of the balance object, and, if data is split from the accounting object, you must also specify the characteristics that are used to carry out the splitting.

This graphic is explained in the accompanying text.

Note that you must supply all the defining characteristics of the accounting object for the master data transfer. You must also include these in the InfoSet.

If you use alternative InfoSet characteristics (if, for example, you are using different position classes in the same InfoSet), then you must register these characteristics by choosing the following in the Implementation Guide: Bank Analyzer ®Source Data Layer ®Source Data Services ®Access to Source Data ®Index Function ®InfoSets ®Assign Additional Settings to InfoSet. In the above activity, you can assign alternative characteristics to InfoSet fields. If, as in this example, you are using primary object key fields, you must configure the role of these characteristics as keys for the respective primary objects by choosing in the Implementation Guide Bank Analyzer ®Basic Settings ®Settings for Metadata → Characteristics → Assign Role

Details

There are two different read procedures in transferring master data:

Full query for key date

In this case, all SDL primary objects are read (provided they have been selected using the InfoSet and selection criteria) but only in the version valid for key date.

Delta Query

In this case, only new or changed primary objects are read. However, all the changed versions are read (provided they have not been invalidated by corrections).

You can find examples to illustrate the difference between full query and delta query in the key date query and delta query documentation.

Because the number of the objects to be evaluated is considerably lower in the delta query it is usually quicker to run than the ‘full query to key date.'

You can use both forms interchangeably, but a delta query always uses the previous delta query as the basis of its starting point. It cannot use the full query because, for example, it cannot include future versions.

The new versions from the delta query are determined by the period between the system time stamp for the last successful master data transfer and the current SDL read time stamp for the financial reporting preprocess.

The system memorizes this time stamp for each product type and legal entity. In some cases, particularly when changes have been made in Customizing, such as selection criteria or InfoSet assignment, it is possible that you will have to reset the delta query. If this is the case, reset the time stamp(s) (from the last, successful master data transfer) with the transaction /BA1/B0_RESET_DELTA.

It is also possible to set a generally valid (applies to all legal entities) lower limit for the business date. SDL objects that are no longer valid on this date are not taken included in the delta reading. This is particularly useful for performance reasons if you a recreating a relationship table and have several obsolete objects in the SDL.

The master data transfer evaluates the technical field Status from the InfoSet. This is determined by the status fields of the primary objects, which are in turn determined by the object-specific fields (see the documentation on the SDL). In this way, logical deletions are automatically recognized and included. This is necessary for the delta query as (logical) deletions can be recognized as changes to this status field.

Activities

For more information on transferring master data, see Transferring Master Data from the SDL .