Hierarchy
INSURANCE (Software Component) SAP Insurance⤷
FS-CM (Application Component) Claims Management⤷
ICL_BASIS (Package) FS-CM: General Functionality
IMG Activity
| ID | SIMG_ICL_CE_ZINCLUDE | Enhancement Using Z Includes |
| Transaction Code | S_P7I_08000892 | (empty) |
| Created on | 20080306 | |
| Customizing Attributes | SIMG_ICL_CE_ZINCLUDE | Enhancement Using Z Includes |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _ICL_CE_ZINCLUDE |
Use
You can use Z includes to insert customer-specific coding into certain SAP programs.
Z includes are often used in connection with calling subprograms. These subprograms do not exist in the delivered SAP coding, but you can create them in your customer system in a Z include or by means of an implicit source code enhancement (see Notes on Different Enhancement Options -> Implicit Enhancement Options in ABAP Source Text).
You can use a Z include to overwrite certain variables of the SAP standard program or to include additional program logic. Z includes are possible in the following places in SAP Claims Management, but you do not necessarily have to create them:
Programs:
- RICL_CLAIM_CHEAT_SHEET
- RICL_CLAIM_DI
- RICL_CLAIM_DI_CHECK
- RICL_CLAIM_DI_JOB_SCHEDULE
- RICL_CLAIM_SEARCH_1
- RICL_CLAIMBUNDLE_SEARCH_1
- RICL_CLAIMS_LIST
- RICL_PAYMENT_REPORT
- RICL_WCOMP_RWB_OVERVIEW2
Function groups:
- ICL_BAS_AUTHORITY
- ICL_CMC_DOCK
- ICL_CORR_EXT
- ICLE_CMC_DOCK
- ICLE_CMC_EXT
- ICLE_BULKINV_BDT
- ICLE_BULKINV_EXT
- ICLH_INVOICE2_BDT
Further notes
- To find all Z includes and subprograms, execute the program RS_ABAP_SOURCE_SCAN. Enter the following selection parameters:
- Packages ICL* and IGN*
- Search term IF FOUND
- For more information, see the notes in the SAP Support System. Search for notes for the FS-CM component with the search term IF FOUND. These notes document how you can perform an enhancement.
Requirements
Standard settings
Activities
Example
A large number of local classes are used in the function group ICLE_BULKINV_BDT when collective invoices are processed.
If you want to overwrite processing of these local classes (such as LCL_INVBRANCH_AL), you must define a local class in the customer namespace in the Z includes ZLICLE_BULKINV_BDTLCD (class definition) and ZLICLE_BULKINV_BDTLCI (class implementation). Alternatively you can create the definition and implementation of the class by means of implicit source code enhancements in the includes LICLE_BULKINV_BDTLCD and LICLE_BULKINV_BDTLCI.
The customer class would then have the following rudimentary structure:
*INCLUDE zlicle_bulkinv_bdtlcd
CLASS ZLCL_INVBRANCH_AL DEFINITION INHERITING FROM LCL_INVBRANCH_AL.
...
METHODS: BRANCH_TO_CLAIM REDEFINITION
...
ENDCLASS.
* INCLUDE zlicle_bulkinv_bdtlcd
CLASS ZLCL_INVBRANCH_AL IMPLEMENTATION.
...
METHOD BRANCH_TO_CLAIM.
* Uebersteuertes coding
...
ENDMETHOD.
ENDCLASS.
The new local customer class then needs to be instantiated by the SAP standard program (instead of the standard class). Note the following:
- Implement the subprogram ZZ_SET_TYPE_INVBRANCH_AL in the Z include ZICLE_BULKINV_BDTF01.
Alternatively, you can do this by means of an implicit source code enhancement in the include LICLE_BULKINV_BDTF01.
* INCLUDE ZICLE_BULKINV_BDTF01
FORM ZZ_SET_TYPE_INVBRANCH_AL USING CV_CLASS TYPE STRING.
CV_CLASS = 'ZLCL_INVBRANCH_AL'.
ENDFORM.
- The subprogram returns the name of the customer class that needs to be instantiated (ZLCL_INVBRANCH_AL in this example).
- The call of the subprogram in the SAP standard program and the subsequent instantiation are as follows:
CLASS LCL_INVBRANCH_AL IMPLEMENTATION.
...
METHOD get_instance.
DATA:
lv_type TYPE string VALUE 'LCL_INVBRANCH_AL'.
PERFORM:
zz_set_type_invbranch_al IN PROGRAM (sy-repid)
USING lv_type IF FOUND.
CREATE OBJECT ro_invbranch_al TYPE (lv_type)
EXPORTING
iv_claim = iv_claim
iv_subclaim = iv_subclaim/
iv_procurement = iv_procurement.
ENDMETHOD. "get_instance
...
ENDCLASS.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20080306 |
| SAP Release Created in |
