SAP actions
The following integrations of SAP actions are prebuilt to support you with a simple setup and without deeper SAP knowledge.
The actions are structured by the corresponding business object.
Actions that are not available can also be accessed through Generic RFC calls.
1. Actions and corresponding BAPIs
Prebuilt actions and corresponding BAPI calls to let your SAP administrator know which additional permissions are necessary for the employed user.
Get Material Details
Retrieves material details.
Corresponding BAPI call: BAPI_MATERIAL_AVAILABILITY
Change Material
Modifies a parameter of selected Material.
Corresponding BAPI call: BAPI_MATERIAL_SAVEDATA
Purchase Order Actions
Change Purchase Order
Modifies a purchase order.
Corresponding BAPI call: BAPI_PO_CHANGE
Add Purchase Order Item
Adds a purchase order item to a purchase order.
Corresponding BAPI call: BAPI_PO_CHANGE
Release Purchase Order
Releases a purchase order.
Corresponding BAPI call: BAPI_PO_RELEASE
Purchase Order Item Actions
Change Purchase Order Item(s)
Modifies a purchase order item.
Corresponding BAPI call: BAPI_PO_CHANGE
Delete Purchase Order Item
Deletes a purchase order item.
Corresponding BAPI call: BAPI_PO_CHANGE
Revoke Deletion
Revokes the deletion of a purchase order item.
Corresponding BAPI call: BAPI_PO_CHANGE
Post Goods Receipt
Posts a Good Receipt to a specific Purchase Order.
Corresponding BAPI call: BAPI_GOODSMVT_CREATE
Revert Goods Receipt
Reverts a goods receipt by using the material document.
Corresponding BAPI call: BAPI_GOODSMVT_CANCEL
Purchase Requisition Actions
Create Purchase Requisition
Creates a purchase requisition.
Corresponding BAPI call: BAPI_PR_CREATE
Change Purchase Requisition
Modifies a purchase requisition.
Corresponding BAPI call: BAPI_PR_CHANGE
Release Purchase Requisition
Releases a purchase requisition.
Corresponding BAPI call: BAPI_REQUISITION_RELEASE_GE
Add Purchase Requisition Item
Adds a purchase requisition item to a purchase requisition.
Corresponding BAPI call: BAPI_PR_CHANGE
Change Purchase Requisition Item
Modifies a purchase requisition item.
Corresponding BAPI call: BAPI_PR_CHANGE
Release Purchase Requisition Item
Releases a purchase requisition item.
Corresponding BAPI call: BAPI_RELEASE_REQUISITION
Delete Purchase Requisition Item
Deletes a purchase requisition item.
Corresponding BAPI call: BAPI_PR_CHANGE
Revoke Deletion
Revokes the deletion of a purchase requisition item.
Corresponding BAPI call: BAPI_PR_CHANGE
Sales Order Actions
Get Sales Order Details
Retrieves sales order details.
Corresponding BAPI call: BAPISDORDER_GETDETAILEDLIST
Create Sales Order
Creates a sales order.
Corresponding BAPI call: BAPI_SALESORDER_CREATEFROMDAT2
Change Sales Order
Modifies a sales order.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Set Delivery Block
Sets a delivery block on a sales order.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Remove Delivery Block
Removes a delivery block from a sales order.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Set Billing Block
Sets a billing block on a sales order.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Remove Billing Block
Removes a billing block from a sales order.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Sales Order Item Actions
Change Sales Order Item
Modifies a sales order item.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Reject Sales Order Item
Rejects one or several sales order items.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Set Delivery Block
Sets a delivery block on a sales order item.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Remove Delivery Block
Removes a delivery block from a sales order item.
Corresponding BAPI call: BAPI_SALESORDER_CHANGE
Post Goods issue
Posts a goods issue on a delivery.
Corresponding BAPI call: WS_DELIVERY_UPDATE
Create Delivery From Sales Order
Creates a delivery from a sales order.
Corresponding BAPI call: BAPI_OUTB_DELIVERY_CREATE_SLS
Create Delivery From Sales Order Items
Creates a delivery from a sales order items.
Corresponding BAPI call: BAPI_OUTB_DELIVERY_CREATE_SLS
Remove Delivery Block
Removes a block on a delivery.
Corresponding BAPI call: BAPI_OUTB_DELIVERY_CHANGE
Complete Open Correspondence
Completes an open correspondence.
Change Outline Agreement
Modifies an existing outline agreement.
Corresponding BAPI call: BAPI_CONTRACT_CHANGE
Downloads
Note
The SAP Automation Transports are currently only available on request.
To request SAP Automation Transports, please create a Support Ticket with the following details:
Ticket Type: Service Request
Product: Celonis Platform
Service: Action Flows
Product Area: SAP
Subject: Request for SAP Automation Transport
Description:
SAP ERP version i.e. SAP ECC6 EHP8 SP10
SAP Basis version i.e. SAP BASIS 7.50 SP9
Function module name i.e. /CELONIS/SD_ORDER_CREDIT_RELEA
Installation of the transport
To install the automation package, please follow the same steps to install the RFC module.
Purpose
Via the Celonis Agent, Action Flows can execute any remote enabled function module a SAP system provides, be it a standard one or a custom one. However, there is some standard SAP functionality which is by default not remote enabled. With the Celonis Automation Package (/CELONIS/PROCESS_AUTOMATION):
Celonis provides wrapper function modules which remote enable standard SAP functionality
Celonis provides standard roles and composite roles to create the required SAP user roles for your specific purposes.
Content
Technically, there is one file containing two transports, one containing the roles and one the code. The function modules are structured into subpackages for SD, FI, VN and MM. And also the roles are structured via composite roles. Details to all included roles and function modules can be found below.
Function Module | Description | Functional Implementation | Individual Role | Composite Role |
---|---|---|---|---|
/CELONIS/CORRESPONDENCE_MARK_R | This action completes an open correspondence | The function module does wrap the standard SAP function module CORRESPONDENCE_MARK_RAGL | /CELONIS/CORRESPONDENCE_MARK_R | /CELONIS/AUTOMATION_FI |
/CELONIS/SD_DELIVERY_CREDIT_RE | This Action releases a Credit Block from a delivery | The function module does wrap the standard SAP function module SD_DELIVERY_CREDIT_RELEASE | /CELONIS/SD_DELIVERY_CREDIT_RE | /CELONIS/AUTOMATION_SD |
/CELONIS/SD_ORDER_CREDIT_RELEA | This action releases a Credit Block from a Sales Order | The function module does wrap the standard SAP function module SD_ORDER_CREDIT_RELEASE In addition to the original function module, it can process multiple entries at one | /CELONIS/SD_ORDER_CREDIT_RELEA | /CELONIS/AUTOMATION_SD |
/CELONIS/SD_ORDER_CREDIT_RE_SI | This action releases a Credit Block from a Sales Order | The function module does wrap the standard SAP function module SD_ORDER_CREDIT_RELEASE | /CELONIS/SD_ORDER_CREDIT_RELEA | /CELONIS/AUTOMATION_SD |
/CELONIS/FI_F32_CLEAR | This action clears debitor using settings of payment preferences (FB00) NoteFI_F32_CLEAR has been deprecated. Use FM /CELONIS/FI_GEN_CLEAR instead. | The function module does wrap the SAP transaction F-32 | /CELONIS/FIF32 | /CELONIS/AUTOMATION_FI |
/CELONIS/FI_DOCUMENT_CHANGE | Change financial accounting document NoteFI_DOCUMENT_CHANGE has been deprecated. Use FM /CELONIS/FI_GEN_CHANGE instead. | The function module does wrap the standard SAP function module FI_DOCUMENT_CHANGE | /CELONIS/FI_DOCUMENT_CHANGE | /CELONIS/AUTOMATION_FI |
/CELONIS/FI_DUNBL_CHANGE_DEB | Change debitor dunning block status in the customer master data | The function module does wrap the standard SAP transaction FD02 | /CELONIS/DUNNINGBLOCK | /CELONIS/AUTOMATION_FI |
/CELONIS/FI_DUNBL_CHANGE_DOC | Change dunning block in multiple financial accounting documents | The function module does wrap the standard SAP function module FI_DOCUMENT_CHANGE | /CELONIS/DUNNINGBLOCK | /CELONIS/AUTOMATION_FI |
/CELONIS/FI_CREDITLIMIT_CHANGE | Change customer credit limit data | The function module does wrap the standard SAP function module CREDITLIMIT_CHANGE | /CELONIS/CREDITLIMIT | /CELONIS/AUTOMATION_FI |
/CELONIS/RETRIEVE_ARC_DOCS | This action retrieves archived documents | The function module does wrap the standard SAP function module ARCHIVOBJECT_GET_TABLE | /CELONIS/ARCHIVELINK_ACCESS | /CELONIS/AUTOMATION_ARCHIVELNK |
/CELONIS/STORE_ARC_DOC | This action stores documents in the archive using ArchiveLink | The function module does wrap standard SAP function modules ARCHIVOBJECT_CREATE_TABLE and ARCHIV_CONNECTION_INSERT | /CELONIS/ARCHIVELINK_ACCESS | /CELONIS/AUTOMATION_ARCHIVELNK |
/CELONIS/FI_GEN_CHANGE | This action changes fields in accounting documents | The function module does wrap SAP transactions FB02/FB09 | /CELONIS/FIGEN | /CELONIS/AUTOMATION_FI |
/CELONIS/FI_GEN_CLEAR | This action provides clearing assistance for G/L accounts, Customers and Vendors | The function module does wrap SAP transactions F-03, F-32 and F-44 | /CELONIS/FIGEN | /CELONIS/AUTOMATION_FI |
Role | Content | Type |
---|---|---|
/CELONIS/AUTOMATION_BASIS | This represents the basic role with all the minimum permissions required for performing RFC calls from Action Flows (and Skills). It is included in all other composite roles | Role |
/CELONIS/AUTOMATION | This represents the composite roles containing the permissions required for ALL provided functionality within the package | Composite |
/CELONIS/AUTOMATION_VN | This represents the composite roles contain the permissions required for all provided functionality within the VN sub-package. For the exact roles and function modules, see above | Composite |
/CELONIS/AUTOMATION_FI | This represents the composite roles contain the permissions required for all provided functionality within the FI sub-package. For the exact roles and function modules, see above | Composite |
/CELONIS/AUTOMATION_SD | This represents the composite roles contain the permissions required for all provided functionality within the SD sub-package. For the exact roles and function modules, see above | Composite |
/CELONIS/AUTOMATION_MM | This represents the composite roles contain the permissions required for all provided functionality within the MM sub-package. For the exact roles and function modules, see above | Composite |
Please note that the roles (except for the AUTOMATION_BASIS role) contain the maximum authorization for using the corresponding packages (delivery with *) and the authorization to execute the RFC Function Modules. Please check the authorization with your authorization team and if necessary, please restrict them according to your needs.
Please note that the roles (except for the AUTOMATION_BASIS role) contain the maximum authorization for using the corresponding packages (delivery with *) and the authorization to execute the RFC Function Modules. Please check the authorization with your authorization team and if necessary, please restrict them according to your needs.
IMPORTANT
The role AUTOMATION_BASIS should always be assigned to users which are supposed to be used in connection with Celonis Action Flow capabilities. For further information in that particular role, please see SAP User Role CELONIS/AUTOMATION_BASIS.
The provided transports cover multiple scenarios for role implementation, please select the procedure that covers your use case the best.
Composite Role /CELONIS/AUTOMATION: This role includes all composite roles, please select this when you want to activate access to all provided function modules as painless as possible
Composite Role /CELONIS/AUTOMATION_FI (SD, MM, VN): Those composite roles contain the function modules that are assigned to the specific SAP module, please select this role if you want to grant limited access on a per SAP module level. When creating a user to be used for a certain module, or when adding RFC permissions to a certain user, please consider these RFCs as well.
Individual Roles: Those roles contain the required permissions for individual function modules, please select these roles if you want to grant access on a very detailed level.
ATTENTION
If you want to adjust the roles, it is not recommended to use the provided roles as is, instead derive your own set of roles from our templates and include the required organizational restrictions for your specific use cases. This also prevents the situation on that your customized roles are overwritten when deploying an update package at a later time.
Celonis provides an ready-to-use user role which can be imported in SAP.
This user role contains the permissions that are necessary to get started with the simple and advanced SAP Action.
Permissions included in CELONIS/AUTOMATION_BASIS user role
Like the Extractor setup, Celonis provides a ready-to-use user role that can be imported into SAP for Automation. This role can be considered the minimum set of permissions required to use the integration, use-case specific RFC permissions will be required on top of this.
The user role CELONIS/AUTOMATION_BASIS has permission to use the following BAPIs & RFC calls:
Object | Field | Activities/Values |
---|---|---|
S_RFC | ACTVT | 16 |
S_RFC | RFC_NAME | BAPI_TRANSACTION_COMMIT, BAPI_TRANSACTION_ROLLBACK, FUNCTION_IMPORT_INTERFACE, RFCPING, RFC_FUNCTION_SEARCH, RFC_GET_STRUCTURE_DEFINITION, RFC_GET_FUNCTION_INTERFACE, RFC_PING, DDIF_FIELDINFO_GET, RFC_METADATA_GET |
S_RFC | RFC_TYPE | FUNC |
Object | Field | Activities/Values |
---|---|---|
S_RFC | ACTVT | 16 |
S_RFC | RFC_NAME | RFC1, SYST, /CELONIS, SDIFRUNTIME, SDTX, SRFC, SYSU |
S_RFC | RFC_TYPE | FUGR |
Warning
Please note that FUNC RFC_METADATA_GET and FUGR SDIFRUNTIME, SDTX, SRFC, SYSU have been added compared to the permissions required for skills, as they are required for the communication via JCo. Thus, these permissions need to be added if you are switching from an agent older than 1.0.0.
Warning
Note that RFC_METADATA_GET might not be present in old SAP installations. In case it's not present, our integration will resort to a fallback solution and work as well.
→ Depending on your use case it might be necessary to manually add permissions for additional BAPIs or RFC calls in addition to the ones included in the user role.
Use case examples:
If you would like your users to be able to change a purchase order, you will have to add permissions for BAPI_PO_CHANGE.
To post a goods movement document for an order that has been delivered by the vendor, you will need to add permissions for BAPI_GOODSMVT_CREATE.
Missing permissions
In case of your user lacks permissions for a specific SAP action that is supposed to be performed, a standard way of dealing with this is to leverage transaction SU53 within SAP to communicate with the SAP basis the authorizations required.
Minimal set of recommended permissions
Instead of importing the user role, creating the corresponding role manually or adding the required permissions to an existing role is possible. The following minimal set of permissions is required (or at least recommended) for using Celonis Agent. Please note, that depending on your use case it might be necessary to manually add permissions for additional BAPIs or RFC calls in addition to the ones included here.
For SAP release 7.10 or newer:
Object | Field | Activities/Values |
---|---|---|
S_RFC | ACTVT | 16 |
S_RFC | RFC_NAME | BAPI_TRANSACTION_COMMIT, BAPI_TRANSACTION_ROLLBACK, FUNCTION_IMPORT_INTERFACE, RFCPING, RFC_FUNCTION_SEARCH, RFC_GET_STRUCTURE_DEFINITION, RFC_GET_FUNCTION_INTERFACE, RFC_PING, DDIF_FIELDINFO_GET, RFC_METADATA_GET |
S_RFC | RFC_TYPE | FUNC |
For older SAP releases, permissions have to be granted on FUGR level, requiring:
Object | Field | Activities/Values |
---|---|---|
S_RFC | ACTVT | 16 |
S_RFC | RFC_NAME | RFC1, SYST |
S_RFC | RFC_TYPE | FUGR |
It is important to understand that via the advanced/generic action, ALL remote-enabled function modules an SAP system contains can be used and allow the implementation of any use case. To extend automation capabilities, generic RFC calls can use any existing remote-enabled functions modules (also custom ones implemented by your SAP basis or those included in the SAP Automation package provided by Celonis).
The Make an RFC Call module generates the inputs based on the Import, Changing, and Table parameter definitions on the Remote Function Module. If no such parameters are defined, then no inputs will show in the AFlow module. The interfaces are generated based on the Import, Changing, Export, and Table parameter definitions. The execution is marked as "failed" if an error is found on the RETURN or ET_MSG parameter.
Necessary permissions for Generic RFC call
SAP user needs permission for the RFC that is called and also for the corresponding action in the SAP system itself.
Make an RFC Call
Performs an arbitrary authorized RFC call.
Connection | Establish a connection to your SAP account. |
Remote Function Module | Enter (map) the module for which you want to perform the API call. Based on the specified function, dynamic fields appear for you to fill and execute the action. |
Advanced settings: | |
BAPI Transaction Handling |
|
Example - Update Delivery
The following RFC call returns the specified delivery details from your SAP account:
Remote Function Module: WS_DELIVERY_UPDATE
Delivery: 0080018919
Matches of the search can be found in the module's Output under Bundle.
In this example, the specified delivery details were returned: