About RFC and R/3
Dear experts,
I am using java along with JCO to connect to SAP and retrieve data from a particular table after every 10secs.Data get retrieved in microsecs.Next cycle comes after another 10 secs and this way
process continues.Mean data gets retrieved , then 10secs break then once again data gets retrieved and so on........infinite loop..
However i haven't experience any problem so long.But still i want to confirm if this could be
causing any extra overheads on SAP R/3 server.
Thanx in advance..
Hi Adiyata
No it should cause any overheads in SAP server .
But a good idead can be instead of running it after every 10 seconds ,if possible try to pick up all the records in one shot and them againg pick it up after a gap of few hrs coz i do believe that your SAP system might be talking to some other systems also.
Regards
Neha
Similar Messages
-
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 youRFC:
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. -
RFC and CURP for Mexican vendors
Hello, I would appreciate you can provide any comments about Master data for Mexican customers/vendors.
In Mexico companies and organizations have a Tax registration number called RFC which is ABC680504BV1 which contains 12 length characters
The field for storing this information in SAP master vendor record is in field TAX NUMBER 1. Table-field: LFA1-STCD1
However in Mexico the natural persons, independent professional persons, have a Tax registration record called CURP which is 13 length characters. Example PIIG720116BV1
If I try to store the CURP in the field TAX NUMBER 1. Table-field: LFA1-STCD1 from the SAP master vendor I get and error message.
In fact the recommendation of SAP is to store the CURP in the field called TAX NUMBER. Table-field: LFA1-STENR and to check the box NATURAL PERSON
However in most of the reports the field TAX NUMBER is not available for displaying information. I am thinking to store the RFC and CURP in the field called VAT Registration number which is available in most of the reports and there is not any check in this field.
I would appreciate if somebody can provide any comments
ThanksHi,
The CURP should be entered in Tax Number 3 (STCD3).
Tax Number 3
Specifies the tax number.
Use
Enter the tax number that applies:
Country Tax number
Argentina Withholding agent number
Brazil State tax number
Bulgaria Social security number
Mexico CURP number
Netherlands Tax registration number (Loonbelastingnummer) of the chain-liability vendor
Russia KPP number
Ukraine VAT registration number
Kind regards -
hi
can any one provide me with some scenarios having
idoc and rfc as senders.Hi
To Configure the RFC to FILE scenario ,Proceed as Follows
a. Create an RFC Destination to XI in transaction code (SM59)
b. Create new destination of type T (TCP/IP)
c. Make sure you select Registered Server Program option before writing your program ID
d. Write you program ID (remember it's case-sensitive)
e. In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
Step2:Repository
1) From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
From the list of Software Component Versions, Choose your own software component version .Click Import.
3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
The namespace is ur:rfctofile
4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
After this specify the connection parameters to the R/3 system:
4.1) System IS :sapfox
4.2) Client IS :800
Then Save it. The new namespace will be visible under software component version node in the left frame.
Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3) Application server:172.25.5.7
4.4) System number: 00
4.5) User name:developer
4.6) Password: Password of Sap R/3 system.
Then click continue .You will find IDOC and RFC node. Click on this node and select the Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Rfc and Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
5). Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6) Create new data types.
6.1) Right click on Data types and select New.
Your Data Type is. dt_file
In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
Save the object.
6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
no need to create Data types. They are imported directly as Message types.
6.3) To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
Select the following.
6.3.1) Category: XSD.
6.3.2) Messages: From All Available Global Elements.
6.3.3) File:
Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7). Create a new Message Type.
7.1) In the left hand frame under Interface objects, right click on the Message types and select new.
7.2) Give a suitable name to the Message type.(MT_ messagetype).
7.3) For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
Save it.
8). Create a Message interface
8.1) In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
Save it.
9) . Create a graphical mapping between the target document and the sender .
9.1) In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2) As Source message select your own Message type.You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.
9.3) As Target Message you can choose your Rfc .Choose Search for Integration Object.
9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.
Save It.
9.6) You can also Test your Mapping by selecting the 'Test Tab'.
9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10). Create an Interface Mapping.
10.1) In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2) Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose Search for Integration Object.
10.3) Target interface: Your Inbound Interface( The Target document interface).
Then Select 'Read Interface' and Assign your 'Mapping Program' .
Mapping Program: Your Message mapping.
Then Save it.
11.) Finally , in the left hand frame ,go to your change list and Activate it
STEP 3: Directory
1) From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
Create a Scenario Object
2). The First Step is to create a Scenario Object
This will serve as container for all your configuration work. Create and save a scenario object
3) In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) . Create a Communication Channel.
6). Expand your service and right click on Communication Channel. Name your Communication Channel
Here we need to configure the adapter.
Since the Sender is 'RFC', Specify the following Parameters
For the adapter type , use the F4 help and select RFC.
Specify Sender since the adapter will be sending messages to XI
Specify the following parameters.
Transport Protocol: RFC
Message Protocol: RFC(RFC XML )
Adapter Engine: Integration Server
Adapter status: Active
RFC Server Parameter:
Application Server(Gateway):172.25.5.7
Application Server Service(Gateway Service): sapgw00
Program Id: Id of Registered server program ( it is case sensititve)
And the adapter is configured. Save it
Since the Receiver is File , Specify the following Parameters
6.1 For the adapter type , use the F4 help and select FILE.
6.2 Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3 Specify the following parameters.
Transport Protocol: File Transport Protocol.(FTP)
Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
Adapter Engine: Integration Server
For the File system access Parameters, enter the following
Source Directory:Test
File Name: Input.txt
6.4 For the FTP Connection Parameters, Specify the Following
Server:172.25.5.240
Port: 21(by default)
Data Connection: Passive
Connection security: None
Connection Mode: Permanently
Transfer Mode: Binary
6.5 For Processing Parameters, Specify the following
File construction mode: Add Time Stamp
File Type: Binary
6.6 For Content Conversion Parameters, Specify the Following
RecordSet Structure:
Adapter Status: Active
The receiver file adapter is now configured. Save your Communication Channel.
Create an Receiver Determination.
7). From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1) Select your sender service and interface.
Sender:
Party: blank
Service: Sender service(Business system)
Interface : Sender interface
7.2) In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
Create an Interface Determination.
7.3) Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1) In the Receiver Determination you just created, have a look at the area Configuration Overview for Receiver Determination at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2) In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3) You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5) When you are done , Save the Interface determination object.
8.) Create a Sender Agreement.
In the left hand frame , right click on Sender Agreement ->New
8.1) Specify the following:
Party: blank
Service: Select your own Business system
Interface: Outbound Interface
8.2) In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.) Create a Receiver Agreement.
Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1) Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2) In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
Specify the following:
Party: blank
Service: Select your own Business system
Interface: Inbound Interface
9.3) In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
Your Configuration is complete. Activate the objects.
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Step2:Repository
1) From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
From the list of Software Component Versions, Choose your own software component version .Click Import.
3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
Your NameSpace is urn:idoctofile
4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
After this specify the connection parameters to the R/3 system:
4.1) System :sapfox
4.2) Client :800
Then Save it. The new namespace will be visible under software component version node in the left frame.
Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3) Application server:172.25.5.7
4.4) System number:00
4.5) User name: developer
4.6) Password: Password of Sap R/3 system.
Then click continue .You will find IDOC node. Click on this node and select the Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5). Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6) Create new data types.
6.1) Right click on Data types and select New.
Your Data Type is :dt_file
In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
Save the object.
6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
no need to create Data types. They are imported directly as Message types.
6.3) To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
Select the following.
6.3.1) Category: XSD.
6.3.2) Messages: From All Available Global Elements.
6.3.3) File:
Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7). Create a new Message Type.
7.1) In the left hand frame under Interface objects, right click on the Message types and select new.
7.2) Give a suitable name to the Message type.(MT_ messagetype).
7.3) For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
Save it.
8). Create a Message interface
8.1) In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
Save it.
9) . Create a graphical mapping between the target document and the sender .
9.1) In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2) As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.
9.3) As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.
Save It.
9.6) You can also Test your Mapping by selecting the 'Test Tab'.
9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10). Create an Interface Mapping.
10.1) In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2) Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3) Target interface: Your Inbound Interface( The Target document interface).
Then Select 'Read Interface' and Assign your 'Mapping Program' .
Mapping Program: Your Message mapping.
Then Save it.
11.) Finally , in the left hand frame ,go to your change list and Activate it
STEP 3: Directory
1) From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
Create a Scenario Object
2). The First Step is to create a Scenario Object
This will serve as container for all your configuration work. Create and save a scenario object
3) In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) . Create a Communication Channel.
6). Expand your service and right click on Communication Channel. Name your Communication Channel
Here we need to configure the adapter.
Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
For the Receiver, Specify the following Parameters
6.1 For the adapter type , use the F4 help and select FILE.
6.2 Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3 Specify the following parameters.
Transport Protocol: File Transport Protocol.(FTP)
Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
Adapter Engine: Integration Server
For the File system access Parameters, enter the following
Source Directory:Test
File Name: Input.txt
6.4 For the FTP Connection Parameters, Specify the Following
Server: 172.25.5.240
Port: 21(by default)
Data Connection: Passive
Connection security: None
Connection Mode: Permanently
Transfer Mode: Binary
6.5 For Processing Parameters, Specify the following
File construction mode: Add Time Stamp
File Type: Binary
6.6 For Content Conversion Parameters, Specify the Following
RecordSet Structure:
Adapter Status: Active
The receiver file adapter is now configured. Save your Communication Channel.
Create an Receiver Determination.
7). From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1) Select your sender service and interface.
Sender:
Party: blank
Service: Sender service(Business system)
Interface : Sender interface
7.2) In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
Create an Interface Determination.
7.3) Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1) In the Receiver Determination you just created, have a look at the area Configuration Overview for Receiver Determination at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2) In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3) You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5) When you are done , Save the Interface determination object.
8.) Create a Sender Agreement.
In the left hand frame , right click on Sender Agreement ->New
8.1) Specify the following:
Party: blank
Service: Select your own Business system
Interface: Outbound Interface
8.2) In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.) Create a Receiver Agreement.
Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1) Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2) In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
Specify the following:
Party: blank
Service: Select your own Business system
Interface: Inbound Interface
9.3) In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
Your Configuration is complete. Activate the objects.
plz rewards points
vikas -
Hello
a novice question about RFCs.
Documentation I have says that I need to import the model and then bind the model object to a context model to be useable.
I have a BAPI that I have imported by creating a model in my application.
I am able to set parameters and call the execute method in the Input type class of the model without binding the model to any context so thought I could carry on without the binding.
However I am having trouble accessing the return type or message from the BAPI after execution and was wondering if this requires the binding?
ThanksHi Harnomit Babraa ,
Can u please tell , how u r executing the rfc without binding it to the context??
have u checked this doc?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/webdynpro/wd%20java/wdjava%20archive/creating%20a%20web%20dynpro%20application%20accessing%20abap%20functions.pdf
regards
Sumit -
Use EOIO on Sender RFC and outbound ABAP proxy calls
In the comm channel of SOAP and FILE there is a simple flag to set for QOS = EOIO
In Plain HTTP adapter a QOS parameter can be supplied.
IDOC uses control record tricks or a Receiver adapter option.
But what about the RFC and XI adapters.
The docu states QOS of EOIO for RFC and XI adapters is possible.
How is set for sender RFC and Sender XI adapters?
regards
PhilPhil,
I was discussing with Michal about this.
I suppose it is not fully EOIO, because you don't send directly from the outbound queue to the inbound queue. The AE service may not have a specific queue for that message, until the queue is associated in adapter module. Maybe (just maybe), if you get unexpected extra processing in the initial AE reception of the message (and hence, before the queue is set, in adapter module), you may have some inconsistencies with the processing order in sender system.
But again, that is just a speculation.
I'm not sure what is the behavior it'll have.
And even if what I speculated is right, it is a really short amount of time.
But again, EOIO would not be 100% guaranteed (maybe 99% hehe).
But sometimes (most of the times) that is not enough.
Regards,
Henrique. -
Hi,
There is this little concept about RFC adapter
I would like a liitle clarifiaction about..
Here it goes..
Let's just say I have made an RFC in R/3.
The same I have imported In xi.
now when we say RFC ...By definition
it is a remote enabled function module.
We import the "interface" of the Same in Xi
So if I make changes in the BODY of the RFC in
R/3... do i need to reimport it in XI.
Besides when XI's reciver RFC adapter is using the
Rfc's interface to make changes in R/3
is it using a Copy of this RFC created in R/3
I would like to intercep at the point it's doing so...
tried putting a break point in the body of rfc.
Another question is regarding RFC sender adapter
Program ID..tcp Ip protocol.
Conceptually How does this connectivity takes place
I tried and it worked ...
I dunno How to explain this connectivity taking place
just on the basis of PROGRAM ID...
Kindly HelpHi Deepak,
+
>>We import the "interface" of the Same in Xi.So if I make changes in the BODY of the RFC in R/3... do i need to reimport it in XI.+
Yes you have to.
>>Another question is regarding RFC sender adapter.Program ID..tcp Ip protocol.Conceptually How does this connectivity takes place I tried and it worked ...I dunno How to explain this connectivity taking place just on the basis of PROGRAM ID...
·An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system).
·If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the corresponding JCo server program.
http://help.sap.com/saphelp_nw04/helpdata/en/09/c88442a07b0e53e10000000a155106/content.htm
Hope this will clarify your doubts.
Regards
Suraj -
Hi all
We need to test some data loads for RFC and connection settings . How do we go about it ?
Thanks allHi,
Actually choosing 'Check' option on source sytem is sufficient to check the conection seetings. If you do not satisfied with this, Do full load of any master data or full/initial upload of selective Transaction data(by filling setup tables).
With rgds,
Anil Kumar Sharma .P -
Hi all,
I want to know more about RFCs. What is the diff between transactional async and sync RFCs. Can u tell me vividly so that it can help me in real time.
Also can u send me some good docs on RFCs in my mail id [email protected]
Pls experts help me on RFCs and explain me vividly.
I will reward points.
With regards,
Abir.Hai Abhir
Sending system side(SEND--800)
Create function module by using Tcode SE37 or SE80
goto attributes select remote function
activate
Receiving system side(RECE--000)
goto Tcode SM59
here select the R/3 Connections-->click on Create Button
give RFC Desstination : TESTRFC
Connection Type : 3 for Connecting two systems
Description : Some meaningful Description
Press enter
give Target system Name : SEND
Language : EN
Client : 800
user Name : sapuser
Password : xxxxxx
save this connections & click on test connections(f8)
& Remote logon(f7)---> it will open a session
with client 800 that is your sending system
then only your RFC is correct
create a report in SE38 Tcode
data : c1 type i.
data : itab like mara occurs 0 with header line.
call function 'ZRFCFM' destination 'TESTRFC' --->Function Module 'ZRFCFM' your just create at Sending system
exporting
importing
exceptions.
Here are the steps.
SM59 Transaction is used for Connection Establishment with Destination.
When you establish a connection to a client through a destination, the HTTP connection must first be entered in transaction SM59.
There are two types of HTTP connection in transaction SM59: Call transaction SM59 to display the different RFC destinations.
The HTTP connection to the external server (connection type G) and the HTTP connection to the R/3 system (connection type H) are different only in their logon procedures. Their technical settings are the same. To display the technical settings, double-click a connection.
You can choose from three tabs. Under Technical Settings, you can specify the following:
・ Target Host: The host to which you want to connect.
Note that if you are using HTTPS as a protocol, you have to specify the full host name (with domain).
・ Service No.: Here, you specify the port. The destination host must of course be configured in such a way that the specified port understands the corresponding protocol (HTTP or HTTPS). See Parameterizing the ICM and the ICM Server Cache.
・ Path Prefix: At the time when the connection to this destination is initiated, the system inserts this sub-path before ~request_uri.
・ HTTP Proxy Options: Here, you can configure a proxy for HTTP connections: You can determine the proxy host and service, as well as users and passwords for the HTTP connection.
The tab page Logon/Security will be different depending on whether you have selected a HTTP connection to an external server (connection type G) or a HTTP connection to an R/3 system (connection type H).
HTTP Connection to an External Server (Connection Type G)
Choose the connection you want to use. You can choose from the following logon procedures:
・ No Logon: The server program does not request a user or password.
・ Basic Authentication: The server program requests a user and password. Basic Authentication is a standard HTTP method for authenticating users. When a user logs on to the target system, he or she provides a user ID and password as authentication. This information is then sent in a header variable as a Base 64-encoded string to the server, through the HTTP connection.
・ SSL Client Certificate: If you use client certificates for authentication, the client authentication is performed through the Secure Sockets Layer (SSL) protocol. In this case, you must also select the SSL Client PSE of the SAP Web AS that contains the relevant certificate for the authentication. The target system must handle the issuer of the SAP Web AS client certificate as a trusted system.
Under Logon/Security, you can also activate SSL to ensure that HTTPS is the protocol used (if you select SSL, make sure that the correct port is entered under Technical Settings). In the security transaction STRUST you can determine which type of SSL client is used. (Getting Started with the Trust Manager, Trust Manager).
The field Authorization for Destination has been implemented as an additional level of protection. We recommend that you specify a user and password for the RFC destination.
HTTP Connection to an R/3 System (Connection Type H)
Here, you can specify more settings for authentication in the target system.
The settings under Technical Settings and Special Options are the same as for connection type G. Under Logon/Security, the connection type H has additional logon procedures. As with external servers, you can activate and deactivate SSL and specify an authorization.
Because the target system is an SAP system, you can set the client and language for the logon as well as the user name and password. If you check Current User, you have to specify the password.
The following authentication procedures are available: Basic Authentication, SAP Standard, and SAP Trusted System, and SSL Client Certificate.
・ HTTP Basic Authentication: Logon with user and password
・ SAP Standard: This procedure uses an RFC logon procedure. The RFC Single Sign-On (SSO) procedure is valid within the one system. The same SAP user (client, language, and user name) is used for logon.
・ SAP Trusted System: Trusted RFC logon to a different SAP system (see Trusted System: Maintaining Trust Relationships Between SAP Systems)).
・ SSL Client Certificate: The SSL protocol enables you to use client certificates for the logon.
Type G/H (SM59)
Timeout:
When sending a HTTP request, you can use this parameter to specify the maximum response time for the connection.
HTTP Setting:
You can use the HTTP version to specify the protocol version of the HTTP request (HTTP 1.0 or 1.1).
Compression:
You can use this option to activate the gzip compression for the request body. This can only be activated in HTTP Version 1.1.
Compressed Response:
In the standard setting, the SAP Web Application Server sends the Accept Encoding field as a header field with the value gzip, if the application server can handle this compression. This notifies the partner that the caller can handle gzip decompression, and that the partner can send compressed data. If you want to prevent a compressed response being sent, choose the option No.
HTTP Cookie:
You can use this option to control the way received cookies are handled.
You can specify the following for cookies:
・ Accept them automatically
・ Reject them automatically
・ Accept or reject them in a prompt
・ Use a handler for the event IF_HTTP_CLIENT~EVENTKIND_HANDLE_COOKIE to process the cookies in the program.
・ In the next section, you can read about the parallelization of requests.
Check this thread
Re: SM59
Thanks & regards
Sreenivasulu P -
Hi Experts,
I want to know more about RFC's .
How to work on RFC's
Examples on RFC's
Doc's on RFC's
Please let me know all these
Regards
khannaHi ,
<b>RFC:</b>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.
<b>Synchronous RFC:</b>
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
<b><b>Transactional RFC (tRFC) and Queued RFC (qRFC</b>).</b> tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
<b>Transactional RFC:</b>
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
<b>Queued RFC:</b>When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
For more information on RFC, please go through the link.
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
Regards,
Bhanu -
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 -
Difference between RFC and Webservices.........??
Hi
<b>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</b>
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
<b>
Virtual Interface</b>
<b>End PointType</b> : 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
<b>
Application</b> -- ex FI-AR
<b>Business Object</b> -- ex KNR
Next Screen
<b>Porfile</b>
>>> Basci Authorization:SOAP Pro
>>> Secure SOAP Profile
Best Regards
Ravi Shankar B
Message was edited by:
RaviShankar B
Message was edited by:
RaviShankar BHi 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 -
Is there another way of getting apps from the appstore without putting your credit card number in, ive heard about the itunes gift card thing can anybody just give me more info about that and how i can buy free things free things from the appstore...pls help as im only a teenager and have no credit credit and my parents dont trust me with theres and they dont care about the fact that you can set up a password/.... PLEASE SOMEONE HELP I WILL BE SO GRATEFUL... And i would really like to get the iphone 4 but if there is no way of etting apps without your credit number then i would have to get a samsung galaxy s3 maybe ...
You can set up an Apple ID without a credit card.
Create iTunes Store account without credit card - Support - Apple - http://support.apple.com/kb/ht2534 -
What is the diffrence between BAPI and RFC and business object
Hi Experts,
Can anybody tel me what is the diffrence between RFC and BAPI , and also what is ther relation with business object?
Thanx in advance.
Nilesh HiwaleHi,
BAPI's are associated with Business Objects and also they are RFC enabled.
But RFC's are the FM's which can be called from external systems, those FM's can be used in many places based on the applications..
Check these Links
whats the difference between BAPI and RFC??
Diff. Between BAPI and RFC
Regards
Kiran -
when i start firefox, everything starts normal then my homepage (igoogle) starts to load, gets to about 30% and stops. from there i can click on links or bookmark and a new tab will open but no page will load. i can't get anywhere. then when i close firefox it appears to close normally but when i try to reopen firefox i get a message that firefox is still running but not responding and the only way to shut it down is to reboot. when it first occured i was running beta 6 (since it became available, i also used beta 4 & beta 5) i then uninstalled beta 6 and downloaded and installed ver 5 same problem. i then did a system restore to a time before the problem.. no luck. i'm not sure what to try next. IE & chrome both work fine
I'm in exactly the same boat - dead at blue screen, only option is to salvage using target mode.
I don't currently have access to another Mac to do target mode. I was planning to buy a new Mac this fall anyway, though. 2 questions in preparation for that purchase:
1) Is there anything I can do before buying a new Mac to make the salvage process more successful? ie, should I spend the time and money going to the genius bar to have them help me get from totally crippled to partially crippled? (As for expertise, I'm a proficient consumer-grade user, but Apple Support walked me through the safe-boot process, etc.)
2) Is Apple going to provide 10.5 once it is released to people who buy a new Mac in these 6 weeks pre-release?
Thanks for your help,
Bailey
Maybe you are looking for
-
What I am trying to achieve is a page with one column for all the text I write, but I also want to show two tables (one placed beside the other, not underneath the other) so on the part of the page where I am showing these tables, I would like to hav
-
How do I get a 2GB jaz drive to work with a mini mac?
I have a Microtech adapter (usb to scsi 25pin adapter) to hook a 2GB jaz drive to a Belkin Hub. I insert a 2GB jaz disk into the jaz drive and can't get the disk to show up on the desktop. Have the latest Iomega driver installed on the computer. Help
-
When I load a XML in a XFA form can I specify the font color?
When I load a XML in a XFA form can I specify the font color? Or can I specify background color, font type(bold, ...).
-
Hi, in 11.5.10 how to : Setting up profile options 3 new system level profile values in the iProcurement setup section : n POR : Proxy Server Name - Proxy server name if the customer has a proxy setup n POR : Proxy Server Port - Proxy server port if
-
Question on the management console ESSO-PR and ESSO-LM
Fiends. I can install the administration console of the ESSO-Logon Manager and Management Console Password Reset in one server Thanks