Dataflow & Messages

Page Up

 

Research into the possibilities of using EDIFACT messages for reporting BOP data must start with a data flow analysis. It has to be established exactly which data are being exchanged between the various parties. This has to be done for all data in the general collection system as well as in the survey-based system.

The following data flows could be distinguished:

Tiedye.gif (77449 bytes) from customers to banks (PAYORD/PAYMUL/PAYEXT and BOPINF)
Tiedye.gif (77449 bytes) from banks to the BOP compiler (BOPCUS and BOPBNK)
Tiedye.gif (77449 bytes) from enterprises to the BOP compiler (BOPDIR)
Tiedye.gif (77449 bytes) from BOP compiler to international statistical organisations and between BOP compilers (GESMES/CB)
Tiedye.gif (77449 bytes) between banks (FINPAY)

These dataflows could be captured with the above-mentioned EDIFACT messages, which are presented in the scheme at page 12. Examples of these messages using fictitious business transactions will be given in Chapter 2. Full details of the messages will be given in the Annexes.

For the sake of clarity, the use of (one of) these messages is fully optional. All messages are independent and could be used as such. For instance, although PAYORD and BOPCUS are linked, it is not necessary to use them both.

 

separator.gif (1392 bytes)