Skip to main content

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  zsan. ** T Y P E    D E C L A R A T I O N ** TYPES  :  BEGIN   OF  ty_mara,          matnr  TYPE  matnr,          ernam  TYPE  ernam,          pstat  TYPE  pstat_d,          END   OF  ty_mara,          BEGIN   OF  ty_makt,          matnr  TYPE  matnr,          spras  TYPE  spras,          maktx  TYPE  maktx,          END   OF  ty_makt,          BEGIN   OF  ty_final,          matnr  TYPE  matnr,          ernam  TYPE  ernam,          pstat  TYPE  pstat_d,          maktx  TY

Tpes of Internal Table in ABAP

Tpes of Internal Table in ABAP
Internal tables are used to access a data in a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line(record) has the same structure.
Standard Internal Tables
Standard Internal Tables are default internal tables.
We can use either key or index operation to read an entry .
we can use either linear search or binary search to search for an entry, .
We can Apply sort operation.
If you are going to address the individual table entries using the index. Index access is the quickest possible access ,this is the best suitable table.
We can use insert and append to add records.
It have an internal linear index.
The system can access records either by using the table index or the key.
The response time for key access is proportional to the number of entries in the table.
The key of a standard table is always non-unique.
You cannot specify a unique key.
This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.
Sorted Internal Tables
These are a special type of internal tables, where data is automatically sorted as you insert the record.
Sorted tables are always saved sorted by the key.
They also have an internal index.
The system can access records either by using the table index or the key.
The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search.
The key of a sorted table can be either unique or non-unique.
When you define the table, you must specify whether the key is to be UNIQUE or NON-UNIQUE. Standard tables and sorted tables are known generically as index tables.
We use either key or index operation to read a record .
This is the most suitable type if you want a table which is sorted as you fill it. You process sorted tables using the INSERT statement.
You use binary search as data is already sorted for searching an entry.
You can't sort as data is already sorted.
You can apply insert, not append.
Hashed Internal Tables
Hashed tables have no linear index.
You can only access a hashed table using its key.
The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm.
The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.
These are used with logical databases i:e with all fields and all records.
Index operation is not possible, you only use key operation.
You use hashed algorithm to search for any entry.
Which are mostly used in ABAP with BI projects
This is the most suitable when you use operation is key access.
You cannot access a hashed table using its index.
The response time for key access remains constant, regardless of the number of table entries.
End

Comments

Popular posts from this blog

How to Create SAP ABAP Query Using SQ01 Step by Step Guide

How to Create SAP ABAP Query Using SQ01 Step by Step. You can create ABAP query objects ,if they are not exist in the SAP system. You can create SAP query without  ABAP programming knowledge. ABAP Query provides users with a variety of ways to define and create different types of  reports , such as  Basic Lists ,  Stats , and  Sorted Lists . ABAP query consists of four elements: Queries InfoSets Groups Translation query Queries The query component is used by end users for Queries. You can create queries, change and queries executed. Transaction  SQ01. Trnslation component / QUERY Many texts to define queries, InfoSets and user groups are generated. These texts are displayed in the language we choose to access the SAP system. We can compare the text or languages ​​that use this component. InfoSets InfoSets are the views of the Special Data Sources. An InfoSet Describes the fields of a data source that can be reported in the query. An InfoSet can be assig

BADI in SAP ABAP Step by Step

BADI in SAP ABAP Step by Step BAdI Acronym of Business Add Ins As a customer outsider, it helps BAdI to improve SAP functionality. Why is BADI? Unlike previous improvement methods, BADI continues the approach aimed at re-use objectives. BADI can be used in a number of times that these standard evaluation techniques can only be used once. For example, if you are upgrading a custom project, you can not map the extension on other custom projects. In order to overcome this disadvantage, SAP provided a new evaluation technique called BADI. Code of transaction for BADI definition: SE18 When you create a BAdI definition, you create a class interface automatically and you can define the methods in the interface. The application of the methods can be made in SE19 transactions. When created BAD, they are generated automatically: An interface with 'IF_EX_' is inserted between the first and second characters of the BAdi name Class classified as 'CL_EX_' inserted betwee

SAP Table Structure T-codes

SAP table structure tcodes E11 - ABAP Dictionary Maintenance Basis - Dictionary Maintenance SE14 - Utilities for Dictionary tables Basis - Activation Program, Conversion Program, DB Utility, MC,  SPDDCU61 - Create table structure Cross Application - Object Dependencies CU63 - Display table structure Cross Application - Object Dependencies CU62 - Change table structure Cross Application - Object Dependencie CU64 - table structure List Cross Application - Object Dependencies LBWE - LO Data Ext.: Customizing Cockpit Logistics - Logistics Information System (LIS)RSA6 - Maintain DataSources Basis - BW Service APIRSO2 - Oltp Metadata Repository Basis - BW Service  APISE84 - Repository Information System Basis - Workbench Tools: Editors, Painters, Modelers SE38 - ABAP Editor Basis - ABAP Editor SE16 - Data Browser Basis - Workbench Utilities SM30 - Call View Maintenance Basis - Table Maintenance Tool SE37 - ABAP Function Modules Basis - Function Builder SE80 - Object Navigator