R12 OM Copy does not navigate to required field when OK button is clicked

Question

We are upgrading from 11.5.10 to 12.1.3.
When a user is copying a Sales Order to a Return in 11i and the user leaves the return reason blank, the form will navigate to the return reason and raise ORA-40202 Field must be Entered.
In R12, the navigation to the required field does not happen. The ORA-420202 is still raised, but the user must click through the tabs to find the return reason.
I have examined OEORDCPY.pll and found the procedure OE_ORDER_COPY_WINDOW.action_ok, which is called when the user clicks on the OK button.
The code below is from R12. Only the section for bug 4879216 is new since 11i. It is clear that the intent is for the form to navigate to the line type or return reason when they are missing (null, required, and enabled).
I have attempted to use forms personalization to navigate to the return reason, when it is missing. However, I could not get the desired result using when-new-item-instance or when-button-pressed as the trigger. Anyone have any suggesstions to correct this change in behaviour?
procedure action_ok IS
QUERY_HEADER_ID NUMBER;
BEGIN
/* Added for bug 4879216 */
validate(ITEM_SCOPE);
IF NOT FORM_SUCCESS THEN
raise form_trigger_failure;
END IF;
/* End of bug 4879216 */
OE_Navigate.g_exec_post_forms_commit:='N';
IF get_item_property('COPY.LINE_TYPE',REQUIRED) = 'TRUE' AND
get_item_property('COPY.LINE_TYPE',ENABLED) = 'TRUE' AND
     NAME_IN('COPY.LINE_TYPE') IS NULL THEN
--fnd_message.debug('go line type');
go_item('copy.line_type');
ELSIF get_item_property('COPY.RETURN_REASON',REQUIRED) = 'TRUE' AND
get_item_property('COPY.RETURN_REASON',ENABLED) = 'TRUE' AND
     NAME_IN('COPY.RETURN_REASON') IS NULL THEN
--fnd_message.debug('go return reason');
     go_item('copy.return_reason');
ELSE
--fnd_message.debug('copy');
OE_ORDER_COPY_MAIN.copy_main(QUERY_HEADER_ID);
END IF;
/* OE_ORDER_COPY_GLOBALS.G_HEADER_ID_TO_QUERY := QUERY_HEADER_ID;
hide_window('COPY');
go_block(OE_ORDER_COPY_GLOBALS.G_SOURCE_BLOCK_NAME);
app_special.enable('MODAL',PROPERTY_ON);
app_special.enable('file.save',PROPERTY_ON);
app_special.enable('file.accept',PROPERTY_ON);
END action_ok;

Answer 1

We have obtained a one-off patch from Oracle to address the issue. Is the patch available for public access? If yes, it would be great if you could share the patch number with us.
Thanks,
Hussein