Ansicht
Dokumentation

/GSINS/INH_SET_VC - Map FS-CM Data to HCM Data

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this Customizing activity, you make the settings that the system uses to transfer data such, as payment data or business partner master data, from Claims Management to the Human Resources component.

You can make the settings on the following screens:

• Country/Region-Specific Settings

You make the settings used to transfer data to a HCM application component on your system or another system.

• Destination: In case the HCM application component is located on another system, you use this field to specify the RFC connection name that you use to transfer the data to the remote HCM application component.

• Mapping Steps

In this step, you specify the selection method that you use for each mapping step defined in the Service Mapping Tool (SMT).

Mapping steps link together source and target structures which the system uses to transfer data from Claims Management to the HCM application component.

• BRF+ Events

In this step, you assign a BRF+ event to a BRFplus function. The system uses BRF+ events to process payments entered on claims. When you save one or more payments on an insurance claim, the event calls the assigned function to carry out the following processing steps:

• Main Disbursement BRF Decision: Calls a function to decide whether the given payment is relevant for processing in the HCM application component

• Payment BRF Decision: In case the given claim contains payments that need to be transferred to HCM, this function checks each payment on the claim, to evaluate whether they belong to the correct claim type. If so, BRF+ creates triggers for further processing of the data in SMT.

• HCM Events

In this step, you assign HCM Events to function module in the HCM application component.

HCM events are used when you process business partner or claim data using the IMP manager tool. Each event is assigned a function module that carries out the necessary processing steps in the HCM module.

Examples include the following:

• Hire Person: the hire person event is called when a certain data is transferred, but the relevant person (such as payee or beneficiary), does not exist in the HCM module. The system therefore creates the person in the HCM module (that is, carries out a hiring personnel action).

• The Payment event is called when payment data is transferred from a claim, a payment record is created on the Additional Payments (0015) infotype in the HCM module

• Event Steps

In this step, you define a series of mapping steps for each HCM event. The steps determine how data is processed when a certain HCM event is called. For example, when the Hire Person event is called, the system retrieves business partner master data from Claims Management and transfers them into the corresponding infotypes, such as Organizational Assignment (0001), Personal Data (0002), Addresses (0006), Planned Working Time (0007).

• Disbursements: assignment of benefit types to wage types

In this step, you assign benefit types to wage types for processing disbursements in the HCM application component. When replicating the disbursements on the Additional Payments (0015) infotype, the system uses these settings to determine in which wage type it should store a disbursement item.

• External Transfers: assignment of benefit types to wage types

In this step, you assign benefit types to wage types for processing external transfers in the HCM application component. When replicating external transfers in the External Bank Transfers (0011) infotype, the system uses these settings to determine in which wage type it should store an external transfer.

General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4595 Date: 20240420 Time: 095810     sap01-206 ( 75 ms )