Skip to Content

Last year on November we have first met the real S/4HANA, which has the logistics simplifications initial pack: most important ones for me were the Business Partner approach ( I’ll share my experiences later)  and MM-IM datamodel change.

To be honest these major changes scared me a lot, when I have first read this paragraph in the simplification document:

With S/4HANA this data model has been changed significantly. The new de-normalized table MATDOC has been introduced which contains the former header and item data of a material document as well as a lot of further attributes. Material document data will be stored in MATDOC only and not anymore in MKPF and MSEG.”

However new code-line or new component S4CORE is very strong about keeping the existing functionaility. I mean with the new component has SAP ERP 6.0 world in S/4HANA as DDIC definition as well as data base object. For keeping existing solution landscape up and run there are Core Data Service (CDS) Views assigned as proxy objects to all those tables ensuring that each read access to one of the mentioned tables below still returns the data as before in SAP ERP 6.0. this means; S4CORE will not kill or harm your running environment.

Let me show what I mean with live samples:

I have posted a IM document by entering goods into stock by using 561 movement type, here is the entry in new de-normalized table called MATDOC:

S4HANA_S4CORE_Sarhan_10.jpg

I really like the new table, it has all the information that you need when you want investigate or to create a report. In this sample I have framed the new time fields, from the new MATDOC, is like a datawarehouse infocube. Ready to run Virtual Data Model. No need to go to many tables in order to have the full fledged information about inventory postings. Meanwhile old tables are available same as before, with the help of CDS views.

Your existing ABAP reports or any other enhancements will run as they run before, for example MSEG is available. Netweaver’s data interface layer will cheat all the existing components by preparing data  on-the-fly collection from the new MATDOC. SE16N also does not know what is behind 🙂

I have run SE16N for MSEG here is the result:

S4HANA_S4CORE_Sarhan_20.jpg

I have framed the fields which are extra selected from MATDOC and put to new MSEG.But how it is happened: thanks to this DDL Source for NSDM_DDL_MSEG. At the bottom of the blog detail definition of the source can be found.

Here are the compatibility layer CDS views:

S4HANA_S4CORE_Sarhan_30.jpg

S4HANA_S4CORE_Sarhan_40.jpg

All information about simplification brought by S4HANA on Premise 1511 can be found here:

https://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20000/en-US/SIMPL_OP1511.…

Final words, yes S4CORE has significant changes in the heart, but not killing the living the landscape.

Cheers,

SarhanPolatates

@AbapCatalog.sqlViewName:      ‘NSDM_V_MSEG’

@EndUserText.label:            ‘MSEG Compatibility View’

@DataAging.noAgingRestriction: ‘false’

@ClientDependent:              ‘true’

@AccessControl.authorizationCheck:#NOT_REQUIRED

define view nsdm_e_mseg  as

select

key mandt,

key mblnr,

key mjahr,

key zeile,

line_id,

parent_id,

line_depth,

maa_urzei,

bwart,

xauto,

matnr,

werks,

lgort,

charg,

insmk,

zusch,

zustd,

sobkz,

lifnr,

kunnr,

kdauf,

kdpos,

kdein,

plpla,

shkzg ,

waers ,

dmbtr ,

bnbtr ,

bualt ,

shkum ,

dmbum ,

bwtar ,

menge ,

meins ,

erfmg ,

erfme ,

bpmng ,

bprme ,

ebeln ,

ebelp ,

lfbja ,

lfbnr ,

lfpos ,

sjahr ,

smbln ,

smblp ,

elikz ,

sgtxt ,

equnr ,

wempf ,

ablad ,

gsber ,

kokrs ,

pargb ,

parbu ,

kostl ,

projn ,

aufnr ,

anln1 ,

anln2 ,

xskst ,

xsauf ,

xspro ,

xserg ,

gjahr ,

xruem ,

xruej ,

bukrs ,

belnr ,

buzei ,

belum ,

buzum ,

rsnum ,

rspos ,

kzear ,

pbamg ,

kzstr ,

ummat ,

umwrk ,

umlgo ,

umcha ,

umzst ,

umzus ,

umbar ,

umsok ,

kzbew ,

kzvbr ,

kzzug ,

weunb ,

palan ,

lgnum ,

lgtyp ,

lgpla ,

bestq ,

bwlvs ,

tbnum ,

tbpos ,

xblvs ,

vschn ,

nschn ,

dypla ,

ubnum ,

tbpri ,

tanum ,

weanz ,

grund ,

evers ,

evere ,

imkey ,

kstrg ,

paobjnr,

prctr,

ps_psp_pnr,

nplnr,

aufpl ,

aplzl ,

aufps ,

vptnr ,

fipos ,

sakto ,

bstmg ,

bstme ,

xwsbr ,

emlif ,

exbwr ,

vkwrt ,

aktnr ,

zekkn ,

vfdat ,

cuobj_ch,

exvkw ,

pprctr,

rsart ,

geber ,

fistl ,

matbf ,

ummab ,

bustm ,

bustw ,

mengu ,

wertu ,

lbkum ,

salk3 ,

vprsv ,

fkber ,

dabrbz,

vkwra ,

dabrz ,

xbeau ,

lsmng ,

lsmeh ,

kzbws ,

qinspst ,

urzei ,

j_1bexbase,

mwskz ,

txjcd ,

ematn ,

j_1agirupd,

vkmws ,

hsdat ,

berkz ,

mat_kdauf,

mat_kdpos,

mat_pspnr,

xwoff,

bemot,

prznr,

llief,

lstar,

xobew,

grant_nbr,

zustd_t156m ,

spe_gts_stock_ty,

kblnr,

kblpos,

xmacc,

vgart as vgart_mkpf,

budat as budat_mkpf,

cpudt as cpudt_mkpf,

cputm as cputm_mkpf,

usnam as usnam_mkpf,

xblnr as xblnr_mkpf,

tcode2 as tcode2_mkpf,

vbeln_im,

vbelp_im,

sgt_scat,

sgt_umscat,

sgt_rcat,

/*

The following 7 fields do belong to functionalities in the former EA-APPL layer.

The fields are part of the table MSEG but not part of NSDM_D_MTDCSA because:

the fields /BEV/* do belong to the excicse duty functionality which is subject of deprecation and as soon as the deprecation

will be done, those fields will be removed to in this compatibility view

the fields OI do belong to JointVenuteAccounting which is right now part of QRT_STAGING and may be become

part of SAPSCORE later and in this case the JVA include needs to be included in NSDM_D_MTDCSA

and the fields need to be fetched from the table

the field DISUB_OWNER belongs to DIMP Subcontracting

*/

cast(‘ ‘ as abap.char( 1 )) as /BEV2/ED_KZ_VER,

cast(‘SAP_SAP’ as abap.char( 12 )) as /BEV2/ED_USER,

cast(‘20200101’ as abap.dats) as /BEV2/ED_AEDAT,

cast(‘235959’ as abap.tims) as /BEV2/ED_AETIM,

disub_owner,

/* Fields for Fashion

The Fashion fields are not yet added to NSDM_S_ITEM structure of the table NSDM_D_MTDCSA.

EA-RETAIL is still not yet fully integrated into S4CORE. During the actual integration of

EA-RETAIL in S4CORE, the table NSDM_D_MTDCSA would be enhanced. 

*/

cast(‘ ‘ as abap.char( 4 )) as fsh_season_year,

cast(‘ ‘ as abap.char( 4 )) as fsh_season,

cast(‘ ‘ as abap.char( 2 )) as fsh_collection,

cast(‘ ‘ as abap.char( 4 )) as fsh_theme,

cast(‘ ‘ as abap.char( 4 )) as fsh_umsea_yr,

cast(‘ ‘ as abap.char( 4 )) as fsh_umsea,

cast(‘ ‘ as abap.char( 2 )) as fsh_umcoll,

cast(‘ ‘ as abap.char( 4 )) as fsh_umtheme,

cast(‘ ‘ as abap.char( 1 )) as sgt_chint,

— Following field is from append ISAUTO_COMPL_MSEG

compl_mark,

— Following 3 fields are from append ISAUTO_ESCR_QTY_DIFFMSEG

fzgls_mark,

etanp_mark,

popup_mark,

cast(0 as abap.curr( 13,2 )) as OINAVNW,

cast(‘ ‘ as abap.char( 2 )) as OICONDCOD,

cast(‘ ‘ as abap.char( 2 )) as CONDI,

— Fields for Retail read the comments for Fields for Fashion

cast(‘ ‘ as abap.char( 18 )) as wrf_charstc1,

cast(‘ ‘ as abap.char( 18 )) as wrf_charstc2,

cast(‘ ‘ as abap.char( 18 )) as wrf_charstc3

from matdoc

where record_type = ‘MDOC’

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

    1. Sarhan Polatates Post author

      Many thanks Joachim,

      I am personally, creating transactions, and try to see how DDL and CDS and compatibility layer works.Because I have the same feelings 🙂

      (0) 

Leave a Reply