error

[Former Member]

hi...

i am in Idoc to file scenerio....i am having following error while monitior in SXMB_MONI....

com.sap.engine.interfaces.messaging.api.exception.MessagingException: Channel has not been correctly initialized and cannot process messages.....

plz help me on this....

[Former Member · Accepted solution]

Hi,

Take the inbound payload of the xml message from MONI and test your mapping once in message mapping of Test TAB.

the you will come to know the exact error.

Regards

seshagiri

[Former Member]

thx...solved

[Former Member]

Heyyy,

Please provide your findings and solution for this,

it will help to others who ever come across this issue

Regards

Seshagiri

[Former Member]

Hi,

First just edit the description and SAVE and ACTIVATE it

STOP the Receiver communication channel and RESTART it again ...

Check all parameters in the channel ..

Regards,

Jude

[Former Member]

Hi....

There is problem with my content conversion in Communcation Channal only....

while i am trying with message protocal -- File then it works fine...IF i change that to 'File Content Conversion' and i mention only one Paramater 'Headerstrucutre.fieldSeparator ,' then the error occurs....

help me on this.

thx.

[Former Member]

Hi,

Specify these in your Receiver File Channel for FCC

Headerstrucutre.fieldSeparator---- ,

Headerstructure.endSeperator -- 'nl'

Headerstructure.fieldNames -- mention your fields names one by one seperated with comma

Headerstructure.lastFieldsOptional-- Yes

Regards

Seshagiri

[Former Member]

HI...

I populate the paramater as u mentioned.....

but till i am getting the same message...

[Former Member]

Hi FLW,

I populate the paramater as u mentioned.....
but till i am getting the same message...

I notice you are using "HeaderStructure", it means you are having a "ItemStructure" as well. If yes, then use the same parameters for Item.

Hope this helps.

regards,

Neetesh

[Former Member]

hi....

I am using only Headerstructure there is no Item structure.....

thanks...

[Former Member]

Could you share all the parameter settings that you are using in your Content Conversion? What is your recordset Structure that you have mentioned?

[Former Member]

HI ,

These is the Parameter strucure i am using,

Headerstrucutre.fieldSeparator ,

Headerstrucutre.endSeperator 'nl'

Headerstrucutre.fieldNames field1,field2,.....

Headerstrucutre.lastFieldsOptional Yes

till i am getting the same issue....

thanks

[Former Member]

Hey,

Let us know the Receiver Data type Structure Hierarchy how it is....

based on that we may have to mention the Recordset name in FCC at Receiver end

Regards

Seshagiri

[Former Member]

Hi,

the receiver data type looks like this....

1 DT_targetfile

1.1 Headerstrucure

1.1.1 field1

1.1.2 field2.........like this the strucure is mentioned....

thanks...

[Former Member]

Heyy,

As you told this is Idoc to File scenario, you Just have to mention Your Receiver FCC in this way

Recordset Structure -

---

Headerstrucure

Headerstrucure.fieldSeparator-- ,

Headerstrucure.endSeparator-- 'nl'

Regards

seshagiri

[Former Member]

Hi,

I think you are created the receiver structure like below

receiver_DT

--order_recordset 1

-

---

order_row 0..unbound

-

---

field1 0..1 or 1

-

---

field2 0..1 or 1

order_row.fieldNames field1,field2

order_row.fieldSeparator ,

order_row.endSeparator 'nl'

Regards

Ramesh

[Former Member]

Hi sesha,

its correct....i mentioned the same way....

but yet i am having the problem....

help me on this...

[Former Member]

Hi,

Just do this way, some time it will run out of issues, change the Structure of Data Type as follows

1 DT_targetfile

--Recordset

--- Headerstrucure

--- field1

--- field2.........

Before Making this changes, just take the backup(Copy to another name) for mapping if mapping is complex.

and in the FCC mention like

Recordset Structure -

---

Recordset,Headerstrucure

Headerstrucure.fieldSeparator-- ,

Headerstrucure.endSeparator-- 'nl'

These are Case sensitive Copy and Paste as it is...

Regards

Seshagiri

Edited by: N V Seshagiri on Oct 19, 2009 7:34 PM

[abhijitbolakhe]

Hi

This error occures due to wrong parameters in Content conversion in Receiver File Adapter.

the Content conversion parameters are case sensitive ....also while copy...paste ...an additional caracter(space) also copied with

the parameters.

Check your content conversion parameters as per given.

Regards

Abhijit

[Former Member]

check your receiver file communication channel whether all the mandatory parameters are maintained or not .Check also File content Conversion parameters if you are using.

[former_member200962]

Check your FILE channel status in ID and RWB:

1) ID --> Open your communication channel and confirm that all the required details are entered correctly...like target directory, file type etc .... there can be a problem here......also ensure that the channel is actiavted and cache is defect-free

2) RWB --> Component Monitoring --> Adapter Engine --> Communication Channel Monitoring --> Check the status of your channel.....if needed Stop and again Start the channel.

Regards,

Abhishek.

[Former Member]

Hi FLW,

com.sap.engine.interfaces.messaging.api.exception.MessagingException: Channel has not been correctly initialized and cannot process messages.....

Make sure your File Channel has been configured correctly. Your mapping test with the incoming payload should be fine, as I don't think this error is due to any mapping-related issue.

Regards,

Neetesh