C_HRHFC_2411 SAP Certified Associate - Implementation Consultant - SAP SuccessFactors Full Cloud/Core Hybrid Questions and Answers

Thedeltamode retrieves onlychanges since the last successful replication, ideal for payroll or auditing.

Filtering options in the monitor include parameters like new hires only, country, and multiple company codes to refine data visibility for troubleshooting. These help narrow down replication issues efficiently.

PAOCFEC_KMAPCOSCis thekey mapping tableused to distinguish cost centers from different ERP systems, even if they share the same name. This prevents collisions and ensures correct assignment during replication.

UI integration is primarily used in:

Side-by-Side: Some processes are in EC, others in SAP ERP.

In the OData Upsert configuration for packaged integration:

Authentication typedefines how the adapter connects securely to SuccessFactors.

Addressspecifies the endpoint URL for the OData service.

The BAdI ECPAO_IN_EXT_PERNR_MAP is specifically used when the mapping mode is set toBAdI Mapping. It allows for custom field transformations during replication, which is essential when standard mappings do not suffice.

TheEmpEmployment and PerPersonAPIs allow filtering on up to20 custom string fields, enabling flexibility in custom data segmentation and reporting.

Connection Type Gis used forHTTP destinationspointing to external services like SAP Integration Suite. This type ensures communication over web protocols, which is necessary for CPI integrations.

In the Business Integration Builder (BIB), the"Is Temporary"flag indicates the national ID is temporary, and"Temporary ID"holds the actual value. These fields are essential for handling scenarios where an employee doesn’t yet have a permanent ID, such as new hires.

SAP emphasizes use ofODataandSOAP APIs, as they arestandardized, versioned, and decoupled, enabling upgradability and extensibility aligned with clean core principles.

The ODTFINCC (Cost Center Integration Content) add-on is specifically designed to handle cost center data replication from SAP ERP to Employee Central. It includes the necessary middleware configurations.

Custom templatesare required to map custom objects.

Transaction SFIOM_KMAP_OSI is used to verify and maintainkey mappingsbetween SAP ERP organizational object IDs and those used in Employee Central. This step is critical to ensure data integrity across systems after migration.

The system chooses thelatest of the configured FTSDsto ensure no data is replicated before the defined cut-off across different dimensions (country, assignment, general). This minimizes the risk of redundant or outdated data being pushed.

APOST requestto an entity in OData API is used for bothcreating new recordsandupdating existing ones, depending on whether the record already exists. This is a common pattern in OData "upsert" logic.

The switch"Fallback Action Type for Hire"ensures that when no specific action type is defined during initial migration, a placeholder record is created using the employee’s hire date. This is useful for continuity in employment history.

Basic extensibility allows mapping of fields between Employee Central and SAP ERP infotypes. For compensation data from the Compensation Information portlet in EC, the corresponding infotype in SAP ERP is Basic Pay (0008), which stores employee base pay and related compensation values. This infotype is explicitly designed to hold structured compensation data which aligns with Employee Central Compensation Information.

To replicate associations, you mustmap association types to ERP relationship types. This determines how the linkage between cust_shop and division is interpreted in the SAP ERP hierarchy.

The transformation template group must include:

Non-filter modeif the data should not be restricted by change pointers.

Primary and secondary mappingto align EC and ERP field structures.

If the BAdI Change Mapped Infotype Data is implemented and infotypes are not included in the replication payload, they are delimited to maintain data consistency and avoid duplicates. The system assumes that missing infotype data means it is no longer valid.