Tuesday Apr 19, 2016

What Are the Available BSO Web Service Methods Available for Purchasing in 12.2.5?

What Are the Available BSO Web Service Methods Available for Purchasing in 12.2.5?

Review (Doc ID 2120274.1)

The following is a list taken from the Integrated Repository showing the available BSO web service objects available in 12.2.5 (or 12.2.4 where patch 19684688 has been applied).

Service Description
createPurchaseOrder This Service Method Creates a Purchase Order with the data provided in the input object PurchaseOrder.

For Create PO, DocumentSubType, StyleId and OrgId are mandatory attributes.


This Service Method takes the Order Number and Organization Name as the input and retrieves the complete Purchase Order details.


This Service Method Updates an existing Purchase Order document as per the data provided in the input object PurchaseOrder.

- For Update PO, DocumentNumber and OrgId, or PoHeaderId are mandatory, to identify the PO to be updated.

- When updating Lines, either provide PoLineId or LineNum to set the context. The same applies to other entities as well.

- To add new Line, either leave LineNum as null, or provide a new LineNum. The same applies to other entities as well.

- For Schedules, Pay Items and Price Breaks, use entity PoLineLocations.

- For BPA Item Attributes, use entities PoAttrVals and PoAttrValuesTLP.

- For Complex PO Pay Item, PaymentType value is mandatory for both create and update scenarios. Possible values are ADVANCE, DELIVERY, LUMPSUM, MILESTONE, RATE.

- Provide only values of attributes to be updated, along with context attributes (discussed above). If an attribute value is provided, and it is not updatable because of the entity status or some other setup, an error message will be returned back and transaction will fail. This applies even when the new value provided is same as current value in PO.

- To nullify the value of a String type of attribute, pass the literal value "WEBSERVICE_NULL_CONSTANT_STRING" or java constant PoConstants.WEBSERVICE_NULL_CONSTANT_STRING

- To nullify the value of a Number type of attribute, pass the literal value -99999999 or PoConstants.WEBSERVICE_NULL_CONSTANT_NUMBER in java.

- To nullify the value of a Date type of attribute, pass the literal value or PoConstants.WEBSERVICE_NULL_CONSTANT_DATE in java

performDocControlAction This Service Method takes the ControlActionInput object as the input and performs the control action on the purchasing document as per the input provided.

Control Actions that are supported by this method are:

- CANCEL (Supports at Header/Line/Shipment level): Cancels the Purchasing document at the specified level

- CLOSE (Supports at Header/Line/Shipment level): Closes the Purchasing document at the specified level

- OPEN (Supports at Header/Line/Shipment level): Opens the Purchasing document at the specified level in case if it is already closed

- INVOICE CLOSE (Supports at Header/Line/Shipment level): Closes the invoice of the Purchasing document at the specified level

- INVOICE OPEN (Supports at Header/Line/Shipment level): Opens the invoice of the Purchasing document at the specified level in case if it is closed

- RECEIVE CLOSE (Supports at Header/Line/Shipment level): Closes the receiving transaction for the Purchasing document at the specified level

- RECEIVE OPEN (Supports at Header/Line/Shipment level): Opens the receiving transaction for the Purchasing document at the specified level in case if it is already closed

- FINALLY CLOSE (Supports at Header/Line/Shipment level): Performs Finally Close operation on the purchasing document at the specified doc level

- FREEZE (Supports at Header level): Performs Freeze operation on the Purchasing document

- HOLD (Supports at Header level): Holds the Purchasing document

- RELEASE HOLD (Supports at Header level): Releases the Hold on the Purchasing document if it is already on Hold

- DELETE (Supports at Header level): Deletes the Purchase order


This Service Method Creates a Purchase Order Modification document with the data provided in the input object PurchaseOrder.

CLM based document.


This Service Method takes the Modification Number and Organization Name as the input and retrieves the complete Purchase Order Modification details.

CLM based document.


This Service Method Updates an existing Purchase Order Modification as per the data provided in the input object PurchaseOrder.

CLM based document.

Thursday Apr 07, 2016

Attending Collaborate 16? Learn More about Analyzers and Social Media

Attending Collaborate 16 in Las Vegas April 10-14? Check out these sessions:

Want options other than logging a Service Request to solve issues? Attend 'Proactive Best Practices: Social Channels get the Conversation Started to Faster Resolution' to get information on how to use social media for quick answers and details on sharing information for quick solutions.

Interested in learning more about Analyzers and what Analyzers are available for EBS Supply Chain Products? Sit in on 'Proactive Best Practices: Case Studies using Supply Chain Management Analyzers'.

Collaborate 16 offers hundreds of presentations and panels packed with the latest information and practical tips for not only the Oracle E-Business Suite, but also Cloud/Fusion Applications, Hyperion, Primavera EPPM, EBS Extensions for Endeca, CRM On Demand, Siebel CRM, BI and EPM, Upgrades, Support, CRM, Financials, HCM, Application Strategy and more! Hope to see you in one of our sessions!

By the way, be sure to follow our live Tweeting during Collaborate 16 at twitter.com/Oracle_EBS.

Tuesday Apr 05, 2016

Depreciation Override in Fixed Assets

Depreciation override can override the system-calculated depreciation amount when the calculated amount does not meet business requirements.  Override is a way to have a different periodic depreciation charged than what is calculated by the depreciation program.  Override amounts are still subject to all standard validations.

One prerequisite to using depreciation override is to set the profile option ‘FA: Enable Depreciation Override’ to Yes.

Depreciation override can be entered in two ways:  
  1. Via the depreciation override form.
  2. Via the FA_DEPRN_OVERRIDE table.
Depreciation override works in two different ways:
  • Used by Depreciation - used to override the system-calculated periodic depreciation amounts.
The steps to perform this override and to see its effects:
  1. Insert a record for the override with the book, asset number, current open period, override amount, used by depreciation, etc.  Set the status to POST.
  2. Run depreciation with or without closing the period.
  3. The status will be changed to POSTED from POST.  In the Asset Workbench form, the amounts entered for override will override the periodic system-calculated depreciation amount. 
OverrideFor example, the usual system-calculated monthly amount for Apr-16 is 500 for an asset.  An override of 800 is entered for Apr-16.  The monthly depreciation charged for Apr-16 is 800, visible when querying in the Asset Workbench.
  • Used by Adjustment - will be processed by performing an adjustment to incorporate the override data.  In this case, a transaction type of ADJUSTMENT will be created, much like a depreciation catch-up.  But, when depreciation is run for this period, the normal depreciation amount will also be calculated.
The steps to perform this override and to see its effects:
  1. Insert a record for override with the book, asset number, a closed period, override amount, and used by adjustment, with status set to POST.
  2. Perform an asset adjustment such as an increase in the cost of an asset. 
  3. After the cost adjustment, you see the line set to POSTED from POST.
  4. Run depreciation with or without closing the period.
For example, if the cost adjustment done in Apr-16 caused a system-calculated catch-up of 3000 and an override is entered with the period of Mar-16 for 2000, the system-calculated monthly depreciation amount for Apr-16, post cost adjustment, would be 500.  After the adjustment, the depreciation catch-up booked in Apr-16 would be 4500, i.e. 3000 system-calculated catch-up and 1500 entered via override, as 500 will be charged in periodic depreciation for Apr-16.  To get the desired adjustments to the catch-up amounts, periodic depreciation needs to be kept in mind.  If the additional catch-up needed is 2000 and the system-calculated catch-up is 500, the deprecation override entered should be 2500.
There are some rules for override to be successfully processed:
  • Override amounts are not picked up if depreciation is already run for the book.  Perform a manual override using an API or perform a transaction like a penny cost adjustment.  Re-run depreciation to have it picked up in the depreciation run.
  • Override amounts are not picked up in the period of retirement.
  • Backdated retirements overlapping depreciation/bonus override are not allowed.
  • Depreciation override of zero is not allowed for an MRC/ALC enabled book.
  • Depreciation override amount has to be less than or equal to the NBV of the asset.
  • Depreciation override amount should not cause the reserve to exceed the depreciation limit.
  • There is no API for depreciation override.
  • Override depreciation is not picked up in the last period of an asset's life for life-based methods.
Points to keep in mind while working with override records:
  • If depreciation is run for the period and an override is missed, enter an override and rollback depreciation via API or by performing a penny cost adjustment.  Re-run depreciation to pick up override amounts.
  • Override has been processed and you see the status as POSTED, but it is incorrect and the period is not closed yet.  Go back to the override form and set the status POSTED back to POST and correct the amounts.  This automatically rolls back depreciation for the asset.  Depreciation can now be re-run to get the correct override amounts picked up.
  • Depreciation run has ended in error due to a validation failure after an override.  Delete the line and enter the correct amount.  Re-run depreciation to get the correct amounts picked up.

With credit to Anshu Malhotra, Oracle Assets Support

Thursday Mar 31, 2016

UK Teachers Pensions

Do you operate payroll for Teachers or report data to the UK Teachers Pension?

Are you intending to start reporting your Teachers data via the Monthly Data Collection (MDC) in 2016 / 2017?

Then this is for YOU!

If you plan to start reporting your Teachers data via the Monthly Data Collection (MDC), you will need to ensure that you have applied the  TYE16: TEACHERS PENSION MONTHLY DATA COLLECTION : EVENT TRACKING functionality which delivers the event triggers to start recording updates which can be captured and produced at a later stage. 

This patch will need to be applied to your production environment by the 1st April to track all of your 2016 / 2017 changes

Please refer to MOS Note:2116089.1 : UK TPA Monthly Data Collection Report Whitepaper

Oracle HRMS Development will be running a Pilot program for the Monthly Data Collection (MDC).


Will deliver the full functionality, including the event triggers.  Although, at this time only customers participating in the MDC Pilot should apply patch 21032735:R12.PQP.C to their test environment.

The logic behind the split of the patches is that we anticipated that customers would not be comfortable applying the full patch into production prior to completion of a full a testing programme.So once the pilot is complete, a mail will be sent out informing all customers of the patch they should apply to their systems.

If any customer wishes to review the content of the MDC patch or apply it to their system, they may download it and test the patch.

However, please load the patch in a test environment only, as we are unable to give priority to issues relating to this patch raised by anyone not participating in the official MDC pilot program.

Oracle AME Integrated With GL Journal Approvals. Business Considerations In Implementing This Enhancement

Oracle Approvals Management (AME) is an Application that provides the users with multiple options to define business rules applying to processes related to approving transactions in Oracle Applications where AME was integrated. 

Recently General Ledger Journals Approval process has been integrated with AME and Workflow, enabling enhanced methods for journals approval processes.

Find below a few relevant details that may help decide in bringing this enhancement to the business: 

  • Can Standard Journal Approval still be used? 

Yes, it is possible to use AME Journal Approval or the Standard GL processes; this is controlled by profile option setup: GL: Use Approval Management (AME).

  • How are organization changes affecting the approval process?
 AME recalculates the chain of approvers after each approval, therefore each transaction will be approved under the latest conditions being set up. 
  • Is the Preparer of the journal affected if AME Journal Approval is used?

The answer is Yes. If AME Journal Approval is enabled, this profile option will not be considered: Journals: Allow Preparer Approval; if the business requires to use this profile in order to control Preparer's access to approve the journal he creates, then use Standard Journal approval in GL as the only method that will take this profile into consideration.  However you may include the Preparer in the Approvers Group and get the same functionality working with AME  even without the profile setup. 

  • Is Approval Limits setup considered by AME?
Maintaining Approval Limits is not mandatory for AME but this setup step could be useful for subsequent AME definitions. 
  • What are the right business situations where AME Journal Approval should be used? 

There is no right or wrong here, this is entirely business decision depending on organizational structures and separations of duties. AME Journal Approval is more flexible, providing ways to be proactive by automatically detecting and routing the journals to approvers according to the separation of duties and not mandatory based on hierarchy; this is very relevant especially for those organizations where the hierarchy is very complex or the approval roles are granted based on skill sets and capabilities of individuals, rather than considering hierarchy only. 

This new feature enables enterprises to enhance their governance, control and compliance with pre-set business rules.  

See how it works here:

Oracle General Ledger Journal Approvals Integration with Oracle Approvals Management (AME) and Oracle Workflow (Doc ID 2038960.1)


US Legislation: Q1 Statutory Update Released

The United States (US) First Quarter (Q1) Statutory Update, 2016 has been released!

Patches released:

The Q1 2016 Statutory patch requires the End of Year 2015 Phase 3 patch as a prerequisite. Note also that it requires the post install steps of running the data installer and hrglobal.drv. Please be sure to carefully read all the readme's before beginning to install this patch, to ensure successful processing.

Q1 2016 Statutory Update Highlights

  • IRS revised 941 for Q1 2016, due April 30, 2016
  • Updated State Quarterly/Periodic Wage Listing (SQWL/SPWL) for Louisiana, New York, Nevada, Pennsylvania, and Utah
  • Q1 SPWL and JIT updates
  • Miscellaneous bug updates

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

**Note: The Release 11i Q1 2016 Statutory Update patch is only available to those customers who purchased continuing legislative support for the US HRMS localization. There is an FAQ available for all E-Business Suite customers which contains critical information as to when regulatory/statutory support ends on Release 11i (as well as 12.1 and 12.2) plus other details that can help US Payroll customers with planning upgrade activities. Please see Section C. Lifetime Support Policy: Coverage for Applications for further details.

UK Legislation: TYE16: Isle of Man (12.2)

The R12.2 Isle of Man Budget Changes for 2016 has been released via My Oracle Support

This patch delivers Isle of Man Budget changes for April 2016.

Please refer MOS Note ID: 2072952.1 for further details.

This is a cumulative patch, it includes the following patch:

  • 21507339:R12.PAY.C : TYE16: P11D LEGISLATIVE CHANGES FOR 2015-16

Patch Readme has important installation, setup instructions and guidelines.

If you encounter any issues with these patches, please raise a Service Request via My Oracle Support with Oracle Payroll Support in the normal way.

Wednesday Mar 30, 2016

Alternate Accounts - GL Feature That Helps Avoid Journal Import Errors

Subledger Create Accounting Program or GL Journal Import may sometimes fail due to having to transfer data into GL on an invalid account - one that was recently disabled or end-dated. 

To help avoid such errors, GL provides the feature of Alternate Accounts which gives the users an opportunity to setup a replacement code combination for an invalidated one, allowing the mentioned programs to continue until successful completion.

How to define this setup? 

Just navigate to GL > Setup > Accounts > Combinations - define your Alternate Account for the code combinations as needed:

General Ledger Alternate Accounts Sample

Where will the Alternate Account be used?

  • in  Subledger Create Accounting Program
  • in GL Journal Import process

Are there situations where Alternate Accounts can not be used?

  • they will not be considered by Subledger or GL forms where the accounts are entered by the users
  • will  not replace an account combination that has posting/budgeting disabled

I like this feature and want to know more!

Sure! Please review this useful document:

R12: How to Use Alternate Accounts in General Ledger? (Doc ID 2111940.1

Tuesday Mar 29, 2016

Webcast: 10 Tips to Improve Create Accounting Performance in Oracle E-Business Suite

Webcast_icon.jpg10 Tips to Improve Create Accounting Performance in Oracle E-Business Suite

Date: April 12, 2016 at 11 am ET, 8 am PT, 5 pm GMT, 8:30 pm India (Mumbai)

This one-hour Advisor Webcast is recommended for those working with Financial Accounting Hub and/or Create Accounting who would like to know more about the purpose and use of Create Accounting and how to resolve performance issues faced when running Create Accounting.

Topics will include:

  • Purpose & use of Create Accounting
  • Performance problems faced during Create Accounting
  • Top 10 Recommendations for better performance
  • Tips & tricks for crisis situations

Details & Registration via the My Oracle Support Community thread:  Advisor Webcast on 12-Apr-16: 10 Tips to Improve Create Accounting Performance in Oracle E-Business Suite

Friday Mar 25, 2016

Recent Changes for Report Manager Affecting GL FSGs Publishing to Excel

General Ledger's Financial Statement Generator provides the option to create a large variety of custom reports based on General Ledger balances. 

Integration of Financial Statement Generator (FSG) with Report Manager and WebAdi to help publish such reports in Excel directly makes this tool even more powerful. 

Recent changes in Report Manager security code have caused FSG  to no longer publish as Excel file, generating either a template instead of the report, or simply throwing error of insufficient privileges being granted to the responsibility.

Prevent this issue from happening!

Please review these documents for details and solution:

Blank Excel Trying to Generate FSG Statement In Report Manager After JAN 2016 CPU Patch 22133441 (Doc ID 2115436.1)

Users Are Getting Insufficient Privilege Error While Trying To Open FSG Report in Report Manager. What Is The Required Menu Function To Resolve This Error? (Doc ID 2098187.1

Act now!

Thursday Mar 24, 2016

UK Legislation - Oracle E-Business Suite UK Payroll Position Statement on Introduction of Pensions Tapered Annual Allowance

Oracle E-Business Suite UK Payroll Position Statement on

Introduction of Pensions Tapered Annual Allowance

UK Legislative payroll client's have been inquiring about Oracle EBS UK payroll's position on the introduction of Pensions Tapered Annual Allowance

For clarifications the Oracle EBS has published a position statement regarding these UK pensions tax relief measures via My Oracle Support

Knowledge Management document:

Oracle E-Business Suite UK Payroll Position Statement - Pensions Tapered Annual Allowance (Doc ID 2120267.1)

Please, if you have any questions regarding this statement, direct them to us through the logging of a My Oracle Support Service Request with the product Oracle HRMS (UK). 

Monday Mar 21, 2016

Released ! 2015/2016 Year end AU.23 Australia Cumulative Release Patch

Dear Australian Legislative Payroll customers

The AU.23 AUSTRALIA CUMULATIVE RELEASE has been released.  


Patch 22847922:R12.PER.B for release 12.1.x
Patch 22847922:R12.PER.C for release 12.2.x

This patch is the minimum requirement to complete 2015/2016 End of Year processing for the Australian Legislation.

Please review the Readme MOS Document 2115036.1 as this release includes many changes (some of which have already been released separately) including but not limited to:

  • New TFN 28 day functionality
  • Third Party Payment changes to simplify this process
  • Ability to email the Payment Summary
  • Changes to Payment Summary format (minor wording changes)
  • Defined Benefit support for SuperStream

For any issues experienced with this patch please log a MOS Service Request with Oracle Support under Oracle HRMS (Australia)

Friday Mar 18, 2016

Return Material To Vendors Using R12.2's New Functionality

In R12.2, now you can return material to vendors from any Organization (org). The new enhanced functionality allows users to do the following:
• Create a return order for returned lines.
• Return material to vendors from any Organization.
– For example, If an item is received in org M1 and is moved to org M2, it can be returned to the supplier from M2 itself. In the Returns form, the user can enter the receipt org as M1 and enter the original receipt number of org M1. User will be shown receipt details of org M1 and he can return the material from M2 itself.
• Users will be able to create returns without referencing a PO or receipt i.e. return against no document.
–E.g. user can return a damaged hard drive of a laptop to the vendor even though the original PO was created for the laptop. Users will need to enter the item, quantity, supplier and other details in receipt form.

Note: This functionality is available only from R12.2 above and will not be backported to prior versions.

The simple data flow model:

To learn more about this new functionality, you can review the functional Webcast recording found in the Logistics Community: Advisor Webcast Questions? "Release 12.2 Return to Vendor with Shipping Integration" on February 24th 2016.

You can also view the Webcast information from document:
Document for this webcast: Enhanced Return to Vendor Process in R12.2.2+ (Doc ID 2109517.1)

Happy return's, and don't forget to keep an eye on our Webcast series:

  • Oracle Inventory, Product Information Management and Warehouse Management Teams Informational Webcasts (Doc ID 1290983.1)

Thursday Mar 17, 2016

UK Legislation: TYE16: Isle of Man


The  TYE16:  Isle of Man IOM Budget changes for 2016-2017 has been released via My Oracle Support.

This patch delivers the Isle of Man Legislative changes.  The patch Readme also has important installation, setup instructions and guidelines – please ensure all necessary Post Install Steps are run after the patch installation.

This patch release is for 12.1 only at this time and can be found out on My Oracle Support > Patches. 

This patches is cumulative and includes all the functionality previously released under the following patches:

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, P11D Changes for tax year 2015-16, Tax Year End bug fixes) for more information

As this is an HRGlobal patch, the post install driver (hrglobal.drv) will need to be executed for PER GB (Human Resource) and PAY GB (Payroll).

Additional information in regards to mandatory patching for Oracle HRMS (UK) can be found in the following MOS document:

If you encounter any issues with these patches, please raise a Service Request via My Oracle Support under Oracle HRMS (UK) - Product 1001

Defining Properties in Oracle Property Manager

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. The property information which is defined in Property Manager can be used

  • To identify and to maintain the physical features of a property
  • To associate the property with Lease agreements
  • To assign it to employees and customers
  • To reporting purpose

Hierarchy of Properties

For built-up property, the default location hierarchy is building, floor, and office. For land, the location hierarchy is land, parcel, and section

1.  Properties: In properties window, you can define property with property name, location / address etc. Once the property is saved, you can associate existing buildings or land with it.  

Under properties, you can have

  • Building: You define buildings in the Building window, including the name, alias, tenure, and from and to dates of the building you are defining.
  • Floors: Once the building is defined, you define the names of the individual floors. You can define from and to dates for each floor, or use the dates that default from the Building window. You can also define the type of space like work space, etc.
  • Offices: Once the floor structure is defined, the next step would be to define offices. You define the individual office spaces by office number. You can define from and to dates, or use the dates defaulted from the Floor window. You can also break down the rent-able, usable, and assignable space by office number, and define the common areas, and the maximum and optimum number of occupants for a space.
2.  Land, Parcels, and Sections

Defining land is identical to defining buildings. You define land using a three-layered structure that includes defining land in the Land window, defining parcels in the Parcel window, and defining sections in the Section window. These windows contain the same fields as the Building, Floor, and Office windows.

For detailed information on how to define properties refer Property Manager user's guide.


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



« May 2016