Project Arc

Functional/Technical Specifications

Functional and Technical

Specification Document for

S/4 HANA MNEMONICS MASTER DATA

1 of 14
 TABLE OF CONTENT

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

1.1 Generic WRICEF Descriptions......................................................................................................4
2. OBJECT SPECIFIC DESIGN...............................................................................................................7
2.1 Reporting (operational and analytical)...........................................................................................7
2.2 Interfaces..................................................................................................................................... 10
2.3 Data Conversion / Historical Data................................................................................................20
2.4 Enhancements............................................................................................................................. 22
2.5 Output (e.g. forms, smart forms)..................................................................................................23
2.6 Workflow...................................................................................................................................... 25
3. ADDITIONAL TECHNICAL SPECIFICATIONS.................................................................................26

` 2 of 14
Functional and Technical Specifications

` 3 of 14
Document Name Team (i.e. OTC) RICEF Number

FS_TS_E_PD758 Mnemonic_PD PD PD-758

Name Telephone Number & EMAIL
address
801-708-4666
Form Completed By Shanker Srinivasan shanker.srinivasan@clevelandcliffs.co
m
Kevin Green 219-399-7671
Business Contact(s) Jeff Manibusan 219-787-7501
Shanker Srinivasan 801-708-4666
Linda Langbehn shanker.srinivasan@clevelandcliffs.co
Functional Contact
m
219-399-7543

Technical Contact Ricardo Campante

Revision History (ALL)

Author Description Version # Date
Shanker CHG0140154 – Mnemonic Master Data upload and 1.0 05/17/2021
Srinivasan BOM Uoload
ED4K945089 CHG0140154 - PD758 Auto forecasting Tons rule
ED4K945243 CHG0140154 - PD758 Auto forecasting -
Mnemonic material
ED4K945302 CHG0140154 - ZSOP753 -
S42_IBP_MNEMONIC_MD_EXTRACTOR
MD4K901471 CHG0140154 - Create Semantics for Auto Forecast
Mat Apps
MD4K901469 CHG0140154 - Auto Forecast Material & BOM
apps
MD4K901481 CHG0140154 - PD758 - Mnemonic Review

Shanker CHG0140154 – Fix 5 – Fix the date conversion in the 1.1 10/28/2021
Srinivasan Mnemonics parts upload.
ED4K946467
Srinivasan N Mnemonic Weight calculation * No of BOM parts 1.2 06/02/2022

Object Overview

` 4 of 14
 FS-E-PD-758 Business OTC
Object ID
Process
SAP S/4HANA
ON-PREMISE SAP Sales and Distribution
SAP Release
1709 Module
( ) Report
( ) Interface
( ) Conversion
Object Type (X) Enhancement
( ) Form
( ) Workflow

Object Title S/4 Hana Mnemonics Master Data

Object Description Mnemonic Part attributes in the master data and upload program.

Mock Up ID / Name

Medium High
Complexity of Object Priority

SAP Program
SAP Transaction Name
Name

Similar SAP
Similar SAP Transaction
Program

` 5 of 14
1. General Object Overview
1.1 Generic WRICEF Descriptions
JUSTIFICATION
For Forecast Analyst to forecast the Automotive products they need Vehicle data that they get from external HIS forecast sheet
called Mnemonics. In order for the forecasting to work in IBP with all the Part and the Vehicle Attribute must be available in SAP so
that information could be sent to IBP for forecasting.

Forecasting project overall flow

` 6 of 14
FUNCTIONAL DESCRIPTION / DESIGN

Mnemonic master data process flow diagram.

1. FA’s will take the HIS Spreadsheet data for Mnemonics and will populate them in the defined Excel upload template for
SAP.
2. Run the program ZUS_PD758_ATTR_UPLOAD using a transaction ZPD14 – Mnemonic Attribute upload by selecting the
excel template. The program will return a log with the list all those new Mnemonic ID that were not previously found were
newly created. Any issues in the upload process will also be captured in the program log will be reported back to the user.

TRANSACTION VOLUME
[Please provide an indication of the expected number of records that will need to be read and displayed using this report]

Approximately 700 Mnemonics to be created.

FREQUENCY & TIMING

These Mnemonics are created based on the monthly update manually.

DEPENDENCIES

` 7 of 14
For the upload program to update all the Mnemonic attribute in the Material, the material master should have been created.

AUTHORIZATION REQUIREMENTS

In the program, please check the authorization for MM01 transaction access for the user to run this update program.

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

Sample Mnemonics file with the attributes

ASSUMPTIONS
The user has the authorization for creating the Material transaction MM01.

` 8 of 14
2. Object Specific Design
2.1 Enhancement

Enhancement
WRIC Description Enhance Application Data Elements Frequency / Owner
EF-ID ment s Volumes
Method
FS-E- Add new field S4 Hana Monthly
758 attributes into
Mnemonic
master and
update program

The new Mnemonic master data material type ZMNM will have the below new Z fields created by extending the MARA
structure. A new Tab called “Mnemonic Attribute to be created in the system where all the below fields will be housed. All
these fields should be editable.

Attribute Description SAP Field Name Data Type Field Length

Production Plant MARA - ZZ1_PRODP_PRD CHAR 40
Sales Parent (OEM) MARA - ZZ1_SLSP_PRD CHAR 40
Production Nameplate MARA - ZZ1_PRODN_PRD CHAR 40
Production Brand MARA - ZZ1_PRODB_PRD CHAR 40
Car/Truck MARA - ZZ1_CARTRK_PRD CHAR 15
Platform MARA - ZZ1_PLATFORM_PRD CHAR 40
Program MARA - ZZ1_PROGRAM_PRD CHAR 40
Vehicle MARA - ZZ1_VEHICLE_PRD CHAR 75
SOP (Start of Production) MARA - ZZ1_SOP_PRD DATE 10
EOP (End of Production) MARA - ZZ1_EOP_PRD DATE 10

Upload Program for updating the Mnemonic attribute fields.

Create a custom program ZUS_PD758_ATTR_UPLOAD with the T.code ZPD14 to update the above fields into the Mara
table. Inside this function use the standard BAPI_MATERIAL_SAVEDATA to update the custom fields into the material
master using the parameter EXTENSIONIN.

Fields in the Excel Structure that should be mapped into the MARA custom fields are below.

Input key for the program to look up for the Mnemonic material to upload the attributes.

Mnemonic-Platform (Excel file) = MARA-MATNR (In the MATNR, concatenate the numbers from the first two digit “MN”)

Excel Fields SAP Field Name Data Field Length

Type
Production Plant MARA - ZZ1_PRODP_PRD CHAR 40
Sales Parent MARA - ZZ1_SLSP_PRD CHAR 40
Production Nameplate MARA - ZZ1_PRODN_PRD CHAR 40
Production Brand MARA - ZZ1_PRODB_PRD CHAR 40
Car/Truck MARA - ZZ1_CARTRK_PRD CHAR 15
` 9 of 14
 Platform MARA - ZZ1_PLATFORM_PRD CHAR 40
Program MARA - ZZ1_PROGRAM_PRD CHAR 40
Vehicle MARA - ZZ1_VEHICLE_PRD CHAR 40
SOP (Start of Production) MARA - ZZ1_SOP_PRD DATE 10
EOP (End of Production) MARA - ZZ1_EOP_PRD DATE 10

If a material master is not found then while uploading the data for a given Mnemonic, then those materials has to be
created first with a create option in the BAPI. For all the existing Mnemonic materials, only the attributes will be updated.

For the new Material creation, along with the above fields also pass the below listed fields

Excel Fields SAP Field Name Field Logic

Mnemonic-Platform MARA-MATNR Always add MN as
(Material Number) the prefix to the
Mnemonic number.
Vehicle MAKT-MAKTX
(Description)
MARA-MEINS (Unit Always pass “LB”
of Measure)
Mnemonic-Platform MARA-BISMT
Industry Sector MARA-MBRSH Always “M”
Material Type MATA-MTART Always “ZMNM”

Excel upload template for Mnemonic Materials

The below is the format of the Excel template that should be used to upload the Mnemonic master data attribute. The
same template is also made available for download from the upload program.

Mnemonic Part review report

Below are the field mapping for the Mnemonic Part report where the BOM information for the Mnemonic is combined with
Mara attributes and presented to the users as a report.

Create a new Transaction – ZPD18 Mnemonic Part Report

1. Report needs to have an option to read only active Mnemonics and Active parts.
- When Only Active Mnemonic is selected, the report should filter the List of Mnemonic where MARA-
MSTAE ≠ 01. Eg Mnemonic material in Dev = MN10016099999 for testing.
- When Only Active Part is selected then for Display the material inside the report for a Mnemonic
where MARA-ZZ1_PARTSTATUS_PRD = “F” or “A”. Eg material in Dev = 600436 for testing which
is assigned to a Mnemonic MN100160267

` 10 of 14
Field Mapping

Attribute Description SAP Field Name Data Type Field Length

Production Plant MARA - ZZ1_PRODP_PRD CHAR 40
Sales Parent (OEM) MARA - ZZ1_SLSP_PRD CHAR 40
Production Nameplate MARA - ZZ1_PRODN_PRD CHAR 40
Production Brand MARA - ZZ1_PRODB_PRD CHAR 40
Car/Truck MARA - ZZ1_CARTRK_PRD CHAR 15
Platform MARA - ZZ1_PLATFORM_PRD CHAR 40
Program MARA - ZZ1_PROGRAM_PRD CHAR 40
Vehicle MARA - ZZ1_VEHICLE_PRD CHAR 75
SOP (Start of Production) MARA - ZZ1_SOP_PRD DATE 10
EOP (End of Production) MARA - ZZ1_EOP_PRD DATE 10
ROMS1   STPO- ROMS1 QUAN 13
ROMS2 STPO- ROMS2 QUAN 13
ROANZ  STPO- ROANZ  QUAN 13
MEINS STPO- MEINS UNIT 3

Upload Program for updating the Mnemonic attribute fields.

Use the function to CSAP_MAT_BOM_MAINTAIN to update the existing BOM and function CSAP_MAT_BOM_CREATE
for new BOM for a material.

Excel upload template for Mnemonic Materials

Version 1.1 – Fix 5

This is a technical fix in the code to have the right date format in the upload template function in the report program.

` 11 of 14
 RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS
Reporting
N/A

Approach
N/A

Metrics
N/A

Log/ Error Handling

Program Log message:

The program should show the log message as below:

Scenario 1: Successful Create / Update

When the program is successful in updating all the existing Mnemonics:

“The Mnemonic Master is Successfully updated for all the given Mnemonics”.

When the program is successful in creating and updating all the newly created Mnemonics:
“Below are the list of all the new Mnemonics created”
Mnemonic # Description
MARA-MATNR MARA-ZZ1_VEHICLE_PRD

Scenario 2: Failure Create / Update

When the program is not able to create or update the Mnemonics: Capture the BAPI error against each
of the failed Mnemonics.
“Below are the list of Mnemonics that was not updated”
Mnemonic # BAPI Error Description
MARA-MATNR MARA-ZZ1_VEHICLE_PRD

Version 1.2 – Mnemonic Weight calculation * No of BOM parts

ZSOP_CDS_C_ZMNM_MATPART  in this program the weight of Mnemonic parts must be multiplied with the No of BOM
parts and Final value should be displayed in the Column – Mnemonic Weight.

` 12 of 14
Additional Technical Specifications

1. Program name: ZUS_PD758_GEN_MNEMONIC_DATA

2. Transaction code: ZPD14
3. Type: Report

Program flow logics Version 1.1:

1. After executing ZPD14, program will check for the authorization of the user. User will be allowed
proceed only if they have MM01 access.
2. If user wants to download the template click on the ‘Download Mnemonic Material Template’.
3. Upload MNEMONIC Material template.
4. After uploading execute the Transaction, ZUS_PD758_GEN_MNEMONIC_DATA will be triggered.
5. ‘GET_EXISTING_MATERIAL’ Perform will be triggered to fetch the existing material number form
MARA.
6. After fetching the all the materials, Process Perform will be triggered.
7. In process perform, reading the data from the uploaded file and check the material number format.
8. If Material number format is wrong, program throws error message.
9. When material number format is correct, all the data are mapped to the BAPI_TE_MARA structure.
10. Material will be save using BAPI_MATERIAL_SAVEDATA.
11. After data is saved, Log will be displayed as output.

Function Module used:

Table Name Description
KCD_EXCEL_DATE_CONVERT Data transfer: convert Excel date into
internal format
DATE_CHECK_PLAUSIBILITY Date plausibility check
BAPI_MATERIAL_SAVEDATA Create and Change Material Master Data
CONVERSION_EXIT_ALPHA_INPUT Conversion exit ALPHA, external->internal

Table used:
Table Name Description
MARA General Material Data
BAPIMATHEAD Header Segment with Control Information
BAPI_MARA Material Data at Client Level
BAPI_TE_MARA Customer-Defined Fields: Material Data at
Client Level
BAPIRET2 Return Parameter

` 13 of 14
 Program name: ZUS_PD758_MNEMONIC_PART_REPORT
Transaction code: ZPD18
Type: Report

Program flow logics Version 1.1:

1. After executing ZPD18, user will get selection option for Mnemonic Material and Part Number and
check boxes for Active Mnemonic and Active Part.
2. After the selection and filter are filled. When we execute program will check for the authorization of the
user. User will be allowed proceed only if they have MM03 access.
3. If the user has the access to program, the program will trigger the GET_DATA Perform.
4. In GET_DTA, data is fetched from ZSOP_CDS_C_ZMNM_MATPART and MARA using Mnemonic
material, Part Number, Cross plant material status, part status.
5. Once the data is fetched and it is stored in the internal table.
6. Data will be displayed in ALV as output.

Function Module used:

Table Name Description
ZBC_ALV_GENERATE General function to create and display ALV
Reports
CONVERSION_EXIT_ALPHA_INPUT Conversion exit ALPHA, external->internal

Table used:
Table Name Description
MARA General Material Data
ZSOP_CDS_C_ZMNM_MATPART CDS View

` 14 of 14