Archives

Authors

Archive for the ‘Application 11i.x/12.x Patches’ Category

The primary goal of post install stpes is to deliver seeded data. Seeded data consists of deduction and earnings elements, formulas, jurisdiction code information, balances, balance classifications, etc. Without this you will miss basic entities such as the ‘Regular Salary’ and ‘Regular Wages’ elements.

To enable Country Legislation you need to register the country specific driver in your application. Once you have successfully installed Oracle E-Business Suite 12.1.1, you need register the legislation using following command.

DataInstall for hrglobal

$ java oracle.apps.per.DataInstall apps apps thin macaw:1553:uat

+————————————————-+

| DataInstall Main Menu |

+————————————————-+

1. Select legislative data to install/upgrade

2. Select college data to install/upgrade

3. Select JIT or OTL to install/upgrade

4. Exit to confirmation menu

Enter your choice : 1

# Localisation Product(s) Leg. Data? Action

— ——————- ———————— ———- ————-

1 Global Human Resources Install

………….

………….

42 Saudi Arabia Human Resources

43 Saudi Arabia Payroll

……

……

…….

57 United States Payroll

58 United States US Federal Human Resources

<Product #><Action> – Change Action

where <Action> is [I : Install, C : Clear]

[Return] – To return to main menu.

Enter your choice (for example 2I) : 42I

# Localisation Product(s) Leg. Data? Action

— ——————- ———————— ———- ————-

42 Saudi Arabia Human Resources Install

43 Saudi Arabia Payroll

<Product #><Action> – Change Action

where <Action> is [I : Install, C : Clear]

[Return] – To return to main menu.

Enter your choice (for example 2I) : 43I

42 Saudi Arabia Human Resources Install

43 Saudi Arabia Payroll Install

<Product #><Action> – Change Action

where <Action> is [I : Install, C : Clear]

[Return] – To return to main menu.

Enter your choice (for example 2I) :

+————————————————-+

| DataInstall Main Menu |

+————————————————-+

1. Select legislative data to install/upgrade

2. Select college data to install/upgrade

3. Select JIT or OTL to install/upgrade

4. Exit to confirmation menu

Enter your choice : 4

DataInstall – Actions confirmation

Do you really wish to exit and save your changes?

[Y] – Yes, save then exit

[N] – No, don’t save but exit

[Return] – To return to the DataInstall Main Menu

Enter your choice (for example Y) : Y

Install the Global legislation driver – hrglobal.drv

hrglobal.drv is the single source for installing and delivering the seeded legislative data. All legislation data is included in hrglobal.drv. However, hrglobal will only install what was selected from datainstall.

Set the Application Enviornment $APPL_TOP/APPS<Context_Name>.env

Apply $PER_TOP/patch/115/driver/hrglobal.drv to the database tier. Be mindful to only run the driver located in this directory..
hrglobal.drv driver should be applied as per a normal patch using the adpatch utility.

Once completed you have successfully installed your legislative HRMS data.

Confirm the forms from HR consultant after successfully apply the hrglobal driver.

From within SQL*Plus, logged in as APPS, run the following:
select STATUS
from fnd_product_installations
where APPLICATION_ID = 278;

This statement should return one row:
S
–
I
6. Set the IZU top in the evniornment file, echo and check the patch
7. Apply 3636980
8. Check the log files

9. Remove standalone RDA if installed into $IZU_TOP/bin/rda
If you have previously installed RDA into the $IZU_TOP/bin/rda directory
by manually extracting it from a zip or tar file, you should remove the rda
directory and its contents from under $IZU_TOP/bin before applying the patch
unified driver.

As an DBA you need to apply patches during implementation or support as when required by functional team or technical team or even application object library patches. You need to keep track of patches that have been applied, in this case you need to prepare patch register which will enable you to check for applied patches as on date. Below is the sample patch register. We will not be responsible for any patch failure or any impact on your current application what so ever.

Once you have successfully applied Oracle Applications Technology Updates for 11i.ATG_PF.H.delta.5 (RUP5), you must complete these additional steps. If you completed a task during a previous 11i patch application, then you do not need to complete the step again, unless otherwise instructed.

This step applies only to those E-Business Suite deployments that are integrated with Oracle Application Server 10g (Single Sign-On and Oracle Internet Directory). If the E-Business Suite deployment is not integrated with Oracle Application Server 10g, you can skip this step.

Do not apply this patch if you want to retain your existing Oracle Login Server 3.0.9 and Oracle Portal 3.0.9 integration. This patch includes libraries that are incompatible with Oracle Login Server 3.0.9.

This patch delivers an updated Single Sign-On SDK; you will need to de-register and re-register all your SSO partner applications. Please follow Option 3 under “Appendix C: Advanced Configuration – Manual SSO/OID Registration” in the Installation Guide, Metalink Note 233436.1, to de-register the partner applications first and then re-register them again.

If you are integrating the E-Business Suite deployment with Oracle Application Server 10g for the first time, refer to MetaLink Note 233436.1 for detailed instructions.

Step 4 Run Technology Stack script. (Conditionally Required)

If your environment is SSL-enabled, run the following script (for Technology Stack patch 4029076, included in 11i.ATG_PF.H.delta.5 (RUP5):

Follow the instructions in OracleMetaLink note 271148.1 to configure and apply interoperability patches for Oracle XML Parser for Java v9.0.4.

Step 6 Run AutoConfig. (Required)

Run AutoConfig on the application and database tiers. For instructions on how to run AutoConfig, refer to OracleMetaLink note 165195.1.

Customers using the AutoConfig Customizations feature must merge any customizations with the AutoConfig templates provided via this patch before running AutoConfig.

Step 7 Create APPS_TS_TOOLS Tablespace. (Conditionally Required)

Customers who have migrated to the new Oracle Applications Tablespace Model must create the APPS_TS_TOOLS tablespace, either manually through SQL*Plus or by invoking the Tablespace Migration Utility menu, before running the AD Splicer to introduce a new product schema. For more information, see: Understanding the Tablespace Migration Utility Main Menu, Oracle Applications System Administrator’s Guide – Configuration.

The default initial size for the APPS_TS_TOOLS tablespace is 500 MB, with auto segment management enabled. If you create the APPS_TS_TOOLS tablespace through SQL*Plus, outside of the OATM utility, you can use the following statement:

You can override these storage recommendations with storage parameters to suit the expected size required for objects that will be in the Tools tablespace at your site.

Step 8 Disable Default Users. (Recommended)

Application User

Product/Purpose

ANONYMOUS

FND/AOL

AUTOINSTALL

AD (Application DBA)

CONCURRENT MANAGER

FND/AOL

FEEDER SYSTEM

AD (Application DBA)

INITIAL SETUP

AD (Application DBA)

STANDALONE BATCH PROCESS

FND/AOL

MOBILEADM

Mobile Applications Admin

ASGADM

Field Service/Sales Application Admin

WIZARD

AD (Application DBA)

ASGUEST

Sales Application guest user

IEXADMIN

Internet Expenses

IBE_GUEST

iSupport Guest user – 1

IBE_ADMIN

iSupport Admin user

IBEGUEST

iSupport Guest user – 1

OP_SYSADMIN

OP (Process Manufacturing) Admin User

OP_CUST_CARE_ADMIN

Customer Care Admin for Oracle Provisioning

IRC_EMP_GUEST

iRec Employee Guest Login

IRC_EXT_GUEST

iRecruitment External Guest Login

Step 9 Copy Fonts for Oracle XML Publisher. (Required)

Copy the following font files from $FND_TOP/resource to the /lib/fonts directory (under OA_JRE_TOP and JRE_TOP) on all Web and concurrent nodes. If $FND_TOP/resource does not contain the font files, apply patch 3639533: Albany (Display) Font 4.02 Release.

If you have defined any custom notification mailer service components that are dedicated to process only messages from a particular item type, then you must update the correlation ID value for those notification mailers to continue processing messages. You can set the correlation ID in the Define page of the advanced configuration wizard in Oracle Workflow Manager. For each notification mailer, set the correlation ID to the internal item type name followed by a colon and a percent sign in the following format:

Make sure your system meets the following requirements before you begin the process of applying this minipack.

·Perl executable (5.004 minimum; 5.005 perferred) is set in your PATH before you apply this minipack.

·FNDLOAD executable

Ensure all application tier server nodes contain the FNDLOAD executable in the $FND_TOP/bin directory. If the executable is not present, apply patch 2684116 on all nodes. When applying AD.I.6 (6502082), apply it on all forms/web server nodes first, and then on the administration server node.

Step 2: Verify that you have implemented the apps.zip architectural change (conditionally required)

Unzip apps.zip under $JAVA_TOP on all application tier nodes, if you have not done so already.

Step 3: Convert to Multiple Organizations (Recommended)

Oracle Applications strongly recommends that you convert to Multi-Org as soon as possible so that you will be prepared for improvements to performance across the E-Business Suite as well as support for Multi-Org Access Control.