VersionPerson Date Modified
0.1
Comments
Intial version
Tab Area
1 ESS Job Sets
2 ESS Jobs
3 Calendar Template
4 Period-End Checklist
Description
List of sample standard and custom programs groupped into Job Sets
List of sample standard programs with suggested schedules
Sample calendar template to present your key jobs and runtimes in a calendat format
The Period-End Procedures in a checklist format
Area DirectionRICEF Nr./ ProcessProcess Name Sequence
MDM Inbound Import Customer and Supplier Data 1
2
3
4
5
6
7
P2P Inbound Import Payables invoices to Oracle 1
2
3
O2C Inbound Import Billing invoices to Oracle 1
2
R2R Inbound Import GL Journals to Oracle 1
2
Ess Job Code UserComponent TypeSOA Composite nam
Import Bulk Customer Data ERP Job
Import Suppliers ERP Job
Import Supplier Addresses ERP Job
Import Supplier Sites ERP Job
Import Supplier Site Assignments ERP Job
Import Supplier Contacts ERP Job
Import Supplier Bank Accounts ERP Job
Load and Import Data ERP Job
Import Payables invoices ERP Job
Validate Payables Invoices ERP Job
Load and Import Data ERP Job
Import Receivables Transactions Using AutoInvoice ERP Job
Load Interface File for Import ERP Job
Import Journals ERP Job
BI Report NamePathParameters
Area Type Direction Source/Target Systems
Core Cloud Process
Core Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
A2R Cloud Process
IC Cloud Process
IC Cloud Process
IC Cloud Process
IC Cloud Process
MDM Integration Inbound
O2C Integration Inbound
O2C Cloud Process
O2C Cloud Process
O2C Cloud Process
O2C Cloud Process
P2P Integration Inbound
P2P Cloud Process
P2P Cloud Process
P2P Cloud Process
P2P Cloud Process
P2P Integration Outbound Bank
P2P Cloud Process
P2P Cloud Process
P2P Cloud Process
R2R Cloud Process
R2R Cloud Process
R2R Cloud Process
R2R Cloud Process
R2R Cloud Process
R2R Cloud Process
SCO Cloud Process
SCO Cloud Process
SCO Cloud Process
SCO Cloud Process
SCO Cloud Process
SCO Cloud Process
SCO Cloud Process
Process Name
Retrieve Latest LDAP Changes
Import User and Role Application Security Data
Create Mass Additions
Import Costs (Payables)
Import Costs (OTL)
Import Costs (Cost Management)
Update Project Performance Data
Create Accounting (Projects)
Generate Revenue
Generate Invoices
Generate Asset Lines
Transfer Assets to Oracle Fusion Assets
Update Asset Information from Oracle Fusion Assets
Post Mass Additions
Create Accounting (Assets)
Calculate Depreciation
Transfer Intercompany Transactions to Payables
Transfer Intercompany Transactions to Receivables
Import Payables invoices
Import Receivables Transactions Using AutoInvoice
Import Customer and Supplier Data from Non-Oracle
Sources
Import Billing Invoices from Non-Oracle Sources
Refresh Receivables Transactions for Customer Account
Summaries
Process Receivables Transactional Events for Summary
Apply Receipts Using AutoMatch
Create Accounting(Receivables)
Import Payables Invoices
Validate Payables Invoices
Import Payables Payment Requests
Process Expense Reimbursements and Cash Advances
Initiate AP Invoices Workflow
Send the Payment File to the Bank
Create MultiPeriod Accounting
Create Accounting (Payables)
Initiate Payment Process Request
Import Journals
AutoPost Journals
Reconcile Clearing Accounts Automatically
Optimize Journal Import Performance
Transfer Control Budget Balances to Essbase
Generate Allocations
Transfer Transactions from Receiving to Costing
Transfer Costs to Cost Management
Transfer Transactions from Inventory to Costing
Create Receipt Accounting Distributions
Create Accounting for Receipts
Create Accounting for Cost Management
Create Cost Accounting Distributions
Parameters User Under Which Schedule
Accounting Date: Today (increased automatically)
Asset Book:
Business Unit:
Process Mode: Importing and Processing
Transactions
Transaction Status: Never previously imported
Transaction Source: Oracle Fusion Payables
Document:
Expenditure Batch:
From Project Number:
To Project Number:
Process Through Expenditure Item Date:
Generate Report: Summary
Business Unit:
Process Mode: Importing and Processing
Transactions
Transaction Status: Never previously imported
Transaction Source: Oracle Fusion Time and Labor
Document:
Expenditure Batch:
From Project Number:
To Project Number:
Process Through Expenditure Item Date:
Generate Report: Summary
Business Unit:
Process Mode: Importing and Processing
Transactions
Transaction Status: Never previously imported
Transaction Source: Oracle Fusion Cost Management
Document:
Expenditure Batch:
From Project Number:
To Project Number:
Process Through Expenditure Item Date:
Generate Report: Summary
Summarization Method: Incremental
Project Unit:
Business Unit:
From Project Number:
To Project Number:
Summarize Budget and Forecast Transactions: Yes
Summarize Commitment Transactions: Yes
Summarize Actual Cost Transactions: Yes
Resource Breakdown Structure Header:
Project Manager:
Subledger Application: Project Costing
Ledger:
Process Category:
End Date: <Sysdate>
Process Category: Final
Process Events: All
Report Style: Summary
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Journal Batch:
Include User Transaction Identifiers: No
Business Unit:
From Project Number:
To Project Number:
Placed in Service Through Date:
Include Common Tasks:
Capital Event Name:
Project Accounting Through Date:
Business Unit:
From Project Number:
To Project Number:
Placed in Service Through Date:
Business Unit:
From Project Number:
To Project Number:
Placed in Service Through Date:
Book
Subledger Application: Assets
Ledger:
Process Category:
End Date: <Sysdate>
Process Category: Final
Process Events: All
Report Style: Summary
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Journal Batch:
Include User Transaction Identifiers: No
Book:
Close Period: No
Business Unit:
Legal Entity:
From Accounting Date:
To Accounting Date:
Business Unit:
Legal Entity:
From Accounting Date:
To Accounting Date:
Business Unit:
Legal Entity:
From Accounting Date:
To Accounting Date:
Business Unit :
Transaction Source : Global Intercompany
Default Due Date: Sysdate
NA
NA
Business Unit:
Number of Instances: 1
Subledger Application : Receivables
Ledger:
Process Category :
End Date : <Sysdate>
Process Category : Final
Process Events: All
Report Style : Summary
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Journal Batch:
Include User Transaction Identifiers : No
Business Unit:
Ledger:
Source:
Import Set:
Invoice Group:
Hold:
Hold Reason:
Accounting Date:
Purge: No
Summarize Report: No
Number of Parallel Processes: 1
Business Unit:
Ledger:
Option: All
Business Unit:
Ledger:
Source:
Import Set:
Invoice Group:
Accounting Date:
Purge: No
Summarize Report: No
Business Unit: All authorized business units
Type: Expense Reimbursemenmts
Business Unit:
Subledger Application: Payables
Ledger:
Accounting Period: current period
Accounting Mode: Final
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Include User Transaction Identifiers: No
Subledger Application: Payables
Ledger:
Process Category:
End Date: <Sysdate>
Process Category: Final
Process Events: All
Report Style: Summary
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Journal Batch:
Include User Transaction Identifiers: No
Template:
Submit Payment Selection Report
Data Access Set:
Source:
Ledger:
Group ID:
Post Account Errors to Suspense:
Create Summary Journals:
Import Descriptive Flexfields:
AutoPost Criteria Set:
Data Access Set:
Ledger:
Reconciliation Type :
To Accounting Period: Current Period
Gather Statistics: Yes
Maintain Indexes: No
Control Budget:
From Budget Period:
Rule or Rule Set:
Journal Category: Allocations
Conversion Rate Type: Corporate
Post Allocations:
Business Unit:
Cutoff Date:
Cost Organization:
Cost Limit:
Bill to Business Unit:
Commit Limit:
Number of Worker Processes:
Subledger Application: Receipt Accounting
Ledger:
Process Category:
End Date: <Sysdate>
Process Category: Final
Process Events: All
Report Style: Summary
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Journal Batch:
Include User Transaction Identifiers: No
Subledger Application: Cost Management
Ledger:
Process Category:
End Date: <Sysdate>
Process Category: Final
Process Events: All
Report Style: Summary
Transfer to General Ledger: Yes
Post in General Ledger: Yes
Journal Batch:
Include User Transaction Identifiers: No
Run Control:
Frequency Time Notification Condition
Every Hour
Every Hour
Once Per Day
Daily
Weekly
Daily
Every Hour
Every Hour
Daily
Daily
Daily
On Demand
Once Per Day
Once Per Day
Once Per Day
Once Per Day
Polls for file every 60 seconds Every minute
Polls for file every 60 seconds Every minute
Every Hour Every Hour
Every Hour Every Hour
Every Hour Every Hour
Multiple Times Per Day
Multiple runs at different time intervals.
Once Per day
Daily
Daily
Once Per Day
On Demand
Monthly 1st day of
Month
Multiple Times Per Day
On Demand
On Demand
Multiple Times Per Day
Once Per Day
Twice a day
Twice a day
Twice a day
Twice a day
Twice a day
Twice a day
Twice a day
Notification to Notification Report Name RICEF Nr./ Process
IC Batch Creation
IC Batch Creation
IC Batch Creation
IC Batch Creation
Customer Balance
Customer Balance
Customer Balance
Create Accounting
AP Invoice Management
AP Invoice Management
Create Accounting
Create Accounting
Journal Posting
GL Reconcilation
Paas Ess Job Code Component Type SOA Composite name BI Report Name Path
NA ERP Job
ERP Job
ERP Job
ERP Job
ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
NA ERP Job
Validate Payables Invoices ERP Job
Initiate AP Invoices ERP Job n/a
Submit Payment Batch ERP Job n/a
NA ERP Job
NA ERP Job
ERP Job
NA ERP Job
Schedule System Comments
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud Import for every combination of the source and BU
ERP Cloud
ERP Cloud Recognizes project contract revenue according to contractual terms by creating revenue dis
ERP Cloud Invoices project contract customers according to contractual terms by creating invoice head
ERP Cloud
ERP Cloud Invoices should be validated after & approved
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud Refresh Customer Balances to see them correct from UI
Screen
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud Import one time payment invoices
ERP Cloud Import expense reports as payment requests to Payables
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud Import Journals from all standard sources
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
ERP Cloud
contractual terms by creating revenue distributions, which are the source of revenue accounting entries.
ontractual terms by creating invoice headers, lines, and distributions.
hich are the source of revenue accounting entries.
d distributions.
Time
(Eastern) Day -2 Day -1 Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8
(Central)
1:00 AM
12:00 AM
2:00 AM
1:00 AM
3:00 AM
2:00 AM
4:00 AM
3:00 AM
5:00 AM
4:00 AM
6:00 AM
5:00 AM
7:00 AM
6:00 AM
8:00 AM
7:00 AM
9:00 AM
8:00 AM
10:00 AM
9:00 AM
11:00 AM
10:00 AM
12:00 PM
11:00 AM
1:00 PM
12:00 PM
2:00 PM
1:00 PM
3:00 PM
2:00 PM
4:00 PM
3:00 PM
5:00 PM
4:00 PM
6:00 PM
5:00 PM
7:00 PM
6:00 PM
8:00 PM
7:00 PM
9:00 PM
8:00 PM
10:00 PM
9:00 PM
11:00 PM
10:00 PM
12:00 AM
11:00 PM
Order Oracle Module Task
34 Purchasing PO.1
35 Purchasing PO.1.1
36 Purchasing PO.2
37 Purchasing PO.3
38 Purchasing PO.4
39 Purchasing PO.5
40 Purchasing PO.6
Task Description
Complete All Transactions for the Period
Notify requesters and buyers their requisitions were created
Review Outstanding and Overdue Purchase Orders (Optional)
Follow up on outstanding receipts - check with Suppliers
Mass Close or Finally Close Purchase Orders (Optional)
Complete the Payables Period-End Process
Perform Period-End or Year-End Budgetary Control or
Encumbrance Processing (If Applicable)
ESS Job Name
Confirm Receipts Workflow
Instructions and Recommendations
Ensure all transactions are entered and completed for the period being closed:
• Complete and approve purchase requisitions
• Complete and approve purchase orders
• Complete receipts and returns
Submit the Confirm Receipts Workflow to send notifications to requestors or buyers who have created
requisitions in Self-service Procurement. The Confirm Receipts Workflow sends notifications for items
with a destination type of Expense, a Routing of Direct Delivery, and a Need–By date that is equal to
or later than today’s date.
Notification recipients can create receipt transactions by responding to the notification or by entering
them on the Receiving work area.
Use custom analysis reports to review outstanding purchase orders, including quantity ordered and
received details.
For purchase orders that have not been received, the appropriate department can use the details
obtained from the Purchasing Real Time subject area, to follow up on the status of the ordered items
with the suppliers. If the goods have been received, but the receipt has not been entered into
Receiving, the receipt transaction needs to be entered by the appropriate personnel.
Note: Where you have selected to accrue receipts at period end, make sure all receipts are entered
for a specific period, before creating receipt accruals for that period. It is not necessary to enter all
the receipts for a period prior to closing that period. Simply backdate the receipt date when entering
receipts for a closed period.
Warning: If Inventory is implemented, it is not possible to process a receipt to a closed Cost
Management period.
Purchase orders for which no further invoice/receipt activity is expected can be mass closed/finally
closed. Finally closing orders will release any unused funds. In the Purchasing Work Area, select the
Close Schedules in Spreadsheet task, enter the criteria, such as budget date, of the orders to be
closed. This will download a spreadsheet with all of the schedules satisfying the criteria, and you can
select the action (Close/Finally Close) for each row and upload the results to close the orders.
Complete the steps to close the Payables period, to enable the creation of receipts accrual entries.
Performing the Payables Period-End process effectively prevents any further invoices or payments
from being entered into Payables for the closed period.
Note: Procurement does not have periods to open or close.
Identify procurement transactions you plan to carry forward into the new fiscal year. Cancel or final
close any procurement transactions you are not carrying forward to the new fiscal year. The
Budgetary Control module will automatically release the unused funds when you cancel or final close
the procurement transactions. The General Ledger module will generate encumbrances accounting
entries to reverse the encumbrance balance when the Create Accounting process is submitted.
Responsible Target Date
