Continuing from last week’s blog article, new enhancements in Oracle E-Business Suite Projects Applications Release 12.2 allow companies to address various project costing requirements without the use of extensions. There are three key enhancements:
Oracle has provided several enhancements that go beyond Standard Costing. These enhancements, which offer more options and greater flexibility, give companies new tools to help ensure that their costing approach fits their business. Read part one of this blog series to learn more:
iPayment is no longer available in Oracle R12. So what has become of the features and functions previously offered by iPayment? R12 introduces the FDP Dashboard as a component of R12 Payments and to replace iPayments features and functions. Continue reading:
The new Oracle Payments system combines Funds Disbursement and Funds Capture into a single centralized payment engine. Organizations can quickly generate enterprise-wide payments across multiple business units, currencies, and regions:
In Release 12 and 11.5.10, out-of-the-box integration between Oracle E-Business Suite Projects and Oracle EAM allows the collection of maintenance costs into Oracle Projects from EAM. You can carry out maintenance activities and consume different resources, and the resulting costs of those activities can be transferred into Oracle Projects.
Oracle E-Business Suite Release 12 offers a global tax solution for “Order to Cash” and “Procure to Pay” flows. This feature utilizes centrally defined rules, rates, and jurisdictions which are stored in a Tax repository to calculate Taxes at a line level and offers strong audit capabilities using the Tax Record Repository.
Oracle customers around the globe eagerly awaited the release of Oracle E-Business Suite Release12 for several years. Oracle R12 was touted as being a genuinely globalized release. Many customers have migrated to a complete Oracle R12 environment.
The functionalities relating to CWKs have been enhanced in EBS R 12.1 and above. Before this release, there were limitations in effectively using CWK across multiple projects if their PO does not reference these individual projects in its Distribution.
This is Part 2 of a 2-part blog series on Program Reporting in Oracle E-Business Suite Project Management (PJT). Dive into the program roll-up metrics, how the process works, publishing work plans for projects and programs, and key design considerations.
The Oracle E-Business Suite Project Management (PJT) application offers a key feature that is not yet widely used but delivers valuable functionality: Program Reporting. This 2 part blog article will help you understand how to use Program Reporting.
