Error in Out bound status in sxmb_moni in WS to IDOC  scenario

HI all,
This question remains unresolved I have Provided the trace contents as asked by XIans.
I am Again sending the contents of the trace.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <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 =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender 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="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = pitest.monet.local:8001</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 10.10.10.26</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<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="3" type="T">system-ID = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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 = 4B7D33199091C54592B7B94A466ED9C2</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="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 4B7D33199091C54592B7B94A466ED9C2</Trace>
<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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0004</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0004</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 4B7D33199091C54592B7B94A466ED9C2</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - ERP_D_ADR200</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">Check conditions for (Inb: Party Srvc If) ERP_D_ADR200 ATT_ABS.ATT_ABS01</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ATT_ABS.ATT_ABS01</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<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 = XBTO4___0002</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="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Begin of pipeline processing PLSRVID = 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="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 4AE42F31B3BC3733A792B4DDEDD54756</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 1D47292048CD11DB8AD9FDDE0A0A0A5E</Trace>
<Trace level="1" type="T">Interface Mapping http://www.gemsconsult.com/LAB_ABA/wstoidoc PublishLeaveStatusSoapIN_to_ATT_ABS01</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_ completed. (executeStep() of com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-KCRS_3RDP_D</Trace>
<Trace level="2" type="T">-ERP_D_ADR200</Trace>
<Trace level="2" type="T">urn:sap-com:document:sap:idoc:messages.ATT_ABS.ATT_ABS01</Trace>
<Trace level="2" type="T">Channel found: - ERP_D_ADR200 - IDOC</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Channel for IDOC adapter: IDoc</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = IDOC</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_IDX_IDOC_SERVICE</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
<Trace level="2" type="T">RFCDEST : ADR_200</Trace>
<Trace level="2" type="T">Port : SAPADR</Trace>
<Trace level="2" type="T">Docrel :</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Saprel : 700</Trace>
<Trace level="2" type="T">Queue-ID:</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service KCRS_3RDP_D</Trace>
<Trace level="1" type="T">Receiver service ERP_D_ADR200</Trace>
<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
- <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
<Trace level="1" type="T">Parse XML-BODY</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPADR</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPADR</Trace>
<Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">Release :</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direction : 2</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert one IDoc</Trace>
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BP7011_1</Trace>
<Trace level="2" type="T">Number of found Data records: 1</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPADR</Trace>
<Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">RFC-Dest :</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>
</Trace>
<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">
<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= ADR_200</Trace>
<Trace level="2" type="T">Used TID = 0A0A0A57187045C17D691641</Trace>
</Trace>
<Trace level="2" type="T">TID : 0A0A0A57187045C17D691641</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="T">Async processing: skip mapping of response</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="3" type="T">system-ID = PIT</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Please let me know where the problem is?
Thanks,
SrinivasaP

Srinivas,
This is your error msg. Right? This is what the others are asking you...
Have you checked Wojcitech's reply? Do that. Let us know the result...
P.S: I copied this from one of your previous threads.
Regards,
Jai Shankar
<i>HI I am Gettin the following error in SXMB_MONI
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
att_abs01is the Idoc used.
Thanks
<b>Hi,
Please check your configuration in IDX1 and verify if port is the same in IDOC receiver communication channel. Check also if in IDX2 you have current IDOC metadata, you can try to download it manually.
Regards,
Wojciech</b>
</i>

Similar Messages

  • WS TO IDOC  ERROR in the OUT BOUND STATUS

    HI all,
    This question remains unresolved I have Provided the trace contents as asked by XIans.
    I am Again sending the contents of the trace.
    Please let me know where the problem is?
    Thanks,
    SrinivasaP

    srini
    check with the steps in the blog:
    <a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi steps required for posting idoc's(XI)</a>
    also
    <a href="/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1 to simple(File-XI-File)scenario and complete walk through for starters(Part1)</a>
    <a href="/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 to simple (File-XI-File)scenario and complete walk through for starters(Part2)</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">Steps to Configure IDoc</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc scenario</a>
    ensure that ur config is in sync. This shud help. Also take the xml payload and test the mapping. If any error in mapping it can fixed then and there.
    PS: Try not to post the same issue in a new thread as it will be difficult to organise. Def you post will be answered.

  • Message has error status at outbound side File To Idoc Scenario

    hi ,
    In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
    When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
    Please suggest what may be the problem ?
    Regards,
    Rohit

    1. First check the RFC destination name used in receiver Idoc adapter communication channel.
    2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
    3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
    4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
    Regards,
    Prateek

  • Find relevant message in SXMB_MONI for a specific IDoc

    Hi,
    I have an IDoc sent from XI to ECC. I need to look at the payload in XI. I was told there was a way to find out which entry in SXMB_MONI is for the IDoc, but cannot remember.
    Does anybody know how to do it.

    Hi,
    use we02 to see the Idoc using IDoc number.Also if you know the pipeline ID or PID you can use SXMB_MONI ->Archived XML Messages (Search using ID)
    Also check BD20 and BD87.
    Regards
    Aashish Sinha
    PS : reward points if helpful
    Edited by: Aashish Sinha on Jan 3, 2008 12:21 PM

  • Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

    I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
    which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
    Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
    Could you please tell me , what is the issue with the partner type configuration .

    Hi,
    Error 29 occurs when there is an incomplete or no partner profile maintained.
    Check whether you have done the correct partner profile settings in WE20 outbound parameters.
    For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
    with correct message type WMMBXY  and Idoc type WMMBID02. Also check for message function code.
    Regards,
    Savitha

  • Out Bound / In Bound IDOC Succes full status in R3

    Hi Frnds,
    I am sending IDOC from OUT BOUND.
    Its succes full wts the Status in R/3 12 or 3. How to check in R/3.
    I am sending IDOC from IN BOUND.
    Its succes full wts the Status in R/3 ??. How to check in R/3.
    Can any one explain the process..
    Regards,
    Raj

    Hi,
    Outbound IDOCs
    Code      Error      Event Severity      SAP Meaning
    02      Yes      Error      Error passing data to port
    03      No      Error if transaction SM58 indicates an RFC transmission error      Data pass to port OK
    04      Yes      Error      Control information of EDI subsystem
    05      Yes      Error      Translation
    06      No      Harmless      Translation
    07      Yes      Error      Syntax check
    08      No      Harmless      Syntax check
    09      Yes      Error      Interchange handling
    10      No      Harmless      Interchange handling
    11      Yes      Error      Dispatch
    12, 13, 14      No      Harmless      OK
    15      Yes      Warning      Interchange acknowledgement negative
    16      No      Harmless      Functional acknowledgement
    17      Yes      Warning      Functional acknowledgement negative
    18      No      Harmless      Triggering EDI subsystem
    20      Yes      Error      Triggering EDI subsystem
    22      No      Harmless      Dispatch OK, acknowledgement still due
    23      Yes      Error      Retransmission
    24      No      Harmless      Control information of EDI subsystem
    25      Yes      Warning      Processing despite syntax error
    26      Yes      Error      Syntax check
    27      Yes      Error      ALE error
    29      Yes      Error      Error in ALE services
    30      No      Harmless      Ready for dispatch (ALE)
    31      No      Harmless      IDOC is marked for deletion
    33      No      Harmless      Original of an IDOC which was edited
    34      Yes      Error      Error in control record of IDOC
    36      Yes      Error      Timeout error; electronic signature not performed
    37      Yes      Error      IDOC added incorrectly
    38      No      Harmless      IDOC archived
    39      No      Harmless      Receive confirmed
    40      Yes      Error      Application document not created in target system
    41      No      Harmless      Application document created in target document
    Inbound IDOCs
    Code      Error      Event Severity      SAP Meaning
    51, 52      Yes      Error      Posting error
    53      No      Harmless      Posting successful
    54      Yes      Error      Error during formal application check
    55      No      Harmless      Formal application check
    56      Yes      Error      IDOC with error added
    60      Yes      Error      Syntax error
    61      Yes      Warning      Processing despite syntax error
    62      No      Harmless      IDOC passed to application
    63      Yes      Error      Error passing IDOC to application
    64      No      Harmless      IDOC ready to be passed to application
    65      Yes      Error      ALE error
    68      No      Harmless      IDOC is marked for deletion
    70      No      Harmless      Original of an IDOC which was edited
    73      No      Harmless      IDOC archived
    Regards
    Seshagiri

  • Out Bound IDOC Status 03

    Hi,
    Can any one let me know about the out bound IDOC ststuses.
    In our system the Out bOund IDOC's are being in status 03, they are not moving to 12. Can any one please let me know why it is not moving to status 12.
    Regards,
    Ravi G

    Hi
    Please execute RBDMOIND program you will get change status 03 to 12
    Thanks,
    Murali

  • Out bound idoc creation urgent!!!!!!!!!!!!

    Hi experts,
              I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.
              IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).
             Please tell me how to create the idoc,  and also the method to trigger it and how to populate the IDOC ( program etc).
              Use full inputs would be promtly rewarded.
    Regards,
    Ram.

    Sample code in the below:
    REPORT zhefrn_idoc_extract_fi LINE-SIZE 160.
    Purpose
    This program extracts FI postings and create IDOCs
    Description
    An IDOC of type ACC_GL_POSTING01 is created from the extracted
    FI-data.
    *- Extract data from BKPF and BSEG
    *- Build the IDOC control record. Use structure EDIDC.
    *- Build and internal table of structure EDIDD with IDOC segments.
    EDIDD contains some keyfields, but the data segment field is simply
    one string, as EDIDD is used for all type of IDOC’s. To simplify the
    process of building this string,  use the SAP datastructures with the
    same name as the segment. E.g for segment E1BPACHE08 use structure
    E1BPACHE08.
    *- Use function module MASTER_IDOC_DISTRIBUTE to create the IDOC’s.
    Remember to commit.
    Important: This program can not handle multiple documents, so all
    postings must have the same key (Company code, currency code,
    postingdate, document date) so that they can be posted in the same
    document. *If the program should handle multiple documents, data
    should be split *according to the key, and an IDOC created for each
    document.
    Standard types
    TABLES:
      bkpf,  "Accounting Document header
      bseg.  "Accounting Document Segment
    TEDS1. "IDoc status values
    Standard types
    TYPES:
      BEGIN OF st_bkpf,
        bukrs LIKE bkpf-bukrs,
        belnr LIKE bkpf-belnr,
        gjahr LIKE bkpf-gjahr,
        blart LIKE bkpf-blart,
        bldat LIKE bkpf-bldat,
        budat LIKE bkpf-budat,
        monat LIKE bkpf-monat,
        waers LIKE bkpf-waers,
      END OF st_bkpf,
      BEGIN OF st_extract,
        bukrs LIKE bkpf-bukrs,
        belnr LIKE bkpf-belnr,
        gjahr LIKE bkpf-gjahr,
        blart LIKE bkpf-blart,
        bldat LIKE bkpf-bldat,
        budat LIKE bkpf-budat,
        monat LIKE bkpf-monat,
        waers LIKE bkpf-waers,
        hkont LIKE bseg-hkont,
        bschl LIKE bseg-bschl,
        shkzg LIKE bseg-shkzg,  "Debit/credit indicator
        dmbtr LIKE bseg-dmbtr,
        wrbtr LIKE bseg-wrbtr,
        dmbe2 LIKE bseg-dmbe2,
      END OF st_extract.
    Table types
    TYPES: tt_bkpf     TYPE STANDARD TABLE OF st_bkpf,
           tt_extract  TYPE STANDARD TABLE OF st_extract,
           tt_edidd    TYPE STANDARD TABLE OF edidd,
           tt_edidc    TYPE STANDARD TABLE OF edidc.
    Internal tables
    DATA:
    G/L Doc header
      gi_bkpf     TYPE tt_bkpf,
    G/L extracted data
      gi_extract  TYPE tt_extract,
    IDOC segment data
      gi_edidd    TYPE tt_edidd,
    Return table
      gi_communication_idoc_control TYPE tt_edidc.
    Global variables
    DATA:
    WA for internal tables
      g_bkpf      TYPE st_bkpf,
      g_extract   TYPE st_extract,
      g_edidd     LIKE edidd,
    *-- IDOC structures:
    IDOC control record
      g_idoc_control_record LIKE edidc,
    G/L document header
      g_e1bpache08 LIKE e1bpache08,
    G/L Account Line Items
      g_e1bpacgl08 LIKE e1bpacgl08,
    Line Item Currency Fields
      g_e1bpaccr08 LIKE e1bpaccr08,
    Return table from MASTER_IDOC_DISTRIBUTE
      g_communication_idoc_control LIKE edidc.
    Selection screen
    SELECTION-SCREEN BEGIN OF BLOCK 1 WITH FRAME.
    SELECT-OPTIONS: a_bukrs FOR bkpf-bukrs,
                    a_budat FOR bkpf-budat,
                    a_hkont FOR bseg-hkont,
                    a_usnam FOR bkpf-usnam DEFAULT 'WMHEFRN'.
    PARAMETERS:     p_create AS CHECKBOX.
    SELECTION-SCREEN END OF BLOCK 1.
    SELECTION-SCREEN BEGIN OF BLOCK 2 WITH FRAME.
    IDOC control record - Receiver
    PARAMETERS:
      p_rcvpor  LIKE edidc-rcvpor DEFAULT 'PORT-HFN', "Rec. Port
      p_rcvprn  LIKE edidc-rcvprn DEFAULT 'WMHEFRN',  "Rec. Partn. number
      p_rcvprt  LIKE edidc-rcvprt DEFAULT 'US',       "Rec. Partn. type.
      p_rcvpfc  LIKE edidc-sndpfc DEFAULT '§§'.       "Partner function
    SELECTION-SCREEN END OF BLOCK 2.
    SELECTION-SCREEN BEGIN OF BLOCK 3 WITH FRAME.
    IDOC control record - Sender
    PARAMETERS:
      p_sndpor  LIKE edidc-sndpor DEFAULT 'SAPC46', "Send. Port
      p_sndprn  LIKE edidc-sndprn DEFAULT 'WMHEFRN',  "Send. Partn.number
      p_sndprt  LIKE edidc-sndprt DEFAULT 'US'.       "Send. Partn. type.
    p_sndpfc  LIKE edidc-sndpfc DEFAULT '§P'.       "Send. Partn. funct.
    SELECTION-SCREEN END OF BLOCK 3.
    Start of selection
    START-OF-SELECTION.
      PERFORM initialize.
      PERFORM extract_data.
      PERFORM build_idoc_control_record.
      PERFORM build_idoc_segments.
      IF p_create = 'X'.
        PERFORM create_idocs.
      ENDIF.
      PERFORM write_report.
    *&      Form  INITIALIZE
    FORM initialize.
      REFRESH: gi_bkpf,
               gi_extract,
               gi_edidd.
      CLEAR: g_idoc_control_record.
    ENDFORM.                    " INITIALIZE
    *&      Form  EXTRACT_DATA
    Extract FI postings to internal table gi_extract
    FORM extract_data.
    Read BKPF
      SELECT  bukrs
              belnr
              gjahr
              blart
              bldat
              budat
              monat
              waers
        FROM bkpf
        APPENDING CORRESPONDING FIELDS OF TABLE gi_bkpf
        WHERE bukrs IN a_bukrs AND
              budat IN a_budat AND
              usnam IN a_usnam.
      LOOP AT gi_bkpf INTO g_bkpf.
        SELECT hkont
               bschl
               shkzg
               dmbtr
               wrbtr
               dmbe2
          FROM bseg
          INTO CORRESPONDING FIELDS OF g_extract
          WHERE bukrs = g_bkpf-bukrs AND
                belnr = g_bkpf-belnr AND
                gjahr = g_bkpf-gjahr.
          MOVE-CORRESPONDING g_bkpf TO g_extract.
          APPEND g_extract TO gi_extract.
          CLEAR g_extract.
        ENDSELECT.
      ENDLOOP.
      SORT gi_extract BY belnr.
    ENDFORM.                    " EXTRACT_DATA
    *&      Form  WRITE_REPORT
    Writes a report showing the selected data, and generated IDOCs
    and errors
    FORM write_report.
      WRITE: / 'Extracted data' COLOR COL_GROUP INTENSIFIED ON.
      LOOP AT gi_extract INTO g_extract.
        AT NEW belnr.
          SKIP 1.
          FORMAT COLOR COL_GROUP INTENSIFIED ON.
          WRITE: 'Document', g_extract-belnr.
          FORMAT RESET.
          NEW-LINE.
        ENDAT.
        WRITE: /
          g_extract-bukrs,
          g_extract-belnr,
          g_extract-gjahr,
          g_extract-blart,
          g_extract-bldat,
          g_extract-budat,
          g_extract-monat,
          g_extract-waers,
          g_extract-hkont,
          g_extract-bschl,
          g_extract-shkzg,
          g_extract-dmbtr,
          g_extract-wrbtr,
          g_extract-dmbe2.
      ENDLOOP.
    Write generated IDOCS
      ULINE.
      SKIP 2.
      WRITE: / 'Generated IDOCs' COLOR COL_GROUP INTENSIFIED ON.
      WRITE: / g_idoc_control_record.
      LOOP AT gi_edidd INTO g_edidd.
        WRITE: / g_edidd-segnam(10) COLOR COL_KEY, g_edidd-sdata(140).
      ENDLOOP.
    Write staus codes returned from function module MASTER_IDOC_DISTRIBUTE
      IF p_create = 'X'.
        ULINE.
        SKIP 2.
        WRITE: / 'Returncoides from function module MASTER_IDOC_DISTRIBUTE'
                  COLOR COL_GROUP INTENSIFIED ON.
        LOOP AT gi_communication_idoc_control INTO
                g_communication_idoc_control.
    Find error message
    select single
    from TEDS1
          WRITE: / g_communication_idoc_control-docnum,
                   g_communication_idoc_control-status.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " WRITE_REPORT
    *&      Form  BUILD_IDOC_CONTROL_RECORD
    The IDOC control record contains message type, port and
    partnerinformation
    FORM build_idoc_control_record.
      g_idoc_control_record-mestyp = 'ACC_GL_POSTING'.   "Message type
      g_idoc_control_record-idoctp = 'ACC_GL_POSTING01'. "IDOC type
    Receiver
      g_idoc_control_record-rcvpor = p_rcvpor. "Port
      g_idoc_control_record-rcvprn = p_rcvprn. "Partner number
      g_idoc_control_record-rcvprt = p_rcvprt. "Partner type
      g_idoc_control_record-rcvpfc = p_rcvpfc. "Partner function
    Sender
      g_idoc_control_record-sndpor = p_sndpor. "Port
      g_idoc_control_record-sndprn = p_sndprn. "Partner number
      g_idoc_control_record-sndprt = p_sndprt. "Partner type
    g_idoc_control_record-sndpfc = p_sndpfc. "Partner function
    ENDFORM.                    " BUILD_IDOC_CONTROL_RECORD
    *&      Form  BUILD_IDOC_SEGMENTS
          text
    -->  p1        text
    <--  p2        text
    FORM build_idoc_segments.
      DATA: l_transdate(8) TYPE c,
            l_itemnr TYPE i.
      CLEAR l_itemnr.
      LOOP AT gi_extract INTO g_extract.
      Build data - The structures from the underlying BAPI are used to
      simplify thje work of building the data part of the IDOC
    *-- Document header segment E1BPACHE08
    *-- The document header should only be generated in the first loop
        CLEAR g_edidd.
        IF sy-tabix = 1.
          CLEAR g_e1bpache08.
          g_edidd-segnam = 'E1BPACHE08'.
          g_edidd-segnum = 1.
          g_e1bpache08-obj_type   = 'BKPFI'.
          g_e1bpache08-obj_key    = '127387347'.
          g_e1bpache08-obj_sys    = 'APOCLNT800'.
          g_e1bpache08-username   = 'WMHEFRN'.
          g_e1bpache08-header_txt = 'Humle er godt'.
          g_e1bpache08-comp_code  = g_extract-bukrs.
          g_e1bpache08-fisc_year  = g_extract-gjahr.
          g_e1bpache08-doc_date   = g_extract-budat.
          g_e1bpache08-pstng_date = g_extract-bldat.
          g_e1bpache08-trans_date = sy-datum.
          g_e1bpache08-fis_period = g_extract-monat.
          g_e1bpache08-doc_type   = 'SA'.
          MOVE g_e1bpache08 TO g_edidd-sdata.
          APPEND g_edidd TO gi_edidd.
        ENDIF.
    *-- Line item segment E1BPACGL08
        CLEAR g_e1bpacgl08.
        CLEAR g_edidd.
        l_itemnr = l_itemnr + 1.
        g_edidd-segnam               = 'E1BPACGL08'.
        g_edidd-segnum = 2.
        g_e1bpacgl08-itemno_acc      = l_itemnr.
        g_e1bpacgl08-gl_account      = g_extract-hkont.
        g_e1bpacgl08-pstng_date      = g_extract-bldat.
        g_e1bpacgl08-item_text       = 'Halli Hallo'.
        MOVE g_e1bpacgl08 TO g_edidd-sdata.
        APPEND g_edidd TO gi_edidd.
    *-- Line Item Currency Fields segment E1BPACCR08
        CLEAR g_e1bpaccr08.
        CLEAR g_edidd.
        g_edidd-segnam          = 'E1BPACCR08'.
        g_edidd-segnum = 3.
        g_e1bpaccr08-itemno_acc = l_itemnr.
        g_e1bpaccr08-curr_type  = '00'.
        g_e1bpaccr08-currency   = g_extract-waers.
        IF g_extract-shkzg = 'H'.
          g_extract-dmbtr = g_extract-dmbtr * -1.
        ENDIF.
        CALL FUNCTION 'CURRENCY_AMOUNT_IDOC_TO_SAP'
             EXPORTING
                  currency    = g_extract-waers
                  idoc_amount = g_extract-dmbtr
             IMPORTING
                  sap_amount  = g_e1bpaccr08-amt_doccur.
        MOVE g_e1bpaccr08 TO g_edidd-sdata.
        APPEND g_edidd TO gi_edidd.
      ENDLOOP.
      SORT gi_edidd BY segnum.
      LOOP AT gi_edidd INTO g_edidd.
        g_edidd-segnum = sy-tabix.
        MODIFY gi_edidd FROM g_edidd.
      ENDLOOP.
      SORT gi_edidd BY segnum.
    ENDFORM.                    " BUILD_IDOC_SEGMENTS
    *&      Form  CREATE_IDOCS
      Create IDOCS
    FORM create_idocs.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
           EXPORTING
                master_idoc_control            = g_idoc_control_record
           TABLES
             communication_idoc_control     = gi_communication_idoc_control
                master_idoc_data               = gi_edidd
          EXCEPTIONS
               error_in_idoc_control          = 1
               error_writing_idoc_status      = 2
               error_in_idoc_data             = 3
               sending_logical_system_unknown = 4
               OTHERS                         = 5
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ELSE.
      Remember to commit !
        COMMIT WORK.
      ENDIF.
    ENDFORM.                    " CREATE_IDOCS
    Process outbound IDOCs
    Process the outbound IDOCs using program RSEOUT00. The program can be executed from SE38. The IDOC should now have status code 03 Data passed to port OK.
    Create inbound IDOCs
    The inbound IDOC can be created from the outbound IDOC using transaction WE12 Modification of Outbound file Triggering inbound Procg. The name of the target file is not important, but it must not have the same name as the source file.
    Note that the program returns an error, but an inpund IDOC is created.
    Source and Sender
    The source file must have the same name and path as the outbound file in the partner profile. In this example it is created in the TMP directory which seem to exist in the root directory.
    Recipient
    Process inbound IDOCs
    The inbound IDOC should now have staus code 64. Use program RBDAPP01 to process the inbound IDOC.
    Please give me reward points If it is useful.
    Thanks
    Murali Poli

  • Out bound IDOC creation

    Hi experts,
    I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.
    IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).
    Please tell me how to create the idoc, and also the method to trigger it and how to populate the IDOC ( program etc).
    Use full inputs would be promtly rewarded.
    Regards,
    Ram.

    Hi
    Creation of Custom IDOc type and message Type
    First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
    take the Basis help to create them.
    1.First create segments in WE31 Tcode with the required dataelements
    2.Create the Basic Idoc Type in WE30
       release the Segments and IDOC type.
    3.Create Message type in We81
    4.Assign the message type to IDOC type in WE82 T code
    5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
    6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for    Inbound) Outbound Fun module
    7.Create  Workflow setting if needed ..
    8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
    9.Define setting for fun module in BD51
    10.In BD51 Define the settings for Fun module..
    10.Assign the Processs Code to Fun mod`ule
    Outbound Interface
    PROCESS DIAGRAM for Outbound Interface
    1. Analyse Hierarchy Levels
    2. Create New segment
    3. Create New IDoc Type
    4. Create New Message Type
    5. Link Message with IDoc Type
    6. Create an entry in EDP13 via transactions WE20 and BD64
    7. Populate the Custom IDoc via ABAP Program
    7b Error Handling
    7c. Send Status Email
    8. Test the Population of the Custom IDoc
    Step 1 – Analyse Hierarchy Levels:
    Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
    Navigate to transaction code WEDI
    Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
    Step 2 – Create a new segment:
    via wedi : Development - IDOC Segments or Transaction code WE31.
    • Enter segment name and click on Create.
    ? The name of the segment type must start with Z1 , and have a maximum of eight characters.
    • Enter description and enter the relevant field names and data elements.
    ? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
    • Save the segment and enter Person Responsible and Processing Person .
    • Go to Edit and Set Release.
    • Repeat this procedure for each new Segment in the IDOC.
    Step 3 – Create a new IDOC Type
    via wedi Development - IDOC Types or Transaction WE30.
    • Enter segment name (starting with Z), click on Basic Type and then Create.
    • Create as new, enter Person Responsible and Processing Person and enter description.
    • On ‘Create Basic Type’ screen decide where segments should be inserted and go to Edit/Create Segment.
    • Complete relevant fields in the Maintain Attributes screen:
    • From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
    • The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
    • The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
    • Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a ‘Child’.
    • When IDOC created return to initial screen. Go to Edit and Set Release.
    • Go to Transaction WE60 to view the IDoc Type you have created.
    Step 4 – Create new Message Type
    via wedi Development - Message Types or Transaction WE81.
    • Display/Change and click on New Entries
    • Create a new Message Type and Save.
    Step 5 – Link Message Type to IDOC Type
    via wedi Development - IDOC Type/Message or Transaction WE82.
    • Display/Change and then click on New Entries.
    • Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
    Step 6 – Create an entry in EDP13 via transactions WE20 and BD64.
    The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
    • WE20 – Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
    • BD64 – Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to ‘Environment’ on Menu and click on Generate Partner Profiles and generate (not save) profile.
    Step 7 – Populate the custom IDOC via ABAP Program
    See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
    • Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
    • The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
    - PERFORM populate_Control_structure USING c_mestyp
    c_SEGMENT_type1.
    • The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
    - PERFORM transfer_Parent_data_to_seg.
    • The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
    - PERFORM master_idoc_distribute.
    • NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
    • The ALE Layer handles the sending of the IDOC to the receiving system.
    • Error Handling (see Step 7b).
    • Commit work.
    Project Specific
    Step 7b – Error Handling• Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
    • Declare a structure of type ‘MCMAILOBJ’ for sending instructions.
    • Enter values for the internal table based on structure ‘MCMAILOBJ’
    • For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module ‘MC_SEND_MAIL’.
    • Enter values in the following parameters: -
    MS_MAIL_SENDMODE = ‘B’ (Batch Mode)
    MS_MAIL_TITLE = 'Mail Title'
    MS_MAIL_DESCRIPTION = ‘Error description’ (e.g. MATNR not given)
    MS_MAIL_RECEIVER = ‘Name of Receiver’ (To be determined)
    MS_MAIL_EXPRESS = ‘E’ (Express Delivery)
    MS_MAIL_DLINAME = Leave Blank
    MS_MAIL_LANGU = 'E' (Language)
    MS_MAIL_FUNKOBJ_NAME = Leave Blank
    TABLES
    MS_MAIL_CONT = I_MCMAILOBJ
    Note:
    It has to be determined separately for each interface how these errors and mail notifications are to be grouped – dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
    When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
    Step 7c – Send status mail
    • Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
    • Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
    • Use function Module ‘MC_SEND_MAIL’ to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
    Step 8 – Test the population of the custom IDOC
    via wedi IDoc - Display IDoc or Transaction WE02.
    • Enter your message type and execute.
    • Status should be green, double click on one of the Idocs you have created to view its contents.
    • If a problem has occurred click on Status which will give you a description of the error.
    • Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
    • Click on each individual segment and view the content to check that the correct data has been read.
    • If you have UNIX access by using AL11 you can view the file that you have created.
    Note:
    For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
    Regards
    Anji

  • Material Master - Error M3 826 Maintenance status of field ... to screen

    Hi Experts of the Material Master,
    I am getting the error M3 826 "Maintenance status of field MARA-BEHVO does not correspond to status of screen K" when all screens are selected in the Create Material Master transaction.
    Here is my situation: I have added the fields MARA-BEHVO and MARA-TEMPB both of status L (Storage) to a screen called "Phys. Characteristics", which has status K (Basic data).
    This produces  the error message above in standard SAP. I didn't want to change the customizing of the screen to allow L, because this screen is also used by other material types.
    I had to copy the screen MGD1 2701 (Phys. Characteristics) to my custom program for Material Master screens anyhow, as the number of fields and their descriptions had to be adjusted.
    The program was created using the activity "Create Program for User Subscreens" in SPRO.
    in the coding of ZMGD1 screen 2701 I have added this code behind the standard module FELDAUSWAHL to manipulate the standard logic that would blend out L fields on a K screen.
    LOOP AT SCREEN.
    *   Material Type
        IF mara-mtart = 'ZPNT'.
    *     Screen-Names of the 3 fields
          IF screen-name = 'MARA-TEMPB' OR
             screen-name = 'MARA-BEHVO'.
            screen-active      = 1.
            screen-invisible   = 0.
            screen-output      = 1.
    *       Change or Create transaction
            IF sy-tcode = 'JP27' OR sy-tcode = 'JP28'.
              screen-input       = 1.
              screen-required    = 1.
            ENDIF. "transaction code JP27 or JP28
            MODIFY SCREEN.
          ENDIF. "screen-name
        ENDIF. "Material Type ZPNT
      ENDLOOP.
    It all works fine when only a number of screens (but including the modified) screens are selected for creation.
    But it fails with the message above on the modified screen when all screens are selected.
    Any ideas?
    Ralf

    from the message, it appears that ZZKUNNR is a custom field attached to your MARA table. So, it is your System specific.  I don't see ZZKUNNR available in MARA.  If you look at the transaction code OMT3B (configuration for material master data screens), you can find K - Basic Data Screen in Maintenance Status field.
    You may look in this area to fix your issue. Because yours is a custom field, its tough to analyse further.
    Reward points, if it helps!
    Regards

  • Error in SXMB_MONI for HTML to Webservice Scenario

    Hi Experts,
    I am facing following error Error in SXMB_MONI for HTML to Webservice Scenario
    "Runtime exception occurred during application mapping com/sap/xi/tf/_MM_EmailRequest_To_ValidateEmail_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog."
    Only one field is used i.e. email address and mapped properly in IR but still the error is persisting, Please suggest some way out.
    Regards,
    Nitin

    Hi,
    Mapping internall follows the SAX parser. Please check if you are trying to process the data of large size.
    generally while parsing the large data this exception get raised. Even though there is just one field, what is the data size you are trying to pass.
    Thanks
    Swarup

  • Messages in Schedule status in SXMB_MONI and going into queue in SMQ2.

    Hi Experts,
    All messages in XI going to schedule status in SXMB_MONI. When i check in SMQ2 to release after some time the messages are going to "SYSFAIL (Time limit exceeded)" status.
    When i double click on the message in SXMB_MONI, the system is going to "Runtime Error (TIME_OUT)".
    Could anyone please help me how to fix this issue.
    Thanks in advance,
    GRK

    Hi,
    my scenario is file to idoc....
    I have set paraemter in SXMB_ADM as below.
    Category                Parameters               CurrentValue        DefaultValue
    RUNTIME                 HTTP_TIMEOUT         100000                      0
    I have gone through as you suggested still when i double click on message in SXMB_MONI...i am getting Runtime Error (TIME_OUT).
    Please do help me..
    Thanks in advance.
    Krish

  • How to give out a status message indicating the number of fields selected

    Hi experts,
    I hope some one might have done what I'm trying to do. Could some one please show me how to give out a status message saying for example how many fields have been give out(or selected) in the t_ouput in an alv grid? Is there a FM that could do this? I mean like giving the FM the t_output and it will show a status message with the number of fields selected?
    Thank you for your input.
    Nadin
    Message was edited by:
            nadin ram

    Hi Ram,
    Write this code,
    Message 'Select Only Ten Fields' type 'I'.
    It displays The Message in Message Box.
    Or if you want the Error Message means,
    Message 'Select Only Ten Fields' type 'E'.
    Thanks,
    reward If Helpful.

  • Incoming purchase order  vs out bound goods receipt processing

    Hi
    any body know how to develop an interface for below requrement
    creating an interface for incoming purchase order creation and out bound goods receipt processing
    please let me know anybody knows this
    Thanks in advance,
    Best regards
    Alleiah

    I done Purchase order inbound ...
    you have to set up partner profile at we20 like message type,idoc type,port..
    Message type : orders
    idoc type : orders05,once you done it creates the purchase order,for testing you can use we19 ,enter data manually and you can see the status at we02 or we05 transaction
    Reward Points if it is helpful
    Thanks
    Seshu

  • [svn:fx-trunk] 10877: Fix a small syntax error in Path bounds calculations that could result in wrong bounds for edge cases involving MoveSegments .

    Revision: 10877
    Author:   [email protected]
    Date:     2009-10-05 15:23:37 -0700 (Mon, 05 Oct 2009)
    Log Message:
    Fix a small syntax error in Path bounds calculations that could result in wrong bounds for edge cases involving MoveSegments.
    Thanks go to Min for noticing the bug!
    QE notes: None
    Doc notes: None
    Bugs: None
    Reviewer: Deepa
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Path.as

    orangekay wrote:
    That is absolutely unreadable.
    I agree completely. How about also providing a link to a set of input files so that we could actually run the code ourselves? Otherwise, there is no chance to debug the source code, it is just a mess.
    You might have better luck with an older version of the file. To quote the comments:
    // Modified on March 31, 2005. Initialized maxchange in nonlinvoltra() as
    // INFTY. Replaced crnmbr() by a similar, but faster routine interior().
    // Many thanks to Stuart Anderson for pointing out this shortcut.
    I suspect that the "interior" function is just plain incorrect. It doesn't matter if it runs on some other OS. Something about it is wrong and the code is so cryptic that it can't be deciphered.

Maybe you are looking for

  • How to find out the idoc type required for our requirement

    Hi,      How to find out the list of available idoc type in SAP. It will be good if i get to know the table name where all the idoc type definitions are gets stored. Say i have some requirement and for that requirement how i can find the proper idoc

  • Use of   DBMS_LOB.LoadCLOBFromFile on insert trigger

    We have a system where most of the data is stored on disk as BFILES. However, in certain circumstances I'd like to read some of the files into the database as CLOBS as well. I'd like to do this on record creation and thought the easiest way to do thi

  • Displaying menu-items in two columns

    in my menus i separate in the label e.g. Cut..Ctrl+X Copy..Ctrl+C Paste..Ctrl+V (i wrote "." instead of blanks) is it possible to left-arange the hotkeys on the right? => Cut.........Ctrl+X Copy.......Ctrl+C Paste......Ctrl+V I don't want to use blan

  • Javaserver faces rendering ui in jdev ide

    Hello, does anyone has experienced with the JavaServer Faces release 1.1_01 FCS, that the cardemo or other jsf application doesn't render the ui components in jdev 9.0.5.2 ide, having of course "execute tags in jsp visual editor" checked ? I hope ORA

  • How to get Tcode by input Program name?

    HI all If I want to get  T_code name from the program.  Which  function modul should  I use? thanks .