Kontakt

Ansicht
Dokumentation

ECPAO_BADI_EXTRCTOUT - BAdI: Mapping of EC and ERP Data for Data Replication to EC

ECPAO_BADI_EXTRCTOUT - BAdI: Mapping of EC and ERP Data for Data Replication to EC

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the integration add-on for Enterprise Resource Planning (ERP) and SuccessFactors Employee Central (EC) when extracting data from the ERP system and replicating it to Employee Central.

You use this BAdI to map data that is maintained in the ERP system to fields from Employee Central. You use it if you cannot map an Employee Central field one to one to an ERP infotype or subtype field or if you want to extract data from sources other than infotype or subtype fields.

The BAdI is called when you have mapped fields that are used in data transfer from ERP to Employee Central in the VC_ECPAO_MAP_OM or VC_ECPAO_MAP view cluster and have selected the mapping mode BAdI Mapping. For more information see Define Field Mapping for Organizational Data and Define Field Mapping for Employee Data.

The BAdI uses the method GET_FIELDS_VALUE with the following parameters:

  • Importing parameters
  • IV_ERP_TEMPLATE: ERP transformation template that you have defined in the VC_ECPAO_MAP_OM or VC_ECPAO_MAP view cluster

  • IV_TEMPLATE_ID: Employee Central template that you have assigned to the ERP transformation template in the VC_ECPAO_MAP_OM or VC_ECPAO_MAP view cluster

  • IV_EC_FIELD: Employee Central field that is contained in the ERP transformation template and for which you want to extract ERP content

  • IV_MOLGA: Country grouping of the data to be extracted

  • IV_PERNR: Personnel number of the employee for whom data is to be extracted (optional parameter)

  • IV_OTYPE: Type of the organizational object for which data is to be extracted (optional parameter)

  • IV_OBJID: ID of the organizational object for which data is to be extracted (optional parameter)

The GET_FIELDS_VALUE BAdI method is called by the following data extraction programs:
  • Employee Data Extraction (ECPAO_EMPL_EXTRACTION)

Pass information to this program using the optional parameter IV_PERNR.
  • Organizational Data Extraction (ECPAO_OM_OBJECT_EXTRACTION)

Pass information to this program using the optional parameters IV_OTYPE and IV_OBJID.
Based on these optional importing parameters, the implementation of the method reads the appropriate data, which is to be sent to Employee Central.
  • Exporting parameter
ET_BADI_FIELD_VAL: Table consisting of the following fields:
  • EC_FIELD_ID: Employee Central field for which you want to extract ERP content

  • VALUE: Content of the Employee Central field

  • BEGDA: Begin of the validity period of the data to be extracted

  • ENDDA: End of the validity period of the data to be extracted

Example: You extract the content for the Employee Central field Cost Center for an employee from ERP. The employee was assigned to three different cost centers over time. In this case, ET_BADI_FIELD_VAL contains three entries with the same EC_FIELD_ID, but different content for VALUE, BEGDA, and ENDDA:
  • Cost center 1 from date 1 to date 2

  • Cost center 2 from date 2 to date 3

  • Cost center 3 from date 3 to high date

You have made the required settings in the VC_ECPAO_MAP_OM or VC_ECPAO_MAP view cluster. For more information see Define Field Mapping for Organizational Data and Define Field Mapping for Employee Data.

If you have selected the mapping mode BAdI Mapping in the VC_ECPAO_MAP_OM or VC_ECPAO_MAP view cluster, create a customer-specific implementation of this BAdI. The implementation must provide the mapping for all fields from the view cluster for which you have selected this mapping mode.

  • CL_ECPAO_MAP_EMP_DATA_VIA_BADI
This class contains some examples of how you can provide ERP content for Employee Central fields. If you create a customer-specific implementation of this BAdI, you can copy the sample class for your implementation and adapt the coding to suit your requirements.





BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5525 Date: 20240523 Time: 175123     sap01-206 ( 76 ms )