Ansicht
Dokumentation

SIMG_ICL_VC_TICL123 - Define Transaction Types for External Services Integration

General Material Data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Use

In this Customizing activity you define the possible transaction types for the following business processes:

• Procurement using an external procurement system

• Appointing a service provider

All settings in the Customizing activity are listed below. They are all relevant for the business process Procurement using an external procurement system. Conversely, only certain settings are relevant for the business process Appointing a service provider. For more information, see the note at the end of the listed settings.

Make the following settings for a transaction type:

• Key

• Name

• Transaction type in the external procurement system

• State whether the goods receipt of the ordered item must be documented in the procurement system.

• Anticipated delivery time in days

• Maximum number of days in which procurement is still permitted

• RFC link to procurement system

• Assign participant roles to a transaction type.

If you select a transaction type on the Claimed Items screen during claims processing, the system only considers services in a certain business partner role for the procurement transaction. This business partner role is determined by the participant role that you assign here. A participant role in the Claims Management system is assigned to one (or no) business partner role in the business partner system.

• Assign insurance lines of business to a transaction type.

This transaction type is only permitted for the lines of business listed here. During claim data capture, the system only displays the transaction types for a line of business that you have assigned here.

• Assign evaluation criteria for vendors to a transaction type.

You can specify these criteria in greater detail as follows:

• You can define a weighting for the relevant evaluation criterion. The sum of the weightings of all evaluation criteria must be 100 for each priority.

• You can define a priority for the relevant evaluation criterion.

• You can define a lower threshold value for equating vendors for an evaluation criterion.

• You can define an upper threshold value for excluding vendors for an evaluation criterion.

Flag one of the evaluation criteria as the preselection criterion.

In the application, the system uses these evaluation criteria to determine a ranking list of the possible services or the best service for the relevant transaction type. The system uses the preselection criterion to make a preselection. Only afterwards does the system consider other evaluation criteria.

Note:

Only the following settings are relevant for the business process Appointing a service provider:

• Key

• Name

• Assignment of transaction type to participant roles

• Assignment of transaction type to lines of business

• Assignment of transaction type to evaluation criteria

In Customizing activity Configure Benefit Type Trees, assign one of the transaction types defined here to a benefit type, at benefit tree level. On the Claimed Items screen, in the Procurement Transaction field, the system displays the transaction type that you defined for the relevant benefit type as a default value. Using the F4 input help, you can select another procurement transaction. In the F4 input help the system displays all the transaction types that you defined in this Customizing activity.

Requirements

• If you want to define your own participant roles, you must do so in Customizing activity Enhance Participant Roles.

• You have executed the Customizing activity Define Insurance Line of Business.

• You have executed the Customizing activity Define Evaluation Criteria.

Standard settings

Activities

Example

Possible transaction types:

• Vehicle repair: You can restrict the line of business to automobile insurance, for example.

• Appraisal for repair costs: You can assign the participant roles Appraiser or Repair Shop to an appraisal, for example.

• Replacement of home contents

• Provision of rental car

Example of Vendor Evaluation on the Basis of Weighting:

For the sake of simplicity, the same priority 1 has been assigned to all evaluation criteria in the following example: If only the four standard evaluation criteria PRICE, SERVICE, DISTANCE, and CUSTSATISF are considered, the overall evaluation of a vendor is calculated by the following formula:

Overall evaluation ,,=
,,,,,, weight_PRICE * value_PRICE
,,,,,,+ weight_SERVICE * value_SERVICE
,,,,,,+ weight_DISTANCE * value_DISTANCE
,,,,,,+ weight_CUSTSATISF * value_CUSTSATISF

• where the following rules apply:

• Value of a weighting is between 0 and 100 (for example, 0 <= weight_a <= 100)

• The sum of the weightings of all evaluation criteria must be 100 for each priority (such as weight_a + weight_b + ... + weight_z = 100),

• where the following rules apply for this value (value is assigned to a business partner in table ICLBUT01):

0 <= value_a <= 100, where value "0"stands for the best possible evaluation and value "100" for a very poor score.

Evaluation criteria that are particularly important therefore have a high weight; evaluation criteria that should not be taken into account have weight "0". The vendor with the lowest weighted overall evaluation has the best score and appears at the top of the vendor evaluation list.

Example of Vendor Evaluation on the Basis of Priority:

It is assumed that all four standard evaluation criteria have the same weight (100), whereas the priorities are assigned as follows:

DISTANCE has priority 1
PRICE has priority 2
CUSTSATISF has priority 3
SERVICE has priority 4.

As in the above scenario, the system calculates the weighted evaluation for each priority. This calculation is not particularly meaningful, because there is only one adder and the weight is always 100. The sequence of vendors is determined as follows: First of all, the weighted evaluations for priority 1 are compared with one another. If this value is the same with two vendors, the weighted evaluations for priority 2 are compared with one another. If this value is still the same, the weighted evaluations for priority 3 are compared with one another, and so on. It is also possible to use the priority as well as the weights. In this case, the methods described above are combined.

Customer Changes

If you want to use more than five priorities, you must define other components in the customer structure CI_VALUE_ALV. The other components must have the name VALUExx, where xx stands for the number combination 06, 07, 08, and so on. (Fields VALUE01 ... VALUE05 for priorities 1, 2, ...5 are in structure ICLVALUE_ALV in the system).

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 9831 Date: 20240607 Time: 195535     sap01-206 ( 141 ms )