Wednesday, November 7, 2012
Thursday, October 25, 2012
SAP INTERNAL TABLE TYPES
Types of Internal Table
1.
Standard Table.
2.
Sorted Table.
3.
Hashed Table.
Standard Tables
The
most appropriate type if one is going to address the individual table entries
using the index or key. Index access is the quickest possible access. Standard
tables have an internal linear index. The indexes of internal tables are
administered as trees.
If you
need key access, standard tables are particularly useful if you can fill and
process the table in separate steps. Key access
to a standard table uses a linear search. 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. If no key is specified, the standard table receives the default
key, which is a combination of all character-like fields.
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. 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 Tables
The
most appropriate type if you need a table which is sorted as you fill it. You
fill sorted tables using the INSERT statement. Entries are inserted according to
the sort sequence defined through the table key. Any illegal entries are
recognized as soon as you try to add them to the table. The response time for
key access is logarithmically proportional to the number of table entries,
since the system always uses a binary search. Sorted tables are particularly
useful for partially sequential processing in a LOOP if you specify the
beginning of the table key in the WHERE condition.
If the key is not unique, the system takes the entry with the
lowest index. 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 not.
Hashed Tables
The
most appropriate type for any table where the main 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. Like database
tables, hashed tables always have a unique key. Hashed tables are useful if you
want to construct and use an internal table which resembles a database table or
for processing large amounts of data.
Defines the table as one that is managed with an internal
hash procedure. You can only access a hashed table using the generic key
operations or other generic operations (SORT, LOOP, and so on). Explicit or
implicit index operations (such as LOOP ... FROM or INSERT itab within a LOOP)
are not allowed. Hashed tables have no linear index. The key of hashed tables must be unique.
Index Tables
A table that can be accessed using an index. Index table is
only used to specify the type of generic parameters in a FORM or FUNCTION. That
means that you can't create a table of type INDEX.
Standard tables and sorted tables are also referred to as index tables because both
tables can be accessed using the table index. Standard tables and sorted tables are known generically as index tables.
Standard tables and sorted tables are also referred to as index tables because both
tables can be accessed using the table index. Standard tables and sorted tables are known generically as index tables.
SAP PROGRAM TYPES
SAP ABAP PROGRAMS
Each ABAP program
has a type, which is defined in the program attributes. The program
type determines which processing blocks a program can contain, and how the
program is handled and executed by the runtime environment.
In the R/3 System, there are various ABAP program
types. The program type determines the basic technical attributes of the
program, and you must set it when you create it. The main difference between
the different program types is the way in which the runtime environment calls
its processing blocks.
Type
1 programs
Type 1 programs do
not have to be controlled using user-defined screens. These are controlled by the runtime environment. Type 1
programs are called as Executable
programs as they can be executed by typing the name of the program directly.
Type 1 programs are also called as Online
program.
Type 1 programs (executable programs) in the R/3 System are often
referred to as reports. Executable programs do not require any user
dialog. You can also assign a transaction code to an executable program. This
kind of transaction is called a report
transaction.
Type
M programs
Type M programs
can only be controlled using screen flow logic. You must start them using a
transaction code, which is linked to the program and one of its screens
(initial screen). You must define your own screens in the Screen Painter
(although the initial screen can be a selection screen). Type M programs are called as Module
pools or Dialogue programs.
Type
F programs
Type F programs
are containers for function modules. These programs cannot be
started using a transaction code or by entering their name directly. Type F programs can be called from other executable
programs or Module Pool programs by inserting the code of the Function Module. Type F programs
are called as Function groups. Function modules may only be
programmed in function groups. Apart from function modules, function groups can
contain global data declarations and subroutines. These are visible to all
function modules in the group. Function Modules and
Function groups can be created using transaction code SE37 or SE80.
Type
K programs
Type K programs are containers for global classes in
ABAP Objects. They cannot be started by using a program name or using a
Transaction Code. Type
K programs are known as Class definitions or Class pool. Type K programs are created using a Class Builder (SE
24).
Type
J programs
You cannot start
type J programs using a transaction code or by entering the program name
directly. These programs are containers for global interface in ABAP Objects. Type J programs are known
as Interface definitions or Interface pool. You create interface
definitions in the Class Builder.
Type
S programs
Type S programs
are known as Subroutine pools. These
types of programs are containers for subroutines. You cannot start a
type S program using a transaction code or by entering the program name.
Instead, they are containers for subroutines, which you can call externally
from other ABAP programs. They cannot contain screens.
Type
I programs
Type
I programs are called as Includes or Include program. They are used to make code simpler by breaking it into
smaller units. You
can insert the coding of an include program at any point in another ABAP
program using the INCLUDE statement. There is no technical relationship between
include programs and processing blocks. These
types of programs cannot be run using the program name or a transaction code. The ABAP Workbench has a mechanism for
automatically dividing up module pools and function groups into include
programs.
Sunday, October 21, 2012
Wednesday, October 17, 2012
TYPES OF VIEWS IN SAP
There are 4 different view types in sap system. These differ in the way in which the view is implemented and in the methods permitted for accessing the view data.
1. Database Views
It is implemented with an
equivalent view on the database.
2. Projection Views
It is used to hide fields of a
table (only projection).
3. Help Views
It is used as selection method
in search helps.
4. Maintenance Views
It permits you to maintain the
data distributed on several tables for one application object at one time.
SAP VIEWS
What is SAP View?
Ans: Data about an application object is often
distributed on several tables. By defining a: view, you can define an
application-dependent view that combines this data. The structure of such a
view is defined by specifying the tables and fields used in the view. Fields
that are not required can be hidden, thereby minimizing interfaces. A view can
be used in ABAP programs for data selection.
The data of a
view is derived from one or more tables, but not stored physically. The
simplest form of deriving data is to mask out one or more fields from a base
table (projection) or to include only certain entries of a base table in the
view (selection). More complicated views can comprise several base tables, the
individual tables being linked with a relational join operation.
In First Step of a view definition the base tables of the view
must be selected.
In Second Step these base tables must be linked by defining the
join conditions. It is also possible to use the join condition from a foreign
key defined between the tables.
In Third Step you must select the fields of the base tables to be
used in the view. Selection conditions that restrict the records in the view
can be formulated in the fourth step.
SAP LOCK MODES
THERE ARE FOUR TYPES OF LOCK MODES IN THE SAP SYSTEM:
1. S (Shared) mode for shared lock.
2. E (Exclusive) mode for exclusive locks.
3. X (eXclusive non-cumulative) mode for exclusive but not cumulative locks
4. (Optimistic) mode for optimistic lock.
SAP Internal Tables
What is an Internal Table?
Internal table is a temporary table stored in the RAM of the application server. It gets created during the program execution and gets deleted once the program ends. Internal tables can exist both as data types and as data objects.
SAP PM BOOKS
Free SAP PM EBOOKS
SAP PM Books Free Download
SAP QM BOOKS
Free SAP QM EBOOKS
SAP QM Books Free Download
SAP PP BOOKS
Free SAP PP EBOOKS
SAP PP Books Free Download
SAP FICO BOOKS
Free SAP FICO EBOOKS
SAP FICO Books Free Download
_______________________________________________________________________________
Tuesday, October 16, 2012
SAP ABAP BOOKS
Free SAP
ABAP EBOOKS
SAP
ABAP Books Free Download
Wednesday, March 14, 2012
SAP MM Tables
SAP Materials Management Tables
SAP MM Purchasing Tables:
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EBUB Index for Stock Transport Requisitions for Material
EINA Purchasing Info Record: General Data
EINE Purchasing Info Record: Purchasing Organization D
EIPA Order Price History: Info Record
EKAB Release Documentation
EKAN Vendor Address: Purchasing Document
EKBE History per Purchasing Document
EKBEH Removed PO History Records
EKBZ History per Purchasing Document: Delivery Costs
EKBZH History per Purchasing Document: Delivery Costs
EKEH Scheduling Agreement Release Documentation
EKEK Header Data for Scheduling Agreement Releases
EKES Vendor Confirmations
EKET Scheduling Agreement Schedule Lines
EKETH Scheduling Agreement Schedules: History Tables
EKKI Purchasing Condition Index
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPA Partner Roles in Purchasing
EKPB "Material Provided" Item in Purchasing Document
EKPO Purchasing Document Item
EKPV Shipping-Specific Data on Stock Tfr. for Purch. D
EKRS ERS Procedure: Goods (Merchandise) Movements to b
EKUB Index for Stock Transport Orders for Material
EORD Purchasing Source List
EQUK Quota File: Header
EQUP Quota File: Item
T024 Purchasing Groups
T024E Purchasing Organizations
T024W Valid Purchasing Organizations for Plant
T024Z Purchasing Organizations
T027A Shipping Instructions, Purchasing
T027B Texts: Shipping Instructions
T027C Codes for Compliance with Shipping Instructions
T027D Compliance with Shipping Instructions: Texts
T069 Certificate Categories
T069Q Control Data for Source Determination and Checkin
T069T Certificate Categories: Text Description
EBKN Purchase Requisition Account Assignment
EBUB Index for Stock Transport Requisitions for Material
EINA Purchasing Info Record: General Data
EINE Purchasing Info Record: Purchasing Organization D
EIPA Order Price History: Info Record
EKAB Release Documentation
EKAN Vendor Address: Purchasing Document
EKBE History per Purchasing Document
EKBEH Removed PO History Records
EKBZ History per Purchasing Document: Delivery Costs
EKBZH History per Purchasing Document: Delivery Costs
EKEH Scheduling Agreement Release Documentation
EKEK Header Data for Scheduling Agreement Releases
EKES Vendor Confirmations
EKET Scheduling Agreement Schedule Lines
EKETH Scheduling Agreement Schedules: History Tables
EKKI Purchasing Condition Index
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPA Partner Roles in Purchasing
EKPB "Material Provided" Item in Purchasing Document
EKPO Purchasing Document Item
EKPV Shipping-Specific Data on Stock Tfr. for Purch. D
EKRS ERS Procedure: Goods (Merchandise) Movements to b
EKUB Index for Stock Transport Orders for Material
EORD Purchasing Source List
EQUK Quota File: Header
EQUP Quota File: Item
T024 Purchasing Groups
T024E Purchasing Organizations
T024W Valid Purchasing Organizations for Plant
T024Z Purchasing Organizations
T027A Shipping Instructions, Purchasing
T027B Texts: Shipping Instructions
T027C Codes for Compliance with Shipping Instructions
T027D Compliance with Shipping Instructions: Texts
T069 Certificate Categories
T069Q Control Data for Source Determination and Checkin
T069T Certificate Categories: Text Description
Tuesday, March 13, 2012
SAP SD Tables
SAP Sales and Distribution Tables:
Customers
KNA1 General Data
KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master – Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
Sales Documents
VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document - Header Data
VBKD Sales Document - Business Data
VBUP Item Status
VBAP Sales Document - Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
Materials
MARA Material Master: General
MARC Material Master: Plant
MAKT Material Master: Short description
MARM Material Master: Conversion factors
MVKE Material Master: Sales
MLAN Material Master: Sales
MAEX Material Master: Export Licenses
MBEW Material Master: Valuation
MLGN Material Master: WM Inventory
MLGT Material Master: WM Inventory type
MVER Material Master: Consumption
DVER Material Master: Consumption
MAPR Material Master: Forecast
MARD Material Master: Storage Location
MCH1 Material Master: X Plant Batches
MCHA Material Master: Batches
MCHB Material Master: Batch Stock
MARCH Material Master C Segment: History
MARDH Material Master Storage Location Segment: History
MBEWH Material Valuation: History
MCHBH Batch Stocks: History
MKOLH Special Stocks from Vendor: History
MSCAH Sales Order Stock at Vendor: History
MSKAH Sales Order Stock: History
MSKUH Special Stocks at Customer: History
MSLBH Special Stocks at Vendor: History
MSPRH Project Stock: History
MSSAH Total Sales Order Stocks: History
MSSQH Total Project Stocks: History
Subscribe to:
Posts (Atom)