2
DESCRIPTION
MOBILE TERMINAL MANAGEMENT SERVER AND MOBILE TERMINAL
MANAGEMENT PROGRAM
Technical 5 Field
[0001]
The present invention relates to a mobile terminal
management server which is a server run by enterprise
resource planning (ERP) and provides various kinds of data
10 via a communication network according to a request from a
mobile terminal used by a user, and a mobile terminal
management program installed in the mobile terminal
management server.
15 Background Art
[0002]
Heretofore, one so-called ERP (Enterprise Resource
Planning) has become mainstream as package software for
establishing a core business system for a company. In a
20 core business system in which this ERP is contained (an
integrated core business system, an ERP system), it is most
often constructed on a relational database, and design of
an application program that focuses on business processes
is mostly made. Thus, it is often operated without
25 focusing on report output.
3
[0003]
For the purpose of processing the large amount of
business data at a high speed, analyzing the business data
from various angles, and outputting reports under such a
5 situation, various data warehouse systems that undertake a
complementary role to the core business system have been
provided (see Patent Literature 1).
[0004]
Further, report inquiry systems that are designed to
10 output a report and provide information about a report or
the like to a mobile communication terminal (a mobile
terminal) have been proposed (see Patent Literatures 2 and
3).
15 Citation List
Patent Literature
[0005]
Patent Literature 1: JP 2002-312208 A
Patent Literature 2: JP 2003-323582 A
20 Patent Literature 3: JP 2007-200136 A
Summary of Invention
Technical Problem
[0006]
25 In the ERP system according to the related art, data
4
(including data input by the user and data calculated from
various kinds of data) acquired in each business process is
registered to each dedicated data table (table) and managed.
In other words, in the ERP system according to the related
5 art, a table to be updated differs according to an input
process such as a received order or shipping instruction.
Here, the "input process" refers to a process of inputting
various kinds of data acquired (decided) by an
administrator of the ERP system in each business process to
10 each table.
[0007]
Figs. 13(A) to 13(E) are explanatory diagrams for
describing an example of a table configuration in the ERP
system according to the related art. For example, when a
15 business flow (a process flow) configured with a plurality
of business processes represents "inventory sales," there
are five input processes of a received order, shipping
instruction, delivery, acceptance inspection, and sales.
In this case, as a table storing data related to the
20 process flow of "inventory sales," five tables of a
received order table, a shipping instruction table, a
delivery table, an acceptance inspection table, and a sales
table are used in the respective input processes, for
example, as illustrated in Figs. 13(A) to 13(E).
25 [0008]
5
In other words, in the ERP system according to the
related art, a table to be updated differs according to an
input process. For this reason, a correspondence between a
plurality of business processes belonging to a single
process flow is made by assigning an identifier (in Figs5 .
13(A) to 13(E), a received order number and a received
order description in the shipping instruction table, a
shipping instruction number and a shipping instruction
description in the delivery table, or the like) to data
10 (process data) related to each business process.
[0009]
For this reason, in the ERP system according to the
related art, it is necessary to specify a table according
to the type of input process and to input an identifier of
15 another corresponding process data for each input process.
In other words, for example, in the example of Figs. 13(A)
to 13(E), when process data related to a business process
"shipping instruction" associated with process data (that
is, various kinds of data stored in the same column as a
20 received order number "A00001" and a received order
description number "0010" in the received order table)
specified by a received order number "A00001" and a
received order description number "0010" is registered to a
database included in the ERP system, it is necessary to
25 register the received order number "A00001" and the
6
received order description number "0010" to the shipping
instruction table together with a shipping instruction
number specifying process data, a shipping instruction
description number, a type representing the type of
business process, and data (for example, an 5 orderer, a
quantity, an amount, a shipping instruction date, and a
shipping text) representing content of a business process,
as process data related to a business process "shipping
instruction." In this case, the same data (for example, an
10 orderer, a quantity, or an amount) may be registered to a
plurality of tables, and thus it is problematic from a
point of view of an efficient data process.
[0010]
Then, similarly to when data is registered, in the
15 ERP system according to the related art, when various kinds
of data stored in various tables are searched for at the
user’s request, for example, it is necessary to search for
necessary process data by tracing an identifier of process
data and to individually acquire data matching a search
20 condition from various tables, and thus there is a problem
in that a processing load required for a search excessively
increases.
[0011]
As described above in the ERP system according to the
25 related art, when various kinds of data stored in various
7
tables are searched for, a processing load is large, and
when various kinds of information processing is performed
by extracting various kinds of data, a processing load
further increases, and thus there is a problem in that it
is hard to rapidly output valid 5 information by information
processing.
[0012]
Particularly, when information is provided according
to a request from a mobile communication terminal (mobile
10 terminal), a rapid response speed is required, and thus the
above problem becomes remarkable.
[0013]
In order to solve the above problems, it is an object
of the present invention to reduce a processing load
15 required for data processing in a business system and
rapidly output valid information in a business system (an
ERP system) that provides information about a report to a
mobile communication terminal (mobile terminal).
20 Solution to Problem
[0014]
A mobile terminal management server 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
25 communication network according to a request from a mobile
8
terminal used by a user, and includes a process flow data
storage unit that stores process flow data including
various kinds of data related to a process flow including a
plurality of business processes, the process flow data
including 5 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, the process-specific
10 data being specific to each business process included in
the same process flow, a customer designation screen
providing unit that provides a customer designation screen
used to designate a customer according to a request from
the mobile terminal, a customer information accepting unit
15 that receives and accepts customer information representing
the customer designated through the customer designation
screen from the mobile terminal, a bond data extracting
unit that extracts bond data related to a bond of the
customer represented by the customer information accepted
20 by the customer information accepting unit with reference
to the process flow data stored in the process flow data
storage unit, a credit management information generating
unit that generates credit management information of the
designated customer based on the bond data extracted by the
25 bond data extracting unit, and a credit management
9
information providing unit that provides the credit
management information generated by the credit management
information generating unit to the mobile terminal.
[0015]
Through the above configuration, in 5 a business system
that provides information related to a report to a mobile
communication terminal, it is possible to reduce a
processing load required for data processing in the
business system and rapidly output valid information.
10 [0016]
The credit management information generating unit may
calculate a total amount of money by adding respective
amounts of money in the bond data extracted by the bond
data extracting unit and generate the credit management
15 information including the total amount of money.
[0017]
The mobile terminal management server may further
include a credit limit information acquiring unit that
acquires credit limit information representing a credit
20 limit of the customer represented by the customer
information accepted by the customer information accepting
unit, and the credit management information generating unit
may determine whether or not the calculated total amount of
money is larger than the credit limit represented by the
25 credit limit information acquired by the credit limit
10
information acquiring unit and generate credit management
information including a determination result of the
determination.
[0018]
For example, the bond data is data including 5 an
amount of a bond issued to a customer among pieces of data
included in the process flow data.
[0019]
For example, the bond data is data including an
10 amount of money in a bond-related business process.
[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
15 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 includes a process flow data storage unit
that stores process flow data including various kinds of
20 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 statuses of the plurality of
business processes included in the process flow, the common
25 data being common to business processes included in the
11
same process flow, the process-specific data being specific
to each business process included in the same process flow,
and the mobile terminal management program causes the
mobile terminal management server to execute a customer
5 designation screen providing process of providing a
customer designation screen used to designate a customer
according to a request from the mobile terminal, a customer
information accepting process of receiving and accepting
customer information representing the customer designated
10 through the customer designation screen from the mobile
terminal, a bond data extracting process of extracting bond
data related to a bond of the customer represented by the
customer information accepted in the customer information
accepting process with reference to the process flow data
15 stored in the process flow data storage unit, a credit
management information generating process of generating
credit management information of the designated customer
based on the bond data extracted in the bond data
extracting process, and a credit management information
20 providing process of providing the credit management
information generated in the credit management information
generating process to the mobile terminal.
Advantageous Effects of Invention
25 [0021]
12
According to the present invention, it is possible to
reduce a processing load required for data processing in a
business system and rapidly output valid information in a
business system (an ERP system) that provides information
5 about a report to a mobile communication terminal.
Brief Description of Drawings
[0022]
Fig. 1 is a block diagram illustrating a
10 configuration example of a report inquiry system.
Fig. 2 is a block diagram illustrating a
configuration example of a mobile terminal management
server.
Fig. 3 is an explanatory diagram illustrating an
15 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 of a menu screen.
20 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.
Fig. 8 is an explanatory diagram illustrating an
25 example of an overall configuration of a selection item
13
arrangement circle displayed on the slip search screen.
Fig. 9 is an explanatory diagram illustrating an
example of a search result list display screen.
Fig. 10 is a flowchart illustrating an example of a
credit 5 management information provision process.
Fig. 11 is an explanatory diagram illustrating an
example of a customer designation screen.
Fig. 12 is an explanatory diagram illustrating an
example of a credit management information display screen.
10 Figs. 13(A) to 13(E) are explanatory diagrams for
describing an example of a table configuration in an ERP
system according to a related art.
Mode for Carrying Out the Invention
15 [0023]
Hereinafter, an embodiment of the present invention
will be described with reference to the accompanying
drawings.
Fig. 1 is a block diagram illustrating a
20 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 10, a relay 20,
a plurality of mobile terminals 31 to 3N (N is an arbitrary
25 positive integer), an enterprise resource planning system
14
100, an enterprise resource planning system 200, and an
enterprise resource planning system 300.
[0024]
The mobile terminal management server 10 is connected
5 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 200, and the enterprise
10 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
15 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.
20 [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
25 a process flow DB 201. The enterprise resource planning
15
system 300 includes a core business server 310 and a
process flow DB 301.
[0026]
Each of the plurality of the enterprise resource
planning 5 systems 100, 200, and 300 which differ in
configuration fulfills 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
10 according to the need (that is, according to its function).
In other words, in the report inquiry system, the system
200 having no core business server or the system 300 having
no DWH server can also fulfill the function of the
enterprise resource planning system by performing
15 communication with the mobile terminal management server 10.
Even though not illustrated, the system having no process
flow DB can also fulfill the function of the enterprise
resource planning system by storing process flow data in
the mobile terminal management server 10. Since a well20
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 system 100 as an example.
[0027]
25 The core business server 110 is connected with the
16
DWH server 120 through a dedicated communication line.
[0028]
The core business server 110 is a server managed, for
example, by the administrator of the report inquiry system
5 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 110 is configured with a general
information processing device including an OS (Operating
10 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 concerning receipts and expenditure of money or
15 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 representing only
20 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 Examples of the business application program include a
17
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
10 relevance between 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
15 and the like and registering various 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.
20 [0032]
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
25 various kinds of programs stored in the business
18
application program DB (not illustrated) 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
5 related data DB (not illustrated) managed by the DWH server
120, and the core business server 110 has a function of
converting process data stored in the process flow DB 101
into a CSV (Comma Separated Values) format according to a
predetermined extraction condition and transmitting the
10 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 converted to CSV
format by an FTP (File Transfer Protocol) to the mobile
terminal management server 10.
15 [0033]
The mobile terminal management server 10 is a server
which is run by ERP and provides various kinds of data
through a communication network according to a request from
a mobile terminal used by the user. For example, the
20 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.
[0034]
25 Fig. 2 is a block diagram illustrating a
19
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 control, a process flow data
5 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
10 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
15 executes, for example, a process of providing process flow
data to the mobile terminals 31 to 3N and a credit
management information provision processing unit 11b that
executes, for example, a process of providing credit
management information to the mobile terminals 31 to 3N.
20 [0035]
The process flow data temporary storage DB 16 is a
storage medium that temporarily stores process flow data
acquired from the enterprise resource planning system 100
side or process flow data stored in the process flow DB 18a.
25 The process flow data stored in the process flow data
20
temporary storage DB 16 is updated, for example, at regular
intervals (for example, at one-day intervals, at three-day
intervals, or at 12-hour intervals).
[0036]
5 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 program DB 17 include a sales business
management program, a purchase business management program,
10 a production management program, a financial accounting
management program, and a managerial accounting management
program.
[0037]
The process flow DB 18a is a storage medium that
15 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 embodiment, the
20 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,
25 the description will proceed in connection with an example
21
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
5 include usually used slip data (for example, 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
10 which is retrievable based on a key such as a slip number.
Here, the 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.).
15 [0038]
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
20 example, an orderer) of content of common data, which will
be described later, is the same.
[0039]
Fig. 3 is an explanatory diagram illustrating an
example of a storage state of process flow data in the
25 process flow DB 18a. As illustrated in Fig. 3, process
22
flow data according to 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.
5 Each item (that is, a column item in the process flow table
PT) corresponding to each section of the process flow 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
10 assigned to the respective sections configuring the process
flow data. Further, process data related to one process
flow (a series of process flow from a received order from a
certain company to deliver) is stored in the same entry in
the process flow table PT (that is, the same row in the
15 process flow table PT). Through this configuration, a
correspondence relation between respective pieces of
process data can be defined.
[0040]
Here, the "main key section" refers to a part in
20 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 flow number and a process flow
description number. In other words, in the present
25 embodiment, a combination of the process flow number and
23
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 flow
data. Here, the "time of initial registration of process
5 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 include addition of data.
10 [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 number is assigned to each process data which
15 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]
20 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
25 specify process flow data including process data
24
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
5 business process "received order" in the type "inventory
sales" of the process flow.
[0043]
The "project specifying data section" is a part in
which main key data serving as data specifying a project
10 among pieces of process flow data is stored. In the
present embodiment, the 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
15 project number and a project description number. In the
present embodiment, when an entry (data row) 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
20 which an entry belongs can be specified.
[0044]
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
25 identifier identifying a description of each business unit
25
configuring a project. Thus, each of the project
description numbers associated with the same 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). 5 . Further,
data (data of the same row) such as the common data section
associated with the same project description number is data
identifying a description of the same business.
[0045]
10 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 as original transaction on sales returns among
pieces of process flow data is stored. In the present
15 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.
[0046]
20 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 flow related to the process flow
25 such as a new transaction, data representing the same value
26
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,
respectively). Further, 5 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]
10 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
15 type of process flow 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
20 according to type of process flow). Further, 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
25 which is data (data representing a progress status of each
27
of a plurality 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
5 of each business process by setting "0" to an unfinished
process and "1" to a finished process on a business 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
10 flow includes business processes of "received order,"
"shipping," "delivery," "delivery acceptance inspection,"
and "sales," process specific data (for example, a received
order date) related to the business process "received
order" is registered. In this case, in the status data, a
15 part corresponding to "sales" becomes "1," and the
remaining parts remain in an initial state (that is, a
state set to "0").
[0049]
In other words, the status section in the present
20 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 determined that each business process is
completed as a predetermined status change condition is
25 satisfied. The status change condition is not specially
28
limited, and in the present embodiment, it is assumed that
"what all process specific data corresponding to one
business process is input" remains stored in a
predetermined storage region of the mobile terminal
5 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 process data unnecessary for a specific process flow
10 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.
15 [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 and
20 a ship-to party 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
25 which process specific data which is data specific to each
29
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
5 each business process among 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,"
10 and data not relying on the business process 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
15 various terms illustrated in Fig. 3 will be briefly
described below.
[0054]
First, the "received order" refers to a state in
which an order has been received from a customer, and a
20 contract with the customer has been made. The "shipping
instruction" refers to a state in which an instruction to
ship a product has been given to a warehouse man or a
person in charge of physical distribution. The "delivery"
refers to a state in which a product has been shipped from
25 a warehouse and then started to be delivered. The
30
"acceptance inspection" refers to a state in which a
customer has completed an acceptance inspection and an
ownership of a product has been transferred to the customer.
The "sales" refers to a state in which an acceptance
5 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]
The term "acceptance inspection" is also used to mean
10 "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." Further, in financial accounting
15 (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.
25 Even though not illustrated, the project schedule data in
31
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 5 is assumed
to be registered in the project table PJT.
[0057]
The mobile terminal management server 10 has a
function of providing various kinds of data stored in the
10 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 present
15 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.
[0058]
20 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
25 functioning as the ERP engine and the DWH server, it is
32
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 5 core business server and the DWH server,
the enterprise resource planning system 200 including only
the DWH server, and the enterprise resource planning system
300 including only the DWH server).
[0059]
10 Each of the mobile terminals 31 to 3N is an
information 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
15 mobile terminals 31 to 3N is assumed to include various
kinds of usable applications to 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
20 extraction key, and the like) used to acquire necessary
report data (process flow data and project schedule data in
the present embodiment) from the mobile terminal management
server 10 according to an operation performed by the user,
and transmitting the query to the mobile terminal
25 management server 10. The mobile terminals 31 to 3N are
33
assumed to include code readers (or code reader functions)
31a to 3Na that read various kinds of codes such as a quick
response (QR) code (registered trademark), respectively.
[0060]
5 In the present embodiment, each of the mobile
terminals 31 to 3N has a function of communicating with the
mobile terminal management server 10 through the relay 20
and the communication network 40 and outputting data
acquired from the mobile terminal management server 10 to a
10 display unit through a function of software such as a
predetermined Web application (a WEB browser).
[0061]
Next, a process of updating the process flow data
stored in the process flow data temporary storage DB 16
15 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 server 10 reads the
process flow data (latest data) stored in the process flow
20 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 process flow data temporary storage DB 16. Thus, the
25 storage information of the process flow data temporary
34
storage DB 16 is updated by a batch process.
[0062]
Next, an operation of the report inquiry system 500
according to the present embodiment will be described with
reference 5 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.
[0063]
Fig. 4 is a flowchart illustrating an example of a
10 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 management server 10 provides the
15 process flow data according to a request from a mobile
terminal 31 used by a user X.
[0064]
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
25 the mobile terminal 31.
35
[0065]
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
5 terminal management server 10, acquires a login screen,
designates information (for 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
10 predetermined information (for example, an electronic
certificate issued to the user X) used for a predetermined
login determination is provided in addition to the user ID
and the password. Further, when the operation to login the
mobile terminal management server 10 is performed, the user
15 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.
[0066]
Upon receiving the login request, the mobile terminal
20 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 the like.
[0067]
25 When it is determined that it is permitted to login
36
(Y in step S103), the mobile terminal management server 10
sets the mobile terminal 31 to a login state. When the
mobile terminal 31 is set to a login state, the mobile
terminal management server 10 transmits menu screen
5 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
providing process without setting the mobile terminal 31 to
10 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.
[0068]
15 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).
[0069]
20 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 which a plurality of selectable menu
25 names are displayed are arranged substantially on the
37
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 by the
5 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
10 expense input button M3 pushed down to input expense, a
master registration button M4 pushed down to register a
master, a credit management button M5 pushed down to make a
credit management information provision request, and an
inventory query button M6 pushed down to query inventory
15 information are provided.
[0070]
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
20 through a 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.
25 [0071]
38
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
5 selection result (step S106).
[0072]
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
10 management server 10 transmits the slip search screen
information representing the slip search screen for
designating a slip search condition to the mobile terminal
31 (step S107).
[0073]
15 Upon receiving the slip search screen information,
the mobile terminal 31 causes the slip search screen
represented by the received slip search screen information
to be displayed on the display unit included in the mobile
terminal 31 (step S108).
20 [0074]
Fig. 6 is an explanatory diagram illustrating an
example of a slip search screen. As illustrated in Fig. 6,
the slip search screen is provided with a plurality of
selection item arrangement circle display regions 601, 602,
25 and 603 to respectively display a plurality of selection
39
item arrangement circles DC, SC, and PC on which a
plurality of selection items 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-5 down condition.
In the present embodiment, as the selection item
arrangement circles DC, SC, and PC, a processed slip type
selection item arrangement circle DC on which the type of
processed slip is selectably displayed, a detailed
10 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 the type of business process
is selectably displayed are provided. Further, as the
15 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
selection type selection item arrangement circle display
20 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.
25 [0075]
40
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
5 is, the processed slip type 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
10 designate a warehousing slip as the search condition, a
delivery 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
15 deposit button D7 to designate a deposit slip as the search
condition. Further, a classification display 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
20 embodiment, the corresponding type of slip can be searched
for by selecting the selection items (selection item
buttons) D1 to D7 (by selecting one or more buttons).
[0076]
The detailed selection type selection item
25 arrangement circle SC is provided with four types of
41
selection items (selection item buttons) to select detailed
narrowing-down condition items, which are arranged
substantially on the circumference thereof. That is, the
detailed selection type selection item arrangement circle
5 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, an organization
button S3 to designate an organization as the search
condition, and an item goods button S4 to designate item
10 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 the detailed selection type selection item arrangement
circle SC. In the present embodiment, when the selection
15 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 narrowing-down
condition is displayed, and a concrete narrowing-down
20 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
narrowing-down condition designation screen. The slip
25 satisfying the designated narrowing-down condition can be
42
searched for by selecting the concrete narrowing-down
condition (one or more concrete narrowing-down conditions
may be selected).
[0077]
5 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
10 is provided 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
15 as the search condition. Further, a classification 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
20 corresponding type can be searched for by selecting the
selection items (selection item buttons) P1 to P3 (one or
more selection item buttons may be selected).
[0078]
In the present embodiment, when the classification
25 display button DA, SA, or PA is pushed down, a rendering
43
operation of 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
5 on the selection item arrangement circle display regions
601, 602, and 603 in the slip 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
10 on the circumference can be executed according to a
predetermined rotation instruction operation (an 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,
15 for example, when the classification display button DA is
pushed down, a selection item rotation rendering operation
of causing a plurality of selection items in the selection
item arrangement circle DC to rotate on the circumference
counterclockwise (in a direction A in Fig. 7) is executed.
20 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
of the screen with a finger near a location at which the
circle formed by the selection item arrangement circle DC
25 is displayed and sliding the finger in a new rotation
44
direction). Further, when the classification display
button DA, SA, or PA is pushed down again, it is desirable
to end the selection item rotation rendering operation.
[0079]
Since 5 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 circles DC, SC, and PC within the screen, and
even when some of the selection items arranged in each of
10 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. Further, since it is
unnecessary to simultaneously display all of the selection
15 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
simultaneously displaying all of the selection items within
20 one screen may be provided.
[0080]
In present embodiment, the selection items arranged
in the selection item arrangement circles DC, SC, and PC
are displayed in a circular frame. However, some or all of
25 the selection items may be displayed in a frame of any
45
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 be another selection item.
[00815 ]
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 selection item arrangement circle display
10 region may be provided, and two or three or more selection
item arrangement circle display regions may be provided.
[0082]
In the example illustrated in Fig. 6, the selection
item arrangement circle display regions 601, 602, and 603
15 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 603 are configured to have a
20 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.
25 [0083]
46
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
5 selected by selecting any one of the selection items
(selection item buttons) D1 to D7 arranged in the processed
slip type selection item arrangement circle 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
10 the selection items (selection item buttons) S1 to 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
15 narrowing-down condition on the detailed narrowing-down
condition designation 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
20 in the process type selection item arrangement circle PC.
Furthermore, in the slip search screen, the user X
designates a search keyword by inputting a keyword to be
used as the narrowing-down condition in the keyword input
region 604.
25 [0084]
47
In the present embodiment, when the user X selects
the item goods S4 among the selection items (selection item
buttons) S1 to S4 arranged in the detailed selection type
selection item arrangement circle SC in the slip search
5 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 mobile terminal 31 reads a
code (for example, a QR code or a barcode) attached to
10 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
goods input region. In the present embodiment, the item
15 goods number can be simply input using the code reader (or
a code reader function) 31a as described above.
[0085]
Further, in the slip search screen, the user X may
select or designate any one or more among the type of slip,
20 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 a business process which is
25 a search target.
48
[0086]
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.
[00875 ]
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
10 condition, and makes a search request (step S109).
[0088]
Upon receiving the search request, the mobile
terminal management server 10 searches for slip data
matching the search condition provided according to the
15 received provision request with reference to the process
flow data stored in the process flow data temporary storage
DB 16 (step S110).
[0089]
When the slip data is searched for according to the
20 search condition, the mobile terminal management server 10
generates 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
25 information to the mobile terminal 31 (step S111).
49
[0090]
Upon receiving the search result list display screen
information, the mobile terminal 31 causes the search
result list display screen represented by the received
5 search result list display screen information to be
displayed on the display unit included in the mobile
terminal 31 (step S112).
[0091]
Fig. 9 is an explanatory diagram illustrating an
10 example of the search result list display screen. As
illustrated in Fig. 9, the search result list display
screen is provided with a display region 701 for displaying
the search result, a back button B1 pushed down to return
to a previous screen, and an edit button B3 pushed down to
15 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 result
list display screen, the mobile terminal 31 transmits a
request of acquiring corresponding slip data to the mobile
20 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 the process flow data temporary storage
DB 16 according to the slip data acquisition request. Then,
25 the mobile terminal 31 displays the received slip data on
50
the display screen of the display unit.
[0092]
When the user X performs an operation of ending
access such as an operation of ending a browser in the
5 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 access such as an operation of
pushing down the back button B1 is made (N in step S113),
10 the mobile terminal 31 causes the process to proceed to
step S108, and displays the slip search screen (see Fig. 6).
[0093]
When the search result list display screen
information is transmitted in step S111, the mobile
15 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 predetermined time
(for example, 5 minutes, 10 minutes, 30 minutes, and the
20 like) (has reached a predetermined time) (step S115).
[0094]
When the logout request is received during
measurement of the standby time (Y in step S116), the
mobile terminal management server 10 stops measuring the
25 standby time, and performs a logout process of releasing
51
the login state (step S117).
[0095]
Further, when it is determined that the standby time
has elapsed a predetermined time (Y in step S115), the
5 mobile terminal management server 10 ends measuring the
standby time, and performs a logout process of releasing
the login state (step S117).
[0096]
In the above-described way, it is determined whether
10 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 permitted to log in, a process flow
data provision request is received, and a process of
15 providing the requested process flow data is executed.
[0097]
As described above, in the slip data providing
process, by setting the process flow data temporary storage
DB 16 as a search target, the mobile terminal 31 needs not
20 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 can be improved when slip data
is provided to the mobile terminal 31. Further, the
25 process flow DB 18a may be set as the search target.
52
[0098]
In the above-described embodiment, report data
satisfying a search condition is searched for with
reference to the process flow table PT storing process flow
data including various kinds of data 5 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
representing a progress status of each of the plurality of
10 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 thus it is possible to reduce a
15 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
20 business 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 abovedescribed
embodiment, the process flow data including the
status data, the common data, and the process-specific data
25 is constructed, and a search is performed with reference to
53
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 5 program for a data
search.
[0099]
Fig. 10 is a flowchart illustrating an example of a
credit management information provision process executed,
10 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
management server 10 provides the credit management
15 information according to a request from the mobile terminal
31 used by the user X.
[0100]
In the credit management information provision
process, the process of step S201 to step S205 is the same
20 as the process of step S101 to step S105 of the slip data
providing process, and a description thereof is not be made
herein.
[0101]
In step S205, the user X pushes down any one of the
25 menu buttons M1 to M6 by a touch operation (a contact
54
operation by a finger) in the menu screen (see Fig. 5)
displayed on the display unit of the mobile terminal 31.
In the present embodiment, the credit management button M5
is assumed to be pushed down. The process when the other
menu buttons M1 to M4 and M6 are pushed down will 5 not be
made herein.
[0102]
When the credit management button M5 is pushed down
in the menu screen, the mobile terminal 31 transmits
10 information representing that the credit management button
M5 has been pushed down to the mobile terminal management
server 10 as the menu selection result (step S206).
[0103]
Upon receiving the menu selection result representing
15 that the credit management button M5 has been pushed down,
the credit management information provision processing unit
11b of the mobile terminal management server 10 transmits
customer designation screen information representing a
customer designation screen used to designate a project to
20 the mobile terminal 31 (step S207).
[0104]
Upon receiving the customer designation screen
information, the mobile terminal 31 causes the customer
designation screen represented by the received customer
25 designation screen information to be displayed on the
55
display unit included in the mobile terminal 31 (step S208).
[0105]
Fig. 11 is an explanatory diagram illustrating an
example of the customer designation screen. As illustrated
in Fig. 5 11, the customer designation screen is provided
with a customer input region 801 through which a customer
is input and a decide button B5 pushed down to make a
decision to acquire credit management information of a
customer input to the customer input region 801.
10 [0106]
In the customer designation screen, the user X
operates an input unit such as a keyboard displayed on the
screen, for example, as the customer input region 801 is
touched, and inputs customer information (for example, a
15 customer name or a number allocated to a customer)
representing 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 a customer.
20 [0107]
When the decide button B5 is pushed down after a
customer is input, the mobile terminal 31 designates the
customer, and transmits a credit management information
provision request to the mobile terminal management server
25 10 (step S209).
56
[0108]
Upon receiving the credit management information
provision request, the mobile terminal management server 10
searches for slip data associated with the customer
presented by the received provision 5 request with reference
to the process flow data stored in the process flow data
temporary storage DB 16, and extracts bond data related to
a bond of the designated customer from the process flow
table PT (step S210). The bond data is certain data
10 including, for example, an amount of a bond issued to a
customer in the slip data. In the present embodiment, the
bond data is assumed to be data including a process flow
number, a process flow description number, customer
information representing a customer, a process flow ID
15 (type), a bond-related business process (a received order,
shipping, sales, or the like in the status part), and an
amount of money.
[0109]
Then, the mobile terminal management server 10
20 acquires credit limit information representing a credit
limit of a designated customer from a customer master
stored in the other DB 10X (step S211).
[0110]
Then, the mobile terminal management server 10
25 generates credit management information based on the
57
extracted bond data and the acquired credit limit
information (step S212). In step S212, the mobile terminal
management server 10 performs a process of adding
respective amounts of money in the extracted bond data and
5 calculating a total amount of money or a process of
determining whether the calculated total amount of money is
larger than the credit limit, and generates the credit
management information including the bond data, the credit
limit information, the total amount information
10 representing the total amount of money, and a determination
result as to whether or not the total amount of money is
larger than the credit limit.
[0111]
When the credit management information is generated,
15 the mobile terminal management server 10 generates the
credit management information display screen information
representing the credit management information display
screen for displaying the generated credit management
information, and transmits the credit management
20 information display screen information to the mobile
terminal 31 (step S213).
[0112]
Upon receiving the credit management information
display screen information, the mobile terminal 31 causes
25 the credit management information display screen
58
represented by the received credit management information
display screen information to be displayed on the display
unit included in the mobile terminal 31 (step S214).
[0113]
Fig. 12 5 is an explanatory diagram illustrating an
example of the credit management information display screen.
As illustrated in Fig. 12, the credit management
information display screen is provided with a customer
display region 802 in which a designated customer is
10 displayed, a credit limit display region 803 in which a
credit limit is displayed, a bond-related data display
region 804 in which bond data and a total amount of money
are displayed, a check result display region 805 in which a
determination result as to whether or not a total amount of
15 money is larger than the credit limit is displayed, and a
back button B6 pushed down to return to a previous screen.
In the present embodiment, as illustrated in Fig. 12, in
the bond-related data display region 804, a process flow
number, a process flow description number, and a bond20
related business process (a received order, shipping, sales,
or the like in the status part) are displayed in
association with one another as the bond-related data, and
a total amount of money is further displayed.
[0114]
25 When the user X performs an operation of ending
59
access such as an operation of ending a browser in the
credit management information display screen (Y in step
S215), the mobile terminal 31 transmits a logout request to
the mobile terminal management server 10 (step S216).
5 Further, when an operation of continuing access such as an
operation of pushing down the back button B6 is performed
(N in step S215), the mobile terminal 31 causes the process
to proceed to step S208, and the customer designation
screen to be displayed (see Fig. 11).
10 [0115]
When the credit management information display screen
information is transmitted in step S213, the mobile
terminal management server 10 starts to measure a time
(standby time) in which an information exchange with the
15 mobile terminal 31 is not performed, and monitors whether
or not the standby time has elapsed a predetermined time
(for example, 5 minutes, 10 minutes, 30 minutes, and the
like) (has reached a predetermined time) (step S217).
[0116]
20 When the logout request is received during
measurement of the standby time (Y in step S218), the
mobile terminal management server 10 stops measuring the
standby time, and performs a logout process of releasing
the login state (step S219).
25 [0117]
60
Further, when it is determined that the standby time
has elapsed a predetermined time (Y in step S217), the
mobile terminal management server 10 ends measuring the
standby time, and performs a logout process of releasing
the login state (step S2195 ).
[0118]
In the above-described way, it is determined whether
or not it is permitted to log in the mobile terminal
management server 10 according to the login request from
10 the mobile terminal 31 which becomes operable by the login
process. When it is permitted to log in, a credit
management information provision request is received, and a
process of providing the requested credit management
information is executed.
15 [0119]
In the above example, in the credit 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.
20 [0120]
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
25 mobile terminals 31 to 3N used by the users includes the
61
process flow data table PT that stores the process flow
data including various kinds of data related to the process
flow including a plurality of business processes, the
process flow data is data including the status data, the
common 5 data, and the process-specific data, the status data
is data representing the progress statuses of the plurality
of business processes included in the process flow, the
common data is data that is common to business processes
included in the same process flow, and the process-specific
10 data is data specific to each business process included in
the same process flow, and the mobile terminal management
server 10 is configured to provide the customer designation
screen used to designate the customer according to the
request from the mobile terminal 31, receive and accept the
15 customer information representing the customer designated
through the customer designation screen from the mobile
terminal 31, extract the bond data related to the bond of
the customer represented by the accepted customer
information with reference to the process flow data stored
20 in the process flow data table PT, generate the credit
management information of the designated customer based on
the extracted bond data, and provide the generated credit
management information to the mobile terminal 31, and thus
in the business system that provides information related to
25 a report to the mobile communication terminal (the mobile
62
terminals 31 to 3N), it is possible to reduce a processing
load required for data processing in the business system
and rapidly output valid information (credit management
information).
5 [0121]
Further, the report data satisfying the 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
10 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 of business
processes included in the process flow, the common data is
15 data that is common to business process 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 the
processing load required for a data search in the business
20 system which is necessary to generate the credit management
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
25 business process. For this reason, in a business system
63
dealing with a huge amount of data, a processing load
required for a search process is very large. In the abovedescribed
embodiment, the process flow data including the
status data, the common data, and the process-specific data
is constructed, a search of information 5 necessary for
generating the credit management information is performed
with reference to the process data table, and thus since a
plurality of data tables are not referred to, it is
possible to significantly reduce a processing load required
10 for a search of data necessary for generating the credit
management information in a business system, and it is also
possible to significantly reduce a creation load of a
processing program for a data search.
[0122]
15 Further, in the above-described embodiment, the
mobile terminal management server 10 is configured to
calculate a total amount of money by adding respective
amounts of money in the extracted bond data and generate
the credit management information including the total
20 amount of money, and thus it is possible to provide the
valid credit management information.
[0123]
Further, in the above-described embodiment, the
mobile terminal management server 10 is configured to
25 acquire the credit limit information representing the
64
credit limit of the customer represented by the accepted
customer information (from the customer master), determine
whether or not the calculated total amount of money is
larger than the credit limit represented by the acquired
5 credit limit information, and generate the credit
management information including the determination result
of the determination, and thus it is possible to provide
the more valid credit management information.
[0124]
10 Further, in the above-described embodiment, the
database (for example, the process flow DB 18a) is disposed
in the process flow data management server (for example,
the mobile terminal management server 10) that manages the
process flow data generated for each process flow, and the
15 process flow data management server is configured to
provide the report data searched for with reference to the
process flow data to the client according to the request
from the client (for example, the mobile terminals 31 to 3N
or the enterprise resource planning systems 100, 200, and
20 300). Thus, it is possible to construct a system in which
a processing load required to provide the report data is
reduced.
[0125]
Further, although not particularly mentioned in the
25 above-described embodiment, the mobile terminal management
65
server 10 executes the above-described processes (see Fig.
4 and Fig. 10) according to a processing program (a mobile
terminal management program) stored in a storage medium
equipped therein.
5
Industrial Applicability
[0126]
According to the present invention, it is useful in
reducing a processing load required for a data search and
10 in outputting valid information rapidly in a business
system (specifically, an ERP system) that provides
information about a report to a mobile communication
terminal.
15 Reference Signs List
[0127]
10 mobile terminal management server
20 relay
31 to 3N mobile terminals
20 40 communication network
51, 52, 53 communication network
100, 200, 300 enterprise resource planning system
110, 310 core business server
120, 220 DWH server
25 500 report inquiry system
66
WE CLAIM:
1. A mobile terminal management server that is a server
run by enterprise resource planning (ERP) and provides
5 various kinds of data via a communication network according
to a request from a mobile terminal used by a user,
comprising:
a process flow data storage unit that stores process
flow data including various kinds of data related to a
10 process flow including a plurality of business processes,
the process flow data including status data, common
data, and process-specific data,
the status data representing progress statuses of the
plurality of business processes included in the process
15 flow,
the common data being common to business processes
included in a same process flow,
the process-specific data being specific to each
business process included in the same process flow,
20
a customer designation screen providing unit that
provides a customer designation screen used to designate a
customer according to a request from the mobile terminal;
a customer information accepting unit that receives
25 and accepts customer information representing the customer
67
designated through the customer designation screen from the
mobile terminal;
a bond data extracting unit that extracts bond data
related to a bond of the customer represented by the
5 customer information accepted by the customer information
accepting unit with reference to the process flow data
stored in the process flow data storage unit;
a credit management information generating unit that
generates credit management information of the designated
10 customer based on the bond data extracted by the bond data
extracting unit; and
a credit management information providing unit that
provides the credit management information generated by the
credit management information generating unit to the mobile
15 terminal.
2. The mobile terminal management server according to
claim 1,
wherein the credit management information generating
20 unit calculates a total amount of money by adding
respective amounts of money in the bond data extracted by
the bond data extracting unit, and generates the credit
management information including the total amount of money.
25 3. The mobile terminal management server according to
68
claim 2, further comprising,
a credit limit information acquiring unit that
acquires credit limit information representing a credit
limit of the customer represented by the customer
5 information accepted by the customer information accepting
unit,
wherein the credit management information generating
unit determines whether or not the calculated total amount
of money is larger than the credit limit represented by the
10 credit limit information acquired by the credit limit
information acquiring unit, and generates credit management
information including a determination result of the
determination.
15 4. The mobile terminal management server according to
any of claims 1 to 3,
wherein the bond data is data including an amount of
a bond issued to a customer among pieces of data included
in the process flow data.
20
5. The mobile terminal management server according to
claim 4,
wherein the bond data is data including an amount of
money in a bond-related business process.
25
69
6. A mobile terminal management program that operates
enterprise resource planning (ERP) and causes a mobile
terminal management server to execute a process of
providing various kinds of data via a communication network
5 according to a request from a mobile terminal used by a
user,
the mobile terminal management server includes a
process flow data storage unit that stores process flow
data including various kinds of data related to a process
10 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 statuses of the
plurality of business processes included in the process
15 flow,
the common data being common to business processes
included in the same process flow,
the process-specific data being specific to each
business process included in the same process flow,
20 the mobile terminal management program causing the
mobile terminal management server to execute:
a customer designation screen providing process of
providing a customer designation screen used to designate a
customer according to a request from the mobile terminal;
25 a customer information accepting process of receiving
70
and accepting customer information representing the
customer designated through the customer designation screen
from the mobile terminal;
a bond data extracting process of extracting bond
5 data related to a bond of the customer represented by the
customer information accepted in the customer information
accepting process with reference to the process flow data
stored in the process flow data storage unit;
a credit management information generating process of
10 generating credit management information of the designated
customer based on the bond data extracted in the bond data
extracting process; and
a credit management information providing process of
providing the credit management information generated in
15 the credit management information generating process to the
mobile terminal.