• Article Type: General
• Product: Voyager
• Product Version: 8.1.2

Description:
Bug Report Form for Issue 16384-14337

Module(s): Acquisitions/EDI
Server platform(s) affected: Solaris/all
PC OS (if applicable): n/a
Browser & version (if applicable): n/a
Release(s): reported/replicated in 7.2.4

Expected results:
Even if an issue is non-predictive, a valid SICI should be constructed when that issue is claimed via EDI.

Actual results:
If the issue is non-predictive, when the EDI message is created, the SICI consists of only the issue’s enum/chron information.

Workflow implications: Some vendors can’t process the EDI file sent to them if there’s an invalid SICI.

Replication steps:
Create a component and in Subscription Maintenance, go to the Non-Predictive tab and enter in issue information for two issues.
Search for this component in Serials Check-in and check in the *second* issue.
Go to the Problems tab in the Serials History for this component – you’ll see the first issue.
Select this issue and click Generate Claim.
In the Generate Claim box, check off Send Claim via EDI and hit OK.
Go to EDI>Process EDI Messages>Outgoing tab.
For your Search By, specify Update Date, supply today’s date and click Find.
Highlight the message this brings up, click in the far right of the Message Number column and click the ellipsis that appears.
Find the line for your claim and look at the PIA – you’ll see something like this:
PIA+5+issue 1:SI::28
Note that this *only* includes the text of the enum/chron, not anything like ISSN, etc.

Resolution:
Fixed in Voyager 8.1.2.

• Article last edited: 3/18/2015