cancel
Showing results for 
Search instead for 
Did you mean: 

Reciever File Content conversion problem

Former Member
0 Kudos

Hi,

i am converting idoc into txt file

in sxmb_moni,the payload of target xml is,


<?xml version="1.0" encoding="UTF-8"?>
<ns0:HRPayroll_014_MT xmlns:ns0="http://XXXX.com/xi/:XXX">
<Infotype014>
	<infotype>001400</infotype>
	<zfty>400</zfty>
	<zicnum>111111</zicnum>
	<begda>20070428</begda>
	<lgart>4000</lgart>
	<betrg>0.00</betrg>
	<anzhl>99.00</anzhl>
</Infotype014>
</ns0:HRPayroll_014_MT>

in File adapter i did like this-

Infotype014.fileldNames	  infotype,zfty,zicnum,begda,lgart,betrg,anzhl
Infotype014.fieldFixedlenghts	  6,3,7,8,4,13,12
Infotype014.processConfiguration	  FromConfiguration
Infotype014.endSeparator	  'nl'

and in RunTime Workbench

i am getting like this

<b>Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:

Parameter 'Infotye014.fieldFixedLengths' or 'Infotye014.fieldSeparator' is missing</b>.

Channel has not been correctly initialized and cannot process messages

please guide me ..how to declare in field Content conversion Prameters.

i dont require column names.fields are fixed lenghts.

regards

Jagan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi friends..

I did CPACache refresh also...
i am getting the same error in RWB..
<b>
Conversion initialization failed: java.lang.Exception: java.lang.Exception: 
Error(s) in XML conversion parameters found: Parameter 'Infotype014.fieldFixedLengths' or 'Infotype014.fieldSeparator' 
is missing
</b> 
i configured Comm.channel like this
Adapter type : file
receiver
Transport Protocol	: File TransferProtocol(FTP)
Message Protocol	:File Content Conversion
Adapter Engine		:Integration Server

Target Directory 	: /xxx/yy
File Name Scheme	: hrpay.txt

FTP Connection parameters
Server 			: xxxxxxxxx
port			: 21
Data Connection 	:passive
Connection security   	: None
User name		:aaa
password		:xxxxxx
Connection Mode: 	:Permanently
Transfer Mode		:Binary
Maximum Number of Concurrency	:1
File Construction Mode : Create
put file 		: directly
Empty Message handling	:Ignore
File Type		:Text


Recordset Structure	:Infotye014

Infotype014.fieldNames		:infotype,zfty,zicnum,begda,lgart,betrg,anzhl
Infotype014.fieldFixedLenghts	:6,3,7,8,4,13,12
Infotype014.processConfiguration:FromConfiguration 
Infotype014.endSeparator	:'nl'

Adapter status : Active


i am getting the in RWB-Message Content like this

  <?xml version="1.0" encoding="UTF-8" ?> 
 <ns0:HRPayroll_014_MT xmlns:ns0="http://xxxxx.com/xi/:xxx">
 <Infotype014>
  <infotype>001400</infotype> 
  <zfty>400</zfty> 
  <zicnum>1234567</zicnum> 
  <begda>20070428</begda> 
  <lgart>4631</lgart> 
  <betrg>0.00</betrg> 
  <anzhl>111</anzhl> 
  </Infotype014>
  </ns0:HRPayroll_014_MT>

if i choose xml type insted of txt..xml is delevering succsessfully
please help me...

regards
Jagan

bhavesh_kantilal
Active Contributor
0 Kudos

Hi,

just use these parameters,

Recordset Structure	:Infotye014

Infotype014.fieldFixedLenghts	:6,3,7,8,4,13,12
Infotype014.endSeparator	:'nl'
Infotype014.addHeaderLine : 0

Regards

Bhavesh

Former Member
0 Kudos

Again I beleive you have made a error in typo

>>Infotype014.fieldFixedLenghts :6,3,7,8,4,13,12

It has to be <b>Infotype014.fieldFixedLengths</b>. Also remove the parameter fieldSeparator.

One more thing press an enter after entering every value for the parameter.

Regards,

Jai Shankar

Answers (12)

Answers (12)

Former Member
0 Kudos

hi thanks bhavesh,jai..and friends..

my problem solved

Former Member
0 Kudos

Hi Bhavesh and Jai..

thank you so much for your help..

this issue in nitemare to me last 2 days..

i think <b>Infotype014.addHeaderLine </b> did the trick

ok friends ..i will use append mode and let you know the status..

regards

Jagan

Former Member
0 Kudos

Hi Friends...

Now i am getting txt file ....my probelm solved ....

Thank you very much for your help and support..

keep going SDN

one more thing friends..i am getting more than one idoc and i want to combine all the idocs in one txt file ..

i want to go for without BPM...

i want to use Append in Reciver file Adapter .

please tell how it works...

for one idoc ..i am getting one row.. i want to collect the idocs and appending to the next lines..

in the reciever file adapter settings

Infotype014.fieldFixedLengths :6,3,7,8,4,13,12

Infotype014.endSeparator :'nl'

Infotype014.addHeaderLine : 0

anything need to add to the above parameters if use <b>APPEND</b> in reciver file adapter insted of Create option..

and also tell me..in partner profile ..now i am using Transfer idoc Immediately ..is it needs to chage to Collect idocs??

my requirement is if we run report..more than one idoc generates..need to combine idocs into one txt file of the above data..

please guide me

Once again Many thanks for your help

regards

Jagan

bhavesh_kantilal
Active Contributor
0 Kudos

Jagam

Glad to know it worked.

If you want to collect Idoc's without BPM you need to follow this blog,

/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm

But , if the only reason that you want to colect Idoc's without BPM is to have a single file, then the APPEND mode would do . Every idoc will add the new record to the exisiting file.

Regards

Bhavesh

PS: Please post your new question in a new thread as that wat things are more clear to people and close this thread by awarding points.

Former Member
0 Kudos

Atlast....:-)

So what really caused the problem?

Collecting IDOCs, see if this blog helps

/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages

Regards,

Jai Shankar

deviprasad_pothireddy
Active Participant
0 Kudos

Hi jaganV,

( This is a small settings problem. It is not a big problem ).

Now see the error,

>> Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:

Parameter 'Infotye014.fieldFixedLengths' or 'Infotye014.fieldSeparator' is missing.

Now copy this thing 'Infotye014.fieldFixedLengths" and paste this in the varialbe list.

Now go to another line.( now it is in change mode). now save this.

now activate the communication channel.

now check the adapter monitoring in the RWB.

Regards,

Deviprasad.

Former Member
0 Kudos

Hi amitanshu,

Thanks for your response..

i given only fieldFixedLenghts

the auditlog is


Time Stamp Status Description 
2007-05-10 15:15:58 Success Message successfully received by messaging system. Profile: XI URL: http://saps020:50100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER 
2007-05-10 15:15:58 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue. 
2007-05-10 15:15:58 Success Message successfully put into the queue. 
2007-05-10 15:15:58 Success The message was successfully retrieved from the receive queue. 
2007-05-10 15:15:58 Success The message status set to DLNG. 
2007-05-10 15:15:58 Success Delivering to channel: FILE_HRP_RECEIVER_HR_PAYROLL014_CC 
2007-05-10 15:15:58 Success MP: entering 
2007-05-10 15:15:58 Success MP: processing local module localejbs/CallSapAdapter 
2007-05-10 15:15:58 Success File adapter receiver: processing started; QoS required: ExactlyOnce 
2007-05-10 15:15:58 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages 
Time Stamp Status Description 
2007-05-10 15:15:58 Error Exception caught by adapter framework: Channel has not been correctly initialized and cannot process messages 
2007-05-10 15:15:58 Error File adapter receiver channel FILE_HRP_RECEIVER_HR_PAYROLL014_CC is not initialized. Unable to proceed: null 
2007-05-10 15:15:58 Success Acknowledgement sent successfully for type: SystemErrorAck 
2007-05-10 15:15:58 Success Acknowledgement creation triggered for type: SystemErrorAck 
2007-05-10 15:15:58 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages. 
2007-05-10 15:15:58 Success The asynchronous message was successfully scheduled to be delivered at Thu May 10 15:20:58 EEST 2007. 
2007-05-10 15:15:58 Success The message status set to WAIT. 

my adaper is in Active status only

please guide me

regards

Jagan

Former Member
0 Kudos

Hi Jagan,

Please give me exact settings and the things you have used in file adapter.

Either way is to use XML2PLAIN module for the conversion.

Thanks

Amitanshu

Former Member
0 Kudos

Hi Bhavesh..

I checked again there is no space in it. the same error coming

i am getting audit log of Comm.channel as


2007-05-10 13:13:07 Success The message was successfully retrieved from the receive queue. 
2007-05-10 13:13:07 Success Message successfully put into the queue. 
2007-05-10 13:13:07 Success Message successfully received by messaging system. Profile: XI URL: http://xxxx:50100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER 
2007-05-10 13:13:07 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue. 
2007-05-10 13:13:07 Success The message status set to DLNG. 
2007-05-10 13:13:07 Success Delivering to channel: FILE_HRP_RECEIVER_HR_PAYROLL014_CC 
2007-05-10 13:13:07 Success MP: entering 
2007-05-10 13:13:07 Success MP: processing local module localejbs/CallSapAdapter 
2007-05-10 13:13:07 Success File adapter receiver: processing started; QoS required: ExactlyOnce 
2007-05-10 13:13:07 Error File adapter receiver channel FILE_HRP_RECEIVER_HR_PAYROLL014_CC is not initialized. Unable to proceed: null 
2007-05-10 13:13:07 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages 
2007-05-10 13:13:07 Error Exception caught by adapter framework: Channel has not been correctly initialized and cannot process messages 
2007-05-10 13:13:07 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages. 
2007-05-10 13:13:07 Success The asynchronous message was successfully scheduled to be delivered at Thu May 10 13:18:07 EEST 2007. 
2007-05-10 13:13:07 Success Acknowledgement creation triggered for type: SystemErrorAck 
2007-05-10 13:13:07 Success The message status set to WAIT. 
2007-05-10 13:13:07 Success Acknowledgement sent successfully for type: SystemErrorAck 

please help me...

jagan

Former Member
0 Kudos

Jagan,

>>Channel has not been correctly initialized and cannot process messages.

This error might be due to improper cache refresh.

1. Make sure the CC is active.

2. Do a CPA cache refresh.

3. As a last option, restart the adapter from VA.

Regards,

Jai Shankar

Former Member
0 Kudos

Hi,

try to check the receiver CC and reactivate and check the status is in active or not and also refresh the cache.. see the below links to refresh the cache

/people/sravya.talanki2/blog/2005/11/03/cache-refresh-errors--new-phenomena

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47...

Regards

Chilla

Former Member
0 Kudos

Hi Jagan,

Please try

RecorsetName : Infotype014

Infotype014.fieldFixedLenghts 6,3,7,8,4,13,12,

dont add anything else first for the content conversion except fieldFixedLengths,

and please give the error log if this doesn't works.

Thanks

Amitanshu

null

Former Member
0 Kudos

Hi Jai and Bhavesh..

thanks for your responses...

i tried with fieldFixed<b>L</b>enghts and i also i tried with removing fieldNames..

i am getting same error "Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'Infotype014.fieldFixedLengths' or 'Infotype014.fieldSeparator' is missing "

please help me

regards

jagan

bhavesh_kantilal
Active Contributor
0 Kudos

Jagan,

What I fear the case here is that you have some extra spaces etc in the parameter in the Receiver File adapter.

Go to the edit mode in the receiver file adapter and go to each of these entries and see if there are any blank spaces etc. If yes, make sure there are none.

Regards

Bhavesh

Former Member
0 Kudos

Jagan,

Can you remove the parmater Infotype014.fieldFixedLengths and add the same again. After specifying the values for the parameter, press Enter key. Some times this may do the trick.

Regards,

Jai Shankar

Former Member
0 Kudos

Hi Jagan,

>>in File adapter i did like this-

Infotype014.fileldNames infotype,zfty,zicnum,begda,lgart,betrg,anzhl

Infotype014.<b>fieldFixedlenghts</b> 6,3,7,8,4,13,12

Infotype014.processConfiguration FromConfiguration

Infotype014.endSeparator 'nl'

The parameters are case senditive. Correct parameter is Infotype014.fieldFixed<b>L</b>enghts

Change this.

Regards,

Jai Shankar

bhavesh_kantilal
Active Contributor
0 Kudos

Jagan,

In your receiver file adapter's content conversion, you need not use the .fieldNames .

Try this setting,

RecorsetName : Infotype014

Infotype014.fieldFixedlenghts	  6,3,7,8,4,13,12
Infotype014.processConfiguration	  FromConfiguration
Infotype014.endSeparator	  'nl'

This should do the trick.

Regards

Bhavesh

Former Member
0 Kudos

Hi Amithanshu,

thnaks for your responses..

i tried <b>Infotype014</b> as recordsetstructure also

same error..

please guide

regards

Jagan

Former Member
0 Kudos

Hi,

Thanks for your reply.

i given Infotype014,* as recordset structure..

i am getting the same error.

regards

Jagan

Former Member
0 Kudos

Please give "Infotype014" as recordset structure.

  • is not required.

Amitanshu

Former Member
0 Kudos

Hi jagan,

If I could guess you have given wrong name in "Recordset Structure" field.

The RWB is giving you the error for missing 'Infotye014.fieldFixedLengths".

and you have given 'Infotype014.fieldFixedLengths" in the content conversion.

Please correct your "Recordset Structure" field put the value Infotype014 instead of Infotye014.

Thanks

Amitanshu

Reward Points if helpful.