The solution used UiPath RPA to connect the existing SAP Ariba and Sage workflows without requiring a complete replacement of either platform. The automation was designed around the existing process while removing repetitive manual activities.
Step 1: Retrieve PO data from SAP Ariba
The UiPath bot logs into SAP Ariba and retrieves the relevant purchase order data. Depending on the process type, the bot identifies POs that need to be created, updated, or closed.
Instead of employees repeatedly logging into Ariba and downloading files manually, the robot performs the data retrieval according to the configured workflow.
Step 2: Read and consolidate the exported files
SAP Ariba provides the PO information across three files containing header, order detail, and line-level information.
The bot reads all three files and consolidates the required information into a structured dataset for Sage. This eliminates the need for an employee to manually search across multiple spreadsheets to find the information needed for a single purchase order.
Step 3: Prepare the Sage transaction
The robot processes the consolidated data and navigates through the Sage ERP environment. It enters the required information into the relevant Sage fields and screens to create, update, or close the purchase order. This is the core of the SAP Ariba automation workflow: information originating in Ariba is automatically transformed into a format that Sage can process.
Step 4: Capture the Sage PO ID
After the transaction is processed, the automation checks the Sage result. When a PO is successfully created, the bot captures the corresponding Sage PO ID. This identifier is then stored in the appropriate output file so that the transaction can be reconciled back to its originating SAP Ariba PO.
Step 5: Handle errors and exceptions
Not every transaction will necessarily process successfully. Instead of stopping the entire workflow when an issue occurs, the automation identifies unsuccessful transactions and records the relevant error information. The bot separates successful and unsuccessful transactions and generates the required error files for further review. This allows human employees to focus on exceptions rather than checking every PO manually.
Step 6: Create SAP Ariba import files
After processing the transactions in Sage, the bot generates the required output files, including the PO ID, header, and error files, using the specific structure expected by SAP Ariba. These files are then imported back into SAP Ariba, creating a traceable connection between the original Ariba PO and its corresponding Sage transaction.
Step 7: Monitor the automated process
Human intervention is limited primarily to exception handling, environment access, and monitoring. Activity logs provide visibility into the robot’s execution, while employees can review reports and investigate transactions requiring attention. This approach demonstrates how UiPath procurement automation can connect applications that were not originally designed to operate as one automated workflow. The resulting P2P automation model reduces repetitive data movement while keeping the existing SAP Ariba and Sage systems in place.
