About filters in IDOCS

Hi all,
How  to set new filter to send perticular data to only one person having function type 59.
Thanks,
Shiva

Hi,
BD95 - Create the New Entry of ALE Object Type and give the table name and field name for which you need to set the filter
BD59 - enter the message type
And then give the ALE Object type which was created throug BD95 and give the segment name for the same field you want to filter the values.
BD64 - Create the new distribution model and once you add the message type then create the filter and while creating the filter, the field which you have configured using BD95 AND BD59 will appear in the filtering criteria. Then you can set the value for the field.
Reg the user authorization you need to write the code in the User Exit for the Outbound function module.
Hope it helps.
Reward if it is useful.
Thanks,
Srinivas

Similar Messages

  • Filters in IDOC ?

    what is a filter ? why are u using this filters in IDOC's ?plzzzzzzzzz explain me with one exmple ?

    Hello Akash
    You will find good examples within the SAP online documentation:
    <a href="http://help.sap.com/saphelp_46c/helpdata/en/18/22b800773211d396b20004ac96334b/frameset.htm">Basic Concepts of ALE Technology</a>
    <b>Filtering</b>
    The transmission can be controlled data-specifically through filters. Filters are conditions that message types and BAPIs have to meet in order to be distributed by ALE outbound processing.
    <b>Example</b>
    A customer uses a centralized inventory management system and several accounting systems. If stocks change in company code 0001, accounting data is sent to accounting system 01; if they change in company code 0002, accounting data is sent to accounting system 02.
    Regards
      Uwe

  • Would you like to send me some Document about ALE EDI IDOC

    hi experts:
    I am learning about ALE,EDI,IDOC,would you like to send me some Document about ALE EDI IDOC?which can include the details of Steps,best it can have the Pictures,thanks a lot.

    Hi Niel,
    There may be a problem with the definition of the rule to delete the characteristic. If you go to transaction RSMRT
    and use the 'check' option to check the rule you created are there any errors for the check?
    If not when you get the error message that you mention is there any additional error messages created in sm21
    or dumps in ST22?
    If not there may be a problem with the consistency of the cube if you goto RSRV>All Elementary tests>Transaction data
    and run these tests for the cubes are there any error messages? If yes please try to use the repair function in RSRV
    to correct any errors.
    If none of the above helps you should delete the run you created, make a dummy change to the cube (e.g add a '.'
    to the description of the cube, save the change and then activate the cube, please then try and create the
    remodelling rule again.
    Best Regards,
    Des.

  • About Filters

    Hi
    can any one explain about FILTERS in reporting......what is this and let me know its importence by giving examples please  iam getting very confusing with this.
    As we know we can create WAD  reports for queries, info providers and query views.. i know first two but i dont know About query viewu2026 what exactly this and how to create itu2026.
    What is work booku2026u2026u2026
    We have the process in the general services EXOR what is this and I am unable to understand its usefulness with the explanation in the books.
    regards......priya
    Edited by: priya kaluri on Dec 1, 2008 12:25 AM

    Hi Priya,
    Sorry for late reply....
    Actually in Process chain its based on Event processing. When there is step then it should raise the Successful (Green) & unsuccesful (Red).
    Now the requirement is depend on to the logic or steps you want to load data in your Data targets.
    For your more understanding share ur id so I can send you document.
    But for simpler understanding, replace 1 with G (For successful event) & 0 with R (For unsuccessful event)  in AND, OR, EXOR Table.
    Please let me know your more questions.
    Regards,
    Mahesh

  • Segment filtering in IDoc -File scenario

    Hello
    I am currently working on IDoc to File scenario where I am distributing changes in materials to legacy systems. For the same I am using MATMAS IDoc and planning to use change pointers to track the changes of the same.
    The scenario is working fine but from fine-tuning perspective can i filter some of the segments from IDoc because I am hardly using few data from MATMAS IDoc.I checked the distribution model in R3 but i guess it allows us to define data filters.
    Thanks in advance.
    Regards
    Rajeev

    hi,
    thanks for the reply but i found one transaction in SAP BD56 where I guess we can specify segments to be filtered.
    Regards
    Rajeev

  • About proxies and IDOC

    Hi all,
    Can any one explain me or give me a lnk to blog on how do we merge more than two IDOC to one file.
    And also blogs,good links about proxies (ABAP).
    Cheers,
    Karthick

    Hi,
    check this links
    XI: Debug your inbound ABAP Proxy implementation  ---Debug your inbound ABAP Proxy implementation
    Choose the Right Adapter to integrate with SAP systems
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1387--- [original link is broken] [original link is broken] [original link is broken] Client Proxy
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1457--- [original link is broken] [original link is broken] [original link is broken] Server Proxy
    ABAP Proxy Runtime
    Programming with Client and Server Proxies
    Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure
    Various multi-mappings and Optimizing their Implementation in Integration Processes (BPM) in XI.
    IDOCs (Multiple Types) Collection in BPM
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2034Regards [original link is broken] [original link is broken] [original link is broken]
    regards
    vasu

  • Question about filtered index

    I am looking over database for the SQL objects having SET QUOTED_IDENTIFIER OFF and SET ANSI_NULLS OFF
    For filtered index both needs to be ON so what about the objects that dont have quoted_identifier and ansi_nulls code line?
    do i need to add SET QUOTED_IDENTIFIER ON and SET ANSI_NULLS ON for those objects as well?

    Following article solved my question
    http://blogs.msdn.com/b/sqlprogrammability/archive/2009/06/29/interesting-issue-with-filtered-indexes.aspx
    I tried creating proc without quoted_identifier and ansi_nulls code line and proc still executes

  • Puzzled about filters for phones.

    I am very puzzled about the filters for the phones.   I have three cordless phones so made sure I had three filters to use with my phones for the broadband.
    I put one filter on the incoming phone line with the cordless with the ansaphone ..... and then plugged the other two cordless into the electric supply and realised I couldn;t put a filter on them .... so was stumped.   But the broadband is staying connected when calls are being answered.    
    I thought I had to have a filter on each phone being used.    Sorry if its a bit garbled... but I'm trying to explain it the best way I can.
    Di
    Solved!
    Go to Solution.

    very simple really as they are cordless phones and as they operate wirelessly only the main phone unit is connected to the phone line the other two phones do not need filters
    If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

  • About FILE to IDOC scenario

    Hi Experts,
    i need some help for doing file to idoc scenario.
    1. what are the configurations we must do while doing this scenario?
    2. How to communicate with Legacy system to sap system?
    3. How to create the business and logical systems for SAP systems in SLD?
    4. How to define parameters in communcation in ID?
    5. what work shold be done using SM59 and WE20? and specify the steps please?
    6. finally if u having word file please send from the creation of logical system for sap system?
    thanx.

    Go thru below mentioned links.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34
    once you go thru them you will find answers for questions.
    thanks,
    Venkat

  • Repost : confused about filters

    Hi,
    Sorry to repost. I am looking for some information. We have all kinds of documents. PDF, DOC, EXCEL , HTML etc. First three are more important ofcourse.
    How can I create an index that would work with atleast the above three formats.
    Do I need to install additional filter ?
    Could someone please show me an example if possible.
    Regards
    Vissu

    Just use the INSO filter. You don't need to install the filters.
    Please check the following section in the reference manual for more information: http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/text.920/a96518/cdatadic.htm#36089

  • Question about inbound PEXR2002 IDOC

    Hi,
      How would you handle multiple deductions (2 different deductions with different reason codes) for the same invoice? What are the segments that are going to be used for this purpose?
    Thanks,
    Nile.

    Hi ,
    check this link...it gives more info
    file to idoc scenario
    sekhar

  • About using FIDCCP02 IDoc type for FB50

    Hi Friends,
           I'm trying to design an Inbound interface using Idoc type FIDCCP02 with MSG type FIDCC1. During testing this IDoc with Tcode WE19 it got processed very well but in tcode WE05 it is showing status as 51 i.e. Accounting transaction not permitted for posting in FI/CO.
          Please Help me out to resolve this problem. Thanks in advance.
    Thanks and Regards,
    Vivek K.

    There are two things that needs to be done to achive this
    1. Maintain Cross Company code information through transaction 'SALE'>>Modelling and Implementation Business Process>>Cross Application settings >> Global Organizational Units >>Cross-System Company Codes
    2. Maintain suitable value for GLVOR in segment E1FIKPF. For eg: RFBU. You can take FI functional consultant help.
    This problem gets resolved. Though I am giving you this reply late and I know that I may not get points but whenever anybody searches for this thread they get the answer.
    Regards,
    Suraj Kumar P

  • About HR Inbound IDOC

    Hi Gurus.
    I'm new on IDOC subject.
    I'm trying to test INBOUND HR IDOC.
    I'm looking someone who tested or used on HR but i think it's not commom on that module.
    I have on system an existing IDOC but everytime i try to test there is an error msg:
    "Application document not posted" Number 51. It gives me something wrong with T777D table.
    I appreciate if you could share your ideas and experience with me.
    Regards.

    Hi Mauricio
    You may use PFAL transaction, to send data from one HR server to another.
    Just give the object id and the receiver where you want to send the data, then login the receiver system
    have a look on the idic using we02.
    Or open tcode we02, give direction as 2(inbound), all idocs will be displayed, check the various parts of idoc over there
    let me know issues if any
    Regards
    Manu

  • About Orders05 outbound Idoc.

    Hi,
    I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
    I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
    I am unable to understand how do I populate the fields.
    Could you please help me.
    Thanks,
    Sandeep.

    HI,
    see the below steps you will completely understand the processing outbound..
    2.1 Outbound Interface
    PROCESS DIAGRAM
    Outbound Interface
    1. Analyse Hierarchy Levels
    2. Create New segment
    3. Create New IDoc Type
    4. Create New Message Type
    5. Link Message with IDoc Type
    6.  Create an entry in EDP13 via transactions WE20 and BD64
    7. Populate the Custom IDoc via ABAP Program
    7b Error Handling
    7c. Send Status Email
    8. Test the Population of the Custom IDoc
    <b>Step 1 – Analyse Hierarchy Levels:</b>
    Analyse the data relationships being processed in the interface.  Define the appropriate hierarchical Parent-to-Child relationships. 
    Navigate to transaction code WEDI
    Transaction WEDI displays the IDOC main menu.  This allows navigation around the various development and control areas to create a customised IDOC.
    <b>Step 2 – Create a new segment:</b>
    via wedi : Development - IDOC Segments or Transaction code WE31.
    •     Enter segment name and click on Create.
    &#61662;     The name of the segment type must start with Z1 , and have a maximum of eight characters.
    •     Enter description and enter the relevant field names and data elements.
    &#61662;     The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
    •     Save the segment and enter Person Responsible and Processing Person .
    •     Go to Edit and Set Release.
    •     Repeat this procedure for each new Segment in the IDOC.
    <b>Step 3 – Create a new IDOC Type</b>
    via wedi Development - IDOC Types or Transaction WE30.
    •     Enter segment name (starting with Z), click on Basic Type and then Create. 
    •     Create as new, enter Person Responsible and Processing Person  and enter description.
    •     On ‘Create Basic Type’ screen decide where segments should be inserted and go to Edit/Create Segment.
    •     Complete relevant fields in the Maintain Attributes screen:
    •     From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
    •     The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
    •     The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
    •     Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a ‘Child’.
    •     When IDOC created return to initial screen.  Go to Edit and Set Release.
    •     Go to Transaction WE60 to view the IDoc Type you have created.
    <b>Step 4 – Create new Message Type</b>
    via wedi Development - Message Types or Transaction WE81.
    •     Display/Change and click on New Entries
    •     Create a new Message Type and Save.
    Step <b>5 – Link Message Type to IDOC Type</b>
    via wedi Development - IDOC Type/Message or Transaction WE82.
    •     Display/Change and then click on New Entries.
    •     Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
    <b>Step 6 – Create an entry in EDP13 via transactions WE20 and BD64.</b>
    The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
    •     WE20 – Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
    •     BD64 – Create a Model View, Enter Sender and Receiver Ports, Attach Message Type.  Go to ‘Environment’ on Menu and click on Generate Partner Profiles and generate (not save) profile.
    <b>Step 7 – Populate the custom IDOC via ABAP Program</b>
    See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
    •     Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
    •     The control record is filled into a structure like EDIDC.  The message type and the Idoc type for the Idoc must be populated into the eddic structure.
    - PERFORM populate_Control_structure USING  c_mestyp
                                                c_SEGMENT_type1.
    •     The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
    - PERFORM transfer_Parent_data_to_seg.
    •     The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
    - PERFORM master_idoc_distribute.
    •     NOTE:  This function module is only called for stand alone programs and Shared Master Data programs (SMD).   It is not called when using extensions or output determination.
    •     The ALE Layer handles the sending of the IDOC to the receiving system.
    •     Error Handling (see  Step 7b).
    •     Commit work.
    Project Specific
    <b>Step 7b – Error Handling</b>•     Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
    •     Declare a structure of type ‘MCMAILOBJ’ for sending instructions.
    •     Enter values for the internal table based on structure ‘MCMAILOBJ’
    •     For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module  ‘MC_SEND_MAIL’.
    •     Enter values in the following parameters: -
    MS_MAIL_SENDMODE         =  ‘B’ (Batch Mode)
    MS_MAIL_TITLE                    =  'Mail Title'
    MS_MAIL_DESCRIPTION     =  ‘Error description’ (e.g. MATNR not given)
    MS_MAIL_RECEIVER           =  ‘Name of Receiver’ (To be determined)
    MS_MAIL_EXPRESS             =  ‘E’ (Express Delivery)
    MS_MAIL_DLINAME            = Leave Blank
    MS_MAIL_LANGU                =  'E'  (Language)
    MS_MAIL_FUNKOBJ_NAME  = Leave Blank
    TABLES
               MS_MAIL_CONT           =  I_MCMAILOBJ
    Note:
    It has to be determined separately for each interface how these errors and mail notifications are to be grouped – dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
    When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
    <b>Step 7c – Send status mail</b>
    •     Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
    •     Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
    •     Use function Module ‘MC_SEND_MAIL’ to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
    <b>Step 8 – Test the population of the custom IDOC</b>
    via wedi IDoc - Display IDoc or Transaction WE02.
    •     Enter your message type and execute.
    •     Status should be green, double click on one of the Idocs you have created to view its contents.
    •     If a problem has occurred click on Status which will give you a description of the error.
    •     Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
    •     Click on each individual segment and view the content to check that the correct data has been read.
    •     If you have UNIX access by using AL11 you can view the file that you have created.
    Note:
    For some interfaces it may be valid to send an empty file to SAP.  This empty file is converted to the custom IDOC format expected by SAP.  This custom IDOC will contain dummy information.  In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
    rewards if useful
    regards,
    nazeer

  • About ale and idocs

    hi all
    i was asked in an interview when we will go for creation of an idoc.pls provide me some real time situaution when we use these idocs

    HI,
    IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND THE PROCESS OF IDOCS BEING SENT BETWEEN TWO SYSTEMS AND IT COULD HELP YOU IF U GO FOR INTERVIEWS.
    Application Linking and Enabling (ALE)
    In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
    For our purpose we have two clients
    namely Client 100 and Client 200.
    System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
    Distribution of Material Master Data Between two Systems
    1) SETUP LOGICAL SYSTEM:  (Note: Do Not Create This Step)
    To do this follow the following steps
    Execute SALE Transaction Code
    On The Screen Click on Sending and Receiving Systems.
    Then Click on Logical Systems.
    Then Click Defining Logical Systems.
    Click New Entries Button
    (E.g. (LG100 sending system)
    (LG200 receiving system))
    Enter two logical system names and their description.
    Save
    Comeback to SALE Transaction Code screen.
    2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
    LG100 assign to client 100
    LG200 assign to client 200
    To do this, do the following.
    Click Assigning Client to Logical System.
    Ignore the message that comes up on the screen.
    Select client 100
    Click details button on the toolbar icon or press F2.
    In the logical system box, enter LG100.
    Click on the save Icon
    Click the back button.
    Now select client 200.
    Click details icon or press f2.
    In logical Systems box, enter LG200.
    Save
    Back.
    Comeback to SALE Transaction Code screen.
    3) Maintain RFC Destination: (TR.CODE:SM59)
    (Note: Do Not Create This Step)
    Click Create Button on the Screen
    On the Screen  Maintain RFC Destination i.e LG200.
    Enter LG200 in RFC destination box.
    Connection type is  3
    Give a description for the RFC destination.
    Maintain Technical Settings on Details on Technical Settings tab
    Target Host as : SAPKDC (NOTE: Save it as a Host Name)
    Maintain Logon Details on Logon/Security tab.
    Language: EN.
    User:      MMUSER200 (This is the logon for dist.)
    Client :      200
    Password:      MM1234.
    Save.
    Click on create to do the above process for Client 200 in
    The client 200 system.
    4) Maintain  Distribution  Model.(BD64). (ABAPer role starts here)
    Execute Maintain distribution model directly for
    creating the model.
    Click on change mode button on App tool bar of the Screen.
    Create Model View pushbutton on App tool bar of the Screen.
    A pop screen will appear in which you specify
    Short text as Distribution for MM Data.
    Enter Technical Name as LGMODEL.
    Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
    A popup screen will appear in which you specify
    Model View as       LGMODEL.
    Sender as           LG100.
    Receiver as      LG200.
    Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
    A popup screen will appear in which you specify
    Model View as       LGMODEL.
    Sender as           LG200.
    Receiver as      LG100.
    SAVE.
    On the same screen goto Menubar and select Environment.
    And then select Generate Partner Profiles , then execute it.
    On the Screen specify the Logical System as LG200.
    Then execute the screen.
    Click back.
    Again On the same screen goto Menubar and select EDIT.
    Again select Model View and then select Distribute.
    ****LOGIN  to client 200.
    Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
    And then select Generate Partner Profiles , then execute it.
    On the Screen specify the Model View as LGMODEL
    And  Specify the Logical System as LG100.
    Then execute the screen.
    Click back.
    *******Switch back to client 100 Session.
    5) Create Material using MM03 Tr.Code.
    Enter the material name as LGMATERIAL
    Industry sector as      Mechanical Engineering
    Material Type as           Finished Products.
    And then Click on Data Pushbutton on the App tool bar.
    Select views.
    In the select views box for materials check basic data 1 AND 2.
    Click enter icon.
    In the next screen that you get
    Give the text of the material as NEW MATERIAL.
    Base unit of measure as KG.
    Gross Weight as 200.
    Net Weight as 100.
    Weight Unit as KG.
    In the description area language (E) and material description.
    Click Save.
    Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
    6) Execute BD10 to transfer the material in which you specify
    the material as LGMATERIAL and
    message type as MATMAS (client100).
    Then a Screen will be displayed in which it shows that
    1 Master Idoc Generated .. Enter
    1 Communication Idoc Generated..Enter.
    *******LOGIN to Client 200.
    7) Execute BD11 to get the material in which you specify
    the material  as LGMATERIAL and
    message type as MATMAS (client200).
    8) Execute Tr.code MM03 and give the material as LGMATERIAL
    and see that the material is displayed as it was in Client 100.
    If not follow these steps.
    9) Execute Tr.code WE19( for rectification of errors in client200).
    Specify the Existing Idoc Number and Executes it .
    A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
    10) Execute Tr.code MM03 and give the material as LGMATERIAL
    and see that the material is displayed as it was in Client 100.
    Now the Material is correctly displayed in Client 200.
    11) Monitoring of IDOCS.
    Transaction Codes:
    IDOC Display of Status: WE 05.
    IDOC Date and Time:   WE07.

Maybe you are looking for