7/22/2019 How to Use Forms Personalization to Restrict Values in Customer Number LOV in Sales Order Form OEXOEORD

1/2

Junaid Iftikhar Ahmed | Sr.Oracle Solution Architect & PM| BCS-SE, MBA-FIN, SCM-EXP1

How to Use Forms Personalization to Restrict Values in Customer NumberLOV in Sales Order Form OEXOEORD

MODULE:

Oracle Order Management

PROBLEM STATEMENT

The goal is to meet the requirement to restrict/limit the values in the Customer Number field LOV (List ofValues) in the sales order form using Forms Personalizations.

SOLUTION

The following is an example of how this can be set up.

1. Go to the Forms Personalization screen from the sales order form (Help>Diagnostics>CustomCode>Personalize).

2. Enter the following in the Condition tab.

Trigger Event = WHEN-NEW-ITEM-INSTANCETrigger Object = ORDER.CUSTOMER_NUMBER*Note this example is for the Customer Number field, not the Customer field.

Context (if restricting to a specific user):Level = UserValue =

3. Enter the following in the Actions tab. Here we have two sequence lines. We are restricting the

Customer Number LOV to only show account_number=1608.

Seq 10, Type = BuiltinBuiltin Type = Create Record Group from Query

Argument =select acct.account_number account_number, acct.account_name account_description,

party.party_number registry_id, party.party_name party_name,party.party_type, acct.cust_account_id cust_account_id,party.email_address email_address, nvl(party.gsa_indicator_flag,'N') gsa_indicatorFROMHZ_PARTIES PARTY, hz_cust_accounts acct WHERE (ACCOUNT_NUMBER = 1608) AND(acct.party_id=party.party_id AND acct.status='A' ) order by party_name

*Note, in order to build this statement, we first took a trace (Help>Diagnostics>Trace>Trace with Binds)

of the action to invoke the Customer Number LOV 'before' setting up the Forms Personalization. Wecreated this sql statement in the same way as the statement seen in the trace file, but replacing the

7/22/2019 How to Use Forms Personalization to Restrict Values in Customer Number LOV in Sales Order Form OEXOEORD

2/2

Junaid Iftikhar Ahmed | Sr.Oracle Solution Architect & PM| BCS-SE, MBA-FIN, SCM-EXP2

WHERE condition for the account_number with an actual value that we wanted to restrict the LOV. We

found that if the sql entered in the Argument field was missing one of the selected columns, for example,'nvl(party.gsa_indicator_flag,'N') gsa_indicator', the LOV restriction did not happen. Hence, if the setup in

this note is not working, it is recommended to take similar troubleshooting steps by generating a tracefile.*There is no semicolon at the end of the statement.

Group Name = TEST_FOR_OEXOEORD--

Seq 20, Type = Property

Object Type = LOVTarget Object = CUSTOMER_NUMBERProperty Name = GROUP_NAMEValue = TEST_FOR_OEXOEORD

Let us know your feedback!We hope you find this information useful. Our desire is to provide the right information when you need it.

Please let us know how we are doing. To provide feedback on this note:

1. Select the "Rate this document" link. Depending on how you are viewing the note, you will find the link

on the:a) bottom left when viewing the note in a separate window.b) upper right when viewing the note in the My Oracle Support window.

2. In the resulting pop-up box, enter your comments and ratings for the document.

3. Select Send Rating.