appstech material

8/10/2019 Appstech Material

http://slidepdf.com/reader/full/appstech-material 1/59

Define Application Users

Overview

An Application User is an authorized user of the Oracle Applications and/or Self-Service WebApplications (OSSWA). A user is uniquely identified by an application userna e. Use the System

Administrator Responsibility to define users.

Define User

!avi"ate to# Security > User > Define

Tip: Tab through the fields when completing this form and watch the status bar for field specificprompts

User !a e# $nter the na e of an application user. An application user enters thisuserna e to si"n on to Oracle Applications and/or Oracle Self-Service WebApplications. %he follo&in" "uidelines apply to this field#• 'an only be one &ord• efine a standard na in" convention such as first initial last na e.• User na e is al&ays in Upper 'ase• Alphanu eric (*A* throu"h *+*) and !u eric (*,* throu"h * *) are

per itted.escription# $nter a description for this user. $nter a user friendly na e as description

e.". ane oe0.

ote: escription entered is displayed on the user0s OSSWA ho e pa"e



&hen si"nin" on to Self Server Web Applications.

%ip# 1ou ay also enter ht l ta"s in this field to for at ho& the user0sna e is displayed for e2a ple enterin" 3font color45red56 aneoe3/font60 &ill display the user0s na e in red on the OSSWA ho e

pa"e.7ass&ord# $nter the initial pass&ord of an application user. %he user &ill be

pro pted to chan"e this pass&ord the first ti e they si"n in. %hefollo&in" "uidelines apply to this field#• 8ust be at least 9 characters and no ore than :,,.• Alphanu eric (*A* throu"h *+*) and !u eric (*,* throu"h * *) are

per itted.

ote: 1ou &ill need to enter this field t&ice for verification7erson# ;f this user is an e ployee select the e ployee*s full na e fro the <O=.'usto er# ;f this user is a custo er select the custo er*s na e fro the <O=.Supplier# ;f this user is a supplier select the supplier*s na e fro the <O=.$-8ail# Optionally enter the e ail address for this user.>a2# Optionally enter the fa2 nu ber for this user.7ass&ord $2piration6ays#

8a2i u nu ber of days bet&een pass&ord chan"es.

7ass&ord $2piration6Accesses#

8a2i u allo&ed nu ber of si"n-ons to Oracle Applications or Self-Service Web Applications allo&ed bet&een pass&ord chan"es.

7ass&ord $2piration6 !one#

Select none if you do not &ish to have pass&ords e2pire by nu ber ofdays or accesses.

$ffective ates6>ro # Optionally enter a start date &hen this user can be"in accessin" theapplications.

$ffective ates6%o# Optionally enter an end date &hen this user can no lon"er access theapplications.

?esponsibility# Select a responsibility you &ish to assi"n this user.

ote: ;n order for a user to access the applications they ust be assi"nedat least one responsibility. Once a user is assi"ned to a responsibility itcannot be deleted therefore you ust deactivate the responsibility byenterin" an end date. ;f you &ant to reactivate a deactivated responsibilityfor a user chan"e the end date to a date after the current date or hi"hli"htthe current end date and delete.

?esponsibility6$ffective ates6>ro #

Optionally enter a start date &hen this user can be"in accessin" theapplications &ith this responsibility.

?esponsibility6

$ffective ates6%o#

Optionally enter an end date &hen this user can no lon"er access the

applications &ith this responsibility.

Securing AttributesSecurin" Attributes are used by the Oracle Self-Service Web Applications. Securin" Attributes allo&ro&s of data to be visible to specified users or responsibilities based on the values contained in the ro&.Securin" Attributes ust be assi"ned at both the user and responsibility level.

!"ample: ;f you &ant to restrict the user ane &ith responsibility of *Ad in* to see only those ro&s&here custo er@id 4 :,,, then assi"n the securin" attribute #$%&$USTO'!R&#D to the



responsibility *Ad in* then the securin" attribute #$%&$USTO'!R&#D and value of ())) to the userane.

avigate to: Security > User > DefineSelect: Securing Attributes

Securin" Attributes6

Attributes#

Select an attribute fro the <O= to be used to deter ine &hich records

this user can access.Securin" Attributes6Application#

Oracle Self-Service Web Application

Securin" Attributes6=alue#

$nter the value to be used to deter ine &hich specific ro&s of records thisuser can access.

!"cluding Attributes$2cludin" Attributes are used by the Oracle Self-Service Web Applications and are defined at theresponsibility level. 7lease refer to the AO* Application Responsibilities Training+doc

ote: Once assi"ned a responsibility a user is e2cluded fro any colu ns defined as e2cludin"attributes for that responsibility.

Responsibilities

A responsibility is a level of authority that deter ines the specific data users can access and the specificenu they see. $ach application user ust be assi"ned to at least one responsibility and several userscan share several responsibilities. ?esponsibilities cannot be deleted. Use the $ffective ates6%o0 fieldto disable a responsibility. Use the System Administrator Responsibility to define responsibilities.



Define Responsibility

!avi"ate to# Security>Responsibility>Define

?esponsibility !a e# $nter an intuitive unique na e for the responsibility you are definin".Application# Select the na e of the application you &ish to associate &ith theresponsibility fro the <O=.

ote: %his na e does not preclude the user of this responsibility froaccessin" other applications0 for s and functions if they are defined in theresponsibility0s enu.

?esponsibility ey# $nter a unique na e for this responsibility to be used by loader pro"ra s.escription# $nter a user-friendly description for the responsibility$ffective ates6>ro # $nter the start date on &hich this responsibility beco es active.$ffective ates6%o# Optionally enter the end date on &hich this responsibility beco es inactive.

ote: ?esponsibilities cannot be deleted. Use this field to de-activate aresponsibility.

Available >ro # A responsibility can be ade available to the user fro either the OracleApplications or the Oracle Self Service Web Application but not both.Select &hich application syste this responsibility &ill be available fro .

ata Broup6 !a e# $nter the O?A'<$ userna e usually *Standard*. %he O?A'<$ userna edeter ines the database tables and table privile"es accessible to theresponsibility so if usin" so ethin" other than *Standard* please bee2tre ely cautious.

ata Broup6 >ro the <O= select the application &hose O?A'<$ userna e for s



Application# connect to &hen you choose this responsibility.8enu# Select a enu that has been defined fro the <O=.Web Cost !a e# ;f your &eb server resides on a different achine fro your database you

ust enter the host na e (U?<) here.Web A"ent !a e# Optionally enter the 7</SD< A"ent !a e for the database used by this

responsibility. ;f unspecified the a"ent na e defaults to the a"ent na ecurrent at lo"-on.

?equest Broup6 !a e/Application#

Assi"n a request security "roup fro the <O= for this responsibility. ;f youdo not assi"n a request security "roup to this responsibility then usersassi"ned this responsibility &ill not be able to run any reports pro"ra s or request sets e2cept for request sets o&ned by the user.

,unction and 'enu !"clusions

1ou can define function and enu e2clusions to restrict specific application functionality available to aresponsibility. >unctions and enu e2clusions are a "reat &ay to apply the separation of duties0concept.

!"ample: 1ou &ant the 7ayable 'lerE to select invoices for pay ent and print a 7reli inary 7ay ent?e"ister but you do not &ant the 'lerE to for at pay ents or print the checEs i ediately.

Solution: ;n order to restrict the options that the 7ayables 'lerE can perfor &hen "eneratin" a checErun si ply e2clude the SUF>U!'%;O!S the 'lerE should not be able to perfor (such as 7ay entFatches 'onfir 7ay ent Fatches >or at 7ay ent Fatches 7rint) fro his/her responsibility. ;n the* efine ?esponsibility* for query the clerEs current responsibility and in the >unction and 8enu$2clusions blocE choose a type of >unction0 and in the <O= choose the subfunctions entionedabove. %he ne2t ti e the clerE si"ns into A7 he/she &ill be restricted to only select build print pay entre"isters etc. outside of the subfunction e2clusions.

!avi"ate to# Security>Responsibility>DefineSelect# 'enu !"clusions



8enu $2clusions6 %ype# • Select 8enu to e2clude all enu entries functions and sub- enus0fro the responsibility.

O? • Select function to e2clude all occurrences of that function fro the

responsibility8enu $2clusions6

!a e#

Select the na e of the function or enu to e2clude fro the responsibility.



$2cludin" Attributes allo& colu ns of data to be visible to specified users or responsibilities. $2cludin"Attributes ust be assi"ned at the responsibility level.

!"ample: ;f you &ant to restrict the user ane &ith responsibility of *Ad in* fro seein" prices in the#$%&-R#$! colu n then assi"n the e2cludin" attribute #$%&-R#$! to the responsibility *Ad in*.

avigate to: Security > Responsibility > DefineSelect: !"cluded #tems

$2cluded ;te s6 !a e# Select an attribute fro the <O= to be e2cluded fro the user0s access.

$2cluded ;te s6Application#

Oracle Self-Service Web Application. (Auto-'o pletion)

Assi"n request "roup to a responsibility

Overview

?equest Broups are used to control access to a "roup of requests. Use the System Administrator ?esponsibility to define ?equest "roups. %here are t&o types of request "roups used by OracleApplications at t&o different levels#

• Responsibility *evel # Used to control access to reports request sets and concurrent pro"ra s fora particular responsibility. A request "roup assi"ned to a responsibility is referred to as a ?equestSecurity Broup. A request security "roup is a collection of requests request sets and concurrent

pro"ra s that users &ho have been assi"ned a "iven responsibility can run.



• ,orm *evel # A request "roup is assi"ned a code &hich is passed as a para eter to the Sub it?equests Windo&. %he code helps define the function that calls the Sub it ?equests Windo&.

ote: ,orm *evel Security .roups are not covered in this document at this time .Define Re/uest .roup 0Responsibility *evel1

!avi"ate to# Security>Responsibility>Re/uest

Broup# $nter a unique na e for the request "roup you are definin".Application# Select the na e of the application you &ish to associate &ith your request

"roup fro the <O=. %his does prevent you fro assi"nin" requestsrequest sets and pro"ra s fro other applications to this "roup.

ote: ;t is reco ended that you define a custo application and assi"nto your custo request "roups in order to protect the durin" an up"rade.

'ode# Assi"n a code to this request "roup if custo izin" the standard Sub it?equests &indo& usin" codes in order to control user access to concurrent

pro"ra s and reports versus li itin" access at the responsibility level.escription# Optionally enter a description of the ?equest Broup.%ype# 'hoose 7ro"ra Application or Set

!a e# 'hoose the na e of the pro"ra application or request set you &ant toinclude in this "roup fro the <O=.

Assign Re/uest .roup to a Responsibility

• Duery the responsibility you &ould liEe to assi"n your request "roup to

!avi"ate to# Security>Responsibility>Define



?equest Broup6!a e# 'hoose a request "roup fro the <O=.

$reate value sets and assign values to value sets

Overview

%his docu ent e2plains ho& to define custo value sets. Use the System AdministratorResponsibility+

Define 2alue Sets

!avi"ate to# Application>2alidation> Set



=alue Set !a e# $nter a unique na e for this value set.

ote: ;t is reco ended that a na in" convention for the value set na es be established. A value set na e should be all one case (upper or lo&er)and no spaces (use underscores in place of spaces (@)). All custo valueset na es should be preceded by a unique prefi2 to protect your value setsdurin" an up"rade. >or instance all ;=AS custo value set na es are

preceded &ith ;=AS (;=AS@'US%O8@=A<U$@S$%).escription# Optionally enter a description for your value set.Security Available# ;f you are plannin" to use fle2field value security &ith any se" ents that

use this value set checE this bo2. ;f your value set is of validation type !one Special or 7air leave this bo2 unchecEed.

$nable <on"list# ;f you thinE your value set &ill contain a lar"e nu ber of values then checE this bo2 so a user ust enter a partial se" ent value before the list ofvalues retrieves all available values. ;f your validation type is !one leavethis bo2 unchecEed.

>or at %ype# >ro the drop do&n list select the type of data for at you &ant to use foryour values. =alid for at types are# 'har ate ate%i e !u berStandard ate Standard ate%i e and %i e.ote:

• Date and DateTime value set formats will be obsoletein Release 12 and are only provided for backwardcompatibility. Use Standard Date and Standard

DateTime for new value sets.• %ranslatable ;ndependent and %ranslatable ependent value sets usthave the 'har0 for at.

8a2i u Size# Specify the lon"est value that can be entered into a se" ent that uses thisvalue set. %his &ill also be the lon"est display size you can specify then youdefine your report para eter or fle2field se" ent. >or report para etersthe a2i u size you can use is GH,. >or %ranslatable ependent and%ranslatable ;ndependent value sets the a2i u is :9,.$aution: 3hen using a validation type of Table ma4e sure thema"imum si5e you select here reflects the si5e of the column you



• Translatable #ndependent: Si ilar to an independent value set e2ceptthe value ay be translated.

• Translatable Dependent: Si ilar to a dependent value set e2cept thevalue ay be translated.

ote: Al&ays define independent value set before dependent value set.

!"ample: =alue Set A is an independent value set containin" t&o values'o puter and 8onitor. =alue Set F is a ependent value set containin"four values 'o paq ell :JK and :9K. >or value set F the values'o paq and ell &ill appear in the list of values only if 'o puter &aschosen for value set A. :JK and :9K &ould appear in the list of values forvalue set F if 8onitor &as chosen for value set A.

.Validation Information

;f usin" a validation type of Table6 Dependent6 Translatable Dependent6 Special6 or -air you &illneed to supply additional validation infor ation.

Table 2alidation

• 'hoose a table in the Oracle Applications that contains the valid values for your value set.• 'reate a WC$?$ clause to li it the values you &ant to use for your set.

!avi"ate to# Application>2alidation> SetSelect# 2alidation Type>TableSelect# !dit #nformation



%able Application# >ro the <O= select the application that the validation table belon"s to. !ote# ;f you are "oin" to display colu ns fro ore than one table inyour <O= you should leave this field blanE.

%able !a e# $nter the table you &ant to use to validate your value set. ;f you plan todisplay colu ns fro ore than one table then enter ultiple tables in thisfield separated by co as. ;f you &ant to use table aliases then enter thehere.!"ample: ra@custo ers rac ra@addresses@all raa

ote: ;f you &ant to use a custo table then you ust do the follo&in" prior to navi"atin" to this for #

• 'reate the validation table in the database• ?e"ister the table &ith the Oracle Application ObIect <ibrary• 'reate the necessary "rants and synony s.

Allo& 7arent =alues# Select this option if you &ant to allo& parent values.=alue !a e# $nter the na e of the colu n in your validation table that contains the

values you &ant to use to validate a value entered for a se" ent or report para eter. 1ou can also use a SD< e2pression in place of a colu n na e but you cannot use bind variables.

ote: ;f you specified a for at type of !u ber then you can only specifycolu ns that have been defined as a !u ber or 'har for at. >or a for attype of ate you can only specify colu ns of type ate and 'har for afor at type of 'har you can only specify colu ns of type 'har.

=alue %ype# %his field &ill be auto atically populated &ith the data type of the colu nyou selected. ;f you use a SD< e2pression in place of a colu n na e thenyou ust select the value type you e2pect the e2pression to return.

Size# %his field &ill be auto atically populated &ith the size of the colu n youselected. ;f you use a SD< e2pression in place of a colu n na e then youust select the value type you e2pect the e2pression to return.

8eanin" !a e# $nter the na e of the colu n in your validation table that containsdescriptions for your values. ;f you leave this field blanE the value setauto atically uses the value colu n as the description but leaves this field

blanE.; !a e# $nter a na e of the colu n in your validation table that contains values

you &ant to use to validate a value but that you do not &ant to display.

!ote# ;f you select a colu n other than the value na e selected above thereport para eter &indo& passes this value to your report. >or fle2fields

this value is stored in your se" ent colu n rather than the value na eidentified above.Where/Order Fy# $nter a SD< WC$?$ clause and/or an O? $? F1 clause. 1ou can use

special bind variables here#

• #L><$ML.=alue@Set@!a e• #blocE.field (used for bacE&ard co patibility only)• #L7?O>;<$L.profile@option@na e

Additional 'olu ns# $nter any additional colu ns you &ant displayed for a se" ent that usesthis value set.



Synta": colu n@na e K'olu n AliasK (&idth). Where &idth is optional.1ou can use an asterisE (N) to specify a colu n &hose display &idthdepends on the values it contains.

ote: 8ultiple colu ns should be separated by co as.

Special7-air 2alidation

• 'reate special validation routines for value sets of type Special or 7air.

!avi"ate to# Application>2alidation> SetSelect# 2alidation Type>Special or 2alidation Type>-airSelect# !dit #nformation

$vent# Specify the event at &hich your special validation routine should fire. =alidevents include#

• !dit # 'alls the special validation routine &hen your user*s cursor enters

the se" ent in a data entry ode.• 2alidate: 'alls the special validation routine &hen the user*s cursorleaves the se" ent or closes the pop-up &indo& or &hen a defaultvalue is copied into the se" ent or report para eter. ;t also fires aftera query to "enerate value descriptions for queried values.

• *oad: 'alls the special validation routine i ediately after a query to populate your se" ent.

Note: The following events are present in OracleApplications forcompatibility with future versions, and you should



Assign 2alues to 2alue Sets

1ou can sEip this step unless your value set is of type ;ndependent %ranslatable ;ndependentependent or %ranslatable ependent. Also if your value set is of type %able and you have definedyour value set to allo& parent values then you can use this &indo& to define parent values for thevalues in your table.

ote: 1ou ust define independent values before related dependent values.

#ndependent 2alue Set

!avi"ate to# Application>2alidation>2alues

!a e# %he na e of your ;ndependent value set &ill appear here.ependent =alue Set# <eave blanE ;ndependent =alue# <eave blanE =alue# $nter the values you &ant to assi"n to this independent value set.escription# $nter a description for this value.$nabled# Select this option to enable the value. =alues cannot be deleted so if you

do not &ant users to select this value any lon"er then deselect this optionor enter an end date.

$ffective >ro # Optionally enter a start date for &hen this value beco es active.$ffective %o# Optionally enter an end date for &hen this value beco es no lon"er active.

Dependent 2alue Set

!avi"ate to# Application>2alidation>2alues



!a e# %he na e of #ndependent value set on &hich the dependent value setdepends &ill appear here.

ependent =alue Set# ;f a dependent value set is assi"ned to your independent value set it &illauto atically appear here.

;ndependent =alue# ;f your independent value set has a dependent value set assi"ned to it thenenter an independent value here then in the ne2t step enter the dependent

values you &ant to assi"n to this independent value. Once you haveentered all the dependent values (done in ne2t step) you &ant associated&ith this independent value then hit the arro& do&n Eey to enter anotherindependent value and proceed &ith enterin" the dependent values you&ant to assi"n to this independent value. 'ontinue &ith this procedureuntil you have assi"ned dependent values to all of your independent values.

=alue# $nter the dependent values you &ant associated &ith the independentvalue specified above.

escription# $nter a description for this value.$nabled# Select this option to enable the value. =alues cannot be deleted so if you

do not &ant users to select this value any lon"er then deselect this optionor enter an end date.

$ffective >ro # Optionally enter a start date for &hen this value beco es active.$ffective %o# Optionally enter an end date for &hen this value beco es no lon"er active.



aming Standards

File Names and Extensions

• >ile na es ust not e2ceed P characters and the first three letters represent the 8odule !a e.

•

;n the file na e &herever $n"lish alphabet letters are used they should be in U77$?'AS$.• >ile !a e should not contain any special characters i.e. Q 5 - L R N and others.

Program Type Directory File Type Extension7</SD< sql 7acEa"e specification 7Es

7acEa"e body 7EbSD<N7lus sql SD< script Sql

Spool file <stinstall/sql ;nstall script Sql

SD<N<oader bin 'ontrol file 'tlata file at<o" file <o"$rror file $rr iscard file is

U!;M bin Shell Script ShSD<N>or s H.9 or T., for s Finary > b

$2ecutable > 2Source > s

SD<N>or s G.J or G.H for s $2ecutable >rSource ;np

Oracle ?eports G., G.9 or T., sr& Finary ?df $2ecutable ?ptSource ?e2

7lease note the custo obIects need to be prefi2ed &ith the follo&in" to clearly define the

odule#-

'>; >inancial'8> 8anufacturin"'SA Sales Ad inistration

''O 'onversion

>or a "iven desi"n there &ill be one and only one 8O nu ber -even thou"h it ay contain pacEa"e procedures SD< scripts SD<Nfor s and Oracle ?eports. 8O nu bers ust beunique across odules.

Nomenclature'odule -refi" 9 'od umber

$2a ple'>;,,,: 8od : is for >inance

'8>,,,G 8od G is for 8anufacturin" 'SA,,,J 8od J is for Sales Ad inistration '8>,,,H 8od H is for 8anufacturin"



A 8O ay have ultiple obIects of the sa e type therefore suffi2 the obIect &ith an$n"lish letter (QA5 throu"h Q+5).

Nomenclature'odule -refi" 9 'od umber 9 *etter

$2a ple 8O '>;,,,: ay co prise of the follo&in"#'>;,,,:a.fr SD<N>or s

'>;,,,:b.fr SD<N>or s'>;,,,:a.sql SD<NScript'>;,,,:.b.sql SD<NScript'>;,,,:a.pEs 7acEa"e Specification'>;,,,:a.pEb 7acEa"e Fody

A database sche a can be co posed of various obIects i.e. tables inde2es sequences vie&ssynony s procedures tri""ers pacEa"es functions and database linEs. 7lease ensure thefollo&in" na in" convention is follo&ed#

ObIect na e can be a a2i u of J, characters lon". 7lease reserve the first three charactersto identify the application. %he na in" convention should facilitate in distin"uishin" the obIects.%he nor to adopt is as follo&s#

Object Type Standard Meaning Example%able J, characters lon" 'SA@SO@C$A $?S;nde2 QMn5 M4(U)nique or (!)on-Unique

n4;nde2 Sequence !u ber 'SA@SO@C$A $?S@U:

=ie& Q=5 = 4 =ie& 'SA@SO@C$A $?S@=Sequence QS5 S 4 Seqeunce 'SA@SO@C$A $?S@S%ri""er QM;U @%?B5 M4(F)efore or (A)fter

;4;nsert/U4Update/ 4 elete%?B4%ri""er

'SA@SO@C ?S@F;U@%?B

7acEa"e Q7 5 or Q7F5 7 47acEa"e Specification7F47acEa"e Fody

'SA@SO@C S@7 'SA@SO@C S@7F

>unction Q>!S5 >!S4>uncton 'SA@SO@C S@>!S

• ObIect na e should not contain any special characters i.e. Q 5 - L R N and others.• ObIect na e should be"in &ith an alphabetic character and ay contain underscore.• ObIect na e no enclature should be self e2planatory havin" a eanin"ful na e that is

understandable by the end users and ;S "roups.

Table• %he sequential order in &hich the colu ns need to be defined are#

7ri ary Eey colu nsWCO colu ns8andatory colu nsOptional colu ns<on" field colu n

• %o be created under the 'usto Sche a &ith necessary "rants to QA77S5 sche a• %he table na e should be plural.• Use the constraint/default definitions and referential inte"rity definitions for the colu ns of

the table.



• $nsure that the colu ns are classified as !U<< or !O% !U<<. Fy default the colu ndefinition is !U<<.

• $nsure that the WCO colu ns ('?$A%$ @F1 '?$A%;O!@ A%$<AS%@U7 A%$ @F1 U7 A%$@ A%$ <AS%@U7 A%$@<OB;! ?$DU$S%@; ) e2ist.

• ;f the data to be stored in the table is partitioned on the Operatin" unit then a O?B@;colu n &ith the default definition ust e2ist.

• $nsure that a pri ary Eey e2ists &ith a !U8F$? data type.• Use the follo&in" data types to qualify a colu n in a table =A?'CA?G !U8F$? A%$

FOO<$A! <O!B.• Whenever appropriate qualify the colu n definition to denote it0s purpose i.e.

_FLAG _CODE _TYPE _DATE _NAME _ID _VALUE

View• =ie& on a partitioned table needs to be created in the QA77S5 sche a. Use the WC$?$

'<AUS$ &ithin the vie& definition to dyna ically partition the data on user access.

Pac age Procedures!Triggers!Functions• 7acEa"e 7rocedures/%ri""ers/>unctions to be created in the QA77S5 sche a.

efine obIects &ith respect to the sche a as follo&s#

Schema ObjectCustom TableCustom IndexCustom SequenceCustom Grants

APPS Synonyms APPS Views

APPS PackageProcedures!"unctions!Triggers

APPS #inks



-rogramming Standard for -*7S * routines

• %he 7</SD< pacEa"es or code &ritten ust be odular and structured. Avoid the use ofBO %O etcV

• efine pacEa"es and procedures anony ous 7</SD< procedure definitions are notacceptable. %he pacEa"e specification and body in the sa e file &ith e2tension Qpls5.

• ?eserved &ords and Eey Oracle &ords to be 'apitalizedSELECT

FROM WHERE

• Source code indentation is essential.• atabase tri""er size to li it to T, lines of code. ;f the lo"ic of the tri""er is ore than T,

lines it is better to create a 7</SD< pacEa"e and call it fro the tri""er. 7</SD< pacEa"e isstored in the database and is already in a co piled state. Also as the pacEa"e can be pinnedthe e2ecution ti e is faster.

• Avoid tri""ers that duplicate the functionality already built in Oracle (e2a ple enforce datainte"rity by usin" declarative inte"rity constraints rather than a F tri""er)

• Within a tri""er < state ents are not allo&ed. Also no transaction control state ents areallo&ed in a tri""er (?O<<FA' SA=$7O;!% 'O88;%).

• $2tensive co ents need to be incorporated into the code.• ;nitialize the variables prior to use &ithin the source code.• ;!S$?% state ent needs to specify the fields and values.

INSERT INTO TABLE table_name( !el"#$ !el"%$

!el"&'VALUES

( al)e#$ ** !el"# al)e%$ ** !el"% al)e&'+ ** !el"&

Variable declarations• =ariable to have a eanin"ful na e and to be initcap. =ariable to be prefi2ed &ith v0

O,"e,N)mbe, O,-an!.at!/nI" In ent/,0ItemI"

• =ariable data type declaration to be associated to appropriate sche a.obIect.fieldO,-an!.at!/nI" mtl_101tem_!tem12/,-an.!t!/n_!"3TYPE+In ent/,0ItemI" mtl_101tem_!tem12!n ent/,0_!tem_!"3TYPE+

"ursor De#initions• 'ursor to refer to obIect na e(s) on &hich it is defined and to be initcap. 'ursor to be

prefi2ed &ith 'ur0• Use aliases to uniquely identify the fields

CURSOR C),S/H",Ln1 IS SELECT a2/,"e,_n)mbe, /,"e,_n)mbe,$

b2!n ent/,0_!tem_!" !n ent/,0_!tem_!" b24a,e5/)1e_!" 4a,e5/)1e_!"

FROM 1/_l!ne1 a



1/_5ea"e,1 bWHERE a25ea"e,_!" 6 b25ea"e,_!"+

• $nsure the drivin" table in all S$<$'% state ents is last in the >?O8 clause• $nsure for every O7$! 'U?SO? state ent there is a correspondin" '<OS$ 'U?SO?

state ent.• Wherever possible use >O? ?ecord in 'ursor <OO7 rather than O7$! 'U?SO?

state ent• ;n order to debu" the 7</SD< pacEa"e use the F8S@OU%7U% routine. 1ou ay need to

S$% S$?=$?OU%7U% O! S;+$ :,,,,,, to "enerate the output. !ote the output is"enerated after the pacEa"e co pletes or ter inates &ith an error. >or a "iven session theF8S@OU%7U% buffer is not cleared. o not use the routine to "enerate flat files orreports.

• o not include e2plicit co its &ithin the pacEa"e. ;n case the pacEa"e requires processin"of records that can create rollbacE se" ent proble please put co its at lo"icaltransaction points &ith SA=$7O;!% and ?O<<FA' functions.

• %he 7</SD< desi"n to taEe into account ho& to re-co ence a ter inated Iob and not re- process the processed records unless there is an e2plicit require ent.

• <atest version provides a facility to output to a flat file• ;nstead of incorporatin" the pro"ra in" lo"ic in the %ri""er or an Alert it is better to &rite

the lo"ic as a pacEa"e procedure. %he advanta"e is the pacEa"e is co piled parsed andstored in the database and therefore it requires pri arily to fetch and e2ecute.

Exception $andling • $nsure that at least the follo&in" e2ceptions are handled in the 7</SD< constructs

NO_DATA_FOUNDTOO_MANY_ROWS OTHERS

• %he error nu ber ust contain the od nu ber the sequence of e2ception.• 7lease use the $??FU> and $??'O $ para eters as an output. %hey ust be the first

t&o para eters in the 7</SD< pacEa"e

;t is advisable to aintain a central repository/library of 7</SD< pacEa"es &ith the s alldescription. %his library ay co prise pacEa"es called fro different routines. 1ou need toensure nobody odifies the shared pacEa"e procedure. Also if ti e per its the pacEa"es ay

be defined and developed to be "eneric in nature &hich &ill enhance the library.

-rogramming Standard for Oracle ,orms

•

Use the %$87<A%$ for to develop ne& for s. %he te plate e2ists inL>! @%O7/for s/US. %he te plate includes the follo&in"#- %ibrary Purpose>! 8$!U aster copy of the shared obIectsA77S%A! LAU@%O7/resource - library of utilities>! SD> AO< utilitiesA77'O?$ 'ontrol 8enu/%ool bar A77 A17 library of calendar

• $nsure all FU%%O!S in Oracle Application looE and behave the sa e



• $nsure all FU%%O!S in Oracle Application use FU%%O! 7roperty 'lass• efine 7roperty 'lass and include in the ObIect Broup• Apply the 7roperty 'lass to obIects to ensure unifor ity in the functionality and visual

appearance• Fuild for s based on the =ie& definitions. %he first colu n in the vie& should be the

?OW; and be "iven the alias na e of ?OW@; .• e-nor alize the >orei"n ey references by buildin" vie&s this &ill avoid net&orE traffic

and aEe the 7?$-DU$?1 and 7OS%-DU$?1 tri""ers to populate the non-database fieldsredundant

• ;n order to insert/update/delete call the O!-;!S$?% O!-U7 A%$ O!- $<$%$ O!-<O' tri""ers to access the base table rather than the vie&

• 'orrection and enhance ents on vie& &ill be at the server level rather than in severalsource code &hich ay or ay not reside on the server

• o not use the ?OO%@W;! OW as it affects the toolbar functionality• When definin" the 8O A< W;! OW (e.". dialo" bo2) code the lo"ic for QO 5 and

Q'A!'$<5 buttons in advance. ;f not done as the Eey tri""ers and enu is disabled on

invoEin" the odal &indo& there &ill be no &ay to e2it the for .• 8odify the te plate procedures A77@'US%O8.O7$!@W;! OW orA77@'US%O8.'<OS$@W;! OW to eet the require ents on openin" or closin" a for

• %ry &ritin" pacEa"e procedure and store in the server. !u ber of procedures to a pacEa"ereco ended by Oracle to be less than G9

• While referencin" a field on the for qualify it &ith the blocE na e#F<O' @!A8$.>;$< @!A8$

• Use e2plicit cursors in tri""ers and handle all possible e2ceptions• Use ?A;S$@>O?8@%?;BB$?@>A;<U?$ to stop processin" at the client level• Use A77@$M'$7%;O!.?A;S$@$M'$7%;O! to stop processin" at the server level• 'A<<@>O?8 routine is in-co patible &ith O7$!@>O?8• %o e2it Oracle Application suite copy Q15 to B<OFA<.A77'O?$@$M;%@><AB and then

call the O@ $1@$M;%@>O?8• Use A77@;%$8@7?O7$?%1.S$%@7?O7$?%1 and

A77@;%$8@7?O7$?%1.S$%@=;SUA<@A%%?;FU%$ to "et the Oracle Applicationstandard behavior

• Use A77@;%$8@7?O7$?%1.B$%@7?O7$?%1 to "et Oracle Application specific property• ?eplace O7$!@>O?8 &ith >! @>U!'%;O!.$M$'U%$ as security depends on the

latter • ?eplace '<$A?@>O?8 &ith O@ $1( '<$A?@>O?80) as the latter raises the

>O?8@%?;BB$?@>A;<U?$ if there is an invalid record• ?eplace 'O88;% &ith O@ $1( 'O88;%@>O?80) as the latter raises the

>O?8@%?;BB$?@>A;<U?$ if there is an invalid record• ?eplace $ ;%@>;$< /$ ;%@%$M%;%$8 &ith O@ $1( $ ;%@>;$< 0) as the latter

raises the calendar &hen the current ite is a A%$• $2tensive co ents are reco ended

Triggers Must be modi#ied PRE*FORM WHEN*NEW*FORM*INSTANCE



Triggers t&at can be modi#ied' but do not delete t&e (PP)ST(ND(*D+EVENT call wit&in t&e respecti,etriggers

7EY*CLRFRM POST*FORM 8UERY*FIND

ACCEPT

Triggers t&at can be o,erridden at t&e -%O". and /TEM le,el 7EY*DUPREC 7EY*MENU 7EY*LISTVALWHEN*NEW*RECORD*INSTANCE WHEN*NEW*BLOC7*INSTANCE WHEN*NEW*ITEM*INSTANCE 8UERY*FIND

ACCEPT ON*ERROR

Do not modi#y t&e #ollowing triggersSTANDARD_ATTACHMENTS 9OOM FOLDER_ACTION 7EY*HELP 7EY*E:IT 7EY*EDIT 7EY*COMMIT WHEN*WINDOW*CLOSEDCLOSE_WINDOW

• 7lease ensure to populate the WCO colu ns• Store the lo"ic for settin" the WCO colu ns in 7?$@;!S$?% and/or in the 7?$@U7 A%$

event tri""ers• 'all standard >! @S%A! A? .S$%@WCO routine in the tri""er to set the WCO values

"olumn Name Type Value Deri,ation'?$A%$ @F1 !ot !ull %O@!U8F$?(>! @7?O>;<$.=A<U$( US$?@; 0))'?$A%;O!@ A%$ !ot !ull S1S A%$<AS%@U7 A%$ @F1 !ot !ull %O@!U8F$?(>! @7?O>;<$.=A<U$( US$?@; 0))<AS%@U7 A%$@ A%$ !ot !ull S1S A%$<AS%@U7 A%$@<OB;! %O@!U8F$?(>! @7?O>;<$.=A<U$( <OB;!@; 0))?$DU$S%@; >! @'O!'U??$!%@?$DU$S%S7?OB?A8@A77<;'A%;O!@; >! @'O!'U??$!%@7?OB?A87?OB?A8@; >! @'O!'U??$!%@7?OB?A87?OB?A8@U7 A%$@ A%$ 7?OB?A8@U7 A%$@ A%$

• 'all fle2field definition in WC$!-!$W->O?8-;!S%A!'$ tri""er • >! @ $1@><$M. $>;!$ is for Eey fle2field• >! @?A!B$@><$M. $>;!$ is for ran"e fle2field• >! @ $S'?@><$M. $>;!$ is for descriptive fle2field• While callin" a fle2field definition ensure tp specifiy the F<O' and >;$<



• Also pass the follo&in" para eters i.e. A77<@SCO?%@!A8$ fle2field 'O $ andstructure !U8 if it is a Eey fle2field else A77<@SCO?%@!A8$ and$S'@><$M@!A8$ for descriptive fle2fields

• >le2field can be invoEed fro several for level tri""ers by callin" >! @><$M.$=$!%• Use standard >! @8$SSAB$ routines to display and retrieve essa"es

-rogramming Standard for Oracle Reports

• $nsure that no lo"ic e2ists in the A>%$? 7A?A8$%$? >O?8. ;f the lo"ic e2ists thenove it to the F$>O?$ ?$7O?% %?;BB$?. %he lo"ic should be incorporated after thecall to S?W;!;% function

• ;nclude the S?W;!;% in F$>O?$ ?$7O?% %?;BB$? • ;nclude S?W$M;% in A>%$? ?$7O?% %?;BB$? • ;nclude 7@'O!'@?$DU$S%@; in the User 7ara eters• ;n order to debu" the report use the S?W.8$SSAB$ routine• Avoid any data anipulation ( 8<) &ithin the report• ;nstead of &ritin" e2tensive lo"ic &ithin the report &rite a 7</SD< 7acEa"e and call it

&ithin the report. %he advanta"e is aintenance beco es si ple and the sa e routine ay be used by other pro"ra s.

S *;*oader

%he basic SD<<OA co and isSD<<OA

US$?; 4 Oracle Userna e/pass&ord'O!%?O< 4 'ontrol file na e

<OB 4 <o" file na eFA 4 Fad file na eA%A 4 ata file na e;S'A? 4 iscard file na e;S'A? 8AM 4 !u ber of discard allo&ed default is A<<0S ;7 4 !u ber of records to sEip default is ,<OA 4 !u ber of records to load default is A<<0$??O?S 4 !u ber of errors allo&ed default is 9,S;<$!% 4 Suppress essa"es durin" run

Data %oad OPT/ON

The data load can either be $or a $ixed length or %ariable length record& 'e(endingu(on the $ormat the loading may ha%e ex(licit or relati%e (ositioning method&

;!S$?% - requires the table to be e pty?$7<A'$ - deletes the ro&s and inserts ne& dataA77$! - appends data to the e2istin" data in the table

(ssembling %ogical records #rom P&ysical *ecords



One logical record may be created and loaded $rom multi(le (hysical records by usingthe $ollowing)*

'O!'A%$!A%$'O!%;!U$;>

0enerating Data

The data may be generated and inserted into the table column by calling one o$ the$unctions within the S+#,#oader scri(t CO-T.O# $ile)*

• CONSTANT - set the colu n to a constant value. o not use to assi"n !U<< to a colu n.%o set a colu n to !U<< do not specify the colu n

• RECNUM - sets the colu n &ith the lo"ical record nu ber fro the load. %he initial valuefro a ne& load is :. ;f the Option S ;7 is used then the ?$'!U8 be"ins &ith S ;7 : asthe initial value

• SYSDATE - sets the colu n to syste date. %he 'CA? colu n only stores the date&hereas the A%$ colu n stores date and ti e

• SE8UENCE - $nsures a unique value for a colu n. 7lease note that sequence increases forloaded or reIected records but does not increase for the discarded or sEipped records

Setting a "olumn to N1%% or 2E*O

-/## or 0ero %alue may be inserted into the table column by calling one o$ the$unctions within the S+#,#oader scri(t CO-T.O# $ile)*

• DEFAULTIF use the Eey&ord to set the colu n to zero &hen specified field test conditionis %?U$

• NULLIF use the Eey&ord to set the colu n to null if &hen the specified field testcondition is %?U$

(pply S3% Operators

1ou may a((ly S+# o(erators to mani(ulate the $ield data while loading into the table&-ote the $ollowing)*

• %o refer to the field na e preceed the field na e &ith a colon (#)• SD< strin" to be enclosed in double quotes• SD< strin" is evaluated after the !U<<;> and $>AU<%;> clause but before the A%$

for at asE • SD< strin"s ay not be used on ?$'!U8 S$DU$!'$ 'O!S%A!% S1S A%$ fields• SD< operators that ay be used include

<OW$? ?%?;8<%?;8%?A!S<A%$$'O $SUFS%? %?U!'



!=<%O@ A%$%O@'CA?

Utilities to Debug6 Trace and Tune

•

F8S@OU%7U%.7U%@<;!$ in 7</SD<• >! @8$SSAB$ in Oracle >or s• S?W.8$SSAB$ in Oracle ?eports• $M7<A;! /7<A! in SD<N7lus• % 7?O> for trace files fro the Operatin" Syste• o not perfor a function on the table field that is bein" used in the WC$?$ clause of a

S$<$'% state ent. %his ay hit perfor ance if an inde2 e2isted on the fieldSELECT /,"e,_t0;e

FROM 1/_5ea"e,1WHERE /,"e,_n)mbe, 6 TO_NUMBER(Pa,amete,'

• %o understand the eanin" of the O?A error essa"es you ay "o to the Operatin" Syste pro pt and type in the follo&in"#-

7ro pt6 /e,, /,a e,,/,_me11a-e_n)mbe, • ;t is reco ended to use the $M;S% function than the ;! function &hile usin"

correlated/sub-queries.

?e"isterin" 'oncurrent 7ro"ra s

'oncurrent $2ecutable/7ro"ra sSa e as e2ecution file na e in uppercase.$2a ple# '>;,,,:a

efine'oncurrent 7ro"ra

Name ust have ;!;%'A7 i.e. Qall &ords ust have the first letter in upper case5. %he na eust contain the prefi2 to identify the odule.$2a ple# '>; A7 ;nvoice 7rint

S5/,t Name ust be the sa e as the e2ecutable na e. ;f the sa e e2ecutable is bein" used forore than one concurrent pro"ra then use underscore and nu ber as suffi2.$2a ple# '>;,,,:a@: '>;,,,:a@G

The Development !nvironment

2ach (roduct 3G#4 Purchasing4 In%entory4 etc&5 in an installation o$ Oracle A((lications hasan associated o(erating system directory& All $iles required to install4 u(grade4 or run the(roduct are stored in this directory 3or related subdirectories5& 2ach (roduct also has one ormore database user accounts which own tables used by the (roduct& A((lication Object#ibrary calls this collection o$ objects an a((lication&

A set o$ customi6ations $or one or more (roducts is installed as an a((lication& Thus it has a(roduct directory and an Oracle user account&



Directory Structure

The directory structure $or an installed (roduct is as $ollows :

LA77<@%O7 X

3product short na e6

X 3product version6 @@@@@@@@@@@@@@@@@@@@@@@@@@@ X@@@@@@@@@@@@@

X X X X X X X X Xad in bin conversions for s lo" out reports sql &f

X X @@@@@@@@@@@@@@@@@@@@@@@@@ @@@@ X X X X X X Xaropen coa custo ers fa pricelist &ft sql

The directory structure $or the custom de%elo(ment objects is as $ollows)

LA77<@%O7 X

('US%O8 !A8$) L('US%O8 !A8$)@%O7X

:.MM @@@@@@@@@@@@@@@@@@@@@@@@@@@ X@@@@@@@@@@@@@

X X X X X X X X Xad in bin conversions for s lo" out reports sql &f

X X @@@@@@@@@@@@@@@@@@@@@@@@@ @@@@ X X X X X X Xaropen coa custo ers fa pricelist &ft sql

The (roduct short name is a two to eight character abbre%iation o$ the (roduct 3i&e& G#4 PO4I-V4 etc&5& The short name $or .a(id Oracle Im(lementation custom a((lications will be

73C/STO8 -A8259&

The (roduct %ersion subdirectory le%el allows multi(le %ersions o$ a (roduct to be a%ailablewithin a single A((lications installation& The naming con%ention is :major %ersion;&:minor%ersion;&:(atch le%el; 3i&e& <&=&>5& The standard is to begin with =&>&> $or a new (roductregardless o$ the general release number or Oracle A((lications&

$reating a $ustom Application

1ou must register the 3C/STO8 -A825 a((lication be$ore you can begin de%elo(ing custommodules& The ste(s to register a new a((lication are)

Y 'reate the directory structure

Y 8odify LA77<@%O7/A77<S1S.env to set the environ ent variable L('US%O8 !A8$)@%O7 andadd L('US%O8 !A8$)@%O7/bin to the 7A%C environ ent variable. $2a ple#

('US%O8 !A8$)@%O74LA77<@%O7/('US%O8 !A8$)/G.:.,e2port ('US%O8 !A8$)@%O77A%C4L7A%C#L('US%O8 !A8$)@%O7/bin$2port 7A%C

Y e2ecute the A77<S1S.env file.



Y Select Application eveloper responsibility and re"ister the application.

$ustom Tables

-ew tables required by your custom (rograms should be created in an Oracle user createdexclusi%ely $or customi6ations& "or con%enience4 it should match the a((lication short name

o$ your custom a((lication 33C/STO8 -A8255& Grants and synonyms will allow otherOracle users to access your custom tables&

To access custom $orms exclusi%ely4 you must register the custom Oracle I' 73C/STO8-A8259 in the A((lication Object #ibrary& I$ custom $orms will be accessed $romres(onsibilities that also access standard $orms4 sim(ly create grants and synonyms so thatthe Oracle user associated with the res(onsibility can access the custom tables&

<our Development Account

The de%elo(ment account will be gi%en the username o$ 3C/STO8 -A825 to con$orm to

3C/STO8 -A825 standards& ?hile indi%idual (rogrammers and analysts may own code inde%elo(ment4 the /-I@ 3C/STO8 -A825 account will be the owner o$ all com(leted customcode&

Custom de%elo(ment should be done within a orn shell with orn shell scri(ts and P#!S+#scri(ts being the tools o$ choice $or data (rocessing&

1ou should de%elo( and test custom modules under the B3C/STO8 -A825 TOP (ortion o$the directory tree& I$ they ha%e not been (re%iously created4 you may ha%e to create thedirectories) admin4 bin4 con%ersions4 $orms4 log4 out4 re(orts4 sql4 and w$ 3log and out can beso$t links to the actual log and out directories5&

=uilding <our -rograms

'e%elo( and test your (rograms $rom within your local directories& "ollow the instructions inthe re$erence manual o$ each Oracle tool you (lan to use to insure your en%ironment is(ro(erly initiali6ed&

?hen modi$ying or creating $orms4 it is not necessary to sa%e them to the database& Insteaduse the #OA' and G2-2.AT2 o(tions o$ S+#,"orms D&> to read and write the source code$ile directly& Also4 your $orm cannot be sa%ed to the database when you register it with

A((lication Object #ibrary&

Any text editor can be used $or C (rograms4 S+#,Plus4 and P#S+# (rograms& The %i editorwill be used because it comes standard with /-I@&

Registering <our -rograms

"ollow the instructions in the Application Object Library Developer's Reference Manual toregister your $orms and (rograms& All (rograms must be registered in order to be attached tomenus or executed in the concurrent manager& Once a concurrent (rogram or re(ort hasbeen registered it does not need to be reregistered a$ter a modi$ication& "orms only need tobe reregistered i$ you add4 delete4 or change the order o$ $ields or 6ones&



$ustomi5ed $ode and Ob ects Registering

Objecti%e )

To kee( the standard Oracle A((lications objects se(arate $rom the custom objects&

Procedure)To create the work tables required in the customi6ation (rocess under Oracle I' 73C/STO8-A8259& The naming con%ention described in the naming con%ention standards section o$this document should be $ollowed& All custom objects should be mo%ed to the custom B3C/STO8 -A825 TOP directory& There are sub*directories $or all o$ the object ty(es&

All custom objects i&e& tables4 menus4 re(orts4 $orms4 %iews4 and sequences should beregistered under E3C/STO8 -A825 Custom A((licationE a((lication name& This is done $or'atabase and "orm objects through the A((lication 'e%elo(er .es(onsibility&

Custom re(orts will a((ear in the A((lication in the same screen as theF StandardF re(orts4but the code will reside in B3C/STO8 -A825 TOP directory& ?hen a existing standardre(ort requires modi$ication4 a clone o$ the re(ort should be made& The new re(ort shouldthen be renamed with a 3C/STO8 -A825 * naming con%ention& The 3C/STO8 -A825 titlewill hel( identi$y the re(ort as custom re(ort&

"ollowing are the ste(s $or the same&

=&.egister concurrent (rogram executable under E3C/STO8 -A825 Custom A((licationEa((lication& See the document

& .egister the (rogram under the E3C/STO8 -A825 Custom A((licationE a((lication&

=& Add the modi$ied or custom (rogram to a request grou(& See thedocument AO# .equest Grou(s Setu( $or additional in$ormation&

The out(ut o$ the re(ort and the log will be created in the regular a((licationEs BO/T andB#OG directory&

%o re"ister %ables navi"ate to Application6 atabase6%able6?e"ister under the Application eveloper?esponsibility.



%o re"ister a >or navi"ate to Application6>or under the Application eveloper ?esponsibility.

%o re"ister a 8enu navi"ate to Application68enu under the Application eveloper ?esponsibility.



Source Code under B. I TOP directory

.egister Tables4Views4 Sequences

"orms4 .e(orts andConcurrent Programs

Create Tables4 %iews4sequences under

Oracle Id . I

Standard OracleA((lications

Create synonyms $or the objects createdunder oracle Id . I

Gi%e grants toA((lications Oracle Id

2nter the A((lication

name as . i CustomA((lication under Standard A((lications

8enu

. i Custom A((lication Standard Oracle A((licat

Option ?:To execute customi6ed code $rom the 3C/STO8 -A825 Custom

A((lication4 Synonyms need to be created under the a((lications3C/STO8 -A825 Custom A((lication I' to allow access to thes(eci$ic standard Oracle objects& Grants need to be createdunder the (articular standard Oracle I' to allow access to the

3C/STO8 -A825 Custom A((lication I'&



Source Code under B. I TOP directory

.egister Tables4Views4 Sequences

"orms4 .e(orts andConcurrent Programs

Create Tables4 %iews4sequences under

Oracle Id . I

Create Synonyms $or th objects used in

customi6ation under Oracle Id . I

Create di$$erent.es(onsibility $or each

a((lication in whichcustomi6ation is done

Standard OracleA((lications

Gi%e grants toA((lications Oracle Id

. i Custom A((lication Standard Oracle A((lications

aming Standards

A database schema can be com(osed o$ a %ariety o$ structures4 generically re$erred to asobjects&



• Fe na ed usin" the sin"ular for representin" the notion of a sin"le e ber of the set or collectionrepresentin" the table. e.". 'US%O8$?@!A8$ not 'US%O8$?@!A8$S.

• Fe consistent bet&een tables clearly representin" the Eeys to be Ioinedand the consistency of the values to be used.•

!ot use table na e prefi2es e2cept for special circu stances. e.".'US%O8$?@!A8$ not '8@'US%O8$?@!A8$ for the colu ncontained in the custo er aster table.• Use table na e prefi2es &hen part of the pri ary Eey. e.". >or an ;

colu n in the 'US%O8$?S table use 'US%O8$?@; .• Use table na e prefi2es to allo& proper forei"n Eey relationships to

aintain the sa e na e. e.". %his allo&s the use of the na e'US%O8$?@; in the O? $?S table &hich ay also contain an ;colu n of its o&n.

Domain ame Suffi"es for $olumns

?hene%er a((ro(riate4 use su$$ixes on column names to denote the domain o$ the %ariable&"or exam(le4 i$ the column is in the domain o$ all codes and contains the status $or an item4use the name STAT/S CO'2 instead o$ the name STAT/S&

Another $requently used exam(le is the use o$ $lags& A $lag column contains a sim(le 1!-character %alue use the domain su$$ix $lag to re(resent this ty(e o$ item& "or exam(le4 ashi(ment con$irmation $lag containing either a E1E or an E-E would be namedSJIP CO-"I.8 "#AG&

Some commonly used su$$ixes include)

"#AG CO'2 T1P2 'AT2 -A82 O?-2. VA#/2

$oding Standards

S(eci$ic coding and testing standards are well documented in other Oracle documentation& Iha%e chosen not to du(licate that in$ormation here& Jowe%er4 here are some major (oints toremember)

Y Use odular codin" techniquesY Use co ents e2tensively. Al&ays thinE about so eone else readin"

your code.

Y Select a style for indentation variable na es etc. and use it consistently.

Y ;nclude eanin"ful error essa"es &hen your pro"ra encounters ane2ception condition.

Y ;n spite of the use of ?$80 in the follo&in" sa ple te plates /N0 andN/0 should be used &henever possible to delineate co ents.



Y 'o and synta2 and Eey&ords such as S$<$'%...>?O8...WC$?$should be capitalized. =ariable na es should be in lo&er case.'o ents should be in i2ed case. >or e2a ple#

/N %est 'ode N/S$<$'% table@na e>?O8 user@synony sWC$?$ synony @na e liEe ;!=@R0Z

Using Templates

2stablishing tem(lates $or common ty(es o$ (rograms is a good way to standardi6e&'e%elo(ers can co(y standard tem(lates and may need to modi$y them to con$orm to3C/STO8 -A825 standards such as $or (rogram comments and case*sensiti%ity&

SQL*Plus Concurrent Pro ram !em"late

Included below is a tem(late $or concurrent (rograms written in S+#,Plus& This is a workingtem(late that will (rint a sim(le re(ort o$ organi6ations de$ined in Oracle In%entory& Itim(lements the cosmetic standards established $or Oracle 8anu$acturing re(orts&

?$8 44444444444444444444444444444444444444444444444444444444444444444444444444?$8 'opyri"ht (c) G,MM 3'o pany !a e6 X?$8 All ri"hts reserved. X?$8 X?$8 44444444444444444444444444444444444444444444444444444444444444444444444444?$8?$8 7?OB?A8 !A8$# MMMMMMMM ($2planation)?$8?$8 7U?7OS$# Sa ple concurrent report in SD<N7lus?$8?$8 'A<<;!B >O?8A%#?$8 %estin"# sqlplus f"/ f" MMMMMMMM 3or" id6?$8 'oncsub# 'O!'SUF f"/ f" 8>B *Oracle 8anufacturin"* 8>B'O! 'O!'U??$!%

?$8 ('US%O8 !A8$) MMMMMMMM 3or" id6?$8 >or s# >! 'O!'U??$!% ('US%O8 !A8$) MMMMMMMM 3or" id6?$8?$8 'A<<$ F1# Oracle 8anufacturin" >or MMMMMMM?$8?$8 C;S%O?1?$8 8O! 11 >irst <ast - ;nitial codin"?$8?$8 44444444444444444444444444444444444444444444444444444444444444444444444444

?$8 --- Bet co and line para etersdefine or"@id 4 *[:*

?$8 --- Set report di ensionsdefine report@&idth 4 :JGS$% <;!$S;+$ [[report@&idthS$% 7AB$S;+$ TH

?$8 --- efine and set i bedded header variables'O<U8! today !$W@=A<U$ @sysdate !O7?;!%'O<U8! or"anization@na e !$W@=A<U$ @or"na e !O7?;!%F?$A O! today

S$<$'% %O@'CA?(S1S A%$ * -8O!-11 CCGH#8;#SS*) today or"anization@na e>?O8 or"@or"anization@definitionsWC$?$ or"anization@id 4 [[or"@id/'<$A? F?$A S



?$8 --- Set titledefine title 4 *Sa ple ?eport*define subtitle 4 **define lefttitle 4 **

%%;%<$ <$>% @or"na e ?;BC% * ate# * @sysdate S ;7 : - <$>% *[[lefttitle* '$!%$? *[[title* - ?;BC% *7a"e# * >O?8A% SD<.7!O sEip : - '$!%$? *[[subtitle* S ;7 G

?$8 --- FlanE footer F%;%<$ S ;7 ,

S$% C$A ;!B O! !$W7AB$ ,'<$A? 'O<U8!S

?$8 --- 'olu n efinitions'O<U8! se" ent: >O?8A% AG, C$A ;!B K;te K'O<U8! description >O?8A% AJ, C$A ;!B K escriptionK'O<U8! cate"ory >O?8A% A:9 C$A ;!B K'ate"oryK

?$8 --- Select state ent

select ;%$8.se" ent: ;%$8.description 'A%.se" ent: cate"oryfro

tl@cate"ories 'A% tl@syste @ite s ;%$8&here

'A%.or"anization@id 4 [[or"@idand 'A%.cate"ory@id 4 ;%$8.cate"ory@idand ;%$8.or"anization@id 4 [[or"@idorder by

;%$8.se" ent:/

?$8 --- 7rint end of report footer

define end@report 4 *NNN $nd of ?eport - [[title NNN*S$% 7AB$S;+$ ,S$<$'% <7A(*[[end@report* ([[report@&idth <$!B%C(*[[end@report*))/G)>?O8 UA</

$ustom -rograms

Overview

%his docu ent e2plains ho& to setup custo pro"ra s in Oracle Applications. ;n order to protect yourcusto pro"ra s fro up"rades it is reco ended that you re"ister a custo application and directorystructure and assi"n your custo pro"ra s to this application.

#$ecutable Pro ram

=uild !"ecutable Source ,ile

Fefore re"isterin" your custo pro"ra you ust first#



• Write the pro"ra /report you &ish to e2ecute fro the Standard ?equest Sub issions &indo& ofthe Oracle Applications. 1ou can &rite your e2ecutable source file by usin" any of the follo&in"ethods#

• Cost Script• Oracle ?eports• 7</SD< Stored 7rocedure• SD< Script• SD<N7lus Script• ' or 7roN' 7ro"ra

• 8ove the e2ecution files to their proper place on the operatin" syste in use. %he follo&in" tablesho&s &here these e2ecution files should be placed in a Uni2 environ ent#

Tool !"t+ DirectorySqlN7lus [ 7</SD< .sql L'US%O8@%O7/

LA77<SD<Oracle ?eports .rdf L'US%O8@%O7/LA77<?$7

Sql <oader .ctl L'US%O8@%O7/LA77<F;!

ote: %he pro"ra na e is case sensitive and ust e2actly atch the $2ecution file you defined previously.

Define $oncurrent -rogram !"ecutable

efine a concurrent pro"ra e2ecutable for each e2ecutable source file you &ant to use &ith concurrent pro"ra s. $2ecutables are defined to linE the custo pro"ra to your e2ecutable source file.

!avi"ate to# $oncurrent>-rogram>!"ecutable

$2ecutable# $nter a na e for your concurrent pro"ra e2ecutable. (1ou assi"n thisna e to your concurrent pro"ra .)

Short !a e# $nter a short na e for your concurrent pro"ra e2ecutable. (1ou assi"nthis na e to your concurrent pro"ra .)



7ara eter# $nter a na e for the para eter. %he na e you enter here &ill be displayedin the Sta"e >unctions 7ara eter &indo& of the ?equest Set for .

Short !a e# $nter a short na e that &ill be used by the function to reference the para eter.

escription# Optionally enter a description of the para eter.

Concurrent Pro ram

Define $oncurrent -rogram

!avi"ate to# $oncurrent>-rogram>Define

7ro"ra # $nter a descriptive na e for your concurrent pro"ra . %his is the na eusers &ill see &hen sub ittin" a request.

Short !a e# $nter a short unique na e. Oracle Applications uses this na e to associate



your concurrent pro"ra &ith an e2ecutable.Application# >ro the <O= select the application you &ish to associate your pro"ra

&ith. ;t is reco ended that you define a custo application &ith its o&ndirectory structure in order to protect your pro"ra s durin" an up"rade.%he Oracle Applications uses this to deter ine &hat O?A'<$ userna ethis pro"ra runs in and &here to place the lo" and output files.

$nabled# 1ou cannot delete a concurrent pro"ra but you can disable it by un-checEin" this bo2. isabled pro"ra s do not sho& up in the user0s lists orappear in the concurrent ana"er queues.

$2ecutable6!a e# >ro the <O= select the e2ecutable that runs your pro"ra . 1ou candefine ultiple pro"ra s that use the sa e e2ecutable.

$2ecutable68ethod# %his field &ill be auto atically populated &ith the e2ecution ethod that&as selected &hen the e2ecutable &as defined.

ote: 1ou can s&itch bet&een Spa&ned and ; ediate overridin" thee2ecution ethod defined in the 'oncurrent 7ro"ra $2ecutable &indo&only if either ethod appears &hen the e2ecutable is selected and both ane2ecution file na e and subroutine na e have already been specified in the'oncurrent 7ro"ra .

$2ecutable6Options# $nter e2ecution option values here. ;f your concurrent pro"ra usesOracle ?eports G., then you ust enter the para eter *=$?S;O!4G.,b*.Other para eters for Oracle ?eports G., that you can enter here are*O?;$!%A%;O!43 al)e 6* and *7AB$S;+$43 4!"t5 623 5e!-5t 6. %hereshould be no spaces before or after the e2ecution options values and the

para eters should be separated by a sin"le space.$2ecutable67riority# ;f you do not assi"n a priority here then the user*s profile option

'oncurrent#7riority sets the request*s priority at sub ission ti e.?equest6%ype# Optionally enter a request type fro the <O= to li it &hich concurrent

ana"ers can run your concurrent pro"ra .

?equest6;ncre entor# ;nternal field used only by Oracle Applications developers?equest68<S >unction# 8ultilin"ual Support function if used by the pro"ra .?equest6Use in S?S# %his ust be checEed if you &ant to be able to run this pro"ra fro the

Standard Sub it ?equest Sub issions for .

=alues#1ou can only checE this bo2 if you have checEed the *Use in S?S* bo2. 1oucan allo& users to enter disabled values (values that have been disabled ore2pired in a value set) as para eter values.'hecE this bo2 if your pro"ra is inco patible &ith all pro"ra s in itslo"ical database includin" itself.'hecE this bo2 if you &ant to turn on SD< tracin" &hen this pro"raruns.

?equest6?estart onSyste >ailure#

'hecE this bo2 if you &ant this pro"ra to be auto atically restarted&hen the concurrent ana"er is restored after a syste failure.

?equest6!<S'o pliant#

'hecE this bo2 if the pro"ra allo&s the sub ission of requests that &illreflect a lan"ua"e and territory different fro the lan"ua"e and territorythe users are operatin" in.$2a ple# Users in the United in"do enter orders in the $n"lish usin"the United in"do date and nu ber for ats then "enerate invoices inBer an usin" Ber an date and nu ber for ats

Output6 >or at# Select the output for at for your concurrent pro"ra fro the drop-do&nlist. =alid values are %e2t C%8< 7 > 7S (7ost Script) and 7'< (C70s7rinter 'ontrol <an"ua"e).



Output6 Save# 'hecE this bo2 if you &ant to have the output fro this pro"raauto atically saved to an operatin" syste file. ;f this bo2 is leftunchecEed then the output is deleted after printin".

Output6 7rint# 'hecE this bo2 if you &ant to be able to print output to a printer.Output6 'olu ns/?o&s# Optionally enter the ini u colu n and ro& len"th for the pro"ra *s

report output. Oracle Applications uses this infor ation to deter ine&hich print style to use.

Output6 Style# ;f you &ant to print your pro"ra *s report output then you should enter a print style fro the <O=.

Output6 Style ?equired# ;f your pro"ra requires a specific print style then checE this bo2 toenforce the print style. !or ally users can chan"e the print style at runti eunless this bo2 is checEed.

Output67rinter# Users can chan"e the printer the pro"ra they are sub ittin" is sent tounless you select a printer fro the <O= for this field. %his option is usefulfor such thin"s as checE printin" &here you &ant to restrict to a certain

printer.

$opy $oncurrent -rogram

Use this feature to create a concurrent pro"ra usin" the sa e e2ecutable request and reportinfor ation.

!avi"ate to# $oncurrent>-rogram>DefineSelect# $opy toB

7ro"ra # $nter 7ro"ra !a eShort !a e# $nter 7ro"ra Short !a eApplication# Application the pro"ra is associated &ith;nclude ;nco patible7ro"ra s#

'hecE this bo2 if you &ant to copy the ;nco patible pro"ra definition tothe ne& custo pro"ra

;nclude 7ara eters# 'hecE this bo2 if you &ant to copy the 7ara eters to the ne& custo pro"ra s



Application# >ro the <O= select the application the inco patible pro"ra belon"s to.efaults to the application the concurrent pro"ra belon"s to.

!a e# >ro the <O= select the pro"ra that is inco patible &ith your pro"ra .

ote: %he na e and application ust uniquely identify a pro"raScope# >ro the drop-do&n list select one of the follo&in"#

• Set: ;ndicates your concurrent pro"ra is inco patible &ith this pro"ra and all its child requests (Set).

• -rogram Only: ;ndicates your concurrent pro"ra is inco patible&ith this pro"ra but not its child requests.

Define -rogram -arameters

!avi"ate to# $oncurrent>-rogram>DefineSelect# -arameters

'onflicts o ain# $nter the para eter &hich &ill hold the value of the conflict do ain of the

pro"ra . %he conflict do ain identifies the data that cannot be accessedor updated si ultaneously by inco patible concurrent pro"ra s.Security Broup# %his field is only used for C?8S security. 7lease refer to the appropriate

docu entation for details.Sequence# 'hoose a sequence nu ber to specify the order in &hich you &ant your

pro"ra to receive para eter values fro the concurrent ana"er. ;t isreco ended that you nu ber in incre ents of :, (:, G, J, H,V.) incase there is ever a need to insert additional para eters bet&een t&oe2istin" ones.



ote: ;f you do not nu ber in incre ents of :, and need to add anadditional para eter bet&een t&o e2istin" para eters you &ill have todelete the para eters and reenter the &ith there ne& sequence nu bers.

7ara eter# $nter the na e of your para eter. A user-friendly na e is defined later(7ro pt).

escription# Optionally enter a description for this para eter.$nabled# ;f this bo2 is not checE then the para eter &ill not be displayed at request

sub ission ti e and &ill not be passed to the e2ecution file.=alidation6=alue Set# >ro the <O= select the value set your para eter &ill use for validation.

%he list of values &ill only display value sets that are of type independenttable and non-validated.

=alidation6 efault %ype# Select a default type fro the <O= if you &ant to set a default value forthis para eter. =alid types are#• $onstant: efault value can be any literal value• -rofile: efault value is the current value in a user profile option• S * Statement: efault value deter ined by a SD< state ent• Segment: efault value is the value entered in a prior se" ent of the

sa e para eter &indo&=alidation6 efault=alue#

$nter a default value for your para eter#• $onstant: $nter any literal value• -rofile: $nter the profile option na e (not the end-user na e). 1ou

do not need to include L7?O>;<$L.• S * Statement: $nter the SD< state ent. ;t ust return only one

ro& and one colu n in all cases.• Segment: $nter the na e of the se" ent

=alidation6?equired# ;f your pro"ra requires an ar"u ent then you should checE this bo2. ;fyou do not checE this bo2 and your pro"ra requires an ar"u ent the

pro"ra &ill co plete in error but if you checE this bo2 then a essa"e&indo& &ill appear notifyin" you that you ust enter a value for this

para eter.

ote: ;f your pro"ra requires an ar"u ent but the default type is profilethen you &ill not need to checE this bo2 since the user &ill not be inputtin"a value

=alidation6$nableSecurity#

;f the value set for this para eter allo&s security rules then optionallyapply any security rules defined for this value set to affect your para eterlist.

=alidation6?an"e# 'hoose either <o& or Ci"h fro the drop-do&n list if you &ant to validateyour para eter value a"ainst the value of another para eter in this

structure. ;f you choose <o&0 for a para eter you ust choose Ci"h0 for another para eter and vice versa. ;f your value set is of the type *7air* thisfield is display only. %he value defaults to pair.

Windo&6 isplay# 'hecEin" this bo2 displays the para eter in the 7ara eters &indo& of theSub it ?equests for .

ote: ;f you do not &ish to display a para eter then aEe sure you assi"na default value to it.

Windo&6 isplay Size# $nter the field len"th in characters for this para eter. %he size you enterhere deter ines the field size in the 7ara eters &indo& of the Sub it



?equests for .

ote: ;f the total of the value set a2i u sizes for all your para eters plus the nu ber of separators you need (nu ber of para eters inus one)e2ceeds GH, then you ay see truncation of your data in so e for s.

Windo&6 escriptionSize#

$nter the display len"th in characters for the para eter value description.

Windo&67ro pt# $nter a user-friendly na e for the para eter. %he user sees the pro ptrather than the para eter na e.

Windo&6'oncatenatedescription Size#

$nter the display len"th in characters for the para eter value description.

%oEen# ;f your para eter belon"s to an Oracle ?eports pro"ra you ust enterthe Eey&ord or para eter here. %his field is case sensitive.!"ample: p@date0SEip this field for other types of pro"ra s.

$oncurrent 'anager

Overview

'oncurrent pro"ra s are typically data-intensive tasEs that run si ultaneously &ith other onlineoperations. A concurrent ana"er is itself a concurrent pro"ra that starts other concurrent pro"ra s.%his docu ent e2plains ho& to start up define and confi"ure concurrent ana"ers. 'oncurrent8ana"ers are defined and assi"ned one or ore &orE shifts. %ar"et processes deter ine the nu ber ofconcurrent requests that can be handled si ultaneously. %herefore a co bination of &orE shifts andtar"et processes are used in order to achieve the ost efficient syste perfor ance.

Felo& is a su ary listin" of the concurrent ana"ers and their functions#

Fasic 'onfi"uration

;nternal 'oncurrent8ana"er (;'8)

%he ;nternal 'oncurrent 8ana"er Starts up verifies the status of resets and shuts do&n the;ndividual ana"ers. Settin"s for the ;'8 cannot be altered

Standard 8ana"er ?uns JT9 days a year GH hours a day and accepts any and all requests. ;thas no specialization and should !O% be altered

!ote# ;f the Standard ana"er is altered in any &ay so e pro"ra s aynot run. We reco end that you define additional ana"ers to handleclient-specific needs.

'onflict ?esolution8ana"er

%he 'onflict ?esolution 8ana"er resolves conflicts such as requestinco patibilities. %he 'onflict ?esolution 8ana"er checEs concurrent

pro"ra definitions for inco patibility rules. ;f a pro"ra is identified as?un Alone then the 'onflict ?esolution 8ana"er prevents the concurrentana"ers fro startin" other pro"ra s in the sa e conflict do ain. Whena pro"ra lists other pro"ra s as bein" inco patible &ith it the 'onflict?esolution 8ana"er prevents the pro"ra fro startin" until anyinco patible pro"ra s in the sa e do ain have co pleted runnin".

Scheduler/7rereleaser Scheduler/7rereleaser ana"er



8ana"er %ransaction 8ana"er(;nternal Only)

%ransaction 8ana"er for dia"nostics only

'odule Specific 'anagers

8odule 8ana"er escription %ypeAccounts?eceivable

?eceivables %a2 8ana"er Used to process ta2 calculations. %ransaction8an"er

'apacity '?7 ;nquiry 8ana"er ?uns capacity inquiries. %ransaction8ana"er

;nventory ;nventory 8ana"er Used to process inventorytransactions if you have chosen

bacE"round processin" ode.;nventory transactions includeaterial transactions de andreservation ove transactionsresource transactions and costin" ofaterial transactions.

'oncurrent8ana"er

;nventory ;!= ?e ote 7rocedure8ana"er

;f you have chosen server side on-line processin" this ana"er allo&s atransaction initiated on the client to

process on the server

%ransaction8ana"er

8asterSchedulin"/8?7

8?7 8ana"er ?uns the i ediate concurrent pro"ra of 8?7

'oncurrent8ana"er

7roIects 7A Strea line 8ana"er 8ana"es strea line processes. 'oncurrent8ana"er

7rovisionin" Oracle 7rovisionin"8ana"er

?uns provisionin" requests 'oncurrent8ana"er

7urchasin" 7O ocu ent Approval8ana"er

8ana"es docu ent approval by providin" the queue for docu entsa&aitin " approval.

%ransaction8ana"er

7urchasin" ?eceivin" %ransaction8ana"er

Used to process receivin"transactions.

%ransaction8ana"er

ote: 8odule specific 'oncurrent 8ana"ers can be deactivated and not started accordin" to clientneeds.

Administer Concurrent %ana ers

1ou can issue co ands to start verify shut do&n or reset concurrent ana"ers individually or usethe ;'8 to control every ana"er at once. ;t is reco ended that you restart an individual concurrentana"er every ti e you chan"e any of its definitions such as &orE shifts tar"et processes specializationand inco patibility rules. %his process forces the ;'8 to reread these definitions.

Startin" the ;'8

>ollo& the steps outlined belo& to start the ;'8 durin" installation of Oracle Applications aftershutdo&n of concurrent ana"ers or after restartin" your operatin" syste or database



• <o" in to the U!;M server as appl "r • Select the appropriate database environ ent• Use the follo&in" co and# Start "r 3O?A'<$@S; 6

'ontrollin" ;ndividual 8ana"ers

!avi"ate to# 'oncurrent68ana"er6Ad inister Select# Any individual ana"er.

!ote# '?8 cannot be controlled usin" the ad inistration for . %he ;'8 cannot berestarted usin" the ad inistration for . ?efer to the Oracle Applications ;nstallation"uide for further details.

%er inate# %er inate the ;'8 to deactivate all concurrent ana"ers and ter inate allconcurrent requests at once. %er inate individual ana"ers to deactivatethe selected ana"er and all requests handled by that ana"er

eactivate# 'an be used on any ana"er $M'$7% the '?8 andScheduler/7rereleaser. eactivate the ;'8 to deactivate all ana"ers ordeactivate individual ana"ers by deactivatin" the selected ana"er.'oncurrent requests currently runnin" are allo&ed to co plete before theana"er(s) shut do&n

!ote# Once deactivated the ;'8 can only be activated fro the server.Activate# Use to activate previously deactivated individual concurrent ana"ers.

!ote# %he ;'8 can only be activated fro the server?estart# Available for any active individual ana"er $M'$7% the ;'8

Scheduler/7rereleaser and '?8. ?estartin" an individual concurrentana"er forces the ;'8 to reread its definition

=erify# Only available &hen you select the ;nternal 8ana"er (;'8). See section belo& on verifyin" concurrent ana"ers



7rocesses# =ie& details for selected concurrent ana"er0s processes?equests# =ie& all runnin" and pendin" requests for selected concurrent ana"er 2erify $oncurrent 'anagers

Fy default the ;'8 periodically onitors each concurrent ana"er0s processes. 1ou can force thisonitorin" activity also Eno&n as 78O! by selectin" the ;'8 and choosin" the =erify button. Alsouse this function to checE that the actual processes atch the tar"et.

avigate to: $oncurrent>'anager>AdministerSelect: #nternal 'anagerSelect: 2erify

Define 3or4 Shifts

A WorE Shift is a specified period of ti e. efine WorE Shifts to specify &hen a concurrent ana"ercan run. WorE Shifts are defined to cover day and ti e periods usin" ilitary ti e notation. When&orE shifts overlap the one &ith the ore specific ti e period taEes precedence. >or e2a ple a &orEshift for a specific date overrides a &orE shift set to run fro a to 9p every 8onday throu"h>riday. When &orE shifts &ith the sa e priority overlap the one &ith the lar"est nu ber of tar"et

processes taEes precedence.



avigate to: $oncurrent>'anager>3or4Shifts

!a e# ;ntuitive na e e.". !i"ht Shift0 Braveyard Shift0 WeeE ays0WeeEends0

%i e6>ro # Start ti e for the shift in ilitary ti e for at ( $$2%&''( e.). *+,&++-,am(

%i e6%o# $nd ti e for the shift in ilitary ti e for at ( $$2%&''( e.). *1 &++-

0pm( !ote# WorEshifts cannot run across idni"ht i.e. they ust end by GJ#9and be"in on or after GH#,,

ays of WeeE6>ro # >irst day of WorEShift e.". 8onday0 for &eeEdays WorEShiftays of WeeE6%o# <ast day of WorEShift e.". >riday0 for &eeEdays WorEShiftate# Date value for a date speci c 3orkS4ift5 e.). *678 +1 2+++-

!ote# ate specific &orEshifts override &orEshifts that do not specify aspecific date



Define $oncurrent 'anager

avigate to: $oncurrent>'anager>Define

8ana"er# ;ntuitive na e for identifyin" your concurrent ana"er Short !a e# ;ntuitive short na e for identification/search purposesApplication# Application odule for identifyin" your concurrent ana"er. A

co bination of the application and ana"er na e creates a uniqueidentification of your concurrent ana"er.

!ote# %he application na e is erely for identification purposes only anddoes not in any &ay define the Einds of requests your concurrent ana"ercan run. 1ou &ill need to apply specialization rules to do this.

escription# Short description of your concurrent ana"er %ype# Select concurrent ana"er. %his field cannot be updated once defined.

;nternal 8onitors are used to onitor and restart the ;'8 in case it e2itsabnor ally for any reason. %ransaction 8ana"ers are used to handlesynchronous requests fro client achines. 7lease refer to the appropriatedocu entation for settin" these up.

ata Broup# <eave blanE. %his field is for %ransaction 8ana"ers only'ache Size# Use this to define the nu ber of request your ana"er Eeeps in e ory.

%he reco ended nu ber is : for lar"e Iobs and J-H for s aller Iobs.'onsu er Broup# ;dentifies the resource consu er "roup7ri ary !ode# Use this to define the pri ary node your concurrent ana"er operates on

if you are operatin" in a parallel concurrent processin" environ ent. !ote# !odes ust be previously re"istered in Oracle Applications beforethey are ade available on this screen.

Secondary !ode# Use this to define the secondary node your concurrent ana"er operateson if you are operatin" in a parallel concurrent processin" environ ent andyour pri ary node "oes do&n.



!ote# !odes ust be previously re"istered in Oracle Applications beforethey are ade available on this screen.

7ri ary Syste Dueue# Use this to define a platfor -specific pri ary syste queue you associate&ith the pri ary node if you are operatin" in a parallel concurrent

processin" environ ent.

!ote# ?efer to platfor -specific docu entation for details.Secondary SysteDueue#

Use this to define a platfor -specific secondary syste queue youassociate &ith the secondary node if you are operatin" in a parallelconcurrent processin" environ ent.

!ote# ?efer to platfor -specific docu entation for details.7ri ary 7latfor # efine your pri ary platfor if you are operatin" in a parallel concurrent

processin" environ ent.Secondary 7latfor # efine your secondary platfor if you are operatin" in a parallel

concurrent processin" environ ent7ro"ra <ibrary !a e# Select a pro"ra library na e to aEe available i ediate concurrent

pro"ra s to your concurrent ana"er.7ro"ra <ibraryApplication#

1our ana"er &ill only be able to run i ediate concurrent pro"ra sre"istered in the pro"ra library you select.

!ote# ?efer to the appropriate docu entation for re"isterin" i ediateconcurrent pro"ra s in a pro"ra library usin" AO<.

Assign 3or4 Shifts

!avi"ate to# 'oncurrent68ana"er6 efineSelect# WorE Shifts

8ana"er# isplays your concurrent ana"er na eApplication# isplays the application na e associated &ith your concurrent ana"er WorE Shift# Select a &orE shift to assi"n to your concurrent ana"er escription# isplays description of the selected WorEShift7rocesses# !u ber of operatin" syste processes the WorEShift runs si ultaneously.

$ach process can run a concurrent request.



Sleep Seconds# !u ber of seconds your concurrent ana"er &aits bet&een checEin" listsof pendin" concurrent requests

$oncurrent 'anager Speciali5ation

Specialization rules can be used to specify the Einds of requests a concurrent ana"er should run bysettin" ;nclude0 and $2clude0 options.

avigate to: $oncurrent>'anager>DefineSelect: Speciali5ation Rules

;nclude/$2clude# Select requests to include or e2clude fro your concurrent ana"er %ype# Select the type of rule to assi"n e.". User0 7ro"ra 0.Application# Select the application associated &ith your rule type

!a e# Select the na e for your rule typeescription# $nter intuitive description for your specialization rule

=asic =usiness eeds

Create an alert that sends a noti$ication to the Payables 8anager when a return is created inPurchasing to ensure (ro(er accounting in Payables&

Create an e%ent 3on insert5 alert that sends a message to the Payables 8anager indicatingan .8A has been created in Purchasing& The message should contain the $ollowingin$ormation)

.8A .e$erence+uantity



.eason $or .eturn8ethod o$ .eturnPO -umber

User -rocedures

The Alert will be acti%ated u(on insert o$ the .CV T.A-SACTIO-S table&

Alert Description

Select# Alert 'anager ?esponsibility !avi"ate to# Alert 6 efine

Application# Oracle 7urchasin" !a e# ?%= $ ail Alert$vent6Application# Oracle 7urchasin"$vent6%able# ?'=@%?A!SA'%;O!SSelect# After ;nserteep MMM ays# :,Select State ent# select distinct a.r a@reference

a.quantity f.description a.attributeJ b.se" ent: ".line@nu ".ite @description ".quantity N unit@price c.vendor@na e



Action %ype# 8essa"e%o# enter an e ail address that has been setupSubIect# ?8A 'reated in 7urchasin"Select# %e2t%e2t# An ?8A &as created in 7urchasin" &ith the follo&in" details#

?8A ?eference # [?8A@?$>$?$!'$

?eturned Duantity # [DUA!%;%1?eason for ?eturn # [?$ASO!@!A8$8ethod of ?eturn # [?$%U?!@8A%CO7O !u ber # [7O@!U8F$? 7O <ine !u ber # [<;!$@!U87O <ine escription # [;%$8@ $S'? 7O <ine A ount # [<;!$@A8OU!%Supplier !a e # [=$! O?@!A8$Supplier Site !a e # [=$! O?@S;%$@'O $

7lease process the related A7 ;nvoice accordin"ly.

'olu n Overflo&# WrapSelect# Action Sets



Seq# :Action Set !a e# ?8A $vent $ ail Alertescription# Send $ ail Alert to 7ayables 8ana"er upon ?8A creationSelect# $nabled8e bers6Seq# :8e bers6Action# ?8A $ ail Alert8e bers6%ype# Action# 8essa"e

8e bers6Action# AbortSelect# $nabled

appstech material

Documents