More and more, EDI is being called upon to replicate functions in the real world. Where we used to fill out forms in triplicate with carbon paper, Carbon Copy requests are on the rise.
While Carbon Copies can definitely be called a Value Added service, and outside the domain of ECGrid, it is provided on the infrastructure for two reasons:
The Carbon Copy process is quite simple. A database is kept of Original Sender/Receiver pairs. Whenever a match is made a copy of the interchange is made and the Original Sender/Receiver pair is replaced with the Carbon Copy Sender/Receiver pair.
Note that this only has to be done once for each Carbon Copy Sender/Receiver pair, not matter how many Carbon Copies it appears in.
Since it is possible that a legitimate requester may be the Carbon Copy Receiver, NetOps can override this limitation when authorization has been obtained from either the Original Sender or Original Receiver.
For this purpose, you might want to make a generic Carbon Copy ECGridID (e.g. ZZ*MYCC). Of course, it will need to be unique across the infrastructure. You can always safely use this as your Carbon Copy Sender QID. Remember that you will need to create an Interconnect Request for your Carbon Copy Sender/Receiver pair.
|© 2008-2011, Loren Data Corp.
All rights reserved.
|ECGrid is a registered service
mark of Loren Data Corp.
ECGridOS is a service mark of Loren Data Corp.