File Exit, Menu Exit, Function Exit.
CMOD : This transaction allows you to create a PROJECT by identifying its ENHANCEMENT(S). After determining all of the ENHANCEMENTS that are part of the PROJECT, you will have to activate the PROJECT. You will still need to code your user-exit; therefore, you may want to wait until this step is completed before activating the PROJECT. §SMOD : This transaction allows you to create an ENHANCEMENT, which you will include in a PROJECT, by identifying its COMPONENT(S). In the case where SAP has already created an ENHANCEMENT for its pre-defined user-exits, you will not need to use transaction SMOD; instead, you should just use transaction CMOD.
Yes, We can use TC SE93 for creating our own transaction code.
Table controls are modified / mproved versions of step loops. in controls we can do, horizontal scrolling, vertical scrolling, scrolling in a perticular field, resize the table, can save the settings for future use, can make selective columns editable,....etc these things are not possible with step loops. step loops are controlled by loop-endloop statements.
In an Interactive Report, user can define maximum 20 secondary lists.
UNPACK field1TO field2 .Unpacks the packed field field1 and places it in the field field2 with leading zeros. If field2 is too short, it is truncated on the left.
Available Dictionary Objects are Domains, Viwes, Match Codes, Lock Objects, Structures, Data Elements, Intenal Types.
Transparent tables have 1 - 1 cardinality b/w Data Dictionary and Database, and non transparent ( Cluster and Pooled) tables have Many - 1 cardinality. Transparent table can access with using OPen & NAtive SQL stmts where as Nontransparent only OPen Sql. Transparent trables can store Table relevent data and non transparent tables can store system data/ application data based on the transparent tables
BDC -> BATCH DATA COMMUNICATION. METHODS OF BDC-> Direct Input method, Batch Input Session method, Call transaction method.
1. Function modules use a special screen to define the parameters where as subroutines use the same ABAP/4 editor to define its parameters.
2. Tables work area can be commonly shared by calling program and subroutine where as function modules do not share commonly.
3. Calling a function module syntax (Call function.) is different from calling a subroutine syntax (perform….).
4. With raise statement user can exit from a function module where as exit is used in subroutines.