JMS sender communication channel content conversion

Hi,
I struck with the content conversion in the JMS Sender communication channel.
I have configured the communication channel with the filed fixed lengths. (Simple type)
The field fixed lengths i have given are 10,2,3,11
The contents in the file 1000000072 230 111
but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
I have configured the sender communication channel as in the document in SDN.
Even, i configured several communication channels. I didn't get this strange error any time.
I have gone through SDN to fix this issue, but i didn't get solution.
If anyone got rectified this kind of error, please answer your solution to me
Thanking you,
Regards,
Krishnaraju.

Hi,
Thanks for all your support. The issue got resolved.
The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
Regards,
Krishnaraju.

Similar Messages

Sharing JMS sender communication channels

Hi all,
We have flatfile interfaces to XI JMS where we would like to share the JMS sender communication channel.
This is normally not possible since you cannot have two sender agreements with the same comm channel.
Are there workarounds for sharing JMS comm channels (we cannot make use of content fields, we do no conversion). is there a way with variables perhaps?
Thanks for any help
Tom

Tom
There is an otption of send a file to multiple receivers.
Therefore use your receiver determination to have multiple receivers and set there some condition.Thus making conditional receivers. Or have two receiver determinations.
This might help you.
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
/people/prasadbabu.nemalikanti3/blog/2006/03/10/bpmsingle-sender-and-multiple-receivers-based-on-synchronous-exchangeswitch-part-1
/people/prasadbabu.nemalikanti3/blog/2006/02/27/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-2
http://help.sap.com/saphelp_nw04/helpdata/en/7d/577941761b070de10000000a1550b0/content.htm
Pls : Reward points if helpful.
Vishal K

2 JMS Sender Communication Channels polling 1 MQ Queue

Hi Experts,
I have a situation where 2 JMS sender communication channels are polling 2 different message type data (via content conversion in JMS) from 1 MQ queue. However adapters are having problem polling the right message from the queue.
Is this something that is not possible?
I know that we can possibly use 2 MQ queues - one for JMS 1 with message type 1 and the other for JMS 2 with message type 2
OR
1 JMS with 1 common message type with 1 MQ queue.
But I want to confirm whether my current situation is suppose to work or not.
Thanks,
Jay

>
Jung Sun Ko wrote:
> Hi Experts,
>
> I have a situation where 2 JMS sender communication channels are polling 2 different message type data (via content conversion in JMS) from 1 MQ queue. However adapters are having problem polling the right message from the queue.
> Is this something that is not possible?
Maintain different queues for different message types.
The adapters else will just pick the message that comes to the queue first based on the polling time irrespective of the message type. It is not intelligent enough
>
> I know that we can possibly use 2 MQ queues - one for JMS 1 with message type 1 and the other for JMS 2 with message type 2
> OR
> 1 JMS with 1 common message type with 1 MQ queue.
>
> But I want to confirm whether my current situation is suppose to work or not.
>
> Thanks,
>
> Jay
Hope the above replies answers your question

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System

Hi All,
Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
If you know of any documentation regarding this, can you please post it?
Thanks,
Jay

Jung,
Are you looking for this help:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Also check this sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
---Satish

Content conversion at JMS sender communication channel

Hi friends,
I have to convert fixed length flat structure to xml message.Therefor i have to do content conversion at the JMS sender comm channel.Can someone please explainthe procedure?
data in the queue would be like as follows.
9999000000124646q12233appej500rc11147822zord

Hi Manikandan,
The structure conversion can handle files containing rows with different structures. In
each row there is a key field to identify the structure. The rows with identical key fields of
course have identical structures.
Let us assume that we have a sample file with four rows. Each row has a two-byte key
field; the first row has a second field with ten bytes; the structure of the second and third
rows is the same and comprises two additional fields with three bytes each; the last row
has a second field with five bytes:
AA1234567890
BBABCABC
BBXYZXYZ
CC12345
The configuration for the conversion could look like this:
Module Configuration
Module Key Parameter Name Parameter Value
Plain2XML Transform.Class com.sap.aii.messaging.adapter.Conversion
Plain2XML Transform.ContentType text/xml;charset=utf-8
Plain2XML xml.conversionType StructPlain2XML
Plain2XML xml.processFieldNames fromConfiguration
Plain2XML xml.documentName MyDocument
Plain2XML xml.documentNamespace http://xi.com/test
Plain2XML xml.recordsetName MyRecordset
Plain2XML xml.recordsetStructure NameA,1,NameB,*,NameC,1
Plain2XML xml.keyFieldName MyKey
Plain2XML xml.keyFieldType CaseSensitiveString
Plain2XML xml.NameA.fieldNames MyKey,field-nameA
Plain2XML xml.NameA.fieldFixedLengths 2,10
Plain2XML xml.NameA.keyFieldValue AA
Plain2XML xml.NameB.fieldNames MyKey,field-nameB1,field-nameB2
Plain2XML xml.NameB.fieldFixedLengths 2,3,3
Plain2XML xml.NameB.keyFieldValue BB
Plain2XML xml.NameC.fieldNames MyKey,field-nameC
Plain2XML xml.NameC.fieldFixedLengths 2,5
Plain2XML xml.NameC.keyFieldValue CC
In xml.recordsetStructure, you add a name for each different structure followed by the
number of occurrences or an asterisk for unbounded occurrences. For each structure
name, you configure the structure separately in a separate namespace such as
xml.NameA.fieldNames and so on.
If your source file is a CSV file, replace each xml.XXX.fieldFixedLengths with
xml.XXX.fieldSeparator.
the result of this conversion looks like this:
<ns:MyDocument xmlns:ns="http://xi.com/test">
<MyRecordset>
<NameA>
<MyKey>AA</MyKey>
<field-nameA>1234567890</field-nameA>
</NameA>
<NameB>
<MyKey>BB</MyKey>
<field-nameB1>ABC</field-nameB1>
<field-nameB2>ABC</field-nameB2>
</NameB>
<NameB>
<MyKey>BB</MyKey>
<field-nameB1>XYZ</field-nameB1>
<field-nameB2>XYZ</field-nameB2>
</NameB>
<NameC>
<MyKey>CC</MyKey>
<field-nameC>12345</field-nameC>
</NameC>
</MyRecordset>
</ns:MyDocument>
Regards,
Vinod.

SOAP over JMS Sender Communication Channel - How to?

Hello folks,
I have an async. scenario in which a SOAP message is posted to a JMS queue, then SAP PI picks up the SOAP message, extracts the payload and maps it into an IDOC to SAP.
Couple of questions...
1. Does the JMS adapter supports SOAP over JMS?
2. Can I get the entire SOAP envelope in SAP PI (just like the "do no use SOAP envelope" function works in the SOAP adapter) ?
3. Is the above scenario possible? Given the fact that my scenario (i.e. ccBPM, mappings, etc..) is expecting a SOAP envelope as input?
Thanks,
Rob

Ok, then I think I am on the right track, but still I cannot get this scenario to work.
JMS (SOAP)-> SAP PI(ccBPM) --> IDOC
I put SOAP messages on the sender queue, those messages dissapear from that queue, so I would expect that I can see them back in PI, but no trace is left behind in the monitoring area... It is like they've never been read from the input queue.
What is happenning with those messages? The definition of the SOAP envelope has been uploaded as an external definition and linked to a message interface in the repository.
JMS Communication channel checked but it is also fine.
Any clues where to look?
Thanks.

Issue with JMS sender Communication Channel

Hi All,
We are tying to connect to IBM WebSphere MQ system from SAP PI and pickup messages thru sender JMS adapter.
This is WebSphere MQ -> PI -> Proxy Async scenario. We deployed the required sda file in SDM. We could connect to MQ system message queue, and pick messages from PI development system.
But, when we are trying to do it from PI test system, we get the following error in Comm Channel monitoring:
Error while processing message 'b000f150-15cf-4484-24ec-d8ad10acb685'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Exception in method process.: BaseEJBException: Exception in method process. at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
The patch levels (ABAP & Java) are the same for both the PI systems.
sda file is also deployed successfully for both systems. Comm Channel config is exactly the same for both the systems.
But, still we get the above error.
We did full cache refresh, CPA cache refresh, stopped/started comm channel, restarted the adapter, java stack, and whole PI system after deployment. But, still we get the same error.
Can you please tell me if i am missing something here?
Thanks,
Chandra

Hi,
>>>MessageFilterException
my exp with this error on JMS
a) delete the channel in ID
b) recreate it and active and it works ....
at least with activemq jms
Regards,
Michal Krawczyk

JMS sender communicaton channel error

Hi,
The JMS sender communication channel throws the following error in Communication Channel monitoring in RWB.
<b>Channel started but Inactive</b>
<b>"Channel removed; check whether channel was deleted or moved to another Adapter Engine"</b>
But the channel is active and a copy object of the same channel works succesfully.
Has anyone faced such an issue?
Thanks,
Ambili

Hi Abhishek,
Thanks for ur reply.
1. Already tried it, but still the same status.
2. Yes, i can see the channel in sxi_cache.
3. Tried this several times, same message.
The issue is just for this channel and as I mentioned before, a copy object of the same channel works perfectly fine.
Thanks,
Ambili
Edited by: Ambili Jose on Jan 19, 2010 7:30 AM

Sender JMS Synchronous communication channel not picking up files from JMS

Hello,
One of our Sender JMS synchronous communication channel (used Sync/Async bridge in the module section to make it Synchronous) is not picking up files from JMS system though the channel looks to be active (greeen).
When I am trying to stop the channel, it is giving error as "1 of 1 administered and selected channels have not been stopped", and after this when I start the cannel again it shows green but not picking up any files.
if anyone is haivng any solution for this, please reply back.
Thanks in advance.

Messages available in JMS system? please check queue's if message were there and it is not picking up then some thing wrong with cc.
simple solution create new communication channel with same details and try to use the same.

Umlaut Conversion issue in Sender communication channel SAP PI

Hi Gurus,
We are facing issue while conversion.
umlaut Conversion issue in Sender communication channel that is reason channel not able to pic the file from the path.
Sender CC error:
Value of incoming field is too large. Segment:'IMD', Field:'7008', MaxLength:'35', value:'Plssvvkbecher LÃ¼bzer 0,4 (1280Stk p' DESCRIPTION: The length of the field value is too big !
Actually field contains 35 Chars only the value is : 'Plssvvkbecher Lübzer 0,4 (1280Stk p'
We tried with “ISO-8859-1” if the field value is less than 35 characters it is able to converting.
Please help me out from this issue.
Thank you.
Regards,
Jittu.

Hi Jittu,
Have you tried using the codepageconversion bean in the modules under the sender? It would be like:
AF_Modules/TextCodepageConversionBean with a parameter of Conversion.charset and a value of utf-8.
Regards,
Ryan Crosby

File Structure - Sender Communication Channel

Hi All,
My Sender flat file structure is below like this
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
I did the Sender Communication Channel configuration - Content Conversion
Document Name : XXX
Document NameSpace: XXXX
Recordset Structure: MT_Test,*
Recordset Sequence: Ascending
Key field Type: String Case-Sensitvie
MT_Test.fieldNames: Filed1,Field2,Field3,Field4,Field5,Field6
MT_Test.fieldSeparator: '|'
MT_Test.additionalLastFileds: ignore
MT_Test.endSeparator : 'nl'
ignoreRecordsetName: true.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_Test xmlns:ns0="http://XXXXX">
<JOBS />
</ns0:MT_Test>
What is the Issue, where i missed some thing, In message mapping, its correct..
Thanks.
SR

SR,
I am still little confused with your below statement.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
>
> <?xml version="1.0" encoding="UTF-8" ?>
> - <ns0:MT_Test xmlns:ns0="http://XXXXX">
> <JOBS />
> </ns0:MT_Test>
You mean to say that in MONI, the mapping output is fine, but when you check the output at RWB -> CC Monitoring for the Sender Channel, then you get the above mentioned XML?
This means that there is nothing wrong with your source CC settings. If the entry in RWB -> Sender CC is wrong, your MONI entry will never be right. So, this is really weird.
What is the source structure that you have defined in DT?
Regards,
Neetesh
Edited by: Neetesh Raj on Sep 29, 2009 2:31 PM

BIC Module Error in Sender Communication channel for EDI to File scenario.

Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
Abhishek

Hi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish

Inactive Sender Communication Channel still processing Files?

We de-activated the Sender Communication Channel of an interface. However, the file adapter keeps processing?
Anybody know what is going on?
Thank-You.

Hi Tom,
1) Check out Whether you have De-activated the Right Adapter.
2) Refresh the Cache,
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
c)Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

PI sender communication channel not reading files from NFS directory

Hello,
I have a sender communication channel configured to read file from NFS directory which is on ECC server. A program in ECC generates the file and puts it on the ECC server in the output directory. PI sender communication channel is supposed to pickup this file and process it. If I give the NFS path as the source directory, I am getting error: Configured source directory '//Server/DIR/OUT' does not exist. I tried putting '
Server\DIR\OUT' too but same error. Do I have to add the NFS path of ECC into PI as logical path?
Any suggestions?
Thanks,
Sangita

Hello Sangita,
Your ECC server is an external system, therefore you need to activate FTP service in that system and use the transport protocol FTP:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
You can use NFS protocol when you have a local directory in XI server.
Best Regards,
.Luis Bernal.

JMS sender communication channel content conversion

Similar Messages

Maybe you are looking for