Tracking Customization's Using Register Flagged Files Tool in R12

Having Better Life With Customizations... http://apps2fusion.com/at/ !"radhika/#$1"tracking"customizations"using"register"flagged"files"tool"in"r12% utm&source'feed(urner)utm&medium'email)utm&campaign'Feed*!+,anilpassi,*2-.racle,+pps,To,Fusion,+pps*2 /hene0er 1e implement .racle +pplications2 the client often comes up 1ith some (usinesses processes 1hich cannot (e completel3 implemented using the e4isting 5R6 processes. These are generall3 accommodated (3 customizations in the 5R6. This gi0es rise to creation of custom o(7ects/s3stems. .0er a period of time 1hen the actual use of s3stem increases the num(er of customizations increases too. 8uring a course of time it ma3 happen that the compan3 needs to upgrade the en0ironment or appl3 certain patches that are released (3 .racle. 9t ma3 happen that there is a strong impact on the customizations that are (uilt. 9f the customizations are done (3 using :Customization ;3 <odification= approach there is a danger of the changes (eing completel3 1ashed off (3 the upgrade or patch application. >o is there an3 1a3 to a0oid this% .r at least a 1a3 to minimize the impact% ?es there is@@@ The 1a3 is to use :Register Flagged Files Tool= in R12. Register Flagged Files tool can (e accessed through .racle +pplications <anager A.+<B responsi(ilit3 in R12. Flagged files is a concept 1ithin the .racle e;usiness >uite A5;>B release 122 1here 3ou flag a standard deplo3ment file2 let's sa3 a Forms file2 a 6ackage or a Ca0a class file. /hen 3ou run the patch anal3sis2 the list of flagged files 1ill (e checked and in case one of these files gets patched2 the anal3sis report 1ill tell 3ou. ?ou can flag as man3 files as 3ou 1ant2 in 1hate0er relationship the3 are 1ith 3our customizations. 9n addition to the flag itself 3ou can add a comment. ?ou should use this comment to point to 3our customization reference Ahere DD+R&R6T&EFF or DD+6&CU>T&E!EB. 9t is suggested to put the flagged files data file directl3 into 3our C5<G9 patch. Here1ith the flagged files registration 1ill (e e4ecuted right at the same time 1hen the patch gets applied. Process Steps: 8e0eloper: I ;uilds C5<G9 I Re0ie1s code and identifies ke3 standard o(7ects referenced I 8etermines standard o(7ect files and flags them I Creates FJ8G.+8 file and adds the same to the C5<G9 patch 8;+: I 54ecutes for e0er3 ne1 .racle standard patch the patch anal3sis in a representati0e en0ironment I Checks and retrie0es the flagged files and comments I >ends flagged file list (ack to de0elopment team for anal3sis / retest 8e0eloper: I +nal3ses / Updates / Retests effected C5<G9s 6rereKuisite: The patch anal3sis has to (e e4ecuted in an en0ironment 1here flagged files ha0e (een registered. A9f 3ou run the patch anal3sis in a 0anilla or outdated en0ironment Acompared to 3our 6R.8B2 the anal3sis 1ill not (e so helpful@B /hen to start 1ith Flagged files% >tart right no1 utilizing this feature. 9t is an in0est to impro0e the production sta(ilit3 and fulfill 3our >G+@ For 11i Users: This functionalit3 is also a0aila(le in release 112 here it is implemented and kno1n as Lapplcust.t4tL. ?ou modif3 .racle +pplication components onl3 1hen 3ou cannot meet a reKuirement using .racle +pplication features and customization (3 e4tension Acustom component de0elopmentB is not an option. Ho1e0er2 3ou should list each component that 3ou modif3 in the file applcust.txt. This file2 located in the M+66G&T.6/admin director3 Aor platform eKui0alentB2 pro0ides a single location for a (rief listing of customizations. .racle +pplications uses this file during patch processes Afor Release 11.E and laterB to generate 1arning messages that customizations are (eing o0er1ritten or ma3 need to (e replaced after the patch. +lso2 3ou can use the list to help determine the scope of changes that ma3 (e needed to customizations after an upgrade or patch. The applcust.txt file pro0ides a place to list the original file name and location and a (rief comment. The a(o0e o(7ect listing process should also (e follo1ed for customization files that are copies of .racle +pplications files in custom top Acustomization (3 e4tensionB. For such customization 3ou also include the destination file name and location Athe customized fileB. There is a format to (e follo1ed 1hile registering 3our customization # <Sprd> <Src Dir> <Src Fname> <Dprd> <Dest Dir> <Dest Fname>

It is easier to understand the format with an example.Consider that the file $AR_TOP/forms/US/AR SU!AT.fm" has "een modified in the method C#$ as $ AR_TOP/forms/US/ AR SU!AT.fm"

is nothin% "ut the Standard produ&t a""re'iation. In simple meanin% the Sprd is ta(en usin% the format $_TOP. is alwa)s whate'er after $_TOP* in our &ase it is forms/US is the exa&t file name. is )our &ustom top where )ou ha'e )our &ustomi+ed/modified file. is the dire&tor) stru&ture after $_TOP is the name of )our &ustom file. So in our example &ase* the format of the entr) will "e as follows , ar forms/US AR SU!AT.fm" xxar forms/US AR SU!AT.fm" If )ou ha'e &ustomi+ed )our file in the C#- method* then )ou &an lea'e the last three entries as "lan( .as "elow/ , ar forms/US AR SU!AT.fm"

Steps in Detail to Register Flagged Files 0a'i%ation1 .R/ S)stem Administrator 2 .-/ Ora&le Appli&ations -ana%er 2 Site -ap 2 -aintenan&e 2 Re%ister 3la%%ed 3iles

Cli&( on 4Add5 "utton.

$nter the filter &riteria to sear&h for the o"6e&t and &li&( on 47o5 "utton.

Results will "e displa)ed.

Sele&t the appropriate o"6e&t and &li&( on 4Add5 "utton.

8rite &omments in the pro'ided field. 9ou should use this &omment to point to )our &ustomi+ation referen&e.

Sample

9our :#A should now run the Pat&h Anal)sis e'er) time he is %oin% to appl) a new pat&h. 0a'i%ation1 .R/ S)stem Administrator 2 .-/ Ora&le Appli&ations -ana%er 2 Pat&h 8i+ard 2 Tas( ;Re&ommend/Anal)+e Pat&hes;

The s&reen shot a"o'e shows the impa&t summar). 3or this "lo% entr) the num"er ;<; titled ;3la%%ed 3iles Chan%ed; is in our fo&us. 8hen )ou &li&( the ;<; )ou will %et a similar s&reen li(e the first in this "lo%* showin% )ou exa&tl) the files whi&h will %et pat&hed if )ou &ontinue and appl) this pat&h in this en'ironment ri%ht now. 0ote1 It is also shown that 6ust <=> of all pat&h files will %et applied. This situation mi%ht "e different in &ase )our en'ironments are on a different pat&h le'el. 3or sure also the &ustomi+ation impa&t mi%ht then "e different. The fla%%in% step &an "e done dire&tl) in the Ora&le Appli&ations -ana%er. To transport su&h a fla%?&omment we use a 30:@OA: s&ript. It is su%%ested to put the fla%%ed files data file dire&tl) into )our C$-@I pat&h. Aerewith the fla%%ed files re%istration will "e exe&uted ri%ht at the same time when the pat&h %ets applied.