Hi,
Suraj has written the most important part already, the part "Schedule Generation and Activation as a job" (all is listed in this section, you can also find this in note 187455).
The second part (Schedule Periodic Transfer using ALE Change Pointers) is actually not correct anymore, or rather "old school" 
. You can activate the change transfer using Business Transaction Event, then all you need is an ACTIVE model which includes your material. Then every change is immediately transferred.
"I have one material code active in two plants and two ewm warehouses belong to different customer.
Now say business want to do some changes to product MatA for Plant 0001 and Warehouse 1111.
But at same time it shall not impact the product master for Plant 0001 and Warehouse 2222 in ewm.
Now changes has done for product MatA in ECC for Plant 0001.
How to automate this changes in EWM for same plant/Warehouse."
Now first of all I do not really understand what you scenario is if you write "one material in two warehouse belong to different customer". So is it the same material or is it two materials?
But anyway: if you change something on plant level - why should this effect the warehouse? What do you change? Are you sure it is CIF relevant at all?
Brgds
Juergen
---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub