Format profiles

What this installation can exchange, and the mappings behind it.

An agreement says what you exchange with one partner. A format profile says what this installation can exchange at all. It is a named format, such as EDIFACT D96A, with one coverage line per document type and direction, and each line names the reporting configuration that carries it: the format mapping on the way out, the model mapping on the way in.

The coverage is checked against the installation

A line whose configuration has not been imported here says so, and a document on that line cannot be rendered or read. That is the quickest reading of whether an installation is finished.

A template, not a second set of rules

Choosing a profile in the partner wizard writes its configurations onto the agreements the wizard generates. After that the agreements are what the engine reads, and changing the profile changes nothing already generated. A profile whose format does not match the documents you picked is dropped, and the wizard says so.

The two onboarding letters read the profile as well, which is where the sentence about what we exchange comes from. It is read from here and never typed.

One configuration may sit on several profiles. EANCOM D96A and EDIFACT D96A are the same structure under two guidelines, and one export format serves both.