IDOC TO FILE Scenario - No Message arrive at PI

Hello,
i want to create a IDoc to File scenario. I already sent an IDoc from an ERP System to the PI.
The status text is ::000 and the information is 'IDoc sent to SAP system or external program'.
In the PI i have a Business System that shoud receive this IDoc but i can't find an incoming Message for example in the message monitor???
Somebody have an idea?
Thank you!

Problem is solved.
I couldn't load the metadata for the IDoc, because their was no client in the RFC-Connection.
I haven't found this problem earlier, because the connection test was working well.
Anyway, thanks to all

Similar Messages

No message in found in XI in IDOC to FILE scenario

Hi everybody,
I am working on a scenario idoc to file. The idoc is sent sucessfully from R/3 , but I am not getting any message in message monitoring in XI.Can anybody help me on this?

Hi Bhagyashree,
Just see if the file is generated at the specified destination....
Meanwhile please go through the info below and cross check with what you have done...
i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
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:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
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 this answers your query.
Regards,
Abhy

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

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

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

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 IDoc to file scenario

Hi Experts,
I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
<?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="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please suggest me in this issue.
Thanks,
Bhuvan.

Check this link:
http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
You might want to refer to the SAP NOTE: 316877
Regards,
Ravi

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

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

Alerts when the acknowledgement fails in IDOC to File Scenario

Hi All,
could you let me know how to handle Alerts for Idoc to File scenario.
My Scenario uses BPM as well.
Thanks,
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.

Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

Hi All,
I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an 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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>FILE_BC</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
Thanks,
Geetha

Thanks everybody! It has got fixed. I just requested No acknowledgements.
Geetha
Edited by: Geetha on Nov 11, 2009 5:45 PM

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

Idoc to file scenario error

Hell Experts,
I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But I didn't get successful results, always the error message shows in SXMB_MONI as follows:
Ackn Status contains system error
During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
tion in Message-Mapping transformatio~
Exception of class CX_XMS_SYSERR_MAPPING
My system Patche level as follows:
SAP_BASIS     640        0012        SAPKB64012
SAP_ABA     640     0012                SAPKA64012
PI_BASIS     2004_1_640 0009        SAPKIPYI69
SAP_BW     350     0009                SAPKW35009
The above error is related to patches problems or any Mapping problems ?
Please help me.
Advanced Thanks.
Regards,
Chandra

Hi,
This may be a mapping issue, try this:
a)in interface mapping see if grids are formed at source and target after executing the test option,
b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
i am not sure of the patch levels.
Regards,
Anirban.

IDOC to file scenario testing error --

Hi experts ,
When doing an IDOC to file scenario the status of the IDOC in XI (the Trace section @ SXMB_MONITOR) shows that
PARTY &SERVICE NOT DEFINED
the failure occurs at message splitting stage .
more details :
the sender is represented as a business system
the receiver has no party and has only a business service
By chance when i tried to check message status in INTEGRATION ENGINE @ RWB
i was able to find that XI is trying to send the mesasage to Receiver with party name 12345 this 12345 is the same which i gave in we20 as the partner number .
What could be the reason ?

This is the error
Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party 0000002569 and receiver service</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) 0000002569 DELINS.DELFOR01</Trace>

IDOC to File scenario Configuraton settings

hi,
   I am doing IDOC to FILE scenario.I am sending IDOC from R/3 to XI and then to XML file.That mean smy scenario is as Follows ( R/3XIfile ) These are my queries
-->I have created RFC Destination from R/3 to XI.should I need to create RFC destination from XI to R/3 ( i mean In XI )??
-->I have created one Port in R/3 and I have linked that port with RFC Destination that i have created.here i am sending IDOC from R?# to XI...SO we call this PORT as SENDER PORT or RECEIVER PORT??
-->and DO we need to create PORT in XI also??is it require for my scenario??
-->DO we need to create Partner Profiles in XI also??
-->DO we need to create LOgical system in XI to represent the XI system?? (as we created LS in R/3 to represent sender system)
--->Here is my big doubt..
               when we test IDOC ..by sing we19 TCODE,
   We need to fill the corresponding details as below,
Receipent                                  Sender
Port                                              Port
PartnerNo                                      PartnerNo
PartnerType                                   PartnerType
my Doubt is,
-->>In which field we need to specify the Port that we have created in R/3..Receipent side OR Sender Side..?? and Why??
-->>Same for ParnerNo..where we need to specify the Logical system which we have created in R/3 should specify??Why??
Please give reply ASAP..with detailedexplanation..
points will be rewarded..
regards,
murali

HI
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You donu2019t 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 will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You donu2019t 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 will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
/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
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 u2013 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 names
cheers
reward poins if found useful

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
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:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
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
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

IDOC TO FILE Scenario - No Message arrive at PI

Similar Messages

Maybe you are looking for