File Sender CC Error ?

Hi Experts
I got error for file to file senario , at sender communication channel monitoring. adapters are green but when i check detialed monitoring i saw this error . can any body help me .
First Error
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BS_FileSenderServer, http://nsfiletofile, OB_FiletoFile; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BS_FileSenderServer, interface namespace http://nsfiletofile interface OB_FiletoFile No sender agreement found for
Second Error
Transmitting the message to endpoint http://SAPxxxx:80000/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during Sender Agreement Determination.\
Status is showing green and shotlog showing fucnctioning
Edited by: praveen.tecnics on Apr 15, 2009 11:46 PM

Hi!
It may sound stupid or even mad. But a few days ago I had a similar problem with a SOAP inbound adapter scenario in a PI 7.1 system. What did I do to solve this issue?
I deleted all objects in the ID
I activated the deletions
Then I started from scratch using the configuration Wizard
... and then ... suddenly it worked.
By the way: Obvioisly there is a big difference between Party '*' and Party ' ' ...
Regards,
Volker

Similar Messages

J2SE File Sender Adapter Error

Hi Experts,
I am doing a scenario on J2SE. Like this: J2SE File Sender -> XI -> J2SE File Receiver.
On File Sender adapter, it has an error, like this "ERROR: Finished sending to Integration Engine with error u201Cjava.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Foundu201D. Skip confirmation and quit this loop"
And this is the full log:
D:\Thach\Input\xi_test.xml
16:51:45 (4052): Start processing u201CTXTu201D file u201CD:\Thach\Input\xi_test.xmlu201D size 190 in u201CEO mode
16:51:45 (4058): Start converting to XML format
16:51:45 (4061): Converted complete file content to XML format
16:51:45 (4062): Sending text message u201Ce1ffc9e0-71e5-11de-8306-0019d12044f1u2033 type u201Capplication/xmlu201D to Integration Engineu2026 (message size: 633 bytes, URL: u201Chttp://host:50200/sap/xi/engine?type=entryu201D)
16:51:45 (4076): ERROR: Finished sending to Integration Engine with error u201Cjava.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Foundu201D. Skip confirmation and quit this loop
16:51:45 (4077): Retry mode - wait 10 sec, 0 msec interval before retry
And this the content of xi_test.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Material_toPPS xmlns:ns0="http://gml.com/xi/XI/Tutorials">
 <Material>
 <Text>Test</Text>
 </Material>
</ns0:MT_Material_toPPS>
And this the configuration of J2SE File Sender:
mode=FILE2XMBWITHROWCONVERSION
XI.TargetURL=http://host:50200/sap/xi/engine?type=entry
XI.User=PISUPER
XI.Password=*********
XI.QualityOfService=EO
XI.SenderParty=
XI.SenderService=BS_PlainJ2SE_Sender
XI.ReceiverParty=
XI.ReceiverService=BS_FileRecv
XI.Interface=MI_Material_toPPS_OB
XI.InterfaceNamespace=http://gml.com/xi/XI/Tutorials
file.type = xml
file.sourceDir=D:
Thach
Input
file.sourceFilename=xi_test.xlm
file.processingMode=test
file.pollInterval=10
#Content conversion parameters in PlainJ2SE Adapter
xml.documentName = MT_Material_toPPS
xml.documentNamespace = http://gml.com/xi/XI/Tutorials
xml.structureTitle = Material
xml.processFieldNames = fromConfiguration
xml.fieldNames = Text
Please help to solve the issue.
Thanks so much,
vn thach

The URL of the Integration Server is wrong or you cannot access the server from the host, where the J2SE adapter is running:
XI.TargetURL=http://host:50200/sap/xi/engine?type=entry
If the Client of the Integration Server is not 000, then you have also to add that line:
XI.Client=XXX

File send adapter error : java.lang.NullPointerException

Hi All,
I have an issue on some of the file sender adapter communication channels .The channels are failing with the error :
Error :"Attempt to process file failed with java.lang.NullPointerException"
This issue is happening for couple of file sender channels.When I try to stop and start the channels couple of times the failed messages are getting processed.And after the processing of the failed file, the new files are successfully polling as usual.
Please share your experiences as on why this issue is happening and what is the permanent fix for the issue ?
Thanks in Advance !
Thanks & Regards,
Roni

Hi Roni,
Try with a J2EE restart of the PI server. Hope that will solve your problem.
Thanks,
Anudeep

File Sender Adapter error

Hi All,
I hav a simple file to IDoc scenario. recently we had upgraded to SP19. And now when i changed the FTP Sender Adapter parameters (FTP and the User), i'm getting the following error.
Message : Channel FTP_Out_TransferStockCount: Sending file failed with com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process. - continue processing
Category: /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File
Location: com.sap.aii.adapter.file.File2XI.processFtpList()
Application: n/a
User: J2EE_GUEST
Host: sapqas08
Node: Server 0 8_35292
I had searched the forum earlier and i found this to be a common problem. but none of the threads were answered. Can anyone please help me out in resolving this issue?
Thnx in Adv.
Anil

HI Anil,
Whether this issue got resolved? If yes, then please provide me the solution. Last day our server was restarted and aftre that we are facing this issue. As I checked the channel monitoring log, it seems like this:
Success MP: Entering module processor
Success MP: Processing local module localejbs/CallSapAdapter
Error MP: Exception caught with cause com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
Error Attempt to process file failed with com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
Success Channel CC_File_Sender: Entire file content converted to XML format
It looks after CallSapAdapter module some issue arised. So, kindly help me to resolve it.
As I checked and found some notes such as 1083488.
PI 7.0 SP13 ADAPTER FRAMEWORK CORE 7.0
Support Package 13, Patch Level 3 (SAPXIAFC13P_3.SCA) is present. So. please suggest.
Regards,
Nutan

File sender adapter Module Error

Hi Everybody,
I have developed an adapter module for file sender to rename the file name which is picked from the directory and I am getting an error
"Attempt to process file failed with java.lang.NullPointerException".
Can anybody tell me why is this error?
Thanks,
Zabi

Hi,
first check that module has been succesfully executed or not .This you can check in RWB .
Secondly go in the file adpater and click on to module tab and check
1-there will be two things one will be adapter module that you have depolyed. other one will be call sap adapter.
2- make sure that call sap adapter should come after the module you have deployed. and having the key value less then adapter module (let say your adapter module is having the key value 1 and call sap adpater is having the key value 0 then you need to change the key value there)
Thanks
sachin

Error Archiving File in File Sender Adapter using AF_Modules/PayloadZipBean

Hi everybody.
I have to pick a zip file up from ftp server, unzip an convert the file in xml.
Im using this modules in file sender adapter:
AF_Modules/PayloadZipBean --> To unzip de file
AF_Modules/MessageTransformBean --> file to xml
The problem is when I try to archive de file. Im getting this error and I dont know why (This path exists /out/ProcesadosSinError/)
Could not archive file 'test.zip' as '/out/ProcesadosSinError/20100518-091029-155_test.zip' after processing: java.io.FileNotFoundException: /out/ProcesadosSinError/20100518-091029-155_test.zip (A file or directory in the path name does not exist.)
Could it be that is not possible to archive with AF_Modules/PayloadZipBean?
Thank u so much

Hi Stefan.
Absolutely. This path exists. It's an absolute path from root. I can´t understand the error!!!!
Thanks!!!
Edited by: Christian Abad Chico on May 18, 2010 9:35 AM

Sender file adapter conversion Error!!

Hello every one....
I am stuck with a problem...in my scenario,, there are possiblities that file may contain more than required paramters... in such case,,, paramters defined in conversion should go ahead and others should be ignored...
for this very purpose i added the paramter:
row.fieldSeparator                 ,
row.fieldNames                     orderno,authcode,status
row.endSeparator                  'nl'
row.additionalLastFields      ignore
the scenario works fine if the file contains thrree comma separated values but it raises an error if no of paramters increase as :
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting
document line no. 1 according to structure 'row':java.lang.Exception: ERROR in configuration: more
elements in file csv structure than field names specified!
we are using PI 7.... does it require some more configuration in additoin to paramter row.additionalLastFields
any help in this regard would be highly appreciated...
thanx

this parameter is already set, and this is the exact behavior i want from adapter engine... but the problem
here is different... the exception is raised at communication channel's conversion routine level,,, the retry
interval is not the one defined in visual admin but infact the interval (polling) time defined in communication
channel.... the system does'nt stop after 3 attempts,, but infact keep on trying to read it....
one peice of information i have found is in sap note:821267 , which states:
*Q35:*
Q: I have configured a File Sender channel with File Content
Conversion or a custom-developed module, which may throw an
exception. When the File Adapter encounters an invalid file, which
triggers a conversion error or an exception in a module, the
adapter will enter a retry interval and upon each following
processing attempt try to process the faulty file. This basically
prevents the File Adapter from picking up files that are located
after the fauilty file according to the configured sort order. How
can I change this behavior?
o A: This is by design. When the File Adapter encounters an invalid
file, manually remove this file from the configured source
directory. You can configure an alerting rule to get notified each
time this occurs.
We are currently evaluating possible solutions that could be used
to skip this manual interaction.
now can there be a way around to make communication channel read the file only 3 times (value defined in adapter engine profile in visual admin)
I have thaught of writing of module.... but the error is raised even before calling module !!
any further clue ???

File To Mail - Error in sender CC

Hi All,
I am trying out a File to mail scenario following the Blog /people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
I am getting the following error in the File Sender Comm Channel :
Mail: error occurred: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.messaging.srt.BubbleException: Failed to call the endpoint [null "null"]; nested exception caused by: java.io.IOException: no sender address specified
I could also see the payload is empty in the Receiver Mail CC
Now can anybody help getting me the mail ...
Thanks in advance

Hi Bhavesh,
I get a checkered flag in Moni ,
But the response has only SOAP header and Body with out payload , I Mail package is checked and base64 is selected ..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:04Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 1DC20B0043D611DBC937000D60D4EDB5</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0009</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - 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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping http://sap.com/xi/XI/Mail/30 GK_File2Mail_IM</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = XIL</Trace>
<Trace level="1" type="T">client = 002</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-14T09:48:05Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

AS2 error The FILE send adapter cannot open file

I have AS2 setup under biztalk. I have receive port which listen to HTTP adapter and keep listening on web site.Then there is corresponding send port which just write that file in folder . Send port just have filter for Receive adapter name.
It works fine, but some time I get error message
The FILE send adapter cannot open file <folder name\guid.txt > for writing.
Details: The system cannot find the path specified.
I am not able to understand what is error for this? Please help me to figure-out this.

Specifying the Backup transport is not going to solve the problem. Specifying the backup transport in this case is something like addressing the symptom of the issue and not finding the solution to root cause of the issue.
As you specified, if the mentioned error only happens some time but not always. In this case, the message "The
FILE send adapter cannot open file <folder name\guid.txt > for writing." would just be a warning message. Just by setting the retry in the send port will solve the issue. i..e Since this issue occurs rarely, it may be short lived glitch.
So by setting the retry count (lets say 3 times) with retry interval (let say 5 mins), this issue can be easily mitigated. You would not lose the message. So during the glitch you would get this message as warning, send port will retry "after specified
retry interval so after 5 mins", so by that time chances of files transfer is high. So this problem can be easily handled just by having retry count and retry interval in send port.
But you need to find the actual cause for this issue or you need to find the permanent resolution for this issue.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Error using Message Transform Bean in SimplePlain2XML in file sender

Hi guys.
Im using Message Transform Bean to convert from file to xml in file sender.
My structure look like this:
ROW (1..n)
>TRANSPORTES (1)
>ENTREGAS (1..n)
And I have configured the module like this:
AF_Modules/MessageTransformBean - transform
transform - Transform.Class - com.sap.aii.messaging.adapter.Conversion
transform - xml.ENTREGAS.endSeparator - 'nl'
transform - xml.ENTREGAS.fieldFixedLengths - 1,30
transform - xml.ENTREGAS.fieldNames - TIPO,NUM_ENTREGA
transform - xml.ENTREGAS.keyFieldValue - E
transform - xml.TRANSPORTES.endSeparator - 'nl'
transform - xml.TRANSPORTES.fieldFixedLengths - 1,30
transform - xml.TRANSPORTES.fieldNames - TIPO,NUM_TRANSPORTE
transform - xml.TRANSPORTES.keyFieldValue - T
transform - xml.conversionType - SimplePlain2XML
transform - xml.documentName - MPrueba_Zip
transform - xml.documentNamespace - http:/XXXXXX.es/XXXX/sap/prueba
transform - xml.keyFieldName - TIPO
transform - xml.processFieldNames - fromConfiguration
transform - xml.recordsetName - row
transform - xml.recordsetStructure - TRANSPORTES,1,ENTREGAS,*
Im getting this error and I don´t know why:
Error: com.sap.aii.messaging.adapter.trans.TransformException: Transformer Conversion3.0.5227 Error initializing Class: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Parameter 'xml.fieldNames' is missing (4403) ; nested exception caused by: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Parameter 'xml.fieldNames' is missing (4403)
Why am i doing wrong?????
Thanks a lot!!!

Hi
For Complex conversion you have to use xml.conversionType as "StructPlain2XML"
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
Regards
Ramg

...file Sender content conversion 'lastFieldsOptional' error

Hi All,
I am working on a File Sender content conversion--> flat file to XI.
it's fixed length field all the rows with same column.
090627 344535AFDFG+GBP65433 ASDSSD GFD dFSSGFD 6757532
090627 344535AFDFG-GBP65433 ASDSSD GFD dFSSGFD 6757532
090627 344535AFDFG-GBP65433 ASDSSD GFD dFSSGFD 6757532
090627 344535AFDFG-GBP65433 ASDSSD GFD dFSSGFD 6757532
090628 344536AFDFG+GBP45434 ASDSSD GFD dFSSGFD 6757532
090628 344536AFDFG-GBP45434 ASDSSD GFD dFSSGFD 6757532
**EOF**
I am sucessfully able to handle the file if i remove "**EOF*" from incoming file. But i get "lastfieldsOptional" error with "*EOF**"
>
Parameters-
     Recordset Structure - ROW,*
     Recordsets per message - *
    ROW.fieldFixedLengths - 6,8,20,10,30,1,3,1,11,1,11,6,10,10,20,10,10,2,6,6,2,6,6,3
    ROW.fieldNames - INV_DATE,INV_NO,PAYMENT_REF,CUST_NO,CUST_NAME...etc etc
   ignoreRecordsetName - true
There are parameters available to ignore Last field(last column) of a Row/Rocerdset
but how to ignore the last row of the file.
Plz suggest some parameter to ignore the last row/field of the file.
Regs,
Ansh

Ansh,
.lastFieldsOptional is obselete and you cannot use. Please see sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
The best thing comes to my mind is use:
.keepIncompleteFields as YES
Also give a try with:
.missingLastfields as add
So with this I think your last line in the file will read into XI. But the value of last line is **EOF**. So the length is 9. Since your the first two fixed lengths are 6 and 8. You will have these values as ***EOF and ***. So while mapping you can use doesnot satrt with * and map it, so that your last line will be ignored.
Note: with this apporach you have to make sure your first two columns never start with *. If you have a doubt then you can use the condition doesnot equal to ***EOF for first field and doesnot equal to *** for the second field when you map. I hope it makes sense to you.
Regards,
---Satish

File Sender Communication channel with error

Hi,
One of the File sender CC is in red but shows "Functioning". But in the Process Detail section it just showing
5/10/11 2:24:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds
5/10/11 2:24:00 AM                                                                     Processing started
5/10/11 2:23:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds
5/10/11 2:23:00 AM                                                                       Processing started
5/10/11 2:22:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds
5/10/11 2:22:00 AM                                                                      Processing started
Please let me know is there any error with my channel ot wny is it red then?
There is no Polling step in the Process Details.. Please reply ASAP
Thanks,
Shweta.

The Status of the channel is "Processing Erros in last 20 seconds". And in the processing deatils it just show the below two steps.
5/10/11 2:24:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds
5/10/11 2:24:00 AM                                                                        Processing started
5/10/11 2:23:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds
5/10/11 2:23:00 AM                                                                         Processing started
5/10/11 2:22:00 AM d28c6542-0d7e-453b-1d96-9e0a18159315 Retry interval started. Length: 60.0 seconds
5/10/11 2:22:00 AM                                                                        Processing started
It is continuasly showing the same message ID "d28c6542-0d7e-453b-1d96-9e0a18159315 " but this ID does not exist in SXMB_moni not in RTW message monitoring.
If I double click the message ID shown in the CC process details it shoes me below content.
Time Stamp Type Description
2011-05-09 22:03:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.
2011-05-09 22:04:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.
2011-05-09 22:05:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.
2011-05-09 22:06:00 Information Channel FileSenderGeneric: Converted complete file content to XML format.
Please tell me what is the problem. there are No java Locks ...I have checked that.
Shweta.

File sender communication channel error

Hi gurus please help me on the below issue ,suddenly my file(sender)communication channle is showing error status stated below error ,it is just simple scenario like file to proxy upto one hour back it is working fine suddenly it is showing below error plz give me the reply im in production suport
Error: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name localejbs/ModuleProcessorBean, cannot resolve object reference. [Root exception is javax.naming.NamingException: Error occurs while the EJB Object Factory trying to resolve JNDI reference Reference Class Name: Type: clientAppName Content: sap.com/com.sap.aii.af.app Type: interfaceType Content: local Type: ejb-link Content: ModuleProcessorBean Type: jndi-name Content: ModuleProcessorBean Type: local-home Content: com.sap.aii.af.lib.mp.processor.ModuleProcessorLocalHome Type: local Content: com.sap.aii.af.lib.mp.processor.ModuleProcessorLocal com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.aii.af.app; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5106] The application [sap.com/com.sap.aii.af.app] will not be started, because of the server state is [STARTING]. at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315) at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106) at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:144) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:63) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:77) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:228) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283) at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:394) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:223) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:242) at javax.naming.InitialContext.lookup(InitialContext.java:351) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:83) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:51) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3451) at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1332) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:622) at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:500) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182) at com.sap.engine.core.thread.impl3.SingleThread.run

Hi Thank for your reply Nbendu and sorry for late reply .
My issue was now resolved but i want to know why this is happend i am getting this issue when ever there is any Basis maintaenance Happens.
If it is due to Basis maintnance then with same combination we have 2 more interfaces is there it is not affecting the other .
Any thoughts.
Regards
Madhu

File Sender with CC Error handling

When using the file sender with content conversion we often receive
Parsing errors in the AFW monitoring due to bad messages.
Q: how can we monitor and e-mail this errors from the AFW,does the CCMS covers everything? Alert monitoring?.
another Q: In higher SPs of XI there is the option to archive error messages,is it possible to raise an alert for the parsing problem even though the file was removed by the Comm. channel to the archive folder.
points will be rewarded.
Regards,
Nimrod.G

hi,
Q: how can we monitor and e-mail this errors from the AFW,does the CCMS covers everything? Alert monitoring?.
yes it is possible thru CCMS
check the below links
Configuring scenario specific E-mail alerts in XI-CCMS: Part - 1,2,3
/people/aravindh.prasanna/blog
XI : Configuring CCMS Monitoring for XI- Part I
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
XI : GRMG Customizing for XI CCMS Heartbeat Monitoring Part II
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
regards'
chandrakanth

File Sender Scenario - Mapping error message

Hi All
Scenario
I am trying to develop a test scenario where a record is read from the file and sent to R/3 using RFC (Bapi)
So i believe this will involve a file adapter as sender and a RFC adapter as receiver, I have configured data types, message types, message mapping, interface mappings, sender determination, receiver determination etc.
Problem
When i put the text file in the polling directory the file is read, but there is an error,
On checking Processed XML message in SXMB_MONI I see that the following steps listed
1 - Inbound message (CENTRAL)
2 - Receiver Determination
3 - Interface Determination
4 - Receiver Grouping
5 - Message Branch According to Receiver
6 - Request Message Mapping
7 - Request Message Mapping
Step 1 - 6 does not show any error message, step 7 has an error with the following message
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_basic_paycreate_file_to_rfc_map~</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException<;/SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
Additional Information
My Business System Commnication channel has a Sender File adapter, this file sender is configured to read from file system from a certain directory and message protocol is File Content Conversion.
In Content Conversion parameters input fieldname and input separator are configured (does anything else need to be configured in this section?)
My input file is of the structure aaa,bbb,ccc,ddd,eee,fff,ggg
My Data Type is of the structure
<data header>
 <aaa></aaa>
 <bbb></bbb>
 <ccc></ccc>
 <ddd></ddd>
 <branch1>
 <eee></eee>
 </branch1>
 <branch2>
 <fff></fff>
 </branch2>
 <branch3>
 <ggg></ggg>
 </branch3>
</data header>
Questions
First question is why is there 2 instance of Request message mapping showing up in the monitor? Isn't this supposed to show up only once?
Second question it appears that the problem is something to do with Mapping (Message Mapping) but i tried to test the message mapping manually using the data generated in the payload and it passes the mapping successfully.
Third question, how is the input flat file converted to the complex structure of data type (as mentioned in additional information above) is this done by the input.filedNames that assigns the corresponding values from flat file to the data type?
Fourth question - is there a way to run the process step by process (as a step through in other programming IDEs?) so the problem can be more easily identified?
Thanks
Anant

Hi All
I little update - it appears that some of the scenarios developed earlier that were working earlier are now also failing at the same process of mapping with this error message.
So i am suspecting that this is not a problem with the mappings in my scenarios but rather a some technical setting related to how XI invokes this class - com.sap.aii.utilxi.misc.api.BaseRuntimeException.
Does any one have any ideas what i can check to confirm this? Whether the problem is in the technical setting or the scenario configuration?
thanks
Anant
error message attached.
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_CheckDeposit_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_CheckDeposit_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

File Sender CC Error ?

Similar Messages

Maybe you are looking for