Characteristic Set page

Use the Characteristic Set page to set up the specific characteristics for a customer facility.

Used By

The customer accounts and customer facilities currently assigned the characteristic set. Before updating a characteristic set, ensure that the changes are accurate for all customers and facilities that are assigned the characteristic set.

Characteristic Set Name

The name used to identify the characteristic set.

Line Item Key

The demand traits that define a line item on shippers and ASNs. All demand that shares the same line item key will display as a single line item. This field can have these values:

Part Only. Part number is the only determining factor.
Part and Pull Signal. Items sharing both part and pull signal will be included in the same line item. If part is the same, but pull signal is different, the requirements will not share a line item.
Part and PO. Items sharing both part and purchase order number will be included in the same line item. If part is the same, but purchase order number is different, the requirements will not share a line item.

List Pull Signals on Shipper

Whether pull signals display on shippers and ASNs if they are included in the demand. If this check box is selected, the Pull signals display.

List POs on Shipper

Whether PO numbers display on shippers if they are included in the demand. If this check box is selected, the PO numbers display.

Definition

The container types for which suppliers must provide information. This field can have these values:

None. Container information is not required and cannot be included on shippers.
Detail. Container information is required at the detail level (the individual containers included in a larger box or pallet and loose containers). Each detail container can contain parts from only a single line item on the shipper.
Both. Both master and detail container information is required. Depending on the Allow Mixed Containers flag, master containers can contain detail containers for multiple line items.

Serial Numbers on Shipper

The container types for which suppliers must provide serial numbers. This field can have these values:

None. Serial numbers are not required and cannot be entered.
Detail. Serial numbers are required only for detail containers.
Both. Serial numbers are required for both detail and master containers.

Allow Mixed Containers

Whether suppliers can send shipments of mixed containers. Mixed containers contain parts from multiple line items on the shipper. Available only if the Container Definition is Both. If this check box is selected, suppliers can group containers on the shipper to indicate that detail containers containing parts from different line items are being sent within the same master container. If this check box is cleared, suppliers cannot mix containers and the Group Containers feature is turned off.

Ship Schedule Reject Level

The level of demand (schedule or requirement) at which suppliers can reject demand. If customers send both Material Releases and Shipping Schedules, the ability to reject is for Shipping Schedules only. This field can have these values:

None. Suppliers cannot reject requirements.
Requirement Level. Suppliers can reject individual requirements.
Schedule Level. Suppliers can reject entire schedules only. They cannot reject only particular requirements on a schedule.

VAN Send Independent of Storage

Whether the demand file is sent to a VAN regardless of Supplier Exchange storage. (When an inbound file cannot be stored, an email notification is sent to the contact that is specified on the Computer Profile page.) If this check box is selected, the file is sent to the VAN even when a file store is not complete. If this check box is cleared, the send is aborted if a file store is not complete.

Add PO Number

Whether PO is a trait that defines demand.

Add Eng Change Level

Whether engineering change level is a trait that defines the demand key.

Add Model Year

Whether model year is a trait that defines demand.

SMI Signal

If this check box is selected, the extended demand key is applied to the SMI module. The inventory is updated with purchase order number/model year/engineering change level accordingly when the SMI part is created or updated. If this check box is cleared, the purchase order number/ model year/engineering change level of an SMI part are not updated.

Material Release

The strategy used to replace material release demand schedules. This field can have these values:

None. Material Release documents are not sent.
Implicit by Facility. When a schedule is sent, all current schedules for the facility are removed and the new schedule becomes current.
Implicit by Facility/Demand Key. When a schedule is sent, all current schedules for the facility and demand combination are removed and the new schedule becomes current.
Implicit by Facility/Supplier. When a schedule is sent, all current schedules for the facility and supplier combination are removed and the new schedule becomes current.
Explicit. Schedules must contain a purpose code indicating whether the existing schedule is to be replaced, modified, or cancelled.
Augment Schedule. Only one schedule is kept. Any requirements sent are added to the existing schedule.

Kanban Signal

If Kanban is turned on for the customer, Augment Schedule must be selected.

Shipping Schedule

The strategy used to replace daily or just-in-time demand. This field can have these values:

None. Shipping Schedule documents are not sent.
Implicit by Facility. When a schedule is sent, all current schedules for the facility are removed and the new schedule becomes current.
Implicit by Facility/Demand Key. When a schedule is sent, all current schedules for the facility and demand combination are removed and the new schedule becomes current.
Implicit by Facility/Supplier. When a schedule is sent, all current schedules for the facility and supplier combination are removed and the new schedule becomes current.
Explicit. Schedules must contain a purpose code indicating whether the existing schedule is to be replaced, modified, or cancelled.
Augment Schedule. Only one schedule is kept. Any other requirements sent are added to the existing schedule.

SMI Signal

You must select Augment Schedule when the SMI Signal is selected for the customer. The Augment Schedule option indicates the strategy used to replace demand when the replacement is triggered by an SMI (Supplier Managed Inventory) signal.

Use CUM Management

Whether CUMs will be used to track requirements for Material Releases and Shipping Schedules. If CUM Management is used, open quantities will be determined based on CUM quantities.

Material Release CUM Method

The strategy used to send and track CUM data for Material Releases. This field can have these values:

CUM to Net. Cumulative quantities are sent as demand. Actual required quantities are calculated based on the CUM required and CUM received.
Net to CUM. Actual required quantities are sent as demand. CUM quantities are calculated by the system.

Shipping Schedule CUM Method

The strategy used to send and track CUM data for Shipping Schedules. This field can have these values:

CUM to Net. Cumulative quantities are sent as demand. Actual required quantities are calculated based on the CUM required and CUM received.
Net to CUM. Actual required quantities are sent as demand. CUM quantities are calculated by the system.

Create Pseudo Requirement For Behind Schedule

Whether the application generates a past due requirement to account for behind status when a new schedule is published. If selected, when CUM Required is greater than CUM Shipped when a new schedule is published, a requirement is added to the schedule for the difference (CUM Required - CUM Shipped) with the previous day as the due date. If not selected, the first requirement of the schedule remains as the first requirement.

CUM Basis for Material Release

The field used to determine the previous CUM (CUM Required Prior) for the schedule. In the XML API file, CUM Received Prior maps to cum_required_qty or cum_required_prior_qty, and CUM Received (YTD) maps to cum_received_qty or cum_received_prior_qty.

CUM Basis for Shipping Schedule

The field used to determine the previous CUM (CUM Required Prior) for the schedule. In the XML API file, CUM Required Prior maps to cum_received_prior_qty or cum_required_prior_qty and CUM Received (YTD) maps to cum_received_qty.

CUM Shipped (YTD) Owner

The entity responsible for updating the CUM Shipped quantity. This field can have these values:

Supplier-Internal. The application updates and maintains CUM Shipped based on ASNs and manual adjustments.
Customer-External. CUM Shipped is updated based on the customer defined CUM Shipped quantity in inbound schedules.

Additional CUM Fulfillment

The fulfillment strategy used when CUMS is applicable. This field can have these values:

None. When schedules are republished, the in-transit quantity and the quantities in staged shippers are not considered for fulfillment.
In-transit Shippers. When schedules are republished, the in-transit quantity is used in the calculation of Due Qty. and CUM Shipped (YTD) fields of the Schedule.
In-transit and Staged Shippers. When schedules are republished, the in-transit quantity and the quantity in staged shippers are used in the calculation of the Due Qty. and CUM Shipped (YTD) fields of the Schedule.
Staged Shippers. When schedules are republished, the quantity of the staged shippers is used in the calculation of the Due Qty. and the CUM Shipped (YTD) fields of the Schedule.

The field is enabled only when the CUM Shipped (YTD) Owner field is set to Customer-External.

New Schedule Fulfillment

How the line items on staged or in-transit shippers are used to fulfill demand when new schedules are published or cancelled by the customer.

None. All shippers are applied to the schedule to which they were originally applied regardless of new publishes or cancellations.
Staged Shipments. When new schedules are published, line items on staged shippers are applied to the new schedule. When schedules are cancelled, line items on staged shippers that were applied to a cancelled schedule are applied to the previous schedule or must be manually updated in the Update In-Transits Supplier page.
In-transit Shipments and Staged Shippers. When new schedules are published, line items on staged and in-transit shippers are applied to the new schedule. When schedules are cancelled, line items on staged or in-transit shippers that were applied to a cancelled schedule are applied to the previous schedule or must be manually updated in the Update In-Transits Supplier page.
Classic. When new schedules are published, the fulfillment from the previous schedule is moved forward to be applied to matching requirements on the newly published schedule.

Partial Ship Complete

Whether partial shipments fully fulfill entire requirements. If this check box is selected, the entire requirement is considered fulfilled and cannot be further shipped against, when a shipment partially fulfills a requirement. If this check box is cleared, the requirement's entire required quantity must be shipped against for it to be fulfilled.

VAN Send Reconciled Releases

Whether the release files sent to the VAN are updated using the fulfillment strategy. If this check box is selected, the releases sent to the VAN are updated based on the fulfillment strategy to match the requirements in the Supplier Exchange database. If this check box is cleared, the releases sent to the VAN match the documents published by the buyer.

Allow Discrete PO Negotiation if Shipment Has Occurred

Whether suppliers can initiate negotiation for discrete POs that have already been shipped against.

Supplier Can Initiate Discrete PO Negotiation

Whether suppliers can begin the negotiation process for published discrete POs.

Generate PO Acknowledgment for Proposed PO

Whether an acknowledgment is generated when proposed POs are sent (imported).

Supplier Acceptance Requires Customer Approval

Whether customers must approve items after suppliers have accepted them. If selected, customers must approve accepted items before discrete POs can be generated from the proposed POs. If not selected, discrete POs can be generated from proposed POs when all items have been accepted by the supplier.

Allow Shipment During Discrete PO Negotiation

Whether suppliers can ship against discrete POs that are under negotiation.

Generate Discrete PO From Finalized Proposed PO

Whether discrete POs are automatically generated from proposed POs that have been fully accepted by suppliers and approved by customers. If selected, discrete POs are automatically generated from proposed POs. If not selected, customers must send (import) discrete POs after the proposed POs are finalized.

Generate PO Acknowledgment For Discrete PO

Whether an acknowledgment is generated when discrete POs are sent (imported).

Allow Backorder for PO

Whether the supplier is permitted to back order purchase order (MRO) demand. If this check box is selected, the supplier can back order purchase orders. If this check box is cleared, the supplier cannot back order purchase orders and the Backorder button and field are not active on the purchase order pages.

Generate Ack (997)

Whether an Acknowledgment (997) is sent to the supplier to confirm that the ASN has been received by the customer. If this check box is selected, 997s are automatically generated. If this check box is cleared, 997s are not sent.

Pull Signal UI Label

The label used in the application for the data sent in the pull signal field.

PO Reject Level

The level (none, header, or line item) at which suppliers can reject purchase orders.

Receipt Status Code

Indicates the type of receipt documents that are sent. This field can have these values:

Explicit. A receipt includes all parts received in the shipment.
Exception. A receipt includes only parts received in the shipment for which there were discrepancies (rejected or missing parts). The parts not included on the receipt document but which were included in the shipment (as indicated by the ASN) are considered to be received in full without discrepancies.

Custom ASN Class Name

The name of the file containing any customer-defined ASN validations not handled by the generic process. If ASN validations are to be performed that are not covered by the generic validation, a custom ASN class must be created by developers.

Logo File

The file containing the customer's logo. If specified, the logo displays in the application and is in printed reports generated by the application. To link the form to the system, click Browse to navigate to the form.

Do Not Close Discrete POs On Shipper Publish

Whether POs are closed when the line items are fulfilled by shipping. If this check box is selected, POs are not closed. To close out POs, the customer must send a cancellation PO to move the PO to Cancelled status. If this check box is cleared, POs are moved to Closed status when the requirements are fulfilled by the supplier's ASN publish.