COARRI：Container discharge/loading report message
Functional definition
A message by which the container terminal reports that the containers specified have been discharged from a seagoing vessel (discharged as ordered, overlanded or shortlanded), or have been loaded into a seagoing vessel.
COPRAR：Container discharge/loading report message
Functional definition
A message to order to the container terminal that the containers specified have to be discharged from a seagoing vessel or have to be loaded into a seagoing vessel
COPARN：Container announcement message
Functional definition
The message contains an order to release, to make available, to accept or to call down containers or to announce the impending arrival of containers. This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The business scenario for the container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT container messages'. The order may pertain to cargo related containers (full container load and less than container load), the arrangement of empty containers prior to loading and after stripping, as well as the arrangements for leasing the empty containers (on- hire and off-hire of containers).
CODECO: Container gate-in/gate-out report message
Functional definition
A message by which a terminal, depot, etc. confirms that the containers specified have been delivered or picked up by the inland carrier (road, rail or barge). This message can also be used to report internal terminal container movements (excluding loading and discharging the vessel) and to report the change in status of container(s) without those containers having physically been moved. This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The business scenario for the container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT container messages'.
BAPLIE: Bayplan/stowage plan occupied and empty locations message
Functional definition
A message to transmit information about equipment and goods on a means of transport, including their location on the means of transport. The message can be exchanged between (liner's) agents, tonnage centers, stevedores and ships masters/operators (see section 1.3 for more details).
集装箱管理里面涉及的EDI大概就是上面提及的几个，一个通用的流程。还要很多的特殊分支的业务没有提及比如租箱业务等还会涉及其他的数据交换。
我这边的“箱管”指的是港口的箱管，具体可能是船公司也可能是船代，我们就给他统称了，因为业务是一样的。
这样我们开始这个流程，首先从“订舱/市场”开始，放一个放箱指令到堆场，就是一个COPARN。我们上面可以看到COPARN可以执行很多的功能，这边是一个 order to release。然后堆场集装箱提走后会出来一个CODECO。这个CODECO的发送方式也有不同，国内目前一般是一天发送一个或2个CODECO。所以造成说箱管那边不是实时的管理，动态滞后了。国外一些做的比较完善的系统，都能做到集装箱进/出场后马上发出一个CODECO，并且在集装箱进/出场前必须先给一个指令一般是COPARN。所以这边设计是箱管接收一个CODECO后，马上会回复一个COPARN，请求进场。这样集装箱就已经装箱在堆场了。然后订舱/市场这边会给码头发一个COPARN(进场)及COPRAR（预装箱）指令，（存在代理的情况下预配指令很多是由代理的出口操作给码头，我们先撇开这些细节，顺这粗的流程先走）。码头会反馈一个COARRI(实际装箱清单)给箱管，另外给出口操作反馈一个BAPLIE。集装箱就上船走了^_^。
