Assets Personalization Presentation for Eastern States

7/28/2019 Assets Personalization Presentation for Eastern States

1/76

Using the New Forms 6iPersonalization Capability toEnforce Business Rules inOracle Assets

Ca s e S tu d y 11i.10


2/76

Goals of Presentation

Overview of our Project

Business case for custom logicPossible ApproachesCapabilities of Forms 6i PersonalizationStep by Step Approach for our RequirementsOther Personalizations in ScopeSummary


3/76

Overview of Project

Large 11i Installation PA, AP, GL, POinstalledRetailer US and Canada

6000 + Locations1.5 MM Asset Recordsin 2 Legacy systems

FA and AR beingimplemented post11.5.10 UpgradeHeavy integration with3 rd Party EAM solutionRapid growth in Asset

base expected better tracking abilityIntegration withProperty Tax Solution


4/76

Business Case for Custom Logic

Large number of potential end users geographicallydispersedSeveral key extensions to support businessrequirementsTurnover and training challenges

Previous systems were home grownOther Oracle modules had been tailored through useof 3 rd party applicationsOracle Assets provided too much flexibility need to

restrict and guide users


5/76

Business Case Cont

During various CRP and training sessions

too many holes identifiedFlexibility of Oracle Assets often viewed asnot restrictive enoughDifferent rules for property vs. equipmentDifferent rules for tax vs. financeDid not want Asset / Books Security features


6/76

Our Options

Customization

Forms Triggers Exception or Alert Based Reports

Use Custom Library3 rd Party Tool Already licensed for other appsForms 6i Personalization


7/76

Our Other Considerations

Customization Costly to Build, Test, Support Future patching and upgrades more difficult Customizations are extra cost if hosted3 rd Party Tool

Required additional expertise Desire to limit use of bolt-on products Stated direction to simplifyCustom Library required scarce skilled

development resources


8/76

The Choice Forms 6i Personalization

Recent 11.5.10 Upgradeallowed opportunity to

experiment and consider asa choiceGoal of organization to avoidcustomizationsGoal of organization to avoid

3 rd party solutions Ability to have real timefeedback

Goal of organization tomove into areas supported

by E-Business SuiteOur Business Analysts hadsuccesses at previouscustomers with theseapproaches

Did not require a developer


9/76

Quick Overview of Forms 6iPersonalization Some Background

Core Modules Available in 11.5.10 as wellas Release 12Located near Examine type utilities

Allows for customers to create rules anddecide how and when they are applied

Not initially heavily documented requiredtrial and error, bartering for Oracle internaldocumentation


10/76

Capabilities of PersonalizationRemove fields, buttons, tabs, etc. from the screenbecause they never use them

Re-label fields and buttons to be more insightful or touse a terminology of the customer Change an attribute of a field update, required, etcChange the default value of fieldsRestrict or enable for a user or a responsibility or application (Industry is Future Use)Have conditional logic for when the rule is invokedHave site specific dynamic messages for immediatefeedback


11/76

Capabilities (Cont) Allows you to make declarative changes to a form. Changes get applied at runtime when the proper

trigger event occurs. Changes can get applied based user, resp, etc You can:

Change object properties Execute certain Forms builtins Display helpful, warning or error messages Activate menu entries Prevent Actions


12/76

Rules-Conditions

Determines when a personalization will applyIf Evaluates to True, then something will happen.


13/76

Context Site, Resp, User

* Note that Industry is reserved for Future Use


14/76

Actions

Determine what the personalization will do

Sequence determines Order (you can havemultiple personalizations)Description is for debugging and for documentation purposes

Language can apply to All or one LanguageSet Properties, Display Messages, CallForms or Functions


15/76

Actions - Example


16/76

Reminder Our Goals

Enforce Business Rules above and beyondstandard functionalityRemove some of the flexibility of the

Applications Avoid Customizations of Forms

Avoid use of 3rd

Party Products Avoid use of Custom LibraryUse Forms 6i Personalization to accomplishall of the above


17/76

For our study- Business Rules

1.Prevent Override of Depreciation ExpenseSegment as Defined onthe Category2.Limit use of locationcombinations to thoseapplicable to thecorporate book US,CA

3.Make RetirementType a mandatory fieldfor reporting andaccounting purposes4.Enforce use of uppercase whenentering or queryingdescriptions


18/76

Prevent Override of Deprn Segment

Categories suggest a default expense

accountUser can override on the Quick AdditionsFormUser can override on the Detailed AdditionsformWe can end up with deprecation expense inwrong accounts


19/76

Standard Quick Additions Functionality Default from Category


20/76

Quick Additions Allows Override


21/76

Case One - Background Research

Quick Additions and Detailed Additions Form are allpart of the Asset Workbench Form Name isFAXASSET (From Help About Oracle Applications)Use Examine Utility to Determine Block Names QuickAdditions ADDITION_DIST and Detailed

Additions is the ASSIGNMENTS_DIST Block

A Default Expense Account is associated with EachCategory/Book Combination as part of the standardsetup


22/76

Case One Background (cont)

Other Key Elements Needed :ASSIGNMENTS_HEADER.DEPRN_EXPENSE_ACCT :ASSIGNMENTS_HEADER.BOOK_TYPE_CODE :ASSIGNMENTS_HEADER.ASSET_CATEGORY_ID

FA_CATEGORY_BOOKS.deprn_expense_a

cct and book_type_code in the base table


23/76

How Did we Determine thisInformation?

Use of basic tools available to support or

business analystsHelp -About this RecordExamine UtilityPast ExperienceE-TRM on Metalink


24/76

How to Determine a Form Name


25/76

Examine Utility

Help Diagnostics Examine

Controlled by (Utilities:Diagnostics) Profile


26/76

Side Note - Control of Access toPersonalization and other Utilities


27/76

How to Invoke Form to DefinePersonalizations

Invoke the Form to Setup the Personalization from the Form you wish to

modify


28/76

Other Menu Items

Core Code Only if you are having issues

Show Custom Events Great for findingevents to attach toPersonalize Invokes the PersonalizationformNormal Run form with Personalizations


29/76

Need to do Several Things

Name the Rule and supply a Condition

Attached to some Event pre-existing logicin the formSupply a Context (who does this apply to?)Create an Action(s) - What should result ?


30/76

Rule Prevent Override - QuickAdds


31/76

Trigger Event When Validate Record


32/76

Condition (SQL Statement)


33/76

SQL- If Field Segment Differs from

Setup Definition

:ADDITION_BOOKS.EXPENSE_ACCT !=(select deprn_expense_acct from

fa_category_bookswhere fa_category_books.book_type_code

= :ADDITION_BOOKS.BOOK_TYPE_CODE

and fa_category_books.category_id =:ADDITION_ADD.ASSET_CATEGORY_ID)


34/76

Use Validate Button


35/76

Use Validate Button


36/76

Action Raise Error and Display

Message


37/76

Save your Work and Try it Out

Navigate all the way out of the formEnsure Personalization Turned OnTurn it off if you get fatal Errors

Test it out while on queried records


38/76

Test our Work


39/76

Exception Raised Rule Enforced

When attempting to save the Record When ValidateRecord Event will Fire Error Message Displayed AsBelow


40/76

Change Back to Default -


41/76

Positive Results!


42/76

Case Two

We have two Sets of Corporate Books for Canada and the USWe need to keep assets in locationsassociated with proper countryWe have thousands of Locations in bothcountries Need to prevent transfer tolocations that are not in the countryassociated with the book


43/76

ResearchLocation Combination (Key Flex) had CountryEmbedded as one of the SegmentsNeeded to Enforce from QuickAdditions and

Additions Form Also Performed edits on Mass Transfers form, butnot illustrated in our presentationWant to make sure US in our Location Segment if inUS Book, CA if in Canadian Book


44/76

SQL Logic Compare Book to

Location Segment 2 (Country)

:ASSIGNMENTS_HEADER.BOOK_TYPE_CODE !=(select decode(a.segment2,'CA','SLC CANADA','US','SLC US

CORP')from fa_locations awhere:ASSIGNMENTS_DIST.LOCATION_ID = a.location_id)

It will Fail if the Country does not match the Book Name codedabove


45/76

Rule and Condition


46/76

Action Error and Fail


47/76

Results Locations Controlled


48/76

Case Three

Make Retirement Type Mandatory

Drives Reporting and Accounting for alldisposalsOut of the Box Retirement Type isOptional, and it is easy to forget to supplythis value Retirements Screen Mass Retirements Screen


49/76

Research

Retirements performed from Same AssetWorkbench in previous Example FAXASSETMass Retirements - FAXMAMRTRetirements LOVRetirement Type Field on Mass Retirements

MASS_RETIREMENTS.RETIREMENT_TYPE_DISP


50/76

Mass Retirement Form


51/76

Retirements Asset Workbench


52/76

Step One Rule and Condition

(Always)


53/76

Action Set Property of Field


54/76

Set Property LOV on Object


55/76

Set Property LOV on Property Name


56/76

Property Required =True


57/76

Results Yellow Field Indicates

Mandatory


58/76

REMINDER-

Be sure to leave and

return to form whiledebugging to ensureyour results are asexpected!


59/76

Case Four

Want to ensure Asset Description is AlwaysUppercaseEase of InquiryEase of ReportingCorporate StandardQuick Additions, Detailed Additions,


60/76

Research

Quick Additions

AdditionsSearch All are FAXASSET form (Workbench)


61/76

Create Rule and Condition


62/76

Create Action CASE_RESTRICTION -

Uppercase


63/76

Repeat Search from Workbench


64/76

Action- Search from Workbench


65/76

Results Uppercase Entry


66/76

Results Uppercase Query -Find


67/76

Level of Effort Required About one Day for these items

Takes time to research field names and tablerelationshipsTake time to testResults arent always positive first time


68/76

Personalizations very Powerful- ExceptRuntime Changes Only

Cannot create new items Cannot move items between canvases Cannot display an item which is not on a canvas Cannot set certain properties Cannot change frames, graphics, boilerplateCertain Events Only WHEN-NEW-FORM-INSTANCE, WHEN-NEW-BLOCK-

INSTANCE, WHEN-NEW-RECORD-INSTANCE, WHEN-NEW-ITEM-INSTANCE

WHEN-VALIDATE-RECORD (not in all forms) Product-specific events


69/76

Additionally - Other Business Rules

were implemented easily and quickly

Tag Number Mandatoryfor Equipment

Use of a Single UnitOnlyTax Types CantUpdate Corporate

BooksMass Retire Warn if No location -

Restriction on Update(who) can change a

Tag Number Prevent Review of Values for Art WorkPrevent certain

Categories of Assetsfrom being updatedexcept by Key users


70/76

Other Tips -Have a Naming Convention for Error Messages PERS-99 Not Allowed

FNDLOAD to move between instances (see Syntaxin Appendix)Tools Menu Personalization Adminstration

Allows search of Functions that have rules definedCheck before calling support with Forms bugs, SRsUpgrades/Patches will require research and testingForms can change (see Validate All from ToolsMenu)


71/76

In SummaryPowerful Tool

These Examples just scratch the surfaceBe willing to Experiment and be flexibleThere isnt always a custom event to attachto in every formCustom Development or 3 rd Party tools arenot always required


72/76

For More Information on

Personalization

If you are not familiar with the basic construct of anOracle Developer form, including terms such as

block, record, item, trigger, property and builtin , youshould consider a course such as Oracle Developer:Forms Fundamentals , offered by Oracle University.


73/76

Resources -Metalink Note 279034.1

Partner Training MaterialsPreviously Developed documentation writtenfor customers


74/76

About the Author Mark C. Clark, Senior Partner O2Works16 + Years with Oracle Applications Implementation and Upgrades Medium through Fortune 500 Large number of IndustriesImplementations through the GlobeContact [email protected] 972.466.2260
mailto:[email protected]:[email protected]


75/76

Appendix Move Between InstancesSyntax to Move Between Instances:Download:

FNDLOAD / 0 Y DOWNLOAD$FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES function_name=

Function_name is a required parameter; if it is not supplied thenno personalizations are downloaded.

Upload:FNDLOAD / 0 Y UPLOAD

$FND_TOP/patch/115/import/affrmcus.lct


76/76

Appendix Library v. Personalizations

Related to Custom LibraryLibrary - No need for Forms builder or Compile

Custom Library supports more complex PL/SQLThey both drive off same eventsPersonalization First First, Then Custom Libraryprocesses

Can use both at same timeUse Custom Library when personalizations notpowerful enough

Assets Personalization Presentation for Eastern States

Documents

Transcript of Assets Personalization Presentation for Eastern States