CN113592374A

CN113592374A - Equipment purchasing management system, method, server and storage medium

Info

Publication number: CN113592374A
Application number: CN202110120497.0A
Authority: CN
Inventors: 朱琳; 李璐; 李帚群
Original assignee: Beijing Kingsoft Software Co Ltd; Beijing Kingsoft Digital Entertainment Co Ltd
Current assignee: Beijing Kingsoft Software Co Ltd; Kingsoft Corp Ltd; Beijing Kingsoft Digital Entertainment Co Ltd
Priority date: 2020-04-30
Filing date: 2021-01-28
Publication date: 2021-11-02

Abstract

The embodiment of the invention provides a system, a method, a server and a storage medium for equipment purchase management, wherein the system comprises: the OA server and various clients in communication connection with the OA server, and an external asset management server; the OA server is in communication connection with the external asset management server; the plurality of clients include: an asset management client. By applying the embodiment of the invention, the data required by the external asset management server can be input from the OA server, and the information of the asset card of each target device and the purchased information are correspondingly stored in the OA server, so that the unified management from the OA server is realized, and the data collection and management are convenient.

Description

Equipment purchasing management system, method, server and storage medium

Technical Field

The invention relates to the technical field of office automation, in particular to a system, a method, a server and a storage medium for equipment purchase management.

Background

At present, enterprises generally need to purchase various office equipment in daily operation, employees often apply for purchasing assets in a mode of oral notification, paper or mails, after purchasing personnel of a purchasing department summarize purchasing requirements, the assets are purchased from external manufacturers together after overall arrangement, after the assets are purchased, information of the purchased assets is manually input into external asset management Systems such as SAP (Systems, Application and Products in Data Processing), friends and golden butterfly by an asset manager, and finally the enterprise assets are subjected to information management in the external asset management Systems. However, the management link before the data is recorded into the asset management system is not well solved, and as assets are stored from purchasing to warehousing, the participating departments are numerous, purchasing-related data needs to be input for many times by different departments in an enterprise, and data input needs to be performed again in an external asset management system, so that the data is dispersed, and the data is inconvenient to collect and manage.

Therefore, there is an urgent need for an asset procurement management system to facilitate data collection and management.

Disclosure of Invention

The embodiment of the invention aims to provide a system, a method, a server and a storage medium for equipment purchase management, which are convenient for data collection and management. The specific technical scheme is as follows:

in a first aspect, an embodiment of the present invention provides an apparatus procurement management system, where the system includes: the OA server and various clients in communication connection with the OA server, and an external asset management server; the OA server is in communication connection with the external asset management server; the plurality of clients include: an asset management client;

the asset management client is used for displaying an asset data entry interface provided by the OA server, receiving first data of each purchased target device input by an asset manager based on the obtained procurement information, and sending an asset creation request to the OA server, wherein the asset creation request comprises: first data for each purchased target device; the first data is: the external asset management server creates first data required by an asset card corresponding to each purchased target device; the purchased information comprises: device details of the purchased target device;

the OA server is used for calling a preset asset creating interface based on the asset creating request, generating an asset card creating request and sending the asset card creating request to an external asset management server, wherein the asset card creating request comprises: first data of each purchased target device; receiving asset card information corresponding to each purchased target device returned by the external asset management server; correspondingly storing each returned asset card information and the purchased information;

the external asset management server is configured to generate a corresponding asset card for each purchased target device based on the first data of each purchased target device in the asset card creation request, and return asset card information corresponding to each purchased target device to the OA server.

In a second aspect, an embodiment of the present invention further provides an apparatus procurement management method, which is applied to the OA server in the foregoing system, and the method includes:

the purchased information is obtained and sent to an asset management client, so that the asset management client displays an asset data entry interface provided by the OA server, receives first data of each purchased target device input by an asset manager based on the purchased information, and sends an asset creation request to the OA server, wherein the asset creation request comprises: first data of each purchased target device; the first data is: the external asset management server creates first data required by an asset card corresponding to each purchased target device; the purchased information comprises: device details of the purchased target device;

receiving the asset creation request;

based on the asset creating request, calling a preset asset creating interface to generate an asset card creating request, and sending the asset card creating request to an external asset management server; the asset card creation request comprises: the first data of each purchased target device, so that the external asset management server generates a corresponding asset card for each purchased target device respectively based on the first data of each purchased target device;

receiving asset card information corresponding to each purchased target device returned by the external asset management server; and correspondingly storing each returned asset card information and the purchased information.

In a third aspect, an embodiment of the present invention further provides an apparatus purchasing management method, which is applied to the external asset management server, where the method includes:

receiving an asset card creation request generated and sent by an OA server by calling a preset asset creation interface; the asset card creation request comprises: first data for each purchased target device; the first data is: the OA server is received through the asset management client and is input by an asset manager based on the purchased information; the purchased information is as follows: the OA server receives the data through the target purchasing client and is input by a purchaser;

respectively generating corresponding asset cards for each purchased target device based on the first data of each purchased target device, and obtaining information of each asset card;

and returning the asset card information corresponding to each purchased target device to the OA server so that the OA server correspondingly stores each returned asset card information and the purchased information.

In a fourth aspect, an embodiment of the present invention provides an OA server in an equipment procurement management system, including a processor, a communication interface, a memory and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;

a memory for storing a computer program;

and a processor for implementing the method steps of equipment procurement management of the OA server when executing the program stored in the memory.

In a fifth aspect, an embodiment of the present invention further provides an external asset management server in an equipment procurement management system, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus;

a memory for storing a computer program; and the processor is used for realizing the method steps of equipment purchasing management of the external asset management server when executing the program stored in the memory.

In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program is executed by a processor to perform any of the steps of the equipment procurement management method.

In a seventh aspect, an embodiment of the present invention further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute any one of the above-mentioned device procurement management methods.

The embodiment of the invention provides a system, a method, a server and a storage medium for managing equipment purchase, wherein the system comprises: OA servers and external asset management servers. By applying the embodiment of the invention, the data required by the external asset management server can be input from the OA server, and the identification information of the asset card of each target device and the purchased information are correspondingly stored in the OA server, so that the unified management from the OA server is realized, and the data collection and management are convenient.

In addition, by applying the embodiment of the invention, the external asset management server generates the corresponding asset cards for each target device respectively based on the first data of each target device, so that when the external asset management server receives a plurality of first data of a plurality of target devices, the external asset management server can generate the asset cards in batch, and the user operation is further simplified.

Of course, not all of the advantages described above need to be achieved at the same time in the practice of any one product or method of the invention.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic structural diagram of an apparatus procurement management system according to an embodiment of the invention;

fig. 2a is a schematic structural diagram of an apparatus procurement management system according to an embodiment of the invention;

FIG. 2b is an interactive flow diagram for equipment procurement management using the equipment procurement management system of FIG. 2 a;

FIG. 2c is an exemplary diagram of a purchase list input interface of the interaction flow of FIG. 2 b;

FIG. 2d is an exemplary diagram of a purchased information entry interface of the interaction flow of FIG. 2 b;

FIG. 2e is an exemplary diagram of a detailed information entry interface in the interaction flow of FIG. 2 b;

FIG. 2f is an exemplary diagram of data required to generate an asset card in the interaction flow of FIG. 2 b;

FIG. 3a is a schematic structural diagram of an apparatus procurement management system according to an embodiment of the invention;

FIG. 3b is an interactive flow diagram of data synchronization in the equipment procurement management system of FIG. 3 a;

FIG. 3c is an interactive flow diagram for equipment procurement management using the equipment procurement management system of FIG. 3 a;

FIG. 4 is a schematic diagram of an application example of the equipment procurement management system according to the embodiment of the invention;

FIG. 5a is a diagram illustrating the call to the SAP RFC function to achieve synchronous communication;

FIG. 5b is another diagram illustrating the call to the SAP RFC function to achieve synchronous communication;

FIG. 6 is a schematic structural diagram of an OA server provided in an embodiment of the present invention;

fig. 7 is a schematic structural diagram of an external asset management server according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

In order to facilitate management of data, embodiments of the present invention provide a system, a method, a server, and a storage medium for device procurement management.

Referring to fig. 1, a schematic structural diagram of an apparatus procurement management system according to an embodiment of the present invention is shown in fig. 1, where the system includes: various clients to which an OA (Office Automation) server 100 is communicatively connected, and an external asset management server 110; OA server 100 is communicatively connected to an external asset management server 110; as shown in fig. 1, the various clients include: asset management client 120.

The asset management client 120 displays an asset data entry interface provided by the OA server 100, receives first data of each purchased target device input by an asset manager based on the obtained procurement information, and transmits an asset creation request to the OA server 100. The asset creation request includes: first data for each purchased target device; the first data is: the external asset management server 110 creates first data required for an asset card corresponding to each purchased target device; the purchased information comprises: device details of the purchased target device.

The OA server 100 is configured to invoke a preset asset creating interface based on an asset creating request, generate an asset card creating request, and send the asset card creating request to the external asset management server 110, where the asset card creating request includes: first data for each purchased target device; and receives asset card information corresponding to each purchased target device returned by the external asset management server 110; and correspondingly storing the returned information of each asset card and the purchased information.

The external asset management server 110 is configured to generate a corresponding asset card for each purchased target device based on the first data of each purchased target device in the asset card creation request, and return asset card information corresponding to each purchased target device to the OA server 100.

It can be seen from the above embodiments that, by applying the embodiments of the present invention, data required by the external asset management server can be input from the OA server, and the identification information of the asset card of each target device and the purchased information are correspondingly stored in the OA server, so that unified management from the OA server is realized, and convenience is brought to data collection and management.

Referring to fig. 2a, fig. 2a is a schematic structural diagram of an apparatus procurement management system according to an embodiment of the invention. The device procurement management system of the present embodiment further includes an employee client 200 and a target procurement client 210 on the basis of the embodiment shown in fig. 1.

The employee client 200 is configured to display a purchase application interface provided by the OA server 100, receive target purchase information input by an employee, generate an equipment purchase request, and send the equipment purchase request to the OA server 100, where the equipment purchase request includes: identification information of the target device obtained from the target procurement information.

The OA server 100 is further configured to generate an OA-side purchase flow sheet based on the equipment purchase request; wherein, in the OA end purchase flow sheet, include: identification information of the target device.

The target purchasing client 210 is configured to display a purchasing information entry interface provided by the OA server 100, obtain the OA-side purchasing flow sheet from the OA server 100, and output the OA-side purchasing flow sheet to a purchaser; and receives the purchased information input by the buyer based on the OA-side purchase flow sheet, and feeds back the information to the OA server 100.

The OA server 100 is further configured to receive the purchased information and send the purchased information to the asset management client 120, so that the asset management client 120 obtains the purchased information. The OA server 100 also stores the procurement flow sheet of the OA terminal and the returned information of each asset card in correspondence with the procured information.

In one specific embodiment, the OA server 100 has the following uses: receiving an equipment purchase request sent by the employee client 200 through a purchase application interface; generating an OA end purchasing flow sheet based on the equipment purchasing request; sending the OA end purchase flow sheet to the target purchase client 210; the OA server 100 receives the purchased information sent back by the target purchasing client 210 through the purchasing information entry interface, and sends the purchased information to the asset management client 120; the asset management client 120 receives an asset creation request sent by the asset management client 120 through an asset data entry interface; the OA server 100 further generates an asset card creation request based on the asset creation request, and transmits the asset card creation request to the external asset management server 110; receiving asset card information of each target device returned by the external asset management server 110; and correspondingly storing the asset card information of each target device, the OA end purchase flow sheet and the purchased information.

In another specific embodiment, the OA server 100 may have the following uses: receiving an equipment purchase request sent by the employee client 200 through a purchase application interface; generating an OA end purchasing flow sheet and identification information based on the equipment purchasing request; sending the identification information of the OA-side purchase flow sheet to the target purchase client 210; the target purchasing client 210 acquires the OA end purchasing flow sheet from the OA server 100 based on the identification of the OA end purchasing flow sheet; then, OA server 100 receives the purchased information sent back from target purchasing client 210 through the purchasing information entry interface, and sends the purchased information to asset management client 120; the asset management client 120 receives an asset creation request sent by the asset management client 120 through an asset data entry interface; the OA server 100 further generates an asset card creation request based on the asset creation request, and transmits the asset card creation request to the external asset management server 110; receiving the identification information of the asset card of each target device returned by the external asset management server 110; and correspondingly storing the identification information of the asset card of each target device, the identification information of the purchase flow sheet of the OA terminal and the purchased information.

In the above embodiment, the device procurement request includes, but is not limited to: identification information of the target device, for example: type information, etc. Specifically, the device type may be a specific device such as a notebook computer, a desktop computer, a printer, and the like. The purchased information is configuration information of the specific device input by a purchaser after purchasing the device based on the requirement of the OA-side purchase flow sheet, for example: the brand, the memory, the hard disk, whether the mouse exists or not of the notebook computer and other configuration information. Asset creation requests include, but are not limited to: the asset manager inputs first data of each target device based on the purchased information; the first data is data required for creating an asset card corresponding to each target device, different target devices have different listed data in the asset card, and the listed data in the asset card of the same target device are different according to different external asset management servers. The asset card creation request includes the first data of each target device, so that the external asset management server 110 generates a corresponding asset card for each target device based on the first data of each target device, and then the external asset management server returns the identification information of the asset card of each target device to the OA server 100. The first data mainly includes company codes, cost centers, asset classifications, and main data evaluation groups required by the external asset management server 110 to generate asset cards.

In this embodiment, the data standard required by the asset card of each target device is derived from the standard specified by the external asset management server 110, and based on the standard specified by the external asset management server 110, the preset data field required by the external asset management server 110 to generate the asset card may be determined in advance, and the data input template may be set based on the preset data field. In this way, the asset manager may enter first data for each target device via the data entry template based on the purchased information.

An external asset management server 110 for receiving an asset card creation request; the asset card creating request comprises first data of each target device; the first data is data required for creating an asset card corresponding to each target device; based on the first data of each target device, a corresponding asset card is generated for each target device, and asset card information or asset card identification information of each target device is returned to the OA server 100.

In this embodiment, the employee client 200, the asset management client 120, and the target purchasing client 210 may be application software installed on a PC, or may be clients that are accessed through a Web server.

In the above embodiment, the OA server 100 and the external asset management server 110 are servers located at different places, and may be maintained and managed by different service providers. Different external asset management servers 110 may be maintained and managed by different service providers, and since the identification information rules of the asset cards are likely to be different due to the different service providers of the external asset management servers 110, the OA server 100 needs to create different device purchase lists and OA-side purchase process lists according to the rules of the required data of the asset cards of the different external asset management servers 110.

The device procurement manifest and the OA-side procurement flow sheet of the OA server 100 may adopt configurable management, such as: the OA server 100 provides configuration interfaces of the device purchase list and the OA-side purchase process list, respectively, and the user configures preset data fields required for generating the asset card through the configuration interfaces. In addition, the OA server 100 may also have a process replication function, which may be implemented quickly to adapt to different external asset management servers 110.

Meanwhile, the OA server supports various interfaces such as Wenservice and https, and meets the requirement of compatibility of the external asset management software. For example, the external asset management server 110 is an SAP server, the SAP server and the OA server may use an ebservice interface, the OA server issues a webservice interface for the SAP server to call, the interface transmits the asset master data (e.g., preset data fields and default values required by the asset card) generated and stored by the SAP server to the OA server and stores the asset master data in the OA database, and the OA server may directly create the equipment purchase list and the purchase flow sheet based on the asset master data. The SAP server may also perform idle data synchronization by calling an interface to push data in a timed task manner, and the data synchronization range may be incremental synchronization, for example: the modified master data of the previous day is synchronized each day.

Therefore, by applying the embodiment of the present invention, the external asset management server 110 generates the corresponding asset cards for each target device based on the first data of each target device, so that when the external asset management server 110 receives a plurality of first data of a plurality of target devices, the external asset management server 110 can generate the asset cards in batch, thereby simplifying the user operation.

In addition, in the prior art, the OA server and the external asset management server do not communicate with each other, and each OA server maintains a database, and the data format and the data content stored in each database are different. If an enterprise needs to use the OA server to manage the purchasing process and needs to use the external asset management server to manage the assets of purchasing, the asset management personnel needs to respectively perform data entry on the OA server and the external asset management server. However, the data entered by the 2 servers are not completely different, and some data are overlapped, so that the situation of data repeated entry occurs.

In the embodiment of the present invention, a communication connection is established between the OA server 100 and the external asset management server 110. Data required by the OA server 100 and data required by the asset card generated by the external asset management server 110 can be input through the OA server, so that the user operation is simplified.

Specifically, by applying the embodiment of the present invention, the asset card information of each target device, the OA-side purchase flow sheet and the purchased information may be stored in the OA server 100 correspondingly, and a one-to-one correspondence relationship between the data and each target device is established. Thus, general employees who request to purchase the target device, general employees who use the target device, a purchase manager, and an asset manager can view, manage, and maintain their own data in the OA server 100 in a unified manner according to their respective authorities.

When the asset manager is to enter asset information into the external asset management server 110, it can be entered into the external asset management server 110 through the OA server 100, and data synchronization of the OA server 100 and the external asset management server 110 can be achieved. Data generated by a certain target device under different standards can be unified in the OA server 100, and one-to-one correspondence is made, so that the data cannot be lost or confused, and the device management of a company is more standard and easier.

Compared with the work of data entry and maintenance on the client side of the external asset management server 110, by applying the embodiment of the invention, an asset manager only needs to automatically enter data through the OA server 100, so that errors caused by manual entry of the external asset management server 110 for multiple times are avoided, the time of the asset manager is saved, and the accuracy of the data is improved. Previously, asset managers had often encountered problems with data loss during manual entry into the external asset management server 110, such as when the external asset management server crashed. Each different device has different asset cards, each external asset management server has different rules of the required data of the asset cards, so if an asset manager maintains a plurality of external asset management servers, the rules of the plurality of asset cards of the plurality of external asset management servers need to be familiar with, the professional requirement of the asset manager is high, and errors are easy, and after the OA server is used for managing the data, the work of a device user, a purchase manager and the asset manager is simple, and errors are not easy.

The external asset management server in the embodiment of the present invention may be a server in any asset management system, such as a management server in an ERP (Enterprise Resource Planning) system, for example, an SAP server, a management server in a friend-using EPR system, or a management server in a golden butterfly ERP system.

Corresponding to the above-mentioned embodiment of the device procurement management system shown in fig. 2a, an interactive flowchart of device procurement management by using the device procurement management system shown in fig. 2a, as shown in fig. 2b, may include:

step S201, sending a device purchase request to an OA server by an employee client; the device purchase request may include identification information of the target device, such as: target device type, etc.

The OA server may set up authority for each employee in advance, and the authorized employee may initiate the purchasing process by filling in the purchasing list at the employee client. For example, the authority for initiating the purchasing process of the personal electronic device is set for the department assistant, and when other personnel in the department need to purchase the electronic device, the department assistant performs statistics, fills the purchasing list on the staff client and initiates the purchasing process. Here, the control of the authority can be achieved in two ways: in the first mode, the employees are grouped based on positions, and different authorities are allocated to each group, such as: the authority to view personal assets, the authority to view department assets, the authority to view all assets, the authority to initiate purchasing processes, the authority to determine purchasing personnel, the authority to determine purchasing orders, and so on. For example: the assistant is put into the assistant role group, and then the authority which can initiate the purchasing process and the authority for checking the department assets are assembled on the assistant role group. And directly maintaining a personnel authority table capable of initiating the purchasing process, wherein the personnel authority table stores a personnel list capable of initiating the purchasing process.

Specifically, when a purchasing process needs to be initiated, the employee client verifies the authority of the employee first, and displays a purchasing application interface provided by the OA server under the condition that the employee has the authority, for example: and the purchase list input interface receives target purchase information input by an employee (namely an authorized user), generates a device purchase request and sends the device purchase request to the OA server.

The OA server may generate an OA bill number for the purchase list according to a preset bill generation rule after the employee opens the purchase list input interface, where the bill number is a unique number of the purchase list and is used to identify the whole flow of the order, and may also serve as an identifier of the OA end purchase flow list after the OA end purchase flow list is subsequently generated. The staff can fill in simple purchasing requirements on the purchasing list input interface, the system can automatically bring out the organization structure, the cost center and the business unit of the staff by filling in the user of the equipment, then fill in default values of fields such as regions, required arrival dates, application descriptions and the like, and then need to fill in equipment specific model requirements in the purchasing list input interface. The specific purchase list entry interface is shown in FIG. 2 c.

Through the purchase list input interface, the user can select the device type, detailed configuration, quantity, and location of use information of the device to be purchased. And the functions of adding, deleting, storing, importing, downloading templates and the like can be realized.

As can be seen from fig. 2c, the information filled by the employee is relatively conventional and understandable, and can be successfully filled without training. This is in contrast to forms filled by asset managers, which are rules that match external asset management server rules, which ordinary employees would not have the ability to fill without learning the rules. The device type drop-down list in fig. 2c is a device type customized by the OA server, and different from the device type of the external asset management server, the device type in fig. 2c is easier for the general staff to fill in, and the content filled in by the asset manager is a professional field more conforming to the rules of the external asset management server, and the general staff does not need to know the professional field.

For example: when employee a initiates the procurement process, OA server will call various existing information of employee a from the data stored in the database according to the identification of employee a, such as name or job number, and fill in the process template form, for example: the organization structure, the superior-subordinate relation, the cost center and the like of the staff save the time for the staff to fill again, and prevent the flow from making mistakes after the staff fills in mistakes and can not be handled continuously.

After the completion of the filling of the purchase list, the employee client generates a device purchase request based on the purchase list and sends the device purchase request to the OA server.

Step S202, the OA server generates an OA end purchase flow sheet based on the equipment purchase request. The OA-side procurement flow sheet may include identification information of the target device obtained from the device procurement request, such as: target device type, etc.

After the OA server generates the OA end purchase flow sheet, the OA document number generated for the purchase list before and the OA end purchase flow sheet may be associated, that is, the OA document number is used as the identifier of the OA end purchase flow sheet.

After receiving the device purchase request, the OA server notifies the next node in the purchase process to perform processing. The next node may be an asset management client for auditing the purchase list. The OA server sends the equipment purchase list to the asset management client, and the asset management client outputs the purchase list to an asset manager.

And the asset manager checks whether the equipment with the configuration is under the name of the employee applying for purchasing, and if so, informs the related personnel. If not, the OA database is queried to determine whether the equipment is in stock, if so, the equipment is distributed to the employee applying for purchase, the equipment is called, and the purchase process is filed.

If the asset manager finds that there is no such device under the name of the employee, and there is no tunable device in inventory, the flow is passed to the next node. The asset management client may return a confirmation purchase message to the OA server. Alternatively, the purchasing principal is notified of the need to purchase the target device.

At this time, the next node is the purchasing client used by the purchasing responsible person.

The purchasing responsible person uses a first purchasing client of the purchasing responsible person to initiate a price inquiry flow to a plurality of second purchasing clients corresponding to a plurality of purchasing specialists. And the first purchasing client receives a plurality of optional purchasing schemes reported by a plurality of purchasing specialists through the second purchasing clients, so that the purchasing responsible person can prefer the optimal purchasing scheme.

For example: the purchasing person in charge selects to initiate a plurality of inquiry sub-processes to each purchasing person in the node. The number of procurement specialists may be unlimited. After receiving the purchasing specialist in the purchasing sub-process, the purchasing specialist can find out the agent and supplier in his own hand to inquire the price, the inquired result is input into the price inquiring sub-process list and is sent back to the first purchasing client of the purchasing person through the second purchasing client.

Here, the inquiry flow sheet entered by the purchasing specialist through the second purchasing client may include: equipment model, buyer, time of purchase, price, offer, place of origin, sales channel (online, offline), inquirer's advice, supplementary accessories, etc.

And the purchasing responsible person sends the optimal purchasing scheme selected by the purchasing responsible person and the identification of the target purchasing client side to the OA server through the first purchasing client side.

Here, the purchasing responsible person can select a plurality of purchasing schemes from a plurality of price inquiry flow lists, and the purchasing responsible person is not limited to one purchasing scheme or a price inquiry scheme returned by one purchasing person and is flexible.

And the OA server sends the optimal purchasing scheme serving as a target purchasing scheme to the target purchasing client and informs the selected target purchasing client of the corresponding purchasing specialist. And stop other inquiry sub-processes.

In some embodiments, the OA server may further send the purchase request to a superior leader of the employee applying for purchase, initiate an approval cost process, and generate an OA-side purchase process sheet after completion of the approval costs at each level.

The examination and approval cost process can be judged according to the purchase amount, and leads from a department responsible person to leaders at all levels in turn according to the personal or department routing table of the employee applying for purchase, the examination and approval is that the leaders are different in level according to the difference of the amount of money, the higher the amount of money is, the higher the examination and approval level is, and vice versa. For example: the enterprise architecture comprises three layers of a group, a department and a company, the upper limit of the examination and approval sum of the group leader is 1000 yuan, the upper limit of the examination and approval sum of the department leader is 10000 yuan, and the examination and approval sum of the company leader is more than 10000 yuan. If the equipment to be purchased is 2000 yuan, the group leader approves the equipment, then the department leader approves the equipment, and after the department leader approves the equipment, the process of the approval cost is finished.

In addition, the approval fee process can be executed before the target purchasing client is selected, so long as the target purchasing scheme is determined.

Step S203, the OA server sends the OA end purchasing flow sheet to the target purchasing client.

Step S204, the target purchasing client sends the purchased information to the OA server; the purchased information is input by a buyer after purchasing the equipment based on the OA end purchase flow sheet.

And the target purchasing client receives the OA end purchasing flow sheet sent by the OA server, namely receives the purchasing instruction and generates an OA end purchasing order. And the purchasing personnel of the target purchasing client starts to place the electronic equipment on line according to the OA-end purchasing order. And after the purchase is finished, inputting actual price, asset information and the like into the system. A batch entry function is supported here. The specific batch entry can be realized through 2 entry interfaces. Referring to FIG. 2d and FIG. 2e, FIG. 2d is an exemplary diagram of a purchased information entry interface in the interaction flow of FIG. 2 b; FIG. 2e is an exemplary diagram of a detailed information entry interface in the interaction flow of FIG. 2 b.

First, through the interface of fig. 2d, the information in the device procurement plan (i.e., the target procurement plan corresponding to the procurement order) can be split. After splitting, detailed configuration information entry needs to be performed on each device.

Then, if the detailed configuration column for multiple devices is selected, after clicking, the interface of FIG. 2e is displayed. The purchasing personnel can add the detailed configuration information of the equipment to the detailed configuration of each equipment respectively by inputting the information once through the interface of fig. 2 e. Further facilitating the input of the purchased information of the user.

And after the purchased information is input, the target purchasing client sends the purchased information to the OA server.

Step S205, the OA server sends the purchased information to the asset management client.

Specifically, in this step, the OA server may send the purchased information to the asset management client for initiating the asset card creation process.

Step S206, the asset management client sends an asset creating request to the OA server; the asset creation request includes: the asset manager inputs first data of each target device based on the purchased information; the first data is data required for creating an asset card corresponding to each target device.

And the asset management client for initiating the asset card creation process sends an asset creation request to the OA server.

The first data is data required for creating an asset card corresponding to each target device. Specifically, when the external asset management server is an SAP server, the first data may mainly include: for a specific example, see fig. 2f, fig. 2f is an exemplary diagram of data required to generate an asset card in the interaction flow of fig. 2 b.

Step S207, the OA server generates an asset card creating request based on the asset creating request; the asset card creation request includes first data for each target device.

In step S208, the OA server sends an asset card creation request to the external asset management server.

Specifically, the OA server may call a preset asset creation interface based on the asset creation request to generate an asset card creation request to be sent to the external asset management server.

Illustratively, the created asset card is communicated through SAP standard JCO middleware, an OA process automatically calls an interface to create the asset card after being checked by an asset manager, the workload of manual creation is saved, human errors are avoided, the asset card is automatically invalidated and the number of the OA asset card is cleared once the conditions that the examination and approval are not passed or the business change process is invalidated and the like occur in the examination and approval of the subsequent process.

In step S209, the external asset management server generates a corresponding asset card for each target device based on the first data of each target device.

Here, the data of the asset card generated by the external asset management server is consistent with the information shown in fig. 2 f.

In step S210, the external asset management server transmits identification information of the asset card of each target device to the OA server.

Step S211, the OA server stores the identification information of the asset card of each target device in correspondence with the OA-side purchase flow sheet and the purchased information.

For example, when the external asset management server is an SAP server, the OA server may Call an SAP RFC (Remote Function Call) Function provided by the SAP system using a preset asset creation interface, and send the asset card creation request to the SAP server. After the SAP server creates an SAP asset card, i.e., master data, the creation results are returned to the OA server. The returned creation result includes identification information of the asset card specific to the SAP, for example, the identification information is an asset number. The purpose of this step is to enter data into the SAP server, requiring the SAP server to create a unique SAP specific asset number for each device to the OA server. The OA server associates the asset number specific to the SAP with the OA document number and other important information of the OA asset, that is, the returned identification information of each asset card is correspondingly stored with the identification of the purchase flow sheet of the OA end where the target device is located and the purchased information. Thus, more comprehensive and three-dimensional asset information can be displayed at the OA end.

In this embodiment, the identification information of the asset card of each target device is returned to the OA server, and in other embodiments, all the information such as the content and identification of the asset card may be returned to the OA server. Correspondingly, the OA server may store each returned asset card information in correspondence with the purchase flow sheet and the purchased information of the OA terminal where the target device is located.

Therefore, each OA document number, namely the mark of the OA end purchase flow sheet can correspond to a plurality of unique asset numbers of SAP, the batch generation of the asset numbers is realized, and the working efficiency and the accuracy are greatly improved.

In addition, when the external asset management server is another management server, such as an ERP management server of a friend or a golden butterfly, the OA server may call an RFC function provided by the friend or golden butterfly system to send an asset card creation request to the management server in the system.

Therefore, by applying the embodiment of the invention, the identification information of the asset card of each target device, the purchase flow sheet of the OA terminal and the purchased information are correspondingly stored in the OA server, and are uniformly managed from the OA server, so that the data management is convenient. In addition, by applying the embodiment of the invention, the external asset management server generates the corresponding asset cards for each target device respectively based on the first data of each target device, so that when the external asset management server receives a plurality of first data of a plurality of target devices, the external asset management server can generate the asset cards in batch, and the user operation is simplified.

Referring to fig. 3a, another schematic structural diagram of the device procurement management system according to the embodiment of the invention is shown:

as shown in fig. 3a, a purchase auditing client 300, an approval client 310, an OA database 320 and an external asset management database 330 are added to the equipment purchase management system shown in fig. 2a, so that more departments can perform unified management on OA services, the process is more standardized, and the data management is further facilitated.

In this embodiment, the device procurement management system may include a plurality of procurement clients, and the target procurement client 210 may be one of the plurality of procurement clients.

The OA server 100 in this embodiment is further configured to send the OA end purchase flow sheet to the purchase auditing client 300 after generating the OA end purchase flow sheet based on the equipment purchase request; a procurement auditing client 300 for sending inquiry requests to a plurality of procurement clients through the OA server 100; receiving the purchase price scheme returned by each purchase client, and determining a target purchase price scheme; and determining a target purchasing client 210 from each purchasing client; the identification of target procurement client 210 and the target procurement price plan are sent to OA server 100.

In this embodiment, the equipment procurement management system may further include at least one approval client 310 (only one stage is schematically shown in fig. 3 a).

The OA server 100 in this embodiment is further configured to send an approval request to the approval client 310 step by step based on the target purchase price scheme; each level of the approval client 310 generates an approval result based on its own approval authority, and returns the approval result to the OA server 100.

In this way, when the approval result is that the approval is passed, the OA server 100 notifies the target purchasing client 210, so that the target purchasing client 210 displays the purchasing information entry interface provided by the OA server 100, and outputs the OA-side purchasing flow sheet and the target purchasing price plan to the purchaser. Thus, after the buyer purchases according to the target purchase price scheme, the buyer enters purchased information including detailed information of the purchased equipment through the purchase information entry interface.

OA database 320 is used to store data generated or received by OA server 100, such as: the information of each asset card, the purchased information, the OA-side purchase flow sheet and the external order information are correspondingly stored in the OA database 320; the external asset management database 330 is used to store data generated or received by the external asset management server 110.

In this embodiment, in order to further facilitate data entry, default data values may also be displayed in some pre-specified data items in each displayed interface for selection by a user.

Specifically, the purchase application interface provided by the OA server 100 and displayed by the employee client 200 may include a data value of a pre-specified data item obtained by the OA server 100 from the OA database 320, and the data value is displayed at a position corresponding to the data item as a default value of the data item for selection by the employee.

The asset data entry interface provided by OA server 100 of asset management client display 120 may also include data values of pre-specified data items obtained by OA server 100 from OA database 320, which are displayed as default values of the data items at locations corresponding to the data items for selection by the asset manager.

The external purchase order information input interface provided by the OA server displayed by the target purchase client may also include a data value of a pre-specified data item obtained by the OA server from the OA database, and the data value is displayed at a position corresponding to the data item as a default value of the data item for selection by the purchaser.

In addition, since some external asset management servers 110 need to generate their own purchase orders, for this purpose, the OA server 100 may also transmit second data required by the external asset management server 110 to generate purchase orders to the external asset management server 110.

Specifically, target purchasing client 210 in this embodiment is further configured to display an external purchasing order information entry interface provided by OA server 100, receive the input purchased information from the purchaser in the external purchasing order information table corresponding to the OA-side purchasing flow sheet, and send the received purchased information to OA server 100; the external purchase order information table includes second data required for the external asset management server to generate a purchase order.

After the purchaser purchases the target device, an external purchase order information entry interface is opened on the target purchase client 210, and the purchased information is entered in the external purchase order information table therein. Thus, the information entry at the external asset management server side is not needed again.

After the information input of the external purchase order information table is completed, the OA server 100 may also call a preset order creating interface to generate an external order creating request, and send the external order creating request to the external asset management server 110; the external order creation request includes: second data to cause the external asset management server 110 to generate an external purchase order based on the second data. The OA server 100 may also receive external purchase order information returned from the external asset management server 110; and correspondingly storing the returned external order information and the OA end purchase flow sheet.

Furthermore, since some external asset management servers 110 need to complete the receiving procedure, for this purpose, the OA server 100 may also generate an external receiving instruction to send to the external asset management server 110.

Specifically, the target purchasing client 210 in this embodiment may further receive, through a purchasing bill voucher entry interface provided by the OA server 100, the related information of the purchasing voucher corresponding to the OA-side purchasing flow sheet input by the purchaser, and send the information to the OA server 100; and selects the target equipment to be received and the corresponding voucher related information thereof in the purchase flow sheet of the OA end through a receiving interface provided by the OA server 100, generates a receiving request and sends the receiving request to the OA server 100.

In this way, the OA server 100 may also call a pre-configured receiving processing interface based on the receiving request to generate an external receiving command, and send the external receiving command to the external asset management server 110; the external receiving instruction includes: and the target equipment to be received in the OA-side purchase flow sheet and the corresponding certificate related information thereof, so that the external asset management server 110 receives the target equipment to be received in the OA-side purchase flow sheet.

In this embodiment, when the external asset management server 110 is: when the SAP server is used, the preset order creating interface and the preset receiving processing interface are both: SAP RFC function interface. In this way, the OA server may call a corresponding SAP RFC function provided by the SAP system using a preset order creation interface and a preset receiving processing interface, and send an external order creation request and a receiving request to the SAP server.

In addition, the OA server 100 may also receive the data of the designated data item sent by the external asset management server 110 according to the synchronization timing duration through a preset data synchronization interface based on the web service, and store the data in the OA database 320; and/or receives the information of the added and/or modified asset cards sent by the external asset management server 110 according to the card update timing duration through a preset data synchronization interface based on the network service, and stores the information into the OA database 320. Wherein the pre-specified data items include: the external asset management server in the first data and in the second data has data items that the OA server does not have.

Correspondingly, the external asset management server 110 is further configured to obtain data of the specified data item from the external asset management database 330 according to the synchronous timing duration, and send the data to the OA server 100 through the data synchronization interface; and/or, the information of the added and/or modified asset cards is obtained from the external asset management database 330 according to the card update timing duration and is sent to the OA server 100 through the data synchronization interface.

In practice, OA database 320 and OA server 100, which may be collectively referred to as an OA system, may be implemented by a single physical machine. The external asset management database 330 and the external asset management server 110 may be referred to as an external asset management system, and if the external asset management server is an SAP server, it may be referred to as an SAP asset management system.

In one embodiment of the equipment procurement management system based on FIG. 3a, the external asset management server 110 may synchronize the data of the pre-specified data items of the external asset management database 330 into the OA database 320 by the synchronization timing length and obtain information of the added and/or modified asset cards from the external asset management database 330 into the OA database 320 by the card update timing length through the timing task.

Referring to fig. 3b, fig. 3b is an interactive flowchart of data synchronization in the device procurement management system shown in fig. 3a, which includes:

step S301, after detecting that the preset synchronization timing duration is reached, the external asset management server obtains a field value of a preset field from the external asset management database.

The field value of the preset field shown in fig. 3b is a specific example of the data of the aforementioned specified data item.

It is practicable that a timer program may be set in the external asset management server, and the external asset management server acquires a field value of a preset field previously stored in the external asset management database every synchronous timing period. For example, at 12 am each day, the field value of the preset data field is acquired. The preset field value may be all values of the preset field, or may be a value with variation in the preset items.

It may be implemented that the field value of the preset data field may be: and the data required by the external asset management server is a plurality of preset data aiming at each preset item according to the actual condition of a company. An example of a preset field value (for example, SAP server is an external asset server) may be as shown in table one:

watch 1

It can be seen that the preset field value may be a plurality of values of the preset data field, the external asset management server sends the field value of the preset data field to the OA server, and the OA server may display the field value in a pull-down menu form on each client according to a preset display page, or may directly display the field value in an interface (for example, a company code, a cost center, etc. in fig. 2 e), so as to facilitate the user to select the field value, which saves time compared with editing.

By means of the timed task, the OA database can be dynamically updated.

In step S302, the external asset management server transmits a field value of the preset data field to the OA server.

It may be implemented that the OA server provides a first interface for receiving a field value specifically updating the preset data field, for example: a webservice interface. The external asset management server transmits the field value of the preset data field to the OA server through a second interface preset by the external asset management server and communicatively connected to the first interface.

In step S303, the OA server updates the received preset field value in the OA database.

In this embodiment, the external asset management server 110 may also synchronize the information of the asset cards to be added and/or modified to the OA database by the card update timing duration through another timing task. Specifically, as shown in fig. 3 b:

step S304, after detecting that the preset card updating timing duration is reached, the external asset management server acquires the information of the asset cards which are added and/or modified within the card updating timing duration from the external asset management database.

In step S305, the external asset management server sends information of the asset card to the OA server.

The OA server preset third interface can be implemented and can be connected with the preset fourth interface of the external asset management server in a communication mode.

Specifically, the third interface and the fourth interface may be configured in advance, and are used for sending, by the external asset management server, the information of the asset card added and/or modified in the external asset management database of the external asset management server within the update timing duration to the interface of the OA server.

In step S306, the OA server stores the information of the asset card added and/or modified in the external asset management database received from the external asset management server into the OA database.

In this embodiment, before step S306, after receiving the identification information of the asset card sent from the external asset management server, the OA server compares and modifies the identification information of the local asset card. Then in step S306, the OA server is enabled to save the information of the added and/or modified asset card into the OA database.

By adopting the mode, the OA server and the external asset management server mutually synchronize the asset card, so that the data of the asset card in the two servers are consistent, and the condition that the data in the OA database is wrong due to the fact that the information of the asset card is not updated in the OA database of the OA server when the information of the asset card is modified at the external asset management server side can be prevented. In this way, synchronization of the external asset management database of the external asset management server with the data in the OA database of the OA server is achieved.

Steps S301 to S306 are realized in a timed manner, and there is no actual context with the subsequent steps.

In other embodiments, timed tasks may also be handled by OA server 100. For example: 0:00 per day, the external asset management server 110 sends a data synchronization request. The external asset management server 110 synchronizes data to the OA server 100 according to the data synchronization request.

Referring to fig. 3c, fig. 3c is an interactive flow chart of device procurement management using the device procurement management system of fig. 3a (for simplicity of the drawing, the external asset management database is not shown in fig. 3 c), including:

step S307, the employee client sends a device purchase request to the OA server; the device procurement request includes: identification information of the target device, such as the type of the target device.

In this step, the employee client may display a purchase application interface provided by the OA server, receive target purchase information input by the employee, generate an equipment purchase request, and send the equipment purchase request to the OA server, where the equipment purchase request includes: identification information of the target device obtained from the target procurement information.

In this embodiment, before displaying the purchase application interface provided by the OA server, the employee client may further send a login request to the OA server. The login request includes: an employee user identification; the OA server can also determine the employee role group to which the employee user belongs based on the employee user identification in the login request; determining the authority of the employee user according to the corresponding relation between the preset employee role group and different group authorities; or determining the authority of the employee user based on the employee user identifier in the login request and the preset corresponding relation between the employee user identifier and different authorities; and if the employee user has the purchase application authority, outputting a purchase application interface to the employee client.

The OA server determines which functions a certain employee has authority according to the pre-stored employee authority table, and displays the functions accessed by the authority to the employee through the page. The method comprises the steps that employees log in an OA server through employee clients, the OA server provides equipment purchasing processes according to account number authority of each employee, the equipment purchasing processes enter a purchasing application form in a clicking mode, the OA server creates unique identification ID numbers for the purchasing application form, and each node of the purchasing process is created according to an employee routing table. And after the employee writes the purchase application form, sending an equipment purchase request to the OA server, and after receiving the equipment purchase request, sending the purchase application form to the next node asset maintenance personnel by the OA server. An authorized employee may be: an applicant applying for purchase of a target device for use; but also a part of employees, for example: and the department assistant applies for the applicant which applies for purchasing the target equipment.

For example, if the account number of the department assistant has the authority, the authority control can be realized in two ways, namely, in one way, the account number of the assistant is put into an assistant role group, and then the assistant role group is matched with the authority capable of sending the equipment purchase request; in another mode, an employee authority table capable of sending the device purchase request can be directly maintained, and the function of sending the device purchase request is realized through the authority table corresponding to the function of sending the device purchase request. Assume employee a is a department assistant with device procurement privileges. After the employee a logs in the employee client through the account of the employee a, the interface of the equipment purchasing process can be seen, the employee without authority cannot see the equipment purchasing process in the function list, cannot initiate the equipment purchasing process, and cannot see the equipment purchasing process interface. In one embodiment, employee a may fill in the target device type on the interface of employee client, click the purchase request trigger button, generate a device purchase request, and send the device purchase request to the OA server.

In another specific embodiment, after the employee a clicks a trigger button of the device procurement process of the interface of the device procurement process, a form of the device procurement process appears for the employee a to fill, and the OA server may generate an OA document number for the form according to a preset rule, where the document number is a unique number in the OA management system and is used to identify data of the order in the whole process. The employee can fill in simple information on the form, such as: filling out the user of the equipment; in this case, the OA server may send the pre-stored attribute information of the organization structure, the superior-inferior relationship, the cost center, the business unit, and the like to the employee client logged in by the employee a account to be displayed and automatically filled in the form. Therefore, the time for filling the employee A again is saved, and the situation that the employee A cannot continuously handle due to the fact that the process is wrong after filling the employee A is wrong is also prevented. The attribute information of the equipment user which is stored in advance is the attribute information of each employee and can be identified by an employee number.

The purchase application form may display a filling box with information on the type, location, expected arrival date and application description of the target device, and employee a may fill in information on the location, expected arrival date and application description, and the type of the target device, for example: the target device type is filled in the target device filling interface of the employee client shown in fig. 2 c. The information filled by employee a is relatively conventional and understandable, and can be successfully filled without training basically, unlike the form filled by the asset manager, which is a rule matching the rules of the external asset management database, and ordinary employees do not have filling ability without learning the rules. The IDC equipment type drop-down list is the self-defined equipment type of the OA management system, different from the equipment type of the external asset management system, the OA equipment type is easier to be filled by common staff, the content filled by an asset manager is a professional field which is more in line with the external asset management rule, and the staff does not need to know.

And providing a trigger button in the purchase application form, clicking the interface equipment purchase request trigger button after the employee finishes filling, and sending an equipment purchase request to the OA server by the employee client, wherein the equipment purchase request comprises the purchase application form.

Step S308, the OA server generates an OA end purchase flow sheet based on the equipment purchase request.

In this embodiment, the device procurement request further includes: and applying for employee user identification of the purchased employee user.

In this embodiment, before generating the OA-side purchase flow sheet, the OA server may send the device purchase request to the asset management client; the asset management client can judge whether to execute a purchasing process based on the employee user identification, the target equipment type and the inventory condition in the equipment purchasing request; and returning the judgment result to the OA server so that the OA server generates an OA end purchasing flow sheet based on the equipment purchasing request when the judgment result of the purchasing flow execution is that the purchasing flow can be executed.

In the second specific implementation manner in step S307, the OA document number may be used as the number of the OA end purchase flow sheet, and the OA server generates the OA end purchase flow sheet based on the data in the form.

Step S309, the OA server sends the OA end purchase flow sheet to the asset management client.

Specifically, when the asset manager views the OA-side procurement process sheet which needs to be processed by the asset manager, the OA server sends the OA-side procurement process sheet to one or more asset management clients.

Step S310, the asset management client sends a purchase determining instruction to the OA server; the procurement determination instruction is issued by an asset manager when determining that no target device is in inventory.

After the asset management client receives the OA end purchase flow sheet, an asset manager can check whether the equipment exists under the name of the employee A or not, and inquire whether the equipment matched with the target equipment exists in the inventory or not online or offline, and if so, the target equipment in the inventory is called for the employee to use. Therefore, the existing target equipment in the warehouse can be effectively utilized for employees, and the cost is saved for companies. The asset manager selects the transposable device on the interface and clicks the confirmation button, and the flow node is returned to the employee. If the inventory has no transferable equipment, the process is transmitted to the next node, and the process is filed to end.

If the target equipment is not in the inventory, the purchase can be carried out, the asset management client sends a confirmed purchase instruction to the OA server, and the process is agreed to the next purchase responsible person node to handle the purchase.

In step S311, the OA server sends the OA-side purchase flow sheet to the purchase auditing client.

The purchase auditing client can be a purchase client used by a preset purchase responsible person.

Step S312, the purchase auditing client sends a purchase price request based on the OA end purchase flow sheet to the OA server.

And after receiving the OA end purchase flow sheet, the purchase auditing client waits for confirmation of the purchase responsible person, and the purchase responsible person selects a plurality of purchase personnel on an interface and sends a purchase price request based on the OA end purchase flow sheet to the OA server. The purchase price request may be an inquiry request. It can be implemented that the purchase price request includes information in a plurality of purchase client identifications and OA end purchase flow sheet, such as: target device type, etc.

In step S313, the OA server distributes the purchase price request to each purchase client.

And the OA server distributes the purchase price request to each purchase client to wait for each purchase client to inquire price. The entered price inquiring flow sheet comprises the following steps: equipment model, buyer, time of purchase, price, offer, place of origin, sales channel (online, offline), inquirer's advice, supplementary accessories, etc.

Thus, the purchase price request is sent to a plurality of purchase clients, a plurality of buyers can report a plurality of alternative purchase price schemes, and the purchase responsible person can prefer the best purchase scheme. The purchase responsible person can select a scheme after receiving the inquiry flow list returned by one or more purchase specialists, and meanwhile, the system can automatically inform the selected purchase specialists that the scheme is selected, all other inquiry sub-flows are automatically ended, the schemes of other persons are not selected, and the system does not need to quote again or wait for the scheme selection result, so that the efficiency is saved, and the inquiry process is ended aiming at the flow.

In step S314, each purchasing client sends a purchasing price plan to the OA server.

The applicable purchase price scheme can include: equipment model, buyer, time of purchase, price, preferential condition, place of production, sales channel, accessories suggested and supplemented by the price inquirer, etc.

In step S315, the OA server sends each purchase price plan to the purchase auditing client.

Step S316, the purchase auditing client sends an approval request to the OA server; the examination and approval request comprises a target purchase price scheme determined based on each purchase price scheme returned by each purchase client.

After the purchase responsible person of the purchase auditing client sees the purchase price proposal returned by one or more buyers, one or more proposals can be selected from the proposal.

Before the step, the purchase auditing client can firstly send an instruction for confirming the target purchase price scheme to the OA server, the OA server sends the selected message to the purchase client with the selected scheme, the flow of other purchase price schemes is finished, other purchase clients do not need to quote again or wait for the selection result of the purchase price scheme, the time is saved, and the efficiency is improved.

Then, the purchase auditing client sends an approval request to the OA server.

And step S317, the OA server sends the approval requests of the purchase approval clients to the approval clients according to the preset approval path.

The examination and approval path corresponding to the pre-stored amount can be determined according to the purchase amount.

Step S318, each approval client sends the approval result to the OA server.

Step S319, the OA server sends the approval result to the purchase auditing client.

And step S320, purchasing the checking client, and sending the target purchasing client identification and one or more target purchasing price schemes to the OA server when the checking result returned by each checking and approving client passes.

In an implementation manner, after the auditing client receives the approval result, the target purchasing client identifier for executing the purchasing may be determined, and of course, the target purchasing client identifier may also be determined by the purchasing auditing client in the step before this step.

In step S321, the OA server records the target purchasing client identifier and the target purchasing price plan in the OA purchasing flow sheet.

Step S322, the OA server sends the OA end purchasing flow sheet to the target purchasing client based on the target purchasing client identifier.

Step S323, the target purchasing client sends the purchased information to an OA server; the purchased information is: and after purchasing the equipment based on the purchase flow list of the OA terminal at the purchasing client, the purchaser selects the determined information and/or the edited information from the list of the preset field values to generate.

As an implementation, the preset field value may refer to the preset field value described in step S301.

In practice, the purchased information may further include: actual price and device number, etc.

In a specific embodiment, when a plurality of target devices are included, at the target purchasing client, after the purchaser purchases the devices based on the OA-side purchasing process in a single line, the purchaser may input the purchased information of the first target device, and when the purchased information of the plurality of target devices is the same as the purchased information of the first target device, the purchaser may use a configuration copy function on a display interface of the target purchasing client, and the target purchasing client modifies the purchased information of the plurality of target devices into the purchased information of the first target device. The batch recording mode saves time.

In step S324, the OA server sends the purchased information to the asset management client.

Step S325, the asset management client sends an asset creating request to the OA server; the asset creation request comprises: first data for each target device; the first data is: and the asset manager selects data which is formed by the determined information and/or the edited information and is required for creating the asset card corresponding to each target device from the list of the preset field values on the basis of the purchased information at the asset management client.

In a specific implementation manner, after receiving purchased information, an asset management client receives data required by an asset manager based on an asset card corresponding to a target device input by the purchased information, and detects whether an operation instruction for configuration copying of a preset first subdata item in first data is received, if so, the data of the preset first subdata item in the first data required for creating each asset card corresponding to each asset is modified into first subdata, receives second subdata input by the asset manager, and takes the second subdata and the first subdata as the first data; the second subdata is data which is required for creating a plurality of asset cards corresponding to a plurality of assets and is removed from the first subdata.

By adopting the mode, the batch input of the data can be realized, and the input efficiency is improved.

Step S326, the OA server verifies whether the first data of each target device meets a preset first data verification condition; if yes, generating an asset card creating request based on the asset creating request; the asset card creation request includes first data for each target device.

The first data verification condition may be implemented to verify whether all necessary items in data required when the external asset management server creates the asset card corresponding to each target device have entered data.

Because the data and the data format required by the external asset management server for creating the asset card are already set, the preliminary verification of the necessary item can be firstly carried out, thus the calling of the interface can be reduced, and the resource is saved.

In step S327, the OA server transmits an asset card creation request to the external asset management server.

The OA server may be communicatively coupled to the OA server via a fifth interface.

Specifically, the fifth interface and the sixth interface may be pre-configured interfaces for the OA server to perform request or data transmission with the external asset management server in the process of creating the asset card by the external asset management server.

In this step, the fifth interface and the sixth interface may be used.

In step S328, the external asset management server generates a corresponding asset card for each target device based on the first data of each target device.

In an implementation manner, after receiving the asset card creation request, the external asset management server may also perform a second verification first, for example, it may be verified whether the first data of each target device in the asset card creation request meets a preset second data verification condition; if yes, the external asset management server generates corresponding asset cards for each target device respectively based on the first data of each target device.

The second data verification condition may be to verify whether the first data conforms to a preset data format of a preset external asset management server. For example, the preset data format specifies: the first field is a field value of field a, the second field must be a field value of field B, and if the second field is a field value of field C, it is not compliant with the preset data format.

In step S329, the external asset management server transmits the identification information of the asset card of each target device to the OA server.

In this step, the identification information of the asset card of each target device may be transmitted using the fifth interface and the sixth interface. Information in the asset card includes, but is not limited to, company code, cost center, asset classification, and master data evaluation group, among others.

And after the external asset management server respectively generates the corresponding asset cards for each target device successfully, the external asset management server sends the identification information of the asset cards of each target device to the OA server. If the generation of the asset cards of part of the target devices fails, the identification information of the successfully generated asset cards and the information of the target devices with failed generation are sent to the OA server, which can be implemented and also can send the reasons of the failure.

It is practicable that if the external asset management device is an SAP server, the identification information of the asset card may be an asset number specific to the SAP, so that the OA server may obtain more comprehensive data for unified management.

Step S330, the OA server correspondingly stores the identification information of the asset card of each target device, the OA-side purchase flow sheet and the purchased information into the OA database.

Step S331, the target purchasing client sends an external order generation request to the OA server; the external order generation request comprises second data input by a buyer based on the identification information of the asset card and the purchased information; the second data is data required to create an external purchase order.

The second data may specifically be: and the buyer selects data which is formed by the determined information and/or the edited information and is required for creating the external purchase order from the list of the preset field values at the target purchase client.

As may be implemented, the identification information of the asset card may include an asset number of an external asset management system.

As an implementation, the second data may include: the supplier, company code, purchase group, payment condition, unit price, currency and delivery date, etc. may be preset field values updated from the OA database, and the part of the second data may be displayed in the form of a pull-down menu at the target purchasing client for the agent to select the required target value. Of course, the second data may also include some fields that need to be edited by the purchaser, such as the factory model of the device.

In step S332, the OA server generates a purchase order creating request based on the purchase external order generating request, where the purchase order generating request includes the second data.

In step S333, the OA server transmits an external order creation request to the external asset management server.

The seventh interface of the OA server may be communicatively coupled to an eighth interface of an external asset management server.

Specifically, the seventh interface and the eighth interface may be interfaces configured in advance for the OA server to perform request or data transmission with the external asset management server in the process of creating the purchase order by the external asset management server.

In this step, the seventh interface and the eighth interface may be used.

In step S334, the external asset management server generates a corresponding external purchase order based on the second data.

The external asset management server may or may not succeed in generating the corresponding external purchase order based on the second data. For example: if the second data filled out does not conform to the specifications and/or logic of the external asset management server, the order generation may fail.

If successful, go to step S335; if the failure occurs, the reason for the failure may be sent to the OA server to generate the corresponding external purchase order again after the correction.

In step S335, the external asset management server sends the external purchase order information to the OA server.

In this step, the external purchase order information may be transmitted using the seventh interface and the eighth interface.

Step S336, the OA server correspondingly stores the external purchase order information, the identification information of the asset card of each target device, the OA-side purchase flow sheet, and the purchased information into the OA database.

Therefore, more comprehensive data are stored in the OA database, unified management is achieved, display is conducted according to user requirements, management is convenient, and user experience is high.

Step S337, the target purchasing client sends a receiving request to the OA server; the receiving request includes identification information of an asset card of the asset to be received in the external asset management server or SAP purchase order information.

The receiving request is generated after the target purchasing client receives a triggering instruction sent by a purchasing person. For example: the buyer clicks the receiving button displayed on the target purchasing client to generate the result.

Step S338, the OA server generates an external goods receiving instruction based on the goods receiving request; the shipping instructions include identification information for the asset card of the asset to be shipped or purchase order information.

In step S339, the OA server transmits the external receiving instruction to the external asset management server.

The OA server may be communicatively coupled to the OA server via a ninth interface.

Specifically, the ninth interface and the tenth interface may be interfaces configured in advance, and used for the OA server to perform instruction or data transmission with the external asset management server in the process of receiving the goods by the external asset management server.

In this step, the ninth interface and the tenth interface may be used.

Step S340, the external asset management server marks the asset corresponding to the identification information of the asset card or the external purchase order information as a receiving state based on the external receiving instruction.

The external receiving instruction may further include a target voucher date and a target posting date of the external purchase order, where the information is information carried in a receiving request sent by the target purchase client. Thus, the step may specifically be: and the external asset management server receives the assets corresponding to the identification information of the asset card or the external purchase order information respectively according to the target voucher date and the target posting date based on the external receiving instruction. The buyer selects the voucher and the posting date at the node, the default of the non-filling is the day, and then the one-key transaction automatically triggers the external asset management server to receive the goods in batches through the OA.

In the prior art, if a purchase order includes a plurality of assets, a buyer needs to sequentially confirm each asset on an interface provided by an external asset management server, and the buyer needs to trigger a receiving confirmation button for each asset. By applying the embodiment of the invention, the buyer can trigger the target purchasing client to send the external purchasing order information to the OA server by one key, the OA server sends the external purchasing order information to the external asset management server in batches and realizes one-by-one confirmation, and finally, the external asset management server receives each asset in the external purchasing order information at the external asset management server, so that the working time of the buyer is saved.

In step S341, the external asset management server transmits the receipt information to the OA server.

As may be implemented, the receipt information includes, but is not limited to, a receipt voucher number.

In this step, the SAP purchase order information may be transmitted through the ninth interface and the tenth interface.

In step S342, the OA server stores the receiving information returned by the external asset management server, and the external purchase order information, the identification information of the asset card of each target device, the OA-side purchase flow sheet, and the purchased information in the OA database in a corresponding manner.

Therefore, the OA server correspondingly stores the receiving information, the external purchase order information, the identification information of the asset card of each target device, the OA end purchase flow sheet and the purchased information, and the data are richer.

By applying the embodiment of the invention, the OA server does not need to accord with the preset rule, thereby being more convenient for the user to operate.

The data stored in the OA server can also store other data sent by each client and approval traces besides the data required by the external asset management server, and the data is rich and more convenient to manage.

Moreover, in this embodiment, the external asset management server generates a corresponding asset card for each target device based on the first data of each target device, so that when the external asset management server receives a plurality of first data of a plurality of target devices, the external asset management server may generate asset cards in batches; and the external asset management server receives the assets corresponding to the identification information or purchase order information of the asset card respectively based on the receiving instruction, so that batch receiving is realized, and user operation is simplified.

In this embodiment, the data required for generating the asset card or creating the external purchase order by the external asset management server may be verified in the OA server and the external asset management server, so as to reduce the interface call and save the resources and time.

It may be implemented that the OA server in the above embodiment may be an OA server cluster, and the external asset management server in the above embodiment may be an external asset management server cluster.

The OA server can also receive an asset query request; the asset query request comprises a query condition; and reading at least one of identification information, purchased information or purchase order information of the asset card meeting the query conditions from the OA database according to the query conditions in the asset query request, and outputting the information. Therefore, after the OA server manages data in a unified manner, the user can inquire the data from the OA server, and the user experience is further improved.

After the process, the employee client fills in the actual equipment leader and sends a continuous processing request to the OA server, wherein the continuous processing request may include the identifier in the purchase process list of the OA terminal and/or the external purchase order information and/or the identifier information of the asset card; and the OA server sends a request for continuous transaction to the archiving client to be archived by the employee to be archived.

After the overview process of the archiving employee of the archiving client is correct, the archiving client sends an archiving request to the OA server, and the OA server carries out archiving and correspondingly stores the archiving information into an OA database of the OA server.

After the archiving is processed, all processes can be inquired in the database of the OA server subsequently, and the data management and inquiry are greatly facilitated.

In the above steps, when the interface of the OA server communicates with the interface of the external asset management server, the RFC function of the external asset management server may be invoked to implement, where the RFC function is a bidirectional interface technology and may implement synchronous communication and asynchronous communication. The preferred communication method may use synchronous communication, so that data can be transmitted in a timely manner. Of course, the use of asynchronous communication is also possible.

Next, a detailed description will be given of a specific application example of the device procurement management system.

Referring to fig. 4, fig. 4 is a schematic view of an application example of the device procurement management system according to the embodiment of the invention.

As shown in FIG. 4, the equipment procurement management system comprises an OA system and an SAP asset management system.

Wherein, in the OA system, an OA database and an OA server are integrated; the SAP asset management system integrates an SAP database and an SAP server.

The main steps of asset management include:

and step 11, filling the detailed information of the equipment in the OA system, wherein the required fields of the assets comprise company codes, cost centers and the like.

The specific asset required fields comprise preset data fields such as company codes and cost centers besides detailed information of the equipment, and the field values of the preset data fields are taken out from the OA database and do not need to be filled by a user independently.

And step 12, the OA system interface calls an SAP RFC function to create SAP asset main data.

Specifically, in this step, the OA system may call the SAP RFC function through the interface, so that the SAP system creates the asset card.

In practical applications, the device to be purchased may be an asset device as a fixed asset of an enterprise, such as a notebook computer or a copy, or may not be a non-asset device of the fixed asset, for example: consumables, and the like. The purchase order sub-tables need to be filled out separately. If the equipment is the asset equipment, executing the step 13a and the step 14 a; if it is a non-asset class device, step 13b and step 14b are performed. The method comprises the following specific steps:

step 13a, in the OA system, filling in the mandatory fields and the asset purchase orders, such as supplier codes, factories, SAP asset numbers, net prices, etc., according to the SAP asset purchase order sublist.

Step 14a, the OA system interface calls the SAP RFC function, causing the SAP asset management system to create an asset purchase order.

Step 13b, in the OA system, filling in the mandatory fields and the asset purchase orders, such as supplier codes, factories, SAP asset numbers, net prices, etc., according to the SAP non-asset purchase order sublist.

Step 14b, the OA system interface calls the SAP RFC function, causing the SAP asset management system to create a non-asset purchase order.

For example: the above order may fill in the required fields through the interfaces shown in fig. 2 b-2 f.

After purchasing the equipment according to the purchase order, the purchasing personnel executes the following steps:

step 15, at the OA system, SAP asset and non-asset purchase order filling is performed, comprising: and the voucher date and the posting date are used for receiving the goods.

Step 16, the OA system calls the SAP RFC function to receive successful asset and non-asset purchase orders.

And step 17, the OA system opens a webservice interface, and the SAP synchronizes basic data to the OA system every day through the interface and the timing task.

The specific basic data, as shown in fig. 4, includes: company code, cost center identification, internal orders (i.e., SAP asset management system orders, which are external orders to an OA server from the OA server perspective), SAP asset classification information, SAP evaluation value identification, supplier number, purchasing organization or group identification, payment condition or currency type or code, measurement unit and group identification, and material number, among others. The data field of these data can be used as the preset data field.

Among them, the SAP RFC function called by the OA system is an important and common bidirectional interface technology between the SAP system and other (SAP or non-SAP) systems, and is also considered as a basic protocol for the SAP to communicate with the outside. In short, the RFC function call procedure is a procedure module that the system calls outside the current system to realize a certain function, and at least one of the calling system and the called system must be the SAP ABAP system. RFC data communication can be broadly divided into two basic modes: synchronous communication and asynchronous communication.

Referring to fig. 5a, the communication is synchronized: synchronous communication in SAP is a one-time function call, provided that when a remote function is called (or a request is sent), the receiving system (server) must be active, can accept the request and proceed with further processing. The sending system (in the embodiment of the present invention, it may refer to an OA server) sends a call request to perform a function call and waits for a response; the receiving system (which may be alternatively referred to as an external asset management server in the embodiments of the present invention) immediately processes the function call request and calculates a response sending system. The synchronous calling has the advantages that the data can be immediately returned to the sending system; the disadvantage is that it must be ensured that both systems are active during a system session, otherwise the session will be interrupted seriously, which affects the processing procedure of the service application. Preferably, the embodiment uses synchronous communication, and has stronger timely response capability compared with asynchronous communication.

Referring to fig. 5b, asynchronous communication: asynchronous communication in SAP is characterized by the fact that the receiving system does not need to be active at the time of the remote function call, and the system can delay receiving and processing the call. If the receiving system is not available, the transmitted request will be saved in the output queue of the transmitting system and call attempts will be repeated at intervals until the receiving system responds to the call. The asynchronous communication has the advantages that the receiving system is not required to be available at any time, and the service processing of the request sending system is not influenced by the conditions such as system maintenance, upgrading and the like; but this mode is not suitable for processes requiring immediate response. For example, the transmitting system OA server sends a request to establish a purchase order to the external receiving system SAP external asset management server, and if the SAP system is temporarily unavailable, the order is temporarily placed in the request queue of the transmitting system and retransmitted at intervals until the SAP system receives the information and reacts. This process may be done in the form of a background operation.

The embodiment of the present invention further provides an OA server, as shown in fig. 6, which includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, wherein the processor 601, the communication interface 602, and the memory 603 complete communication with each other through the communication bus 604.

A memory 603 for storing a computer program;

the processor 601 is configured to implement the following steps when executing the program stored in the memory 603:

the purchased information is obtained and sent to an asset management client, so that the asset management client displays an asset data entry interface provided by an OA server, receives first data of each purchased target device input by an asset manager based on the purchased information, and sends an asset creation request to the OA server, wherein the asset creation request comprises: first data for each purchased target device; the first data is: the external asset management server creates first data required by an asset card corresponding to each purchased target device; purchased information, including: device details of the purchased target device;

receiving the asset creation request;

Therefore, by applying the embodiment of the invention, the asset card information of each target device and the purchased information are correspondingly stored in the OA server, so that unified input and management from the OA server are realized, and convenience is brought to data management.

In addition, by applying the embodiment of the invention, the external asset management server generates the corresponding asset cards for each target device respectively based on the first data of each target device, so that when the external asset management server receives a plurality of first data of a plurality of target devices, the external asset management server can generate the asset cards in batch, and the user operation is simplified.

According to the solution of the embodiment of the invention, enterprises can provide a set of personal electronic equipment purchasing process system to replace the former process of applying for purchasing equipment by paper or mails. The electronic application flow of the invention ensures that the asset management is more standard, improves the office efficiency of a plurality of post workers such as an asset manager, facilitates the inquiry and retrieval of asset data, and has convenient and fast data archiving operation and low possibility of errors. Through the purchasing process system of the personal electronic equipment, the asset data stored by an external asset management server (such as an ERP system) and an OA system can be organically unified together, information intercommunication is realized, and more timely, accurate and comprehensive data processing capability is provided for enterprises.

In an embodiment of the present invention, the OA management system is interfaced with the SAP management system. An enterprise usually uses an ERP system to manage assets and financial data of the company, and also uses an OA management system independent of the ERP system to manage work and office processes and data of the company, and the two systems often need to exchange data and have consistent data with each other. Sometimes, multiple sets of ERP systems and/or multiple sets of internal OA management systems are used by an enterprise, for example, multiple sets of ERP systems are purchased by a multinational company and a group company, and different internal OA management systems exist in each family company. Common internal OA management systems include a jin shan KOA management system, a sales management system, and a NOC system (Network Operation Center). Common ERP systems are Utility friend, butterfly, SAP, etc. Each ERP system has its own system architecture and data storage rules, and the number, type, abbreviation and code of the data are different. The OA management system in a company needs to construct its own data architecture, management and transmission mode according to the rule of the ERP system to realize data exchange between the two systems. The asset management system of SAP, which is one of ERP systems, is expected to be applicable to various types and different-scale enterprises, so that the asset management system is very large and complex, has a plurality of parameters and a plurality of values, is suitable for professional managers, but is not friendly to the operation of ordinary staff. The SAP asset manager needs professional training to work up to adapt to the set of asset management system, because the SAP asset manager needs numerical data rules, manually completes data filling, and inputs the management data (such as equipment information) from the interior of the enterprise into the SAP system to facilitate the collection and management of the SAP. The SAP system is not suitable for operation of ordinary employees, ordinary employees cannot correspond the ordinary types of electronic devices to the types and parameters in the asset management system, the operation modes of various interfaces cannot be understood immediately, and the entry rules peculiar to the SAP system are unknown, so that if an enterprise requires each ordinary employee who initiates purchase needs to enter data by entering the device information to be bought into the SAP, the entered data is wrong, and the data cannot be managed correctly when data management is performed later. Compared with common staff, equipment maintenance personnel and purchasing personnel, the entry work is completed by a trained SAP asset manager more suitably. In the prior art, an SAP asset manager needs to collect asset information purchased by employees through mails, oral notes, paper application forms or an OA management system at ordinary times and then input the asset information into an SAP system one by one, so that a lot of time is spent, and more data are still prone to errors. Because the SAP system is developed by other companies and is universally suitable for all users around the world, in order to improve the working efficiency of SAP asset managers, the rules of the SAP system can be adapted by developing the own OA management system of the company without modifying the SAP system, and the work of the asset managers can be simplified. Especially large enterprises, when a plurality of external systems and the OA management system are used for cooperative work, the OA system can more effectively liberate manpower by using the specific solution of the invention.

In the OA management system according to the embodiment of the present invention, a transaction flow is created, and a plurality of transaction nodes are set in the transaction flow. Each common staff can initiate a purchasing process, the next node is a purchasing responsible person after confirmation, the purchasing responsible person sends a sub-process to the asset maintenance personnel to ask the asset maintenance personnel to check whether the existing equipment can be transferred for use, after the confirmation of the asset maintenance personnel is obtained, the purchasing responsible person initiates the sub-process to a plurality of purchasing personnel to create the sub-node of each purchasing personnel, after one purchasing personnel completes the sub-node, the sub-node is transmitted back to the purchasing responsible person, the purchasing responsible person can initiate the purchasing process to each purchasing personnel again, after the purchasing personnel completes the purchasing, the purchasing responsible person is informed, the purchasing responsible person forwards the confirmation to the asset management personnel, the asset management personnel sends the received data to the SAP system after the confirmation, and the whole process is finished.

The OA management system provides a window initiated by a purchasing process for each common employee through an employee client, creates a unique ID number for the purchasing process, and creates a process node according to an organization structure table of the employee. The general staff can fill information such as the model, the quantity, the specification and the like of the electronic equipment which can be understood by the general staff in a purchase list provided by a window, the general staff initiates a purchase request of the electronic equipment after clicking confirmation, wherein the time for creating the flow node by the OA management system can be created after clicking confirmation by the staff at the latest. And the OA management system receives the purchase request confirmed by the employee and sends the purchase request to the next processing node, namely the purchase responsible person. The purchase responsible person possesses one or more purchase personnel, the OA management system provides purchase sub-processes for the purchase personnel respectively, the price quoted by the purchase personnel is quoted and fed back to the purchase responsible person, and the purchase responsible person designates one or more purchase personnel to be responsible for purchasing products offline, so that a back-to-back price quoted and purchased management mode is realized, and the purchase work is fairer and more reasonable. And the asset manager sends a request for creating the asset card to the SAP system after receiving the acquired equipment information. The asset information which accords with the SAP rule can be input into the SAP system in batches, and the problem of manual input is solved. After receiving the flow of the purchasing responsible person, the purchasing personnel inputs the order information required by the SAP, the system automatically associates the asset information input by the asset manager with the order information, sends an instruction to the SAP system to automatically create an SAP purchasing order and approve the SAP purchasing order. And the asset manager inputs the receiving date and continues the handling process through the OA system interface, sends an instruction to the SAP system to automatically receive the SAP purchase order, and automatically generates a material certificate and a accountability certificate in the SAP system. The OA management system is provided with a timed task function, and solves the problem of information asymmetry of an OA system and an SAP system in a timed task mode, so that data of the SAP and the OA system can be kept consistent.

The asset management staff is responsible for maintaining electronic equipment such as desktop computers, notebook computers and displays, managing the electronic equipment, establishing and maintaining an electronic equipment list, and recording operations such as warehousing, old calling, ex-warehouse and calling into the list. The purchasing responsible person decides which product to purchase, a plurality of buyers who inquire price outside exist in the purchasing group, and each buyer has an own account number and maintains own inquiry sub-flow respectively. Once the purchasing responsible person decides which product to buy, the system can automatically inform the selected inquiring person that the purchasing scheme of the selected inquiring person is selected, the sub-flow of the purchasing scheme which is not selected by other purchasing persons can be automatically filed, and in addition, the purchasing responsible person can also appoint any purchasing person to purchase the product, so that the product is not limited to the purchasing person who inquires the price at that time. The flow actions can effectively avoid the purchasing risk.

The equipment purchasing system provided by the invention has a convenient asset manager maintenance asset interface and a plurality of sub-processes, such as purchasing process of purchasing personnel, shelving and shelving process of asset maintenance personnel and receiving process of asset manager.

The embodiment of the present invention further provides an external asset management server, as shown in fig. 7, including a processor 701, a communication interface 702, a memory 703 and a communication bus 704, where the processor 701, the communication interface 702, and the memory 703 complete mutual communication through the communication bus 704.

A memory 703 for storing a computer program;

the processor 701 is configured to implement the following steps when executing the program stored in the memory 703:

receiving an asset card creation request generated and sent by an OA server by calling a preset asset creation interface; the asset card creation request includes: first data for each purchased target device; the first data is: the OA server is received through the asset management client and is input by an asset manager based on the purchased information; the purchased information is: the OA server receives the information through the target purchasing client and is input by a purchaser based on a purchasing flow sheet of the OA terminal;

and returning the asset card information corresponding to each purchased target device to the OA server, so that the OA server correspondingly stores each returned asset card information and the purchased information.

Therefore, by applying the embodiment of the invention, the purchased information of the identification information of the asset card of each target device is correspondingly stored in the OA server, and is uniformly managed from the OA server, so that the data management is convenient.

The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

It is possible to implement, the OA server and the external asset management server are electronic devices.

The communication interface is used for communication between the electronic equipment and other equipment.

The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In yet another embodiment of the present invention, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of any of the above-mentioned device procurement management methods.

In yet another embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the above-described method of device procurement management.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, or device that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, apparatus, or device. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, apparatus or device that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for embodiments such as the system, the server, the computer-readable storage medium, and the computer program product, since they are substantially similar to the method embodiments, the description is simple, and for relevant points, reference may be made to part of the description of the method embodiments.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.

Claims

1. An equipment procurement management system characterized by, the system comprising: the OA server and various clients in communication connection with the OA server, and an external asset management server; the OA server is in communication connection with the external asset management server; the plurality of clients include: an asset management client;

2. The device procurement management system of claim 1 characterized by, in the various clients, further comprising: an employee client and a target purchasing client;

the employee client is configured to display a purchase application interface provided by the OA server, receive target purchase information input by an employee, generate an equipment purchase request, and send the equipment purchase request to the OA server, where the equipment purchase request includes: identification information of the target equipment obtained from the target purchase information;

the OA server is further used for generating an OA end purchasing flow sheet based on the equipment purchasing request; wherein, in the OA end purchase flow sheet, include: identification information of the target device;

the target purchasing client is used for displaying a purchasing information input interface provided by the OA server and obtaining the OA end purchasing flow sheet from the OA server and outputting the OA end purchasing flow sheet to a purchaser; receiving the purchased information input by the buyer based on the OA end purchasing flow sheet, and feeding back the purchased information to the OA server;

the OA server is further used for receiving the purchased information and sending the purchased information to an asset management client so that the asset management client can obtain the purchased information; and correspondingly storing the purchase flow sheet of the OA terminal and the returned information of each asset card and the purchased information.

3. The system of claim 2,

the target purchasing client is further used for displaying an external purchasing order information input interface provided by the OA server, receiving the input purchased information in an external purchasing order information table corresponding to the OA terminal purchasing flow sheet by a purchaser, and sending the input purchased information to the OA server; the external purchase order information table comprises second data required by the external asset management server for generating the purchase order;

the OA server is also used for calling a preset order creating interface to generate an external order creating request and sending the external order creating request to the external asset management server; the external order creation request comprises: the second data to cause the external asset management server to generate an external purchase order based on the second data; receiving external purchase order information returned by the external asset management server; and correspondingly storing the returned external order information and the OA end purchase flow order.

4. The system of claim 3,

the target purchasing client is further used for receiving the related information of the purchasing voucher corresponding to the OA end purchasing flow sheet input by a purchaser through a purchasing bill voucher input interface provided by the OA server and sending the information to the OA server; selecting target equipment to be received in the purchase flow sheet of the OA end and corresponding certificate related information thereof through a receiving interface provided by the OA server, generating a receiving request and sending the receiving request to the OA server;

the OA server is also used for calling a preset receiving processing interface based on the receiving request so as to generate an external receiving instruction and send the external receiving instruction to the external asset management server; the external receiving instruction includes: and the target equipment to be received in the OA end purchase flow sheet and the corresponding certificate related information thereof, so that the external asset management server receives the target equipment to be received in the OA end purchase flow sheet.

5. The system of claim 4,

the external asset management server is: an SAP server;

the preset asset creating interface, the preset order creating interface and the preset receiving processing interface are all as follows: SAP RFC function interface.

6. The system of claim 3,

the system further comprises: an OA database and an external asset management database; the information of each asset card, the purchased information, the OA end purchasing flow sheet and the external order information are correspondingly stored in an OA database;

the OA server is also used for receiving the data of the designated data item sent by the external asset management server according to the synchronous timing duration through a preset data synchronization interface based on network service and storing the data into the OA database; and/or, receiving information of the added and/or modified asset cards sent by an external asset management server according to the card updating timing duration through a preset data synchronization interface based on network service, and storing the information into an OA database; wherein the pre-specified data items include: data items that the external asset management server in the first data and in the second data has, but the OA server itself does not have;

the external asset management server is also used for acquiring data of specified data items from the external asset management database according to the synchronous timing duration and sending the data to the OA server through the data synchronous interface; and/or acquiring the information of the added and/or modified asset cards from the external asset management database according to the card update timing duration, and sending the information to the OA server through the data synchronization interface.

7. The system of claim 6,

the purchase application interface provided by the OA server displayed by the employee client comprises a data value of the pre-specified data item acquired by the OA server from the OA database, and the data value is displayed at a position corresponding to the data item as a default value of the data item for selection of the employee;

the asset data entry interface provided by the OA server and displayed by the asset management client comprises the data value of the pre-specified data item acquired by the OA server from the OA database, and the data value is displayed at the position corresponding to the data item as the default value of the data item for the selection of an asset manager;

the external purchase order information input interface provided by the OA server and displayed by the target purchase client comprises the data value of the pre-specified data item acquired by the OA server from the OA database, and the data value is displayed at the position corresponding to the data item as the default value of the data item for selection of a purchaser.

8. The system of claim 2,

the employee client is further configured to send a login request to the OA server before displaying a purchase application interface provided by the OA server, where the login request includes: an employee user identification;

the OA server is further used for determining the employee role group to which the employee user belongs based on the employee user identification in the login request; determining the authority of the employee user according to the corresponding relation between the preset employee role group and different group authorities; or determining the authority of the employee user based on the employee user identifier in the login request and the corresponding relation between the preset employee user identifier and different authorities; and if the employee user has the purchase application authority, outputting a purchase application interface to the employee client.

9. The system of claim 2,

the device procurement request further comprises: applying for employee user identification of purchased employee users;

the OA server is further used for sending the equipment purchase request to the asset management client before generating an OA end purchase flow sheet based on the equipment purchase request;

the asset management client is also used for judging whether to execute a purchasing process based on the employee user identification, the target equipment type and the inventory condition in the equipment purchasing request; and returning the judgment result to the OA server so that the OA server generates an OA end purchasing flow sheet based on the equipment purchasing request after receiving the judgment result of executing the purchasing flow.

10. The system of claim 2,

the system further comprises: purchasing an auditing client; the target purchasing client side comprises the following steps: one of a plurality of purchasing clients;

the OA server is further used for sending the OA end purchase flow sheet to a purchase auditing client after generating the OA end purchase flow sheet based on the equipment purchase request;

the purchase auditing client is used for sending inquiry requests to a plurality of purchase clients through the OA server; receiving the purchase price scheme returned by each purchase client, and determining a target purchase price scheme; determining a target purchasing client from each purchasing client; and sending the identification of the target purchasing client and the target purchasing price scheme to the OA server.

11. The system of claim 10,

the system further comprises: at least one level of approval client;

the OA server is also used for sending an examination and approval request to the examination and approval client step by step based on the target purchase price scheme;

each level of the approval client generates an approval result based on the approval authority of the client and returns the approval result to the OA server;

and the OA server informs the target purchasing client side when the approval result is that the approval is passed so that the target purchasing client displays a purchasing information input interface provided by the OA server and outputs the OA terminal purchasing flow sheet and the target purchasing price scheme to a purchaser.

12. A method for managing equipment procurement, which is applied to the OA server in the system of any one of claims 1 to 11, the method comprising:

receiving the asset creation request;

13. The device procurement management method of claim 12 characterized by, in the plurality of types of clients, further comprising: an employee client and a target purchasing client;

before the obtaining of the purchased information, the method further comprises:

outputting a purchase application interface to an employee client so that the employee client displays the purchase application interface provided by the OA server, receives target purchase information input by an employee, generates an equipment purchase request and sends the equipment purchase request to the OA server;

generating an OA end purchasing flow sheet based on the equipment purchasing request; wherein, in the OA end purchase flow sheet, include: the identification information of the target equipment enables the target purchasing client to display a purchasing information input interface provided by the OA server, obtain the OA end purchasing flow sheet from the OA server and output the OA end purchasing flow sheet to a purchaser, receive the purchased information input by the purchaser in the OA end purchasing flow sheet and feed the purchased information back to the OA server;

the step of correspondingly storing each returned asset card information and the purchased information comprises the following steps:

and correspondingly storing the purchase flow sheet of the OA terminal and the returned information of each asset card and the purchased information.

14. The method of claim 13, wherein after the step of saving the OA-side purchase flow sheet and the returned information of each asset card in correspondence with the purchased information, further comprising:

outputting an external purchase order information input interface to the target purchase client, so that the target purchase client displays the external purchase order information input interface provided by the OA server, receives the input purchased information in an external purchase order information table corresponding to the OA terminal purchase flow sheet by a purchaser, and sends the input purchased information to the OA server; the external purchase order information table comprises second data required by the external asset management server for generating the purchase order;

calling a preset order creating interface to generate an external order creating request, and sending the external order creating request to an external asset management server; the external order creation request comprises: the second data to cause the external asset management server to generate an external purchase order based on the second data;

receiving external purchase order information returned by the external asset management server; and correspondingly storing the returned external order information and the OA end purchase flow order.

15. The method of claim 14,

the target device includes: asset devices and/or non-asset devices;

the step of outputting the external purchase order information input interface to the purchase client comprises the following steps:

determining that the target device is an asset device or a non-asset device based on the identification information of the target device;

if the target equipment is asset equipment, outputting an external purchase order information input interface to the purchase client, wherein an external purchase order information table contained in the interface is an asset purchase order information sub-table;

and if the target equipment is non-asset equipment, outputting an external purchase order information input interface to the purchase client, wherein an external purchase order information table contained in the interface is a non-asset purchase order information sub-table.

16. The method of claim 15, wherein after the step of saving the returned external order information corresponding to the OA-side procurement process order identifier, further comprising:

outputting a purchase bill voucher input interface to the target purchase client, so that the purchase client receives purchase voucher related information which is input by a purchaser and corresponds to the OA-end purchase flow bill through the purchase bill voucher input interface provided by the OA server and sends the purchase voucher related information to the OA server;

outputting a receiving interface to the target purchasing client so that the target purchasing client selects the target equipment to be received in the OA-end purchasing flow list and the corresponding certificate related information thereof through the receiving interface provided by the OA server, generates a receiving request and sends the receiving request to the OA server;

calling a preset receiving processing interface based on the receiving request to generate an external receiving instruction, and sending the external receiving instruction to an external asset management server; the external receiving instruction includes: and the target equipment to be received in the OA end purchase flow sheet and the corresponding certificate related information thereof, so that the external asset management server receives the target equipment to be received in the OA end purchase flow sheet.

17. The method of claim 16,

the external asset management server is: an SAP server;

18. The method of claim 14,

the method further comprises the following steps: receiving a data value of a designated data item which is obtained and sent by an external asset management server from an external asset management database according to synchronous timing duration through a preset data synchronization interface based on network service, and storing the data value into the OA database; and/or the presence of a gas in the gas,

receiving information of added and/or modified asset cards which are obtained and sent from an external asset management server according to the card updating timing duration from an external asset management database through a preset data synchronization interface based on network service, and storing the information into an OA database; wherein the pre-specified data items include: the external asset management server in the first data and in the second data has data items that the OA server does not have.

19. The method of claim 18,

the step of outputting the purchase application interface to the employee client comprises the following steps:

obtaining the data value of the pre-designated data item from the OA database, adding the data value serving as the default value of the data item to the position corresponding to the data item in the purchase application interface, and outputting the data value to the employee client for the employee to select;

the step of outputting the asset data entry interface to the asset management client comprises the following steps:

acquiring the data value of the pre-designated data item from the OA database, adding the data value serving as the default value of the data item to the position corresponding to the data item in the asset data entry interface, and outputting the data value to the asset management client for a resource manager to select;

the step of outputting an external purchase order information input interface to the target purchase client comprises the following steps:

and acquiring the data value of the pre-specified data item from the OA database, and adding the data value as a default value of the data item to the position corresponding to the data item in the external purchase order information entry for selection of a buyer.

20. The method of claim 19, further comprising:

receiving an asset query request sent by any client; the asset query request comprises a query condition;

and reading at least one of identification information, purchased information or external purchase order information of the asset card meeting the query condition from the OA database according to the query condition in the asset query request, and outputting the information.

21. The method of claim 13,

before the step of outputting the purchase application interface to the employee client, the method further includes:

receiving a login request sent by the employee client, wherein the login request comprises: an employee user identification;

determining the employee role group to which the employee user belongs based on the employee user identification in the login request; determining the authority of the employee user according to the corresponding relation between the preset employee role group and different group authorities; or determining the authority of the employee user based on the employee user identifier in the login request and the corresponding relation between the preset employee user identifier and different authorities; and if the employee user has the purchase application authority, outputting a purchase application interface to the employee client.

22. The method of claim 13,

before the step of generating an OA end purchase flow sheet based on the equipment purchase request, the method further includes:

sending the equipment purchase request to the asset management client; enabling the asset management client to judge whether to execute a purchasing process based on the employee user identification, the target equipment type and the inventory condition in the equipment purchasing request; and returning the judgment result to the OA server;

and after receiving a judgment result of executing the purchasing process, executing the step of generating the purchasing process list of the OA terminal based on the equipment purchasing request.

23. The method of claim 13,

after the step of generating an OA end purchase flow sheet based on the equipment purchase request, the method further includes:

sending the purchase flow sheet of the OA terminal to a purchase auditing client; enabling the purchase auditing client to send inquiry requests to a plurality of purchase clients through the OA server; receiving the purchase price scheme returned by each purchase client, and determining a target purchase price scheme; determining a target purchasing client from each purchasing client; and sending the identification of the target purchasing client and the target purchasing price scheme to the OA server.

24. The method of claim 23,

the system further comprises: at least one level of approval client;

the method further comprises the following steps: based on the target purchase price scheme, sending an examination and approval request to an examination and approval client step by step; enabling each level of the approval client to generate an approval result based on the approval authority of the client and return the approval result to the OA server;

and under the condition that the approval result is that the approval is passed, the target purchasing client is notified, so that the target purchasing client displays a purchasing information input interface provided by the OA server and outputs the OA end purchasing flow sheet and the target purchasing price scheme to a buyer.

25. The method of claim 12,

before the step of calling a preset asset creating interface based on the asset creating request to generate an asset card creating request and sending the asset card creating request to an external asset management server, the method further includes:

verifying whether the first data of each purchased target device meets a preset first data verification condition;

if yes, the step of calling a preset asset creating interface based on the asset creating request, generating an asset card creating request and sending the asset card creating request to an external asset management server is executed.

26. A device procurement management method applied to the external asset management server according to any one of claims 1 to 11, the method comprising:

27. The method of claim 26,

the purchased information is specifically: the OA server receives the information through the target purchasing client and is input by a purchaser based on a purchasing flow sheet of the OA terminal; the OA end purchase flow sheet is generated by the OA server based on the equipment purchase request sent by the employee client;

the method further comprises the following steps:

receiving an external order creation request generated and sent by the OA server by calling a preset order creation interface, wherein the external order creation request comprises: a second data; the second data is data required by the external asset management server to generate a purchase order, and comprises: the OA server receives the purchased information through the target purchasing client and the purchasing staff inputs the purchased information in an external purchasing order information table corresponding to the OA terminal purchasing flow sheet;

generating an external purchase order based on the second data, and obtaining external purchase order information;

and returning the external purchase order information to the OA server, so that the OA server correspondingly stores the returned external order information and the OA end purchase flow sheet, and correspondingly stores the OA end purchase flow sheet and each returned asset card information and the purchased information.

28. The method of claim 27, further comprising:

receiving an external goods receiving instruction generated and sent by the OA server by calling a preset goods receiving processing interface, wherein the external goods receiving instruction comprises: the OA end purchases the target equipment to be received in the flow sheet and the corresponding certificate related information; the relevant information of the purchase voucher is as follows: the OA server receives the purchase voucher related information corresponding to the OA end purchase flow sheet input by a purchaser through the target purchase client;

and receiving the target equipment to be received in the purchase flow sheet of the OA end based on the external receiving instruction.

29. The method of claim 28,

the external asset management server is: an SAP server;

30. The method of claim 27,

the method further comprises the following steps:

acquiring data of a pre-designated data item from the external asset management database according to the synchronous timing duration; wherein the pre-specified data items include: data items that the external asset management server in the first data and in the second data has, but the OA server itself does not have;

sending the obtained data of the specified data item to an OA server through a preset data synchronization interface based on network service, so that the OA server stores the received data in an OA database; and/or the presence of a gas in the gas,

updating the timing duration according to the cards, and acquiring information of the added and/or modified asset cards from the external asset management database;

and sending the obtained information of the added and/or modified asset cards to the OA server through a preset data synchronization interface based on network services, so that the OA server stores the received information of the added and/or modified asset cards into the OA database.

31. An OA server in a device procurement management system is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;

a memory for storing a computer program; a processor for implementing the method steps of any of claims 12 to 25 when executing a program stored in the memory.

32. An external asset management server in an equipment purchasing management system is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

a memory for storing a computer program; a processor for implementing the method steps of any of claims 26 to 30 when executing a program stored in the memory.

33. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method steps of any one of claims 12 to 25; or to carry out the method steps of any of claims 26 to 30.