RFBIBL00 - call transaction - Restart Mechanism

Hi Gurus,
I am using program RFBIBL00 thru call transaction mode.
I have gone through the Documentation of the program regarding Restart Mechanism.
Can any one pls help to understand/implement regarding Restart mechanism.
Regards'
Madan.

Hello Madan,
Were you able to obtain more information about this? I'm having the same issue right now, and I would appreciate some help.
Can you please inform me if you found something?
Thanks,
Yusuf

Similar Messages

CALL TRANSACTION ... UPDATE 'S' and Restartable Update Request

Dear experts,
I have a program that calls a transaction by using the CALL TRANSACTION ... UPDATE 'S' statement. This transaction then performs a database update by using CALL FUNCTION ... IN UPDATE TASK statement. The database update may cause an error due to the primary key conflict.
One behavior that I notice of my program is when the database update raises an error, the corresponding update request in the update table log (SM13) will be flagged as error and non-restartable, eventhough the update module in question is restartable. Why is it like this?
To make my question clearer, I attach my transaction, program and update module below. They are very simple.
Update module:
FUNCTION z_121_15_update_module.
*"*"Update Function Module:
*"*"Local Interface:
*" IMPORTING
*"     VALUE(IMP_ZSCARR_CUSTOM) TYPE ZSCARR_CUSTOM
INSERT into zscarr_custom values imp_zscarr_custom.
IF sy-subrc NE 0.
    WRITE sy-subrc TO subrc.
    MESSAGE subrc TYPE 'A'.
ENDIF.
ENDFUNCTION.
Subroutine in the transaction that calls the update module above:
FORM save.
zscarr_custom-carrname = sy-uzeit.
CALL FUNCTION 'Z_121_15_UPDATE_MODULE' IN UPDATE TASK
    EXPORTING
      imp_zscarr_custom = zscarr_custom.
COMMIT WORK.
LEAVE TO SCREEN 0.
ENDFORM.
The program that calls the transaction whose the subroutine above:
*& Report Z_121_15_COMPLEX_LUW_19
*& Program that calls a transaction.
*& Called transaction(s): Z_121_15_CLUW_20
REPORT z_121_15_complex_luw_19.
DATA:
it_bdcdata TYPE TABLE OF bdcdata,
wa_bdcdata TYPE bdcdata,
subrc TYPE char10.
wa_bdcdata-program = 'Z_121_15_COMPLEX_LUW_20'.
wa_bdcdata-dynpro = '100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'ZSCARR_CUSTOM-CARRID'.
wa_bdcdata-fval = '01'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = 'SAVE'.
APPEND wa_bdcdata TO it_bdcdata.
CALL TRANSACTION 'Z_121_15_CLUW_20' USING it_bdcdata MODE 'E' UPDATE 'A'.
*IF sy-subrc > 0.
WRITE sy-subrc TO subrc.
MESSAGE subrc TYPE 'S'.
*ENDIF.
Thanks in advance.
Regards,
Haris

What I mean is, for example, when the called update module in the code below issues a type A message,
CALL FUNCTION 'Z_121_15_UPDATE_MODULE' IN UPDATE TASK
    EXPORTING
      imp_zscarr_custom = zscarr_custom.
COMMIT WORK AND WAIT.
then, in SM13, the corresponding update task will be flagged as non restart-able, eventhough the update module itself is defined as restart-able.
This also happens in the case follows: let the code below is a part of a transaction program that calls an update module
CALL FUNCTION 'Z_121_15_UPDATE_MODULE' IN UPDATE TASK
    EXPORTING
      imp_zscarr_custom = zscarr_custom.
COMMIT WORK.
and the transaction above is called by a program by using
CALL TRANSACTION 'THE_TRANSACTION_ABOVE' ....... UPDATE 'S'.
Am I correct? This is my conclusion so far.

Error msgs in call transaction mode using RFBIBL00

Hi Gurus,
I am using FRBIBL00 program in call transaction mode to post FI documents and i am getting the below msgs:
FB012                    Session 1 : Special character for 'empty field' is /
F5201                    Posting period 008 0831 is not open
FB012                    Session 1 : Special character for 'empty field' is /
FB007                    Session 1 session name TEST1 was opened
FB008                    Session 1 session name TEST1 was created
Please help me in resolving this.
Regards'
Madan.

Hi Prabhu/Vishwa,
Thanks for your quick response.
I am calling RFBIBL00 in "call transaction" mode to post FI ocs.
here is the format of the file written on to the application server.
Session - 0TEST1       100KBQ9FCEC    00000000X/
Header - 1FB01                20080816SAYBP120080831/ CHF /         /         20080831/               /               /                        /   /
Item level - 2BBSEG                         50/         //   79378           /               /               /               IU//               /
2BBSEG                         40/         //   79378           /               /               /               IU//               /
2BBSEG                         50/         //   42266           /               /               /               IU//               /
2BBSEG                         40/         //   42266           /               /               /               IU//               /
The file format is correct, it is working fine in case of Batch session method.
I want it to work for both Batch session and Call transaction.
Please help me to reslove call transaction mode.
Regards'
Madan.

How use RFBIBL00 for call transaction method.

Hi,
I am trying to use the direct input program RFBIBL00 to park document throught the transaction FBV1.
Though I am trying to use call transaction option 'C'. Not able to process data directly but a session is getting created in SM35.
Please let me know how to handle this.
Thanks in advance.
Pradeep.

HI
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/lsmwwithRIFBIBL00
Regards
Pavan

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

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.

Set parameter and call transaction

Hi.
To use the call transaction with the skip first screen option we have to use the set parameter statement. Depending on the PID which the technical specs of the fields contain, it is possible to preset these values. My query is that if the screen contains checkboxes and a lot of them, how do i select them?
Please advice as this is a part of my project.
Regards....

Hi,
Here is what's given in the help of "Call transaction".
Example
CALL TRANSACTION 'SP01'.
Addition 1
... AND SKIP FIRST SCREEN
Effect
Skips the first screen in the transaction (provided all the required fields have been assigned values by the SPA/GPA mechanism).
I need to know how to assign values to the transaction XK02. It's got checkboxes and it must skip the first screen.
Please help.
A BDC table disables the GUI status and I am unable to go back to the calling program.
Thanks and Regards,
Prem.

Can anybody pls tell me limitations of BDC Session & Call transaction?

hi, Guys, this is srinivas.
How can we deside which method is to(BDC session/ Call transaction)
use to upload data to SAP database?
Can we run Call Transaction in Background?
Which is preferable for bulk data? and Why?
how can we restart Session if any error occurs?
Thanku?

Hi,
Hope it helps this......
SAP BDC INTERVIEW QUESTIONS & ANSWERS
1.       What is full form of BDC Session?
Batch Data Communication Session.
2.       What are the steps in a BDC session?
The first step in a BDC session is to identify the screens of the transaction that the program will process. Next step is to write a program to build the BDC table that will be used to submit the data to SAP. The final step is to submit the BDC table to the system in the batch mode or as a single transaction by the CALL TRANSACTION command.
3.       How do you find the information on the current screen?
The information on the current screen can be found by SYSTEM à STATUS command from any menu.
4.       How do you save data in BDC tables?
The data in BDC tables is saved by using the field name BDC_OKCODE and field value of /11.
5.       What is the last entry in all BDC tables?
In all BDC tables the last entry is to save the data by using the field name BDC_OKCODE and a field value of /11.
6.       What is a multiple line field?
A multiple line field is a special kind of field which allows the user to enter multiple lines of data into it.
7.       How do you populate data into a multiple line field?
To populate data into a multiple line field, an index is added to the field name to indicate which line is to be populated by the BDC session (Line index).
8.       Write the BDC table structure.
BDC table structure
FIELD                     TYPE                            DESCRIPTION
Program                CHAR (8)                      Program name of transaction.
DynPro                 CHAR (4)                      Screen number of transaction.
DynBegin              CHAR (1)                      Indicator for new screen.
Fnam                    CHAR (35)                     Name of database field from screen.
Fval                      CHAR (80)                     Value to submit to field.
9.       Does the CALL TRANSACTION method allow multiple transactions to be processed by SAP?
No. The CALL TRANSACTION method allows only a single transaction to be processed by SAP.
10.    Does the BDC-INSERT function allow multiple transactions to be processed by SAP?
Yes.
11.    What is the syntax for CALL TRANSACTION?
CALL TRANSACTION trans .
Three possible entries are there for MODE.
                  A          -           Show all screens.
                  E          -           Show only screens with errors.
                  N          -           Show no screens.
Regards,
V.Balaji
Reward if usefull

Call transaction & leave the current screen

Hi
I have created two Table maintanence Generator one for master table & second for transaction table. In my master table i have written code for calling the second TMG
ie, call transaction 'zhdms'.
but my problem is from my first TMG when im clicking on one button it calling the second TMG. & im making new entries over der & when i click on BACK button it will call the first TMG & again if i am clicking on Next button it will move on to second screen. but it is showing one information like DEveloper is locked. we can only display it. how to avoid this.
Can we avoid this using leave screen . How to write code for that.

Hi ,
Try this
CALL TRANSACTION AND SKIP FIRST SCREEN.
Effect
Skips the first screen in the transaction (provided all the required fields have been assigned values by the SPA/GPA mechanism).
or
LEAVE TO { {TRANSACTION tcod} | {CURRENT TRANSACTION} } AND SKIP FIRST SCREEN.
Effect
Ends current processing and starts the (new) transaction tcod. All previous internal sessions are deleted from the stack and one new internal session is opened for the program of the transaction that was called. When this session has finished, the system returns to the next higher area menu.
If you specify CURRENT TRANSACTION (as of Release 6.20), the current transaction is called with exactly the same transaction code it was called with using CALL TRANSACTION or LEAVE TO TRANSACTION. With the exception of parameter or variant transactions, this is the transaction code that is also in the system field sy-tcode.. In the case of parameter or variant transactions, it is their transaction code, while sy-tcode contains the name of the implicitly-called dialog transaction.
Regards,
Chitra.

How bapi different from session and call transaction?

how bapi different from session and call transaction?
thanks in advance.

For one, Batch Data Communication (BDC) is older. Business Application Programming Interface (BAPI) came later, about 10 years ago (you can see this already from the name, which contains marketese like "business" ).
More important though, they are different technologies. With BDC you build the "batch input transaction" yourself, with an ABAP program which creates the "batch input session" ("Batch-Input-Mappe" in german). You then take that session, like an object, and "run" it on a system (most of the time, this is done on a local system by the administrators, after it has been tested for correctness).
With BAPI, a system (local or remote) exposes its interface to you through some kind of Remote Function Call (RFC). Practically, it tells you: "What do you want to do? Insert that data into Materials Management? Here is the function and the the parameters you have to use for each record". You only work with the Interface - the exposed function. How this function works does not have to interest you. You don't have sessions to "run", you fire your function calls filled with data, one after another and you're done.
BAPI can be run remotely. With BDC, you probably have to call the administrators of the remote system and send them the session you created for them to run. With BDC you go through the whole transaction in one BDC session, with BAPI you may need more than one "BAPI calls" to do this.
With BAPI you don't fill obcure field names with values, you just fill the parameters. You can use a BAPI from inside your ABAP program to let a "business object" do some clearly defined work for you, then you can continue with your code doing other things. You don't do this with BDC. With BDC you write a dedicated program that creates the "session", which is then executed separately.
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP
program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the
BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and
invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate
fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are
not available for all application areas.
Business Add-In (BADI) are a new SAP enhancement technique based on ABAP Objects.
They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.

Screen no change in BDC call transaction method

Hi experts
Greetings!
I have a BDC created in call transaction method for t-code FB01.
Data passed successfully to the first screen but when it navigates to the second screen I am not able to pass any data.
After debugging I found that the issue was because of the DYNPRO value.
It was 8500 when I created this recording but now the screen number shows 350.
Is is possible that screen nos change because of any support stack or OSS notes implementation.
In run time i tried to change the value to 350 and it works fine..
Thanks
Jay

Hi,
LSMW Direct input method is better for your quiry. Becasuse i wrote BDC for FB01 but not working properly.
So i used LSMW, helped me a lot. Progmra name is RFBIBL00. Or else i will export and send you if you want. It can handle multiple line items upto 950.
Thanks,
Sriram

Call transaction FB01 vs submit RSBDCSUB

Hi guys,
I would like to know how I can get the message log when I execute
SUBMIT RSBDCSUB WITH MAPPE EQ G_GROUP "batch input name
                      WITH Z_VERARB EQ 'X'
                      WITH FEHLER EQ SPACE
                      WITH LOGALL EQ SPACE
                      EXPORTING LIST TO MEMORY
                      AND RETURN.
instead of :
CALL TRANSACTION 'FB01' USING BDCDATA
                  MODE 'N' UPDATE 'S'
                  MESSAGES INTO MESSTAB.
I would like get the same information of MESSTAB but using submit RSBDCSUB
I try it with :
CALL FUNCTION 'LIST_FROM_MEMORY'
        TABLES
          LISTOBJECT = LISTOBJECT
        EXCEPTIONS
          NOT_FOUND = 4
          OTHERS     = 8.
CALL FUNCTION 'LIST_TO_ASCI'
        EXPORTING
          LIST_INDEX         = -1
        TABLES
          LISTASCI           = VLIST
          LISTOBJECT         = LISTOBJECT
        EXCEPTIONS
          EMPTY_LIST         = 1
          LIST_INDEX_INVALID = 2
          OTHERS             = 3.
      CALL FUNCTION 'LIST_FREE_MEMORY'
        TABLES
          LISTOBJECT = LISTOBJECT.
And in VLIST I only get the number of folder with G_GROUP batch info.
for example " 2 folder get it". I would like to know for example if there are errors in my batch input.
Thanks a lot in advance.
Best regards.
Ana

I'd not suggest your solution.
better use RFBIBL00 ( or BAPI_ACC_DOCUMENT_POST - read docu)
for rfbibl00 you can use
SUBMIT RFBIBL00 WITH callmode = 'D'....
A.

Which method should use? Call Transaction or Session Method?

I need to upload 1,00,000 records then which method i need to use? Either session or call transaction?

Hi.....
A (asynchronous updating) The called transaction does not wait until the database has been
updated, it simply forward the updates to the SAP update service. This usually speeds up the CT
program. This processing mode is NOT recommended for large data sets as the called transaction
does not receive a completion message from the update module.
The calling CT program therefore cannot tell if the transaction has been successfully completed. You
should use the updating administration function (transaction SM13) to determine whether updating
was terminated early. The error analysis /correction functions for are less helpful than with
synchronous updating.
S (synchronous updating) With synchronous updating the called transaction waits until all the
updates have been completed. So processing is slower than with synchronous updating. The called
transaction can however report any updating errors to the program, which makes error
analysis/correction easier.
And
Unlike the classical batch input processing with sessions CALL TRANSACTION does not offer any
special processing procedures for transactions containing errors. There are no restart functions for
transactions that contain errors or that cause updating terminations.
Now you decide which one is best...
For large amount of data Sessions method is the better.
Thanks,
Naveen.I

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 -

RFBIBL00 - call transaction - Restart Mechanism

Similar Messages

Maybe you are looking for