8/12/2019 How to Change Requisition Description Default Value on Checkout Form

1/2

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

How To Change Requisition Description Default Value On Checkout FormIn this Document

APPLIES TO:

Oracle iProcurement - Version 11.5.10 to 12.1.3 [Release 11.5 to 12.1]Information in this document applies to any platform.

GOAL

On the consolidated checkout form of iProcurement delivered in 11.5.10 / Supply Chain ManagementFamily Pack J, the field Requisition Description defaults with the value of the first line item description.

In prior releases this was blank. How to change the default value for the requisition description so that itis set to default to blank or null?

SOLUTION

This is the product intent as delivered with 11.5.10.

The customization for the Initial Value for the Requisition Description is not possible via personalizations.Also, there is no option via customization of the POR_CUSTOM_PKG package to populate this with a

default value.

An Enhancement Request (ER) has been submitted to Oracle Development.

ER:Bug 4705084- REQUISITION DESCRIPTION DEFAULT VALUE

This ER will be reviewed and considered by Development for a future release. It will remain open until it

is either incorporated into the product, or it is deemed not feasible.

Progress on ER:Bug 4705084can be monitored in My Oracle Support as follows:

1) In the upper right corner there is a "Search Knowledge Base" field.2) Enter the Bug Number in that field and click the Find (hourglass).3) In the returned Knowledge Browser field click on the double down arrow key to show AdvancedSearch fields.

4) In the Source drop down field uncheck Knowledge Base and check Bug Database and then click Close.5) Click on Search button.

6) On the Bug number that is returned, click on the Star icon to the left to add as a Favorite.

7) In the Favorites drop down menu (in the upper right) under the Bugs drop down choice, this ER isnow listed.

Reference:Note 841907.1- How To Monitor Bugs And Enhancement Requests Via My Oracle Support

Below is a list of ER related status values, and what each status represents:

12 - To External (User Group) Review

https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/DocumentDisplay?id=841907.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=841907.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=841907.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=841907.1https://support.oracle.com/epmos/faces/BugDisplay?id=4705084https://support.oracle.com/epmos/faces/BugDisplay?id=4705084

8/12/2019 How to Change Requisition Description Default Value on Checkout Form

2/2

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

15 - Enhancement Req. Internal(Oracle) Review

22 - Approved for Future Release23 - Scheduled for Future Release

Oracle makes every effort to listen to you, our customer, and shape our products accordingly. Althoughwe are unable to follow-up directly or implement all new functionality requests, Development does review

and prioritize these requests on a regular basis. Selected new functionality may be implemented insubsequent releases based on a number of factors, including feedback from the Product Advisory Council(PAC).