Thursday Jan 07, 2016

Too Many Decimals? Round And Round

Occasionally, Inventory Support runs into confusion over how the E-Business Suite (EBS) handles decimal places for transaction quantities. An example is that the Work In Process (WIP) Product allows 6 decimals places versus the Inventory Product, which allows 5 decimal places. This is a known limitation that the applications handle by rounding quantities.

In a normal Inventory transaction, the rounding is taken care of immediately, so rounding does not usually cause confusion. If for example, you entered a quantity .000006 in a Miscellaneous Receipt, then the system will round the quantity to .00001. The system rounds using the "ROUND" function to 5 decimals. As a result, 1 through 4 will round down and 5 thru 9 will round up. If for example we try to receive .000004, this would round down to 0 which is not a valid transaction quantity and would raise an error.

Here is an example in Inventory where the application rounds down. The user had entered the Quantity of .000004 (six decimal places) and received the following message:

Here is an example where the system rounds down to 0 and raises an error:

In WIP, the examples can be more complicated. The WIP forms often will help the user avoid issues. For example, you would not be able to issue .000004 because it would round to 0 in inventory. The WIP Completion and Issue forms should stop the user from entering this quantity. The user though could enter .000005 and greater as this rounds up to .00001, not zero. If we build a job for .000006. We assemble the job and look at the Inventory transactions. In Inventory, we see the assembly quantity .000006 rounded to .00001.

Would you like to see this changed? You have the power by voting in the long standing Idea (Enhancement Request) where you can discuss and vote on an enhancement:

Rounding is something you may want to be aware of in EBS. You can find more information in documents:
Inventory and Work in Process Round Decimal Quantities Differently (Doc ID 793356.1)
What is the Restriction of Decimal Precision for Receiving Forms in 11.5.10 and R12? (Doc ID 736699.1)

Wednesday Jan 06, 2016

Integration of Oracle Property Manager with Other Applications

Oracle Property Manager provides an integrated solution with other Oracle Applications. It integrates with other applications such as General Ledger, Oracle Payables, Oracle Receivables etc. Here is a glimpse of other sub ledgers which are integrated with Oracle Property Manager.

1. Oracle General Ledger:- Property Manager  retrieves few setup related information like  chart of account, accounting period types, accounting calendar, ledger, subledger accounting options etc  from General Ledger. Also the normalized accounting entries are transferred from Property Manager to general ledger via Oracle Subledger Accounting module.

2. Oracle Subledger Accounting:- Oracle Property Manager predefines certain setups in Oracle Subledger Accounting like accounting events and event types, sources, account derivation rules etc and these setups will be used when the create accounting program is run in Property Manager.

In addition to that you can transfer normalization-related accounting information from Oracle Property Manager to Oracle Subledger Accounting. Oracle Subledger Accounting creates the appropriate journal entries and transfers them to Oracle General Ledger.

3. Oracle Human Resources (HRMS):- The employee information which we use in Oracle Property Manager while managing office space and allocating locations to employees, are retrieved from HRMS.

Also in HRMS module we can define a hierarchy of organizations to represent the structure of the company. Once you have created the required organizations, you can classify one or more as operating units. In Oracle Property Manager, operating units are used to partition data. Users create all leases, agreements, contacts, locations, and space assignments for a specific operating unit.

4. Oracle Payables :- The owner of the property your organization intends to lease (the landlord) must be set up as a supplier in Oracle Payables and this supplier information will be used while creating a expense lease in Property Manager. Also Property manager uses the other information’s like payment term, distribution set etc which are setup in payables.

Once the leases are created and payments are approved, their invoice information is send to Accounts Payables for invoice creation and for payment processing.

5. Oracle Receivables :- In Property Manager, while creating a revenue lease few information which we use like customers, transaction source, transaction types, grouping rules, payment terms etc are retrieved from Oracle Receivables module.

Also once the Revenue leases are created and finalized, billing lines are approved and transferred to Receivables for invoice creation and further the accounting of invoices is sent to General ledger.

In addition to above, Oracle Property Manager module also integrates with Oracle E-Business Tax, Oracle Projects and Oracle Enterprise Asset Management.

The tax rates which we define in Oracle E-Business Tax appear in the tax input classification or tax output classification LOVs on the term details window. Users can thus associate the appropriate tax rates with lease terms.

You can assign projects which are defined in Oracle Projects module to a location in Oracle Property Manager. By linking locations to projects, your organization can track where project team members are located and the exact costs of space assignment.

The integration between Oracle Property Manager and Oracle Enterprise Asset Management (eAM) enables eAM assets to correspond with locations defined in Oracle Property Manager. Using the Export Locations to Enterprise Asset Management concurrent program we can export location data to Oracle Enterprise Asset Management.

Oracle Property Manager also uses an open interface to integrate with CAD and CAFM applications. This integration enables you to manipulate and view information about your space definition and usage in either a forms-based or CAFM environment, synchronizing data across applications as required.

For more details on integration of Property manager with Other subledgers, refer the Property Manager implementation guide.

WEBCAST: UK Legislative Updates 2015/2016 Seminar

Webcast_icon.jpgUK Legislative Updates for 2015/2016 

Wednesday, January 20, 2016  10:30 am GMT Time (London, GMT) and  2:30 am PST (San Francisco, GMT-08:00)

This one-hour session will highlight the technical and legislative changes affecting the forthcoming tax year end (2015/16) and payroll processing for 2015/16.  It will detail new legislation effective from 6th April 2016, including changes to PAYE & NI.

This session will also set out the RTI processes for completing the 2015/16 tax year and moving into 2016/17.

A short question and answer period will be included.

Details & Registration can be located at:   Event Information: UK Legislative Updates 2015/2016 Seminar

Tuesday Jan 05, 2016

UK Legislation: Release of UK Year End/SOY and RTI Early Adopter Program

As in previous years, Oracle HRMS Development will be running an Early Adopter program for the UK Year End and RTI Legislative Update patch.

    • Note: Only customers participating in the Early Adopter Program should apply this to their system.
The HRGlobal patch has been released to provide the software updates for processing UK Tax Year End 2015/16,  new legislation,  along with Real Time Information (RTI) changes which are all required starting from 6 April 2016.

The Early Adopter Program begins on 11th January 2016 as scheduled, and is planned to run until 25th January.

During this time, the Early Adopters will apply the patch and test the changes provided in it.

This allows the patch to be further tested in a customer environment, but under controlled conditions.

How Reapproval Rules can cause Purchasing Documents to require Reapproval?

Are your Reapproval rules causing documents to require Reapproval? What are reapproval rules?

To understand reapproval rules it is important to make a distinction between new documents and already approved documents, which are modified after approval:

  •  If a new document is created the purchase order, release or requisition will always go through the approval process.
  •  However, adding or changing specific information for an already approved document, may cause the document to unapprove, regardless of whether the revision is incremented. Almost all changes that cause the revision to be incremented also unapprove the document, as does placing the document on hold, reserving it or canceling it.

The reapproval rules help you control whether-or how much of-a revision (for example, to Quantity) requires the document to undergo the entire approval process or to be instantly approved. So in other words the reapproval rules determine if a modified purchasing document requires reapproval or not.

For a complete overview of the Requires Reapproval Rules and the Change Order workflow within Purchasing and understanding which changes can cause a document to require reapproval , you can review How Reapproval Rules Can Cause Purchasing Documents To Require Reapproval? Doc ID 1114515.1

Case Study of Using Oracle Database In-Memory with OM

A new white paper has been published to review the results from various test cases performed on certain Order management use cases after enabling In-Memory column store feature of Oracle database 12C. Three performance intensive use cases have been selected for this case study and numerous tests have been performed by changing the data that is loaded into In-Memory column store, keeping all other database parameters constant. This paper publishes the results of those tests and also provides recommendations about what data needs to be loaded into In-Memory.

The white paper is entitled "A Case Study of Using Oracle Database In-Memory with Oracle EBS Order Management" can be view from Oracle Order Management Suite White Papers (Doc ID 113492.1).

Tuesday Dec 29, 2015

GL Posting Performance After Database Upgrade to or Patch Available!

Posting journal entries in General Ledger is the last step of the accounting cycle, transferring these entries in a final state to update GL balances and locking them for further updates. This is the main GL process that will afterwards support Reporting on the balances, Translation, Consolidation and other business specific processes. As Posting is very common activity in GL, it is very important that the concurrent requests run with reasonable performance.

Posting bad performance was reported after Database Upgrade to or A higher parse time than 11g may be seen in 12c for a complex query with a multi-table join with SQL plan directives enabled.

Database Patch 20807398 is now available to fix this for you!

Did you upgrade the Database to the mentioned versions recently?

Proactively review this document today, before the users get to report performance issues:

GLPPOS: After Database Upgrade to or Posting Has Poor Performance Due to SQL Plan Directives (Doc ID 2068068.1)

Monday Dec 28, 2015

Oracle Mexico Payroll Year Begin 2016 Update

The Oracle Mexico Payroll Year Begin 2016 patches have been released and are now available!

It is highly recommended that you review the following concerning these patches:

  1.  These patches are different from all other statutory updates (there are additional post installation steps), so please be sure to carefully read the entire patch readme delivered with the patch before beginning to install these patches to ensure successful processing.
  2. Additionally, please take a moment to also review the MyOracleSupport Document(s)

These notes will provide the following information for the specific application version
        • Year End New and Changed Features
        • Year End New and Changed Components
        • Software Updates in this Patch
        • Change Record

Affordable Care Act (ACA) Reporting Phase 2 Patch for 12.1.x has been released

Affordable Care Act (ACA) Reporting Phase 2 Patch Update

  • 12.2 - Targeted for release by the end of December 2015.
  • 11i   - Targeted for release in early January 2016.

"ACA Phase 2" delivers the ability to archive, generate and print the actual Forms 1095-C for employee recipients.

The ACA Reporting Phase 2 Patch 22141344:R12.BEN.B, is currently available for download from My Oracle Support for Release 12.1 customers using Standard or Advanced Benefits.

  • Release 12.1 customers must be on Release 12.1 HRMS RUP6 or later in order to apply this patch.
  • Before applying the ACA Reporting Phase 2 patch, the 2015 ACA Reporting Phase 1 Patch 21162146:R12.BEN.B must also be applied.

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

For complete details on what has been delivered, please consult the functional readme in My Oracle Support:

  • Document 2089776.1 - 2015 Employer Shared Responsibility Reporting Under the Affordable Care Act - Phase 2 Functional Readme for Release 12.1 Customers on HRMS RUP6 or Later.

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).

Saturday Dec 26, 2015

General Ledger Calendar Definition for the New Year: Keep in Mind 2016 is a Leap Year!

General Ledger's Calendar is used to define 'years' from accounting perspective, allowing business users to decide on the periods and period types they would include. These may be identical or different from calendar-year perspective, meaning that they could include more than 12 periods (adjustment or non-adjustment periods), may follow a fiscal-year definition that is specific to a certain country or fiscal system, or simply match various business requirements.

On setting up GL Calendar for the next year, please keep in mind 2016 is a Leap Year! Do not miss February,29 from your calendar!

Accounting Calendar - February 2016

How to check the existing definition?

  • Simply verify the setup in General Ledger form - query for the calendar and relevant period
  • Under Gl responsibility, run Calendar Validation Report, check the output for any violations reported
  • Use SQL scripts to look into the tables directly

The following document may help: General Ledger Calendar Setup, Usage and Troubleshooting (Doc ID 130539.1)

Did you find a gap in your calendar?

If you already defined the calendar and just spotted a gap - most common mistake at this time of the year is to miss out February29 from the definition - Act Now!

Do Not use Sql to update the tables yourself as this may generate massive corruption. Let Oracle Support help!

Raise a Service Request sooner rather than later. Calendar missing dates is something we may be able to fix; as times passes, it adds complexity to the solution to be provided making it impossible to be applied for some cases, mostly due to having Subledgers tables affected too.

Check your GL Calendar now!

Thursday Dec 17, 2015

Announcement ! HCM Technical Analyzer has been RENAMED HR Technical Analyzer

Announcement !!

HCM Technical Analyzer  has been renamed  HR Technical Analyzer.

Based on valuable customer feedback, the Oracle EBS HCM team has reworked the HCM Technical Analyzer and this has been re-released as the 'HR Technical Analyzer'.

Payroll, OTL and Benefits information were removed from the HCM Technical Analyzer, as these are available in specific analyzers:

Check out this sample output.

The HR Technical Analyzer is a self-service health-check script that reviews HR related data, analyzes current configurations and settings for the environment and provides feedback and recommendations on best practices.  Analyzers may also be used as data collection tools by Oracle's support engineers.  Your application data is not altered in any way when you run this analyzer.

Information are structured in sections, but you can use “Show All Sections” and “Expand All Checks” in order to see all information.

Please, ensure that you download the latest version and you setup the new analyzer as concurrent request:

  1. Copy file HRTechnicalAZ.ldt on your server and use the applications FNDLOAD command below to import the concurrent program definition into your instance. 
    Run this command from the directory where you have downloaded the ldt file on your server, and note that the APPS password is needed:       


  2. This creates the concurrent program "HR Technical Analyzer" in the Human Resources application.

  3. Assign this concurrent program to all responsibilities that are used and run it as concurrent request.

Analyzers are designed by Oracle Support to proactively assist you to better diagnose and maintain your Oracle Application environments.  We welcome and encourage you to share your feedback via the HR Analyzer feedback link in the My Oracle Support Community : Human Capital Management - EBS (MOSC) .

Your feedback shapes the content of existing Analyzers and drives creation of new Analyzers.

Wednesday Dec 16, 2015

Patches Released! US Q4 2015, US and Canadian 2015 Year End Phase II and 2016 Year Begin

The following US and Canadian Year End Statutory Update patches have been released! 

  • US Q4 2015
  • US and Canadian End of Year 2015 Phase 2
  • US and Canadian Year Begin 2016
  • Canadian Year Begin 2016 for HR ONLY     

US Highlights:
  • 1099-R Federal and State (including Combined Filer) Updates
  • 1099-R Corrections Process for Submitting to the IRS
  • Support for Employer-level Changes in Federal W-2C Magnetic Media reporting
  • 2016 updates for North Carolina and Puerto Rico EFW2 (State W-2 Magnetic Media)
  • RITA/CCA updates for 2015
  • SQWL/SPWL changes for Louisiana, Nevada, and Puerto Rico
  • Q4 2015 JIT updates
  • 2016 IRS Standard Deduction Amounts
  • 2016 SUI/SDI/TDI rates and wage base updates
  • 2016 State Minimum Wage Increases for California, Colorado, Connecticut, Massachusetts, and New York - impacts garnishment processing
  • 2016 Boone County, KY changes

Canada Highlights:

  • 2015 PDF templates for T4, T4A, RL-1 and RL-2 slips
  • T4A Magnetic Media updates
  • RL-1 and RL-2 Electronic Interface updates
  • Authorization and certification numbers for RL1 and RL2 PDF and Electronic Interface
  • 2016 Federal and Provincial Basic Amounts
  • 2016 Statutory Holidays

Year End 2015 Phase 2:

 Release  Patch  Document
 11i Patch 22371110 - US & CANADA END OF YEAR 2015 STATUTORY UPDATE II FOR 11I

Document 2087285.1 - Release 11i - US Payroll Readme for End of Year 2015 Phase 2 and Q4 2015 Statutory Updates

Document 2088045.1 - Release 11i - 2015 Canadian Payroll Year End Phase 2 Readme

 12.1.x Patch 22371111:R12.PAY.B - US & CANADA END OF YEAR 2015 STATUTORY UPDATE II FOR R12.1

Document 2087286.1 - Release 12.1 - US Payroll Readme for End of Year 2015 Phase 2, Q4 2015 and Year Begin 2016 Statutory Updates

Document 2088046.1 - Release 12.1.x - 2015 Canadian Payroll Year End Phase 2 and Year Begin 2016 Readme
 12.2.x Patch 22371111:R12.PAY.C - US & CANADA END OF YEAR 2015 STATUTORY UPDATE II FOR R12.2

Document 2087287.1 - Release 12.2 - US Payroll Readme for End of Year 2015 Phase 2, Q4 2015 and Year Begin 2016 Statutory Updates

Document 2088047.1 - Release 12.2.x - 2015 Canadian Payroll Year End Phase 2 and Year Begin 2016 Readme

* Note: The End of Year 2015 Phase 2 includes the End of Year 2015 Phase 1, US Q4 2015 as well as the Year Begin 2016 statutory updates

Year Begin 2016 for US and Canadian Payroll Customers:

 Release  Patch  Document
 11i Patch 22371100 - US & CANADA YEAR BEGIN 2016 STATUTORY UPDATE FOR 11I Document 2088231.1 - Release 11i - 2016 US Payroll Year Begin Readme
Document 2088876.1 - Release 11i - 2016 Canadian Payroll Year Begin Readme
 12.1.x Patch 22371101:R12.PAY.B - US & CANADA YEAR BEGIN 2016 STATUTORY UPDATE FOR R12.1

Document 2087286.1 - Release 12.1 - US Payroll Readme for End of Year 2015 Phase 2, Q4 2015 and Year Begin 2016 Statutory Updates

Document 2088046.1 - Release 12.1.x - 2015 Canadian Payroll Year End Phase 2 and Year Begin 2016 Readme   
 12.2.x Patch 22371101:R12.PAY.C - US & CANADA YEAR BEGIN 2016 STATUTORY UPDATE FOR R12.2

Document 2087287.1 - Release 12.2 - US Payroll Readme for End of Year 2015 Phase 2, Q4 2015 and Year Begin 2016 Statutory Updates

Document 2088047.1 - Release 12.2.x - 2015 Canadian Payroll Year End Phase 2 and Year Begin 2016 Readme

Canada Year Begin 2016 for HR Only:

 Release  Patch  Document
 11i Patch 22371102 - CANADA YEAR BEGIN 2016 STATUTORY UPDATE FOR HR ONLY PATCH FOR 11I Document 2088038.1 - Release 11i  - 2016 Canadian Year Begin for HR Only Customers Readme
 12.1.x Patch 22371103:R12.PER.B - CANADA YEAR BEGIN 2016 STATUTORY UPDATE FOR HR ONLY PATCH FOR 12.1 Document 2088062.1 - Release 12.1 - 2016 Canadian Year Begin for HR Only Customers Readme
 12.2.x Patch 22371103:R12.PER.C - CANADA YEAR BEGIN 2016 STATUTORY UPDATE FOR HR ONLY PATCH FOR 12.2 Document 2088064.1 - Release 12.2 - 2016 Canadian Year Begin for HR Only Customers Readme

If you encounter any issues with these patches or have any questions regarding them, please raise a Service Request via MyOracleSupport.

Attention Oracle Exchange and Oracle Supplier Network Customers!

Last weekend, Oracle performed a hardware upgrade to the Oracle Supplier Network. Oracle Development and Oracle Support would like to alert you to some information that could impact you.  If you have any questions regarding this information, please update the My Oracle Support Community thread Changes for Oracle Exchange and Oracle Supplier Network Customers, and someone from Support will respond back to you.

For more information, you can review the following documents available related to these changes:
• Exchange Migration - Changes Planned For The Oracle Exchange Platform (Doc ID 2083643.1)
• New UI (User Interface) In OSN Including Punchout Feature After Hardware Upgrade (Doc ID 2083662.1)

Please take the time to review the information.  It is important that you be aware of these changes and how they may impact you. We will be actively updating content with any and all new information in an effort to make any transitions or changes easier for you and your suppliers.

Friday Dec 04, 2015

New ROE Web Processing ! Delivered in the Record of Employment Interface Process

The Oracle HRMS (Canada) product delivers new functionality for Record of Employment (ROE) Web processing.

Service Canada has indicated that they are decommissioning these older ROE Web formats on March 31st, 2016.

  •     27 Week Flat file
  •     53 Week Flat file
  •     53 Week XML file version 1.0
  •     27 Week Online Form (Supporting Validation for 27 week Payroll Extract)

Leaving only the following as mechanism for submission of ROEs to them:

  •     53 Week XML Payroll Extract File XML version 2.0
  •     53 Week Online Form

To accommodate this decommissioning the Oracle HRMS (Canada) development team has released Record of Employment Interface process, in addition to the existing Record of Employment Magnetic Media process. .

This new process equates to the "53 Week XML Payroll Extract File XML version 2.0" mentioned on the Service Canada website and will become a mandatory format for submitting ROEs from April 1st, 2016 onward.

The process Record of Employment Interface has been delivered in these patches for EBS Application versions 12.1.x and 12.2.x:

For those who are already starting to test and are looking to convert earlier we have created the following notes to help you further:

  • Best practice for Converting to and Use of the Record of Employment Interface Process (Document 2080661.1)
  • Which file to Send and How to Format the Record of Employment (ROE Web flat and XML) Submission Files To Upload To Service Canada (Document 1612973.1)
  • Record of Employment Processing (ROE) (Document 248386.1)

If you have any questions or issues with regards to this new functionality, please post on this community EBS:Payroll under the CA legislation category or  log a new Service Request with Oracle HRMS (Canada) product support.

Thursday Dec 03, 2015

Time To Resolution Reduced!

In EBS Inventory Support, we offer many avenues to help you get quick solutions. One important avenue is the My Oracle Support (MOS) Knowledge Management database to help you search and quickly solve issues. Another avenue is to log a Service Request (SR). In order to help to reduce your SR time to resolution (TTR), we are proud to announce the release of new Problem Types for the Inventory Product.

Problem Types allow you to categorize your SR issue in order to direct it to the correct Support Team and Subject Matter Expert. We have expanded the Inventory Problem Types in areas like Inventory Transactions, in order to give you an ability to log a more detailed SR for an area like 'Transactions Setup'.

Along with the new Problem Types, we have also automated Inventory SR's in order to request important diagnostic information up front, in order to speed up the TTR. This will help you get your solutions faster.

Oracle Inventory Support offers many different paths to solutions for your issues. Don't forget all the quick easy solutions in the Logistics and Inventory Items (APC/PLM/PIM) Communities, or the searchable Knowledge Management documents in the MOS Knowledge base. And if you need to log a SR, the new Inventory Problem Types will help to better define your issue and reduce your SR TTR.

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



« February 2016