Scribd
Upload
133 views2 pages

Applies To:: Cannot Replace Record Group With Form Personalization (Doc ID 763410.1)

This document discusses how to replace an existing record group in Oracle Order Management via form personalization. It provides steps to create a new record group through personalization using a SQL statement with bound or literal values. An example form personalization is given that changes the record group in a sales order screen according to customer provided information.

Uploaded by

Venkatesh Gurusamy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
133 views2 pages

Applies To:: Cannot Replace Record Group With Form Personalization (Doc ID 763410.1)

This document discusses how to replace an existing record group in Oracle Order Management via form personalization. It provides steps to create a new record group through personalization using a SQL statement with bound or literal values. An example form personalization is given that changes the record group in a sales order screen according to customer provided information.

Uploaded by

Venkatesh Gurusamy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

1/4/2015

Document763410.1

CannotReplaceRecordGroupWithFormPersonalization(DocID763410.1)
InthisDocument
Goal
Solution

Steps

Condition

Actions

Example

Condition

Actions

SQL

APPLIESTO:
OracleOrderManagementVersion11.5.10.2to11.5.10.3[Release11.5.10]
Informationinthisdocumentappliestoanyplatform.
Checkedforrelevanceon06Jan2010
***CheckedforRelevanceon11JUN2010***
***Checkedforrelevanceon14MAY2014***

GOAL
HowdoesonereplaceanexistingvanillarecordgroupinOEXOEORDviaformpersonalization?

SOLUTION
Pleasegothroughthebelowtocreaterecordgroupthroughpersonalizationproperly.
[Link]
[Link]
query,caremustbetakentoensurethatthecolumnnamesanddatatypesmatchwhatwasdefinedfortheLOV
thatisbeingchanged.
TheSQLmayreferencevaluesfromformfields,[Link]
featureshouldbetestedfromSQL*[Link]
thepersonalizationhasreferencestoboundvariables,substitutevaluesthatwouldnormallybeexpected.

Steps
TocreateapersonalizationtochangetherecordgroupusedbyanLOV,createanewpersonalizationasfollows:

Condition
TriggerEvent:WHENNEWFORMINSTANCElevel.
ProcessingMode:NotinEnterQueryMode.
SettheappropriateContextLevel.

Actions
#1
Type:Builtin
[Link]

1/2

1/4/2015

Document763410.1

BuiltinType:CreateGroupfromQuery
Argument:<theSQLstatementtobeused>
GroupName:<thenewrecordgroupname>
#2
Type:Property
ObjectType:LOV
TargetObject:<theLOVtousethenewrecordgroup>
PropertyName:GROUP_NAME
Value:<therecordgroupnamecreatedinactionstep1>

Example
ForExample,thefollowingformspersonalizationchangeswillchangetherecordgroupinthesalesorderscreen
accordingtocustomerprovidedinformation:

Condition
TriggerEvent=WHENNEWITEMINSTANCE
TriggerObject=ORDER.ORDER_TYPE

Actions
Property
ObjectType=LOV
TargetObject=Order_Type
PropertynameGROUP_NAME
Value=YF_OT
InBuiltin>CreateNewRG>Language/All>ENABLED
Builtintype=CreateRecordGroupfromQuery

SQL
InArgumentsectionpleaseusethefollowingSQL:
SELECTOTTT.TRANSACTION_TYPE_id,[Link],[Link]
FROMOE_TRANSACTION_TYPES_TLOTTT,OE_TRANSACTION_TYPES_ALLOTTA
WHERELANGUAGE=USERENV('LANG')
ANDOTTA.TRANSACTION_TYPE_ID=OTTT.TRANSACTION_TYPE_ID
ANDOTTA.TRANSACTION_TYPE_CODE='ORDER'
ANDOTTA.ORG_ID=136

[Link]

2/2

You might also like