Frends.Edifact.CreateFromJson / 1.0.0
Summary
Assembles a valid EDIFACT interchange from JSON, and can generate the interchange header rather than making you construct it.
Typical use — the outbound half of EDIFACT exchange, after a mapping step has produced the message content
Input for converting Edifact native document to other formats.
| Name | Type | Default | Example | Description |
|---|---|---|---|---|
| CreateUNBHeader | Boolean |
False |
true |
Should the UNB header be created, if not included in input document. |
| HeaderData | HeaderData |
– | – | UNB header data. Used if CreateUnbHeader is set to true. |
| ControlNumber | String |
– | 131 |
Interchange control reference |
| InterchangeSenderIdentification | String |
– | SENDER1 |
Interchange sender identification |
| InterchangeSenderInternalIdentification | String |
– | ABC |
Interchange sender internal identification |
| InterchangeRecipientIdentification | String |
– | RECEPIENT1 |
Interchange recipient identification |
| InterchangeRecipientInternalIdentification | String |
– | ABC |
Interchange recipient internal identification |
| DateOfPreparation | String |
yyMMdd |
991231 |
Date of preparation |
| TimeOfPreparation | String |
hhmm |
0000 |
Time of preparation |
| Json | String |
– |
{
"Edifact": {
"UNB": { ... }
"TSINVOIC": { ... }
"UNZ": { ... }
}
} |
Edifact in JSON format. The JSON format should be the same as produced by Frends when converting Edifact documents to JSON. |