Capture Messages while Inbound processing of IDOC

Hi ,
I have a scenario where in i have to upload a file from application server using inbound IDOC. I am using the program RSEINB00 (using submit) for this, The idoc is getting posted successfully but i need to capture the messages in form of a log so that i can find out what all IDOC numbers are generated and how many of them. In case any error is there. I need to display a log of it.
Timely help in this regard will be appreciated and rewarded suitably.
Rgds,
Kewal
P.S. : Please suggest if there is any other method to process inbound IDOC (accept we19 TX)

Hi kewal ,
As per the scenario explained by you , I suggest you to do following steps
1.The program you are using is RSEINB00 , has a function mosule present named ' IDOC_ERROR_WORKFLOW_START'. This function module can gice yo the Error message log in case of Inboung IDOC processing fails.
2.You have two options , eithe you find out any user exit and atttach your own code to it or Complaetely cope that code into your z-program. Int he function module mentioned above , the export parameter  ' G_MESSAGE_FIELDS ' wud give you the error message , error status , error no etc.
3. So for the INbound IDOC status messages starts with 51-70 , so depending upon ur logic , read all those message into an internal table .Then transfer that to a file .So an error log can be genearated.
I hope this solves ur problem.
Regards.
Note: Reward if useful.

Similar Messages

  • User Exit  for Inbound Process - Changing IDOC control record

    Hi,
    I want to utilize the identification field (under details tab) of the IDOC Control Record. What is the suitable user exit for inbound process that i can use to change the IDOC control record?

    It's been a long time since I have done any IDOC processing. 
    Go to SE37 and enter the function module IDOC_INPUT_ORDERS.  Display the source code.  Search for "CALL CUSTOMER".  You should see several "CALL CUSTOMER-FUNCTION" lines.  These are enhancements where you can manipulate the IDOC data.  If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value.  Double-clicking on the number in quotes will bring you to an "EXIT_" function module.  A "ZX" INCLUDE program is referenced.  If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it.  The values passed into the function module are available in the INCLUDE.
    Ideally, you should create a project in transaction CMOD that references the chosen enhancement.  This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

  • Regarding Error Message while releasing Process Order

    Dear friends,
                              While releasing process order i m getting following error message.
    " Storage location in PUB(loc1) is not same as storage location (loc2)''.
    how to remove this error and release the order.
    Thanks & regards,
    Sandip Sonar

    Hi Sandip,
    The error message LP 099 'Stor. location in PUB X is not the same as prod.stor. location Y' is issued when the system finds  inconsistancy in your customizing of the couple storage location - Production supply area for your components in your process order.                                                                               
    The logic of the storage location determination is the following ...
    The issuing storage location is determined in three steps:                                                                               
    1. First, the issue storage location of the material to be issued   (MARC-LGPRO) is transferred to the material master from the  MRP    data if it is filled.                                                 
    2. The system overwrites this value with the issue storage location from the bill of material (RC29P-LGORT, STPO-LGORT) if it is     filled.                                                               
    3. If the operation to which the component is assigned in production  order contains a work center with supply area, the storage    location is transferred from this supply area (PVBE-LGORT).     However, this transfer is only carried out if storage location  data (MARD) is maintained for this storage location for the    material.                                                                               
    The logic of the supply area determination:                              
    Priority of supply area determination for WM staging is as follows :     
    1. Supply Area of Work Center               (highest priority)   If no supply area defined look to                                     
    2. Supply Area in item of Bill of material  (second priority)   If no supply area defined look to                                     
    3. Material Master View MRP2                (third priority)         If no supply area defined -> Error message LP 099                                                                               
    I hope this helps in sorting the issue.  
    Regards,
    Mauro

  • Plant missing in the inbound processing of IDOC ORDERS?

    Hi gurus,
    We are using IDOC ORDERS to create sales order in the inbound processing of R3 4.7 system, finally we found the sales order was created succesfully in VA03, but the plant(WERKS) and storage location(LGORT) couldn't be seen even the idoc has relevant value.
    Have you met this case? Any help will be appreciated. Thanks.

    Hi Himanshu,
    Thans for your reply. I gave the field  E1EDP01-WERKS the relevant value, but in VA03 we couldn't see the plant value when the idoc status was 53. When we debug it in WE19, we found the plant value probably wasn't assigned.
    Any ideas?

  • Inbound Processing of Idocs with status other than success

    Hi,
           I am new to ALE/Idocs. Can anyone  please let me know how can I process the Idocs which have the status other than 53.
    Thanks &  Regards,
    Indira

    Hi,
    In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
    - Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
    - Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
    - Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
    ~ Bineah

  • Inbound Processing of iDoc Status Message

    Silly me - I thought this would be simple ...
    I am currently changing our bank interface from a customized ABAP solution to use more standard SAP utilities (particularly iDocs).  I have the configuration set up to use the PAYEXT message type sending PEXR2002 iDocs to a file port.  Our bank is receiving these documents and is returning an iDoc status message containing the status of each payment iDoc that they received from us.
    My problem is that I can't figure out how to get these status iDocs to update the status of the corresponding PEXR2002 iDoc.
    I am trying to execute an RFC interface to apply these status messages to my system using the following OS command:
    D:\usr\sap\VPR\SYS\exe\uc\NTAMD64\startrfc.exe -3 -d RT2 -u xxxxxx -p xxxxxx -c 220 -h SPR32K36 -s 00 -F EDI_STATUS_INCOMING -E PORT=ZFI_INT003
    The error message that I receive when this is run is:
    RFC Call/Exception: SYSTEM_FAILURE
    Group             Error Group 104
    Key                RFC_ERROR_SYSTEM_FAILURE
    Message        Status record 1 is invalid (TABNAM: 'EDI_DC40')
    The port (ZFI_INT003) is the file port that is configured for the outbound file.  in WE20, this port has the "Status File" tab set to use the logical file name where the status file is being stored on the server.  the startrfc command is connecting to the SAP system and opening the status file.  I'm not sure where I'm going wrong here. 
    Can someone please help get me pointed in the right direction?  I've obviously missed something here.
    Thanks,
    Glen

    Hi,
    call function modules:
    EDI_DOCUMENT_OPEN_FOR_PROCESS
       EDI_DOCUMENT_STATUS_SET
       EDI_DOCUMENT_CLOSE_PROCESS
    kind regards,
    HP

  • Delivery date issue in the ASn inbound process via IDOC

    HI
    we want to start with ASN and we ´re already receiving IDOC´s
    DESADV Delvry03
    we are using Fm /SPE/IDOC_INPUT_DESADV1 and we have tried IDOC_INPUT_DESADV1 but teh reesult was the same.
    The segment E1EDT13 Qualifier 007/009/006  exist and we are able to create a inbound delivery. The problem we have is that we are not able to calculate the delivery date in the inbound delivery.
    The idea was that the vendors sends us the GI date (Qualifier 007) and our SAP calculates based on the plannend delivery time in the SA/PO the expected GR date 8what we see in MD04). But at the moment we only the creation date as delivery date.
    what do we miss?
    thanks for the help
    regards
    Alex

    Hi,
    Firstly, for DESADV processing delivery date field (LFDAT) is taken from qualifier '007' while goods issue is from '006'.
    As far as I understood you would like to get delivery date based on data from given delivery schedules. But note that inbound delivery items are not related specifically to delivery schedules. Instead, those are referenced to purchasing document items only. Therefore it is not exactly specified what delivery date should be selected for which inbound delivery.
    Alternative could be to perform scheduling for inbound deliveries based on route transit times etc.But in standard inbound delivery types are not available for SD scheduling and thus it is not directly available.
    If you need to get such functionality, you would need to use one of the DESADV processing u-exits available and include your own logic for lfdat calculations.
    Regards,
    Dominik Modrzejewski

  • Query:Convertion of PO to SO while inbound processing

    Helo all,
    I could successfully send PO data to  receiver server using IDOC.
    Now my requirement is  creation of SO at runtime when PO enters in system as idoc.
    I searched forums, but didnt got exact solution.
    Kindly guide.
    Thanks.
    Edited by: Sanjay_lnt on Nov 12, 2010 3:03 PM

    Hi Sanjay,
    Do you want to create one SO along with PO in PO inbound FM ??? I think you are using the standard FM. So you can do the coding to create the SO from in the inbound FM exit or Badi. Better if can create one wrapper FM to create the SO and call that FM in background task, so that it will not hamper the inbound FM performance.
    Also you can achieve the same functionality using output types. Just create one output types and attached with the EF in NACE and process it as special function.
    Thanks
    Subhankar

  • Inbound processing of idoc

    Hi,
    What are inbound posting modules ?
    If i use a ABAP program to read valuers from a flat file to a internal table and if i supply the internal table to a posting module will a Idoc be created?
    If not Please suggest how i could transfer the data in my internal table to a idoc.
    Regards,
    Vignesh

    Hi,
    Try using this FM:
    FM IDOC_INPUT_FIDCC2
    Reward Points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • Error In inbound Processing IDoc

    Dear All,
    I am facing error while inbound processing of IDoc
    In status record of IDoc following errors are occuring
    Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
    The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
    Status 51: Application Document not posted
    Log details :
    Error : Material Number should be filled.
    When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
    Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
    Thanks

    Hi Praveen,
    I checked the data in IDoc for this segment.
    It is ok as required in basic message type.
    e.g. the error says that mandetory segment E1MAKTM is missing.
    when i check basic type
    MSGFN : Function
    internal data type : CHAR
    Internal length : 000003 characters
    Position in segment : 001, Offset : 0063. external length : 000003
    SPRAS : Language Key
    internal data type : LANG
    Internal length : 000001 characters
    Position in segment : 002, Offset : 0066. external length : 000001
    MAKTX : Material Description (Short Text)
    internal data type : CHAR
    Internal length : 000040 characters
    Position in segment : 003, Offset : 0067. external length : 000040
    SPRAS_ISO : Language according to ISO 639
    internal data type : CHAR
    Internal length : 000002 characters
    Position in segment : 004, Offset : 0107. external length : 000002
    is information.
    and data in segment of IDoc is
    MSGFN     005
    SPRAS     E
    MAKTX     MANATA2000 TEST ALE
    SPRAS_ISO     EN
    which i think is ok.
    I have no clue why this syntax error is coming.
    Thanks
    Niketan

  • Idoc inbound processing? from non-sap system?

    Hi experts,
    I'm confused with some functions below:
    IDOC_INBOUND_SYNCHRONOUS
    INBOUND_IDOC_PROCESS
    IDOC_INBOUND_SINGLE
    IDOC_INBOUND_ASYNCHRONOUS
    can you tell me what are the differences? when to use them?
    for sap outbound processing, we can only call function master_idoc_distribute to generate idoc or use message control to trigger outbound idoc. no other options, correct?
    for sap inbound processing, if we use message control for automatical posting, we have process code which read  the inbound idoc file and do the sap posting. when to use those functions above?
    does the middlewares like seeburger, GIS call those functions to generate idocs at SAP side?
    in what scenarios can we use those functions? read directly non-sap file into sap internal table then call the functions to create inbound idoc? how about the posting? call inbound processe code function after the functions above?
    in case the interface between sap and legacy system is using above functions to build inbound idoc in sap and sap use process code for inbound posing, sap can monitor all inbound process using idoc, but how can the legacy system mornitor the interface?
    Thanks.
    Legend.
    Edited by: legend li on Dec 21, 2010 4:58 PM
    Edited by: legend li on Dec 21, 2010 5:40 PM

    Hi Christophe,
    Awesome!!!!!! it worked, You are the best.
    I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
    Can you kindly share the  IDoc data to be passed in...along with respective segments and fields:
    Segment                                                 Field
    E101CRMXIF_BUSTRANS     OBJECT_TASK         
    E101CRMXIF_BUSTRANS     PROCESS_TYPE
    E101CRMXIF_BUSTRANS     POSTING_DATE
    E101CRMXIF_PARTNER                          PARTNER_NO
    E101CRMXIF_PARTNER                RELATION_PARTNER_NO
    E101CRMXIF_ORGMAN         SALES_ORG
    E101CRMXIF_ORGMAN          DIS_CHANNEL
    E101CRMXIF_ORGMAN         DIVISION
    E101CRMXIF_SALES             PO_NUMBER_SOLD
    E101CRMXIF_SALES            YOUR_REF_SOLD
    E101CRMXIF_SALES            PO_NUMBER_SHIP
    E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
    E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
    E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
    E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
    E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
    E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
    E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
    E101CRMXIF_SCHEDLIN_I     ORDER_QTY
    Thanks a ton in advance .
    Vijay

  • What is the internal  processing for idocs

    Dear friends this is subbu working as a abap consultant.
    can any body explain the how idocs are transfered (inbound process and outbound process)

    1.Here out bound means sender.Inbound mens --receiver.
    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.
    There are two filtering in IDoc.
    Segment Filtering:
    Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
    Data Filtering:
    Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Please check this link for more information.
    http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
    Reward points..

  • Deletion marked material should give error message while creating proc ord

    Hello,
    i had marked the material for deletion through T-code MM06 & saved.
    Now when i'm creating the process order for the deleated material, System is giving only Warning message that " Material XXXX in plant XXXX has been marked for deletion."
    But my requirement is system shold give an ERROR message while creating Process Order for the deleted material.

    Yes Brahman is Right,
    Check the followig..
    Go to OMCQ and change the message category  to E- Error message instead of W- Waring message in Message no M7 127, but
    not  M7 121.
    and check it,
    Regards,
    Pavan idlur.

  • Monitoring inbound processing and Sync/ Async communication on PI7.11

    Hi All,
    I am new to PI. We have following two requirements to be done on PI 7.11
    1)     Monitoring inbound processing (Txn Code SWF_INB_MON)
    2)     Monitoring Sync/ Async communication (Txn Code SXMS_SAMON)
    Kindly let me know how should I proceed or what document should I follow or any scenario is to be configured.

    Hi,
        1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
               Note that you require administrator authorization for transaction SWF_INB_ADM
        2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail." 
         3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing. For monitoring individual messages click on "Display Message Packages".
    regards,
    ganesh.

  • Error message while creating an inbound delivery to generate an idoc

    hi,
    i am getting the following error message while creating an inbound delivery(vl31n) where the message has to be sent ot decentralized warehouse mangament using idoc .
    ." No recipient could be determined for object BUS2015 method SAVEREPLICA"
    Procedure for System Administration
    The system attempts to determine a recipient for object BUS2015 method SAVEREPLICA using the filter object types WHSE_NO. The system cannot determine a recipient. Define a filter object type WHSE_NO with a valid filter value for recipient determination for object BUS2015 method SAVEREPLICA.
    need help
    regards
    leo

    Inbound delivery is not part of Sales and Distribution. You might want to move your post to either the Logistics Materials Management (MM) forum or the Workflow forum.
    Also sometimes search for OSS notes by the message class and number helps.

Maybe you are looking for