If you want an SAP program to be extends the system, without any changes and that will further depend upon the settings in the modification you would have to use event which is further known as business transaction event. Business transaction event is nothing but it is just a customer improvements. Basically it defines the standard interface, which helps you in understanding how the communication is completed to or from the external system to SAP.
For such type of transactions you will need two types of interfaces:
- Publish and subscribe interfaces.
- Process interfaces.
If you want to have information about the particular events (at the time of document being entered) in the SAP standard application and which will further generate the data as a result available to the external software you would have to publish or subscribe interfaces.
Let us have an example of such events in the R/3 systems:
- Master record was generated, altered or might be blocked.
- Document was first entered then parked and overturned.
- May be the items were cleared or reset.
If you want to submit the business processes to a dissimilar control which cannot be understood with the standard system, which means process interfaces replicate the standard processes. Moreover it is conceivable to attach the distinct external developments to the standard R/3 system. The extra developments are basically worked with the help of ABAP/4 development workbench you would have to use process interface.
1. As soon as document is generated in SAP, you must have to do something for this, let us have an example, for this you have to update the Ztables or the related information which is further sent to the related user.
2. You must have to save all the overturned documents in the Ztables, and for this you have to notify the person who is responsible for document that must be reversed.
All reversed documents should be saved in the Ztables for further analysis or to notify the responsible person that document has been reversed.