Database Reference
In-Depth Information
be performed, namely, extracting/parsing historical information about a business
object, such as the previous port name of the voyage and the previous ETA of the
port call or previous vessel.
Realization of business cases using event processing (Rule Engine)
To do business with a shipping company, the Trading Partner (TP) must be provided with
Schedule object(s) and should be compliant with the following composite conditions:
• All voyages with the POL
PORTCODE_A <and>
• ALL PODs in certain
COUNTRY_ID <and>
• With two certain PODs in
TRADE_AREA
These conditions are rather obvious, as TP must have a port with goods waiting to load
(POL) and all the trade ports for unloading goods (PODs) according to the carrier's sched-
ule. In addition to this, some more operational conditions must be applied:
• A port call must
not
be canceled (some kind of suspension status that is unde-
cided)
• A voyage must be in the public distribution state (available for booking, that is,
the vessel is on a commercial route and is not going for maintenance)
Let's see how these five conditions can be interpreted using basic events on the sender's
side in terms of DB CRUD operations:
• Adding a port call to the voyage using
INSERT
on the TP side
• Updating port call information, which includes operations that depend on condi-
tions based on TP rules, in the following manner:
◦
DELETE FOR ALL
ports in the voyage if POL
PORTCODE_A
is re-
moved (simply, TP is not interested in the voyage without its port of
loading)
◦
INSERT FOR ALL
ports in the voyage if POL
PORTCODE_A
is added
and POLs
◦ Are in the TP's area of interest (opposite to the previous point; the entire
voyage will be provided if the TP's port of loading added)
◦
INSERT FOR SINGLE
port if new POD is added in the TP's area of in-
terest (simple adding new port of discharge)
◦
DELETE FOR SINGLE
port if the POD belongs to the TP's area of in-
terest
◦ Removed from voyage (opposite to previous point)
Search WWH ::
Custom Search