{"id":7,"date":"2026-04-01T03:13:31","date_gmt":"2026-04-01T03:13:31","guid":{"rendered":"https:\/\/vannguyen.it.com\/?project=sap-tms-and-rpa-automation-at-aqua"},"modified":"2026-04-01T13:43:04","modified_gmt":"2026-04-01T13:43:04","slug":"sap-tms-and-rpa-automation-at-aqua","status":"publish","type":"project","link":"https:\/\/vannguyen.it.com\/?project=sap-tms-and-rpa-automation-at-aqua","title":{"rendered":"SAP, TMS, and RPA Automation at AQUA"},"content":{"rendered":"<h3>Business Context<\/h3>\n<p>This automation case focused on sample-order approvals that were still being handled manually inside SAP. Each order could consume around 30 minutes of user time, and the workload repeated at high weekly volume, creating an obvious operational bottleneck.<\/p>\n<h3>Pain Points Addressed<\/h3>\n<ul>\n<li>Manual approval inside SAP was slow, repetitive, and costly in staff time.<\/li>\n<li>At weekly scale, thousands of orders created a queue that was too large for sustainable manual handling.<\/li>\n<li>Users were spending time on repetitive approval clicks instead of dealing with true exceptions.<\/li>\n<li>Without an automated feedback loop, teams had to keep checking results manually.<\/li>\n<\/ul>\n<h3>Automation Design<\/h3>\n<p>The solution used Excel as the intake and control layer for approval-ready records. An RPA bot then opened SAP, executed the approval actions that a user would normally perform, and wrote the outcome back so the operating team could track results without logging into every transaction manually.<\/p>\n<h3>Application and ERP Layer<\/h3>\n<p>This was not just a simple script. The automation had to bridge business input, a control file, SAP execution, and result reporting. That meant treating Excel as an operational queue, using the bot as an execution worker, and keeping enough structure around outputs so business users could trust the run.<\/p>\n<h3>Operational Impact<\/h3>\n<p>The main gain was throughput. Work that previously consumed about 30 minutes per order moved into a repeatable automation path, which is a significant shift when the weekly volume reaches thousands of orders. The team could then spend more time on exception handling and less time on repetitive SAP actions.<\/p>\n<h3>Why This Project Matters<\/h3>\n<p>This case shows practical ERP-side automation: identifying a high-friction approval step, designing a control layer around it, letting RPA execute the repetitive SAP work, and returning outcomes back to the users in a usable way.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>RPA automation replaced a manual sample-order approval process that took about 30 minutes per order, using Excel intake, SAP bot actions, and automated result feedback at high weekly volume.<\/p>\n","protected":false},"featured_media":0,"template":"","class_list":["post-7","project","type-project","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/vannguyen.it.com\/index.php?rest_route=\/wp\/v2\/project\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vannguyen.it.com\/index.php?rest_route=\/wp\/v2\/project"}],"about":[{"href":"https:\/\/vannguyen.it.com\/index.php?rest_route=\/wp\/v2\/types\/project"}],"version-history":[{"count":1,"href":"https:\/\/vannguyen.it.com\/index.php?rest_route=\/wp\/v2\/project\/7\/revisions"}],"predecessor-version":[{"id":47,"href":"https:\/\/vannguyen.it.com\/index.php?rest_route=\/wp\/v2\/project\/7\/revisions\/47"}],"wp:attachment":[{"href":"https:\/\/vannguyen.it.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}