ERP basic data Huaxia

One 、 Organizational structure

Here I refer to the organizational structure of Kingdee's test account , The specific organizational structure background will not be repeated .

There are tree operations , Then the left and right structures . It is very convenient to use and interact .

Two 、 User and authority system

1、 role

After adding a role, the create name and data type will appear .

Here we focus on the three public data types ：1、 All data - It can be understood as the administrator of the system .2、 Data of this institution - In the previous section, we set up a mechanism , If this option is selected, the data of other organizations cannot be viewed by changing the role （ This enables data isolation between organizations ）.3、 Personal data - You can only view documents created by yourself （ This is mainly for similar sales and purchases , It is sensitive to the data of some users at the same level ）.

2、 jurisdiction

Authority here , It is also a conventional design . It is divided into function permission and Data permission .

There is a tree structure in the function permission ：

Data permissions can be assigned ： edit 、 to examine 、 De audit

 3、 user

When adding a new user, in addition to the regular user name 、 password , Added name 、 role 、 Institutions . Conventional ERP The system rarely allows users to register directly , Generally, it is an internal distribution account of the enterprise . In addition, the meaning of adding a name is , Some documents need to print the name directly , So the name is very important for the account . The role and organization determine the function and authority of the user .

Inside the password , Give a default password directly . Someone here will ask , Will there be a risk of disclosure , What if someone else logs in , The newly created account of the whole group is a default password . My answer is that there are security risks , But the risk will not be great . Generally, the current system will force users to change their passwords after logging in , In addition, such accounts are issued , Employees in the enterprise will be informed through internal e-mail and other means . Of course, some systems are not excluded , There is no mandatory password change , Cause other employees to log in to this person's account .

 

3、 ... and 、 Basic data

1、 Supplier information

Regular supplier entry , Subsequently, it is used for purchase management . Here I mainly want to say . Huaxia ERP It is really aimed at small and medium-sized customers , Very few required items . Just a noun . For SMEs , Sometimes it's really unnecessary to have so many required items , The scale of follow-up enterprises has come up , According to the control needs , You can add more . This design can at least make the logic run through , Run smoothly , Reduce the cost of using .

 

2、 Customer information

Regular customer information entry , Subsequently, it is used for sales management

 

3、 Member information

The member information is mainly the retail module

4、 Warehouse information

Normal operation , Later, it is used in the warehouse management module

5、 Revenue and expenditure items

Classify revenue and expenditure items , Facilitate subsequent statistical data . 

6、 Settlement account

Different settlement accounts can be set . For different management needs ： For example, cash 、 Transfer accounts 、 Remittance, etc .

7、 Operator management

Set different types of handlers , It can be managed in subsequent sales and financial documents . Here you can see , The name does not follow the previous user management . This is convenient for a user , It can be used by many people . A finance department only needs one account , When corresponding to specific business documents , Select a specific handler . The same goes for sales . Of course, the advantage is that customers need to buy many accounts , The disadvantage is that information can be seen by everyone . This design supports at least from the technical level , A variety of user scenarios .

8、 Vehicle management

This is mainly used to enter vehicle information , But it is not related to other modules . There may be new functions in the future ？

9、 Customer follow up （ Personally, I don't think it should be included in the basic data module ）

Customer management should be regarded as the follow-up operation before the sales order in sales management .CRM Core functions in the system . At present, this function is still relatively shallow , It can only serve as a record .