DESCRIPTION
MOBILE TERMINAL MANAGEMENT SERVER AND MOBILE TERMINAL MANAGEMENT
PROGRAM

Technical Field 5
[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 via a
communication network according to a request from a mobile 10
terminal used by a user, and a mobile terminal management program
installed in the mobile terminal management server.

Background Art
[0002] 15
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 core
business system in which this ERP is contained (an integrated
core business system, an ERP system), it is most often constructed 20
on a relational database, and design of an application program
that focuses on business processes is mostly made. Thus, it
is often operated without focusing on report output.
[0003]
For the purpose of processing the large amount of business 25
3
data at a high speed, analyzing the business data from various
angles, and outputting reports under such a situation, various
data warehouse systems that undertake a complementary role to
the core business system have been provided (see Patent
Literature 1). 5
[0004]
Further, report inquiry systems that are designed to 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). 10

Citation List
Patent Literature
[0005]
Patent Literature 1: JP 2002-312208 A 15
Patent Literature 2: JP 2003-323582 A
Patent Literature 3: JP 2007-200136 A

Summary of Invention
Technical Problem 20
[0006]
In the ERP system according to the related art, data
(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, 25
4
in the ERP system according to the related 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 5
to each table.
[0007]
Figs. 15(A) to 15(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 business flow 10
(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 process flow of "inventory sales," 15
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. 15(A) to 15(E).
[0008] 20
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 Figs. 15(A) to 15(E), a received order number 25
5
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 (process
data) related to each business process.
[0009] 5
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 another
corresponding process data for each input process. In other
words, for example, in the example of Figs. 15(A) to 15(E), when 10
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 received order number "A00001"
and a received order description number "0010" in the received
order table) specified by a received order number "A00001" and 15
a received order description number "0010" is registered to a
database included in the ERP system, it is necessary to register
the received order number "A00001" and the received order
description number "0010" to the shipping instruction table
together with a shipping instruction number specifying process 20
data, a shipping instruction description number, a type
representing the type of business process, and data (for example,
an 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 25
6
instruction." In this case, the same data (for example, an
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] 5
Then, similarly to when data is registered, in the 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 10
acquire data matching a search 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 15
related art, when various kinds of data stored in various 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 20
valid information by information processing.
[0012]
Particularly, when information is provided according to
a request from a mobile communication terminal (mobile terminal),
a rapid response speed is required, and thus the above problem 25
7
becomes remarkable.
[0013]
In order to solve the above problems, it is an object of
the present invention to reduce a processing load required for
data processing in a business system and rapidly output valid 5
information in a business system (an ERP system) that provides
information about a report to a mobile communication terminal
(mobile terminal).

Solution to Problem 10
[0014]
A mobile terminal management server of the present
invention is a mobile terminal management server that is a server
run by ERP and provides various kinds of data via a communication
network according to a request from a mobile terminal used by 15
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
process flow data including status data, common data, and
process-specific data, the status data representing progress 20
statuses of the plurality of business processes included in the
process flow, the common data being common to business processes
included in the same process flow, and the process-specific data
being specific to each business process included in the same
process flow, an aggregate description subject designation 25
8
screen providing unit that provides an aggregate description
subject designation screen used to designate an aggregate
description subject according to a request from the mobile
terminal, an aggregate description subject information
accepting unit that receives and accepts aggregate description 5
subject information representing the aggregate description
subject designated through the aggregate description subject
designation screen from the mobile terminal, a process data
search unit that searches for process data related to a plurality
of business processes for the aggregate description subject 10
represented by the aggregate description subject information
accepted through the aggregate description subject information
accepting unit with reference to the process flow data stored
in the process flow data storage unit, an aggregate description
information generating unit that generates aggregate 15
description information representing an aggregate description
for the designated aggregate description subject based on the
process data searched for through the process data search unit,
and an aggregate description information providing unit that
provides the aggregate description information generated by the 20
aggregate description 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 25
9
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 aggregate description subject may be a customer, the 5
aggregate description subject information accepting unit may
receive and accept customer information representing a customer
designated through the aggregate description subject
designation screen from the mobile terminal, the process data
search unit may search for process data in which a payment is 10
not made among bills for the customer represented by the customer
information, and the aggregate description information
generating unit may generate aggregate billing description
information representing an aggregate billing description in
which the designated customer is a billing destination. 15
[0017]
The aggregate billing description information may include
individual billing amounts and a total billing amount obtained
by adding the individual billing amounts.
[0018] 20
The aggregate description subject may be a vendor, the
aggregate description subject information accepting unit may
receive and accept vendor information representing a vendor
designated through the aggregate description subject
designation screen from the mobile terminal, the process data 25
10
search unit may search for process data in which a payment is
not made among bills from the vendor represented by the vendor
information, and the aggregate description information
generating unit may generate aggregate payment description
information representing an aggregate payment description in 5
which the designated vendor is a payment recipient.
[0019]
The aggregate payment description information may include
individual payment amounts and a total payment amount obtained
by adding the individual payment amounts. 10
[0020]
Further, a mobile terminal management program of the
present invention is a mobile terminal management program that
operates ERP and causes a mobile terminal management server to
execute a process of providing various kinds of data via a 15
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 data including various kinds of data related to a process
flow including a plurality of business processes, the process 20
flow data including status data, common data, and
process-specific data, the status data representing progress
statuses of the plurality of business processes included in the
process flow, the common data being common to business processes
included in the same process flow, and the process-specific data 25
11
being specific to each business process included in the same
process flow, and the mobile terminal management program causing
the mobile terminal management server to execute an aggregate
description subject designation screen providing process of
providing an aggregate description subject designation screen 5
used to designate an aggregate description subject according
to a request from the mobile terminal, an aggregate description
subject information accepting process of receiving and accepting
aggregate description subject information representing the
aggregate description subject designated through the aggregate 10
description subject designation screen from the mobile terminal,
a process data search process of searching for process data
related to a plurality of business processes for the aggregate
description subject represented by the aggregate description
subject information accepted in the aggregate description 15
subject information accepting process with reference to the
process flow data stored in the process flow data storage unit,
an aggregate description information generating process of
generating aggregate description information representing an
aggregate description for the designated aggregate description 20
subject based on the process data searched for in the process
data search process, and an aggregate description information
providing process of providing the aggregate description
information generated in the aggregate description information
generating process to the mobile terminal. 25
12

Advantageous Effects of Invention
[0021]
According to the present invention, it is possible to
reduce a processing load required for data processing in a 5
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 Description of Drawings 10
[0022]
Fig. 1 is a block diagram illustrating a configuration
example of a report inquiry system.
Fig. 2 is a block diagram illustrating a configuration
example of a mobile terminal management server. 15
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 slip
data providing process.
Fig. 5 is an explanatory diagram illustrating an example 20
of a menu screen.
Fig. 6 is an explanatory diagram illustrating an example
of a slip search screen.
Fig. 7 is an explanatory diagram illustrating an example
of a slip search screen. 25
13
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.
Fig. 9 is an explanatory diagram illustrating an example
of a search result list display screen. 5
Fig. 10 is a flowchart illustrating an example of an
aggregate information providing process.
Fig. 11 is an explanatory diagram illustrating an example
of a condition designation screen (an aggregate billing
statement). 10
Fig. 12 is an explanatory diagram illustrating an example
of an aggregate information (aggregate billing description
information) display screen.
Fig. 13 is an explanatory diagram illustrating an example
of a condition designation screen (an aggregate payment 15
statement).
Fig. 14 is an explanatory diagram illustrating an example
of an aggregate information (aggregate payment description
information) display screen.
Figs. 15(A) to 15(E) are explanatory diagrams for 20
describing an example of a table configuration in an ERP system
according to a related art.
Mode for Carrying Out the Invention
[0023]
Hereinafter, an embodiment of the present invention will 25
14
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 illustrated in Fig. 1, the report
inquiry system 500 includes a mobile terminal management server 5
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
enterprise resource planning system 300.
[0024] 10
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. The mobile terminal
management server 10 is connected with the enterprise resource
planning system 100, the enterprise resource planning system 15
200, and the enterprise resource planning system 300 via
communication networks 51, 52, and 53 such as a LAN (Local Area
Network) or a dedicated communication line, respectively.
Further, the mobile terminal or the enterprise resource planning
system may be configured to communicate with another mobile 20
terminal or another enterprise resource planning system via the
mobile terminal management server, or the mobile terminal or
the enterprise resource planning system may be configured not
to communicate with another mobile terminal or another enterprise
resource planning system. 25
15
[0025]
The enterprise resource planning system 100 includes 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. 5
The enterprise resource planning system 300 includes a core
business server 310 and a process flow DB 301.
[0026]
Each of the plurality of the enterprise resource planning
systems 100, 200, and 300 which differ in configuration fulfills 10
a functions of an enterprise resource 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 200 15
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 flow DB can also fulfill the function 20
of the enterprise resource planning system by storing process
flow data in the mobile terminal management server 10. Since
a well-known technique is used for the core business server or
the like included in each core business system, the following
description will be made using the enterprise resource planning 25
16
system 100 as an example.
[0027]
The core business server 110 is connected with the DWH
server 120 through a dedicated communication line.
[0028] 5
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 information). The core business server 10
110 is configured with a general information processing device
including an OS (Operating System) and a relational DB.
[0029]
Here, the report is the general term of books and a type
of slip. Further, the books denote one in which matters 15
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 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 20
representing only the slip data as report data will be described
as an example.
[0030]
The core business server 110 executes various kinds of
processing according to a business application program. 25
17
Examples of the business application program 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
program. 5
[0031]
The DWH server 120 is a server managed, for example, 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 10
respective items from among business data such as report data
accumulated in time series. Further, 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 15
kinds of data to a predetermined storage region. Further, the
DWH server 120 may be configured to extract data corresponding
to each storage region from a state of CSV format without carrying
out data format conversion.
[0032] 20
The process flow DB 101 is a storage medium that 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) 25
18
of the core business server 110. The process flow data will
be 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 converting 5
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 transfers a data file whose format is 10
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 which
is run by ERP and provides various kinds of data through a 15
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 managed by the system
administrator of the report inquiry system 500. 20
[0034]
Fig. 2 is a block diagram illustrating a configuration
example of the mobile terminal management server 10. As
illustrated in Fig. 2, the mobile terminal management server
10 includes a control unit 11 that performs various kinds of 25
19
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, 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 5
implement the function of the general core business server. The
other DB 10X has a portion which does not specifically 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 10
process of providing process flow data to the mobile terminals
31 to 3N, an aggregate billing description information provision
processing unit 11b that executes, for example, a process of
providing aggregate billing description information to the
mobile terminals 31 to 3N, and an aggregate payment description 15
information provision processing unit 11c that executes, for
example, a process of providing aggregate payment description
information to the mobile terminals 31 to 3N.
[0035]
The process flow data temporary storage DB 16 is a storage 20
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 intervals (for example, at one-day 25
20
intervals, at three-day 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 of the program stored in the business application 5
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 program.
[0037] 10
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 means of various
kinds of information processing using various kinds of programs
stored in the business application program DB 17. In the present 15
embodiment, the description will proceed in connection with an
example in which process flow data including various kinds of
data 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 20
will proceed in connection with an example in which the mobile
terminal management server 10 centrally manages process flow
data generated in each process flow 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, 25
21
data in which received order slip header information, received
order slip 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 5
slip number includes a received order number, a purchase order
number, a shipping number, an acceptance or delivery numbers,
a bill reference, a billing number, an accounting number, and
the like.).
[0038] 10
Further, the mobile terminal management server 10 may 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 15
same.
[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 20
the present embodiment includes a main key section, a project
specifying data section, a 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 25
22
data 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 flow (a series of process 5
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 process data can be defined. 10
[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 stored. In the present
embodiment, the main key section is configured with a process 15
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 (ID) of each process flow data. The main key
section is updated at the time of initial registration of process 20
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 corresponding
process data which belongs to a certain process flow but is not
registered yet is registered. Here, "update" is assumed to 25
23
include addition of data.
[0041]
Further, the "process flow number" is an identifier to
specify one process flow data (that is, a first column in the
process flow table PT illustrated in Fig. 3). The process flow 5
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 process flow data which is the same
in the type and the orderer of the process flow data.
[0042] 10
Further, the "process flow description number" is an
identifier specifying specific process flow data among 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 15
including process data representing that an order for a business
of the amount "1200" and "2600" is received from an orderer "T001"
by a 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 20
process flow.
[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 25
24
project specifying data section 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) 5
is added to 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] 10
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 description numbers associated with the same 15
project number 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 description number is 20
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 flow
data (or another process data) related to the process flow such 25
25
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 updated at the time of initial
registration of process flow data. 5
[0046]
The process flow number and the process flow description
number of another process flow related to the process flow are
stored in the reference number and the reference description
number, respectively. However, when there is no other process 10
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 reference key section (that is, the process
flow number and the process flow description number are stored
in the reference number and the reference description number, 15
respectively). Further, when the reference key section
represents another process data related to the process flow,
data specifying the type of process data is further stored in
the reference key section.
[0047] 20
The "type section" is a part in which type data which is
data representing the type of process flow such as 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 25
26
is not limited to inventory sales or sample shipping. Further,
it is assumed that a necessary 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, 5
two or more other types of process flows will be provided later
(see 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 10
of business processes included in the process flow) representing
the progress of the process flow 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 15
process needed 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," and "sales," process specific 20
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 state
set to "0"). 25
27
[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 data which
will be described later is input, specifically, when it is 5
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 "what all process specific data
corresponding to one business process is input" remains stored 10
in a predetermined storage region of the mobile terminal
management server 10 as the status change condition.
[0050]
In the present embodiment, since the process flow of a
different type is stored in the same table, a part that stores 15
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, a part storing
unnecessary process data becomes null data, and "0" is stored
in the status data corresponding to the null data. 20
[0051]
The "common data section" is a part in which common 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, a ship-to party, a customer, 25
28
and a vendor among pieces of process flow data is stored. The
common data section is updated at the time of initial registration
of process flow data.
[0052]
The "process-specific data section" is a part in which 5
process specific data which is data specific to each business
process included in the same process flow such as the received
order date or data (for example, text data representing a
precaution such as "arrival by delivery date" or "fragile goods
(handle with care)" registered in each business process among 10
pieces of process flow data is stored. The process specific
data section is updated for each business process. Thus, 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 15
is referred to as "common data."
[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. 20
[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 ship a product has been 25
29
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 customer
has completed an acceptance inspection and an ownership of a 5
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 recorded).
[0055] 10
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 quantity,
a color, a shape, and a quality)" or that "an ownership of an
asset is transferred when an acceptance inspection is completed." 15
Further, in financial accounting (or institutional accounting)
or on the ERP system, in order to explicitly specify a transfer
timing of an ownership of an asset, an event of "acceptance
inspection" is defined to be distinguished from delivery.
[0056] 20
The project DB 18b is a storage medium that stores project
schedule data representing a business schedule of 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, 25
30
the project schedule data in which information representing a
business schedule (for example, a schedule of a budget, a purchase,
received order, 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 5
be registered in the project table PJT.
[0057]
The DWH DB 19 is a storage medium that stores, for example,
aggregate information generated in the past based on the process
flow data. In the present embodiment, aggregate billing 10
description information, aggregate payment description
information, and the like which will be described later are
registered.
[0058]
The mobile terminal management server 10 has a function 15
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 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 20
present embodiment. In other words, the mobile terminal
management server 10 has a function as the core business server.
In other words, the mobile terminal management server 10 includes
an ERP engine.
[0059] 25
31
Even though not illustrated, in the present embodiment,
the mobile terminal management server 10 is 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 5
server, it is possible to provide information requested as the
enterprise resource planning system to the enterprise resource
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 10
planning system 200 including only the DWH server, and the
enterprise resource planning system 300 including only the DWH
server).
[0060]
Each of the mobile terminals 31 to 3N is an information 15
processing device, such as iPad (registered 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 20
deal with report data, such 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 the present 25
32
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) 31a to 3Na that read various kinds of codes 5
such as a quick response (QR) code (registered trademark),
respectively.
[0061]
In the present embodiment, each of the mobile terminals
31 to 3N has a function of communicating with the mobile terminal 10
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).
[0062] 15
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 example, at 2:00 am) when an update
is performed everyday) comes, the mobile terminal management 20
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 in a predetermined storage region of the process flow data
temporary storage DB 16, and updates storage information of the 25
33
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.
[0063]
Next, an operation of the report inquiry system 500 5
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 specially relate to
the present invention may not be made.
[0064] 10
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 system 500
according to the present embodiment. Here, the description will
proceed in connection with an example in which the mobile terminal 15
management server 10 provides the process flow data according
to a request from a mobile terminal 31 used by a user X.
[0065]
In the slip data providing process, first, the mobile
terminal 31 receives a login request by the user X's login 20
operation (step S101). The login operation refers to, for
example, an input operation of a previously set secret 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. 25
34
[0066]
In a state in which the user X logs in the mobile 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 5
example, a user ID and a 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 login 10
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 various kinds of screens. 15
[0067]
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 determination may be
made based on an ID, a password, an electronic certificate, and 20
the like.
[0068]
When it is determined that it is permitted to login (Y
in step S103), the mobile terminal management server 10 sets
the mobile terminal 31 to a login state. When the mobile terminal 25
35
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 that it is not permitted to login (N in step S103),
the mobile terminal management server 10 ends the slip data 5
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 server 10
performs a process of notifying the mobile terminal 31 of login
refusal. 10
[0069]
Upon receiving the menu screen information, the mobile
terminal 31 causes the menu screen represented by the received
menu screen information to be displayed on the display unit
included in the mobile terminal 31 (step S105). 15
[0070]
Fig. 5 is an explanatory diagram illustrating an example
of a menu screen. As illustrated in Fig. 5, a menu arrangement
circle display region 501 is provided on the menu screen. A
menu arrangement circle MC in which menu buttons M1 to M6 on 20
which a plurality of selectable menu names are displayed are
arranged substantially on the circumference thereof is displayed
on the menu arrangement circle display region 501. Further,
a title display region MA on which the title of the menu arrangement
circle MC disposed on the central region of the circle formed 25
36
by the menu arrangement circle MC is displayed is provided on
the menu arrangement circle display region 501 as illustrated
in Fig. 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 5
M3 pushed down to input expense, a master registration button
M4 pushed down to register a master, an aggregate billing button
M5 pushed down, for example, to make an aggregate billing
description information provision request, and an aggregate
payment button M6 pushed down to make an aggregate payment 10
description information provision request.
[0071]
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 15
touch operation (a contact operation by a finger). In the present
embodiment, the slip search button M1 is 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.
[0072] 20
When the slip search button M1 is pushed down in the menu
screen, the mobile terminal 31 transmits information
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). 25
37
[0073]
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 5
representing the slip search screen for designating a slip search
condition to the mobile terminal 31 (step S107).
[0074]
Upon receiving the slip search screen information, the
mobile terminal 31 causes the slip search screen represented 10
by the received slip search screen information to be displayed
on the display unit included in the mobile terminal 31 (step
S108).
[0075]
Fig. 6 is an explanatory diagram illustrating an example 15
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 plurality of selection items 20
selectable to designate a 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
arrangement circles DC, SC, and PC, a processed slip type 25
38
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 selectably displayed,
and a process type selection item arrangement circle PC in which 5
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 circle display region 601 to display the processed
slip type selection item arrangement circle DC, a detailed 10
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 item
arrangement circle display region 603 to display the process
type selection item arrangement circle PC are provided. 15
[0076]
The processed slip type selection item arrangement circle
DC is provided with seven types of selection items (selection
item buttons) to select a slip, which are arranged substantially
on the circumference thereof. That is, the processed slip type 20
selection item arrangement circle DC is provided with a received
order button D1 to 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 25
39
button D4 to designate a delivery slip as the 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 5
button DA on 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 buttons) D1 10
to D7 (by selecting one or more buttons).
[0077]
The detailed selection type selection item arrangement
circle SC is provided with four types of selection items
(selection item buttons) to select detailed narrowing-down 15
condition items, which are arranged 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 designate a vendor as the search condition, 20
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
selection" is displayed is arranged on the central region of 25
40
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 narrowing-down condition
designation screen (not illustrated) to designate a concrete 5
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 item goods number when the item goods button S4 is selected,
and the like) can be designated through the detailed 10
narrowing-down condition designation screen. The slip
satisfying the designated narrowing-down condition can be
searched for by selecting the concrete narrowing-down condition
(one or more concrete narrowing-down conditions may be selected).
[0078] 15
The process type selection item arrangement circle PC is
provided with three types of selection items (selection 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 20
with a production button P1 to designate "production" in the
business process as the search 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 25
41
display button PA on which a classification name "process" is
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 5
item buttons) P1 to P3 (one or more selection item buttons may
be selected).
[0079]
In the present embodiment, when the classification display
button DA, SA, or PA is pushed down, a rendering operation of 10
rotating the corresponding selection item arrangement circle
DC, SC, or PC is executed. In other 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 15
search screen so that a 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 20
operation 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 of causing a plurality of 25
42
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 operation by the user X (an operation of touching a portion 5
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 button DA, SA, or PA is pushed
down again, it is desirable to end the selection item rotation 10
rendering operation.
[0080]
Since the selection item rotation rendering operation is
performed as described above, as illustrated in Fig. 8, it is
unnecessary to arrange all of the selection item arrangement 15
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 be sequentially displayed by
rotating the selection item arrangement circles DC, SC, and PC. 20
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 of each selection item can be increased. Further, when
the screen size is large, a configuration capable of 25
43
simultaneously displaying all of the selection items within one
screen may be provided.
[0081]
In present embodiment, the selection items arranged in
the selection item arrangement circles DC, SC, and PC are 5
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, and a star shape.
Further, each selection item arranged in each of the selection
item arrangement circles DC, SC, and PC is an example, and may 10
be another selection item.
[0082]
In the example illustrated in Fig. 6, the slip search screen
is configured to include the three selection item arrangement
circle display regions 601, 602, and 603. However, a single 15
selection item arrangement circle display region may be provided,
and two or three or more selection item arrangement circle display
regions may be provided.
[0083]
In the example illustrated in Fig. 6, the selection item 20
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 of the selection item
arrangement circles DC, SC, and PC displayed on each of the
selection item arrangement circle display regions 601, 602, and 25
44
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 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. 5
[0084]
In the slip search screen, the user X selects each selection
item arranged in each of the selection item 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 10
one of the selection items (selection item buttons) D1 to D7
arranged in the processed slip type selection item arrangement
circle 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 15
S4 arranged in the detailed selection type selection item
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 20
screen. Further, in the slip search 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 designates 25
45
a search keyword by inputting a keyword to be used as the
narrowing-down condition in the keyword input region 604.
[0085]
In the present embodiment, when the user X selects the
item goods S4 among the selection items (selection item buttons) 5
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 item goods input region to be
displayed on the display unit of the mobile terminal 31. The 10
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 user X's operation, and causes an item goods
number represented by the read code to be displayed on the item 15
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.
[0086]
Further, in the slip search screen, the user X may select 20
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 search screen, the
user X may make multiple selections or multiple designations
on each of the type of slip, a detailed search condition, and 25
46
a business process which is a search target.
[0087]
When the search condition is selected or designated in
the slip search screen, the user X pushes down a search button
605 through the touch operation. 5
[0088]
When the search button 605 is pushed down in a state 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 10
search request (step S109).
[0089]
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 15
with reference to the process flow data stored in the process
flow data temporary storage DB 16 (step S110).
[0090]
When the slip data is searched for according to the search
condition, the mobile terminal management server 10 generates 20
search result list display screen information 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). 25
47
[0091]
Upon receiving the search result list display screen
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 5
unit included in the mobile terminal 31 (step S112).
[0092]
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 screen is provided with 10
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) is selected by the touch operation in the search 15
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 to the mobile
terminal 31 with reference to the process flow data stored in 20
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.
[0093] 25
48
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 management
server 10 (step S114). Further, when an operation of continuing 5
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).
[0094] 10
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 mobile terminal 31 is not performed,
and monitors whether or not the standby time has elapsed a 15
predetermined time (for example, 5 minutes, 10 minutes, 30
minutes, and the like) (has reached a predetermined time) (step
S115).
[0095]
When the logout request is received during measurement 20
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).
[0096] 25
49
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 the login state (step
S117). 5
[0097]
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 the mobile terminal
31 which becomes operable by the login process. When it is 10
permitted to log in, a process flow data provision request is
received, and a process of providing the requested process flow
data is executed.
[0098]
As described above, in the slip data providing process, 15
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 the core business server
in the mobile terminal management server 10. Thus, security 20
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.
[0099]
In the above-described embodiment, report data satisfying 25
50
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 is data including status data,
common data, and process-specific data, the status data is data 5
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 in the
same process flow, and the process-specific data is data specific
to each business process included in the same process flow, and 10
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 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 15
process. For this reason, in a business system dealing with
a huge amount of data, a processing load required for a search
process is very large. In the above-described embodiment, the
process flow data including the status data, the common data,
and the process-specific data is constructed, and a search is 20
performed with reference to the process data table. 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 in a business system, and it is also possible to
significantly reduce a creation load of a processing program 25
51
for a data search.
[0100]
Fig. 10 is a flowchart illustrating an example of an
aggregate information providing process executed, for example,
by the mobile terminal management server 10 in the report inquiry 5
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 aggregate
information (the aggregate billing description information and
the aggregate payment description information) according to a 10
request from the mobile terminal 31 used by the user X.
[0101]
In the aggregate information providing 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, 15
and a description thereof is herein omitted.
[0102]
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) displayed on the display 20
unit of the mobile terminal 31. In the present embodiment, the
aggregate billing button M5 or the aggregate payment button M6
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.
[0103] 25
52
When the aggregate billing button M5 is pushed down in
the menu screen, the mobile terminal 31 transmits a menu selection
result representing that the aggregate billing button M5 has
been pushed down to the mobile terminal management server 10
(step S206). 5
[0104]
Upon receiving the menu selection result representing that
the aggregate billing button M5 has been pushed down, the
aggregate billing description information provision processing
unit 11b of the mobile terminal management server 10 transmits 10
condition designation screen information representing a
condition designation screen used to designate a customer of
a billing destination to the mobile terminal 31 (step S207).
[0105]
Upon receiving the condition designation screen 15
information designating the customer, the mobile terminal 31
causes the condition designation screen used to designate the
customer represented by the received condition designation
screen information to be displayed on the display unit included
in the mobile terminal 31 (step S208). 20
[0106]
Fig. 11 is an explanatory diagram illustrating an example
of the condition designation screen used to designate a customer.
As illustrated in Fig. 11, the condition designation screen is
provided with a customer input region 801 for inputting a customer, 25
53
a decide button B5 used to decide a customer input to the customer
input region 801, and the like.
[0107]
In the condition designation screen, the user X operates
an input unit such as a keyboard displayed on the screen, for 5
example, as the customer input region 801 is touched, and inputs
a customer to the customer input region 801. When the input
of the customer ends, the user X pushes down the decide button
B5 by the touch operation. In this way, the user X designates
the customer. 10
[0108]
When the decide button B5 is pushed down after the customer
is input, the mobile terminal 31 presents customer information
representing the designated customer to the mobile terminal
management server 10, and transmits the aggregate billing 15
description information provision request (step S209).
[0109]
Upon receiving the aggregate billing description
information provision request, the mobile terminal management
server 10 searches for slip data (for example, data in which 20
a date is not input to a payment date among pieces of data in
which a date is input to a bill issue date of the process-specific
data section) in which a bill has been issued but a payment is
not made yet before a due date (that is set to a customer master
stored in the other DB 19, for example) from among pieces of 25
54
slip data associated with a customer represented by the customer
information presented according to the received provision
request with reference to the process flow data stored in the
process flow data temporary storage DB 16, and extracts slip
data (slip data necessary to generate the aggregate billing 5
description information) related to billing for the designated
customer from the process flow table PT (step S210).
[0110]
When the slip data is extracted, the mobile terminal
management server 10 generates the aggregate billing description 10
information based on the extracted slip data (step S211). In
step S211, the mobile terminal management server 10 allocates
an aggregate billing description number uniquely identifying
a currently generated aggregate billing description, calculates
a total amount by adding non-paid billing amounts represented 15
by the extracted slip data, and generates the aggregate billing
description information including individual amount
information representing each billing amount, total amount
information representing a total amount, and an allocated
aggregate billing description number. 20
[0111]
Further, the mobile terminal management server 10
registers the generated aggregate billing description
information to an aggregate billing description table of the
DWH DB 19. In step S211, the mobile terminal management server 25
55
10 may generate current aggregate billing description
information using the aggregate billing description information
generated in the past with reference to the aggregate billing
description table.
[0112] 5
When the aggregate billing description information is
generated, the mobile terminal management server 10 generates
aggregate billing description information display screen
information representing an aggregate billing description
information display screen for displaying the generated 10
aggregate billing description information, and transmits the
aggregate billing description information display screen
information to the mobile terminal 31 (step S212).
[0113]
Upon receiving the aggregate billing description 15
information display screen information, the mobile terminal 31
causes the aggregate billing description information display
screen represented by the received aggregate billing description
information display screen information to be displayed on the
display unit included in the mobile terminal 31 (step S213). 20
[0114]
Fig. 12 is an explanatory diagram illustrating an example
of the aggregate information (aggregate billing description
information) display screen. As illustrated in Fig. 12, the
aggregate billing description information display screen is 25
56
provided with an aggregate billing description number display
region 902 in which an aggregate billing description number
allocated by the mobile terminal management server 10 is
displayed, a customer display region 903 in which a customer
designated by the user X is displayed, an individual billing 5
information display region 904 in which individual billing
information is displayed, a total billing amount display region
905 in which a total billing amount is displayed, and a back
button B6 pushed down to make a separate information provision
request. In the present embodiment, as illustrated in Fig. 12, 10
a process flow number, a process flow description number, and
an amount are displayed on the individual billing information
display region 904 in association with one another.
[0115]
Meanwhile, when the aggregate payment button M6 is pushed 15
down in the menu screen, the mobile terminal 31 transmits a menu
selection result representing that the aggregate payment button
M6 has been pushed down to the mobile terminal management server
10 (step S206).
[0116] 20
Upon receiving the menu selection result representing that
the aggregate payment button M6 has been pushed down, the
aggregate payment description information provision processing
unit 11c of the mobile terminal management server 10 transmits
the condition designation screen information representing the 25
57
condition designation screen used to designate a vendor serving
as a payment recipient to the mobile terminal 31 (step S207).
[0117]
Upon receiving the condition designation screen
information for designating the vendor, the mobile terminal 31 5
causes the condition designation screen for designating the
vendor represented by the received condition designation screen
information to be displayed on the display unit included in the
mobile terminal 31 (step S208).
[0118] 10
Fig. 13 is an explanatory diagram illustrating an example
of the condition designation screen for designating the vendor.
As illustrated in Fig. 13, the condition designation screen is
provided with a vendor input region 802 for inputting a vendor,
a decide button B8 pushed down to decide the vendor input to 15
the vendor input region 802, and the like.
[0119]
In the condition designation screen, the user X operates
an input unit such as a keyboard displayed on the screen, for
example, as the vendor input region 802 is touched, and inputs 20
a vendor to the vendor input region 802. When the input of the
vendor ends, the user X pushes down the decide button B8 by the
touch operation. In this way, the user X designates the vendor.
[0120]
When the decide button B8 is pushed down after the vendor 25
58
is input, the mobile terminal 31 presents vendor information
representing the designated vendor to the mobile terminal
management server 10, and transmits the aggregate payment
description information provision request (step S209).
[0121] 5
Upon receiving the aggregate payment description
information provision request, the mobile terminal management
server 10 searches for slip data (for example, a date is not
input to a remittance date among pieces of data in which a date
is input to a bill issue date of the process-specific data section) 10
in which a bill has been issued but a remittance is not made
yet before a due date (that is set to a master stored in the
other DB 19, for example) of a company to which the user X belongs
from among pieces of slip data associated with the vendor provided
by the vendor information presented according to the received 15
provision request with reference to the process flow data stored
in the process flow data temporary storage DB 16, and extracts
slip data (slip data necessary to generate the aggregate payment
description information) related to the payment to the designated
vendor from the process flow table PT (step S210). 20
[0122]
When the slip data is extracted, the mobile terminal
management server 10 generates the aggregate payment description
information based on the extracted slip data (step S211). In
step S211, the mobile terminal management server 10 allocates 25
59
an aggregate payment description number uniquely identifying
a currently generated aggregate payment description, calculates
a total amount by adding non-remitted unpaid amounts represented
by the extracted slip data, and generates aggregate payment
description information including individual amount 5
information representing each payment amount, total amount
information representing a total amount, and an allocated
aggregate payment description number.
[0123]
Further, the mobile terminal management server 10 10
registers the generated aggregate payment description
information to an aggregate payment description table of the
DWH DB 19. In step S211, the mobile terminal management server
10 may generate current aggregate payment description
information using the aggregate payment description information 15
generated in the past with reference to the aggregate payment
description table.
[0124]
When the aggregate payment description information is
generated, the mobile terminal management server 10 generates 20
aggregate payment description information display screen
information representing an aggregate payment description
information display screen for displaying the generated
aggregate payment description information to the mobile terminal
31 (step S212). 25
60
[0125]
Upon receiving the aggregate payment description
information display screen information, the mobile terminal 31
causes the aggregate payment description information display
screen represented by the received aggregate payment description 5
information display screen information to be displayed on the
display unit included in the mobile terminal 31 (step S213).
[0126]
Fig. 14 is an explanatory diagram illustrating an example
of the aggregate information (aggregate payment description 10
information) display screen. As illustrated in Fig. 14, the
aggregate payment description information display screen is
provided with an aggregate payment description number display
region 912 in which the aggregate payment description number
allocated by the mobile terminal management server 10 is 15
displayed, a vendor display region 913 in which a vendor
designated by the user X is displayed, an individual payment
information display region 914 in which individual payment
information is displayed, a total payment amount display region
915 in which a total payment amount is displayed, and a back 20
button B9 pushed down to make the separate information provision
request. In the present embodiment, as illustrated in Fig. 14,
a process flow number, a process flow description number, and
an amount are displayed on the individual payment information
display region 914 in association with one another. 25
61
[0127]
When the user X performs an operation for ending access
such as an operation of ending a browser in the aggregate
information display screen (Y in step S214), the mobile terminal
31 transmits the logout request to the mobile terminal management 5
server 10 (step S215). Further, when an operation for continuing
access such as an operation of pushing down the back button B7
or B9 is performed (N in step S214), the mobile terminal 31 causes
the process to proceed to step S205, and displays the menu screen
(see Fig. 5). 10
[0128]
When the aggregate information display screen information
is transmitted in step S212, the mobile terminal management
server 10 starts to measure a time (standby time) in which an
information exchange with the mobile terminal 31 is not performed, 15
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
S216).
[0129] 20
When the logout request is received during measurement
of the standby time (Y in step S217), the mobile terminal
management server 10 stops measuring the standby time, and
performs a logout process of releasing the login state (step
S218). 25
62
[0130]
Further, when it is determined that the standby time has
elapsed a predetermined time (Y in step S216), the mobile terminal
management server 10 ends measuring the standby time, and
performs a logout process of releasing the login state (step 5
S218).
[0131]
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 the mobile terminal 10
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.
[0132] 15
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.
[0133] 20
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 used by the users includes the process flow table PT 25
63
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 status
data, the common data, and the process-specific data, the status
data is data representing the progress statuses of the plurality 5
of business processes included in the process flow, the common
data is data that is common to business processes included in
the same process flow, and the process-specific data is data
specific to each business process included in the same process
flow, and the mobile terminal management server 10 is configured 10
to provide an aggregate description subject designation screen
(a condition designation screen) for designating an aggregate
description subject (a customer and a vendor) according to a
request from the mobile terminal 31, receive and accept aggregate
description subject information representing the aggregate 15
description subject designated through the aggregate
description subject designation screen, search for process data
related to a plurality of business processes for the aggregate
description subject represented by the accepted aggregate
description subject information with reference to the process 20
flow data stored in the process flow table PT, generate aggregate
description information (the aggregate billing description
information and the aggregate payment description information)
representing an aggregate description for the designated
aggregate description subject based on the searched process data, 25
64
and provide the generated aggregate description information to
the mobile terminal 31, and thus in the business system that
provides information related to a report to the mobile
communication terminal (the mobile terminals 31 to 3N), it is
possible to reduce a processing load required for data processing 5
in the business system and rapidly output valid information (the
aggregate description information (the aggregate billing
description information and the aggregate payment description
information)).
[0134] 10
Report data satisfying a search condition is searched for
with reference to the process flow table PT storing the process
flow data including various kinds of data related to the process
flow including a plurality of business processes, the aggregate
description information (the aggregate billing description 15
information and the aggregate payment description information)
is generated and provided, the process flow data is data including
the project specifying data, the status data, the common data,
and the process-specific data, the status data is data
representing the progress statuses of the plurality of business 20
processes included in the process flow, the common data is data
that is common to business processes included 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 data 25
65
search in a business system which is necessary for generating
the aggregate description information. In the business system
of the 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 5
process. For this reason, in a business system dealing with
a huge amount of data, a processing load required for a search
process is very large. In the above-described embodiment, the
process flow data including the status data, the common data,
and the process-specific data is constructed, a search of 10
information necessary for generating the aggregate description
information (the aggregate billing description information and
the aggregate payment description information) is performed with
reference to the process data table, and thus it is unnecessary
to refer to a plurality of data tables, and it is possible to 15
significantly reduce a processing load required for a search
of data in a business system which is necessary for generating
the aggregate description information and significantly reduce
a creation load of a processing program for a data search.
[0135] 20
In the above-described embodiment, when the aggregate
description subject is a customer, and the mobile terminal
management server 10 is configured to receive and accept customer
information representing a customer designated through the
aggregate description subject designation screen (see Fig. 11) 25
66
from the mobile terminal 31, search for process data in which
a payment is not made among bills to the customer represented
by the customer information, and generate the aggregate billing
description information representing the aggregate billing
description in which the designated customer is the billing 5
destination, in the business system that provides information
related to a report to the mobile communication terminal (the
mobile terminals 31 to 3N), it is possible to reduce a processing
load required for data processing in the business system and
rapidly output the aggregate billing description information 10
as the valid information.
[0136]
Further, in the above-described embodiment, when the
aggregate description subject is a vendor, the mobile terminal
management server 10 is configured to receive and accept vendor 15
information representing a vendor designated through the
aggregate description subject designation screen (see Fig. 13)
from the mobile terminal 31, search for process data in which
a payment is not made among bills from the vendor represented
by the vendor information, and generate the aggregate payment 20
description information representing the aggregate payment
description in which the designated vendor is the payment
recipient, in the business system that provides information
related to a report to the mobile communication terminal (the
mobile terminals 31 to 3N), it is possible to reduce a processing 25
67
load required for data processing in the business system and
rapidly output the aggregate payment description information
as the valid information.
[0137]
Further, in the above-described embodiment, the database 5
(for example, the process flow DB 18a) is disposed in the process
flow data management server (for example, 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 10
searched for with reference to the process flow data to the client
according to the request from the client (for example, the mobile
terminals 31 to 3N 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 15
is reduced.
[0138]
Further, although not particularly mentioned in the
above-described embodiment, the mobile terminal management
server 10 executes the above-described processes (see Fig. 4 20
and Fig. 10) according to a processing program (a mobile terminal
management program) stored in a storage medium equipped therein.

Industrial Applicability
[0139] 25
68
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 terminal. 5

Reference Signs List
[0140]
10 mobile terminal management server
20 relay 10
31 to 3N mobile terminals
40 communication network
51, 52, 53 communication network
100, 200, 300 enterprise resource planning system
110, 310 core business server 15
120, 220 DWH server
500 report inquiry system
69

CLAIMS

1. A mobile terminal management server that is a server run
by enterprise resource planning (ERP) and provides various kinds
of data via a communication network according to a request from 5
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 process flow
including a plurality of business processes,
the process flow data including status data, common data, 10
and process-specific data,
the status data representing progress statuses of the
plurality of business processes included in the process flow,
the common data being common to business processes included
in the same process flow, and 15
the process-specific data being specific to each business
process included in the same process flow;
an aggregate description subject designation screen
providing unit that provides an aggregate description subject
designation screen used to designate an aggregate description 20
subject according to a request from the mobile terminal;
an aggregate description subject information accepting
unit that receives and accepts aggregate description subject
information representing the aggregate description subject
designated through the aggregate description subject 25
70
designation screen from the mobile terminal;
a process data search unit that searches for process data
related to a plurality of business processes for the aggregate
description subject represented by the aggregate description
subject information accepted through the aggregate description 5
subject information accepting unit with reference to the process
flow data stored in the process flow data storage unit;
an aggregate description information generating unit that
generates aggregate description information representing an
aggregate description for the designated aggregate description 10
subject based on the process data searched for through the process
data search unit; and
an aggregate description information providing unit that
provides the aggregate description information generated by the
aggregate description information generating unit to the mobile 15
terminal.

2. The mobile terminal management server according to claim
1,
wherein the aggregate description subject is a customer, 20
the aggregate description subject information accepting
unit receives and accepts customer information representing a
customer designated through the aggregate description subject
designation screen from the mobile terminal,
the process data search unit searches for process data 25
71
in which a payment is not made among bills for the customer
represented by the customer information, and
the aggregate description information generating unit
generates aggregate billing description information
representing an aggregate billing description in which the 5
designated customer is a billing destination.

3. The mobile terminal management server according to claim
2,
wherein the aggregate billing description information 10
includes individual billing amounts and a total billing amount
obtained by adding the individual billing amounts.

4. The mobile terminal management server according to claim
1, 15
wherein the aggregate description subject is a vendor,
the aggregate description subject information accepting
unit receives and accepts vendor information representing a
vendor designated through the aggregate description subject
designation screen from the mobile terminal, 20
the process data search unit searches for process data
in which a payment is not made among bills from the vendor
represented by the vendor information, and
the aggregate description information generating unit
generates aggregate payment description information 25
72
representing an aggregate payment description in which the
designated vendor is a payment recipient.

5. The mobile terminal management server according to claim
4, 5
wherein the aggregate payment description information
includes individual payment amounts and a total payment amount
obtained by adding the individual payment amounts.

6. A mobile terminal management program that operates 10
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 according to a request from
a mobile terminal used by a user,
the mobile terminal management server comprising a process 15
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 process flow data including status data, common data,
and process-specific data, 20
the status data representing progress statuses of the
plurality of business processes included in the process flow,
the common data being common to business processes included
in the same process flow, and
the process-specific data being specific to each business 25
73
process included in the same process flow,
the mobile terminal management program causing the mobile
terminal management server to execute:
an aggregate description subject designation screen
providing process of providing an aggregate description subject 5
designation screen used to designate an aggregate description
subject according to a request from the mobile terminal;
an aggregate description subject information accepting
process of receiving and accepting aggregate description subject
information representing the aggregate description subject 10
designated through the aggregate description subject
designation screen from the mobile terminal;
a process data search process of searching for process
data related to a plurality of business processes for the
aggregate description subject represented by the aggregate 15
description subject information accepted in the aggregate
description subject information accepting process with
reference to the process flow data stored in the process flow
data storage unit;
an aggregate description information generating process 20
of generating aggregate description information representing
an aggregate description for the designated aggregate
description subject based on the process data searched for in
the process data search process; and
an aggregate description information providing process 25
74
of providing the aggregate description information generated
in the aggregate description information generating process to
the mobile terminal.