System Tables in SAP
Saturday, March 22, 2008
SAP RFC
SAP RFC
RFC (Remote Function Call), these are function modules in SAP but are remotely enabled. This makes them similar to SAP BAPIs. Thus a Remote function module can be called from another Non-SAP System using a .Net connector or a Java connector. RFCs can be used to interface SAP and Non SAP systems or 2 different SAP R/3 systems.
SAP ABAP RFCs are of 3 types
Synchronous RFC
Transactional RFCs
Queued RFCs.
Synchronous RFC
In Synchronous RFCs both the Systems must be available at the time of the call. These RFCs are based on Synchronous communication.
Transactional RFCs
Here the called system need not be available at the time of the call. A unique transaction ID is generated and the called program is stored in the system along with the data. If the receiving system is not available for a long time then the call is scheduled to run in a batch.
Queued RFCs.
To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).
qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (in reference to the sequence defined in different application programs) in the participating queues.
For more details and related topics please see the following links
Creating SAP RFCs
SAP Function Modules
SAP BAPIs
SAP BAPIs in Real life
RFC (Remote Function Call), these are function modules in SAP but are remotely enabled. This makes them similar to SAP BAPIs. Thus a Remote function module can be called from another Non-SAP System using a .Net connector or a Java connector. RFCs can be used to interface SAP and Non SAP systems or 2 different SAP R/3 systems.
SAP ABAP RFCs are of 3 types
Synchronous RFC
Transactional RFCs
Queued RFCs.
Synchronous RFC
In Synchronous RFCs both the Systems must be available at the time of the call. These RFCs are based on Synchronous communication.
Transactional RFCs
Here the called system need not be available at the time of the call. A unique transaction ID is generated and the called program is stored in the system along with the data. If the receiving system is not available for a long time then the call is scheduled to run in a batch.
Queued RFCs.
To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).
qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (in reference to the sequence defined in different application programs) in the participating queues.
For more details and related topics please see the following links
Creating SAP RFCs
SAP Function Modules
SAP BAPIs
SAP BAPIs in Real life
SAP BAPI
SAP BAPI
BAPI (Business Application Programmer Interfaces), are the interfaces provided by SAP. BAPIs can be used for the following.
1) Integrating SAP to Non SAP systems using .NET Connector and Java Connector for example Visual Basic (Microsoft), or with Visual Age for Java (IBM)
2) Creating a Web Based interface to SAP
3) Uploading Data to SAP
4) Posting Data to SAP from within SAP
5) Creating an interface between various SAP Systems
Related Transaction Codes
BAPI
SE37
Please refer the diagram below.
SAP ABAP BAPIs
The Business Application Programming Interfaces allow object-oriented access to the SAP system through methods for the business object types. Together with the business object types, BAPIs define and document the interface standard at the business level.
Benefits of using BAPIs
BAPIs allow integration at the Business Level, as each BAPI is built around a Business Object
BAPIs are well defined and are internally consistent
For a BAPI access is through a object-oriented interface and connectors such as .Net and Java Connector are available for building an interface with Non SAP Systems
Stability is not affected because they are upward compatible and all the BAPI interfaces will survive an R/3 Upgrade.
For More Details See the links Below.
BAPIs in Real Life
RFCs
Function Modules
BAPI (Business Application Programmer Interfaces), are the interfaces provided by SAP. BAPIs can be used for the following.
1) Integrating SAP to Non SAP systems using .NET Connector and Java Connector for example Visual Basic (Microsoft), or with Visual Age for Java (IBM)
2) Creating a Web Based interface to SAP
3) Uploading Data to SAP
4) Posting Data to SAP from within SAP
5) Creating an interface between various SAP Systems
Related Transaction Codes
BAPI
SE37
Please refer the diagram below.
SAP ABAP BAPIs
The Business Application Programming Interfaces allow object-oriented access to the SAP system through methods for the business object types. Together with the business object types, BAPIs define and document the interface standard at the business level.
Benefits of using BAPIs
BAPIs allow integration at the Business Level, as each BAPI is built around a Business Object
BAPIs are well defined and are internally consistent
For a BAPI access is through a object-oriented interface and connectors such as .Net and Java Connector are available for building an interface with Non SAP Systems
Stability is not affected because they are upward compatible and all the BAPI interfaces will survive an R/3 Upgrade.
For More Details See the links Below.
BAPIs in Real Life
RFCs
Function Modules
Subscribe to:
Posts (Atom)
|
ABAP TIPS
|
| Always use Pretty Printer and Extended Program Check before releasing the code. Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive. |
