Call transaction inside job

hi all,
I have a call transaction program for tcode ME55, the probleme is when i execute the program directly via se38 to release the sales documents it work fine, on the other hand when i call the program via SM37 nothing will happen.
thanks,
karim

Hi,
What exactly do you want to do by calling t.code me55 ? Upload some data in background or display the transaction to a user only ?
If you want to do a call transaction in background, you will have to pass BDC data to it as well. Then transaction will run with the passed data then. To know what data to pass, simply record your transaction in SHDB T.code and create a program for the BDC.
ME55 is a report, so perhaps you can use SUBMIT with the selection parameters in your program to be able run that program in background.
regards,
Advait

Similar Messages

Call transaction inside Update task

<b>Is it possible to use call transaction inside an update function module?</b>
My requirement is like this.
When I execute LB10 storage units will be created..then we have to go to lt09 and then create a TO's there for all these Storage units..
Now, when I try to call a bdc session from an exit, the storage units are not updated there. so the BDC is getting failed..
To resolve this, I kept all the BDC code in to a Zfunction module and made it an update funtion module. I am calling this function module form the exit IN UPDATE TASK.
But the call transaction is not working....
I have tried with L_TO_CREATE_MOVE_SU inside the Z function module..Still no use..
is there any other way that I can solve this?

Hi,
Calling a FM in Update Task is one of the bundling techniques used in ABAP to avail functionality provided by SAP Update System. Here all database updates are processed at the end of the SAP LUW in contrast to normal FM call where the database updates are done and commited at the time of call (Database LUW). It is necessary to bundle all your database updates in an SAP LUW e.g. all database updates in a transaction (like VA01) should be bundled. Almost all standard SAP transactions use bundling techniques.
This technique separates the dialog process and update process. The dialog part of the transaction can span more than one screen(one dialog step) and can be processsed by more than one dialog work process. A work process is released when the dialog step changes (screen changes) and the work process sends a database commit (called Implicit Database LUW). So with each screen change there is a database commit and database remains in consistent state.
Now when using bundling technique, when a COMMIT WORK is encountered, system ends the dialog process with a dialog work porcess and starts the update process using an update work process.
The dialog step containing the COMMIT WORK is considerd as the last dialog step of the transaction and all the update function modules are processed now in the last dialog step by the update work process though they were called earlier during the earlier dialog steps.
It is necessary to create update FMs to take advantage of this technique. The update FM is created FM by setting the Update moduleradiobutton in the Attributes tab in SE37.
In a normal FM call, if there are database updates (UPDATE, INSERT, MODIFY, DELETE) than database is commited after the FM processing is over as the FM starts its own Database LUW and ends it too.
<b>Reward Points</b>
Regards

Call transaction inside of call function in back ground task

Hi,
Is it possible to use call transaction statemement inside of call function in back ground task. I am getting error if i use the same. Any help will be highly appreciated.

Hi,
I don't think this is possible. The call goes into error in SM58, what you can try to do is after the function is called, you can submit the program RSARFCEX by setting the user name as sy-uname and other parameters as * and set all the checkboxes.
regards,
Advait

Call transaction & LUW

Hi experts !!
I'm traying to delete a shipment and all the shipment's deliveries.
I have made 2 FM with a call transaction inside that delete single shipment and single delivery respectively.
Atthe end of the call transcation the system executes a COMMIT WORK, but i need to commit data when the complete transport (shipment and deliveries) are deleted; if one of the deliveries fail, the other data deleted must be retireved ( with a ROLLBACK WORK ?? ).
How can i make it ?
thanks in advance !!

then update mode or local update task may not help you.
but follow below code and it may have performance issue.
declare one variable
data n type i.
set n as 20
n = 20.
after call transaction
use below logic
do n times.
write your select query.
if sy-subrc eq 0.
exit.
endif.
enddo.
first see the 20 times ,even if you are not getting then increase 30 or 40 times ,see the results.
Thanks
Seshu

Issue in background job for call transaction

Dear All,
I am facing a strange issue with call transaction. I need to add some Purchase requisitons in the APO using Call transactionmethod. It is working fine In All screen mode and No Screen Mode. But when I schedule the program in BAckground processing it is not wokring fine. It is not creating any Purchase requisitioins. When I debug the background Job it is creating Purchase requisitions.
Please find the code below
    DATA: l_wa_params TYPE ctu_params.
    l_wa_params-dismode = l_c_mode.
    l_wa_params-updmode = 'A'.
    l_wa_params-defsize = 'X'.
    l_wa_params-racommit = 'X'.
    CALL TRANSACTION '/SAPAPO/RRP3' USING fp_i_bdcdata OPTIONS FROM l_wa_params
                                        MESSAGES INTO l_i_bdcmsgcoll.

Hi,
I have exactly the same problem with transaction /SAPAPO/RRP5.
Thanks in advance for your help,
Yannick CAREL

Require Job name in SM37 while executing call transaction in background

Hi all,
I am executing a report program, which contains Call transaction.
I have recorded properly. The recording contains background job screen also ( means a separate popup came and i gave the job name and i gave immediately )
When i execute in this program in foreground its creating job,its showing the job in sm37.
But when i execute this program in background, it does not showing the job name in sm37.
Anyone kindly help this out?
Anandhab

Hi,
The job will be created by the step level user.
Try searching again with jobname and * for username.
Regards,
Jovito

Call transaction in Background job

Hi,
I am executing a program in background. In that program I am having a CALL TRANSACTION as below:
CALL TRANSACTION 'ME22'
    USING g_t_bdctab
    MODE 'N'
    UPDATE 'S'
    MESSAGES into g_t_bdcmsg.
But it is not working. The same is working when the program is executed in foreground.
Is this means, we cannot have CALL TRANSACTION in background?
If Yes, then what could be the solution for it?
Thanks,
Pankaj.

Hello Pankaj,
Call transaction works in background.
Provided you are not picking file from presentation server.
If you are picking file from presentation server, place the same file in application server and during background job pick the file from application server then your program works perfectly.
Regards,
Tarun

How to do the job scheduling in BDC Call transaction

Hi Experts,
I've a Query like how to do the job scheduling in BDC Call transaction
If anybody knows the answer please send me the reply.
Thanks.
Regards,
Rekha

Hi ,
any progarm can be scheduled, wether it may be BDC or report thru SM36 Tcode.
But do rememeber that if ur BDC is using GUI_UPLOAD function module, then it wont work , coz the function Gui_upload or GUI_DOWNLOAd wont work in back ground.
If u r going to use OPEN_DATASET , READ dataset ....then it can be scheduled. i.e BDC can work if ur program retrievesz the data from Application server.
Rvert back if any issues,
Reward with poinst if helpful.
Regards,
Naveen

Error in Back ground job schedule for call transaction

Hi Experts ,
I have a Program which as Three BDC in it . 1 - to create contact person , 2- customer 3-sales order
Using call transaction if i run with all screens and no screens it's running fine..
if i schedule it background job
conact and customer works fine but sales order not works ..
can anyone give me the solution ?

Hi Phani and Pavan ,
It works Fine for Back ground anf fore ground i.e ( N and A ) sales order is created here .
but Sales order not created when i schedule it in back ground as
Program - execute in back ground .
sales not created when i schedule it in background job only using SM36 or Program - execute in back ground ?
Edited by: Pradeep Annaiah on Jan 13, 2009 5:29 AM

How to create a background job for call transaction

hi gurus
can any one suggest me
how to create the background job for call transaction.
thank you
regards
kals.

Hi,
Refer
https://forums.sdn.sap.com/click.jspa?searchID=10926107&messageID=889652
Regards
Kiran Sure

BDC Call Transaction - Doc.No not getting generated in Message Internal tab

Dear All,
I am using BDC Call Transaction method for uploading data for transaction, Iam able to successfully capture the Error messages, sucess messages and the transaction number is also displayed for the bdc run in Mode A, but in case of scheduling the job in background, the Error messages are displayed but the transaction number is not captured in the message Internal table( BDCMSGCOLL).
Kindly look into the matter and revert back for any further info.
Regards
Naresh

Hi,
Please try using the following kind of code in 'CALL TRANSACTION'
    opt-dismode = 'E'.     " Exclusive mode
    opt-defsize = 'X'.
    opt-updmode = 'S'.
    opt-nobinpt = ' '.
    CALL TRANSACTION transaction_code USING ft OPTIONS FROM opt
                                                                         MESSAGES INTO t_bdcmsgcoll .
Hope this will work.
Thanks,
Leo

I want in LSMW SAME CODING. THIS IS USING BDC CALL TRANSACTION

REPORT ZXX_BDC_PRA NO STANDARD PAGE HEADING LINE-COUNT 20
                                            LINE-SIZE 150 .
Program Name :ZXX_BDC_PRA                             *
Object Id     :                                        *
Develper Name : praveen                                *
Start Date    : 25.06.07                               *
Description   : uploading flat file to sap system      *
*--structure for Data Uploading.
DATA: BEGIN OF IT_STR ,
        VKORG LIKE RF02D-VKORG,
        VTWEG LIKE RF02D-VTWEG,
        SPART LIKE RF02D-SPART,
        KTOKD LIKE RF02D-KTOKD,
        NAME1 LIKE KNA1-NAME1,
        SORTL LIKE KNA1-SORTL,
        ORT01 LIKE KNA1-ORT01,
        PSTLZ     LIKE KNA1-PSTLZ,
        LAND1 LIKE KNA1-LAND1,
        SPRAS LIKE KNA1-SPRAS,
        END OF IT_STR.
*--Internal Table for Data Uploading.
DATA: ITAB LIKE IT_STR OCCURS 0.
*--Internal Table to sucessfull Records.
DATA:   ITAB1 LIKE IT_STR OCCURS 0.
*--Internal Table to Store Error Records.
DATA:    ITAB2 LIKE STANDARD TABLE OF IT_STR WITH HEADER LINE.
*--Internal Table for Storing the BDC data.
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA:   COUNT TYPE I VALUE 1,
        S VALUE 0, E VALUE 0.
Selection screen *
SELECTION-SCREEN BEGIN OF BLOCK b1
                 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE TYPE IBIPPARMS-PATH.
SELECTION-SCREEN END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
*functionality to use drill down list
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      PROGRAM_NAME = SYST-CPROG
      DYNPRO_NUMBER = SYST-DYNNR
    IMPORTING
      FILE_NAME     = P_FILE.
Start-of-selection *
START-OF-SELECTION.
DATA FILENAME TYPE STRING.
FILENAME = P_FILE.
*-- Form to upload flatfile data into the internal table.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                = FILENAME
      FILETYPE                = 'ASC'
      HAS_FIELD_SEPARATOR     = 'X'
    TABLES
      DATA_TAB                = ITAB
    EXCEPTIONS
      FILE_OPEN_ERROR         = 1
      FILE_READ_ERROR         = 2
      NO_BATCH                = 3
      GUI_REFUSE_FILETRANSFER = 4
      INVALID_TYPE            = 5
      NO_AUTHORITY            = 6
      UNKNOWN_ERROR           = 7
      BAD_DATA_FORMAT         = 8
      HEADER_NOT_ALLOWED      = 9
      SEPARATOR_NOT_ALLOWED   = 10
      HEADER_TOO_LONG         = 11
      UNKNOWN_DP_ERROR        = 12
      ACCESS_DENIED           = 13
      DP_OUT_OF_MEMORY        = 14
      DISK_FULL               = 15
      DP_TIMEOUT              = 16
      OTHERS                  = 17.
*--Generating the BDC table for the fields of the internal table.
LOOP AT ITAB INTO IT_STR.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0107'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'RF02D-KTOKD'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_FIELD       USING 'RF02D-VKORG'
                                  IT_STR-VKORG.
    PERFORM BDC_FIELD       USING 'RF02D-VTWEG'
                                   IT_STR-VTWEG.
    PERFORM BDC_FIELD       USING 'RF02D-SPART'
                                  IT_STR-SPART.
    PERFORM BDC_FIELD       USING 'RF02D-KTOKD'
                                    IT_STR-KTOKD.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0110'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNA1-SPRAS'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_FIELD       USING 'KNA1-NAME1'
                                IT_STR-NAME1.
    PERFORM BDC_FIELD       USING 'KNA1-SORTL'
                                    IT_STR-SORTL.
    PERFORM BDC_FIELD       USING 'KNA1-ORT01'
                                    IT_STR-ORT01.
    PERFORM BDC_FIELD       USING 'KNA1-PSTLZ'
                                  IT_STR-PSTLZ.
    PERFORM BDC_FIELD       USING 'KNA1-LAND1'
                                  IT_STR-LAND1.
    PERFORM BDC_FIELD       USING 'KNA1-SPRAS'
                                    IT_STR-SPRAS.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0120'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNA1-TXJCD'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0125'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNA1-NIELS'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0360'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNVK-NAMEV(01)'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=ENTR'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0310'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNVV-BEGRU'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM BDC_DYNPRO      USING 'SAPMF02D' '0324'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                  'KNVP-PARVW(01)'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                  '=ENTR'.
*--Calling the transaction 'Vd01'.
    CALL TRANSACTION 'VD01' USING BDCDATA MODE 'N' UPDATE 'S'
    MESSAGES INTO MESSTAB.
    PERFORM MESSAGES.
    REFRESH : BDCDATA, MESSTAB.
ENDLOOP.
END-OF-SELECTION.
*--Populating the Success records internal table.
IF ITAB1[] IS NOT INITIAL.
format color 5.
    WRITE: /'SUCCESSFUL RECORDS'.
    format color off.
    LOOP AT ITAB1 INTO IT_STR.
      WRITE:/ IT_STR-VKORG,IT_STR-VTWEG,
              IT_STR-SPART,IT_STR-KTOKD,
              IT_STR-NAME1,IT_STR-SORTL,
              IT_STR-ORT01,
              IT_STR-PSTLZ,
              IT_STR-LAND1,
              IT_STR-SPRAS.
      S = S + 1.
    ENDLOOP.
REFRESH : ITAB1.
    WRITE:/ 'TOTAL RECORDS',S.
ENDIF.
*--Populating the error records internal table.
IF ITAB2[] IS NOT INITIAL.
FORMAT COLOR 3.
    WRITE :/ 'ERRORS RECORDS ARE'.
FORMAT COLOR OFF.
    LOOP AT ITAB2.
      WRITE:/ ITAB2-VKORG,
              ITAB2-VTWEG,
              ITAB2-SPART,ITAB2-KTOKD,
              ITAB2-NAME1,ITAB2-SORTL,
              ITAB2-ORT01,
              ITAB2-PSTLZ,
              ITAB2-LAND1,
              ITAB2-SPRAS.
        E = E + 1.
    ENDLOOP.
REFRESH : ITAB2.
    WRITE: / 'TOTAL RECORDS',E.
REFRESH : ITAB2.
ENDIF.
End of Selection *
END-OF-SELECTION.
TOP-OF-PAGE *
TOP-OF-PAGE.
WRITE:/ SY-ULINE.
WRITE:/10 'REPORT ID',21 SY-REPID,35 'USERNAME',46 SY-UNAME,
60 'SYSTEM DATE',70 SY-DATUM,80 'SYSTEM TIME',90 SY-UZEIT,
100 'PAGE NO',108 SY-PAGNO.
WRITE:/ SY-ULINE.
FOrm to Populate the BDC table.
       Start new screen                                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.                    "BDC_DYNPRO
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> SPACE.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
ENDFORM.                    "BDC_FIELD
*&      Form messages
FORM MESSAGES .
LOOP AT MESSTAB.
    IF MESSTAB-MSGTYP = 'I'.
     WRITE : / MESSTAB-MSGV1.
    ELSEIF
MESSTAB-MSGTYP = 'S'.
      INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB1 .
      COUNT = COUNT + 1.
     WRITE : / MESSTAB-MSGV1.
    ELSEIF
    MESSTAB-MSGTYP = 'E'.
      INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB2.
      COUNT = COUNT + 1.
     WRITE : / MESSTAB-MSGV1.
    ENDIF.
ENDLOOP.
ENDFORM.                    " messages

Hi
Go through the doc and do the same using LSMW
BDC is the way to transfer data by writing a batch input program which can use either session or call transaction method.
LSMW used to transfer data without/less code.
What type of data we transfer using LSMW?
LSMW is best suited for transferring master data.
Actually BDC and LSMW are not comparable at all.
for example LSMW itself can use BDC as a way of mass data transfer.
BDC is a mass data transfer technique via screen logic of existing SAP Data entry transactions. It behaves as if you are manually making thousand of entires into sap system as a background job. And that is probably the reason why BAPI's are preffered over BDC's.
On the other hand LSMW is a tool to facilitate DATA migration from other legacy systems ... It contains step by step procedure for data migration.
Like Managing Data Migration Projects , Creating Source Structures , Mapping Source structures wid Target structures , etc etc
LSMW internally might well be using the following techniqes for data transfer..
1. IDOX
2. Direct Input / BDC
4. BAPI's
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :
LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.
LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.
LSMW mapping is done by SAP while in BDC we have to do it explicitly .
LSMW is basically for standard SAP application while bdc basically for customized application.
Coding can be done flexibly in BDC when compared to LSMW
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as that of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
Reward points for useful Answers
Regards
Anji

BDC call transaction

Hi All,
Help needed. Im facing a problem in BDC call transaction. Im calling a z screen ie i have developed a modulepool prog. In this I have given a zscreen.
Now by using a call transasction method im calling this screen ie the zscreen and i want to update a z table through a flat file.
the system is able to read the flat file and then im able to read it in my internal table. after this im transfering this internal table content in the BDCtable it is even taking it up but then when im calling the command:
CALL TRANSACTION 'YVTRANS' USING jtab MODE 'A' UPDATE 'S' MESSAGES INTO ktab.
It takes me to the screen connected by the ztcode yvtrans. but no data is coming in the screen . and then vn im inserting the content but nothing happens wat could be the probable error.
This is my code:
*& Report ZBDCCALLTXN1
REPORT zbdccalltxn1.
*& Report ZBDCCALLTXN
*REPORT zbdccalltxn.
PREDEFINED TABLES ***
TABLES:zemp.
INTERNAL TABLE TO UPLOAD FLAT FILE ***
DATA:BEGIN OF itab OCCURS 0,
     empno LIKE zemp-empno,
     name LIKE zemp-empname,
     deptno LIKE zemp-deptid,
     deptname LIKE zemp-deptname,
     END OF itab.
INTERNAL TABLE FOR MAPPING USING BDCDATA ***
DATA:BEGIN OF jtab OCCURS 0.
        INCLUDE STRUCTURE bdcdata.
DATA:END OF jtab.
INTERNAL TABLE FOR ERROR CAPTURING USING BDCMSGCOLL ***
DATA:BEGIN OF ktab OCCURS 0.
        INCLUDE STRUCTURE bdcmsgcoll.
DATA:END OF ktab.
FUNCTION MODULE TO UPLAOD FLAT FILE ***
CALL FUNCTION 'UPLOAD'
EXPORTING
    filename                      = 'C:\Documents and Settings\mad13363\Desktop\file.txt'
   filetype                      = 'ASC'
                   HAS_FIELD_SEPARATOR           = ' '
                   HEADER_LENGTH                 = 0
                   READ_BY_LINE                  = 'X'
                   DAT_MODE                      = ' '
                   CODEPAGE                      = ' '
                   IGNORE_CERR                   = ABAP_TRUE
                   REPLACEMENT                   = '#'
                   CHECK_BOM                     = ' '
                   VIRUS_SCAN_PROFILE            =
                 IMPORTING
                   FILELENGTH                    =
                   HEADER                        =
TABLES
    data_tab                      = itab
EXCEPTIONS
   file_open_error               = 1
   file_read_error               = 2
   no_batch                      = 3
   gui_refuse_filetransfer       = 4
   invalid_type                  = 5
   no_authority                  = 6
   unknown_error                 = 7
   bad_data_format               = 8
   header_not_allowed            = 9
   separator_not_allowed         = 10
   header_too_long               = 11
   unknown_dp_error              = 12
   access_denied                 = 13
   dp_out_of_memory              = 14
   disk_full                     = 15
   dp_timeout                    = 16
   OTHERS                        = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ DATA FROM ITAB ***
LOOP AT itab.
REFRESH jtab.
PERFORM sub USING 'YVTRANS' '0100'.
TRANSFER THE DATA FROM INTERNAL TABLE TO APLLICATION ***
PERFORM sub1.
TO SAVE THE RECORDS IN DB SERVER ***
PERFORM sub1 USING 'BDC_OKCODE' 'INSERT'.
LOGIC TO PROVIDE VALIDATIONS USING BDCDATA, DISPLAY MODE, BDCMSGCOLL ***
CALL TRANSACTION 'YVTRANS' USING jtab MODE 'A' UPDATE 'S' MESSAGES INTO ktab.
LOGIC REQUIRED FOR LOG FILE ***
LOOP AT ktab.
    IF ktab-msgtyp = 'I' OR
        ktab-msgnr = 000.
      WRITE:/1 'VENDOR', 15 itab-empno, 30 'INSERTED'.
    ELSEIF ktab-msgtyp = 'E' OR
              ktab-msgnr = '001'.
      WRITE:/1 'VENDOR', 15 itab-empno, 30 'NOT INSERTED'.
    ENDIF.
ENDLOOP.
REFRESH ktab.
ENDLOOP.
FROM TO PASS PRG NAME, SCREEN NUMBER AND FIRST SCREEN ***
FORM sub USING a b.
CLEAR jtab.          " CLEAR REFRESHES WORK AREA
jtab-program = a.
jtab-dynpro = b.
jtab-dynbegin = 'X'.
APPEND jtab.
ENDFORM.                    "SUB
FROM TO PASS FEILD NAME AND FIELD VALUE ***
FORM sub1.
CLEAR jtab.
jtab-fnam = 'zemp-EMPNO'.
jtab-fval = itab-empno.
jtab-program = 'YVTRANS'.
jtab-dynpro = '0100'.
APPEND jtab.CLEAR jtab.
*Passing screen information to BDCDATA
jtab-fnam = 'ZEMP-EMPNAME'.
jtab-fval = itab-name.
jtab-program = 'YVTRANS'.
jtab-dynpro = '0100'.
APPEND jtab.CLEAR jtab.
jtab-fnam = 'ZEMP-DEPTID'.
jtab-fval = itab-deptno.
jtab-program = 'YVTRANS'.
jtab-dynpro = '0100'.
APPEND jtab.CLEAR jtab.
jtab-fnam = 'ZEMP-DEPTNAME'.
jtab-fval = itab-deptname.
jtab-program = 'YVTRANS'.
jtab-dynpro = '0100'.
APPEND jtab.CLEAR jtab.
*Passing BDC_OKCODE to BDCDATA
jtab-fnam = 'BDC_OKCODE'.
jtab-fval = 'INSERT'.
APPEND jtab.CLEAR jtab.
ENDFORM.                                                    "sub1
reward for all useful ans

Hi madhvi,
                   You are using jtab within the form.. i dont think you can use it directly inside ur FORM sub1 without declaring it or without passing it. and it will give you the syntax error.
and please send me the step by step code you have written in editor so that i can check it and can reply you with proper solution'
Thanks ,
Prasanna

Initial Load Error - No generation performed. Call transaction GN_START

Hi Folks,
We are doing middleware configuration for data migration between R3->CRM.Have followed "Best Practies" configuration Guide.
System Using; CRM 2007 and ECC6.0
Issue
While performing initial load, system is throwing the error as
001- No generation performed. Call transaction GN_START
002-Due to system errors the Load is prohibited (check transaction MW_CHECK)!
After calling the transaction GN_START system asks for job scheduling,whereas I have already scheduled it.
A job is already scheduled periodically.
Clicking on 'Continue' will create another job
that starts immediately.
After checking(MW_CHECK),message is displayed as
No generation performed. Call transaction GN_START.
If anybody has encountered the similar issue and has resolved it,their guidence will be greatly appriciated.
Thanks in Advance
VEERA B

Veera,
We also faced the same problem when we have done the upgrade from CRM 4.0 to CRM 2007.
For that you go to SMWP where you can see all the errors related to Middleware with the error message so try to remove the error,
Also pls check in RZ20 and activate the middleware trace tree.
Regards
Vinod

When we have to go for session method, when we have to go for call transact

when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

Data Transfer
During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
Direct Input:
In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
Call Transaction:
In this method you can check the data consistency with the help of screen logic.
Batch Input Session:
In this method data consistency is checked with the help of screen logic.
Direct Input Method
Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
Call Transaction Method
Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
Batch Input Session Method
This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
System à Services à Batch input. Moreover, you can have the session run in the background processing.
Writing a Data Transfer Program
If you want to write a data transfer program, you have to follow the steps mentioned below.
Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
Thirdly, you will have to initialize the SAP data structure.
Fourthly, fill the structure with data, performing any conversions and error checking that are required.
Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
Batch Input Method
Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
The process flows for a batch input are discussed below.
Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
Error Handling in Batch Input Method
It is found that most problems usually fall into one of the following two categories discussed below.
In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
Conclusion
I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
Thanks,
Shankar

Call transaction inside job

Similar Messages

Maybe you are looking for