SAP ABAP IMG Activity BADI ISH_CONTRACT_MA (BAdI: SG, CH: Calculate Contract Scheme Maximum)
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 BADI ISH_CONTRACT_MA BAdI: SG, CH: Calculate Contract Scheme Maximum  
Transaction Code S_KK4_96000537   IMG Activity: BADI ISH_CONTRACT_MA 
Created on 20020111    
Customizing Attributes BADI ISH_CONTRACT_MA   BAdI: SG, CH: Calculate Contract Scheme Maximum 
Customizing Activity BADI ISH_CONTRACT_MA   BAdI: SG, CH: Calculate Contract Scheme Maximum 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_CONTRACT_MAXIMUM    

Use

This Business Add-In (BAdI) lets you dynamically determine the maximum for a contract scheme during billing processes.

Besides the institution and the case number, the following information is available to you for this calculation:

  • I_NVVF: Insurance relationship
  • I_TN16: Contract scheme header data

    The IS-H System uses this data to determine the value for the field VARMAX, among other things.

    Meaning of the field VARMAX:

    The Calculation field (technical name TN16-VARMAX) is available to you for specifying a calculation rule in the header data of a contract scheme. The values you can select for this field must have already been defined in Customizing for IS-H under SG,CH: Settings for Contract Scheme Maximum. In the BAdI, you can use this field to create various rules.

  • I_RNPP10: Table containing the already processed insurance relationships each with the distributed amounts.
    • Example:
    • You have a case with three insurance relationships (IR):
      - A: rank 1
      - B: rank 5
      - C: rank 98
      When the BAdI is called for IR A, the table I_RNPP10 has still to be filled, since processing of IRs has not yet taken place.
      When the BAdI is called for IR B, the table contains one entry for IR A.
      When the BAdI is called for IR C, the table contains two entries, one for IR A, and the other for IR B.
  • E_MAXIMUM: Maximum that the IS-H System calculated for the specified contract scheme (header level). You can modify this value in the BAdI.
  • E_DAILY_MAX: Maximum per day/visit that the IS-H System calculated for the specified contract scheme (header level). You can modify this value in the BAdI.

Requirements

The system only calls the BAdI for contract schemes for which you have specified a value in the Calculation field (technical name TN16-VARMAX) in the contract scheme header data.

Standard settings

Activities

Example

Scenario:

The case has two insurance relationships. The first insurance relationship (basic insurance) covers 70 % of the costs of medical services. The supplementary insurance provides flat rate coverage of 20,000 SGD per case minus all costs borne by the basic insurance.

Implementation:

In IMG activity SG,CH: Settings for Contract Scheme Maximum in Customizing for IS-H, make an entry for your own rule. For example:

X1, short text: Reduced Maximum.

  1. You create a contract scheme with a Maximum per Case of SGD 20,000. Specify your rule <LSReduced Maximum' in the Calculation field.
  2. Assign the supplementary insurance to this contract scheme.
  3. You now have to implement the following logic for rule X1 in the BAdI:

Reducing the field E_MAXIMUM by the amount the first insurance relationship has already covered produces the maximum. This information is located in field COVAM in table I_RNPP10.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
BADI ISH_CONTRACT_MA CH Switzerland
BADI ISH_CONTRACT_MA SG Singapore
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20020111 
SAP Release Created in 463B