Translation of non-ABAP objects

Hello colleagues,
I know that SAP provides special Translation Environment for translation of ABAP-objects (TX SE63 etc.). But what about translation of non-ABAP objects? Could be SE63 suitable for this task or it can be performed only via translation xlf files (SAP NW Developer Studion and so on)?
Regards,
Arkadiy

Hi Prakash,
firstly thank you for you reply.
Secondly I know about three main categories of non-ABAP objects but I haven't an information about what is it certainly? So there are at least two questions in my opinion:
1) Could it be suitable to translate Java objects or WebDyn Pro Java objects?
2) If yes, how it can be suitable for it? Because I know how I can translate Java or WebDynpro via NW Developer Studio, but I don't know how it can be possible via SE63.
Really I can't find any helpful information about translation non-ABAP objects via SE63.
Could anyone help me in my questions?
Regards,
Arkadiy

Similar Messages

CTS+ Configuration for Transporting non-ABAP objects in Portal Landscape using solution manage 7.1 sp8

Hi,
Currently we have cts+ already configured for our portal systems in our landscape through solution manager 7.0.
Recently we had setup a new solution manager 7.1 and need to perform cts+ configuration using this new solution manager 7.1 as we are planning to remove our old solution manager 7.0 very soon.
We are using NWDI system for transporting our portal transports.
Please help me with steps on how to configure cts+ using solution manager 7.1 using NWDI.

Hi Naveen,
Please find given below BBPCRM & SAP_BW version..
BBPCRM 500 0013 SAPKU50013 BBPCRM BBP/CRM Supp. Pack.
SAP_BW 701 0003 SAPKW70103 SAP Business Warehouse Component Supp. Pkg.
This problem is not only with Bussiness process tab (T-Code: Solution_manage) also System monitoring Still i searching solution for this But once we are restarting System that time this problem is not occuring but after some time system is giving this DUMP
Regards,
Suresh

Translation of a Workbench request(ABAP Object)

Hi,
I want to maintain translation for all the objects in a workbench request at one go.
Is this possible? If yes, how?
I tried using se63 for this but could not make out. Please help.
Regards,
Jose

Hi Jose,
Please refer the below links :-
http://help.sap.com/saphelp_nw70/helpdata/en/d4/73c33e3a443907e10000000a114084/content.htm
https://help.sap.com/saphelp_nwmobile71/helpdata/en/d4/73c33e3a443907e10000000a114084/content.htm
Hope this is useful.
Regards,
Anish

Undesratsnding abap objects

hi
can any one provide basic material for underatanding object oriented in abap...with many sample programs(preferably)....u can also provide me links....
thank you,
Ginni

Methods in ABAP Objects - Example
The following example shows how to declare, implement, and use methods in ABAP Objects.
Overview
This example uses three classes called C_TEAM, C_BIKER, and C_BICYCLE. A user (a program) can create objects of the class C_TEAM. On a selection screen, the class C_TEAM asks for the number of members of each team.
Each object in the class C_TEAM can create as many instances of the class C_BIKER as there are members in the team. Each instance of the class C_BIKER creates an instances of the class C_BICYCLE.
Each instance of the class C_TEAM can communicate with the program user through an interactive list. The program user can choose individual team members for actions. The instances of the class C_BIKER allow the program user to choose the action on a further selection screen.
Constraints
The ABAP statements used for list processing are not yet fully available in ABAP Objects. However, to produce a simple test output, you can use the following statements:
WRITE [AT] /<offset>(<length>) <f>
ULINE
SKIP
NEW-LINE
Note: The behavior of formatting and interactive list functions in their current state are not guaranteed. Incompatible changes could occur in a future release.
Declarations
This example is implemented using local classes, since selection screens belong to an ABAP program, and cannot be defined or called in global classes. Below are the definitions of the two selection screens and three classes:
Global Selection Screens
SELECTION-SCREEN BEGIN OF: SCREEN 100 TITLE TIT1, LINE.
PARAMETERS MEMBERS TYPE I DEFAULT 10.
SELECTION-SCREEN END OF: LINE, SCREEN 100.
SELECTION-SCREEN BEGIN OF SCREEN 200 TITLE TIT2.
PARAMETERS: DRIVE RADIOBUTTON GROUP ACTN,
 STOP RADIOBUTTON GROUP ACTN,
 GEARUP RADIOBUTTON GROUP ACTN,
 GEARDOWN RADIOBUTTON GROUP ACTN.
SELECTION-SCREEN END OF SCREEN 200.
Class Definitions
CLASS: C_BIKER DEFINITION DEFERRED,
 C_BICYCLE DEFINITION DEFERRED.
CLASS C_TEAM DEFINITION.
PUBLIC SECTION.
TYPES: BIKER_REF TYPE REF TO C_BIKER,
 BIKER_REF_TAB TYPE STANDARD TABLE OF BIKER_REF
 WITH DEFAULT KEY,
 BEGIN OF STATUS_LINE_TYPE,
 FLAG(1) TYPE C,
 TEXT1(5) TYPE C,
 ID TYPE I,
 TEXT2(7) TYPE C,
 TEXT3(6) TYPE C,
 GEAR TYPE I,
 TEXT4(7) TYPE C,
 SPEED TYPE I,
 END OF STATUS_LINE_TYPE.
CLASS-METHODS: CLASS_CONSTRUCTOR.
METHODS: CONSTRUCTOR,
 CREATE_TEAM,
 SELECTION,
 EXECUTION.
PRIVATE SECTION.
CLASS-DATA: TEAM_MEMBERS TYPE I,
 COUNTER TYPE I.
DATA: ID TYPE I,
 STATUS_LINE TYPE STATUS_LINE_TYPE,
 STATUS_LIST TYPE SORTED TABLE OF STATUS_LINE_TYPE
 WITH UNIQUE KEY ID,
 BIKER_TAB TYPE BIKER_REF_TAB,
 BIKER_SELECTION LIKE BIKER_TAB,
 BIKER LIKE LINE OF BIKER_TAB.
METHODS: WRITE_LIST.
ENDCLASS.
CLASS C_BIKER DEFINITION.
PUBLIC SECTION.
METHODS: CONSTRUCTOR IMPORTING TEAM_ID TYPE I MEMBERS TYPE I,
 SELECT_ACTION,
 STATUS_LINE EXPORTING LINE
 TYPE C_TEAM=>STATUS_LINE_TYPE.
PRIVATE SECTION.
CLASS-DATA COUNTER TYPE I.
DATA: ID TYPE I,
 BIKE TYPE REF TO C_BICYCLE,
 GEAR_STATUS TYPE I VALUE 1,
 SPEED_STATUS TYPE I VALUE 0.
METHODS BIKER_ACTION IMPORTING ACTION TYPE I.
ENDCLASS.
CLASS C_BICYCLE DEFINITION.
PUBLIC SECTION.
METHODS: DRIVE EXPORTING VELOCITY TYPE I,
 STOP EXPORTING VELOCITY TYPE I,
 CHANGE_GEAR IMPORTING CHANGE TYPE I
 RETURNING VALUE(GEAR) TYPE I
 EXCEPTIONS GEAR_MIN GEAR_MAX.
PRIVATE SECTION.
DATA: SPEED TYPE I,
 GEAR TYPE I VALUE 1.
CONSTANTS: MAX_GEAR TYPE I VALUE 18,
 MIN_GEAR TYPE I VALUE 1.
ENDCLASS.
Note that none of the three classes has any public attributes. The states of the classes can only be changed by their methods. The class C_TEAM contains a static constructor CLASS_CONSTRUCTOR. C_TEAM and C_BIKER both contain instance constructors.
Implementations
The implementation parts of the classes contain the implementations of all of the methods declared in the corresponding declaration parts. The interfaces of the methods have already been defined in the declarations. In the implementations, the interface parameters behave like local data.
Methods of Class C_TEAM
The following methods are implemented in the section
CLASS C_TEAM IMPLEMENTATION.
ENDCLASS.
CLASS_CONSTRUCTOR
METHOD CLASS_CONSTRUCTOR.
 TIT1 = 'Team members ?'.
 CALL SELECTION-SCREEN 100 STARTING AT 5 3.
 IF SY-SUBRC NE 0.
 LEAVE PROGRAM.
 ELSE.
 TEAM_MEMBERS = MEMBERS.
 ENDIF.
ENDMETHOD.
The static constructor is executed before the class C_TEAM is used for the first time in a program. It calls the selection screen 100 and sets the static attribute TEAM_MEMBERS to the value entered by the program user. This attribute has the same value for all instances of the class C_TEAM.
CONSTRUCTOR
METHOD CONSTRUCTOR.
 COUNTER = COUNTER + 1.
 ID = COUNTER.
ENDMETHOD.
The instance constructor is executed directly after each instance of the class C_TEAM is created. It is used to count the number of instance of C_TEAM in the static attribute COUNTER, and assigns the corresponding number to the instance attribute ID of each instance of the class.
CREATE_TEAM
METHOD CREATE_TEAM.
 DO TEAM_MEMBERS TIMES.
 CREATE OBJECT BIKER EXPORTING TEAM_ID = ID
 MEMBERS = TEAM_MEMBERS.
 APPEND BIKER TO BIKER_TAB.
 CALL METHOD BIKER->STATUS_LINE IMPORTING LINE = STATUS_LINE.
 APPEND STATUS_LINE TO STATUS_LIST.
 ENDDO.
ENDMETHOD.
The public instance method CREATE_TEAM can be called by any user of the class containing a reference variable with a reference to an instance of the class. It is used to create instances of the class C_BIKER, using the private reference variable BIKER in the class C_TEAM. You must pass both input parameters for the instance constructor of class C_BIKER in the CREATE OBJECT statement. The references to the newly-created instances are inserted into the private internal table BIKER_TAB. After the method has been executed, each line of the internal table contains a reference to an instance of the class C_BIKER. These references are only visible within the class C_TEAM. External users cannot address the objects of class C_BIKER.
CREATE_TEAM also calls the method STATUS_LINE for each newly-created object, and uses the work area STATUS_LINE to append its output parameter LINE to the private internal table STATUS_LIST.
SELECTION
METHOD SELECTION.
 CLEAR BIKER_SELECTION.
 DO.
 READ LINE SY-INDEX.
 IF SY-SUBRC <> 0. EXIT. ENDIF.
 IF SY-LISEL+0(1) = 'X'.
 READ TABLE BIKER_TAB INTO BIKER INDEX SY-INDEX.
 APPEND BIKER TO BIKER_SELECTION.
 ENDIF.
 ENDDO.
 CALL METHOD WRITE_LIST.
ENDMETHOD.
The public instance method SELECTION can be called by any user of the class containing a reference variable with a reference to an instance of the class. It selects all of the lines in the current list in which the checkbox in the first column is selected. For these lines, the system copies the corresponding reference variables from the table BIKER_TAB into an additional private internal table BIKER_SELECTION. SELECTION then calls the private method WRITE_LIST, which displays the list.
EXECUTION
METHOD EXECUTION.
 CHECK NOT BIKER_SELECTION IS INITIAL.
 LOOP AT BIKER_SELECTION INTO BIKER.
 CALL METHOD BIKER->SELECT_ACTION.
 CALL METHOD BIKER->STATUS_LINE IMPORTING LINE = STATUS_LINE.
 MODIFY TABLE STATUS_LIST FROM STATUS_LINE.
 ENDLOOP.
 CALL METHOD WRITE_LIST.
ENDMETHOD.
The public instance method EXECUTION can be called by any user of the class containing a reference variable with a reference to an instance of the class. The method calls the two methods SELECT_ACTION and STATUS_LINE for each instance of the class C_BIKER for which there is a reference in the table BIKER_SELECTION. The line of the table STATUS_LIST with the same key as the component ID in the work area STATUS_LINE is overwritten and displayed by the private method WRITE_LIST.
WRITE_LIST
METHOD WRITE_LIST.
 SET TITLEBAR 'TIT'.
 SY-LSIND = 0.
 SKIP TO LINE 1.
 POSITION 1.
 LOOP AT STATUS_LIST INTO STATUS_LINE.
 WRITE: / STATUS_LINE-FLAG AS CHECKBOX,
 STATUS_LINE-TEXT1,
 STATUS_LINE-ID,
 STATUS_LINE-TEXT2,
 STATUS_LINE-TEXT3,
 STATUS_LINE-GEAR,
 STATUS_LINE-TEXT4,
 STATUS_LINE-SPEED.
 ENDLOOP.
ENDMETHOD.
The private instance method WRITE_LIST can only be called from the methods of the class C_TEAM. It is used to display the private internal table STATUS_LIST on the basic list (SY-LSIND = 0) of the program.
Methods of Class C_BIKER
The following methods are implemented in the section
CLASS C_BIKER IMPLEMENTATION.
ENDCLASS.
CONSTRUCTOR
METHOD CONSTRUCTOR.
 COUNTER = COUNTER + 1.
 ID = COUNTER - MEMBERS * ( TEAM_ID - 1).
 CREATE OBJECT BIKE.
ENDMETHOD.
The instance constructor is executed directly after each instance of the class C_BIKER is created. It is used to count the number of instance of C_BIKER in the static attribute COUNTER, and assigns the corresponding number to the instance attribute ID of each instance of the class. The constructor has two input parameters - TEAM_ID and MEMBERS - which you must pass in the CREATE OBJECT statement when you create an instance of C_BIKER.
The instance constructor also creates an instance of the class C_BICYCLE for each new instance of the class C_BIKER. The reference in the private reference variable BIKE of each instance of C_BIKER points to a corresponding instance of the class C_BICYCLE. No external user can address these instances of the class C_BICYCLE.
SELECT_ACTION
METHOD SELECT_ACTION.
 DATA ACTIVITY TYPE I.
 TIT2 = 'Select action for BIKE'.
 TIT2+24(3) = ID.
 CALL SELECTION-SCREEN 200 STARTING AT 5 15.
 CHECK NOT SY-SUBRC GT 0.
 IF GEARUP = 'X' OR GEARDOWN = 'X'.
 IF GEARUP = 'X'.
 ACTIVITY = 1.
 ELSEIF GEARDOWN = 'X'.
 ACTIVITY = -1.
 ENDIF.
 ELSEIF DRIVE = 'X'.
 ACTIVITY = 2.
 ELSEIF STOP = 'X'.
 ACTIVITY = 3.
 ENDIF.
 CALL METHOD BIKER_ACTION( ACTIVITY).
ENDMETHOD.
The public instance method SELECT_ACTION can be called by any user of the class containing a reference variable with a reference to an instance of the class. The method calls the selection screen 200 and analyzes the user input. After this, it calls the private method BIKER_ACTION of the same class. The method call uses the shortened form to pass the actual parameter ACTIVITY to the formal parameter ACTION.
BIKER_ACTION
METHOD BIKER_ACTION.
 CASE ACTION.
 WHEN -1 OR 1.
 CALL METHOD BIKE->CHANGE_GEAR
 EXPORTING CHANGE = ACTION
 RECEIVING GEAR = GEAR_STATUS
 EXCEPTIONS GEAR_MAX = 1
 GEAR_MIN = 2.
 CASE SY-SUBRC.
 WHEN 1.
 MESSAGE I315(AT) WITH 'BIKE' ID
 ' is already at maximal gear!'.
 WHEN 2.
 MESSAGE I315(AT) WITH 'BIKE' ID
 ' is already at minimal gear!'.
 ENDCASE.
 WHEN 2.
 CALL METHOD BIKE->DRIVE IMPORTING VELOCITY = SPEED_STATUS.
 WHEN 3.
 CALL METHOD BIKE->STOP IMPORTING VELOCITY = SPEED_STATUS.
 ENDCASE.
ENDMETHOD.
The private instance method BIKER_ACTION can only be called from the methods of the class C_BIKER. The method calls other methods in the instance of the class C_BICYCLE to which the reference in the reference variable BIKE is pointing, depending on the value in the input parameter ACTION.
STATUS_LINE
METHOD STATUS_LINE.
 LINE-FLAG = SPACE.
 LINE-TEXT1 = 'Biker'.
 LINE-ID = ID.
 LINE-TEXT2 = 'Status:'.
 LINE-TEXT3 = 'Gear = '.
 LINE-GEAR = GEAR_STATUS.
 LINE-TEXT4 = 'Speed = '.
 LINE-SPEED = SPEED_STATUS.
ENDMETHOD.
The public instance method STATUS_LINE can be called by any user of the class containing a reference variable with a reference to an instance of the class. It fills the structured output parameter LINE with the current attribute values of the corresponding instance.
Methods of Class C_BICYCLE
The following methods are implemented in the section
CLASS C_BICYCLE IMPLEMENTATION.
ENDCLASS.
DRIVE
METHOD DRIVE.
 SPEED = SPEED + GEAR * 10.
 VELOCITY = SPEED.
ENDMETHOD.
The public instance method DRIVE can be called by any user of the class containing a reference variable with a reference to an instance of the class. The method changes the value of the private attribute SPEED and passes it to the caller using the output parameter VELOCITY.
STOP
METHOD STOP.
 SPEED = 0.
 VELOCITY = SPEED.
ENDMETHOD.
The public instance method STOP can be called by any user of the class containing a reference variable with a reference to an instance of the class. The method changes the value of the private attribute SPEED and passes it to the caller using the output parameter VELOCITY.
CHANGE_GEAR
METHOD CHANGE_GEAR.
 GEAR = ME->GEAR.
 GEAR = GEAR + CHANGE.
 IF GEAR GT MAX_GEAR.
 GEAR = MAX_GEAR.
 RAISE GEAR_MAX.
 ELSEIF GEAR LT MIN_GEAR.
 GEAR = MIN_GEAR.
 RAISE GEAR_MIN.
 ENDIF.
 ME->GEAR = GEAR.
ENDMETHOD.
The public instance method CHANGE_GEAR can be called by any user of the class containing a reference variable with a reference to an instance of the class. The method changes the value of the private attribute GEAR. Since the formal parameter with the same name obscures the attribute in the method, the attribute has to be addressed using the self-reference ME->GEAR.
Using the Classes in a Program
The following program shows how the above classes can be used in a program. The declarations of the selection screens and local classes, and the implementations of the methods must also be a part of the program.
REPORT OO_METHODS_DEMO NO STANDARD PAGE HEADING.
Declarations and Implementations
Global Program Data
TYPES TEAM TYPE REF TO C_TEAM.
DATA: TEAM_BLUE TYPE TEAM,
 TEAM_GREEN TYPE TEAM,
 TEAM_RED TYPE TEAM.
DATA COLOR(5).
Program events
START-OF-SELECTION.
CREATE OBJECT: TEAM_BLUE,
 TEAM_GREEN,
 TEAM_RED.
 CALL METHOD: TEAM_BLUE->CREATE_TEAM,
 TEAM_GREEN->CREATE_TEAM,
 TEAM_RED->CREATE_TEAM.
SET PF-STATUS 'TEAMLIST'.
WRITE ' Select a team! ' COLOR = 2.
AT USER-COMMAND.
CASE SY-UCOMM.
 WHEN 'TEAM_BLUE'.
 COLOR = 'BLUE '.
 FORMAT COLOR = 1 INTENSIFIED ON INVERSE ON.
 CALL METHOD TEAM_BLUE->SELECTION.
 WHEN 'TEAM_GREEN'.
 COLOR = 'GREEN'.
 FORMAT COLOR = 5 INTENSIFIED ON INVERSE ON.
 CALL METHOD TEAM_GREEN->SELECTION.
 WHEN 'TEAM_RED'.
 COLOR = 'RED '.
 FORMAT COLOR = 6 INTENSIFIED ON INVERSE ON.
 CALL METHOD TEAM_RED->SELECTION.
 WHEN 'EXECUTION'.
 CASE COLOR.
 WHEN 'BLUE '.
 FORMAT COLOR = 1 INTENSIFIED ON INVERSE ON.
 CALL METHOD TEAM_BLUE->SELECTION.
 CALL METHOD TEAM_BLUE->EXECUTION.
 WHEN 'GREEN'.
 FORMAT COLOR = 5 INTENSIFIED ON INVERSE ON.
 CALL METHOD TEAM_GREEN->SELECTION.
 CALL METHOD TEAM_GREEN->EXECUTION.
 WHEN 'RED '.
 FORMAT COLOR = 6 INTENSIFIED ON INVERSE ON.
 CALL METHOD TEAM_RED->SELECTION.
 CALL METHOD TEAM_RED->EXECUTION.
 ENDCASE.
ENDCASE.
The program contains three class reference variables that refer to the class C_TEAM. It creates three objects from the class, to which the references in the reference variables then point. In each object, it calls the method CREATE_TEAM. The method CLASS_CONSTRUCTOR of class C_TEAM is executed before the first of the objects is created. The status TEAMLIST for the basic list allows the user to choose one of four functions:
When the user chooses a function, the event AT USER-COMMAND is triggered and public methods are called in one of the three instances of C_TEAM, depending on the users choice. The user can change the state of an object by selecting the corresponding line in the status list.

Abap Objects doubts.

Hi Experts.
Plz give me some details for the following questions.
1. what is abstract class.
2. give me some example program using inheritance.
3. Some sample programs using events.
4. Narrow casting & wide casting.. And describe the use of it.
5. How to declare internal table in ABAP OOPS.
6. What is the use of table type.?
7. What is instance.?
8. Explain friend class.
Thank in advance.
Points will be given for the answers.
regards,
J.Joe

HI
1. what is abstract class.
Abstract classes are normally used as an incomplete blueprint for concrete (that is, non-abstract) subclasses, for example to define a uniform interface.
Classes with at least one abstract method are themselves abstract.
Static methods and constructors cannot be abstract.
You can specify the class of the instance to be created explicitly: CREATE OBJECT <RefToAbstractClass> TYPE <NonAbstractSubclassName>.
Abstarct classes themselves cant be instantiated ( althrough their subclasses can)
Reference to abstract classes can refer to instance of subclass
Abstract (instance) methods are difined in the class , but not implemented
They must be redefined in subclasses
CLASS LC1 DEFINAITION ABSTARCT
PUBLIC SECTION
METHODS ESTIMATE ABSTARCT IMPORTING
ENDCLASS.
2. give me some example program using inheritance.
The following simple example shows the principle of inheritance within ABAP Objects. It is based on the Simple Introduction to Classes. A new class counter_ten inherits from the existing class counter.
REPORT demo_inheritance.
CLASS counter DEFINITION.
PUBLIC SECTION.
 METHODS: set IMPORTING value(set_value) TYPE i,
 increment,
 get EXPORTING value(get_value) TYPE i.
 PROTECTED SECTION .
 DATA count TYPE i.
ENDCLASS.
CLASS counter IMPLEMENTATION.
METHOD set.
 count = set_value.
ENDMETHOD.
METHOD increment.
 ADD 1 TO count.
ENDMETHOD.
METHOD get.
 get_value = count.
ENDMETHOD.
ENDCLASS.
CLASS counter_ten DEFINITION INHERITING FROM counter.
PUBLIC SECTION.
 METHODS increment REDEFINITION .
 DATA count_ten.
ENDCLASS.
CLASS counter_ten IMPLEMENTATION.
METHOD increment.
 DATA modulo TYPE I.
 CALL METHOD super->increment .
 write / count.
 modulo = count mod 10.
 IF modulo = 0.
 count_ten = count_ten + 1.
 write count_ten.
 ENDIF.
ENDMETHOD.
ENDCLASS.
DATA: count TYPE REF TO counter,
 number TYPE i VALUE 5.
START-OF-SELECTION.
 CREATE OBJECT count TYPE counter_ten .
CALL METHOD count->set EXPORTING set_value = number.
DO 20 TIMES.
 CALL METHOD count->increment.
ENDDO.
The class COUNTER_TEN is derived from COUNTER. It redefines the method INCREMENT. To do this, you must change the visibility of the COUNT attribute from PRIVATE to PROTECTED. The redefined method calls the obscured method of the superclass using the pseudoreference SUPER->. The redefined method is a specialization of the inherited method.
The example instantiates the subclass. The reference variable pointing to it has the type of the superclass. When the INCREMENT method is called using the superclass reference, the system executes the redefined method from the subclass.
3. Some sample programs using events.
Events in ABAP Objects - Example
The following example shows how to declare, call, and handle events in ABAP Objects.
Overview
This object works with the interactive list displayed below. Each user interaction triggers an event in ABAP Objects. The list and its data is created in the class C_LIST. There is a class STATUS for processing user actions. It triggers an event BUTTON_CLICKED in the AT USER-COMMAND event. The event is handled in the class C_LIST. It contains an object of the class C_SHIP or C_TRUCK for each line of the list. Both of these classes implement the interface I_VEHICLE. Whenever the speed of one of these objects changes, the event SPEED_CHANGE is triggered. The class C_LIST reacts to this and updates the list.
Constraints
The ABAP statements used for list processing are not yet fully available in ABAP Objects. However, to produce a simple test output, you can use the following statements:
WRITE [AT] /<offset>(<length>) <f>
ULINE
SKIP
NEW-LINE
Note: The behavior of formatting and interactive list functions in their current state are not guaranteed. Incompatible changes could occur in a future release.
Declarations
This example is implemented using local interfaces and classes. Below are the declarations of the interfaces and classes:
Interface and Class declarations
INTERFACE I_VEHICLE.
DATA MAX_SPEED TYPE I.
EVENTS SPEED_CHANGE EXPORTING VALUE(NEW_SPEED) TYPE I.
METHODS: DRIVE,
 STOP.
ENDINTERFACE.
CLASS C_SHIP DEFINITION.
PUBLIC SECTION.
METHODS CONSTRUCTOR.
INTERFACES I_VEHICLE.
PRIVATE SECTION.
ALIASES MAX FOR I_VEHICLE~MAX_SPEED.
DATA SHIP_SPEED TYPE I.
ENDCLASS.
CLASS C_TRUCK DEFINITION.
PUBLIC SECTION.
METHODS CONSTRUCTOR.
INTERFACES I_VEHICLE.
PRIVATE SECTION.
ALIASES MAX FOR I_VEHICLE~MAX_SPEED.
DATA TRUCK_SPEED TYPE I.
ENDCLASS.
CLASS STATUS DEFINITION.
PUBLIC SECTION.
 CLASS-EVENTS BUTTON_CLICKED EXPORTING VALUE(FCODE) LIKE SY-UCOMM.
CLASS-METHODS: CLASS_CONSTRUCTOR,
 USER_ACTION.
ENDCLASS.
CLASS C_LIST DEFINITION.
PUBLIC SECTION.
METHODS: FCODE_HANDLER FOR EVENT BUTTON_CLICKED OF STATUS
 IMPORTING FCODE,
 LIST_CHANGE FOR EVENT SPEED_CHANGE OF I_VEHICLE
 IMPORTING NEW_SPEED,
 LIST_OUTPUT.
PRIVATE SECTION.
DATA: ID TYPE I,
 REF_SHIP TYPE REF TO C_SHIP,
 REF_TRUCK TYPE REF TO C_TRUCK,
 BEGIN OF LINE,
 ID TYPE I,
 FLAG,
 IREF TYPE REF TO I_VEHICLE,
 SPEED TYPE I,
 END OF LINE,
 LIST LIKE SORTED TABLE OF LINE WITH UNIQUE KEY ID.
ENDCLASS.
The following events are declared in the example:
The instance event SPEED_CHANGE in the interface I_VEHICLE
The static event BUTTON_CLICKED in the class STATUS.
The class C_LIST contains event handler methods for both events.
Note that the class STATUS does not have any attributes, and therefore only works with static methods and events.
Implementations
Below are the implementations of the methods of the above classes:
Implementations
CLASS C_SHIP IMPLEMENTATION.
METHOD CONSTRUCTOR.
 MAX = 30.
ENDMETHOD.
METHOD I_VEHICLE~DRIVE.
 CHECK SHIP_SPEED < MAX.
 SHIP_SPEED = SHIP_SPEED + 10.
 RAISE EVENT I_VEHICLE~SPEED_CHANGE
 EXPORTING NEW_SPEED = SHIP_SPEED.
ENDMETHOD.
METHOD I_VEHICLE~STOP.
 CHECK SHIP_SPEED > 0.
 SHIP_SPEED = 0.
 RAISE EVENT I_VEHICLE~SPEED_CHANGE
 EXPORTING NEW_SPEED = SHIP_SPEED.
ENDMETHOD.
ENDCLASS.
CLASS C_TRUCK IMPLEMENTATION.
METHOD CONSTRUCTOR.
 MAX = 150.
ENDMETHOD.
METHOD I_VEHICLE~DRIVE.
 CHECK TRUCK_SPEED < MAX.
 TRUCK_SPEED = TRUCK_SPEED + 50.
 RAISE EVENT I_VEHICLE~SPEED_CHANGE
 EXPORTING NEW_SPEED = TRUCK_SPEED.
ENDMETHOD.
METHOD I_VEHICLE~STOP.
 CHECK TRUCK_SPEED > 0.
 TRUCK_SPEED = 0.
 RAISE EVENT I_VEHICLE~SPEED_CHANGE
 EXPORTING NEW_SPEED = TRUCK_SPEED.
ENDMETHOD.
ENDCLASS.
CLASS STATUS IMPLEMENTATION.
METHOD CLASS_CONSTRUCTOR.
 SET PF-STATUS 'VEHICLE'.
 WRITE 'Click a button!'.
ENDMETHOD.
METHOD USER_ACTION.
 RAISE EVENT BUTTON_CLICKED EXPORTING FCODE = SY-UCOMM.
ENDMETHOD.
ENDCLASS.
CLASS C_LIST IMPLEMENTATION.
METHOD FCODE_HANDLER .
 CLEAR LINE.
 CASE FCODE.
 WHEN 'CREA_SHIP'.
 ID = ID + 1.
 CREATE OBJECT REF_SHIP.
 LINE-ID = ID.
 LINE-FLAG = 'C'.
 LINE-IREF = REF_SHIP.
 APPEND LINE TO LIST.
 WHEN 'CREA_TRUCK'.
 ID = ID + 1.
 CREATE OBJECT REF_TRUCK.
 LINE-ID = ID.
 LINE-FLAG = 'T'.
 LINE-IREF = REF_TRUCK.
 APPEND LINE TO LIST.
 WHEN 'DRIVE'.
 CHECK SY-LILLI > 0.
 READ TABLE LIST INDEX SY-LILLI INTO LINE.
 CALL METHOD LINE-IREF->DRIVE.
 WHEN 'STOP'.
 LOOP AT LIST INTO LINE.
 CALL METHOD LINE-IREF->STOP.
 ENDLOOP.
 WHEN 'CANCEL'.
 LEAVE PROGRAM.
 ENDCASE.
 CALL METHOD LIST_OUTPUT.
ENDMETHOD.
METHOD LIST_CHANGE .
 LINE-SPEED = NEW_SPEED.
 MODIFY TABLE LIST FROM LINE.
ENDMETHOD.
METHOD LIST_OUTPUT.
 SY-LSIND = 0.
 SET TITLEBAR 'TIT'.
 LOOP AT LIST INTO LINE.
 IF LINE-FLAG = 'C'.
 WRITE / ICON_WS_SHIP AS ICON.
 ELSEIF LINE-FLAG = 'T'.
 WRITE / ICON_WS_TRUCK AS ICON.
 ENDIF.
 WRITE: 'Speed = ', LINE-SPEED.
 ENDLOOP.
ENDMETHOD.
ENDCLASS.
The static method USER_ACTION of the class STATUS triggers the static event BUTTON_CLICKED. The instance methods I_VEHICLEDRIVE and I_VEHICLESTOP trigger the instance event I_VEHICLE~SPEED_CHANGE in the classes C_SHIP and C_TRUCK.
Using the Classes in a Program
The following program uses the above classes:
REPORT OO_EVENTS_DEMO NO STANDARD PAGE HEADING.
Global data of program
DATA LIST TYPE REF TO C_LIST.
Program events
START-OF-SELECTION.
CREATE OBJECT LIST.
SET HANDLER: LIST->FCODE_HANDLER,
 LIST->LIST_CHANGE FOR ALL INSTANCES.
AT USER-COMMAND.
CALL METHOD STATUS=>USER_ACTION.
The program creates an object of the class C_LIST and registers the event handler method FCODE_HANDLER of the object for the class event BUTTON_CLICKED, and the event handler method LIST_CHANGE for the event SPEED_CHANGE of all instances that implement the interface I_VEHICLE.
4. Narrow casting & wide casting.. And describe the use of it.
Narrowing Cast
The assignment of a subclass instance to a reference variable of the type "reference to superclass" is described as a narrowing cast, because you are switching from a more detailed view to a one with less detail.
Description up-cast is also used.
use
A user who is not interested in the finer points of cars, trucks, and busses (but only, for example, in the fuel consumption and tank gauge) does not need to know about them. This user only wants and needs to work with (references to) the lcl_vehicle class. However, in order to allow the user to work with cars, busses, or trucks, you generally need a narrowing cast.
Widening cast
The widening cast logically represents the opposite of the narrowing cast. The widening cast cannot be checked statically, only at runtime. The Cast Operator ?= (or the equivalent MOVE ... ?TO ) must be used to make this visible.
It changes from a less detailed view to one with more detail.
use
The client, the car rental company wants to execute a function for specific vehicles form the list (vehicle_list). For example, the client wants to ascertain the truck with the largest cargo capacity. However, not all vehicles are in the trucks list, it also includes references to cars and busses.
5. How to declare internal table in ABAP OOPS.
BEGIN OF LINE,
 ID TYPE I,
 FLAG,
 IREF TYPE REF TO I_VEHICLE,
 SPEED TYPE I,
 END OF LINE,
6. What is the use of table type.?
Please check the SAP help , as all these things are provided in detail in it .
In case you find it difficult to find it or search for it here is the link
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
7. What is instance.?
Instance methods are called using CALL METHOD <reference>-><instance_method>.
Static methods (also referred to as class methods) are called using CALL METHOD <classname>=><class_method>.
If you are calling a static method from within the class, you can omit the class name.
You access instance attributes using <instance>-><instance_attribute>
8. Explain friend class.
In rare cases, classes have to work together so closely that they need access to their protected and private components. To avoid making these components available to all users, there is the concept of friendship between classes.
To do this you use the FRIENDS additions to the CLASS statement, in which all classes and interfaces that are to be provided friendship are listed
In principle, providing friendship is one-sided: A class providing friendship is not automatically a friend of its friends. If a class providing friendship wants to access the non-public components of a friend, this friend has to explicitly provide friendship to it.
Classes that inherit from friends and interfaces that contain a friend as a component interface also become friends. However, providing friendship, unlike the attribute of being a friend, is not inherited. A friend of a superclass is therefore not automatically a friend of its subclasses.
Reward if usefull

How to use selection buttons in an ALV created without abap objects?

Hi, I use an alv created without ABAP Objects to show some information. Can I introduce inside the alv, the top buttons to select all rows / none row? And the second question, how may I introduce lateral buttons in the ALV to select indidividual rows?
Thanks!

HI
i think you use REUSE_ALV_LIST_DISPLAY or REUSE_ALV_GRID_DISPLAY FMs.
Try to calling the function in this way
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
      EXPORTING
*      I_INTERFACE_CHECK              = ' '
*      I_BYPASSING_BUFFER             =
*      I_BUFFER_ACTIVE                = ' '
       i_callback_program             = 'YOURREPORT'
       i_callback_pf_status_set       = 'SET_PF_STATUS'
       i_callback_user_command        = 'USER_COMAND'
*      I_STRUCTURE_NAME               =
       is_layout                      = ls_layout
       it_fieldcat                    = fieldcat
*      IT_EXCLUDING                   =
*      IT_SPECIAL_GROUPS              =
*      IT_SORT                        =
*      IT_FILTER                      =
*      IS_SEL_HIDE                    =
*      I_DEFAULT                      = 'X'
       i_save                         = 'A'
      is_variant                     = gt_variant
      it_events                      = event_tab
*      IT_EVENT_EXIT                  =
*      IS_PRINT                       =
*      IS_REPREP_ID                   =
*      I_SCREEN_START_COLUMN          = 0
*      I_SCREEN_START_LINE            = 0
*      I_SCREEN_END_COLUMN            = 0
*      I_SCREEN_END_LINE              = 0
*    IMPORTING
*      E_EXIT_CAUSED_BY_CALLER        =
*      ES_EXIT_CAUSED_BY_USER         =
       TABLES
         t_outtab                     = tb_output
      EXCEPTIONS
        program_error                  = 1
        OTHERS                         = 2.
ENDFORM.                    " LISTA
where
'SET_PF_STATUS'
'USER_COMAND'
are two form like this.
FORM set_pf_status USING rt_extab TYPE slis_t_extab.
SET PF-STATUS 'ZSTANDARD'. " EXCLUDING rt_extab.
ENDFORM.                               " SET_PF_STATUS
FORM user_comand USING r_ucomm     LIKE sy-ucomm
                         rs_selfield TYPE slis_selfield.
CASE r_ucomm.
    WHEN '&CPR'.
    WHEN 'YOUR CODE FUNCTION'
endcase.
I hope it can help you.
Bye
enzo

ABAP objects and AIF

hi all
I have a question. I have made several ABAP objects which i am using in my programs. But now i have to build a AIF with those objects, but i understand that AIF in SAP cannot retrieve objects immediately.
Also i saw that if i want to create all kinds of internal tables and structures, it would cost me a lot of work.
Is there a solution where i can use those objects with AIF?
kind regards,
Anton Pierhagen

Hi Otto
That was my idea. Because ABAP OO is the new type of programming in ABAP .
So i hoped i could transfer objects from the ABAP objects to variables in the PDF layout.
But the only way to do this ( whiich i only see it ) is to translate the variables of the objects to values in tables and structures.
That's not a very useful manner i would like to program my application. Because first i put everything in objects and afterwards i set everything back in tables and structures.. I had better set everything in custom structures and tables immediately.
So i am going to find another way. Maybe i set all the data in an HTML page and transfer this via mail and so on.
But thanks for your reply!
Kind regards
Anton Pierhagen

Simple Examples on ABAP Objects without using include or function modules

Hi,
I am new to ABAP. I need simple example codes on ABAP Objects. It should not have Includes or Function Modules. Just simple codes, using local & global classes, interfaces etc. I searched the forum and even <<the site that shall not be mentioned>>, but did not find a solution. Kindly help please.
Regards,
Smruthi.
Edited by: Matt on Mar 1, 2009 1:20 PM - forbidden site reference removed

Hello Smruthi
If you go to the Forum Search and choose the forum ABAP Objects then serach for ZUS_SDN and you will find many of my simple sample reports.
These reports usually do not contain any includes but they may call function modules which makes perfectly sense. For example, if you are still doing a direct table SELECT instead of using an available BAPI (or class) to get a business object then this is a clear sign of poor (=non-ABAP-OO) programming.
Regards
Uwe

BPS Flat file load ABAP objects migration error.

Hello
We are trying to load a flat file via the SAP-GUI and BPS and everything works well in DEV based on the HOw-TO guide. When trying to move the ABAP objects to QA, we get a migration error on the type /1sem/_yth_data_260ZBYAPEPL. Of course the 260ZBYAPEP is relevant to our configuration and in QA we do have the equivalent structure /1sem/_yth_data_614ZBYAPEPL.
How come the type in DEV does not translate to the equivalent type in QA just like any objects we transport to QA?
Thank you all.
YB.

Dear YB,
the element /1sem/_yth_data_260ZBYAPEPL has to be changed according to the QA manually only. Sytem can't change the clent no. automaticaaly when u transport to the QA.
so in /1sem/_yth_data_260ZBYAPEPL replce 260 with ur QA Client no.
Narendra Reddy

Design Pattern and ABAP Objects

Hello Friends,
I would like to know, if ABAP Objects can be used to do pattern oriented programming ?
For example GANG of four has provided almost more then 30 design pattern ( MVC, singelton, Obserable, FACADE,,,etc) can we implement patterns using ABAP ??
Many thanks
Haider Syed

Hi,
Take a look at the following site:
http://patternshare.org/
It has all the basic patterns from the GOF and a lot more. I can recommend the ones from Martin Fowler but be sure you start with the ones from the GOF.
All patterns are described by using UML so it's very easy to translate them into ABAP OO code.
Regarding your other question. For the observer pattern I used an interface which the SAP had already created if_cm_observer and created my own abstract observable class. The observable class is nearly a 100% copy of the java.util. one
regards
Thomas

ALV Tree using ABAP Objects

Can anyone tell me how to Copy a node on an ALV Tree using context menu ?

Hello Vidya
The sample report ZUS_SDN_ALVTREE_CTXMENU demonstrates how to copy nodes on an ALV tree.
Before showing the entire coding I would like to point out a few crucial parts of the coding:
(1) Defintion of OUTTAB list
TYPES: BEGIN OF ty_s_outtab.
INCLUDE TYPE vbak.
TYPES: nkey TYPE lvc_nkey.
TYPES: ntype TYPE lvc_value. " 'VKORG' / 'VTWEG' / 'SPART' / leaf
TYPES: END OF ty_s_outtab.
TYPES: ty_t_outtab TYPE STANDARD TABLE OF ty_s_outtab
 WITH DEFAULT KEY.
The OUTTAB list contains two additional fields holding the tree key (LVC_NKEY) and the node type.
(2) The main logic of the report is implemented in event handler method handle_node_ctxmenu_sel.
 WHEN 'COPY_SUBTREE'.
 CALL METHOD go_alvtree->get_subtree
 EXPORTING
 i_node_key = node_key
 IMPORTING
 et_subtree_nodes = lt_subtree.
 CALL METHOD go_alvtree->get_parent
 EXPORTING
 i_node_key = node_key
 IMPORTING
 e_parent_node_key = ld_parent_key.
 LOOP AT lt_subtree INTO ld_node_key.
 READ TABLE gt_outtab INTO ls_outtab
 WITH KEY nkey = ld_node_key.
 APPEND ls_outtab TO lt_outtab.
 ENDLOOP.
 READ TABLE lt_outtab INTO ls_outtab INDEX 1.
 ld_ntype = ls_outtab-ntype.
 DELETE lt_outtab WHERE ( vbeln IS INITIAL ). " hierarchy nodes
 CASE ld_ntype.
 WHEN 'VKORG'.
 ld_top_key = ld_parent_key.
 WHEN 'VTWEG'.
 ld_vkorg_key = ld_parent_key.
 WHEN 'SPART'.
 ld_vtweg_key = ld_parent_key.
 WHEN 'LEAF'.
 ld_spart_key = ld_parent_key.
 ENDCASE.
" Note: similar logic like in routine CREATE_HIERARCHY
 SORT lt_outtab BY vkorg vtweg spart kunnr audat.
 LOOP AT lt_outtab INTO ls_outtab.
*& Report ZUS_SDN_ALVTREE_CTXMENU
*& Based on: BCALV_TREE_03
REPORT zus_sdn_alvtree_ctxmenu.
TYPES: BEGIN OF ty_s_outtab.
INCLUDE TYPE vbak.
TYPES: nkey TYPE lvc_nkey.
TYPES: ntype TYPE lvc_value. " 'VKORG' / 'VTWEG' / 'SPART' / leaf
TYPES: END OF ty_s_outtab.
TYPES: ty_t_outtab TYPE STANDARD TABLE OF ty_s_outtab
 WITH DEFAULT KEY.
DATA:
gd_repid TYPE syst-repid,
gd_okcode TYPE ui_func,
go_docking TYPE REF TO cl_gui_docking_container,
go_alvtree TYPE REF TO cl_gui_alv_tree.
DATA:
gt_outtab TYPE ty_t_outtab, " Sales Document
gt_fcat TYPE lvc_t_fcat.
* CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
* §2. Define an event handler method to build up a context menu
* (postfix of event name: _CONTEXT_MENU_REQUEST).
* This event is fired each time the user klick with the right
* mouse button on a node.
 CLASS-METHODS:
 handle_node_ctxmenu_req
 FOR EVENT node_context_menu_request OF cl_gui_alv_tree
 IMPORTING
 node_key
 menu,
* §3. Define an event handler method to respond to a function code
* triggered by your menu (postfix: _CONTEXT_MENU_SELECTED).
* This event is fired when the user selects an entry of the
* build up context menu.
 handle_node_ctxmenu_sel
 FOR EVENT node_context_menu_selected OF cl_gui_alv_tree
 IMPORTING
 node_key
 fcode
 sender.
* 'sender' is an implicit event parameter that is provided by
* ABAP Objects runtime system. It contains a reference to the
* object that fired the event. You may directly use it to
* call methods of this instance.
ENDCLASS. "lcl_eventhandler DEFINITION
* CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
* §4. Implement your event handler methods.
METHOD handle_node_ctxmenu_req.
* Event parameter 'menu' holds a reference to the standard context
* menu of ALV Tree (functions 'Expand'/'Collapse' on nodes).
* You may either append your own functions (separated by a line)
* or clear the menu if you do not want to allow standard functions.
* In this case the standard menu is cleared.
 CALL METHOD menu->clear.
* The next line defines one line of the context menu.
 CALL METHOD menu->add_function
 EXPORTING
 fcode = 'DEL_SUBTREE'
 text = 'Delete Subtree'(901). "Delete Subtree
 CALL METHOD menu->add_function
 EXPORTING
 fcode = 'COPY_SUBTREE'
 text = 'Copy Subtree'(902). "Copy Subtree
ENDMETHOD. "handle_node_ctxmenu_req
METHOD handle_node_ctxmenu_sel.
* At this point of execution, the user selected a menu entry of the
* menu build up in event handler method handle_node_cm_req.
* Query your own function codes and react accordingly.
 DATA:
 l_rc TYPE c,
 ld_ntype TYPE lvc_value,
 ld_parent_key TYPE lvc_nkey,
 ld_node_key TYPE lvc_nkey,
 lt_subtree TYPE lvc_t_nkey,
 ls_outtab TYPE ty_s_outtab,
 ls_last TYPE ty_s_outtab,
 lt_outtab TYPE ty_t_outtab.
 DATA:
 ld_vkorg_key TYPE lvc_nkey,
 ld_vtweg_key TYPE lvc_nkey,
 ld_spart_key TYPE lvc_nkey,
 ld_last_key TYPE lvc_nkey,
 ld_top_key TYPE lvc_nkey.
 CASE fcode.
 WHEN 'DEL_SUBTREE'.
 CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
 EXPORTING
 textline1 = 'Do you really want to delete'(902)
 textline2 = 'this node and all its subnodes?'(903)
 titel = 'Confirmation'(904)
 cancel_display = ' '
 IMPORTING
 answer = l_rc.
 IF l_rc EQ 'J'.
 CALL METHOD sender->delete_subtree
 EXPORTING
 i_node_key = node_key.
* Do not forget to refresh the display when you change the contents
* of your list.
 CALL METHOD sender->frontend_update.
 ENDIF.
 WHEN 'COPY_SUBTREE'.
 CALL METHOD go_alvtree->get_subtree
 EXPORTING
 i_node_key = node_key
 IMPORTING
 et_subtree_nodes = lt_subtree.
 CALL METHOD go_alvtree->get_parent
 EXPORTING
 i_node_key = node_key
 IMPORTING
 e_parent_node_key = ld_parent_key.
 LOOP AT lt_subtree INTO ld_node_key.
 READ TABLE gt_outtab INTO ls_outtab
 WITH KEY nkey = ld_node_key.
 APPEND ls_outtab TO lt_outtab.
 ENDLOOP.
 READ TABLE lt_outtab INTO ls_outtab INDEX 1.
 ld_ntype = ls_outtab-ntype.
 DELETE lt_outtab WHERE ( vbeln IS INITIAL ). " hierarchy nodes
 CASE ld_ntype.
 WHEN 'VKORG'.
 ld_top_key = ld_parent_key.
 WHEN 'VTWEG'.
 ld_vkorg_key = ld_parent_key.
 WHEN 'SPART'.
 ld_vtweg_key = ld_parent_key.
 WHEN 'LEAF'.
 ld_spart_key = ld_parent_key.
 ENDCASE.
 SORT lt_outtab BY vkorg vtweg spart kunnr audat.
 LOOP AT lt_outtab INTO ls_outtab.
 IF ( ld_ntype = 'VKORG' ).
 " new sales organisation
 IF ( ls_outtab-vkorg = ls_last-vkorg ).
 ELSE.
 PERFORM add_sales_org
 USING
 ls_outtab
 ld_top_key
 CHANGING
 ld_vkorg_key.
 ls_outtab-nkey = ld_vkorg_key.
 ls_outtab-ntype = 'VKORG'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ENDIF.
 ENDIF.
 IF ( ld_ntype = 'VKORG' OR
 ld_ntype = 'VTWEG' ).
 " new distribution channel
 IF ( ls_outtab-vkorg = ls_last-vkorg AND
 ls_outtab-vtweg = ls_last-vtweg ).
 ELSE.
 PERFORM add_distrib_chan
 USING
 ls_outtab
 ld_vkorg_key
 CHANGING
 ld_vtweg_key.
 ls_outtab-nkey = ld_vtweg_key.
 ls_outtab-ntype = 'VTWEG'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ENDIF.
 ENDIF.
 IF ( ld_ntype = 'VKORG' OR
 ld_ntype = 'VTWEG' OR
 ld_ntype = 'SPART' ).
 " new channel
 IF ( ls_outtab-vkorg = ls_last-vkorg AND
 ls_outtab-vtweg = ls_last-vtweg AND
 ls_outtab-spart = ls_last-spart ).
 ELSE.
 PERFORM add_division
 USING
 ls_outtab
 ld_vtweg_key
 CHANGING
 ld_spart_key.
 ls_outtab-nkey = ld_spart_key.
 ls_outtab-ntype = 'SPART'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ENDIF.
 ENDIF.
* Leaf:
 PERFORM add_complete_line
 USING
 ls_outtab
 ld_spart_key
 CHANGING
 ld_last_key.
 ls_outtab-nkey = ld_last_key.
 ls_outtab-ntype = 'LEAF'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ls_last = ls_outtab.
 ENDLOOP.
 CALL METHOD cl_gui_cfw=>set_new_ok_code
 EXPORTING
 new_code = 'REFRESH_TREE'
* IMPORTING
* RC =
 ENDCASE.
ENDMETHOD. "handle_node_ctxmenu_sel
ENDCLASS. "lcl_eventhandler IMPLEMENTATION
START-OF-SELECTION.
PERFORM init_controls.
* Link the docking container to the target dynpro
gd_repid = syst-repid.
CALL METHOD go_docking->link
 EXPORTING
 repid = gd_repid
 dynnr = '0100'
* CONTAINER =
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL SCREEN '0100'.
* NOTE: no screen elements, ok_code -> gd_okcode
** PROCESS BEFORE OUTPUT.
** MODULE STATUS_0100.
** PROCESS AFTER INPUT.
** MODULE USER_COMMAND_0100.
END-OF-SELECTION.
*& Module STATUS_0100 OUTPUT
* text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
* text
MODULE user_command_0100 INPUT.
TRANSLATE gd_okcode TO UPPER CASE. " facilitate manual entries
CASE gd_okcode.
 WHEN 'BACK' OR
 'EXIT' OR
 'CANC'.
 SET SCREEN 0. LEAVE SCREEN.
when 'REFRESH_TREE'.
 CALL METHOD go_alvtree->update_calculations
* EXPORTING
* NO_FRONTEND_UPDATE =
 WHEN OTHERS.
ENDCASE.
CLEAR: gd_okcode.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Form INIT_CONTROLS
* text
* --> p1 text
* <-- p2 text
FORM init_controls .
DATA:
 ls_hierarchy_header TYPE treev_hhdr.
* Create docking container
CREATE OBJECT go_docking
 EXPORTING
 parent = cl_gui_container=>screen0
 ratio = 90
 EXCEPTIONS
 OTHERS = 6.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL METHOD go_docking->set_extension
 EXPORTING
 extension = 99999 " full-size screen
 EXCEPTIONS
 cntl_error = 1
 OTHERS = 2.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* create tree control
CREATE OBJECT go_alvtree
 EXPORTING
 parent = go_docking
 node_selection_mode = cl_gui_column_tree=>node_sel_mode_single
 item_selection = ' '
 no_html_header = 'X'
 no_toolbar = ''
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 create_error = 3
 lifetime_error = 4
 illegal_node_selection_mode = 5
 failed = 6
 illegal_column_name = 7.
IF sy-subrc <> 0.
 MESSAGE x208(00) WITH 'ERROR'. "#EC NOTEXT
ENDIF.
PERFORM build_hierarchy_header CHANGING ls_hierarchy_header.
* Hide columns and sum up values initially using the fieldcatalog
PERFORM build_fieldcatalog.
* IMPORTANT: Table 'gt_sflight' must be empty. Do not change this table
* (even after this method call). You can change data of your table
* by calling methods of CL_GUI_ALV_TREE.
* Furthermore, the output table 'gt_outtab' must be global and can
* only be used for one ALV Tree Control.
CALL METHOD go_alvtree->set_table_for_first_display
 EXPORTING
 is_hierarchy_header = ls_hierarchy_header
 CHANGING
 it_fieldcatalog = gt_fcat
 it_outtab = gt_outtab. "table must be empty !
PERFORM init_tree.
ENDFORM. " INIT_CONTROLS
*& Form INIT_TREE
* text
* --> p1 text
* <-- p2 text
FORM init_tree .
PERFORM create_hierarchy.
PERFORM register_events.
* Update calculations which were initially defined by field DO_SUM
* of the fieldcatalog. (see build_fieldcatalog).
CALL METHOD go_alvtree->update_calculations.
* Send data to frontend.
CALL METHOD go_alvtree->frontend_update.
ENDFORM. " INIT_TREE
*& Form build_hierarchy_header
* text
* <--P_LS_HIERARCHY_HEADER text
FORM build_hierarchy_header
 CHANGING
 cs_hierarchy_header TYPE treev_hhdr.
cs_hierarchy_header-heading =
 'SalesOrg/DistChannel/Division'(300).
cs_hierarchy_header-tooltip = 'Customer: Master Sales Data'(400).
cs_hierarchy_header-width = 45.
cs_hierarchy_header-width_pix = ''.
ENDFORM. " build_hierarchy_header
*& Form build_fieldcatalog
* text
* --> p1 text
* <-- p2 text
FORM build_fieldcatalog .
* define local data
DATA:
 ls_fcat TYPE lvc_s_fcat.
REFRESH: gt_fcat.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
 EXPORTING
* I_BUFFER_ACTIVE =
 i_structure_name = 'VBAK'
* I_CLIENT_NEVER_DISPLAY = 'X'
* I_BYPASSING_BUFFER =
* I_INTERNAL_TABNAME =
 CHANGING
 ct_fieldcat = gt_fcat
 EXCEPTIONS
 inconsistent_interface = 1
 program_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT gt_fcat INTO ls_fcat.
 CASE ls_fcat-fieldname.
 WHEN 'VBELN' OR
 'AUDAT' OR
 'AUART' OR
 'WAERK' OR
 'VKORG' OR
 'VTWEG' OR
 'SPART' OR
 'BSTNK' OR
 'KUNNR'.
 WHEN 'NETWR'.
 ls_fcat-do_sum = 'X'.
 ls_fcat-h_ftype = 'SUM'. " or: 'MAX' / 'AVG'
 WHEN OTHERS.
 ls_fcat-tech = 'X'.
 ENDCASE.
 MODIFY gt_fcat FROM ls_fcat INDEX syst-tabix.
ENDLOOP.
ENDFORM. " build_fieldcatalog
*& Form create_hierarchy
* text
* --> p1 text
* <-- p2 text
FORM create_hierarchy .
* define local data
DATA:
 ls_outtab TYPE ty_s_outtab,
 ls_last TYPE ty_s_outtab,
 lt_outtab TYPE ty_t_outtab.
DATA:
 ld_vkorg_key TYPE lvc_nkey,
 ld_vtweg_key TYPE lvc_nkey,
 ld_spart_key TYPE lvc_nkey,
 ld_last_key TYPE lvc_nkey,
 ld_top_key TYPE lvc_nkey.
" Select data
SELECT * FROM vbak INTO CORRESPONDING FIELDS OF TABLE lt_outtab
 UP TO 1550 ROWS.
" sort table according to conceived hierarchy
SORT lt_outtab BY vkorg vtweg spart kunnr audat.
* Define one top node. In this way it is possible to calculate
* values for the whole hierarchy.
CALL METHOD go_alvtree->add_node
 EXPORTING
 i_relat_node_key = ''
 i_relationship = cl_gui_column_tree=>relat_last_child
 i_node_text = 'Sales Documents'
 IMPORTING
 e_new_node_key = ld_top_key.
CLEAR: ls_outtab.
ls_outtab-nkey = ld_top_key.
ls_outtab-ntype = 'ROOT'.
MODIFY gt_outtab FROM ls_outtab INDEX 1
 TRANSPORTING nkey ntype.
LOOP AT lt_outtab INTO ls_outtab.
 " new sales organisation
 IF ( ls_outtab-vkorg = ls_last-vkorg ).
 ELSE.
 PERFORM add_sales_org
 USING
 ls_outtab
 ld_top_key
 CHANGING
 ld_vkorg_key.
 ls_outtab-nkey = ld_vkorg_key.
 ls_outtab-ntype = 'VKORG'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ENDIF.
 " new distribution channel
 IF ( ls_outtab-vkorg = ls_last-vkorg AND
 ls_outtab-vtweg = ls_last-vtweg ).
 ELSE.
 PERFORM add_distrib_chan
 USING
 ls_outtab
 ld_vkorg_key
 CHANGING
 ld_vtweg_key.
 ls_outtab-nkey = ld_vtweg_key.
 ls_outtab-ntype = 'VTWEG'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ENDIF.
 " new channel
 IF ( ls_outtab-vkorg = ls_last-vkorg AND
 ls_outtab-vtweg = ls_last-vtweg AND
 ls_outtab-spart = ls_last-spart ).
 ELSE.
 PERFORM add_division
 USING
 ls_outtab
 ld_vtweg_key
 CHANGING
 ld_spart_key.
 ls_outtab-nkey = ld_spart_key.
 ls_outtab-ntype = 'SPART'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ENDIF.
* Leaf:
 PERFORM add_complete_line
 USING
 ls_outtab
 ld_spart_key
 CHANGING
 ld_last_key.
 ls_outtab-nkey = ld_last_key.
 ls_outtab-ntype = 'LEAF'.
 DESCRIBE TABLE gt_outtab. " fill sy-tfill
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tfill
 TRANSPORTING nkey ntype.
 ls_last = ls_outtab.
ENDLOOP.
ENDFORM. " create_hierarchy
*& Form ADD_SALES_ORG
* text
* -->P_LS_OUTTAB text
* -->P_LD_TOP_KEY text
* <--P_LD_VKORG_KEY text
FORM add_sales_org
 USING
 value(us_outtab) TYPE ty_s_outtab
 value(ud_relat_key) TYPE lvc_nkey
 CHANGING
 cd_node_key TYPE lvc_nkey.
* define local data
DATA:
 ld_nodetext TYPE lvc_value,
 ls_outtab TYPE ty_s_outtab.
ld_nodetext = us_outtab-vkorg.
" add node
CALL METHOD go_alvtree->add_node
 EXPORTING
 i_relat_node_key = ud_relat_key
 i_relationship = cl_gui_column_tree=>relat_last_child
 i_node_text = ld_nodetext
 is_outtab_line = ls_outtab
 IMPORTING
 e_new_node_key = cd_node_key.
ENDFORM. " ADD_SALES_ORG
*& Form add_DISTRIB_CHAN
* text
* -->P_LS_OUTTAB text
* -->P_LD_VKORG_KEY text
* <--P_LD_VTWEG_KEY text
FORM add_distrib_chan
 USING
 value(us_outtab) TYPE ty_s_outtab
 value(ud_relat_key) TYPE lvc_nkey
 CHANGING
 cd_node_key TYPE lvc_nkey.
* define local data
DATA:
 ld_nodetext TYPE lvc_value,
 ls_outtab TYPE ty_s_outtab.
ld_nodetext = us_outtab-vtweg.
" add node
CALL METHOD go_alvtree->add_node
 EXPORTING
 i_relat_node_key = ud_relat_key
 i_relationship = cl_gui_column_tree=>relat_last_child
 i_node_text = ld_nodetext
 is_outtab_line = ls_outtab
 IMPORTING
 e_new_node_key = cd_node_key.
ENDFORM. " add_DISTRIB_CHAN
*& Form add_division
* text
* -->P_LS_OUTTAB text
* -->P_LD_VTWEG_KEY text
* <--P_LD_SPART_KEY text
FORM add_division
 USING
 value(us_outtab) TYPE ty_s_outtab
 value(ud_relat_key) TYPE lvc_nkey
 CHANGING
 cd_node_key TYPE lvc_nkey.
* define local data
DATA:
 ld_nodetext TYPE lvc_value,
 ls_outtab TYPE ty_s_outtab.
ld_nodetext = us_outtab-spart.
" add node
CALL METHOD go_alvtree->add_node
 EXPORTING
 i_relat_node_key = ud_relat_key
 i_relationship = cl_gui_column_tree=>relat_last_child
 i_node_text = ld_nodetext
 is_outtab_line = ls_outtab
 IMPORTING
 e_new_node_key = cd_node_key.
ENDFORM. " add_division
*& Form add_complete_line
* text
* -->P_LS_OUTTAB text
* -->P_LD_SPART_KEY text
* <--P_LD_LAST_KEY text
FORM add_complete_line
 USING
 value(us_outtab) TYPE ty_s_outtab
 value(ud_relat_key) TYPE lvc_nkey
 CHANGING
 cd_node_key TYPE lvc_nkey.
* define local data
DATA:
 ld_nodetext TYPE lvc_value,
 ls_outtab TYPE ty_s_outtab.
WRITE us_outtab-kunnr TO ld_nodetext+0 NO-ZERO.
WRITE us_outtab-audat TO ld_nodetext+20 DD/MM/YYYY.
CONDENSE ld_nodetext.
" add node
CALL METHOD go_alvtree->add_node
 EXPORTING
 i_relat_node_key = ud_relat_key
 i_relationship = cl_gui_column_tree=>relat_last_child
 i_node_text = ld_nodetext
 is_outtab_line = us_outtab " !!!
 IMPORTING
 e_new_node_key = cd_node_key.
ENDFORM. " add_complete_line
*& Form register_events
* text
* --> p1 text
* <-- p2 text
FORM register_events .
DATA:
 lt_events TYPE cntl_simple_events,
 ls_event TYPE cntl_simple_event.
* The following four tree events registers ALV Tree in the constructor
* method itself.
* - cl_gui_column_tree=>eventid_expand_no_children
* (needed to load data to frontend when a user expands a node)
* - cl_gui_column_tree=>eventid_header_context_men_req
* (needed for header context menu)
* - cl_gui_column_tree=>eventid_header_click
* (allows selection of columns (only when item selection activated))
* - cl_gui_column_tree=>eventid_item_keypress
* (needed for F1-Help (only when item selection activated))
* Nevertheless you have to provide their IDs again if you register
* additional events with SET_REGISTERED_EVENTS (see below).
* To do so, call first method GET_REGISTERED_EVENTS (this way,
* all already registered events remain registered, even your own):
CALL METHOD go_alvtree->get_registered_events
 IMPORTING
 events = lt_events.
* (If you do not these events will be deregistered!!!).
* You do not have to register events of the toolbar again.
* Register additional events for your own purposes:
* §5. Register first context menu event on frontend (with postfix
* (_REQUEST). The second is registered automatically.
ls_event-eventid = cl_gui_column_tree=>eventid_node_context_menu_req.
APPEND ls_event TO lt_events.
* register events on frontend
CALL METHOD go_alvtree->set_registered_events
 EXPORTING
 events = lt_events
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 illegal_event_combination = 3.
IF sy-subrc <> 0.
 MESSAGE x208(00) WITH 'ERROR'. "#EC NOTEXT
ENDIF.
* §6. Register both context menu events on backend (ABAP Objects
* event handling).
SET HANDLER:
 lcl_eventhandler=>handle_node_ctxmenu_req FOR go_alvtree,
 lcl_eventhandler=>handle_node_ctxmenu_sel FOR go_alvtree.
ENDFORM. " register_events
Regards,
Uwe

Download ABAP Objects to a local directory

Hi! Just want to ask if there's someone who knows any program that can download a copy of ABAP Objects to a local directory? Thanks a lot!!!

Hi Jason.
Find the Below code to download ABAP Source code to your local directory . Before downloading just create " :\source " directory.
Hope this info Helps YOU.
Reward Points If It Helps YOU.
Regards,
Raghav
[code]*
Download and Upload your ABAP program from/to your local harddisk.
Allows individual or mass transfering of ABAP program.
Before using, create a folder c:\Source
REPORT ZDOWN_UP_LOAD
 NO STANDARD PAGE HEADING
 LINE-SIZE 255.
Declare Database Objects
tables:
 DOKIL,
 TRDIR.
Constants
CONSTANTS:
 MC_TRDIR_IDENTIFIER(72) TYPE C VALUE '%&%& RDIR',
 MC_REPORT_IDENTIFIER(72) TYPE C VALUE '%&%& REPO',
 MC_TEXT_IDENTIFIER(72) TYPE C VALUE '%&%& TEXP',
 MC_THEAD_IDENTIFIER(72) TYPE C VALUE '%&%& HEAD',
 MC_DOC_IDENTIFIER(72) TYPE C VALUE '%&%& DOKL',
 MC_TRDIR_SHORT(4) TYPE C VALUE 'RDIR',
 MC_REPORT_SHORT(4) TYPE C VALUE 'REPO',
 MC_TEXT_SHORT(4) TYPE C VALUE 'TEXP',
 MC_THEAD_SHORT(4) TYPE C VALUE 'HEAD',
 MC_DOC_SHORT(4) TYPE C VALUE 'DOKP'.
Declare Module level data structures
DATA: BEGIN OF MTAB_PROGRAM_SOURCE OCCURS 0,
 LINE(72) TYPE C,
 END OF MTAB_PROGRAM_SOURCE.
DATA: MTAB_PROGRAM_TRDIR LIKE TRDIR OCCURS 0 WITH HEADER LINE.
DATA: MTAB_PROGRAM_TEXTS LIKE TEXTPOOL OCCURS 0 WITH HEADER LINE.
DATA: MSTR_THEAD LIKE THEAD.
DATA: BEGIN OF MTAB_PROGRAM_FILE OCCURS 0,
 LINE(275) TYPE C,
 END OF MTAB_PROGRAM_FILE.
DATA: BEGIN OF MTAB_DIRECTORY OCCURS 0,
 NAME LIKE TRDIR-NAME,
 DESC(72) TYPE C,
 SAVENAME LIKE RLGRAP-FILENAME,
 END OF MTAB_DIRECTORY.
DATA: BEGIN OF MTAB_PROGRAM_DOCUMENTATION OCCURS 0,
 LINE(255) TYPE C,
 END OF MTAB_PROGRAM_DOCUMENTATION.
Selection Screen
*-- Options for upload/download of programs
SELECTION-SCREEN BEGIN OF BLOCK FRM_OPTIONS WITH FRAME TITLE TEXT-UDL.
PARAMETERS:
 RB_DOWN RADIOBUTTON GROUP UDL DEFAULT 'X'. " Download reports
SELECTION-SCREEN BEGIN OF BLOCK FRM_TRDIR WITH FRAME TITLE TEXT-DIR.
SELECT-OPTIONS:
 S_NAME FOR TRDIR-NAME, " Program Name
 S_SUBC FOR TRDIR-SUBC " Program Type
 DEFAULT 'F' OPTION EQ SIGN E," Exclude Functions by default
 S_CNAM FOR TRDIR-CNAM " Created by
 DEFAULT SY-UNAME,
 S_UNAM FOR TRDIR-UNAM, " Last Changed by
 S_CDAT FOR TRDIR-CDAT, " Creation date
 S_UDAT FOR TRDIR-UDAT. " Last update date
SELECTION-SCREEN END OF BLOCK FRM_TRDIR.
*-- Options for uploading programs
PARAMETERS:
 RB_UP RADIOBUTTON GROUP UDL. " Upload reports
SELECTION-SCREEN BEGIN OF BLOCK FRM_UPLOAD WITH FRAME TITLE TEXT-UPL.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(29) TEXT-SNG.
PARAMETERS:
 RB_FILE RADIOBUTTON GROUP HOW DEFAULT 'X'.
SELECTION-SCREEN COMMENT 33(42) TEXT-FNA.
SELECTION-SCREEN END OF LINE.
PARAMETERS:
 RB_LIST RADIOBUTTON GROUP HOW.
SELECTION-SCREEN END OF BLOCK FRM_UPLOAD.
SELECTION-SCREEN END OF BLOCK FRM_OPTIONS.
*-- Options for up/downloading programs
SELECTION-SCREEN BEGIN OF BLOCK FRM_FILEN WITH FRAME TITLE TEXT-FIL.
PARAMETERS:
 RB_DOS RADIOBUTTON GROUP FIL DEFAULT 'X', " Save to local
 RB_UNIX RADIOBUTTON GROUP FIL, " Save to UNIX
 P_PATH LIKE RLGRAP-FILENAME " Path to save files to
 DEFAULT 'c:\Source\'.
SELECTION-SCREEN END OF BLOCK FRM_FILEN.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_NAME-LOW.
 CALL FUNCTION 'F4_PROGRAM'
 EXPORTING
 OBJECT = S_NAME-LOW
 SUPPRESS_SELECTION = 'X'
 IMPORTING
 RESULT = S_NAME-LOW
 EXCEPTIONS
 OTHERS = 1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_NAME-HIGH.
 CALL FUNCTION 'F4_PROGRAM'
 EXPORTING
 OBJECT = S_NAME-HIGH
 SUPPRESS_SELECTION = 'X'
 IMPORTING
 RESULT = S_NAME-HIGH
 EXCEPTIONS
 OTHERS = 1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_UNAM-LOW.
 PERFORM GET_NAME USING 'S_UNAM-LOW'
 CHANGING S_UNAM-LOW.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_UNAM-HIGH.
 PERFORM GET_NAME USING 'S_UNAM-HIGH'
 CHANGING S_UNAM-HIGH.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_CNAM-LOW.
 PERFORM GET_NAME USING 'S_CNAM-LOW'
 CHANGING S_CNAM-LOW.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_CNAM-HIGH.
 PERFORM GET_NAME USING 'S_CNAM-HIGH'
 CHANGING S_CNAM-HIGH.
TOP-OF-PAGE.
 IF RB_LIST = 'X'.
 FORMAT COLOR COL_HEADING.
 NEW-LINE.
 WRITE: AT 3 TEXT-H01,
 AT 15 TEXT-H03.
 FORMAT COLOR OFF.
 ENDIF.
AT LINE-SELECTION.
 CHECK RB_LIST = 'X'. " only do in list mode
 READ LINE SY-CUROW FIELD VALUE MTAB_DIRECTORY-SAVENAME.
*-- Read file into an internal table
 PERFORM READ_REPORT_FROM_DISK TABLES MTAB_PROGRAM_FILE
 USING MTAB_DIRECTORY-SAVENAME.
*-- Split table into TADIR entry, report lines, and report text
 PERFORM SPLIT_INCOMING_FILE TABLES MTAB_PROGRAM_FILE
 MTAB_PROGRAM_SOURCE
 MTAB_PROGRAM_TEXTS
 MTAB_PROGRAM_DOCUMENTATION
 CHANGING TRDIR
 MSTR_THEAD.
*-- Save all of the data
 PERFORM INSERT_NEW_REPORT TABLES MTAB_PROGRAM_SOURCE
 MTAB_PROGRAM_TEXTS
 MTAB_PROGRAM_DOCUMENTATION
 USING TRDIR
 MSTR_THEAD.
Start of processing
START-OF-SELECTION.
 FORMAT COLOR COL_NORMAL.
 IF RB_DOWN = 'X'.
 PERFORM DOWNLOAD_REPORTS.
 ELSEIF RB_UP = 'X'.
 PERFORM UPLOAD_REPORTS.
 ENDIF.
END-OF-SELECTION.
 IF RB_DOWN = 'X'.
 CONCATENATE P_PATH
 'directory.txt'
 INTO P_PATH.
 PERFORM SAVE_TABLE_TO_FILE TABLES MTAB_DIRECTORY
 USING P_PATH.
 ENDIF.
 FORM UPLOAD_REPORTS *
FORM UPLOAD_REPORTS.
*-- Can upload a reports entered in selection criteria or
*-- select from a list. List can be from index.txt in same directory
*-- (created by the download) or by reading the first line of each file
*-- in the directory.
 IF RB_FILE = 'X'. " Upload single program from a file
*-- Read file into an internal table
 PERFORM READ_REPORT_FROM_DISK TABLES MTAB_PROGRAM_FILE
 USING P_PATH.
*-- Split table into TADIR entry, report lines, and report text
 PERFORM SPLIT_INCOMING_FILE TABLES MTAB_PROGRAM_FILE
 MTAB_PROGRAM_SOURCE
 MTAB_PROGRAM_TEXTS
 MTAB_PROGRAM_DOCUMENTATION
 CHANGING TRDIR
 MSTR_THEAD.
*-- Save all of the data
 PERFORM INSERT_NEW_REPORT TABLES MTAB_PROGRAM_SOURCE
 MTAB_PROGRAM_TEXTS
 MTAB_PROGRAM_DOCUMENTATION
 USING TRDIR
 MSTR_THEAD.
 ELSEIF RB_LIST = 'X'. " Show list for user to choose from
*-- get list of report names/descriptions from directory text
 CONCATENATE P_PATH
 'directory.txt'
 INTO P_PATH.
 PERFORM READ_REPORT_FROM_DISK TABLES MTAB_DIRECTORY
 USING P_PATH.
 SORT MTAB_DIRECTORY.
*-- Write out list of report names/descriptions
 LOOP AT MTAB_DIRECTORY.
 WRITE:
 / MTAB_DIRECTORY-NAME UNDER TEXT-H01,
 MTAB_DIRECTORY-DESC UNDER TEXT-H03,
 MTAB_DIRECTORY-SAVENAME.
 ENDLOOP.
*-- Process user selections for reports to upload.
 ENDIF.
ENDFORM. " upload_reports
 FORM DOWNLOAD_REPORTS *
 From the user selections, get all programs that meet the *
 criteria, and save them in ftab_program_directory. *
 Also save the report to disk. *
FORM DOWNLOAD_REPORTS.
 DATA:
 LC_FULL_FILENAME LIKE RLGRAP-FILENAME.
*-- The table is put into an internal table because the program will
*-- abend if multiple transfers to a dataset occur within a SELECT/
*-- ENDSELCT (tested on 3.1H)
 SELECT * FROM TRDIR
 INTO TABLE MTAB_PROGRAM_TRDIR
 WHERE NAME IN S_NAME
 AND SUBC IN S_SUBC
 AND CNAM IN S_CNAM
 AND UNAM IN S_UNAM
 AND CDAT IN S_CDAT
 AND UDAT IN S_UDAT.
 LOOP AT MTAB_PROGRAM_TRDIR.
*-- Clear out text and source code tables
 CLEAR:
 MTAB_PROGRAM_FILE,
 MTAB_PROGRAM_SOURCE,
 MTAB_PROGRAM_TEXTS,
 MTAB_PROGRAM_DOCUMENTATION.
 REFRESH:
 MTAB_PROGRAM_FILE,
 MTAB_PROGRAM_SOURCE,
 MTAB_PROGRAM_TEXTS,
 MTAB_PROGRAM_DOCUMENTATION.
*-- Get the report
 READ REPORT MTAB_PROGRAM_TRDIR-NAME INTO MTAB_PROGRAM_SOURCE.
*-- Get the text for the report
 READ TEXTPOOL MTAB_PROGRAM_TRDIR-NAME INTO MTAB_PROGRAM_TEXTS.
*-- Get the documentation for the report
 CLEAR DOKIL.
 SELECT * UP TO 1 ROWS FROM DOKIL
 WHERE ID = 'RE'
 AND OBJECT = MTAB_PROGRAM_TRDIR-NAME
 AND LANGU = SY-LANGU
 AND TYP = 'E'
 ORDER BY VERSION DESCENDING.
 ENDSELECT.
*-- Documentation exists for this object
 IF SY-SUBRC = 0.
 CALL FUNCTION 'DOCU_READ'
 EXPORTING
 ID = DOKIL-ID
 LANGU = DOKIL-LANGU
 OBJECT = DOKIL-OBJECT
 TYP = DOKIL-TYP
 VERSION = DOKIL-VERSION
 IMPORTING
 HEAD = MSTR_THEAD
 TABLES
 LINE = MTAB_PROGRAM_DOCUMENTATION
 EXCEPTIONS
 OTHERS = 1.
 ENDIF.
*-- Put the report code and texts into a single file
*-- Put the identifier line in so that the start of the TRDIR line
*-- is marked
 CONCATENATE MC_TRDIR_IDENTIFIER
 MTAB_PROGRAM_TRDIR-NAME
 INTO MTAB_PROGRAM_FILE-LINE.
 APPEND MTAB_PROGRAM_FILE.
*-- Add the TRDIR line
 MTAB_PROGRAM_FILE-LINE = MTAB_PROGRAM_TRDIR.
 APPEND MTAB_PROGRAM_FILE.
*-- Put the identifier line in so that the start of the report code
*-- is marked
 CONCATENATE MC_REPORT_IDENTIFIER
 MTAB_PROGRAM_TRDIR-NAME
 INTO MTAB_PROGRAM_FILE-LINE.
 APPEND MTAB_PROGRAM_FILE.
*-- Add the report code
 LOOP AT MTAB_PROGRAM_SOURCE.
 MTAB_PROGRAM_FILE = MTAB_PROGRAM_SOURCE.
 APPEND MTAB_PROGRAM_FILE.
 ENDLOOP.
*-- Put the identifier line in so that the start of the report text
*-- is marked
 CONCATENATE MC_TEXT_IDENTIFIER
 MTAB_PROGRAM_TRDIR-NAME
 INTO MTAB_PROGRAM_FILE-LINE.
 APPEND MTAB_PROGRAM_FILE.
*-- Add the report texts
 LOOP AT MTAB_PROGRAM_TEXTS.
 MTAB_PROGRAM_FILE-LINE = MTAB_PROGRAM_TEXTS-ENTRY .
 APPEND MTAB_PROGRAM_FILE.
 ENDLOOP.
*-- Put the identifier line in so that the start of the THEAD record
*-- is marked
 CONCATENATE MC_THEAD_IDENTIFIER
 MTAB_PROGRAM_TRDIR-NAME
 INTO MTAB_PROGRAM_FILE-LINE.
 APPEND MTAB_PROGRAM_FILE.
 MTAB_PROGRAM_FILE = MSTR_THEAD.
 APPEND MTAB_PROGRAM_FILE.
*-- Put the identifier line in so that the start of the report
*-- documentation is marked
 CONCATENATE MC_DOC_IDENTIFIER
 MTAB_PROGRAM_TRDIR-NAME
 INTO MTAB_PROGRAM_FILE-LINE.
 APPEND MTAB_PROGRAM_FILE.
*-- Add the report documentation
 LOOP AT MTAB_PROGRAM_DOCUMENTATION.
 MTAB_PROGRAM_FILE = MTAB_PROGRAM_DOCUMENTATION.
 APPEND MTAB_PROGRAM_FILE.
 ENDLOOP.
*-- Make the fully pathed filename that report will be saved to
 CONCATENATE P_PATH
 MTAB_PROGRAM_TRDIR-NAME
 '.txt'
 INTO LC_FULL_FILENAME.
 PERFORM SAVE_TABLE_TO_FILE TABLES MTAB_PROGRAM_FILE
 USING LC_FULL_FILENAME.
*-- Write out message with Program Name/Description
 READ TABLE MTAB_PROGRAM_TEXTS WITH KEY ID = 'R'.
 IF SY-SUBRC = 0.
 MTAB_DIRECTORY-NAME = MTAB_PROGRAM_TRDIR-NAME.
 MTAB_DIRECTORY-DESC = MTAB_PROGRAM_TEXTS-ENTRY.
 MTAB_DIRECTORY-SAVENAME = LC_FULL_FILENAME.
 APPEND MTAB_DIRECTORY.
 WRITE: / MTAB_PROGRAM_TRDIR-NAME,
 MTAB_PROGRAM_TEXTS-ENTRY(65) COLOR COL_HEADING.
 ELSE.
 MTAB_DIRECTORY-NAME = MTAB_PROGRAM_TRDIR-NAME.
 MTAB_DIRECTORY-DESC = 'No description available'.
 MTAB_DIRECTORY-SAVENAME = LC_FULL_FILENAME.
 APPEND MTAB_DIRECTORY.
 WRITE: / MTAB_PROGRAM_TRDIR-NAME.
 ENDIF.
 ENDLOOP.
ENDFORM. " BUILD_PROGRAM_DIRECTORY
 FORM SAVE_TABLE_TO_FILE *
--> FTAB_TABLE *
--> F_FILENAME *
FORM SAVE_TABLE_TO_FILE TABLES FTAB_TABLE
 USING F_FILENAME.
 IF RB_DOS = 'X'. " Save file to presentation server
 CALL FUNCTION 'WS_DOWNLOAD'
 EXPORTING
 FILENAME = F_FILENAME
 FILETYPE = 'ASC'
 TABLES
 DATA_TAB = FTAB_TABLE
 EXCEPTIONS
 OTHERS = 4.
 IF SY-SUBRC NE 0.
 WRITE: / 'Error opening dataset' COLOR COL_NEGATIVE,
 F_FILENAME COLOR COL_NEGATIVE.
 ENDIF.
 ELSE. " Save file to application serve
 OPEN DATASET F_FILENAME FOR OUTPUT IN TEXT MODE encoding default.
 IF SY-SUBRC = 0.
 LOOP AT FTAB_TABLE.
 TRANSFER FTAB_TABLE TO F_FILENAME.
 IF SY-SUBRC NE 0.
 WRITE: / 'Error writing record to file;' COLOR COL_NEGATIVE,
 F_FILENAME COLOR COL_NEGATIVE.
 ENDIF.
 ENDLOOP.
 ELSE.
 WRITE: / 'Error opening dataset' COLOR COL_NEGATIVE,
 F_FILENAME COLOR COL_NEGATIVE.
 ENDIF.
 ENDIF. " End RB_DOS
ENDFORM. " SAVE_PROGRAM
 FORM READ_REPORT_FROM_DISK *
 Read report into internal table. Can read from local or *
 remote computer *
FORM READ_REPORT_FROM_DISK TABLES FTAB_TABLE
 USING F_FILENAME.
 DATA:
 LC_MESSAGE(128) TYPE C.
 CLEAR FTAB_TABLE.
 REFRESH FTAB_TABLE.
 IF RB_DOS = 'X'.
 TRANSLATE F_FILENAME USING '/\'. " correct slash for Dos PC file
 CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 FILENAME = F_FILENAME
 FILETYPE = 'ASC'
 TABLES
 DATA_TAB = FTAB_TABLE
 EXCEPTIONS
 CONVERSION_ERROR = 1
 FILE_OPEN_ERROR = 2
 FILE_READ_ERROR = 3
 INVALID_TABLE_WIDTH = 4
 INVALID_TYPE = 5
 NO_BATCH = 6
 UNKNOWN_ERROR = 7
 OTHERS = 8.
 IF SY-SUBRC >< 0.
 WRITE: / 'Error reading file from local PC' COLOR COL_NEGATIVE.
 ENDIF.
 ELSEIF RB_UNIX = 'X'.
 TRANSLATE F_FILENAME USING '\/'. " correct slash for unix
 OPEN DATASET F_FILENAME FOR INPUT MESSAGE LC_MESSAGE IN TEXT MODE encoding default.
 IF SY-SUBRC = 0.
 DO.
 READ DATASET F_FILENAME INTO FTAB_TABLE.
 IF SY-SUBRC = 0.
 APPEND FTAB_TABLE.
 ELSE.
 EXIT.
 ENDIF.
 ENDDO.
 CLOSE DATASET F_FILENAME.
 ELSE.
 WRITE: / 'Error reading file from remote computer'
 COLOR COL_NEGATIVE,
 / LC_MESSAGE,
 / F_FILENAME.
 SY-SUBRC = 4.
 ENDIF.
 ENDIF.
ENDFORM. " READ_REPORT_FROM_DISK
 FORM SPLIT_INCOMING_FILE *
--> FTAB_PROGRAM_FILE *
--> FTAB_PROGRAM_SOURCE *
--> ` *
--> FTAB_PROGRAM_TEXTS *
FORM SPLIT_INCOMING_FILE TABLES FTAB_PROGRAM_FILE
 STRUCTURE MTAB_PROGRAM_FILE
 FTAB_PROGRAM_SOURCE
 STRUCTURE MTAB_PROGRAM_SOURCE
 FTAB_PROGRAM_TEXTS
 STRUCTURE MTAB_PROGRAM_TEXTS
 FTAB_PROGRAM_DOCUMENTATION
 STRUCTURE MTAB_PROGRAM_DOCUMENTATION
 CHANGING FSTR_TRDIR
 FSTR_THEAD.
 DATA:
 LC_DATATYPE(4) TYPE C, " Type of data, REPO, TEXP, RDIR
 LC_PROGRAM_FILE LIKE MTAB_PROGRAM_FILE.
 LOOP AT FTAB_PROGRAM_FILE.
 LC_PROGRAM_FILE = FTAB_PROGRAM_FILE.
 CASE LC_PROGRAM_FILE(9).
 WHEN MC_TRDIR_IDENTIFIER.
 LC_DATATYPE = MC_TRDIR_SHORT.
 WHEN MC_REPORT_IDENTIFIER.
 LC_DATATYPE = MC_REPORT_SHORT.
 WHEN MC_TEXT_IDENTIFIER.
 LC_DATATYPE = MC_TEXT_SHORT.
 WHEN MC_DOC_IDENTIFIER.
 LC_DATATYPE = MC_DOC_SHORT.
 WHEN MC_THEAD_IDENTIFIER.
 LC_DATATYPE = MC_THEAD_SHORT.
 WHEN OTHERS. " Actual contents of report, trdir, or text
 CASE LC_DATATYPE.
 WHEN MC_TRDIR_SHORT.
 FSTR_TRDIR = FTAB_PROGRAM_FILE.
 WHEN MC_REPORT_SHORT.
 FTAB_PROGRAM_SOURCE = FTAB_PROGRAM_FILE.
 APPEND FTAB_PROGRAM_SOURCE.
 WHEN MC_TEXT_SHORT.
 FTAB_PROGRAM_TEXTS-key = FTAB_PROGRAM_FILE-line.
 APPEND FTAB_PROGRAM_TEXTS.
 WHEN MC_THEAD_SHORT.
 FSTR_THEAD = FTAB_PROGRAM_FILE.
 WHEN MC_DOC_SHORT.
 FTAB_PROGRAM_DOCUMENTATION = FTAB_PROGRAM_FILE.
 APPEND FTAB_PROGRAM_DOCUMENTATION.
 ENDCASE.
 ENDCASE.
 ENDLOOP.
ENDFORM. " SPLIT_INCOMING_FILE
 FORM INSERT_NEW_REPORT *
--> FTAB_PROGRAM_SOURCE *
--> FTAB_PROGRAM_TEXTS *
--> F_TRDIR *
FORM INSERT_NEW_REPORT TABLES FTAB_PROGRAM_SOURCE
 STRUCTURE MTAB_PROGRAM_SOURCE
 FTAB_PROGRAM_TEXTS
 STRUCTURE MTAB_PROGRAM_TEXTS
 FTAB_PROGRAM_DOCUMENTATION
 STRUCTURE MTAB_PROGRAM_DOCUMENTATION
 USING FSTR_TRDIR LIKE TRDIR
 FSTR_THEAD LIKE MSTR_THEAD.
 DATA:
 LC_OBJ_NAME LIKE E071-OBJ_NAME,
 LC_LINE2(40) TYPE C,
 LC_ANSWER(1) TYPE C.
*-- read trdir to see if the report already exists, if it does, prompt
*-- user to overwrite or abort.
 SELECT SINGLE * FROM TRDIR WHERE NAME = FSTR_TRDIR-NAME.
 IF SY-SUBRC = 0. " Already exists
 CONCATENATE 'want to overwrite report'
 FSTR_TRDIR-NAME
 INTO LC_LINE2 SEPARATED BY SPACE.
 CONCATENATE LC_LINE2
 INTO LC_LINE2.
 CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
 EXPORTING
 DEFAULTOPTION = 'N'
 TEXTLINE1 = 'The selected report already exists, do you'
 TEXTLINE2 = LC_LINE2
 TITEL = 'Report already exists'
 CANCEL_DISPLAY = SPACE
 IMPORTING
 ANSWER = LC_ANSWER
 EXCEPTIONS
 OTHERS = 1.
 ELSE.
 LC_ANSWER = 'J'.
 ENDIF.
 IF LC_ANSWER = 'J'.
*-- Create the TADIR entry. (TRDIR entry created by INSERT REPORT)
 LC_OBJ_NAME = TRDIR-NAME.
 CALL FUNCTION 'TR_TADIR_POPUP_ENTRY_E071'
 EXPORTING
 WI_E071_PGMID = 'R3TR'
 WI_E071_OBJECT = 'PROG'
 WI_E071_OBJ_NAME = LC_OBJ_NAME
 WI_TADIR_DEVCLASS = '$TMP'
 EXCEPTIONS
 EXIT = 3
 OTHERS = 4.
 IF SY-SUBRC = 0.
*-- Create Report
 INSERT REPORT FSTR_TRDIR-NAME FROM FTAB_PROGRAM_SOURCE.
*-- Create Texts
 INSERT TEXTPOOL FSTR_TRDIR-NAME FROM FTAB_PROGRAM_TEXTS
 LANGUAGE SY-LANGU.
*-- Save Documentation
 CALL FUNCTION 'DOCU_UPDATE'
 EXPORTING
 HEAD = FSTR_THEAD
 STATE = 'A'
 TYP = 'E'
 VERSION = '1'
 TABLES
 LINE = FTAB_PROGRAM_DOCUMENTATION
 EXCEPTIONS
 OTHERS = 1.
 ELSE.
 WRITE: / 'Error updating the TADIR entry' COLOR COL_NEGATIVE,
 'Program' COLOR COL_NEGATIVE INTENSIFIED OFF,
 FSTR_TRDIR-NAME, 'was not loaded into SAP.'
 COLOR COL_NEGATIVE INTENSIFIED OFF.
 ENDIF.
 ELSE.
 WRITE: / FSTR_TRDIR-NAME COLOR COL_NEGATIVE,
 'was not uploaded into SAP. Action cancelled by user'
 COLOR COL_NEGATIVE INTENSIFIED OFF.
 ENDIF.
ENDFORM. " INSERT_NEW_REPORT
 FORM GET_NAME *
--> VALUE(F_FIELD) *
--> F_NAME *
FORM GET_NAME USING VALUE(F_FIELD)
 CHANGING F_NAME.
 DATA: LTAB_FIELDS LIKE DYNPREAD OCCURS 0 WITH HEADER LINE,
 LC_PROG LIKE D020S-PROG,
 LC_DNUM LIKE D020S-DNUM.
 TRANSLATE F_FIELD TO UPPER CASE.
 refresh ltab_fields.
 LTAB_FIELDS-FIELDNAME = F_FIELD.
 append ltab_fields.
 LC_PROG = SY-REPID .
 LC_DNUM = SY-DYNNR .
 CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 DYNAME = LC_PROG
 DYNUMB = LC_DNUM
 TABLES
 dynpfields = ltab_fields
 EXCEPTIONS
 OTHERS = 01.
 read table ltab_fields index 1.
 IF SY-SUBRC EQ 0.
 F_NAME = LTAB_FIELDS-FIELDVALUE.
 refresh ltab_fields.
 ENDIF.
 CALL FUNCTION 'F4_USER'
 EXPORTING
 OBJECT = F_NAME
 IMPORTING
 RESULT = F_NAME.
ENDFORM. " GET_NAME
*TEXPZKBPROGS
IDIR File Download Options (File Selection)
IFIL File Options
IFNA Enter filename below (under File Options)
IH01 Prog Name
IH03 Program Description
ISNG Upload a single file
IUDL Upload to SAP/Download from SAP
IUPL File Upload Options
R Backup/Restore program source code with texts
P_PATH Path to save programs to
RB_DOS Files on local computer
RB_DOWN Download Programs
RB_FILE Upload a single file
RB_LIST Select program(s) from a list
RB_UNIX Files on remote computer
RB_UP Upload Programs to SAP
S_CDAT Date Created
S_CNAM Created by UserID
S_NAME Program Name
S_SUBC Program Type
S_UDAT Date Changed
S_UNAM Last Changed by UserID
*HEADZKBPROGS
DOKU ZHRBDC54
*DOKLZKBPROGS
*--- End of Program[/code]

How to translate std. ABAP report in german language to English in SAP

Dear All,
How to translate std. ABAP code in German language to English in SAP ?

Hi,
code does not need to be translated.
Data elment descriptions, documentation, text elements, etc. can be translated in the transaction se63.
Also you can translate almost each single object in the editor in the menue goto-translation.
Regards,
Gianpietro

Logical Database in Abap Objects

Hi to All
I want do it a program report using a Logical Database.
Is this possible ??? But when I make a GET <node>, occurs the following error:
 "" Statement "ENDMETHOD" missing. ""
I'm doing the following:
CLASS MONFIN IMPLEMENTATION.
 METHOD TRAER_DATOS.
 GET VBRK.
 ENDMETHOD.
ENDCLASS.
Please, somebody tell me how I use the logical database in Abap Objects.
Thank you very much
Regards
Dario R.

Hi there
Logical databases whilst of "some use" are not really part of OO.
If you want to use a logical database in an abap OO program I would create a special class which just does the get data from your DB and pass this either at record or table level.
Techniques such as GET XXXX LATE aren't really part of any OO type of application since at Object Instantiation time you should be able to access ALL the attributes of that object.
As far as OO is concerned Logical databases are a throwback to "Dinosaur Technology".
Since however modules such as SD and FI are still heavily reliant on relational structures (i.e linked tables etc) then there is still some limited life in this stuff but for OO try and solve it by another method.
If you really must use this stuff in OO then do it via a FMOD call and save the data in a table which your method will pass back to your application program.
You can't issue a GET command directly in a method.
Cheers
Jimbo

Adding leading zeros in abap objects.

Can anyone explain me
1. How to add leading zeros to a field in abap objects.
For eg:
data: dmb(6) type c value '123456',
actually the output value of c should have leading zeros added to it for length 16.
i.e '0000000000123456' . If the length of dmb is less than 16 then leading zeros should be added to that value to make it 16 as length.
Please tell me how to do it in ABAP Objects.

Hi Camila
Try to use the statement
DATA: ALPHABET(15) VALUE ' ABCDEFGHIJ',
 M1(4) VALUE 'ABCD',
 M2(6) VALUE 'BJJCA '.
SHIFT ALPHABET LEFT DELETING LEADING M1.
The field
ALPHABET
remains unchanged.
SHIFT ALPHABET LEFT DELETING LEADING SPACE.
The field ALPHABET now has the following contents:
'ABCDEFGHIJ '.
SHIFT ALPHABET RIGHT DELETING TRAILING M2.
ALPHABET now has the following contents:
' ABCDEFGHI'.
IN CHARACTER MODE
Effect
This is the default setting (see above), and the addition is therefore optional.
Note
Performance:
For performance reasons, you should avoid using SHIFT in WHILE loops.
The runtime required to shift a field with length 10 by one character to the right or left requires about 5 msn (standardized microseconds). A cyclical shift requires around 7 msn. The runtime for the ...
LEFT DELETING LEADING
... variant is around 3.5 msn, for ...
RIGHT DELETING TRAILING
... around 4.5 msn.
Reward all helpfull answers
Regards
Pavan

Translation of non-ABAP objects

Similar Messages

Maybe you are looking for