Monday Apr 20, 2015

SR Automation Explained

We have been working hard to improve our time to resolution on the Service Requests you raise by automating the information and diagnostic gathering step. 

A vast majority of Payables SRs will now automatically ask you to provide a specific set of files, depending on how you answer the questions we ask when you choose your problem type.  The system will provide you with a clear action plan shortly after the SR is submitted requesting files e.g screenshots, log files and diagnostic outputs. 

Automation will continue to ask you to provide any missing files, until all the needed files have been provided.  At that point, your assigned engineer will be in a position to begin reviewing your issue and analyzing your uploaded files, with the intention to get you your solution faster.

For more information about Automation and how it works please review the following document:

Automated Troubleshooting Process (Doc ID 1998077.1)

Wednesday Mar 11, 2015

ORAchk 12.1.0.2.3 is Now Available for Download!

The new ORAchk release 12.1.0.2.3 is now available to download.

New Features in ORAchk 12.1.0.2.3

Broader Linux Support

ORAchk 12.1.0.2.3 now includes new support for both Linux on System Z and Oracle Enterprise Linux 7.

Deeper Product Support

ORAchk now supports upgrade checks for 12.1.0.2, enabling you to do pre and post upgrade checking for Oracle Database 12.1.0.2 to avoid the most common upgrade problems.

ORAchk now supports ASM checks and patch recommendations for single instance databases as well as the already supported RAC instances.

ORAchk can now query details related to the OS resource consumption of different GoldenGate processes, identifying any components using excessive resources. It also identifies if GoldenGate is configured to avoid known performance problems.

Oracle Enterprise Manager Agent support has now been added to the existing support for Enterprise Manager Repository checks. The agent checks now appear in a new “Enterprise Manager” section of the report. With the new EM 12c Agent checks, you will quickly identify common EM Agent configuration mistakes that if undetected can result in poor performance or a failure to run the Agent process.

New Report Section “Findings Needing Further Review”

There are certain things ORAchk can only do a partial check for, where a complete check requires information outside the scope of the machine or that require other customer specific knowledge. These partially identified checks now appear in the new section marked “Findings needing further review”. If you review these checks and verify they are not problematic you can choose to exclude them in the same way as any other checks, see Document 1268927.2 for further details.

Improved Health Score Calculation

The ORAchk Health Score calculation has been improved with version 12.1.0.2.3. Certain INFO level checks, which only communicate best practice and do not confirm a problem in your environment, no longer deduct points from your health score. This means that if you follow the recommended advice for excluding any non relevant “Findings needing further review” then a health score of 100 is now obtainable.

Over 60 New Health Checks

This release of ORAchk adds new checks for some of the most impactful problems seen to Oracle Customer Support specifically in the areas of:

  • Database performance, install, scalability & ASM
  • Cross stack checks for Oracle Applications running on Solaris & Oracle Hardware
  • Enterprise Manager Agents performance and failure to run
  • Oracle EBS Accounts Payables

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

Tuesday Mar 03, 2015

R12: Important Enhancement: ON-THE-FLY SLA Upgrade of Historical SLA Distributions--BATCH MODE!

Previous Announcement

In September of 2014 we announced the release of an important new enhancement in Oracle Payables that would allow you to transparently upgrade upstream 11i transactions from periods which had not been upgraded for Subledger Accounting (SLA), and which would negatively affect the accounting of dependent downstream transactions--without needing to apply the SLA Hot Patch or run the SLA: Upgrade Historical Subledger Transaction Accounting program.

The details and important benefits of that critical release and how it works can be found in detail in this blog post from back in Nov-14.

The only limitation to the functionality released back then was that it was only available when accounting transactions in "Online Mode". Now we are happy to announce that the second phase of this enhancement is also available.

Release of Phase 2

On 06-Feb-2015, the "Batch Mode" version of this enhancement was released via patch 20427746.  This patch introduces an entirely new concurrent process: "Payables Upgrade SLA Distributions for Historical Referenced Transactions". This process should be run in tandem with the "Create Accounting" program. It can be run independently prior to running "Create Accounting", or they can be run together as a request set.

Payables Upgrade SLA Distributions for Historical Referenced Transactions Concurrent Program

The parameters of the new program are similar to those used by the "Create Accounting" process to identify unaccounted events to process.

  •  Ledger
  •  Process Category
  •  Start Date
  •  End Date
  •  Batch Size
When run, the new program will identify all of the historical upstream transactions which would affect your unaccounted events, and upgrade them on the fly as required to prevent any errors when the "Create Accounting" program subsequently runs.

The original note describing the online version of the enhancement "R12: Important Enhancement ON-THE-FLY Upgrade of Historical SLA Distributions" (Doc ID 1938253.1) has been updated to provide additional information about the batch mode version of this enhancement.

If you have any questions or comments on this new functionality please post in the dedicated Payables Community thread

Friday Jan 30, 2015

New R12 Consolidated Patch for R12 1099 Reporting Available!

Development have just released a new consolidated patch for R12 customers for easier 1099 patching

Patch 19802493 was originally released as the R12 2014 changes patch but it did not contain all the files needed to ensure the latest code for all aspects of 1099 reporting.

Customers new to 1099 reporting would have had to apply multiple R12 patches to update all the necessary files for problem free reporting.  As a result a consolidation patch was requested for simplicity to ensure customers only needed to apply one patch.

If you have already applied 19802493 this is still valid as it provides the changes for this year.  However, if you are new to 1099s, didn't apply last years patches or are having issues with your reporting then you should ensure to apply the consolidation patch detailed below.

What do you need to do?

Apply the following patch specific to your release:

11i: Apply Patch 19802504 - 1099 REPORTING CHANGES FOR YEAR 2014

12.0.x: Apply Patch 20432513:R12.AP.A - 1099 CONSOLIDATION FOR THE YEAR 2014 for R12

12.1.x: Apply Patch 20432513:R12.AP.B - 1099 CONSOLIDATION FOR THE YEAR 2014 for R12

12.2.x: Apply Patch 20432513:R12.AP.C - 1099 CONSOLIDATION FOR THE YEAR 2014 for R12
 

Oracle Payables Plans for 2014 1099 Reporting (Doc ID 209913.1) has been updated with the new patch details.

This is an important update on the original blog post

Wednesday Jan 07, 2015

Get Notified When A New or Updated Product Analyzer or Diagnostic is Released

Support continues to invest in the expansion of product analyzers and other diagnostics by improving them with additional checks and when we do we release new versions of these tools. 

In order for you to be alerted by email when a new version is released, we strongly suggest that you make your frequently used diagnostic tools 'Favorites' and utilize the 'Hot Topics E-Mail' feature. 

Follow these instructions to enable the Hot Topics email notification:

  • Query one of the diagnostics e.g. Doc ID 1360390.1 in My Oracle Support and click on the Star to the left of the title to make the document a favorite.
    Note: If the star is filled in yellow then it is a favorite already.

    ScreenHunter_001.bmp

  • Subscribe to receive automated e-mail notification.
  • At the top of the page, click on your name. At the drop down go to My Account.

    2.bmp

  • Go to Hot Topics E-Mail

    3.bmp

  • Select "Documents I've marked as favorites" and make sure you change the Format to "HTML".

  • You can set the Frequency of the notifications to Daily or Weekly.

    4.bmp

Thursday Nov 27, 2014

1099 Tax Reporting Patches for 2014 Are Now Available

The 1099 Tax Reporting changes for 2014 are now available for download from My Oracle Support.

Year 2014 IRS Mandated Changes:

The following updates were made to reflect the United States (US) 1099 tax reporting changes required by the US Internal Revenue Service (IRS) for the tax year 2014:

  • The payment year was updated from 2013 to 2014 on US 1099 forms.
  • The state of Iowa was removed from the Combined Filing Program.

What Do You Need To Do?

1. Apply one of the following patches:

11i: Apply Patch 19802504 - 1099 REPORTING CHANGES FOR YEAR 2014
12.0.x: Apply Patch 19802493:R12.AP.A - 1099 REPORTING CHANGES FOR YEAR 2014
12.1.x: Apply Patch 19802493:R12.AP.B - 1099 REPORTING CHANGES FOR YEAR 2014
12.2.x: Apply Patch 19802493:R12.AP.C - 1099 REPORTING CHANGES FOR YEAR 2014

2. Run the Oracle Payables 1099 Setup Test (Doc ID 829636.1) to check for any problems and resolve any reported issues before testing 1099 functionality.

For full details please review Oracle Payables Plans for 2014 1099 Reporting (Doc ID 209913.1)

Questions or comments? 

Ask a question on the dedicated community thread for this topic

Monday Nov 24, 2014

How to Create Custom Invoice Charges Matching Validations for LCM

In R12.2.4 Landed Cost Management and Oracle Payables development teams are delivering Invoice Matching Enhancements which will not only expose the LCM information at the time of invoice matching but they are also creating hooks for users to write their own code for validating from a LCM perspective.

A white paper has been written to help the technical teams understand how validations could be written, including sample code.

The following are supported by those public APIs:

  • Validate a match to an individual receipt line, under LCM perspective, and decide if the match should be allowed or not, depending on the validation results
  • Validate the whole invoice, under LCM perspective, and decide if the invoice should be put on hold or not, depending on the validation results

For more information please review How to Create Custom Invoice Charges Matching Validations for LCM (Doc ID 1678192.1)


Wednesday Nov 12, 2014

R12: Resolve Supplier Bank Account Issues When Creating Payment For Customer Refunds

Whilst creating the payment for a Customer Refund (Payment Request) Invoice it is common to see the following error:

  • Supplier Bank Account attached to document payable is end dated

One reason for this message is that there is a missing record in the IBY_PMT_INSTR_USES_ALL table.

Previously we have used data fixes to correct the problem but now the application offers a way to resolve this without the data fix by using the "Enable As Supplier" functionality provided by the Supplier Hub application.

Full details are available by reviewing the My Oracle Support document:

R12 Solve Customer Refund - Supplier Bank Account Attached To Document Payable Is End Dated (Doc ID 1942142.1)

Questions or issues?

Please post any comments or concerns in the Payables Community Thread for this topic.

Tuesday Nov 04, 2014

R12 : Important Enhancement ON-THE-FLY Upgrade of Historical SLA Distributions

In Oracle Payables, a payment has a functional dependency on invoice, i.e. the payment needs to be accounted to same liability account as the invoice has been accounted for. In such a scenario, invoice is referred to as the upstream transaction and the payment as the downstream transaction.

In a business flow prior entry application, the upstream accounting is mandatory for the downstream transaction accounting to go through. The accounting journals must be created in each ledger (primary, ALC and secondary) for all upstream transactions to have the accounting to be created in all the related ledgers of primary ledger for the downstream transaction.

Similar dependencies are there for other transactions also like Invoice Cancellation, Prepayment Application, Payment Cancellation, Payment unclearing etc.

Business flow failures generally have the error:

  • Error 0 : This line cannot be accounted until the accounting event for the application Payables that it references has been fully accounted.

Old Method:

In order to resolve this situation, users needs to identify and account all upstream transactions before accounting the downstream transactions.  This was more complex for transactions that referenced one or more 11i transactions as the upstream transaction and in some cases it was mandatory to have Hot Patch applied or SLA: Upgrade Historical Subledger Transaction Accounting Program ran to cover the period related to the upstream transaction.  This was required even for accounting a single downstream transaction.

New Method:

With the exciting enhancement delivered via Patch 19568225, downstream transactions failing business flow for an upgraded upstream transaction can be successfully accounted using ON-LINE accounting of the downstream transaction.

With on-the-fly upgrade, a new profile option SLA: On-the-fly Upgrade of Historical Subledger Accounting Distributions is introduced which when set to Yes will cause a dedicated procedure to identify the few upstream transactions missing XDL and populate them on the fly, prior to accounting the downstream transaction, and this is transparent to the user. Thus the volume of transactions which "require" upgrade is reduced from a huge number (across multiple years and applications) to just a few upstream transactions which are related to the current downstream transaction.

Key benefits of this enhancement:

  • Prior to the enhancement, even if there is a single upstream transaction in payables which is missing distribution links, users would be required to apply the hot patch for the entire non-upgraded date range, till the period containing the upstream transaction. e.g. consider the earliest upgraded period is JAN-14. If user pays an upgraded invoice from 11i which has a GL date as JAN-2000, then when using hot patch or the On-Demand distribution links upgrade users would need to upgrade the transactions for around 13 years of invoices and payment both. Hence, accounting a single transaction required upgrade for all of the transactions for over 13 years, which due to data volume and complexities of upgrade be very time consuming.

  • Also, hot patch required that all the data be upgraded for 'all' applications (not just payables), which adds to the time and complexity of upgrade.

  • Also, even if there is a single transaction in the overall time duration which when upgraded (to create XLA_DISTRIBUTION_LINKS records for the upstream transactions) which would cause the Hot patch or On Demand XDL upgrade to error out (XLA_DISTRIBUTION_LINKS_U1 violation), the entire concurrent process would fail. Scanning the entire time duration for corruptions causing failure in XDL population, fixing the same, and restarting the upgrade is often complicated and requires development intervention over bugs, which causes delays with accounting the downstream transactions. 

Please review R12: Important Enhancement ON-THE-FLY Upgrade of Historical SLA Distributions (Doc ID 1938253.1) for full details.

If you have any questions or comments on this new functionality please post in the dedicated Payables Community thread.

Tuesday Oct 14, 2014

ORAchk Health Checks Tool: New Version 12.1.0.2.1 Released

The new ORAchk release 12.1.0.2.1 is now available to download.

Easier to stay up to date with the most current version of ORAchk

ORAchk release versioning now aligns with and follows the same format used by the Oracle 12c Database Patch Set Updates (PSUs); this version is 12.1.0.2.1, the next will be 12.1.0.2.2.

It’s also now even easier to update ORAchk across multiple machines.

  1. Download the latest release of orachk.zip into a shared network staging directory
  2. Set the environment variable $RAT_UPGRADE_LOC to the staging directory
  3. The next time ORAchk is run it will prompt you to auto update

Over 70 new EBS checks

ORAchk support for EBS has been enriched and broadened, with even more checks for Oracle Payables (R12) and Oracle Workflow and now with release 12.1.0.2.1 introduces new support for Oracle Order Management (R12) and Oracle Process Manufacturing (R12).

New ORAchk Support for Windows

ORAchk is now supported on Windows when run within a Cygwin environment. Instructions for configuring Cygwin can be found from Document 1268927.2. ORAchk now includes hundreds of database and application checks which will run on Windows. There are even more Windows specific checks in the pipeline.

Easier execution for environments with role separation

You no longer need to have different users execute different ORAchk profiles to workaround your company’s implementation of role separation. ORAchk can now be run once as root to execute all checks. Prior to executing checks that do not require root access, ORAchk will switch user to the lower level accounts.

Faster execution time

When running against multiple databases, ORAchk can now run database checks in parallel meaning it takes a fraction of the time to complete execution. Parallel database execution is now the default. It can be turned off, if you prefer to run checks serially.

Enhanced comparison of result output

Quickly find out what has changed on your system between two ORAchk runs. When ORAchk is run with the –diff command it will now not only compare check results but collection data too. Quickly compare and understand differences in kernel parameters or database initialization parameters.

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

Wednesday Oct 08, 2014

R12 Payments: Resetting Default E-Business Suite Messaging Email Setting

Potential Sending of Email with Incorrect Sender

If your Oracle E-Business Suite system is using certain features of the Oracle Payments module, and it has not been fully configured with implementation specific sender addresses for outbound emails, your system may be sending emails that appear to come from visioncorp.com.

This may happen if your:

  • Oracle E-Business Suite system is using certain features of the Oracle Payments module
  • Oracle E-Business Suite system has not been fully configured with implementation specific sender addresses

Oracle Payments supports sending of email notifications of payment processing events. For this purpose Oracle Payments uses email templates with placeholders or substitution variables. One of these variables is the sender's email address used in the From email header.

This data element in the default template is sourced from a message in FND_NEW_MESSAGES, the message names are

    IBY_FD_SRA_EMAIL_FROM
    IBY_FC_PYR_NOTIF_EMAIL_FROM

the default shipped values are

   IBY_FD_SRA_EMAIL_FROM                        account_payables@visioncorp.com
   IBY_FC_PYR_NOTIF_EMAIL_FROM           account_recieveables@visioncorp.com

This means that if you are using Oracle Payment with the "Separate Remittance Advice" (SRA) feature configured for email notification and you have not changed the sender address as part of your implementation as described in Doc ID 471471.1, your system will be sending these notifications with a From header reflecting a @visioncorp.com address.

The same situation is seen if anyone is testing the SRA feature on a unconfigured demo system (such as a VISION demo instance).

This may cause confusion for the legitimate recipients of such email addresses who may conclude the email messages were sent from the owner of the visioncorp.com domain rather than the actual sender of the email message.

The results of such confusion are unpredictable but may cause ignoring the email (since the FROM address is not recognized as valid) or may cause the receiving organization to bounce the email to the visioncorp.com domain email address with unpredictable text indicating the reason the email is being "returned" to visioncorp.com.

There are three methods to resolve this issue and all are detailed in the following document:

Resetting Default E-Business Suite Messaging Email Setting (Doc ID 1923170.1)

Tuesday Sep 16, 2014

New Functionality - Invoice Approval Parallel Processing

Invoice approval workflow now supports parallelization at the invoice header level on 12.1.x and 12.2.x.

The main advantage for this change is to shorten the processing time for an invoice to get approved.

The parallel approval process imposes a hierarchical (tree) structure on the transaction’s approver list and enables each part of the tree at a given level to progress through its notification-approval cycle asynchronously.

This enables the approval process of each item in the transaction to continue irrespective of the progress of approval process of other items in the transaction and reduces the transaction's approval process time.

If user selects the parallel ordering mode, the approval notifications will be sent to all approvers at the same time. The invoice may get approved when one or all approvers approve the invoice, depending on the voting regime that is set up.

What voting regimes are supported?

Serial:
This voting regime assigns group-or-chain-member order numbers in ascending order of the member order numbers, breaking ties arbitrarily.
All group members must approve the notification in order for the invoice to get approved.

Consensus:
This voting regime assigns group-or-chain-member oder number one to all members.
All group members must approve the notification in order for the invoice to get approved.

First-Responder-Wins:
This voting regime assigns group-or-chain-member order number one to all members.
As soon as one approver approves the notification, the invoice will get approved.

Order number:
This voting regime sets each member's group-or-chain-member order number to the member's order number.
All group members must approve the notification in order for the invoice to get approved.


For more information please review R12: New Functionality Invoice Approval Parallel Processing (Doc ID 1904137.1)

Please provide any feedback on this new feature via the community post on this topic.

Friday Sep 05, 2014

Invoice Validation Parallel Processing New Functionality Available

What has changed?

The Invoice Validation concurrent program is now equipped to spawn multiple child requests based on the Purchase Order matched invoice load and the newly seeded profile "AP:Maximum Invoice Validation Child Requests".

The user continues to submit a single Invoice validation program with his/her preferred parameters but internally the program groups the invoices matched to same Purchase Orders and ensures that each such group is processed by a single child request.

Whereas for invoices that are not matched to any Purchase Orders, the system distributes these invoices equally amongst the maximum number of child requests spawned (as per the value set by the user in the aforementioned profile).

Why the change?

1) The current invoice validation concurrent program was not scaling up for high volume of invoices.

2) If multiple requests of the invoice validation concurrent program are submitted and invoices matched to the same Purchase Orders are processed by two or more requests then there are possibilities of lock contention errors on PO_HEADERS_ALL in any of the requests that concurrently attempts to update the PO object.

3) To avoid conflicts, user had to wisely select the parameters at the time of submitting the concurrent program or have conflict domains defined that constrained the program to execute serially.

4) Submitting multiple requests of the program causes an overhead of reviewing multiple log files and outputs.

More Information

R12: New Functionality Invoice Validation Parallel Processing (Doc ID 1917614.1)

If you have any questions on this new functionality please use the community thread


Friday Aug 29, 2014

Subledger Accounting: Proration Types in Multi Period Accounting

Looking for an overview and explanation of different Proration Types in Multi Period Accounting (MPA) feature in R12?

Multi Period Accounting (MPA) enables users to create accounting for a single accounting event for more than one GL period.  This functionality is primarily used to recognize revenue or a prepaid expense across multiple GL periods.

Within Multi Period Accounting, application provides different ways to Prorate the amounts.

  • First Period
  • Days In Period
  • Total Days In Period
  • 360 Days

The Amount prorated depends on the Proration Type.

R12: Subledger Accounting: White Paper Explaining Different Proration Types in Multi Period Accounting (Doc ID 1915795.1)
explains the proration type in detail and includes a step by step guide on how to configure the MPA feature for a business transaction.

Tuesday Aug 26, 2014

Understanding External Bank Account Masking

Struggling with Bank Account Masking functionality in Oracle Payments?

In support we often see questions asked related to the masking of External Bank Accounts so if you also want to learn more about this functionality then take a look at the following document:

External Bank Account Masking (Doc ID 1918242.1)

In it you will find the answers to the following common questions:

  • How are External Bank Account numbers masked?
  • What Setups Need to be Changed in Order to Update EXTERNAL Bank Accounts That Have Been Masked?
  • How to Set the Masking for Selected Responsibilities?


About

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

Twitter

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
7
9
10
11
16
17
18
22
23
24
25
26
27
28
29
30
31
      
Today