UNILIN-UNIMAT: Wearers

Information About Wearers

Wearer identity is based on administration no within the customer scope resolved from the device.

The old source document used Unimat No., customer No. and Admin. No. together. In the current interface:

device number resolves the customer
administration no identifies the wearer inside that customer
wearer number remains descriptive source information

The customer number from the source row may still be present, but it is descriptive only. Device ownership decides the actual customer scope used for processing.

T.1 New Wearer

Purpose: Creates a wearer in the device-derived customer scope, or leaves the row as a no-op when that wearer already exists.
Valid for: All new wearers, with or without personal garments.
What happens when the row is read: The device is resolved first. The customer scope is then taken from that device. The system checks whether the wearer identity already exists in that customer scope.
If the wearer already exists: No business change is made.
If the wearer does not exist: A new wearer is created.
Note: This mutation shall be sent before personal garments are assigned to the wearer.

Fields:

Field Length Format Explanation

Field	Length	Format	Explanation
Mutation code	1	`1`	Always `1`.
Wearer number	15	alphanumeric	Laundry wearer number. Descriptive only in the current interface.
Administration no	10	numeric	Primary wearer identity within customer scope.
Wearer name	40	alphanumeric	Name displayed for the wearer.
Unimat number	3	numeric	Device number used to resolve customer scope.
Uniform number	2	numeric	Optional wearer-to-uniform reference. A non-empty and non-zero value means the row intends to connect this wearer to the matching uniform number in the device-derived customer scope. The interface resolves the link immediately if the uniform already exists, or later in the same file when an `A` row creates that uniform. If no matching uniform is ever created or found, the row is treated as an error.
Gender	1	alphanumeric	Optional wearer attribute.
Customer number	6	alphanumeric	Descriptive source value only.
Department	3	alphanumeric	Optional department attribute.
Max # of garments	3	numeric	Optional wearer limit for garments in use at the same time. In the current interface this is carried as the wearer limit field.
Personal code / card	-	current extension	Optional source attribute when supplied. In the current interface this is preserved as a wearer card when present.

Mutation code

1

Always 1.

Wearer number

alphanumeric

Laundry wearer number. Descriptive only in the current interface.

Administration no

numeric

Primary wearer identity within customer scope.

Wearer name

alphanumeric

Name displayed for the wearer.

Unimat number

numeric

Device number used to resolve customer scope.

Uniform number

numeric

Optional wearer-to-uniform reference. A non-empty and non-zero value means the row intends to connect this wearer to the matching uniform number in the device-derived customer scope. The interface resolves the link immediately if the uniform already exists, or later in the same file when an A row creates that uniform. If no matching uniform is ever created or found, the row is treated as an error.

Gender

alphanumeric

Optional wearer attribute.

Customer number

alphanumeric

Descriptive source value only.

Department

alphanumeric

Optional department attribute.

Max # of garments

numeric

Optional wearer limit for garments in use at the same time. In the current interface this is carried as the wearer limit field.

Personal code / card

current extension

Optional source attribute when supplied. In the current interface this is preserved as a wearer card when present.

T.5 Change Wearer Information

Purpose: Used for changes in wearer information.
Valid for: All wearers, with or without personal garments.
What happens when the row is read: The current wearer is resolved from device scope and administration no. In Q-Cloud 2 terms, this row behaves like a wearer upsert: the wearer is updated if it already exists in the device-derived customer scope, otherwise a new wearer is created from the row data.
If the wearer exists: The wearer information is updated.
If the wearer does not exist: The wearer is created from the provided data.
Note: Normal in-place updates are supported. Moving a wearer to another device should not be treated as a simple field change because device scope is authoritative. If the row carries a uniform number, that wearer-to-uniform relation is handled the same way as for T.1: it is applied immediately when the uniform already exists, or deferred until a later A row creates that uniform in the same file.

Fields:

Field Length Format Explanation

Field	Length	Format	Explanation
Mutation code	1	`5`	Always `5`.
Wearer number	15	alphanumeric	Existing laundry wearer number.
Administration no	10	numeric	Existing wearer identity.
Wearer name	40	alphanumeric	Updated wearer name.
Unimat number	3	numeric	Existing device number.
Uniform number	2	numeric	Updated wearer-to-uniform reference. The same resolve-or-defer rule applies as for mutation `1`.
Gender	1	alphanumeric	Updated wearer attribute.
Customer number	6	alphanumeric	Descriptive source value only.
Department	3	alphanumeric	Updated department.
Max # of garments	3	numeric	Updated garment limit.
New wearer no.	15	alphanumeric	Optional new source reference.
New Unimat No.	3	numeric	Optional new device reference from the legacy format.
New Customer No.	6	alphanumeric	Optional new customer reference from the legacy format.
New Admin. No.	10	numeric	Optional new wearer identity from the legacy format.

Mutation code

5

Always 5.

Wearer number

alphanumeric

Existing laundry wearer number.

Administration no

numeric

Existing wearer identity.

Wearer name

alphanumeric

Updated wearer name.

Unimat number

numeric

Existing device number.

Uniform number

numeric

Updated wearer-to-uniform reference. The same resolve-or-defer rule applies as for mutation 1.

Gender

alphanumeric

Updated wearer attribute.

Customer number

alphanumeric

Descriptive source value only.

Department

alphanumeric

Updated department.

Max # of garments

numeric

Updated garment limit.

New wearer no.

alphanumeric

Optional new source reference.

New Unimat No.

numeric

Optional new device reference from the legacy format.

New Customer No.

alphanumeric

Optional new customer reference from the legacy format.

New Admin. No.

numeric

Optional new wearer identity from the legacy format.

T.7 Delete Wearer

Purpose: Removes a wearer from the device-derived customer scope.
Valid for: Wearers with no garments remaining in use.
What happens when the row is read: The wearer is resolved in device-derived customer scope.
If the wearer exists and has no garments remaining: The wearer is deleted from the Q-Cloud 2 wearer register.
If the wearer exists and still has garments: The delete is rejected because garments are still in use.
If the wearer does not exist: No business change is made.
Note: This follows the same serious warning as the old source document: a wearer must not be deleted while garments still belong to that wearer. In the current interface, a missing wearer is treated as a no-op, but a wearer with garments in use is a hard error.

Fields:

Field Length Format Explanation

Field	Length	Format	Explanation
Mutation code	1	`7`	Always `7`.
Wearer number	15	alphanumeric	Laundry wearer number. Descriptive only.
Administration no	10	numeric	Primary wearer identity.
Unimat number	3	numeric	Device number used for customer resolution.
Customer number	6	alphanumeric	Descriptive source value only.

Mutation code

7

Always 7.

Wearer number

alphanumeric

Laundry wearer number. Descriptive only.

Administration no

numeric

Primary wearer identity.

Unimat number

numeric

Device number used for customer resolution.

Customer number

alphanumeric

Descriptive source value only.