My Oracle Support Banner

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 JULY 03, 2017

Applies to:

Oracle Product Hub - Version 12.1.3 and later
Information 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

  1. Profile "ENG: ALLOW AUTO-SUBMIT WORKFLOW" is Yes at Site level
  2. Create ECO from front end
    (N)PIM > Change Management > Create Change Order
    ==>Change Order Number : SAC-53699
  3. Create ECO using ENG_ECO_PUB.PROCESS_ECO API
    ==>Change Order Number : SAC-53700

  4. 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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.