Kontakt

Ansicht
Dokumentation

SIMG_ICL_M_TICL600 - Assign Condition Field in Claim to Application Rule Variant

SIMG_ICL_M_TICL600 - Assign Condition Field in Claim to Application Rule Variant

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Use

In this Customizing activity you define the assignment of Condition Field for ILM Objects Claim and Claim Bundle to the application rule variant. This is done dependent on a combination of internal claim type, subclaim type, and coverage type (see also "Prerequisites" below).

You need this assignment for the following:

  • The condition field from the combination of internal claim type, subclaim type and coverage type exceeds the maximum permitted character length of 12 characters. To be able to store the required information in the ILM object Claim and/or Claim Bundle, you must map the combination of internal claim type, subclaim type and coverage type in an application rule variant. You can then store this application rule variant in the ILM object Claim and/or Claim Bundle.
  • You must also enter the information from the condition field in the ILM object Business Partner to determine the end of the retention period of a business partner.
Since the ILM object Business Partner does not know any FS-CM specific fields (such as internal claim type), there is the generic condition field Application Rule Variant in this Customizing activity.

Consider the following when making settings in this Customizing activity:

  • If you do not enter any value in the fields for the internal claim type, subclaim type, and coverage type, the system then uses the value of the condition field for the application rule variant as well.
  • If you leave the Application Rule Variant field empty, the system also uses the value of the condition field for the application rule variant as well.
  • To reduce the number of entries, you can enter a plus sign (+) in the fields for claim type, subclaim type, and coverage type.
The system then looks first of all for a specific entry (in other words, for a certain value in the field, such as coverage type = VK). If the system does not find any specific entry, it looks for a generic entry with the plus sign (+). The sequence is that the system first looks in the Coverage Type field, then in the Subclaim Type field, and lastly in the Claim Type field.
  • If you have stipulated in Customizing activity Define Fields for Creating Condition Field (see "Prerequisites" below) that the coverage type or also the subclaim type are not used, then the corresponding fields are hidden.

Requirements

In Customizing activity Define Fields for Creating Condition Field, you can define which fields should be used.

Standard settings

Activities

Example






ABAP Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 3496 Date: 20240523 Time: 234741     sap01-206 ( 71 ms )