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.
Amy Stapleton
Amy Stapleton has several decades of experience managing software development projects. She began her career at SAP in Walldorf, Germany. After returning to the US, Amy gained hands-on project management experience in ERP implementations at major corporations across many industries. Amy joined the National Aeronautics and Space Administration (NASA) in 2001 where she served as an IT Manager. She assisted in the Space Agency’s implementation of an enterprise core financial system using SAP. Amy retired from NASA in 2015 and is now founder of Hutch.AI and an analyst at Opus Research, working in the area of artificial intelligence
You may contact the author at
amy@hutch.ai.
If you have comments about this article or publication, or would like to submit an article idea, please contact the
editor.
Premium
