Part 2 of the sap-harness series looks at what actually happens on the wire when sap:sync and sap:push talk to the SAP ADT REST API: walking the package tree, finding out where source really lives per object type, and getting lock, push, unlock, activate in the right order (the hard way). It also covers why a 200 response from the activation endpoint isn’t the same thing as success, and how local drift gets tracked without ever touching the server.
Read More Technology Blog Posts by Members articles
#abap