Welcome to the Investors Trading Academy talking glossary of financial terms and events.
Our word of the day is “FOB - Free On Board”
The FOB abbreviation is an import/export term relating to the point at which responsibility for goods passes from seller – the exporter to buyer or importer. It's in this listing because it's commonly misunderstood and also has potentially significant financial implications. FOB meant originally that the seller is liable for the goods and is responsible for all costs of transport, insurance, etc., until and including the goods being loaded at the port.
Logically FOB also meant and still means that the seller is liable for any loss or damage up to the point that the goods are loaded onto the vessel at the FOB port, and that thereafter the buyer assumes responsibility for the goods and the costs of transport and the liability. From the seller's point of view an FOB price must therefore include his costs of transport from factory or warehouse, insurance and loading, because the seller is unable to charge these costs as extras once the FOB price has been stated. The FOB expression originates particularly from the meaning that the buyer is free of liability and costs of transport up to the point that the goods are loaded on board the ship slightly different ways, even to the extent that other interpretations are placed on the acronym, most commonly 'Freight On Board ‘While liability and responsibility for goods passes from seller to buyer at the point that goods are agreed to be FOB, the FOB principle does not correlate to payment terms, which is a matter for separate negotiation. FOB is a mechanism for agreeing price and transport responsibility, not for agreeing payment terms.
By Barry Norman, Investors Trading Academy
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.