Debugging of idocs

hi,
         can anyone tell me how to debug  idocs step by step with tcodes.
regards,
srinu.

Hi srinu
<b>If IDoc is in status 51, it means it was properly delivered to R/3. So you can now set a break-point in the respective IDoc handling function and reprocess the IDoc with BD87 (or report: RBDINPUT). Then debug the IDoc function and find where the error message is issued.
If you un-check the option field "background processing," you will get more options and in the menu there is a selection that allows you to throw the function into batch input dialog mode. If you choose "process foreground from error," it will stop on the screen where the error happens. Then you will know which field is not supplied properly by XI.</b>
<b><i>IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc with BD87 you can have a breakpoint in the function and it will stop. For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).</i></b>
Rewards if helpfull
Regards
Pavan

Similar Messages

  • I looking for a transaction for debug the IDOCS

    Hello friends,
    I looking for a transaction that allowed me to debug the IDOC´s when the direction is only 1 (Outbound),  for ex. for IDOC´s has direction 2 (Inbound) I used the WE19 transaction, and to choose the "Inbound Function Module" button and I take the "Call in debug mode" checkbox,
    Can you tell me if exist another program for this?
    Thanks in advance,
    David

    Hi,
    IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc with BD87 you can have a breakpoint in the function and it will stop. For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
    For your knowledge [reference1|Re: How to debug Idoc; [reference2|Outbound IDoc debug;.
    May it helps you.
    Regards,
    DS.

  • How to debug Outbound IDoc

    Hi Friends,
    I want to know how to debug Outbound IDoc .
    is there is any tool for debugging outbound idocs
    Thanks,
    Bhaskar.

    hi
    Go to tcode WE19. Give idoc number press F8. You will get next screen. There you have push button in tool bar called "INBOUND FUNCTION MOUDLE". Click on it. You will get one pop-up screen.
    There give function module name and tick the check box called " Call in debugging mode" and select radio button called "In foreground". Then press ok. It will take you to debugging mode.
    Reward if it dose.
    Thanks
    Siva kumar

  • Can we debug a idoc?

    can we debug a idoc?

    Hi,
    You can debug "idoc processing" in the transaction WE19.
    Provide the appropriate inbound function module and execute in debugging mode..
    1>Provide idoc number
    2>Execute
    3>For inbound
    Select the option inbound function module
    provide inbound function module
    select call in debugging mode
    For Outbound
    select the option Standard outbound processing
    This process you can perform for the failed idocs..to change any particular data to successfully process them
    Thank you

  • How to debug outbound Idoc function module for invoice

    I have to debug the outbound IDOC function module and UserExit for invoice message type INVOIC, process code SD09, function module is IDOC_OUTPUT_INVOIC and user exit for the function module LVEDF001.
    I tried putting the break point in function module IDOC_OUTPUT_INVOIC and recreate the IDOC using WE19 but it creates the idoc but does not stop at the break point. I have also tried generation of idoc through VF02. It again creates the idoc but does not stop at the function module.
    Please let me know if I am missing any thing and not doing it right.
    Appreciate your help.
    Rohit

    Hi Ali,
        I faced the same problem. Thing is the break point is not getting triggered when i ran tha IDOC through WE19.
    What i have done is i created a project for my exit in CMOD and kept some junk code in the exit and executed it through BD21. Then the Break point got triggered. See if it works.
    Regards,
    Uday S.

  • Debugging inbound idoc user exit

    Hi all,
    I have a client who wishes to do some data validation when creating an inbound idoc.  We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
    The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
    Cheers,
    Stephen

    go thru the below information.
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    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
    You need to excahnge data between systems you need an interface as medium for data transfer.
    IDoc also treat one of the interface options for data transfer.
    Check this link
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    IDOC Debugging:
    1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
    2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
    For outbound function module debugging you can use the following:
    1) RBDMIDOC - for master IDocs configured via change pointers.
    2) RSNASTED - for transaction IDocs with output/message control.
    3) RSEOUT00 - For IDoc whose status is "to be processed".

  • Debugging outbound idocs

    Hi,
    Can anyone suggest me how to debug the outbound idocs like in case we19 for inbound.
    i am creating an idoc for ORDERS message type with process code ME10. i need to debug to know if data is populating in segments correctly.
    shylesh

    Hi Sailesh,
    You can set break point at FM <b>IDOC_OUTPUT_ORDERS</b> and go through the code step by step.
    Also you can check customer function for any custom enhancement related to populating/deleting IDoc segment within the above FM.
    Hope this will help.
    Regards,
    Ferry Lianto

  • How debug outbound idoc

    hi ,
    How i can set break point  in FM , for outbound idoc .
    Thanks,
    Sridhar
    Moderator Message: Please search before posting
    Edited by: kishan P on Sep 6, 2010 7:19 PM

    hi ,
    How i can set break point  in FM , for outbound idoc .
    Thanks,
    Sridhar
    Moderator Message: Please search before posting
    Edited by: kishan P on Sep 6, 2010 7:19 PM

  • How to debugging the idocs and who to downloads the idocs

    please send this exact answer
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on May 17, 2011 11:45 AM

    Shravanthi:
    Define a 'On UPDATE' trigger for the table
    ex.
    CREATE OR REPLACE TRIGGER my_trigger
    before update on my_table
    for each row
    begin
    :new.ts_column := sysdate;
    :new.user_id_column := v('APP_USER');
    end;
    Varad
    Edited by: varad acharya on Nov 6, 2008 10:19 AM - Added the :new ref

  • Debugging IDOCs

    Hello -
    How do I debug an IDOC ?   The transaction codes I know for processing IDOCs are:
    WE02,  BD87 and WE19
    I am trying to debug an IDOC which is creating a credit memo request in VA01.
    Thank you,
    LP

    LCPicker,
    There is an easy way, go to WE19, put the Idoc number and hit F8 then choose for e.g inbound function module, set the function(you can find it at WE64), checked "CAll in debug mode" and if you want check foreground mode.
    regards,
    Alexandre

  • OUTBOUND IDOC DEBUGGING

    I have Output type  defined for the application V3
    i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
    This output type is defined for edi processing.
    Now the problem is when invoice is created and this
    outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code  and find the function module that is running in the background for collection of data of invoice and
    filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
    Help me out i will be waiting for the response.

    Hi,
    You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
    Let me know if you need further help.
    Thanks,
    Eric

  • IDOC scenario Debugging

    Hi,
       I want to debug the IDOC senarios(Both File to Idoc and Idoc to file ).. for this.. from where can we start.. and what are the things we need to check.. how can we debug the scenarios...
    i mean.. just give me the descriptive steps..
    Thanks
    BABU

    HI,
    1. Start with checking the status in sm58 of sender R/3
    Follow the steps
    No message in found in XI in IDOC to FILE scenario
    2. Try deleating the IDoc from IDX2 and refiring the same.
    3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
    In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
    4. Monitor the SM58 in R/3 for IDOC status.
    5. Trouble shooting file to IDOC and IDOC to file
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    Refer below links for indepth troubleshooting
    File to IDOC, trouble shooting
    Refer below steps
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    IDOC to File steps to be followed please verify your scenario with it
    R3 system.
    1. Create SM 59 RFC destination to XI,.
    2. We21 - Create port to XI.
    3. We 20 -- Maintain Partner Profile for the outbound Idoc.
    XI SLD
    1. Create technical system for R3 system
    2. Create Business System for the Client of the R3 system.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    These are the required steps for IDoc to File scenario...
    In R3 (i.e., your IDES system)...
    RFC dest to XI (sm59) - any name
    Logical system (bd54) - any name
    Port to XI (we21) - any name
    Partner profile for the logical system (we20) - use Logical system name created in bd54
    In XI...
    RFC dest to R3 (sm59) -
    Port to R3 (idx1) -
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3 with Logical system name as r3 sys.
    In we19
    and give in control record as
    Sender : Port ; Partner
    Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
    see the below links
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    Thanks
    Swarup
    Edited by: Swarup Sawant on Feb 9, 2008 1:32 PM

  • How to Debug Idoc Adapter from XI to R/3

    Hi,
    Can any one please help in debugging the Idoc adapter from XI to R/3.
    Here is the my problem - XI to R/3 idocs have been created correctly but the service relation ship is created incorrectly.
    i.e. When XI creates inbound idoc into R/3, it is also linking some other non relevant idoc which is created 2 years back as a outbound idoc reference to that original idoc.
    And this outbound idoc is coming to XI and the same can be seen in IDX5(Table - IDXRCVPOR) for that message.
    I tried to see various parameters on idoc_inbound_asynchronus FM and when I execute this FM in R/3, idocs are being created correctly and service relation ship is also correct.
    I tried to debug the RFC by using dialog user in the idoc adapter - IDX_OUTBOUND_XMB. For this we forced to fail the message at the adapter level and then manually restarted in SXI_MONI so that it will stop in debug mode in IDX_OUTBOUND_XMB.. But it didn't.
    Can any one help on this ?
    Thanks in Advance..
    Nagarjuna

    If my understanding is correct, your inbound function module processing the IDoc is triggering another IDoc to be sent back to PI? If so, then have you checked the distribution model? If you want to supress it you can try removing it as the outbound Idoc for the logical system in we20 (Partner Profiles)?

  • How to Debug IDOC posting

    Hi,
       Could anyone please advise how to debug an IDOC posting. I am new to ABAP.
    regards,
    Munavar Basha A.K.

    Hi,
    1)Use tcode we19 , enter your idoc no and click on the inbound function module push button then check call in debugging mode to debug.
    or
    1. Go to BD87
    2. make a right click at the IDoc and choose restrict and process.
    3. delete the check at the bottom(Background Processing)
    4. Go ahead
    5. edit -> process -> Foreground at Error
    Thanks Hope this will be Helpful
    Thanks
    Kalyan

  • How to do IDOC debugging for both inbound and outbound

    Hi
    can somebody please help me on how to debug the idoc both inbound and outbound in SAP PI.
    Regards
    Blue

    Hi,
    Yes, i have checked but did not get any satisfactory answer.
    here is the solution:
    Inbound:
    We19, Give the idoc #,
    click on the inbound functional module and select the radio button in the fore ground
    check the check box call in debug mode, this will enter in the functional module debugging.
    Outbound:
    Check BD73, give the idoc # and execute
    or
    RSNASTED program and set the breakpoint there
    is this correct, i have not tested/ checked yet.
    Regards
    Blue

Maybe you are looking for

  • Re: Reason Of Rejection field in the Sales Order screen in IC Web client

    Hi guys WE have implemented CRM 6.0 & ECC 6.0 Our call center guys login to IC Webclient to place Standard Orders in the CRM system which replicates to ECC. Now as most of us know that the Order cannot be rejected once a Delivery Document is created

  • Webdynpro appln Url parameter "sap-wd-client= XML client "

    Hi all,     I am a beginner in Webdynpro application development. I have a query on the usuage of Url parameter "sap-wd-client=XmlClient" in webdynpro application.       When i set the Application parameter property of webdynpro iview in portal as "s

  • Problems with iMac retina 5K (artifacts, glitches and etc.)

    Hello dear Apple. I have bought new iMac with retina 5K display and I have found lot of problem with it. It was December 2014 when I got my first iMac. And after then I have found few real problems with it. The first problem is I can't open high reso

  • Master Style page changing/deleting images

    Hi all - This has been a reoccurring problem for quite some time. I have several master style pages in my project; each one is laid out the same with my company's logo and a module name in a header, then a copyright in the footer. While working, I'll

  • Filter sap.ui.table.Table by an external string

    Hi all, I'd like to display in the table only rows whose specified column contains a particular external string, i.e. not something that the user types into the column menu. I though Table.filter(column, string) would be the right method to call, but