Reg:file to idoc scenario

In a file-xi-idoc scenario i created a business service for legacy
system and a business system for R/3 receiver system
i didn't assign logical system for the sender business service
and assigned a logical system for the reciver business system
so while maintaining partner profile in the R/3 system
i have to give partner no:
partner type:
here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
so then what do i need to give in the above two fields?
answers required briefly

Hello,
you know this pdf:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
Could be helpful.
Regards
Patrick

Similar Messages

Reg File to IDOC scenario with Acknowledgment

Hi Experts!
In a File to IDOC scenario , how to get the acknowledgment back to PI after posting the IDOC to SAP system and send the acknowledgment to the sender system.
What setting needs to be done in Sap and PI? Is it better if we have a BPM or is it good to have another interface to pass the acknowledgment IDOC back to the file sender.
Regards,
Srini

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Error in File-PI-Idoc scenario

Dear All,
While working on File-PI-Idoc scenario, I am getting the error as
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have checked various other posts on the same error but still I am not able to resolve this.
Please help me in resolving this error.
reg,
nj

Nishu,
Please check whether you have assigned the following roles to the particular user you are using for data communication.
Roles:
SAP_XI_IS_SERV_USER,
SAP_XI_APPL_SERV_USER
Regards,
Sugata

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

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

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

How to handle the control records in case of file to idoc scenario.

Hi All,
can you please clarify me how to handle the control records in case of file to idoc scenario.

Hi,
In File to Idoc scenario even though you selected apply control record values from payload and you are not getting those correct values which you have provided in the mapping.
Also check the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox
Regards
Seshagiri

About FILE to IDOC scenario

Hi Experts,
i need some help for doing file to idoc scenario.
1. what are the configurations we must do while doing this scenario?
2. How to communicate with Legacy system to sap system?
3. How to create the business and logical systems for SAP systems in SLD?
4. How to define parameters in communcation in ID?
5. what work shold be done using SM59 and WE20? and specify the steps please?
6. finally if u having word file please send from the creation of logical system for sap system?
thanx.

Go thru below mentioned links.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34
once you go thru them you will find answers for questions.
thanks,
Venkat

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
 I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

Partner Profile for file to IDOC scenario

Hi experts,
I am doing file to Idoc scenario. I did the ALE configuration steps between XI and r/3. For sender (ThirdParty) system, I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
Thanks
Manoj

Hi,
>>I defined Business system. While defining partner profiles in WE20 I got confused, whether to Give XI logical system Name or Third party logical system name. Please clarify..........
in most cases you will only use one logical system in WE20
this will be XI's logical system - and you can route all the traffic
via this logicail system - this is the most popular case
for more about IDOCs and XI have a look at my book:
Mastering IDoc Business Scenarios with the SAP XI
http://www.sap-press.com/product.cfm?account=&product=H1935
Regards,
Michal Krawczyk
http://mypigenie.com - XI/PI FAQ

Alert Configuration for File to IDoc scenario

I have followed Alerts : Step-by-Step /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
and configured Alerts for file to IDoc scenario.
But the problem is, I did not notice any alerts being generated. I could notice the IDocs being posted to destination system. So I was going through Alerts-Troubleshoute Guide. In intension to maintain monitoring level, I clicked Configuration tab. But I did not notice my sender and receiver system there to maintain.
Can any body help me to detail out the procedure to add sender and receiver systems to maintain the monitoring level?
Regards,
Suraj Kumar

hi Suraj,
WHich SP version are you on??
If you are on Sp14 or above, then unfortunately, Michal's Trouble Shooting for Alerts will not help.
From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
If this is working fine, then the last step, implement the note 913858.
Regards,
Bhavesh

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

Regarding RFC connection in File to IDOC Scenario

Hi everyone,
I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario
!!! Note: RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!
Regards,
Varun Reddy.K

Hi Varun
Follow these steps
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Regards,
Santosh

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

Reg:file to idoc scenario

Similar Messages

Maybe you are looking for