Wednesday Aug 28, 2013

HCM: North America Year End is Just Around the Corner!

Are you ready for Year End? As we all know, Year End is a very busy time of patching, processing, sending out employee tax reports, and governmental filings. Oracle Support and Oracle Development want to help ensure a successful year end for your business.

Timing - The legislative deadlines are still a few months away, but here is a quick reminder of the timing:

 United States

Year End forms are due to all employees by January 31, 2014, followed by Federal and State Filings

 Canada Employee Year End forms and the government Year End Magnetic filings are due at the end of February
 Mexico Various employee reports and government filings are due between January 31st and May 31

Patching Information  - Refer to the following notes for important patching information that you’ll need for Year End.  As a reminder, the current Roll up Patch (RUP) is a mandatory requirement for Year End processing in the Oracle Payroll localizations delivered by Product Development legislations and US Federal HR products.  So you want to be prepared by having the latest RUP patch already tested & applied.

 United States & Canada Doc ID 111499.1 - Oracle North American Payroll - 11.5.x Mandatory Patches
Doc ID 386434.1 - Oracle North American Payroll - 12.0.x Mandatory Patches
Doc ID 858794.1 - Oracle North American Payroll - 12.1.x Mandatory Patches
 Mexico Doc ID 941742.1 - Oracle Mexican Payroll - 12.0.x Mandatory Patches
Doc ID 941673.1 - Oracle Mexican Payroll - 11i.x Mandatory Patches
Doc ID 941743.1 - Oracle Mexican Payroll - 12.1.x Mandatory Patches

Note for R11i users: Please be aware of year end support for each legislation.  As announced in the NA Payroll World:  R11i US and Canadian Payroll customers who are on (and who purchased Extended Support) will be supported through Year End 2014. R11i Mexico Payroll customers are only supported through Year End 2012.

Patching Schedule - Stay tuned for the release of the Year End patches.  Here are the targeted release dates:

US & Canada:

Year End Phase 1 – End of September
Year End Phase 2 – December 15th
Year End Phase 3 – January 15th 

Reference Doc ID 216109.1 Oracle Human Resources (HRMS) Payroll North America Annual Patching Schedule

Mexico (no specific target dates, but here’s the typical schedule we’ve seen over the last few years):

Year End Phase 1 – Mid December
Year Begin – End of December
Year End Phase 2 – End of January

Reference Doc ID 975677.1 Mexico HRMS 2012 Year End Patch Release Schedule

Also refer to the following note from time to time, as it will be updated as new information becomes available:  Doc ID 1577601.1 North American Year End 2013 / 2014 Year Begin Patch Information and Useful Links.

Advisor Webcasts - Again this year, the North America Payroll Team will be hosting the Year End Advisor Webcasts to deliver information to assist you for year end processing.  Once the schedule & topics are finalized, the webcasts will be announced.  In addition, you can view past webcasts that have been archived.   For the current schedule and links to the archives, refer to the following note: 

Doc ID 740966.1 Advisor Webcasts: Current Schedule and Archived Recordings.  

Be sure to check the note frequently for details of upcoming webcasts...don’t miss out!

Thursday Aug 22, 2013

Why Doesn't My Sales Order Generate A Contract?

When a Sales Order is created in Order Management which includes a Service line, when the order is booked and shipped a Service Contract is created (or amended depending on the order).

In some cases, the service contract is not created.  In this blog post I try to give some pointers to help you debug this integration point.  Note that in R12 there was a change in how this integration point works, here I refer only to R12 functionality.  If you are on an earlier EBS release please see Doc ID 463912.1 for troubleshooting steps.

Is your order interfaced?

Make sure that your order has been successfully shipped and the line has been interfaced.  Sometimes the order can be deferred until a future date.  Check the OM workflow to see if that's happened.  You'll see the deferred date in the OM Order Line (OEOL) 'Fulfill' node.  If it's not deferred to a future date but is not closed, then running the Workflow Background Process is required to progress the workflow.

Is the instance created in IB?

Make sure that the install base instance has been created.  Search in IB using the sales order number and make sure that the item with the linked service line is created as an instance.
Remember that the inventory item must be set up with 'Track in Installed Base' and 'Service Allowed' set to yes (ticked) in the item master.

What's the status of the interfaced record?

When the sales order is processed, a record is created in the OKS_REPROCESSING table.  Check the status of the this record in Service Contracts > Reprocess Order.
Query using the sales order number. This should return the sales order with a status of NEW (if the record is available for processing) or ERROR (if the record has been processed but failed to create the service contract).
If the status is NEW then all you have to do is select it for processing and then submit the Service Contracts Order Processing concurrent program.
If the status is ERROR then the error message displayed should give you an indication of why the contract creation has failed.

If all fails and you can't find the order in the Reprocess Order form, the query below will return order numbers with service lines which have not created a contract and are not in OKS_REPROCESSING table.   
select ord.order_number "Order_Number",
ord.header_id "Order_Id",
line.service_reference_line_id "Reference ID",
line_id "Service_Line_ID"
from csi_item_instances ib,
oe_order_lines_all line,
oe_order_headers_all ord
where not ib.last_oe_order_line_id is null
and ib.last_oe_order_line_id = line.service_reference_line_id
and ord.header_id = line.header_id
and line.flow_status_code = 'CLOSED'
and line.service_reference_type_code = 'ORDER'
and line.line_id not in
(select order_line_id from oks_reprocessing);
You can then use this information to implement a workaround such as creating the service contract manually OR you can log a service request with Oracle Support to get a datafix which will insert the missing order lines into OKS_REPROCESSING.

The following notes also have useful information about this integration point:
Integration Troubleshooting: Order Management to Service Contracts (Doc ID 1455545.1)
R12 How to Process Order Lines from Order Management to Create Service Contracts (Doc ID 785760.1)

Webcast: Using Subledger Accounting (SLA) to Override Accounting Created by Auto-Accounting


Webcast: Using Subledger Accounting (SLA) to Override Accounting Created by Auto-Accounting

Date: September 4, 2013 at 11 am ET, 10 am CT, 9 am MT, 8 am PT

Learn how Subledger Accounting(SLA) allows you to select accounting combinations from a variety of sources. Get an overview of the components of SLA and how they can be used to influence the accounting created by the sub-ledgers. This one-hour session is recommended for technical and functional users of Receivables, Payables, Fixed Assets and the other subledgers who would like more information on using SLA to override accounting created by AutoAccounting in Release 12. We will discuss Journal Line Types, Account Derivation Rules, Mapping Sets, Journal Descriptions and the use of Descriptive Flexfields. Illustrative examples showing account replacement will also be provided.


  • Use of Journal Line Types
  • Account Derivation Rules
  • Mapping Sets
  • Journal Descriptions
  • Use of Descriptive Flexfields
  • Examples showing account replacement:
    • for negative revenue lines with a fixed accounting combination
    • for freight lines with fixed accounting based on the Transaction Line Descriptive Flexfield
    • for exchange gain and loss based on the Transaction Type Receivable Account or Remittance Bank Cash Account.


For more details and how to register see Doc ID 1564394.1

Wednesday Aug 21, 2013

New 12.1.3 Procurement Rollup Patch Specific for Approvals

See the newly released 12.1.3 Procurement Rollup patch specific for Approvals.
Here is a high level overview of the fixes included in this Approvals Patch 16932593:R12.PO.B:

1.      Approvals Management Engine (AME)

  • AME Approval can be completed successfully even when the document verification has failed. Added logic to inform parent workflow to continue when verification fails.
  • The approval chain correctly starts from the submitted of the document when using PO AME approval.

2.      EDI

  • Vendor site attachment is aligned to the purchasing document.

3.      Purchase Order Approval

  • Accessing document from approval notification is enhanced.
  • Code related to Document forward are enhanced, this is a major feature used by business users to manage document pending for approval with ex-employees and document pending with employees on vacation.
  • Performance issues on PO approval are rectified and fine-tuned

4.      Requisition Approval

  • Action history on requisition document is fine tuned to capture delegation and forward to actions.

5.      Supplier communication

  • Email Notification to supplier displays supplier country of origin instead of supplier country.
  • Enhancement to trigger notification to supplier if Requisition associated to Purchase order is cancelled

Visit Doc ID 1567464.1  for complete details on this patch.

Tuesday Aug 20, 2013

AR: News Collection

Below is a listing of our recent blog postings on topics in the Accounts Receivables (AR) product area:

HCM: News Collection

Below is a listing of our recent blog postings on topics in the Human Capital Management (HCM) product area:

AR: Are you still on Release 12.0? Recommendations For A Smooth Month End Close In Oracle Receivables

Oracle Receivables highly recommends the following if you are running R12.0 application version.

1.  Upgrade to 12.0.6 if you are not on 12.0.6.

2.  Apply the latest consolidated patch for Receivables: Patch 12702898:R12.AR.A

3.  Run Import/Validate AAD following the following notes:

4.  Use the Subledger Period Close Exception Report to view all accounting events and journal entries that fail period close validation. This report helps in resolving exceptions quickly so that exceptions are not left to slow down the period-end close. It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or non-transferred journal entries.
You can also generate the Subledger Period Close Exceptions Report through a concurrent request as follows:

Receivables Responsibility:
Nav: Control -> Requests -> Run
Execute the Subledger Period Close Exceptions Report

For more information on this report see Doc ID 793598.1: How to Use the Subledger Period Close Exceptions Report for Period Close Activity?

5.  Additional Patches on top of RUP patch listed below, these are current versions as of August 20, 2013.


Patch Number

Fixed File Version

Accounting Program Package 10381819:R12.AR.A ARPXLEXB.pls 120.77.12000000.105
Rules .ldt 16355924:R12.AR.A ARXLAAAD.ldt 120.47.12000000.84
Accounting Generation Package 15960521:R12.AR.A ARPDDB.pls 120.51.12000000.133
Xransfer to General Ledger 12965313:R12.XLA.A xlaaptrn.pkb 120.61.12000000.33
Rounding issues for RA CUST TRX LINE GL DIST ALL TABLE 14575753:R12.AR.A ARPLCREB.pls 120.31.12000000.29
Revenue Recognition 14102661:R12.AR.A
ARPLARLB.pls 120.42.12000000.17
Aging 7 Bucket Report 16308319:R12.AR.A ARXAGMW.rdf 120.54.12000000.67
Rounding Applications table 10176632:R12.AR.A ARRECACB.pls 120.44.12000000.52
AR Reconciliation Report 14085187:R12.AR.A ARRECONB.pls 120.22.12000000.20
AR to GL Reconciliation Report 14376360:R12.AR.A ARGLRECB.pls 120.21.12000000.43

Have You Tuned Up Your Concurrent Processing Processes?

Back in December we posted a blog about the new Concurrent Processing Analyzer, but this is such a cool tool that we thought we'd just send out another reminder!

The CP Analyzer will help you Self-Service your CP footprint. Take a look at Doc ID 1411723.1 it has the script to download plus a 9 min video to tell you all about how to use it.

Concurrent Processing Analyzer Features

This is a non-invasive script which provides recommended actions to be performed on the instance it was run on.  For production instances, always apply any changes to a recent clone to ensure an expected outcome.

Benefits include:

  • E-Business Applications Concurrent Processing Analyzer Overview
  • E-Business Applications Concurrent Request Analysis
  • E-Business Applications Concurrent Manager Analysis
  • Identifies Concurrent System Setup and configurations
  • Identifies and recommends Concurrent Best Practices
  • Easy to add Tool for regular Concurrent Maintenance
  • Execute Analysis anytime to compare trending from past outputs

Go to Doc ID 1411723.1 for more details and script download.

Feedback welcome!

Monday Aug 19, 2013

HCM: Three New Troubleshooting Assistants for HCM...and One Gets a New Look

You may be familiar with the term "Search Helper".  A Search Helper for iRecruitment was introduced last year as an easy and fast method to finding a relevant, complete solution to common issues encountered by our customers.  Search Helpers exist for many products across the E-Business Suite.

Search Helpers have been re-tooled to provide an improved customer experience within My Oracle Support.  Part of that re-tooling includes reformatting and renaming the Search Helpers to one or more Assistants that more clearly define the intent or purpose of the guided resolution.  Whether you are using the Assistant within My Oracle Support to resolve an issue through Search/Browse or as part of SR creation, you will notice a different look to the Assistants, but the same information as was previously available via the Search Helpers will be provided via the Assistants.

Here's a new look at the Troubleshooting Assistant for iRecruitment (Doc ID 1451641.1):

Three new Troubleshooting Assistants have been published to help you resolve errors in HR and Payroll.
Check out the new assistants:
ORA Errors in HR - Doc ID 1561356.1
ORA Errors in Payroll -  Doc ID 1561515.1
APP Errors in Payroll - Doc ID 1566491.1

For a full listing of all assistants in EBS check the index note Doc ID 1501724.1.

Friday Aug 16, 2013

Procurement Community Development Corner is Now Live!

We are excited to announce the launch of our Procurement Community Development Corner, which is now live!  Visit this area regularly to get the latest information straight from the Procurement Development teams. 

We encourage you to participate in any of the discussions presented in this region whether you have additional questions, want to share some best practices, or just want to comment on the discussion.   Check it out!  

AR: Learn The Impact Of System Options Checkbox "Create Detailed Distributions"

The Create Detailed Distributions check box in the Receivables system options form was created as part of the "Merge Distributions Enhancement" (Bug: 7559194: LINE LEVEL DISTRIBUTIONS NOT NEEDED FOR HEADER LEVEL CASH APPLICATION/ADJUSTMENT).  Distributions were getting created at the level of granularity of an invoice line.  This would result in a large number of distributions/meta data being passed to the Sub ledger Accounting Module.

When the checkbox is checked, Receivables will create detailed invoice line level distributions.  These detailed distributions allow the system to create line level applications for receipts and adjustments.

You should CHECK this checkbox if any of the conditions below are true:

1. If the Primary or Secondary ledgers associated with the operating unit is using one of the following subledger accounting representations:

  • The Multifund Receivable accounting representation, where receivable accounting lines for an invoice are created at the level of invoice line.
    Note: Release 12 seeds Subledger accounting methods: Multi-Fund Accrual - Account Method and Multi-Fund Accrual - Balancing Method
  • The Cash Basis accounting representation, where accounting is created only at the time of receipt of cash.
    Note: Release 12 seeds Subledger accounting methods: Encumbrance Cash and Standard Cash

2. If you want to apply receipts or adjustments to invoice lines using Line level Cash Application feature or Line Level Adjustment feature.

3. If you want to derive account code fully or partially from the invoice lines when accounting for adjustments or receipt applications.

Keep in mind that checking this box could cause performance issues.  There will be a larger volume of distribution records, which could potentially cause performance issues during the Submit Accounting or Create Accounting process for Receipt Applications.  There are two patches that will aid in performance issues (Patch 16198666 and Patch 16060007) See Doc ID 1534178.1 and Doc ID 1481222.1 for more details in preventing any performance related issues.

When the checkbox is UNCHECKED, Oracle Receivables will create summarized distributions. The receivable distributions for adjustments and applications are not maintained at the invoice line level, instead a summarized receivable distribution is created at the invoice header level. Adjustments and receipt applications are not pro-rated across the invoice lines. This is same way the receivable distributions are created in Release 11i.

Following is the impact of having the checkbox UNCHECKED:

  • When you create Batch Sources (Navigation: Setup > Transactions > Sources), in the Batch Source tab, the checkbox Generate Line Level Balances will be disabled.
  • When you create Receipt Applications (Navigation: Receipt > Receipts) in the Applications form, the Apply in Detail button will be disabled.
  • When you create Adjustments against transactions (Navigation: Transactions > Transactions, Toolbar Menu Actions > Adjust) in the Account, IDs tab, the Line column will be disabled.
  • When using the Receipt or Adjustment APIs, you cannot create line level applications.

For an explanation on the validation that takes place when checking and unchecking the box see Doc ID 1081657.1.


Thursday Aug 15, 2013

Top Adpatch Patching Issues For Release 11i And 12.x

Do you have problems or questions applying E-Business Suite patches?
Do you want to learn more about:

  • Patching strategy
  • Minimizing the risks when applying a patch
  • How to troubleshoot different patching issues
  • What information can be useful and should be uploaded in service requests or community threads (depending on the issue received)

Then use Document Id 1444322.1 Top Adpatch Patching Issues For Release 11i And 12.x as your starting point.  This document has a wealth of information about how to plan your patching so that you have a successful patching session and how to resolve failures if they happen anyway.

Many patch issues can be resolved quickly by following the troubleshooting steps in Doc ID 1444322.1.  If you need extra help try searching the E-Business Suite Patching Community by patch number first, someone else may have already hit and resolved your issue.  If you need to log a service request then providing information about all the troubleshooting steps you've already followed will help avoid you having to answer the same questions again; provide us all needed information (including all the patch log files) and you may find that we can answer your patching issue from the first update!

Want to discuss this some more?  Come and join us in the E-Business Suite Patching Community and discuss patching issues with Oracle experts and industry peers.

HCM: Introducing the 'RetroPay Analyzer' for EBS Payroll

The HCM Proactive Support Delivery Team is introducing a new Health-Check script - RetroPay Analyzer - to assist in proactive analysis of your RetroPay environment.

RetroPay Analyzer script reviews the current RetroPay parameters information, setup information, profiles, assignments statuses, custom / seeded retro elements, retro success and failed information, any history, instance patching and references along with providing helpful feedback / recommendations, and best practices for any RetroPay related areas highlighted as a concern on your system. 

To obtain the RetroPay Analyzer, go to

When reviewing the analyzer output, you can immediately see when issues are identified as they are displayed in red so that they are easily seen.  In addition to identifying areas of concerns, the analyzer also identifies My Oracle Support (MOS) articles which can be utilized to resolve the issue.

Proactive RetroPay Analyzer Benefits:

  • Immediate Analysis and Output of your RetroPay Environment
  • Parameter driven, so can be executed for a specific Business Group or Legislation
  • Identifies any issues and displays content for immediate attention
  • Identifies and Recommends RetroPay Best Practices
  • Ability to execute the analyzer at any time

Additionally, Oracle will be delivering instructions on how this Analyzer can be set up as a concurrent request so that our Functional Colleagues, who actually perform the RetroPay processing, will have the ability to run this Analyzer if required.  

To obtain the concurrent manager setup, go to

  • Doc ID 1568260.1 How to run EBS Payroll - RetroPay Analyzer Tool as a Concurrent Request.

Tuesday Aug 13, 2013

Are you Running EBS 12.1.1 or 12.1.2 in Production?

If you are currently on EBS 12.1.1 or 12.1.2 then the standard recommendation is is to apply the EBS 12.1.3 suite-wide Release Update Pack.  If you can't apply the suite-wide 12.1.3 Release Update Pack, you should apply the individual 12.1.3 Family Packs for the EBS products that you've deployed.

But, guess what, you're probably already closer to EBS 12.1.3 than you think!  Why is that?  If you've applied any patches to your 12.1.1 or 12.1.2 environment, you probably already have much of 12.1.3 already in production today.  (You can read more about this and the background to it in the EBS Technology Blog here).

Check this out yourself and see just how close to EBS 12.1.3 you may be.  The Oracle Applications Manager contains a tool that all Apps DBAs should use: Patch Wizard.  The Patch Wizard has an 'Analyze Specific Patches' function that tells you how a specific patch will affect your system.

The resulting 'Patch Impact Analysis' report provides you with a summary of:

  • Applications patched
  • New files introduced
  • Existing files changed
  • Existing files unchanged.

You can learn more about patch wizard, including the latest improvements, in Doc ID 976188.1.

Monday Aug 12, 2013

Are You Taking Control of Your Workflow Processes with Workflow Analyzer?

Get immediate analysis and output of your EBS workflow environment by using the EBS Workflow Analyzer! This script reviews the current workflow footprint, analyzes the configurations, environment, provides feedback and makes recommendations on best practices and areas of concern.

Go to Doc ID 1369938.1 for more details and script download with a short overview video.

Proactive Workflow Analyzer Benefits:

  • Immediate Analysis and Output of Workflow Environment
    • Identifies Aged Records
    • Identifies Workflow Errors & Volumes
    • Identifies looping Workflow items and stuck activities
    • Identifies Workflow System Setup and configurations
    • Identifies and Recommends Workflow Best Practices
  • Easy To Add Tool for regular Workflow Maintenance
  • Execute Analysis anytime to compare trending from past outputs

The Workflow Analyzer presents key details in an easy to review graphical manner. For example, the Workflow Runtime Data Table Gauge will show critical (red), bad (yellow) and good (green) depending on the number of workflow items (WF_ITEMS). A pie chart shows the workflow error notification types and a bar chart shows the workflow runtime data footprint.

Workflow analyzer outputs

Have questions?  Visit the My Oracle Support EBS - Core Workflow Community.


Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected



« August 2013 »