EDI vs ALE: Electronic Data interchange/ Application Link Enabling

If we send data to an external partner, we generally speak of EDI, while ALE is a

mechanism to reliable replicate data between trusting systems to store a redundant
copy of the IDoc data. The difference is made clear, when we think of a purchase
order that is sent as an IDoc. If we send the purchase order to a supplier then the
supplier will store the purchase order as a sales order. However, if we send the
purchase order via ALE to another R/3 system, then the receiving system will store
the purchase order also as a purchase order.
EDI
In EDI the partner is determined based on output type configuration. A partner
profile should be maintained for every partner. Usually this setup is used for
communication with external customers & Vendors also known as B2B
communication. Partner profiles gives control over when to send IDocs and what
data to be sent in control record of IDocs to a business partner. EDI is widely used
for exchanging business documents with external customers & vendors.

ALE
In ALE we need to have a distribution model (BD64) for partner determination. One
or more receivers (logical systems) may exist for a message type. A Master Idoc is
created once and depending on the number receivers determined in ALE
distribution model, it will be copied to that many communication Idocs. Then
communication IDocs will be sent to all the receivers. ALE is used widely for Master
Data distribution or any other communication with in the Customer's landscape.
Like 3 PL and Plants etc

Create Logical system SALE

Create Distribution ModelBD64
Select the model and add message type give sender and receiver Give message
type
Environment---Generate Partner Profiles
Edit--- Model View----distribute
Partner types LS in We20
Transactional RFC in WE21 Ports
BD51 for new inbound FM

WE81 Message type

WE82 Message type ---Idoc type---- Extension

WE21 Define the ports
WE30
WE31
WE57 Link the Function Module with the Message type and the Basic type Extension
WE42 Create Process Code

Difference between TYPE and LIKE in SAP ABAP :

TYPE : It will allocate memory during execution (object type).

TYPE will improve performance.
It is used when userdefined object link with SAP system data type.
TYPE refers to the user defined data types
TYPE,assign datatype directly to the data object while declaring.
LIKE : Tt will allocate memory immediatly.
It is when data object link with the other data object.
LIKE refers to existing data type of data object
LIKE,you assign the datatype of another object to the declaring data object.
The datatype is referenced indirectly.
Read more at http://sapabap-freshers.blogspot.com/2013/04/difference-betweentype-and-like-in-abap.html#GZI2rSuzth1HTHwY.99
Vendor master Development

http://scn.sap.com/docs/DOC-33664
Enhancement Framework
http://scn.sap.com/docs/DOC-22648
Finding Customer Exit
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=189893877
Finding badi through St05
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=85000885