TCA

Fusion Tax – Run Maintain Geography Name Referencing

In R12, this was a nice simple process, a solution that has been refined over the years to a stable and great solution. Fusion on the other hand still has a few teething issues as you would expect with any new release of software.

In R12, when running the same process, you had a drop down list of values so you could choose the table name. No such luck with Fusion tax at the moment (maybe fixed in future release), you need to know the table names and manually type them in, any mistakes and your request will fail.

This is the parameters:

Fusion TaxThat’s it nothing else to help you!

Continue Reading

Oracle R12 – US Tax Geography Validations

This post has been put together to demonstrate how you can correctly set-up your ‘Trading Community Architecture’ (TCA) for the United States in Oracle R12.
Step 1.

Navigate to the Trading Community Manager responsibility.
TCA > Administration > Geography Hierarchy

Then, search for ‘United States’ and then click on ‘Manage Validations’.

Oracle R12 - Manage Validations for TCA - Geography Hierarchy

Step 2.

HZ_LOCATIONS
HZ Locations will already be available but won’t have been correctly assigned. Set the values as shown below. HZ_Locations are your suppliers and customers.

Oracle R12 - Correctly Assign HZ_Locations
Step 3.

HR_LOCATIONS_ALL
HR Locations will need to be added as it is not seeded. Set the values as shown below. HR_Locations are your own locations.

Add your own HR Locations
Step 4.

Continue Reading

Oracle R12 – US Geography data clean up

This is not an approved Oracle approach but if you need to clean up bad data from an 11i upgrade where you have all sorts of States, Counties or Cities then the flowing SQL could help you.

 

DELETE

hz_relationships

where subject_id IN (

select geography_id

from hz_geographies where created_by_module = ‘EBTAX_MIGRATION’

)

and subject_table_name = ‘HZ_GEOGRAPHIES’

;

 

DELETE

hz_relationships

where object_id IN (

select geography_id

from hz_geographies where created_by_module = ‘EBTAX_MIGRATION’

)

and object_table_name = ‘HZ_GEOGRAPHIES’

;

 

The last step must be the delete of the HZ_GEOGRAPHIES as it is used in the queries above

 

DELETE hz_geographies where created_by_module = ‘EBTAX_MIGRATION’

;