legal entities upgrade troubleshooting

Legal Entity ConfiguratorTroubleshooting LE Upgrade

Author: Legal Entity Development

Creation Date: April 18, 2023

Last Updated: April 18, 2023

File URL: http://files.oraclecorp.com/

Version: 1.1

Status: FINAL

Approver Name Role Date

Copyright 2023 Oracle Corporation All Rights Reserved

This document is not a promise to deliver and may not be included as part of any contract.

1. Contents

1.1 Change Record

Date Author Version Change Reference

09-Dec-2008 Shyamala Narayanaswamy 1 Created10-Dec-08 Jacintha Mary 1.1 Moved it to Oracle template, added more navigation steps and added

some additional content..

1.2 Contributors

Contributor Role Position

Jacintha Mary Development ManagerShyamala Narayanaswamy Development ManagerSanjeeva Rampure Sr. Applications Engineer

1.3 Reviewers

Name Role Position Document Status Date Reviewed Comments Incorporated

Erreur ! Utilisez l'onglet Accueil pour appliquer Heading 1 au texte que vous souhaitez faire apparaître ici. Oracle Confidential - For internal use only Page ii of xiii

Contents

1. Contents..................................................................................................................ii

1.1 Change Record.........................................................................................................................ii

1.2 Contributors..............................................................................................................................ii

1.3 Reviewers.................................................................................................................................ii

2. Introduction............................................................................................................4

2.1 Scope of the Document............................................................................................................4

3. LE Upgrade – All countries..................................................................................5

3.1 Upgrade Overview....................................................................................................................5

3.2 Trouble Shooting Upgrade Failure...........................................................................................5

3.2.1 Missing Legal Entities....................................................................................................53.2.2 Missing Location............................................................................................................63.2.3 Missing Country.............................................................................................................73.2.4 HR Country Code does not match with HZ Country Code............................................8

4. LE Upgrade – Global...........................................................................................10

4.1 Upgrade Overview..................................................................................................................10

4.2 Trouble Shooting Upgrade Failure.........................................................................................10

4.2.1 Invalid Location data....................................................................................................104.2.2 Required Segment on the Location Descriptive Flexfield...........................................10

5. LE Upgrade – Additional Action Items.............................................................12

5.1 Generic Post Upgrade Datafix................................................................................................12

5.2 Next Upgrade Run from 11i to R12.......................................................................................12

5.3 Impacted Products..................................................................................................................12

6. Open and Closed Issues.......................................................................................13

6.1 Open Issues.............................................................................................................................13

6.2 Closed Issues..........................................................................................................................13

Erreur ! Utilisez l'onglet Accueil pour appliquer Heading 1 au texte que vous souhaitez faire apparaître ici. Oracle Confidential - For internal use only Page iii of xiii

2. Introduction

2.1 Scope of the Document

This document addresses the commonly encountered LE upgrade issues and the steps to identify and fix the problem. The issues listed here are mainly due to customer specific setup data and requires user intervention to resolve the issue.

LE upgrade cannot be fixed to prevent these issues, as these are data specific errors.

Erreur ! Utilisez l'onglet Accueil pour appliquer Heading 1 au texte que vous souhaitez faire apparaître ici. Oracle Confidential - For internal use only of 13

3. LE Upgrade – All countries

3.1 Upgrade Overview

LE upgrade qualifies existing HR organization of type GRE/LEs in 11i as legal entities and migrates them to R12. It creates one main establishment for every legal entity. It also creates identifying registration for every legal entity and the main establishment.

If the LE and its related entities are not migrated or created during upgrade, it leads to problems in Legal Entity Configurator and multiple other products. It is recommended the customer resolve LE upgrade issues before continuing further with the upgrade. Customers must not skip the LE upgrade.

3.2 Trouble Shooting Upgrade Failures

3.2.1 Missing Legal Entities

Run the following query in the upgraded R12 instance:

select hr_legal.organization_id legal_entity_id,

hr_legal.name,

hrl.location_id,

hrl.location_code,

hrl.style,

hrl.legal_address_flag,

hrl.country country

from

(

SELECT O.ORGANIZATION_ID, otl.name

FROM HR_ORG_UNITS_NO_JOIN O,

HR_ALL_ORGANIZATION_UNITS_TL OTL,

HR_ORGANIZATION_INFORMATION O2,

HR_ORGANIZATION_INFORMATION O3

WHERE O.ORGANIZATION_ID = O2.ORGANIZATION_ID

AND O.ORGANIZATION_ID = O3.ORGANIZATION_ID (+)

AND O2.ORG_INFORMATION_CONTEXT||'' = 'CLASS'

AND O3.ORG_INFORMATION_CONTEXT (+) || '' = 'Legal Entity Accounting'

AND O2.ORG_INFORMATION1 = 'HR_LEGAL'

AND O2.ORG_INFORMATION2 = 'Y'

AND O.ORGANIZATION_ID = OTL.ORGANIZATION_ID


AND OTL.LANGUAGE = USERENV('LANG')) hr_legal,

hr_locations_all hrl,

hr_all_organization_units hou

where

hr_legal.organization_id =hou.organization_id

and hou.location_id = hrl.location_id(+)

and hr_legal.organization_id not in ( SELECT

legal_entity_id

from xle_entity_profiles

where created_by =-1);

This query lists all the HR organization of type GRE/LEs that have not been migrated to R12 as Legal Entities. Each row represents the missing Legal Entity and related HR location information.

3.2.2 Missing Location

If there is no location_id for the Legal Entity in the “Missing Legal Entities “ query results above, the LE will not be migrated. A LE must have a location to be considered for migration.

Solution

Associate a Location to the GRE/LE that was not migrated in upgraded R12 instance.

Navigation

(a) Responsibility -> Human resources

(b) Click on Workstructures--> Description

(c) Query the organization

(d) Attach a location from the LOV on the Location field

Example

Figure 1: Missing Location

In the above example, a valid location must be attached to Vision Russia.


3.2.3 Missing Country

If there is no country in the “Missing Legal Entities “ query results above, the LE will not be migrated. A LE must have a country to be considered for migration.

Solution

Associate a country to thelocation associated to the GRE/LE that was not migrated in upgraded R12 instance.

Navigation


(b) Click on Workstructures--> Location

(c) Query the Location with a “Location Code” value from the results set of “Missing Legal Entities”

(d) Update the country for the location, based on the value returned from the query below.

selecthzg.country_code from hz_geographies hzgwhere hzg.geography_name = <country name for your location>and hzg.geography_type ='COUNTRY';

(e) Save the location (or)

(f) If the legal_address_flag in the “ Missing Legal Entities “ query results is 'Y', the update cannot be done thru the UI (navigation steps provided above). The update statement below has to be run in the upgraded R12 instance.

update hr_locations_all hrlset hrl.country =( selecthzg.country_code from hz_geographies hzgwhere hzg.geography_name = <country name for your location>and hzg.geography_type ='COUNTRY')where location_id = < location_id from for missing legal entity>

COMMIT;

Example


In the above example, the HR location Johannesburg attached to Vision South Africa does not have Country information. Location Johannesburg should be updated with Country ‘ZA’ for Vision South Africa.

3.2.4 HR Country Code does not match with HZ Country Code

If the LE upgrade fails to migrate LE’s, even if there is a valid location or country, the cause most likely is that the HR ccountry does not match up with the HZ country code.

Solution

Associate a valid country to the location associated to the GRE/LE that was not migrated in upgraded R12 instance.

Navigation


(b) Click on Workstructures--> Location

(c) Query the Location with a “Location Code” value from the results set of “Missing Legal Entities”

(d) Execute the query:

selecthzg.country_code from hz_geographies hzgwhere hzg.geography_name = <country name for your location>and hzg.geography_type ='COUNTRY';

(e) Compare the country_code returned in step d, with the value found in step c, if they are different the LE would not be migrated.

(f) Update the country for the location, based on the value returned in step d.

(g) Save the location (or)

(h) If the legal_address_flag in the “ Missing Legal Entities “ query results is 'Y', the update cannot be done thru the UI (navigation steps provided above). The update statement below has to be run in the upgraded R12 instance.

update hr_locations_all hrlset hrl.country =( selecthzg.country_code from hz_geographies hzgwhere hzg.geography_name = <country name for your location>and hzg.geography_type ='COUNTRY')where location_id = < location_id from for missing legal entity>

COMMIT;

Example

HR country for Vision Saudi Arabia


HZ country for Saudi Arabia

The HR country for Location attached to Vision Saudi Arabia is ‘Saudi’. The HZ country for Saudi Arabia is ‘SA’. Location HR-Riyadh has to be updated with ‘SA’ as the country for Vision Saudi Arabia to be migrated.


4. LE Upgrade – Global

4.1 Upgrade Overview

Brazil – Brazilian companies are migrated as establishments.

Belgium – The VAT reporters defined in the “Define VAT Reporters” form will be migrated as legal Entities

4.2 Trouble Shooting Upgrade Failure

4.2.1 Invalid Location data

If there is invalid location data in the Brazil or Belgium tables, then the location and Legal Entity cannot be migrated.

Solution

Correct the invalid location data in the Belgium reporting entities and the Brazilian company Information tables.

Navigation - Brazil

(a) Responsibility -> Brazilain Localizations

(b) Click on Localizations --> Company Information Define

(c) Check the address fields for all companies.

(d) Update with the correct information.

Navigation - Belgium

(a) Responsibility -> Belgian Localizations

(b) Click on Belgian Localizations --> VAT Reporters

(c) Check the address fields for all reporters.

(d) Update with the correct information.

4.2.2 Required Segment on the Location Descriptive Flexfield

If there is a required segment on the location descriptive flexfield, then the location and Brazilain or Belgium Legal Entities or Establishments cannot be migrated.

Solution


Correct the invalid location data in the Belgium reporting entities and the Brazilian company Information tables.

Navigation

(a) Responsibility -> System Administrator

(b) Click on Application --> Flexfield Descriptive

(c) Query for title “Additional Location Details” and applcation “Human Resources”

(d) If the Descriptive flexfield is setup with any required segments, set it to “Not required”

(e) Rerun the generic datafix or the upgrade

(f) Afer upgrade, set the segment to required in your R12 instance.


5. LE Upgrade – Additional Action Items

5.1 Generic Post Upgrade Datafix

If you performed any of the action items mentioned in section 3 or 4, you must rerun the generic LE upgrade datafix 7629745:R12.XLE.A(For 12.0.X environments) and 8983728:R12.XLE.B (For 12.1.X environments) to migrate the missing Legal Entities.

It is not required to rerun the whole upgrade, if the LE upgrade failed. The generic datafix will assist you in migrating the missed Legal Entities.

5.2 Next Upgrade Run from 11i to R12

If you have plans for additional upgrade tests, it is is a must you fix your data in the 11i instance. This will ensure Legal Entities are migrated successfully and other dependant products refer to the right Legal Entities.

This will prevent you from requiring running data fix scripts from other products like Cash Management, as the referring LE is wrong.

5.3 Impacted Products

If the LE upgrade failed to migrate Legal Entities successfully and you are using Cash Management or Intercompany, you must work with the corressponding products to the get the datafix.

Cash Management – Generic Data Fix Script –In Progress


http://aru.us.oracle.com:8000/ARU/ViewCheckin/process_form?bug=8983728:R12.XLE.B&release=1500

http://aru.us.oracle.com:8000/ARU/ViewCheckin/process_form?bug=7629745:R12.XLE.A&release=1500

6. Open and Closed Issues

6.1 Open Issues

Number Description Date Raised Priority Owner Action Target Date

1.

2.

3.

Priority: H= High; M=Medium, L=Low

6.2 Closed Issues

Number Description Date Raised Priority Owner Resolution Date Closed

Priority: H= High; M=Medium, L=Low


legal entities upgrade troubleshooting

Documents