Help on web to IDOC scenario

Hi Guys,
I hav a scenario whr i need to get the currency rate from url ( http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml ) once in a day and have to post thru XI using IDOC (exchange_rate01) in R/3.
Should i go for plain HTTP adapter or wat must be approach??
if smbd can detail on aproach for XI dev plz...
Regs,
Anshul

Hi
Just check it out for full details
IR
1)define Data type for sender and receiver system, later Message Type, later Message Interface.
2) Define you mapping and Interface mapping.
3)active your changes
ID
1)Define Serder Comunication channel type SOAP.
in DEFAULT XI PARAMETER you must put Message interface and Namespace of serder structure defined in IR
2) Define Receiver Communication channel.
3)define Receiver Determination
3)define Interface Determination
4)Define Sender agreement
5) Define Receiver Agreemen.
6)Active your changes.
DEFINE WEB SERVICE:
7)go to tool>enviroment>define Web services and put this string
http://<Host>:<Port>/XISOAPAdapter/MessageServlet?channel=:<Bussines_System>:<Communication Channel>.
Example: http://srv-xi01-adm:50000/XISOAPAdapter/MessageServlet?channel=:SCR_D:scr_d_soap_customer_sender
8)next step select MI of list
9)en next step you must define your sender BS and Message Interface.
10) Save Web service.
Test ur service with for example XML-Spy
Steps to make a request using the XML SPY:
1. Open the XML SPY, in the menu go to SOAP  Create new SOAP request
2.it will open a new window you will provide the path wsdl file that you have recently save .
3.Click on OK button a new window will be opened which shows the SOAP request
4.In the menu choose SOAP  Send request to server
5.Asynchronous Request: If your request is successful you will receive a SOAP response which will be empty response in an asynchronous request .
to configure file receiver adapter take in mind these blogs
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
Thats all!!
Thanks
Dheeraj Kumar

Similar Messages

Help on file to idoc scenario-

Hi Homiar,
I have the same scenario like u
flatfile -> XI -> Idoc
I have the flat file in my XI system i have file inbound adapter and idoc outbound adapter.
i have created the interface objects like for file i have created a outbound interface and for idoc i have imported the interface and i have mapped it as an inbound interface ,
while i process the file i get the following error in the SXMB_moni
<SAP:Text language="EN">Technical routing: Unable to find endpoint for sender XI,FILEINBOUND/http://namespace for receiver R3,ORDERS.ORDERS04/urn:sap-com:document:sap:idoc:messages</SAP:Text>
Please help me .
very urgent......
thankx in advance.
shree

Shree,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
For the Inbound File Adapter, check if you have an entry like :
XMB.TargetURL=http://<server>:80xx/sap/xi/engine?type=entry
Replace <server> & xx with appropriate values.
If this doesn't work, please send me your Inbound File adapter.
Regards,
Homiar.

Help on EDI to IDOC scenario using seeburger

Hi,
Anyone plzz explain me edi 850 to idoc orders05 scenario. at the same time how generated idoc will creat salesorder.
Thanks,
Seenu.

Hi,
You can see some basics about this integration in this blog:
/people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
You need to get the 850 xsd and import it in IR. Then map your xsd to order05 idoc. Then to test first seeburger adapters need to be deployed. Now you need to configure your classifier and then the splitter if you have multiple 850s within one transmission. Then finally the BIC module to convert edi to xml. Then once you have your xml you need to do your message mapping with the idoc and send to sap.
Once you install the seeburger adapters in your landscape you will have the documents for each of these ones. Go through them and configure.
Regards,
---Satish

File to Multiple Idocs scenario. Pls help

Hi All,
For Single File to Multiple Idocs scenario i am referring blog --
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
Suppose my source file is
AAA, BBB,CCC
111,222,333
ZZZ,ZZZ,ZZZ
I want to make 2 IDOCS for the first 2 records (AAA, BBB,CCC   and 111,222,333)
and do not want to make IDOC for the 3rd record -- how to achive this.
Regards

Hi,
If the condition is like, for 'AAA' and '111', IDocs to be generated, then do as follows.
If IDOCs are of same type.
1. Value
> Equals -
> createIf -
> IDOC
   Constant('AAA')
2. Value
> Equals -
> createIf -
> IDOC
   Constant('111')
3. Value
> Equals -
> not -
> createIf -
> IDOC
   Constant('ZZZ')
If 2 IDocs are of differnet types,
create different mapping programs with same logic.
If 2 IDocs are to be generated based on the record no in the file rather than the first field value, i think you can go for Global container.
Refer these,
[http://help.sap.com/saphelp_nw04/helpdata/en/ee/bf9640dc522f28e10000000a1550b0/frameset.htm]
[http://help.sap.com/saphelp_nw04/helpdata/EN/49/1ebc6111ea2f45a9946c702b685299/content.htm ]
[http://help.sap.com/saphelp_erp2004/helpdata/en/75/8e0f8f3b0c2e4ea5f8d8f9faa9461a/frameset.htm]
thanks.
Edited by: P.Ravi Varma on Apr 22, 2009 10:27 AM

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

File to IDOC scenario error...

Hi all,
we hhave created an File to Idoc scenario .
we are getting the following error in SXMB_MONI t-code.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BUS_SENDER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can any one plz say wat this error might be..
TIA
Regards,
Raj

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

IDoc scenario

Hi all,
I have done file to idoc scenario. in that
No error in sxmb_moni
IN SAP system( we05)
EDI: Partner profile inbound not available
Status 56
Message from
Control records is-> patner
Recipient Information
(EMPTY)
IDS47800
LS
Sender Information.
SAPC08
NW4SR1
LS
When select the options in
IDOC adapter
1. Apply control record from the payload.
I took help from these wlg
https://websmp201.sap-ag.de/nw-howtoguides
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
if IDOC adapter , select the options,
1. Apply control record from the payload.
2. Take sender from payload.
3. take receiver from payload.
Then
Error in sxmb_moni
Error: Copy sender from payload: Sender not in
Objects that have created->
Object created in Sap(r/3)C47 for client 800
SM59-> C08_010
WE21->(NW4SR1_C08)Port->NW4SR1_C08,R.d.->C08_010
BD54->IDS47800 (Client ->800)
WE20->IDS47800;Patnerno->IDS47800,P.T.->L.S.
              Inboudn parmtrs->CREMAS( Patnerno IDS47800,P.T.->LS,M.T.->CREMAS,Process code->CRE1
Object created in XI C08 for client 010
SM59-> IDS47800
IDX1-> SAPC47,Client->800,R.D.->(IDS47800)
IDX2-> SAPC47,Idoc type->cremas03,client 800
/* BD54-> NW4SR1,Client 010 (NW4SR1) **In sld Sender service l.s. NW4SR1 updated in Business system (pdp( third party) in Integration Directory                    */
SLD->T.S.(WEB as abap and logical system is ->IDS47800)
           B.S. whose name is VAGUABAP(WEB as abap for above T.S.)
In Integration Directory-> sender service(pdp) and receiver service(VAGUABAP)
May i go for modelview concept? when we go for model view? can any body tell compleate steps for file to idoc with an example(not IR and ID Objects). or send any document. mailid -> [email protected]
Friends, Please find where I have done mistake. Your help is rewardable.

Hi,
Have a look into this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Techincal System and product will be created. Then create a business system for the R/3 technical system. Also fill out Partner profile entries in the R/3 in WE20 ->outbound parameters and test it..
Regards,
moorthy

Reg:Steps in IDOC Scenario

Hi,
    I am very new to IDOC concept so can anyone tell me what is the use and why do we want to create,
1)RFC Destination
2)Port
3)Logical sysytem name
4)Partner Profile ,in IDOC Scenario and also let me know the steps that I have to implement while doing that scenario.
Thanks in advance
B.Lavanya

Hi,
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
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 : DSZVFGD
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:VILAS
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.7.116
          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

SOAP to IDOC scenario

Hello All,
I have a scenario where the sender system is outside our landscape and I need to post the PO data to SAP system using XI. I know its a SOAP to IDOC scenario but I am not given a wsdl but am given only a xsd and one XML as input. Can I use this XSD to create a sender message interface or is there any way I can convert the XSD to WSDL? Also, where should I give the path of the XML file in sender SOAP adapter?
And also I have to create a value mapping table where I have almost 4000 entries. Can any one let me know on how to create this?
I have browsed thru the SDN but havent found any information that I am looking for. Can anyone please help me on this.
I will be greatful if anyone can help me with Step by Step to SOAP to IDOC scenario.
Thanks and regards,
Neelima

I think what is this person asked to do is build an integration scenario using two business system
1. A business system understand web service technologies and also have a data definition they would like to use to communicate data with their business partner.
2. A business system which like to accept DATA in the format of IDOC.
So As long as we use XI as an integration framework, this is called SOAP to IDOC scenario.
I recomend to use the following steps to implement the integration need.
1. Understand the XSD data structure from the external service provider.
2. Using the external data definition create and outbound interface either SYNC or ASYNC format ( You have to discuss this with service provider for confirmation) in XI.
3. External service provider can use this outbound interface definition and associated data structure to send their data in their provided XML format to XI integration server.
4. Create an inbound service definition by using the XSD structure created for the IDOC you like to use.
5. XI integration server can use the inbound interface definition to pass the outbound interface message received once the outbound and inbound interface are connected using a configured scenario.
6. Using the outbound message type and inbound message type create a message mapping.
7. Using the message mapping create an interface mapping between outbound and inbound interface.
8. Create a WSDL from the outbound interface so that the service provider can use the service contract defined by the outbound interface in a web service enabled business system (Note: you have provided the data requirement in XSD format indicate that your business system is web service enabled). Make sure you are not getting fooled by the concept propose URL for the WSDL. You must provide the URL end point in created WSDL according to the following format.
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=<party>:<service>:<channel>
If the SOAP adapter channel belongs to a service without party, the address is as
follows:
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=:<service>:<channel>
9. Provide the WSDL to the service provider, ask them to use that WSDL to send data to your integration framework.
10. Configure the SOAP adaptor in sender mode, so that it can act as a end point to receive the XML data based on the XSD defined in the WSDL and convert the same to an XI document.
11. When u define the sender soap adaptor make sure you have selected the namespace and interface name same as the one you created for outbound interface.
Also recomend to read two How to guide related to web service and soap adaptor to complete your scenario.
Thanks

Required Help and Documentations for following Scenarios. URGENT

Hi every one,
I require help and materials for following scenarios:
1) RFC to IDOC
2) JDBC to RFC & IDOC
3) Mail to File
4) HTTP to RFC, JDBC & IDOC
5)WEB SERVICES to RFC & IDOC
6) IDOC to ABAP proxy
7) Java Proxy to JDBC
my email id: [email protected]
urgent plzz help me...
Message was edited by:
satish c

Satish,
I would suggest to go through sravyas weblogs where she has given all the links to all the scenarios:
/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
Also check this weblogs which they have explained with some scenarios:
Following are the links to weblogs which will help to develop the basic scenarios.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1 - File to File Part 1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 - File to File Part 2
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - File to Mail
/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i - Dynamic File Name Part 1
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii - Dynamic File Name Part 2
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address - Dynamic Mail Address
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi - Message Flow in XI
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
/people/michal.krawczyk2/blog/2005/08/22/xi-maintain-rfc-destinations-centrally - Maintain RFC destination centrally
/people/sravya.talanki2/blog/2005/08/18/triggering-e-mails-to-shared-folders-of-sap-is-u - Triggering Email from folder
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party - Handling different partners for IDoc
/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi - Modeling Integration Scenario in XI
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible - Testing of integration process
/people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects - Authorization in XI
http://help.sap.com/saphelp_nw04/helpdata/en/58/d22940cbf2195de10000000a1550b0/content.htm - Authorization in XI
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
/people/sameer.shadab/blog/2005/09/21/executing-unix-shell-script-using-operating-system-command-in-xi - Call UNIX Shell Script
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi - Transport in XI
/people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping - Using ABAP XSLT Extensions for XI Mapping
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure - Mail Adaptor options
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/sap.user72/blog/2005/11/17/xi-controlling-access-to-sensitive-interfaces - Controlling access to Sensitive Interfaces
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14 - The same filename from a sender to a receiver file adapter - SP14
/people/prasad.illapani/blog/2005/11/14/payload-based-message-search-in-xi30-using-trex-engine - Payload Based Message Search in XI30 using Trex Engine /people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i - XI : Configuring CCMS Monitoring for XI- Part I
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter - XI: HTML e-mails from the receiver mail adapter
/people/sap.user72/blog/2005/11/22/xi-faqs-provided-by-sap-updated - XI : FAQ's Provided by SAP
Regards,
---Satish

Error while executing a JDBC to Idoc scenario : No standard agreement found

Hello SAP PI Gurus,
I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.
<SAP:AdditionalText>No standard agreement found for ,
BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
While i test the configuration...i get an error in reciever agreement as mentioned above.
Can you pls help me in resolving this issue.
Regards,
Ravi

Hi,
I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
Thanks
Priyanka

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

IDoc to JDBC and JDBC to IDoc Scenario

Dear All,
I am working on IDoc to JDBC and JDBC to IDoc Scenario.
I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
Does anyone have completed STEP by STEP scenario document for this?
How my Idoc will sent to XI?
How XI will pick up data from IDoc?
How XI will Convert data to JDBC and UPDATE in Oracle Database?
And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
Where and When i can watch my process and data?
How can i test the whole integration?
I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE it gives me error
"Unable to refresh cache "NO_BUSINESS_SYSTEM"
"Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
Please solve all the above problems i will reward u points
thanks,
RP

Hi,
While we working on IDOC to JDBC interface..
We have to deploy JDBC Drivers?
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Configuring the Sender JDBC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
Configuring the Receiver JDBC Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
Idoc Reveiver adapter..
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Thanks,
Satya Kumar
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

Help on web to IDOC scenario

Similar Messages

Maybe you are looking for