How To Investigate Error: Instance Cannot be marked as Creation Complete (Doc ID 972935.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Installed Base - Version 11.5.10 to 12.2.4 [Release 11.5 to 12.2]
Information in this document applies to any platform.

Goal

This datafix has been approved by development for Customer consumption 27-Apr-2012.

IMPORTANT: The information contained in this document may contain omissions, inaccuracies or other errors. It is provided "as is" and without warranty. Oracle does not warrant that the information in the materials is up to date or error free, nor does it provide any other warranties, whether expressed or implied in law, including the implied warranties of merchantability or fitness for a particular purpose. The materials are not a program or documentation under the terms of your license agreement(s) with Oracle. In no event shall Oracle be liable for any direct, indirect, incidental, special or consequential damages, or damages for loss of profits, revenue, data or use, incurred by you or any third party, whether in an action in contract or tort, arising from your access to, or use of, this information.

If you have any questions or concerns please contact Oracle Support before running the script.

 

This Note is about how to investigate the cause of IB transaction error message:

CSI_API_INVALID_ATTRIBUTES - 'Instance Cannot be marked as Creation Complete, because one or all of the following mandatory params are not available: Serial Number (If Serialized),  Lot Number (If Lot Controlled),  Revision (If Rev Controlled),  Instance Location,  Instance Status.'

This error message is notorious for its difficulty to find out what is wrong. The error can occur for different reasons. The 'missing' data can be about serialnumber, lotnumber or revision control. The error can occur for a parent instance or for one of it's children. The 'missing' information can be missing from the material transaction, the installation details or the IB data in csi_item_instances. The error message does not provide information on what information is missing from where.

This note gives instructions on how to modify the standard code to include some debug code that will provide the necessary information. This will be required until <Bug 9174592> is accepted and implemented in the standard code by InstallBase development.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms