LUIS SANDRIES

Systems & Troubleshooting

Debugging is most useful when the resolution becomes repeatable. These cases show how I frame an issue, isolate the failure, validate the fix, and leave the next person with a clearer system.

Procter & Gamble · Accounts payable operations

Invoice exceptions were consuming a manual workflow

Problem
Supplier invoice discrepancies across North and Latin America required repeated manual handling in a time-sensitive SAP FI process.
Root cause
A recurring, rules-based reconciliation path was being handled as individual manual work, creating avoidable delay and inconsistent visibility.
Fix
Implemented a KNIME-assisted workflow around SAP FI handling and automated reporting in Excel while preserving documented exception steps.
Validation
The revised workflow reduced invoice-handling time by more than 95% and continued to produce audit-ready records and daily status reporting.
Follow-through
Documented the process in SOPs and created how-to videos and visual status reports so the improvement could be understood and reused.

Investigation

  • ▹Reviewed invoice states, price blocks, purchase-order mismatches, and the handoffs between suppliers, buyers, IT, and Order Management.
  • ▹Mapped the repeated decision points and identified which steps could be standardized without removing exception review.
  • ▹Compared daily workload and processing time before and after the automated path.
  • SAP FI
  • KNIME
  • Excel
  • SOP documentation
View related experience →

Procter & Gamble · Site Integrated Planning internship

Supply-chain reporting was slow and master data was noisy

Problem
Supply-chain reporting took repeated manual preparation while obsolete or inaccurate SAP SCM material records risked downstream ordering and production problems.
Root cause
Manual report assembly and aging master data created two connected failure points: slow visibility and unreliable planning inputs.
Fix
Automated report generation with Excel VBA and cleaned and updated the supporting SAP SCM material data with planner confirmation.
Validation
Report processing time fell by 70%, and updated records were checked with the planners responsible for the affected factories.
Follow-through
Created process documentation, status snapshots, action logs, and training communication for continued use across the planning group.

Investigation

  • ▹Reviewed the report-generation steps and identified repetitive transformations suited to a macro-driven workflow.
  • ▹Worked with planners across Latin American factories to verify material updates and distinguish current data from obsolete records.
  • ▹Logged changes and meeting actions so the operational context stayed traceable.
  • Excel VBA
  • SAP SCM
  • Microsoft Teams
  • SharePoint
View related experience →

Independent systems tool · mac-scrcpy-env

An Android camera needed to behave like a Mac webcam

Problem
A phone camera could stream over ADB, but the multi-step setup was fragile and difficult to reproduce across sessions and video applications.
Root cause
The solution depended on several tools, permissions, and ordered startup steps that were easy to configure differently each time.
Fix
Packaged the environment behind a Makefile-driven workflow that bootstraps dependencies, connects the device, and starts the stream with one command.
Validation
Verified the virtual camera as an input in Zoom, Microsoft Teams, OBS, and other macOS applications.
Follow-through
Turned the working setup into a reproducible environment instead of leaving it as undocumented terminal history.

Investigation

  • ▹Separated device connectivity, ADB authorization, scrcpy streaming, and virtual-camera availability into independently testable stages.
  • ▹Checked the camera feed at the system boundary before testing it inside Zoom, Teams, and OBS.
  • ▹Identified the dependencies and startup order that had to remain consistent.
  • Shell
  • Makefile
  • ADB
  • scrcpy
  • macOS