New vendor record error: "co1043 - duplicate nn - Vendor does not exist".

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We recently loaded vendor records into the file using p_file_04. When users attempt to add vendor records through the client, we get an error message, "co1043 - duplicate 34 - Vendor does not exist". Vendor record is not visible in client, but can be seen in sql (and in fact I was able to add it twice):

select * from z70 where Z70_REC_KEY like 'LLMTEST%'
Z70_REC_KEY Z70_REC_KEY_2 Z70_EDI_VENDOR_COD
------------------------- ----------------------------------- ------------------
LLMTEST
LLMTEST
2 rows selected

The server log does not include any information pointing to errors in the z70 or z72:

Is there a way to check that p_file_04 created all necessary oracle indexes?

Resolution:
util a/17/14 for the z70 shows that, though it is in the file_list, the z70_id is *not* in the " Exist in the Database" list.

You need to do util a/17/2 to build the z70_id.

I suspect that you used p_file_04 with "Procedure to Run" Append.

The $aleph_proc/p_file_04_1 drops the table's Oracle index when the Append option is specified.

It seems that your p_file_04 included records which were duplicates of existing z70 records, and this prevented the z70_id index from being built successfully at the end of p_file_04. (An error to this effect should appear in the p_file_04 log.)

You will need to use util a/17/18 to delete the duplicate z70's and build the index (instead of a/17/2).

KB 8192-424 describes the use of util a/17/18.

• Article last edited: 10/8/2013