...

If you forget to create your site dir and configure it, your app will not build. This is a common problem. If mortar 00.xx or insidemit are not checked out and set up properply, your app will not build. See iJAG FAQ on checking out an Eclipse project for instructions on setting up your site dir and configuring itdeploying locally.

To run your app, just right click the project and select Run As > Run on Server. The first time you do this it will ask you to pick which server to run on. If you check the checkbox at the bottom it won't ask you this again. By default, it will go to the action EntryAction.do. If project(s) other than the one you've chosen to run are run also, it is because they were added to your server earlier. You can remove them from the server by going to the Servers window, expanding the Oracle server, selecting the project you wish to remove, right clicking and selecting Remove.

...

The documentation for implementing search help is in the search help tag library (searchhelp.tld) originating from our skeleton (see Demo Application above). The

Most of the time the ABAP developer should will need to add code to the generic SAP RFC for RFC, Z_CA_SEARCH_HELP, to implement the specific search help that is needed. This RFC , Z_CA_SEARCH_HELP, is expecting:

• a key to be passed from the JSP  
• the field names that are going to be searched.

The where the first two or three characters of the key represent the business area (: EHS, FI, HR, MM - MM stands for Materials Management and is covered by the Logistics team). This RFC also requires the field names that are going to be searched. The ABAP developer must supply (materials management - Logistics Team). Ask the ABAP developer for the key and the field names. For instance, the key for the JV G/L Account Search Help is

Examples of keys and their field names:

• FI_JV_GL_ACCT
  • DESCRIPTION
  • GL
  • COMPANYCODE
• EHS_LIST_PERSON_BY_NAME
  • LAST
  • FIRST
• HR_COST_OBJECT
  • KSTRG
  • TEXT

 ABAP developers should use English for our keys & field names but we sometimes slip up and use the German abbreviations. KSTRG is the German abbreviation for Cost Objects.

<form-bean
name="SearchHelpParamsForm"
type="edu.mit.mortar.controller.data.SearchHelpParamsForm"/>
<form-bean
name="SearchHelpCriteriaForm"
type="edu.mit.mortar.controller.data.SearchHelpCriteriaForm"/> and the fields associated with this Search Help are DESCRIPTION, GL and COMPANYCODE.

Revision History

(latest on top)

...