Local classes/interfaces are only known within the program in which they are defined and implemented.Local classes/interfaces are not stored in the Repository (no TADIR entry). There is no “global” access to these classes/interfaces (for example, from other programs).

If a local class is implemented in an include which is then embedded in two different programs, then references to the “same” class still cannot be exchanged at run time. Two classes that do not conform to type are created at run time.Unlike local in program classes/interfaces, global classes/interfaces can be created and implemented using the ABAP Workbench Tool Class Builder or transaction SE24. These classes/interfaces are then available to all developers.

Global class and interface names share the same namespace.Global classes/interfaces have a TADIR entry: R3TR CLASS  The smallest transport unit is method LIMU METH.The Class Builder is a tool in the ABAP Workbench that is used to create, define and test global ABAP classes and interfaces.

In the initial screen, select the object type you want to work with - class or interface. Then choose one of the display, change, create or test functions.In the initial screen you have the choice of viewing the contents of the R/3 class library using the Class Browser or going straight to basic data maintenance of the object types and the Class Editor, where you can define the object types and their components.
The object type definition can be immediately followed by method implementation in the ABAP Editor. You can also access the test environment from the initial screen or from the Class Editor.

In the Class Builder you have the same options for creating a global class as for creating a local class.



CRM Technical Architecture

No comments :

Post a Comment