SAP ABAP IMG Activity SIMG_ISHMED_RAD_BA10 (BAdI: Prefetching)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NORD (Package) R/3MED: Services processing EDV-G
IMG Activity
ID SIMG_ISHMED_RAD_BA10 BAdI: Prefetching  
Transaction Code S_KK4_96000616   IMG Activity: SIMG_ISHMED_RAD_BA10 
Created on 20020508    
Customizing Attributes SIMG_ISHMED_RAD_BA10   IS-H*MED RAD: BAdI: Prefetching Algorithm 
Customizing Activity SIMG_ISHMED_RAD_BA10   IS-H*MED RAD: BAdI: Prefetching Algorithm 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISHMED_PREFETCHING    

Use

This Business Add-In (BAdI) is used in the Radiology component. The ISHMED_PREFETCHING Business Add-In is used for customer-specific Prefetching customization. The BAdI is called when a study document is created and determines which documents (studies) should be forwarded to the recipient.

Standard settings

The BAdI is not active as standard.

This BAdI cannot be used multiple times and is also not filter-dependent.

The active standard BAdI implements prefetching according to the routing rules. Documents on the patient whose document category, version and status is entered in the routing rule, are forwarded.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Further notes

Prefetching is initiated when radiological objects are created. A prefetch order is created in the N1PREFETCHSPOOL table. The prefetch order indicates that documents for this patient/service will be forwarded.

  • If the scheduled performance date of the entered service is the same as the current date, the system will immediately perform the prefetching and process the prefetch order.
  • If the scheduled performance date is in the future, the system will process the prefetch order with the first prefetching on the day of performance. Alternatively, you could develop a program which processes prefetch orders during the night.

Routing rules are created in the TN1ROUTING table using maintenance dialog box. A routing rule determines which documents (document category, document version, document status) for a requested service should be routed, regardless of the requesting and performing

OU. For the requesting OU you may enter a departmental OU, a nursing OU or a wildcard "*". In the routing rule, the source and target of the routing order are determined by the AE title. If no document status is entered in the routing rule, the system will use the Release status as the default.

See also

Interface Documentation

Method Documentation

Default Implementation

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20020508 
SAP Release Created in 463B