DESCRIPTION
MOBILE TERMINAL MANAGEMENT SERVER AND MOBILE TERMINAL
MANAGEMENT PROGRAM
Technical 5 Field
[0001]
The present invention relates to a mobile terminal
management server which is a server run by enterprise
resource planning (ERP) and provides various kinds of data
10 via a communication network according to a request from a
mobile terminal used by a user, and a mobile terminal
management program installed in the mobile terminal
management server.
15 Background Art
[0002]
Heretofore, one so-called ERP (Enterprise Resource
Planning) has become mainstream as package software for
establishing a core business system for a company. In a
20 core business system in which this ERP is contained (an
integrated core business system, an ERP system), it is most
often constructed on a relational database, and design of
an application program that focuses on business processes
is mostly made. Thus, it is often operated without
25 focusing on report output.
3
[0003]
For the purpose of processing the large amount of
business data at a high speed, analyzing the business data
from various angles, and outputting reports under such a
5 situation, various data warehouse systems that undertake a
complementary role to the core business system have been
provided (see Patent Literature 1).
[0004]
Further, report inquiry systems that are designed to
10 output a report and provide information about a report or
the like to a mobile communication terminal (a mobile
terminal) have been proposed (see Patent Literatures 2 and
3).
15 Citation List
Patent Literature
[0005]
Patent Literature 1: JP 2002-312208 A
Patent Literature 2: JP 2003-323582 A
20 Patent Literature 3: JP 2007-200136 A
Summary of Invention
Technical Problem
[0006]
25 In the ERP system according to the related art, data
4
(including data input by the user and data calculated from
various kinds of data) acquired in each business process is
registered to each dedicated data table (table) and managed.
In other words, in the ERP system according to the related
5 art, a table to be updated differs according to an input
process such as a received order or shipping instruction.
Here, the "input process" refers to a process of inputting
various kinds of data acquired (decided) by an
administrator of the ERP system in each business process to
10 each table.
[0007]
Figs. 13(A) to 13(E) are explanatory diagrams for
describing an example of a table configuration in the ERP
system according to the related art. For example, when a
15 business flow (a process flow) configured with a plurality
of business processes represents "inventory sales," there
are five input processes of a received order, shipping
instruction, delivery, acceptance inspection, and sales.
In this case, as a table storing data related to the
20 process flow of "inventory sales," five tables of a
received order table, a shipping instruction table, a
delivery table, an acceptance inspection table, and a sales
table are used in the respective input processes, for
example, as illustrated in Figs. 13(A) to 13(E).
25 [0008]
5
In other words, in the ERP system according to the
related art, a table to be updated differs according to an
input process. For this reason, a correspondence between a
plurality of business processes belonging to a single
process flow is made by assigning an identifier (in Figs5 .
13(A) to 13(E), a received order number and a received
order description in the shipping instruction table, a
shipping instruction number and a shipping instruction
description in the delivery table, or the like) to data
10 (process data) related to each business process.
[0009]
For this reason, in the ERP system according to the
related art, it is necessary to specify a table according
to the type of input process and to input an identifier of
15 another corresponding process data for each input process.
In other words, for example, in the example of Figs. 13(A)
to 13(E), when process data related to a business process
"shipping instruction" associated with process data (that
is, various kinds of data stored in the same column as a
20 received order number "A00001" and a received order
description number "0010" in the received order table)
specified by a received order number "A00001" and a
received order description number "0010" is registered to a
database included in the ERP system, it is necessary to
25 register the received order number "A00001" and the
6
received order description number "0010" to the shipping
instruction table together with a shipping instruction
number specifying process data, a shipping instruction
description number, a type representing the type of
business process, and data (for example, an 5 orderer, a
quantity, an amount, a shipping instruction date, and a
shipping text) representing content of a business process,
as process data related to a business process "shipping
instruction." In this case, the same data (for example, an
10 orderer, a quantity, or an amount) may be registered to a
plurality of tables, and thus it is problematic from a
point of view of an efficient data process.
[0010]
Then, similarly to when data is registered, in the
15 ERP system according to the related art, when various kinds
of data stored in various tables are searched for at the
user’s request, for example, it is necessary to search for
necessary process data by tracing an identifier of process
data and to individually acquire data matching a search
20 condition from various tables, and thus there is a problem
in that a processing load required for a search excessively
increases.
[0011]
As described above in the ERP system according to the
25 related art, when various kinds of data stored in various
7
tables are searched for, a processing load is large, and
when various kinds of information processing is performed
by extracting various kinds of data, a processing load
further increases, and thus there is a problem in that it
is hard to rapidly output valid 5 information by information
processing.
[0012]
Particularly, when information is provided according
to a request from a mobile communication terminal (mobile
10 terminal), a rapid response speed is required, and thus the
above problem becomes remarkable.
[0013]
In order to solve the above problems, it is an object
of the present invention to reduce a processing load
15 required for data processing in a business system and
rapidly output valid information in a business system (an
ERP system) that provides information about a report to a
mobile communication terminal (mobile terminal).
20 Solution to Problem
[0014]
A mobile terminal management server according to the
present invention is a mobile terminal management server
that is a server run by ERP and provides various kinds of
25 data via a communication network according to a request
8
from a mobile terminal used by a user, and includes a
process flow data storage unit that stores process flow
data including various kinds of data related to a process
flow including a plurality of business processes, the
5 process flow data including project specifying data, status
data, common data, and process-specific data, the project
specifying data specifying business projects to which the
plurality of business processes included in the process
flow belong, the status data representing progress statuses
10 of the plurality of business processes included in the
process flow, the common data being common to business
process included in a same process flow, and the processspecific
data being specific to each business process
included in a same process flow, a business project
15 designation screen providing unit that provides a business
project designation screen for designating a business
project according to a request from the mobile terminal, a
business project information accepting unit that receives
and accepts business project information representing the
20 business project designated through the business project
designation screen from the mobile terminal, a process data
search unit that searches for process data related to a
plurality of business processes belonging to the business
project represented by the business project information
25 accepted by the business project information accepting unit
9
with reference to the process flow data stored in the
process flow data storage unit, a business project
management information generating unit that generates
business project management information representing a
progress status of the designated business project 5 based on
the process data searched for by the process data search
unit, and a business project management information
providing unit that provides the business project
management information generated by the business project
10 management information generating unit to the mobile
terminal.
[0015]
Through the above configuration, in a business system
that provides information related to a report to a mobile
15 communication terminal, it is possible to reduce a
processing load required for data processing in the
business system and rapidly output valid information.
[0016]
The project specifying data includes, for example,
20 project identification information uniquely identifying a
business project and business project description
identification information uniquely identifying a
description of each business unit configuring a business
project.
25 [0017]
10
The business project management information
generating unit may be configured to generate the business
project management information including actual performance
information representing an actual business performance of
the 5 designated business project.
[0018]
The mobile terminal management server may further
include a project schedule data storage unit that stores
project schedule data representing a business schedule of
10 each business project, and the business project management
information generating unit may be configured to specify
the project schedule data representing the business
schedule of the designated business project with reference
to the project schedule data, and generates the business
15 project management information including the specified
project schedule data.
[0019]
The business project management information
generating unit may be configured to compare the business
20 schedule of the designated business project with the actual
business performance, generate actual performance
accounting information representing an accounting progress
status, and generate the business project management
information including the generated actual performance
25 accounting information.
11
[0020]
Further, a mobile terminal management program
according to the present invention is a mobile terminal
management program that operates ERP and causes a mobile
terminal management server to execute a process 5 of
providing various kinds of data via a communication network
according to a request from a mobile terminal used by a
user, the mobile terminal management server including a
process flow data storage unit that stores process flow
10 data including various kinds of data related to a process
flow including a plurality of business processes, the
process flow data including project specifying data, status
data, common data, and process-specific data, the project
specifying data specifying business projects to which the
15 plurality of business processes included in the process
flow belong, the status data representing progress statuses
of the plurality of business processes included in the
process flow, the common data being common to business
process included in a same process flow, and the process20
specific data being specific to each business process
included in a same process flow, and the mobile terminal
management program causing the mobile terminal management
server to execute a business project designation screen
providing process of providing a business project
25 designation screen for designating a business project
12
according to a request from the mobile terminal, a business
project information accepting process of receiving and
accepting business project information representing the
business project designated through the business project
designation screen from the mobile 5 terminal, a process data
search process of searching for process data related to a
plurality of business processes belonging to the business
project represented by the business project information
accepted in the business project information accepting
10 process with reference to the process flow data stored in
the process flow data storage unit, a business project
management information generating process of generating
business project management information representing a
progress status of the designated business project based on
15 the process data searched for in the process data search
process, and a business project management information
providing process of providing the business project
management information generated in the business project
management information generating process to the mobile
20 terminal.
Advantageous Effects of Invention
[0021]
According to the present invention, it is possible to
25 reduce a processing load required for data processing in a
13
business system and rapidly output valid information in a
business system (an ERP system) that provides information
about a report to a mobile communication terminal.
Brief 5 Description of Drawings
[0022]
Fig. 1 is a block diagram illustrating a
configuration example of a report inquiry system.
Fig. 2 is a block diagram illustrating a
10 configuration example of a mobile terminal management
server.
Fig. 3 is an explanatory diagram illustrating an
example of a storage state of process flow data.
Fig. 4 is a flowchart illustrating an example of a
15 slip data providing process.
Fig. 5 is an explanatory diagram illustrating an
example of a menu screen.
Fig. 6 is an explanatory diagram illustrating an
example of a slip search screen.
20 Fig. 7 is an explanatory diagram illustrating an
example of a slip search screen.
Fig. 8 is an explanatory diagram illustrating an
example of an overall configuration of a selection item
arrangement circle displayed on the slip search screen.
25 Fig. 9 is an explanatory diagram illustrating an
14
example of a search result list display screen.
Fig. 10 is a flowchart illustrating an example of a
project management information provision process.
Fig. 11 is an explanatory diagram illustrating an
example 5 of a project designation screen.
Fig. 12 is an explanatory diagram illustrating an
example of a project management information display screen.
Figs. 13(A) to 13(E) are explanatory diagrams for
describing an example of a table configuration in an ERP
10 system according to a related art.
Mode for Carrying Out the Invention
[0023]
Hereinafter, an embodiment of the present invention
15 will be described with reference to the accompanying
drawings.
Fig. 1 is a block diagram illustrating a
configuration example of a report inquiry system 500
according to an embodiment of the present invention. As
20 illustrated in Fig. 1, the report inquiry system 500
includes a mobile terminal management server 10, a relay 20,
a plurality of mobile terminals 31 to 3N (N is an arbitrary
positive integer), an enterprise resource planning system
100, an enterprise resource planning system 200, and an
25 enterprise resource planning system 300.
15
[0024]
The mobile terminal management server 10 is connected
with each of the mobile terminals 31 to 3N via a
communication network 40 such as the Internet and the relay
20. 5 The mobile terminal management server 10 is connected
with the enterprise resource planning system 100, the
enterprise resource planning system 200, and the enterprise
resource planning system 300 via communication networks 51,
52, and 53 such as a LAN (Local Area Network) or a
10 dedicated communication line, respectively. Further, the
mobile terminal or the enterprise resource planning system
may be configured to communicate with another mobile
terminal or another enterprise resource planning system via
the mobile terminal management server, or the mobile
15 terminal or the enterprise resource planning system may be
configured not to communicate with another mobile terminal
or another enterprise resource planning system.
[0025]
The enterprise resource planning system 100 includes
20 a core business server 110, a data warehouse server (DWH
server) 120, and a process flow DB 101. The enterprise
resource planning system 200 includes a DWH server 220 and
a process flow DB 201. The enterprise resource planning
system 300 includes a core business server 310 and a
25 process flow DB 301.
16
[0026]
Each of the plurality of the enterprise resource
planning systems 100, 200, and 300 which differ in
configuration fulfills a functions of an enterprise
resource 5 planning system by performing communication
(transmission and reception of various kinds of
information) with the mobile terminal management server 10
according to the need (that is, according to its function).
In other words, in the report inquiry system, the system
10 200 having no core business server or the system 300 having
no DWH server can also fulfill the function of the
enterprise resource planning system by performing
communication with the mobile terminal management server 10.
Even though not illustrated, the system having no process
15 flow DB can also fulfill the function of the enterprise
resource planning system by storing process flow data in
the mobile terminal management server 10. Since a wellknown
technique is used for the core business server or the
like included in each core business system, the following
20 description will be made using the enterprise resource
planning system 100 as an example.
[0027]
The core business server 110 is connected with the
DWH server 120 through a dedicated communication line.
25 [0028]
17
The core business server 110 is a server managed, for
example, by the administrator of the report inquiry system
500, and has various functions of managing report
information related to various businesses (for example,
functions of generating, updating, and holding info5 rmation).
The core business server 110 is configured with a general
information processing device including an OS (Operating
System) and a relational DB.
[0029]
10 Here, the report is the general term of books and a
type of slip. Further, the books denote one in which
matters concerning receipts and expenditure of money or
goods are filled, and the "slip" denotes one that is data
to become a basis when creating books and constitutes
15 evidence of transactions and the like on a business. In
the present embodiment, the case where the core business
server 110 deals with the process data representing only
the slip data as report data will be described as an
example.
20 [0030]
The core business server 110 executes various kinds
of processing according to a business application program.
Examples of the business application program include a
sales business management program, a purchase business
25 management program, a production management program, a
18
financial accounting management program, and a managerial
accounting management program.
[0031]
The DWH server 120 is a server managed, for example,
5 by the system administrator of the present system, and
includes various functions of implementing a data warehouse.
Here, the "data warehouse" denotes a system that analyzes
relevance between respective items from among business data
such as report data accumulated in time series. Further,
10 the DWH server 120 has a function of converting a file of a
CSV (Comma Separated Values) format transferred from the
core business server 110 into a predetermined data format
and the like and registering various kinds of data to a
predetermined storage region. Further, the DWH server 120
15 may be configured to extract data corresponding to each
storage region from a state of CSV format without carrying
out data format conversion.
[0032]
The process flow DB 101 is a storage medium that
20 stores process flow data configured with various kinds of
process data (or report data) collected and marshaled by
means of various kinds of information processing using
various kinds of programs stored in the business
application program DB (not illustrated) of the core
25 business server 110. The process flow data will be
19
described in detail later. In the present embodiment, the
enterprise resource planning system 100 includes a business
related data DB (not illustrated) managed by the DWH server
120, and the core business server 110 has a function of
5 converting process data stored in the process flow DB 101
into a CSV (Comma Separated Values) format according to a
predetermined extraction condition and transmitting the
process data to the mobile terminal management server 10.
In the present embodiment, the core business server 110
10 transfers a data file whose format is converted to CSV
format by an FTP (File Transfer Protocol) to the mobile
terminal management server 10.
[0033]
The mobile terminal management server 10 is a server
15 which is run by ERP and provides various kinds of data
through a communication network according to a request from
a mobile terminal used by the user. For example, the
mobile terminal management server 10 is configured with an
information processing device such as a WWW server, and
20 managed by the system administrator of the report inquiry
system 500.
[0034]
Fig. 2 is a block diagram illustrating a
configuration example of the mobile terminal management
25 server 10. As illustrated in Fig. 2, the mobile terminal
20
management server 10 includes a control unit 11 that
performs various kinds of control, a process flow data
temporary storage DB 16, a business application program DB
17, a process flow DB 18a, a project DB 18b, a DWH DB 19,
5 and the other DB 10X that stores various kinds of data (for
example, data used by various kinds of programs stored in
the business application program DB 17) necessary to
implement the function of the general core business server.
The other DB 10X has a portion which does not specifically
10 relate to the present invention, and thus a detailed
description thereof will not be made. The control unit 11
includes a slip data provision processing unit 11a that
executes, for example, a process of providing process flow
data to the mobile terminals 31 to 3N and a project
15 management information provision processing unit 11b that
executes, for example, a process of providing project
management information to the mobile terminals 31 to 3N.
[0035]
The process flow data temporary storage DB 16 is a
20 storage medium that temporarily stores process flow data
acquired from the enterprise resource planning system 100
side or process flow data stored in the process flow DB 18a.
The process flow data stored in the process flow data
temporary storage DB 16 is updated, for example, at regular
25 intervals (for example, at one-day intervals, at three-day
21
intervals, or at 12-hour intervals).
[0036]
The business application program DB 17 is a storage
medium that stores a program used for various kinds of
businesses. Examples 5 of the program stored in the business
application program DB 17 include a sales business
management program, a purchase business management program,
a production management program, a financial accounting
management program, and a managerial accounting management
10 program.
[0037]
The process flow DB 18a is a storage medium that
stores process flow data configured with various kinds of
process data (or report data) collected and marshaled by
15 means of various kinds of information processing using
various kinds of programs stored in the business
application program DB 17. In the present embodiment, the
description will proceed in connection with an example in
which process flow data including various kinds of data
20 related to a process flow including a plurality of business
processes is stored in a process flow table PT in the
process flow DB 18a. Further, in the present embodiment,
the description will proceed in connection with an example
in which the mobile terminal management server 10 centrally
25 manages process flow data generated in each process flow
22
through the single process flow table PT. Further, in the
present embodiment, the process flow data is assumed to
include usually used slip data (for example, data in which
received order slip header information, received order slip
5 description information, delivery date schedules, and the
like are associated with slip data corresponding to a
received order slip, and which is stored with the structure
which is retrievable based on a key such as a slip number.
Here, the slip number includes a received order number, a
10 purchase order number, a shipping number, an acceptance or
delivery numbers, a bill reference, a billing number, an
accounting number, and the like.).
[0038]
Further, the mobile terminal management server 10 may
15 be configured to manage process flow data through a
plurality of tables, for example, for each type which will
be described later or for each one in which a part (for
example, an orderer) of content of common data, which will
be described later, is the same.
20 [0039]
Fig. 3 is an explanatory diagram illustrating an
example of a storage state of process flow data in the
process flow DB 18a. As illustrated in Fig. 3, process
flow data according to the present embodiment includes a
25 main key section, a project specifying data section, a
23
reference key section, a type section, a status section, a
common data section, and a process-specific data section.
Each item (that is, a column item in the process flow table
PT) corresponding to each section of the process flow data
5 represents the type of process data configuring the process
flow data. In other words, data related to the business
processes configuring the process flow is stored to be
assigned to the respective sections configuring the process
flow data. Further, process data related to one process
10 flow (a series of process flow from a received order from a
certain company to deliver) is stored in the same entry in
the process flow table PT (that is, the same row in the
process flow table PT). Through this configuration, a
correspondence relation between respective pieces of
15 process data can be defined.
[0040]
Here, the "main key section" refers to a part in
which main key data which is data to uniquely specify
process flow data among pieces of process flow data is
20 stored. In the present embodiment, the main key section is
configured with a process flow number and a process flow
description number. In other words, in the present
embodiment, a combination of the process flow number and
the process flow description number serves as an identifier
25 (ID) of each process flow data. The main key section is
24
updated at the time of initial registration of process flow
data. Here, the "time of initial registration of process
flow data" refers to when an entry (data row) is added to
the process flow data, for example, when another
5 corresponding process data which belongs to a certain
process flow but is not registered yet is registered. Here,
"update" is assumed to include addition of data.
[0041]
Further, the "process flow number" is an identifier
10 to specify one process flow data (that is, a first column
in the process flow table PT illustrated in Fig. 3). The
process flow number is assigned to each process data which
is the same in predetermined item. In the present
embodiment, the same process flow number is assigned to
15 process flow data which is the same in the type and the
orderer of the process flow data.
[0042]
Further, the "process flow description number" is an
identifier specifying specific process flow data among
20 pieces of process flow data to which the same process flow
number is assigned. In other words, for example, the
process flow table PT illustrated in Fig. 3 can uniquely
specify process flow data including process data
representing that an order for a business of the amount
25 "1200" and "2600" is received from an orderer "T001" by a
25
combination of the process flow number "000001" and the
process flow description number "0010" or "0020" in the
business process "received order" in the type "inventory
sales" of the process flow.
5 [0043]
The "project specifying data section" is a part in
which main key data serving as data specifying a project
among pieces of process flow data is stored. In the
present embodiment, the project specifying data section
10 includes a project number and a project description number.
In other words, in the present embodiment, a project and a
description thereof can be specified by a combination of a
project number and a project description number. In the
present embodiment, when an entry (data row) is added to
15 process flow data, a project number and a project
description number are designated, and thus an entry is
added such that a project and a project description to
which an entry belongs can be specified.
[0044]
20 The "project number" is an identifier identifying a
single project. For the same project, the same project
number is used. The "project description number" is an
identifier identifying a description of each business unit
configuring a project. Thus, each of the project
25 description numbers associated with the same project number
26
is an identifier identifying a description of each business
unit (for example, cladding or power facility) configuring
the same project (for example, dam construction). Further,
data (data of the same row) such as the common data section
associated with the same project 5 description number is data
identifying a description of the same business.
[0045]
Next, the "reference key section" is a part in which
reference key data which is data to specify another process
10 flow data (or another process data) related to the process
flow such as original transaction on sales returns among
pieces of process flow data is stored. In the present
embodiment, the reference key section is configured with a
reference number and a reference description number, and is
15 updated at the time of initial registration of process flow
data.
[0046]
The process flow number and the process flow
description number of another process flow related to the
20 process flow are stored in the reference number and the
reference description number, respectively. However, when
there is no other process flow related to the process flow
such as a new transaction, data representing the same value
as the main key section of the same entry is stored in the
25 reference key section (that is, the process flow number and
27
the process flow description number are stored in the
reference number and the reference description number,
respectively). Further, when the reference key section
represents another process data related to the process flow,
5 data specifying the type of process data is further stored
in the reference key section.
[0047]
The "type section" is a part in which type data which
is data representing the type of process flow such as
10 inventory sales or sample shipping among pieces of process
flow data is stored. The type section is updated at the
time of initial registration of process flow data. The
type of process flow is not limited to inventory sales or
sample shipping. Further, it is assumed that a necessary
15 process is decided in advance depending on the type of the
process flow (that is, the type of business process or the
number of business processes to be included differ
according to type of process flow). Further, two or more
other types of process flows will be provided later (see
20 Fig. 9).
[0048]
The "status section" is a part in which status data
which is data (data representing a progress status of each
of a plurality of business processes included in the
25 process flow) representing the progress of the process flow
28
among pieces of process flow data is stored. In the
present embodiment, the status data represents the progress
of each business process by setting "0" to an unfinished
process and "1" to a finished process on a business process
needed 5 eded by the process flow. In other words, for example,
as illustrated in Fig. 3, it is assumed that when the
process flow relates to "inventory sales" and the process
flow includes business processes of "received order,"
"shipping," "delivery," "delivery acceptance inspection,"
10 and "sales," process specific data (for example, a received
order date) related to the business process "received
order" is registered. In this case, in the status data, a
part corresponding to "sales" becomes "1," and the
remaining parts remain in an initial state (that is, a
15 state set to "0").
[0049]
In other words, the status section in the present
embodiment is updated for each business process. In other
words, the status section is updated when process specific
20 data which will be described later is input, specifically,
when it is determined that each business process is
completed as a predetermined status change condition is
satisfied. The status change condition is not specially
limited, and in the present embodiment, it is assumed that
25 "what all process specific data corresponding to one
29
business process is input" remains stored in a
predetermined storage region of the mobile terminal
management server 10 as the status change condition.
[0050]
In 5 the present embodiment, since the process flow of
a different type is stored in the same table, a part that
stores process data unnecessary for a specific process flow
may exist among items (column items) configuring a table.
In this case, it is assumed that in the process flow table,
10 a part storing unnecessary process data becomes null data,
and "0" is stored in the status data corresponding to the
null data.
[0051]
The "common data section" is a part in which common
15 data which is data (that is, data which is common between
the business processes included in the same process flow)
not relying on the business process such as an orderer and
a ship-to party among pieces of process flow data is stored.
The common data section is updated at the time of initial
20 registration of process flow data.
[0052]
The "process-specific data section" is a part in
which process specific data which is data specific to each
business process included in the same process flow such as
25 the received order date or data (for example, text data
30
representing a precaution such as "arrival by delivery
date" or "fragile goods (handle with care)" registered in
each business process among pieces of process flow data is
stored. The process specific data section is updated for
each business process. Thus, 5 in the present embodiment,
among pieces of process flow data, data relying on the
business process is referred to as "process specific data,"
and data not relying on the business process is referred to
as "common data."
10 [0053]
The process flow data according to the present
embodiment has been described so far, and a definition of
various terms illustrated in Fig. 3 will be briefly
described below.
15 [0054]
First, the "received order" refers to a state in
which an order has been received from a customer, and a
contract with the customer has been made. The "shipping
instruction" refers to a state in which an instruction to
20 ship a product has been given to a warehouse man or a
person in charge of physical distribution. The "delivery"
refers to a state in which a product has been shipped from
a warehouse and then started to be delivered. The
"acceptance inspection" refers to a state in which a
25 customer has completed an acceptance inspection and an
31
ownership of a product has been transferred to the customer.
The "sales" refers to a state in which an acceptance
inspection of a customer has been checked and a debt amount
on a customer has been fixed (that is, a debt has been
5 recorded).
[0055]
The term "acceptance inspection" is also used to mean
"business of inspecting whether or not goods for supply or
services satisfy an ordered specification (that is, a
10 quantity, a color, a shape, and a quality)" or that "an
ownership of an asset is transferred when an acceptance
inspection is completed." Further, in financial accounting
(or institutional accounting) or on the ERP system, in
order to explicitly specify a transfer timing of an
15 ownership of an asset, an event of "acceptance inspection"
is defined to be distinguished from delivery.
[0056]
The project DB 18b is a storage medium that stores
project schedule data representing a business schedule of
20 each project. In the present embodiment, in the project DB
18b, the project schedule data representing the business
schedule of each project is stored in a project table PJT.
Even though not illustrated, the project schedule data in
which information representing a business schedule (for
25 example, a schedule of a budget, a purchase, received order,
32
a purchase order, and the like) for achieving a
corresponding business is associated with, for example, a
project number and a project description number is assumed
to be registered in the project table PJT.
5 [0057]
The mobile terminal management server 10 has a
function of providing various kinds of data stored in the
process flow DB 18a, the project DB 18b, the DWH DB 19, and
the other DB 10X according to a request from a
10 predetermined external device, that is, requests from the
mobile terminals 31 to 3N and the enterprise resource
planning systems 100, 200, and 300 in the present
embodiment. In other words, the mobile terminal management
server 10 has a function as the core business server. In
15 other words, the mobile terminal management server 10
includes an ERP engine.
[0058]
Even though not illustrated, in the present
embodiment, the mobile terminal management server 10 is
20 assumed to have a function as a DWH server having various
functions of implementing a data warehouse. As the mobile
terminal management server 10 has a structure of
functioning as the ERP engine and the DWH server, it is
possible to provide information requested as the enterprise
25 resource planning system to the enterprise resource
33
planning systems having different configurations (for
example, the enterprise resource planning system 100
including both the core business server and the DWH server,
the enterprise resource planning system 200 including only
the DWH server, and the enterprise 5 resource planning system
300 including only the DWH server).
[0059]
Each of the mobile terminals 31 to 3N is an
information processing device, such as iPad (registered
10 trademark), which includes a central processing unit (CPU),
a read only memory (ROM), a random access memory (RAM), and
a display unit. In the present embodiment, each of the
mobile terminals 31 to 3N is assumed to include various
kinds of usable applications to deal with report data, such
15 as a WEB browser. In the present embodiment, for example,
each of the mobile terminals 31 to 3N has a function of
defining a query (a search item, a search key, an
extraction key, and the like) used to acquire necessary
report data (process flow data and project schedule data in
20 the present embodiment) from the mobile terminal management
server 10 according to an operation performed by the user,
and transmitting the query to the mobile terminal
management server 10. The mobile terminals 31 to 3N are
assumed to include code readers (or code reader functions)
25 31a to 3Na that read various kinds of codes such as a quick
34
response (QR) code (a registered trademark), respectively.
[0060]
In the present embodiment, each of the mobile
terminals 31 to 3N has a function of communicating with the
5 mobile terminal management server 10 through the relay 20
and the communication network 40 and outputting data
acquired from the mobile terminal management server 10 to a
display unit through a function of software such as a
predetermined Web application (a WEB browser).
10 [0061]
Next, a process of updating the process flow data
stored in the process flow data temporary storage DB 16
will be described. In the present embodiment, when a data
update timing (for example, a predetermined timing (for
15 example, at 2:00 am) when an update is performed everyday)
comes, the mobile terminal management server 10 reads the
process flow data (latest data) stored in the process flow
DB 18a included in the mobile terminal management server 10,
stores (newly stores or overwrites) the process flow data
20 in a predetermined storage region of the process flow data
temporary storage DB 16, and updates storage information of
the process flow data temporary storage DB 16. Thus, the
storage information of the process flow data temporary
storage DB 16 is updated by a batch process.
25 [0062]
35
Next, an operation of the report inquiry system 500
according to the present embodiment will be described with
reference to the accompanying drawings. Here, a
description of an operation or process which does not
5 specially relate to the present invention may not be made.
[0063]
Fig. 4 is a flowchart illustrating an example of a
slip data providing process executed, for example, by the
mobile terminal management server 10 in the report inquiry
10 system 500 according to the present embodiment. Here, the
description will proceed in connection with an example in
which the mobile terminal management server 10 provides the
process flow data according to a request from a mobile
terminal 31 used by a user X.
15 [0064]
In the slip data providing process, first, the mobile
terminal 31 receives a login request by the user X's login
operation (step S101). The login operation refers to, for
example, an input operation of a previously set secret
20 number. Here, when the login to the mobile terminal 31 is
permitted, it is permitted to make various kinds of
operations for using various kinds of functions included in
the mobile terminal 31.
[0065]
25 In a state in which the user X logs in the mobile
36
terminal 31, when the user X executes a predetermined login
operation, the mobile terminal 31 accesses the mobile
terminal management server 10, acquires a login screen,
designates information (for example, a user ID and a
5 password which are previously set) necessary to login on
the login screen, and makes a login request (step S102).
For example, the login request is made such that
predetermined information (for example, an electronic
certificate issued to the user X) used for a predetermined
10 login determination is provided in addition to the user ID
and the password. Further, when the operation to login the
mobile terminal management server 10 is performed, the user
X may be requested to designate a language (for example,
Japanese) used in a group to which the user belongs or
15 various kinds of screens.
[0066]
Upon receiving the login request, the mobile terminal
management server 10 determines whether or not it is
permitted to log in (step S103). For example, the
20 determination may be made based on an ID, a password, an
electronic certificate, and the like.
[0067]
When it is determined that it is permitted to login
(Y in step S103), the mobile terminal management server 10
25 sets the mobile terminal 31 to a login state. When the
37
mobile terminal 31 is set to a login state, the mobile
terminal management server 10 transmits menu screen
information representing a menu screen to the mobile
terminal 31 (step S104). However, when it is determined
5 that it is not permitted to login (N in step S103), the
mobile terminal management server 10 ends the slip data
providing process without setting the mobile terminal 31 to
the login state. Further, when it is determined that it is
not permitted to login, the mobile terminal management
10 server 10 performs a process of notifying the mobile
terminal 31 of login refusal.
[0068]
Upon receiving the menu screen information, the
mobile terminal 31 causes the menu screen represented by
15 the received menu screen information to be displayed on the
display unit included in the mobile terminal 31 (step S105).
[0069]
Fig. 5 is an explanatory diagram illustrating an
example of a menu screen. As illustrated in Fig. 5, a menu
20 arrangement circle display region 501 is provided on the
menu screen. A menu arrangement circle MC in which menu
buttons M1 to M6 on which a plurality of selectable menu
names are displayed are arranged substantially on the
circumference thereof is displayed on the menu arrangement
25 circle display region 501. Further, a title display region
38
MA on which the title of the menu arrangement circle MC
disposed on the central region of the circle formed by the
menu arrangement circle MC is displayed is provided on the
menu arrangement circle display region 501 as illustrated
in Fig. 5. 5 Here, as the menu buttons M1 to M6, a slip
search button M1 pushed down to search for a slip, a new
slip button M2 pushed down to newly create a slip, an
expense input button M3 pushed down to input expense, a
master registration button M4 pushed down to register a
10 master, a project button M5 pushed down to make a project
management information provision request, and an inventory
query button M6 pushed down to query inventory information
are provided.
[0070]
15 In the menu screen displayed on the display unit of
the mobile terminal 31 in which a touch panel is arranged,
the user X pushes down any one of the menu buttons M1 to M6
through a touch operation (a contact operation by a finger).
In the present embodiment, the slip search button M1 is
20 assumed to be pushed down. Here, a description of the
process when the other menu buttons M2 to M6 are pushed
down will not be made.
[0071]
When the slip search button M1 is pushed down in the
25 menu screen, the mobile terminal 31 transmits information
39
representing that the slip search button M1 has been pushed
down to the mobile terminal management server 10 as a menu
selection result (step S106).
[0072]
5 Upon receiving the fact that the slip search button
M1 is pushed down as the menu selection result, the slip
data provision processing unit 11a of the mobile terminal
management server 10 transmits the slip search screen
information representing the slip search screen for
10 designating a slip search condition to the mobile terminal
31 (step S107).
[0073]
Upon receiving the slip search screen information,
the mobile terminal 31 causes the slip search screen
15 represented by the received slip search screen information
to be displayed on the display unit included in the mobile
terminal 31 (step S108).
[0074]
Fig. 6 is an explanatory diagram illustrating an
20 example of a slip search screen. As illustrated in Fig. 6,
the slip search screen is provided with a plurality of
selection item arrangement circle display regions 601, 602,
and 603 to respectively display a plurality of selection
item arrangement circles DC, SC, and PC on which a
25 plurality of selection items selectable to designate a
40
search condition are arranged substantially on the
circumference thereof, and a keyword input region 604 to
input a keyword to be used as a narrowing-down condition.
In the present embodiment, as the selection item
5 arrangement circles DC, SC, and PC, a processed slip type
selection item arrangement circle DC on which the type of
processed slip is selectably displayed, a detailed
selection type selection item arrangement circle SC in
which the title of a detailed item for narrowing-down is
10 selectably displayed, and a process type selection item
arrangement circle PC in which the type of business process
is selectably displayed are provided. Further, as the
selection item arrangement circle display regions 601, 602,
and 603, a processed slip type selection item arrangement
15 circle display region 601 to display the processed slip
type selection item arrangement circle DC, a detailed
selection type selection item arrangement circle display
region 602 to display the detailed selection type selection
item arrangement circle SC, and a process type selection
20 item arrangement circle display region 603 to display the
process type selection item arrangement circle PC are
provided.
[0075]
The processed slip type selection item arrangement
25 circle DC is provided with seven types of selection items
41
(selection item buttons) to select a slip, which are
arranged substantially on the circumference thereof. That
is, the processed slip type selection item arrangement
circle DC is provided with a received order button D1 to
5 designate a received order slip as the search condition, a
purchase order button D2 to designate a purchase order slip
as the search condition, a warehousing button D3 to
designate a warehousing slip as the search condition, a
delivery button D4 to designate a delivery slip as the
10 search condition, a sales button D5 to designate a sales
slip as the search condition, a billing button D6 to
designate a billing slip as the search condition, and a
deposit button D7 to designate a deposit slip as the search
condition. Further, a classification display button DA on
15 which a classification name "processed slip" is displayed
is arranged on the central region of the processed slip
type selection item arrangement circle DC. In the present
embodiment, the corresponding type of slip can be searched
for by selecting the selection items (selection item
20 buttons) D1 to D7 (by selecting one or more buttons).
[0076]
The detailed selection type selection item
arrangement circle SC is provided with four types of
selection items (selection item buttons) to select detailed
25 narrowing-down condition items, which are arranged
42
substantially on the circumference thereof. That is, the
detailed selection type selection item arrangement circle
SC is provided with a customer button S1 to designate a
customer as the search condition, a vendor button S2 to
5 designate a vendor as the search condition, an organization
button S3 to designate an organization as the search
condition, and an item goods button S4 to designate item
goods as the search condition. Further, a classification
display button SA on which a classification name "detailed
10 selection" is displayed is arranged on the central region
of the detailed selection type selection item arrangement
circle SC. In the present embodiment, when the selection
items (selection item buttons) S1 to S4 (one or more
buttons may be selected) are selected, a detailed
15 narrowing-down condition designation screen (not
illustrated) to designate a concrete narrowing-down
condition is displayed, and a concrete narrowing-down
condition (for example, which corresponds to a vendor
company name when the customer button S1 is selected, an
20 item goods number when the item goods button S4 is selected,
and the like) can be designated through the detailed
narrowing-down condition designation screen. The slip
satisfying the designated narrowing-down condition can be
searched for by selecting the concrete narrowing-down
25 condition (one or more concrete narrowing-down conditions
43
may be selected).
[0077]
The process type selection item arrangement circle PC
is provided with three types of selection items (selection
5 item buttons) to select the business process, which are
arranged substantially on the circumference thereof. That
is, the process type selection item arrangement circle PC
is provided with a production button P1 to designate
"production" in the business process as the search
10 condition, a sales button P2 to designate "sales" in the
business process as the search condition, and a purchase
button P3 to designate "purchase" in the business process
as the search condition. Further, a classification display
button PA on which a classification name "process" is
15 displayed is arranged on the central region of the process
type selection item arrangement circle PC. In the present
embodiment, a slip related to a business process of a
corresponding type can be searched for by selecting the
selection items (selection item buttons) P1 to P3 (one or
20 more selection item buttons may be selected).
[0078]
In the present embodiment, when the classification
display button DA, SA, or PA is pushed down, a rendering
operation of rotating the corresponding selection item
25 arrangement circle DC, SC, or PC is executed. In other
44
words, in the present embodiment, a selection item rotation
rendering setting (a setting by a computer program) is made
on the selection item arrangement circle display regions
601, 602, and 603 in the slip search screen so that a
5 selection item rotation rendering operation of causing a
plurality of selection items in the corresponding selection
item arrangement circle DC, SC, or PC to rotationally move
on the circumference can be executed according to a
predetermined rotation instruction operation (an operation
10 of pushing down the classification display button DA, SA,
or PA) of the mobile terminal 31 by the user X.
Specifically, in the screen state illustrated in Fig. 6,
for example, when the classification display button DA is
pushed down, a selection item rotation rendering operation
15 of causing a plurality of selection items in the selection
item arrangement circle DC to rotate on the circumference
counterclockwise (in a direction A in Fig. 7) is executed.
In this case, the rotation direction may be changed
according to a predetermined rotation direction change
20 operation by the user X (an operation of touching a portion
of the screen with a finger near a location at which the
circle formed by the selection item arrangement circle DC
is displayed and sliding the finger in a new rotation
direction). Further, when the classification display
25 button DA, SA, or PA is pushed down again, it is desirable
45
to end the selection item rotation rendering operation.
[0079]
Since the selection item rotation rendering operation
is performed as described above, as illustrated in Fig. 8,
5 it is unnecessary to arrange all of the selection item
arrangement circles DC, SC, and PC within the screen, and
even when some of the selection items arranged in each of
the selection item arrangement circles DC, SC, and PC are
not displayed on the screen, all of the selection items can
10 be sequentially displayed by rotating the selection item
arrangement circles DC, SC, and PC. Further, since it is
unnecessary to simultaneously display all of the selection
items arranged in each of the selection item arrangement
circles DC, SC, and PC within one screen, the display size
15 of each selection item can be increased. Further, when the
screen size is large, a configuration capable of
simultaneously displaying all of the selection items within
one screen may be provided.
[0080]
20 In present embodiment, the selection items arranged
in the selection item arrangement circles DC, SC, and PC
are displayed in a circular frame. However, some or all of
the selection items may be displayed in a frame of any
other shape such as a rectangular shape, a triangular shape,
25 and a star shape. Further, each selection item arranged in
46
each of the selection item arrangement circles DC, SC, and
PC is an example, and may be another selection item.
[0081]
In the example illustrated in Fig. 6, the slip search
5 screen is configured to include the three selection item
arrangement circle display regions 601, 602, and 603.
However, a single selection item arrangement circle display
region may be provided, and two or three or more selection
item arrangement circle display regions may be provided.
10 [0082]
In the example illustrated in Fig. 6, the selection
item arrangement circle display regions 601, 602, and 603
are provided to partially overlap one another, and the
selection items (selection item buttons) arranged in each
15 of the selection item arrangement circles DC, SC, and PC
displayed on each of the selection item arrangement circle
display regions 601, 602, and 603 are configured to have a
display form (for example, to differ in a color) that
differs according to each of the selection item arrangement
20 circles DC, SC, and PC. However, any method may be used to
the extent of the different display form, and a display
form may be changed by changing the shape or form.
[0083]
In the slip search screen, the user X selects each
25 selection item arranged in each of the selection item
47
arrangement circles DC, SC, and PC by the touch operation.
Specifically, the type of slip which is a search target is
selected by selecting any one of the selection items
(selection item buttons) D1 to D7 arranged in the processed
slip type selection item arrangement circle 5 DC. Further,
in the slip search screen, the user X selects the title of
a detailed item for narrowing-down by selecting any one of
the selection items (selection item buttons) S1 to S4
arranged in the detailed selection type selection item
10 arrangement circle SC. When any one of the selection items
(selection item buttons) S1 to S4 is selected, a detailed
search condition is designated by inputting a concrete
narrowing-down condition on the detailed narrowing-down
condition designation screen. Further, in the slip search
15 screen, the user X selects the type of business process
which is a search target by selecting any one of the
selection items (selection item buttons) P1 to P3 arranged
in the process type selection item arrangement circle PC.
Furthermore, in the slip search screen, the user X
20 designates a search keyword by inputting a keyword to be
used as the narrowing-down condition in the keyword input
region 604.
[0084]
In the present embodiment, when the user X selects
25 the item goods S4 among the selection items (selection item
48
buttons) S1 to S4 arranged in the detailed selection type
selection item arrangement circle SC in the slip search
screen, the mobile terminal 31 causes the detailed
narrowing-down condition designation screen including the
5 item goods input region to be displayed on the display unit
of the mobile terminal 31. The mobile terminal 31 reads a
code (for example, a QR code or a barcode) attached to
goods through the code reader (or a code reader function)
31a disposed in the mobile terminal 31 in response to the
10 user X's operation, and causes an item goods number
represented by the read code to be displayed on the item
goods input region. In the present embodiment, the item
goods number can be simply input using the code reader (or
a code reader function) 31a as described above.
15 [0085]
Further, in the slip search screen, the user X may
select or designate any one or more among the type of slip,
a detailed search condition, a business process which is a
search target, and a search keyword. Further, in the slip
20 search screen, the user X may make multiple selections or
multiple designations on each of the type of slip, a
detailed search condition, and a business process which is
a search target.
[0086]
25 When the search condition is selected or designated
49
in the slip search screen, the user X pushes down a search
button 605 through the touch operation.
[0087]
When the search button 605 is pushed down in a state
5 in which the search condition is selected or designated,
the mobile terminal 31 provides the mobile terminal
management server 10 with the selected or designated search
condition, and makes a search request (step S109).
[0088]
10 Upon receiving the search request, the mobile
terminal management server 10 searches for slip data
matching the search condition provided according to the
received provision request with reference to the process
flow data stored in the process flow data temporary storage
15 DB 16 (step S110).
[0089]
When the slip data is searched for according to the
search condition, the mobile terminal management server 10
generates search result list display screen information
20 representing the search result list display screen
displaying a list of searched slip data as a search result,
and transmits the search result list display screen
information to the mobile terminal 31 (step S111).
[0090]
25 Upon receiving the search result list display screen
50
information, the mobile terminal 31 causes the search
result list display screen represented by the received
search result list display screen information to be
displayed on the display unit included in the mobile
terminal 5 31 (step S112).
[0091]
Fig. 9 is an explanatory diagram illustrating an
example of the search result list display screen. As
illustrated in Fig. 9, the search result list display
10 screen is provided with a display region 701 for displaying
the search result, a back button B1 pushed down to return
to a previous screen, and an edit button B3 pushed down to
edit the search result. Further, when the process flow
type (inventory sale, direct shipping sale, and the like)
15 is selected by the touch operation in the search result
list display screen, the mobile terminal 31 transmits a
request of acquiring corresponding slip data to the mobile
terminal management server 10. The mobile terminal
management server 10 transmits the corresponding slip data
20 to the mobile terminal 31 with reference to the process
flow data stored in the process flow data temporary storage
DB 16 according to the slip data acquisition request. Then,
the mobile terminal 31 displays the received slip data on
the display screen of the display unit.
25 [0092]
51
When the user X performs an operation of ending
access such as an operation of ending a browser in the
search result list display screen (Y in step S113), the
mobile terminal 31 transmits a logout request to the mobile
terminal 5 management server 10 (step S114). Further, when
an operation of continuing access such as an operation of
pushing down the back button B1 is made (N in step S113),
the mobile terminal 31 causes the process to proceed to
step S108, and displays the slip search screen (see Fig. 6).
10 [0093]
When the search result list display screen
information is transmitted in step S111, the mobile
terminal management server 10 starts to measure a time
(standby time) in which an information exchange with the
15 mobile terminal 31 is not performed, and monitors whether
or not the standby time has elapsed a predetermined time
(for example, 5 minutes, 10 minutes, 30 minutes, and the
like) (has reached a predetermined time) (step S115).
[0094]
20 When the logout request is received during
measurement of the standby time (Y in step S116), the
mobile terminal management server 10 stops measuring the
standby time, and performs a logout process of releasing
the login state (step S117).
25 [0095]
52
Further, when it is determined that the standby time
has elapsed a predetermined time (Y in step S115), the
mobile terminal management server 10 ends measuring the
standby time, and performs a logout process of releasing
5 the login state (step S117).
[0096]
In the above-described way, it is determined whether
or not it is permitted to log in the mobile terminal
management server 10 according to the login request from
10 the mobile terminal 31 which becomes operable by the login
process. When it is permitted to log in, a process flow
data provision request is received, and a process of
providing the requested process flow data is executed.
[0097]
15 As described above, in the slip data providing
process, by setting the process flow data temporary storage
DB 16 as a search target, the mobile terminal 31 needs not
access a part (specifically, the business application
program DB 17 and the process flow DB 18a) functioning as
20 the core business server in the mobile terminal management
server 10. Thus, security can be improved when slip data
is provided to the mobile terminal 31. Further, the
process flow DB 18a may be set as the search target.
[0098]
25 In the above-described embodiment, report data
53
satisfying a search condition is searched for with
reference to the process flow table PT storing process flow
data including various kinds of data related to a process
flow including a plurality of business processes, the
process flow data 5 is data including status data, common
data, and process-specific data, the status data is data
representing a progress status of each of the plurality of
business processes included in the process flow, the common
data is data that is common to business processes included
10 in the same process flow, and the process-specific data is
data specific to each business process included in the same
process flow, and thus it is possible to reduce a
processing load required for a search of data in a business
system. In the business system of the related art, since
15 report data is managed by an individual data table for each
business process, when a search is performed, it is
necessary to refer to all data tables on a relevant
business process. For this reason, in a business system
dealing with a huge amount of data, a processing load
20 required for a search process is very large. In the abovedescribed
embodiment, the process flow data including the
status data, the common data, and the process-specific data
is constructed, and a search is performed with reference to
the process data table. Thus, since a plurality of data
25 tables are not referred to, it is possible to significantly
54
reduce a processing load required for a search of data in a
business system, and it is also possible to significantly
reduce a creation load of a processing program for a data
search.
5 [0099]
Fig. 10 is a flowchart illustrating an example of a
project management information provision process executed,
for example, by the mobile terminal management server 10 in
the report inquiry system 500 according to the present
10 embodiment. Here, the description will proceed in
connection with an example in which the mobile terminal
management server 10 provides the project management
information according to a request from the mobile terminal
31 used by the user X.
15 [0100]
In the project management information provision
process, the process of step S201 to step S205 is the same
as the process of step S101 to step S105 of the slip data
providing process, and a description thereof is not be made
20 herein.
[0101]
In step S205, the user X pushes down any one of the
menu buttons M1 to M6 by a touch operation (a contact
operation by a finger) in the menu screen (see Fig. 5)
25 displayed on the display unit of the mobile terminal 31.
55
In the present embodiment, the project button M5 is assumed
to be pushed down. The process when the other menu buttons
M1 to M4 and M6 are pushed down will not be made herein.
[0102]
When the project button M5 is pushed down 5 in the menu
screen, the mobile terminal 31 transmits information
representing that the project button M5 has been pushed
down to the mobile terminal management server 10 as the
menu selection result (step S206).
10 [0103]
Upon receiving the menu selection result representing
that the project button M5 has been pushed down, the
project management information provision processing unit
11b of the mobile terminal management server 10 transmits
15 project designation screen information representing a
project designation screen used to designate a project to
the mobile terminal 31 (step S207).
[0104]
Upon receiving the project designation screen
20 information, the mobile terminal 31 causes the project
designation screen represented by the received project
designation screen information to be displayed on the
display unit included in the mobile terminal 31 (step S208).
[0105]
25 Fig. 11 is an explanatory diagram illustrating an
56
example of the project designation screen. As illustrated
in Fig. 11, the project designation screen is provided with
a project number input region 801 through which a project
number is input and a decide button B5 pushed down to
decide the project number 5 input to the project number input
region 801.
[0106]
In the project designation screen, the user X
operates an input unit such as a keyboard displayed on the
10 screen, for example, as the project number input region 801
is touched, and inputs a project number of a corresponding
project to the project number input region 801. When the
input of the project ends, the user X pushes down the
decide button B5 by the touch operation. In this way, the
15 user X designates a project.
[0107]
When the decide button B5 is pushed down after the
project number is input, the mobile terminal 31 designates
the project by presenting the project number, and transmits
20 the project management information provision request to the
mobile terminal management server 10 (step S209).
[0108]
Upon receiving the project management information
provision request, the mobile terminal management server 10
25 searches for slip data associated with the project number
57
presented by the received provision request with reference
to the process flow data stored in the process flow data
temporary storage DB 16, and extracts the slip data related
to the designated project (a target project serving as a
project management information 5 generation target) from the
process flow table PT (step S210).
[0109]
Then, the mobile terminal management server 10
searches for data associated with the project number
10 presented by the received provision request with reference
to the project schedule data stored in the project DB 18b,
and extracts the project schedule data related to the
designated project (the target project serving as the
project management information generation target) from the
15 project table PJT (step S211).
[0110]
When the slip data and the project schedule data are
extracted, the mobile terminal management server 10
generates the project management information based on the
20 extracted slip data and the project schedule data (step
S212). In step S212, the mobile terminal management server
10 compares the extracted project schedule data with the
extracted slip data, generates the actual performance
accounting information representing an accounting progress
25 status in the project (specifically, for example,
58
calculates a ratio of a paid amount to a budget amount),
and generates business project management information
including the generated the actual performance accounting
information. In other words, in the present embodiment,
the mobile terminal management server 10 5 generates the
project management information including the business
schedule information represented by the extracted project
schedule data, the actual performance information
represented by the extracted slip data, and the generated
10 actual performance accounting information.
[0111]
When the project management information is generated,
the mobile terminal management server 10 generates the
project management information display screen information
15 representing the project management information display
screen for displaying the generated project management
information, and transmits the project management
information display screen information to the mobile
terminal 31 (step S213).
20 [0112]
Upon receiving the project management information
display screen information, the mobile terminal 31 causes
the project management information display screen
represented by the received project management information
25 display screen information to be displayed on the display
59
unit included in the mobile terminal 31 (step S214).
[0113]
Fig. 12 is an explanatory diagram illustrating an
example of the project management information display
screen. As illustrated in Fig. 5 12, the project management
information display screen is provided with a project
number display region 802 for displaying a project number
of a designated project, a project management information
display region 803 for displaying the project management
10 information, and a back button B6 pushed down to makes a
separate information provision request. In the present
embodiment, as illustrated in Fig. 12, a project
description number, a schedule (the business schedule
information represented by the project schedule data, and
15 specifically, information representing an accounting code,
an amount of money, or the like) on a corresponding
business, actual performance logistics information
(information representing the actual performance
represented by the extracted slip data, and specifically,
20 information representing a process flow type, item goods, a
quantity, an amount of money, and the like) on a
corresponding business, and the actual performance
accounting information (information representing the
progress status of the actual performance with respect to
25 the schedule, and specifically, information representing an
60
accounting code, an amount of money, and the like) are
displayed on the project management information display
region 803 as the project management information in
association with one another.
5 [0114]
When the user X performs an operation of ending
access such as an operation of ending a browser in the
project management information display screen (Y in step
S215), the mobile terminal 31 transmits a logout request to
10 the mobile terminal management server 10 (step S216).
Further, when an operation of continuing access such as an
operation of pushing down the back button B6 is performed
(N in step S215), the mobile terminal 31 causes the process
to proceed to step S208, and the project designation screen
15 to be displayed (see Fig. 11).
[0115]
When the project management information display
screen information is transmitted in step S213, the mobile
terminal management server 10 starts to measure a time
20 (standby time) in which an information exchange with the
mobile terminal 31 is not performed, and monitors whether
or not the standby time has elapsed a predetermined time
(for example, 5 minutes, 10 minutes, 30 minutes, and the
like) (has reached a predetermined time) (step S217).
25 [0116]
61
When the logout request is received during
measurement of the standby time (Y in step S218), the
mobile terminal management server 10 stops measuring the
standby time, and performs a logout process of releasing
the login state (step S2195 ).
[0117]
Further, when it is determined that the standby time
has elapsed a predetermined time (Y in step S217), the
mobile terminal management server 10 ends measuring the
10 standby time, and performs a logout process of releasing
the login state (step S219).
[0118]
In the above-described way, it is determined whether
or not it is permitted to log in the mobile terminal
15 management server 10 according to the login request from
the mobile terminal 31 which becomes operable by the login
process. When it is permitted to log in, a process flow
data provision request is received, and a process of
providing the requested process flow data is executed.
20 [0119]
In the above example, in the project management
information provision process, the slip data search target
is the process flow data temporary storage DB 16, but the
process flow DB 18a may be the search target.
25 [0120]
62
As described above, in the above-described embodiment,
the mobile terminal management server 10 that is a server
run by ERP and provides various kinds of data via the
communication network 40 according to the request from the
mobile terminals 31 to 3N 5 used by the users includes the
process flow table PT that stores the process flow data
including various kinds of data related to the process flow
including a plurality of business processes, the process
flow data is data including the project specifying data,
10 the status data, the common data, and the process-specific
data, the project specifying data is data capable of
specifying business projects to which the plurality of
business processes included in the process flow belong, the
status data is data representing the progress statuses of
15 the plurality of business processes included in the process
flow, the common data is data that is common to business
process included in the same process flow, and the processspecific
data is data specific to each business process
included in the same process flow, and the mobile terminal
20 management server 10 is configured to provide the business
project designation screen (the project designation screen)
for designating the business project (project) according to
the request from the mobile terminal 31, receive and accept
the business project information (for example, the project
25 number) representing the business project designated
63
through the business project designation screen from the
mobile terminal 31, search for process data related to a
plurality of business processes belonging to the business
project represented by the accepted business project
information with reference to the 5 process flow data stored
in the process flow table PT, generate the business project
management information (the project management information)
representing the progress status of the designated business
project based on the found process data, and provide the
10 generated business project management information to the
mobile terminal 31, and thus in the business system that
provides information about a report to the mobile
communication terminal (the mobile terminals 31 to 3N), it
is possible to reduce a processing load required for data
15 processing in the business system, and it is possible to
rapidly output the valid information (the project
management information).
[0121]
In other words, the process flow data includes the
20 project specifying data, and the business project
management information (the project management information)
is generated and provided according to the provision
request from the mobile terminal 31, and thus it is
possible to rapidly provide the valid information (the
25 project management information) capable of checking the
64
progress of a project.
[0122]
Further, the report data satisfying the search
condition is searched for with reference to the process
flow table PT 5 storing the process flow data including
various kinds of data related to the process flow including
a plurality of business processes, the process flow data is
data including the project specifying data, the status data,
the common data, and the process-specific data, the status
10 data is data representing the progress statuses of the
plurality of business processes included in the process
flow, the common data is data that is common to business
process included in the same process flow, and the processspecific
data is data specific to each business process
15 included in the same process flow, and thus it is possible
to reduce the processing load required for a data search in
the business system which is necessary to generate the
business project management information (the project
management information). In the business system of the
20 related art, since report data is managed by an individual
data table for each business process, when a search is
performed, it is necessary to refer to all data tables on a
relevant business process. For this reason, in a business
system dealing with a huge amount of data, a processing
25 load required for a search process is very large. In the
65
above-described embodiment, the process flow data including
the project specifying data, the status data, the common
data, and the process-specific data is constructed, a
search of information necessary for generating the business
5 project management information (the project management
information) is performed with reference to the process
data table, and thus since a plurality of data tables are
not referred to, it is possible to significantly reduce a
processing load required for a search of data necessary for
10 generating the business project management information (the
project management information) in a business system, and
it is also possible to significantly reduce a creation load
of a processing program for a data search.
[0123]
15 Further, in the above-described embodiment, the
project specifying data includes project identification
information uniquely identifying a business project and
business project description identification information
uniquely identifying a description of each business unit
20 configuring a business project, and thus it is possible to
specify a project and a business belonging to a project
with reference to the process flow data, and it is possible
to increase an existence value of the process flow data.
[0124]
25 Further, in the above-described embodiment, the
66
mobile terminal management server 10 is configured to
generate the business project management information (the
project management information) including the actual
performance information representing the actual business
performance of the designated 5 business project, and thus it
is possible to easily understand the actual business
performance of the corresponding project based on the
business project management information.
[0125]
10 Further, in the above-described embodiment, the
mobile terminal management server 10 includes the project
DB 18b storing the project schedule data representing the
business schedule of each business project, and is
configured to specify the project schedule data
15 representing the business schedule of the designated
business project with reference to the project schedule
data and generate the business project management
information (the project management information) including
the specified project schedule data, and thus it is
20 possible to easily understand the business schedule of the
corresponding project based on the business project
management information. Further, in the above-described
embodiment, the business project management information
(the project management information) may not include the
25 project schedule data.
67
[0126]
Further, in the above-described embodiment, the
mobile terminal management server 10 is configured to
compare the business schedule of the designated business
project with the actual business performance, generate 5 the
actual performance accounting information representing the
accounting progress status, and generate the business
project management information including the generated the
actual performance accounting information, and thus it is
10 possible to easily understand the progress status of the
corresponding project based on the business project
management information. Further, in the above-described
embodiment, the business project management information
(the project management information) may not include the
15 actual performance accounting information.
[0127]
Further, in the above-described embodiment, the
database (for example, the process flow DB 18a) is disposed
in the process flow data management server (for example,
20 the mobile terminal management server 10) that manages the
process flow data generated for each process flow, and the
process flow data management server is configured to
provide the report data searched for with reference to the
process flow data to the client according to the request
25 from the client (for example, the mobile terminals 31 to 3N
68
or the enterprise resource planning systems 100, 200, and
300). Thus, it is possible to construct a system in which
a processing load required to provide the report data is
reduced.
5 [0128]
Further, although not particularly mentioned in the
above-described embodiment, the mobile terminal management
server 10 executes the above-described processes (see Fig.
4 and Fig. 10) according to a processing program (a mobile
10 terminal management program) stored in a storage medium
equipped therein.
Industrial Applicability
[0129]
15 According to the present invention, it is useful in
reducing a processing load required for a data search and
in outputting valid information rapidly in a business
system (specifically, an ERP system) that provides
information about a report to a mobile communication
20 terminal.
Reference Signs List
[0130]
10 mobile terminal management server
25 20 relay
69
31 to 3N mobile terminals
40 communication network
51, 52, 53 communication network
100, 200, 300 enterprise resource planning system
110, 310 5 core business server
120, 220 DWH server
500 report inquiry system
70

CLAIMS
1. A mobile terminal management server that is a server
run by enterprise resource planning (ERP) and provides
5 various kinds of data via a communication network according
to a request from a mobile terminal used by a user,
comprising:
a process flow data storage unit that stores process
flow data including various kinds of data related to a
10 process flow including a plurality of business processes,
the process flow data including project specifying
data, status data, common data, and process-specific data,
the project specifying data specifying business
projects to which the plurality of business processes
15 included in the process flow belong,
the status data representing progress statuses of the
plurality of business processes included in the process
flow,
the common data being common to each business process
20 included in a same process flow, and
the process-specific data being specific to each
business process included in a same process flow;
a business project designation screen providing unit
that provides a business project designation screen for
25 designating a business project according to a request from
71
the mobile terminal;
a business project information accepting unit that
receives and accepts business project information
representing the business project designated through the
business project designation screen 5 from the mobile
terminal;
a process data search unit that searches for process
data related to a plurality of business processes belonging
to the business project represented by the business project
10 information accepted by the business project information
accepting unit with reference to the process flow data
stored in the process flow data storage unit;
a business project management information generating
unit that generates business project management information
15 representing a progress status of the designated business
project based on the process data searched for by the
process data search unit; and
a business project management information providing
unit that provides the business project management
20 information generated by the business project management
information generating unit to the mobile terminal.
2. The mobile terminal management server according to
claim 1,
25 wherein the project specifying data includes project
72
identification information uniquely identifying a business
project and business project description identification
information uniquely identifying a description of each
business unit configuring a business project.
5
3. The mobile terminal management server according to
claim 1 or 2,
wherein the business project management information
generating unit generates the business project management
10 information including actual performance information
representing an actual business performance of the
designated business project.
4. The mobile terminal management server according to
15 claim 3, further comprising a project schedule data storage
unit that stores project schedule data representing a
business schedule of each business project,
wherein the business project management information
generating unit specifies the project schedule data
20 representing the business schedule of the designated
business project with reference to the project schedule
data, and generates the business project management
information including the specified project schedule data.
25 5. The mobile terminal management server according to
73
claim 4,
wherein the business project management information
generating unit compares the business schedule of the
designated business project with the actual business
performance, 5 , generates actual performance accounting
information representing an accounting progress status, and
generates the business project management information
including the generated actual performance accounting
information.
10
6. A mobile terminal management program that operates
enterprise resource planning (ERP) and causes a mobile
terminal management server to execute a process of
providing various kinds of data via a communication network
15 according to a request from a mobile terminal used by a
user,
the mobile terminal management server comprising a
process flow data storage unit that stores process flow
data including various kinds of data related to a process
20 flow including a plurality of business processes,
the process flow data including project specifying
data, status data, common data, and process-specific data,
the project specifying data specifying business
projects to which the plurality of business processes
25 included in the process flow belong,
74
the status data representing progress statuses of the
plurality of business processes included in the process
flow,
the common data being common to business process
included in a same 5 process flow, and
the process-specific data being specific to each
business process included in a same process flow,
the mobile terminal management program causing the
mobile terminal management server to execute:
10 a business project designation screen providing
process of providing a business project designation screen
for designating a business project according to a request
from the mobile terminal;
a business project information accepting process of
15 receiving and accepting business project information
representing the business project designated through the
business project designation screen from the mobile
terminal;
a process data search process of searching for
20 process data related to a plurality of business processes
belonging to the business project represented by the
business project information accepted in the business
project information accepting process with reference to the
process flow data stored in the process flow data storage
25 unit;
75
a business project management information generating
process of generating business project management
information representing a progress status of the
designated business project based on the process data
searched for in the 5 process data search process; and
a business project management information providing
process of providing the business project management
information generated in the business project management
information generating process to the mobile terminal.