on 11-23-2006 2:50 AM
hey guys
plese let me know how to do file-to-RFC scenario,i dont wanna use BPM(asynchronous) right now,please give me step by step solution as i m new to XI .
i would really appreciate any help
thanx
amir
Hi,
It is just like File to File Scenario.
1) Import the RFC created in the R/3 into the Integration Repository
2) Create Data Type, Message Type, Message Interface required for the File structure
3) Create Message Mapping/Interface mapping between File structure and RFC structure.
4) Configure all integrtaion directory objects like Configuration Scenario, Communication Channel ( File- Sender, RFC - Reciever), Sender/Receiver Agreement, Interface Determinations.
Assuming there is a RFC(SM59- TCP/IP connection) destination created in the XI to connect to R/3 . Also RFC is in place in the R/3 system.
Note this doc may help u in RFC programming-http://help.sap.com/saphelp_nw04/helpdata/en/22/0424ba488911d189490000e829fbbd/content.htm
Hope this helps,
Regards,
moorthy
null
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
XI can also understand .txt files but you would need to perfrom content conversion in the file adapter to convert the txt to XML.
As you are just starting upon XI, you can use a .XML file. Create an XML file corresponding to the source strucutre ( or) copy the Source XML from the test bad of your mapping.
To check if your scenario worked fine,
1. See if file is picked up.
2. use Transaction SXMB_MONI and see if there is a success message in the inbound side and outobund side in MONI.
3. Log on to the R3 system where the RC is triggered and see if there is any dump in ST22 .
Regards,
Bhavesh
does it has to be a xml file or it can be any .txt file?
>>>>
Depends.... you can use a XML file and thus avoid doing File Content conversion (FCC). Else in case it is a text file then you would have to do FCC to create the XML file.
FCC:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
hey
the file is being picked up properly but in SXMB_moni, there is an error which says "no receiver found"
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Grouping
-->
- <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>
what might cause the problem
thanx
amir
in your ID check the receiver determination you have created. The error that you have got is because a suitable receiver could not be identified.
Make sure you have created a Recv. determination and its corresponding Interf. determination. Also make sure all the ID activities have been completed which includes adapters, sender agreement, recv. agreement etc
Hey in my Receiver determination under the "Configuration overview for Receiver determination" the mapping column says 'not specified' in red.even though i did the mappin in IR and it seems to be working fine there,also since i m doin File to RFC i dont have Receiver interface in the interface determination,hope i m not wrong there.
thanx
amir
<i> the mapping column says 'not specified' in red.</i>
>>>
you need to specify the interface mapping in IR here.
<i>also since i m doin File to RFC i dont have Receiver interface in the interface determination,hope i m not wrong there.</i>
>>>>
your RFC itself will be your inbound interface here
Hi,
You need to create Receiver Determination.
Sender system your file system,sender interface ,sender namespace.
Mention SAP system in configured receivers.
And then create interface detremination between your file interface and RFC(will be receiver Interface).
Add Interface Mapping which you have created in repository in Interface Mpaiing section of Interface determination.
Thanks,
Tuhin
Hey guys
that receiver determination error is resolved,i waz messin up the outbound and inbound interfaces.
now the file is being picked up but i m getting a red flag in SXMB_moni.
and the error is
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
-
Invalid at the top level of the document. Error processing resource 'file:///C:/WINDOWS/Temp/22d4008HTML000003.xml'. Line ...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
i dont know why buy i get the very same error in message mapping irrespective of any scenario is do.is it something wrong with my server(as this server is for educational purpose only) or my mapping is getting wrong all the time?
moreover this is the error message in m getting in payload
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_file_RFC_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/sap/xi/tf/_MM_file_RFC_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
hope this might give u a better idea of the problem
thanx
amir
Aamir,
Open you source XML or source file in a browser like Intrernet Explorer. If it opens it is a valid XML else it is invalid.
Take a look at this blog to see how to download source file from the message in MONI and test your mapping,
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Regards,
Bhavesh
Hey
yes there is some error in mapping,i copied my source xml instance form payload and got the following error.
Messages:
03:00:49 Start of test
Cannot produce target element /ns0:BAPI_COMPANY_GETDETAIL. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
03:00:49 End of test
i really appreciate help of u guys.do u guys know where is the problem?
appreciate ur immense help
thanx
aamir
Hey
my sender data type is something like dis:
MT_RFC_sender
Recordset
Row
Company
Street
Address
and my receiver data type is
BAPI_COMPANY_GETDETAILS
COMPANYID
the way i have mapped them is as follows
MT_RFC_sender <----
>BAPI_COMPANY_GETDETAILS
Recordset
Row
Company<----
>COMPANYID
Street
Address
do i need to do any other mapping too?
thanx for ur help
amir
do one thing ...
test the mapping by giving values in the test tab. if it is a success,
take the source of that and save as a xml file. Then use that to test your scenario.
I assume that your current xml file being used and the MT defined in XI does not match.
Paste your current XML file and the XML source generated by giving values in test here. if we compare the both it can lead to some conclusion.
Hi Aamir,
As said by Moorthy follow the steps which he had stated.
But if you want the response from RFC to be handled, then you can use BPM. You can refer to this blog which gives step by step procedure for File to RFC scenario.
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
As you are new to XI, first try what Moorthy has suggested. Later try the above.
I hope this helps.
Regards.
Praveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.