Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    BULK: Bad data in first record of imported file prevents creation of PO

    • Article Type: Known Issue
    • Product: Voyager
    • Product Version: 8.1.0
    • Relevant for Installation Type: Total Care; Dedicated-Direct; Direct; Local

    Symptoms

    • When a bulk import rule is set to create a PO, and a record in an import file:
      • has more characters than what is allowed in the database; and
      • is the first record in the file

    then the PO line items for the subsequent records are created, and it looks as if the PO is created, but the PO is not created, and the line items are orphaned in the database.

    • If the bad data is not the first record in the file, the import behaves as it should: PO is successfully created, line items for valid records are created, and the line item for the bad record is rejected.

    Defect Status

    Issue 16384-18401 / VYG-628 is resolved for Voyager 8.1.2 and higher.

    Replication steps

    1. Set up a bulk import rule with the following:
      • Profiles > Single MFHD > Bibs, Mfhds, POs (see screenshots)
      • There are 2 record files attached. Both of them contain a bib record with a print note that exceeds the allowable character limit in the Voyager database (103 characters; Voyager limit for line_item_notes.print_note is 60 characters).
    2. Import the file ImpWithBadNotes.mrc.
    3. The following will be logged in the log.imp* file:
    ::::::::::::::
    I am 26744.  I will be doing all of '/m1/incoming/amy/ImpWithBadNotes.mrc' for you.
    The import code is "ARUP" for this run.
    Selected import rule is for use with loading embedded order data.
    The Bib dup profile is "OCLCUnconditional" for this run.
    This import is using a rule that allows for creating Bibs and MFHDs.
    This import is using a rule for copying MARC21 holdings fields from bibs to MFHDs.
    Warning:No cat_control_barcode profile found for [ARUP].
    Using Acquisitions Desk as the Order Location.
    Expecting 'U' as character set
    Tue May  1 13:29:00 2012
    1(1):Duplicate Bibs above threshold: replace 0, warning 0.
            Adding Bib record 75868.
    no PO Number information found in bib.
     Purchase Order Number: 996
    MFHD_ID 74673 created.
    no ledger found in bib; using default ledger.
    no fiscal period found in bib; using default fiscal period.
    Warning!  No Notes information found in bib.
    Warning! Unable to find  vendor title field
    Warning!  No Piece ID information found in bib.
    Fail to create line item.
    Error in creating line item.    bib id: 75868, mfhd id: 74673
    2(2):Duplicate Bibs above threshold: replace 0, warning 0.
            Adding Bib record 75869.
    MFHD_ID 74674 created.
    no ledger found in bib; using default ledger.
    no fiscal period found in bib; using default fiscal period.
    Warning!  No Notes information found in bib.
    Warning!  No Instruction information found in bib.
    Warning! Unable to find  vendor title field
    Warning!  No Piece ID information found in bib.
    3(3):Duplicate Bibs above threshold: replace 0, warning 0.
            Adding Bib record 75870.
    MFHD_ID 74675 created.
    no ledger found in bib; using default ledger.
    no fiscal period found in bib; using default fiscal period.
    Warning!  No Notes information found in bib.
    Warning!  No Instruction information found in bib.
    Warning! Unable to find  vendor title field
    Warning!  No Piece ID information found in bib.

    BIBLIOGRAPHIC, MFHD, ITEM or AUTHORITY Records
    Processed:     3
    Added:         3
    Discarded:     0
    Rejected:      0
    Errored:       0
    Replaced:      0
    Merged:        0
    Deleted:       0
    Mfhds created: 3
    Items created: 0
    Error in reconcile purchase order

    Purchase Order Number: check log
    Number of PO Created:   1
    Number of PO Approved:  0
    Number of Line Item Processed:  3
    Number of Line Item Rejected:   1
    Number of Line Item Inserted:   2
    Tue May  1 13:29:07 2012


    Result:

    • LINE_ITEM table has 2 line items associated with the PO, but no corresponding rows in PURCHASE_ORDER.
    • In Acquisitions, will not be able to find PO number 996.
    • Line item data not accessible in clients

    Workaround

    Verify data integrity of first record in record file when create POs with bulk import.


    • Article last edited: 3/2/2015