Featured Bloggers
R12 Upgrades
R12.2 Financials – New Functionality Added for Financials
Date: August 23rd, 2011
Categories: E-Business Suite
Although yet to be confirmed, Oracle is expected to release version R12.2 of it’s eBusiness Suite in October 2011. BizTech has analyzed the following modules, and has determined that significant functionality is expected to be added in R12.2. Some of the more significant functionality has been backported to older releases, and where appropriate, BizTech has identified the necessary patches.
» Read More
R12.2 Financials – Tax, Legal and Regulatory Updates
Date: August 23rd, 2011
Categories: E-Business Suite
Although yet to be confirmed, Oracle is expected to release version R12.2 of it’s eBusiness Suite in October 2011. BizTech has compiled a list of the Tax, Legal and Regulatory updates that are expected to be added, amended, or removed in this latest release.
» Read More
R12.2 Financials – Modules with No New Functionality
Date: August 23rd, 2011
Categories: E-Business Suite
Although yet to be confirmed, Oracle is expected to release version R12.2 of it’s eBusiness Suite in October 2011. BizTech has compiled a list, module by module, of the main features that have been added, amended, or removed in this latest release.
BizTech has analyzed the following modules, and has determined that at this time, no new functionality is expected to be added in R12.2
» Read More
Tips for troubleshooting Purchase Order Import errors with Projects
Date: August 15th, 2011
Categories: E-Business Suite
Recently, I received a call from a customer requesting my assistance with troubleshooting Purchase Order Import errors in R12. The customer was trying to import 1000 purchase orders that were related to projects. They were encountering the following error and were having difficulty finding the root cause as the message was vague:
Project information on the distribution is not valid. &PJM_ERROR_MSG
Here are some tips on places to look to resolve such issues:
» Read More
Supplier Site Payment Methods in R12
Date: July 26th, 2011
Categories: E-Business Suite
In R12 the suppliers were merged into the Trading Community Architecture (TCA). The default payment method for supplier sites are now located in the IBY_EXT_PARTY_PMT_MTHDS table and not the AP_SUPPLIER_SITES_ALL table. Below is a query that will return a list of all suppliers, supplier sites and their payment methods. The default payment method is denoted with a primary flag = ‘Y’.
» Read More
Upgrading to EBS R12? What happens to my custom NACHA files?
Date: April 13th, 2011
Categories: E-Business Suite, Oracle Application Services
As a consultant I have seen numerous organizations conduct business with banks that do not conform to the ACH CCD Cash Concentration/ Disbursement File format. Most recently I was at an organization that sends electronic funds transfer (EFT) files to a Canadian bank that required a proprietary file format for incoming EFT files. To conform to the bank’s requirements, the organization had customized the NACHA Payment Format program in 11i.
In R12, Oracle introduced the Payments module which replaces the payments functionality within Payables. The Payments module utilizes BI Publisher templates instead of Oracle Reports to generate formatted EFT files. As a result, you have to re-implement the customizations that were made to the NACHA Payment Format program in earlier releases.
The organization was frustrated to hear that they would need to re-implement the customizations they made in 11i to accommodate their bank’s proprietary file format, since they had invested a significant amount of time and money to modifying the NACHA Payment Format program which was written in Oracle Reports. Their frustration was short lived once they saw how easy it was to create and/or modify eText templates using BI Publisher. They were able to develop the new eText template in the required format using BI Publisher in one day compared to the 7-10 days it had taken them to modify the APXNACHA.rdf report in 11i.
In R12, Oracle comes standard with several different EFT file formats including the following:
- US NACHA CCD Format
- US NACHA CCDP Format
- US NACHA PPDP Format
- US CCDP Consolidated Format
- US PPDP Consolidated Format
- US NACHA Generic Format
With very little guidance, the Oracle developer from this organization was able to download the template from the Payments Setup Administrator and begin working with an XML file that the organization generated from the Payments module by running a payment batch for electronic payments. The developer chose to start with the US NACHA CCD Format because it most closely matched the proprietary format of the bank. Within a couple of hours the developer was reviewing and validating an actual EFT file using the template viewer within the Oracle BI Publisher Desktop application. He was able to modify the file and immediately review the results all from his own desktop using the XML file that was downloaded. By the end of the day he was able to upload the new template to Oracle via the Payments Setup Administrator. The next day the organization was able to generate test files to send to the bank for validation.
So, the bad news is that your NACHA templates from 11i will need to be rebuilt when upgrading to R12, but the implementation has become much easier by using BI Publisher. If you’re lucky, one of the numerous out of the box templates will satisfy your banks requirements and you won’t need to modify anything.
Stay tuned for additional posts on how to modify the ‘Oracle Payments Funds Disbursement Payment Instruction Extract 1.0’ data definition if your bank requires data fields not in the XML output.
Cloud Computing CRM Managed Services OBIEE 11g Oracle-Essbase Oracle Business Intelligence Oracle EBS R12 Oracle Financials Oracle Hyperion Financial Management Oracle Hyperion Planning R12 Upgrades Supply Chain
