Monday Mar 07, 2016

EBS Financials February 2016 Recommended Patch Collections (RPCs) Released!

Oracle E-Business Suite (EBS) Financials Development has released February 2016 Recommended Patch Collections (RPCs) for the following products:
  • Assets
  • Cash Management
  • Collections (coming soon)
  • E-Business Tax
  • Calculation
  • Reporting Ledger
  • iReceivables
  • Loans
  • Payables
  • Receivables
  • Sub-Ledger Accounting
  • Payments
  • Internet Expenses
For details and the complete list of available RPCs for Oracle EBS Financials, please see Doc ID 954704.1, EBS: R12.1 Oracle Financials Recommended Patch Collection (RPC).

Thursday Mar 03, 2016

Upgrade BOM's With Confidence

Upgrading from 11i to R12 and you use Bill of Material's (BOM's)? Strike before you upgrade to avoid known errors related to duplicate BOM's. In later versions of 11.5.10, index BOM_STRUCTURES_B_U1 was added to prevent the ability to create duplicate BOM's. Great, right? Yes, very great, except in a case where you are upgrading to R12 and you haven't checked for and removed old duplicate BOM's, before or if index BOM_STRUCTURES_B_U1 was added. If you have duplicate BOM's, upgrade processes such as the one offered in Doc ID 1082375.1, will fail. You can get ahead of this issue by using note, Find Two Bills of Material (BOM) for the Same Item (BOMFDBOM) leading to ORA-01427 or SQL-02112 error (Doc ID 370841.1).

Duplicate BOM's not only can cause errors while upgrading, they can cause different issues in your system and affect resources. Use Doc ID 370841.1 to help check for duplicate BOM's and let's make sure duplicate BOM's don't throw a wrench into your upgrade.

Tuesday Feb 23, 2016

Rapid Install StartCD 51 for EBS 12.2 is Now Available!

Announcement: Rapid Install StartCD 51 for EBS 12.2 is Now Available!

Tuesday Feb 16, 2016

Affordable Care Act (ACA) Employer Information Reporting Requirements for Reporting Year 2015

We would like to make you aware of some recent E-Business Benefits patch releases that provide important updates concerning the Affordable Care Act (ACA) Employer Information Reporting requirements for reporting year 2015. As has been mentioned in previous announcements: In order to accommodate the Employer Information Reporting requirements under the Affordable Care Act, Oracle Development is following a "phased" approach by delivering a series of patches that supply what is required for supporting Forms 1094-C and 1095-C.

Since the beginning of this year, the following ACA Reporting-related patches have been released for Release 11i*, 12.1 and 12.2 customers.

2015 ACA Consolidated Reporting Patch - I**

Patch Highlights:

  •  New multi threaded concurrent process for printing employee/recipient Forms 1095-C
  •  New options to rearchive a single employee's data and/or print (or reprint) a Form 1095-C for a single employee via the View Employee Archive Data Page.
  •  Miscellaneous additional bug fixes

Please see the following readme's on My Oracle Support for full details:

  • Document 2098441.1 - 2015 Employer Shared Responsibility Reporting Under the Affordable Care Act - Consolidated Reporting Patch Functional Readme for Release 12.1 Customers
  • Document 2098463.1 - 2015 Employer Shared Responsibility Reporting Under the Affordable Care Act - Consolidated Reporting Patch Functional Readme for Release 12.2 Customers

**Note that the 2015 ACA Consolidated Reporting Patch - I includes both ACA Reporting Phase I and Phase II patches.

2015 ACA Reporting Phase II ***

Patch Highlights:
  • Additional Setup for ACA (optional)
  • New Concurrent Programs to archive and print the necessary Employee 1095-C data as well as the ability to purge the archived data, if needed.
  • New View Employee Archive Data Page

Please see the following readme's on My Oracle Support for full details:

  • Document 2089792.1 - 2015 Employer Shared Responsibility Reporting Under the Affordable Care Act - Phase 2 Functional Readme for Release 11i Customers
  • Document 2089776.1 - 2015 Employer Shared Responsibility Reporting Under the Affordable Care Act - Phase 2 Functional Readme for Release 12.1 Customers
  • Document 2089761.1 - 2015 Employer Shared Responsibility Reporting Under the Affordable Care Act - Phase 2 Functional Readme for Release 12.2 Customers

*** Note the 2015 ACA Reporting Phase II patch includes the 2015 ACA Reporting Phase 1 patch.
**** Note that the Release 11i 2015 ACA Reporting Phase II patch also includes both the 2015 ACA Reporting Phase 1 patch AND the ACA Consolidated Reporting Patch - I updates (and more).

Further patches will be forthcoming in early 2016 that will provide EBS US Standard and Advanced Benefits customers with the ability to input data for COBRA eligible employees (those who gained eligibility due to reduction of hours) when COBRA is administered by a third party. This will include eligibility/offer and cost information along with details on the coverage of the COBRA employee and dependents in self-insured plans. Additionally, further "consolidated reporting" patches will also be released that contain important ACA Reporting-related bug fixes. Future patches will also deliver the ability to file/transmit employer information returns electronically with the IRS. Please note Oracle Development will not be supporting paper filing with the IRS.

More information on the Affordable Care Act can found on My Oracle Support in

  • Document 2007993.2 – Information Center: Oracle HRMS (US) – Affordable Care Act (All Application Versions).

This page provides information on the Employer Shared Responsibility Provisions and Reporting as well as other Affordable Care Act information by providing links to the following whitepapers (and other documents) on My Oracle Support:

  • Document 2052173.1 - US HCM & Benefits Affordable Care Act High Priority Alert
  • Document 2052175.1 - Oracle EBS US Benefits & HCM Affordable Care Act Mandatory Patches
  • Document 1597102.1 - Oracle E-Business Suite Advanced Benefits Position Statement: Patient Protection and Affordable Care Act 2010 & Affordable Care and Education Reconciliation Act 2010
  • Document 1930035.1 - Oracle E-Business Suite Advanced Benefits Position Statement: Employer Shared Responsibility Reporting
  • Document 1990141.1 - Oracle E-Business Suite: Patient Protection and Affordable Care Act 2010: Using System Extract to View Eligible Employee Service Hours
  • Document 1542487.1 - Oracle E-Business Suite US HR & Payroll Position Statement: Employer Shared Responsibility Provisions Under the Affordable Care Act
  • Document 1091444.1 - Oracle E-Business Suite US Payroll Position Statement: Patient Protection and Affordable Care Act 2010 & Affordable Care and Education Reconciliation Act 2010

Also, you can ask questions or start discussions about the ACA on My Oracle Support Community with members of Oracle Development and Support or other customers by going to the Compensation and Benefits - EBS (MOSC) and clicking on Category Affordable Care Act (ACA). In this Community, you may also find links to recent Advisor Webcasts on the Affordable Care Act along with followup questions & answers (Q&A).

*Important Note:

Please note that the 11i patch is only available to those customers who have purchased continuing legislative support for the US HRMS localization as the 11.5.10 Sustaining Support Exception (which includes tax, legal, and regulatory updates for US and Canadian HRMS customers on Release 11.5.10.CU2) ended 31 December, 2014. To obtain any 2015 ACA Reporting patch, Release 11i US Payroll customers will need to consult the following documents on My Oracle Support which contain critical information as to when regulatory/statutory support ends as well as additional support coverage options that are available:

  • Document 1495337.1 - ANNOUNCEMENTS: E-Business Suite 12.1 Premier Support Now Through Dec. 2016 and 11.5.10 Sustaining Support Exception Updates
  • Document 1494891.1 - E-Business Suite Releases - Support Policy FAQ
  • Document 1596629.1 - ANNOUNCEMENT: Additional Coverage Options for 11.5.10 E-Business Suite Sustaining Support

Monday Feb 15, 2016

How Does the 2016 Leap Year Impact Fixed Assets?

A leap year affects calendar setups as well as depreciation calculations in Fixed Assets.  Leap year for a monthly calendar means just having February end on the 29th rather than the usual 28th.  However, for a daily calendar, the additional day will need to be added to any period in the calendar, since the maximum number of periods a calendar can have is 365.  Therefore, one period in the calendar will have two days in it.  For example, the 28th of February could be from the 28th of February to the 29th of February, or the 30th of December could be from the 30th of December to the 31st of December.

Usually calendars for the next fiscal year get set automatically by the depreciation run when the last period of the fiscal year is closed.  In the case of a leap year, it is recommended that the calendar be set in advance so that the additional day shows up in the correct period and in the correct way for your business requirements.  If the calendar was not set up in advance and you find it is not set correctly for your business requirements, the following steps may be used to re-set the dates correctly (for unused periods):

1.  Query the calendar in the calendars form

2.  Go to the last recordFeb 29

3.  Delete the last record

4.  Save

5.  Delete the new last record

6.  Save

7.  Repeat until you arrive at the currently open period, which you cannot delete

8.  Add new periods back in with your amended dates

Leap year does not affect depreciation calculations for books with even allocation and monthly calendars.   However, books with allocation by days and daily calendars, will show a change in the depreciation expense amounts.

Here is an example of an asset with a cost of $3000, depreciating at 33.33%.
Depreciation for Feb-2015 would be calculated as follows:
= (3000*33.33%) / 365*28

In a leap year, the same asset has depreciation for Feb-2016 calculated as follows:
= (3000*33.33%) / 366*29

To extend the example ahead, look at the Mar-2016 depreciation calculation:
= (3000*33.33%) / 366*31
= 84.70

Basically, the yearly depreciation remains the same but the allocation between periods changes.  So, where an earlier yearly depreciation was divided by 365 days, for a leap year it is divided by 366 to calculate a day’s depreciation.  The depreciation for each calendar period is calculated based on the date function counting the number of days between the from- and to-dates, i.e., between the 1st of February and the 29th of February there are 29 days and between the 1st of March and the 31st of March there are 31 days.

Some additional examples can be found in Doc ID 564999.1 - R11i Depreciation Program (FADEPR) Calculates Wrong Depreciation For Leap Year.

With credit to Anshu Malhotra, Oracle Assets Support

Friday Feb 12, 2016

Dutch Legislation - SHA-256 Hash Code Generation for Dutch Sepa XML Patches Released

The following patches have been released via My Oracle Support for the following: 

Dutch Legislation - SHA-256 Hash Code Generation for Dutch Sepa XML

  Release 12.1 : Patch 22605799:R12.PAY.B
  Release 12.2 : Patch 22605799:R12.PAY.C

Post Install Steps need to be run after patch installation.

See the following notes for further details:

  Netherlands : Legislative Updates for 2016 (Doc ID 2081080.1)
  Netherlands Payroll Mandatory Patches Release 12.1 (Doc ID 863866.1)
  Netherlands Payroll Mandatory Patches Release 12.2 (Doc ID 1626273.1)

If you encounter any issues with these patches, please raise a Service Request via My Oracle Support.

Thanks !

UK: P11D Legislative Changes

UK P11D Legislative changes have been delivered for 12.2 and are now available to download. 

12.2 – 21507339:R12.PAY.C - HRGlobal

This patch will provide the changes required for P11D processing for tax year 2015/16.

This is a cumulative patch and does include the Tax Year End patch.

Post Install Steps need to be run after patch installation. The patch Readme has important installation, setup instructions and guidelines.

Please refer to My Oracle Support Document 2072952.1(UK legislative Changes for end of tax year 2015/16, the start of tax year 2016/17 and the Real Time Information changes effective from April 2016  and P11D Changes for tax year 2015-16) can be found at:

The following My Oracle Support document has been updated:

1904656.1: UK Payroll Mandatory Patches (R12.2)

If you encounter any issues with these patches, please raise a Service Request via My Oracle Support.

Thursday Feb 11, 2016

A Brief Discussion on Oracle Property Manager Setup Checklist

As we have seen in the earlier post, Oracle Property Manager integrates with many sub ledgers. So when you first install and set up Oracle Property Manager for your business, you must configure several components with in Property Manager as well as in other subledgers. Here is a brief discussion on those required setups

  1. In other subledgers
  2. In Oracle Property Manager
A. In other subledgers: Oracle Property Manager integrates / uses many information which are defined in other sub ledgers. So before we start implementing Property Manager, few mandatory / optional setups need to be done in other subledgers. The below table gives a glimpse of few important setups



General Ledger

- Define Chart of Account

- Enter Accounting Calendar / period type

- Define legal Entities

- Define Ledger

- Define / enable Currency and exchange rates

- Set up profile GL: Ledger Name


- Define employees

- Define Organization

- Define Security Profiles


- Modify predefined setups in Oracle Subledger Accounting (if required)

- Set Up Subledger Accounting Options


- Enter Customer Details

- Define transaction types / sources

- Define Payment term


- Enter suppliers

- Define distribution sets


- Set up taxes

B. In Oracle Property Manager: When you first install and set up Oracle Property Manager for your business, you must configure several components, including flexfields, lookups, and system options. After these components are properly configured, you can use Oracle Property Manager without making any routine modifications.

The required setups in Property Manager can be mainly classified into

a. Profile options

b. System Options

c. Descriptive Flexfields and look ups

d. Location Hierarchy

e. Contacts

a. Profile options: A profile is a set of changeable options that affect the way your application looks and behaves. In Property Manager, we have many profile options which decides the way a functionality / application works. In Property Manager few profiles are set at system options level and few are set at system administrator level.

For more details on the different profile options available, values that can be set for each profile option, how application / functionality changes with each option, refer the document 1099133.1.

b. System options: System options to customize the Oracle Property Manager environment for each operating unit. System options determine your ledger and currency conversion type, accounting option etc. System options also control how Oracle Property Manager displays location aliases, sends information to Oracle Payables, and Oracle Receivables, and governs creation of leases and space assignments. It also has options to set the automatic number generation for lease, rent increase, variable rent etc.

c Descriptive Flexfields and look ups: Descriptive flexfields are normally used to capture the additional information that is important and unique to your business and these information’s are not captured in standard application. So while implementing Oracle Property Manager, one has to decide what addition information business wants to capture and based on that define the structure of descriptive flex fields and their respective value sets.

Oracle Property Manager module also provides an option to add and modify some of the look up values to better match your enterprise needs in the Oracle Property Manager Lookups window.

d. Location Hierarchy: In Oracle Property Manager, the term property refers to land or to built-up property. Whether your property consists of vacant land or buildings, you can define it at several levels. For built-up property, the default location hierarchy is building, floor, and office. For land, the location hierarchy is land, parcel, and section.

However, different industries use different terms for properties. So based on your business needs, You can customize property-naming conventions by changing the meaning and description fields for the PN_LOCATION_TYPE lookup. After you change the values in the lookup, the new property terms replace the old terms throughout Oracle Property Manager.

e. Contacts: Contact feature is normally used to record the contact details of companies or other business entities /parties to the lease like land lords, insurance companies, security, maintenance etc. You can record contact information for each contact, including the name and address of the business, telephone number, and e-mail address of people in the contact company.

For additional / detailed information on each of these setup considerations refer Oracle Property Manager Implementation guide.

Wednesday Feb 10, 2016

HRMS MX: End of Year 2015 Phase I One Off Patch Released

Oracle HRMS (MX) customers should download and apply the latest one off patch delivered by Oracle on February 9th 2016

R12.1 – 
22690160:R12.PAY.B - Format 27 W1 and DIM Report
R12.1 – 22690160:R12.PAY.C - Format 27 W1 and DIM Report

This patch provides the changes required for addressing the Format 27 W1 and DIM Report Field 118.  

Please review the associated readme for the patches above for more detailed information.

Tuesday Feb 09, 2016

New ORAchk Version Released

The new ORAchk release is now available to download.

New Features in ORAchk

Faster Execution

Significant performance improvements have been implemented in ORAchk's discovery, execution, and report generation.

Testing shows this release of ORAchk runs up to 45% faster than the previous release.

Quickly see the issues that require attention

The report format has been enhanced:

  • All related checks are listed in the same section. For example, all Database Server checks (passed or failed) are now shown together under the Database Server section.
  • There are new check boxes at the top of the report to allow you to focus on what you need to fix.
  • Check status is color coded for quick visual reference.
  • Each check now expands in place when you click on the "View" link allowing you to easily see the recommendations and details in-line without the need to jump around to different areas of the report.
  • E-Business Suite checks are now grouped by the module they apply to and the E-Business Suite version number is shown in the report summary as well as at the top of the E-Business Suite section.

Improved Security

Security of ORAchk files and directories has been enhanced and Collection Manager Database connections are now stored in an encrypted wallet.

Health Check Catalog

ORAchk now has a searchable Health Check Catalog, which lets you quickly view and filter available checks by Product, Level, Release Authored, and Platform.

The Health Check Catalog is available via the "Health Check Catalog" tab of Document 1268927.2 and also bundled within the ORAchk distribution.

Health Verification for Oracle Solaris Clusters

Initial support has been implemented in this release for some Oracle Solaris Cluster Checks, which verify best practice for configuration and runtime Oracle Solaris Cluster details.

Save time configuring and accessing ORAchk reports

  • Orachk allows you to verify Collection Manager database configuration before ORAchk automated execution, ensuring results can be stored correctly the first time.
  • You can receive an email html report when running ORAchk in adhoc mode, meaning you no longer need the extra step of transferring the report to your local machine for viewing.
  • Verify email configuration by using ORAchk to send a test email ensuring the ORAchk report will be received correctly the first time.
  • Quickly subscribe or unsubscribe to email notifications of automated collection results, comparisons and ORAchk Collection Manager tablespace free space warnings.

Support to integrate with Kibana, Elastic Search & Others

ORAchk output is now also available in JSON format, allowing it to be consumed by many different log monitoring and analytics tools.

For more details and to download the latest release of ORAchk see Document 1268927.2

Friday Feb 05, 2016

Mobile Apps and MSCA – A Tale Of Two Products

Have you heard the terms Mobile Applications (Apps) and Mobile Supply Chain Applications (MSCA)? Confused? Let's try to add some clarity.

Technology brings us great benefits, but for some people benefits are not obvious until they are explained or demonstrated. To do this well often requires specialized, discipline-specific vocabulary (the word “ray” means something different to an astronomer [think gamma ray, ray of sunlight] than it does to a marine biologist [manta ray? sting ray?])

The “Oracle discipline” is no exception - In Inventory we work with two different Products with the term "Mobile" in their names; Mobile Apps and Mobile Supply Chain Apps. People have been known to casually refer to either one as “the Mobile”, which obviously can cause some confusion. We recommend an excellent document to clear up the confusion: What Is The Difference Bewteen Mobile Applications and Mobile Supply Chain Applications (MSCA)? (Doc ID 2103922.1)

Mobile Apps

Mobile Apps


Whether you're a Mobile Apps User, a MSCA User, or both, it's important to know the distinction between the Product names. Hopefully Doc ID 2103922.1 helps clear things up, and happy mobiling!

Thursday Jan 28, 2016

The Oracle Mexico Payroll End of Year 2015 Phase 1 patches have been released and are now available on My Oracle Support!

The Oracle Mexico Payroll End of Year 2015 Phase 1 patches have been released
and are now available on My Oracle Support!


- Social Security Quota calculation has been made configurable based on IDW value.

- SUA Interface Extract has been modified to comply with SUA version 3.4.4 requirements.

- BBVA-Bancomer Direct Deposit Interface has been updated to support 108 character layout.

- ‘Overtime and Holidays Worked’ secondary classification has been split into two separate classifications.

- Information Declaration Report (DIM) has been modified to comply with DIM version 3.3.10 requirements.

- New minimum wage rate effective January 1st, 2016.

- The state tax components have been updated for: Chihuahua, Hidalgo, Puebla, Queretaro, San Luis Potosi and Veracruz states.

Patch numbers:

Please see the patch readme’s on My Oracle Support for full patch install instructions and functional information:

Please log a Service request with the Oracle HRMS Mexico product for further assistance with these patches.

Tuesday Jan 26, 2016

Reconciling Receivables to General Ledger

What is AR to GL Reconciliation Report?

  • Compares the Account Balances process from Receivables to General Ledger
  • Highlights Journal Sources where Discrepancies Exist
  • Report will show differences between Account Balances only if item did not successfully process to General Ledger
  • Pulls information from the XLA tables to General Ledger during the Import Process of Create Accounting or Submit Accounting from Receivables
[Read More]

Thursday Jan 21, 2016

Add An Idea And Get Your ER's Moving

Back in our November 2014 post, we posted our first Blog on the the Enhancement Request (ER) process move to Community Ideas. We thought it might be time to revisit this important subject.

As a refresher, the Idea process has replaced the old ER Process. In the new Idea process, you no longer need to create a Service Request (SR) with the corresponding Product group for an ER, you create your own Idea directly in the Product community. Then you and anyone in the Community can vote on and/or discuss your Idea.

Benefits of the new process? You have the ability to create, manage, and vote on your own Idea. You can discuss and expand on your Idea in threads with other Community Users (which includes Oracle Development and EBS Product Management). You can see the progress that your Idea is making through votes and discussion threads. You can view, vote on, and discuss all other existing Idea's. You can filter Ideas by many different options, including 'Delivered' Ideas. And best of all, you can easily monitor where your Idea stands.

How does it work? To get to existing Ideas, go to the Logistics or Inventory Items (APC/PLM/PIM) Communities, navigate: Content > Ideas (tab). To create an Idea, click on: Create an idea.

You can create an Idea with any information that suits you. We suggest that you be as detailed as possible and provide your product release, screenshots or video's (if applicable), define your business process (including industry benefits), feature gaps, and the overall benefits of the Idea. Remember, this is your opportunity to provide information on why you would like your Idea implemented and how it would benefit others. Your stumping for votes.

The new Idea ability in Communities is the quickest way to get your ideas directly in front of Oracle Development. Top voted ideas float to the top and certainly draw more attention. As always, Oracle puts you, the Customer, in the forefront. Moving ER's to Communities Ideas now gives you the power over your ER's. Please help us in tracking features that are important to you. Also, for more information on ER's to Communities, see note Oracle E-Business Suite Product Enhancement Request to My Oracle Support Community FAQ (Doc ID 1584210.1).

January 2016 Updates to AD and TXK for EBS 12.2

Announcement: January 2016 Updates to AD and TXK for EBS 12.2 -

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



« April 2016