With out CLOSE_FORM in BDC

Hi experts,
If i write the code with out CLOSE_FORM what will happen to my session in BDC programing , Can any body explain breifly?

Hi Vamsi Krishna,
<b>BDC_CLOSE_GROUP</b>
This Function Module closes the BDC Group. No Parameters.
If we do not use this FM, the session which is opened using BDC_OPEN_GROUP is not marked as closed and so it throws an syntax error.
Hope this resolves your query.
Reward all the helpful answers.
Regards

Similar Messages

How can we handle dateformat from diff countries into india in bdc with out

hi
experts can u help me pz
how can we handle dateformat from diff countries into india in bdc with out chnaging system parameters while uploading.
i.e flatfile date is germanformat
target date is indianformat.
thanks and regords.

use WRITE statement to format date.. along with extension ...
DD/MM/YY
or
DD/MM/YYYY

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.

BDC with out authorization

Hello Frnds
please let me know with out authorization how can we go to particulat transaction,.. how can we implement BDC Prg...?
Thnks

If you call a transaction indirectly, that is from another transaction, the authorization check is not automatically performed. You must use transaction SE97 to set the check indicator check for the entry for the pair of calling and called transaction to ensure that the called transactions are also subject to an authorization check (see SAP Note 358122).
[http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm]

BDC-Log Out from Production Server with out error message

Hi all
I have written one BDC for "FWZZ" transaction.
It is wrking fine in dev & qual.
But in prod it is logging out with out any error message.
what might be the reason??
Thaks & Regards
Swathi

Hi Swathi!
There is little you can do. The BDC can only be shortened by avoiding unecessary steps (each return code needs some time) - but most likely you have already a short way through the transaction.
But maybe there are some field exits / user exits / customizing settings, which start slow database actions. As long as in Dev and Qual aren't so much entries, there wasn't a problem, but now in Prod you have a performance problem.
Make a runtime analysis or a SQL-trace to see what's happening during the call transaction. This should give you an idea, where to look for the slow parts.
Regards,
Christian

To create a Material using BAPI with out passing the material number

Hello Experts,
I am using BAPI_MATERIAL_SAVEDATA to create a material of some Ztype. I am successfully creating a material if I am passing Material Number as input. I want the material number to generated internally.
When I am doing material creation with same input data with out material number using BDC, it is working fine. It is generating the material number.
But, not with the BAPI.
Do, I need to specify this some where in the BAPI to generate the Material number internally? Please let me know.
Please help me in this regard.
Thanks & Regards,
Naresh.

Hi,
Read the BAPI documentation regarding Internal Number range for materials.
When you create material master data, the following fields must always
contain a value in the structure:
o   MATERIAL
    Only external number assignment is supported for the material number
    (MATERIAL). If you want the material number to be assigned
    internally, the method BAPI_MATERIAL_GETINTNUMBER must first be
    called. This method determines an internal number for the material
    to be created. You must enter this internal number in field
    HEADDATA-MATERIAL.
Regards
Vinod

Run the SOST transaction in the Background with, or without, a BDC

Hello all,
I was trying to write a Z-Program that would create a BDC that executed Transaction SOST to resend fax messages. It turned out that I could not record the ALV Grid that contains most of the selection/filter criteria functions because those functions exist in the ALV Grid. Some fields exist above the ALV Grid and could be recorded. I record them and used them in my BDC to filter for the faxes I wished sent. I also used a saved layout for the filtering I would have applied if I cold have recorded the ALV Grid.
All seemed well in testing until I attempted to run my Z-Program in the Background. The Z-Program creates the BDC which in tern executes the resending of faxes. I did not realize that the SOST transaction had a completely different screen layout in the Background. That was something pointed out to me when I was instructed to Record the BDC in "Simulate Background Mode". It doesn't seem like I can enter selection criteria in the Background version of the screen at all.
Has anyone been able to run the SOST transaction in the Background with, or without, a BDC? If not has anyone ever automated the SOST functionality in a Z-Program? Can SOST run in the background at all?
Thanks

Hi,
try to resend it using program RSCONN01.
Regards,
Adrian

How to Insert Data in Database using BCS with out External List

Hi,
How to Insert,Update and Delete User Interface data using business connectivity service with out External List.Please suggest me solution.
Regards,
khadar

Once you've configured the external content type, you can interact with it using the BDC Object Models available to you. You can use server side or client side and interact with the database without an external list.
Check these links:
Server side:
http://msdn.microsoft.com/en-us/library/office/ff464357(v=office.14).aspx#sectionSection3
Client Side: http://msdn.microsoft.com/library/jj164116.aspx
Brandon Atkinson
Blog: http://sharepointbrandon.com

Scenario's With out XI

Hi,
What are the scenarios we can do with out XI as a Middleware.
Regards
Suman

Hi,
You can do this kind of activity for processing the IDOC and pushing it to flat file with using ABAP report..(Function modules are available for it)
In BDC, you normally use to do the recording across the various dilog processing.
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.
With LSMW you can upload the data using file via..BDC, IDOC, BAPI etc
XI is middleware...you can use the other external middelwares also..as EDI, Tibco, Mercator and many more...
If you wish to avoid the middelware then upto certain extent, it can be achieved..for e.g. you could use RFCs as Webservice...then RFC, ALE communications across various SAP systems was already there..but then all will be Point -to point connectivity ....and XI is based on Hub n spoke architecture...
Thanks
Swarup

How to run session method with out having Authorization.

Hi,
A Session is generated in sm35 by other person. The Authorization is in his id. My Question is can i run the session. if yes , how to run with out authorization.

If you want to process in foreground then you can run if you have authorization for SM35 and also for the transaction inside the session . Suppose the BDC session is for ME21 . If you have ME21 authorization you can run the session even if its created by other user .
If you have no auth for ME21 then you cannot run the session in foreground but you can still run in background as in background the authorization of the user in authorization column ( user who created session ) will be checked for ME21 .
Cheers .
Sanjay

Invoice creation with out PO and Item using BAPI_INCOMINGINVOICE_CREATE

Hello,
I have a requirement to create the invoce with out PO number. Is there any chance to create the invoice through BAPI_INCOMINGINVOICE_CREATE with out using PO number and item ( ITEMDATA table ).
Thanks for your support.
Regards
Nags

Hello Burak,
Now i am able to post the docuemnt through BAPI_ACC_DOCUMENT_POST, unable to post the parking docuemnt.
WIth this Function module PRELIMINARY_POSTING_FB01 it very big process to map the fields, because SAP it self
filling lot of fields.
Mean while i have tried the BDC to park the document, but i am getting an error that 'Parking is not possible through batch input'.
RECENTLY ADDED
Now i am getting an issue when we post with the function moduel :PRELIMINARY_POSTING_FB01 , after executing the function module it is giving the document number, but if it fails there is no return table or exeptions to catch the errors . is there any way to over come the problem.
I need to post the document and park the docuemnt.
please suggest.
Thanks & Regards
Nags

How can i get all values from jtable with out selecting?

i have one input table and two output tables (name it as output1, output2). Selected rows from input table are displayed in output1 table. The data in output1 table is temporary(means the dat wont store in database just for display purpose).
Actually what i want is how can i get all values from output1 table to output2 table with out selecting the data in output1 table?
thanks in advance.
raja

You could set the table's data model to be the same:
output2.setModel( output1.getModel() );

How do I delete an old iCloud account with out knowing the password in order to make a new one

i recently sent my phone to my aunt and she reset the phone but my own iCloud is still on the phone how can she change it with out me giving her my password

That is Activation Lock. The only way around it is to log in with your credentials. Go to Settings/iCloud. Turn off Find my iPhone, and then uncheck iCloud. At some point you will have to put in your Apple id credentials (the one you use for app purchases). Then go to Settings/General/Reset and click on Reset All Settings. I would suggest you select Erase All Contents and Settings. That will set the phone back to factory defaults. She can then set the phone up as hers and download the apps she wants with her own Apple id.
Have a nice day.

Put old I life on new computer now I photo dosn't work it says cant open because it may be damaged or incomplete so all my pictures can not be accesed how do I get back to I photo or take what I installed off with out losing all my pictures?

I got a new Mac and was trying to burn from I movie to get it to a disk but new I mac dose not have I DVD . So I had my old I Life 11 disc with I DVD on it and I installed it, when I did this it did something to my I photo I can not open it at all it has a message that reads ,you can't open the application IPhoto because it may be damaged or incomplete . Now I can not get or see any of my photos how do I reverse what I did? can I take that I Life back out and how? with out losing all my pictures? and how do you burn to DVDs now without IDVD?

Diane,
Your photos are in the iPhoto Library. Almost certainly that is intact, so don't worry.
Go to your Home folder and open the folder called Pictures. What you want is in there, iPhoto Library. Don't do anything there, this is just to reassure yourself.
So it is a matter of getting the iPhoto app to work. Apps are in the Applications folder. Find it and trash it.
Next download iPhoto:
https://itunes.apple.com/us/app/iphoto/id408981381?mt=12

With out CLOSE_FORM in BDC

Similar Messages

Maybe you are looking for