10/31/2019 Document 2439356.

1
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Error The Effectivity Dates You Have Entered Are Overlapping With The Existing Dates For The
Component XXXX On The Bill For Revised Item YYYY occurs When Using ENG_ECO_PUB API For
Component Changes (Doc ID 2439356.1)
Modified: Aug 26, 2018 Type: PROBLEM

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Engineering - Version 12.1.3 and later

Information in this document applies to any platform.

SYMPTOMS

When doing a BOM update of the existing components, the following error occurs.

Error
The effectivity dates you have entered are overlapping with the existing dates for the component
&REVISED_COMPONENT_NAME on the bill for revised item &REVISED_ITEM_NAME.

Steps
The issue can be reproduced at will with the following steps:
1. Use the ECO api ENG_ECO_PUB for BOM components update by passing the relevant parameters.
2. Error occurs as mentioned above.

CHANGES

CAUSE

Per bug 9780939, due to a flaw in the code logic, the following error is occurring when user tries to update the BOM using the
change order API.
A function that is written in BOMLCMPB.pls to check if the same component is entered with overlapping dates is raising the
error message and failing the transaction.

Error Message
The effectivity dates you have entered are overlapping with the existing dates for the component
&REVISED_COMPONENT_NAME on the bill for revised item &REVISED_ITEM_NAME

Error Name
BOM_COMP_OPSEQ_DATE_OVERLAP

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=991spkm7j_406&id=2439356.1 1/2
10/31/2019 Document 2439356.1

References
Bug 9780939 - INT1213.4:ENG:GETTING ERROR WINDOW WHILE TRYING TO CHANGE THE REVISED COMPON QTY

SOLUTION

To implement the solution, please execute the following steps:

1. Download and review the readme and pre-requisites for Patch 9780939:R12.BOM.C.

2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Confirm the following file versions:

BOMLCMPB.pls version 120.43.12010000.14

You can use the commands like the following:

strings -a $BOM_TOP/patch/115/sql/BOMLCMPB.pls | grep '$Header'

5. Retest the issue.

6. Migrate the solution as appropriate to other environments.

REFERENCES

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=991spkm7j_406&id=2439356.1 2/2