Editing ABAP Program with out using ABAP Editor

Dear Gurus,
I know that ABAP Programs like SAPMSSY1, etc. are stored in Table D010S or REPOSRC as per the version of the SAP Released.
my problem is that whem i open the table REPOSRC (Having around 34 colums), no doubt thati found the program list but i am not be able to see any thing which is written in Program language..!
how I will be able to access these program in there source language and so make certain changes in them.
actually during the RFC Logon, I am getting the error that "Error in Reading Program SAPMSSY1"
R/3 Basis System: Run-time error "GEN_SOURCE_FORMAT " occurred in accessing SAPMSSY1.
So pls tell me where I can find the actual program language so that I can make certian changes in them.
Pls REMEMBER THAT I CAN NOT USE ANY T-CODE LIKE SE36 etc. TO ENTER INTO ABAP EDITOR, AS STILL I AM NOT LOGGED ON. AT THE TIME OF GUI LOGIN I AM GETTING THE SYSTEM ERROR MESSAGE "DUMMY". WHAT THIS IS MEAN FOR??
Regards,
Abhishek

I CAN NOT ENTER INTO THE SYSTEM. AS I GOT THIS ERROR IN THE LAST STEP (RFC JOBS- POST PROCESSING) OF MY SAP INSTALLATION.so can not log in into the system.
SO WHERE I CAN MODIFY THE PROGRAMMING OF "SAPMSSY1" ?
AND RESOLLVED THE ABOVE SAID PROBLEM.
I am using ORACLE 9i with patch 92080 on Windows 2000 Server with SP 4
SAP Kernel is 620 with patch no. 251 and patch level 0
SAP GUI IS 710
Abhishek

Similar Messages

BDC PROGRAM WITH OUT USING A FM?

Hi Experts,
I need wirte a BDC program for tcode PA30.
i did the screen recording part using tcode-shdb.
i need to use field i recorded as input fields.
Now the main part is how to write code? with out using a class/method?
class/method which i earlier used is class : CL_GUI_FRONTEND_SERVICES.
                                                         method: gui_upload.
am not using ny flat file/xml file to upload?
are there any function modules which i can use?
and how to write code with out using FM?
if any can solve my issue would be very helpful...plz provide code...which would be more helpful.
Thanks in Adv.
Krrish.

Hi,
   If you are migrating employee data, I would suggest you to do it through PA40 transaction rather PA30. systematic screen validations it will go through. If you dont want to use any FM and wanted to do using recording pls find the below code which will update the employee data through PA40 with call transaction method.
SELECTION SCREEN
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE   text-001.
PARAMETERS: p_plan TYPE ibipparms-path OBLIGATORY.
SELECTION-SCREEN: END OF BLOCK b1.
TYPES: BEGIN OF ty_error,
         pernr TYPE persno,       " Personnel number
         rel_obj_id(12),         " Related Object ID
         msg(200) TYPE c,       " To store Message
       END   OF ty_error.
DATA: i_tplan TYPE STANDARD TABLE OF alsmex_tabline WITH HEADER LINE,
      i_intern TYPE STANDARD TABLE OF alsmex_tabline WITH HEADER LINE,
      i_error    TYPE ty_error OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF w_pa000,
       pernr TYPE persno,
       begda TYPE begda,
      END OF w_pa000.
DATA: wa_plan LIKE i_plan,
      wa_messtab    TYPE bdcmsgcoll, " Messages
      wa_error      TYPE ty_error. " Errors
DATA: it_pa000 LIKE STANDARD TABLE OF w_pa000 WITH HEADER LINE,
      it_pa002 LIKE STANDARD TABLE OF w_pa000 WITH HEADER LINE,
      it_pa001 LIKE STANDARD TABLE OF w_pa000 WITH HEADER LINE.
DATA: g_mode LIKE ctu_params-dismode VALUE 'N',
       g_file TYPE ibipparms-path.
ALV field catalog
DATA : i_fieldcat TYPE slis_t_fieldcat_alv.
      Batchinputdata of single transaction
DATA:   i_bdcdata LIKE bdcdata    OCCURS 0 WITH HEADER LINE.
      messages of call transaction
DATA:   i_messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
      error session opened (' ' or 'X')
Table to hold the return messages
DATA: BEGIN OF i_errmsg OCCURS 10.
        INCLUDE STRUCTURE bapiret2.
DATA: END OF i_errmsg.
ALV List header table
DATA : i_header1 TYPE slis_t_listheader.
ALV List header table
DATA : i_header TYPE slis_listheader.
***ALV Events
DATA: is_layout TYPE slis_layout_alv.
DATA : it_event TYPE slis_alv_event.
DATA : it_event1 TYPE slis_t_event.
To get the F4 help for file
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_plan.
PERFORM get_filename.
START OF SELECTION
START-OF-SELECTION.
Initialise data
PERFORM initialise_events.
Retrieve data from Excel file
PERFORM retreive_data.
Populate final data into an internal table
PERFORM populate_data.
Process the excel file data to create a record for IT0007
PERFORM process_data.
END OF SELECTION
END-OF-SELECTION.
PERFORM final_output.
*&      Form GET_FILENAME
FORM get_filename .
*Function module used for F4 help
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
    IMPORTING
      file_name     = p_plan.
ENDFORM.                    " GET_FILENAME
*&      Form INITIALISE_EVENTS
FORM initialise_events .
i_header-typ = 'H'.
i_header-key = 'R'.
i_header-info = 'BDC Interface for PA Infotypes 0000,0001,0002'.
APPEND i_header TO i_header1.
CLEAR i_header.
i_header-typ = 'S'.
i_header-info = 'Hiring, Org.Assignment, Personnel Data'.
APPEND i_header TO i_header1.
CLEAR i_header.
***Events and form name
it_event-name = 'TOP_OF_PAGE'.
it_event-form = 'TOP_OF_PAGE'.
APPEND it_event TO it_event1.
ENDFORM.                    " INITIALISE_EVENTS
*&      Form RETREIVE_DATA
FORM retreive_data .
PERFORM upload_data.
ENDFORM.                    " RETREIVE_DATA
*&      Form UPLOAD_DATA
FORM upload_data .
FM to upload data from excel sheet to internal table
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      filename                = p_plan
      i_begin_col             = g_colbeg
      i_begin_row             = g_rowbeg
      i_end_col               = g_colend
      i_end_row               = g_rowend
    TABLES
      intern                  = i_tplan
    EXCEPTIONS
      inconsistent_parameters = 1
      upload_ole              = 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.
ENDFORM.                    " UPLOAD_DATA
*&      Form POPULATE_DATA
FORM populate_data .
processing the internal table generated from the function module
Passing data from Excel file to internal table
CLEAR: g_cnt_processed,
         g_cnt_err_processed,
         i_intern,
         i_plan.
LOOP AT i_tplan.
    AT NEW row.
      CLEAR i_plan.
    ENDAT.
    CASE i_tplan-col.
Begin Date
      WHEN '0001'.
        i_plan-pernr = i_tplan-value.
End Date
      WHEN '0002'.
        i_plan-begda = i_tplan-value.
      WHEN '0003'.
        i_plan-massg = i_tplan-value.
Sign
      WHEN '0004'.
        i_plan-plans = i_tplan-value.
      WHEN '0005'.
        i_plan-werks = i_tplan-value.
      WHEN '0006'.
        i_plan-persg = i_tplan-value.
      WHEN '0007'.
        i_plan-persk = i_tplan-value.
      WHEN '0008'.
        i_plan-anrex = i_tplan-value.
      WHEN '0009'.
        i_plan-nachn = i_tplan-value.
      WHEN '0010'.
        i_plan-vorna = i_tplan-value.
      WHEN '0011'.
        i_plan-gesch = i_tplan-value.
      WHEN '0012'.
        i_plan-gbdat = i_tplan-value.
      WHEN '0013'.
        i_plan-fatxt = i_tplan-value.
      WHEN '0014'.
        i_plan-famdt = i_tplan-value.
      WHEN '0015'.
        i_plan-gblnd = i_tplan-value.
      WHEN '0016'.
        i_plan-anzkd = i_tplan-value.
      WHEN '0017'.
        i_plan-natio = i_tplan-value.
      WHEN '0018'.
        i_plan-btrtl = i_tplan-value.
      WHEN '0019'.
        i_plan-gsber = i_tplan-value.
      WHEN '0020'.
        i_plan-abkrs = i_tplan-value.
    ENDCASE.
Appending the internal table tb_data, tb_chng
    AT END OF row.
      APPEND i_plan.
      IF i_plan IS INITIAL.
        g_cnt_err_processed = g_cnt_err_processed + 1.
      ENDIF.
    ENDAT.
ENDLOOP.
To get the total number of records processed
DESCRIBE TABLE i_plan LINES g_lines.
g_cnt_processed = g_cnt_err_processed + g_lines.
CLEAR g_lines.
ENDFORM.                    " POPULATE_DATA
*&      Form PROCESS_DATA
FORM process_data .
CLEAR wa_error.
REFRESH i_bdcdata.
Check if the employee numbers from the template has already been hired
SELECT pernr
         begda
         FROM pa0000
         INTO TABLE it_pa000
         FOR ALL ENTRIES IN i_plan
         WHERE pernr = i_plan-pernr
           AND massn = 'ZA'.
IF sy-subrc = 0.
    SORT it_pa000 BY pernr.
Check if employee has a corresponding infotype 0001 record
    SELECT pernr
           begda
           FROM pa0001
           INTO TABLE it_pa001
           FOR ALL ENTRIES IN it_pa000
           WHERE pernr = it_pa000-pernr AND
                 begda = it_pa000-begda.
    IF sy-subrc = 0.
      SORT it_pa001 BY pernr.
Check if employee has a corresponding infotype 0002 record
      SELECT pernr
           begda
           FROM pa0001
           INTO TABLE it_pa002
           FOR ALL ENTRIES IN it_pa001
           WHERE pernr = it_pa001-pernr AND
                 begda = it_pa001-begda.
      IF sy-subrc = 0.
        SORT it_pa002 BY pernr.
      ENDIF.
    ENDIF.
ENDIF.
LOOP AT i_plan.
    REFRESH i_bdcdata.
***your recording to be pasted here***
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'P0006-BEGDA'.
    PERFORM call_transaction.
    APPEND wa_error TO i_error.
    REFRESH: i_bdcdata, i_messtab.
    CLEAR: wa_error, i_error.
ENDLOOP.
ENDFORM.                    " PROCESS_DATA
*&      Form BDC_DYNPRO
FORM bdc_dynpro USING program dynpro.
CLEAR i_bdcdata.
i_bdcdata-program = program.
i_bdcdata-dynpro   = dynpro.
i_bdcdata-dynbegin = 'X'.
APPEND i_bdcdata.
ENDFORM.                    "BDC_DYNPRO
*&      Form BDC_FIELD
FORM bdc_field USING fnam fval.
IF fval <> nodata.
CLEAR i_bdcdata.
i_bdcdata-fnam = fnam.
i_bdcdata-fval = fval.
APPEND i_bdcdata.
ENDIF.
ENDFORM.                    "bdc_field
*&      Form ERROR_RECORD_DATA
FORM error_record_data .
CLEAR: g_lines,
       wa_messtab,
       g_msg.
DESCRIBE TABLE i_messtab LINES g_lines.
READ TABLE i_messtab INTO wa_messtab INDEX g_lines.
IF sy-subrc = 0.
    CLEAR g_msg.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        id        = wa_messtab-msgid
        lang      = sy-langu
        no        = wa_messtab-msgnr
        v1        = wa_messtab-msgv1
        v2        = wa_messtab-msgv2
        v3        = wa_messtab-msgv3
        v4        = wa_messtab-msgv4
      IMPORTING
        msg       = g_msg
      EXCEPTIONS
        not_found = 1
        OTHERS    = 2.
   IF wa_messtab-msgtyp = 'E'.
    IF wa_messtab-msgtyp = 'S' AND wa_messtab-msgnr = '102' AND wa_messtab-msgid = 'PG'.
      wa_error-pernr = i_plan-pernr.
      wa_error-rel_obj_id = 'S'.
      wa_error-msg = 'Personnel Number Created Successfully'.
    ELSE.
      wa_error-pernr = i_plan-pernr.
      wa_error-rel_obj_id = 'E'.
      wa_error-msg = g_msg.
    ENDIF.
   APPEND wa_error TO i_error.
   CLEAR i_error.
ENDIF.
ENDFORM.                    " ERROR_RECORD_DATA
*&      Form FINAL_OUTPUT
FORM final_output .
CLEAR g_lines.
SORT i_error.
*************added*********************************************
loop at i_error into wa_error.
    if wa_error-MSG eq 'No batch input data for screen MP000600 2000'.
      wa_error-rel_obj_id = 'S'.
      wa_error-MSG = 'Record Created Successfully'.
      modify i_error from wa_error.
    endif.
endloop.
loop at i_error into wa_error.
    if wa_error-rel_obj_id = 'S'.
      g_cnt_success = g_cnt_success + 1.       " Append success count
    elseif wa_error-rel_obj_id = 'E'.
      g_cnt_failure = g_cnt_failure + 1.       " Append error count
    endif.
endloop.
***Field catalog
PERFORM field_cat.
***Assigning Program name
g_repid = sy-repid.
SORT i_error.
***Display Output
IF NOT it_final[] IS INITIAL.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program       = g_repid
           i_callback_user_command = 'USER_COMMAND'
           i_callback_pf_status_set = 'PF_STATUS_SET'
            i_save                   = 'A'
            it_events                = it_event1
            is_layout                = is_layout
            it_fieldcat              = i_fieldcat[]
       TABLES
            t_outtab                 = i_error[].
ELSE.
   MESSAGE i015(zv_msg) WITH 'No Data Found for this selection'.
   LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM.                    " FINAL_OUTPUT
*&      Form top_of_page
      text
FORM top_of_page.
***FM for Displaying Heading
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = i_header1[]
      i_logo             = 'ENJOYSAP_LOGO'.
ENDFORM.                    "top_of_page
*&      Form FIELD_CAT
FORM field_cat .
ENDFORM.                    " FIELD_CAT
*&      Form CALL_TRANSACTION
FORM call_transaction .
CALL TRANSACTION 'PA40' USING i_bdcdata
                               MODE g_mode
                               UPDATE 'S'
                               MESSAGES INTO i_messtab.
If call transaction successful
IF sy-subrc = 0.
   g_cnt_success = g_cnt_success + 1.       " Append success count "changed
    PERFORM error_record_data. " Populate all data
If call transaction not successful
ELSE.
    PERFORM error_record_data. " Populate all table
   g_cnt_failure = g_cnt_failure + 1.       " Append error count "changed
ENDIF.
ENDFORM.                    " CALL_TRANSACTION

Bdc program with out coding

Hi All,
I want to know how to write a bdc program with out coding...
Thank you,
Gopi....

Hai.
check this.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
Flat file can be created in your hard disk as follows:
1 Vinod Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:\FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.
regards.
sowjanya.b.

Accessing BAPI's using JAVA with out using webdynpro URGENT

hi Experts,
What is the procedure for calling RFC/BAPI's using JAVA with out using the webdynpro. Please let me know what are the possibilities with step by step implementation.
Regards
Vijay

Hi Boris Rubarth,
Thaks for relavant information.
I have kind of the requirement. The clinet is asking for connecting the SAP RFC using java application. The build Jar or .war or .Ear for which are going to develop should be compatible for running on any of the Applications server like they have Tom cat, weblogic, websphere server.
so the .jar for or .ear file which we are going to develop should be able to run accessing the RFC/ BAPIs from any of these servers other than SAP WAS that is what their target.
Please give me your suggestion, which is better approach. currently their SAP system is 4.6c . So presently it is not possible the webservice approach. But they have plans to go for upgrade to ECC6.0
In that case only JCO option is possible. If use this option . Is it possible to access application which is deployed irrespective of the WAS by doing the required configuration.
Basically i am aware of the ABAP webservice work bech steps and also the JAVA coding also.
Please suggest me what is the better way to achieve this.
Regards

I would like to know how i can create a bell graph with out using sub VIs, the data that i created consists in 500 readings with values of 0 to 100, i calculated the mean value and standard diviation. I hope some one can help me

I would like to know how i can create a bell graph with out using sub VIs, the data that i created consists in 500 readings with values of 0 to 100, i calculated the mean value and standard diviation. I hope some one can help me

Here's a quick example I threw together that generates a sort-of-bell-curve shaped data distribution, then performs the binning and plotting.
-Kevin P.
Message Edited by Kevin Price on 12-01-2006 02:42 PM
Attachments:
Binning example.vi ‏51 KB
Binning example.png ‏12 KB

How to Install crystal run time programs with out designer.

Can anyone suggest me how to install crystal run time program with out installing entire designer software.
Is it coming along with CR software package, which we have to do custom install or is it coming as a different package.
Currently my client is using only the run time programs to trigger crystal report from VB app but developers have installed entire software for development. We need to figure out how this install can be done, as it was done long time before and folks who have done it left the company.
Any suggestion on this would be of great help to me.

See this wiki:
https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsforVisualStudio.NETRuntimeDistribution-Versions9.1to12.0
Ludek

Payment to Vendor by bank transfer with out useing APP

Dear all,
I of our Client has issue-- that i want post a wire transfer to vendor with out using APP.
thanks & regards
krishna reddy

Hi Rajendra
1. You need to check with your client which bank they are going to use
2. Check with the Bank the file format they are looking for - XML or TXT, etc
Also ask them the contents of the file, the fields they want in it and how they must be populated
3. Ask them if they are going to provide you a program to generate the file.. Some banks like CITI do provide
4. If they dont provide, you may have to write your own program to generate the TXT file
XML files can be generated using DMEE (Payment Medium Work Bench)
5. Once file is generated, you need to transmit it to the Bank
6. Before transmission, you may have a 3rd party vendor to do the file encryption
Br. Ajay M

How to get the line in the template (smartform) with out using under score

Hi,
     How to get the line in the template (smartform) with out using under score,
     and how to print the box (line the check box - small squre box (which is used ot mark the tick by the user in front of the item).
     Please provide the valueble answer as early as possible.
Thanks,
Ravi

Hi Ravi,
Line -
Use a SMATSTYLE for this purpose.in the smartstyle create a paragraph or character with underline atribute.Then call the smartstyle in the text.
Search SDN with Key <b>UNDERSCORE</b>.. will get few more posts on the same.
For Checkbox - refer link
Re: Quick Question on Smartforms
Re: putting tick mark into check box in smartform
Reward points if this Helps.
Manish
Message was edited by:
        Manish Kumar

Please suggest a select query / sub query with out using any subprograms or

source table: Three columns ORIGIN, DESTINATION,MILES
Origin      Destination Miles
Sydney      Melbourne      1000
Perth      Adelaide      3000
Canberra      Melbounre      700
Melbourne      Sydney           1000
Brisbane      Sydney           1000
Perth      Darwin           4000
Sydney      Brisbane      1000
out put :Three columns ORIGIN, DESTINATION,MILES
Duplicate routes are to be ignored so the output is
Origin      Destination      Miles
Sydney      Melbourne      1000
Perth      Adelaide      3000
Canberra      Melbounre      700
Brisbane      Sydney           1000
Perth      Darwin           4000
Please suggest a select query / sub query with out using any subprograms or functions/pkgs to get the out put table.

Hi,
user9368047 wrote:
... Please suggest a select query / sub query with out using any subprograms or functions/pkgs to get the out put table.Why? If the most efficient way to get the results you want involves using a function, why wouldn't you use it?
Here's one way, without any functions:
SELECT     a.*
FROM           source_table a
LEFT OUTER JOIN      source_table b ON   a.origin          = b.destination
                                      AND a.destination      = b.origin
                      AND a.miles          = b.miles
WHERE   b.origin > a.origin    -- Not b.origin > b.origin
OR     b.origin IS NULL
;If you'd care to post CREATE TABLE and INSERT statements for your sample data, then I could test this.
Edited by: Frank Kulash on Nov 6, 2012 7:39 PM
Corrected WHERE clause after MLVrown (below)

Develope a report with out using alv

REPORT OBJECT:
      The report to list the material quantities returned because of breakage or expiry date or for any other reason.for material the quantities are summed up
under expiry quantity ,breakage and other quantity for a particular month.
       above mentioned is the object of my report .
      please help me any one to develop the report with out using   ALV'S.

Hello Pravardhan
Your requirements are definitely demanding for an ALV list because all the calculations can be done by the user himself without any programming. The only thing you need to do is to collect all necessary data. In addition, all criteria for calculating subtotals/totals (e.g. month) must be available as separate column on the ALV list.
This is reasonable programming, anything else not. If the users have an ALV list they can easily adjust the layout to their specific needs without calling for a developer.
We should always develop our programs with a <b>strong focus on the user's perspective</b>.
Regards
Uwe

How to queue custom events with out using af:calientListener.- onKeyUp.

Hi,
I have a custom component ( extending richinput text).
defined a new attribute called "onkeyup" and added necessary logic in Renderer. Some thing like
write.writeAttribute("onkeyup" , "handleEvent()");
I rendered the java script code too ..... in my custom renderer. ( I neigther want to write java script in metaContainer of document tag nor wants to use resource tag..)
and the handleEvent code is something like this.
function handleEvent()
In this method i want to write the code which pushes my custom event to the queue.
some thing like this..
component = event.getSource();
AdfCustomEvent.queue(component, "customEvent",{payload:component.getSubmittedValue()}, true);
event.cancel();
Usually if use a clientListener then it will call the method { handleEvent(event) } passing event parameter so that we can get the source of that event.
But as i dont want to use the clientEventListener.... as of now... i can't get the component because i don have the event object with my method.
So could any one please letme know , how can i queue my custom event in to my customcomponent... with out using ClientListeners.
Edited by: mchepuri on Nov 9, 2009 10:04 AM

Hi,
AFAIK, you cannot queue an event to the serverListener without a clientListener.
-Arun

How Achieve timedseries calculations with out using AGO And ToDate function

Hi,,
1)
How Achieve timedseries calculations with out using AGO And ToDate functionion
this question asking in interview ..is it possible..?
if yes please response as soon as possible..
2) i have 2 cloumns Product and value...
client requirement is they need ranks based on Value ..in dashboard .using dashboard prompt..edit box...if user enter any number (ex :5 ) report should show top 5 ranks if he enter 20 should be top 20 ranks..
how to achive this ?
thanks,
raj

Consider yor first question:
1. Yes, we can create timeseries measures without using AGO and TODATE
1. Create ALIAS of fact tabe in the physical layer
2. Join the Time id from the ALIAS fact table with the YAGO_MONTH_ID column from your time dimension table (For calculating Year Ago variants) similarly join with MAGO_MONTH_ID column for Month Ago measures.
3.Pull the ALIAS tables as an additional Logical table source in the Lgical layer
4.Keep the mapping of the columns from the ALIAS table as its is
5. For e.g If you pick Revenue from the Year Ago Alias table it will give you the "Prior Year Revenue"
See if this helps you

How to display the alv report blocks wise with out using the blocked alv

Hi
How to display the alv report with out using the blocked alv function module.
Thanks
Chinnu

see this Standard Program
RPR_ABAP_SOURCE_SCAN

Last 10 records of a table with out using count

How can i get last 10 records of a table with out using count() method? if there is some page size(eg 10) , and if we want last page. is it posible without ount()? if posible how?
Message was edited by:
user480375

"is there any other way without nesting?"
Not correctly, no. What is your problem with nesting? Nested queries are not inherently slower than unnested queries. In some cases, such as this, they are the only correct way to do the query. Even an analytic version of the Top N needs to be nested because:
SQL> SELECT object_name
2 FROM t
3 WHERE ROW_NUMBER() OVER (ORDER BY object_name DESC) < 11
4 /
WHERE ROW_NUMBER() OVER (ORDER BY object_name DESC) < 11
ERROR at line 3:
ORA-30483: window functions are not allowed hereTTFN
John

How to get the inserted row primary key with out using select statement

how to return the primary key of inserted row ,with out using select statement
Edited by: 849614 on Apr 4, 2011 6:13 AM

yes thanks to all ,who helped me .its working fine
getGeneratedKeys
String hh = "INSERT INTO DIPOFFERTE (DIPOFFERTEID,AUDITUSERIDMODIFIED)VALUES(DIPOFFERTE_SEQ.nextval,?)";
          String generatedColumns[] = {"DIPOFFERTEID"};
          PreparedStatement preparedStatement = null;
          try {
               //String gen[] = {"DIPOFFERTEID"};
               PreparedStatement pstmt = conn.prepareStatement(hh, generatedColumns);
               pstmt.setLong(1, 1);
               pstmt.executeUpdate();
               ResultSet rs = pstmt.getGeneratedKeys();
               rs.next();
//               The generated order id
               long orderId = rs.getLong(1);

Editing ABAP Program with out using ABAP Editor

Similar Messages

Maybe you are looking for