Scheduled Deprecation of Legacy Obligation Features
Posted
by Wes Curtis
on Oracle Blogs
See other posts from Oracle Blogs
or by Wes Curtis
Published on Tue, 5 Jun 2012 15:50:48 +0000
Indexed on
2012/06/05
16:44 UTC
Read the original article
Hit count: 391
/Oracle
The Obligation object in ETPM includes some functionality and tables that, to our knowledge, are not being used by customers and implementers are this time. Removing this logic and the related tables should benefit the performance of and simplify logic executed during Obligation maintenance processing. The Release Notes included with ETPM v2.3.1 announced that the product plans to deprecate the functionality on Obligation for Contract Terms, Contract Quantities, Tax Exemptions, Terms & Conditions and Obligation Type Start Options. Our plan is to remove this functionality in the next release of ETPM.
We have already confirmed with most project teams that these features are not being used so the deprecation should have no impact on existing designs or process. If you think your project may be impacted by this deprecation, please review any Business Object that has been created for the Obligation maintenance object to make sure that no elements are being defined for any of the following child tables:
- CI_SA_CONTERM
- CI_SA_CONT_QTY
- CI_TOU_CONT_VAL
- CI_SA_TC
As part of this deprecation, the following administrative tables are being removed along with their related metadata:
- Contract Quantity Type
- Tax Exempt Type
- Terms and Conditions
Please contact myself or the Oracle Tax Product Management team if your implementation has actually used these objects in their designs. We can discuss options to mitigate impacts of this planned deprecation. We will continue to announce planned deprecations in the Release Notes for each release and will contact project teams ahead of time to confirm that these deprecations will have little to no impact on our customers.
© Oracle Blogs or respective owner