I already have an ABAP routine that collects weighbridge readings through a COM-port. Now I want to keep that option and add a second channel that talks to the weighbridge controller over TCP/IP using plain HTTP. The goal is simple: as soon as a vehicle settles on the scale the weight must hit the SAP screen in real time, exactly the way it does today through the serial link. You will build or adapt the communication layer so that: • an HTTP request/response cycle fetches the live weight from the device, • the result is handed straight to the same SAP user-exit / BAdI we use for the serial workflow, and • both channels can coexist without any user choosing one or the other manually. The device already exposes an HTTP endpoint; I’ll share the spec when we start. Response times have to feel instantaneous to the operator (sub-second round-trip in the plant LAN). No extra middleware is allowed—native SAP functionality such as CL_HTTP_CLIENT, RFC destinations or a lightweight ABAP daemon is fine. Deliverables 1. ABAP source (classes, function modules or OData/RFC service) that performs the HTTP call and parses the payload. 2. Updated integration point that slots the result into our current weighing transaction. 3. Unit and shop-floor test scripts demonstrating real-time capture over both channels. 4. Technical document covering setup, transport sequence and fallback strategy. Acceptance criteria • A weight change on the bridge is reflected in SAP within one second via HTTP. • Existing COM-port flow continues to work unchanged. • All code passes ATC with no high-priority findings.