Document 1992106.

1 of 5

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

E Business Tax Extensible Parameters Feature and its Usage (Doc ID 1992106.1)
In this Document
Abstract
History
Details

Sample Tax Extensibility Tax Rule Implementation

Behavior of the feature for other Documents (Adjusted, Applied, Ref Docs types)
Summary

APPLIES TO:
Oracle E-Business Tax - Version 12.0.6 to 12.2.4 [Release 12.0 to 12.2]
Information in this document applies to any platform.

ABSTRACT
Introduction of E Business Tax feature "Tax Extensible Parameters".

HISTORY
The feature facilitates extending the tax determinants. The customers are currently allowed to define the tax rules based on seeded
tax determinants but this feature allows them to extend the determinants and use them in the tax rules to ensure desired tax calculation.
The Tax Extensible Parameters provides an option to use any attribute as a tax determinant and subsequently use these tax determinants in
the tax rules.. A few complex business case require the customer to use additional determinants hence this feature.

DETAILS
The main intent of the enhancement is to provide flexibility and robustness to define any business attribute which Customers can choose as
a tax determinant and then build simple tax rules to address the requirements easily.
Key considerations
1.

The feature supports multiple data types. The attribute of the Character, Numeric and Date data types are supported and each data
type can have 10 attributes.

2.

The feature can be enabled for a combination of operating unit, application and event class.

3.

The errors due to any incorrect custom hook API implementation are properly handled and logged.

Sample Tax Extensibility Tax Rule Implementation

Lets take the below sample requirement to see the usage of the Enhancement.

Requirement: Customer wants a particular tax to be not applicable for Sales Transactions based on the outcome of a complex logic
held by business; say for e.g. Customization or Standard is the result of the logic. Here this Outcome has to be used as a tax
determinant and define a tax rule using expenditure types.
Solution: Call the extensibility feature provided by E-Business Tax to implement the aforementioned requirement. E-Business Tax
provides 10 numeric, 10 characters, and 10 date attributes on the transaction line input table which the client can customize and
populate. These attributes are provided for client extensibility purposes. To address this requirement, character9 extensible attribute
can be populated with the project expenditure type, and this attribute can then be used to define the tax rule.

The following are the steps to implement the above requirement.

2/7/2016 7:58 PM

Document 1992106.1

2 of 5

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

1. Turn on the extensibility by checking the Allow extensible tax parameter check box on the Configuration Owner Tax Options UI for
the application, Operating unit, and event class for which you want to enable the tax rule. Enable the feature at Configuration Owner
Tax Options using the below navigation.
Tax Managers -> Defaults and
Controls -> Configuration Owner Tax Option. Query for the current OU for which the Transactions are being created as Configuration
Owner, Application Name: Receivables, Event Class: Invoice. Enable Option Allow Extensible Tax Rules (End date the Current
Configuration Owner Tax Option and create new one with everything else same and this option enabled).

2. Override the zx_tax_param_extensibility_pkg.derive_extensible_params API and change the c_pop_tax_extn_params cursor to

populate char9 extensible attribute with the value of the project expenditure type and compile it in the database. The cursor will
fetch the project expenditure type into zx_tax_param_extensibility_pkg.output_structure.char1 which will be further populated in the
main code into char9 on zx_transaction_lines_gt.
3. Define a determining factor set using the Determining Factor Class: Transaction Input Factor and the Determining Factor Name:
Character Attribute 9. The Screenshot below shows the Determining Factor Set TESTCUSTATTR defined.

4. Define a condition set using the above defined Determining Factor Set and form a desired condition by entering the value of the
project expenditure type for which you want the rule to be executed. The Screen shot below shows the Determining Factor Set
TESTCUSTATTR defined.

2/7/2016 7:58 PM

Document 1992106.1

3 of 5

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

5. Create a tax rule and use the condition set defined above. The below screenshot shows Tax Applicability Tax Rule TESTRULEATTR
created which will determine if Character Attribute 9 is equal to Customization or not and then make the tax not applicable or
applicable.

2/7/2016 7:58 PM

Document 1992106.1

4 of 5

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

6. Modify the Custom Hook Code API (Sample Code file Attached) ZX_TAX_PARAM_EXTENSIBILITY_PKG.derive_extensible_params as
per the business logic.
For simplicity If I considered the value for Char9 is a constant which is needed to be populated for every transaction,(The
Modified Package is provided to this note as an attachment) then the changes required are listed below
un-comment the cursor c_pop_tax_extn_params. By Default its commented.
Modify Cursor c_pop_tax_extn_params to populate the Constant Value Customization in place of NULL against Char9
Modify the Conditions such that the cursor c_pop_tax_extn_params is only opened for application_id = 222 , entity_code = '
TRANSACTIONS', event_class_code = 'INVOICE'

Behavior of the feature for other Documents (Adjusted, Applied, Ref Docs types)
1. For Credit Memos, Debit Memos, Prepayment applications, PO Matched Invoices etc the tax parameter extensible attributes are
copied from the base document even when the Option Allow extensible tax parameter is not enabled.
2. For Credit Memos, Debit Memos, Prepayment applications, PO Matched Invoices etc the tax parameter extensible attributes are
populated from the Custom Hook API when the Option Allow extensible tax parameter is enabled.

SUMMARY
This feature or enhancement is available to customers through the Patch 21083552:R12.ZX.A/B/C AND Patch 21075928:R12.ZX.A/B/C
1.

The feature supports multiple data types. The attribute of the Character, Numeric and Date data types are supported and each data
type can have 10 attributes.

2.

The feature can be enabled for a combination of operating unit, application and event class.

3.

The errors due to any incorrect custom hook API implementation are properly handled and logged.

Didn't find what you are looking for?

2/7/2016 7:58 PM

Document 1992106.1

5 of 5

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

2/7/2016 7:58 PM