Project Arc

Functional/Technical Specifications

Functional and Technical

Specification Document for

INTERFACE OUTBOUND ( PART GENEALOGY ) S/4 TO SQL

1 of 11
TABLE OF CONTENT

1. GENERAL OBJECT OVERVIEW........................................................................................................ 4

1.1 Generic WRICEF Descriptions......................................................................................................4
2. OBJECT SPECIFIC DESIGN...............................................................................................................6
2.1 Reporting (operational and analytical)...........................................................................................6
2.2 Interfaces....................................................................................................................................... 9
2.3 Data Conversion / Historical Data................................................................................................11
2.4 Enhancements............................................................................................................................. 13
2.5 Output (e.g. forms, smart forms)..................................................................................................14
2.6 Workflow...................................................................................................................................... 16
3. ADDITIONAL TECHNICAL SPECIFICATIONS.................................................................................17

` 2 of 11
Functional and Technical Specifications
Document Name Team (i.e. OTC) RICEF Number

FSTS_I_PD755_S42_SQL_PARTGENEALOGY PD 755
Name Telephone Number & EMAIL address
Shanker Srinivasan 801-708-4666
Form Completed By

Kevin Green 219-399-7671

Business Contact(s) 219-787-7501
Linda K Langbehn 219-399-7543
Functional Contact Shanker Srinivasan 801-708-4666
Anusree xxx-xxx-xxx
Technical Contact Baskar & Ricardo Campanate

Revision History (ALL)

Author Description Version # Transport List Date
Shanker CHG0140154 - S4 to SQL Part Genealogy SQL table 1.0 ED4K945654
Srinivasan update
ED4K945668
ED4K945822
ED4K945841
Shanker CHG0140154 - PIV Fix 3 & 4 1.1 ED4K946391 10/26/2021
Srinivasan ED4K946426
Srinivasan Adding 3 new fields to capture the RED legacy Item 1.2 05/25/2022
Narasimman number against SAP Material ID

Object Overview

SOP755 Business Automotive parts forecasting

Object ID
Process

1709 SAP SOP

SAP Release
Module
( ) Report
(X) Interface
( ) Conversion
Object Type ( ) Enhancement
( ) Form
( ) Workflow

Object Title

Object Description

Mock Up ID / Name

Simple / Medium / Complex Low / Medium / High

Complexity of Object Priority

N/A SAP Program

SAP Transaction Name
Name

Similar SAP Similar SAP

Transaction Program

` 3 of 11
1. General Object Overview
1.1 Generic WRICEF Descriptions
JUSTIFICATION
This Interface is created to provide the S4 Hana Auto parts master genealogy data into the SQL as a data dump for further
reporting in legacy. A new extractor ZIBP_2_SQL_PART_GENEALOGY is created in S4 to supply the required data where CPI will
read those and update the SQL landing table called PART_GENEALOGY in the SQL database

FUNCTIONAL DESCRIPTION / DESIGN

Functional Diagram (Visio doc maintained separately)

TRANSACTION VOLUME
All the Auto product master data from S4 system. (Approx. 6500 parts)
Daily = +- 10
Cutover = 35000 max

FREQUENCY & TIMING

It is a real-time extractor.

DEPENDENCIES
The Part status custom field ZPART_STATUS should be populated with the status of the parts in all the existing parts.

` 4 of 11
AUTHORIZATION REQUIREMENTS
N/A

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING REPORT, ETC)
N/A

ASSUMPTIONS
 5 years of historical conversion.

` 5 of 11
2. Object Specific Design
2.1 Interfaces
A BW InfoSource Extractor “ZSQL_PART_GENEALOGY” will be created under MM component with all the material master attributes
for the auto parts for sending it to Auto IBP planning area.

Interface
WRICE Description Interface Applications Data Frequency / Owner
F-ID Method Elements Volumes
SOP755 S42SQL_PA
RT_GENEAL
OGY

Interface Process Flow Diagram, incl. Transfer Method/ Network Integration

File Specifics

` 6 of 11
 (The below link for the Data mapping requirement will be changed after the Go-live. This should be updated later.)

https://arcelormittal.sharepoint.com/:x:/r/sites/AMUSA_PM_AutoForecasting/Blueprint/13%20Master%20Data%20Mapping/Master
%20data%20list_Auto.xlsx?d=wd264d05f0bd24a54be6966cc49e43418&csf=1&web=1&e=zoY5px

There are two mapping rule created for based on part status with “Future” and all other status like “Active”,
“Inactive”, “Built-out” and “Obsolete”.

MAPPING SAP FIELDS TO SOURCE / TARGET

Table
Data
Field/Attribute name Field description Mapping rule / Field Logic
type
Char
KUNNR Customer number (10) KNMT_KDMAT
Char
MATNR Material Number (40) IBINVAL_SEL_F
Char
KDMAT Customer Material (35) KNMT_MATNR
Char
WRKST Basic Material (48) KNMT- ERDAT
DATS
START_DATE Created ON (8) ZUS_305_PARTGENE-START_DATE
START_TIME Created AT Tims (6) ZUS_305_PARTGENE-START_TIME
DATS
END_DATE Changed ON (8) ZUS_305_PARTGENE-END_DATE
END_TIME Changed AT Tims (6) ZUS_305_PARTGENE-END_TIME

Char ZSOP_CDS_I_KNMT_1ST_CHAR-
PLANT Plant (20) WERKS
UDATE Created ON Char (8) CDHDR-UDATE
UTIME Created AT Char (6) CDHDR-TIME
Char
USERNAME User Name (12) CDHDR-USERNAME
Char
SYSMT System (10) ZUS_305_PARTGENE-SYSMT
DATS
ACT_DATE Active Part Date (8) ZUS_305_PARTGENE-ACT_DATE
Char
RED_ITEM_ID Red Legacy Item ID (40) IBINVAL_SEL_F
DATS
START_DATE Created ON (8) ZUS_305_PARTGENE-START_DATE
DATS
END_DATE Changed ON (8) ZUS_305_PARTGENE-END_DATE

REC_START_DAT Record Start Date DATS (8) ZUS_305_PARTGENE-START_DATE

` 7 of 11
 E
REC_END_DATE Record End date DATS (8) ZUS_305_PARTGENE-END_DATE

RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Reporting
N/A

Approach
N/A

Metrics
N/A

Error Handling
N/A

2.2 Enhancements

enhancements
WRIC Description Data Object Functional Alternative Reason Owner
EF-ID (Sales Order) Gap SAP Standard
PD-
755

Functional Design / Flow, Validation and Variants

Fields in the CDS view

Read data from custom CDS view called ZSOP_PRODAUTO_I per the logic below.

Only the auto parts materials are selected to send in this interface into non-auto and the selection should be based on
the below parameters:

MARA-MTART = “ZPRT”
MARA-WRKST NE “SPACE”

Infer the values in the CDS as per the field logic mentioned in the mapping tables.

Read the data from the custom table ZUS_305_PARTGENE

Join the below table with the MATNR key to get the list materials to be considered for Genealogy extractor.
Where ZSOP_PRODAUTO_I – MATNR = ZUS_305_PARTGENE - MATNR

Getting the right Genealogy Data in the extractor

Check for the parameter table ZUSSOP754DAILY to check if the flag is set for the Daily or Cutover

DAILY = X
` 8 of 11
When X, then take the system date and (-1) day; date and pass it into table CDPOS to get the changes
where

CDHDR-UDATE = System Date & (-1 day)

OBJECTID = MATERIAL
FNAME = KDMAT

Customer Part Genealogy report extractor output

Below should be the ALV output layout of the custom table and the Genealogy report for the given
customer part number. 

Materi Part Red

Local Last Last
al NAFT CPN Plan active Ite Rec
Paren CPN  CPN End  updated update Start  End Rec End
numbe A ID  Start  t  Date  m Start 
t  Date  d by 
r  ID
80205 10122 11/8/201 6/25/202 6/25/202 205 11/8/201 11/8/201
601404  201401547  4/21/2021  4/21/2021  4/21/2021 
5  2  8  IHE  1 USERID  1  5  8  8 
80205 10122 4/21/202 6/25/202 6/25/202 205 4/21/202 4/21/202
601404  2026037B  6/25/2021  6/25/2021  6/25/2021 
5  2  1  IHE  1 USERID  1  5 1  1 
80205 10122 201401547 6/25/202 12/31/999 6/25/202 6/25/202 205 6/25/202 12/31/999 6/25/202 12/31/999
601404 
5  2  D  1  9 IHE  1 USERID  1  5 1  9  1  9 

The logic to get the part active date should be as below. 

If for a given SAP material, a record is found in the table ZUS_305_PARTGENE for the
field ACT_DATE where the SYSMT=SAP then that record must be updated in the Part active Date,
else take the value from CDHDR-UDATE where the OBJECTID=MATERIAL and
CDPOS- FNAME = ZZ1_PARTSTATUS_PRD and CDPOS- VALUE_NEW = A. 

Version 1.1 – PIV Fix 3 & 4

This is a technical code fix for the below items.

 Performance improvements and fix to duplicate issues, only fetching changes of the customer/material info
record for the 8 series customer.
 For daily variant, show the result for created materials within the period of time.

Version 1.2 – Adding Red Legacy Item ID and its Start and End Date
 Create new fields as specified in the mapping table (RED_ITEM_ID, START DATE, END DATE,
REC_STARTDATE, REC_END DATE) in the table ZUS_305_PARTGENE.
 This Red Item number will get updated from SQL connection against SAP Material ID with validity
dates.
 Transaction - ZOTC05 Part Genealogy Report extract and display above 3 fields in the output.
 Based on the Record End Date and Start Date, the Active RED Legacy Item would be considered.
 Based on the Record Start and End Date the Latest record will be read as Active information
` 9 of 11
3. Additional Technical Specifications
1. Program name: ZUS_SOP755_PART_GENE_EXTRACTOR
2. Extractor: ZPD755_S42SQL_PARTGENE_EXTR
3. Type: Extractor.
Program flow logics Version 1.1:
1. After selection option input enter the filter parameters (MATNR, KUNNR) and executing the
extractor.
2. Extractor triggers the ZUS_SOP755_PART_GENE_EXTRACTOR FM with the filter parameter.
3. We use ZBC_GET_PARAMETER FM to fetch parameter lookup using ‘ZUSSOP754DAILY’
parameter.
4. Next we select objected from CDHDR by inner joining CDPOS using ‘’SD_KNMT’ in object class ,
objectid without any space, ‘KDMT’ in fname and ‘U’ in chngind.
5. After the objected ID is selected, we perform determinar_tamanho_estrutura and
converter_estrutura_para_carac from zbcpar002 Program.
6. Selecting MATNR, ZPART_STATUS, PRDID from ZSOP_CDS_I_PROD_AUTO using filter
parameter.
7. We select MATNR, WRKST, KDMAT, PLANT, KUNNR, START_DATE,
END_DATE, SYSMT, ACT_DATE 
By inner joining zus_305_partgene using MATNR and KUNNR.
8. Again we select DISTINCT records of PLANT_CODE, PLANT_TEXT,  CAP_DESC, CITY,  STATE
by using INNER Join for T001W, ADRC where R_OBJECTID_KNMT = 'ICP' AND
R_OBJECTID_MAT  = 'IEQ'.
9. While mapping the data with output we select OBJECTID, CHANGENR, UDATE,
 USERNAME, VALUE_NEW, VALUE_OLD by inner joining CDHDR AND CDPOS.
10. Once the extractor is executed output will be populated using
ZUS_SOP755_PART_GENE_EXTRACTOR Structure.

Function Module used:

Table Name Description
CONVERSION_EXIT_MATN1_INPUT Function module for material number
conversion (INPUT)
CONVERSION_EXIT_ALPHA_INPUT Conversion exit ALPHA, external->internal
ZUS_SOP755_PART_GENE_EXTRACTOR Part genealogy and Material Extractor

Table used:
Table Name Description
ZSOP_CDS_I_PROD_AUTO Prod Autopart CDS View
ZUS_305_PARTGENE Customer Part Genealogy
ZSOP_CDS_I_KNMT_1ST_CHAR CDS View
T001W Plants/Branches
ZUS_308_DINTAX Get dinamic tax codes to Create Materia Master
` 10 of 11
 for Non Auto
CDHDR Change document header
CDPOS Change document items
MARA General Material Data

` 11 of 11