997 inbound error in AK404

Hi All,
Attached 997(acknowledgement coming inbound from customer to SAP) is failing with error in parsing at AK404 (index out of bounds exception)
Any idea why?
thx
mike

Did you try converting the raw file into XML using B2B toolkit? There should be a checkbox for enabling "Log converting" which should log all the steps..
In addition, Compare the file with any other successful 997 and see if you can find any difference..

Similar Messages

  • B2B Inbound Error : Need Clarification

    Hi All,
    I would like to illustrate a particular use case for B2B Inbound Errors and if there is any workaround available to get over the problem. We are using B2B version 10.1.2
    Use Case Details</strong1. Consider the scenario wherein we have a Inbound EDI File which has 100 transactions in it. B2B reads the file and automatically debatches into individual transactions and processes them separately.
    2. Out of the 100 transactions in the input file, if say 5 transactions are error transactions, we have observed that all the 100 transactions error out in B2B.
    3. The 95 correct transactions fail with the error "General Validation Error" and the 5 error transactions have the exact error details in the B2B Message Reports.
    4. Ideally, B2B should error out only the 5 error transactions and process rest of the 95 transactions without allowing them to fail with "General Validation Error".
    I am sure that most of us must have faced this error. Could someone please let me know the folllowing:
    1. Is there any setting in B2B by which we can enable it to error out only the transactions which have valid errors in a single file
    2. Is there any other workaround that we can take to avoid this issue.
    The reason we need to have a solution for this is because in our Production B2B environment we receive inbound files from Trading Partners which have hundreds of transactions in each file.
    If, even a single transaction has error, then the whole file errors out and it is quite cumbersome to browse through the B2B Message Reports to get the exact error transaction because all the correct transactions would failed with error "General Validation Error".
    Please let me know the inputs.
    Thanks,
    Dibya

    Hi Ramesh,
    Thanks for the clarification and information. We have already set the parameter OneErrorAllError = true and my understanding was that if we set this parameter to TRUE, it means that if one transaction in the OUTBOUND batch errors out then the whole batch will error out.
    I was not aware that it also holds true for INBOUND. Is there any other way that we can set this parameter based on direction (INBOUND or OUTBOUND).
    We would like to have this parameter set for OUTBOUND and disabled for INBOUND Transactions.
    Please let me know. Thanks Again.
    Regards,
    Dibya

  • EDI inbound error message

    Hi
    While processing the inbound DELINS Idoc, i am getting the error message Vendor number & has not been saved for customer &.
    Could you please guide me to do the necessary configuration to avoid this error.
    Thanks in Advance
    Regards
    Shaju

    you can goto We 19 and reprocess the idoc in debug mode to find the actual problem.
    GO TO WE02
    Get the Partner Number
    GOTO WE20
    Get the inbound Process code
    Get the function module associated with the same
    Make a Break Point on the function module

  • CIF Inbound error in APO

    Hello Guru,
    May am trying to CIF and activate a plant from R/3 to APO via, doing in R/3 rimodgen and rimodac the result in APO is error in SMQ2 (Inbound queue) saying ::023 XXXX Production Plant, or message no. Message no. SR053
    Hope you can help me resolve this APO error.
    Thanks

    Totchiki,
    Pretty self explanatory.  The address that is moved over with the plant contains basic configuration data that does not exist in your SCM system.
    Configuration of Regions in SCM are found at OVK2.  Configuration for Regions in ERP are found in the same transaction.  Ideally, you would like these two to be identical for both systems.  At a bare minimum, though, the regions that are contained in every address transferred across to SCM must exist in the SCM configuration.  Add the regions to SCM that the error messages tell you are undefined.
    Best Regards,
    DB49

  • HTTP Inbound error - 500 SOAP PARSING HEADER

    I am working with receiving inbound acknowledgement a text file from the customer to FTP through XI, the URL I supplied to the customer is in the form.
    http://<url address linked to XI server:port>/sap/xi/engine?namespace=<namespace>&
    interface=<sender interface>&
    service=<Sender Service>&
    party=&agency=&scheme=&
    QOS=EO&sap-user=&sap-password=&sap-client=005&sap-language=EN
    Customer is receiving the error message and I don't see any trace of them contacting our XI. When I tried testing usign SAP pI 7 client test tool with out providing /SAP/XI/engine? it doesn't throw any error and no xml payload file generated in FTP though no error seen.
    Any one have any idea what this probelm could be?
    Thanks,
    Menaga

    Hi,
    you can do this
    1. start ICF trace  form transaction SICF in order to log the message which is being send by your partner
    this way if anything is reaching XI you will see it in the log
    http://help.sap.com/saphelp_nw04/Helpdata/EN/80/b2dd3a6dac703be10000000a11405a/content.htm
    Regards,
    Michal Krawczyk

  • B2B Inbound error after version upgrade

    Hi All,
    1. We upgraded from 11.1.1.3 to 11.1.1.6.
    In 11.1.1.3, for Inbound, we used B2B adapter to get the message from IP_IN_QUEUE. We created a process with receive activity and the messages were picked from the queue successfully.
    In 11.1.1.6, we migrated the code without any change and while testing, we are getting the following error,
    B2B Label:PCBPEL_11.1.1.6.0_GENERIC_111214.0600.1553: oracle.fabric.common.FabricInvocationException: IDeliveryService.request() invoked for one-way operation 'receive'. This method can only be used to invoke two-way operations which return an output message. Please check the WSDL which defines this operation and use the method IDeliveryService.post() to invoke a one-way operation
    Do we need any configuration to be done for this ?
    2. As a work around, i tried using a AQ adapter to fetch the message from IP_IN_QUEUE. But no luck, getting the following error,
    BINDING.JCA-11975
    AQ_INVALID_QUEUE.
    Unable to obtain queue table name.
    Queue does not exist or not defined correctly.
    Drop and re-create queue.
    Dont know whether there is problem with the queue, because outbound queue (IP_OUT_QUEUE) is working (wire messages sent to TP).
    Help me in resolving this issue.
    Thanks,
    Terry

    Hi Anuj,
    i tried your suggestion,
    Scenario 1:
    When Notify Inbound Receipt Acks= false, Exception from TP reaching Queue and my exception consumer(b2berroruser) is running successfully. But when TP sends Successful ack, i dont see the message in the queue and hence my success response consumer (b2buser) is not getting executed.
    Scenario 2:
    When Notify Inbound Receipt Acks= true, Exception from TP reaching Queue but 2 rows getting creating,
    User_data col. of the IP_QTAB,
    Row1: PROD_SOAINFRA.IP_MESSAGE_TYPE('0AA0652813ADFCE80270000016D93592-1','null','TP','HostTP','Exception','Exception','1.0',3,'oracle.sql.CLOB@4528f1','null')
    Row2: PROD_SOAINFRA.IP_MESSAGE_TYPE('0AA0652813ADFCE80270000016D93592-1','null','TP','HostTP','Exception','Exception','1.0',4,'oracle.sql.CLOB@e6e083','null')
    At this instance both my exception consumer(b2berroruser) and response consumer(b2buser) are getting executed (weird). and as expected both the above rows are getting off from the table.
    When TP sends Successful ack, its getting stagnated in the queue, my response consumer (b2buser) is not picking it up.
    User_data col. of the IP_QTAB for receipt ack (which is getting stagnated): PROD_SOAINFRA.IP_MESSAGE_TYPE('0AA0652813ADFA3F75F0000016D934A1-1','null','TP','HostTP','Receipt Acknowledgment','Invoice','1.0',3,'oracle.sql.CLOB@1742edd','null')
    In B2B reports i see only one response (either exception/ack) from TP for a transaction.
    Thanks for your suggestions.
    Terry

  • SAP Inbound error

    Hi,
      I am doing file to IDOC. The message is showing Successful but it is was going to R/3. I am giving there that xml message which generated in SXMB_MONI.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:TimeSent>2006-09-26T05:25:36Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>BS_KAREEM_3RDPARTY</SAP:Service>
      <SAP:Interface namespace="http://file2ZIDOC_Kareem">MI_FILE2IDOC_KAREEM</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>BS_R3_SYSTEM</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ZMTIDOCIN.ZIDOCIN</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>Mrkk5K/IO/2cNNOwFbUlQg==</SAP:ObjectId>
      <SAP:SWCV>/fKMsErhEduTP/v6CjIBJA==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ZMTIDOCIN.ZIDOCIN</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2006-09-26T05:25:36Z" wasRead="false">
      <SAP:Engine type="AE">af.x11.apollo</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-09-26T05:25:37Z" wasRead="false">
      <SAP:Engine type="IS">is.01.apollo</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-09-26T05:25:37Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
      <SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>
      <SAP:Info>0000000000004003;</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>001</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000004003</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPX11</SAP:SNDPOR>
      <SAP:SNDPRN>C11CLNT001</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPA11</SAP:RCVPOR>
      <SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS />
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY>70C7D1704D1F11DBC92E000D60E1FBDF</SAP:ARCKEY>
      </SAP:IDocOutbound>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20060926</SAP:Date>
      <SAP:Time>105537</SAP:Time>
      <SAP:Host>apollo</SAP:Host>
      <SAP:SystemId>X11</SAP:SystemId>
      <SAP:SystemNr>01</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>003</SAP:ProcStatus>
      <SAP:AdapterStatus>007</SAP:AdapterStatus>
      <SAP:User>PIAFUSER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>002</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId />
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService />
      <SAP:QIdInternal>XBTO2___0002</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="001">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">0A32012412084518B9D10012</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID">0A32012412084518B9D10013</SAP:EOReferenceOutbound>
      <SAP:MessageSizePayload>1004</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>3457</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>1004</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>650</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IDOC</SAP:AdapterOutbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>13</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Receiver_Agreement_GUID>773C6AD79B4C3C31ACD5CE98876A9904</SAP:Receiver_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052536.997</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.013</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.013</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.216</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.232</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.325</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.325</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.419</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.419</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.45</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="apollo">20060926052537.45</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="end" host="apollo">20060926052537.466</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>773C6AD79B4C3C31ACD5CE98876A9904</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName />
      <SAP:FromServiceName>BS_KAREEM_3RDPARTY</SAP:FromServiceName>
      <SAP:ToPartyName />
      <SAP:ToServiceName>BS_R3_SYSTEM</SAP:ToServiceName>
      <SAP:ToInterfaceName>ZMTIDOCIN.ZIDOCIN</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
    - <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Field>
      <SAP:Name>ReceiverService</SAP:Name>
      <SAP:ExtractorId>604DD4C04D1F11DB98B1000E7FF4C3A7</SAP:ExtractorId>
      </SAP:Field>
    - <SAP:Field>
      <SAP:Name>SenderService</SAP:Name>
      <SAP:ExtractorId>5D504C304D1F11DBB7BD000E7FF4C3A7</SAP:ExtractorId>
      </SAP:Field>
      </SAP:FieldMapping>
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_R3_SYSTEM</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_File2ZIdoc_Receiver_kareem</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>interfaceVersion</SAP:Name>
      <SAP:Value>3</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passControlSetValues</SAP:Name>
      <SAP:Value>1</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passReceiverValue</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passSenderValue</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value>SAPA11</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>queueing</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>restoreOriginalParty</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>rfcDestination</SAP:Name>
      <SAP:Value>RFC_ZEUS_ABAP</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>sapRelease</SAP:Name>
      <SAP:Value>700</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>segmentVersion</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <SAP:System xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Record namespace="http://sap.com/xi/XI/Message/30/general" name="senderAgreementGUID">def5775cf87c3aee8e94b2e814a8791b</SAP:Record>
      </SAP:System>
    - <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 = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver 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="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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <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="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</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 = 70C7D1704D1F11DBC92E000D60E1FBDF</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="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="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0006</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler 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="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <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="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</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="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <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="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 = XBTO2___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="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <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="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</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="1" type="T">Corresponding internal pipeline SAP_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="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <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="1" type="T">Interface Mapping http://file2ZIDOC_Kareem MI_FILE2IDOC_KAREEM</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <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>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <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="1" type="T">Sender and Receiver after Header-Mapping</Trace>
      <Trace level="1" type="T">Sender service BS_KAREEM_3RDPARTY</Trace>
      <Trace level="1" type="T">Receiver service BS_R3_SYSTEM</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 SAPA11</Trace>
      <Trace level="1" type="T">Convert one IDoc</Trace>
      <Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</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= RFC_ZEUS_ABAP</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      </Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Async processing completed OK.</Trace>
      <Trace level="1" type="T">system-ID = X11</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description />
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>
    THX.

    Ansar,
    The note : 837595 would give the list of authorizations.
    <i>************************************************************************************************************
    Summary
    Symptom
    Loading the IDoc metadata from the reference system terminates with the following error message:
    "Metadata EDISDEF for port, IDoc type and CIM type not maintained".
    Other terms
    IDoc adapter, metadata, EDISDEF, IDX2, authorization, Release 4.6C
    Reason and Prerequisites
    You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
    This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
    Solution
    In transaction PFCG, extend the role of the logon user by adding the following authorizations:
    Authorization object S_RFC
    Field name RFC_TYPE value FUGR
    Field name RFC_NAME value EDIMEXT, SDTX
    Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
    Field name ACTVT   value 03
    Field name EDI_CIM value ' '
    Field name EDI_DOC value TXTRAW01
    Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
    Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
    Field name ACTVT      value 03
    Field name DICBERCLS  value
    Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.
    Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function.
    ************************************************************************************************************</i>
    Regards,
    Bhavesh

  • BD87 idoc inbound error for message type HRMD_A

    Hello there,
    I am getting below error  while fetching Inbound idoc in tcode BD87, see log below from ST22
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-10328" occurred in the current database connection "LCA".
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    How to correct the error
        Database error text........: "Mismatch of number of stream members for
         parameter (3) (application 6, database 9)."
        Database error code........: "-10328"
        Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
        "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
        "SIMSCTRL_EXEC_COM"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
    the
    Do we need SAP_APO in order to install LiveCache?
    We have below landsacpe
    - SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
    -LCAPPS Component release 2005_700 with SP
    SAPKIBHD05.
    - We dont have SAP_APO component
    -SAP LiveCache system have MAXDB 7.7.04.29 as backend.
    - Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
    any suggestion how to resolve it?
    Mani

    >
    Mani wrote:
    > I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
    > So Do i still need SAP_APO component?
    I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
    Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
    In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
    The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
    > I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
    Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
    > Secondly can you help me something specific to my problem in coding form?
    Already did.
    > i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
    > LCA >> LiveCache Monitoring >> Tools
    > but i am not able to execute the same, is it a error or we need to configure something?
    Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
    > Operational status is active green light, below is file status.
    >
    >
    KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
    > KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
    > KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
    > KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
    > BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
    > DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
    > DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
    > LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
    > LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
    > LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
    > INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
    > DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
    > ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
    > LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    >
    > any clue whats wrong?
    > Mani
    The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
    That's it.
    As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
    Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
    regards,
    Lars

  • IDOC INBOUND ERROR ( STATUS - 51 )

    hi all,
    when procssing the inbound idoc's i am getting an error ststing that " No status record was passed to ALE by the application " what may be the problem .
    helpfull answers will be rewarded with points.
    regards,
    murali.

    See the code in this function module IDOC_INPUT_CLOSE. I think, even though you are writing the status records to the database, you need to send a status back to XI(ALE) with your status record. That is why I think you are getting this message.
    In WE02, what do you see as status records for 1)original IDOC and 2) your new IDOCs?
    Are you getting this message after you create the new IDOCs or before you split them? Can you tell us what is the logic of your function module(just design logic not the code)?
    Regards,
    Srinivas

  • IDOC INBOUND Error !

    Actually I received a test IDOC ( FIDCCP02) from middleware see beyond, when it was dropped in our R/3 Box. it has a status 51 - Application Document not posted ( the application failed to return a status record to the ALE layer )
    I tried to reprocess with prog. RBDMANIN it didn’t worked and I tried BD87 but it says: this is due to an error in the application function module which processed the inbound IDOC.
    Then, I tried to post the IDOC  through WE19 with particular IDOC number, the test IDOC has been created and it is surprisingly posing data to custom segment ( user exit developed for particular IDOC extension ), Actually this custom segment has diverted to custom table. But it is not posting standard segments data to standard tables.
    As per my understanding it is posting the data for the user exit which I developed in FM.  But the FM is not triggered properly for the standard segments. May be FM executing only user exit  developed for IDOC extension .
    can some one pls tell me  what is the problem behind this ? Appropriate suggestions would be appreciated.

    Seshu,
    Thank you.
    yes checked it with partner profiles, in WE19 by giving the existing idoc number and click on standard inbound option on the menu, it indicates green light, that means partner profiles or correct right ? or do you think it may show like that ?
    if problem with the function module, what could be the problem ? whether the user exit  which i developed interpreting the triggering of FM ?
    actually i receiving IDOC from see beyond, so created RFC destination for See beyond with TCP/IP Connection, with connection type: T & i used same Program ID which they used at Outbound R/3 system .
    Pls suggested me accordingly
    Regards,
    Sridhar

  • ALE Inbound Error Handling

    Hi
    Here I have problem in setting up Error handling in outbound/inbound processing of Idocs in ALE....
    Can any one please explain how to do it....
    My requirement is, if ever idoc goes in to error then the user has to be intimated by mail in SAP Inbox.As per my knowledge it can be done through partner profile...if specify user name in partner profiles/post processing agent place.
    My doubt is will it be same in outbound/Inbound?
    Do i need to do anything other than specifying usernames in partner profiles?
    What is the use of Idoc Administrator?
    Please explain how to do that....
    Awaiting your valuable answers...
    Thanks
    Suresh
    Message was edited by: Suresh Babu  Mannem

    I think you also need to specify the "post processing agent" in your Partner profile - Message Type.
    Check WE20.
    In case you don't want to use organizational assignment then leave the task as it is as general task.
    So only the user specified in "post processing agent" will be taken into consideration.
    Here are the steps that you need to do for a complete error handling procedure ( but you can avoid organizational assignment if you just need to use User Name as receipient ):
    I've taken it from F1 help on error handling:
    Error Handling
    In this section, you can make the settings for error handling:
    Create organizational units and assign standard tasks
    Maintain EDI administration ( Idoc administrator section on Xn OYEA or We40 )
    Maintain error process code ( Xn OYEA or We40 )
    Further you can check it using Verification Processing on OYEA / WE40 .
    Errors are processed in the system in which the error occurred.
    You can repost IDocs that were not posted (with status 51) using program RBDMANIN.
    Requirements
    ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
    Workflow functions as follows:
    A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
    If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
    If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
    For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
    1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
    2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
    3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
    If an error occurs, the system determines:
    1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
    2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
    3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
    Activities
    Create organizational units and assign standard tasks
    Maintain EDI administration
    Maintain error process code
    If you used EDI communication in an earlier version, you can check the assignment of error process codes to the standard tasks.
    Check names of the employees responsible in the partner profiles.

  • Problem in workflow Inbound error Idocs (IDOCAPPL)

    Hi All,
      First of all I am new to workflow. I have created a custom business object ZIDOCAPPL by copying standard object IDOCAPPL. My requirement is to send emails to the users with the inbound Idoc error details.
    My workflow has below tasks.
    Task 1: Create a entry in Ztable with error idoc details. (Background step)
    Task 2: Send a email to the list of users with EDIDC data.
    Task 3: Idoc foreground correction (Foreground step - Using IDOCAPPL-INPUTFOREGROUND method).
    Task 4: Delete the entry form Ztable, which was created in task 1(Background step)
    For this, I have created a ZIDOCAPPL BO and in that created methods for step 1(Create entry in ztable) and Step 4(Delete entry in Ztable).
    Triggering event (SWE2) : IDOCAPPL - INPUTERROROCCURED.
    So my problem is , I need to create below Function modules. Please suggest the logic for below function modules, as I did not understood clearly.
    1-  A new Function module for send email step, that creates the list of users. The user list need to be leveraged from Rule FM and the email through USR01. (This need to be called in my custom ZIDOCAPPL BO method and for  send email step of task 2)
    2- A new FM needs to fetch the positions (table HRP1001) under the sub org units (partners) again under the main Org unit The returned positions needs to be linked back to the task and also for the emails. ( I think this need to be linked to the Role of the idoc foreground correction task (Task 3).
    Appreciated your inputs. Thanks in advance.
    Thanks,
    Ranj.

    I recommend that you do NOT copy the object, but rather create a sub-type.

  • WE19 inbound error

    Hello,
    I try to send a material idoc inbound via WE19 in my netweaver system.
    I can send an idoc via WE 19, but there is the msg that the function module is not allowed or it that there is no function module für
    aii_delinf_in.
    In WE42 I can configure an "identification" for the process code. My AII Master Guide says that there should be a IDOC_INPUT_DELVRY or an IDOC_INPUT_DESADV1 but there is none.
    Do I have to code sth there or where and how can I implement these IDOC_INPUT_* to assign them as an identification in WE42?
    Since there is no identification at the moment, everything seems to work (concerning the partner profiles in WE20), but I get this error. How can I fix this? Pls answer, thx.

    Does no one know what to do?
    Do I have to program this function module?
    The right one does not exist in AII, only in XI. But our solution shall be without XI, so I have to create the missing function module by myself. But what do I have to check?
    What do I have to do to create a function module?

  • Price Catalog inbound error

    Hi All,
    I'm working on Quotations inbound. Populating po_headers_interface and po_lines_interface. After successfully importing one quotation with multiple price breaks, again i'm trying to add new line to the existing quotation. To do this i'm using the action code as UPDATE. While importing them getting the following error
    Error: Information specified in po_lines_interface table does not match the parent record in po_lines table. ...and .... PO_PDOI_INVALID_LOCATION_REC
    Appreciate all ur help.
    If any one having the sample insert codes for the same, do provide, so that i can look into my code.
    Thanks
    Rajeswar

    Hi,
    Thx Mani for ur time. I tried with all options like
    Header action -- line action
    Original -- Original
    Original -- Update
    Original -- Add
    Add -- Add
    Add -- Update
    Still i'm struck-up at the same error as i mentioned in my first Message.
    Thanks in advance for ur time and guidance.
    Rajeswar

  • Help!PO inbound ERROR in SRM SUS when create a PO from R/3

    Hi All:
         I met a problem in SRM SUS,when create a po in R/3 and send this PO to SRM SUS,but there was a  error in XI monitor t-code:SXMB_MONI, i have created the buyer via t-code: BBP_SUS_BP_ADM,and sent the vender from R/3 that is ok.
        check this xml.plesse take a look at error information.
         <FAULT_TEXT>An error occured within an XI interface: Exception occurredA:BBP_BUPA:263 -Ordering party has to be a company Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
         <FAULT_URL />
         I am used  SRM server 5.5, package level is SAPKIBKT06.
         Plesse help....
    Thanks
    Best Regards

    At least i did it.
    The solution was in the transaction BUPA_TAXNUMTYPE. Here you can define wether you want to check the duplicated TAXNUMBERS or not. After applying some patches we think the value of the entry corresponding to our country, changed. So we put the value to OFF and everything worked fine again.
    Thank you.

Maybe you are looking for

  • The other section on my iPod touch is 1.73GB!

    Connected my iPod touch (4th Generation) to iTunes and noticed how high the 'other' section on it is. I do not have much album artwork or many notes or contacts. Why is the 'other' stuff taking up so much memory on my iPod and how can I delete it? Th

  • Keep iPod Touch 2G connected to Mac when at desk?

    When I'm using my iPod Touch 2G at my desk, should I keep it plugged into my Mac? After the battery is charged to 100%, is the iPod running off the power from the Mac or is it running off the battery? Which will make the battery last longer? 1. Keepi

  • Trouble updating Topaz Labs plug-in

    I'm running Topaz Lab's Black and White plug-in under Aperture.  When I get into the plug-in it tells me there is an update available, but when I go to update I get a "Download Failed" error.  Something about "Cannot open /: Path is a directory" erro

  • RAC with Multiple controlfile's

    Is it possible to start multiple oracle instances with different controlfiles (with one database name/alias) instead of using the common controlfile. right now we are using all files in common except pfile like standalone pfile for each instance. The

  • CFContent + CFOutput needs to be on same line?

    Hi everyone, recently I have been devloping a simple page for my webapp the spits out some XML data. I have it working perfectly, just like I want. However, the last line: <cfcontent type="text/xml" reset="yes" /><cfoutput>#variables.xmldata#</cfoutp