Regarding idoc to file

hello all,
i am working on a scenario where i need to send an idoc from my r/3 system to xi process it and store it in application layer folder of XI. i am able to see the idoc xml in message monitor also. but i am getting a error message "<SAP:Stack>Party and service not defined</SAP:Stack>" and also i found the following message in trace " <Trace level="1" type="T">...There is no Interface Determination configured for receiver party 0000001012 and receiver service</Trace> "
i configured my receiver bussiness system as a third party system with communication channel as file adapter, made also the necessary configuration in both the design and configuration.
where might i have gone wrong, i need some one to help me its really urgent.
thanks,
raju.

hi,
are you using Logical system as Partner profile in R3 to send the idoc ?
if not then:
- either change it to logical system
- configure a party in integration directory for your non LS sender
Regards,
michal

Similar Messages

Regarding IDOC 2 FILE Scenario

Hi Friends,
please help on IDOC 2 File Scenario. I have done tha ALE settings in R3 system and the Idoc has been generated out of r3 system. but how it wiil be sent to XI server can any body help me on this issue.make it as quick as possible.

Hi,
Goto We02 and take the IDOC number froom there.
goto WE19, give the copied idoc number and click on execute.
Check for Control records for that IDOC and say outbound processing
ALE Settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Check this for posting the IDOC From R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI+--
StepsSummarized&
Regards
Seshagiri

Issues regarding IDOC to File scenario

There are two SAP systems 1) SAP CRM and 2) SAP XI
My scenario is trying to send a BBPCO.BBPCO01 IDoc from SAP CRM system to SAP XI system.
I configured a scenario in Integration Builder with only one communication channel for the File Receiver. I have not defined a sender communication channel sender as this is a IDOC communication from another SAP system.
I have not defined a sender agreement for the scenario as there is no sender communication channel.
I sent an IDOC (we19) to SAP XI system with needed receiver port and logical system information (it automatically filled the sender information) from the SAP CRM system. IDOC status (we02) was displayed 03.It's sent successfully.
The receiver port and logical system are correct. I tested the connection in SALE transaction code.
Below are my question.
When i check the message monitor (SXMB_MONI) on the SAP XI system, I don't see any messages.
Can it be that messages have not reached the XI system ?
Where can the messages go ? is there a different place to see the received IDOC message ?
Any help would be greatly appreciated.
Thanks.

Thanks for the quick reply.
I looked at the sm58 transaction code on SAP CRM system. The status text shows the error message.
Transaction IDX1: Port SAPEC1, client 800, RFC destination contain error.
nothing on the sm58 of SAP XI system.
Where should i create the port and RFC destination for SAP CRM, is it in the XI system ?

Regarding IDOC 3 File scenario

Hi This i Uday, please help me on IDOC2FILE scenario. i have done all the design and configuration part in XI.
for ALE settings
In R3 System
I have created alogical system named ls_uday,by using TC BD54.
and then i assigned this logical system for my R3 client 800.
and then i created my rf connection using transaction code SM59 named ls_uday, in that
i have given in technical setting i have given the target host as XI ip number and sys number
and logon settings as my xi usr name and passwd. and then i have created the port using tc we21 ls_uday.
and then created partner profile using tc we20 and then added the respective idoc as outbound.
In XI i also created same
bd54 ls-day
sm59 ls_day
idx1 ls_day
idx2 ls_day.
whre i have to do model view. please help me on this issue as early as possible.
don't send me any screen shots explain in textual format.

Hi,
go to BD64 distribution model and create a model view and goto ENVIRONMENT Tab..
Steps
SAP XI
1) RFC Destination (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.
2) Create Port (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 (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
idoc to idoc
regards,
Kishore

Idoc to file scinario

how to get the file name as idoc number dynamically in idoc to file scenario?

Hi Ram,
The below mentioned link will help u in this regard
Idoc to file:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Ram Kindly close the Previous posts if u r problem is solved
Reward with points if helpful
Regards
Sai Ganesh

Problem regarding the Payloads in IDOC to file scenario

Hi All
My scenario is IDoc to file where I use to get 5 IDocu2019s (in it there will be 10 segments) at a time and in one IDoc there will be only 9 segments, and that IDoc (with 9 segments) must be the last payload (I.e. file) at the target side (i.e. IDocu2019s with 10 segments must be at the first and the IDoc with 9 segments must be at last in the target payload).
Thanks in advance

Hi,
as the thread is marked as question you should not forget to ask something
Regards,
Udo

Regarding remote login in IDOC to FILE Scenario

Hi Friends,
 I have been struggling from this issue from many days.
when i am doing IDOC to FILE Scenario, i was posting an CREMAS03 IDOC from ECC client 800 to SAP XI Client 001.
 After executing WE19 in SAP ECC, its automatically asking for XI login detals.
will it really ask for login details.
Because if we do FILE to IDOC Scenario, it wont ask for login details.
 If i check RFC destination from XI to ECC, we could easily remote logon to ECC without asking for any logon details, but if i check RFC destination from ECC to XI, its asking for Lodin ID and Password.
Regards,
Varun Reddy.K

HI Varun
Check the roles assigned to you.
The roles are...SAP_XI_ADMINISTRATOR and SAP_XI_DEVELOPER.
If u have created the user in SU01 just now..and checking logon to IB immediately ..it will not come cos it takes some time for the users to get reflected in JAVA stack.
Cheers..
Vasu
** Reward Points if found useful **

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

In idoc to file scenario, if XI system is down where do idocs pile up?

In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
what tcode can I use to reprocess it?

Sender System ,Check BD87 .. you will see alll the IDOCs in Yellow state ..
You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
regards
PS

FIle Content Conversion Problem in IDOC-XI-File Scenario

Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
Prabhat

If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

Help needed in Idoc To File Scenario

Hi Experts,
My scenario is Idoc to File.
Here my job is to convert the purchase order idoc into xml file.
In this there are three conditions.
                   converting the standard PO into xml file
(ii)                 converting the PO with serial number into xml file
(iii)                converting the PO using serial number with subcontracting into xml file
so what I feel is I need to create one scenario and based on the condition that particular PO will convert into xml file.
Conditions:
                   if no condition is specified then it is standard PO first case
(ii)                 if field tdline ne space then it is PO with serial number second case
(iii)                if field pstyp eq 3 then it is PO using serial number with    subcontracting third case.
Please guide how to do this scenario.
IR:
1)       how many data types I need to create
2)       how many message types I need to create
3)       how many message interfaces I need to create
4)       how many message mappings I need to create
5)       how many message interfaces I need to create
ID:
1)       how many receiver determinations I need to create
2)       how many interface determinations I need create
3)       how many receiver agreements I need to create
And where to write the conditions at message mapping level or at receiver determination level.
Kindly provide solution to every point.
Regards,
Venkat.

1) if no condition is specified then it is standard PO first case
2) if field tdline ne space then it is PO with serial number second case
3) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
you have to create
1. outbound ( IDOC)
2. 3 Inbound (same MT)
create 3 mapping program each for 1 condition
create 3 interface mappings
ID:
1 reveri BS.
3 Interface determinations, so 3 receiver agrement.......
you can put the condition on the mapping or in the condition tab of the interface determinations.

Picking a IDOC Flat File stored in SAP R/3 Application Server by SAP PI

Hi,
Can SAP PI pickup a IDOC Flat File stored in SAP R/3 Application Server Directory and send it back as an Inbound IDOC.
Scenario:
We have a data in the EXCEL Sheet, which will be used to a fill an IDOC and the IDOC will be just save in the SAP R/3 Application Server Directory, but can not be triggered due to its peculiar behavior. Afterwards, SAP PI should pole the SAP R/3 and pick up that IDOC Flat File from the R/3 Application Server and send it back to the SAP R/3 as an Inbound IDOC.
For Ref: IDOC does not have a Outbound Process Code, thus can not be triggered and send to SAP PI. It is always used as a Inbound IDOC in SAP R/3 system.
Regards,
Saurabh

SAP PI should pole the SAP R/3 and pick up that IDOC Flat File from the R/3 Application Server
If SAP PI = 7.11 --> /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
send it back to the SAP R/3 as an Inbound IDOC
why to send some information again into R3 which it already has? cant some internal code in R3 read the info from excel and then update the IDOC directly?

Regarding idoc to file

Similar Messages

Maybe you are looking for