1 prepare the environments.… · 1 prepare the environments ... custom application of oracle ......

1 Prepare the environments

1.1 Edit the Environment User Data A. Open workbench of PPM

B. Go to Sys Admin> User Data

C. List User Data

D. Double click Environment User Data

E. Add field "Oracle EBS version (if installed)"

i. The token must be ORACLE_EBS_VERSION

ii. Set the default value

F. Add field "Oracle EBS root folder environment file (12.2)", the token must be

ROOT_FOLDER_ENV_FILE_122

G. Add field "Oracle EBS Apps environment file (Version<12.2)", the token must be

APPS_ENV_FILE

H. Add field "Oracle EBS DB environment file (Version<12.2)", the token must be

DB_ENV_FILE

I. Adjust the layout of the fields (Optional)

1.2 Modify your environment in workbench of PPM

If your environment represents an EBS instance, you need to setup the Environment User Data,

otherwise there is nothing you need to do.

Go to Sys Admin > Environments, list the environment

Double click the environment you want to modify.

There is a difference about the setting of the Environment User Data between EBS 12.2 (or

higher) and old EBS version prior to 12.2.

1.2.1 EBS 12.2 or higher

Oracle E-Business Suite Release 12.2.2 and higher includes a script to set the run or patch

edition environment by name. The script is called "EBSapps.env" and is found in the root

directory of an Oracle E-Business Suite application-tier installation.

HP recommend you to upgrade your EBS 12.2 instance to 12.2.2 or higher.

If your environment represents an Oracle EBS instance of 12.2 (12.2.2 is the minimal version) or

higher, please select "12.2 or higher" value for Oracle EBS version (if installed) field. For Oracle

EBS root folder environment file (12.2) field, please input the full path of the script

"EBSapps.env". In the following screenshot, the path for example is

/u01/oracle/VIS/EBSapps.env.

1.2.2 Old EBS version prior to 12.2

If your environment represents an old Oracle EBS instance prior to 12.2, please select "Lower

than 12.2" value for Oracle EBS version (if installed) field.

Please input the full path of the Apps environment file into Oracle EBS Apps environment file

(Version<12.2) field. In the following screenshot, the path for example is

/media/oracle/VIS/apps/apps_st/appl/APPSVIS_ppmqavm78.env.

Please input the full path of the DB environment file into Oracle EBS DB environment file

(Version<12.2) field. In the following screenshot, the path for example is

/media/oracle/VIS/db/tech_st/11.1.0/VIS_ppmqavm78.env.

2 Import the exemplary workflows/special commands/ojbect

types For example, the PPM home is M:\CPE-Instances\9.30_GA and the data files are saved in the

M:\CPE-Instances\9.30_GA\transfers folder, the password of admin user is admblabla, you can

open a command line and change directory to M:\CPE-Instances\9.30_GA\bin, run the

following commands to import them:

sh ./kMigratorImport.sh -username admin -action import -password admblabla -filename

'M:\CPE-Instances\9.30_GA\transfers\bak' -i18n charset -refdata nochange -flags

NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\ENV_001_EBS_FileServer.zip' -i18n charset -refdata

nochange -flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\ENV_002_EBS_PPMQAVM78.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\ENV_003_EBS_PPMPCOE05.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\ENV_004_EBS_PPMQAVM36.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\OT_002_EBS_FILE.zip' -i18n charset -refdata nochange

-flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\OT_003_EBS_SQL.zip' -i18n charset -refdata nochange

-flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\OT_008_EBS_AOL_DATA_UPLOAD.zip' -i18n charset -

refdata nochange -flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\OT_009_EBS_AOL_DATA_DOWNLOAD.zip' -i18n charset -



'M:\CPE-Instances\9.30_GA\transfers\SP_sc_oracle_ebs_source_and_check_dest_server.zip' -

i18n charset -refdata nochange -flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\SP_sc_oracle_ebs_source_dest_server.zip' -i18n

charset -refdata nochange -flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\SP_sc_oracle_ebs_source_source_server.zip' -i18n

charset -refdata nochange -flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\UD_ENVIRONMENT_USER_DATA.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\VAL_001_EBS_VERSION.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\VAL_002_EBS_EDITION_TYPE.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\VAL_003_EBS_SQLERROR_EXIT.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\VAL_007_EBS_APP_SHORT_NAME.zip' -i18n charset -



'M:\CPE-Instances\9.30_GA\transfers\WF_007_EBS_FILE_DEMO_PPMPCOE05.zip' -i18n charset -



'M:\CPE-Instances\9.30_GA\transfers\WF_008_EBS_FILE_DEMO_PPMQAVM36.zip' -i18n charset -



'M:\CPE-Instances\9.30_GA\transfers\WF_009_EBS_AOL_DATA_DOWNLOAD_DEMO.zip' -i18n charset

-refdata nochange -flags NYYNNNNNNYYYNNNNNNN


'M:\CPE-Instances\9.30_GA\transfers\WF_010_EBS_AOL_DATA_UPLOAD_DEMO.zip' -i18n charset -



'M:\CPE-Instances\9.30_GA\transfers\WF_011_EBS_FILE_DEMO_PPMQAVM78.zip' -i18n charset -



'M:\CPE-Instances\9.30_GA\transfers\WF_012_EBS_SQL_PPMPCOE05.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\WF_013_EBS_SQL_PPMQAVM36.zip' -i18n charset -refdata



'M:\CPE-Instances\9.30_GA\transfers\WF_014_EBS_SQL_PPMQAVM78.zip' -i18n charset -refdata


3 About these exemplary objects

3.1 Environments Environment Name Comment

001_EBS_FileServer 001_EBS_FileServer acts as a file server. In production environment, you might use a CVS server or other enterprise version- control system instead. The /media/oracle/data is the base directory of the file server.

002_EBS_PPMQAVM78 002_EBS_PPMQAVM78 reprsents an Oracle EBS instance of 12.1

003_EBS_PPMPCOE05 003_EBS_PPMPCOE05 represents an Oracle EBS instance of 12.2.3, which is in an online patching cycle

004_EBS_PPMQAVM36 004_EBS_PPMQAVM36 represents an Oracle EBS instance of 12.2.3, which is not in an online patching cycle

3.2 Validations Validation Name Comment

001_EBS_VERSION 001_EBS_VERSION is a drop down list of EBS versions, currently it has two values, one is 12.2-, another is 12.2. 12.2- means the EBS version prior to 12.2.

002_EBS_EDITION_TYPE 002_EBS_EDITION_TYPE is a drop down list of EBS edition types, it has two values, one is run, another is patch.

003_EBS_SQLERROR_EXIT 003_EBS_SQLERROR_EXIT is a drop down list which is used as the error handling option of SQL script execution.

007_EBS_APP_SHORT_NAME 007_EBS_APP_SHORT_NAME is a drop down list for Oracle

application short name. This short name will be used to locate the top directory of the specified application. For example, CLM is the short name of HP Object Migrator which is a custom application of Oracle EBS, $CLM_TOP will point to the top directory of HP Object Migrator in the Oracle EBS file system.

008_EBS_FNDLOAD_AOL_TYPE 008_EBS_FNDLOAD_AOL_TYPE is a drop down list that encodes all the necessary information which is used to execute FNDLOAD utility of Oracle EBS. Currently it has only two values, one is Messages, another is Value set. You can extend this drop down list in order to support more object types.

3.3 Special commands Special Command Name Comment

sc_oracle_ebs_source_and_check_dest_server Source the environment of destination EBS instance and check the online patching cycle for EBS 12.2 if the target edition type is patch. After this SP is executed, the following commands can detect the temporary variable P_DEST_IS_VALID.

sc_oracle_ebs_source_dest_server Source the environment of destination EBS instance.

sc_oracle_ebs_source_source_server Source the environment of source EBS instance.

3.4 Object Types Object Type Name Comment

002_EBS_FILE Copy a file from file server and deploy it to the target EBS instance regardless of the EBS version.

A. If the target EBS instance is 12.2- (old version prior to 12.2), the file will be deployed to the appropriate directory specified by the parameters of the object type.

B. If the target EBS instance is 12.2 and the target

edition type is run, the file will be deployed to the patch edition in addition to the run edition automatically.

C. If the target EBS instance is 12.2 and the target

edition type is patch, the patch edition should be available. In other words, if the target EBS instance is not in an online patching cycle, a warning

message will be displayed and the file deployment will be canceled. If all prerequisite conditions meet, the file will be deployed to the patch edition and the entry of this file will be added to the custom synchronization driver file located at $APPL_TOP_NE/ad/custom/adop_sync.drv automatically. The adop utility of Oracle EBS will use the driver file to synchronize files between the run file system and the patch file system later.

003_EBS_SQL Execute a SQL script on the target EBS instance A. If the target EBS instance is 12.2- (old version prior

to 12.2), the SQL script will be executed directly.

B. If the target EBS instance is 12.2 and the target edition type is run, the script will be executed from the run edition of the database.


edition type is patch, the patch edition should be available. In other words, if the target EBS instance is not in an online patching cycle, a warning message will be displayed and the script execution will be canceled. If all prerequisite conditions meet, the script will be executed from the patch edition of the database.

008_EBS_AOL_DATA_UPLOAD From file server, copy a data file downloaded by the FNDLOAD utility to the target EBS server, then run FNDLOAD utility to upload the data file to the target EBS instance.

A. If the target EBS instance is 12.2- (old version prior to 12.2), the FNDLOAD utility will be run as normal.

B. If the target EBS instance is 12.2 and the target

edition type is run, the FNDLOAD utility will be run from the run edition.


edition type is patch, the patch edition should be available. In other words, if the target EBS instance is not in an online patching cycle, a warning message will be displayed and the upload will be canceled. If all prerequisite conditions meet, the FNDLOAD utility will be run from the patch edition.

009_EBS_AOL_DATA_DOWNLOAD From source EBS server, run FNDLOAD utility of Oracle EBS to download an object of Value Set or Messages to a data

file which filename extension is usually ldt, then copy the data file to the file server.

A. If the source EBS instance is 12.2- (old version prior to 12.2), the FNDLOAD utility will be run as normal.

B. If the source EBS instance is 12.2, the FNDLOAD

utility will be always run from the run edition no matter whether the source EBS instance is in an online patching cycle or not.

4 Demo scenarios

Workflow Used Object Type Used

Demo File Scenario Description

007_EBS_FILE_DEMO_PPMPCOE05

002_EBS_FILE

DEP_FILE_RUN.wrf Deploy a file to the run edition of an EBS instance

008_EBS_FILE_DEMO_PPMQAVM36

002_EBS_FILE

DEP_FILE_PATCH_1.wrf Deploy a file to the patch edition of an EBS instance which is not in an online patching cycle

007_EBS_FILE_DEMO_PPMPCOE05

002_EBS_FILE

DEP_FILE_PATCH_2.wrf Deploy a file to the patch edition of an EBS instance which is in an online patching cycle

012_EBS_SQL_PPMPCOE05

003_EBS_SQL

RUN_SQL_RUN.wrf Run SQL script from the run edition of the EBS instance

013_EBS_SQL_PPMQAVM36

003_EBS_SQL

RUN_SQL_PATCH_1.wrf Run SQL script from the patch edition of the EBS instance which is not in an online patching cycle

012_EBS_SQL_PPMPCOE05

003_EBS_SQL

RUN_SQL_PATCH_2.wrf Run SQL script from the patch edition of the EBS instance which is in an online patching cycle

014_EBS_SQL_PPMQAVM78

003_EBS_SQL

RUN_SQL_12.1.wrf Run SQL script on an EBS 12.1 instance

009_EBS_AOL_DATA_DOWNLOAD_DEMO

009_EBS_AOL_DATA_DOWNLOAD

FND_DOWNLOAD_VS.wrf

Run FNDLOAD to download an object of Value Set

010_EBS_AOL_DATA_UPLOAD_DEMO

008_EBS_AOL_DATA_UPLOAD

FND_UPLOAD_VS_1.wrf Run FNDLOAD to upload a data file to the run edition of the target EBS instance

010_EBS_AOL_DATA_UPLOAD_DEMO

008_EBS_AOL_DATA_UPLOAD

FND_UPLOAD_VS_2.wrf Run FNDLOAD to upload a data file to the patch edition of the target EBS instance which is not in an online patching cycle

011_EBS_FILE_DEMO_PPMQAVM78

002_EBS_FILE

DEP_FILE_12.1.wrf Deploy a file to an EBS instance of EBS 12.1

The following chapters are the detailed information about these demos.

4.1 DEP_FILE_RUN.wrf

4.1.1 Parameters

Base directory of file server: /media/oracle/data

4.1.2 Check points

1. Whether the file is deployed to the run edition (Yes)

2. Whether the file is deployed to the patch edition automatically (Yes)

4.2 DEP_FILE_PATCH_1.wrf

4.2.1 Pre check points

1. PPMQAVM36 is not in an online patching cycle (Yes)

4.2.2 Parameters

4.2.3 Check points

1. Whether a warning message is shown (Yes)

2. Whether the deployment to patch edition will be canceled (Yes)

4.3 DEP_FILE_PATCH_2.wrf


1. PPMPCOE05 is in an online patching cycle (Yes)

2. Check content of the adop_sync.drv

4.3.2 Parameters

One package line deploys one file, we create three package lines in the package, totally deploy

three files:

o CLMRMCP1.debug.rdf

o CLMRDPG1.debug.rdf

o CLMRDVW1.debug.rdf

4.3.3 Check points

1. Check whether the three files will be deployed into the patch edition file system (yes)

2. Check the run edition file system by the way (no files have been deployed to run edition

file system)

3. Check whether the adop_sync.drv will be changed (Yes)

mkdir -p %s_other_base%/EBSapps/appl/clm/12.0.0/reports/US

cp %s_current_base%/EBSapps/appl/clm/12.0.0/reports/US/CLMRDVW1.debug.rdf %s_other_base%/EBSapps/appl/clm/12.0.0/rep

orts/US/CLMRDVW1.debug.rdf


cp %s_current_base%/EBSapps/appl/clm/12.0.0/reports/US/CLMRDPG1.debug.rdf %s_other_base%/EBSapps/appl/clm/12.0.0/repo

rts/US/CLMRDPG1.debug.rdf


cp %s_current_base%/EBSapps/appl/clm/12.0.0/reports/US/CLMRMCP1.debug.rdf %s_other_base%/EBSapps/appl/clm/12.0.0/repo

rts/US/CLMRMCP1.debug.rdf

4.4 RUN_SQL_RUN.wrf

4.4.1 Parameters

4.4.2 Check points

1. Whether the table PPM_DPM_DEMO_CUSTOMER has been created on the run edition

of the database (Yes)

4.5 RUN_SQL_PATCH_1.wrf


1. PPMQAVM36 is not in an online patching cycle (Yes)

4.5.2 Parameters

4.5.3 Check points

1. Whether a warning message is shown (Yes)

2. Whether the SQL script execution from the patch edition database will be canceled (The

patch edition database doesn’t exist at all!)

4.6 RUN_SQL_PATCH_2.wrf


1. PPMQAVM05 is in an online patching cycle (Yes)

4.6.2 Parameters

4.6.3 Check points

1. Whether the procedure PPM_DPM_DEMO_PROCEDURE1 will be created in the patch

edition database (Yes)

2. Whether the procedure PPM_DPM_DEMO_PROCEDURE1 will be available in the run

edition database. (As we expect, we cannot see it from the run edition database)

4.7 RUN_SQL_12.1.wrf

4.7.1 Parameters

The Edition Type of Target EBS parameter doesn’t take effect if the target EBS instance is 12.1,

you can ignore it.

4.7.2 Check points

1. Whether the procedure PPM_DPM_DEMO_PROCEDURE2 will be created in the EBS 12.1

database (Yes)

2. Whether the DpM object type 003_EBS_SQL is compatible with both EBS 12.2 and EBS

12.1 (Yes)

4.8 FND_DOWNLOAD_VS.wrf


1. Check the Value Set PPM_DPM_DEMO_VS_CITY on EBS 12.2 instance PPMPCOE05

2. Check the Message PPM_DPM_DEMO_MSG_HELLOWORLD on EBS 12.2 instance

PPMPCOE05

4.8.2 Parameters

The first package line will download the value set PPM_DPM_DEMO_VS_CITY, the second

package line will download the message PPM_DPM_DEMO_MSG_HELLOWORLD. The data file

will be saved in AOL_download directory of the file server. For PPM_DPM_DEMO_VS_CITY, you

need not specify the Application Short Name parameter, but for

PPM_DPM_DEMO_MSG_HELLOWORLD, you must specify it.

4.8.3 Check points

1. Check the new generated data file PPM_DPM_DEMO_VS_CITY.v1.ldt (looks fine)

2. Check the new generated data file PPM_DPM_DEMO_MSG_HELLOWORLD.v1.ldt (looks

fine)

4.9 FND_UPLOAD_VS_1.wrf


1. Check whether the Value Set PPM_DPM_DEMO_VS_CITY exists on EBS 12.2 instance

PPMQAVM36 (No)

4.9.2 Parameters

4.9.3 Check points

1. Check whether the PPM_DPM_DEMO_VS_CITY will be created on EBS 12.2 instance

PPMQAVM36 (Yes)

4.10 FND_UPLOAD_VS_2.wrf


1. Check whether EBS 12.2 instance PPMQAVM36 is in an online patching cycle (No)

4.10.2 Parameters

4.10.3 Check points

1. Check whether an warning message is shown (Yes)

2. Check whether the message will be created on EBS 12.2 instance PPMQAVM36 (No)

4.11 DEP_FILE_12.1.wrf


1. Check there is no file CLMRMVS1.debug.rdf under the specified path of the EBS 12.1

instance PPMQAVM78 (Yes)

4.11.2 Parameters

If the target EBS instance is 12.1, the parameter Edition Type of Target EBS will not take effect,

you can just ignore this parameter.

Base directory of file server: /media/oracle/data

4.11.3 Check points

1. Whether the file is deployed to the specified path of the EBS 12.1 instance PPMQAVM78

(Yes)

2. Whether the DpM object type 002_EBS_FILE is compatible with both EBS 12.1 and 12.2

(Yes)

5 Tricky points You might notice we use the same URL to open the web UI of PPMPCOE05 (16.186.74.75) and

PPMQAVM36 (16.186.76.75) which are all EBS 12.2 instance. It is true. PPMQAVM36 has been

cloned from PPMPCOE05, we have not changed the server name.

On the client, we change C:\Windows\System32\drivers\etc\hosts to make PPMPCOE05 point

to the IP address that we want to connect.

#16.186.74.75 ppmpcoe05.asiapacific.hpqcorp.net ppmpcoe05

16.186.76.75 ppmpcoe05.asiapacific.hpqcorp.net ppmpcoe05

1 prepare the environments.… · 1 prepare the environments ... custom application of oracle ......

Documents