Idoc filetering ,segment filtering

hi ,
can any one send me the document to create idoc filtering thru bd53,and segment filtering thru bd56.
[email protected]
points are assured!
thanks
Ganesh
Message was edited by:
        ganesh ram

Hai,
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 Partner / Receiver Partner.
Data Filtering:
Data filtering can be done in distribution model 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.
Pls go thru this Link,
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm

Similar Messages

  • EDI IDoc Segment Filtering Transactions

    Hi All,
    Is there any transaction for EDI IDoc segment filtering where partner profile is set up with partner type as 'customer' or 'vendor' (and not partner type as 'logical system' where ALE IDoc segment filtering transactions BD59 & BD64 can be used) ?
    Thanks !

    Thanks Lokeshwari.
    Actually, a perticular field in an IDoc segment needs to be filtered. e.g. I dont want to send idocs with a perticular item category for ORDERS05 IDoc.
    Is there any transaction to fulfill the same ?

  • What is Data filtering and Segment filtering in ALE/IDOCs

    Hi sap gurus
    what is Data filtering and Segment filtering in ALE/IDOCs

    Hi,
    Filtering at the IDoc Level
    Identify the filter object (BD59)
    Modify the distribution model
    Segment Filtering
    specify the segments to be filtered (BD56)
    The Reduced IDoc Type
    Analyze the data.
    Reduce the IDoc type (BD53)
    Thanks and regards.

  • Idoc Segment Filtering error.

    Hi,
    I have a scenario of IDOC to IDOC Scenario, in which i have to filter some segments based on the field value.
    Ex: DESADV09 is my input and output IDOC
    Having segment as below:
    Segment -
    E1EDK08
    Fields----
    Field1
    Fields----
    Field2
    Segment----
    E1EDP07
    Fields----
    Field3
    Fields----
    Field4
    Segment----
    E1EDP08
    Segment----
    E1EDP09
    Fields----
    Field5
    Fields----
    Field6
    Segment----
    ZCODE
    Segment----
    ZQUALIFIER
    Fields----
    Field7
    Fields----
    Field8
    Here using the qualifiter segment we need to filter the E1EDP09 segments,
    The condition is If Field7 == Network, and Field8 == GSM, I need all the E1EDP09 segments.
    The E1EDP09 segments has to filter with the above condition.
    For example if 10 E1EDP09 segments comes in the input IDOC if i have only 6 satisfed with the above condition I need only those 6 E1EDP09 segments at the output.
    I have tried with all the options but i couldn't fiter that, can anyone throw some light on this..
    Thanks,
    --Sai

    Hello,
    You can try using the mapping below:
    For E1EDP09 mapping:
    Field8 --> concat --> equalsS:GSMNetwork --> ifWithoutElse --> removeContext --> E1EDP09
    Field7 --> /                                           /
    E1EDP09 --------------------------------------------> /
    The code above will pass the number of E1EDP09 that satisfies your condition.
    For the E1EDP09 child nodes e.g /DESADV01/IDOC/E1EDK08/E1EDP07/E1EDP09/HLNUM:
    Field8 --> concat --> equalsS:GSMNetwork -----------------> ifWithoutElse --> removeContext --> E1EDP09
    Field7 --> /                                                        /
    HLNUM --> MapWithDefault --> removeContext --> formatByExample --> /
    E1EDP09 -------------------------------------------> /
    The code above will pass all the E1EDP09 fields that satisfies your condition
    Hope this helps,

  • What's the difference between segment filtering and reduced message type

    Hi gurus,
    What's the difference between segment filtering and reduced message type? It seems they have the same functionality: Reduce the segment while idoc is generated.
    Thanks in advance.

    Hi,
    BD53 is for IDoc Reduction.
    this allows you to create a reduced message based upon a standard message type.If you want see mandatory fields. go to T-coe BD53 and give one standard messege type name and eg: matmas
    there mandatory fields will be in Green color..
    And BD56- This transaction is used to filter out segments of IDocs for combination of sender and receiver. This is usefull in scenarios where a standard IDoc with many segments is used but the receiving partner is only interested in some of the segments
    the table related to this transation is TBD20
      please go through below blog you have an idea abt that,
    http://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
    http://saptotal.com/IDoc%20Segment%20Filtering.html
    regards,
    ganesh.

  • Determine Partner number based on IDoc Data Segments

    Are there any user exits or BADI, which can be used to determine Control record parameters (Partner), based on IDoc Data segments? This is for an Inbound IDoc, into ECC.
    I found EXIT_SAPLEDI1_001. But, this has only control record. It is used to determine control record parameters, by using control record only.
    Thanks,
    Juwin

    Dear Juwin,
    Could you please provide some info. about what you are trying to achieve by trying to determine the partner dynamically?
    If the scenario is something like 'Partner A should get data related to only plant 1000 and Partner B should get data related to only plant 2000', you could use filters in the Distribution model to achieve this.
    BR,
    Aashrith

  • Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

    Hi all,
    I have extended the the standard IDOC MATMAS05  classification view with structure as below-
    E1MARAM                        Master material general data (MARA)--->Mandatory segment
         Z1KLART                        KLART --->Extended chaild to E1MARAM
             Z1CLASS                        segment for class --->Extended chaild to Z1KLART
             Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
         E1MARA1                        Additional Fields for E1MARAM
         E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to                                                                               
    E1MARAM )
    I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
    Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
    This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
    Please help to resolve the issue.
    Thank you.
    Edited by: sanu debu on Apr 30, 2009 11:25 AM
    Edited by: sanu debu on Apr 30, 2009 11:31 AM

    Hi,
       You cannot add an segment in the middle of other segments.
    YOu have to add any segment at the last.
    If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
    In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
    Regards,
    Ravi Kanth Talagana

  • EDI: Syntax error in IDoc (mandatory segment missing)

    HI all,
    Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
    Status ID - E0
    Message No - 072
    Status of the IDoc - 26
    Please help me how to solve this issue?
    Thanks,
    Srini

    Hi,
    This error normally comes up when the sequence of segments has been disturbed.
    For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
    You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
    Thanks,
    Manish

  • Creating own IDOC with segments

    can any one let me know the steps to create <b>Z</b> IDOC and segments required  for  it.
    and also the sample code (program) to poplulate the data into those segemnts from a (excel/csv file )or tables.
    Thanks..

    hi Aday,
    There are basically two types of IDOCs.
    Basic IDOCs
    Extended IDOCs
    Idoc Components
    Basic Idoc
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extension Idoc
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDoc
    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.
    Create IDOC Type
    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
    Regards,
    Naveen

  • Idocs n segments

    what are the types of idocs and wat are the types of segments?

    Hi Sunil,
       Idoc type are Two ( Tcode we30 )
    1. Basic Idoc ( Ex: cremas, debmas,matmas, orders01, And Some Z Idocs        (Which you will create )
    2. Extended Idoc : Theses are Generally created when you want to do any modification or enhancements to the existing basic idocs.
    Segments are two
       Parent And Child will attached to parent
    They may be Customised or Standard
    Thanks
    manju
    If you are plesed, Reward points

  • 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

  • Condition Based Segment Filtering in ALE

    Hi Guys,
    I have a scenario in which I have to filter the segments from the IDoc depending upon a condition.
    For example if VKORG = ' 0001' then delete the segment.
    I understand that it should be possible through ABAP code.
    I am looking for some direct configuration steps in order to do the same.
    Can anybody help?
    Regards,
    Prakash Pandey

    Hi,
    As per my understanding, we do filer based value the Idocs (in T.code: bd64)and not the segments.
    Segments are filtered based on message type sender and receiver details and not the value based.
    Also deleting here is content deletion from the segment in communication.
    Regards
    Satya

  • Need IDOC and segment for mappping the sales order number

    Hi,
    we need the IDOC name and segment for mapping the sales order number created by oracle in sap for transaction VA01.
    Whether the sales order number created by Oracle can be used to create the sales order in sap using the idoc ACC_SALES_ORDER01?
    . If we can do,then what is the segment and field for the sales order number in the idoc ?
    Please reply asap it's very urgent
    Thanks
    Edited by: suresh kumar nandhagopal on May 16, 2008 12:07 PM

    Hi,
    IDOC for sales order is ORDERS05. Segment E1EDKA1, for field go to SE11 and enter E1EDKA1 to find field for sales order.
    Cheers.
    ...Reward if useful.

  • IDOC Missing Segment Field

    Hi,
    Some of my outbound IDOC's are missing a particular field in the Segment.....
    This is probably because that Segment field don't have any value and hence missing from IDOC.
    What can be the possible approach for Solving this probelm?

    Hi Abhishek,
    Can you please get the solution for such issue?
    I didnt aware of Enhancement Spot...
    Looking for your reply..
    Regards,
    Raghu
    Edited by: Raghu Raman on Jan 5, 2009 1:27 PM

  • XI IDOC missing segment definition in type E1LFM1M

    Hi experts,
    we have recently upgraded our ERP system to NW 702 EH5. As aresult a new segment definition was added to our segment type E1LFM1M ( segment def. E2LFM1M007). The problem we are havign is that our XI system is still running on NW700 and it doesnt have this segment defintion. Since the upgrade we are getting an error in transaction RFC complaining about the new segment definition E2LFM1M007 everytime we try to send a vendor from ERP to SUS using BD14. Is there a way we can deactivate the new segment definition E2LFM1M007 in segment type E1LFM1M?
    Thanks,
    Abdul.

    Hi Abdul,
    Actually it does not matter what are your systems' versions, PI can always handle an IDoc properly. All you need to do is perform the following steps in your PI system:
    1. Log on to ABAP stack, go to t-code idx2, find your ECC system and that particular IDoc (I believe this will be CREMAS) and delete its metadata.
    2. Log on to Enterprise Services Repository, find your SWCV where the IDoc definition was loaded, and load it again from your ECC system, then activate the change.
    3. If necessary, also adjust the message mapping to use/not use the new segment. Activate your changes.
    Once you have these steps completed, you are ready to retest your scenario and say goodbye to the error.
    Hope this helps,
    Grzegorz

Maybe you are looking for