Kontakt

Ansicht
Dokumentation

ECPAO_ECTMPL_METADATA_WRITER - Import of Metadata from Employee Central Using XML File

ECPAO_ECTMPL_METADATA_WRITER - Import of Metadata from Employee Central Using XML File

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This program imports metadata such as field names and field descriptions from SAP SuccessFactors Employee Central (EC) to the Enterprise Resource Planning (ERP) system. This metadata is used when transferring data between Employee Central and ERP.

Note
You can only use this program to import metadata for Web service entities. If you want to import metadata for CSV data import entities, use the Import of Metadata from Employee Central(ECPAO_ECFLD_METADATA_WRITER) program instead. For more information, see Import Metadata from Employee Central Using CSV File.

Integration

If you run this program in a test system or client and haven't selected the Test Run checkbox, the program asks for a transport request, on which the imported metadata will be saved. Selection of a suitable transport request is mandatory for productive runs. Using this request you can transport the entries to the productive system or client.

You use the metadata imported by this program in Customizing in the VC_ECPAO_MAP_OM and VC_ECPAO_MAP view clusters. For more information, see Define Field Mapping for Organizational Data and Define Field Mapping for Employee Data.

Prerequisites

You have specified your Employee Central instance ID in the V_ECPAO_COMPANY view. For more information, see Specify Employee Central Instance ID.

You have downloaded the metadata that you want to import from Employee Central and stored the metadata file in the XML format on a server or on your local disk. To download metadata from Employee Central, go to the Admin Center and choose the OData API Metadata Refresh and Export tool. Then choose Export for the Export Metadata to File option.

Features

Selection

Make the following entries:

  • Select your Employee Central instance ID.
  • Select the Employee Central entity for which you want to import the metadata.
Note
If you don't specify a specific template, the metadata is imported for all Employee Central entities that are defined in Customizing and use the Web Service Transfer communication channel.
For more information see Define Employee Central Entities for Additional Org. Data Entities and Define Employee Central Entities for Additional Employee Data Entities.
  • Specify the file path under which the metadata XML file that you've downloaded from Employee Central is stored on the server or on your local disk.
  • Specify if the program is to perform a test run. If you carry out a test run, you receive a log that lists the fields and field contents to be imported. If you carry out a productive run, the EC Entity Field Mapping (ECPAO_FLD) table is updated with the metadata and you are shown a success message.
  • Select the Update Metadatacheckbox to import metadata or the Delete Metadatacheckbox the delete imported metadata from the ERP system.
  • Select the Update Metadata checkbox to import metadata or the Delete Metadata checkbox to delete imported metadata from the ERP system.

Note
You can't delete metadata in the ERP system that you have already used for field mappings. Otherwise your mappings become invalid. You are shown an error message if you try to delete metadata that is used for field mappings.
When you are replicating the data from Employee Central, two values are configured for a particular field in ERP while you are entering only one value in Employee Central. Hence any additional fields can be added to the ECPAO_FLD table without the need of adding any additional unused fields from Employee Central. Make sure that all the field properties are maintained properly.

Standard Variants

Output

For test runs, you receive a detailed log. For productive runs in the test system or client, you are asked for are transport request, to which the program assigns the imported entries. For all productive runs, you are shown a success or error message.

In situations such as the following you are shown a warning message: You have already imported metadata from Employee Central and used it in Customizing to map ERP data. The next run of the program would change this metadata since the new version of the metadata XML file that you import into the ERP system contains changes that you've made in Employee Central. Your mapping might therefore become invalid.

The following fields are updated in the ECPAO_FLD table:

  • EC Instance: The Employee Central instance ID you have specified on the selection screen of this program
  • EC Entity: The entity you have specified on the selection screen of this program. If you haven't specified an Employee Central template, the metadata is imported for all Employee Central templates.
  • EC Field: ID of the Employee Central field. The program generates this ID to identify the field in the ERP system. The Employee Central field IDs 1-15 are reserved for standard fields (see below). The IDs of the other fields use ascending numbers starting from 16.
  • EC Field Name: Name of the Employee Central field imported from the XML file you have specified on the selection screen of this program.
For navigation properties, the name is concatenated from the navigation property (such as divisionFlxNav or parentNav) and the key field (either startDate or externalCode), linked with a forward slash (for example: divisionFlxNav/startDate).
For country-specific job classification fields, the name of all visible fields is also concatenated:
  • For predelivered countries such as the USA or Australia, the name is concatenated from the navigation properties toJobClassificationCountry and toJobClassification and the field name, linked with forward slashes (for example: toJobClassificationCountry/toJobClassificationAUS/ascoCode)

  • For other countries such as Germany, the name is concatenated from the navigation properties toJobClassificationCountry and cust_JobClassification and the field name, linked with forward slashes (for example: toJobClassificationCountry/cust_JobClassificationGermany//ascoCode)

  • EC Field Description: Description of the Employee Central field imported from the XML file you have specified on the selection screen of this program.
  • Required: Required field indicator (see Is Required).
Note
Check the Employee Central data models (primarily, the Succession Data Model and the Country-Specific Data Models) to make sure that all required fields are indicated there.
  • Data Type: The data type (such as string or decimal) a field has in Employee Central (see Data Type of EC Field)
  • Visible: Indicator that the field is visible in Employee Central
Note
Only visible fields can be used for data transfer from Employee Central to the ERP system. For more information see Is Relevant for Data Transfer from EC.
Navigation Field: Indicator that the field is a navigation field in Employee Central
  • Filterable: Indicator that the field is filterable in Employee Central
  • Upsertable: Indicator that the field is upsertable in Employee Central
Note
Only upsertable fields can be used for data transfer from the ERP system to Employee Central. For more information see Is Relevant for Data Transfer to EC.

Activities

To check the data that is stored in the ECPAO_FLD table, go to the Transport Imported Metadata and Check Metadata for File-Based Data Transfer Customizing activity (see Transport Imported Metadata and Check Metadata for File-Based Data Transfer).

Example






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: 11649 Date: 20240601 Time: 012004     sap01-206 ( 175 ms )