File to file scenario...in PI7.1

Hiiii.....
Its my first file to file scenario...i finished al my design and Integration Builder work...
In my Runtime workbench...in communiction channel monitoring i have
started my sender and receiver communication channel no errors found over thr...
but my input file still not transferred....What may the issue...help me out to sort this problem...
With Regards....
Dinesh Babu M

Hi Abshiek...
How to Release the channel lock...i checked regarding visual administration where can we find it in PI 7.1...help me out to sort this problem,....
With Regards...
Dinesh Babu...

Similar Messages

PI7.1 File to Idoc scenario issue.

Hi,
We recently had an upgrade from PI7 to PI7.1.
When testing File to Idoc scenario ,we had an issue as below
Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="1" type="T">Error during lookup - com.sap.aii.mapping.lookup.LookupException: Error when calling an adapter by using the communication channel GeneratedReceiverChannel_RFC (Party: , Service: ED2_200, Object ID: a8f14398a9993dccadbe983d401f693a) The channel with object ID a8f14398a9993dccadbe983d401f693a could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache.</Trace>
<Trace level="1" type="T">Error when parsing RFC Response - null</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
This was working fine before upggrade.
Any changes required to be done in scenario?
Pls let me know.
Thanks,
Srinivasa

do a CPA cache refresh
http://hostname:port/CPACache/refresh?mode=full
also check if the object is visible in tcode SXI_CACHE..
also refresh the SXI_CACHE

File to idoc scenario in pi 7.1

Hi All,
I am testing file to Idoc scenario.
I have few queries. I am using PI 7.1
1) in Message mapping - I import the receiver idoc metadata. and doing mapping.
So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
Please advice how to overcome
3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message.
"EDI: Partner profile inbound not available"
I checked all the relevent partner prfile configuration is already there"
I have already used all the forums , I did these scenario in past in PI 7.0 and never faced much issue . but doing first in PI 7.1 after a long time, so I might be possible, I am missing some thing. Please advice and help. thank
Ram

Hi Ram,
There is nothing new in PI7.1 which can cause these errors.. it is because the interface is configured wrongly
>>1) in Message mapping - I import the receiver idoc metadata. and doing mapping.So there are couple of mandatory fields over there. Please let me know how to treat them. Do I need to diable them or put some value. for exp Direct, Segment. SNDPRN RECPRN all these madatory fields are there. Please advice.
If you know the value the you can create the control record during mapping and the fields which you don;t required you can map it co constant. It is using this control record the partner profile entries are found and if there is a mismatch then the idoc will fail with the error which you mentioned in point 3
>>2) When I am creating communication component for sender side(File system) then should I assign the logical port and if then what name it can be . Is there any other place we need to maintain this entry. I remember in PI 7.0 I dont need to assign the local name. But here i see I need to do. if I am not putting the name over there then it throw error message "Unable to convert the sender service <Business Compoenetname> to an ALE logical system.
No in 7.1 also we dont have to do anything like that. There is a blog on this error from Michael, please go through it and understand why and how this error occurs. May be in PI7.0 you were lucky enough for not getting this error
>>3) now any how I am able to process the idoc from PI and its coming to ECC system. but it showing failed over there and giving me error message. "EDI: Partner profile inbound not available"I checked all the relevent partner prfile configuration is already there"
Check the control record of the generated idoc and see whether you have a partner profile entry for the parameters mentioned in it. If not then you need to correct them in PI
Regards
Suraj

Java.lang.NullPointer Exception in File-RFC-File wtihout BPM scenario

Hi All,
I have implemented scenario File - RFC - File without BPM in PI7.1 according to below link by bhavesh
[File - RFC - File without a BPM - Possible from SP 19.;
but I am getting error java.lang.NullPointer Exception in Audit log of sender communication channel when it enters in ResponseOnewayBean.
I had implemented the same in PI 7.0 but there it was working fine.
Is there any limitations on the use of the above beans in PI7.1 as I could see two more threads on the same unanswered yet.
Please help me in resolving as it is priority task for me
Thanks,
Amit

Sometime back I saved this SAP Note 1261159 for this error. Not sure if it is still valid. Try to get it implemented.
Regards,
Prateek

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

Step by Step Guide Details for RFC to File and File to RFC scenario

Hi Guru's
Good day to you. I am tyring to develop some scenarios based on RFC adaptor. so i want to start up with basic scenarios like RFC to File scenario(Here i just want to pull some data from SAP using RFC and put it in destination folder as an text file) and FILE to RFC scenario (Here i just want to take some data from the file and update into SAP).
For doing these scenarios i would like to request you people to send me the step by step guide which explains me about the complete steps of configurations required to do the RFC to FILE scenario and FILE to RFC scenario.
I found some scenarios and i am in confused state. so i request you to please put your experience to help me out.
thanks in advance.
Regards
Raj

Hi Aaron,
I don't know your scenario and your ECC and PI versions but I learned how to use ABAP Proxy more than 1 year ago with the following tutorial:
Edit--> The forum doesn't allow me to post external link, just search "ABAP Proxy Communication Scenario" in google and visit the 1st result
The way to develop ABAP Proxys has changed a little if your PI is 7.1. In the ECC side, the transaction SPROXY looks much better too if you have a recent version of the ECC.
Edited by: Marshal on Oct 8, 2009 5:08 PM
I've found that SDN Document. Maybe the scenario is not the most simple to start with ABAP Proxy but is very well documented and is for PI 7.1. The document also handles the inbound and outbound proxys
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c00ca32e-f991-2b10-f5be-97114bd2b08f&overridelayout=true]
Edited by: Marshal on Oct 8, 2009 5:22 PM

File to File scenario

Hi,
I have a problem in file to file scenario in which the file is not getting transferred from source to target.
Source communication channel - Transport protocol - NFS | Process mode : Delete | The file is picked but not able to delete from the directory.
Error: File: d:\test\file.txt deleting after processing failed - retry
The file is not transferred to target is it because of this CC is not able to delete the file. Does windows also have any authorization issue if so how should one check the authorization. I have the admin access of my system.
Thanks.

Hi,
Firstly, Since the scenario works perfectly while using Test mode, so all your design & configuration are OK.
Now, there can be Two reasons why PI is not able to delete the file and process it (during Delete Mode):
(The Problem will persists if you use Archive Mode also)
Prob 1. The directory is write protected or read only
Prob 2. The file is write protected or read only
Solution:
If Unix System
Soln for Prob 1. - go to the directory structure
for ex: if directory where file is kept is /staging/Interface/PI/Test/inbox/
then go to /staging/Interface/PI/Test/ and give command ls -lrt
It will show the directory names with permisions.
use chmod 777 inbox and the permissions willl be changed ( drwxrwxrwx )
Soln for Prob 2. - Get inside /staging/Interface/PI/Test/inbox/ and give command ls -lrt
if the file does not have authorizations as (-rwxrwxrwx) give chmod 777 <filename> and then give command touch <filename>
If Windows System
Soln for Prob 1. - Goto the directoty and right click on the folder and deselect the Read Only Checkbox.
Soln for Prob 2. - Right Click on the file and deselect the Read Only Checkbox
Try again and the scenario will work surely. Let me know if any issues.
Regards,
Souvik
Edited by: Souvik Chatterjee on Mar 14, 2011 8:14 AM

Regarding Background Job scheduling for file to file scenario

Hi Guru's
Good morining all of u
I have one doubt on ...
can we do background job scheduling for file to file scenario?
Please give me response as early as possible.
thanks and regards
sai

background jobscheduling for file adapter...
you can schedule the file adapter according to your requirement as follows:
In the Communication Channel Monitoring Locate the link Availability Time Planning, In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

Message has error status at outbound side File To Idoc Scenario

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

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

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error in File to File scenario

Hi All,
im trying out the file to file scenario [binary file using file content conversion]from SDN Wiki:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
On the runtime workbench, adapter engine is in red/error status due to error in the receiver comunication channel.
The sender communication channel is working fine. During testing, my file is being picked up and deleted(processing mode set to delete).
I am able to see the msgs in sxmb_moni and in Message Monitoring, the status is delivered.
However, the receiver channel does not show any error msgs at all.
Yday when i tested , i got the foll error msg:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'EMP.Contacts.fieldFixedLengths' or 'EMP.Contacts.fieldSeparator' is missing
However tdy i dont see any new error msgs during testing (no changes made to the recvr channel).
Given that the sender communication channel is wrking, can i safely assume that file adapter is wrking fine. If not, how do i check the status of the file adapter [in RWB, i can see the file adapter and various other adapters(with a grey diamond icon next to them). how do i interpret the status of the adapter?
Would really appreciate if anyone can advice on how to troubleshoot this?
Many thanx!
cheers
Prachi
I hv tried doing a full cpa cache refresh.

Hello Prachi ,
I thinks its because of receiver File Processing Parameters,as you are considering here File Content Conversion.
If your structure is like this
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Proveedor_100011 xmlns:ns1="http://sap.com/xi/webservices/buyordint">
<config>
<directory>c:/tmp</directory>
<filename>dynamicFile3.txt</filename>
</config>
<root>
<string>Header;423423</string>
<lines>
<value>LINE;</value>
</lines>
</root>
</ns1:Proveedor_100011>
Then your content conversion is -
RecordSet Structure: config,root
root.fieldSeparator = ;
root.endSeparator = 'nl'
config.fieldFixedLenghts = 0
config.fixedLenghtTooShortHandling = CUT
http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
With Regards,
Raju.
Please give points if useful.....

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

Error in message Mapping(file to file scenario)

Hi friends,
In file to file scenario i am getting error like this while activating standard change list in IR.
Activation of the change list canceled Check result for Message Mapping MM_file2filejuly27 | URN:file2fileJuly27.com:
Starting compilation
Compilation complete
Check result for Software Component Version praba.com | PRABA.COM | 2007 | 0:
The standard error type ExchangeLogData is not defined for the namespace URN:file2fileJuly27.com
Save the software component version definition again. The object is then saved automatically
could you help me out how to correct this error?

Prabha,
You should not delete any existing standard Data types provided by SAP. ExchangeLogData and ExchangeDaultData are standard data types get created when you create new namespace.
If you have already deleted then copy them from other Namespace to your namespace. Activate your default data type first and then your objects.
Hope this will solve your problem.
Nilesh

Error while calling RFC adapter(FILE-XI-RFC scenario)

Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?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="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

Error while doing File to File Scenario

All,
I am trying a simple file to file scenario - where xi picks up the file from a location and maps the message and dumps it in another location.
I am Getting the below error while doing the same .........
Time Stamp Status Description
2009-03-30 14:30:24 Success Channel Test_send_cc: Send binary file "d:\input\input.xml". Size 203 with QoS EO
2009-03-30 14:30:24 Success Application attempting to send an XI message asynchronously using connection AFW.
2009-03-30 14:30:24 Success Trying to put the message into the send queue.
2009-03-30 14:30:24 Success Message successfully put into the queue.
2009-03-30 14:30:24 Success The application sent the message asynchronously using connection AFW. Returning to application.
2009-03-30 14:30:24 Error Attempt to delete file "d:\input\input.xml" after processing failed. Retry
2009-03-30 14:30:24 Success The message was successfully retrieved from the send queue.
2009-03-30 14:30:24 Success The message status set to DLNG.
*+2009-03-30 14:30:24 Error Transmitting the message to endpoint http://filip:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.*
2009-03-30 14:30:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Mar 30 14:35:24 GMT+05:30 2009.
And i cant see the meesages using the SXMB_MONI trasaction
please help me resolve ths issue
Regards,
Mahesh.
Edited by: mahesh uma on May 3, 2008 2:12 PM

Hi Uma,
Go through this links::
Hope these links are useful to you..
Urgent: Message not transmitted from AFW to Integration server
Error with huge file
File to JDBC error
Thanks,
Satya Kumar..

File to file scenario...in PI7.1

Similar Messages

Maybe you are looking for