Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues...

39
Technical Foundation: AOL Users Michael Brown, Colibri Limited [email protected]

Transcript of Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues...

Page 1: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Technical Foundation:AOL Users

Michael Brown, Colibri [email protected]

Page 2: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Agenda• What is the AOL?• Reading an ERD• Finding the Tables• Users and Responsibilities• Profiles• Descriptive Flexfields• Applications DBA - Patches• Useful Applications during Cloning

Page 3: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

What is the AOL?• Application Object Library

– Commonly thought of as FND

– Core set of common tables, applications– Tables belong to APPLSYS

Page 4: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Reading an ERD (eTRM format)

Table A May Have One and only One Table BTable B Must Have One or More Table A

Table A Must Have One and only One Table CTable C Must Have One and only One Table A

Page 5: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Reading an ERD (Presentation)

Table A May Have One and only One Table BTable B Must Have One or More Table A

Table A Must Have One and only One Table CTable C Must Have One and only One Table A

Page 6: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Finding The Tables• Help-> Record History

– http://roswell2.colibriltd.com:8011

Page 7: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 8: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 9: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 10: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 11: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 12: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Finding The Tables• Help -> Record History• eTRM

– http://etrm.oracle.com– Must be logged on to Metalink to access

Page 13: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 14: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 15: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 16: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 17: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 18: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 19: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 20: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 21: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 22: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 23: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 24: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Users and Responsibilities

Page 25: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 26: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Profiles

Page 27: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 28: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 29: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 30: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Descriptive Flexfields• Provide customizable ”expansion

space” on your forms. • Appear as a single–character, unnamed

field enclosed in brackets ([ ])

Page 31: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Descriptive Flexfields

Page 32: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 33: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Patches• Actually part of Applications DBA, not

AOL• Patches should all be recorded in

Database, but enough issues that Oracle no longer checks prerequisites against the database by default

Page 34: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Patches

Page 35: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.
Page 36: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Useful Cloning TrickNote: Actual Profile Option Id values must be

determined for your instance.alter session set nls_date_format='MM/DD/YY HH24:MI';update apps.fnd_profile_option_valuesset profile_option_value=‘IDENTIFIER '||(select

rtrim(ltrim(instance_name)) from v$instance)||' (Cloned from PROD on '||&&SYSDATE||')'

where application_id=0and level_id=10001and profile_option_id=125/

Page 37: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Script (Cont)update fnd_responsibility_tlset responsibility_name='--IDENTIFIER '||(select rtrim(ltrim(instance_name)) from v$instance)||' (Cloned from PROD on '||&&SYSDATE||')'

where responsibility_name like '--%'/update apps.fnd_profile_option_valuesset profile_option_value='TEAL'where application_id=0and level_id=10001and profile_option_id=5785/

Page 38: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Script (Cont)update apps.fnd_profile_option_valuesset profile_option_value='PURPLE'where application_id=0and level_id=10001and profile_option_id=5785and (select rtrim(ltrim(instance_name)) from v$instance)=‘TEST’

/

Note: Actual Profile Option Id values must be determined for your instance.

Page 39: Technical Foundation: AOL Users •Patches should all be recorded in Database, but enough issues that Oracle no longer checks prerequisites against the database by default. Patches.

Questions