Project On Erp (Idns)

SCHOOL OF COMPUTER AND INFORMATION SCIENCES INDIRA GANDHI NATIONAL OPEN UNIVERSITY
Master of Computer Application 5th Semester CS - 17

Submitted By
MCA(5)-17/Project/2005 CS-17/Project Proposal
Sachin Barad Yogesh Dwivedi

Enrollment No. 000454265 no. 012680027 Enrollment
Index
Contains
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Project Needs Limitation of the Current System Objectives / Features of the Project Project Category Tools / Platform Languages Used Data Flow Diagram Flow Chart with Module Description and Validation Data Structure Process Logic of Modules and Reports of the Module Testing Scope of Future Application
Page No.
3 4 5 6 6 6 7 16 32 43 48 49
Sachin Barad
Enrollment No. :- 000454265
Page 2 of 49
1)
Title of the project
Intelligent Digital Nervous System
Project Need
Having meeting with Mr.Jignesh Shah who is Managing Director for Drashti Systems Pvt. Ltd. We have concluded As there is a rapid development and migration is happing in todays Information technology world to adopted high speed information flow , so many organization is implementing ERP for there information need. But the cost of the same is very high for available ERP solution. Hence the organization are going for the customize development of the ERP. In the process of implementation of ERP small business organizations are going with module implementation. The cost of implementation is also the barrier for implementing full ERP at once. During discussion phase we came to know that the Drashti system is using there customized software for order processing and invoicing purpose which was created long back in FoxPro. The following limitation has come up from the discussion.
Sachin Barad
Page 3 of 49
Limitation of the Current System
Organization is unable to flow the information to there respected executives as the system is made earlier and it is complex to use for the user.
Organization has to maintain so much of manual report for information. Updated information is not available immediate. It so much time consuming process in the old software.
The data which is required will be stored only for the current financial year only, hence any historical or summary report for the back years can not be retrieved for by the software.
Software require so many data entry for the same customer and orders. Security to the software is less the n required one.
The same software is desktop base application hence it can not work on the network.
Information user are dependent on user for the information.
Sachin Barad
Page 4 of 49
2)
Objectives / Features of the Project

To give the total and effective security to the system so that nobody can
make unauthorized changes in the database. To prevent any sort of misuse by providing so effective platform and
languages that even small data will be protected. To develop a totally user-friendly software. The existing system is a dos based system and not user-friendly, whereas
this system will provide fully GUI based system. It will give more interactivity and flexibility to user. Efficient for information and updated information. Digital back born for the information in the organization will be formed.
Sachin Barad
Page 5 of 49
3)
Project Category
Enterprises Resource Planning (ERP)
4)
Tools / Platforms
For Server :Software Microsoft Windows NT Server Microsoft Windows 2000 Server Hardware Above PIII 700 Mhz. system with 128 MB RAM and 2 GB free space on the disk for application database For Client :Software Microsoft Windows 98 Microsoft Windows 2000 Professional Hardware Above Cel500 Mhz system with 64 MB RAM and 500 MB free space on the dick for application.
5)
Languages Used
Front End Back End (Database) Reports :::Microsoft Visual Basic 6.0 Oracle 8i Crystal Reports 8.0
Sachin Barad
Page 6 of 49
MCA(5)-17/Project/2005 Cu stom er CS-17/Project Proposal
Supplier
6)
Sales & Order
Purchase
Managment
iDNS
Production
Invoicing
Inventory
Dispatch & Delivery
Distribution
Payment Receivables
Payments Payables
Module Diagram of IDNS (Intelligent Digital Nervous System)
Sachin Barad
Page 7 of 49
7)
A Context Free Diagram of Intelligent Digital Nervous System
Customers
Sales orders

Commitments Purchases orders
A Context Diagram of the
Rejected Sales Order Notices Invoices Statements Payments by customers
Shipments
iDNS Intelligent
Digital Nervous System
Supplier invoices Supplier statements
Suppliers
Payments to suppliers Request for Production Order Shipments Stock
Furnished Goods
Dispatch
Production
Inventory
Sachin Barad
Page 8 of 49
8)
I)
Complete Structure of the System

Analysis (Data Flow Diagrams) :
Sales Orders
Customers
Rejected sales order notices Invoices
A Figure 1 Diagram of the Intelligent Digital Nervous System
Shipment
Statements Payments by customers
1. Orders
4. Dispatch
Receivables ledger data Rejected Items Furnished Goods against order
Purchasing Data Commitments
Purchase Orders Shipments Supplier invoices
3. Payment Receivables & Payables
Payables ledger data Payments to suppliers
2. Inventory & Warehouse
Suppliers
Supplier statements
Furnished Goods Request for Row Materials
Production
LEVEL1 DFD
Sachin Barad
Page 9 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal LEVEL2 DFD
1)
Customer & Order Module : -
Sales orders
Customers
Rejected Sales Order Notices
A Figure 1 Diagram of the Systems that Fill Customer Orders

Accepted Orders
1.1 Order Entry

s doo Gf ot ne mi h S p
Payments by customers
Rejected Items
Completed orders
Filled Items
s ne mt a S t e t
Invoices Billed orders Receivables ledger data
1.4 Accounts receivable
1.3 Billing
Sachin Barad
Page 10 of 49

2)
Invoice Module : -
1
Filled Items
A Figure 2 Diagram of the Invoicing
2.1 Obtain customer data
Customer Data
Customer file
Invoice Data
Invoices
2.2 Prepare invoices
Billed Orders
Customers Customers
Completed Orders
Sachin Barad
Page 11 of 49

3)
Supplier & Purchase Module : -
A Figure 3 Diagram of the Supplier, Purchase and Inventory
Purchasing data
3.1 Purchasing
Commitments Purchase orders
Filled purchase orders
Issued purchase order data
Shipments
Suppliers
3.2 Receiving
Received items Stock
Inventory & Warehouse

Supplier Invoices
Received Purchases Incurred obligations Payable ledger data 3.3 Accounts payable
Supplier Statements Payments to suppliers
Sachin Barad
Page 12 of 49

4)
Payment Receivables Module: -
Billed orders
A Figure 4 Diagram of the Accounts Receivable

New receivables Receivables records
4.1 Add new receivables
Statement records
Accounts Accounts receivable receivable file file

Receivables records to delete
4.4 Provide general ledger data

Receivables ledger data
4.3 Prepare statements

Statements Payments by customers
4.2 Delete paid receivables

Paid receivables records
Customers
Paid Paid receivables receivables file file
Sachin Barad
Page 13 of 49

5)
Payment Payables Module :-
A Figure 5 Diagram of the Accounts Payable

2 Incurred Obligations 5.1 Set up supplier payables records Received Purchases New Payables data Payables Records Payables Ledger Data 5.4 Provide general ledger data 3
Accounts Accounts payable payable file file

Payables Records to delete Paid Payables Records
2.2
Received Received purchases purchases file file

Receipt Data
Payment data
5.3 Delete paid payables

Paid Supplier Data
Paid Paid payables payables file file
Supplier Invoices
Invoice and Invoice and statement statement file file
Supplier statements
5.2 Make supplier payments
Invoice Data
Payments to Suppliers
Suppliers Suppliers
Sachin Barad
Page 14 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal 6) Inventory Module :-
A Figure 6 Diagram of the Inventory

Accepted orders
6.1 Check the balance on hand
Item records
Inventory file additions
6.3 Add received items
Received items
Items available
Inventory Inventory
Updated item records Inventory ledger data
6.2 Check the reorder point
Inventory records
Purchasing data
6.4 Provide general ledger data
Sachin Barad
Page 15 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal II) I)
Flow Chart
::-
Customer Flow Chart
Start
New Customer Request
Check Customer
No
Generate Customer
Yes
Edit Customer
No
Update Customer Details
Yes
Save Customer Details
Stop
Sachin Barad
Page 16 of 49
Module Description
The above module is work for the customer information and data. It will first check that the entered customer is already existing or not. If the same is not existing then it will generate new customer id for the new customer. If the customer already existing then the system allow user to either edit or delete the customer. Finally system will save the data to the database.
Validation for the Module
Above module is having validation over the duplication of the customer information. It will not validate new customer name If it already exists then it will never allow to add new customer.
Sachin Barad
Page 17 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal II) Sales & Orders Flow Chart :-
Start
New Order Request
Check Customer Validation
No
Yes
Check Order Material Details
No
Reject Order
Yes
Check Payments Approval
No
Yes
Order Accept
Stop
Sachin Barad
Page 18 of 49
Module Description
The above module works for the sales and order information and data. It will first check that the entered customer is already existing or not. If the same is not existing then it will reject the order and forward for the new customer code request. After that it will check for the order product is right or not if the same is not as per the product then order is rejected by the system. After that system check wither the payment method and amount order is right or not , if it is not right then the order will be rejected by the system. After having full complete order system accepts the order and give unique order id to the new order and give to production.
Above module only accept the order only if the customer is having the customer id. The system will also validate the configuration and ordered product. It will also validate the payment terms and the order amounts.
Sachin Barad
Page 19 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal III) Invoicing Flow Chart :-
Start
Obtain Order No. & Order Data
Obtain Customer Data
Prepare Invoice
Update Ledger Data
Stop
Sachin Barad
Page 20 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal Module Description
The above module take the order number and based on that it will obtain the order and customer data. After gathering all the data it will produce the invoice and it will be forwarded to the account receivable and dispatch.

Above module only accept the valid order no based on that it will gather all the data.
Sachin Barad
Page 21 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal IV) Dispatch Flow Chart :-
Start
Obtained Ordered Data
Obtain Customer Data
Check Goods Validation
No
Back to Production
Yes
Shipment to Customer
Update Order Status
Stop
Sachin Barad
Page 22 of 49
Module Description
The above module works for shipment to the customer for there respective order. It will obtain the customer and order data after that it will test the goods and then it dispatches the goods to the customer. It will provide the airway bill number or the mode of transportation to the customer.
Above module only dispatch the goods if it is as per the customer order.
Sachin Barad
Page 23 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal V) Supplier Flow Chart :-
Start
New Supplier Request
Check Supplier Validity
No
Reject Supplier
Yes
Add Supplier
Add Supplier Items
Stop
Module Description
The above module add new supplier to the system. It will first accept the registration request from the supplier and after validating the same it will ad the supplier to the system.
Above module only accept the supplier if the information provide by the supplier is validated by the user.
Sachin Barad
Page 24 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal VI) Inventory Flow Chart :-
Start
Request from Produciton
On Hand Quantity Check
No
Indent to Purchase
Yes
Supply to Produciton
Stop
Module Description
Above module deles with the indent raised by the production. It will check the on hand qty for the indented item. If it is available then it will forward the material to the production. If it is not available then it will indent to the purchase for the same.
Above module validate the qty on hand . If it is not available then the system will indent the same to purchase.
Sachin Barad
Page 25 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal VII) Purchase Flow Chart

Start
:-
Indent from Inventory
Check Supplier Availbility
No
Add New Supplier
Yes Select Supplier
Obtain Goods
Goods Check
No Validate
Reject & Return to Supplier
Validate
Invoice Transaction
Stop
Sachin Barad
Page 26 of 49
Above module deles with the purchasing activity of the system. The system will receives the indent form the inventory for the new item. It will check the qty ordered for the same. If is not ordered then it will order the same to the supplier after selecting the supplier. After receiving the materials it will checks the goods and if it is ok then forward the invoice to payable account and material to the inventory. If the goods received is not as per the requirement then the good s will be rejected by the supplier.
Above module validate the ordered qty. if it is ordered then the system will no purchase new goods. After receiving the goods it valid the received item quality.
Sachin Barad
Page 27 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal VIII) Production Flow Chart :-
Start
New Request for Produciton
Check Availbility of Furnished Goods in Inventory
No
Yes
Check Row Material Availbility in Inventory
No
Indent to Inventory
Yes Furnished Goods to Dispatch
Stop
Sachin Barad
Page 28 of 49
Module Description
Module gets the new request for the production. It will check the product availability in the ware house if it is available then it will forward the goods to the dispatch. If the same is not available in the ware house then the production will check on hand qty of the raw material. If the same is not available then it will indent to the inventory. If it will have the available raw material then it will produces the material and then it will forward the same to the dispatch.
Module validates the warehouse stoke for the availability of the ordered product. As well as it will validate the on hand raw material available for the production.
Sachin Barad
Page 29 of 49
MCA(5)-17/Project/2005 CS-17/Project Proposal IX) Payment Receivables & Payables :-
Start
Check Paym ent Type
Paym ent Payable
Check Supplier Account
Paym ent Receivable
Yes Check Goods Supplied
Pending Payments of Customer
No
No
Genertate Receipt
Notify to Others Departm ent
Yes
Yes
Make Payment
No
Notify to Others Deparm ent
Stop
Sachin Barad
Page 30 of 49

Module deals with the payment to be paid to be received by the organization. It will first check the payment mode either it is receivable or it is payable. If the payment is receivable then it will check the payment pending for the customer. If no more payment is pending from the customer end then the system generates the receipt of the payment. But if the payment id pending and it is above the limit then system notify the respective department for the pending payment. If the payment mode is receivable then the module check the ordered items received and accepted or not. If it is accepted by the organization then it will give the payment to the supplier, but if it is not accepted by the organization and it is still on hold then it will notify to the respective department for the same.
Above module validates the mode of payment that is either payment is receivable or payable. After that it validates the payment pending from the customer. It also validates the supplier goods acceptance.
Sachin Barad
Page 31 of 49
III)
Data Structures of the Modules :-
TABLES
Account_Master
Fields Data Type Length Whether N u l l AC_Code Varchar2 10 No PK Account code of Customer, Vendor & AC_Name AC_TYPE Firm_Name Address City Phone_O Phone_F Fax Email_ID Website Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 30 15 50 100 50 30 30 30 50 30 No No Others Account Name Account Type Account Holders Firm Name Address of Account Holder City of Account Holder Office Phone No. Factory Phone No. Fax No. Email ID Website Rules Initial Values Description
Sachin Barad
Page 32 of 49
Account_Details
Fields AC_Code Billing_Name Billing_Add Billing_City State Biling_Phone Ship_Name Ship_Add Ship_City Ship_State Ship_Phone Data Type Length Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 10 30 100 50 30 30 30 100 50 30 30 Whether No No Rules PK Initial Values Description Account Code Billing Name Billing Address City of Billing Address State of Billing Address Phone No. of Billing Address Shipment Name Shipment Address City of Shipment Address State of Shipment Address Phone No. of Shipment Address
Sachin Barad
Page 33 of 49
Item_Master
Fields Item_Code Item_Name Item_Type Capacity Item_Config Data Type Length Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 10 30 15 20 50 Whether No No Rules PK Initial Values Description Item Code Item Name Item Type Item Capacity Item Configuration
Purchase_Master
Fields PO_No PO_Date Supplier_Code Discount Freight Others_Charges PO_Amt Foreign Key Supplier_Code Data Type Length Number Date Varchar2 Number Number Number Number 10 8 10 15,2 15,2 15,2 15,2 Whether No No Rules PK Initial Values Description Purchase Order No. Purchase Order Date Supplier Code Discount Freight Charges Others Charges Purchase Order Amt Reference Key AC_Code
Reference Table Account_Master
Sachin Barad
Page 34 of 49
Purhcase_Tran
Fields PO_No Item_Code Qty Rate Amount Foreign Key Item_Code Data Type Length Number Varchar2 Number Number Number 10 10 10,2 15,2 15,2 Whether No No Rules PK Initial Values Description Purchase Order No. Item Code Item Quantity Item Rate Total Amount Reference Key Item_Code
Reference Table Item_Master
Sachin Barad
Page 35 of 49
Production_Master
Fields Batch_Code Batch_Date Product_ID Product_Name Product_Config Price User_Code Effect_Date Remarks Data Type Length Varchar2 Date Varchar2 Varchar2 Varchar2 Number Number Date Varchar2 10 8 10 30 100 15,2 5 8 20 Whether No No No Rules PK Initial Values Description Batch Code Batch Date Product ID Product Name Product Configruation Production Price User Code Effect Date Remarks
Product_Details
Fields Product_ID Srno Item_Code Qty Foreign Key Item_Code Data Type Length Varchar2 Number Varchar2 Number 10 5 10 10,2 Whether No Rules Initial Values Description Product ID Srno Item Code Item Quantity Reference Key Item_Code
Reference Table Item_Master
Sachin Barad
Page 36 of 49
Production_Tran
Fields Order_No. Product_ID Batch_Code Product_SID Qty User_Code Effect Date Remarks Foreign Key Product_ID Order_No Data Type Length Number Varchar2 Varchar2 Number Number Number Date Varchar2 8 10 10 10 10,2 5 8 20 Whether No Rules Initial Values Description Order No. Product ID Batch Code Product Serial ID Order Quantity User Code Effect Date Remarks Reference Key Product_ID Order_No
Reference Table Production_Master Order_Master
Sachin Barad
Page 37 of 49
Order_Master
Fields Order_No. Order Date Cust_Code Amount Status Discount_Per User_Code Effect_Date Remarks Data Type Length Number Date Varchar2 Number Varchar2 Number Number Date Varchar2 8 8 10 15,2 10 10,2 5 8 20 Whether No Rules PK Initial Values Description Order No. Order Date Customer Code Amount Status Discount Percentage User Code Effect Date Remarks
Order_Details
Fields Order_No. Srno Product_ID Item_code Qty Rate Amount Data Type Length Number Number Varchar2 Varchar2 Number Number Number 8 5 10 10 10,2 10 10 Whether No No Rules PK Initial Values Description Order No. Srno Product ID Item Code Quantity Item or Product Rate Amount
Foreign Key Product_ID Item_Code
Reference Table Production_Master Item_Master
Reference Key Product_ID Item_Code
Sales_Master
Fields Invoice_No Invocie_Date Order_No Order_Date Data Type Length Number Date Number Date 8 8 8 8 Whether No No No No Rules PK Initial Values Description Invoice No. Invoice Date Order No. Order Date
Page 38 of 49
Sachin Barad

Cust_Code Rate Amount Tax Freight Discount Total_Amount User_Code Effect_Date Remarks Varchar2 Number Number Number Number Number Number Number Date Varchar2 10 10 15,2 15,2 15,2 15,2 15,2 5 8 20 No Customer Code Item or Product Rate Amount Taxes Freight Charges Discount Discount User Code Effect Date Remarks
Sales_Details
Fields Invoice_No Srno Product_SID Qty Rate Amount Tax Data Type Length Number Number Number Number Number Number Number 8 5 10 15,2 15,2 15,2 15,2 Whether No Rules PK Initial Values Description Invoice No. Srno Product Serial No. Quantity Rate of Product Amount of Product Tax on Product
Sachin Barad
Page 39 of 49
Inventory
Fields Item_Cat Item_Code InOut_Type InOut_No InOut_Date Qty_Added Used_Qty Balance_Qty Tran_Type User_Code Effect_Date Remarks Data Type Length Varchar2 Varchar2 Varchar2 Number Date Number Number Number Varchar2 Number Date Varchar2 15 10 8 15 8 15,2 15,2 15,2 10 5 8 20 Whether No No Rules PK Initial Values Description Item Category Item Code Inward /Outward Status Inward/Outward No. Inward/Outward Date New Added Quantity Used Quantity Balance Quantity Transaction Type User Name Effect Date Remarks
Dispatch
Fields Order_No Shipment_No AWB_No Courier_Code Dispatch_Date Invoice_No User_Code Effect_Date Remarks Data Type Length Number Number Number Varchar2 Date Varchar2 Number Date Varchar2 20 15 15 10 8 10 5 8 20 Whether No No Rules PK Initial Values Description Order No. Shipment No. Air Way Bill No. Courier Code Inward/Outward Date Invoice No. User Code Effect Date Remarks
Sachin Barad
Page 40 of 49
Bank_Master
Fields Tran_ID Tran_Date AC_Code Discription Bank_Code Cheque_No Cheque_Date Amount DC User_Code Effect_Date Remarks Data Type Length Number Date Varchar2 Varchar2 Varchar2 Varchar2 Date Number Varchar2 Number Date Varchar2 15 8 10 30 10 10 8 15,2 1 5 8 20 Whether No No Rules PK Initial Values Description Transaction ID Transaction Date Account Code Discription Bank Code Cheque No. Cheque Date Amount Debit / Credit Status User Name Effect Date Remarks
Cash_Master
Fields Tran_ID Tran_Date AC_Code Discription Amount DC User_Code Effect_Date Remarks Data Type Length Number Date Varchar2 Varchar2 Number Varchar2 Number Date Varchar2 15 8 10 30 15,2 1 5 8 20 Whether No No Rules PK Initial Values Description Transaction ID Transaction Date Account Code Discription Amount Debit / Credit Status User Name Effect Date Remarks
Payment_Settlement Fields Tran_Type Tran_ID Srno Invoice_No Amount Data Type Length Varchar2 Number Number Number Number 10 15 5 10 15,2 Whether No No Rules PK PK Initial Values Description Transaction Type Transaction ID Srno Invoice No. Amount
Page 41 of 49
Sachin Barad

DC User_Code Effect_Date Remarks Varchar2 Number Date Varchar2 1 5 8 20 Debit / Credit Status User Name Effect Date Remarks
Sachin Barad
Page 42 of 49
IV)
1.
PROCESS LOGIC OF MODULES

Process logic for Customer module
:-
In this module unique code for each customer will be created. If the customer already exists and require to change address then it will be stored in the details table with new billing address or shipment address. It will not allow adding same customer in the module. That will allow customer vise analysis possible. Reports 2. Customer vise Sales Customer vise revenue Customer vise order Customer vise details Customer contact details
Process logic for the module Sales & order In this module order number will be garneted which will be unique. Through out the process the order no will be the key to access the information from the system. The order will be accepted only if the customer valid customer and order product is valid. With the payment checks. That will take the order and forward the same to the production for the production. Reports Date vise order details Month vise order details Completed order details Pending order details Rejected order details
Sachin Barad
Page 43 of 49

3. Process logic for the module Production Production module will receive the order for production. Production will check if the certain ordered product is available in ware house then it will forward the same to the dispatch department and forward the details to payment receivable and payable as well as to the invoicing module. If the production is required the n production will check on had Qty of raw material to produce the product. If not available then indent to inventory for the same. After completing the production it follow the same process of forwarding as described above. Reports 4. Date vise Production Month & Year vise production Production time Batch efficiency
Process logic for the invoicing module Based on the information passed by the production , this module creates invoices by using the customer and order details table. Then it will forward the information to the account payable and receivable. As well as it will forward a copy of invoice to the dispatch. Reports Date vise Invoices Month Year vise invoices Customer vise invoices Order vise invoices Rejected invoice Changed Invoice
Sachin Barad
Page 44 of 49

5. Process logic for Inventory As soon as module receives the indent from the production, it will check the indent items on hand qty. If it is not available then it will select the supplier for the same and give the indent to purchase. After obtaining the qty it will forward the same to the production for the production. If the material is available then it will forward the same to the production department immediately Reports 6. Date vise stock Item vise stock details Orders item details Order level reached item details Indents pending from the Purchase
Purchase Purchase will receive the indent of purchase of raw material from the inventory. It will check the supplier who supplies the same. It will select the supplier and the give the purchase order to the supplier. After obtain the martial, purchase will send the goods to the inventory and after receiving the acceptance from the inventory it will forward the invoice to the payment receivable & payable. If supplier for the said item is not available then it request supplier module to add new supplier for the same. Reports Date vise Purchase order Month year vise Purchase order Pending Invoice with purchase Pending acceptance Pending Purchase order
Sachin Barad
Page 45 of 49

7. Process logic for the supplier module Supplier module will add the supplier for which the organization requires. It will check the supplier and accept or reject the same. Organization only can only purchase from the registered supplier with them. It will also do the quotation and negotiation. Reports 8. Item vise registered supplier Item vise best supplier Supplier registered Rejected supplier
Process logic for the payment payable & receivable module This module receive both invoice i.e. incoming and outgoing. That mans that this module receives against which they have to collect the payment and invoice against which they have to give the payments. In the receivables they will check if the dispatch and order is completed then they will ask for the payment and notify the same to the respective department. If they collect the payment then they will generate payment receipt for the goods. If it is to be paid then they will check with purchase if it is cleared by them they will pay the payment and take the receipt from the respective supplier. Reports Date vise payment received Month, year vise payment received Date vise payment paid Date vise payment paid Out standing payment receivable Out standing payment payable
Sachin Barad
Page 46 of 49

9. Process logic for dispatch & distribution After receiving the goods for dispatch against the order number. Dispatch will do the packing and ship the billed material to the customer shipment address mentioned in the order with the invoice. It will take the dispatch details with airway bill number or the mode of delivery and update in the system. After module receives the received confirmation from the customer it will finally close the order. Reports Date vise shipment Month, year vise shipment Product vise shipment Customer vise shipment Daily shipment
Sachin Barad
Page 47 of 49
(V)
TESTING
:-
The testing of this program will occur at three different levels:

i.
We will test individual client applications in stand alone mode - the client server application is not consider at this point of testing. That will only test the client end application.
ii.
We will client software and associated server applications in concert, but we will not explicitly exercised any network operation.
iii.
The complete C/S architecture, including network operation and performance is tested in this phase for the complete software.
In this project there will be alpha testing, because the Drasti system does not have the necessary infrastructures for conducting these tests over there. So they will come to our site for the testing.
Sachin Barad
Page 48 of 49
(6)
SCOPE OF FUTURE APPLICATION :
The project is attempt to make full functional ERP system for the organization. After completing the ERP stage we can implement further management utilities for the better decision making process for the management. After having a full integration of the entire network and integrating all the application with the system will provide fully computerize digital communication and process for the organization. This application further developed or integrated with the new emerging business software. It will further developed for SRM, SCM & many more modules.
e-commerce Employees SCM ERP ORMS Product Design CRM Customers Suppliers
As shown in the above figure organization can implement the whole decision making digital system. Which will virtually works as a digital brain for the company. Company can also implement data ware housing for the historical reports and knowledge for the further decision support. Hence the said system is virtually the back born of the digital information path for the organization and it can integrate with any other software to provide flexibility.
Sachin Barad
Page 49 of 49

Project On Erp (Idns)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project On Erp (Idns)

Uploaded by

Copyright:

Available Formats

SCHOOL OF COMPUTER AND INFORMATION SCIENCES INDIRA GANDHI NATIONAL OPEN UNIVERSITY

Master of Computer Application 5th Semester CS - 17

MCA(5)-17/Project/2005 CS-17/Project Proposal

Sachin Barad Yogesh Dwivedi

MCA(5)-17/Project/2005 CS-17/Project Proposal

Title of the project

Intelligent Digital Nervous System

MCA(5)-17/Project/2005 CS-17/Project Proposal

Limitation of the Current System

Information user are dependent on user for the information.

MCA(5)-17/Project/2005 CS-17/Project Proposal

Objectives / Features of the Project

MCA(5)-17/Project/2005 CS-17/Project Proposal

MCA(5)-17/Project/2005 Cu stom er CS-17/Project Proposal

Sales & Order

Dispatch & Delivery

Module Diagram of IDNS (Intelligent Digital Nervous System)

MCA(5)-17/Project/2005 CS-17/Project Proposal

A Context Free Diagram of Intelligent Digital Nervous System

Intelligent Digital Nervous System

A Context Diagram of the

Rejected Sales Order Notices Invoices Statements Payments by customers

Supplier invoices Supplier statements

Payments to suppliers Request for Production Order Shipments Stock

MCA(5)-17/Project/2005 CS-17/Project Proposal

Complete Structure of the System

Rejected sales order notices Invoices

A Figure 1 Diagram of the Intelligent Digital Nervous System

Statements Payments by customers

Purchasing Data Commitments

Purchase Orders Shipments Supplier invoices

3. Payment Receivables & Payables

Payables ledger data Payments to suppliers

2. Inventory & Warehouse

Furnished Goods Request for Row Materials

MCA(5)-17/Project/2005 CS-17/Project Proposal LEVEL2 DFD

Customer & Order Module : -

Rejected Sales Order Notices

A Figure 1 Diagram of the Systems that Fill Customer Orders

1.1 Order Entry

Invoices Billed orders Receivables ledger data

1.4 Accounts receivable

MCA(5)-17/Project/2005 CS-17/Project Proposal

A Figure 2 Diagram of the Invoicing

2.1 Obtain customer data

2.2 Prepare invoices

MCA(5)-17/Project/2005 CS-17/Project Proposal

Supplier & Purchase Module : -

A Figure 3 Diagram of the Supplier, Purchase and Inventory

Commitments Purchase orders

Filled purchase orders

Issued purchase order data

Received items Stock

Inventory & Warehouse

Supplier Statements Payments to suppliers

MCA(5)-17/Project/2005 CS-17/Project Proposal

Payment Receivables Module: -

A Figure 4 Diagram of the Accounts Receivable

4.1 Add new receivables

Accounts Accounts receivable receivable file file

4.4 Provide general ledger data

4.3 Prepare statements