Manish,
Before you embark upon such a solution, I strongly suggest that you determine how many such changes occur in a normal business day, and the tolerance of your CS group for receiving notifications for each of them. My experience is that CS is typically unprepared for a flood of notifications, and that careful design of any notification process is required BEFORE embarking on this business process. Should ALL changes be transmitted? A subset? How to determine?
So. Like most documents in SAP, production orders can be configured to have an output. This output can take the form of a printed document, or an email message, among other output types. A change to a production order can trigger the creation of such an output type. Such configuration would be more or less standard. Speak to your local PP functional expert for guidance for creating this output type..
Also, it is possible for an ABAPer to create a customized summary report, which collects a list of production orders that have been changed, say within a specific time frame (each day, or ???). This report can be configured to print to paper, to print to spool, deliver by email, or other standard output type for reports. This you would have to spec out and hand over to your ABAPers.
There may be other solutions. I personally couldn't recommend any of them.
Best Regards,
DB49