Enable Event Driven Configuration

Describes how to enable an Event-Driven Configuration for modules using SAP S/4HANA workflows and SAP Fieldglass workflows.

Prerequisites

Only users with Configuration Manager permissions can perform these tasks.

If adding attachments to the Service Entry Sheet (SES) payload, the company configuration Integration Ariba Include SES Attachments must be enabled.

Context

An Event Driven Config must be set up for each module used.

For SAP S/4HANA-initiated workflows, enable event-driven configurations for the Statement of Work, SOW Revision, SOW Invoice, and Event modules.

For SAP Fieldglass-initiated workflows, enable event-driven configurations for the Fee, Schedule, Expense Sheet, and Time Sheet modules.

SAP S/4HANA-Initiated Workflows

Procedure

From the Configuration Manager Self-Service Dashboard, select Event Driven Config.
To add a new event-driven configuration, select New on the Event-Driven Config List page.
Select one of the valid modules from the Module drop-down menu.
Valid values:
- Statement of Work
- Statement of Work Revision
- SOW Invoice
- Event
The Event Driven Config Id auto-populates with the company code, followed by the module name and a randomly generated ID number.

Enter the information for each module as described in the Module Configuration Table – SAP S/4HANA Workflows :

In the following configuration table, any highlighted endpoints/URLs are placeholders, as these values are subject to change based on the system and middleware connectivity settings an SAP S/4HANA client has. Replace the values with client-specific values as needed.

Use the setup details in the following table for SAP S/4HANA initiated workflows.

Module Configuration Table – SAP S/4HANA Workflows

Configuration Property

Configuration Value

Module

Valid values:

Statement of Work
SOW Revision
SOW Invoice
Event

Ariba Realm ID

This field must be populated if more than one event driven configuration is active for the module, activity, and delivery of outbound messages to a differing endpoint.

For example: If another Event Driven Configuration is present, entitled [BUYER]_EVENT_SES_PUSH_22K, then define a value in this field – such as “1”. Both Event Driven Configurations must define values for this field.

If this is the only Event Driven Configuration for the push of the EVENT module outbound, then it can remain blank.

Event Driven Config ID

Replace the auto-populated value as follows:

Module	Event Driven Config ID
Statement of Work	[BUYER]_SOW_ACK_PUSH
SOW Revision	[BUYER]_SOWR_ACK_PUSH
SOW Invoice	[BUYER]_SOW_INV_ACK_PUSH
Event	[BUYER]_EVENT_SES_PUSH_4R2

Activity

Upload Data – for SOW, SOWR, and SOW INV

Submit, Approved – for Event

Transporter Class

For Events with attachments, use:

insite.webservices.outbound.SAPS4MIMETransporter

Otherwise, use:

insite.webservices.outbound.SAPS4Transporter

Auth Type

Leave this field blank, which by default uses certificate-based authentication for the outbound triggered messages being sent to CIG and SAP Business Network.

Test End Point or Prod End Point

Enter the following in the appropriate field.

https://edge-qa-test.cig.cfapps.xxx.xxxxxx.ondemand.com/cxf/receiveFGSOAP

Test Notification Emails or Prod Notification Emails

Leave blank.

Notify At Retry

Leave default value.

Custom Script

Enter the custom script corresponding to the module as follows:

Module	Custom Script
Statement of Work	SOW_ACK_PUSH
SOW Revision	SOWR_ACK_PUSH
SOW Invoice	SOW_INV_ACK_PUSH
Event	SES_4R2_EVENT_PUSH

Transport Status

Push

Return to the Event Driven Config List and repeat the process for all four modules.

SAP Fieldglass-Initiated Workflows

From the Event Driven Config List page, select New.
The Add Event Driven Config page opens.
Select one of the valid modules from the Module drop-down menu.
Valid values:
- Fee
- Schedule
- Expense Sheet
- Time Sheet
The Event Driven Config Id auto-populates with the company code, followed by the module name and a randomly generated ID number.

Enter the information for each module as described in the Module Configuration Table – SAP Fieldglass Workflows.

Use the setup details in the following table for SAP Fieldglass-initiated workflows.

Module Configuration Table – SAP Fieldglass Workflows

Configuration Property

Configuration Value

Module

Fee

Schedule

Expense Sheet

Time Sheet

Create Revision?

For a new configuration, No.

Ariba Realm ID

This field must be populated if more than one event-driven configuration is active for the module, activity, and delivery of outbound messages to a differing endpoint.

For example: If another Event Driven Configuration is present, entitled [BUYER]_Fee_SES_PUSH_22K, then define a value in this field, such as “1”. Both Event Driven Configurations must define values for this field.

If this is the only Event Driven Configuration for the push of one of these modules outbound, then it can remain blank.

Event Driven Config ID

Replace the auto-populated value as follows:

Module	Event Driven Config ID
Fee	[BUYER]_FEE_SES_PUSH_4R2
Schedule	[BUYER]_SCHEDULE_SES_PUSH_4R2
Expense Sheet	[BUYER]_ES_SES_PUSH_4R2
Time Sheet	[BUYER]_TS_SES_PUSH_4R2

Activity

Submit, Approved

Transporter Class

If the SES includes an attachment, use:

insite.webservices.outbound.SAPS4MIMETransporter

Otherwise, use:

insite.webservices.outbound.SAPS4Transporter

Auth Type

Leave this field blank, which by default uses certificate-based authentication for the outbound triggered messages being sent to CIG and SAP Business Network.

Test End Point or Prod End Point

Enter the following in the appropriate field.

https://edge-qa-test.cig.cfapps.xxx.xxxxxx.ondemand.com/cxf/receiveFGSOAP

Test Notification Emails or Prod Notification Emails

Leave blank.

Notify At Retry

Leave default value.

Custom Script

Enter the custom script corresponding to the module as follows:

Module	Custom Script
Fee	SES_4R2_FEE_PUSH
Schedule	SES_4R2_SCHEDULE_PUSH
Expense Sheet	SES_4R2_ES_PUSH
Time Sheet	SES_4R2_TS_PUSH

Transport Status

Push

Return to the Event Driven Config List and repeat the process for all four modules.