Skip to main content
Question

Creating Purchase Orders with Multiple Line Items via Celonis Action Flow (SAP Module - Make an RFC Call (BAPI_PO_CREATE1))

  • March 26, 2026
  • 0 replies
  • 2 views

vishal.yadav14
Level 1
Forum|alt.badge.img

I am working on an engagement where we want to create Purchase Orders (PO) in SAP triggered from Celonis based on Purchase Requisitions (PR). We are trying to implement this via Action Flows using an RFC call (BAPI_PO_CREATE1). We have the following scenarios:

  1. Mirror PR – All PR lines in one PO with identical lines

  2. Combine PR – Combine several PRs into one PO

  3. Individual – Multiple PR lines are converted into individual POs

  4. Add PR – Add PR lines into an existing PO

For scenarios 1, 2, and 4, there can be multiple PR line items that need to be created within a single PO (or appended to an existing PO).

Current Challenge

We are facing issues in structuring and passing multiple line items from Celonis to SAP within a single RFC call. Specifically:

We are able to fetch multiple PR line items using “Get Rows”

We are using Array Aggregators to construct required SAP structures like POITEM and POITEMX

However, Celonis Action Flows seem to allow only a single linear route into the RFC module, and we are unable to:

Pass multiple aggregated arrays (POITEM, POITEMX, POSCHEDULE, etc.) together into one RFC call

Or merge multiple aggregators into a single input for the RFC module

Clarification Required

We would appreciate your guidance on the recommended approach for:

Passing multiple table parameters (POITEM, POITEMX, POSCHEDULE, etc.) into a single RFC call within an Action Flow

Whether Celonis supports combining multiple Array Aggregator outputs into one module, or if variables are the expected approach

Best practice to construct SAP-compatible structures for multi-line PO creation using BAPI_PO_CREATE1

Any reference implementation or example or detailed documentation (if available) for creating a PO with multiple line items from PR data

It would be really helpful if you could share:

Recommended design pattern for this use case

Sample configuration or documentation references

Any known limitations or workarounds within Action Flows

Thanks in advance for your support.