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 .

Similar Messages

  • Doubt in idoc 2 file scenario

    Hi,
    I want to create idoc 2 file scenario with out any Transformation.
    In that case how/what to create Data type for receiver.
    I want to receive the same idoc in the receiver folder/Directory (like XML file) with out any transformation.
    Thanks
    Ruban

    Hi,
    For this scenario you need to create the Data type structures as similar to IDOC type and just have to transfer to file without FCC.
    It will transfer the IDOC data as it is in XML format
    refer
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    (Just avoid using FCC conversions on receiver file adapter in above scenarios)
    Thanks
    Swarup
    Edited by: Swarup Sawant on Mar 24, 2008 6:15 PM

  • Doubt in Idoc To File Scenario

    Hi Experts,
    I didn't created any scenario in XI, i have created an idoc in R/3 and i have send it to XI system using tcode we19, i could able to see the idoc in XI system in tcode IDX5, when i double click on the xml message in IDX5, i am getting the follwoing error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Identification
      -->
    - <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="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Actually without creating the scenario in XI also i shouldn't get any error, i should get the xml message without any errors. Please correct me if iam wrong. Kindly suggest me what might be the problem for getting this sort of error.
    U'r help will be greatly appreciated.
    Thanks & Regards,
    Venkat.

    Hi Venkat,
      >> <i>Actually without creating the scenario in XI also i shouldn't get any error, i should get the xml message without any errors.</i>
          If you check in the inbound message payload u can see the xml message with out errors. But the error is due to non availability of receiver determination path to send the xml message to the desired target system from XI.
      So create all the design objects in IR and configuration objects in ID and then try to trigger idoc from r/3 and check the mapping flow and check whether the desired file is created in the target folder.
      For more info refer the below blogs:
      https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken]
    Regards,
    Prasanthi.

  • 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

  • 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

  • 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 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.

  • 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>

  • XI: idoc 2 file scenario( Contain error in SM58)

    Hi experts,
    Here i am having one issue. i have done Idoc 2 file scenario...i have created material in R/3 successfully. when i have sent the material to legacy system..Idoc was generated Successfully in r/3 but i haven't seen that message in SXMB_MONI..
    i got the error message in SM58 i.e. IDX1 port SAPDE1, Client 220, RFc Destination Contain error.
    plz any one can u help me on this....
    Regards,
    Yadav

    Hi Yadav,
    The RFC port you defined is not correct in IDX1. The Port name must be in the form of u201CSAPxxxu201D, where xxx is the system ID of the backend SAP system.
    Just cross check it.
    Check this for more details:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    Regards,
    Sachin

  • 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

  • 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 in TRFC for IDoc to File scenario while sending IDoc

    Hi,
    Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
    Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
    When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
    For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
    Can anybody help me out in resoving the error?
    Regards,
    Suraj Kumar

    Hi,
    Thanks for your reply.
    It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
    Hope I am clear.
    Please let me know, if you need any further information.
    Regards,
    Suraj

  • 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-Error in defining Adapter specific Identfier

    Hi All,
    I am configuring IDOC to FILE scenario where IDOC will be send from ECC to PI System.I did following configuration
    I created RFC,PORT,LS and Partner Profile on R/3 System. I had maintained SLD and IR. In ID I created Configuration scenario and business system.When I click on menu->Adapter specific Identfier where I want to specify IDOC Adapter and RFC Adapter. But it is not allowing to edit it is not editable. As we provide LOGICAL SYSTEM,sender system ID and client number of the sender system.

    Hi Kavi,
    I assume you correctly filled the Logical System of your Business System in the SLD...
    Then in Integration Direction, use menu "SLD clear cache".
    Always in Integration Direction, open your Business System, go to menu "adapter specific identifier", and... close to button "close", you should have another button like something ''check'' or "compare to SLD' or ''retreive SDL data'' (I have not an openned PI to check the right term). Use this button to get value stored in SLD to this local definition.
    Mickael

  • Problem in idoc to file scenario

    hi
    while creating the idoc to file scenario i am facing few problems.
    1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
    2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
    3) i am using my ecc6 training server as my sender and using my XI server as receiver.
    4) i am sending idoc from ecc6 and converting it  to file in XI server and saving it in XI server itself(my receiver in this case).
    my error:
    i send my idoc from we19 transaction, and i see a error message stating
    that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
    my doubts.
    1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
    2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
    3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
    kindly help me with this issue.
    regards
    manoharan

    >
    manoj murugesan wrote:
    > 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
    >
    > 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
    >
    > 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
    >
    >
    > kindly help me with this issue.
    >
    >
    > regards
    > manoharan
    and to 1 & 2 ref. below,
    Configuration steps required for posting idoc's(XI) -
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    ALE configuration for pushing idocs from SAP to XI -
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

Maybe you are looking for

  • Upgrade to 4.0 - asking for 'follow-up activities for middleware'?!??!!

    HI, My upgrade from 3.1 to 4.0 has been going smoothly up to now. It stopped in phase REQ_BBWPCRM now asking me to perform the actions in the chapter 'Follow-up activities for the Middleware' in the documentation 'Upgrade Guide - CRM 5.0'. No mention

  • Call a smartform in the SAP system from portal

    Hi Friends My requirement is to trigger a smartform in SAP, from portal. Please guide me on how to achieve this. Thanks Saran

  • Support for JRockit for WebLogic 10.3 in Solaris x86

    Hi All, I am trying to install JRockit Mission Control 3.1.2 in a Solaris 10 x86 platform. For Solaris Spark I know there is a special distribution.. For Solaris 10 x86 I am trying to install the generic linux version. When I try to install the jrmc-

  • Need info. about dbms_pipe!

    Hi all, Can anybody give me some explanation & an example of dbms_pipe. My requirement is, i want to run host commands through PL/SQL procedure. My host command will be a pro*c executable. In order to run a host command in a pl/sql procedure, i think

  • When NIKON D7200 NEF  (RAW) will be supported

    I have just bought new Nikon d7200 camera. When I' realised that it is not supported in Lightroom 5.7 I was very disappointed. I'm just asking when Nikon D7200 NEF will be supported.