IDOC filter at Field / Segment Level

Hi
Can you please tell me how to set an IDOC filter at field and segment level in short?
Thanks

Hi,
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 detail information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Similar Messages

  • Search customize field/segment in IDoc

    Hi,
    I've have requirement to delete a customize field ZMKOL that belong a append structure Yxxxx in VBAP. By doing that, i need to scan through all the existing IDoc interfaces that using ZMKOL.
    Right now, i do have a list of inbound and outbound interfaces that using in my company.  So could you please advise what is the best way for me to identify field ZMKOL is using in which interface?
    Please comment.

    Since ZMKOL is a custom field, to include it in an IDoc someone had to create a custom segment and extend the IDoc. The custom segments are maintained in WE31. Find out which custom segments have this field and then you'll be able to find which IDocs include these segments.
    Also just do a 'where used' on the field in SE11 - this will most likely find the programs where the field is being populated for the IDocs.
    Do a search on IDoc extension if you need more info.

  • Change description of value fields and segment level chars in prod system

    Hi
    1 . We would like to change the description of some value fields.... We would like to know whether the change has to be carried out directly in the production client by opening the client using SCC4 or we should change the description in development client and transport it to production...
    We are afraid that if we transport the operating concern again from dev to production system using KE3I, it may affect the transaction data which is already lying in the production system
    2. We would also like to create and include some new fields as Segment level characteristics in COPA... What is the proces for the same and whether the same has to be done directly in production or transported from dev client
    3. Some value fields which were copied in our operating concern from a template of Air line Industry, are not suitable to oour business. So we are trying to change their description.. But SAP does not allow to change the description of thes value fields..
    Only those value fields which were created by us starting from VV***, can be changed.. Description of those delivered from the template, cant be changed. What is the process of doing the same
    Regards
    Ajay Maheshwari

    Hi
    When the Operating concern was copied from Airline Industry, many standard chars which are not applicable to Airline Industry were not copied.... For eg: Material group 1 to 5... These are std fields of Mat master which normally exist in Operating concern when I used to create it manually.... Many other chars reqd by the business are not available
    Someone else copied it using Airline template and many reqd chars are not available at all... I have the option of creating User defined chars for it and write a derivation rule to populate it... 
    Though COPA is active, my client does not use it as of now in ECC 5.0.. They would like to use it post ECC 6.0.. So, I thought its better to start afresh than carrying forward the mistakes done by someone else.. They are OK with this model, but I wanted to be sure what all issues can be faced due to this
    Regards
    Ajay Maheshwari

  • What is the mean IDDAT field of ORDRSP idoc's E1EDP01/E1EDP03 segment

    Hi experts,
    I'm trying to use ORDRSP idoc to map to a target structure.
    I need to know mean of IDDAT field of ORDRSP idoc's E1EDP01/E1EDP03 segment.
    For example if IDDAT = 024  what does it mean?
    Is there a list shows means of fields with different values?
    Thanks.

    Hi,
    the segment E1EDP03 is a  "qualified" segment.
    The possible values of a qualifier field are defined in DDIC as domain value range (fixed values or by value table)  of the corresponding data element.
    In your case, the qualifier (data element) IDDAT has the domain DATID assigned with the T54C5 value table.
    So the possible values are contained in the value table T54C5.
    Using the maintenance transaction SM30 itu2019s possible change the value list; for this reason check in your system the meaning of the qualifier IDDAT = u2018024u2019.
    Regards,
    Andrea

  • Views Status at MARA general info segment level

    Hi all,
    Please guide me how to maintain Views Status at MARA general info segment level.I am extending standard MATMAS IDOC for my own fields.
    Thank you.

    You actually need to run it with "check -access"; memuse and leaks won't help with the crash, which happens because of illegal memory access. Hopefully, "check -access" will help you to locate the bad guy, but that's not panacea either.
    To be precise:
    - start dbx
    $ dbx <your app>
    - issue
    (dbx) check -access
    (dbx) run
    and wait for dbx to stop and report suspicious memory access.

  • File to IDOC - multiple source fields to 1 field

    Hello,
    I implement scenario from file to IDOC.
    In source side I have 2 fields (in different levels) that I want to map to 1 field in the IDOC.
    Is it possible to do it? And how?
    Regards
    Elad

    Hello,
    The sorce file is xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <PLM_Out_MT>
       <Quotation/>
       <TransactionHeader>
          <TransDateTime/>
          <Sender/>
          <Receiver/>
       </TransactionHeader>
       <QuotationHeader>
          <DocTyp/>
          <ContractNo/>
          <PurcNo/>
          <PurcDat/>
          <ValToDate/>
          <GenHeadText/>
          <PlmUser/>
       </QuotationHeader>
       <QuotationLines>
          <QuotationLine>
             <ItemNum/>
             <ItemCat/>
             <Quantity/>
             <ReqDelDate/>
             <OrgReqDate/>
             <Version/>
             <QuotationTexts>
                <QuotationText>
                   <TEXT_ID/>
                   <TEXT_LINE/>
                </QuotationText>
             </QuotationTexts>
          </QuotationLine>
       </QuotationLines>
    </PLM_Out_MT>
    The target is:
    <?xml version="1.0" encoding="UTF-8"?>
    <ZCUSTQUOT_WITH_REF01><IDOC BEGIN="1"><Z1ZCUSTQUOT_WITH_REF SEGMENT="1"><E1BPSDHD1 SEGMENT="1"><DOC_TYPE></DOC_TYPE><PURCH_DATE></PURCH_DATE><PP_SEARCH></PP_SEARCH><REF_DOC></REF_DOC></E1BPSDHD1><E1BPSDITM SEGMENT="1"><ITM_NUMBER></ITM_NUMBER><MATERIAL></MATERIAL></E1BPSDITM><E1BPSCHDL SEGMENT="1"><ITM_NUMBER></ITM_NUMBER><REQ_QTY></REQ_QTY></E1BPSCHDL><E1BPSDTEXT SEGMENT="1"><ITM_NUMBER></ITM_NUMBER><TEXT_ID></TEXT_ID><TEXT_LINE></TEXT_LINE></E1BPSDTEXT></Z1ZCUSTQUOT_WITH_REF></IDOC></ZCUSTQUOT_WITH_REF01>
    I need to map in the first time from <GenHeadText/> to  <TEXT_LINE> and in the second time from <TEXT_LINE/> to <TEXT_LINE>
    Is not possibole to use with concatenate  because i need all the time to map diffrebt field.
    Elad

  • IDOCType PORDCR101 : XML IDoc conversion: No known segments identified

    Hello all,
    I'm strugling with the mapping to the IDOC create puchase order PORDCR1.PORDCR101.
    The source structure for the moment is exactly the same as the target strcuture i.e. our IDOC.
    So I would not expect to much problems with this one.
    However, when sending the message we get the following error in SXI_MONITOR:
    <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    I also augmented the trace lvl to 3 and got the following in the Trace-part of TC SXI_MONITOR and
    suspect it starts to get wrong already in the beginning
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">---- Outbound IDoc-Adapter -
    </Trace>
      <Trace level="1" type="T">----
    </Trace>
    Trace level="1" type="T">Convert one IDoc</Trace> .
      <Trace level="2" type="T">Convert Control Record</Trace>
      <Trace level="2" type="T">Convert Data Records</Trace>
      <Trace level="3" type="T">Segment= E1BPMEPOHEADER</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADER</Trace>
      <Trace level="2" type="T">Ignore segment field: COMP_CODE</Trace>
      <Trace level="3" type="T">Segment= E1BPMEPOHEADERX</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADERX</Trace>
      <Trace level="3" type="T">Segment= E1BPMEPOADDRVENDOR</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E1BPMEPOADDRVENDOR
    I already found the four or so other threads on the SDN website about this error and in the mean-time tried them (delete and reload the structure with IDX2, set the begin and segment-attribute to 1, make sure that the segments-names self are also mappend) but to no avail.
    We just implemented two other IDOC's (DELVRY03 and WMMBID02) and they arrive at SAP without problmens.
    Hope you have form ideas to get me out of this one.
    Tnx and best regards.
    Bart.

    Hi Bart,
    We had a similar problem.... It took us 2 days to find out what the problem was... Nothing on SDN was helpfull so far... First we incremented the trace level of XI to see the debug messages... Then we saw that certain segments could not be identified and are ignored, others not...
    So further investigation in IDX2 to the specific IDoc with problems showed us a list with all used segments and their versions. Some segments had only 1, others had more versions....
    So we could identify the problem as a segment version problem. It seemed that our IDoc Communication Channel took not the most recent version. So we changed the "Segment Version" to the most recent one and the problem was solved!
    Please reward points if this was usefull to you...
    cheers!
    Pedro

  • Problem on idoc filter on - ALE

    Hi all,
    I'm working with ale, in particular with CLFMAS IDOC.
    In trx. BD64 we have a filter for this idoc.
    The problem is that I need to filter the field
    E10CLFM-objek with a select-option and no with single values?
    Is it possible?
    regards,
    enzo

    Hi,
    U can set the filter on field level in BD64.
    select the model view,click on NO FILTER SET option. you will get one modal screen... click on create button. then select the field..set the filter.
    Thanks
    Eswar

  • Map or filter a field

    Dears,
    I have a BAPI based interface and I need to map or filter one field of its IDoc.
    Is it possible to set a fixed value at BD64 transaction or any other transaction?
    The external system sends the field with valid values and I need to change them to zero.
    The BAPI used in the interface is standard so I was hoping that would be possible to change the value without changing the BAPI.
    Interface: HR-PDC
    Message Type: HRCC1UPTEVEN
    Basic Type: HRCC1UPTEVEN01
    Segment: E1BPCC1UPTEVEN
    BAPI: Object PTMgrExtPExpenses, method Insert (Function HR_CC1_TIMEEVENT_POST).
    Field: TIMEID_NO
    Thanks in advance!
    Best Regards.
    Anaer Lima

    "Not" is not yet implemented, but it is one of our top 10 requested features. So fear not, we'll be adding it. It's not the top item on the list, however, and it is not exactly inexpensive (as there are not just a few ways of using it). So I can not
    yet provide an estimate regarding when it will show up.
    But without a doubt, we won't be omitting no aspects of nothing except none of the features other than what we didn't implement for nobody. Not.
    - Chris

  • Simulair report for FBL5N and FBL1N for new general ledger on segment level

    We are working with segments in new G/L ledger. We want to run a open item report where we can combine customers and vendors by segment. The vendors and customers are linked in the master data. In the "old"  reports FBL5N and FBL1N you can do this but not by segment.I found the following report on segment level:
    - S_PCO_36000218 - Receivables: Segment
    - S_PCO_36000219 - Payables: Segment
    What I'm missing is to run 1 report for Customers and vendors. What I'm missing to is that there are only some fields available on line item level. (I like to have invoice number, documentype,.......)
    Is there a standard report for this in new genaral leger?
    Is it possible to ad additional field to th list viewer.

    What is this user license type?  All financial transactions need professional license.
    Thanks,
    Gordon

  • Error : idoc xml record in segment attribute instead of SEGMENT

    hi friends
    can any one solve my problem. In message mapping I mapped with a IDOC. In message mapping I Mapped all the fields. Still I am getting the error as "IDOC XML RECORD IN SEGMENT ATRIBUTE INSTEAD OF SEGMENT" I dont know about this error.
    can any one solve this problem please . I am doing this scenario since 5 days. help me..
    thanks in advance
    Vasu

    Hi Vasudeva,
    Can you pls provide little more details on the scenario ?
    Also at which place are you getting this error ?
    Assuming that you have created a message mapping for some source message to target IDoc message, here are some suggestions.
    1) Test the message mapping. (are you getting the error in testing itself ?)
    2) Apart from mandatory fields' mapping, are there any constants to be assigned to some IDoc fields ? Or any node to be disabled ? Or any such additional things...
    Regards,

  • Looping and Grouping at segment level

    Hi Friends,
    Scenario: JDBC to IDOC
    PRODID     ORDERNUM                          TRUCKNO     DISTANCE               BANS         ABANS     BBANS         CRMSID
    100001     230001          4578     540          10     00     10     IC1201
    100001     230001          4578     500          20     00     30     IC1201
    100001     230001          4578     520          20     00     40     IC1201
    100001     230001          4578     510          30     00     50     IC1201
    100001     230001          4578     570          40     00     60     IC1201
    100001     230001          4578     560          50     00     10     IC1201     
    100001     230001          4578     440          10     00     10     IC1203
    100001     230001          4578     540          60     00     80     IC1203
    100001     230001          4578     640          70     00     10     IC1203
    100001     230001          4578     940          40     00     10     IC1208
    100001     230001          4578     640          80     00     40     IC1208
    100001     230001          4578     840          00     00     10     IC1208
    100001     230001          4578     740          10     00     40     IC1205
    100001     230001          4578     540          70     00     10     IC1205
    Requirement:
    I want to create an IDOC basing upon CRMSID. So, am able to create it using this below logic.
    CRMSID --> RemoveContext --> SORT --> SplitByValue(ValueChange) --> CollapseContext --> IDOC
    So, there are 4 IDOC's to be generated. But, each IDoc will have multiple segments to be generated since the other fields (DISTANCE     BANS     ABANS     BBANS) data is changing.
    Can some one provide exact grouping and looping for this as got stuck with this.
    Thanks.
    Swarna.

    Hi Swarna,
    For individual fields   use the below logic... for example field BANS,
    formatByExample-splitByEachValue--TargetBANS
    FormatByExample:
    input1:resultOfSortByKey
    input2:CRMSIDremovecontext-sort--splitByValueChange
    SortByKey:
    input1:CRMSID--removecontext
    input2:SourceBANS--remove context
    Please try this logic and let me know on further clarification.
    Thanks
    Priyanka

  • Error in IDOC: XML IDoc conversion: No known segments identified

    Hi Team
    i am facing error in my scenario.  When we are testing my  interface, another  Interface is picking up the Messages and resulting into an error.
    There is no mapping involved in my scenario.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    please help me out
    thanx in advance

    Hi,
      Do The following:
    1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
    2) Have a look into this SAP Note- 742093
    3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
    4) If any field which is mandatory in the idoc must not be disabled...take care about it.
    Hope this will help you...
    Regds,
    Pinangshuk.

  • Split Single IDOC into Multiple IDOC's Based on Segment Type

    Hi Experts,
    I have a scenario IDOC to FILE ,  Split Single IDOC into Multiple IDOC's based on Segment Type
    Outbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Segment 2
    Segment 3
    Status Record
    I should get output like below
    Inbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 2
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 3
    Status Record
    Please suggest me step by step process to achieve this task.
    Thanks.

    Thanks a lot Harish for reply.
    I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
    Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

  • XML IDoc conversion: No known segments identified PPCC2PRETTICKET01

    Hello to everybody,
    I'm working with JDBC adapter to IDOC scenario with standard message PPCC2PRETTICKET01 and I found this message:
    IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME
    XML IDoc conversion: No known segments identified
    I've read previous thread and I've already try to Reimport the Idocs into Repository
    and Delete the Idoc metadata from the in Transaction IDX2 and reimport the same.
    I'm in SAP NetWeaver 2004s.
    Do you have another ideas?
    Many thanks

    Hi,
    I've filled up control record in message mapping, I tried with Apply C R but it doesn't work.
    I don't know how to disable EDI_DC40 in message mapping because the fields are red.
    I've filled up every segment field with a constant with the right segment name but nothing.
    This is the payload after the error but since the JDBC adapter in:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <PPCC2PRETTICKET01>
    - <IDOC BEGIN="1">
    - <EDI_DC40 SEGMENT="EDI_DC40">
      <TABNAM>EDI_DC40</TABNAM>
      <DIRECT>2</DIRECT>
      <IDOCTYP>PPCC2PRETTICKET01</IDOCTYP>
      <MESTYP>PPCC2PRETTICKET</MESTYP>
      <SNDPOR>SAPXI0</SNDPOR>
      <SNDPRT>LS</SNDPRT>
      <SNDPRN>XIDEV100</SNDPRN>
      <RCVPOR>SAPDEV</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>SYSDEV300</RCVPRN>
      </EDI_DC40>
      </IDOC>
      </PPCC2PRETTICKET01>
    Thank for more ideas.
    Fabrizio

Maybe you are looking for