studio-bettermilk/uipath-foundation-pack-for-accelerators-for-sap-ecc

Purpose and Runtime

This is a UiPath accelerator library for SAP ECC automation, organized as reusable XAML workflows rather than a single application. It covers Basis administration, Finance, Manufacturing, Sales, and Sourcing/Procurement operations through SAP GUI automation and SAP BAPI/RFC-oriented workflows. Execution requires UiPath Studio/Robot, SAP GUI/ECC access, and Excel-compatible files for arguments, inputs, configuration, and outputs.

Entry Points and Composition

Each capability is an independently invocable workflow, conventionally named SRC_*.xaml; there is no evident global orchestrator. The project metadata and discoverable entry-point manifest are:

• project.json

• project.uiproj

• entry-points.json

Representative top-level orchestrators include:

• SRC_BAPIv2.2_REGISTER/SRC_BAPIv2.2_REGISTER.xaml

• SRC_CM_SAP_LOGON_E/SRC_CM_SAP_LOGON_E.xaml

• UiPath Accelerator for SAP ECC for Finance/SRC_PAYMENT_RUN_E/SRC_PAYMENT_RUN_E.xaml

Consumers compose these workflows into their own UiPath processes, passing typed arguments and spreadsheet-backed data.

Shared SAP Session and GUI Automation Layer

Common workflows establish and terminate SAP GUI sessions, navigate transactions, populate controls/grids, inspect labels/status/scrollbars, and capture screenshots. This is the boundary to the SAP GUI client and is selector-sensitive.

• SRC_CM_SAP_LOGON_E/SapLogon.xaml

• SRC_CM_SAP_LOGOFF_E/ExecuteLogoff.xaml

• SRC_Common/SRC_SetTransactionCode.xaml

GUI-centric business workflows usually split an entry XAML from screen-specific execution stages, e.g. SetScreenDataFlow, validation, and message handling:

• UiPath Accelerator for SAP ECC for Sourcing and Procurement/SRC_MAT_MSTR_CRT_E/SRC_MAT_MSTR_CRT_E.xaml

• UiPath Accelerator for SAP ECC for Sourcing and Procurement/SRC_MAT_MSTR_CRT_E/Execution/SetScreenDataFlow.xaml

• UiPath Accelerator for SAP ECC for Finance/SRC_PARK_ACC_E/SetScreenDataFlow.xaml

BAPI/RFC Execution and Transaction Boundary

BAPI-based automations are packaged per SAP business operation across all domains (user/role administration, financial documents, purchase orders, production orders, sales orders, etc.). The generic register workflow provides the most explicit execution pipeline: validate arguments and required fields, build BAPI arguments, execute, evaluate return values/retries, commit, and write logs.

• SRC_BAPIv2.2_REGISTER/SRC_BAPIv2.2_REGISTER.xaml

• SRC_BAPIv2.2_REGISTER/ExecuteBAPI.xaml

• SRC_BAPIv2.2_REGISTER/Commit.xaml

RFC table reads and unit/data-element facilities support SAP metadata and table-driven operations:

• SRC_Common/SRC_RFC_READ_TABLE_v2.2.xaml

• SRC_BAPIv2.2_TABLEDATA_OUTPUT_E/GetSAPDataTable.xaml

• SRC_BAPIv2.2_VALTBL_CNV_E/SRC_BAPIv2.2_VALTBL_CNV_E/GetT006.xaml

Spreadsheet-Driven Contracts and Localization

Excel files are the primary external data contract: argument templates, batch input, resource strings, selector definitions, and English/Japanese variants. Workflows load and transform spreadsheet data into UiPath tables/rows before SAP calls or GUI entry.

• SRC_CM_FNCMDL_EXE_E/Data/Arg-SRC_CM_FNCMDL_EXE_E(EN).xlsx

• UiPath Accelerator for SAP ECC for Basis Administration/SRC_DEFINE_JOB_E/Config/Selector-SRC_DEFINE_JOB_E(EN).xlsx

• SRC_Common/SRC_LoadExcelData.xaml

Selector and resource workbooks isolate language/UI-version variation from workflow control flow; this is a material maintenance boundary for SAP GUI changes.

Outputs, Monitoring, and Audit

Export-oriented workflows retrieve SAP tables, job logs, dumps, authorization data, CCMS alerts, and GUI results into DataTables, Excel, text, MHTML, or HTML. Error/status handling and logs provide the observable result boundary for batch operations.

• SRC_CM_GET_TBL_E/Execution/SearchDataExport.xaml

• UiPath Accelerator for SAP ECC for Basis Administration/SRC_BAPIv2.2_JOBLOG_EXPORT_E/ExportJobLog.xaml

• SRC_Common/SRC_WriteLogToExcel.xaml