Category Archives: oracle apps hrms

Download IRecruitment Resumes in Server and in client(TOAD)

We had a requirement from user that to download and process all the resume.

So When checked with the Doc ID 1578603.1 it tells that we can Download Resume as there is no Inbuild Tool but we can write Queries If Any. The uploaded resumes can be found in table IRC_DOCUMENTS via the column CHARACTER_DOC which is of type CLOB.

On Toad We can See below as Save to File Option by which we can download and give the same name as FILE_NAME Column to the Document.

 

Now we are going to download the same on server in bulk and Implementing for many records below is the script.

Steps to download in Server

Step: 1

CREATE DIRECTORY datadump AS ‘E:\datadump\test’;

Create a Directory with Server path by SYS user in database. As the above command is for windows server. In case your Environment is Linux use the correct path accordingly.

Step: 2

grant read, write on directory DATADUMP to apps

Grant Read, Write access to the Directory

Step: 3 Verify

select directory_path from all_directories where directory_name = ‘DATADUMP’;

SELECT * FROM all_tab_privs WHERE table_name = ‘DATADUMP’;

Check whether the directory has been created correctly  and access has been given correctly.

Step: 4 Query to retrive the records.

SELECT PPF.FULL_NAME AS PERSON_NAME,
PPF.EMAIL_ADDRESS,
PPF.DATE_OF_BIRTH,
PAV.NAME AS VACANCY_NAME,
DOC.DOCUMENT_ID,
DOC.BINARY_DOC,
DOC.FILE_NAME
FROM PER_ALL_PEOPLE_F PPF,
PER_ALL_ASSIGNMENTS_F PAF,
PER_ALL_VACANCIES PAV,
IRC_ASSIGNMENT_STATUSES IAS,
PER_ASSIGNMENT_STATUS_TYPES_V AST,
IRC_DOCUMENTS DOC,
IRC_NOTIFICATION_PREFERENCES INP
WHERE sysdate BETWEEN PPF.EFFECTIVE_START_DATE
AND PPF.EFFECTIVE_END_DATE
AND PPF.PERSON_ID = PAF.PERSON_ID
AND PAF.VACANCY_ID = PAV.VACANCY_ID
AND PAF.ASSIGNMENT_ID = IAS.ASSIGNMENT_ID
AND pav.name = p_vac_name
AND ias.ASSIGNMENT_STATUS_TYPE_ID = ‘4’ –Active Application
AND irc_utilities_pkg.GET_RECRUITMENT_PERSON_ID (PPF.PERSON_ID) =
INP.person_id(+)
AND INP.PERSON_ID = DOC.PERSON_ID(+)
AND IAS.ASSIGNMENT_STATUS_TYPE_ID = AST.ASSIGNMENT_STATUS_TYPE_ID(+)
AND doc.TYPE(+) LIKE ‘%RESUME’
AND doc.end_date(+) IS NULL;

Step: 5 Execute the Below Script

DECLARE
l_file UTL_FILE.FILE_TYPE;
l_buffer RAW (32767);
l_amount BINARY_INTEGER := 32767;
l_pos number := 1;
l_blob BLOB;
l_blobname VARCHAR2 (50);
l_blob_len number;
ctrl number;
— p_vac_name varchar2(100):=’IRC110′;

cursor c_irc_doc(p_vac_name in varchar) is SELECT PPF.FULL_NAME AS PERSON_NAME,
PPF.EMAIL_ADDRESS,
PPF.DATE_OF_BIRTH,
PAV.NAME AS VACANCY_NAME,
DOC.DOCUMENT_ID,
DOC.BINARY_DOC,
DOC.FILE_NAME
FROM PER_ALL_PEOPLE_F PPF,
PER_ALL_ASSIGNMENTS_F PAF,
PER_ALL_VACANCIES PAV,
IRC_ASSIGNMENT_STATUSES IAS,
PER_ASSIGNMENT_STATUS_TYPES_V AST,
IRC_DOCUMENTS DOC,
IRC_NOTIFICATION_PREFERENCES INP
WHERE sysdate BETWEEN PPF.EFFECTIVE_START_DATE
AND PPF.EFFECTIVE_END_DATE
AND PPF.PERSON_ID = PAF.PERSON_ID
AND PAF.VACANCY_ID = PAV.VACANCY_ID
AND PAF.ASSIGNMENT_ID = IAS.ASSIGNMENT_ID
AND pav.name = p_vac_name
AND ias.ASSIGNMENT_STATUS_TYPE_ID = ‘4’ –Active Application
AND irc_utilities_pkg.GET_RECRUITMENT_PERSON_ID (PPF.PERSON_ID) =
INP.person_id(+)
AND INP.PERSON_ID = DOC.PERSON_ID(+)
AND IAS.ASSIGNMENT_STATUS_TYPE_ID = AST.ASSIGNMENT_STATUS_TYPE_ID(+)
AND doc.TYPE(+) LIKE ‘%RESUME’
AND doc.end_date(+) IS NULL;

BEGIN

FOR i in c_irc_doc loop(‘IRC110’)–Position Name for taking the Resume

l_blob_len := DBMS_LOB.getlength(i.binary_doc);
l_file := UTL_FILE.fopen(‘APPS_DATA_FILE_DIR’,i.file_name,’WB’, 32767);
— Read chunks of the BLOB and write them to the file created in directory until complete.
WHILE l_pos < l_blob_len LOOP
DBMS_LOB.read(i.binary_doc, l_amount, l_pos, l_buffer);
UTL_FILE.put_raw(l_file, l_buffer, TRUE);
l_pos := l_pos + l_amount;
END LOOP; — This will end the While loop when condition met.
l_blob_len :=0;
l_pos :=1;
— Close the file.
UTL_FILE.fclose(l_file);
end loop; — This will end the FOR loop when all BLOB files in the table have been downloaded.
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line(‘Exception’||SQLERRM||SQLCODE);
— Close the file if something goes wrong.
IF UTL_FILE.is_open(l_file) THEN
UTL_FILE.fclose(l_file);
END IF;
–RAISE;
END;
/

 

Steps to download in TOAD

Execute the Query in the Step : 4

Now click on Binary Doc Column and right click Single Column Export

 

Now give the path and Column of the Value to be renamed for File

 

Then Export will be downloaded.

Now the Resumes will be downloaded in the mentioned path.

TOAD 12 is faster for Exporting Blob than in Server.

If you have an older version of Toad, it’s called “Export BLOBs (long,raw)” instead.

Happy resume Exporting….

Advertisements

Making a responsibility as Read Only in Oracle Applications

We have to set two Profile options in Responsibility to make as read only and it is applicable for only HR responsibilities.

Login user with System Administrator responsibility and navigate to Profile-> System menu as shown below in the picture

HR: User type

HR:Query Only Mode

 

 

User Hooks in Oracle Apps for comments validation

I had a requirement to Validate the comments for certain leave types. So I first try to do the same in BG_ABSENCE_DURATION Fast formula. However I was facing some problem that is

  • Not able to capture comments or Absence Attendance Id in fast formula
  • While clicking on next only the record will get created and comments will be passed still it was complex to write logic in FF

So I went with User Hooks.

In simple words user hooks is functionality provided in Oracle HRMS for validating or extending our custom functionality based on business rules.

What we can do with user hooks is : Validate EIT, SIT, Absence and manipulate and maintain the data for Oracle to our tables

Attention: You should not manually edit the API source code files supplied by Oracle If you do modify these codes, Oracle Applications will be unable to support the product, and upgrades may not be possible. Oracle Applications only supports direct calls to the published APIs. Direct calls to any other server-side package procedures or functions that are written as part of the Oracle HRMS Applications suite are not supported.

Note: All Oracle HRMS forms does not use HRMS APIs, User hook can be implemented for only those forms which perform functions through API. The HR_API_HOOKS table holds all available API hooks for APIs in HR_API_MODULES table.

Implementation Steps For User Hooks

Four steps are required to implement API User Hooks:

Step 1 – Identifying the correct User Hook API

SELECT ahk.api_hook_id,
ahk.api_module_id,
ahk.hook_package,
ahk.hook_procedure
FROM hr_api_hooks ahk, hr_api_modules ahm
WHERE ahm.module_name like ‘%_PERSON_ABSENCE%’
AND ahm.api_module_type = ‘BP’
AND ahk.api_hook_type = ‘AP’
AND ahk.api_module_id = ahm.api_module_id

It will show all Person Absence relevant APIs.We need to select the correct API that matched with our requirement. For Example for above mentioned requirement, we shall select CREATE_PERSON_ABSENCE_A API. We shall note its API_HOOK_ID (3840) and API_MODULE_ID (1731) as API_HOOK_ID will be used at the time of registration of user hook mentioned in Step 3 ahead and API_MODULE_ID will be needed in running the processor in Step 4.

Step 2. Create PL/SQL procedure to execute your logic.

CREATE OR REPLACE PACKAGE APPS.XXHW_ABS_USERHOOK_PKG
AS
PROCEDURE XXHW_CREATE_ABS_VAL_P
(P_EFFECTIVE_DATE in DATE
,P_PERSON_ID in NUMBER
,P_BUSINESS_GROUP_ID in NUMBER
,P_ABSENCE_ATTENDANCE_TYPE_ID in NUMBER
,P_ABS_ATTENDANCE_REASON_ID in NUMBER
,P_COMMENTS in LONG
,P_DATE_NOTIFICATION in DATE
,P_DATE_PROJECTED_START in DATE
,P_TIME_PROJECTED_START in VARCHAR2
,P_DATE_PROJECTED_END in DATE
,P_TIME_PROJECTED_END in VARCHAR2
,P_DATE_START in DATE
,P_TIME_START in VARCHAR2
,P_DATE_END in DATE
,P_TIME_END in VARCHAR2
,P_ABSENCE_DAYS in NUMBER
,P_ABSENCE_HOURS in NUMBER
,P_AUTHORISING_PERSON_ID in NUMBER
,P_REPLACEMENT_PERSON_ID in NUMBER
,P_ATTRIBUTE_CATEGORY in VARCHAR2
,P_ATTRIBUTE1 in VARCHAR2
,P_ATTRIBUTE2 in VARCHAR2
,P_ATTRIBUTE3 in VARCHAR2
,P_ATTRIBUTE4 in VARCHAR2
,P_ATTRIBUTE5 in VARCHAR2
,P_ATTRIBUTE6 in VARCHAR2
,P_ATTRIBUTE7 in VARCHAR2
,P_ATTRIBUTE8 in VARCHAR2
,P_ATTRIBUTE9 in VARCHAR2
,P_ATTRIBUTE10 in VARCHAR2
,P_ATTRIBUTE11 in VARCHAR2
,P_ATTRIBUTE12 in VARCHAR2
,P_ATTRIBUTE13 in VARCHAR2
,P_ATTRIBUTE14 in VARCHAR2
,P_ATTRIBUTE15 in VARCHAR2
,P_ATTRIBUTE16 in VARCHAR2
,P_ATTRIBUTE17 in VARCHAR2
,P_ATTRIBUTE18 in VARCHAR2
,P_ATTRIBUTE19 in VARCHAR2
,P_ATTRIBUTE20 in VARCHAR2
,P_OCCURRENCE in NUMBER
,P_PERIOD_OF_INCAPACITY_ID in NUMBER
,P_SSP1_ISSUED in VARCHAR2
,P_MATERNITY_ID in NUMBER
,P_SICKNESS_START_DATE in DATE
,P_SICKNESS_END_DATE in DATE
,P_PREGNANCY_RELATED_ILLNESS in VARCHAR2
,P_REASON_FOR_NOTIFICATION_DELA in VARCHAR2
,P_ACCEPT_LATE_NOTIFICATION_FLA in VARCHAR2
,P_LINKED_ABSENCE_ID in NUMBER
,P_BATCH_ID in NUMBER
,P_CREATE_ELEMENT_ENTRY in BOOLEAN
,P_ABS_INFORMATION_CATEGORY in VARCHAR2
,P_ABS_INFORMATION1 in VARCHAR2
,P_ABS_INFORMATION2 in VARCHAR2
,P_ABS_INFORMATION3 in VARCHAR2
,P_ABS_INFORMATION4 in VARCHAR2
,P_ABS_INFORMATION5 in VARCHAR2
,P_ABS_INFORMATION6 in VARCHAR2
,P_ABS_INFORMATION7 in VARCHAR2
,P_ABS_INFORMATION8 in VARCHAR2
,P_ABS_INFORMATION9 in VARCHAR2
,P_ABS_INFORMATION10 in VARCHAR2
,P_ABS_INFORMATION11 in VARCHAR2
,P_ABS_INFORMATION12 in VARCHAR2
,P_ABS_INFORMATION13 in VARCHAR2
,P_ABS_INFORMATION14 in VARCHAR2
,P_ABS_INFORMATION15 in VARCHAR2
,P_ABS_INFORMATION16 in VARCHAR2
,P_ABS_INFORMATION17 in VARCHAR2
,P_ABS_INFORMATION18 in VARCHAR2
,P_ABS_INFORMATION19 in VARCHAR2
,P_ABS_INFORMATION20 in VARCHAR2
,P_ABS_INFORMATION21 in VARCHAR2
,P_ABS_INFORMATION22 in VARCHAR2
,P_ABS_INFORMATION23 in VARCHAR2
,P_ABS_INFORMATION24 in VARCHAR2
,P_ABS_INFORMATION25 in VARCHAR2
,P_ABS_INFORMATION26 in VARCHAR2
,P_ABS_INFORMATION27 in VARCHAR2
,P_ABS_INFORMATION28 in VARCHAR2
,P_ABS_INFORMATION29 in VARCHAR2
,P_ABS_INFORMATION30 in VARCHAR2
,P_ABSENCE_ATTENDANCE_ID in NUMBER
,P_OBJECT_VERSION_NUMBER in NUMBER
);
END XXHW_ABS_USERHOOK_PKG;

 

CREATE OR REPLACE PACKAGE BODY APPS.XXHW_ABS_USERHOOK_PKG
IS
PROCEDURE XXHW_CREATE_ABS_VAL_P (
P_EFFECTIVE_DATE IN DATE,
P_PERSON_ID IN NUMBER,
P_BUSINESS_GROUP_ID IN NUMBER,
P_ABSENCE_ATTENDANCE_TYPE_ID IN NUMBER,
P_ABS_ATTENDANCE_REASON_ID IN NUMBER,
P_COMMENTS IN LONG,
P_DATE_NOTIFICATION IN DATE,
P_DATE_PROJECTED_START IN DATE,
P_TIME_PROJECTED_START IN VARCHAR2,
P_DATE_PROJECTED_END IN DATE,
P_TIME_PROJECTED_END IN VARCHAR2,
P_DATE_START IN DATE,
P_TIME_START IN VARCHAR2,
P_DATE_END IN DATE,
P_TIME_END IN VARCHAR2,
P_ABSENCE_DAYS IN NUMBER,
P_ABSENCE_HOURS IN NUMBER,
P_AUTHORISING_PERSON_ID IN NUMBER,
P_REPLACEMENT_PERSON_ID IN NUMBER,
P_ATTRIBUTE_CATEGORY IN VARCHAR2,
P_ATTRIBUTE1 IN VARCHAR2,
P_ATTRIBUTE2 IN VARCHAR2,
P_ATTRIBUTE3 IN VARCHAR2,
P_ATTRIBUTE4 IN VARCHAR2,
P_ATTRIBUTE5 IN VARCHAR2,
P_ATTRIBUTE6 IN VARCHAR2,
P_ATTRIBUTE7 IN VARCHAR2,
P_ATTRIBUTE8 IN VARCHAR2,
P_ATTRIBUTE9 IN VARCHAR2,
P_ATTRIBUTE10 IN VARCHAR2,
P_ATTRIBUTE11 IN VARCHAR2,
P_ATTRIBUTE12 IN VARCHAR2,
P_ATTRIBUTE13 IN VARCHAR2,
P_ATTRIBUTE14 IN VARCHAR2,
P_ATTRIBUTE15 IN VARCHAR2,
P_ATTRIBUTE16 IN VARCHAR2,
P_ATTRIBUTE17 IN VARCHAR2,
P_ATTRIBUTE18 IN VARCHAR2,
P_ATTRIBUTE19 IN VARCHAR2,
P_ATTRIBUTE20 IN VARCHAR2,
P_OCCURRENCE IN NUMBER,
P_PERIOD_OF_INCAPACITY_ID IN NUMBER,
P_SSP1_ISSUED IN VARCHAR2,
P_MATERNITY_ID IN NUMBER,
P_SICKNESS_START_DATE IN DATE,
P_SICKNESS_END_DATE IN DATE,
P_PREGNANCY_RELATED_ILLNESS IN VARCHAR2,
P_REASON_FOR_NOTIFICATION_DELA IN VARCHAR2,
P_ACCEPT_LATE_NOTIFICATION_FLA IN VARCHAR2,
P_LINKED_ABSENCE_ID IN NUMBER,
P_BATCH_ID IN NUMBER,
P_CREATE_ELEMENT_ENTRY IN BOOLEAN,
P_ABS_INFORMATION_CATEGORY IN VARCHAR2,
P_ABS_INFORMATION1 IN VARCHAR2,
P_ABS_INFORMATION2 IN VARCHAR2,
P_ABS_INFORMATION3 IN VARCHAR2,
P_ABS_INFORMATION4 IN VARCHAR2,
P_ABS_INFORMATION5 IN VARCHAR2,
P_ABS_INFORMATION6 IN VARCHAR2,
P_ABS_INFORMATION7 IN VARCHAR2,
P_ABS_INFORMATION8 IN VARCHAR2,
P_ABS_INFORMATION9 IN VARCHAR2,
P_ABS_INFORMATION10 IN VARCHAR2,
P_ABS_INFORMATION11 IN VARCHAR2,
P_ABS_INFORMATION12 IN VARCHAR2,
P_ABS_INFORMATION13 IN VARCHAR2,
P_ABS_INFORMATION14 IN VARCHAR2,
P_ABS_INFORMATION15 IN VARCHAR2,
P_ABS_INFORMATION16 IN VARCHAR2,
P_ABS_INFORMATION17 IN VARCHAR2,
P_ABS_INFORMATION18 IN VARCHAR2,
P_ABS_INFORMATION19 IN VARCHAR2,
P_ABS_INFORMATION20 IN VARCHAR2,
P_ABS_INFORMATION21 IN VARCHAR2,
P_ABS_INFORMATION22 IN VARCHAR2,
P_ABS_INFORMATION23 IN VARCHAR2,
P_ABS_INFORMATION24 IN VARCHAR2,
P_ABS_INFORMATION25 IN VARCHAR2,
P_ABS_INFORMATION26 IN VARCHAR2,
P_ABS_INFORMATION27 IN VARCHAR2,
P_ABS_INFORMATION28 IN VARCHAR2,
P_ABS_INFORMATION29 IN VARCHAR2,
P_ABS_INFORMATION30 IN VARCHAR2,
P_ABSENCE_ATTENDANCE_ID IN NUMBER,
P_OBJECT_VERSION_NUMBER IN NUMBER)
IS
L_ABSENCE_TYPE VARCHAR2 (500) := NULL;
L_ASSIGNMENT_ID NUMBER;
L_ABSENCE_START_DATE DATE
:= NVL (P_DATE_START, P_DATE_PROJECTED_START);
L_ABSENCE_END_DATE DATE := NVL (P_DATE_END, P_DATE_PROJECTED_END);
L_ABSENCE_FUTURE_ST_DATE DATE;
L_ABSENCE_FUTURE_END_DATE DATE;
LN_LENGTH NUMBER := 0;
LC_MSG VARCHAR2 (500);
BEGIN
IF P_ABSENCE_ATTENDANCE_TYPE_ID IN (4085, 4086, 4087, 4088)
THEN
LN_LENGTH := NVL (LENGTH (TO_CHAR (P_COMMENTS)), 0);

IF LN_LENGTH <= 1
THEN
LC_MSG := ‘Comments are Mandatory’;
HR_UTILITY.SET_MESSAGE (800, LC_MSG);
HR_UTILITY.RAISE_ERROR;
END IF;
ELSE
NULL;
END IF;
END XXHW_CREATE_ABS_VAL_P;
END XXHW_ABS_USERHOOK_PKG;

3. Register your procedure with one or more specific user hooks.

We shall use the API_HOOK_ID identified in Step 1 in the parameter p_api_hook_id. Through this API, custom logic will be registered against user hook.

DECLARE
L_API_HOOK_ID NUMBER := 3840;
L_API_HOOK_CALL_ID NUMBER;
L_OBJECT_VERSION_NUMBER NUMBER;
L_SEQUENCE NUMBER;
BEGIN
SELECT HR_API_HOOKS_S.NEXTVAL INTO L_SEQUENCE FROM DUAL;

HR_API_HOOK_CALL_API.CREATE_API_HOOK_CALL (
P_VALIDATE => FALSE,
P_EFFECTIVE_DATE => SYSDATE – 10,
P_API_HOOK_ID => L_API_HOOK_ID,
P_API_HOOK_CALL_TYPE => ‘PP’,
P_SEQUENCE => L_SEQUENCE,
P_ENABLED_FLAG => ‘Y’,
P_CALL_PACKAGE => ‘XXHW_ABS_USERHOOK_PKG’, –CUSTOM PACKAGE
P_CALL_PROCEDURE => ‘XXHW_CREATE_ABS_VAL_P’, — CUSTOM PROCEDURE
P_API_HOOK_CALL_ID => L_API_HOOK_CALL_ID,
P_OBJECT_VERSION_NUMBER => L_OBJECT_VERSION_NUMBER);
DBMS_OUTPUT.PUT_LINE (‘L_API_HOOK_CALL_ID ‘ || L_API_HOOK_CALL_ID);
END;

 

After this step, you shall be able to see the reference of your custom package/ procedure in table HR_API_HOOK_CALLS. You can check it by using following query

SELECT *
FROM HR_API_HOOK_CALLS
WHERE api_hook_id = 3840;

4. Run the pre-processor program

Run pre-processor script hrahkone.sql with module name as parameter (PER_TOP/admin/sql/hrahkone.sql).It compile API hook. After running this your APIhook Package should have custom procedure call.

or

DECLARE
L_API_MODULE_ID NUMBER := 1731;
BEGIN
HR_API_USER_HOOKS_UTILITY.CREATE_HOOKS_ONE_MODULE (L_API_MODULE_ID);
DBMS_OUTPUT.PUT_LINE (‘Success’);
EXCEPTION
WHEN OTHERS
THEN
DBMS_OUTPUT.PUT_LINE (‘Exception : ‘ || SQLERRM);
END;

Alternately you can use the following API to run the pre-processor

At this level, your user hook is implemented and should work as per your requriement.
If you change your custom package body, you dont need to run the pre-processor again but if you change the procedure signature, you will need to run the pre-processory again,

 

Delete custom code from APIuser Hook

Get Hook Call ID and Object Version_number

SELECT api_hook_call_id,object_version_number
FROM HR_API_HOOK_CALLS
WHERE call_package = ‘LSG_USERHOOK_PKG’
AND call_procedure = UPPER(‘LSG_CREATE_ABS_VAL_P’)

DECLARE
L_API_MODULE_ID NUMBER := 1731;
BEGIN
HR_API_USER_HOOKS_UTILITY.CREATE_HOOKS_ONE_MODULE (L_API_MODULE_ID);
DBMS_OUTPUT.PUT_LINE (‘Success’);
EXCEPTION
WHEN OTHERS
THEN
DBMS_OUTPUT.PUT_LINE (‘Exception : ‘ || SQLERRM);
END;

Note : In case if you are facing any error cross check the same parameters are there in the seeded package.

Source learned from

Thank You.

Process for Reversal of Payroll when Journal is Posted

We had a Issue that HR was testing Payroll for a user but unfortunately Finance had done costing and they have posted to GL.

I had many things running in my mind that whether we will be able to roll back all the process or what can be done to resolve this as Finance has posted and it should be also reversed. After that with help of my collegue we have done this.

Reversal in HRMS allows to reverse the Entries in Costing which nullifies the amount.

Example :

Basic Salary Pay Value 01.00.00000.000.32110.000.0000.0000 Credit

In the above table the first one which will be as credit to Employee. So once we done reversal and costing we will get the record as below so Now the credit amount and debit amount gets nullified

Basic Salary Pay Value 01.00.00000.000.32110.000.0000.0000 Debit

Only reversal can be used after post payroll process and retry will not work after post payroll process. The steps are as follows.

Step 1: Reversal of the Payroll

Select the employee whom we have to rollback/reverse

Nav : Fastpath –> Reverse Payroll Run –> Select the Employee –
Check the Employee and the reversal as shown below

Step 2: Make sure the Reversal has applied.

Global HRMS Manager –> View –> Assignment Process Results

 

Step 3 : Check the Costing Detail Report whether there is a reflection

select * from pay_costing_details_v where effective_date between :p_frm_date and :p_to_date and EMPLOYEE_NUMBER = ‘005225’

Step 4 : Costing process.

As costing entries were not yet created not we have costing process.

So run the costing process

Step 5: Check the Costing Detail Report

Once Costing Process is done now check the reverse of the entry has been created.

Cross check the same using costing detail report or by the below query

select * from pay_costing_details_v where effective_date between :p_frm_date and :p_to_date and EMPLOYEE_NUMBER = ‘005225’

Step 6: Transfer to GL process

Once this is done run transfer to GL process

Step 7: Import the Journal

Go to General Ledger and Import the Journal

General Ledger –> Import  –> Run

Step 8: Validate the journal entries and post it.

   

App-Pay-33238: Error PTO_CARRY_OVER_FF Opening Absence Form – system cannot calculate accruals for this date because the employee’s payroll did not exist

As we this error in with our  and when I checked in oracle support I got this document number Doc ID 418621.1

 

When attempting to access the absence screen the following error occurs as per the below screenshot

Error:
APP-PAY-33238 An error has occurred in a user defined
function at line 65 of the formula PTO_PAYROLL_CARRYOVER.
The error text associated with the function call is: The
system cannot calculate accruals for this date because the
employee’s payroll did not exist for the full accrual term…

Please correct the problem with the function call, or
contact your system administrator or support representative.
Steps to Reproduce:
The issue can be reproduced at will with the following steps:

Responsibility: XX HRMS Manager
1. People > Enter and maintain > Other Button
2. Choose the absence option

Cause

The payroll period needs to be extended. This is explained in the error message shown.

Solution

To implement the solution, please execute the following steps:

1. Go into a HRMS responsibility.

2. Navigate to Payroll > Description.

3. Extend the value in the number of years field as shown in the below screenshot.

4. Retest the issue.

5. Migrate the solution as appropriate to other environments.

 

Salary Management rollback the proposed Salary

To rollback the proposed salary which has been uploaded by webadi in Salary Management we have to use API to delete the uploaded Records.

So first query the records that has been uploaded in the backend by the below Query

select * from per_pay_proposals where change_date = :p_date;

Once you are sure to remove the records use the below

DECLARE
CURSOR fetch_det
IS
SELECT   *
FROM   per_pay_proposals
WHERE   TRUNC (change_date) = trunc(sysdate-73);

l_salary_warning   BOOLEAN;
l_err_msg          VARCHAR2 (500);
BEGIN
FOR i IN fetch_det
LOOP
BEGIN
hr_maintain_proposal_api.delete_salary_proposal (
p_pay_proposal_id         => i.pay_proposal_id,
p_business_group_id       => i.business_group_id,
p_object_version_number   => i.object_version_number,
p_validate                => FALSE,
p_salary_warning          => l_salary_warning
);
COMMIT;
DBMS_OUTPUT.put_line (
‘Proposal has been Deleted: ‘ || i.pay_proposal_id
);

COMMIT;
EXCEPTION
WHEN OTHERS
THEN
l_err_msg := SQLERRM;
DBMS_OUTPUT.put_line (‘Inner Exception: ‘ || l_err_msg);
END;
END LOOP;
EXCEPTION
WHEN OTHERS
THEN
l_err_msg := SQLERRM
DBMS_OUTPUT.put_line (‘Main Exception: ‘ || l_err_msg);
END;