How To Replace Seeded Saudi Payslip With A Custom One
How To Replace Seeded Saudi Payslip With A Custom One
How To Replace Seeded Saudi Payslip With A Custom One
In this Document
Goal
Solution
APPLIES TO:
GOAL
SOLUTION
The information on defining a flow pattern is in the Oracle Fusion Applications Workforce
Deployment Implementation Guide
-Define Payroll Flow Patterns is under Define Payroll.
1. Select the Manage Payroll Flow Patterns task in the Payroll Checklist work area or the
Refine Extracts flow from the Data Exchange work area.
2. Create a new flow pattern or search for and select an existing flow pattern to copy.
3. Select a legislative data group.
4. On the Basic information page, specify the following information.
1. LDG Required, as shown in the following table
The activity associated with the task determines the work area where you can submit the
flow.
o Optionally, rename the task and description and change the activity or task group
for the task.
For example, you might place all your reports in the Statutory activity and rename
each verification task so it includes the report name.
All flow patterns begin with a Start task and conclude with an End task. Tasks are
sequential but you can start processing on more than one task. For example, if your flow
pattern includes three reports you use to verify calculation results, you can specify Start
Flow in the Task column for each report. In the Following Task column, select the report
that should start next.
8. On the Parameters page, select the parameters to complete when submitting the flow
pattern.
The application uses the flow parameters to submit and complete the tasks in the flow
pattern, or as a basis for deriving values to submit the remaining tasks in the flow pattern.
9. On the Task Parameters page, review the parameters, and if necessary update the
parameters.
For example, you might specify a constant if the value is the same for all tasks, such as
the Process Configuration Group parameter.
10. Review the resulting checklist for the flow pattern before submitting the flow pattern.
11. Define a security profile for it using the Manage Payroll Flow Security Profile task in the
Setup and Maintenance work area.
The HCM data role security controls who can submit the flow pattern or view the
resulting flow from the Payroll Dashboard or payroll work areas.
In this Document
Purpose
Fast Formulas
1) Why are the seeded formulas failing after an install or applying a patch?
3) How can I get details of errors encountered whilst either compiling or executing formulas?
6) How do I see a database item for a changed element, element input or balance, if it does not
display?
Step 2 - Grant SELECT privilege on these FUSION tables to the CUSTOM user
Step 4 - create a private synonym for the custom package in the FUSION_DYNAMIC schema
5) How will calculation rule Unit X Rate for element work, while running the Payroll?
6) What aspects of element eligibility rules can I change after starting to use an element?
7) What happens if I override an element entry that has a runtime default set at the element's
definition?
12) Why can’t I select the element from an element list of values on the Element Entries page?
12) Why can’t I create entries for all elements on Element Entries page?
13) Are there any naming convention guidelines when creating elements?
14) SQLs to identify element eligibility and employee element entries for an element
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.1.5.0.0 and later
Oracle Fusion Global Payroll - Version 11.1.5.0.0 and later
Information in this document applies to any platform.
PURPOSE
This document is designed to provide answers to some of the most frequently asked questions
regarding Elements and Fast Formulas within Oracle Fusion Applications.
If you are a Software-as-a-Service (SaaS) customer, there may be sections in this document that
need not be performed by you. Please log a Service Request in My Oracle Support for Oracle to do this
for you
Fast Formulas
1) Why are the seeded formulas failing after an install or applying a patch?
You must compile all seeded formulas after an install or patch by selecting the “Submit a Process
or Report” task from the Payroll Checklist work area and then running the “Compile Formula”
process.
The database items, globals, and functions can be viewed and used on the Manage Fast Formulas
page. They appear in a panel on the far right of the main formula maintenance page, but can be
too far right to be immediately visible. To access this region, rearrange the page by either
minimizing the panels on the left side of the page or by resizing the panels.
3) How can I get details of errors encountered whilst either compiling or executing formulas?
You can find the following topics in Oracle Fusion Application Help, which list the errors:
This can be done by selecting the “Submit a Process or Report” task from the Payroll Checklist
work area and then running the “Compile Formula” process.
6) How do I see a database item for a changed element, element input or balance, if it does not
display?
Payroll data has a base name and a translated name. The database items for elements, element
input values, and balances have names that are generated from the base names of the element,
element input value, or balance. Changing the name updates the translated name but not the base
name. Unfortunately, the pages only display the translated name. The database items are still
present, but with the original names.
The database item or function might not exist. For a formula function, a function with the same
name and combination of parameters might not exist.
Each formula has a formula type with a related set of contexts. Contexts are application-specific
parameters – for example, a payroll run has contexts for the legislative data group, payroll, and
payroll action. Formula functions and database items can also take context parameters. If a
function or a database item requires contexts other than those supported by the formula type then
the formula cannot use the function or database item.
The formula might not exist or the application is running at a partitioning level incompatible
with the formula. For example, a United States payroll run cannot use United Kingdom formulas.
FUSION is the Fusion schema object (tables, views, PLSQL package) owner.
FUSION_DYNAMIC is the fusion dynamic schema owner. The dynamic schema is where
dynamically created objects such as the PLSQL generated by the formula compiler is held.
FUSION_RUNTIME is the Fusion user under which code is executed.
The custom schema is the Fusion schema where the customer’s schema objects (e.g. tables,
views, PLSQL packages) are created. The custom schema user will be referred to as
MYCUSTOM here, although it’s up to the customer what to call it.
Note: The following is not advice for database administrators on the best way to create the
function. It’s just the correct sequence of steps.
Step 1 - Create private synonyms for the referenced FUSION tables in the CUSTOM schema
This DDL is executed under the CUSTOM user. The DDL is required so that the PLSQL
function can compile in custom schema. Private synonyms are necessary to minimise the
visibility of the Fusion tables.
Step 2 - Grant SELECT privilege on these FUSION tables to the CUSTOM user
This is necessary for the custom plsql packages to compile, and is executed under the FUSION
user.
This is created by the custom user and has invoker rights (AUTHID CURRENT_USER) so that
it executes with the privileges of the caller (invoker) rather than the creator (definer i.e.
MYCUSTOM).
This DDL is executed as the FUSION_DYNAMIC user. This is necessary so that formulas using
the formula function can be compiled.
This is done under the CUSTOM user. This is necessary so that formulas using the formula
function can be compiled.
--
/*
+====================================================================
====+
| Copyright (c) 2011 Oracle Corporation, Redwood Shores, CA, USA |
| All rights reserved. |
+====================================================================
====+
Name
Comp Object Summary Routine
Purpose
This package for delivering pfg formula functions
History
Date Who Version What?
---- --- ------- -----
07-dec-2010 tjesumic 000.001 Created.
--+-
=====================================================================
==+
*/
--
function get_latest_salary (p_Assignement_id in number,
p_effective_date in date ,
p_plan_name in varchar2) return varchar2;
end zz_cmp_pfg_functions;
/
commit;
exit;
begin
end if ; -- L_PL_ID
return l_return ;
end get_latest_salary;
--
end ZZ_CMP_PFG_FUNCTIONS;
commit;
exit;
Declare
--
-- Start of parameters
--
-- Modify values as needed.
--
l_function_key varchar2(100) := 'ZZ_CMP_GET_LATEST_SALARY';
l_function_name varchar2(100) := 'ZZ_CMP_GET_LATEST_SALARY' ;
l_data_type varchar2(100) := 'N' ; -- Data Type returned by formula function.
l_definition varchar2(100) := 'ZZ_CMP_PFG_FUNCTIONS.GET_LATEST_SALARY';
l_description varchar2(200) := 'Returns the latest salary.';
l_enterprise_id number := 11129;
l_function_id number;
--
-- End of parameters
--
PROCEDURE formula_functions(
p_enterprise_id IN VARCHAR2,
p_function_key IN VARCHAR2 ,
p_alias_name IN VARCHAR2 ,
p_base_function_name IN VARCHAR2 ,
p_data_type IN VARCHAR2 ,
p_definition IN VARCHAR2 ,
p_tl_description IN VARCHAR2,
p_function_id out number ) IS
l_found boolean;
CURSOR base_entity_cur IS
SELECT function_id
FROM FF_FUNCTIONS_B
WHERE upper(FUNCTION_KEY) = upper(p_function_key)
and ENTERPRISE_ID = p_enterprise_id
;
cursor c_langs is
select language_code
from fnd_languages
where installed_flag in ('B', 'I')
;
base_entity_rec base_entity_cur%ROWTYPE;
l_function_id number;
BEGIN
--
-- Insert/Update Formula Functions
--
OPEN base_entity_cur;
FETCH base_entity_cur INTO base_entity_rec;
l_found := base_entity_cur%found;
CLOSE base_entity_cur;
IF (l_found) then
l_function_id := base_entity_rec.function_id;
update ff_functions_tl
set description = p_tl_description
where function_id = l_function_id
and source_lang = 'US'
;
END IF;
--
-- Delete function context usages and parameters.
--
END formula_functions;
--
-- Supports the seeding of a single FUNCTION PARAMETERS.
--
PROCEDURE function_parameters(
p_f_function_key in varchar2 ,
p_function_id IN NUMBER ,
p_sequence_number IN NUMBER ,
p_class IN VARCHAR2 ,
p_continuing_parameter IN VARCHAR2 ,
p_data_type IN VARCHAR2 ,
p_name IN VARCHAR2 ,
p_optional IN VARCHAR2 ) IS
BEGIN
INSERT INTO FF_FUNCTION_PARAMETERS
(SEQUENCE_NUMBER
,CLASS
,CONTINUING_PARAMETER
,DATA_TYPE
,NAME
,OPTIONAL
,FUNCTION_ID
,CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE,
LAST_UPDATE_LOGIN)
VALUES
(P_SEQUENCE_NUMBER
,P_CLASS
,P_CONTINUING_PARAMETER
,P_DATA_TYPE
,P_NAME
,P_OPTIONAL
,P_FUNCTION_ID
,0, SYSDATE, 0, SYSDATE, 0);
);
EXCEPTION
END;
--
-- Supports the seeding of a single FUNCTION CONTEXT USAGES.
--
PROCEDURE function_context_usages(
p_c_context_name IN VARCHAR2 ,
p_c_context_leg_code IN VARCHAR2 ,
p_f_function_key IN VARCHAR2 ,
p_function_id in number ,
p_sequence_number IN NUMBER ) IS
l_context_id number;
BEGIN
SELECT CONTEXT_ID
INTO L_CONTEXT_ID
FROM FF_CONTEXTS_B
WHERE UPPER(BASE_CONTEXT_NAME) = UPPER(p_c_context_name)
AND ((UPPER(P_C_CONTEXT_LEG_CODE) = LEGISLATION_CODE) OR
LEGISLATION_CODE IS NULL AND NVL(ENTERPRISE_ID,0) = 0 AND
LEGISLATIVE_DATA_GROUP_ID IS NULL)
;
EXCEPTION
raise;
END;
Begin
formula_functions(
p_enterprise_id => l_enterprise_id,
p_function_key => l_function_key ,
p_alias_name => null ,
p_base_function_name => l_function_name ,
p_data_type => l_data_type ,
p_definition => l_definition ,
p_tl_description => l_description,
p_function_id => l_function_id );
function_parameters(
p_function_id => l_function_id,
p_f_function_key => l_function_key ,
p_sequence_number => 1 ,
p_class => 'I' ,
p_continuing_parameter => 'N' ,
p_data_type => 'T' ,
p_name => 'P_PLAN_NAME' ,
p_optional => 'Y'
);
function_context_usages(
p_c_context_name => 'HR_ASSIGNMENT_ID' ,
p_c_context_leg_code => null ,
p_f_function_key => l_function_key ,
p_function_id => l_function_id,
p_sequence_number => 1 ) ;
End ;
/
commit ;
exit ;
Payroll Relationship elements can only be created for elements with a deduction classification.
It prevents all new element entries for the element. Selecting this option will not affect any
existing element entries. Use caution with this feature. When hiring, terminating, or updating
assignments, this option will prevent element entry creation for the element, even if the element
is used for automatic entries.
You can define more than one eligibility criteria for each element but there must be no overlap
between them. For example, you could create one criteria for the combination of grade A and the
job Accountant. However, you could not create one criteria for grade A and a second for the job
Accountant. This would imply that an accountant on grade A is eligible for the same element
twice. If you have more than one criteria for an element, you can enter different default values,
qualifying conditions, and costing information for each eligibility group.
5) How will calculation rule Unit X Rate for element work, while running the Payroll?
This element has input values for unit, unit type, rate and multiple. Unit type can be hours or
days.
If rate is not specified then the rate is calculated using the salary basis. Multiple defaults to 1 if
none specified.
6) What aspects of element eligibility rules can I change after starting to use an element?
After you have used an element you can make the following changes to the eligibility rules:
7) What happens if I override an element entry that has a runtime default set at the element's
definition?
If you override it, then any subsequent changes to the default value on the element or element
eligibility definition will not affect the element entry. However, you can clear your entry if you
want to restore the default value.
One element is given to employees, the input values on the Manage Elements page cannot be
update. If your business has a situation that the input value (ex: Amount, Percentage) needs to be
changed on all employees, the best option is this:
Please refer to Integrating with Oracle HCM Cloud Gide > Payroll Batch Loader
Workbooks chapter for more information.
When searching for an element entry, you must enter the desired date in the Effective As-of date
field. You can then drill down to the entry details and update or end date as of the desired date.
On the Element Entries page, you cannot delete entries created automatically from other features.
For example, paid-time-off absence entries and benefit entries cannot be updated or deleted on
the Element Entries page. Users can end date element entries in Manage Element Entries page.
12) Why can’t I select the element from an element list of values on the Element Entries page?
You may be encountering an intermittent issue on Internet Explorer 8 that prevents you from
selecting the element from element list of values.
12) Why can’t I create entries for all elements on Element Entries page?
The entries for some elements are created through different features such as paid-time-off
absence entries and benefit entries. You cannot manually create entries for these types of
elements using the Element Entries page.
13) Are there any naming convention guidelines when creating elements?
Users should avoid the use of the 2-character country code at the start of the element name, no
hyphens, and the name cannot begin with a number (such as 401k). Also, beware of extra,
consecutive spaces in the name as it can cause the associated fast formula to fail compilation.
14) SQLs to identify element eligibility and employee element entries for an element
Unable to delete the element for which it seems that there are no element entries exist. There
could be still rows in the eligibility and element entries tables that prevent deleting an element.
Use these sample sqls to identify lokcing records:
b. SQL to find out employees' person numbers who have this element in their element
entries:
Goal
Solution
References
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
GOAL
We have copy of seeded payslip and the only change in custom payslip is company logo. Now
we are processing the monthly payslip and even though template is with business logo. We are
getting Oracle logo only after generate Payslip request.
SOLUTION
Please verify the permission setup again and check if you had customized template only in the
AE payslip and not on the other payslip report under custom folder.
In case proper permission is not in place report will not be accessible, please do check again.
REFERENCES
In this Document
Goal
Solution
References
APPLIES TO:
GOAL
A custom package has been created to produce custom xml tags and is entered in the XML Code
field in Self Service Preference at the business group level as
XXHR_PAYSLIP_PKG.XX_US_PAYSLIP
However, the custom tags are not appearing on the custom template created for this purpose.
How to find custom xml tags that are created for Online Payslip in PDF format ?
SOLUTION
Oracle Support received the following information from Oracle Development on how to identify
and see the custom XML tags that are produced:
Unlike the CheckWriter and Deposit Advice Processes where XML File is first generated
through a Concurrent Request and later merged with Template, Online Payslip generates XML
and merges it with RTF Template in procedures itself without saving it to database or filesystem.
For PDF Payslip, the XML file is generated by calling the procedure
PAY_PAYROLL_XML_EXTRACT_PKG.GENERATE. Package
PAY_PAYROLL_XML_EXTRACT_PKG has two overloaded procedures with name
GENERATE. The procedure with below signature is the one used by PDF Payslip.
PROCEDURE GENERATE (
P_ACTION_CONTEXT_ID number,
P_CUSTOM_XML_PROCEDURE varchar2,
P_GENERATE_HEADER_FLAG varchar2, -- {Y/N}
P_ROOT_TAG varchar2,
P_DOCUMENT_TYPE varchar2,
P_XML OUT NOCOPY BLOB
)
The XML content generated is propagated through Parameter P_XML and merged with RTF
Template to display the Online PDF Payslip. The XML content generated for PDF Payslip is not
saved any where in the database.
If customer is interested in capturing the XML generated for PDF Payslip, they can follow below
mentioned steps in their Test instance.
>> Please note that these steps are only for Debugging purpose and should not be applied
in the Production instance.<<
1. Create a temporary table to hold the XML Data using APPS Login
Save the Package Body and compile the changes. Make sure the compilation completes
successfully.
4. Now try accessing PDF Payslip for the required employee. The XML generated will now be
saved to temporary table TEMP_PDF_PAYSLIP_XML. The Column
ASSIGNMENT_ACTION_ID has the Assignment Action ID corresponding to the Payroll
Archive run of the Employee for which Payslip is viewed. For debugging purpose, if same
Payslip is accessed multiple times, the column CREATION_DATE can be used to retrieve the
latest XML.
Please note:
Support analysts may address questions regarding basic functionality, but the charter does not
allow Support to assist in debugging custom code. The Applications architecture is very complex
and is under proprietary control. Any issues with the standard Application can be directed to the
appropriate Applications support team, (i.e. General Ledger, Accounts Receivable, etc.).
You can use the E-Business Customization Community to seek assistance or share knowledge
with other customers:
https://community.oracle.com/community/support/oracle_e-business_suite/e-
business_customizations
NOTE:1530347.1 - Using Custom XML with Oracle US & Canadian Payroll Reports
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
GOAL
Why after running the Generate Payslips process, the PDF produced is using the Oracle seeded
template instead of the Custom version?
We have followed Oracle instructions to do this (ref. Fusion Global Payroll: How To Invoke
Custom UK Payslip (Note 2077621.1)
SOLUTION
Please add BI Consumer and Generate payslip roles in Permission for /shared/Human Capital
Management/Payroll/Regulatory and Tax Reporting/UK/
REFERENCES
NOTE:1569322.1 - Fusion Global Payroll: How Can I Configure a Payslip in Fusion Payroll?
NOTE:2077621.1 - Fusion Global Payroll: How To Invoke Custom UK Payslip
Document Details
APPLIES
TO:
How to add a
custom logo to Information
the payslip? Center:
Fusion
Global
Payroll
SOLUTION [2661318.2]
In order to add
a custom logo Information
to the Payslip, Center:
you will need Fusion HCM
to download a Extracts
[2690351.2]
copy of the
template used,
then make the
changes to the
logo, and then Document References
customize the No
US Online
References
Payslip by
following the available
steps below: for this
document.
1) Select
Navigator >
Reports and
Analytics.
Recently Viewed
2) Navigate to UK Payroll: Seeded Payslip Showing Instead Of Custom One [2558527.1] Show
More
the report
from the tree
located on the
How To Find Custom XML Tags For PDF Online Payslip [1909531.1]
left hand side.
3) Select the
report which Fusion Applications - Global Payroll - Custom Payslip Displaying Oracle Logo Instead Of
you’d like to The Company Logo [2564155.1]
load a custom
template for.
For example
Fusion Applications HCM OTBI: Head Count Measure In Workforce Management -
we will look at Worker Assignment Real Time, Does Not Show All Employees [1915309.1]
adding a
custom
Payslip.
Fusion Global Payroll: Elements and Fast Formulas Frequently Asked Questions (FAQ)
4) When the [1420170.1]
popup loads
you need to
select View,
which will
load up the
BIP Server
5) Once the
BIP server has
loaded, you
may need to
alter your
URL so that
you can
continue with
the below
steps. Change
the URL from
‘analytics’ to
‘xmlpserver‘
6) If you
don’t see a
folder tree on
the left hand
side select
‘Catalog’ from
the menu bar.
7) Once again
navigate down
the tree to the
report and you
will see all
UK seeded
reports, which
contains the
templates.
8) Select
‘More’ then
‘Customize’ -
this will
automatically
create an
identical copy
of the UK's
payslip report
inside the
Custom
folder.
9) The UI
should
automatically
take you to the
new custom
location,
however if
you are
coming back
into the UI
after, you need
to ensure you
are editing
within the
custom folder
10) Take a
copy of the
template name
'UK_PAYSLI
P' and delete
the template
(always worth
taking a
backup of the
seeded
template in
case you want
to revert back
to it when
customizing
your own
template).
You do this by
selecting Edit
and saving to
your local
machine.
12) Upload
your new
version of the
UK’s payslip.
Ensure you
call it
UK_PAYSLI
P and Locale
is set to
English
By using the
customization
feature the
new template
will
automatically
be used for all
requests for
that report.
Related
Products
Oracle Cloud > Oracle Software Cloud > Oracle Human Capital Management Cloud > Oracle Fusion Global Payroll
Cloud Service > Global Payroll > Functional Setup Manager / Other Setup
Keywords
Symptoms Yes
Cause No
Solution
Document Details
Status: PUBLISHED
Oracle Fusion Global Payroll
Cloud Service - Version Last Major Update: Oct 15, 2018
11.12.1.0.0 and later
Information in this Last Update: Sep 21, 2020
document applies to any
platform.
SYMPTOMS
STEPS Information
Center:
----------------------- Fusion HCM
The issue can be Extracts
reproduced at will with [2690351.2]
the following steps:
1. Generate payslip for
employee -
2. Review Total pay/Net Document References
pay values
CAUSE
Related
Products
Oracle Cloud > Oracle Software Cloud > Oracle Human Capital Management Cloud > Oracle Fusion Global Payroll
Cloud Service > UK - United Kingdom Legislation > UK - Earnings
Keywords
ABSENCES; BALANCES; BI CATALOG; CUSTOM; DEDUCTION; DOUBLE; FOLDER; GENERATE; INCORRECT; PAYSLIP;
PERMISSION; PUBLISHER; REPORT; SUMMARY TOTALS; UNITED KINGDOM
In this Document
Goal
Solution
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
GOAL
SOLUTION
Please review Fusion Global Payroll: How To Invoke Custom UK Payslip (Doc ID 2077621.1)
and at steps 2 and 3 from this document create an identical copy of the Saudi payslip report
inside the Custom folder /shared/Custom/Human Capital Management/Payroll/Regulatory and
Tax Reporting/Saudi Arabia/ where you should replace the seeded Payslip with your custom one.
After this please create a new delivery option pointing to the custom folder and add the value
SA Online Payslip in the column Overriding Delivery Mode ( Navigate to Data Exchange->
Manage Extracts Definition, search for Payslip -Extract Delivery Options). Please check also to
have below value in the BURSTING_NODE
/DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/REL_ACTION_ID
Rollback all the processes and retest the payslip by resubmitting all the needed processes from
scratch
Symptoms
Cause
Solution
References
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.18.02.0 and later
Information in this document applies to any platform.
SYMPTOMS
ERROR
-----------------------
ReportID : /Custom/Human Capital Management/Payroll/Regulatory and Tax
Reporting/UK/Paper Payslip.xdo
Output failed.
[INSTANCE_ID=bip.bi_server1] [OUTPUT_ID=7138] Invalid format requested: xml
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Submit Generate payslips process
2. BIP process fails
CAUSE
SOLUTION
Please set the Bursting property to 'Disable' on the Delivery option> Additional details for UK
Printed Payslip.
REFERENCES
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Fusion Global Human Resources Cloud Service - Version 11.1.7.0.0 and later
Oracle Fusion Application Toolkit Cloud Service - Version 11.1.7.0.0 and later
Oracle Fusion Application Toolkit - Version 11.1.7.0.0 and later
Information in this document applies to any platform.
GOAL
To determine why the Head Count measure only displays employees hired through the UI and
doesn't show employees that were imported.
SOLUTION
In Fusion HCM, Headcount & FTE are measures that require user inputs with no defaults.
NOTE : There is no sql script user can run to set all the active primary work assignments
HeadCount field to 1.
But, you can use/modify the earlier suggestion to use assignment count.
This will be pretty close to what you are looking for.
Basically pull all active assignments and filter for employees etc.
The assignment fact in the following subject area pulls all active assignments using following
logic.
You can modify the report by filtering on assignment type to get the headcount as per their
requirements.
Additional information/clarification:
To
How To Assign A Legal Entity To A Ledger (Doc ID 1344517.1)
Bottom
In this Document
Goal
Fix
The following Functional Setup Manager (FSM) steps are required to Assign an LE to a
Ledger:
References
APPLIES TO:
GOAL
FIX
If you are planning to create any transactions that has a financial impact
then you will need to assign
an LE to a Ledger.
After clicking on the "Go To Task" for the "Assign Legal Entities" task
you will be taken into the "Assign Legal Entities" page. This page will
show all the LEs that are currently assigned to your chosen Ledger.
Click on the create icon then select your LE and click on Apply. Once
you have finished applying then click
on done which will bring you back to the "Define Accounting
Configuration" task list.
Important - Once the assignment has been done you will then need to run
the "Review and Submit Accounting Configuration" program.
No
Document Details
Type: HOWTO
Status: PUBLISHED
Language: English
Related Products
Information Centers
Information
Center:
Patching
Issues with
Fusion
Financials
Management
(FM)
[1625192.2]
Oracle
Catalog:
Service
Request
Data
Collections
(SRDCs) for
all Products
and Services
[51.2]
Oracle
Catalog:
Information
Centers for
All Products
and Services
[50.2]
Document References
How To
Create a
New Ledger
in Fusion
General
Ledger
[1274512.1]
How To
Create
Legal
Entities
[1333573.1]
Recently Viewed
Fusion Global Payroll: What Must be Done to Set Up Fusion Payroll or Fusion Payroll
Interface to Pay Employees? [1616273.1]
Show More
Attachments
asgn_le_to_led (38.69 KB)
Fusion Global Payroll: Gross Earnings Completes with Warning Selected for To
Payroll Process HR_7277_COST_ALLOCAT (Doc ID 1631901.1) Bottom
In this Document
Symptoms
Cause
Solution
References
APPLIES TO:
SYMPTOMS
CAUSE
SOLUTION
Creating the card and card association helped resolve this issue.
Click on Associations link and make sure that there are associates to Tax Reporting Unit (TRU)
and to Assignment Number.
For more information please refer to Oracle Fusion Applications Workforce Deployment, Global
Payroll Guide
REFERENCES
NOTE:1536421.1 - Fusion HRMS (US): Error ORA-20001: An assertion failure was detected at location
pay_payroll_run.get_calc_breakdown_id:1
http://docs.oracle.com/cd/E38454_01/doc.1117/e35673.pdf
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.20.01.0 and later
Information in this document applies to any platform.
GOAL
Saudi Government (General Organization for Social Insurance) Announced in April 2020 to
register 70 % from Saudi Employees in the (SANED Program - Unemployment support) and
SANED program is supporting those Saudi Employees by paying their salaries directly and not
through company payroll anymore.
Question: How can we keep their Monthly Costing details/Journals running normally such as
(Gratuity Provision & Annual Leave Provision) ?
SOLUTION
We have delivered a document to help address this type of situations, please consider the bellow:
Oracle HCM Cloud Saudi Arabia: GOSI Suspension For Employees And Employers Due to
COVID-19 (Doc ID 2672787.1)
If the payment is suspended, you don't need to cost (e.g. to send a costing journal for the GL) for
something that you are not paying out.
Even if the employee is being paid, GOSI would still calculated as zero, so nothing relating to
GOSI would be costed.
As additional observation, Gratuity wouldn't be accrued each month if the employee isn't being
paid, but the accrual would catch up the next time the employee is paid, and this corrected figure
would be costed at that time.
This would not affect any Gratuity actually paid on termination.
NOTE:2672787.1 - Oracle HCM Cloud Saudi Arabia: GOSI Suspension For Employees And Employers Due
to COVID-19
NOTE:2650274.2 - Information Center: Fusion Human Capital Management - COVID-19
Loading GCC Countries Data Using HCM Data Loader (Doc ID 2561763.1) To Bottom
In this Document
Abstract
History
Details
References
APPLIES TO:
ABSTRACT
This document provides information about loading the following calculation cards using HCM
Data Loader:
HISTORY
DETAILS
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
GOAL
The customer upload a new employees and missed to fill the nationality or the citizenship
information.
The calculation cards not added automatically to the employees.
After that the customer updated all employees with nationality but the calculation cards not
added.
The customer faced this issue before but with KSA legislative to add calculation card when
Oracle ran a script.
The customer requested to run the script to create automatically calculation cards for the
employees.
SOLUTION
The automatic creation of the calculation cards did not triggered due to missing information in
the citizenship and Social Insurance Number fields for the personal data for the employees while
hiring.
Regarding HDL:
There is no specific template for UAE or any gcc localization. But customers
can use the generic loader template plus can refer the implementation guide.
Please refer to HCM Data Loader: Business Object Documentation (Note 2020600.1)
REFERENCES
Abstract
History
Details
Summary
References
APPLIES TO:
Oracle Fusion Global Human Resources Cloud Service - Version 11.1.10.0.0 and later
Information in this document applies to any platform.
ABSTRACT
Using HCM Data Loader, you can bulk-load data from any source to Oracle Cloud Human
Capital Management. This document provides information about HCM business objects.
HISTORY
Description: Using HCM Data Loader, you can bulk-load data from any source to Oracle Cloud
Human Capital Management. This document provides information about HCM business objects.
DETAILS
Most HCM Data Loader business object documentation has been moved on Oracle Help Center
into HCM Business Objects Integration Guide. You can still find white papers about loading a
few business objects, including some localization-specific business objects, via this document
(2020600.1) on My Oracle Support. See the References section for links to the remaining
business object white papers.
Supported Objects
Supported business objects are listed on the View Business Objects page in the Data Exchange
work area. The Human Capital Management Integration Specialist job role has access to this user
interface.
On the View Business Objects page, you can generate data-file templates. When you click the
name of a business object on the View Business Objects page, you access information about the
object. This information includes:
The component hierarchy of the object.
Detailed information about the currently selected component, including its parent
component, file discriminator, data-file name, and the name of any translation object
Information about each attribute of the component, including
o Whether it's required
o Its name, type, and length
o Whether it's a key value or can be used as a key value and, if so, the key type
Oracle Cloud Customer Connect provides example .dat files for work structures and workers.
The resources shared in these forums will continue to grow. You can access Cloud Customer
Connect either in the Navigator or by going to https://appsconnect.custhelp.com/.
After signing in, select the HCM Cloud Integration forum on the Human Capital Management
page.
SUMMARY
REFERENCES
NOTE:2259608.1 - HCM Data Loader: Loading Electronic Income Withholding Orders (e-IWO)
NOTE:2022617.1 - Data File Validator Tool for HCM Data Loader
NOTE:2098480.1 - HCM Data Loader: Loading Calculation Cards for United Kingdom
NOTE:2124649.1 - HCM Data Loader: Loading Calculation Cards for Australia
NOTE:2141697.1 - HCM Data Loader: Loading Payroll Interface Inbound Records
NOTE:1664133.1 - Oracle HCM Data Loader: User Guide
NOTE:1504483.1 - All Fusion HCM Cloud Product Papers
NOTE:2233630.1 - HCM Data Loader: Loading Calculation Cards for France
NOTE:2030124.1 - HCM Data Loader: Loading Person Disability
Fusion Saudi Arabia Payroll: Unable to Reverse Terminate an Employee To
(Doc ID 2169665.1) Bottom
In this Document
Symptoms
Cause
Solution
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.20.10.0 and later
Oracle Fusion Global Payroll - Version 11.12.1.0.0 and later
Information in this document applies to any platform.
This note was created for Release 11.1.10.0.0. The note has been reviewed and is current for release
11.13.20.07.0.
SYMPTOMS
ERROR
-----------------------
An application error occurred. See the incident log for more information.
An application error occurred. Your help desk can use the following information to obtain a more
detailed description of this incident: 197, Server Domain: HCM Domain, Server instance:
CoreProcessesServer_1, Application Name: HcmCoreApp.
To reverse the termination for this employee, first delete the gratuity calculation card.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Reverse terminate employee.
2. Error is returned.
CAUSE
This is expected, and the user needs to delete the Gratuity card for the employee he or she is
doing a reverse termination for.
SOLUTION
Delete the card first and then attempt to re-terminate the employee.
In this Document
Abstract
History
Details
References
APPLIES TO:
ABSTRACT
Suggested Absence Management setup, so that you can manage your workers’ absences and
corresponding entitlements.
HISTORY
Description: Suggested Absence Management setup, so that you can manage your workers’
absences and corresponding entitlements.
DETAILS
This paper provides examples, based on statutory requirements, of the setup tasks required for
creating Saudi-specific absence elements and absence management for your enterprise from
Release 10 onwards.
REFERENCES
Olacle Fusion HRMS (SA): Absence Management Implementation and Functional Considerations (2.1 MB)
How to replace seeded Saudi Payslip with a custom one? (Doc ID To
2528955.1) Bottom
In this Document
Goal
Solution
APPLIES TO:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
GOAL
SOLUTION
Please review Fusion Global Payroll: How To Invoke Custom UK Payslip (Doc ID 2077621.1)
and at steps 2 and 3 from this document create an identical copy of the Saudi payslip report
inside the Custom folder /shared/Custom/Human Capital Management/Payroll/Regulatory and
Tax Reporting/Saudi Arabia/ where you should replace the seeded Payslip with your custom one.
After this please create a new delivery option pointing to the custom folder and add the value
SA Online Payslip in the column Overriding Delivery Mode ( Navigate to Data Exchange->
Manage Extracts Definition, search for Payslip -Extract Delivery Options). Please check also to
have below value in the BURSTING_NODE
/DATA_DS/G_1/FILE_FRAGMENT/PAYSLIP/PAYMENT_RECORD/REL_ACTION_ID
Rollback all the processes and retest the payslip by resubmitting all the needed processes from
scratch
In this Document
Purpose
What's the difference between retrying a payroll process and retrying a payroll calculation?
How can I identify the payroll flow that includes a specific element for an employee?
What is the difference between rolling back and reversing a payment action?
APPLIES TO:
PURPOSE
This document is designed to provide answers to some of the most frequently asked questions
regarding calculation, validation and balancing in Oracle Fusion Payroll.
What's the difference between retrying a payroll process and retrying a payroll calculation?
Use the Retry Payroll Process task to reprocess all tasks except the tasks to Calculate Payroll and
Recalculate Payroll for Retroactive Changes. Submit the task to rerun the selected payroll
process and to recalculate the results.
Use the Retry Payroll or Retroactive Calculation task to retry only the tasks to Calculate Payroll
and Recalculate Payroll for Retroactive Changes. Submit the task to recalculate the payroll run
results, such as the gross-to-net results, or to recalculate retrospective changes that were not
included in the original payroll run.
Refer to Note 1556326.1 Fusion Payroll: FAQ For Marking for Retry, Retrying, and Rolling
Back Payroll Results for more information.
There are several processes that need to be executed in this sequence in order to see employee's
payslip. Navigation: Payroll > Checklist > Submit a Process or Report > Pick your Legislative
Data Group:
- Calculate Payroll
- Calculate Prepayments
- Archive Periodic Payroll Results
- Generate Check Payments, this process generates the file with checks
- Make EFT Payments
- Generate Payslips
Sometimes that there is a need for more then one payment to be paid to an employee in case of a
bonus or termination or other reasons. In this case employee can be processed in a payroll run
and a Quickpay or use of payroll relationship group parameter in the normal run to calculate
payroll for the selected persons and generate EFT file. When we run Make EFT Payment
process, it will generate EFT file for the new prepayment results (i.e. payments for the payroll
relation group selected in the normal run). In this way we can run separate payroll calculation
process for each payroll relationship group and generate multiple EFT files.
Please note that the dates for the first run/ prepayment need to be the before the dates for the
second run / prepayment. Otherwise the second prepayment will not process the employee
because there are prepayments and EFT payment exist for the employee already.
Roll back the person's record from the View Person Process Result page, which deletes the
record. If you have already processed later actions for the person, such as prepayments, you must
roll back these actions before you can roll back the payroll run results for the person. You can
put failed employees in payroll relationship group. Please refer to Note 1556341.1 Fusion
Payroll: FAQ For Object Groups on how to create a payroll relationships group
Remove a person from the run if you discover a problem that requires corrections that would
delay the payroll run. You can remove the person, make the corrections, and process a QuickPay
action.
Submit the Element Result Register to confirm that the payroll included the element, to
determine the value paid the employee, and the name of the payroll flow where the element
results were calculated. When you submit the Element Result Register, you must enter the
payroll name and the end date. If you do not know which payroll the person is assigned to, query
the person's payroll details on the Manage Payroll Relationships page to identify the person's
assigned payroll.
What is the difference between rolling back and reversing a payment action?
Rolling back a process deletes the action and leaves no audit trail. For example, you might roll
back the prepayment process if you discover an error before generating payments.
The reversal process reverses the payroll calculation, generating a negative run result to offset
the original run result, and leaves an audit trail. Once the payment process has been run, you can
no longer roll back; you must reverse the payroll calculation. For example, you might reverse the
calculation for a payment that was generated in error and was not issued. You can reverse any
process that produces run results, including a normal payroll run and a QuickPay run. The
Cancel Payment flow includes the Reverse Payroll Calculation task.
After you calculate the payroll, you can view balances on the Statement of Earnings section of
the Person Process Results page. Balances are not automatically included for the Information
balance group, nor for the Gross-to-Net balance group for legislations not predefined by Oracle.
You must load these balances and the balance groups before you can view their results in the
Statement of Earnings.
Closing a payroll period can interfere with changes to recurring entries. Payroll periods are not
like General Ledger periods. You do not need to close payroll periods.
NOTE:1556326.1 - Fusion Payroll: FAQ For Marking for Retry, Retrying, and Rolling Back Payroll Results
NOTE:1556341.1 - Fusion Payroll: FAQ For Object Groups