Mapping Error- In IDoc to File scenario

Hi Experts,
Got the Mapping error for one interface (IDoc to file). After comparing with successful message found that the field value (TDLINE) is not availbale in first segment (E1EDT10) in idoc for this failed one.
Mapping is :
TDLINE -- Exists --- Creatif --- Receiver field(in the file)
But here due to the the empty value in first segment the message is failed in XI system, next segment values is not trasmitted to the recever end(maping is the same above). To overcome this issue please suggest the suitable mapping design in IR.
Regards
Mahesh

Hi,
After your CreateIf, use a "IfWithoutElse" by selecting the properties "Keep SUPPRESS Values". To do that, do a right click on IfWithoutElse, choose "Properties".
With this option, you will keep the fact that you have nothing in the source, and so the target context will have a "SUPPRESS" line.  I have not THE solution, so do your own test.
If it's not enough, see also about the "mapWithDefault" (but that depends of your real rule).
Regards.
Mickael

Similar Messages

  • Error in IDoc to file scenario

    Hi Experts,
    I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
      <SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Please suggest me in this issue.
    Thanks,
    Bhuvan.

    Check this link:
    http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
    You might want to refer to the SAP NOTE: 316877
    Regards,
    Ravi

  • How to suppress the Acknowledgement  Error in IDOC to File scenario?

    Hi -
    I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
    I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
    i tried that option but i still get the 'Acknowledgement not possible' error.
    Is there any other way to suppress this error?
    Thanks,
    Tirumal

    Hi Tirumal,
    Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
    This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
    Also go through these documents for any further help:
    http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    Regards,
    abhy

  • Context handling in message mapping  for an IDoc to File Scenario

    Hi,
    Can somebody help me with this issue. I have an Idoc to file scenario. heres my idoc structure. Its a custom Idoc
    Header (1..1)
    Detail (0..Unbounded)
             DependentDetail (0...Unbounded)              Note: This dependentdetail is a subelement of Detail
    Trailer(1...1)
    I  created my target structrure the same way as the Idoc structure.
    My output is a simple text file. I need the output in this format
    Header
    Detail1
       Dependentdetail1
       DependentDetail2
       DependentDetail3
    Detail2
       DependentDetail1
       Dependentdetail2
    Detail3
    Detail4
    Trailer
    Since the Detail and Dependent Detail records are unbounded .
    But right now i m getting my output like this:
    Header
    Detail1
    Detail2
    Detail3
    Detail4
    Trailer
    But the DependentDetail record in not showing up in the output file. I didnot do any context change in my mapping. So do I need to do any context handling??...If so can somebody explain me with this.
    Thanks,
    Adam
    Edited by: hymanroth on Apr 29, 2011 11:11 PM

    Thanks Kenneth foryour quick reply,
    Yes, I see the payload for Dependent detail in SXMB_MONI. So as you said earlier there's a problem with my content conversion.
    my content conversion is as follows:
    Header.fieldNames                             
    Header.fieldFixedLengths                
    Header.endSeparator                        
    Detail.fieldNames                               
    Detail.fieldFixedLengths                    
    Detail.endSeparator
    DependentDetail.fieldNames
    DependentDetail.fieldFixedLengths                   
    DependentDetail.endSeparator
    Trailer.fieldNames                             
    Trailer.fieldFixedLengths                
    Trailer.endSeparator  
    So As I told  earlier. With the above content conversion. I am not able to get the Dependent detail record in my output file. So If there is a change in my content conversion can u check it and tell me where I went wrong.
    Thanks,
    Harsh
    Edited by: hymanroth on May 2, 2011 7:03 PM

  • Error in Idoc-XI-File scenario

    dear all,
    i am doing one Idoc to Xi and then to a flat file scenario. i have created one BS of type 3rd party for receiver and ont BS of type Web as ABAP. Then I created one namespace and import the Idoc type there. I have not created any DT, MT, MI, MM. I have created one interface Mapping where both sender & receiver has same structure & I have selected there mapping type of ABAP-Class with one Z program name.
    Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type.
    Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?
    Warm Rgards,
    N.Jain

    <i>Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type. </i>
    >>
    you dont need a Sender IDoc channel to be configured.
    <i>Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?</i>
    >>>
    1. what does it say in SXMB_MONI ? Has the IDoc come into XI ?
    2. In communication channel monitoring what is the error for the recv. file adapter

  • AckRequestNotSupported error in IDoc to file scenario

    Hi,
    I have a scenario from IDoc to file adatper, when i try to run this scenario, every thing is ok except there is a error in message monitor.
    This error is regarding the Acknowledgment("Acknowledgment not possible"), But the ALEAUD IDoc have been sent to the orignal sender (IDoc side) with the empty content except the Header segment such as sender name, receiver name etc.
    And when i tracted the detail information in message monitor, i got the following error information.
      *<SAP:Status>AckRequestNotSupported</SAP:Status>*
      *<SAP:Category>permanent</SAP:Category>*
    I also went through some weblog and artical, i didn't got the solution.
    If some body also have this error?
    thanks & Best regards
    Rocky
    Following is My acknowledgment error information: FYI
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Response*
      -->
    - <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
      <SAP:Status>AckRequestNotSupported</SAP:Status>
      <SAP:Category>permanent</SAP:Category>
      </SAP:Ack>
    Outbound Acknowledgment content:
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>030</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000036022</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ALEAUD</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPO01</SAP:SNDPOR>
      <SAP:SNDPRN>A01CLNT030</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPO05</SAP:RCVPOR>
      <SAP:RCVPRN>A05CLNT231</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS>03</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 />
      </SAP:IDocOutbound>

    Hi Rocky,
    Check the below links of setting up of ALEAUDUT RESPONSE:
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Check this document on handling IDOC acknowledgements. This might give you some idea.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    Please check the above two links if u have missed anything in setting up the acknowledgement.Let me know if u need furthur information
    Thanks,
    Bhargav.
    Note:Award points if found useful.

  • RFC error in idoc to file scenario in PI 7.0

    Hi Experts,
       I am getting a RFC error message like this below
    :u201D  RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_XI_SEND_MAIL in remote system (RfcClient[RFC_REJECTION_MAIL]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.u201D
    Here  Z_XI_SEND_MAIL is a customised function module which is calling some classes. This function module is responsible for sending emails to a group of people.  This function module is working fine in acceptance server and development server but throwing exception in production. Thus the users are unable to receive emails. There has been no code changes in the function module. Idocs are being triggrred from sap r/3 system into XI, then being processed by a BPM, finally RFC   (Z_XI_SEND_MAIL )   is being called to send email messages. SXMB_MONI  is showing that the email message is being send to the RFC properly but communication channel is showing the above mentioned error.
    Please suggest me what might be the reason of such errors?
    Regards
    Anupam

    Hello,
    Have you tested the production data in your acceptance system or development system for the interface?
    Is it working fine??
    It seems that the function module is generating exception, which could be due to data.
    -Rahul

  • Questions to a Mapping for IDOC-to-File Scenario

    Hi all,
    I want do develop a Message-Mapping for an IDOC-to-File Scenario. A SAP System sends an IDOC to the XI-System and the XI-System should make a mapping an send a XML-File to a FTP-Server. The Strukture of the target message is very easy:
    <xdoc>
       <Invoice>
          @purno
          <HeaderInfo>
             <invno/>
             <shipdate/>
             <extvalue/>
          </HeaderInfo>
          <DetailInfo>
             <LineItem>
                @lineno
                <vpartno/>
                <descrip/>
                <qtyord/>
                <cost/>
                <vendmemo/>
             </LineItem>
          </DetailInfo>
       </Invoice>
    </xdoc>
    The source message is an IDOC. This IDOC can contain one or more positions (E1EDP01). Those different positions should be mapped into different LineItem's (see target structure) -> so in the target file one or more LineItems can appear.
    Is it possible to implement this process with a common message-mapping or have I to implement a business process?
    Thanks
    with best regards
    Christopher

    Hi Christopher,
    <i>Is it possible to implement this process with a common message-mapping or have I to implement a business process?</i> - This thing is possible with common message mapping......you dont need business proces for it.......in msg mapping after taking the source IDOC and target xml struc, map the E1EDP01 field to LineItem field.......just check the occurance of these nodes.....it should be 0..unbounded.........so as many E1EDP01 nodes will be there in idoc, that many LineItem nodes in target will be created.......
    Thanks,
    Rajeev Gupta

  • Error in Operation Mapping for Idoc to File Scenario

    Hi Experts,
    I am doing Idoc to File Scenario for Timesheet IDoc "HRSM_C" and following step are through,
    Sender agreement --> Receiver Determination --> Interface Determination
    got stuck in Operation mapping, it sahows error
    "Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1"
    Also not all the fields of IDoc HRSM_C are transferred to the XI server as I am unable to see all the fields in xml file using transaction idx5, as I suppose the reason behind may be there are no values in those fields.
    Please suggest how to resove the issue and transfer all the fields from R3 to XI in Idoc eventhough it doesn't contain any value.

    Hi
    Refresh CPA cache using user PIDIRUSER.
    Look Note 951318 for Mapping Cache Refresh.

  • Error/Doubts in Idoc-XI-File scenario

    Dear All,
    I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
    For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
    Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
    Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
    In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
    Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
    Can anybody guide if I have followed the correct steps & where I am doing the error.
    Warm Regards,
    N.Jain

    Hi ,
    Plese refer the following blogs ,
    IDoc to File
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    You have to do all this settings mentioned in the docuemnt:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    Also can you check this weblogs on the same:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Thanks ,
    Suvarna
    Award pts if  it helps .

  • Idoc to file scenario error

    Hell Experts,
    I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
    Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But  I didn't get successful results, always the error message shows in SXMB_MONI as follows:
    Ackn Status  contains system error
    During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
    tion in Message-Mapping transformatio~
    Exception of class CX_XMS_SYSERR_MAPPING
    My system Patche level as follows:
    SAP_BASIS     640        0012        SAPKB64012
    SAP_ABA     640     0012                SAPKA64012
    PI_BASIS     2004_1_640 0009        SAPKIPYI69
    SAP_BW     350     0009                SAPKW35009
    The above error is related to patches problems or any Mapping  problems ?
    Please  help me.
    Advanced Thanks.
    Regards,
    Chandra

    Hi,
      This may be a mapping issue, try this:
    a)in interface mapping see if grids are formed at source and target after executing the test option,
    b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
    i am not sure of the patch levels.
    Regards,
    Anirban.

  • Error Resource not Found in SXMB_MONI while doing IDoc to File Scenario

    Hi Experts,
    I am doing IDoc to File Scenario and I am facing Following Error in SXMB_MONI,
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>
      <SAP:P1>193c0e01-bd37-11dd-850c-d879ac131b1f</SAP:P1>
      <SAP:P2>http://clarityPOC</SAP:P2>
      <SAP:P3>com/sap/xi/tf/_MM_Timesheets_iDocToFile_.class</SAP:P3>
      <SAP:P4>-1</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have tested the same file in test tab of mapping, execution of  mapping is successful there.
    Regards,
    Nitin Patil
    Edited by: Nitin Patil on Dec 5, 2008 7:09 AM

    Hi Dharmveer I have done the cache refresh ID in XI Data Cache Refresh using link
    http://sapnbipoc:50000/rep/support/admin/index.html
    but still same error persisting
    and in Integration Builder> Environment>Cache Status Overview >Problem tab
    following error (initial part of the error pasted) is shown
    Thrown:
    com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Adapter Engine af.npi.sapnbipoc not found in SLD
         at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:56)
         at com.sap.aii.ib.server.abapcache.sld.AdapterEngineQueries.getAEUrl(AdapterEngineQueries.java:41)
         at com.sap.aii.ib.server.abapcache.logons.IR_LogonData.<init>(IR_LogonData.java:26)
    Regards,
    Nitin Patil

  • Seeburger IDOC-to-File scenario: Error using Classifier module

    Hello,
    I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
    In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
    localejbs/SeeClassifier        classifier
    localejbs/CallBicXIRaBean      bic
    CallSapAdapter                 0
    classifier   attID             classifierAtt
    classifier   destSourceMsg     MainDocument
    classifier   showInAuditLog    true
    bic          classifierAttID   classifierAtt
    bic          destEncoding      UTF8
    bic          destSourceMsg     MainDocument
    bic          destTargetMsg     MainDocument
    bic          mappingName       AUTO
    bic          newLine           true
    bic          srcEncoding       UTF8
    After conversion in XI, the file fails to write to the folder because of this error:
    Message processing failed. Cause: javax.resource.ResourceException: ---
    Conversion of synchronous request from module chain ended with errors
    ---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
    See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
    Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
    BICMapping Error: The mapping [not specified] you are trying to load cannot
    be found in the right path! Maybe you forgot to compile or to activate the
    mapping!
    When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine.  But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
    I am only facing this problem for the IDOC-to-File scenario.  Somehow the same configuration works for a File-to-IDOC scenario.
    I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be.  Has anyone encountered this problem before?
    Any suggestions would be appreciated.
    Thanks,
    Arianne

    Hi Yomesh,
    Here is the payload.
    <?xml version="1.0" encoding="UTF-8"?>
    <LIST>
      <S_ISA>
        <D_I01>00</D_I01>
        <D_I02/>
        <D_I03>00</D_I03>
        <D_I04/>
        <D_I05>ZZ</D_I05>
        <D_I06>CELORGS01</D_I06>
        <D_I05_2>ZZ</D_I05_2>
        <D_I07>AVX</D_I07>
        <D_I08>032008</D_I08>
        <D_I09>1718</D_I09>
        <D_I10>X</D_I10>
        <D_I11>00401</D_I11>
        <D_I12>000000008</D_I12>
        <D_I13>0</D_I13>
        <D_I14>T</D_I14>
        <D_I15>^</D_I15>
        <S_GS>
          <D_479>PO</D_479>
          <D_142>CLS01</D_142>
          <D_124>058895921</D_124>
          <D_373>20080320</D_373>
          <D_337>1718</D_337>
          <D_28>8</D_28>
          <D_455>X</D_455>
          <D_480>004010</D_480>
          <S_ST>
            <D_143>850</D_143>
            <D_329>800001</D_329>
            <S_BEG>
              <D_353>00</D_353>
              <D_92>SA</D_92>
              <D_324>4500005037</D_324>
              <D_373>20051110</D_373>
            </S_BEG>
            <S_CUR>
              <D_98>BY</D_98>
              <D_100>USD</D_100>
            </S_CUR>
            <S_FOB>
              <D_146>CC</D_146>
              <D_309>OR</D_309>
              <D_352>FREE CARRIER</D_352>
              <D_334>02</D_334>
              <D_335>FOB</D_335>
              <D_309_2>DE</D_309_2>
            </S_FOB>
            <S_ITD>
              <D_336>01</D_336>
              <D_333>3</D_333>
              <D_351>45</D_351>
            </S_ITD>
            <G_SN9>
              <S_N9>
                <D_128>L1</D_128>
                <D_369>GEN</D_369>
                <S_MSG>
                  <D_933>TEST</D_933>
                </S_MSG>
                <S_MSG>
                  <D_933>MESSAGE</D_933>
                </S_MSG>
              </S_N9>
            </G_SN9>
            <G_SN1>
              <S_N1>
                <D_98>BY</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
                <S_PER>
                  <D_366>BD</D_366>
                  <D_93>Graham Crawford</D_93>
                </S_PER>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>BT</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>SE</D_98>
                <D_93>3M COMPANY</D_93>
                <D_66>92</D_66>
                <D_67>0000019591</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>ST</D_98>
                <D_93>SAMPLE</D_93>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SPO1>
              <S_PO1>
                <D_350>00010</D_350>
                <D_330>10.000</D_330>
                <D_355>EA</D_355>
                <D_212>10</D_212>
                <D_639>PE</D_639>
                <D_235>BP</D_235>
                <D_234>230-1812-01JDS</D_234>
                <D_235_2>EC</D_235_2>
                <D_234_2>A00000000000002</D_234_2>
                <G_SPID>
                  <S_PID>
                    <D_349>F</D_349>
                    <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
                  </S_PID>
                </G_SPID>
                <S_REF>
                  <D_128>CO</D_128>
                  <D_127>4500005037-00010</D_127>
                </S_REF>
                <G_SSCH>
                  <S_SCH>
                    <D_380>10.000</D_380>
                    <D_355>EA</D_355>
                    <D_374>002</D_374>
                    <D_373>20051208</D_373>
                  </S_SCH>
                </G_SSCH>
              </S_PO1>
            </G_SPO1>
            <G_SCTT>
              <S_CTT>
                <D_354>1</D_354>
              </S_CTT>
            </G_SCTT>
            <S_SE>
              <D_96/>
              <D_329>800001</D_329>
            </S_SE>
          </S_ST>
          <S_GE>
            <D_97>1</D_97>
            <D_28>8</D_28>
          </S_GE>
        </S_GS>
        <S_IEA>
          <D_I16>1</D_I16>
          <D_I12>000000008</D_I12>
        </S_IEA>
      </S_ISA>
    </LIST>
    Thanks,
    Arianne

  • Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

    Hi All,
    I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an error
    <?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_INV_SND_SERV</SAP:Code>
      <SAP:P1>FILE_BC</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are  getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
    Thanks,
    Geetha

    Thanks everybody! It has got fixed. I just requested No acknowledgements.
    Geetha
    Edited by: Geetha on Nov 11, 2009 5:45 PM

  • IDOC to file scenario testing error --

    Hi experts ,
    When doing an IDOC to file scenario the status of the IDOC in XI (the Trace section @  SXMB_MONITOR) shows that
    PARTY &SERVICE NOT DEFINED
    the failure occurs at message splitting stage .
    more details :
    the sender is represented as a business system
    the receiver has no party and has only a business service
    By chance when i tried to check message status in INTEGRATION ENGINE @ RWB
    i was able to find that XI is trying to send the mesasage to Receiver with party name 12345 this 12345 is the same which i gave in we20 as the partner number .
    What could be the reason ?

    This is the error
    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="1" type="T">...There is no Interface Determination configured for receiver party 0000002569 and receiver service</Trace>
    <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) 0000002569 DELINS.DELFOR01</Trace>

Maybe you are looking for

  • Goods receipt report

    Hello, I wrote a report regarding materials that don't have a goods receipt in the last x days. It works , but I am not satisfied by the performance of the report. First, I have selected all the materials that I consider as active in the sistem. SELE

  • Why does save get greyed out in ID CC after a few commands?

    Hi everybody, I'm trying out ID CC on an iMac running OS X 10.9.2 and after a couple of commands, the save, save as, undo, etc just get grayed out. I've tried restoring the preferences, restoring permissions, reinstalling CC after a complete clean wi

  • NEXT page in Smartform 4.6c

    Hi Friends I have one requirement.I am creating PO smartform, there are two pages are required.First page has header data and item data etc.The second page has contains text(terms and conditions).The first page and second page main window width is di

  • BT Cloud App for Mac - Upload freeze issues?

    Anyone experiencing freeze issues during upload sessions?  I just downloaded the app yesterday and kicked off an upload of 20K (ish) files.  It progressed nicely through the day, but clearly froze at some point during the night.  Following a reboot I

  • Role Menu for ESS (WDA) in SAP NWBC

    Dear experts, I am implementing ESS&MSS using SAP NWBC. For this use the following documentation: Configuration of the Role Menu for ESS (WDA) in SAP NWBC - SAP Documentation SAP delivers the composite role SAP_EMPLOYEE_ESS_WDA_2. 1. Call up transact