Preference between rfc and bapi

Hi
If rfc and bapi are available for the similar task to implement ...........as a XI consultant which one you will suggest ?? If so could you please explain me the reason for the same ??
thanks
kumar

Hi,
From an XI Implementation perspective,
BAPI's do not have a implict COMMIT associated with them and so , in the receiver RFC adapter you need to provide the COMMIT HANDLING FOR BAPI CALLS. This option was avilable from SP 14.
Prior to that you had to writter a warpper RFC and import it into XI and use this instead of the BAPI.
The RFC's conatin an Implicit commit so no such issue here.
regards
Bhavesh

Similar Messages

Unable to differentiate between RFC and BAPI

Hi guys,
    Nowadays I am studying the above concepts:BAPI and RFC. But I am confused by the two.
So far I learnt that the two are both techniques used to realize communication between SAP and external
systems,and frequently via Remote-enabled Function.
   My confusion is the distinctions between the two. Would you please do me a favor? Tks

Hi   Alex,
Just check it out these answers.
Remote Function Call :
RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
RFCs manage the communication process, parameter transfer and error handling.
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
BAPI
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module
ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access.
Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects.
You create business objects and those are then registered in your BOR (Business Object Repository)
which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.
In this case u only specify the business object and its method from external system
in BAPI there is no direct system call. while RFC are direct system call.
Some BAPIs provide basic functions and can be used for most SAP business object types.
These BAPIs should be implemented the same for all business object types.
Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs.
Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
another points,
BAPI is object oriented. It is placed under Business objects as methods.
RFC is just a Function module or a call.
RFC: is just a FM that can be called from remote system too(destination defined in transaction SM59).
BAPI: Business Application Programming Interface
A BAPI is a method of a business object defined in the Business Object Repository (BOR). For example, in the BOR, you can find a business object called SalesOrder, which conceptually represents a sales order in the system. A business object typically has several methods that can be used to read, create, modify a particular instance of the business object, or list instances of the business object matching certain selection criteria. These methods are BAPIs.
Technically, a BAPI is implemented using a RFM. But, unlike the non-BAPI RFMs, a BAPI is usually well documented, has nicer parameter names, and is supported by SAP for several SAP software releases. You can browse Business objects and BAPIs in the SAP system using transaction BAPI.
Thanks
Eshwar
*Rewards if useful*

Aout RFC and BAPI

Hi Eperts,
Would you please tell me the difference between the two,because I learnt that BAPI is a kind of RFC,I'm not sure whether it is right or not.

Hi,
RFC Vs BAPI
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA.
In this case you only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI. It is not possible to connect SAP to Non-SAP systems to retrieve data using RFC alone. RFC can acces the SAP from outside only through BAPI and same is for vice versa access.
RFC is the protocol used by SAP for remote communication, that is, for communications between remote (independent) systems. RFC is used for communications between two independent SAP systems, or for communications between an SAP system and a non-SAP system, such as an external application. It can also be used for communications between modules on the same system. Using the RFC interfaces you can extend the functionality of R/3 applications from an external program.
Reward if it useful...
Lakshmi.

Diffrent between BDC and BAPI

Gurus..
Please let know what is the diffrent between BAPI and BDC development?
thanks

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
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
Regards
Anji

RFC AND BAPI

Hi,
Difference b/w the BAPI and RFC.

Dear Bhagavan,
Go through the following threads
BAPI and RFC
What is the difference between RFC and BAPI?.
RFC AND BAPI
BAPI& RFC
Best Regards,
Srikanth
Reward the useful answers and you will get
ONEPOINTyourself

About RFC and BAPI

Hello Masters,
What Makes the exact difference between RFC and BAPIs. Both can perfom same thing. BAPI uses the RFCs only. Then how can it justify?
Thank you

RFC:
RFC --- > Function module and general will be used to make call to function
sending the function (XI has RFC adapter)
BAPI:
BAPI ---> Other version of RFC (Objected oriented) mostly we will use for Sync
calls (Mostly in XI using proxies we will call BAPI's)
Refer these links for more details:
http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
http://www.sap-img.com/fu033.htm
BAPI Vs IDOC - in detail
http://searchsap.techtarget.com/tip/1,289483,sid21_gci824860,00.html
/thread/127699 [original link is broken]
IDOC,RFC,BAPI
Re: When and Why we use BAPI, RFC and IDOC.. in XI
Diff... between ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify
idoc and bapi
Difference among IDOCS,BAPI,RFC?
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
Differences Between RFC & BAPIS
RFC Vs BAPI
For more details:
refer this thread.
What are idocs, BAPI, RFC?
BAPI is nothing but the Business process programing interface which are standard and stable and these are store in the business object repository.
Standardized programming interface that enables external applications to access business processes and data in an SAP System
RFC is the remote function call which is used to call the function remotely which may be in same system or ather system
its also used communication between SAP systems , between SAP systems ,external systems.
idoc and bapi
Difference among IDOCS,BAPI,RFC?
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
Differences Between RFC & BAPIS
RFC Vs BAPI
http://www.sap-img.com/abap/ale-bapi.htm
RFC means remote function call,
these are the function modules which can help u to access across the sap and from sap to third party front end,
BAPI means Business application programing interface which is the RFC enable function module and uses in OOPS concept.
RFC ,IDoc and BAPI
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
This is a short description of BAPI and RFC
BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system.

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

WAD Call RFC and BAPI

Dear all,
I have a problem about using WAD call RFC and BAPI get BW data,who can help me?

HI Bill,
Please give details of what you are trying to do.
Brian

Are all RFCs and BAPIs automatically exposed as web services?

Hello,
Our product helps business users exchange data with SAP. We use standard RFCs and BAPIs to communicate with SAP. This is a .NET application although my question is not specific to .NET.
It seems SAP obsolete their .NET connector in near future. The emphasis is on web services. This is a great move. We can simply drop using the .NET connector and start using the web services. However, I have a few doubts:
1. RFCs and BAPIs are automatically exposed for remoting. When the customer installs our application, it just works out of the box. Customers do not have to make any configuration changes to SAP to expose RFCs and BAPIs.
In the new world, are all RFCs and BAPIs automatically exposed as web services or one has to go through each RFC/BAPI and expose it explicitly?
2. Is there a comprehensive WSDL schema available anywhere for all the RFCs/BAPIs?
3. Are there any other web services (besides RFCs/BAPIs) that SAP Netweaver exposes? Where can I get more information?
Thank you in advance for your help.
Regards,
Pradeep

Darryl,
Thank you for your help or at least trying to help me. However, you left me with more questions than answers:-(.
1. "Old" does not mean "bad." Each RFC/BAPI serves a specific function. If some RFC is being obsoleted, there must be a replacement documented somewhere. Is there one?
2. I can look into SE80 (and other transactions) to see what is exposed. However, what I need to understand is what is SAP's stance on exposing standard web services.
Can others please share your thoughts?
Regards,
Pradeep

Difference between RFC and Webservices.........??

Hi
What is the difference between RFC and webServices... Like webServices these RFC also i can use in any language rite?? Then what is main difference
Can any one tell me which perfomance is good.. either webService or RFC...? and why??
While creating webService in R/3 its asking the following details can any one explain those

Virtual Interface
End PointType : what is the end point type. please explain about the different options available...(Business Object, Funtion Group, Function Module, XI Message Interface)
On next Screen

Application -- ex FI-AR
Business Object -- ex KNR
Next Screen
Porfile
>>> Basci Authorization:SOAP Pro
>>> Secure SOAP Profile
Best Regards
Ravi Shankar B
Message was edited by:
RaviShankar B
Message was edited by:
RaviShankar B

Hi Ravi,
Jin has correctly explained.
Only two connectors are provided from SAP
JCO- for connecting java applications
>.Net connectors - for connecting >net applications
And SAP has provided these connectors bcoz these the two most popular technologies or framefork these days which are very common.
But In my previous examples , I try to explain the concepts only by giving .net as example.
Now for making you clear, No SAP connector is available for C++ for accessing RFC but C++ can access web services using XML and SOAP
Again Note these points.
RFC is SAP specific.
Used For----->
SAP applications- SAP applications
SAP Appl - Java Applications(Using JCO)
SAP Applications->Net Applications( using >NEt connectorprovided by SAP)
Web Service is open standard
Any Platform/Any Language to Any Platform/Language( which can understand SOAp and XML).
For Web Service Detail--
Refer to this link
Re: What is meant by Webservice
Regards,
Piyush

Bapi doubt ...difference rfc and bapi

Plese give me the following information.
1) wt is the difference between BAPIRETURN, BAPIRET1 and BAPIRET2?
2) wt is the diff. between an RFC-enabled fm and BAPI ?

Hi again,
1. YES, Definitely it will behave like BAPI.
2. The sap concept of
   naming function modules (related to business object)
   and naming them as BAPI*
   is JUST FOR IDENTIFIECATION PURPOSE,
           and nothing else.
We can give ANY NAME.
regards,
amit m.
Message was edited by: Amit Mittal

What is the difference between rfc and idoc

hi,
My name is rambabu.can anyone of u please tell me the main differences between idoc and rfc??
Thanks in Advance

hi Ramesh,
Remote Function Calls (RFC) and data exchange through IDoc
message documents. RFC makes direct and synchronous calls of a program in
the remote system. If the caller is an external program it will call an
RFC-enabled function in R/3 and if the calling program is the R/3 system
it will call an RFC-function in another R/3-system or it will call a
non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are
a subset of the RFC-enabled function modules, especially designed as
Application Programming Interface (API) to the SAP business object, or in
other words: are function modules officially released by SAP to be called
from external programs.
IDocs are text encoded documents with a rigid structure that are used to
exchange data between R/3 and a foreign system. Instead of calling a
program in the destination system directly, the data is first packed into
an IDoc and then sent to the receiving system, where it is analyzed and
properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls
and IDoc data exchange is the fact, that every action performed on IDocs
are protocolled by R/3 and IDocs can be reprocessed if an error occurred
in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE
are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to
deliver data to the receiving system. ALE is basically the scheduling
mechanism that defines when and between which partners and what kind of
data will be exchanged on a regular or event triggered basis. Such a
set-up is called an ALE-scenario.
Regards
Sreeram.G.Reddy

Exception handling in rfcs and bapis

exception handling in rfcs and bapis

Hi Jayakrishna,
In General , there are non execptions in BAPIs, because of the reason, that the exception raised in a SAP envoronment may not mean anything for a non SAP initiator. All the exception situations would only fill the return table(TYpe BAPIRET2 or something like that). If you read that table after the call to the bapi, you can understand what has gone wrong.
Regards,
Ravi

Accessing RFCs and BAPIs from enterprise java beans

Hello folks,
 my question is concerning comunication between EJBs and RFCs. I want to develop a simple session bean that connects to a R/3 back-end, calls a RFC then returns some data, let's say, an example of this could be a list of employees from BAPI_EMPLOYEE_GETDATA.
 Ok, by using a web dynpro and adaptive RFC my works could be very very easy, but I'd like to test this way: session (stateless) EJB -> RFC. Can I:
* use JCO.ClientService with a non-portal SAP WAS?
* use embedded JRA (SAP Library stated "The SAP JRA is an add-on for the SAP JCo. If you use the SAP Web AS, the SAP JRA is installed automatically with the SAP JCo.", but I found nothing so in Connector Container Service ...)
* install and configure JRA by myself?
I'm working on a SAP WAS 6.40 Sneak Preview (Java only), and finding a path for easily integrate SAP WAS developed ejbs and external business system. SAP Library suggest to "obtain the JCo connection through the connection framework": is it related to JRA, JCA and SAP Resource Adapter?
Thank you
Pasquale

hello
i´ve written a simple stand alone client to test jra connection to a sap system
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.util.Properties;
import javax.resource.cci.Connection;
import javax.resource.cci.ConnectionFactory;
import javax.resource.cci.Interaction;
import javax.resource.cci.MappedRecord;
import javax.resource.cci.RecordFactory;
import javax.resource.cci.ResultSet;
import javax.resource.spi.ManagedConnectionFactory;
import com.sap.mw.jco.jra.*;
public class Example
 public void exampleTest()
 Properties properties = new Properties();
 Connection connection=null;
 try
 properties.load(new FileInputStream ("props.txt"));
 catch(Exception e)
 System.out.println("properties could not be loaded");
 e.printStackTrace();
 try
 ManagedConnectionFactory mf = new JRA.ManagedConnectionFactoryImpl(properties);
 ConnectionFactory cf = (ConnectionFactory)mf.createConnectionFactory();
 connection = cf.getConnection();
 RecordFactory rf = cf.getRecordFactory();
 Interaction interaction = connection.createInteraction();
 MappedRecord request = rf.createMappedRecord("STFC_STRUCTURE");
 // Since the STFC_STRUCTURE does not create any new records
 // in the data base, you do not need to start a trancation here.
 // fill out a structure with dummy data
 MappedRecord importstruct = (MappedRecord)request.get("IMPORTSTRUCT");
 importstruct.put("RFCFLOAT","1.23456");
 importstruct.put("RFCCHAR4","ABCD");
 importstruct.put("RFCINT1", "11");
 importstruct.put("RFCDATE", "2001-08-24");
 // fill out a table with dummi data
 ResultSet rfctable = (ResultSet)request.get("RFCTABLE");
 for (int i = 0; i < 10; i++)
 rfctable.moveToInsertRow();
 rfctable.updateString("RFCCHAR4","EFGH");
 rfctable.updateInt("RFCINT1", i);
 rfctable.updateString("RFCDATE", "1961-08-24");
 rfctable.updateDouble("RFCFLOAT",1.65432);
 rfctable.insertRow();
 // call defined RFC and cast the result to the optional ResultMap interface
 ResultMap response = (ResultMap)interaction.execute(null,request);
 // release resources
 interaction.close();
 // create an xml file from the output of the called RFC
 // the optional interface ResultMap offers additional methods, like writeXML
 FileOutputStream os = new FileOutputStream(response.getRecordName() + "_Structure_from_NotManaged_Example.xml");
 response.writeXML(new java.io.OutputStreamWriter(os,"UTF-8"),true);
 os.close();
 ResultSet resultSet = (ResultSet)response.get("RFCTABLE");
 System.out.println("Name of the table is: "+resultSet.getRecordName());
 catch (Exception ex)
 ex.printStackTrace();
 System.exit(1);
 finally
 if (connection != null)
 try
 connection.close();
 catch(Exception exception1)
 public static void main(String[] args)
 Example anExample = new Example();
 try
 anExample.exampleTest();
 catch(Throwable t)
 t.printStackTrace();
the property file looks like this:
jco.client.client=010
jco.client.user=user
jco.client.passwd=pass
jco.client.ashost=your host
jco.client.sysnr=00
but this only an example for a standalone test client
to use jra inside j2ee first deploy the connector with the settings you need and then get a connection to it using jndi
i don´t have an example at hand for using it inside an ejb or servlet, but if you need one i'll have a look

Can you read Reports and Tables through RFCs and BAPIS?

Is there any way to read established reports and tables through RFC or BAPI function calls? We have a middleware that can execute various BAPIs and RFCs. I see a few promising ones: RFC_READ_REPORT, but no examples anywhere what the parameters needed are for the inputs.

Hello Scott,
Check below FMs for reading tables and programs.
Tables : RFC_READ_TABLE
Program : RFC_READ_DEVELOPMENT_OBJECT
Please note that for reading program using RFC_READ_DEVELOPMENT_OBJECT , lines in program should not exceed 72 chars else FM will throw dump(READ_REPORT_LINE_TOO_LONG).
Program code will appear in table QTAB which is 72 chars wide.

Preference between rfc and bapi

Similar Messages

Maybe you are looking for