Struct Contrl 

pub struct Contrl { /* private fields */ }

A CONTRL message under construction.

Build one with receipt, acknowledgement, or from_report, then render it with segments or to_edifact_string.

The message reference defaults to the subject interchange’s control reference, which keeps a CONTRL traceable to what it answers without the caller having to invent one; override it with with_message_reference.

Implementations

impl Contrl

pub fn receipt(interchange: &InterchangeEnvelope) -> Self

The receipt message of ISO 9735-4 §5.3.1 — action code 8.

Says only that the interchange arrived. It carries no per-message reporting, because nothing has been checked yet.

pub fn acknowledgement(subject: &ValidatedInterchange) -> Self

Acknowledge a clean interchange — action code 7 throughout.

Every message is acknowledged implicitly by the UCI, so no UCM is emitted: §5.3.4 makes explicit acknowledgement of every message redundant when the interchange level already says so.

pub fn from_report( subject: &ValidatedInterchange, segments: &[Segment<'_>], report: &ValidationReport, ) -> Self

Report the outcome of a validation run.

segments is the subject interchange as parsed — it is what turns an issue’s byte span into the segment position UCS DE 0096 needs, so findings land at the right place rather than all piling up on the UCI.

Where a rejection lands

Action code 4 means “this level and all lower levels rejected”, so putting it on the UCI because one message was bad would reject every other message in the interchange too. §5.3.2 pairs it with code 7 — “this level acknowledged, next lower level acknowledged if not explicitly rejected” — and that is the combination used here:

• A fault in the interchange envelope itself rejects the UCI, and nothing follows, because everything below is implicitly rejected.
• A fault in a group’s UNG/UNE rejects that group’s UCF.
• A fault inside a message leaves both above it at 7 and rejects only that message’s UCM.

Warnings are reported but reject nothing, which matches the way ValidationReport already separates the two.

Grouped interchanges

§5.3.1 makes segment groups 1 and 3 mutually exclusive: a subject that uses UNG/UNE is reported through UCF, and one that does not is reported through UCM directly under the UCI. Which shape you get follows the subject — there is nothing to configure.

pub fn with_message_reference(self, reference: impl Into<String>) -> Self

Set the UNH message reference (DE 0062) of the CONTRL itself.

Defaults to the subject interchange’s control reference.

pub fn with_interchange_error(self, error: SyntaxError) -> Self

Record an interchange-level error on the UCI.

Ignored when error is not permitted at the interchange level by ISO 9735-4 Annex A — a CONTRL carrying a code its level may not use is one the partner’s translator rejects, which helps nobody.

pub const fn action(&self) -> Action

The verdict this message carries at the interchange level.

pub fn message_reference(&self) -> &str

The UNH message reference this CONTRL will carry.

pub fn segments(&self) -> Vec<OwnedSegment>

Render the message as segments, UNH through UNT.

UNT DE 0074 is computed from what was actually emitted, so the count is right by construction rather than by the caller remembering to update it.

pub fn to_bytes(&self) -> Result<Vec<u8>, EdifactError>

Render the message to EDIFACT bytes, without an interchange envelope.

Errors

Propagates any writer failure.

pub fn to_edifact_string(&self) -> Result<String, EdifactError>

Render the message to an EDIFACT string, without an interchange envelope.

Errors

As to_bytes, plus EdifactError::InvalidUtf8.

pub fn to_interchange_bytes( &self, syntax_identifier: &str, syntax_version: &str, date: &str, time: &str, control_reference: &str, ) -> Result<Vec<u8>, EdifactError>

Wrap the message in its own interchange and render it.

ISO 9735-4 §5.3 requires a CONTRL to travel in an interchange of its own and never inside a group, so this is the form to actually send. The sender and recipient are swapped relative to the subject interchange, because the reply goes back the way it came.

Example

let wire = Contrl::acknowledgement(&validated)
    .to_interchange_string("UNOC", "3", "260101", "0930", "ACK-1")?;

// The reply is addressed back to the original sender.
assert!(wire.starts_with("UNB+UNOC:3+RECEIVER+SENDER+260101:0930+ACK-1'"));
assert!(wire.ends_with("UNZ+1+ACK-1'"));

Errors

Propagates any writer failure.

pub fn to_interchange_string( &self, syntax_identifier: &str, syntax_version: &str, date: &str, time: &str, control_reference: &str, ) -> Result<String, EdifactError>

String form of to_interchange_bytes.

Errors

As to_interchange_bytes, plus EdifactError::InvalidUtf8.

Trait Implementations

impl Clone for Contrl

fn clone(&self) -> Contrl

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Contrl

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.