Problem in FILE to PROXY interface

Question

Hi friends,
I am trying to implement File(csv) to proxy but i am facing problem in its monitoring.
1. when i go to SXMB_MONI of XI system then i can see BLACK arrow msg as my msg status , what does it mean ???
2. when i try to find the detail description of message then i cant see the msg generated after mapping in my XI system.
3. Payload contains <ns0: element prefix in message type and in namespace, and when i am trying to use same structure in my message mapping created in IR, its giving null pointer error becoz of conflict in <ns: prefix generated at message mapping time and  <ns0: generated at runtime.
Whats the reason behind this <ns and <ns0???
4. When i clicked on my Queue ID information of my message in sxmb_moni then it takes me to some other message wherein i could see the target structure but its not having any segmant in that .
My file adapter status is green
I cant see anything at SXMB_MONI of my R/3 system where i have created my proxy.
My message mapping is working fine (its direct mapping of four fields) when i am testing it in IR.
I WUD APPRECIATE ANY HELP FROM XI EXPERTS.
Thanks
null

Answer 1

Hi Manish -
<i>>>>1. when i go to SXMB_MONI of XI system then i can see BLACK arrow msg as my msg status , what does it mean ???</i>
It means the message is scheduled and waiting in the queue to be processed.  Probably a message processed before it, which was put in the same queue, had an error and is blocking other messages in the queue from being processed.
When you to the Queue ID of the message with the black arrow and link into it, it takes you to the specific queue the message is held in.  When you drill into the queue, the message at the top probably has an error.  The queue must be started again or the errored message must be cancelled from SXMB_MONI. 
<i>>>>2. when i try to find the detail description of message then i cant see the msg generated after mapping in my XI system.</i>
Try turning logging on:  SXMB_ADM->Integration Engine Configuration then Change Specific Configuration (button) then look for:
RUNTIME (Category), LOGGING (Parameter), value of 1 (Current Value)
Once the mapping error is fixed, you should be able to see your target message in the payload of the Request Message Mapping step.
Regards,
Jin