This playlist helps you master the international commercial terms in a simple lucid manner
Playlist Link - https://www.youtube.com/playlist?list=PL_16BSQMjAHMiQVULRRSb613OrR0_L4MD
Incoterms stand for international commercial terms that apply to every buyer and seller when they engage in international business( shipments ).It lays down the scope as far as packing , insurance , freight etc goes for the buyer and the seller
To cut short the crap , let's understand with a example and dive straight in ,
Say i am a manufacturer of cars in India . I get a Order from IBM /USA for 100 $ car .
Let's look at what all order cases are possible
(1) IBM places a exworks order
Here , it is my duty to simply produce the cars and git it packed till the factory gates
After that the ownership is transferred to the buyer
He will get the custom clearance , trasnported to the Indian Port , get it shipped , pay for the occean freight , transit insurance m again get the goods custom cleared at the american port , get iot unloaded and again transport it to his warehouse
My scope as a seller ended as soon as i packed the goods at the factory gate
(2) IBM roughened up by the indian exercise places a FOB order
Here , not only do i have to make the cars and get it packed but also after getting custom clearance get it transported to the port and put it on the boat
Once i do that , the ownership of the goods now get transferred to the buyer .Until i put it on the boat , all insuirance etc is in my scope
Now again , paying for the occean freight , transit insurance m again get the goods custom cleared at the american port , get iot unloaded and again transport it to his warehouse is in IBM's scope
(3) IBM places a CIF order
Now , i have to make the cars and get it packed , get custom clearance , transport it to the occean port , putit on boat , organise for the shipping and insurance during the transit .....simply put till the goods reach the american port , the ownership of the goods still remain with me
Once the goods reach american port , then my ownership ends and thereon,get the goods custom cleared at the american port , get iot unloaded and again transport it to his warehouse is in IBM's scope
(4) IBM places a FDD order
Here , everythig is my scope ...until the goods reach the buyer's warehouse , all thing's are in my scope
I.e producing the goods , getting it packed , shipping it to america , getting custom clearance both in india and america , getting goods unloaded at america and then further arranging transport for the goods to be taken to the buyer warehouse ....once the goods reach the buyer warehouse , the ownership now changes hands
This is how using this small hypotheical example , we have learnt what are international commercial terms .You see at certain point , there was wide disputes as to who is responsible for what amd so the need was felt to have a common uniform set of rules for international commerce
Let your knowledge help people ...the blessing's you get will keep you alive for making more valuable tuts ,
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.