Proxy or RFC or IDOC?

What way is better to connect from XI to web as 7.0?
In what cases is better to use rpoxy then RFC or IDOC and in what cases is better to use RFC or IDOC then proxy?

Hi,
always use IDOCs when possible - error handling etc.
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Similar Messages

RFC or IDOC or ABAP Proxy

Hi,
What is the best way(R3 Side) for standardization?
R3 <-> Legacy.
I've read all related article on sdn, but i am not still clear on which best way RFC or ABAP Proxy or IDOC in real life.
if you are, what is suggestion?
thanks
dennis

Ogawa,
There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
---Satish

SAP R/3(Client100 using Proxy)---- XI----- RFC(SAP R/3 client 222) Scenario

Hi all,
I have the requirement to work on SAP R/3 ( with client 100 by using outbound Proxy)-->XI--->RFC(R/3 Client 222).
i have done IR & ID Part. Now i am going to create Report in R/3 side (100 client). But, it is synchronous, i am getting so much confusion. Please help me how to write the code for it.
The RFC is BAPI_EXCHANGERATE_GETDETAIL.
I created Request message, Response message for sender.
The message mappings are as follows:
For Request:
Sender Request------> BAPI Request
For Response:
BAPI Response---->Sender Response.
Interface mapping
Sender Interface---->BAPI.
Request message contains the fields:
Rate Type,
SourceCurrency,
TargetCurrency,
Response Message contains:
Exchange rate,
FactorFromRatio
FactorToRatio.
Please try to understand this requiement and help me to write code for this.
Thanks in advance.
Regards,
Nagarjuna.

Hi Nagarjun,
If you look at the exporting and importing paramters of your Method EXECUTE_SYNC...
You would find the abap equivalent of your Message Type. Hence you know all the fields.
No it depends on the business Logic, or ratheer what the RFC is suppose to be requested for is filled in an an Input paramter to the Method.
This can be an IDOC To, in that case your MT should be similar. Fill in the transmiaaion IDOC values.
OR you can Actually harcode the values, make your Itab, and send it across ( as this is just for test purposes )
Hope this helps.
Regards
Abhishek

Could XI/PI integrate R3 without RFC or IDoc?

Hi, Experts.
           i got a problem, there is a requirement that my customer wanna to reduce RFC in their R3 by PI, they call it as "RFC
migrates to SAP PI"
           i am wondering that could SAP XI/PI get R3 Data directly without RFC or IDoc interface in R3?
           Please help me, thank you a lot?
Edited by: Ivan Lin on Jul 28, 2009 9:57 AM

>>i wonder whether pi could get the source system's tables,
I won't suggest to maintain ECC data in XI,why do you want to replicate same data in two different servers.
One option can be to use File instead of RFC,IDOC or Proxy.
This wont require any coding and will solve your purpose too.
You can take hints form the below blog and see how he is dumping IDOC's via a XML port( the blog is mainly to send IDOC in batch mode but you can use for individual IDOC too)
We are using the same approach to integrate CRM without any IDOC,RFC or proxy coming in XI.
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
Thanks
Aamir

RFC to IDOC

Hi,
My scenario is RFC to IDOC
When the IDOC is received it triggers the Create/change sales document program.
for Create i have 1 Custom IDOC and for Change/deletion i have another IDOC.
The inbound IDOC should be able to handle Creation/Change and deletion.
already i have imported RFC and IDOC's
So, could you please confirm me once again...the procedure in IR and ID
Regards,
Yeswanth

Hi,
This may helps you...
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b803343d711d1893e0000e8323c4f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4943f2b7-0a01-0010-37af-faff35b2f08c
For IDOC Scenarios you need to do the ALE Configuration First.For the ALE Configuration you can look into this Blog:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
In this blog(/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step) Michal mentions about Gateway Service and Gateway Host/Server. How and where do I find this information. Can somebody clarify what it means. also in this blog /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters he talks about something about partner profile. What is this?
Regards
Aashish Sinha
PS : reward points if helpful

RFC to IDOCs

Hi Experts,
I have a scenario for RFC -- XI -- IDOC
In my XI dev. system already i have imported RFC and IDOC's
I have 2 Custom IDOC's
First IDOC is for Create
Second IDOC is for Change/Delete
Based on the condition i should select either one of the above IDOCs.
So, How many Message Mappings shall i need to create or
If i import both IDOCs at Receiver side and can i do the Mapping.
Awaiting for your response and Reward points for helpful answers...
Thanks & Regards,
Ramana Kumar. A

Thanks Varun,
based on the condition here,
field1 map with E1EDK03 (field: IDDAT) and the description here is, Fixed value = 001 set up in connection with the next field.
Here i map constant 001 to E1EDK03 node
Is this correct?
Next Field here is DATUM and the desc. here is If = `1´ then map date from field1 else if `blank`
field2 map with E1EDK03 (field: IDDAT) and the description here is, Fixed value = 002 set up in connection with the next field.
Here i map constant 002 to E1EDK03 node
Is this correct?
Next Field here is DATUM and the desc. here is If = `1´ then map date from field2 else if `blank`
Regards,
Ramana.

How to handle HTTP-POST encrypted data for ECC Using proxy or RFC

I have a scenario HTTP-POST ->PI->ECC.sender is HTTP Post send encrypted data i need to handle the data and stored in to SAP ECC with out decrypt using PI .what should i take for receiver can i use inbound proxy or RFC and how can handle the encrypted data for decrypt.
Regards
Ravi

1. my sender is HTTP POST . what should i configure in sender communication channel in SAP PI .like SOAP or HTTP .What are the parameters i need to pass .
>>>
If you are on PI 7.3 and above, configure the HTTP AAE adapter - Configuring the Java HTTP Adapter on the Sender Channel - Advanced Adapter Engine - SAP Library
2.while using inbound proxy for encrypted data i need store the data in to table , the same proxy can i call another outbound service for decrypt same data.
>>>>
Yes you can always a proxy within a proxy.

What is RFC and IDOC Adapters in XI ?

Hi,
What is the RFC and IDOC Adapters in XI , in which scenarios we use this adapter , what is the advantages and disadvantages of RFC , IDOC ? can any help me out.
Thanks & Regards
Surendra M

Surendra,
What is the RFC and IDOC Adapters in XI :
IDOC: Generaly standard IDOCs are used to update the data in R/3 or to extarct the data from R/3.
RFC: Are generally used for synchronoue scenarios.
in which scenarios we use this adapter
For example you can use the IDOC ORDERS05 to post the sales orders.
Similarly you can use BAPI_COMPANY_GETDETAILS to fetch the company details.
what is the advantages and disadvantages of RFC , IDOC ?
Advantages: Both can be used for data retrival and posting. RFC can be used for synchronus purpose but IDOCs are always asynchronous.
Disadvangages: If you are using custome made RFC/IDOC then you have to import the RFC/IDOC into XI every time when you make any small changes in the structure.
Also go through this blog to choose the right adapter to integrate with SAP systems.
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Regards,
Sarvesh

Is it possible? RFC to IDOC Scenario

Hi,
Is it possible direct RFC to IDOC scenario ?
How many message interface? Message mapping? Interface Mapping are neccessary.
(scenario is simple and i think there is no need for message type or data type as i can map my fields easily in message mapping)
I do not want to do RFC--File----IDOC scenario
regards
hussaan

searched on forum and found this solution
Three checkpoints:
1. Make sure you have entered the correct outbound and inbound interfaces.
2. Make sure you have activated your interfaces and mappings.
3. Make sure the cache is up-to-date (you can refresh cache by transaction sxi_cache).
Other very important tip when you create interface mapping.
Probably you did not select the inbound interface before selecting the Interface Mapping. First select the inbound interface (target interface), then you will see the interface mapping in the list
Go to your interface mapping and activate it. ( You might have to make a cosmetic change , like changing the description).
2. Go to transaction SXI_CACHE in the XI box and do a complete cache refresh. Once it is done, check that the mappings shown are the latest one.
ateeq
Edited by: ateeq lodhi on Nov 2, 2008 7:46 PM

Regarding rfc and idoc sender

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

RFC and IDoc

Hello
Both RFC and Idoc adapters are used to connect to SAP system from XI. Why is that we have to configure RFC Destination, port and partner agreement for Idoc while we do not have to do that for RFC ? Both use the same RFC protocol still we do the configurations only for Idoc. Can someone explain to me the technical reasons why we do that
Thanks
Radhika

Hi,
RFC Adapter resides in Adapter Engine,
IDoc resides in I.E,when you triiger an IDoc it directly Hits I.E,like communication with Other SAP System.
Thats why we need to create the port .....details for IDoc.
But coming i future it IDoc adapter ,HTTP Adapter moving in to JAVA Stack,wait till 2010 july.
in PI7.1 EHP1 there are too many changes in Idoc adapter,like Idoc package we can do at Sender IDoc adapter level.
Regards,
Raj

Rfc to idoc...... how to create order

hi,
i worked on rfc to idoc scenario...... using matmas idoc to create material from r/3 system to IDES system through (rfcxiidoc) scenario
Now i want to do it to create an order using rfc to idoc
I am not sure which IDOC structure i will use and which fields are mandatory and optional?
I am looking to do that scenario with minimum required fields
hussaan

hi,
The fields which are mandatory in case of order creation depends on your system settings.Like for a sales order or purchase order,you first create an orderusing transaction me23n for purchase order and va01 for sales order and check which fields are mandatory and get minimum no of required fields.
In this PO to SO scenario Idoc message controls will also come into picture.
Then after doing the required ALE settings you can test your scenario.
regards,
ujjwal kumar

Java Proxy - XI - RFC Synchronous Scenario OUTBINDING Problem.

Java Proxy -> XI -> RFC Synchronous Scenario. Problem
Hi,
 I'm doing a Java Proxy -> XI -> RFC Syncronous Scenario.
 A Java Server Socket is running as a Demon. When a client make a request to the Java Server Socket, this one call Java Proxy Client and set up the parameters.
 The first time that execute the scenario it works perfectly but no the next one and so on.
 The error when I check the monitor (TCODE: SXMB_MONI) is in PLSRV_OUTBOUND_BINDING.
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">no outbound binding found.</Trace>
<Trace level="1" type="T">No standard agreement found for , DES210_DEV, , JPX_DEV, urn:servipago:SERVIPAGO_SAP_02, mi_os_t1</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
And it has sense, because my scenario doesn't begin with the execution of FM (RFC).
A Hint, my services in the first try are:
 Sender Service: JPX_DEV (Java Proxy Client)
 Receiver Service: DES210_DEV (R/3 4.6C)
But the second try and so on the services that I saw in the monitor are:
 Sender Service: DES210_DEV (R/3 4.6C)
 Receiver Service: JPX_DEV (Java Proxy Client)
I can't understand why they swich each other.
Any idea?

Hi,
Outbound binding problem is because of Reciever Determination/Agreement is not activated or refreshed correctly.
Try to recreate or refresh and activate it. Then check it.
also do the cache refresh in SXI_CACHE.
Also in go to Integration Builder(XI home page)->Administration->Cache Overview and do all the cache refresh.
Hope this helps
Regards,
Moorthy

RFC,ALE,IDOC,EDI,BAPI

HI,
FOR NET WEAVER XI what topics i should be perfect to work with xi.
in rfc, ale ,idoc,bapi , edi.
knowledge in the topics is enough or i sholud be perfect in above topics .
plz give necessary sugessitions.
thanks.

Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part I
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part II
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III
why dont you start by looking into those.

RFC,XIF,IDOC,BDOC

Guys,
This is an entry level question. I am new to SAP. I would like to have a brief explanation of RFC, XIF, IDOC and BDOC.
Alos how they are related.
Will reward points.
Thanks,
Narasimha

Hi Narasimha,
RFC stands for Remote Function Calls So if you have a program say in R/3 system which is Remote enabled then you can call this program from CRM system.
XIF - External interface. XIF adaptors used to exchange the data from External system to SAP system.
Bdocs(Business document) in CRM are equivalent to an IDOC(Intermediary document) in R/3. They are used to exchange the data with the systems connected with CRM. Bdocs are of two types:
a. Messaging Bdoc(MBdoc) : Used as Data container in CRM
b. Syncronization Bdoc(SBdoc) : For Data Synchronization with Mobile Applications
More about BDOC :
The definition of BDoc messages does not contain implementation details.
BDoc messages can be represented in various way.
Depending on the environment an optimal representation is used, e. g.
CRM Server : Internal tables
Laptops : ADO record sets
Non-SAP System : XML
You can see all the processed Bdocs in SMW01. All the Bdoc types you can see in the SBDM transaction.
Reward points if my post helps!!
Best regards,
Vikash.

Proxy or RFC or IDOC?

Similar Messages

Maybe you are looking for