It’s a type of metadata repository that is used by BW data structures, and connects to all applications around the system. BW programs can access the ABAP dictionary using "Structured query language" (SQL). When the ABAP dictionary is accessed, the basis system translates the open SQL commands to database specific commands.
Transaction code used is “SE11”
(Fig: 1)
Basic elements are Domains, Data Elements and Tables
Domains:-
Define basic elements having a defined data type and data length (eg: Customer Number). All further ABAP dictionary elements will be based on defined domains.
A Customer number is defined as a 10 digit alpha numerical field by domain /BI0/OCUSTOMER with the data type char and length 10 and Master data value table as /BI0/MCUSTOMER.
(Fig: 2)
Data Elements:-
..Defined as description layer over the domains. Each data element refers specifically to a domain, and each domain can be used by several data elements. Data element contains descriptive data that can be used as a header when displaying field content. Eg: Customer number usually mapped as one of the partner roles such as Ship- To party, Sold-To party etc, where each refers to the domain customer number.
(Fig: 3)
Tables:-
A structure of several fields is defined as a table. All the fields of a structure need to be defined by a data element. Only field name is shown in the table. Within the table a data element can be used repeatedly. There are two types of table in ABAP dictionary; Transparent tables (option to store data in database and is created automatically) and Structures (they can be reused in programs as preconfigured type declarations)
(Fig: 4)
