Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
lm_allen
Explorer
0 Kudos
262

Background

There are a few blogs already available showing how to enhance an enterprise service, as well as an SAP guide (SAP Note 2474420 - Enterprise Services Enhancement Guide).  These resources though do not cover usage of the data type after the enhancement.  Hopefully the below blog will help fill in the gap. 

Step By Step Guide

In this example wanted to enhance the below Service Interface

lm_allen_19-1736769521279.png

Looking at the message type we can get the data type used

lm_allen_20-1736769521280.png

We can enhance this data type to add fields to the main message, equally can enhance sub-nodes if required.

 

In SLD

created product

lm_allen_21-1736769521280.png

Create Software component linked to this product

lm_allen_22-1736769521281.png

Add Installation Time dependency to component wish to enhance

lm_allen_23-1736769521281.png

 

In ESR

Import software component

lm_allen_24-1736769521281.png

Once imported can see the dependency set in SLD under the 'Basis Objects'

lm_allen_25-1736769521282.png

Create namespace

lm_allen_26-1736769521282.png

Add Data Enhancement Type

lm_allen_27-1736769521282.png

Nb: worth naming DTE based on data type to be enhanced (ie DTE_TransportationDocumentRequestMessage in this case would be a better name than one used in this example, useful if enhancing multiple nodes)

 

Set the Data Type you with to enhance (selected from the underlying dependency).  This can be a data type at any node level

lm_allen_0-1736770691504.png

Add fields that you want in the enhancement

lm_allen_29-1736769521283.png

Save and activate

If we now view the message type we are enhancing can see new field added.  Note this only shows under the S4CORE 107 Dependency object in our new Software Component and not in the standard SAP Software component

lm_allen_30-1736769521283.png

 

lm_allen_31-1736769521284.png

 

In S4 Hana ABAP code in a BADI is used to populate these new fields.

 

When creating an Iflow in NWDS:

Use the original SAP standard service interface

lm_allen_32-1736769521284.png

lm_allen_33-1736769521284.png

lm_allen_34-1736769521284.png

 

Although this is linked to the original unenhanced Message type it is setup as XI compatible, this means that it will accept any message structure (root node remains unchanged so would still work even if not XI compatible)

lm_allen_35-1736769521284.png

For operation mapping - again use the original service interface

lm_allen_36-1736769521285.png

 

For the message mapping however you need to use the enhancement message type under the newly created software component since this will show the newly added fields.

lm_allen_37-1736769521285.png

 

Labels in this area