Triggering idoc from ECC to XI

I have a idoc-xi-jms scenario where
I have a matrial master, and whenever I change sth in it idoc got to be triggered from ECC with change pointer logic.
I have changed 2 materials and when I ran the RBDMIDOC Program manually, surprisingly some 20000 idocs are triggered.
Can somebody advise me how can I avoid this typical problem if I want to send only changed materials ( i.e only 2 idocs) ??
Thanks
kumar

the change pointer program ususally accumlates all the changes ad then sends them out....
chk the tables CDHDR and CDPOS for changes usually before you trigger the RBDMIDOC program.
Also you can create use the enhancement spot to create a custom code which deletes the changes caused by other criteria than wht you are looking for.
Hope this helps!!
Cheers!!
Sidharth

Similar Messages

  • Error to send a IDOC from ECC to SUS

    Hi,
    I am trying to connect to SAP SUS System using HTTP adapter using PI 7.0.The scenario is
    ECC ->PI->SAP SRM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP SUS on PI. I have encountered the following error after executing the scenario.
    <?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="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>Error during parsing of SOAP header</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have configured HTTP receiver with Addressing type HTTP Destination and configured the HTTP destination field with RFC destination(Connection Type H) created on PI. Here my source and target structures are same i.e DELVRY03. I have triggered DELVRY03 idoc from ECC and i am expecting same xml to be sent to SAP SUS but stuck up with the above mentioned error.
    Someone know how fix this problem?
    Tks,
    Erik

    HI,
    As per my understanding to your scenario, You want to send one IDoc from ECC to SAP SUS system using SAP PI.
    So i hope you must have configured on all the steps required to Send one IDoc to PI syste, Secondly, are you using any Standard interface in PI to send data to SAP SUS system? If yes, you need to create an HTTP Destination for that system and then you have to create XI Receiver Adapter with that HTTP destination to post incoming message to SAP SUS system.
    Your error suggests you are using Plain HTTP adapter to post data to SAP SUS, which is in my understanding is incorrect.
    Regards
    Aashish Sinha
    Edited by: Aashish Sinha on Feb 21, 2011 9:15 AM

  • Unable to import IDoc from ECC to PI 7.1(ESR)

    Hi,
    I am creating an IDoc to File scenario in PI7.1 . I am trying to import the MATMAS IDoc from ECC to PI 7.1.So under the SWCV -> Imported Objects - > Wizard to import IDod/RFC opens -> I enter the ECC system login details -> But when I expand the IDoc node here,I find no IDoc from ECC ,moreover it throws me an error " component should be attached to some frame or dialog"
    Can you please suggest me as what is going wrong.
    Thanks,
    Venu

    Hi all,
    I am using PI 7.3
    When I Import object and passing parameter like application server, system number, uid and password.
    I got this error
            Unable to establish connection to R/3 system servertm_TM9_06 (system=00, client=001)
    Troubleshooting information: 
    Is the target system online?
    Check the connection data; server name and group fields are case-sensitive
    Tips for administrators (see configuration guide for details): 
    Does the user have sufficient authorization in the target system?
    Is the target system configured correctly in etc/services?
    See error logs for details    
    Please help me.

  • IDOC from ECC to XI not coming

    in a XI scenario, IDOC is being sent from ECC to XI,
    in ECC, tcode- we05 i can see the IDOC status as 03 (Green),
    but it has not reached XI,
    this problem occurs sometimes, i mean to say, for the same scenario, sometimes IDOC comes properly, sometimes it doesnt,
    i have seen SM58 in ECC, no dump there,
    all port, partner profiles are ok, since it is 03 status (Green) ,

    Hi Sudheep,
    Check in XI's ABAP Stack of SMQ2, i.e Inbound Queue of XI.
    Check if there is nay entries are present in SMQ2 and release them by clicking on Unlock button.
    And also check in IDX2 whether the meta data is loaded or not and see in IDX5 for IDOC-XML
    Regards
    Seshagiri

  • Download IDOCS from ECC to XI in 7.1.

    Hi
    Can anyone explain how do we download the Idocs from the ECC to PI in 7.1 version
    Thanks
    PR

    HI
    is your requirement to import IDOC metadata from ECC to XI.
    If yes then you need to create an RFC destinations from ECC to XI and XI to ECC for making two way communications for IDOCs of TYPE 3 (ABAP).
    Then from your Software component enable the option for import IDOC and RFC interfaces from SAP systems permitted. Go to imported objects under same SWCV and right click to import IDOC meta data.
    Check the link for refrence
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252bto%252bidoc
    Thanks
    Gaurav

  • Triggering IDoc from SE38

    hi,
    i am triggering IDoc to XI from my report in ABAP.
    when i am filling the control record in the report , the value for the RCVPRN i.e receiver partner should be determined from the partner profiles and should not be hard coded in the report.
    how do i achieve this .
    kindly help
    very urgent
    regards ,
    loveena

    HI,
    You can do this with ABAP report.
    Please refer the table EDP21---Partner Profile: Inbound
    Here all the message types for the Logical system are maintained.
    From this you could get the RCVPRN values. The field SNDPRN contains the values of RCVPRN.
    But here one Message type can be available with multiple RCVPRN values. So in ABAP code you need to handle as per requirment.
    Thanks
    Swarup

  • PO XML proxy is triggered twice from ECC to SUS

    Dear Experts,
    We are using Classical scenario. Once a shopping cart is created and approved a PO will be created in ECC through PI and corresponding SUS PO will be created in SUS system, It will be triggered from ECC. when we check in SXMB_MONI transaction. There are 2 proxy genetared to SUS. Actually only one should trigger.
    Kindly guide how it can be checked.
    Thanks & Regards
    Arun.K.P

    Hi jackytam  ,
    /people/yeusheng.teo/blog/2008/01/05/ordering-unit-vs-order-pricing-unit-in-srm-sus
    you make get some pointers
    regards,
    Neelima

  • Problem when sending IDOC from ECC to MII 12.0

    Hi all,
       I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
       But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
       - 53 IDOCS were successfully outbounded (list in WE02).
       - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
       - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
       I'm wonder why some IDOCs were successful while some others were error. If the bean  IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
       I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
       If some have the same problem and know how to resolve it, could you please help me?
    Thank a lot in advance,
    Vinh Vo

    Hi Vinh,
    Please read the following document:
    [IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
    If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.  
    In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it. 
    I suggest that you follow the document completely and do nothing else to set up a new listener. 
    If you are not using ECC 6.0, you may find the paths are different,  but the transactions codes are generally the same.  However, you may want to check with some of the older installation instructions regarding specific modifications.  Look in the Wiki for MII under Connectivity.
    Good luck,
    Mike

  • IDOC from ECC to PI

    Hi,
    When an IDOC is posted to PI are all the fields populated in PI. If any field in IDOC doesn't have any value will that field be populated in PI also?.
    Thanks .

    Hi Manu,
    No you cant see all the fields of IDOC in PI which processed from ECC.  You can see the fileds only which carries the value from ECC . Rest of empty value fields will not populate in PI.
    Edited by: S Kumar on Nov 21, 2011 10:37 AM

  • Triggering IDoc from R3 using variant program

    Hi,
    I am using the variant program to trigger the IDoc from R/3 System.
    It is successful in r/3 system but its not reaching in XI.
    Help me in resolving this issue.
    Regards,
    Inder

    do you find any trace in SM58 ?
    Check if there are proper authorizations for the user in the destination.
    For authorization;
    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

  • Re-triggering Idocs from SAP Communication layer

    Hi,
    Our webmethods middleware went down for 4 hours. We are trying to see if there is a quick way to retrigger Idocs from SAP for around 3000 doc (various doc, PO, SO, Delivery, Shipment etc). Trying to see if we can change the status in SAP and retrigger (without writing a program). Is there a way to do it. Any pointers would be useful.
    Thanks,
    Anand

    There is no quick way to resend IDocs that have already passed.  I worked at a client in the past that had written a custom program to change the status of an IDoc.  The report program had a similar selection screen to WE05, but current status and new status as parameters.  The program would retrieve IDocs based on the selection criteria and update EDIDC-STATUS to '30'.  You can then resend the IDocs using RSEOUT00.
    You do not need to modify EDIDS.

  • Error while Reading Idocs from ECC 6.0 to Sun IDM .

    Hi Gurus,
    We have a scenerio where we have to update the Sun IDM Server with all the changes in HR Data happening in ECC.
    For that... we have
    1. Created a Logical System for Sun IDM server, Port, RFC Connection (TCP/IP).
    2. Assigned Partner Profiles, Distribution Model etc. for msg. type HRMD_A ;
    3. We have created a Communications User used by the IDM server to connect to ECC.
    Idocs are created daily and are in status 03 - Data passed to Port OK !
    and on the In Sun Identity manager 8.0 we have created SAP resource adapter for ECC 6.0,
    after giving resource parameters our test connection is successful.
    We also changed edit synchronisation policy for the same but when we start synchronisation in IDM, it is unable to read any idocs although Idocs are generated in SAP .
    Log file gives the message as "Incoming IDoc list request containing 0 documents"
    We also have one more error ;
    some times while doing a connection test : JCO.Server could not find server function '剆䍟偉乇'
    while most of the times the connection is successful.
    Please suggest .

    Hi Gurus,
    The error got resolved .
    The changes in the settings i did :
    SAP SIDE : Made the RFC Connection Unicode.
    IDM SIDE : Checked on the "SAP Server Unicode" checkbox; while doing the HR Activ Synch Settings.
    This Resolved the error.
    regards
    Vaibhav

  • BPM/MDM Process - Confirmations Back to BPM from ECC

    We are implementing a BPM / central MDM solution.  After the new master data is sent from the BPM to MDM, and syndicated through PI to ECC, the requirement is to send a confirmation back from ECC that the new master data (ex. Vendor) was created.  I don't see such a confirmation in any of the related blogs on the BPM/MDM subject.
    (1)  Is there a way to send a confirmation back to the BPM (file that BPM picks up?, BPM listener-type service?)?
    (2)  Do you recommend using BAM or ALEAUD for the confirmation out of SAP?  Both would work.  With ALEAUD, I could catch errors in PI and handle them.  With BAM on a Vendor.Created event, I would have no extra IDoc statuses to filter away.
    Thanks,
    Keith

    Hello,
    There are 2 options .
    You can use an outbound IDOC from ECC to PI - after the material is successfully created and PI can update MDM with the status and id created.
    1. You can write a service that will check MDM periodically to see if got back the status & id from ECC/PI successfully.
    2. The other way is to write a synchronous webservice call where BPM will wait for a PI service to provide an update directly to BPM. You need to model Synchronous call in BPM.
    Regards, Anil

  • Problem while triggering IDoc

    hi,
    When i am triggering idoc from R/3 , it is saying idoc transferred to port,
    but when i am checking the idoc in XI system idx5 , i am not able to view the idocs,
    What could be the reason for this?
    Also when i am creating distribution model in BD64 and then saying distribute , it is giving this message:
    <b><b>Model view BANK_CREAT has not been updated
    Reason: Maintenance systems for model view BANK_CREAT are not identical
    ..... Maintenance system in sending system DMYCLNT702
    ..... Maintenance system in receiving system DMYCLNT100</b></b>
    Note:DMYCLNT702 - Testing client
            DMYCLNT100 - Development
    Urgent help needed,
    Thanks,
    Loveena

    Hi,
    Chk the following details which will be helpful:
    A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
    First - Maintain the Sender R/3 System:
    SM59 : Create a RFC destination to XI
    WE21 : Create a TRFC Port ->Specify the RFC Destination Created
    BD54 : Create a Logical System for the Idoc Receiver
    WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
    Second - Log on to XI System:
    SM59 : RFC Destination for Sender System
    IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
    IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
    Also chk the following link providing details of pushing idocs:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

  • Getting Error in SM58 and IDX2 while using IDOC from

    Dear All,
    Getting error when trying to send FIDCCP02 Idoc from ECC to PI system.
    "Basic Type 'FIDCCP02' is unknown"
    Getting the same error while trying to import metadata using IDX2 from PI side.
    All connections and distribution model are created.
    Please help
    Regards

    hey,
    I checked all config again but getting error while checking ocnsistency in BDM5 on ECC system(E1Q).
    It is failing when the messge type FIDCC1 reaches PI QA (X1Q) system and the error states
    Message type FIDCC1 is not defined
    Please check last line of below message:
    E1QCLNT001     Checks in own system E1QCLNT001          
         Message type     @08\QCheck OK@     Message type FIDCC1 is defined
         Segment filtering     @08\QCheck OK@     No segment filtering
         Conversions     @08\QCheck OK@     No conversion
         Partner profile     @08\QCheck OK@     Partner profile has been created
                                      @08\QCheck OK@     .....Port PI_QA
              @08\QCheck OK@     .....Port PI_QA
              @08\QCheck OK@     .....Packet size 0001
              @08\QCheck OK@     .....Basis type FIDCCP02
              @08\QCheck OK@     .....enhancement
         Port     @08\QCheck OK@     Port PI_QA : To PI Quality System
              @08\QCheck OK@     .....Port type: Transactional RFC
              @08\QCheck OK@     .....port version 3: IDoc record types from Version 4.0 onwards
              @08\QCheck OK@     .....Logical address (destination) X1QCLNT001
         Logical address (destination)     @08\QCheck OK@     Logical address (destination) X1QCLNT001 is defined
    X1QCLNT001     Checks in partner system X1QCLNT001          
         Check of own logical system     @08\QCheck OK@     Own logical system is X1QCLNT001
              @08\QCheck OK@     Logical system is the same as the target address
                       Message Type     *@0A\QCheck resulted in error@*     Message type FIDCC1 is not defined
    When I am clicking on error it is taking to WE81 on PI side.
    So do I need to add this message type in PI system as it is present in ECC side?
    Thanks
    Edited by: Chanakya Sharma on Dec 10, 2010 12:10 PM

Maybe you are looking for