ESSEL PROPACK

LIMITED
Vendor Master Data Management
System
  Existing Vendor Master Data Management
System through Master Data online (MDO)

Steps for creating vendor code in MDO

 User with role vendorinitiator fills all necessary info about vendor
provided b vendor through mail . Temporary code gets generated and
workflow gets triggered for approval process .
 User with role vendorApprover receives mail regarding temporary code
for approval . Approver check all the data and file attached to the same
and approves or rejects the code
 If approval rejects the code it again goes to initiator for correction and
mail gets triggered regarding rejection of code with reason of rejection .
 If approval approves the code, vendor code gets generated in SAP
through IDOC .

Major drawbacks of MDO system.

 Need separate data base for MDO system. Hence we need maintained
same data in SAP as well as MDO data base.
 Inconsistency in workflow.

Steps to tackle Drawbacks of MDO system.

 Moving out of MDO system and creating new Portal based system
which will directly integrate with SAP
 Use for WebDynPro to introduce new system which will use same Data
base as SAP.
 This new system will be totally controlled internally by core team.
Action to be taken:

Requirement:

 To Create vendor master internally

Purpose:

 Vendor creation directly in SAP doesn’t have any approval or any checks
and validations which are required to ensure whether master data
created is correct or not .
 For this we need to create master data in using web based Portal
platform which will provide necessary checks and validation along with
approval steps.
 Basic flow chart for the processes is as follows.
 Star
t

Initiator will log in through SAP ID and will use transaction code to initiate request to create vendor in Web P

Initial screen will appear containing

buttons to create, change and display
and extend vendor codes, along with
input fields to search created vendor
codes

Check whether vendor is already created with same YES

name and country by searching for the name in SAP Vendor code will a
search

Initiator will do
required changes
& will resubmit NO
request for
approval

Create new vendor by providing necessary data and attachment

Initiatoraswill
perdo
the rules and
required validations.
changes Submit
in existing the reque
vendor code

Approval will check all the data

and approve or reject the
request.
Reject with rejection reason & mail will be triggered

Approved

Vendor master will be created/ changed with SAP

code.
Layout of the Portal will be similar to following example

Workflow based system and detailed flow chart for creation

and approval process is as follows
 Start Workflow

Initiator will log in to Accounting Info Email will be

create request for 1. Reconciliation triggered to
new vendor Account (from Purchase head
drop down) for approval
2.payment term
Initial screen (from drop down)
1.Create vendor 3. Check double
2.Change vendor invoice (flagged)
3.Extend vendor
3.Display vendor Check all
purchase
Withholding tax related Data
Fields : 1.WH Tax country and document
Rejected with
1.Purchase Org (Drop down as per reason of
2.Company code SAP data )
3.Account group rejection

Approved

General data Mail will be

Purchasing Data
1. Tittle triggered to
1. Order currency
1.Name Finance head for
2.schema group
2. Address approval
3. GR based In.
Mail will be
3. Contact details verf. –( flagged)
triggered to
4. Country 4. Service based In.
initiator
5. Pin code Verf- (flagged)

Check all
finance
Account control and related Data
Tax data Additional data &document Rejected with reason of
1. Customer 1. PAN number
rejection
2.Tax number 3 2. Reason to create
(GST).(Only for India) vendor
3. Product / service Approved
supplied
4. Current vendor for
Warning same product/ Vendor code will be
message should service created by using BAPI in
pop up to check 5. Benefit in item SAP
online GST and
related info

Mandatory

Payment information
attachments Indicators:
1. Declaration on
1. Bank Key :-
letter head for
Mandatory fields Dependant fields
Dropdown field
correctness of data
2. Bank account Default fields Optional fields
2. Cancelled cheque
number
copy
3. Account holder
3.PAN card copy
4.GST certificate

Save and Submit the

YES record.
Availability
All data will be saved
check for
in Ztable in SAP
bank key

No Temporary
transaction code will
Create new bank key be generated and
with details proceed for approval