Problem IDOC to File scenario: No service for system SAPIDC, clnt in ID

in IDOC to File scenario, when IDOCis triggered from R/3 to XI, it gives error in SM58 transaction
"No service for system SAPIDC, client 800 in Integration Directory"

In a scenario, i have a BPM which has a transformation step which contains a mutimapping ...means 2 messages mapped to 1 messgaes, here in the mapping i m using an UDF and written code to extract the file name from dynamic configuration.....
the problem is ...the same BPM contains another transformation step which contains a message mapping (which is not multi mapping), and here the code (UDF) works to fetch the file name...
the code is all correct....and it looks like
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String sourceFileName = conf.get(key);
if (sourceFileName == null ){
sourceFileName = "ErrorFile.xml";}
return sourceFileName;

Similar Messages

Questions to a Mapping for IDOC-to-File Scenario

Hi all,
I want do develop a Message-Mapping for an IDOC-to-File Scenario. A SAP System sends an IDOC to the XI-System and the XI-System should make a mapping an send a XML-File to a FTP-Server. The Strukture of the target message is very easy:
<xdoc>
 <Invoice>
 @purno
 <HeaderInfo>
 <invno/>
 <shipdate/>
 <extvalue/>
 </HeaderInfo>
 <DetailInfo>
 <LineItem>
 @lineno
 <vpartno/>
 <descrip/>
 <qtyord/>
 <cost/>
 <vendmemo/>
 </LineItem>
 </DetailInfo>
 </Invoice>
</xdoc>
The source message is an IDOC. This IDOC can contain one or more positions (E1EDP01). Those different positions should be mapped into different LineItem's (see target structure) -> so in the target file one or more LineItems can appear.
Is it possible to implement this process with a common message-mapping or have I to implement a business process?
Thanks
with best regards
Christopher

Hi Christopher,
Is it possible to implement this process with a common message-mapping or have I to implement a business process? - This thing is possible with common message mapping......you dont need business proces for it.......in msg mapping after taking the source IDOC and target xml struc, map the E1EDP01 field to LineItem field.......just check the occurance of these nodes.....it should be 0..unbounded.........so as many E1EDP01 nodes will be there in idoc, that many LineItem nodes in target will be created.......
Thanks,
Rajeev Gupta

Question on IDoc to File scenario

Hi Guys
I am doing an IDoc to File Scenario, and my sender system is maintained in the SLD as a business system, an I have created my RFC destination and Port acording this blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1310. [original link is broken] [original link is broken] [original link is broken] but when I use transaction idx2 the is niothing on a LOADED METADAT.
I have imported the idoc to integration repository : "FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01"
My file will be created on the FTP Server directory.
My question is, do I have to created the RFC connection of type 3 or type T.
Thanks
Yonela

Hi Yonela,
Go thru the following threads and troubleshoot..
IDoc was saved but cannot or should not be sent
"IDOC saved but cannot be sent"
Regds,
Pinangshuk.

Problem in idoc to file scenario

hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan

>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

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

Issues in IDOC to File scenario using bussiness service

Hi Team
I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent). The setting which have done on SAP side are as below
SAP SIDE CONFIGURATIONS
1. Created RFC destination : RFC_XI_SYSTEM
2. Created port : PORT_TEST
3. created logical system: IDOC2FILE
4. created partner profiles: IDOC2FILE
XI side configurations
1. Created RFC destination: RFC_SAP_SYSTEM
2. Created port : by using IDX1 t-code
DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
3. metadata: by using idx2.
DOUBT: here it is asking for IDOC type and source port, i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know, please find the SAP and XI system details below and suggest accordingly.
SAP system details
Client: 800
User name: sapuser
system id: DEV
system number:10
XI system details
Client:100
username:xisuper
system id: SXI
system numebr: 00
I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
Thanks in advance.
Raju

To complete your scenario successfully with better understanding of Idoc adapter
read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

IDoc to File scenario Monitoring Problem

Hi,
I have a problem in monitoring. In my IDoc to file scenario the ftp server is not reachable (wrong ip) but still in sxmb_moni I get a successful processed message with acknowledgement system error.
Now, why dont I get an normal error in sxmb_moni?
Thanks in advance...

Hi,
>>Now, why dont I get an normal error in sxmb_moni?
Why because in MONI we generally get the Errors related to the Message Processing like mapping, and pipe line Services.
But the error which u got is related to the Receiver, so this we can find out in the Receiver File Adapter monitoring( CC monitoring)
MONI Shows the Errors those are related to the ABAP Satck means if any Errors occurs while going the process on ABAP Stack
But the error which u got is on Adapter Engine Process, so Definately the Error finding place is on Receiver CC monitoring
REgards
Seshagiri
Edited by: N V Seshagiri on Sep 26, 2008 1:17 PM

Setup for IDoc-XI-File scenario

Hi All,
Please provide info where can I find, step by step documentation for the basic setup on R/3 and XI areas, before start developing IDoc-XI-File or File-XI-IDoc scenarios.
Thank you,
Sree

Hi,
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC ->
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
(It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Context handling in message mapping for an IDoc to File Scenario

Hi,
Can somebody help me with this issue. I have an Idoc to file scenario. heres my idoc structure. Its a custom Idoc
Header (1..1)
Detail (0..Unbounded)
         DependentDetail (0...Unbounded)              Note: This dependentdetail is a subelement of Detail
Trailer(1...1)
I created my target structrure the same way as the Idoc structure.
My output is a simple text file. I need the output in this format
Header
Detail1
   Dependentdetail1
   DependentDetail2
   DependentDetail3
Detail2
   DependentDetail1
   Dependentdetail2
Detail3
Detail4
Trailer
Since the Detail and Dependent Detail records are unbounded .
But right now i m getting my output like this:
Header
Detail1
Detail2
Detail3
Detail4
Trailer
But the DependentDetail record in not showing up in the output file. I didnot do any context change in my mapping. So do I need to do any context handling??...If so can somebody explain me with this.
Thanks,
Adam
Edited by: hymanroth on Apr 29, 2011 11:11 PM

Thanks Kenneth foryour quick reply,
Yes, I see the payload for Dependent detail in SXMB_MONI. So as you said earlier there's a problem with my content conversion.
my content conversion is as follows:
Header.fieldNames
Header.fieldFixedLengths
Header.endSeparator
Detail.fieldNames
Detail.fieldFixedLengths
Detail.endSeparator
DependentDetail.fieldNames
DependentDetail.fieldFixedLengths
DependentDetail.endSeparator
Trailer.fieldNames
Trailer.fieldFixedLengths
Trailer.endSeparator
So As I told earlier. With the above content conversion. I am not able to get the Dependent detail record in my output file. So If there is a change in my content conversion can u check it and tell me where I went wrong.
Thanks,
Harsh
Edited by: hymanroth on May 2, 2011 7:03 PM

Problem with IDOC TO FILE Scenario

Hi Experts,
I am doing IDOC TO FILE Scenario.
I have done all the configuration.I have cretaed RFC,PORT,LS and Partner profile at both R/3 and
XI Side.
when I am trying to generate IDOC using we19 and I put the r/3 port,partner in sender and XI
port and partner in receiver it gives me error as "Port 'SAPCU6_100' does not exist in the table
of port descriptions.
Please help me.....
Regards

HI Saras,
Please go through the below weblog which has all the stpes which is required for ur scenario...I think screen by screen help u to debug ur problem and it will help u to find out the msitake which u have made.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

Error in Operation Mapping for Idoc to File Scenario

Hi Experts,
I am doing Idoc to File Scenario for Timesheet IDoc "HRSM_C" and following step are through,
Sender agreement --> Receiver Determination --> Interface Determination
got stuck in Operation mapping, it sahows error
"Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1"
Also not all the fields of IDoc HRSM_C are transferred to the XI server as I am unable to see all the fields in xml file using transaction idx5, as I suppose the reason behind may be there are no values in those fields.
Please suggest how to resove the issue and transfer all the fields from R3 to XI in Idoc eventhough it doesn't contain any value.

Hi
Refresh CPA cache using user PIDIRUSER.
Look Note 951318 for Mapping Cache Refresh.

Error in TRFC for IDoc to File scenario while sending IDoc

Hi,
Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
Can anybody help me out in resoving the error?
Regards,
Suraj Kumar

Hi,
Thanks for your reply.
It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
Hope I am clear.
Please let me know, if you need any further information.
Regards,
Suraj

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
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.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

No service for system ECC R/3 , for IDOC to file interface in SM58

Hi all,
I am geting a error No service for system XXXXX, client 100 iIntegration Directory,
when i go to IIDX2 and Updating the IDOC type , i am not able to add it is give me a error 100
please help me in this
thanking you

Hi,
Check the threads Idoc adapter - No service for a system in Integration directory
No service for system ... in Integration Directory
Thanks!

Problem IDOC to File scenario: No service for system SAPIDC, clnt in ID

Similar Messages

Maybe you are looking for