Is it possible to deactivate the required field Need by Date in Sourcing Line?

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem: Is it possible to deactivate the required field Need by Date in Sourcing Line?



Solution:

I have done a research of this issue and have found following explanation on this issue:
quote
Adding the comments for clarification on why this change was made
.
Currently, need by dates are not required in the create flow, but Promise
date is always required in the bidding flow if the outcome is Standard
Purchase Order.
We want to relieve the restriction that promise date is required in the
bidding flow, as it turns out that PO does not require it all the time. PO
requires need by date or promise date only for certain types of items.
.
Solution:
In the create flow, if the line has an inventory item that is a "planned"
item, EITHER the need by from OR the need by to date is required. If it is
a one item in sourcing or if the inventory item is NOT a planned item, we
should keep these 2 fields optional.
.
In the bidding flow, we should always try to default the promise date to the
'need by to' date, if that is null then default the 'need by from' date. If
both are null, promise date remains null. The ONLY case the promise date
will be required is when the need by dates are scored.
.
For the create po process, we should be passing in both the need by dates on
the line as well as the promise date on the bid, so we are okay. PO's
autocreate API will work if either one of these fields are entered, if the
item is a planned item as per the PO logic.
.
An item is a "planned item" if in MTL_SYSTEM_ITEMS table,
INVENTORY_PLANNING_CODE in (1, 2) or MRP_PLANNING_CODE in (3, 4, 7, 8, 9)
.
Also, for bidding by spreadsheet
The * next to the Promise date column will be removed and the current tip to
indicate when promise date is required will still be there(* next to line
number if required/ # if optional). The logic to show the '*' next to the
line number if promise date is required will change based on the above new
conditions.
unquote

So Development has made here a change which cannot be changed by personalization.
This only can be done via code change.
There is already existing an Enhancement Request:
ER 5066191 : NEED-BY DATE REQUIRED ERROR SHOULD BE MORE DESCRIPTIVE
quote
1. PROBLEM DESCRIPTION:
When creating an RFQ and adding items like CM13139 that have
attributes such as "inventory planned" (or whatever it's called)
you get an error message stating that "need-by date is required
for line X." This is confusing for the end user, especially
because the field is not visibly marked as required.
2. EXPECTED BEHAVIOR:
The system should either dynamically mark the field as required
based on the item chosen or at least provide a more descriptive
error message (eg, "need-by is required for line X because the
selected item is inventory planned.").
unquote
See that this will be implemented in R15.

Get Oracle Certifications for all Exams
Free Online Exams.com