SAP S/4HANA Extension :: Integration Framework

Installation

Go to Extensions → Marketplace → Search for extension SAP S/4HANA Extension → Click the Install action in "ACTIONS" menu

Figure 1. SAP S/4HANA Extension at Marketplace

Figure 2. SAP S/4HANA Extension Installation : Step 1

Figure 3. SAP S/4HANA Extension Installation : Step 2

Figure 4. SAP S/4HANA Extension Installation : Step 3

Figure 5. SAP S/4HANA Extension Installation : Step 4

Figure 6. SAP S/4HANA Extension Installation : Complete

Configurations

Configuration properties are pre-populated which user can modify as per the requirement.
There are different tabs like CONNECTION, DATA SETTINGS and ENDPOINTS from which the user can configure the properties to get SAP S/4HANA connector working.
Configure the following properties from Extensions → Settings.

1. CONNECTION

SAP S4HANA Extension Settings Connection

Variable

Description

Example

3DEXPERIENCE Agent id

3DEXPERIENCE Agent id for Extension

3DEXPERIENCE Agent secret

3DEXPERIENCE Agent secret for Extension

Base URL to SAP

Base url of SAP S/4HANA

https://<host address>

SAP Client ID

Client id of SAP S/4HANA

500

SAP S/4HANA Login name

User name to login to SAP S/4HANA

SAP S/4HANA Password

Password for the user name

2. DATA SETTINGS

The below shown values are from a demo point of view.

SAP S4HANA Extension Settings Data Settings

Variable

Description

Example

BOM Category

-

M

BOM Header Qty Baseunit

-

1

BOM Item Category

-

C

BOM Line Condensed

-

true

BOM Variant Usage

1 = Engineering BOM, 2 = Production BOM, Default = 1

2

Business Object Type Name

BUS1001006

Change Number Release Key

-

0

Change Number Status

-

1

Default Quantity

Single item quantity

1

Document Created by CAD

-

false

Include Revision Version

Example; A.1

false

Inventory Valuation Procedure

-

S

Language

EN = English

EN

Material

SAP Object Type

Material

Material BOM

SAP Object Type

MaterialBOM

Multiple BOM Alt

false

Price Unit Quantity

-

1

Plant number

-

1100

Product Configurable

-

true

Product Group

Group at SAP S/4HANA

ZFORK

Product Type

Type at SAP S/4HANA

FERT

3. DEVELOPMENT

As of release V1 , the DEVELOPMENT tab is meant for development environment. It is used to generate Item numbers and Change Action numbers as required by the destination system (SAP S/4HANA).

4. ENDPOINTS

Variable

Description

Example

BOM URI

SAP S/4HANA API uri used to send payload for Send BOM & Send BOM with CA use case

sap/API_BILL_OF_MATERIAL_SRV;v=2/MaterialBOM

CA URI

SAP S/4HANA API uri used to send payload for Send CA use case

sap/opu/odata/sap/API_CHANGEMASTER;v=2/A_ChangeMaster

Item Revise URI

SAP S/4HANA API uri used to send payload for Revise Engineering Item use case

sap/opu/odata/sap/API_PRODUCT_SRV/A_Product('<ITEM_NAME>')

Material CA URI

SAP S/4HANA API uri used to send payload for Associate CA use case

sap/opu/odata/sap/API_CHANGEMASTER; v=2/A_ChangeMaster('<CA_NUMBER>')/to_ChangeMstrObMgReMaterial

Product URI

SAP S/4HANA API uri used to send payload for Send Engineering Item use case

sap/opu/odata/sap/API_PRODUCT_SRV/A_Product

Send Attachment URI

SAP S/4HANA API uri used to send attachment for Send Document use case

sap/opu/odata/sap/API_CV_ATTACHMENT_SRV/AttachmentContentSet

Token URI Endpoint

SAP S/4HANA API uri to fetch the token

sap/opu/odata/sap/API_PRODUCT_SRV/

SAP S/4HANA service is available out of the box. This SAP S/4HANA service is mapped with the events under event mapping.
- A Service corresponds to a job queue. Every event mapping needs to specify to which service it belongs. A service can be configured to run its jobs in sequence OR parallel execution. Either create a single service to handle all the events or create separate services for each event mapping.

Event Mapping

Need to enable what events needs to be published from the DS tenant using Event Publishing app.
- Event mapping holds the information about which use-case needs to be executed when the event is received. It is a binding between the event and job-request.

Example for configured events publishing are as follows
Engineering item → Created, Status Changed, Versioned, etc…

Event mapping need to be created so that required use case should get executed on receiving the event from DS tenant. While creating the events we need to provide the details like
- Service name
- Agent
- Event class and its type
- Configuration to be invoked
Following event mapping is available out of the box.

Events

Event Categories & Types

Created

Status Changed

Versioned

Computed

Connected

Disconnected

⊟ Event Category :
Collaborative Spaces Control

├ 🗎 Document

├ 🧊 Engineering Item

🔵

⊟ Event Category : Change
Process

├ 🄲🄰 Change Action

🔵

SAP-S/4HANA-Create-Eng-Material-Send-Eng-Material - gets invoked on creation of an Engineering item in DS tenant.
SAP-S/4HANA-Send-BOM - gets invoked on release of an engineering item in DS tenant.
SAP-S/4HANA-Send-CA - gets invoked on creation of Change Action in DS tenant.
SAP-S/4HANA-Release-CA-Send-BOM - gets invoked on release of a Change Action in DS tenant.
SAP-S/4HANA-Revise-Engineering-Item - gets invoked on creation of revision of an Engineering item in DS tenant.
SAP-S/4HANA-Send-Document - gets invoked on release of an Engineering item in DS tenant.

SAP S/4HANA use cases use token to connect to the destination url for sending the payload.

In general, any SAP S/4HANA use case, use the below javascript classes.

Component

Details

1. Use case invoker

It invokes the processor of the specific use case. The invoker is also responsible to pass in the optional set of properties to the use case processor

2. Processor

It has the logic to fetch the data, build the payload and send it to SAP S/4HANA using the Destination Handler.

3. Token Resolver

It fetches the authentication token by connecting to the corresponding SAP S/4HANA url

4. Destination Handler

It has the logic to connect to the SAP S/4HANA urls by performing necessary actions and send the payload.

5. Logger

Logs the details of the items being accessed in the use case.

6. Helper

It has the methods to build the payload for SAP S/4HANA.

7. Util

It has the utility methods that helps to transform the payload data.