Ansicht
Dokumentation

SIMG_ISHMED_CAPDOCNE - Copy a Cardiological Sample Document

Fill RESBD Structure from EBP Component Structure   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

You wish to create your own cardiological document using a sample document. The required work steps are described below.

1. Copy sample document category
   Start transaction N2T5 or the report RN2UTDT_COPY (navigation via RN2PMD_DISTRIBUTION) and enter the institution, document category name and version of the sample document as a template. Fill in the institution, document category name and version of the new document category to be created (pay attention to namespace!).
   Execute the "Copy" function.
   In the popup dialog for the options, click the checkboxes
   "With Abstract Design" and
   "WIth Element List" and use the pushbutton for "OK".
   You branch to the abstract design. Execute the "Preset" function.
   Change at least the name of the master element, the tab and all tab pages.
   This is necessary so that you can then insert or remove elements within these structures. You can optionally change the names of other structures and elements, however, we recommend this, as otherwise the structure (the abstract design) of your documents will be changed when newer versions of the sample documents are imported. This is particularly necessary in multiple structures, if you intend to insert new elements. The simplest way to give elements a new name is to use the Find/Replace function to exchange the namespace N8CA for a namespace which is not in use in your system.
   You may not and cannot change individual elements, structures, and tables, but should replace these later with your own documentation elements.
   Execute a check. If no errors are reported, you can save the new document category. This creates the abstract design and the new documentation elements. The element list of the new document category is saved immediately after the copy procedure.
   The alias names of the documentation elements are retained. In the Package field, enter a transportable development class of your installation (you should make all changes in the development system and then transport the entire document category into downstream systems without regenerating). As a result this is then created with the correct development class when objects are subsequently generated.
2. Copy data include and include with user exits
   Starttransaction N2T8, enter the institution, document category name and the version of the sample document and display the document category.
   On the next screen use one of the "Detail" pushbuttons.
   Select the "User Exits" tab page and determine the name of the data include, the include with the user exists and the name of your own form.
   Copy the data include and the include with the user exits into your namespace (e.g. using SE80 or Create and Copy/Paste) and activate them.
3. Complete new document category definition
1. Enter the name of the new includes into your new document category definition on the "User Exits" tab page.
   
   - Call the element list.
2. On the "Dialog Positions" and "Dialog - Tab Page Assignments" tab pages, check whether the tab page assignment of the fields of the patient and case data, parameters and request details match those in the sample docuument.
3. On the "Dialog Function" tab page check whether the OK code and form routine were correctly transferred for active objects (e.g. checkboxes, radio buttons).
4. Select the "User Exits Interface (Gen-2)" tab page.
   Check whether all entries in the "Grouping" column match those in the sample document category (and supplement if necessary).
   You can change both alias names of the master element and the tab.
5. For some business partners (findings creator, supervisor) the external data module ISHMVMAST2 is used.
   First you must make all fields of this GP structure must be made visible, so that the program logic takes these into account during generation. After the first generation you can make the Abbreviation, Rank, and Specialist Area fields invisible once again.
6. In your document category find the fields of the "link element" type and supplement the customizing in the same way as the entry in the sample document.
   If necessary enter the newly selected name.
7. If you have copied the cardiac catheter findings, you should observe the necessary entries for the data transfer from the cardiac catheter log .
4. Table processing
   Start table processing.
   For each table you execute the "Save" and "Activate" functions.
   Some tables contain value fields and corresponding unit fields. These tables cannot be activated here. Use transaction SE11 to create the same value/unit relationship as the sample document and activate the table. If you again call table processing in the document category definition, all tables should be complete and activated.
5. Layout check
1. Make a layout check and ensure that the layout corresponds to that of the sample document (with exception of the business partner fields). For some fields you may need to toggle between a list box and a radio button (graphic indicator).
6. Generate dialog application
1. Generate the (complete) program.
7. Copy and adapt forms for printing
1. Start transaction SE71.
   Execute the "Utilities> Copy from Client" action.
   Enter the form name and the source client of your form entered in the sample document and the new form name as the destination in your namespace. In the new form you must adapt the name of the source, which still contains the table names of the sample document e.g. in N2CA02-ISHMPATNAM(*) you must replace the string N2CA02 with the table name valid in your document category. The printout of the cardiac catheter findingsis implemented in the sample document using a smart form. To do this you should aso copy the form N8CAHKB_1 using the Smartforms transaction into your namespace, in order to be able to adapt the letter header. The new name must match that of the new SAPscript form. You can optionally copy the other smart forms (N8CAHKB_2 to N8CAHKB_5).
8. Enter form name in document category
1. Enter the new form name in your document category definition on the "User Exits" tab page as your own form. You should also refer to the notes on printing the
   cardiac catheter findings.
9. Test new document
1. You should now test your new document category, before you incorporate your desired changes. To do this you require a suitable environment (service facility, service performed for a patient).
10. Incorporate desired changes
1. In case of changes you should first edit the abstract design of your document category. You cannot change supplied structures and tables! This means that you may need to create new superordinate documentation elements. If the abstract design is being processed, update your document category definition. Select the (proposed) options:
   - Transfer parameters from the element list
   - Recalculate dialog positions: No
   You then edit the definite layout to adapt the layout.

Change BDS objects for the interactive HTML viewer

In some documents HTML objects are used as graphical input helps
. These use functionalities of the PMD link element 'HTML Viewer'. These can merge HTML code and background graphics, which are separately stored in so-called Business Document Service, at runtime and also transfer data from HTML forms into the PMD or send data from the PMD into the HTML form, if the 'Activate Form Processing' indicator is set. The addressing of this functionality is controlled by user exits in the PMD. The supplied BDS objects for HTML documents in cardiology are entered as follows "BDS:N2DSCA...." in the customizing of the link objects of the HTML viewer type. In order to use HTML documents here, several steps are necessary: - In table BDS_LOCL two special entries are necessary. You can check these using the transaction SBDSV1 . The entries 'ISHMED_HTML' and 'ISHMED_PICTURES' must exist. - Use transaction OAC2 to determine whether a document type is active for HTML (e.g. BDS_HTMLT) and another document type for images (e.g. BDS_IMAGE) ([S]tatus column). - Start transaction OAOR and select documents of the class ISHMED_HTML or ISHMED_PICTURES, class type 'OT'. Select the supplied document which you wish to replace and export this locally. Edit it locally and execute the transaction again, but this time assign a name (e.g. Z-namespace) for your new BDS object. By double-clicking on a document type (HTML or image) you can start the upload. If your BDS object should also be available in target systems, select the individual object with the checkbox and initiate a manual transport by button. (Note: BDS objects are transported using their UID, which is changed at each new upload. A transport must always be created, if the BDS object has been changed in the meantime). - If you wish to use your own HTML documents, you must also enhance the table TN2LINKHTMLBDS by adding corresponding entries, to guarantee an assignment between the HTML document and background graphic (maintenance e.g. using the transaction SM30). Enter the ID of the BDS object for the HTML code in the OBJID field and up to 9 IDs for BDS codes of graphics, which should be displayed within this HTML code, in the fields PIC1 to PIC9. In the code itself you must enter these codes for the graphics at the position where a reference to the graphic should be (e.g. within an img tag). At runtime the system searches the predescribed table of code and the ID of the BDS graphic object is replaced by a functioning reference. These entries must also be transported manually.

1. Transport your own document categories
1. Once you have completed all adaptation work you should use report RN2UTDTS3 to transport your document categories. Even if you previously entered the package, you will probably not have entered all objects in transport requests, you must at least also transport the function group of the PMD. If necessary, delete the resulting transport requests (e.g. table definition) and create a transport including function group and tables.

General Material Data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 11727 Date: 20240607 Time: 133921     sap01-206 ( 258 ms )