{"id":31200,"date":"2026-01-06T08:28:21","date_gmt":"2026-01-06T08:28:21","guid":{"rendered":"http:\/\/kovaion-new1.local\/generating-employment-agreement-letter-through-the-checklist\/"},"modified":"2026-01-06T12:49:14","modified_gmt":"2026-01-06T12:49:14","slug":"generating-employment-agreement-letter-through-the-checklist","status":"publish","type":"post","link":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/generating-employment-agreement-letter-through-the-checklist\/","title":{"rendered":"Generating Employment Agreement Letter Through the Checklist"},"content":{"rendered":"

Within Oracle HCM Cloud, users possess the capability to generate an offer letter or agreement letter through the ORC<\/a> <\/strong><\/span>feature. However, it is essential to note that this generation can only occur once. Once the candidate transitions into an employee, should the business team require additional documents, such as an employment agreement or other types of letters, those letters will be sent to the employee accompanied by a notification. These letters will then be securely stored as attachments in the Oracle HCM Cloud, serving as Document of Records (DOR) attachments.<\/p>\n

This functionality enables employees to conveniently download the letter, sign it, and subsequently upload it back to the document of records. By leveraging this feature, the business team can effectively utilize it as a repository to easily download any necessary letters while on the go, as needed.<\/p>\n

 <\/p>\n

Case Study of the Employee Agreement Letter Through the Checklist:<\/h2>\n

To grasp the functionality of the “Generate Employee Agreement Letter Through the Checklist” feature, let’s examine an example: When hiring a candidate, the business team can generate and send an offer letter to the employee. However, they cannot trigger both the offer and agreement letters simultaneously. This action can only be carried out once the candidate successfully transitions into an employee.<\/p>\n

The business team aims to send an agreement letter to each candidate, containing the relevant details. Subsequently, employees will receive a notification prompting them to sign the document and upload it back to the Document of Records (DOR)<\/a>.<\/strong><\/span> This feature proves particularly advantageous when generating a large number of letters for employees in similar situations.<\/p>\n

 <\/p>\n

Steps to enable the “Generate Employee Agreement Letter Through the Checklist” feature:<\/h3>\n

Step 1:<\/strong> Navigate to reports and analytics<\/span> and create a report using <\/span>the <\/span>RTF template<\/span> with the SQL query (as per requirement) <\/span>provided<\/span> below. <\/span>Make sure that <\/span>the report<\/span> is<\/span> in <\/span>the <\/span>shared folder \/Custom folder<\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n

\"Generating-Employment-
Fig.1: SQL code execution area for report creation. <\/strong><\/figcaption><\/figure>\n

 <\/p>\n

SQL Code:<\/h4>\n

Select distinct<\/span><\/p>\n

papf.person_number emp_no,<\/span><\/p>\n

PPNF.DISPLAY_NAME emp_name,<\/span><\/p>\n

job.DESIGNATION,<\/span><\/p>\n

pct.name checklist_name,<\/span><\/p>\n

patt.task_name<\/span><\/p>\n

from<\/span><\/p>\n

per_all_people_f papf,<\/span><\/p>\n

PER_PERSON_NAMES_F ppnf,<\/span><\/p>\n

PER_ALL_ASSIGNMENTS_M PAAM,<\/span><\/p>\n

per_allocated_checklists pac,<\/span><\/p>\n

PER_CHECKLISTS_TL pct,<\/span><\/p>\n

per_allocated_tasks pat,<\/span><\/p>\n

PER_ALLOCATED_TASKS_TL patt,<\/span><\/p>\n

(select distinct PJ.JOB_ID id,<\/span><\/p>\n

PJ.NAME DESIGNATION<\/span><\/p>\n

from<\/span><\/p>\n

PER_JOBS_F_TL PJ,<\/span><\/p>\n

PER_ALL_ASSIGNMENTS_M PAAM<\/span><\/p>\n

where<\/span><\/p>\n

1=1<\/span><\/p>\n

AND PJ.JOB_ID = PAAM.JOB_ID<\/span><\/p>\n

and trunc(sysdate) between PJ.effective_start_date and PJ.effective_end_date<\/span><\/p>\n

and trunc(sysdate) between paam.effective_start_date and paam.effective_end_date<\/span><\/p>\n

) Job<\/span><\/p>\n

where<\/span><\/p>\n

1=1<\/span><\/p>\n

and papf.person_id = ppnf.person_id<\/span><\/p>\n

and papf.person_id = paam.person_id<\/span><\/p>\n

and paam.person_id = pac.person_id<\/span><\/p>\n

and pct.CHECKLIST_ID = pac.CHECKLIST_ID<\/span><\/p>\n

and pac.allocated_checklist_id = pat.allocated_checklist_id<\/span><\/p>\n

and pat.allocated_task_id = patt.allocated_task_id<\/span><\/p>\n

and job.id (+) = PAAM.job_id<\/span><\/p>\n

AND PPNF.NAME_TYPE = ‘GLOBAL’<\/span><\/p>\n

AND PAAM.ASSIGNMENT_TYPE = ‘E’<\/span><\/p>\n

AND paam.assignment_status_type = ‘ACTIVE’<\/span><\/p>\n

and patt.task_name like ‘agreement%’<\/span><\/p>\n

and patt.language = sys_context(‘userenv’,’lang’)<\/span><\/p>\n

and pat.allocated_task_id = nvl(:P_ALLOCATED_TASK_ID, (case when pat.status!=’COM’ then pat.allocated_task_id end))<\/span><\/p>\n

and trunc(sysdate) between papf.effective_start_date and papf.effective_end_date<\/span><\/p>\n

and trunc(sysdate) between ppnf.effective_start_date and ppnf.effective_end_date<\/span><\/p>\n

and trunc(sysdate) between paam.effective_start_date and paam.effective_end_date<\/span><\/p>\n

–and papf.person_number = ‘XXXX’<\/span><\/p>\n

 <\/p>\n

Step 2:<\/strong> Create a report using the RTF<\/a><\/strong><\/span> template<\/p>\n

\"Generating-Employment-Agreement-
Fig.2: Report Path<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

Step 3:<\/strong> Create a document type with a report path.<\/p>\n

Navigate to setup and maintenance, search for Document Types then create a document type by providing the report path as mentioned below. so, that user will be able to see the document in the checklist.<\/p>\n

Report path: \/Custom\/Nanda\/agrrement details.xdo?P_ALLOCATED_TASK_ID={AllocatedTaskId}<\/p>\n

\"Generating-Employment-Agreement-
Fig.3: Document type creation<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

Step 4:<\/strong> Create a checklist.<\/p>\n

Navigate to setup and maintenance, search for \u201cchecklist templates\u201d then create a checklist template by giving the action name such as \u2018\u2019Hire\u2019\u2019 (as per requirement)<\/p>\n

\"Generating-Employment-Agreement-
Fig.4: Checklist Template<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

Step 5:<\/strong> Create a checklist task.<\/p>\n

Navigate to the task tab, click Create, and provide the details below.<\/p>\n

 <\/p>\n

Task Type:<\/strong> Report<\/p>\n

Report path:<\/strong> \/Custom\/Nanda\/agrrement details.xdo?P_ALLOCATED_TASK_ID={AllocatedTaskId}<\/p>\n

Document Type:<\/strong> Select the document type that has been created<\/p>\n

Document Are For:<\/strong> Select Performer<\/p>\n

Attachments:<\/strong> Enable<\/p>\n

Add Attachment to Document of Record:<\/strong> Select the document type that has been created<\/p>\n

Attachment Are for:<\/strong> Performer<\/p>\n

\"Generating-Employment-Agreement-
Fig.5: Check Task<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

Step 6:<\/strong> Hire an employee<\/p>\n

Once the business team hires a candidate checklist will get a trigger and the employee is able to access the document in the journey or through the checklist.<\/p>\n

\"Generating-Employment-Agreement-
Fig.6: Checklist Template<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

 <\/p>\n

\"Generating-Employment-Agreement-
Fig.7: Task Tab<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

Click on See Document, and the letter will get downloaded. Once the document gets downloaded employee can view the generated letter, and the employee can sign it, and upload it back (Drag and Drop). So, the document will get stored in the document of record, and the business team can access the document from the document of record section.<\/p>\n

\"Generating-Employment-Agreement-
Fig.8: Document of Record Section<\/strong><\/figcaption><\/figure>\n

 <\/p>\n

Business Benefits<\/strong><\/h3>\n
    \n
  • A significant benefit of this feature is the generation of bulk letters tailored to individual employee details, thereby streamlining the efforts of the business team.<\/li>\n
  • As a default setting, the letters will be securely stored as attachments within the person’s document of record section.<\/li>\n
  • The business team retains the ability to conveniently access the document letters at any given time.<\/li>\n<\/ul>\n

     <\/p>\n

    Limitations<\/strong><\/h3>\n
      \n
    • The business team cannot generate multiple letters for the same employee at a time using one checklist task. This means that if the business team needs to generate multiple employment agreement letters for the same employee, they would need to initiate separate checklist tasks for each letter to be generated.<\/li>\n<\/ul>\n

       <\/p>\n

      The Bottom Line<\/h3>\n

      Overall, with the “Generating Employment Agreement Letter Through the Checklist” feature in Oracle HCM Cloud, businesses can streamline their document generation process, improve efficiency, and ensure that employment agreements are accurately generated and securely stored, ultimately facilitating a smoother onboarding experience for new employees.<\/p>\n

       <\/p>\n

      Author:\u00a0 <\/strong>Nanda Patil, Associate Consultant<\/p>\n","protected":false},"excerpt":{"rendered":"

      Within Oracle HCM Cloud, users possess the capability to generate an offer letter or agreement letter through the ORC feature. However, it is essential to note that this generation can only occur once. Once the candidate transitions into an employee, should the business team require additional documents, such as an employment agreement or other types […]<\/p>\n","protected":false},"author":1,"featured_media":24982,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[18],"tags":[],"class_list":["post-31200","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oracle-hcm"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/31200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/comments?post=31200"}],"version-history":[{"count":1,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/31200\/revisions"}],"predecessor-version":[{"id":31201,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/31200\/revisions\/31201"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/media\/24982"}],"wp:attachment":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/media?parent=31200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/categories?post=31200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/tags?post=31200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}