Parameters

Internal Parameters

These parameters allow emails to include context-specific information such as workflow events, order details, requestor names, item lists, and actionable links, ensuring messages are personalized, informative, and actionable.

Parameters	Description
RECIPIENT	The individual or group that receives the message, file, or notification.
INDEX_FILE_ID	Unique identifier assigned to the index file within the system.
SERVER_LINK	URL or network path pointing to the relevant server resource.
CATALOG_NAME	The name of the catalog or dataset being referenced.
REQUESTING_ORG_NAME	The organization of the user who initiates the process.
COUNT_ITEMS	Number of items included in the current transaction, request, or dataset.
EXPIRE	Expiration status or date indicating when the resource or request becomes invalid.
VALID_START_DATE	Date when the resource, request, or dataset becomes valid for use.
VALID_END_DATE	Date when the resource, request, or dataset expires or becomes inactive.
ITEMS_LIST_HTML	HTML-formatted list of items, used for rendering in emails or web pages.
MYCART_NAME	User-defined or system-assigned name of the shopping cart or collection of items.
GLB_OBJECT_TYPE	Type of object being processed globally across the system (e.g., file, request, item).
CREATOR	User or system entity that created the record, file, or request.
GLB_SERVER_URL	Global server endpoint URL for accessing shared resources. https://cloud.beneering.com/dc4/ - PROD (Produktion) https://cloud-t.beneering.com/dc4/ - QA (Testing) https://cloud-d.beneering.com/dc4/ - DEV (Development)
GLB_ORG_NAME	Global name of the organization associated with the request or resource.
MYCART_NUMBER	Unique identifier assigned to a specific shopping cart instance.
GLB_EVENT_TYPE	Type of event being logged or triggered globally (e.g., approval, submission, update).
GLB_LANGUAGE	Language code or name used for content localization or communication.
ERRORS	List or count of errors encountered during processing.
WARNINGS	List or count of warnings generated during processing (non-fatal issues).
EXPIRE_TAB	Tab or section indicating expiration-related details in the UI or dataset.
EXPIRE_DAYS	Number of days before the request or resource expires.
GOLIVE_DATE	Date on which the request, system, or resource goes live.
APPROVER	User or role responsible for approving the request or transaction.
REQUESTOR	User or role who initiated the request.
SENDER	User, system, or process responsible for sending the message or notification.
REGISTRATION_LINK	URL provided for user or organization registration.
CHANGE_PASS_LINK	URL provided for password change/reset functionality.
LOGIN	User identifier used to log into the system (e.g., username or email).
REPORT_NAME	Name or title of the report being generated or referenced.
STATUSES	Current states of items, requests, or processes (e.g., pending, approved, rejected).
KEY_FIELDS	Set of primary fields used for indexing, searching, or identifying records.
PIVOT_FIELDS	Fields used to group or summarize data in reports or dashboards.
INDEX_FILE_DETAILS	Metadata or descriptive details about the index file.
TYPE	General classification or category of the object, request, or resource.

SAP parameters - common

SAP parameters are configuration values that control the behavior of the SAP system at runtime. Common parameters typically apply across multiple modules and processes, ensuring consistent system operation.

SAP Parameters	Description
`GLB_SERVER_URL`	`The global server endpoint URL used by SAP applications to connect with backend services or resources.`
`EVENT_NAME`	`Name of the event triggered in the SAP system (e.g,, creation, update, approval).`
`CREATED_BY`	`SAP user ID or system process that created the object or record.`
`CREATED_AT`	`Unformatted SAP timesamp. Timestamp (YYYYMMDDHHMMSS) indicating when the object or record was created in the system.`
`FORMATTED_CREATED_AT`	`Human-redable formatted date/time of record creation, typically displayed in UI or reports.`
`LANGUAGE`	`Language key (e.g,, EN, DE, FR) used for localization of messages, labels or forms.`
`CREATOR_NAME`	`Full name of the user or entity that created the record (mapped CREATED_BY).`
`CHANGER_NAME`	`Full name of the user or entity who last modified the record.`
`CUST_PORG_NAME`	`Customer's purchasing organization name, representing the organizational unit responible for procurement.`
`CUST_PGRP_NAME`	`Customer's purchasing group name, representing the group of buyers responisble for specific materials or services.`
`PROCESS`	`Business process identifier or name (e.g,, Purchase Requsition, Sales Order, Invoice).`
`PD_OBJ_ID`	`Unique identifier of the process document object within SAP.`
`PD_NAME`	`Name or title assigned to the process document.`
`PD_DESCRIPTION`	`Detailed description of the process document's purpose or contents.`
`PD_ITEMS_LIST_HTML`	`HTML-formatted list of items within the process document, often used in emails, reports, or SAP Fiori apps.`

SAP parameters - per object

Per-object parameters are configuration values that apply specifically to an individual object (such as a document, record, user, or transaction) rather than the entire SAP system. These parameters allow fine-tuned control of system behavior on an object level.

RFX:

Static (always):

RFX Parameters	Description
`RFQ_ID`	Unique identifier of the Request for Quotation (RFQ) document in the system.
`END_DATE`	Timestamp (YYYYMMDDHHMMSS) indicating when the object or record was closed or ended. System date field representing when the RFQ submission period ends.
`FORMATTED_END_DATE`	Human-readable formatted end date, displayed in reports or UI (e.g., “22-Aug-2025 18:00”).
`OPEN_DATE`	Timestamp (YYYYMMDDHHMMSS) indicating when the object or record was opened. Date when the RFQ becomes open/active for suppliers to view and submit quotations.
`FORMATTED_OPEN_DATE`	Human-readable formatted open date for display purposes.
`RFQ_NAME`	Name or title of the RFQ, often used as a quick identifier in lists or dashboards.
`RFQ_DESCRIPTION`	Detailed description of the RFQ, providing context on the goods/services requested.
`RFM_ID`	Unique identifier for the Request for Material (RFM) document in the system.
`RFM_DESCRIPTION`	Description of the RFM, typically explaining the material needs or requirements.
`SUPPLIER_ID`	Unique identifier of the supplier/vendor in the SAP Vendor Master
`SUPPLIER_NAME`	Full legal or trade name of the supplier/vendor associated with the RFQ/RFM.

RFQ Email Event Types	Description
'/BENMSG/RFQ_EMAIL_CRT_NEW' or	An email notification is sent to the CRT (creator of the request). The CRT is the person who receives the email, ensuring they are informed that a new RFQ has been generated and requires their attention.
'/BENMSG/RFQ_EMAIL_CRT_APPR' or	CRT receives an email notification that the request has been approved.
'/BENMSG/RFQ_EMAIL_CRT_REJE' or	CRT receives an email notification that the request has been rejected and may require corrections.
'/BENMSG/RFQ_EMAIL_CRT_SUBM' or	CRT receives an email notification confirming the request has been submitted for review.
'/BENMSG/RFQ_EMAIL_CRT_OPEN' or	CRT receives an email notification that the request is currently open and active in the workflow.
'/BENMSG/RFQ_EMAIL_CRT_CLSE' or	CRT receives an email notification that the request has been closed and the workflow is completed.
RFM Email Event Types	Description
'/BENMSG/RFM_EMAIL_PUR_APPR' or	Triggered when an RFM is approved by the purchaser (PUR). An email notification is sent to inform them that their request has been approved.
'/BENMSG/RFM_EMAIL_PUR_SUBM' or	Triggered when an RFM is approved by the purchaser (PUR). An email notification is sent to inform them that their request has been submitted.
'/BENMSG/RFM_EMAIL_PUR_CANC' or	Triggered when an RFM is approved by the purchaser (PUR). An email notification is sent to inform them that their request has been canceled.
'/BENMSG/RFM_EMAIL_PUR_APPR_ACC' or	Triggered when an RFM is approved by the purchaser (PUR). An email notification is sent to inform them that their request has been accepted.
'/BENMSG/RFM_EMAIL_PUR_APPR_REJ'.	Triggered when an RFM is approved by the purchaser (PUR). An email notification is sent to inform them that their request has been rejected.

RECIPIENT- (The primary recipient of the notification or message (can be a supplier, partner, or organization).
SUPPLIER_LIST- (List of suppliers (IDs or codes) associated with the RFQ/RFM, typically used for distributing notifications.)
SUPPLIER_LIST_HTML- (HTML-formatted version of the supplier list, optimized for inclusion in emails or web-based reports.)
PARTNER_ID- (Unique identifier of a business partner (customer, supplier, or internal partner) in the SAP system.)

RFQ Email Event Types	Description
'/BENMSG/RFQ_EMAIL_SUP_CANC' or	Email notification sent to suppliers when an RFQ is canceled.
'/BENMSG/RFQ_EMAIL_SUP_CLSE' or	Email notification sent to suppliers when an RFQ is closed (no longer open for responses).
'/BENMSG/RFQ_EMAIL_SUP_OPEN' or	Email notification sent to suppliers when an RFQ is opened and ready for quotations.
'/BENMSG/RFQ_EMAIL_SUP_SUBM' or	Email notification sent to suppliers when an RFQ has been submitted for their response.
'/BENMSG/RFQ_EMAIL_SUP_REOPEN'.	Email notification sent to suppliers when a previously closed RFQ is reopened.

PARTNER_ID- (Unique identifier of a business partner (customer, supplier, or internal partner) in the SAP system.)
RECIPIENT- (The primary recipient of the notification or message (can be a supplier, partner, or organization).
SUPPLIER_NAME - Full name of the supplier/vendor associated with the RFQ/RFM or transaction
SUPPLIER_ID - Unique identifier of the supplier/vendor in the SAP system

RFM Email Event Types	Description
'/BENMSG/RFM_EMAIL_SUP_APPR' or	Email notification sent to the supplier when a Request for Material (RFM) is approved.
'/BENMSG/RFM_EMAIL_SUP_REJE'	Email notification sent to the supplier when a Request for Material (RFM) is rejected.

RECIPIENT- (The primary recipient of the notification or message (can be a supplier, partner, or organization).

RFM Email Event Types	Description
`/BENMSG/RFM_EMAIL_ACT_CHAT`	Email notification triggered when a chat or message activity is initiated or updated within the context of a Request for Material (RFM). This event is typically used to notify relevant participants (e.g., supplier, purchaser, requester) of new communication related to the RFM.

When: REQUESTOR
- RECIPIENT- The supplier and approver are notified when the requestor initiates or updates a chat/message in the RFM context.
When: SUPPLIER
- RECIPIENT- The requestor and approver are notified when the supplier initiates or updates a chat/message in the RFM context.
When: APPROVER
- RECIPIENT -The requestor and supplier are notified when the approver initiates or updates a chat/message in the RFM context.

RFQ Email Event Types	Description
'/BENMSG/RFQ_EMAIL_SUP_ADDED' or	Email notification sent when a supplier is newly added to an RFQ.
'/BENMSG/RFQ_EMAIL_SUP_UPDATE' or	Email notification sent when details of an RFQ are updated/changed and suppliers need to be informed.
'/BENMSG/RFQ_EMAIL_SUP_REMINDER'	Reminder email notification sent to suppliers for pending or upcoming RFQ deadlines.

RECIPIENT- (The primary recipient of the notification or message (can be a supplier, partner, or organization).
SUPPLIER_NAME- The name of the supplier associated with the notification. This identifies which supplier is being informed or reminded regarding the RFQ.
PARTNER_ID- A unique identifier for the supplier or business partner in the system. Used for system-to-system communication, reporting, or integration with supplier master data.

RFQ Email Event Types	Description
`/BENMSG/RFQ_EMAIL_CRT_REJE`	Email notification sent when a Request for Quotation (RFQ) creation request is rejected. The notification is typically delivered to the requester or creator, informing them of the rejection reason or status.
`/BENMSG/RFM_EMAIL_PUR_APPR_REJ`	Email notification sent when a Request for Material (RFM) approval request is rejected by the purchasing organization. The notification is delivered to the requester and/or relevant stakeholders, indicating that the approval did not proceed.

REJECTION_NOTE- Textual note or comment provided when rejecting an RFQ/RFM, usually containing the reason for rejection.
REJECTED_BY- Identifier (user ID, name, or role) of the person or system that performed the rejection action.
REJECTION_DATE- System timestamp indicating when the rejection action occurred.
FORMATTED_REJECTION_DATE -Human-readable version of the rejection date, formatted for display in emails, reports, or UI (e.g., 22-Aug-2025 14:35).

RFM Email Event Types	Description
`/BENMSG/RFM_EMAIL_ACT_CHAT`	Email notification triggered when a chat or discussion activity occurs in relation to a Request for Material (RFM). This event is used to notify involved stakeholders (e.g., requester, purchaser, supplier) that a new chat message, update, or communication has been added to the RFM, ensuring collaboration and timely follow-up.

CHAT_MESSAGE_TEXT- The content of a chat message related to an RFQ/RFM.
CHAT_MESSAGE_CREATED_BY- Identifier (user ID or name) of the person who authored the chat message.
CHAT_MESSAGE_FORMATTED_DATE- Human-readable date and time when the chat message was created, formatted for display (e.g., 22-Aug-2025 15:10).
ASSIGNMENT_NOTE- Additional note or comment entered when assigning an RFQ/RFM to a user or role.
ASSIGNED_TO- Identifier (user ID, role, or organization unit) to which the RFQ/RFM has been assigned.
ASSIGNMENT_DATE- System timestamp recording when the assignment action was performed.
FORMATTED_ASSIGNMENT_DATE- Human-readable version of the assignment date/time, intended for use in emails, reports, or UI displays.

Confirmation:

RECIPIENT- (The primary recipient of the notification or message (can be a supplier, partner, or organization).

Confiramtion Parameters	Description
'/BENMSG/CNF_EMAIL_SUP_REJE' or	Email notification sent to the supplier when a confirmation is rejected.
'/BENMSG/CNF_EMAIL_SUP_SUBM' or	Email notification sent to the supplier when a confirmation has been successfully submitted.
'/BENMSG/CNF_EMAIL_SUP_TRANSF' or	Email notification sent to the supplier when a confirmation has been transferred within the system (e.g., moved to another responsible unit or process step).
'/BENMSG/CNF_EMAIL_SUP_TRANSF_E'.	Email notification sent to the supplier when an error occurs during the transfer of a confirmation.

PURCHASE_ORDER- The unique identifier (number) of the purchase order associated with the confirmation event. This links the email notification to the relevant order.
PURCHASE_ORDER_ITEM- The specific line item number within the purchase order. Used to indicate which item in the order the confirmation event refers to.
PORD_ITEM_NAME- The name or description of the purchase order item (e.g., material or service name). Provides a human-readable reference for the recipient to easily identify the item.

Order:

Order Parameters	Description
`'/BENMSG/ORD_EMAIL_SHIP_ERR'.`	Email notification sent when an error occurs in the shipping process of an order. This event typically alerts suppliers, logistics partners, or internal stakeholders that the shipment could not be processed or contains issues requiring attention.

DOC_NUMBER- The unique document number assigned to the order. Used to identify and track the specific order in the system.

Order Parameters	Description
`'/BENMSG/ORD_EMAIL_SUP_CRT' OR`	Email notification sent to the supplier when a new order is created and assigned to them.
`'/BENMSG/ORD_EMAIL_SUP_UPD' OR`	Email notification sent to the supplier when an existing order is updated (e.g., changes in quantities, dates, or terms).
`'/BENMSG/ORD_EMAIL_SUP_DEL'`	Email notification sent to the supplier when an order is deleted or canceled.

VENDOR_NO- The supplier’s unique identification number in the system. Ensures correct linkage between the order and the registered supplier.
VENDOR_NAME- The name of the supplier/vendor associated with the order. Provides a human-readable reference for recipients to easily identify the business partner.
PURCHASE_ORDER- The unique purchase order number linked to the event.
GLB_SERVER_URL- A system-generated link (URL) directing the recipient to the global server or portal where they can view, acknowledge, or act on the order details.

Central Workflow:

RECIPIENT- (The primary recipient of the notification or message (can be a supplier, partner, or organization).
GLB_SERVER_URL- A system-generated link (URL) directing the recipient to the global server or workflow portal where they can access and manage the workflow item.
EVENT_NAME- The name of the triggered event (e.g., work item created, replaced, forwarded). Provides clarity on why the notification was sent.
MYCART_NUMBER- The unique identifier for the shopping cart related to the workflow item. Used for tracking and reference.
MYCART_NAME- The user-defined name or title of the shopping cart, providing a human-readable reference for easy identification.

Parameters	Description
`1.'/BENMSG/CWF_BUS2105_MSG_WI_CRT'`	Email notification triggered when a new workflow item (WI) of type BUS2105 is created. This typically informs the responsible user(s) that a new task or work item requires attention.
`2.'/BENMSG/CWF_BUS2105_MSG_WI_REP'`	Email notification triggered when a workflow item (WI) of type BUS2105 is reassigned, updated, or replaced. This informs the new assignee(s) or stakeholders of changes to the workflow item.

ITEMS_LIST_HTML- A formatted HTML list of items included in the shopping cart or workflow context, allowing recipients to view item details directly within the email.
REDIRECT_URL- A link that redirects the recipient to the relevant workflow task or system screen for further action.
APPROVE_URL- A direct action link embedded in the email that allows the recipient to approve the workflow item with a single click.
REJECT_URL- A direct action link embedded in the email that allows the recipient to reject the workflow item with a single click.
REQUESTOR- The creator of the request (e.g., shopping cart or workflow item). This identifies who initiated the workflow and is the person usually notified of status updates.

Parameters	Description
`'/BENMSG/CWF_BUS2105_MSG_WI_REJ'`	Email notification sent when a workflow item (WI) of type BUS2105 is rejected. This informs the requester or relevant stakeholders that the task or approval associated with the workflow item did not proceed and may require further action.

COMMENT- The remark, reason, or note entered by the approver/reviewer when rejecting or acting on the workflow item. This gives the requester clear feedback on why the workflow item was rejected or what additional actions may be needed.
APPROVER- The name or identifier of the approver who took action on the workflow item (approve/reject). Provides accountability and transparency in workflow tracking.
ITEMS_LIST_HTML- A formatted HTML representation of items (e.g., shopping cart contents, service entry lines) included in the workflow. Allows recipients to quickly review item details directly in the email without logging into the system.

Parameters	Description
`'/BENMSG/CWF_BUS2105_MSG_WF_FIN'`	Email notification sent when a workflow of type BUS2105 is completed. This informs all relevant stakeholders that the workflow process has finished successfully and no further actions are required.

ITEMS_LIST_HTML- A formatted HTML representation of items (e.g., shopping cart contents, service entry lines) included in the workflow. Allows recipients to quickly review item details directly in the email without logging into the system.

Internal Parameters

Parameters

Description

SAP parameters - common

SAP Parameters

Description

SAP parameters - per object

RFX:

RFX Parameters

Description

RFQ Email Event Types

Description

RFM Email Event Types

Description

RFQ Email Event Types

Description

RFM Email Event Types

Description

RFM Email Event Types

Description

RFQ Email Event Types

Description

RFQ Email Event Types

Description

RFM Email Event Types

Description

Confirmation:

Confiramtion Parameters

Description

Order:

Order Parameters

Description

Order Parameters

Description

Central Workflow:

Parameters

Description

Parameters

Description

Parameters

Description