Call transaction doubt?

hi experts,
I want to call a transaction and to invoke a function code in the called transaction without any user interaction. Is it possible to use call transaction "Tcode" statement and pass a fuction code along with it. else suggest me how to over come this problem.
with regards,
James....
valuable answers will be rewarded..........

this is one more addtion of the CALL TRANSACTION statement
... USING bdc_tab [bdc_options]
Effect
Use this addition to pass an internal table bdc_tab of row type BDCDATA from the ABAP Dictionary to a dialog transaction. The additions bdc_options control the batch input processing. When a transaction with addition USING is called, the system field sy-binpt is set to value "X" in the called program - while this transaction is running, no other transaction can be called with this addition.
The internal table bdc_tab is the program-internal representation of a batch input session and must be filled accordingly. The structure BDCDATA has the components shown in the table below.
Component Description
PROGRAM Name of the program of the called transaction
DYNPRO Number of the dynpro to be processed
DYNBEGIN Flag for the beginning of a new dynpro (possible values are "X" and " ")
FNAM Name of a dynpro field to be filled or batch input control statement, for example, to position the cursor
FVAL Value to be passed to the dynpro field or to the control statement
Using the internal table bdc_tab, you can provide any number of screens of the called transaction with input and user actions.
System Fields
sy-subrc Description
0 The batch input processing of the called transaction was successful.
< 1000 Error in the called transaction. If within the transaction a message was sent, you can receive it using the addition MESSAGES.
1001 Error in batch input processing.
Note
Outside of ABAP Objects you can specify the additions AND SKIP FIRST SCREEN and USING together. However, this does not make sense, because the addition AND SKIP FIRST SCREEN is desigend only to fill the mandatory input fields using SPA/GPA parameters, while the batch input table specified with USING controls the entire transaction flow including the display of the screens.
Example
Call of the Class Builder (transaction SE24) and display of class CL_SPFLI_PERSISTENT. The internal table bdcdata_tab contains the input for the batch input processing of the first dynpro (1000) of the transaction. Using structure opt, the batch input processing is set to suppress the first screen and to display the next screen in the standard size.
DATA class_name(30) TYPE c VALUE 'CL_SPFLI_PERSISTENT'.
DATA: bdcdata_wa TYPE bdcdata,
bdcdata_tab TYPE TABLE OF bdcdata.
DATA opt TYPE ctu_params.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSEOD'.
bdcdata_wa-dynpro = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'SEOCLASS-CLSNAME'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'SEOCLASS-CLSNAME'.
bdcdata_wa-fval = class_name.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=CIDI'.
APPEND bdcdata_wa TO bdcdata_tab.
opt-dismode = 'E'.
opt-defsize = 'X'.
CALL TRANSACTION 'SE24' USING bdcdata_tab OPTIONS FROM opt.

Similar Messages

Doubt in uploading using call transaction method

hi all
i am uploading f-29 in call transaction method .. i have a problem in currency field, the currency field is not picking up it shows a error that input field is longer than screen field .. i have declared currency field as type BSEG-WRBTR(same as screen field ...how to go about
thanks
lokesh

Hi,
When you use the database value directly in your BDC, you will have this issue. It is always advisable to use character fields when doing BDC. so change it to charecter field and try it..
Regards
Sudheer

Simple doubt in BDC Call Transaction Method

Hi Friends,
When i try to call vk13 transaction and pass the screen field values for the second screen and execute it it is displaying properly.But when i try to pass the different value in the bcddata internal table it is changing properly but in the screen it not updating that value.Alawly the screen fields are taking the values passed the first time.But in the internal table which we are oassing to the calltransaction it is changing correctly but not in the corresponding screen fields. Why it is happening so. Can any one help me out of this problem.
Thanks in Advance.

I am not passing through the selection screen . It is like iteractive report. when i select the particular line in the list output then the screen fields should take the values from that selected line. First time when i select the line it is taking properly.
But next time when i select the line the content of the i_bdc_tbl is changing correctly but when it enter in to the transaction it is not taking the values from the i_bdc_tbl. Simply it is displaying the screen fields with the old values. It is not updating the screen fields with the values from the i_bdc_tbl. Why the screen fields are not replaced with the value of i_bdc_tbl? Why it is not getting refreshed with the new values?
Just i am posting the bdc portion of my code here. So you can help me out on this.
AT LINE-SELECTION.
SELECT SINGLE kozgf FROM t685 INTO v_kozgf
 WHERE kschl = wa_report-kschl.
SELECT kolnr kotabnr FROM t682i INTO TABLE i_t682i
 WHERE kozgf = v_kozgf.
SORT i_t682i BY kolnr.
READ TABLE i_t682i WITH KEY kotabnr = wa_report-tabna+1(3)
 TRANSPORTING NO FIELDS.
CHECK sy-subrc = 0.
v_index = sy-tabix.
REFRESH i_bdc_tbl.
l_tabix = '01'.
PERFORM f_vk13.
CONCATENATE 'RV13' wa_report-tabna INTO v_bdc_val_field.
PERFORM bdc_dynpro USING v_bdc_val_field '1000'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'F004-LOW'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=ONLI'.
CREATE DATA v_rec TYPE (wa_report-tabna).
ASSIGN v_rec->* TO <wa_table>.
SELECT SINGLE * FROM (wa_report-tabna) INTO <wa_table>
WHERE kschl = wa_report-kschl AND matnr = wa_report-matnr AND knumh = wa_report-objectid.
CALL FUNCTION 'DDIF_FIELDINFO_GET'
 EXPORTING
 tabname = wa_report-tabna
 TABLES
 dfies_tab = lwa_tabna
 EXCEPTIONS
 not_found = 1
 internal_error = 2
 OTHERS = 3.
READ TABLE lwa_tabna WITH KEY fieldname = 'KSCHL'.
p1 = sy-tabix + 1.
READ TABLE lwa_tabna WITH KEY fieldname = 'MATNR'.
p2 = sy-tabix.
LOOP AT lwa_tabna.
 v_field = lwa_tabna-fieldname.
 IF lwa_tabna-position BETWEEN p1 AND p2.
 ASSIGN COMPONENT lwa_tabna-position OF STRUCTURE <wa_table> TO <fld>.
 PERFORM f_vk13_s2 USING lwa_tabna-fieldname <fld>.
 ENDIF.
ENDLOOP.
PERFORM bdc_field USING 'RV130-DATAM'
 wa_report-fdate_value_new.
PERFORM bdc_field USING 'BDC_OKCODE'
 'ONLI'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'F001'.
CALL TRANSACTION 'VK13' USING i_bdc_tbl
 MODE 'A'.
FORM f_vk13.
DATA: l_tabix(2) TYPE c.
*Condition type
PERFORM bdc_dynpro USING 'SAPMV13A' '0100'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'RV13A-KSCHL'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
PERFORM bdc_field USING 'RV13A-KSCHL'
 wa_report-kschl.
*Key combination
PERFORM bdc_dynpro USING 'SAPLV14A' '0100'.
PERFORM bdc_field USING 'BDC_CURSOR'
 'RV130-SELKZ(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=WEIT'.
PERFORM bdc_field USING 'RV130-SELKZ(01)'
l_tabix = v_index.
SHIFT l_tabix RIGHT.
OVERLAY l_tabix WITH '00'.
CONCATENATE 'RV130-SELKZ(' l_tabix ')' INTO v_bdc_field.
PERFORM bdc_field USING v_bdc_field
 'X'.
ENDFORM. "f_vk13
 FORM BDC_DYNPRO
 This form accepts the program name and screen number
 and places the values into the I_BDC_TBL internal table.
FORM bdc_dynpro USING program dynpro.
CLEAR wa_bdc_tbl.
wa_bdc_tbl-program = program.
wa_bdc_tbl-dynpro = dynpro.
wa_bdc_tbl-dynbegin = 'X'.
APPEND wa_bdc_tbl TO i_bdc_tbl.
ENDFORM. "BDC_DYNPRO
 FORM F_BDC_FIELD
 This form accepts the field name and the corresponding value
 for that field and places them into the I_BDC_TBL internal table.
FORM bdc_field USING fnam fval.
CLEAR wa_bdc_tbl.
MOVE fnam TO wa_bdc_tbl-fnam.
MOVE fval TO wa_bdc_tbl-fval.
APPEND wa_bdc_tbl TO i_bdc_tbl.
ENDFORM. "BDC_FIELD
*& Form f_vk13_s2
 text
--> p1 text
<-- p2 text
FORM f_vk13_s2 USING p_fieldname p_fld.
CONCATENATE wa_report-tabna '-' p_fieldname INTO v_bdc_val_field.
CHECK NOT p_fld IS INITIAL.
PERFORM bdc_field USING v_bdc_val_field p_fld.
ENDFORM. " f_vk13_s2
Thanks.

Difference between call transaction and session method

Hello Experts.
i have one doubt.
suppose if we have 100 records to upload, and we got an error in 55 record. In this case what will call trans will do and what will session will do.
i mean the call trans will process 56th record or not . will it stop at 55 itself. What will session will do in this case.
thank you so much for all the replies.

Hi shiva,
In the Call transaction Method,
It will process all the records if the Update Mode is 'N', it will store all the error messages in BDCMSGCOLL structure. The errored records would be stored in that structure.
In Session Method,
It stops in the 55th error record, it wont move further.
Edited by: Raj on May 21, 2008 9:23 PM

Problem with "Call Transaction" which calls a view cluster

Hi Colleagues ,
I have a rare issue with the call transaction , here is the use case for it :
1> I call a transaction(calls a screen X) in a report ,
2> I have a button in the screen , which calls another transaction(calls a screen X2) .
3> On the screen X2 i have another button which calls transaction (calls the view cluster ).
problem :
i'm not able to see the navigation pane in the view cluster on the left. its missing .
but when the view cluster is called direclty , i'm able to see the navigation pane in the view cluster ..
My initial doubt was , is this the problem with nesting of 'Call Transaction' calls ????
please answer the thread , i have to fix this ASAP.
regards,
Dilip

problem solved.

How to use call transaction stmt from webdynpro application

Hi Expers,
Can I use call transaction 'tcode' in my webdynpro application, I have tried in my application but i am getting short dump saying
Error analysis+
An exception occurred that is explained in detail below.The exception, which is assigned to class'CX_SY_SEND_DYNPRO_NO_RECEIVER', was not caught and therefore caused a runtime error. The reason for the exception is: During background processing, the system attempted to send a screen to a user. Current screen: "SAPLMGMM " 0060.
I haven't used any more statements in my application am sure from my application side everything perfect. but I have seen a screen shot
with SAP screen in webbrowser.
Please help me out if you are not clear abt my doubt please ask me for clear idea.
Thanks in advance
Phalani M

Hello,
Since you can't use the call transaction command in web dynpros components, I suggest you to create a report and fill a BDC table on this and use the call transaction in this report.
So, in your web dynpro component you can use a command SUBMIT to create a job in background.
DATA: number TYPE tbtcjob-jobcount,
 name TYPE tbtcjob-jobname VALUE 'JOB_TEST',
 print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
 jobname = name
IMPORTING
 jobcount = number
EXCEPTIONS
 cant_create_job = 1
 invalid_job_data = 2
 jobname_missing = 3
 OTHERS = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
 SPOOL PARAMETERS print_parameters
 WITHOUT SPOOL DYNPRO
 VIA JOB name NUMBER number
 AND RETURN.
IF sy-subrc = 0.
 CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
 jobcount = number
 jobname = name
 strtimmed = 'X'
 EXCEPTIONS
 cant_start_immediate = 1
 invalid_startdate = 2
 jobname_missing = 3
 job_close_failed = 4
 job_nosteps = 5
 job_notex = 6
 lock_failed = 7
 OTHERS = 8.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
ENDIF.
Regards.

Call transaction (MF60) with variant

hi
in user will save some variant of the TCODE : MF60, and will put they in job what use SM36 to set job schedule.but the resule message can't be know in BG work.
i want to write a report to run the Transaction (MF60) and to save message with abap application log.
first:
how to find the Transaction contain variant?
second:
if i use abap code: CALL transaction in report,how to set variant to transaction.
three:
i know the command:SUBMIT will call from VARIANT:
but MF60's report is RMPU_SEL_SCREEN,but this report have two transaction: MF60,MF63.
how to set Transaction to this RMPU_SEL_SCREEN.
four:
i know the SM36 will set variant to TCODE,how to open job in ABAP.
thank you very much!

in my company,users will create themselves varaints about MF60.
and they put variants in job schedule (use SM36 ) in bg work at night.
so when these job is over,the last message don't show for they.
they doubt about it and they will spent lot time to get what oneself document for last genearate.
i want to write a report and put this report in job schedule to run MF60.
and get last message for call transaction in abap appliacation log.
next day users just use TCODE SLG1 to view last night run MF60 result.
so first i must get all MF60 of variant what will be run and get message
when this transancations is over.save message in database!
thank you very much for your help!

Can we use Call transaction and session method in same program ?

Hi experts,
Is it suggested to use call Transaction and session method in the same Program ?
i have a doubt , why cant we use multiple call transactions in same program instead of session method if we have multiple transaction updations ?

Hi Dengyong Zhang,
we can use the call transation and session method in same program.
However for better performance it's benificial to use call trasaction method of BDC. but if u want to upload very large amount of data then Session method is more preferable to use.
Session method is one of the method of BDC.
U can also use BAPI to upload the data in SAP but it's a different concept than BDC. Performance wise BAPI is more advantageous than BDC.

Call transaction and session method error

hi,
suppose i have 100 records, there is an error in 91 record, then my doubt is up to 90 records data is process to database or not?
Please clear doubt
1. if it is call transaction,
2.if it is session method.

hi,
in session method if u go for fore ground process it will process record by record
suppose if error record is entered it doesnt proceed further, u had to enter correct record
then it allows u to proceed furtherafter procesing all the records it asks u to save
then all records get stored uin data base tables.
suppose if u go for back ground process in error mode,
all the records get processed, except the error record.
in call transaction,
wen ever error record occurs it wont proceed further untill correct record is entered,
finally all the records is processed it will ask u to save then only records get saved in data base.
regards
siva

Alternatine to call Transaction.

Hi All,
Need a Solution to call se38 with a program name 'ZTEST' which skips the first screen.
I tried using
SET PARAMETER ID 'RID' FIELD 'ZTEST'
CALL transaction 'SE38' AND SKIP FIRST SCREEN .
But unable to skip the first screen and display the report.
Thanks & Regards,
Santosh

HI ,
i think for call transaction alternative is SUBMIT so
y can;t u try using SUBMIT if any doubt let me know .
SUBMIT
Basic forms:
1. SUBMIT rep.
2. SUBMIT (name).
Extras:
1. ... LINE-SIZE col
2. ... LINE-COUNT line
3. ... TO SAP-SPOOL List output to the SAP spool database
4. ... USING SELECTION-SCREEN scr
5. ... VIA SELECTION-SCREEN
6. ... AND RETURN
7. ... EXPORTING LIST TO MEMORY
8. ... USER user VIA JOB job NUMBER n
9. ...Various additions for passing parameters to rep
10. ... USING SELECTION-SETS OF PROGRAM prog
Effect
Calls report rep.
The system leaves the active program and starts the new report rep. In basic form 2, you can specify the name of the report in the field name. You must specify the name in uppercase, otherwise a runtime error occurs.
Note
·     You can only start programs with type '1' using SUBMIT. If the program has a different type, the system triggers a runtime error.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition 1
... LINE-SIZE col
Effect
The list generated by the report has the line width col.
Addition 2
... LINE-COUNT line
Effect
The list generated by the report has line lines per page.
Addition 4
... USING SELECTION-SCREEN scr
Effect
When you execute the report, the system uses the selection screen number that you specify in the scr field. This must be a selection screen defined using the SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN statements.If you omit the addition, the system uses the standard selection screen 1000.
This addition allows you to start the same report in different situations, using a different selection screen each time.
Notes
1.     The addition VIA SELECTION SCREEN determines whether the report is processed in the foreground or the background.
2.     What happens if the required screen does not exist or is not a selection screen?
Screen 1000:
If you want to use the standard selection screen (... USING SELECTION-SCREEN 1000 or do not specify a ... USING SELECTION-SCREEN) addition, the system does not process a selection screen.
Other selection screens:
The system triggers a runtime error.
Addition 5
... VIA SELECTION-SCREEN
Effect
The selection screen is displayed. In this case, the selection screen is displayed again after the report list has been displayed. The values entered by the user remain displayed.
Addition 6
... AND RETURN
Effect
Returns to the calling transaction or program after the called program has been executed. SUBMIT ... AND RETURN creates a new internal session.
Addition 7
... EXPORTING LIST TO MEMORY
Effect
Does not display the output list of the called report, but saves it in ABAP memory and leaves the called report immediately. Since the calling program can read the list from memory and process it further, you need to use the addition ... AND RETURN . Also, since the called report cannot be requested for printing, the addition ... TO SAP-SPOOL is not allowed here. In addition, you must not assign a function code to the ENTER key in the current GUI status. The saved list is read from the SAP memory using the function module 'LIST_FROM_MEMORY' and can then be saved to the database using EXPORT, for example. You can process this list further with the function modules 'WRITE_LIST', 'DISPLAY_LIST' ... of the function group "SLST".
Addition 8
... USER user VIA JOB job NUMBER n
Effect
Schedules the specified report in the job specified by the job name job and the job number n. The job runs under the user name user and you can omit the addition USER user. The assignment of the job number occurs via the function module JOB_OPEN (see also the documentation for the function modules JOB_CLOSE and JOB_SUBMIT). This addition can only be used with the addition ...AND RETURN.
Note
When scheduling a report with the SUBMIT ... VIA JOB job NUMBER n statement, you should always use the addition ...TO SAP-SPOOL to pass print and/or archive parameters. Otherwise, default values are used to generate the list and this disturbs operations in a production environment.
SY-SUBRC = 0:
Job scheduled successfully
SY-SUBRC = 4:
Job scheduling terminated by user
SY-SUBRC = 8:
Error in job scheduling (JOB_SUBMIT)
SY-SUBRC = 12:
Error in internal number assignment
Addition 10
... USING SELECTION-SETS OF PROGRAM prog
Effect
Uses variants of the program prog when executing the program rep.
Note
Important
The programs prog and rep must have the same SELECT-OPTIONS and PARAMETERs. Otherwise, variants of the program prog may be destroyed.
Note
When using this addition, the specified variant vari of the program prog is taken in USING SELECTION-SET vari. On the other hand, all variant-related actions on the selection screen of rep (Get, Save as variant, Display, Delete) refer to the variants of prog.
Example
SUBMIT REPORT01
       VIA SELECTION-SCREEN
       USING SELECTION-SET 'VARIANT1'
       USING SELECTION-SETS OF PROGRAM 'REPORT00'
       AND RETURN.
Effect
Executes the program REPORT01 with the variant VARIANT1 of the program REPORT00.
Exceptions
Non-Catchable Exceptions
·     Cause: The specified program was not found.
Runtime Error: LOAD_PROGRAM_NOT_FOUND
·     Cause: Invalid value passed to a selection with SIGN.
Runtime Error: SUBMIT_WRONG_SIGN
·     Cause: The specified program is not a report.
Runtime Error: SUBMIT_WRONG_TYPE
·     Cause: More than one value passed to a report parameter.
Runtime Error: SUBMIT_IMPORT_ONLY_PARAMETER
·     Cause: Table passed to a selection with WITH sel IN itab that has an unexpected structure.
Runtime Error: SUBMIT_IN_ITAB_ILL_STRUCTURE
Additional help
Starting Executable Programs (Reports)
THx

Whts the difference between call transaction and session

hi,
can u plz tell me the differnces between call transaction method in BDC and session method.
my doubt is even the call transaction method also can me scheduled using job scheduler then why do we need session method

Hi
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
Reward points for useful Answers
Regards
Anji

Unable to Capture ALV output in an Internal Table, after CALL TRANSACTION

Dear all,
My requirement is to run multiple materials in T-code CK86_99 but as we know CK86_99 is only adequate to one material at a time.
So, I want to capture the Output of the T-code in my Internal table with respect to all the Material Numbers I use in the Select-Options of my Z Program.
Below is the Code I developed so far, but the Class
cl_salv_bs_runtime_info=>get_data_ref(
 IMPORTING r_data = lf_ref ).
is not capturing the Ouput...
Please have a look and enlighten me how it could be solved.
TABLES : mara.
DATA : BEGIN OF wa_mara,
matnr TYPE mara-matnr,
END OF wa_mara.
DATA: it_bdcdata TYPE TABLE OF bdcdata,
 wa_it_bdcdata LIKE LINE OF it_bdcdata,
 it_mara LIKE TABLE OF wa_mara.
* BELNR(10).
FIELD-SYMBOLS:<fs_tab> TYPE ANY TABLE,
<fs_line> TYPE any.
DATA:lf_ref TYPE REF TO data,
 lf_ref1 TYPE REF TO data.
SELECT-OPTIONS so_matnr FOR mara-matnr.
PARAMETERS p_werks LIKE t001w-werks.
*BELNR = 'Z92'. " Give Document Number here
SELECT matnr FROM mara INTO TABLE it_mara WHERE matnr IN so_matnr.
DATA opt TYPE ctu_params.
LOOP AT it_mara INTO wa_mara.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-program = 'SAPMKKB0'.
wa_it_bdcdata-dynpro = '0300'.
wa_it_bdcdata-dynbegin = 'X'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_CURSOR'.
wa_it_bdcdata-fval = 'KKB0-MATNR'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'KKB0-MATNR'.
wa_it_bdcdata-fval = wa_mara-matnr.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_CURSOR'.
wa_it_bdcdata-fval = 'KKB0-WERKS'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'KKB0-WERKS'.
wa_it_bdcdata-fval = p_werks.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_OKCODE'.
wa_it_bdcdata-fval = 'OSNY'."'ONLI'."=CRET'.
APPEND wa_it_bdcdata TO it_bdcdata.
* CLEAR wa_it_bdcdata.
* wa_it_bdcdata-program = 'SAPLKKRSOO'.
* wa_it_bdcdata-dynpro = '0100'.
* wa_it_bdcdata-dynbegin = 'X'.
* APPEND wa_it_bdcdata TO it_bdcdata.
* CLEAR wa_it_bdcdata.
* wa_it_bdcdata-fnam = 'BDC_OKCODE'.
* wa_it_bdcdata-fval = 'BACK'."=CRET'.
* APPEND wa_it_bdcdata TO it_bdcdata.
* CLEAR wa_it_bdcdata.
* wa_it_bdcdata-program = 'SAPMKKB0'.
* wa_it_bdcdata-dynpro = '0300'.
* wa_it_bdcdata-dynbegin = 'X'.
* APPEND wa_it_bdcdata TO it_bdcdata.
* CLEAR wa_it_bdcdata.
* wa_it_bdcdata-fnam = 'BDC_OKCODE'.
* wa_it_bdcdata-fval = 'EXIT'."=CRET'.
* APPEND wa_it_bdcdata TO it_bdcdata.
opt-dismode = 'N'.
cl_salv_bs_runtime_info=>set(
 EXPORTING display = abap_false
 metadata = abap_true
data = abap_true ).
CALL TRANSACTION 'CK86_99' USING it_bdcdata OPTIONS FROM opt.
TRY.
cl_salv_bs_runtime_info=>get_data_ref(
 IMPORTING r_data = lf_ref ).
 ASSIGN lf_ref->* TO <fs_tab>.
 CATCH cx_salv_bs_sc_runtime_info.
 MESSAGE 'Unable to retrieve ALV data' TYPE 'E'.
ENDTRY.
cl_salv_bs_runtime_info=>clear_all( ).
IF <fs_tab> IS ASSIGNED.
 CREATE DATA lf_ref1 LIKE LINE OF <fs_tab>.
 ASSIGN lf_ref1->* TO <fs_line>.
ENDIF.
*LOOP AT <FS_TAB> ASSIGNING <FS_LINE>.
*ENDLOOP.

Hi Abhay,
 If you go to Transaction code SE93, enter the tcode "CK86_99" and click display, you may see the default value for transaction is "KKBB" and the screen field for P_SCREEN = 0300, P_TCODE = ck86_99.
 You may need to copy the transaction code "KKBB" and go to SE93 again, enter the tcode for "KKBB" then click display, now you may see the program name is "RKKB1000".
 Hope this answer your question.
Thanks
Hock Lin

Call transaction error handling

how to maintain the log i.e sucess/failures like below.
Line No. Success/ Failure Document No Error Details
1 S Doc 740000001
2 S Doc 740000002
3 F Co- code does not exist
4 F GL Account does not exist
I'm getting only one last document no: but i need all the documents to be displayed i.e either success/failures.
below is my code.
TYPES: BEGIN OF ty_filedata,
 bukrs TYPE bukrs, "Company code
 blart TYPE blart, "Document type
 bldat TYPE char10, "Document Date
 budat TYPE char10, "Posting date
 xblnr TYPE xblnr, "Reference
 bktxt TYPE bktxt, "Document Header text
 waers TYPE waers, "Currency
 newbs TYPE bschl, "Posting Key for the next line item
 wrbtr TYPE char10, "Amount
 zuonr LIKE bsik-zuonr, "Assignment
 sgtxt TYPE sgtxt, "Text
 newko TYPE hkont, "Account for the next line item
 END OF ty_filedata.
TYPES: BEGIN OF ty_detail_log,
 item_no TYPE i, " Item line no.
 status(1) TYPE c, " Status - success/failure
 doc_no TYPE bkpf-belnr," Document No.
 message TYPE string, " Message
 END OF ty_detail_log.
*& DATA declaration of internal tables
 Internal Table declaration for excel data
DATA: it_itab TYPE STANDARD TABLE OF alsmex_tabline INITIAL SIZE 0,
 Internal Table declaration for upload data
 it_upload TYPE STANDARD TABLE OF ty_filedata INITIAL SIZE 0,
 Internal Table Declaration for BDCDATA
 it_bdcdata TYPE STANDARD TABLE OF bdcdata,
 Internal Table Declaration for BDCMSGCOLL
 it_bdcmsgcoll TYPE STANDARD TABLE OF bdcmsgcoll,
 Internal Table Declaration for FILENMAE
 lf_fname TYPE rlgrap-filename.
 t_err_log TYPE STANDARD TABLE OF ty_err
 INITIAL SIZE 0, " table for validation error log
 t_DETAIL_LOG TYPE STANDARD TABLE OF TY_DETAIL_LOG.
 C_MSGNO TYPE BDC_MNR VALUE '312',
*& DATA declaration of work area
 Work Area declaration for Excel Data
DATA: w_itab TYPE alsmex_tabline,
 Work Area declaration for upload data
 w_upload TYPE ty_filedata,
 Work Area declaration for upload data
 w_upload_n TYPE ty_filedata,
 Work Area declaration for upload data
 w_bdcdata TYPE bdcdata,
 Work Area declaration for upload data
 w_bdcmsgcoll TYPE bdcmsgcoll,
 w_detail_log TYPE ty_detail_log.
*& SELECTION-SCREEN
SELECTION-SCREEN: BEGIN OF BLOCK bk1 WITH FRAME TITLE text-001.
PARAMETERS:p_file TYPE rlgrap-filename. " MODIF ID G1.
SELECTION-SCREEN: END OF BLOCK bk1.
*& AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 dynpro_number = syst-dynnr
 CHANGING
 file_name = p_file
 EXCEPTIONS
 mask_too_long = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
*& START-OF-SELECTION
START-OF-SELECTION.
DATA: lw_itab TYPE alsmex_tabline.
lf_fname = p_file.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 filename = lf_fname
 i_begin_col = '1'
 i_begin_row = '6'
 i_end_col = '12'
 i_end_row = '999'
 TABLES
 intern = it_itab[]
 EXCEPTIONS
 inconsistent_parameters = 1
 upload_ole = 2
 OTHERS = 3.
IF sy-subrc <> 0.
*MESSAGE S205(ZF_COMMON_MSGS_FIN1) DISPLAY LIKE C_E.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ELSE.
IF it_itab IS NOT INITIAL.
 SORT it_itab BY row col.
DELETE it_itab WHERE row LT 6.
 LOOP AT it_itab INTO lw_itab.
 w_itab = lw_itab.
 AT NEW row.
 CLEAR: w_upload.
 ENDAT.
 CASE w_itab-col.
 WHEN '0001'.
 w_upload-bukrs = w_itab-value.
 WHEN '0002'.
 w_upload-blart = w_itab-value.
 WHEN '0003'.
 w_upload-bldat = w_itab-value.
 WHEN '0004'.
 w_upload-budat = w_itab-value.
 WHEN '0005'.
 w_upload-xblnr = w_itab-value.
 WHEN '0006'.
 w_upload-bktxt = w_itab-value.
 WHEN '0007'.
 w_upload-waers = w_itab-value.
 WHEN '0008'.
 w_upload-newbs = w_itab-value.
 WHEN '0009'.
 w_upload-wrbtr = w_itab-value.
 WHEN '0010'..
 w_upload-zuonr = w_itab-value.
 WHEN '0011'.
 w_upload-sgtxt = w_itab-value.
 WHEN '0012'.
 w_upload-newko = w_itab-value.
 ENDCASE.
 AT END OF row.
 APPEND w_upload TO it_upload.
 CLEAR: w_upload.
 ENDAT.
 ENDLOOP.
*endif.
ENDIF.
DATA: lw_upload TYPE ty_filedata,
 lv_lines TYPE sy-tabix,
 lv_index TYPE sy-tabix.
DESCRIBE TABLE it_upload LINES lv_lines.
LOOP AT it_upload INTO lw_upload.
 lv_index = sy-tabix.
 w_upload = lw_upload.
 IF NOT w_upload-bukrs IS INITIAL.
 IF lv_index GT 1.
 CALL TRANSACTION 'FB01' USING it_bdcdata
 MODE 'N' UPDATE 'S' MESSAGES INTO it_bdcmsgcoll.
 PERFORM fr_format_message_text.
 REFRESH: it_bdcdata.
 ENDIF.
 PERFORM bdc_dynpro USING 'SAPMF05A' '0100'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'BKPF-XBLNR'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_field USING 'BKPF-BLDAT'
 w_upload-bldat.
 PERFORM bdc_field USING 'BKPF-BLART'
 w_upload-blart.
 PERFORM bdc_field USING 'BKPF-BUKRS'
 w_upload-bukrs.
 PERFORM bdc_field USING 'BKPF-BUDAT'
 w_upload-budat.
 PERFORM bdc_field USING 'BKPF-WAERS'
 w_upload-waers.
 PERFORM bdc_field USING 'BKPF-XBLNR'
 w_upload-xblnr.
*perform bdc_field using 'FS006-DOCID'
 PERFORM bdc_field USING 'RF05A-NEWBS'
 w_upload-newbs.
 PERFORM bdc_field USING 'RF05A-NEWKO'
 w_upload-newko.
 ENDIF.
 IF lv_index NE lv_lines.
 lv_index = lv_index + 1.
 READ TABLE it_upload INTO w_upload_n INDEX lv_index.
 PERFORM bdc_dynpro USING 'SAPMF05A' '0300'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'BSEG-WRBTR'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_field USING 'BSEG-WRBTR'
 w_upload-wrbtr.
 PERFORM bdc_field USING 'RF05A-NEWBS'
 w_upload_n-newbs.
 PERFORM bdc_field USING 'RF05A-NEWKO'
 w_upload_n-newko.
 ELSE.
 PERFORM bdc_dynpro USING 'SAPMF05A' '0300'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'BSEG-WRBTR'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=BU'.
 PERFORM bdc_field USING 'BSEG-WRBTR'
 w_upload-wrbtr.
 ENDIF.
 PERFORM bdc_dynpro USING 'SAPLKACB' '0002'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'COBL-ANLN1'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=ENTE'.
ENDLOOP.
CALL TRANSACTION 'FB01' USING it_bdcdata
 MODE 'N' UPDATE 'S' MESSAGES INTO it_bdcmsgcoll.
PERFORM fr_format_message_text .
REFRESH: it_bdcdata.
*& Form BDC_DYNPRO
FORM bdc_dynpro USING program dynpro.
CLEAR w_bdcdata.
w_bdcdata-program = program.
w_bdcdata-dynpro = dynpro.
w_bdcdata-dynbegin = 'X'.
APPEND w_bdcdata TO it_bdcdata.
ENDFORM. "BDC_DYNPRO
 Insert field *
FORM bdc_field USING fnam fval.
IF fval <> space.
 CLEAR w_bdcdata.
 w_bdcdata-fnam = fnam.
 w_bdcdata-fval = fval.
 APPEND w_bdcdata TO it_bdcdata.
ENDIF.
ENDFORM. "BDC_FIELD
*& Form fr_format_message_text
FORM fr_format_message_text.
DATA: lf_msg TYPE string.
WRITE:/ sy-uline(125).
FORMAT COLOR 1 INTENSIFIED ON.
WRITE : /1 sy-vline,
 2 text-041 , "'record Number',
 16 sy-vline,
 17 text-042 , " 'success/failure',
 35 sy-vline,
 36 text-043, " 'document no',
 55 sy-vline,
 56 text-044, "'Error details',
 125 sy-vline.
WRITE:/ sy-uline(125).
LOOP AT it_bdcmsgcoll INTO w_bdcmsgcoll.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 id = w_bdcmsgcoll-msgid
 lang = sy-langu
 no = w_bdcmsgcoll-msgnr
 v1 = w_bdcmsgcoll-msgv1
 v2 = w_bdcmsgcoll-msgv2
 v3 = w_bdcmsgcoll-msgv3
 v4 = w_bdcmsgcoll-msgv4
 IMPORTING
 msg = lf_msg
 EXCEPTIONS
 not_found = 1
 OTHERS = 2.
 IF sy-subrc EQ 0.
 WRITE:/01 sy-vline,
 02 sy-tabix,
 16 sy-vline,
 17 w_bdcmsgcoll-msgtyp,
 35 sy-vline,
 36 w_bdcmsgcoll-msgv1,
 55 sy-vline,
 56 lf_msg,
 125 sy-vline.
 WRITE:/ sy-uline(125).
 ENDIF.
ENDLOOP.
ENDFORM. "fr_format_message_text
Thanks in advance.

Hi Neelima,
Just put the following code within that LOOP...ENDLOOP statement.
LOOP AT it_upload INTO lw_upload.
CALL TRANSACTION 'FB01' USING it_bdcdata
MODE 'N' UPDATE 'S' MESSAGES INTO it_bdcmsgcoll.
PERFORM fr_format_message_text .
REFRESH: it_bdcdata.
ENDLOOP.
Regards,
R.Nagarajan.
We can -

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

VALUES not getting passed in t.code 'FMY3' VIA call transaction 'FMY3'

hi guru's,
i have created a ALV report for funds precommitment,when i click the document number,the respective document is not opening
i have coded like this
IF selfield-value IS NOT INITIAL.
        READ TABLE final INDEX selfield-tabindex.
        SET PARAMETER ID: 'KBL' FIELD final-belnr,
                          'KBP' FIELD final-blpos.
        CALL TRANSACTION 'FMY3' AND SKIP FIRST SCREEN.
      ENDIF.
the transaction is called,but with empty value in the field and the document is not opening....please help me with this regard...
    thanks in advance,
regards,
Balaji.S

Hello Venkat.O,
i have a similar problem with the overwrite of the memory ID, when calling transaction FMY3. In the code block you mentioned, the system gets the right value from the memory ID, that i've set before calling the transaction. But i found that after that the system runs in the include LFMFRO01, the code
MODULE init_suppress OUTPUT.
IF status2 = st2_app.                "/Genehmigen/Ablehnen
Lesen aus Memory: wird in WF-Methode 'APPROVE' gefüllt
    IMPORT wfdata TO g_f_wfdata FROM MEMORY ID con_memid_wf.
    IF NOT g_f_wfdata-belnr IS INITIAL.
      IF g_f_wfdata-blpos = space.
        g_f_wfdata-blpos = con_initial_blpos.
      ENDIF.
      kbld-belnr = g_f_wfdata-belnr.
and here the system gets the memory of the last document created and overwrites the selecion-screen field KBLD-BELNR with that value. And the value i had stored in the parameter ID 'MRV', and that the system gets it right in the code you show, is overwritten..
This seems like a bug from SAP, don't you think?
This way the system will always show the last doc. when calling transaction, after setting a parameter ID..

Call transaction doubt?

Similar Messages

Maybe you are looking for