...
- form is the project's controller > data > actionForm (ReportRequestForm) associated with the JSP with the magnifying glass icon
. - origaction is the project's controller > action > action (/RequestReport.do) that launched the JSP with the magnifying glass icon .
- key is the key (FI_SAFO_COST_OBJECT) you get from the ABAP developer.
- interactive ("y") indicates whether there are so many potential search results that you should first request search criteria ("y") If there are ? 50
or under no search criteria are necessary and mortar will take the end user directly to the search results ("n"). (? - Ask your UI person but generally if there are a max of 15 search result rows interactive should be "n". - title is what will appear (Cost Objects Title) after "Search for " on the search help criteria page.
- incrit crit are the names (KSTRG & TEXT) you get from the ABAP developer.
- incrit label are the labels (Input Cost Object & Input Description) for these names that will appear on the search help criteria page.
- incrit vfield are the actionForm field names (co & coDesc) that correspond to these names & labels.
- dispfield field are optional tags used to specify which columns will be displayed in the search results. If specified these columns must be the same names as the metadata column headings returned by the RFC. The ABAP developer can supply the names of these columns.
- outfield rfield are used to map the columns to the actionForm field names. These must be the same names as the metadata column headings returned by the RFC. The ABAP developer can supply the names of these columns.
- outfield dfield are the actionForm field names (co & coDesc) corresponding to the results columns.
Beyond having the ABAP developer modify Z_CA_SEARCH_HELP to incorporate your specific search help and making these changes to your JSP, there is nothing else that needs to be done to implement search help for any project that has been created using oas-skeleton and mortar 4.2x or higher
...