Developers often struggle with custom ABAP/4 code or database logging to devise ways to track changes to data and then to trigger output of that changed data across outbound interfaces to non-R/3 systems. The onus of creating a way to track changes as they occur rests squarely on the shoulders of these developers, but it doesn't have to. There are easier, more automated ways to facilitate real or near real-time outbound interfaces: change pointers, message control, and workflow. The benefits of tapping into these pre-existing SAP R/3 mechanisms can be significant. You can track changes to data and automatically trigger your outbound interface without writing any custom ABAP/4 code in Customer Exits and without turning on database logging. This article will show you that it's not difficult to do.