In this enveloping procedure the intermediary group (UNG) envelope will not be implement as it is not required per EDIFACT standard not it would bring any additional value to the tutorial.
We will proceed with the creation of the UNH envelope, and you can see how it is correlated with the UNB level and how the envelope chain is implemented. As in the UNB level this envelope will be implemented with a wildcard * for the sender and recipient fields, making this a generic use envelope.
The message type is again CONTRL for it's simplicity although in this case the message type doesn't make that much difference the procedure will always be the same.
1. Navigate Trading Partner > Document Envelopes > Envelopes and select New Envelope Go. Select the EDIFACT Standard.
2. Select the Outbound UNH level.
3. Give it a meaningful name GENERIC_UNH_UNT_ENVELOPE_OUTBOUND
4. As said we are leaving the Sender ID and the Recipient ID with the wildcard *. The envelope chain is set in the Next Envelope setting, which uses the UNB envelope build in the first part of the tutorial. One could start implementing the envelopes starting in the UNH level and selecting Create Next Envelope, this is just a way of doing it won't make any practical difference in terms of implementation.
This are the required parameters to build the envelope message.
5. Set how to generate the Reference Number.
6. One can map and carry with both translation, validation and enveloping in the same step but this will be out of this tutorial scope, nevertheless you can specify NONE as the map to use in the next step.
7. Select the details for message enrichment, as said in point 6. If map is NONE the values of Validate translation input and output will be ignored.
8. Finally specify the security settings, which will be leave as none in this tutorial.
9. Confirm, Finish and proceed to step 3 of the tutorial where we are going to see how to use the enveloping in the BPs.
We will proceed with the creation of the UNH envelope, and you can see how it is correlated with the UNB level and how the envelope chain is implemented. As in the UNB level this envelope will be implemented with a wildcard * for the sender and recipient fields, making this a generic use envelope.
The message type is again CONTRL for it's simplicity although in this case the message type doesn't make that much difference the procedure will always be the same.
1. Navigate Trading Partner > Document Envelopes > Envelopes and select New Envelope Go. Select the EDIFACT Standard.
2. Select the Outbound UNH level.
This are the required parameters to build the envelope message.
Message Type: CONTRL
Message Version Number: 2
Message Release Number: 1
Controlling Agency, Coded: UN
There is an extra setting using in the Business Process to specify that this is the envelope that we want to use, this allows to create identical envelopes for different situations if you need so. It is used in EDI Encoder service at BP level.
Accepter Lookup Alias: CONTRL_2_1_UN
Some other field to consider.
Limit Interchange Size -> can leave it with default settings or adjust to requirements, it's the max allowed size for interchange messages.
Use Correlation Overrides -> we want it to be Always and will be taking advantage of it on the next tutorial step in the Correlation Service.
5. Set how to generate the Reference Number.
6. One can map and carry with both translation, validation and enveloping in the same step but this will be out of this tutorial scope, nevertheless you can specify NONE as the map to use in the next step.
7. Select the details for message enrichment, as said in point 6. If map is NONE the values of Validate translation input and output will be ignored.
8. Finally specify the security settings, which will be leave as none in this tutorial.
9. Confirm, Finish and proceed to step 3 of the tutorial where we are going to see how to use the enveloping in the BPs.
Sem comentários:
Enviar um comentário