Call transaction method in back ground Processing?

HI Friends,
I am working on interface program to post documents of 309 movement type into MIGO transaction .
my program is executing succesfully when i am processing in fore ground.
but when i am processing in background it is giving error .
can any help in this requirement?
*Solution rewarded*

My Program will do transfer Posting from material to material.
when i am executing the program in back ground mode The Program statement call transaction fails with the following error
CALL_TRANSACTION MIGO_TR Return code = 1,001 RECORD: 0
S
Field GODYNPRO-ACTION . is not an input field
S
Field GODYNPRO-REFDOC . is not an input field
S
Field GOITEM-UMMAKTX . is not an input field
S
similar statement when executing in foreground it is posting document succesfully.
kindly revert back for any other information.

Similar Messages

Calling a method in back ground / separate task

Hi,
Can we call a Public Instance Method in either Background task or in separate task?.
If not is there any alternative in ABAP Objects?.
Similiar to what we do in Function module calls like..
CALL FUNCTION func STARTING NEW TASK taskname.
CALL FUNCTION func IN BACKGROUND TASK.
Please guide me.
Thanks,
Satya

Hi, Rich.
As I know, share object also haven't these kind of functionality.
Actually, share object is an enhancement for the import/export concrete mechansim. It import the root class and other conception into the share functionality, and also support more flexiblity access way to the object which has been set to shared.
But it doesn't support the action like run method in the background, as I know.
Thanks

Back Ground Process In OOABAP

Hi all,
How can i process Back ground process on Object oriented
Thanks Rayeez,

Hi Rayeez,
I had a requirement wherein I had to call ALV Grid display in background, here I used OO ABAP and just before creating the custom container I checked IF cl_gui_alv_grid=>offline( ) IS INITIAL.
You can find similar methods for your OO Class and check if it is initial.
<b>Please reward points if it helps.</b>
Regards,
Amit Mishra

Clarification on session and call transaction method.

in session method updation is synchronous and processing is asynchrounous. Session Method can handle Multiple Applications at a time. Where as Call Transaction Method can handle only one Application.
can anyone explain the above lines with a simple example.what is updation and what is meant by processing.how a session handles multiple transactions as we know that sessions cannot be run in parallel?At a time multiple screens are updated in session?how?
in the below thread it has been mentioned "2. If u want to execute the program in future u can create a session and keep it ready so that u can execute it at any point of time. That is not possible in call transaction method."
Session Method & Call Transaction
if we write the bdc program with call transaction , then it can also be used in future ,then what makes the difference.
what is meant by local update?when we need to use local update in call transaction?.

We're not your free code factory. Try yourself, search for existing solutions, and come back here with specific problems.

What are the parameters in Call transaction method?

Hi ABAPER'S,
Please give me what are the parameters in call transaction method?
Thanks,
Prakash

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
Syntax:
CALL TRANSACTION <tcode>
USING <bdc_tab>
MODE <mode>
UPDATE <update>
<tcode> : Transaction code
<bdc_tab> : Internal table of structure BDCDATA.
<mode> : Display mode:
A
Display all
E
Display errors only
N
No display
<update> : Update mode:
S
Synchronous
A
Asynchronous
L
Local update
A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION 'TFCA' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
The MODE Parameter
You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
A Display all. All screens and the data that goes in them appear when you run your program.
N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The UPDATE Parameter
You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
The MESSAGES Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
(This example uses a flight connection that does not exist to trigger an error in the transaction.)
DATA: BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.
BDCDATA-PROGRAM = 'SAPMTFCA'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CARRID'.
BDCDATA-FVAL = 'XX'.
APPEND BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CONNID'.
BDCDATA-FVAL = '0400'.
APPEND BDCDATA.
CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
LOOP AT MESSTAB.
WRITE: / MESSTAB-TCODE,
MESSTAB-DYNAME,
MESSTAB-DYNUMB,
MESSTAB-MSGTYP,
MESSTAB-MSGSPRA,
MESSTAB-MSGID,
MESSTAB-MSGNR.
ENDLOOP.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Return codes:
Value
Explanation
0
Successful
<=1000
Error in dialog program
> 1000
Batch input error
System fields:
Name:
Explanation:
SY-MSGID
Message-ID
SY-MSGTY
Message type (E,I,W,S,A,X)
SY-MSGNO
Message number
SY-MSGV1
Message variable 1
SY-MSGV2
Message variable 2
SY-MSGV3
Message variable 3
SY-MSGV4
Message variable 4
Error Analysis and Restart Capability
Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
write out or save the message table
use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

How to handle the pop-ups in va02 transaction in Call Transaction Method

Hi Experts ,
I am trying to do bdc by call transaction method for va02 transaction but i am getting popups .
How can i handle the popups and for different sales orders i am getting different popups.
is there any way to handle the pop ups dynamically.
Thanks ain advance.

hi,
when you are using BDC then you will have to handle all the popups. this is minus point in using bdc as you need to feed each and every single bit of information so that bdc works fine and if anything misses then your bdc program will get stuck in middle of processing.
best thing is check for function module or BAPIs available for those transactions. For VA02 there is a BAPI available ''BAPI_SALESORDER_CHANGE''. Try using this BAPI and if this BAPI doesnt handle the change you want to make in sales order then only go for BDC.
you can also check BAPIs available in 'BAPI' tcode.
hope this is helpful.
Regards,
Saba

Back ground processes, dialogue processes and Process chains

Hai all,
I am going through making process chains and I am struck with one thing:
"How many background process chains and dialogue processes you have during run time"
This is the problem. I understood everything else except this.The concept says that I have to know what is the capacity of the system, how many background and dialogue processes it could accomodate, how many are left and how many you can use for your process chain.How do we find out this? and could somebody please explain me or refer to documentation about the Back ground processes, dialogue processes and Process chains.
Thanks.

Hi Visu,
You can see the number of dialog and background processes by using transaction SM51 and then double clicking on the server (we only have one but it may be different for each). Our BASIS folks take care of the number of processes as well. And, for us we have a schedule that changes the number at a certain time of day because you tend to need more dialog during the day but more batch at night.
The transaction to look at and change the settings is RZ03. Then use the menu path Edit->Operation Modes you can select either Configuration or Timetable here. Both give information in different ways. I tend to double click around to see what it might tell me.
I hope this helps a bit,
Diane

Error in BDC Back Ground Processing

Dear All,
I am facing problem on while executing BDC program. First i am executing in Foreground method there it displaying errors occured,
means it showing full discription or error.
But when i used Back ground processing its displayig the full error discription like "No posting object defined for 1230/ / / " here i need full error discription.
please do the need full.
Regrads,
Srinivas.

Hi
In background processing you cannot see the error message, for that you have to write logic for capturing messages.
Use 'Format_Message' function module so that you can get the complete message and then you can display that on the screen.
Hope it helps...

Calling Transaction code & returning back to calling program

Hi,
I have requirement as below
Write the report to call the transaction code say for example different tcode (1000 in number) need to be executed and after every tcode execution it should return back to calling report. I tried using "CALL TRANSACTION 'ABC' AND SKIP FIRST SCREEN" it does execute the tcode but need the user interaction to return back to report, where here i want do this programatically.
can someone please help me & what is possible ways this can be do able.
Thanks,
John.

There are two method of BDC
1- Call transaction method
2- BDC Session method
In this case you can use call tansaction method.
Syntax- call tansaction abc using gt_bdcdata.
Do the recording with t-code SHDB for that particular transaction and after the necessary modification use it in your program.
Please check f1 help of call transaction for details.

Passing select-options values using call transaction method

Hi Experts,
I have a scenario in which i have three fields BUKRS,WERKS and MATKL in an internal table i_tab and I have MATNR as a selection-option.
After this I have to use call transaction <tcode> for all the line items in the internal table and the MATNR select-option values I have to pass directly for each line of i_tab using call transaction method.
TYPES: BEGIN OF t_tab,
          bukrs TYPE bukrs,
          werks TYPE werks_d,
          matkl TYPE matkl,
        END OF t_tab.
DATA: w_tab TYPE t_tab,
            i_tab      TYPE STANDARD TABLE OF t_tab.
SELECT-OPTIONS: s_matnr FOR marc-matnr.
Now I am putting a loop at i_tab and have to use CALL TRANSACTION <TCODE> for each line with the SELECT-OPTIONS for MATNR.
Please tell me whether we can pass multiple ranges for MATNR using call transcation method.
for example there can be multiple single values/multiple ranges/excluded ranges for MATNR. so please suggest me how tho achieve this sceanrio using CALL transaction method of BDC.
Thanks a lot.
Regards,
Krishan

Hi Krishan,
For the Call transaction TCODE there is extension ....OPTIONS from OPT. Just Check it out. I think it is possible like this.
... OPTIONS FROM opt
*Effect*
This addition gives you control using the values of the components of the structure opt, which must be of the Dictionary type CTU_PARAMS. The components have the following meaning:
DISMODE
Processing mode (comparable with the MODE addition)
UPDMODE
Update mode (comparable with the UPDATE addition)
CATTMODE
CATT mode (controlling a CATT procedure)
The CATT mode can have the following values:
' ' No CATT procedure active
'N' CATT procedure without single screen control
'A' CATT procedure with single screen control
DEFSIZE
Use standard window size
RACOMMIT
COMMIT WORK does not end CATT procedure
NOBINPT
No batch input mode, that s SY-BINPT = SPACE.
NOBIEND
No batch input mode after BDC data has been read
The components DEFSIZE , RACOMMIT, NOBINPT, NOBIEND always take the following values:
'X' Yes
' ' No
If the OPTIONS addition is omitted, the following settings are valid for the control parameters:
DISMODE from the MODE addition
UPDMODE
from the UPDATE addition
CATTMODE
No CATT procedure active
DEFSIZE
Do not use standard window size
RACOMMIT
COMMIT WORK ends procedure successfully
NOBINPT
Batch input mode, that is SY-BINPT =X.
NOBIEND
Batch input mode also active after BDC data has been read
Regards,
Swapna.

Handling Warning pop up windows in BDC call transaction method

Hi All,
Iam using a BDC to automate the Costing Process i.e. Transaction CK40N using call transaction method. In a particular Screen after i perform the execute action, a warning pop up window appears. Only if I click on OK, the execution continues or else it will not proceed. How to handle this situation in case a warning pop up window appears based on the input which is given? In other words a Dynamic warning message. Thanks in advance....
Regards,
Nirmal

Hello,
U can either use NO_DIALOG or SUPPRESS DIALOG to avaid this,.
Regards,
Vasanth

How to avoid a POP-UP in CALL Transaction Method

Hi All,
I am doing a BDC for transaction CA02 by using CALL Transaction method, while i am trying to delete an operation i am getting a POP-UP asking YES/NO. My program contains the BDC OKCODE value as '=YES' for deletion of the operation/s. Still the POP-UP is persisting.
Could you please let me know how can i avoid the POP-UP or is there any other way handling the POP-UP's.
Reward Points Gauranteed. )
Thanks in Advance,
Suresh

This means that you are running your CALL TRANSACTION in the frontend.
One way would be to use the MODE addition
Here is an extract from the Help
... MODE mode
Effect
The processing mode can take the following values:
'A' Display screen
'E' Display only if an error occurs
'N' Do not display
'P' Do not display; debugging possible
But the fact that you get a popup you don't expect is worrying. You have to process this Popup otherwise the result is hazardous !

How to create a session using call transaction method.

hi , this is nagaraju,
How to create a session using call transaction method.

Hi,
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
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 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. Unless session is processed, the data is not transferred to database table.
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.
SESSION METHOD
Data is not updated in database table unless Session is processed.
No sy-subrc is returned.
Error log is created for error records.
Updation in database table is always synchronous
CALL TRANSACTION
Immediate updation in database table.
Sy-subrc is returned.
Errors need to be handled explicitly
Updation in database table can be synchronous Or Asynchronous.
Regards,
Sruthi.

Difference between Session method and Call transaction method

Hi,
Difference between Session method and Call transaction method in BDC

Hi,
SESSION method:
Is a standard procedure for transferring large amount of data into the R/3 system.
Data consistency is ensured because batch input uses all thje checks conducted on the normal screen.
It is a two step procedure:
1. Progarm: creates batch input session. This session is the data file that includes everything to begin the transaction.
2. Process session: Which then actually transfers the data to database table.
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 a session.
A session stores the actions that are required to enter your data using normal SAP transactions i.e. data is transferred to session which inturn transfers data to database table. Session is an intermediate step between internal table and database table.
Data along with it's actions are stored in session. i.e. data for screen fields, to which screen it is passed, the program name behind it and how next screen is processed.
When the program has finished generating the session, u can run the session to execute the SAP transactions in it.
BDC_OPEN_GROUP
          You create the session through program by BDC_OPEN_GROUP function.
1) User Name: User Name.
2) Group       : Name of the session
3) Lock Date : The date when you want to process the session.
4) Keep        : This parameter is passed as 'X' when you want to retain session even       after processing it.
BDC_INSERT
     Data is transferred to session by BDC_INSERT.
BDC_CLOSE_GROUP.
     With this function the session will be closed.
CALL TRANSACTION method.
Syntax: call transaction <tr code> using <bdctab>
                             mode <A/N/E>
                             update <S/A>
                             messages into <internal table>.
<tr code>   : transaction code
<bdctab>   : Name of the BDC table
mode: mode in which you execute the transaction.
A   : all screen mode ( all the screens of the transaction are displayed )
N   : no screen mode ( no screen will be displayed when you execute the transaction )
E   : error screen ( only those screens are displayed where in you have error record )
Update type:
S: synchronous update in which if you change data of one table then all the related tables gets updated and SY_SUBRC is returned for once and all.
A: asynchronous update in which if you change data of one table, the sy-subrc is returned and then updation of other affected tables takes place. So if system fails to update other tables still sy-subrc returned is zero.(that is when first table gets updated ).
messages: if you update database table, operation is either successful or unsuccessful. These messages are stored in internal table. This internal table structure is like BDCMSGCOLL.
       TCODE: transaction code.
       DYNAME: batch input module name.
       DYNNUMB: batch input dyn no.
       MSGTYP: batch input message type.
       MSGSPRA: batch input language id of message.
       MSGID:    message id.
       MSGV1.MSGV5: message variables
For each entry which is updated in the database table message is available in BDCMSGCOLL.
Reward if useful
Regards
Srinu

Call Transaction Method Error

I am trying to update the MARA table using Inbound Proxy.
i am able to do so by Create Session Method which i can Process using Transaction SM35.But i am unable to do the same by Call Transaction Method. What could be the reason For same?
Actually the code in the method is not Getting Triggered incase of Call transaction Method.
Also can there be some Queue problem???
How to configure out the same if the case is of Queue.
Message was edited by: Amit Singla

I am trying to update the MARA table using Inbound Proxy.
i am able to do so by Create Session Method which i can Process using Transaction SM35.But i am unable to do the same by Call Transaction Method. What could be the reason For same?
Actually the code in the method is not Getting Triggered incase of Call transaction Method.
Also can there be some Queue problem???
How to configure out the same if the case is of Queue.
Message was edited by: Amit Singla

Call transaction method in back ground Processing?

Similar Messages

Maybe you are looking for