ENG_ECO_PUB API Is Not Populating CHANGE_NOTICE_PREFIX and CHANGE_NOTICE_NUMBER in ENG_ENGINEERING_CHANGES
(Doc ID 2283047.1)
Last updated on MAY 12, 2020
Applies to:
Oracle Product Hub - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
CHANGE_NOTICE_PREFIX and CHANGE_NOTICE_NUMBER columns in ENG_ENGINEERING_CHANGES table are not getting populated
when creating the change order through ENG_ECO_PUB.PROCESS_ECO API.
ECO number is getting generated by API automatically. Also there is no input value for CHANGE_NOTICE_PREFIX and CHANGE_NOTICE_PREFIX as a input parameter while running API.
Expected Behavior
CHANGE_NOTICE_PREFIX and CHANGE_NOTICE_NUMBER columns in ENG_ENGINEERING_CHANGES table are getting populated
when creating the change order through ENG_ECO_PUB.PROCESS_ECO API.
Steps to Reproduce
- Profile "ENG: ALLOW AUTO-SUBMIT WORKFLOW" is Yes at Site level
- Create ECO from front end
(N)PIM > Change Management > Create Change Order
==>Change Order Number : SAC-53699 -
Create ECO using ENG_ECO_PUB.PROCESS_ECO API
==>Change Order Number : SAC-53700 -
Check ENG_ENGINEERING_CHANGES
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |