Collection of EBS R12 setup problems and matelink Solutions

 

1) tax is empty when create a tax jurisdiction

Oracle E-Business Tax-version: 12.0.2
Information in this document applies to any platform.

Goal

Q1: created a new tax regime, tax and tax status in e-business tax.
Now want to create a tax jurisdiction that can be linked up to a rate so that I can complete the configuration.
When I go to select the tax value on the "Create tax jurisdiction" Page, nothing is listed in the lov.
As a result, cannot complete the tax jurisdiction configuration.
What am I missing?

Q2: for the taxes that got migrated as part of the upgrade from 11.5.9 to R12, tax jurisdiction values does not exist. Is this intended?

Solution

A1: Check your tax setup. Have you defined geography type? If not, you will be not able to tie the geography based setting of tax jurisdictions, without first defining this.

A2: Yes, this is correct, this is the intended functionality. Please see comment from development in bug 5713854:
"Only for Migrated records, we cannot derive jurisdiction for a tax. So only for Migrated records, system allows tax definition without having associated jurisdictions ."

2) Geography name is empty when create a tax juristiction

Oracle project costing-version: 12.0 to 12.1
This problem can occur on any platform.

Symptoms

In a fresh Release 12 environment, when creating a new jurisdiction, the geography values (state, province, city, etc) cannot be found in the list of values (LOV ). no records are retured or in some cases only some are returned.

Changes

Geography hierarchy was defined for a new country from scratch

Cause

The geography start dates were set to be 30-dec-2008 but the tax and jurisdictions were being defined with back dated dates of 01-Jan-2000. since the geographies were not active on that earlier date they did not show up in the list of values.

Solution

Resolution for this was to change the start date of the tax and jurisdiction to be on or after the start date of the geography values.

3) retriable activities
Error: Please define a party tax profile for operating unit & org_id

Oracle receivables-version: 12.0 to 12.0
This problem can occur on any platform.
Arxsumrt. FMB

Symptoms

Unable to setup receivables activities. When attempt to navigate
Form.

Navigator drop-down> setup, retriable, retriable activities
Error: Please define a party tax profile for operating unit & org_id

Cause

The issue is caused by the following setup:
Did not setup operating unit owning tax content Profile

This issue is described in bug 5899659-receivables activity error please define party tax profile for & ordid

Solution

To implement the solution, Please execute the following steps:

1. Go into the responsibility: tax managers

2. Navigate to parties-> party tax-> profiles

3. Party type: operating unit owning tax content
Party Name: populate your operating unit name

You shoshould have a result to this query.
If you do not make sure you create a party tax profile for your operating unit of
Type: First Party legal entity.

4. Verify the each component of location address associated with your organization is valid

5. retest the issue.

6. migrate the solution as appropriate to other environments

4) unable to create a party tax profile for a newly defined operating unit

Oracle E-Business Tax-version: 12.0 to 12.1
This problem can occur on any platform.

Symptoms

After setting up a new operating unit, the operating unit can be selected in the party tax profile form within EB tax but a profile cannot be created as the create button is not displayed.

Changes

Occurs when a new operating unit is defined

Cause

This occurs when the location address associated to the new operating unit is defined incorrectly. the SQL used to select operating units in ebtax validates that the country code is correct. unfortunately the locations form allows a user to enter the country code free-form thus if a user enters "United States" instead of us the operating unit will not be displayed.

Solution

-- To implement the solution, Please execute the following steps ::
1. Go into the responsibility: receivables Manager

2. Navigate to setup> system> organizations> locations

3. query the location that you have defined for the new operating unit

4. Open the address and change the country from to use the proper 2 digit abreviation save

5. Return to Tax Manager and verify that you can now set the party tax Profile

5)Unable to see the Legal Entity List of value in the bank account owner Field

Oracle cash management-version: 12.0 to 12.0
This problem can occur on any platform.
Accountownerusepg 120.8

Symptoms

Unable to create a new bank account in Release 12 in cash management. The list of values in the bank account owner does not bring the information of the legal entities that have been created.

Cause

This is not a bug, it is a setup issue. Cash management responsibility must be assigned the legal entities that you want to grant the access to all bank accounts.

Solution

Please do the following to assign legal entities to the cash management responsibility:

1. log in as SysAdmin.
2. Go to the user management responsibility.
3. Path: Roles & role inheritance
4. In the type field select roles and responsibilities
5. Wait until a new field appears, you will see the Category field, please select Miscellaneous
6. In the application select 'cash management' and click on go button.
7. Search your cash management responsibility or role that you are using to create your bank account.
8. Click on the update icon.
9. A new window will be displayed, please click in the security wizard button.
10. For ce umx Security wizard click on the run wizard.
11. In this window you shocould Add the legal entities that you want to grant the access to all
Bank accounts within a legal entity and choose the privilages that you want to assign to this role on
Bank accounts such as: use, maintenance and bank account transfers.
12. Save and apply the changes and then verify in cash management responsibility if you now are
Able to see that legal entity in the bank account creation form.

6) arxsudrc: cannot open receept class form-FRM-40735, ORA-6502

Oracle receivables-version: 12.0.5
This problem can occur on any platform.

Symptoms

When attempting to enter the receept classes form, the following error occurs.

FRM-40735: PRE-FORM trigger raised unhandled exception ORA-06502


The issue can be reproduced at will with the following steps:

1. log into application and select receivables responsibility
2. Nav: setup-> receipts-> receipclasses

Due to this issue, users cannot complete the setup

Cause

Replicate seed data has not been executed. Running replicate seed data process will create the seed data for the new operating unit

Solution

To implement the solution, Please execute the following steps:

1. Connect to the application with System Administrator responsibility
2. run concurrent program 'replicate seed data'

7) retriable activities screen when opened throws error ORA-01422: exact fetch returns more than requested number of rows.

Oracle receivables-version: 12.0 to 12.0.6
This problem can occur on any platform.
Receivables activities form.

Symptoms

Symptoms:

When opening the retriable activities screen it triggers.

ORA-01422: exact fetch returns more than requested number of rows.

Cause

The cause of the issue is invalid/incorrect data in <ar_system_parameters_all>.
Found that there were duplicate records for the org_id with set_of_books_id =-1.

Solution

Execute the below scripts in the test instance and retest the issue before migrating the changes to production.

Create Table ar_system_parameters_all_bckup_82
As select * From ar_system_parameters_all
Where set_of_books_id =-1
And org_id = <& enter_org_id for operating_unit>;

Delete from ar_system_parameters_all
Where set_of_books_id =-1
And org_id = <& enter_org_id for operating_unit>;
Commit;

After executing the scripts, log out of Oracle Applications and log in again so that the parameters get affected.
Click on receivables responsibility and navigate to set up-> receipts-> receivables activities and retest the issue.