Object Tables 

Definition

Logically superordinate database table within a table group in the special purpose ledgers.

Use

SAP saves data in relational databases: Oracle, Informix, and Entire SQL (ADABAS). Relational databases select information using key fields. The highest number of key fields in a database is 16, and therefore, this is the maximum number of fields that the user can define. FI-SL uses object tables to display coding block fields and to increase the number of possible coding block fields. The new object tables also enable you to directly maintain and validate dimension combinations. Technically, these object tables enhance the "real" coding block to overcome the technical database limitations.

Structure

SAP delivers two types of object tables: Object/partner and movement attribute.

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, company code/company

Object numbers determine how the summary and line item database tables are 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).

Movement Attributes

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

Fixed Dimensions

You cannot change fixed dimensions.

Client, object number for the movement attribute dimensions

Object numbers determine how the summary and line item database tables are accessed via the object tables. The object numbers for the movement 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 movement attribute-dependent.

In a business transaction, you post CO data to the FI-SL system. The cost centers that you post to are defined in 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 movement attribute in the movement attributes table.

Examples of variable dimensions in object table 2 include controlling area, movement type, and transaction.

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