| Title: | DEC/EDI |
| Notice: | DEC/EDI V2.1 - see note 2002 |
| Moderator: | METSYS::BABER |
| Created: | Wed Jun 06 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3150 |
| Total number of notes: | 13466 |
More Questions about DEC/EDI from new Swedish partner EDI Matrix: 4. Isn't it possible to set the syntax version number (UNB/S001/0002) to other than the value of 1? I would like to be able to set the syntax version number to 2 or 3, but I can't find the field in DEC/EDI Agreements Details Editor in the Trading Partner Editor (I'm working with the DEMO version of the Command Center) 5. Can I define my own "Message Numbering Scheme"? How? 6. When should I use Trading Partner Group? Can I have an example? I would be grateful for quick responses! Regards, Eva Appelqvist, EDIMatrix [email protected]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3039.1 | Manage Format | METSYS::NELSON | David, http://samedi.reo.dec.com/ | Tue Mar 04 1997 20:03 | 8 |
>4. Isn't it possible to set the syntax version number (UNB/S001/0002)
>to other than the value of 1?
I believe this can be done by using `manage format' in the Tables Editor.
The change will apply to all trading partner agreements using that
version of EDIFACT. However, she can copy an EDI standard and apply
the change to the new version.
| |||||
| 3039.2 | SYSTEM::HELLIAR | http://samedi.reo.dec.com/ | Wed Mar 05 1997 08:25 | 22 | |
5. Can I define my own "Message Numbering Scheme"? How?
>> The Message Numbering Schemes reside in shareable libraries which
>> we provide. Adding a new scheme has to be done by us.
6. When should I use Trading Partner Group? Can I have an example?
>> A Trading Partner Group is only of use if you are using message
>> segment, or composite element definitions which are specific to
>> more that one trading partner i.e. its a trading partner specific
>> definition which is shared between trading partners.
>> An example would be that a standard EDIFACT segment, GRH,
>> which is used in a standard message, such as DRINKS, has
>> the second element, DRINKS_OWED, set to OPTIONAL. However, some
>> trading partners decide that this is not OPTIONAL, and that
>> DRINKS_OWED should be MANDATORY. To do this a trading partner
>> (if only of use to one trading partner) or trading group (if
>> multiple trading partners want to MANDATE DRINKS_OWED) definition
>> is created of DRINKS, which changes the definition of GRH.
>>
>> This is by no means the only way in DEC/EDI to make DRINKS_OWED
>> MANDATORY but just highlights one possible use.
| |||||