Utilizing the Oracle Fusion Human Capital Management (Oracle Fusion HCM) File-Based Loader, you can stack information in mass, including business object history, from any information source to Oracle Fusion HCM.
Key Features of File Base Loader
FBL loads information from source framework to Fusion HCM
Burdens information fit as a fiddle by means of Flat documents in a CSV structure for explicit Business Objects
Supports Initial information creation and continuous updates
Approves and loads the information
Backing for Error Correction
Supports complex information objects with full date powerful history
Supports various information sources
Supports Initial information creation and continuous updates
Appropriate for Large volumes, various leveled information
Document Based Loader utilizes the Oracle Fusion HCM Load Batch Data procedure to stack your source information to the Oracle Fusion application tables. The Load Batch Data process:
Imports information at first in object-explicit groups to organize tables.
Readies the information for load in the stage tables.
Burdens information from the stage tables to the Oracle Fusion application tables.< alt="" src=images/prophet combination/prophet combination hcm/fb1.png"/>
Information Loading Sequence utilized in Oracle Fusion HCM File-Based Loader
For fruitful utilization of File-Based Loader:
Comprehend your arrangement model.
Set up the source information.
Security Roles required for FBL
To stack information from the Oracle Web Center Content server, you should have the obligation job File Import and Export Management Duty. Of course, the accompanying activity jobs acquire the File Import and Export Management Duty job:
1.Human Capital Management Application Administrator
2.Human Capital Management Integration Specialist
To stack information from the Load Batch Data organize tables to the Oracle Fusion application tables, you should have the HCM Batch Data Loading Duty job. Naturally, the accompanying activity jobs acquire the HCM Batch Data Loading Duty job:
Stage 1: Configuration Parameters
The Load Batch Data process in Oracle Fusion HCM loads information from the stage tables to the Oracle Fusion application tables. Go to the Manage HCM Configuration for Coexistence task in the Setup and Maintenance work territory to set the design parameters.
Snap on Detach to see the full table. Determine the estimations of the considerable number of parameters. The arrangement parameters decide how this procedure works in your condition.
Stage 2: Defining Oracle Fusion Business Objects
The Business protests that begin in your source framework may reference different business questions that start in Oracle Fusion HCM. For these referenced business objects, you should create cross-reference data and remember this data for your source framework. The accompanying screen shot shows the Oracle Fusion business objects for which you may require cross-reference data, and the Oracle Fusion task that you perform to characterize every business object.
Stage 3: Generate the Mapping record for Cross Reference Information
To produce cross-reference data, present the Generate Mapping File for HCM Business Objects process from the Manage HCM Configuration for Coexistence page
In the event that the procedure status is 12, it implies the activity demand has run and finished effectively. On the off chance that the procedure status isn't 12, it implies that the activity demand not finished effectively. You can see the log record under Navigator - Tools - Scheduled Processes, looking by the procedure id and fix the blunder.
Significant point to consider
Stage 4: Mapping File Download
The Generate Mapping File for HCM Business Objects process makes at least one information documents (.dat records) for every business object. The .dat documents are bundled naturally in a compressed information record that is kept in touch with the WebCenter Content server. To download the record:
1.Open the File Import and Export page (Navigator - Tools - File Import and Export).
2.Set the Account an incentive in the Search segment to hcm/dataloader/fare and snap Search.
The compress record of reference data shows up in the indexed lists.
3.Click the record name in the indexed lists.
4.When incited, spare the document locally.
5.Unzip the document and you can see rundown of cross reference records created by Fusion.
You should utilize the Globally Unique Identifier (GUID) values from the cross-reference data that you produced, to guarantee that remote key references in your source information to the current Oracle Fusion objects are right.
The accompanying screen capture shows GUIDs from a XR_SETID_SET.dat document.
The accompanying portrays the qualities in the XR_SETID_SET.dat document:
Stage 5: Map Source Data to Reference Data
We have to characterize mappings between source information and the cross-reference information imported to the source condition. Presently the inquiry is the manner by which you will realize what the sections it searches for are. Prophet has distributed a segment mapping spread sheet. Following is the mapping Spreadsheet which discloses segments to be available in the level records and business rules to be followed while planning information.
Key Features of File Base Loader
FBL loads information from source framework to Fusion HCM
Burdens information fit as a fiddle by means of Flat documents in a CSV structure for explicit Business Objects
Supports Initial information creation and continuous updates
Approves and loads the information
Backing for Error Correction
Supports complex information objects with full date powerful history
Supports various information sources
Supports Initial information creation and continuous updates
Appropriate for Large volumes, various leveled information
Document Based Loader utilizes the Oracle Fusion HCM Load Batch Data procedure to stack your source information to the Oracle Fusion application tables. The Load Batch Data process:
Imports information at first in object-explicit groups to organize tables.
Readies the information for load in the stage tables.
Burdens information from the stage tables to the Oracle Fusion application tables.< alt="" src=images/prophet combination/prophet combination hcm/fb1.png"/>
Information Loading Sequence utilized in Oracle Fusion HCM File-Based Loader
For fruitful utilization of File-Based Loader:
Comprehend your arrangement model.
Set up the source information.
- Get ready information for transfer.
- Deal with the transfer procedure.
Security Roles required for FBL
To stack information from the Oracle Web Center Content server, you should have the obligation job File Import and Export Management Duty. Of course, the accompanying activity jobs acquire the File Import and Export Management Duty job:
1.Human Capital Management Application Administrator
2.Human Capital Management Integration Specialist
To stack information from the Load Batch Data organize tables to the Oracle Fusion application tables, you should have the HCM Batch Data Loading Duty job. Naturally, the accompanying activity jobs acquire the HCM Batch Data Loading Duty job:
- Application Implementation Consultant
- Human Capital Management Application Administrator
Stage 1: Configuration Parameters
The Load Batch Data process in Oracle Fusion HCM loads information from the stage tables to the Oracle Fusion application tables. Go to the Manage HCM Configuration for Coexistence task in the Setup and Maintenance work territory to set the design parameters.
Snap on Detach to see the full table. Determine the estimations of the considerable number of parameters. The arrangement parameters decide how this procedure works in your condition.
Stage 2: Defining Oracle Fusion Business Objects
The Business protests that begin in your source framework may reference different business questions that start in Oracle Fusion HCM. For these referenced business objects, you should create cross-reference data and remember this data for your source framework. The accompanying screen shot shows the Oracle Fusion business objects for which you may require cross-reference data, and the Oracle Fusion task that you perform to characterize every business object.
Stage 3: Generate the Mapping record for Cross Reference Information
To produce cross-reference data, present the Generate Mapping File for HCM Business Objects process from the Manage HCM Configuration for Coexistence page
In the event that the procedure status is 12, it implies the activity demand has run and finished effectively. On the off chance that the procedure status isn't 12, it implies that the activity demand not finished effectively. You can see the log record under Navigator - Tools - Scheduled Processes, looking by the procedure id and fix the blunder.
Significant point to consider
- Whenever you make changes to any of the Oracle Fusion business objects, you should recover the mapping record. For instance, in the event that you characterize extra individual sorts, at that point you should recover the GUIDs for the Oracle Fusion example.
- The GUIDs related with an Oracle Fusion occasion don't change. Be that as it may, GUIDs differ among occasions. In this manner, the GUIDs that you create from the stage condition are not quite the same as those that you produce from the generation condition. You should create them in the two situations.
Stage 4: Mapping File Download
The Generate Mapping File for HCM Business Objects process makes at least one information documents (.dat records) for every business object. The .dat documents are bundled naturally in a compressed information record that is kept in touch with the WebCenter Content server. To download the record:
1.Open the File Import and Export page (Navigator - Tools - File Import and Export).
2.Set the Account an incentive in the Search segment to hcm/dataloader/fare and snap Search.
The compress record of reference data shows up in the indexed lists.
3.Click the record name in the indexed lists.
4.When incited, spare the document locally.
5.Unzip the document and you can see rundown of cross reference records created by Fusion.
You should utilize the Globally Unique Identifier (GUID) values from the cross-reference data that you produced, to guarantee that remote key references in your source information to the current Oracle Fusion objects are right.
The accompanying screen capture shows GUIDs from a XR_SETID_SET.dat document.
The accompanying portrays the qualities in the XR_SETID_SET.dat document:
- FusionGUID - A one of a kind, 32-character alphanumeric identifier utilized by both Oracle Fusion HCM and source applications, for example, Oracle PeopleSoft and Oracle EBS.
- FusionKey - The worth that is utilized by Oracle Fusion HCM.
- PeopleSoftKey-The worth that is utilized by the source framework (Oracle PeopleSoft or some other system).
- Description-Description of the worth recognized by the keys.
- Description2-Description of the worth recognized by the keys.
Stage 5: Map Source Data to Reference Data
We have to characterize mappings between source information and the cross-reference information imported to the source condition. Presently the inquiry is the manner by which you will realize what the sections it searches for are. Prophet has distributed a segment mapping spread sheet. Following is the mapping Spreadsheet which discloses segments to be available in the level records and business rules to be followed while planning information.
No comments:
Post a Comment