INOB Issue while archiving WBS and Networks

[Former Member]

Hi All,

I am using PS_PROJECT archiving object for archiving WBS Elements and Networks. But during Write phase, below error message was dislplayed:

Error Message

There is no entry for instance 000000000001489184 in either INOB or IBase

Job cancelled after system exception ERROR_MESSAGE

Could you please help me when this error occurs and how to solve this problem.

Version: SAP R/3 4.7

Regards,

Sandeep

[jpfriends079 · Accepted solution]

Check tcode CUTABLEINFO and insert the instance number you have into the Instance(CUOBJ) field.

Be sure to check at the very least at the bottom of the screen the check boxes for IBINOBS and IBINOWN.

The owner of the configuration is the object that originated the instance.

An observer of the instance is simply an object that needed a copy of the characteristic values in the instance. If any transaction can find your instance's owner, it's this one.

Or

You can also refer SAP 1470060 - Error CX 074 (There is no entry for instance XXX in either INOB or IBase)

Hope it can assist you.

Thanks & Regards

JP

[Former Member · Accepted solution]

Hi JP,

I used CUTABLEINFO tcode and followed your instructions. But when executed I received message "Configuration does not exist in the folder". Please elaborate on this.

I had already tried the SAP Note 1470060 instructions but no useful results achieved.

Thanks for your help.

Regards,

Sandeep

[jpfriends079 · Accepted solution]

Check SAP

- Note 437921 - Display of configuration results (preferred)

- Note 1003264 - CUTABLEINFO: Unstructured output

- Note 1156136 - CUTABLEINFO: Characteristic name is not displayed completely

- Note 356513 - No info on blank configuration database

- Note 334338 - No information for empty configuration storage

- Note 823482 - Material variants and pricing

- Note 917987 - General performance in variant configuration

Hope it can assist you.

Thanks & Regards

JP

[Former Member · Accepted solution]

Hi JP,

Thanks for suggesting SAP notes but did not help much for solving the issue. There is a note number 418078 which seems helpful.

Regards,

Sandeep