Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 14

Vendor Network System (VNet)

For
Mitsubishi Motors Krama Yudha Sales Indonesia
(MMKSI)

Functional Specification
[Modul ID]
[Modul Name]

Revision [0.0]

PT. Berlian Sistem Informasi


KTB Annex Bld. 4th Floor, Jl. Jend. A. Yani. Pulomas,
Tel. +62 21 4786 7575 (Hunting) Fax. +62 21 4714964 www.bsi.co.id
[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

Document Control
Author [author name]
File Name [file name]
Path [path on repository]
Create Date 18/02/2016 15:58:00
Last Edited 07/12/2021 10:39:00 AM
Number of Pages 14

Revision History
Date Revision Description Author
dd/mm/yyyy 0.0 Initiate [author name]

dd/mm/yyyy 0.1 Revise on... [author name]

dd/mm/yyyy 1.0 Baseline [BSI Project Manager]

Document Approval
By signing this document, I acknowledge I have read the document and give the Project
Management Team approval to proceed.
Date Name Role Signature
BSI Business Analyst

BSI Business Analyst

BSI Project Manager

BSI Project Director

Customer Project
Manager
Customer Project
Director
Customer Project
Director
Customer Project
Controller
Customer Project
Controller

TABLE OF CONTENT
Confidential PT. Berlian Sistem Informasi, 2024 Page 2
[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

1 INTRODUCTION........................................................................4
1.1 PURPOSE.................................................................................4
1.2 SCOPE....................................................................................4
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...................................4
1.4 REFERENCES.............................................................................4
2 CONFIGURATION......................................................................4
3 PROCESS SPECIFICATION: B.4.1.1.12.3 UPLOAD LOCAL D/N. . .4
3.1 OBJECTIVE...............................................................................4
3.2 ACCESS CONTROL.......................................................................4
3.3 SCREEN FUNCTIONALITY...............................................................5
3.4 OPERATION FLOW.......................................................................5
3.5 SCREEN DESIGN.........................................................................5
3.5.1 Upload Local D/N Selection Screen........................................5
3.5.2 Data List Display before Upload Screen.................................5
3.5.3 Screen Functionality...........................................................6
3.6 OPERATION DESCRIPTION..............................................................6
3.7 DATA STRUCTURE / SCREEN ITEM LIST.............................................7
3.7.1 Data Structure in New Table (ZSPDT00XX)............................7
3.7.2 Data Structure in Existing Table...........................................8
Functional Specification
1 Introduction
1.1 Purpose
This functional is intended to explain how to maintain Email setting and VNet in-
apps notification.

1.2 Scope
System Admin can create email template and also in-app notification.

1.3 Definitions, Acronyms, and Abbreviations


Some definitions that used in this document:
a. VNet (Vendor Network)
b. MMKSI (Mitsubishi Motors Krama Yudha Sales Indonesia)

1.4 References
This functional scope is refers to “to be design” in Approval Email Template and
VNet In-App Notification

2 Configuration
N/A

Confidential PT. Berlian Sistem Informasi, 2024 Page 3


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

3 Process Specification: Admin – Create Email Account


3.1 Objective
Account Email is menu to make SMTP of email.

3.2 Access Control


Following are users and their access control for this screen :
User Entry Update Posting Cancel Find
System Admin Y Y Y N Y

3.3 Screen Functionality


a. Open Email Account Menu
b. Create Email Account

3.4 Operation Flow


N/A

3.5 Screen Design


3.5.1 Account Email Menu

Confidential PT. Berlian Sistem Informasi, 2024 Page 4


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

3.5.2 Account Email Form

3.5.3 Screen Functionality


The Screen Input General Setting is shown as follows:

Buttons Function
3.5.1. Open Menu Approval Template

Execute Menu Email Account opened

3.5.2. Approval Template

Add new Create Email Account

3.6 Operation Description


No. Operation Description
Name
3.6.1. Open Menu Email Account
1 Initial 1.1. System Admin open Email Account Menu
operation -
in
selection
screen
3.5.2. Data List Display before Upload Screen
1 Button(s) 1.1 Create Email Account
Operation 1.2 Form
- Email Account =
- Email Name =
- Host =
- SMTP Name =
- SMTP Password =
- Port =

Confidential PT. Berlian Sistem Informasi, 2024 Page 5


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

4 Process Specification: C.1.2 Admin Create Email


Template
3.7 Objective
Menu for create email template, used for setting email redaction and etc.

3.8 Access Control


E.g : Following are users and their access control for this screen :
User Entry Update Posting Cancel Find
System Admin Y Y Y N Y

3.9 Screen Functionality


a. Open Email Template Menu
b. Create Email template

3.10 Operation Flow


N/A

3.11 Screen Design


3.11.1 Menu Email Template

3.11.2 Create Email Template

Confidential PT. Berlian Sistem Informasi, 2024 Page 6


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

3.11.3 Screen Functionality


The Screen Input General Setting is shown as follows:

Buttons Function
3.5.1. Open Menu Email Template

Execute Menu Approval template opened

3.5.2. Create Email Template

Add new Create Email Template

3.12 Operation Description


No. Operation Description
Name
4.6.1. Open Menu Email Template
1 Open 1.1. System Admin open Email Template Menu
Email 1.2. Filter by:
Template - Template Code
Menu - Template Title
- Created Date
1.3. Menu can open by System Admin and Vendor Admin
4.6.2. Create Email template
1 Button(s) 1.1 Admin create template email
Operation 1.2 Process Need Email Notif
a. User Administration
A.1.1 – System Admin Login (First Time/ After Reset Password)
A.1.2 – System Admin Login (Not First Time/ After Reset Password)
A.1.3 – System Admin Reset Password by System
A.1.4 – System Admin Change Password
A.1.5 – System Admin Forgot Password
A.1.6 – MMKSI User (Admin) Login
A.1.7 – MMKSI User (Non-Admin) Login
A.1.8 – MMKSI Admin Registration
A.1.9 – MMKSI Admin Lock/ Unlock by System Admin
A.1.10 – MMKSI Admin Set Inactive by System Admin

Confidential PT. Berlian Sistem Informasi, 2024 Page 7


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

No. Operation Description


Name
A.1.11 – MMKSI Admin Change Role
A.1.12 – MMKSI Admin Update Data Profile
A.1.13 – MMKSI User (Non – Admin) Registration
A.1.14 – MMKSI User (Non – Admin) Lock/ Unlock by MMKSI Admin
A.1.15 – MMKSI User (Non – Admin) Set Inactive by MMKSI Admin
A.1.16 – MMKSI User (Non – Admin) Change Role
A.1.17 – MMKSI User (Non – Admin) Update Data Profile
A.1.18 – Vendor Admin Registration
A.1.19 – Vendor Admin Login (First Time/ After Reset Password)
A.1.20 – Vendor Admin Login (Not First Time/ After Reset Password)
A.1.21 – Vendor Admin Lock/ Unlock by MMKSI - Admin
A.1.22 – Vendor Admin Reset Password by MMKSI - Admin
A.1.23 – Vendor Admin Set Inactive by MMKSI Admin
A.1.24 – Vendor Admin Change Role
A.1.25 – Vendor Admin Update Data Profile
A.1.26 – Vendor Admin Change Password
A.1.27 – Vendor Admin Forgot Password
A.1.28 – Vendor User Reset Password by System
A.1.29 – Vendor User (Non – Admin) Registration
A.1.30 – Vendor User Login (First Time/ After Reset Password)
A.1.31 – Vendor User Login (Not First Time/ After Reset Password)
A.1.32 – Vendor User Lock/ Unlock by Admin
A.1.33 – Vendor User Reset Password by Admin
A.1.34 – Vendor User Set Inactive by Vendor Admin
A.1.35 – Vendor User Change Role
A.1.36 – Vendor User Update Data Profile
A.1.37 – Vendor User Change Password
A.1.38 – Vendor User Forgot Password
A.1.39 – Deactivate Vendor
A.1.40 – Activate Vendor

b. Approval
C.1.1 – Admin - Assign VNet Approval Templates
C.1.2 – Admin - Update VNet Approval Stages
C.1.3 – Vendor Approval Update Vendor Data
C.1.4 – MMKSI Approval Update Vendor Data
C.1.5 – Vendor Approval Update Pricing Data
C.1.6 – MMKSI Approval Update Pricing Data
C.1.7 – MMKSI Approval PO
C.1.8 – Vendor Confirm PO
C.1.9 – Vendor Approval for Invoice Submission
C.1.10 – MMKSI Approval Invoice
C.1.11 – MMKSI Confirm JV

c. Master Data
B.1.1 – Material Master Data Synchronization
B.1.2 – Vendor Master Data Synchronization
B.1.3 – Info Record Data Synchronization
B.1.4 – Depo Master Data

d. Paint Ordering

Confidential PT. Berlian Sistem Informasi, 2024 Page 8


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

No. Operation Description


Name
F.1.1 – Dealer Request Paint
F.1.2 – Purchase Order for Paint
F.1.3 – Goods Receipt and Invoicing Paint
F.1.4 – Payment Paint
F.1.5 – Claim Paint

e. Oil&Tire Ordering
E.1.1 – Update Depo stock data
E.1.2 – Dealer Request Oil&Tire
E.1.3 – Purchase Order for Oil&Tire
E.1.4 – Goods Receipt and Invoicing Oil&Tire
E.1.5 – Payment Oil&Tire
E.1.6 – Claim Oil&TIre

f. Sparepart ordering
D.1.1 - FORECAST FOR SPARE PART ORDERING
D.1.2 - CAMPAIGN FOR SPARE PART ORDERING
D.1.3 - PURCHASE ORDER FOR SPARE PARTS ORDERING
D.1.4 - GOODS RECEIPT AND INVOICING SPARE PARTS
D.1.5 - PAYMENT SPARE PARTS
D.1.6 - CLAIM SPARE PARTS
D.1.7 - RECEIVE SPARE PARTS ON SUBCONTRACTOR VENDOR
D.1.8 - REQUEST STOCK MMKSI ON VENDOR WAREHOUSE
D.1.9 - PICKING LABEL INFORMATION

Confidential PT. Berlian Sistem Informasi, 2024 Page 9


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

5 Process Specification: C.1.3 Admin Create Notification


Setting
3.13 Objective
Menu for create in-apps notification.

3.14 Access Control


E.g : Following are users and their access control for this screen :
User Entry Update Posting Cancel Find
System Admin Y Y Y N Y

3.15 Screen Functionality


a. Open Notification Menu
b. Create Setting of notification

3.16 Operation Flow


N/A

3.17 Screen Design


3.17.1 Menu Notification Setting

3.17.2 Create Notification Setting

Confidential PT. Berlian Sistem Informasi, 2024 Page 10


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

Confidential PT. Berlian Sistem Informasi, 2024 Page 11


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

3.17.3 Open Notification List

3.17.4 Screen Functionality

3.18 Operation Description


No. Operation Description
Name
5.6.1. Open Menu Email Template
1 Open 1.1. System Admin open Notification Setting
Email 1.2. Filter by:
Template - Notif Code
Menu
5.6.2. Create Email template
1 Button(s) 1.1 Admin create notification setting
Operation 1.2 Process Need Email Notif
a. User Administration

Confidential PT. Berlian Sistem Informasi, 2024 Page 12


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

No. Operation Description


Name
A.1.1 – System Admin Login (First Time/ After Reset Password)
A.1.2 – System Admin Login (Not First Time/ After Reset Password)
A.1.3 – System Admin Reset Password by System
A.1.4 – System Admin Change Password
A.1.5 – System Admin Forgot Password
A.1.6 – MMKSI User (Admin) Login
A.1.7 – MMKSI User (Non-Admin) Login
A.1.8 – MMKSI Admin Registration
A.1.9 – MMKSI Admin Lock/ Unlock by System Admin
A.1.10 – MMKSI Admin Set Inactive by System Admin
A.1.11 – MMKSI Admin Change Role
A.1.12 – MMKSI Admin Update Data Profile
A.1.13 – MMKSI User (Non – Admin) Registration
A.1.14 – MMKSI User (Non – Admin) Lock/ Unlock by MMKSI Admin
A.1.15 – MMKSI User (Non – Admin) Set Inactive by MMKSI Admin
A.1.16 – MMKSI User (Non – Admin) Change Role
A.1.17 – MMKSI User (Non – Admin) Update Data Profile
A.1.18 – Vendor Admin Registration
A.1.19 – Vendor Admin Login (First Time/ After Reset Password)
A.1.20 – Vendor Admin Login (Not First Time/ After Reset Password)
A.1.21 – Vendor Admin Lock/ Unlock by MMKSI - Admin
A.1.22 – Vendor Admin Reset Password by MMKSI - Admin
A.1.23 – Vendor Admin Set Inactive by MMKSI Admin
A.1.24 – Vendor Admin Change Role
A.1.25 – Vendor Admin Update Data Profile
A.1.26 – Vendor Admin Change Password
A.1.27 – Vendor Admin Forgot Password
A.1.28 – Vendor User Reset Password by System
A.1.29 – Vendor User (Non – Admin) Registration
A.1.30 – Vendor User Login (First Time/ After Reset Password)
A.1.31 – Vendor User Login (Not First Time/ After Reset Password)
A.1.32 – Vendor User Lock/ Unlock by Admin
A.1.33 – Vendor User Reset Password by Admin
A.1.34 – Vendor User Set Inactive by Vendor Admin
A.1.35 – Vendor User Change Role
A.1.36 – Vendor User Update Data Profile
A.1.37 – Vendor User Change Password
A.1.38 – Vendor User Forgot Password
A.1.39 – Deactivate Vendor
A.1.40 – Activate Vendor

b. Approval
C.1.1 – Admin - Assign VNet Approval Templates
C.1.2 – Admin - Update VNet Approval Stages
C.1.3 – Vendor Approval Update Vendor Data
C.1.4 – MMKSI Approval Update Vendor Data
C.1.5 – Vendor Approval Update Pricing Data
C.1.6 – MMKSI Approval Update Pricing Data
C.1.7 – MMKSI Approval PO
C.1.8 – Vendor Confirm PO
C.1.9 – Vendor Approval for Invoice Submission

Confidential PT. Berlian Sistem Informasi, 2024 Page 13


[Project Name] Revision : 0.0
Functional Specification Date : 10/02/15
[DocName]

No. Operation Description


Name
C.1.10 – MMKSI Approval Invoice
C.1.11 – MMKSI Confirm JV

c. Master Data
B.1.1 – Material Master Data Synchronization
B.1.2 – Vendor Master Data Synchronization
B.1.3 – Info Record Data Synchronization
B.1.4 – Depo Master Data

d. Paint Ordering
F.1.1 – Dealer Request Paint
F.1.2 – Purchase Order for Paint
F.1.3 – Goods Receipt and Invoicing Paint
F.1.4 – Payment Paint
F.1.5 – Claim Paint

e. Oil&Tire Ordering
E.1.1 – Update Depo stock data
E.1.2 – Dealer Request Oil&Tire
E.1.3 – Purchase Order for Oil&Tire
E.1.4 – Goods Receipt and Invoicing Oil&Tire
E.1.5 – Payment Oil&Tire
E.1.6 – Claim Oil&TIre

f. Sparepart ordering
D.1.1 - FORECAST FOR SPARE PART ORDERING
D.1.2 - CAMPAIGN FOR SPARE PART ORDERING
D.1.3 - PURCHASE ORDER FOR SPARE PARTS ORDERING
D.1.4 - GOODS RECEIPT AND INVOICING SPARE PARTS
D.1.5 - PAYMENT SPARE PARTS
D.1.6 - CLAIM SPARE PARTS
D.1.7 - RECEIVE SPARE PARTS ON SUBCONTRACTOR VENDOR
D.1.8 - REQUEST STOCK MMKSI ON VENDOR WAREHOUSE
D.1.9 - PICKING LABEL INFORMATION
5.6.3 Notification List
Notificatio 1.1. Notification show top10 newest
n List View 1.2. Unread notification show in highlight
All 1.3. Read notification show not in highlight still show on top 10 newest
notification
1.4. Click Button view all and direct to page notification List

Confidential PT. Berlian Sistem Informasi, 2024 Page 14

You might also like