FAQs: Working with Distribution Segments

What are distribution segments?

A distribution segment allows the library to define the eventual destination of funded copies. Ordered material may be assigned a library holding code or may be routed to an external agency or user. Distribution segments belong to a funding segment. Several distribution segments can belong to a single funding segment. All distribution segments contain ship, number of copies, date received, and packing fields.

There are three kinds of distribution segments.

Holding Distribution – Allows you to designate the location to which the copies should be distributed. A holding distribution segment additionally contains Holding Code and Loaded fields.
User Distribution – Allows you to specify a user ID for sending the received materials to a designated department or person. A user distribution segment additionally contains User ID and Delivered fields.
Multi-Volume Distribution – Allows you to receive partial sets by volume or part name. A multi-volume distribution always belongs to another distribution segment, either a user distribution or a holding distribution. The multi-volume distribution segments are typically generated automatically by SirsiDynix Symphony when a partial order of volumes is received. A multi-volume distribution segment additionally contains a parts field. When you receive a multi-part set, the names of parts received must be noted in the received field. You must also type the unreceived volumes for the volume distribution for unreceived issues in the orderline to be properly created.

How do I add an orderline with a simple holding distribution?

Most small libraries will order copies from a single fund with a single distribution. In fact, the default segment created for new orders supports this funding/distribution scenario.

How do I add an orderline with a simple basic user distribution?

To create a simple single user distribution

How do I distribute one orderline’s copies to multiple locations or users?

Often, libraries buy two copies of the same title, one for general shelving and one for the Reference area.

Note: When modifying existing segments, be certain to remove the entire segment cluster (all related fundings/distributions).

How do I distribute an orderline to only one location if it is split among multiple funds?

In the following example, you are purchasing a $600.00 reference book for the Reference Department and splitting the cost, by amount, between two funds.

Note: When modifying existing segments, be certain to remove the entire segment cluster (all related fundings/distributions).

Note: You are required to designate one fund as a “REST” fund. A fund with this designation will absorb any increases in costs as items are received and invoiced.

How do I distribute multiple copies to one location if purchased from multiple funds?

Libraries often buy multiple copies of a title, but from different funds, even though they are for the same library or department.

Note: When modifying existing segments, be certain to remove the entire segment cluster (all related fundings/distributions).

When I try to create or edit an orderline, a message about the fund cycle not having library authorization for the library of the distribution holding code displays. What does this message mean?

In multilibrary systems that use the Fund Library Authorization policy, each fund cycle‘s library authorization is compared to the holding code library in the associated holding distribution(s). The library of each holding code must be present in the fund cycle’s library authorization. When the holding code library is not authorized in the associated fund cycle, the following message displays.

This fund cycle does not have library authorization for the library of the distribution holding code.The message lists the fund ID and the holding code name that did not pass validation. When the message window is closed, the insertion point will be placed in the first fund ID field that did not pass validation. An invalid fund cycle/holding code pair will not be saved.

Note Library authorization is done only for holding distributions. Library authorization is not used for user distributions.

Related topics