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 via a
10 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.
Background Art
15 [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 core
business system in which this ERP is contained (an integrated
20 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 focusing on report output.
[0003]
25 For the purpose of processing the large amount of business
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 5 1).
[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
10 proposed (see Patent Literatures 2 and 3).
Citation List
Patent Literature
[0005]
15 Patent Literature 1: JP 2002-312208 A
Patent Literature 2: JP 2003-323582 A
Patent Literature 3: JP 2007-200136 A
Summary of Invention
20 Technical Problem
[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
25 to each dedicated data table (table) and managed. In other words,
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 5 ss process
to each table.
[0007]
Figs. 16(A) to 16(E) are explanatory diagrams for
describing an example of a table configuration in the ERP system
10 according to the related art. For example, when a 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
15 storing data related to the 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. 16(A) to 16(E).
20 [0008]
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
25 an identifier (in Figs. 16(A) to 16(E), a received order number
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.
5 [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 another
corresponding process data for each input process. In other
10 words, for example, in the example of Figs. 16(A) to 16(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 received order number "A00001"
and a received order description number "0010" in the received
15 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 register
the received order number "A00001" and the received order
description number "0010" to the shipping instruction table
20 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 orderer, a quantity, an amount, a shipping instruction date,
and a shipping text) representing content of a business process,
25 as process data related to a business process "shipping
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.
5 [0010]
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
10 data by tracing an identifier of process data and to individually
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]
15 As described above in the ERP system according to the
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
20 thus there is a problem in that it is hard to rapidly output
valid information by information processing.
[0012]
Particularly, when information is provided according to
a request from a mobile communication terminal (mobile terminal),
25 a rapid response speed is required, and thus the above problem
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 5 output valid
information in a business system (an ERP system) that provides
information about a report to a mobile communication terminal
(mobile terminal).
10 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 communication
15 network according to a request from a mobile terminal used by
a user, and includes a process flow data storage unit that stores
process flow data including various kinds of data related to
a process flow including a plurality of business processes, a
production target product related information storage unit that
20 stores production target product related information capable
of specifying a reference quantity of a production target product
and a configuration quantity of a component of the product with
respect to the reference quantity, the process flow data
including status data, common data, and process-specific data,
25 the status data representing progress statuses of the plurality
8
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 data being specific to each
business process included in the same process flow, a production
plan registration 5 request information designation screen
providing unit that provides a production plan registration
request information designation screen used to designate
production plan registration request information for making a
production plan information registration request according to
10 a request from the mobile terminal, a production plan
registration request information accepting unit that receives
and accepts the production plan registration request information
designated through the production plan registration request
information designation screen from the mobile terminal, a
15 configuration quantity specifying unit that specifies a
configuration quantity of a component of the production target
product based on a scheduled production quantity of the
production target product included in the production plan
registration request information accepted by the production plan
20 registration request information accepting unit and the
production target product related information, and a production
plan information registering unit that registers production plan
information including the configuration quantity of the
component specified by the configuration quantity specifying
25 unit and the scheduled production quantity of the production
9
target product included in the production plan registration
request information to the process flow data stored in the process
flow data storage unit.
[0015]
Through the above configuration, in a business system 5 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 mobile terminal management server may further include
a production plan registration result information providing unit
that provides production plan registration result information
representing the production plan information registration
15 result to the mobile terminal.
[0017]
The mobile terminal management server may further include
an actual production performance registration request
information designation screen providing unit that provides an
20 actual production performance registration request information
designation screen used to designate actual production
performance registration request information for making an
actual production performance information registration request
according to a request from the mobile terminal, an actual
25 production performance registration request information
10
accepting unit that receives and accepts the actual production
performance registration request information designated
through the actual production performance registration request
information designation screen from the mobile terminal, a
production schedule checking unit that checks whether or 5 not
a product of an actual production performance target is scheduled
to be produced using manufacturing order identification
information corresponding to the product of the actual production
performance target included in the actual production performance
10 registration request information accepted by the actual
production performance registration request information
accepting unit with reference to the process flow data stored
in the process flow data storage unit, and an actual production
performance information registering unit that registers actual
15 production performance information representing that a delivery
of the product of the actual production performance target is
completed when the production schedule checking unit checks that
the product of the actual production performance target is
scheduled to be produced, and updates the process flow data.
20 [0018]
The mobile terminal management server may further include
an actual production performance registration result
information providing unit that provides the actual production
performance registration result information representing the
25 actual production performance information registration result
11
to the mobile terminal.
[0019]
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 5 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
including a process flow data storage unit that stores process
10 flow data including various kinds of data related to a process
flow including a plurality of business processes and a production
target product related information storage unit that stores
production target product related information capable of
specifying a reference quantity of a production target product
15 and a configuration quantity of a component of the product with
respect to the reference quantity, 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
20 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, and
the mobile terminal management program causes mobile terminal
management server to execute a production plan registration
25 request information designation screen providing process of
12
providing a production plan registration request information
designation screen used to designate production plan
registration request information for making a production plan
information registration request according to a request from
the mobile terminal, a production plan registration 5 request
information accepting process of receiving and accepting the
production plan registration request information designated
through the production plan registration request information
designation screen from the mobile terminal, a configuration
10 quantity specifying process of specifying a configuration
quantity of a component of the production target product based
on a scheduled production quantity of the production target
product included in the production plan registration request
information accepted in the production plan registration request
15 information accepting process and the production target product
related information, and a production plan information
registering process of registering production plan information
including the configuration quantity of the component specified
in the configuration quantity specifying process and the
20 scheduled production quantity of the production target product
included in the production plan registration request information
to the process flow data stored in the process flow data storage
unit.
25 Advantageous Effects of Invention
13
[0020]
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 5 information about
a report to a mobile communication terminal.
Brief Description of Drawings
[0021]
10 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.
Fig. 3 is an explanatory diagram illustrating an example
15 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 example
25 of an overall configuration of a selection item arrangement
14
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 of an example of a
5 production information registration process.
Fig. 11 is an explanatory diagram illustrating an example
of a data storage state of a BOM master.
Fig. 12 is an explanatory diagram illustrating an example
of a production plan registration screen.
10 Fig. 13 is an explanatory diagram illustrating an example
of a production plan registration result display screen.
Fig. 14 is an explanatory diagram illustrating an example
of an actual production performance registration screen.
Fig. 15 is an explanatory diagram illustrating an example
15 of an actual production performance registration result display
screen.
Figs. 16(A) to 16(E) are explanatory diagrams for
describing an example of a table configuration in an ERP system
according to a related art.
20
Mode for Carrying Out the Invention
[0022]
Hereinafter, an embodiment of the present invention will
be described with reference to the accompanying drawings.
25 Fig. 1 is a block diagram illustrating a configuration
15
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 positive integer), an enterprise 5 nterprise resource planning
system 100, an enterprise resource planning system 200, and an
enterprise resource planning system 300.
[0023]
The mobile terminal management server 10 is connected with
10 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 resource planning system 300 via
15 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
terminal or another enterprise resource planning system via the
20 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.
[0024]
25 The enterprise resource planning system 100 includes a
16
core business server 110, a data warehouse server (DWH server)
120, and a process flow DB 101. The enterprise resource planning
system 200 includes a DWH server 220 and a process flow DB 201.
The enterprise resource planning system 300 includes a core
5 business server 310 and a process flow DB 301.
[0025]
Each of the plurality of the enterprise resource planning
systems 100, 200, and 300 which differ in configuration fulfills
a functions of an enterprise resource planning system by
10 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
having no core business server or the system 300 having no DWH
15 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
of the enterprise resource planning system by storing process
20 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
system 100 as an example.
25 [0026]
17
The core business server 110 is connected with the DWH
server 120 through a dedicated communication line.
[0027]
The core business server 110 is a server managed, for
example, by the administrator of the report inquiry system 5 ystem 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
10 including an OS (Operating System) and a relational DB.
[0028]
Here, the report is the general term of books and a type
of slip. Further, the books denote one in which matters
concerning receipts and expenditure of money or goods are filled,
15 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 the slip data as report data will be described
20 as an example.
[0029]
The core business server 110 executes various kinds of
processing according to a business application program.
Examples of the business application program include a sales
25 business management program, a purchase business management
18
program, a production management program, a financial accounting
management program, and a managerial accounting management
program.
[0030]
The DWH server 120 is a server managed, for example, b5 y
the system administrator of the present system, and includes
various functions of implementing a data warehouse. Here, the
"data warehouse" denotes a system that analyzes relevance between
respective items from among business data such as report data
10 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
kinds of data to a predetermined storage region. Further, the
15 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.
[0031]
The process flow DB 101 is a storage medium that stores
20 process flow data configured with various kinds of process data
(or report data) collected and marshaled by means of various
kinds of information processing using various kinds of programs
stored in the business application program DB (not illustrated)
of the core business server 110. The process flow data will
25 be described in detail later. In the present embodiment, the
19
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
process data stored in the process flow DB 101 into a CSV (Comma
Separated Values) format according to a predetermined 5 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
converted to CSV format by an FTP (File Transfer Protocol) to
10 the mobile terminal management server 10.
[0032]
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
15 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.
[0033]
20 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
control, a process flow data temporary storage DB 16, a business
25 application program DB 17, a process flow DB 18a, a project DB
20
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
implement the function of the general core business server. The
other DB 10X has a portion which does not specifically 5 lly relate
to the present invention, and thus a detailed description thereof
will not be made. The control unit 11 includes a slip data
provision processing unit 11a that executes, for example, a
process of providing process flow data to the mobile terminals
10 31 to 3N and a production information registration processing
unit 11b that executes, for example, a process of registering
production information (production plan information and actual
production performance information) according to a request from
the mobile terminals 31 to 3N and providing a registration result.
15 [0034]
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. The process flow data
20 stored in the process flow data 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).
[0035]
The business application program DB 17 is a storage medium
25 that stores a program used for various kinds of businesses.
21
Examples of the program stored in the business application
program DB 17 include a sales business management program, a
purchase business management program, a production management
program, a financial accounting management program, and a
5 managerial accounting management program.
[0036]
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
10 kinds of information processing using various kinds of programs
stored in the business application program DB 17. In the present
embodiment, the description will proceed in connection with an
example in which process flow data including various kinds of
data related to a process flow including a plurality of business
15 processes is stored in a process flow table PT in the process
flow DB 18a. Further, in the present embodiment, the description
will proceed in connection with an example in which the mobile
terminal management server 10 centrally manages process flow
data generated in each process flow through the single process
20 flow table PT. Further, in the present embodiment, the process
flow data is assumed to include usually used slip data (for example,
data in which received order slip header information, received
order slip description information, delivery date schedules,
and the like are associated with slip data corresponding to a
25 received order slip, and which is stored with the structure which
22
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
5 the like.).
[0037]
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
10 or for each one in which a part (for example, an orderer) of
content of common data, which will be described later, is the
same.
[0038]
Fig. 3 is an explanatory diagram illustrating an example
15 of a storage state of process flow data in the process flow DB
18a. As illustrated in Fig. 3, process flow data according to
the present embodiment includes a 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
20 data section. 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 assigned to the
25 respective sections configuring the process flow data. Further,
23
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 process flow table PT). Through this
5 configuration, a correspondence relation between respective
pieces of process data can be defined.
[0039]
Here, the "main key section" refers to a part in which
main key data which is data to uniquely specify process flow
10 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 embodiment, a combination of the process
flow number and the process flow description number serves as
15 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
flow data" refers to when an entry (data row) is added to the
process flow data, for example, when another corresponding
20 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.
[0040]
Further, the "process flow number" is an identifier to
25 specify one process flow data (that is, a first column in the
24
process flow table PT illustrated in Fig. 3). The process flow
number is assigned to each process data which is the same in
predetermined item. In the present embodiment, the same process
flow number is assigned to process flow data which is the same
5 in the type and the orderer of the process flow data.
[0041]
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
10 assigned. In other words, for example, the process flow table
PT illustrated in Fig. 3 can uniquely specify process flow data
including process data representing that an order for a business
of the amount "1200" and "2600" is received from an orderer "T001"
by a combination of the process flow number "000001" and the
15 process flow description number "0010" or "0020" in the business
process "received order" in the type "inventory sales" of the
process flow.
[0042]
The "project specifying data section" is a part in which
20 main key data serving as data specifying a project among pieces
of process flow data is stored. In the present embodiment, the
project specifying data section 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
25 by a combination of a project number and a project description
25
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 which an entry
5 belongs can be specified.
[0043]
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
10 a description of each business unit 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).
15 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.
[0044]
Next, the "reference key section" is a part in which
20 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 embodiment, the reference
key section is configured with a reference number and a reference
25 description number, and is updated at the time of initial
26
registration of process flow data.
[0045]
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 5 description
number, respectively. However, when there is no other process
flow related to the process flow such as a new transaction, data
representing the same value as the main key section of the same
entry is stored in the reference key section (that is, the process
10 flow number and the process flow description number are stored
in the reference number and the reference description number,
respectively). Further, when the reference key section
represents another process data related to the process flow,
data specifying the type of process data is further stored in
15 the reference key section.
[0046]
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
20 stored. The type section is updated at the time of initial
registration of process flow data. The type of process flow
is not limited to inventory sales or sample shipping. Further,
it is assumed that a necessary process is decided in advance
depending on the type of the process flow (that is, the type
25 of business process or the number of business processes to be
27
included differ according to type of process flow). Further,
two or more other types of process flows will be provided later
(see Fig. 9).
[0047]
The "status section" is a part in which status data 5 which
is data (data representing a progress status of each 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
10 represents the progress of each business process by setting "0"
to an unfinished process and "1" to a finished process on a business
process needed 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
15 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 part corresponding to "sales" becomes "1," and
20 the remaining parts remain in an initial state (that is, a state
set to "0").
[0048]
In other words, the status section in the present
embodiment is updated for each business process. In other words,
25 the status section is updated when process specific data which
28
will be described later is input, specifically, when it is
determined that each business process is completed as a
predetermined status change condition is satisfied. The status
change condition is not specially limited, and in the present
embodiment, it is assumed that "what all process specific 5 ific data
corresponding to one business process is input" remains stored
in a predetermined storage region of the mobile terminal
management server 10 as the status change condition.
[0049]
10 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 may exist
among items (column items) configuring a table. In this case,
it is assumed that in the process flow table, a part storing
15 unnecessary process data becomes null data, and "0" is stored
in the status data corresponding to the null data.
[0050]
The "common data section" is a part in which common data
which is data (that is, data which is common between the business
20 processes included in the same process flow) not relying on the
business process such as an orderer and a ship-to party among
pieces of process flow data is stored. The common data section
is updated at the time of initial registration of process flow
data.
25 [0051]
29
The "process-specific data section" is a part in which
process specific data which is data specific to each business
process included in the same process flow such as the received
order date or data (for example, text data representing a
precaution such as "arrival by delivery date" or "fragile 5 gile goods
goods (handle with care)" registered in each business process
among pieces of process flow data is stored. The process specific
data section is updated for each business process. Thus, in
the present embodiment, among pieces of process flow data, data
10 relying on the business process is referred to as "process
specific data," and data not relying on the business process
is referred to as "common data."
[0052]
The process flow data according to the present embodiment
15 has been described so far, and a definition of various terms
illustrated in Fig. 3 will be briefly described below.
[0053]
First, the "received order" refers to a state in which
an order has been received from a customer, and a contract with
20 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 a warehouse and then started to be delivered.
25 The "acceptance inspection" refers to a state in which a customer
30
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 inspection of a customer has
been checked and a debt amount on a customer has been fixed (that
5 is, a debt has been recorded).
[0054]
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,
10 a color, a shape, and a quality)" or that "an ownership of an
asset is transferred when an acceptance inspection is completed."
Further, in financial accounting (or institutional accounting)
or on the ERP system, in order to explicitly specify a transfer
timing of an ownership of an asset, an event of "acceptance
15 inspection" is defined to be distinguished from delivery.
[0055]
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
20 schedule data representing the business schedule of each project
is stored in a project table PJT. Even though not illustrated,
the project schedule data in which information representing a
business schedule (for example, a schedule of a budget, a purchase,
received order, a purchase order, and the like) for achieving
25 a corresponding business is associated with, for example, a
31
project number and a project description number is assumed to
be registered in the project table PJT.
[0056]
The mobile terminal management server 10 has a function
of providing various kinds of data stored in the process 5 ocess 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
10 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.
[0057]
15 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
20 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
25 planning system 200 including only the DWH server, and the
32
enterprise resource planning system 300 including only the DWH
server).
[0058]
Each of the mobile terminals 31 to 3N is an information
processing device, such as iPad (registered trademark), 5 ), 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
10 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
15 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
20 such as a quick response (QR) code (registered trademark),
respectively.
[0059]
In the present embodiment, each of the mobile terminals
31 to 3N has a function of communicating with the mobile terminal
25 management server 10 through the relay 20 and the communication
33
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).
[0060]
Next, a process of updating the process flow data 5 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
10 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
15 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.
[0061]
Next, an operation of the report inquiry system 500
20 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.
[0062]
25 Fig. 4 is a flowchart illustrating an example of a slip
34
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 process flow 5 data according
to a request from a mobile terminal 31 used by a user X.
[0063]
In the slip data providing process, first, the mobile
terminal 31 receives a login request by the user X's login
10 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.
15 [0064]
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
20 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
25 determination is provided in addition to the user ID and the
35
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.
5 [0065]
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
10 the like.
[0066]
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
15 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
20 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.
25 [0067]
36
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).
5 [0068]
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
10 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
15 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
20 M3 pushed down to input expense, a master registration button
M4 pushed down to register a master, a production plan
registration button M5 pushed down to makes a production plan
information registration request, and an actual production
performance registration button M6 pushed down to make an actual
25 production performance information registration request.
37
[0069]
In the menu screen displayed on the display unit of the
mobile terminal 31 in which a touch panel is arranged, the user
X pushes down any one of the menu buttons M1 to M6 through a
touch operation (a contact operation by a finger). In the 5 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.
[0070]
10 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).
15 [0071]
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
20 representing the slip search screen for designating a slip search
condition to the mobile terminal 31 (step S107).
[0072]
Upon receiving the slip search screen information, the
mobile terminal 31 causes the slip search screen represented
25 by the received slip search screen information to be displayed
38
on the display unit included in the mobile terminal 31 (step
S108).
[0073]
Fig. 6 is an explanatory diagram illustrating an example
of a slip search screen. As illustrated in Fig. 6, the 5 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
10 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
15 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
20 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
25 selection type selection item arrangement circle display region
39
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.
5 [0074]
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
10 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
15 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
20 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
25 to D7 (by selecting one or more buttons).
40
[0075]
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
5 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,
10 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
15 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
20 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
25 narrowing-down condition designation screen. The slip
41
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).
[0076]
The process type selection item arrangement circle PC 5 C 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
10 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
15 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
20 item buttons) P1 to P3 (one or more selection item buttons may
be selected).
[0077]
In the present embodiment, when the classification display
button DA, SA, or PA is pushed down, a rendering operation of
25 rotating the corresponding selection item arrangement circle
42
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
5 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
10 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
15 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
20 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
25 rendering operation.
43
[0078]
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
circles DC, SC, and PC within the screen, and even when 5 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.
10 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
15 simultaneously displaying all of the selection items within one
screen may be provided.
[0079]
In present embodiment, the selection items arranged in
the selection item arrangement circles DC, SC, and PC are
20 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
25 be another selection item.
44
[0080]
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 region may be 5 provided,
and two or three or more selection item arrangement circle display
regions may be provided.
[0081]
In the example illustrated in Fig. 6, the selection item
10 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
15 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.
20 [0082]
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
25 one of the selection items (selection item buttons) D1 to D7
45
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
S4 5 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
10 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
15 a search keyword by inputting a keyword to be used as the
narrowing-down condition in the keyword input region 604.
[0083]
In the present embodiment, when the user X selects the
item goods S4 among the selection items (selection item buttons)
20 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
25 mobile terminal 31 reads a code (for example, a QR code or a
46
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
goods input region. In the present embodiment, the item 5 tem goods
number can be simply input using the code reader (or a code reader
function) 31a as described above.
[0084]
Further, in the slip search screen, the user X may select
10 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
15 a business process which is a search target.
[0085]
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.
20 [0086]
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
25 search request (step S109).
47
[0087]
Upon receiving the search request, the mobile terminal
management server 10 searches for slip data matching the search
condition provided according to the received provision request
with reference to the process flow data stored in the 5 he process
flow data temporary storage DB 16 (step S110).
[0088]
When the slip data is searched for according to the search
condition, the mobile terminal management server 10 generates
10 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).
15 [0089]
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
20 unit included in the mobile terminal 31 (step S112).
[0090]
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
25 a display region 701 for displaying the search result, a back
48
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
result list display screen, the mobile terminal 31 5 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
10 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.
[0091]
15 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
20 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).
[0092]
25 When the search result list display screen information
49
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
predetermined time (for example, 5 minutes, 10 5 minutes, 30
minutes, and the like) (has reached a predetermined time) (step
S115).
[0093]
When the logout request is received during measurement
10 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).
[0094]
15 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).
20 [0095]
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
25 permitted to log in, a process flow data provision request is
50
received, and a process of providing the requested process flow
data is executed.
[0096]
As described above, in the slip data providing process,
by setting the process flow data temporary storage DB 16 as 5 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
10 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.
[0097]
In the above-described embodiment, report data satisfying
15 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
20 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
25 thus it is possible to reduce a processing load required for
51
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
process. For this reason, in a business system dealing 5 ling 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
10 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
15 for a data search.
[0098]
Fig. 10 is a flowchart illustrating of an example of a
production information registration process executed by the
mobile terminal management server 10 or the like in the report
20 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 registers
production plan information or actual production performance
information to the process flow table PT according to a request
25 from the mobile terminal 31 used by the user X.
52
[0099]
Further, in the present embodiment, a bill of materials
(BOM) master illustrated in Fig. 11 is assumed to be stored in
the other DB 10X. Production target product related information
capable of specifying a reference quantity of a product 5 duct of a
production target and a configuration quantity of a component
with respect to the reference quantity of the product is
registered to the BOM master. In the example illustrated in
Fig. 11, production target product related information
10 representing that a reference quantity of a product of an item
goods C1 is 100, components of the product of the item goods
C1 are components of item goods C2, C3, and C4, a configuration
quantity of the component of the item goods C2 is 10, a
configuration quantity of the component of the item goods C3
15 is 15, and a configuration quantity of the component of the item
goods C4 is 20 is registered to the BOM master. Since 100 products
of the item goods C1 are manufactured according to the production
product related information illustrated in Fig. 11, it represents
that 10 components of the item goods C2, 15 components of the
20 item goods C3, and 20 components of the item goods C4 are used.
The production target product related information is registered
by, for example, the user X in advance.
[0100]
In the production information registration process, the
25 process of step S201 to step S205 is the same as the process
53
of step S101 to step S105 of the slip data providing process,
and thus a description thereof is herein omitted.
[0101]
In step S205, the user X pushes down any one of the menu
buttons M1 to M6 by a touch operation (a contact operation 5 eration 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
production plan registration button M5 or the actual production
performance registration button M6 is assumed to be pushed down.
10 The process when the other menu buttons M1 to M4 are pushed down
will not be made herein.
[0102]
When the production plan registration button M5 is pushed
down in the menu screen, the mobile terminal 31 transmits
15 information representing that the production plan registration
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 that
20 the production plan registration button M5 has been pushed down,
the production information registration processing unit 11b of
the mobile terminal management server 10 transmits production
information registration screen information (production plan
information registration screen information) representing a
25 production information registration screen (production plan
54
information registration screen) used to register production
information (production plan information) to the mobile terminal
31 (step S207).
[0104]
Upon 5 pon receiving the production plan information
registration screen information, the mobile terminal 31 causes
the production plan information registration screen represented
by the received production plan information registration screen
information to be displayed on the display unit included in the
10 mobile terminal 31 (step S208).
[0105]
Fig. 12 is an explanatory diagram illustrating an example
of the production plan information registration screen. As
illustrated in Fig. 12, the production plan information
15 registration screen is provided with an item goods input region
801 used to input an item goods, a quantity input region 802
used to input a quantity, a scheduled production date input region
803 used to input a scheduled production date, and a decide button
B5 pushed down to decide the information input to the input regions
20 801 to 803.
[0106]
In the production plan information registration screen,
the user X operates an input unit such as a keyboard displayed
on the screen, for example, as each of the input regions 801
25 to 803 is touched, and input information to the input regions
55
801 to 803. Here, for example, it is assumed that the item goods
C1 is input to the item goods input region 801 as a production
plan target product, 100 is input to the quantity input region
802 as a quantity of a production schedule of a product of the
item goods C1, and February 15, 2012 is input to the 5 scheduled
production date input region 803 as a scheduled production date
of the product of the item goods C1 as illustrated in Fig. 12.
When the input of the information to the input regions 801 to
803 ends, the user X pushes down the decide button B5 by the
10 touch operation. In this way, the user X inputs production plan
registration request information (information including item
goods, a quantity, and a scheduled production date of a product
in the present embodiment) to make a production plan information
registration request.
15 [0107]
When the decide button B5 is pushed down after the
production plan registration request information is input, the
mobile terminal 31 presents the production plan registration
request information to the mobile terminal management server
20 10, and transmits the production plan information registration
request (step S209).
[0108]
Upon receiving the production information registration
request, when the received registration request is the production
25 plan information registration request (Y in step S210), the
56
mobile terminal management server 10 searches the BOM master
stored in the other DB 10X, specifies production target product
related information for a product of item goods included in the
presented production plan registration request information,
generates production plan information including components 5 nents used
to manufacture a product of item goods that is scheduled to be
produced and a configuration quantity of each component for
manufacturing a product of item goods that is scheduled to be
produced by a scheduled quantity in addition to information
10 representing the production plan registration request
information, and registers the generated production plan
information to the process flow data table PT (step S211).
Further, the mobile terminal management server 10 specifies the
components used to manufacture a product of item goods that is
15 scheduled to be produced with reference to the BOM master.
Further, the mobile terminal management server 10 calculates
a configuration quantity of each component for manufacturing
a product of item goods that is scheduled to be produced by a
scheduled quantity using a calculation formula "(quantity of
20 product that is scheduled to be produced/reference quantity of
product registered to BOM master) × configuration quantity of
component with respect to reference quantity registered to BOM
master."
[0109]
25 When the production plan information is generated and then
57
registered, the mobile terminal management server 10 generates
production plan registration result display screen information
representing a production plan registration result display
screen used to display a production plan information registration
result, and transmits the production plan registration 5 result
display screen information to the mobile terminal 31 (step S212).
[0110]
Upon receiving the production plan registration result
display screen information, the mobile terminal 31 causes the
10 production plan registration result display screen represented
by the received production plan registration result display
screen information to be displayed on the display unit included
in the mobile terminal 31 (step S215).
[0111]
15 Fig. 13 is an explanatory diagram illustrating an example
of the production plan registration result display screen. As
illustrated in Fig. 13, the production plan registration result
display screen is provided with a production plan registration
result display region 804 in which a production plan registration
20 result is displayed and a back button B6 pushed down to return
to a previous screen. In the present embodiment, as illustrated
in Fig. 13, a data table including items such as a process flow
number, a process flow description number, a process flow ID
(type), a manufacturing warehousing schedule, a manufacturing
25 delivery schedule, actual activity performance, warehousing,
58
delivery, a manufacturing order, item goods, a quantity, and
an activity quantity is displayed on the production plan
registration result display region 804 as the production plan
registration result, item goods C1 of a product that is scheduled
to be produced and item goods C2, C3, and C4 of components 5 ts thereof
are displayed on item goods items, and a scheduled production
quantity (100) of the product of the item goods C1 and
configuration quantities (10, 15, and 20) of the components of
the item goods C2, C3, and C4 are displayed.
10 [0112]
Meanwhile, when the actual production performance
registration button M6 is pushed down in the menu screen, the
mobile terminal 31 transmits a menu selection result representing
that the actual production performance registration button M6
15 has been pushed down to the mobile terminal management server
10 (step S206).
[0113]
Upon receiving the menu selection result representing that
the actual production performance registration button M6 has
20 been pushed down, the production information registration
processing unit 11b of the mobile terminal management server
10 transmits the production information registration screen
information (the actual production performance information
registration screen information) representing the production
25 information registration screen (actual production performance
59
information registration screen) used to register the production
information (actual production performance information) to the
mobile terminal 31 (step S207).
[0114]
5 Upon receiving the actual production performance
information registration screen information, the mobile
terminal 31 causes the actual production performance information
registration screen represented by the received actual
production performance information registration screen
10 information to be displayed on the display unit included in the
mobile terminal 31 (step S208).
[0115]
Fig. 14 is an explanatory diagram illustrating an example
of the actual production performance information registration
15 screen. As illustrated in Fig. 14, the actual production
performance information registration screen is provided with
a manufacturing order number input region 901 used to input a
manufacturing order number, an item goods input region 902 used
to input item goods, a quantity input region 903 used to input
20 a quantity, and a decide button B7 pushed down to decide
information input to the input regions 901 to 903.
[0116]
In the actual production performance information
registration screen, the user X operates an input unit such as
25 a keyboard displayed on the screen, for example, as the input
60
regions 901 to 903 are touched, and inputs information to the
input regions 901 to 903. Here, for example, it is assumed that
a manufacturing order number B1 of a manufacturing order
representing a production plan of a product (a product for which
there is actual production performance) that is produced 5 and
warehoused is input to the manufacturing order number input
region 901, the item goods C1 is input to the item goods input
region 902 as an actual production performance target product,
and 100 is input to the quantity input region 903 as an actual
10 production quantity of the product of the item goods C1 as
illustrated in Fig. 14. When the input of the information to
the input regions 901 to 903 ends, the user X pushes down the
decide button B7 by the touch operation. In this way, the user
X inputs actual production performance registration request
15 information (information including a manufacturing order number,
item goods of a product, and a quantity in the present embodiment)
for making an actual production performance information
registration request.
[0117]
20 When the decide button B7 is pushed down after the actual
production performance registration request information is
input, the mobile terminal 31 presents the actual production
performance registration request information to the mobile
terminal management server 10, and transmits the actual
25 production performance information registration request (step
61
S209).
[0118]
Upon receiving the production information registration
request, when the received registration request is the actual
production performance information registration request (N i5 n
step S210), the mobile terminal management server 10 searches
for the production plan information (see the production plan
information of Fig. 13) associated using the manufacturing order
number included in the presented actual production performance
10 registration request information with reference to the process
flow data table PT, checks a manufacturing delivery schedule
of a product of an actual production performance target in the
production plan information, and registers the actual production
performance information to the process flow data table PT
15 according to the presented actual production performance
registration request information when there is a manufacturing
delivery schedule and the quantities match (step S213). In the
present embodiment, a process of registering a flag representing
"delivered" to a "delivery" item of a product and a component
20 of an actual production performance in the searched production
plan information.
[0119]
When the actual production performance information is
registered, the mobile terminal management server 10 generates
25 actual production performance registration result display
62
screen information representing an actual production
performance registration result display screen used to display
an actual production performance information registration
result, and transmits the actual production performance
registration result display screen information to the 5 mobile
terminal 31 (step S214).
[0120]
Upon receiving the actual production performance
registration result display screen information, the mobile
10 terminal 31 causes the actual production performance
registration result display screen represented by the received
actual production performance registration result display
screen information to be displayed on the display unit included
in the mobile terminal 31 (step S215).
15 [0121]
Fig. 15 is an explanatory diagram illustrating an example
of the actual production performance registration result display
screen. As illustrated in Fig. 15, the actual production
performance registration result display screen is provided with
20 an actual production performance registration result display
region 904 in which the actual production performance
registration result is displayed and a back button B8 pushed
down to return to a previous screen. In the present embodiment,
as illustrated in Fig. 15, a data table including items such
25 as a process flow number, a process flow description number,
63
a process flow ID (type), a manufacturing warehousing schedule,
a manufacturing delivery schedule, actual activity performance,
warehousing, delivery, a manufacturing order, item goods, a
quantity, and an activity quantity is displayed on the actual
production performance registration result display region 905 4
as the actual production performance registration result, and
item goods C1 of a product of an actual production performance
target and item goods C2, C3, and C4 of components thereof are
displayed on item goods items. Further, a display representing
10 that a flag representing "warehoused" is registered is performed
on warehousing items in the item goods C1 of the product of the
actual production performance target and the item goods C2, C3,
and C4 of the components thereof.
[0122]
15 When the user X performs an operation of ending access
such as an operation of ending a browser in the registration
result display screen (Y in step S216), the mobile terminal 31
transmits a logout request to the mobile terminal management
server 10 (step S217). Further, when an operation of continuing
20 access such as an operation of pushing down the back button B6
or B8 is made (N in step S216), the mobile terminal 31 causes
the process to proceed to step S208, and displays the production
information registration screen (see Figs. 12 and 14).
[0123]
25 When the registration result display screen information
64
is transmitted in step S212 or S214, 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 predetermined time (for example, 5 minutes, 5 nutes, 10
minutes, 30 minutes, and the like) (has reached a predetermined
time) (step S218).
[0124]
When the logout request is received during measurement
10 of the standby time (Y in step S219), the mobile terminal
management server 10 stops measuring the standby time, and
performs a logout process of releasing the login state (step
S220).
[0125]
15 Further, when it is determined that the standby time has
elapsed a predetermined time (Y in step S218), the mobile terminal
management server 10 ends measuring the standby time, and
performs a logout process of releasing the login state (step
S220).
20 [0126]
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. At this time,
25 when it is permitted to log in, a production information
65
registration request is received, and a process of registering
information according to a request and providing a result thereof
is executed.
[0127]
In the above example, 5 , in the production information
registration process, the slip data search target is the process
flow data temporary storage DB 16, but the process flow DB 18a
may be set to be the search target.
[0128]
10 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 data table
15 PT that stores the process flow data including various kinds
of data related to the process flow including a plurality of
business processes and the BOM master (see Fig. 11) that stores
the production target product related information capable of
specifying a reference quantity of a production target product
20 and a configuration quantity of a component of a product with
respect to the reference quantity, 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
25 in the process flow, the common data is data that is common to
66
business processes included in the same process flow, 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 to provide the production
plan registration request information designation screen 5 creen (the
production plan register screen: see Fig. 12) used to designate
the production plan registration request information for making
the production plan information registration request according
to the request from the mobile terminal 31, receive and accept
10 the production plan registration request information designated
through the production plan registration request information
designation screen from the mobile terminal 31, specify a
configuration quantity of a component of a production target
product based on a scheduled production quantity of a production
15 target product included in the accepted production plan
registration request information and the production target
product related information, and register the production plan
information including a configuration quantity of a specified
component and the scheduled production quantity of the production
20 target product included in the production plan registration
request information, 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
25 in the business system and rapidly register valid information
67
(production plan information).
[0129]
In other words, 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 5 ous 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
10 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, 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
15 load required for data processing in the business system that
is necessary for registering the production plan 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
20 tables on a relevant business process are referred to. 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 project specifying data, the status data, the
25 common data, and the process-specific data is constructed, and
68
a search of information necessary for registering the production
plan information is performed with reference to the process data
table, and thus it is unnecessary to refer to a plurality of
data tables, it is possible to significantly reduce a processing
load required for a search of data in the business system 5 that
is necessary for registering the production plan information,
and it is possible to significantly reduce a creation load of
a processing program for a data search.
[0130]
10 Further, a configuration quantity of a component of a
production target product is specified using the production
target product related information capable of specifying a
configuration quantity of a component of a product with reference
to a reference quantity, and the production plan information
15 including a configuration quantity of a specified component and
a scheduled production quantity of a production target product
included in the production plan registration request information
is registered to the process flow data stored in the process
flow data table PT, and thus it is possible to significantly
20 reduce a processing load required for data processing in a
business system that is necessary for registering the production
plan information.
[0131]
Further, in the above-described embodiment, the mobile
25 terminal management server 10 is configured to provide the
69
production plan registration result information representing
the production plan information registration result to the mobile
terminal 31, and thus it is possible to cause the user to check
the registration result.
5 [0132]
Further, in the above-described embodiment, the mobile
terminal management server 10 is configured to provide the actual
production performance registration request information
designation screen (actual production performance registration
10 screen: see Fig. 14) used to designate the actual production
performance registration request information for making the
actual production performance information registration request
according to the request from the mobile terminal 31, receive
and accept the actual production performance registration
15 request information designated through the actual production
performance registration request information designation
screen from the mobile terminal 31, check whether or not a product
of an actual production performance target is scheduled to be
produced using the manufacturing order identification
20 information (the manufacturing order number) corresponding to
the product of the actual production performance target included
in the accepted actual production performance registration
request information with reference to the process flow data
stored in the process flow data table PT, register the actual
25 production performance information representing that a delivery
70
of the product of the actual production performance target is
completed when it is checked that the product of the actual
production performance target is scheduled to be produced, and
updates the process flow data, and thus it is unnecessary to
5 refer to a plurality of data tables, it is possible to
significantly reduce a processing load required for a search
of data in a business system that is necessary for registering
the actual production performance information, and it is possible
to significantly reduce a creation load of a processing program
10 for a data search.
[0133]
Further, in the above-described embodiment, the mobile
terminal management server 10 is configured to provide the actual
production performance registration result information
15 representing the actual production performance information
registration result from the mobile terminal 31, and thus it
is possible to cause the user to check the registration result.
[0134]
Further, in the above-described embodiment, the database
20 (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
25 searched for with reference to the process flow data to the client
71
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
5 is reduced.
[0135]
Further, although not particularly mentioned in the
above-described embodiment, the mobile terminal management
server 10 executes the above-described processes (see Fig. 4
10 and Fig. 10) according to a processing program (a mobile terminal
management program) stored in a storage medium equipped therein.
Industrial Applicability
[0136]
15 According to the present invention, it is useful in
reducing a processing load required for a data search and in
outputting valid information rapidly in a business system
(specifically, an ERP system) that provides information about
a report to a mobile communication terminal.
20
Reference Signs List
[0137]
10 mobile terminal management server
20 relay
25 31 to 3N mobile terminals
72
40 communication network
51, 52, 53 communication network
100, 200, 300 enterprise resource planning system
110, 310 core business server
120, 220 5 DWH server
500 report inquiry system
73

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 5 quest 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 process flow
including a plurality of business processes;
10 a production target product related information storage
unit that stores production target product related information
capable of specifying a reference quantity of a production target
product and a configuration quantity of a component of the product
with respect to the reference quantity;
15 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 data being common to business processes included
20 in the same process flow,
the process-specific data being specific to each business
process included in the same process flow,
a production plan registration request information
designation screen providing unit that provides a production
25 plan registration request information designation screen used
74
to designate production plan registration request information
for making a production plan information registration request
according to a request from the mobile terminal;
a production plan registration request information
accepting unit that receives and accepts the production 5 plan
registration request information designated through the
production plan registration request information designation
screen from the mobile terminal;
a configuration quantity specifying unit that specifies
10 a configuration quantity of a component of the production target
product based on a scheduled production quantity of the
production target product included in the production plan
registration request information accepted by the production plan
registration request information accepting unit and the
15 production target product related information; and
a production plan information registering unit that
registers production plan information including the
configuration quantity of the component specified by the
configuration quantity specifying unit and the scheduled
20 production quantity of the production target product included
in the production plan registration request information to the
process flow data stored in the process flow data storage unit.
2. The mobile terminal management server according to claim
25 1, further comprising a production plan registration result
75
information providing unit that provides production plan
registration result information representing the production
plan information registration result to the mobile terminal.
3. The mobile terminal management server according to c5 laim
1 or 2, further comprising:
an actual production performance registration request
information designation screen providing unit that provides an
actual production performance registration request information
10 designation screen used to designate actual production
performance registration request information for making an
actual production performance information registration request
according to a request from the mobile terminal;
an actual production performance registration request
15 information accepting unit that receives and accepts the actual
production performance registration request information
designated through the actual production performance
registration request information designation screen from the
mobile terminal;
20 a production schedule checking unit that checks whether
or not a product of an actual production performance target is
scheduled to be produced using manufacturing order
identification information corresponding to the product of the
actual production performance target included in the actual
25 production performance registration request information
76
accepted by the actual production performance registration
request information accepting unit with reference to the process
flow data stored in the process flow data storage unit; and
an actual production performance information registering
unit that registers actual production performance 5 information
representing that a delivery of the product of the actual
production performance target is completed when the production
schedule checking unit checks that the product of the actual
production performance target is scheduled to be produced, and
10 updates the process flow data.
4. The mobile terminal management server according to claim
3, further comprising an actual production performance
registration result information providing unit that provides
15 the actual production performance registration result
information representing the actual production performance
information registration result to the mobile terminal.
5. A mobile terminal management program that operates
20 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:
25 a process flow data storage unit that stores process flow
77
data including various kinds of data related to a process flow
including a plurality of business processes; and
a production target product related information storage
unit that stores production target product related information
capable of specifying a reference quantity of a production 5 on target
product and a configuration quantity of a component of the product
with respect to the reference quantity,
the process flow data including status data, common data,
and process-specific data,
10 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
15 process included in the same process flow,
the mobile terminal management program causing mobile
terminal management server to execute:
a production plan registration request information
designation screen providing process of providing a production
20 plan registration request information designation screen used
to designate production plan registration request information
for making a production plan information registration request
according to a request from the mobile terminal;
a production plan registration request information
25 accepting process of receiving and accepting the production plan
78
registration request information designated through the
production plan registration request information designation
screen from the mobile terminal;
a configuration quantity specifying process of specifying
a configuration quantity of a component of the 5 production target
product based on a scheduled production quantity of the
production target product included in the production plan
registration request information accepted in the production plan
registration request information accepting process and the
10 production target product related information; and
a production plan information registering process of
registering production plan information including the
configuration quantity of the component specified in the
configuration quantity specifying process and the scheduled
15 production quantity of the production target product included
in the production plan registration request information to the
process flow data stored in the process flow data storage unit.