mdm - material creation

7/29/2019 MDM - Material Creation

1/13

MDM - Material Creation


2/13

Terms and Definitions

Term Definition

MC Material Creation

EP Enterprise Portal

RFC Remote Function Call

Page 2 of 13


3/13

Table of Contents

INTRODUCTION.......................................................................................................4

PURPOSE ...............................................................................................................4

DOCUMENT CONVENTIONS......................................................................................4

PROJECT SCOPE......................................................................................................4

REFERENCES..........................................................................................................4

PRODUCT PERSPECTIVE..........................................................................................5

PRODUCT FEATURES...............................................................................................5

BUSINESS FEATURES...............................................................................................5

ROLE/APPROVAL MATRIX.........................................................................................5

OPERATING ENVIRONMENT......................................................................................5

USER DOCUMENTATION...........................................................................................5

ASSUMPTIONS AND DEPENDENCIES.........................................................................5

AUTHORIZATION DETAILS........................................................................................6

TAB/VIEW DETAILS................................................................................................11

BASIC DATA..........................................................................................................11

PURCHASE............................................................................................................11

ACCOUNTING........................................................................................................11

MRP.....................................................................................................................11

WORK SCHEDULE..................................................................................................11

SALES..................................................................................................................11

QUALITY...............................................................................................................12

STORAGE LOCATION..............................................................................................12

PLANT STORAGE...................................................................................................12

COSTING...............................................................................................................12

CLASSIFICATION...................................................................................................12

MATERIAL DETAIL.................................................................................................12

SAP MM STANDARD TABLES..................................................................................13

Page 3 of 13


4/13

Introduction

Purpose

The specification document describes the functional scope of the WebDynpro to bedeveloped for Material Creation. This document forms the framework and reference to develop theapplication. It provides the functionalities that are part of the application based on the requirementsgathering.

This document forms the basis for any requirement thats agreed to be part of this development.

Any addition to the requirements stated in this document will be treated as a separate development.

Document Conventions

All requirements stated in this document have to be considered during the project execution.

Throughout the document, the terms WebDynpro, is used to refer to the new webpage thats

being developed and deployed for Material Creation

Intended Audience and Reading Suggestions

Project managers Project scope document

Developers For understanding the business requirements

and to build functional and technicalspecifications for each functionality describedin document

Testers For understanding the business functionality

and to build test cases for each functionalitydescribed in the document

Senior Management / Business Owners To give an overview of the proposed solution

and the features that form part of the solution

Project Scope

The Scope of the proposed solution involves;

1. Material Creation

References

N/A

Page 4 of 13


5/13

Product Perspective

Implementation of WebDynpro web pages increases business process agility via automation along

with increased data accuracy of the below scenarios;

Material Creation

Product Features

N/A

Business Features

S.NO Group Functionality

1. Material Creation Creation of Material master via an Webdynpro web

pages with all the above information filled from user

directly with necessary approvals in place

Role/Approval Matrix

S.No Application Role/Approval Matrix

1 Material Creation Details attached later

Operating Environment

The below diagram depicts the landscape.

TODO: To be filled

Process flow Material Creation (Example)

User Documentation

User documentation that would be delivered as part of the project documentation is

Installation guide and configuration guide (covers application installation, post installationconfiguration) is delivered to team

Application user procedure manual, is to be developed post realization phase

Recordings of the scenarios

Assumptions and Dependencies

Page 5 of 13


6/13

Authorization Details

User Detail Approver Details

ZEVEN02 ZEVEN05ZEVEN03 ZEVEN06

ZEVEN04 ZEVEN09

Initial screen:

1. Material

2. Industry sector

3. Material type

Sr No Field Description Size R/O Inputtype

PossibleValue

1MATNR Material 18 R

2MBRSH Industry sector 1 R

Dropdown T137T

3MTAR

T Material type 4 RDropdown T134T

Material Validation:

1. Back end : Need to validate from Ztable and Mara table to check existence.

Materil Naming.xlsx

2View Validation:

MM_Initial_Views_29-12-12.xls

Page 6 of 13


7/13

Ztable : ZTH_MM_T_VIEWVISIBILITY it should be table maintenance generator.

Material type MtartPrimarykey

Industry SectorMBRSH

Primarykey

Basic Data Char1

Classification Char1

Sales Char1

Foreign Trade Char1

Purchasing Char1

MRP Char1

Forcasting Char1General Plant DataStorage Char1WarehouseManagement Char1

Quality Management Char1

Accounting Char1

WM Execution Char1

WM Packaging Char1

DSD Data Char1

DSD Totals Char1

EHS Specifications Char1Label Data Char1

Organizational Level:

It should be displayed before display view tabs

SrNo

Field Description R/O Inputtype

Possible Value

1WERKS Plant R/O

Dropdown T001W

2LGOR

TStorageLocation R/O

Dropdown

Plant,storage locationand desc should bedisplayed as per in MM01

Table : T001L

3MTAR

T Sales org R/ODropdown TVKWZ Table

4VTWEG Dist.Channel R/O

Dropdown

Table TVTW (Code &Description)

Page 7 of 13


8/13

Validation depends upon organization selection

(i) If we select only plant, fields in views displayed as per MM01

(ii)Since plant is mandatory , If we select only storage location, plant and storagelocation should validate the combination against table T001L

(iii) Since dist channel is mandatory , If we select only sales org, then it should

validated be in the combination against table TVTA

(iv) If plant is entered then validation should happen for material and plant

combination from MARC Table.

(v)If plant is not entered material should be validated from MARA Table.(To check

whether material created without plant, if yes throw error because material

can be created only once without plant)

(vi) Sales organization should be displayed from the table tvkwz if plant is

entered

Common:

(i) If you entered into any tab without entering the mandatory fields, application

should not allow to go any tab.

(ii) For every F4 help description should be displayed .

(iii)Authorization person only can access the application

(iv) User can not be allowed to involve in another process

Eg: if user ZEVEN02 created material, authorized person only can approve and it

should be maintained in Matrix table.

(v)Avoid hard core wherever it is possible.

(vi) Application should not allow to go any tab and show error message if

basic data is not filled

Fields condition validation:

FIELDSCONDITION.xlsx

Page 8 of 13


9/13

Matrix Table:

*Table maintenance is required

FieldsData

ElementDomain Condition

Primarykey

Plant Werks_dF4 help,

T001w Yes,

Materialtype Mtart F4 help Yes

User Type char 1 A,U YesUserLevel num(1) yes

Name Syuname

mail_idad_smtpadr

Track Table:

FieldsDomain Condition

Primarykey

Material Matnr yes

Ref_no Char (18) yes

Plant WerksYes(nullable)

Matyp Mtart yes

User Type char A,U yes

User Level num (1) yes

Name Syuname

Mail_idad_smtpadr

Status Char (1)A,R,S,C,T

RemarksChar(250 )

Created on Datum

Created at Uzeit

Page 9 of 13


10/13

created by Syunamelastchangedon Datumlastupdateduser SyunameLastchangedat Uzeit

Material List:

Material List RFC should be taken from the ztable Track table

Input :

Fields type Condition

Material F4 Ztable

Ref_nochar(18) Ztable

Createdfrom datumCreated

to datumStatus char1

List

Fields Condition

Material matnr

Ref.nochar(18)

Plantwerks

_dMaterial

Type mtart

PersonDescription should be dispalyednot key

Level

Nameuname

StatusDescription should be dispalyednot key

Page 10 of 13


11/13

Updatedon datum

Remarkschar(250)

List needs to display for authorized persons only.

Needs to validate from track table before display.

Tab/View Details

Basic Data

i. Fields should not change depends plant or any organization level, basic data

always same

Purchase

Accounting

MRP

Work Schedule

Sales

Page 11 of 13


12/13

Quality

Storage Location

Plant Storage

Costing

Classification

Material Detail

Fields should be displayed depends upon User type.

Avoid hard core, validate from Matrix table.

Button Validation:

SAVE - CREATION:

i. All mandatory validation

ii. Call BAPI_MATERIAL_SAVEDATA

CANCEL CREATE:

I. Clear all values and go to initial screen

BACK CREATION:

i. Go to previous page without clear fields value

CHANGE DETAIL

i. User - all fields are in editable mode except material no, industry sector,

material type.

ii. Approve dont display change button

Page 12 of 13


13/13

REJECT DETAIL:

i. User dont display

ii. Approver display button

iii. Show error message if it is already approved, need to be validated from Tracktable.

APPROVER DETAIL:

i. User dont display

ii. Approver display

iii. Show error message if already rejected or approved

Sample code:

for_study.txt

SAP MM STANDARD TABLES

1. MARA

2. MARC

3. MARD

4. MBEW

5. MARM - Multiple Entries

6. MLAN - Multiple Entries

7. MAKT

8. MVKE - Multiple Entries

Page 13 of 13

mdm - material creation

Documents