Examples of Loading Performance Documents

You can use HCM Data Loader to create performance documents in bulk and to perform supported actions on existing performance documents. For example, you can complete, cancel, reopen, restore, or delete a performance document, and you can load or update supported document data such as participants, attachments, section ratings, and comments.

This topic shows you how to load Performance Document objects and their supported components. In the examples, all components are referenced by their user keys.

The action performed by the load is determined by the value you specify for the Operation attribute. Some operations create a new performance document, while others require the performance document to already exist. The following table lists the valid operation values defined in the Performance Administration Action lookup (ORA_HRA_ADMIN_ACTION) and describes any dependencies.

Operation Value Notes
ORA_CREATE_PD Creates a performance document. This action requires that the performance template period and worker assignment must already exist.
ORA_COMPLETE_PD Completes a performance document. The performance document must already exist and must not be completed or canceled.
ORA_CANCEL_PD Cancels a performance document. The performance document must already exist and must not be canceled.
ORA_REOPEN_PD Reopens a performance document. The performance document must already exist and its status must either be completed or canceled.
ORA_RESTORE_PD Restores a performance document. The performance document must already exist and its status should be canceled.
ORA_DELETE_PD Deletes a performance document. The performance document must already exist and its status should be canceled.
ORA_CALC_MANAGER_RATING Updates manager calculated section ratings in performance documents. The performance document must already exist.
ORA_ADD_PARTICIPANT Creates or deletes participants for performance documents. The performance document must already exist.
ORA_ATTACH_PD Creates or deletes attachments for performance documents. The performance document must already exist.
ORA_TRANSFER_PD Transfers performance documents to a new performance document manager. The performance document must already exist and the same performance document must not exist on the assignment that it’s being transferred to.
ORA_UPDATE_MODEL_PROFILE_IN_PD Synchronizes model profile competency sections in performance documents with the current competencies in the model profile. When you select Update Competency Sections on the Mass Actions for Performance Documents page for HR administrators, competencies added to the model profile are added to the performance document, and competencies removed from the model profile are removed from the performance document if they haven't been evaluated. The performance document must already exist.
ORA_SYNC_PD Synchronizes goal data in performance documents with the corresponding goal data in Goal Management and Career Development when synchronization is initiated by the Synchronize Goal Data in Performance Documents scheduled process. The performance document must already exist.
ORA_RATING_PD Provides section ratings and comments in performance documents. The performance document must already exist.
ORA_UPDATE_PERS_PROFILE_IN_PD Synchronizes competencies in person profile competency sections in performance documents with the employee’s Talent profile when the Synchronize Person Profile Content in Performance Documents scheduled process is run. The performance document must already exist.
ORA_CALCULATED_RATING_PD Updates recalculated section ratings in performance documents when rating calculation is initiated from All-in-One Evaluations. When you select Calculate ratings in All-in-One Evaluations, the ratings are recalculated and the updated values are loaded using this operation. The performance document must already exist.
ORA_SUBMIT_PD Submits manager evaluation tasks in performance documents when submission is initiated from All-in-One Evaluations. When you submit manager evaluations in All-in-One Evaluations, the manager evaluation tasks are submitted using this operation. The performance document must already exist.
ORA_SUBMIT_PD_IGNORE_WARNING Submits manager evaluation tasks in performance documents and ignores processing warnings when submission is initiated from All-in-One Evaluations. When you submit manager evaluations in All-in-One Evaluations and choose to continue despite processing warnings, the manager evaluation tasks are submitted using this operation and the warnings are ignored. The performance document must already exist.

Loading Performance Documents

This example PerfDocComplete.dat file creates a performance document for a specified worker assignment.

METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|StartDate|EndDate|Operation|ManagerAssignmentNumber
MERGE|PerfDocComplete|E121468|Annual Evaluation|2023/01/01|2023/12/31|ORA_CREATE_PD|EEEE8153756

The performance template contains default values for start date, end date, and manager assignment number that populate when you create the document. To override the defaults, simply provide your own values in the .dat file.

Note:

If you need to mass update participants or attachments, you must delete and load them again using HCM Data Loader.

This example PerfDocComplete.dat file reopens a performance document for a specified worker assignment.

METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|Operation
MERGE|PerfDocComplete|E955160008191842|2026 Review Period|ORA_REOPEN_PD

Loading Attachments

This example PerfDocComplete.dat file loads an attachment to an existing performance document.

METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|Operation
MERGE|PerfDocComplete|EEEE8153772|Annual Evaluation|ORA_ATTACH_PD
METADATA|Attachment|CustomaryName|AssignmentNumber|Title|DataTypeCode|URLorTextorFileName|MimeType|File|Description
MERGE|Attachment|Annual Evaluation|EEEE8153772|JBlum Resume|FILE|jblum.txt|text/plain|jblum.txt|Jorge Blum Resume

These rules apply when you load attachments:

  • You must include the parent performance document in the PerfDocComplete.dat file. Set the Operation attribute to ORA_ATTACH_PD for both MERGE and DELETE instructions for the Attachment component.

  • The MimeType value is the Multipurpose Internet Mail Extensions (MIME) value, as defined and standardized by the Internet Engineering Task Force in RFC 6838.

  • The attachment itself is a binary large object, referenced by the File attribute. You include the attachment in the BlobFiles folder in the .zip file that you upload.

  • You can only bulk delete attachments and load them again. Update action isn't supported.

Loading Participants

This example PerfDocComplete.dat file deletes a participant record from an existing performance document.

METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|Operation
MERGE|PerfDocComplete|EEEE8153772|Annual Evaluation|ORA_ADD_PARTICIPANT
METADATA|Participant|AssignmentNumber|CustomaryName|ParticipantRoleTypeCode|ParticipantPersonNumber
DELETE|Participant|EEEE8153772|Annual Evaluation|Colleague|ZHRA-8154961

These rules apply when you load participants:

  • When you create participants, the parent performance document must already exist. You can't perform two actions on the .dat file. For example, you can’t create performance document and add a participant in the same PerfDocComplete.dat file.
  • You must include the parent performance document in the PerfDocComplete.dat file. Set the Operation attribute to ORA_ADD_PARTICIPANT for both MERGE and DELETE instructions for the Participants component.
  • The participant person record, as identified by the ParticipantPersonNumber attribute value, must already exist.
  • The ParticipantRoleTypeCode value must have been selected in the performance template.
  • You can only bulk delete participants and load them again. Update action isn't supported.
  • When deleting participants in a performance document, you must set the ForceDelete optional parameter to Y if the feedback status is anything other than Request Not Sent (REQUEST_NOT_SENT) or Not Started (NOTSTR). This additional parameter ensures the user understands that completed feedback is deleted and can't be recovered.
  • If you want the participant to be sent a notification to provide feedback as part of the data load, set the Send Notifications to Mass Load Participants process to Yes. You can enter a message for the notification in the Message attribute.

Loading Performance Document Section Ratings and Comments

This example PerfDocComplete.dat file updates existing section ratings and comments of worker, manager, and participants. This applies to all sections where section ratings or comments, or both section ratings and comments, are enabled.

METADATA|PerfDocComplete|AssignmentNumber|CustomaryName|Operation
MERGE|PerfDocComplete|EEEE8153805|360 WKR and MGR allow to select and request participants-2017|ORA_RATING_PD
METADATA|RatingsAndComments|AssignmentNumber|CustomaryName|ParticipantPersonNumber|ParticipantRoleTypeCode|SectionName|SectionTypeCode|RatingName|Comments
MERGE|RatingsAndComments|EEEE8153805|360 WKR and MGR allow to select and request participants-2017|8153793|Manager|ZHRA-Competency Section|REG|ZHRA-Outstanding|Manager Comments
MERGE|RatingsAndComments|EEEE8153805|360 WKR and MGR allow to select and request participants-2017|8153818|Worker|ZHRA-Competency Section|REG|ZHRA-Expert|Worker Comments

These are the general considerations for loading performance document section ratings and comments:

  • You can use HDL to load performance document section ratings and comments when more than one performance document needs updating.
  • You can only update goal or competency section and overall summary ratings, and section comments.
  • Use the update action to enter, change, or remove section ratings and comments.