Finding a  IDOC or RFC in SAPHR

Hi,
Can you suggest me finding standard IDOC or RFC :
Typically we have to feed some input fields to SAP HR system for employee performance purpose. We are about to find standard IDOC or RFC for feed to HRP SAPR/3.
Input  is : CSV file.
File size expected to be less than 10,000 rows and typically less than 5,000 rows
SAPR/3 would use either RFC or IDOC to process input file
--> Still we need to find standard IDOC or RFC for feed this input.if we do not find IDOC or RFC then what is other methodology to feed this data into HRPSAPR/3? and how do we find standard IDOC or RFC for HR employee details?
Middleware we are using XI.
Thanks in Advance.
PILeran

hi
follow the link for list of idoc tyoes
http://www.sapmaterial.com/messagetypes_Assignment_to_IDOCtypes.html
regards
ravish
<b>plz dont forget to reward points if helpful</b>

Similar Messages

  • IDocs or RFC's

    Hi All,
    Our CRM system needs to be integrated with a 3rd party tool, using standard adapters connectivity was established. Question is, how do we determine for our business scenario whether to use IDocs or RFC's ?
    I am confused with how to send and receive data from an external system (Standard IDocs - how do I find standard IDocs or RFC's for communication)
    I have to send data from table(s) depending upon status change of sales order. Kindly help with any pointers or suggestions.
    Thanks.

    Hi Jacob,
    You must consider the following points before choose the right tool for your scenario:
    The connection with 3rd party shall be synchronous or can be asynchronous?
    If the business process scenario demands a synchronous connection, you should consider a RFC connection; however keep in mind that a RFC connection holds an opened work process instance until the execution is running.
    If you can use an asynchronous connection is your scenario, it is interesting to use iDoc, once you have a range of standard tools to manage all exchanged data between SAP CRM and 3rd party. (e.g log of execution, reprocessing iDoc with errors, among others...)... If there is no standard iDoc for your scenario, you can create a brand new one...
    I hope it helps!
    Best Regards,
    Gabriel Santana

  • Idocs and rfcs not found!!

    Hi,
    Check whether you can find these Idocs in the R/3 System if you goto the tcode we05/we07 and try to check whether this idoc has already been executed, and also try to import those idocs in the SWCV.
    I could not find the RFC name which u have mentioned, let me know more details about that RFC.
    Regards,
    Nithiyanandam

    Manas,
                I have done that long ago, if required I can send u the screen shot of the IR. It's not there!!
    Arnab

  • Problems with sending IDOC via RFC from Unicode to NonUnic

    Hello
    I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
    I have tried different options in sm59, but it didnt help.
    Any ideas? The recipient system is rather old, version 4.0

    hey,
    I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and  RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

  • Best Scenarios when to use IDOC Adapter, RFC Adapter and Proxy

    Please provide me links/weblogs which demonstrate the full scenario that when to use IDOC Adapter, RFC Adapter and Proxy when working with sender R/3 system.
    Regards
    Rachit

    Hi abhinash,
    Check these links for java proxy
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    for ABAP Proxy ...
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
    http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
    for RFC .....
    RFC-xi-SOAP Scenario
    How to send RFC response message back to XI File/FTP adapter?
    https://weblogs.sdn.sap.com/pub/wlg/3865//Troubleshooting [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    Hope you will find them useful ..
    Regards
    Abhi

  • What are idocs, BAPI, RFC?

    Hi,
    What are idocs, BAPI, RFC?
    Regards,
    anuj

    Hii,
    BAPIs and RFCs are the functions exposed by SAP, when it comes to the integration part, you have to know that particular BAPI or RFC. For example, if you want to get table data or want to query to the SAP table then you use RFC_READ_TABLE. Similarly if you want to know whether customer is existing, you need to know which RFC/BAPI has this info. May I know which tool are you using, are you talking about generating a proxy and playing around that.
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    BAPI
    BAPI Programming guide: -
    http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
    BAPI user guide: -
    http://help.sap.com/saphelp_46c/helpdata/en/7e/5e115e4a1611d1894c0000e829fbbd/frameset.htm
    BAPI STEP BY STEP PROCEDURE: -
    http://www.sap-img.com/abap/bapi-step-by-step-guidance.htm
    Example:-
    http://www.erpgenie.com/abap/bapi/example.htm
    PDF download: -
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/200dd1cc-589e-2910-98a9-bb2c48b78dfa
    list of all bapis
    http://www.planetsap.com/LIST_ALL_BAPIs.htm
    for BAPI's
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sappoint.com/abap/bapiprg.pdf
    http://www.sappoint.com/abap/bapiactx.pdf
    http://www.sappoint.com/abap/bapilst.pdf
    http://www.sappoint.com/abap/bapiexer.pdf
    http://service.sap.com/ale
    http://service.sap.com/bapi
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://www.planetsap.com/Bapi_main_page.htm
    http://www.topxml.com/sap/sap_idoc_xml.asp
    http://www.sapdevelopment.co.uk/
    http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
    Also refer to the following links..
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.planetsap.com/Bapi_main_page.htm
    http://www.sapgenie.com/abap/bapi/index.htm
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    BADI
    Check these links on BADI
    http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
    http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
    http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
    http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
    http://www.esnips.com/doc/3b7bbc09-c095-45a0-9e89-91f2f86ee8e9/BADI-Introduction.ppt
    Check this link for advantage of BADIs over User exits
    http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
    Reward points if useful.
    Regards,
    Sushama

  • Cannot find sent IDOCs in XI

    Hi,
    my requirement is to send ORDERS05 IDoc from one SAP ERP 5.0 via a XI-System to another SAP ERP 6.0 to create purchase orders.
    I´ve done the required settings in the sending system like TRFC port (WE21), partner profiles (WE20), RFC destination (SM59), logical system (BD54).
    I´ve done the settings in the XI via transactions SM59, IDX1, IDX2 and the integration builder.
    I can create and send IDocs of message type ORDERS. The have the status "03-The IDoc was sent to an R/3 System or an external program via a transactional RFC" and the port of the XI system.
    But I don´t know if the arrive in the XI system because when I go to XI I cannot find the IDoc, wether with TA SXMB_MONI nor with TA WE02.
    Can anyone help me please?
    Thanks in advance,
    Gerald

    You are right, I think my user has authorization problems.
    When I do an "authorization check" for the system user I get the message "name or password not correct (repeat login)". But I am sure that I use the same name and password for RFC destination of sender system as in PI-System created before.
    Therefore I think it should be authorization problems. Are there any special roles or profiles that are needed for this kind of system user? I´ve granted several SAP_XI* and SAP_BC* roles to the system user...
    Regards,
    Gerald
    It works now, thank you!
    The problem was the password for the XI-user. It has to be in capital letters.....
    Edited by: Gerald Brosch on Feb 18, 2010 9:47 AM

  • Scenario - IDoc - XI - RFC - IDoc

    Hi Experts,
    I am new to BPM.
    We have 2 sap systems...SAP1, SAP2.
    The BPM scenario is,
    When Material changes made in MM02 of SAP1, changepointers creates an IDoc1. IDoc1 is first sent to XI. Now in SAP2, it is to be checked whether that particular changed in SAP1 exists in SAP2 or not. For this, from XI an RFC call is made to SAP2, depending on the return values, the IDoc message that has been reached to XI (from SAP1) is sent to SAP2.
    How to achieve this.
    Any docs, links would help me. I am very new to BPM.
    -Naveen.

    Hi,
    <i>Can any one give me some direction.</i>
    >>>Are you talking about BPM steps ? if so I have given that.
    For Message Interfaces-
    1) Abs, Async, Message Interface of type Idoc
    2) Abs, Sync, Message Interface of type RFC
    3) Abs, Async Message Interface of type Idoc , which is sending to SAP2 system. If you have mapping changes.
    Mapping is outside the BPM, Create a dummy message type for RFC response. To check the response in the BPM
    i.e Idoc to RFC Req Mapping
        RFC Response to Dummy RFC response
    Hope this helps,
    Regards,
    Moorthy

  • Finding out Idoc number of the Invoice List

    Hi!
    how to find out Idoc numberr if I have number of Invoice List?
    For example, I have number of Invoice List for checking it in tcode VF22, but how to get Idoc number of the Invoice List in order to check it in WE02?
    Will reward,
    Mindaugas

    Hi,
         Use NAST with the invoice to get the latest record for that output type..
    use the table CMFP to get the IDOC number..The combination is
    NAST-CMFPNR = CMFP-NR..
    Then in the column CMFP-MSGV1 you can find the idoc number
    <b>Reward points</b>
    Regards

  • DIFFERENCE B/W  IDOC  AND RFC   ADAPTERS

    HI FRIENDS,
    WHAT IS THE  DIFFERENCE B/W   IDOC  AND  RFC   ADAPTERS..? AND WHICH ONE IS
    PREFERABLE  TO USE    IN TRANSFERING DATA FROM THIRD-PARTY SYSTEM TO  SAP.?
    REGARDS,
    RAMAKRISHNA.

    Hi
    These links will help you to understand :
    http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
    Please dont forget to reward with points.
    Edited by: Dheeraj Kumar on Mar 3, 2008 2:59 PM

  • How can we find the Idoc number which posts the material document in SAP

    Hi All,
    How can we find the Idoc number which posts the material document in SAP. We could not able to find the IDOC number from the material document which was posted by Idoc.
    Thanks
    Chandru

    Hi,
    In MIGO you can go to service of object(Just above show overview) and check 5th option workflow you will find the idoc number.
    regards
    suresh

  • Idoc-xi-rfc scenario random fails to be processed

    Hallo all .
    Let me first describe our scenario.
    Generally it is an IDOC - > XI -> RFC case.
    Idocs are created after an order creation .
    In XI there are two different mappings, depending on the idoc structure (the IDOC  type is the same, but the segments created are different)  and two different receivers, each one with an individual communication channel. Each channel is allowed to have up to 200 multiple simultaneous connections .
    Then, each functions decides whether the inbound data is appropriate for it and processes it or not .
    Our problem is this :
    If we send a bunch of orders (eg 100), all of them are processed successfully except of some of them, (eg 4 ).
    In the SXMB__MONI, they are all marked as "waiting for acknowledgment" .
    Yet, there is no obvious reason for their failure.
    If we send again the failed orders, then 3 of them may be processed.
    And finally if we send them again even the last one will be processed.
    So, from what I can see, this problem cannot exist due to the data we send, or the XI configuration, or the functions that are finally called. Actually, it seems to be absolutely random.
    Any suggestions would be highly appreciated .
    Edited by: John Syrigos on Dec 30, 2008 6:08 PM
    Some clarifications : The business scenario is to handle the ORDER idocs that created in the SAP ERP system from SD (Outbound Deliveries) or the Stock Transport Orders (Outbound Deliveries). The problem for the created IDocs is that if the outbound delivery is coming from SD then for each line item of the sd document fills the segment A for example and if the outbound delivery is coming from the Stock Transport Order then fills another IDOC segment for example B. For this reason we decide to create two separate interface mappings in order to send each IDOC in both of the Function Module that handle which of them will be executed. In the daily order processing the user every afternoon use a standard SAP ERP transaction and collect all the outbound deliveries and create for the collectively the appropriate IDOCs. We suppose the mass processing will create some problems.
    Thanks in advance

    hi,
    one simple advice (less then one day) would be to change
    >Generally it is an IDOC - > XI -> RFC case.
    either to:
    Generally it is an IDOC - > XI -> ABAP proxy case.
    or if this is not abap proxy enabled receiver system to:
    Generally it is an IDOC - > XI -> IDOC case.
    if you already have a working RFC then changing it to and IDOC
    and changing a mapping is less then one day and in both cases
    abap proxy and IDOC you will have a clear status and LOG!
    (as both IDOCs and ABAP proxies are persistent in receiver system)
    this is the best possible option I believe and nothing will get lost for sure
    Regards,
    Michal Krawczyk
    http://mypigenie.com XI/PI FAQ

  • IDoc - XI - RFC Issues

    Trying to set up an IDoc->XI->RFC Scenario.  Am able to receive the IDoc into XI but are having issues getting this to the other system via RFC.
    Status in Monitor for Processed XML Messages (SXMB_MONI) is "Recorded for Outbound Processing".  When I "display" the specifics I see the Inbound Message was processed fine but the Receiver Grouping is set to "Recorded for Outbound Processing". 
    I check SMQ2 and I can see my data in the status "Transaction Recorded".  I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".
    Also in SMQR the scheduler status is "Inactive".  Not sure if that is relevant or not.
    Hoping someone has seen this and can help me get whatever I'm missing set up!
    Thanks!

    Hi,
    <i>Also in SMQR the scheduler status is "Inactive". Not sure if that is relevant or not.</i>
    This status is OK.
    <i>I check SMQ2 and I can see my data in the status "Transaction Recorded". I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".</i>
    >> in SMQ2 what is the status ? Is it running/sysfail etc ?
    If it is SYSFAIL, then double click on that and check the exact error.
    Else, you can go to SMQR or SXMB_ADM->Manage Queues->QRFC monitor->  .. then go to specified Queue name(whatever having the problem) and deregister it. Then go to SMQ2 and execute/activate the Queue . This time you will not get the info "Queue is registered...." Then go again SMQR and Re-reigister it.
    For more ~
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Re: Recorded for Outbound Processing
    Hope this helps,
    Regards,
    Moorthy

  • Idoc - XI - RFC

    Dear ll
    i developing a scenario in Pi
    i.e  IDOC - XI - RFC
    my doubt is , when i am creating the Interface determination ,  we have to specify the Interface mapping r Not . If S y. because i am not created any MT for My scenario.becasue i am using std Idoc & RFC which i know already
    in the Interface determination , i am directly put a a inbound interface as my RFC name . When i try to Put IM . Its disabled , Not able to Put.even i have a  Message interface (1 for inbound & another is for outbound) .
    my doubt is is it really required a IM in Interface determination ..

    Hi Irfan,
    You don't need to create any DT,MT or MI for RFC and IDocs. But still you need to define a mapping  (between IDoc and RFC)
    and which should be incorporated in the Interface mapping. have you provided the correct sap standard namespaces for IDoc and rfc while creating your interface determination?
    While createin the Interface determination have dragged the indbound and outbound interface as IDOc / RFC ?
    please check this hope it should resolve the issue.
    Thanks
    Sugata B Majumder

  • Idoc to rfc

    Hello,
               Could you tell me that, can we do the IDOC to RFC scenario in XI.

    Hi Ravi,
    First of all i dont think there will be any requirement for IDOc to R/3.This scenario doesnot make any sense i mean why u need to send a IDoc from R/3 system to again R/3 system using R/3 adapter.
    See IDoc and RFC are the two adapters which r used when we need to communicate XI with any other SAP system .
    But u can make one sceanrio like this
    Idoc ->XI->FIle->XI-RFC
    i mean u will send a Idoc from R/3  into File  ...again u r picking the file and sending in to some table of R/3.
    Regards
    'BILL

Maybe you are looking for

  • Adding a document to XMLTYPE table with schema

    Hi all: I am doing an example to create a table with a registered schema associated (in Oracle9ir2), and i am trying to insert a document that fits to schema into the table. The example is very simple: I have the following schema: <schema xmlns="http

  • File Upload UI Element

    Hi,   We are using the Standard Webdynpro File upload element in the screens. When the user clicks on the 'Browse' button the File Selector popuop is thrown using which the user can select the file.   Can we have on specific type of files be displaye

  • GRC 10.0: Access Request Creation - LDAP user advanced search not working

    Dear Experts, We are implementing SAP GRC Access Control and we have an issue in Access Request Creation. If we put the user name in "User" field and press intro, the user details are updated, but if we want to make an "Advanced search" the user is n

  • TM could not complete the backup

    Yesterday I took my iMac and Time Capsule to the Genius Bar and were able to get my initial full back completed. This morning I got "TM could not complete the backup" in a popup window with "The backup disk image /Volumes/Data-1/{username}'s iMac.spa

  • Importing Records to iTunes

    How do I import my record collection into iTunes? I have one of those gadget boxes that takes the audio from the turntable and ports to the audio in on my PC. I don't want to have to take the intermediate step of creating a CD and then importing that