SAP ABAP IMG Activity ISH_SERVICE_FORM01 (Form-Based Service Entry)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NPAS (Package) Application development patient accounting system
IMG Activity
ID ISH_SERVICE_FORM01 Form-Based Service Entry  
Transaction Code S_KK4_96000369   IS-H IMG 
Created on 20000825    
Customizing Attributes ISH_SERVICE_FORM01A   IS-H: Attribute Form-Based Service Entry 
Customizing Activity ISH_SERVICE_FORM01P   IS-H: Maintenance Object Form-Based Service Entry 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_SERVICE_FORM01    

Use

You can define forms for entering services. Forms are an easy way for end users to enter services via a simple mouse-click.

  • You can design your own forms.
  • You can define as many forms as you need for each institution.
  • You can use service forms in case-related service entry (transaction code NL10) and in patient admission (transaction code NV2000).
  • You access forms
    • Via a form folder in the service entry work environment
    • Via an admission variant tab page in patient admission.

Activities

To create a new form, proceed as follows:

  1. Start be entering a form name and a description, then specify the institution and the application (admission or service entry) in which you want to use the form.
  2. Enter the name of the HTML form from the Business Document Service (BDS) and the name of the relevant pictures from the BDS in the HTML form group box, then save these settings.
  3. Create an implementation of the Business Add-In (BAdI) ISH_SERVICEFORM. For this purpose, refer in particular to the delivered example implementation. After activating the BAdI, you can use the form.

Bear the following points in mind when creating an HTML form:

  • You can use an editor of your choice to create an HTML form.
  • You can use any element recognized by Internet Explorer 5.0 and upwards when creating your form.
  • You can use up to six different pictures for the design of your HTML form.
  • Store both the HTML file and the pictures in the BDS. The HTML files for HTML forms must be stored in class ISH_HTML and the pictures in class ISH_PICTURES in the BDS. For further information about using the BDS, refer to the F1 Help for the fields for the HTML file and the pictures.
  • To ensure the seamless integration of HTML forms, you should adhere to the following conventions when creating your form:
    • Form data must be transferred to the SAP System using the post method. Use the following syntax: <form name="myForm" method="post" action="SAPEVENT:SUBMIT_FORM_AS_POST_METHOD">.
    • To send the filled-in HTML form (i.e. to transmit it to the SAP System ), you can either include a submit button in the form, or trigger a submit with every mouse click using the JScript event onClick. The second option has the advantage that the end user does not have to click on any extra pushbuttons when the form is filled in. The JScript for a submit triggered by onClick could look something like this:
      function submit_service()
      {
      document.myForm.submit();
      }
    • Pictures must have the same names ("object keys") as in the BDS; they must be written entirely in uppercase:
      • <img src="PICTURE1.GIF">.
    • You cannot decomment JScript coding (this is common practice to avoid problems with browsers that are not JScript enabled). As a rule, you should avoid using comments in JScript source code, since these can result in JScript runtime errors.
    • Note that the font size depends on the browser settings unless you have specified it in HTML coding.
    • An example for an HTML form is contained in the BDS. It is located in the class ISH_HTML, class type OT with object key ISH_SERVICE_FORM_EXAMPLE_01.

Example

Requirements

Standard settings

Recommendation

Activities

Further notes

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TNSRVF01 V - View SM30  
History
Last changed by/on SAP  20000825 
SAP Release Created in 462