Replicating Master Data for Internal Order and Project Entities

This topic provides job and global variable information required to replicate master data for the Internal Order and Project entities.

Extract Internal Order and Project Data from Flat Files

Perform the following steps to extract data using the Universal Connector connection:

Note: The internal order entity is only available for Flat File/Universal Connector.

1. In the Local Object Library > Projects tab, open the required job depending on the entity:

   Entity	Project	Job
   Internal Order	MDR_Internal_Order	MDR_Internal_Order_UC_EXTRACT
   Project	MDR_Project	MDR_JOB_Project _UFF_EXTRACT

2. Update the values of the following variables in the job using the Tools > Variables option:
   • $G_ERP: Indicates the ERP name, such as UC.
   • $G_SOURCE_SYSTEM: Indicates the source system name.
   • $G_UID: Indicates that the job is automatically triggered from the Management Console.
   • $G_COMMIT_SIZE: Indicates the commit size. The default value is 100000.
   • $G_UC_FOLDER_LOCATION: Indicates the folder path from which the utility should retrieve files. If left blank, the utility will default to the folder path defined in the SourceConnect Management Console Connection tab during the UC data source configuration.
   • $G_UC_File_Wildcard: Indicates the file name pattern (wildcard) that the utility should use to identify relevant files. The default value is .CSV. Some examples include UC_.CSV, EBS_*.CSV.
   • $G_UC_Skipped_Rows: Indicates the number of initial data rows to skip during file extraction. The default value is 0. Only positive integers are allowed.

     Note: Do not include empty lines in this count. Only count rows that contain data and need to be skipped. For example, if rows 1–3 contain data and rows 4–5 are empty, enter 3 as the value. The empty rows will be skipped automatically.

3. Run the job. This job extracts data from the source csv file and loads it into staging tables, performing both column-wise and data-wise validation checks during execution. A message indicating the job status displays.

Extract Project Data from Source Systems

Perform the following steps to extract data from data sources:

1. In the Local Object Library > Projects tab, open the MDR_JOB_Project _<DataSourceName>_EXTRACT job depending on the data source. For example, for Oracle PeopleSoft, open the MDR_JOB_PROJECT_PSFT_EXTRACT job under MDR_Project.
2. Update the values of the following variables in the job using the Tools > Variables option:

   Note: The variable names may differ in SAP Data Services Designer depending on the source system.

   • $FILE_PATH: Indicates the location of the csv folder that is available in the SchClient folder.
   • $<DataSourceName>$_PROJECT_OT: Indicates whether the data that must be extracted is one-time data or contains only the modified records. Set to 1 for loading only one-time load and 0 for loading only changed records.
   • $G_CLIENT: Indicates the client number.
   • $LANGUAGE: Indicates the language code that must be used for the project description.
   • $G_COMP_CD: Indicates the SAP company code to which the Microsoft Dynamics NAV company code is mapped. This is required only for Dynamics NAV.
3. Run the job. A message indicating the job status displays.

Load Internal Order and Project Data into SAP S/4HANA

Perform the following steps to load the extracted data into the staging database using the ETL job:

1. In the Local Object Library > Projects tab, open the required job depending on the entity:

   Entity	Project	Job
   Internal Order	MDR_ Internal_Order	MDR_Internal_Order_GOLD_LOAD
   Project	MDR_Project	MDR_JOB_Project _<DataSourceName>_GOLD_LOAD

2. Update the values of the following variables in the job using the Tools > Variables option depending on the entity:
   • Internal Order
     1. $G_SOURCE_SYSTEM: Indicates the source system name, UC.
     2. $DEFAULT_LANGUAGE: Indicates the language code that must be used if no language code is defined in the source system.
     3. $FILE_PATH: Indicates the location of the csv folder that is available in the SchClient folder.
     4. $G_ERROR_FILE_PATH: Indicates the location of the error logs.
   • Project
     1. $G_SOURCE_SYSTEM: Indicates the source system name.
     2. $G_CLIENT: Indicates the client number in SAP S/4HANA.
     3. $FILE_PATH: Indicates the location of the csv folder that is available in the SchClient folder.
     4. $PROJECT_PROFILE: Indicates the SAP project profile that is used for creating the project in SAP S/4HANA.
     5. $G_DB_TYPE: Indicates the database type.
     6. $G_DB_VERSION: Indicates the database version.
     7. $BUS_AREA: Indicates the business area of the project.
     8. $TIME_UNIT: Indicates the time unit.
     9. $TIME_UNIT_ISO: Indicates the time unit.
     10. $CO_AREA: Indicates the controlling area.
     11. $PROFIT_CTR: Indicates the profit center.
     12. $NETWORK_ASSIGNMENT: Indicates the network assignment of the project.
     13. $APPLICANT_NO: Indicates the applicant number of the project.
     14. $G_JOB_NAME: Indicates the job name.
     15. $G_ERROR: Indicates the error.
     16. $G_ERROR_LOG_FILE: Indicates the error log file.
     17. $CONTROL_KEY: Indicates the control key value that is used for creating the activities in the project in SAP S/4HANA. For example, PS01 indicates network-external processing.
     18. $NETWORK_TYPE: Indicates the network type that is used for creating the network in the project in SAP S/4HANA. For example, PSO2 indicates network with activity assignment.
     19. $NETWORK_PROFILE: Indicates the network profile that is used for creating the network in the project in SAP S/4HANA.
     20. $G_MAIL: Indicates the email ID where you want the job status to be sent.
3. Run the job. A message indicating the job status displays. The extracted data is imported into SAP S/4HANA.

Upload Data Mappings into SAP S/4HANA for Project Entity

After your data is extracted and loaded, a mappings file is created that defines the relationship between your source system data and SAP S/4HANA data. You can then upload these data mappings using ETL jobs.

To upload data mappings:

1. Open SAP Data Services Designer as an administrator and sign in to your repository.
2. In Local Object Library > Projects tab, open the MDR_JOB_Project_MAPPING_LOAD job.
3. Update these variables using Tools > Variables:
   1. $MDG_SOURCE_SYSTEM: Indicates the logical system name.
   2. $SOURCE_SYSTEM: Indicates the source system for the mappings upload.
   3. $FILE_PATH: Indicates the location of the csv folder in the SchClient folder.
4. Run the job. A message indicating the job status displays.