Object Tables 

Use

SAP stores its data in standard relational databases: Oracle, Informix, and Entire SQL (ADABAS). Relational databases select information using key fields. The highest number of key fields supported in an underlying database is 16, which limits the number of key fields possible for customer definition. FI-SL uses object tables to display coding block fields, as well as to increase the number of possible coding block fields. The object table structures also allow you to directly maintain and validate dimension combinations. Technically, these object tables are spliced into a longer "virtual" coding block to overcome the underlying technical database limitations.

Features

SAP delivers two types of object tables: object/partner and transaction attributes

A) Object/Partner (Receiver/Sender)

This object table supports 15 variable dimensions, including the local company code/global company. Two of the variable dimensions are used for internal purposes, leaving 13-14 variable dimensions available for customer definition.

The variable dimensions defined in this object table have a sender/receiver relationship (for example, receiver account (RACCT) and sender account (SACCT)).

Fixed Dimensions

You cannot change fixed dimensions.

Client, object number for object (receiver) and partner (sender) dimensions, valid period intervals, local company code/global company

Object numbers determine how the summary and line item database tables will be accessed via the object tables. The object numbers for the object (receiver) and partner (sender) dimensions are defined in object table 1.

Variable Dimensions

The variable dimensions are the key dimensions of the coding block. These dimensions are defined in object table 1 and can be used in the summary and line item database tables as object dimensions (receivers) and/or partner dimensions (senders). Object and partner dimensions have a direct relationship, where partner dimensions are the senders of data, and object dimensions are the receivers of data.

Account (ACCT), cost center (CNTR).

An example of an object/partner object table delivered with FI-SL is GLREFO (only for local ledgers).

B) Transaction Attributes

This object table supports 15 variable dimensions. The variable dimensions defined in this object table are transaction attribute-dependent and do not have a sender/receiver relationship (for example, controlling area (KOKRS)). The optional transaction attributes table (object table 2) contains:

Fixed Dimensions

You cannot change fixed dimensions.

Client, object number for the transaction attribute dimensions

Object numbers determine how the summary and line item database tables will be accessed via the object tables. The object number for the transaction attribute dimensions are defined in object table 2.

Variable Dimensions

These variable dimensions do not have a direct sender/receiver relationship; instead, the variable dimensions are transaction attribute-dependent.

Within one business transaction, you are posting CO data to FI-SL, and the cost centers to which you are posting are defined within a specific controlling area. You only post to FI-SL for this controlling area. Since 1) the controlling area remains the same for the sender cost center (SCNTR) and receiver cost center (RCNTR), and 2) the controlling area does not have a sender/receiver relationship with another field (for example, sender controlling area, receiving controlling area), you can include the controlling area dimension as a transaction attribute in the transaction attributes table.

Example variable dimensions in object table 2 include controlling area, movement type, and activity.

An example of a transaction attribute object table delivered with FI-SL is GLREFC (only for local ledgers).