IDoc to Fie Scenario Problem In PI

Hi Experts,
i am doing scenario like IDoc to file , i have created evrthing configurations all and all.
i trigger IDoc on r3 system using T-code we19, it showing sucess on r3 sytem. i am checking IDOc monitoring using t-code we05 to showing status 03. but the message not coming to PI system, what is problem it may be, please guide me
regards,
alekhya reddy.

Hi,
The Following are the Possible checks
1) Check in R/3 side SMQ1 & SMQ2
2) Check in R/3 side SM58
In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
If the entry is available then select it and press F6, to push it manually.
This happens normally if IDOC stuck up in queues.
regards,
ganesh.

Similar Messages

IDOC to File scenario problem

Hello,
I configured this scenario:
R/3 4.6C (IDOC) -> XI -> XI File Adapter (IDOC-XML)
I am on SP Stack 10 (i386)
IDOC arrived to XI with success, but there is no file in out directory of File adapter. In Audit Log in Adapter Engine of XI I get errors:
1. Error Unable to find channel ID
2. Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: bf6a8684-e3ac-9540-a055-c9156b6c4edb
After 3 retries message stuck in System Error.
Here is a detail log:
2005-03-03 08:50:57 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi3:53700/MessagingSystem/receive/AFW/XI
2005-03-03 08:50:57 Success Using connection AFW. Trying to put the message into the receive queue.
2005-03-03 08:50:58 Success The message was successfully retrieved from the receive queue.
2005-03-03 08:50:58 Success The message status set to DLNG.
2005-03-03 08:50:58 Error Unable to find channel ID
2005-03-03 08:50:58 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: bf6a8684-e3ac-9540-a055-c9156b6c4edb.
2005-03-03 08:50:58 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 03 08:55:58 CET 2005.
2005-03-03 08:50:58 Success The message status set to WAIT.
2005-03-03 08:55:58 Success The message was successfully retrieved from the receive queue.
2005-03-03 08:55:58 Success The message status set to DLNG.
2005-03-03 08:55:58 Error Unable to find channel ID
2005-03-03 08:55:58 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: bf6a8684-e3ac-9540-a055-c9156b6c4edb.
2005-03-03 08:55:58 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 03 09:00:58 CET 2005.
2005-03-03 08:55:58 Success The message status set to WAIT.
2005-03-03 09:00:58 Success The message was successfully retrieved from the receive queue.
2005-03-03 09:00:58 Success The message status set to DLNG.
2005-03-03 09:00:58 Error Unable to find channel ID
2005-03-03 09:00:58 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: bf6a8684-e3ac-9540-a055-c9156b6c4edb.
2005-03-03 09:00:58 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 03 09:05:58 CET 2005.
2005-03-03 09:00:58 Success The message status set to WAIT.
2005-03-03 09:05:58 Success The message was successfully retrieved from the receive queue.
2005-03-03 09:05:58 Success The message status set to DLNG.
2005-03-03 09:05:58 Error Unable to find channel ID
2005-03-03 09:05:59 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: bf6a8684-e3ac-9540-a055-c9156b6c4edb.
2005-03-03 09:05:59 Error The message status set to NDLV.
Also I checked admin_adapter.txt file in \usr\sap\XI3\DVEBMGS37\j2ee\cluster\server0\log\services\com.sap.aii.adapter.file.svc directory:
2005-03-02 22:40:02 : File Adapter Administration Stopping Sequence Executed
No adapter configured
2005-03-02 22:44:07 : File Adapter Administration initialized
No adapter configured
But, I configured File Adapter in Integration Directory as Active, and also in SXI_CACHE is present:
Communication Channel File
Adapter Engine Type CA
Adapter Engine Name af.xi3.xi3
Adapter Name File
Adapter Namespace http://sap.com/xi/XI/System
Adapter Software Component 3B787A8035C111D6BBE0EFE50A1145A5
Message Protocol File
Message Protocol Vers. 3.0.0527
Transport Protocol File
Call Direction O
Where is a problem?.
BTW, I get a same problem with DEMO: Distributing Booking Order Data.

Hi,
Try make a CPACache refresh.
(Http://<host>:5<sysnr>00/CPACache/refresh?mode=full) use XIDIRUSER.
We had a similar error after SP10, (every thing seems active, but it wasn't). It was solved by doing the cache refresh.
Hope it's help you
Rolf

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

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

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

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

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;

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

Problem in IDOC to SOAP Scenario

Hi All,
we have an IDOC to SOAP scenario in which we have got WSDL from the client for the targets.. Please let us know the WSDL would be the message type and we need to create interface for it . Also the SOAP header is not appearing in the target xml.
Thanks

Hi ,
This means when the data is sent to the webservice it will contain the SOAP header just that we cannot see it in Moni . Also
What about the acknowledgement . Our message is successfull but with message that awaiting acknowledgement.
What we basically need a synchronous scenario of IDOC to SOAP but the response not going back to SAP-R3 . We recieve the response only in SAP-PI. Saw some blogs but the message is going back to SAP-R3. Please help us on this
Thanks
Edited by: vishal gadkari on Aug 22, 2009 4:15 PM

Problem in Idoc to JDBC scenario(uses BPM)

Hi
I have a IDoc to JDBC scenario which also uses BPM.
The JDBC adapter has to execute a Stored procedure on Sybase database.
I work on XI3.0 SP14.
When I am sending IDoc to XI it is failing in CALL adapter step.
The error message is "Unable to convert sender service TruckLiftAccountUpdate to an ALE logical system".
However this scenario is working in Production with same settings.But it is not working in Quality and it is giving the above error.
Can any one help me in this.
Thanks in advance.
KP

Thanks for your quick reply..
All the settings are in place.
Here the Idoc is coming to BPM and BPM cant able to execute the stored procedure.and we are getting the error from BPM to target system.
Here error is unable to convert the sender service(from BPM service) to ALE
logical system.
same settings are there in Production but it is not working in QA.
Thanks in adavnce,
KP

RFC Destination not getting connected - IDoc to XI scenario

Hi Everybody,
I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
Please give me step by step solutions.... Thanks in Advance...
Regards/Guru

Requirements in R3 system:
1. Create RFC destination pointing to XI in SM59
2. Create port for XI using we21
3. create Outbound Entry in partner Profile for XI in we20.
Requirements in XI system:
1. Create Technical System pointing to the R3 system.
2. create Business System pointing to the R3 system.
If you want to send IIDOC out of XI,
1. SM59 - Create RFC destination
2. IDX1 - Create port
3. IDX2 - Import Metadata.
Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
Check dis link for more info:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
please refer to michel book on IDCO usage in XI
Message was edited by:
Sreeram Reddy

ALEAUD in IDOC to File Scenario

Hi,
I have a IDOC to file scenario in which im sending the PAYEXT IDOC from SAP to a bank as the IDOC-XML.
ie the user will create a payment in the SAP system , this shoud trigger an IDOC to XI. XI puts the IDOC-XML sturcture into a FTP folder path from which the bank will pick it up. Now the bank has to send an acknowledgement(asynchronously) that the payment was processed. And this response should be captured and returned to the user.
can we use ALEAUD as the acknowledgement or does using ALEAUD make no sense here?

Hi,
Assuming that the bank will send you a file to the FTP server you can simply pick up this file and mapi it to the Systat IDoc. I would assumt that the IDoc status's would not be in the file so you would have to do some value mapping or other logic to determine the IDoc status codes that you want.
The IDoc is very simple with few fields so the mapping should not be a problem.
Please note you do not use BPM for this scenario. In essence this would be a new flow of File --> PI --> IDoc
Import the STATUS.SYSTAT IDoc into the Design and play from there, you can make a POC now and test the functionality which would probably be best for you at this point.
Let me know if you need more details
Edited by: Alexander Ong on Jul 14, 2009 4:57 PM

IDOC-XI-JDBC scenario, jdbc sent too slow

i have a IDOC-XI-JDBC scenario,
the problem is that near 5 Lac IDOC is sent to XI, each IDOC is processes by an instance of the scenario, and the sent to the Database is too clow...means 4000 records per hour,
can i configure the JDBC receiver adapter in a way, so that it becomes faster/more concurrent,

Hey,
First raise the issue to the DBA he might help resolve the ISSUE more efficently.
Secondly check in the JDBC adapter -> Adavance mode -> Disconnect from the data base after processing each message shouldn't be set.
Even check with Database Transaction Isolation Level -> default is value of the connected database.
The isolation level determines how transactions running in parallel can influence each other
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
Why not the other way around > Collect multiple idocs in a file restrict maxium number of idocs to required value then send the file ?
Stefan Grube Example:
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
if it is with bpm then collect multiple idoc with occurance change and send them.
Cheers,
*RAJ*
**REWARD POINTS IF FOUND USEFULL

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.

37 Status code in IDoc to File Scenario

Hi Experts,
I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
while I am testing from SAP backend system (All required configuration steps are also good).
I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
please help me.
Thanks in advance,
Regards,
Sudeepth.

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 Fie Scenario Problem In PI

Similar Messages

Maybe you are looking for