Owner: abap dictionary complete URL:http://www.abapdictionary.blogspot.com Join Date: Mon, 29 Oct 2007 10:10:17 -0500 Rating:0 Site Description: This site consists of every thing regarding ABAP DICTIONARY.You can find every thing regarding ABAP dictionary including a series of lessons to explain complete course ,faq's ,interview questions etc.
Site statistics:Click here
SAP TABLES 2007-11-06 09:53:00 MM MODULECYCLE:Purchase Requisition (PR) Request for Quotation (RFQ) (Vendor Evaluation) Purchase Order (PO) Goods Receipt Note (GRN) Invoice Verification Data to FITables and important Fields.LFA1 – vendor data (LIFNR)LFB1 -- Company Code Segment : Vendor Data(LIFNR, BUKRS)LFC1 -- FI Related Vendor Data (LIFNR, BELNR)LFM1 – Pur. Orgn. Related Vendor Data (LIFNR, EKORG)MARA – Material Master (MATNR)MARC – Material Master with Plant Data (MATNR, WERKS)MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)MAKT – Material Master Material Descriptions (MATNR, MATKL)MBEW – Material Valuation Data (MATNR, BWTAR)MVKE – Material Master : Sales related DataMDKP, MDTB – MRP related Data( Header, Item)MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)EBAN – Pur. Req. Data( BANFN, BNFPO, BADAT, MATNR)EINA – Purchase Info. Record(General Data)(INFNR, MATNR, LIFNR)EINE – Purchase Info. Record (pur. Orgn. Data)
TABLE TYPES IN ABAP 2007-11-04 06:21:00 Choosing a Table TypeThe table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.Standard tablesThis is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.Sorted tablesThis is the most a
SELECTION METHOD ON SEARCH HELP IN ABAP 2007-11-02 04:30:00 The possible values displayed for a field by the input help are determined at runtime by a selection from the database. When a search help is defined, you must define the database object from which the data should be selected by specifying a table or a view as the selection method. It makes sense to use a view as selection method if the data about the possible values that is relevant for the input help is distributed on several tables. If this data is all in one table or in the corresponding text table, you can use the table as a selection method. The system automatically ensures that the text of the text table is used in the user's logon language. If there is not yet a view that combines the data that is relevant for an input help, you must first create it in the ABAP Dictionary. Maintenance views may not be used as the selection method for search helps. Normally a database view is used. However, you should note that database views (in the R/3 System) are always created with a
SEARCH HELP IN ABAP 2007-11-01 07:27:00 SEARCH HELP IN ABAP : The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection. The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4. If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions. The display of the possible entries is enhanced with further useful information about the displayed values. This feature is especially useful if the field requires the entry of a formal key. Since the input help is a standard function, it should look and behave the same throughout the entire R/3 System. The development environment therefor
INNER AND OUTER JOINS IN ABAP 2007-11-01 07:24:00 INNER AND OUTER JOINS IN ABAP: The set of data that can be selected with a view greatly depends on whether the view implements an inner join or an outer join. With an inner join, you only get those records which have an entry in all the tables included in the view. With an outer join, on the other hand, those records that do not have a corresponding entry in some of the tables included in the view are also selected. The hit list found with an inner join can therefore be a subset of the hit list found with an outer join. Database views implement an inner join. You only get those records which have an entry in all the tables included in the view. Maintenance views implement an outer join.(124)RELATED POSTSABAP VIEWS
ABAP VIEWS 2007-11-01 07:15:00 NEED OF VIEWS: Data for an application object is often distributed on several database tables. Database systems therefore provide you with a way of defining application-specific views on data in several tables. These are called views. Data from several tables can be combined in a meaningful way using a view (join). You can also hide information that is of no interest to you (projection) or only display those data records that satisfy certain conditions (selection). The data of a view can be displayed exactly like the data of a table in the extended table maintenance. Given two tables TABA and TABB. Table TABA contains 2 entries and table TABB 4 entries. The tables are first appended to one another. This results in the cross-product of the two tables, in which each record of TABA is combined with each record of TABB. Usually the entire cross-product is not a meaningful selection. You should therefore limit the cross-product with a join condition. The join condition describes how the r
APPEND STRUCTURE 2007-11-01 07:09:00 APPEND STRUCTURE: Append structures permit you to append customer fields to a SAP standard table without having to modify the table definition. An append structure is a structure which is assigned to exactly one table. There can be several append structures for a table. When a table is activated, all the active append structures for the table are found and their fields are appended to the table. If an append structure is created or changed, the table to which it is assigned is also activated and the changes also take effect there when it is activated. Like all structures, an append structure defines a type that can be used in ABAP programs. With Release 4.6C you can define foreign keys for fields that already exist in the table using an append structure. Search helps can also be attached to fields that already exist in the table. Customers create append structures in their namespace. The append structures are thus protected against overwriting during an upgrade. The new versions of t
CHANGES TO DATA BASE TABLES 2007-11-01 03:17:00 CHANGES TO DATA BASE TABLES: Correct access by ABAP programs to a database table is only possible if the runtime object of the table is consistent with the structure of the table in the database. Each time the table is changed in the ABAP Dictionary, you must check if the database structure of the table must be adjusted to the changed ABAP Dictionary definition of the table when it is activated (when the runtime object is rewritten). The database structure does not have to be altered for certain changes to the ABAP Dictionary. For example, you do not have to change the database structure when the order of the fields in the ABAP Dictionary is changed (other than for key fields). In this case the changed structure is simply activated in the ABAP Dictionary and the database structure remains unchanged. The database table can be adjusted to the changed definition in the ABAP Dictionary in three different ways: By deleting the database table and creating it again. The table on the dat
DEPENDENCIES OF ABAP DICTIONARY OBJECTS 2007-10-31 21:48:00 ACTIVE AND INACTIVE VERSIONS: During development, you sometimes need to change an (active) object already used by the system. Such changes are supported in the ABAP Dictionary by separating the active and inactive versions. The active version of an ABAP Dictionary object is the version that the components of the runtime environment (for example ABAP processor, database interface) access. This version is not initially changed. An inactive version is created when an active object is changed. The inactive version can be saved without checking. It has no effect on the runtime system. At the end of the development process, the inactive version can be made the active version. This is done by activation. The inactive version of the object is first checked for consistency. If it is consistent, the inactive version replaces the active one. From now on, the runtime system uses the new active version.RUN TIME OBJECTS: The information about a structure (or table) is distributed in the ABAP Diction
CONSISTENCY 2007-10-30 22:23:00 The domain describes the value range of a field by specifying its data type and field length. If only a limited set of values is allowed, they can be defined as fixed values. Specifying fixed values causes the value range of the domain to be restricted by these values. Fixed values are immediately used as check values in screen entries. There is also an F4 help. Fixed values are only checked in screens. No check is made when data records are inserted in a table by an ABAP program. Fixed values can either be listed individually or defined as an interval. The value range of a field can also be defined by specifying a value table in the domain. In contrast to fixed values, however, simply specifying a value table does not cause the input to be checked. There is no F4 help either. If you enter a value table, the system can make a proposal for the foreign key definition. A value table only becomes a check table when a foreign key is defined.If you refer to a domain with a value table i
INDEXING AND BUFFERING 2007-10-30 12:15:00 PERFORMACE DURING TABLE AINDEXINGCCESS : An index can be used to speed up the selection of data records from a table. An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read. When creating indexes, please note that: An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position. Only those fields whose values significantly restrict the amount of data are meaningful in an index. When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently cha
TABLES IN ABAP DICTIONARY 2007-10-27 23:10:00 The structure of the objects of application development are mapped in tables on the underlying relational database. The attributes of these objects correspond to fields of the table. A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization. A field has a unique name and attributes; for example it can be a key field. A table has one or more key fields, called the primary key. The values of these key fields uniquely identify a table entry. The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description). A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying f
ABAP DICTIONARY INTRODUCTIOIN 2007-10-26 10:10:00 The ABAP Dictionary permits a central management of all the data definitions used in the R/3 System. In the ABAP Dictionary you can create user-defined types (data elements, structures and table types) for use in ABAP programs or in interfaces of function modules. Database objects such as tables and database views can also be defined in the ABAP Dictionary and created with this definition in the database. The ABAP Dictionary also provides a number of services that support program development. For example, setting and releasing locks, defining an input help (F4 help) and attaching a field help (F1 help) to a screen field are supported. Tables and database views can be defined in the ABAP Dictionary. These objects are created in the underlying database with this definition. Changes in the definition of a table or database view are also automatically made in the database. Indexes can be defined in the ABAP Dictionary to speed up access to data in a table. These indexes are also created
Creating Collective Search Helps 2008-06-06 08:28:00 Procedure In the initial screen of the ABAP Dictionary, select object class Search
help, enter the name of the search help and choose Create. A dialog box appears in which you must select the type of search help. Select Collective
search help and choose . The maintenance screen for collective search helps is displayed. Enter an explanatory text in the field Short text. You can for e Read more:Creating
SAP Data Base Index Unique Scan 2008-06-07 12:34:00 If, for all fields in a unique index (primary index or unique secondary index), WHERE conditions are specified with '=' in the WHERE clause, the database optimizer selects the access strategy index unique scan. For the index unique scan access strategy, the database usually needs to read a maximum of four data blocks (three index blocks and one table block) to access the table record. In the Read more:Index
Data Base Index over view 2008-06-07 12:31:00 Overview When you create a database table in the ABAP Dictionary, you must specify the combination of fields that enable an entry within the table to be clearly identified. The key fields must be specified at the top of the table field list, and define them as key fields. A minimum of 1 key field and a maximum of 16 key fields can be defined. When the table is activated, an index formed from Read more:Index
Data Base Optimizer part two 2008-06-07 12:24:00 Continued from the last post data base optimizer part one.Unsuitable access path : If the single object analysis establishes that an expensive SQL statement has an unsuitable access path, you can narrow (and thus optimize) the search. The search range is the number of data records that needs to be checked in a table in order to satisfy an SQL statement. When the SQL statement is processed on Read more:Optimizer
Hashed Table usage 2008-06-07 12:18:00 What is use of using HASHED TABLE? Hashed table is useful when your have to work with very big internal table and to read it with "READ TABLE WITH KEY ..." The time access is constant ! Definition of a Hashed Table
: "Defines the table as one that is managed with an internal hash procedure. You can imagine a hashed table as a set, whose elements you can address using their u
Data Base Optimizer 2008-06-06 10:52:00 Cost Based Data Base Optimizer
The database optimizer is the most important part of a relational database system. For each SQL statement, the database optimizer determines the strategy for accessing data records. Access can be with database indexes (index access), or without database indexes (full table scan). The cost-based database optimizer determines the access strategy on the basis of
Problems with data base access in sap abap 2008-06-08 00:57:00 MISSING CRITICAL OPERATORS IN WHERE CLAUSE If fields in the WHERE clause are specified with operators NOT or , these WHERE conditions cannot be used for a search over a database index. You should therefore formulate SQL statements positively wherever possible. If a positive formulation cannot be used, for example because the IN list would be too long, you should still specify the WHERE condit
Problems with data base access part two 2008-06-08 00:49:00 OLD TABLE INDEX STATISTICS To ensure that the cost-based database optimizer functions properly, the table and index statistics must be updated regularly. The database optimizer uses these statistics as a basis for selecting the access strategy used to execute a particular SQL statement. The database administrator must update the table and index statistics regularly. To find out when the last u
Problems with data base access 2008-06-08 00:43:00 Optimizing SQL statements only makes sense if the R/3 System and database system are correctly configured. This is the responsibility of the R/3 System administrator and the database administrator respectively. Technical problems may have an effect on the whole system (for example, wrongly set parameters, communication problems, old table and index statistics), or may only affect SQL statements on
Data Base Joins part two 2008-06-08 00:37:00 Sort merge join When a join is processed using the sort merge join access strategy, the following steps are performed: The table records that correspond to the WHERE clause are selected The tables in the join are sorted according to the JOIN condition The table records are merged For the SQL statement above, the selective WHERE condition for field CUOBJ, table VVBAP, and the sel
Data Base Joins 2008-06-08 00:25:00 In the R/3 System, users often need to access information stored in different tables. The database-logical operator used to do this is called the JOIN operator. In ABAP, there are various ways to implement the JOIN operator (nested SELECTs, SELECT FOR ALL ENTRIES, DB views, ABAP JOINS, subqueries, explicit cursor). If you want the database system to determine the resulting set of the JOIN
Data Base Index in detail 2008-06-08 00:19:00 Full Table Scan If the database optimizer selects the full table scan access strategy, the table is read sequentially. Index
blocks do not need to be read. For a full table scan, the read table blocks are added to the end of an LRU list. Therefore, no data blocks are forced out of the data buffer. As a result, in order to process a full table scan, comparatively little memory space is requir
Changing Index design rules 2008-06-09 06:47:00 An index only makes sense if SQL statements that use the index return less than 5% of the table records. The index fields must therefore significantly reduce the resulting sets. Otherwise, the database optimizer would perform a full table scan anyway. Index
es must not be contained in other indexes (that is, they must be disjunct), because the cost-based database optimizer can also select the inde Read more:Changing
, design
Index design in data base for SAP 2008-06-11 06:38:00 Changing the index design
of a table in the R/3 System can affect SQL statements other than the one you want to optimize. You must therefore ensure that other SQL statements are not negatively influenced by a new, changed or deleted index. To do this, you must first establish which database views are referenced on the table. You can find this information in the where-used list in the ABAP Diction Read more:Index
Changing Index design rules part two 2008-06-10 10:40:00 Selective Analysis and distinct values : When you are sure about what the index fields mean (that is, their semantic meaning), check how many distinct values there are for each index field. Distinct values are the number different values per field in a particular database table. The relationship between the total number of data records in a table and the distinct values per field indicates how Read more:Index
, design
, Changing
Accessing individual tables in abap dictionary 2008-06-12 07:47:00 SELECT FOR ALL ENTRIES:With SELECT FOR ALL ENTRIES, you can divide SELECT statements into loops. This variant enables you to create a JOIN between an internal table and a database table. In the example above, only the records from table KKNA1 are read that have customer numbers in the internal table g_itab_vvbak. The following problems occur with SELECT FOR ALL ENTRIES: You cannot have an e
Using data base hints in abap reports 2008-06-12 07:34:00 If you want to force the database optimizer to choose a particular execution path, use database hints. In R/3 Releases before 4.5A, database hints can only be used in the respective database-specific SQL dialects (native SQL in the parentheses EXEC SQL. … ENDEXEC.). As of R/3 Release 4.5A, you can use database hints directly from OPEN SQL. To do this, add the addition %_HINTS DBMS ‘DBHINT’
Recommend Site To A Friend
