Replace the bold lookup value description variable with a Replace the bold language code values with the actual language code. Replace the bold lookup value type variable with the type of lookup Replace the bold industry code variable with the lookup valu

Working with Project Lifecycle Workbench 2-3 To add your own lookup values: 1. Run an SQL statement, as shown in Example 2–1 , to insert the required lookup value into the AIA_LOOKUPS_B table. Example 2–1 SQL Statement Used to Insert Lookup Values into AIA_LOOKUPS_B INSERT INTO AIA_LOOKUPS_B LOOKUP_TYPE, LOOKUP_CODE, PARENT_LOOKUP_CODE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_ VERSION_NUMBER SELECT lookup value type, lookup value code, null, SYS_CONTEXTUSERENV, AUTHENTICATED_IDENTITY, sysdate, SYS_CONTEXT USERENV, AUTHENTICATED_IDENTITY, sysdate, 1 FROM DUAL WHERE NOT EXISTS SELECT 1 FROM AIA_LOOKUPS_B WHERE LOOKUP_TYPE = lookup value type AND LOOKUP_CODE = lookup value code;

a. Replace the bold lookup value type variable with the type of lookup

code that you want to use: INDUSTRY, PROJECT_STATUS, SERVICE_TYPE, TASK_SCOPE, or PRODUCT_CODE.

b. Replace the bold lookup value code variable with the lookup value

code that you want to add. This value has a 30-character limit. 2. Run an SQL statement, as shown in Example 2–2 , to insert the required lookup value code, meaning, and description into the AIA_LOOKUPS_TL table. After running this SQL statement, a message displays to notify you of the number of rows that were created. If this value is correct, enter commit. Example 2–2 SQL Statement Used to Insert Lookup Values into AIA_LOOKUPS_TL INSERT INTO AIA_LOOKUPS_TL LOOKUP_TYPE, LOOKUP_CODE, MEANING, DESCRIPTION, LANGUAGE, SOURCE_LANG, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE _DATE, OBJECT_VERSION_NUMBER SELECT lookup value type, lookup value code, lookup value in UI, lookup value description, SYS_CONTEXT USERENV, LANG, SYS_CONTEXTUSERENV, LANG, SYS_CONTEXTUSERENV, AUTHENTICATED_IDENTITY, sysdate, SYS_CONTEXTUSERENV, AUTHENTICATED_ IDENTITY, sysdate, 1 FROM DUAL WHERE NOT EXISTS SELECT 1 FROM AIA_LOOKUPS_TL WHERE LOOKUP_TYPE = lookup value type AND LOOKUP_CODE = lookup value code;

a. Replace the bold lookup value type variable with the type of lookup

code that you used in step 1.

b. Replace the bold lookup value code variable with the lookup value

code that you added in step 1. This value has a 30-character limit.

c. Replace the bold lookup value in UI variable with the actual lookup

value that you want to appear in the UI. This value has an 80-character limit.

d. Replace the bold lookup value description variable with a

description of the lookup value. This is optional. This value has a 240-character limit. 3. Project Lifecycle Workbench lookup values are configured with the following language settings: LANGUAGE = US and SOURCE_LANG = US. By default, an 2-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack AIA Installer-based Foundation Pack installation will have the supporting US language installed. If your implementation uses a value other than LANGUAGE = US, you must run an SQL statement, as shown in Example 2–3 , to populate the AIA_LOOKUPS_TL table with the internationalized text for the lookup value that you added in step 2. Example 2–3 SQL Statement to Insert Internationalized Text for Lookup Values into AIA_ LOOKUPS_TL INSERT INTO AIA_LOOKUPS_TL LOOKUP_TYPE, LOOKUP_CODE, MEANING, DESCRIPTION, LANGUAGE, SOURCE_LANG, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_ DATE, OBJECT_VERSION_NUMBER SELECT lookup value type, industry code, industry lookup value in UI, industry description, language code , US, SYS_CONTEXTUSERENV , AUTHENTICATED_IDENTITY, sysdate, SYS_CONTEXTUSERENV, AUTHENTICATED_ IDENTITY, sysdate, 1 FROM DUAL WHERE NOT EXISTS SELECT 1 FROM AIA_LOOKUPS_TL WHERE LOOKUP_TYPE = lookup value type’ AND LANGUAGE = language code AND LOOKUP_CODE = industry code;

a. Replace the bold language code values with the actual language code.

For more information, see Setting Up a Globalization Support Environment in Oracle Database Globalization Support Guide.

b. Replace the bold lookup value type variable with the type of lookup

code that you used in step 1.

c. Replace the bold industry code variable with the lookup value code that

you added in step 1. This value has a 30-character limit.

d. Replace the bold industry lookup value in UI variable with the