DESCRIPTION
Title of Invention
PORTABLE TERMINAL MANAGEMENT SERVER AND PORTABLE TERMINAL
5 MANAGEMENT PROGRAM
Technical Field
[OOOl]
I
The present invention relates to a portable terminal
10 managing server that is a server operated by ERP ~ and provides
I
various kinds of data through a communication network in
I
accordance with a request from a portable terminal used by
a user and a portable terminal managing program installed to
a portable terminal managing server.
15
Background Art
[0002]
Conventionally, as package software used for building
an enterprise system of a company, package software called
20 enterprise resource planning (ERP) is in the main stream.
Manyenterprise systems (integratedenterprise systemsor ERP
systems) to which such ERP is installed are built on
relational databases. Thus, many application programs are
designed mainly for business processing, and there are many
25 enterprise systems operated not mainly for outputting forms.
[0003]
Under such circumstances, various data warehouse
systems responsible for complementary roles of enterprise
systems are provided which are for the purpose of processing
a large amount of business data at a high speed, analyzing
the business data from various angles, and outputting forms
5 (see Patent Literature 1).
[0004]
Such backbone information management systems used for
the purpose of outputting forms, which provide information
of a form or the like for a portable communication terminal
10 (portable terminal), are proposed (see Patent Literatures 2
and 3).
Citation List
Patent Literature
15 [0005]
Patent Literature 1: JP 2002-312208 A
Patent Literature 2: JP 2003-323582 A
Patent Literature 3: JP 2007-200136 A
20 Summary of Invention
Technical Problem
[0006]
According to the above-described backbone information
management systems providing information such as forms for
25 portable communicationterminals, while there is convenience
of enablingthe acquisition of informationatavisitingplace
or during transportation, there is a problem of increasing
the risk of information leakage. Thus, in backbone
information management systems providing information of
forms or the like for portable communication terminals,
high-level security is required.
Inthe above-describedbackboneinformationmanagement
system, generally, licenses are given to the user side, and
the use of the system is approved only to licensees. Like
I 10 above, it is determined whether a user is registered or not
based on a license. However, for example, there is a problem
in that one license may be illegally used by a plurality of
users. Inacasewheresuchalicenseisillegallyused, while
it is apparent that there is a considerable disadvantage for
15 a supervisor of the system, the system is used by an
unauthorized user. Accordingly, invalid data may be
inserted into registration data of a registered user, or
registration data of a registered user may be downloaded
illegally. Accordingly, fromthe viewpoint of improvingthe
20 security of the system and protecting the supervisor of the
system and users, a technology for preventing such
unauthorizeduse in an easy and reliablemanner is requested.
[ 0 0 0 8 ]
An object of the present invention is to improve the
25 security of a system by preventing an unauthorized behavior
based on an illegal license in a business system (ERP system)
providing information relating to a form for a portable
communication terminal and protecting a supervisor of the
system and users by solving the problems described above.
Solution to Problem
[00091
According to the present invention, there is provided
a portable terminal managing server that is a server operated
by ERP and provides various kinds of data through a
communication network in accordance with a request from a
portable terminal used by a user. The portable terminal
managing server includes: a process flow data storing means
that stores process flowdataincludingvarious kinds of data
relating to a process flow including a plurality of business
processes so as to be inquirable for the portable terminal;
a login determining means that determines whether login is
permitted to the portable terminal based on presented user
license information when there is a login request from the
portable terminal presenting the user license information,
which is license information issued to the user from a server
supervisor ofthe portable terminal managing server; a login
processingmeansthatperforms aloginprocessina case where
the login is determined to be permitted by the login
determining means; a process request reception means that
accepts various process requests fromthe portable terminal
that is in a login state for which the login process is
performed by the login processing means; and a process
performing means that performs a predetermined process in
accordance with the process request accepted by the process
request receptionmeans. The process performingmeans makes
the process request by presenting server license information
that is server license information as license information
issued to the server supervisor and can uniquely specify the
user license information in a case where the process request
is made for an integrated enterprise system exhibiting a
functionbycommunicatingwiththeportableterminalmanaging
server as a predetermined process.
[OOlO]
By employing the above-described configuration, in a
business system providing information relating to a form for
a portable terminal, the security of the system can be
improvedbypreventing anunauthorizedbehaviorthatisbased
on an illegal license, and a system supervisor and users can
be protected.
[OOll]
The server license information may be used as the user
license information, and the login determining means may be
configured to determine whether login is permitted to the
portable terminal by determining whether or not the user is
a registered user based on the server license information
presented as the user license information.
[0012]
It may be configured such that one piece of the user
license information is issuable for one piece of the server
license information and is license information associated
with one piece of the server license information, the login
determining means determines whether login is permitted to
the portable terminal by determining whether or not the user
is a registered user based on the presented user license
5 information, and the process performing means makes the
process request for the integrated enterprise system by
presentingthe serverlicenseinformationassociatedwiththe
user license information usedbythe login determiningmeans
with one-to-one correspondence.
10 [0013]
A user ID and a password may be used as the license
information.
[0014]
In addition, according to the present invention, there
15 is provided a portable terminal managing program that causes
a portable terminal managing server to perform a process of
providing various kinds of data through a communication
network in accordance with a request froma portable terminal
used by a user by operating ERP. The portable terminal
20 managingprogramcausestheportableterminalmanaging server
including a process flow data storing means that stores
process flow data including various kinds of data relating
to aprocess flow including apluralityofbusiness processes
so as to be inquirable for the portable terminal to perform:
25 determining whether login is permitted to the portable
terminal based on presented user license information when
thereisaloginrequestfromtheportableterminalpresenting
the user license information, which is license information
issued to the user from a server supervisor of the portable
terminalmanaging server; performingaloginprocessinacase
where the login is determined to be permitted in the
5 determining of whether login is permitted; accepting various
process requests fromthe portable terminal that is in a login
state for which the login process is performed in the
performing of aloginprocess; andperformingapredetermined
process in accordance with the process request accepted in
10 theacceptingofvariousprocess requests. Intheperforming
I
I of a predetermined process, the process request is made by
~I presenting server license information that is server license
i
information as license information issued to the server I supervisor and can uniquely specify the user license
15 information in a case where the process request is made for
an integrated enterprise system exhibiting a function by
communicating with the portable terminal managing server as
a predetermined process.
20 Advantageous Effects of Invention
[0015]
According to the present invention, the security of a
systemcanbeimprovedbypreventinganunauthorizedbehavior
based on an illegal license in a business system providing
25 information relating to a form for a portable terminal, and
a supervisor of the system and users can be protected.
Brief Description of Drawings
[0016]
Fig. 1 is a block diagram that illustrates a
configuration example of a backbone information management
5 system.
Fig. 2 is a block diagram that illustrates a
configurationexampleofaportableterminalmanaging server.
Fig. 3 is an explanatory diagram that illustrates an
example of the stored state of process flow data.
10 Fig. 4 is an explanatory diagram that illustrates the
stored state of update condition data.
Fig. 5 is a flowchart that illustrates an example of
a process flow data providing process.
Fig. 6 is an explanatory diagram that illustrates an
15 example of a data search screen.
Fig. 7 is an explanatory diagram that illustrates an
example of a search result screen.
Fig. 8 is a flowchart that illustrates an example of
an authentication process.
20 Fig. 9 is a timing diagram that illustrates a content
of the authentication process.
Fig. 10 is a flowchart that illustrates another example
of the authentication process.
Fig. 11 is an explanatory diagram that illustrates an
25 example of user information.
Fig. 12 is a timing diagram that illustrates another
content of the authentication process.
Fig. 13 is a flowchart that illustrates an example of
a process flow data updating process.
Fig. 14 is an explanatory diagram that illustrates an
example of an editing screen.
I
I
I 5 Fig. 15 is a flowchart that illustrates an example of
l
a database updating process.
Fig. 16 is a flowchart that illustrates an example of
a form output process.
Fig. 17 is an explanatory diagram that illustrates an
10 example of a process flow data updating request input screen.
I Fig. 18 is an explanatory diagram that illustrates an
example of an update error notification displaying screen.
Fig. 19 is an explanatory diagram that illustrates an
example of a form displaying screen.
15 Fig. 20 is an explanatory diagram that illustrates the
transition of a form status based on the process flow data
state.
Fig. 21 is a block diagram that illustrates another
configuration example of a backbone information management
20 system.
Fig. 22 is a flowchart that illustrates further another
example of the authentication process.
Fig. 23 is an explanatory diagram that illustrates
another example of the user information.
25 Fig. 24 is a timing diagram that illustrates further
another content of the authentication process.
Description of Embodiment
[0017]
Hereinafter, an example according to an embodiment of
the present invention will be describedwith reference tothe
5 drawings.
Fig. 1 is a block diagram that illustrates a
configuration example of a backbone information management
system500 accordingtoanembodiment ofthepresent invention.
As illustratedin Fig. 1, thebackbone informationmanagement
10 system 500 includes: a portable terminal managing server 10;
arepeater20; apluralityofportableterminals 31to 3N (here,
N is an arbitrary positive integer); and integrated
enterprise systems 100, 200, and 300. The portable terminal
managing server 10 and the portable terminals 31 to 3N are
15 interconnectedthroughacommunicationnetwork40 suchas the
Internet and the repeater 20. The portable terminalmanaging
server 10 is connected to the integrated enterprise systems
100, 200, and 300 through a local area network (LAN) or
communication networks 51, 52, and 53 such as dedicated
20 communication lines. In addition, the portable terminals or
the integrated enterprise systems may be configured to be
communicable with each other through the portable terminal
managing server or to be non-communicable with each other.
[0018]
25 The integrated enterprise system 100 includes an
enterprise server 110, a data warehouse server (DWH server)
120, and a process flow DB 101. The integrated enterprise
system 200 includes a DWH server 220 and a process flow DB
201. The integrated enterprise system 300 includes an
enterprise server 310 and a process flow DB 301.
[0019]
5 A plurality of the integrated enterprise systems 100,
200, and 300 having mutually-different configurations
communicate (transmit or receive various kinds of
information) with the portable terminal managing server 10
as is necessary (that is, according to the function of each
10 system), thereby exhibiting the functions of the integrated
enterprise systems. In other words, as a backbone
information management system 500, even the system 200 not
includinganenterprise server or the system300 not including
a DWH server can exhibit the function of the integrated
15 enterprise systembycommunicatingwiththeportableterminal
managing server 10. In addition, although not illustrated
in the figure, even a system not including a process flow DB
can exhibit the function of the integrated enterprise system
bystoringprocess flow data inthe portable terminalmanaging
20 server 10. In the enterprise server or the like included in
each enterprise system, a known technology is used, and thus,
hereinafter, the integrated enterprise system 100 will be
described as an example.
[0020]
25 It is assumed that the enterprise server 110 and the
DWHserver120 are connectedtoeachotherthroughadedicated
communication line.
[0021]
For example, the enterprise server 110 is a server that
is managed by the supervisor of the backbone information
management system 500 andhas various functions formanaging
(for example, generation, update, storage, and the like of
information) form information relating to various tasks.
The enterprise server 110 is configured by a general
information processing apparatus including an operating
system (0s) and a relational DB.
[0022]
Here, a "form" is a general term of an account book and
a slip. In an "account book", items relating to receipts and
disbursements of money and products are written, anda "slip"
is source data for generating an account book and is a proof
of a business transaction or the like. In this example, a
case will be described in which the enterprise server 110
handles process data (data relatingto eachbusiness process)
representing only slip data as the form data.
[0023]
The enterprise server 110 performs various processes
in accordance with a business application program. As
examples of the business application program, there are a
sales managing program, a sales managing program, a
production control program, a financial accounting managing
program, and a management accounting managing program.
[0024]
The DWH server 120, for example, is a server that is
managed by a system supervisor of this system and has various
functions for implementing a data warehouse. Here, a "data
warehouse" represents a system analyzing the relevance
between items in the business data such as form data
accumulated in a time series. In addition, the DWH server
120hasa functionforconvertinga file inthe comma separated
values (CSV) format transmitted from the enterprise server
110 into a predetermined data format or the like and
registering various kinds of data in a predetermined storage
area. Furthermore, the DWH server 120 may be configured not
to convert the data format but to extract data corresponding
to each storage area from the state of the CSV format.
[0025]
The process flow DB 101 is a storage medium storing
process flow data configuredbyvarious kinds of process data
(or form data) that is collected, arranged, or the like by
various kinds of information processing using various
programs stored in a business application program DB (not
illustratedinthe figure) ofthe enterprise server 110. The
process flow data will be described in detail later. In this
example, the integrated enterprise system 100 includes a
business-related data DB (not illustrated in the figure)
managedbythe DWH server 120. The enterprise server 110 has
a function for converting the process data stored in the
process flow DB 101 into a CSV format in accordance with a
predetermined extraction condition and transmitted the
converted process data to the portable terminal managing
server 10. In addition, in this example, the enterprise
server110transmitsthe data file convertedintothe CSV form
to the portable terminal managing server 10 through the file
transfer protocol (FTP) .
[0026]
The portable terminal managing server 10 is a server
that is operated by the ERP and is a server that provides
various kinds of data through a communication network in
accordance with a request from a portable terminal used by
auser. T h e p o r t a b l e t e r m i n a l m a n a g i n g s e r v e r l O , forexample,
is configuredby an information processing apparatus such as
a WWW server and is managed by the system supervisor of the
backbone information management system 500 or a supervisor
of the portable terminal managing server 10 other than the
system supervisor of the backbone information management
system 500.
[0027]
Fig. 2 is a block diagram that illustrates a
configuration example of the portable terminal managing
server 10. As illustrated in Fig. 2, the portable terminal
managing serverloincludes: aprocess flowdatamanagingunit
11 performing a process relating to the management of the
process flow data; a login managing unit 12 performing a
process relating to the management of login; a process flow
data providing processing unit 13 performing a process of
providing the process flow data for the portable terminals
31 to 3N and the like; a process flow data updating processing
unit14 performingaprocess of updatingtheprocess flow data
in accordance with requests from the portable terminals 31
to 3N and the like; a customer information managing unit 15
performing a process relating to the management of customer
information; a business application program DB 17; a process
flow DB 18; and the other DB 19 storing various kinds of data
(for example, data used by various programs stored in the
business application program DB 17) that is necessary for
implementing the function of a general enterprise server.
Here, theother DB19is apart that is notparticularlyrelated
to the present invention, and thus, detailed description
thereof will not be presented.
[0028]
The business application program DB 17 is a storage
medium storing programs used for various businesses. As the
programs stored in the business application program DB 17,
there are a sales managing program, a purchase managing
program, aproductioncontrolprogram, a financial accounting
managing program, a management accounting managing program,
and the like.
[00291
The process flow DB 18 is a storage medium storing the
process flow data configuredbyvarious kinds of process data
(or form data) that is collected, arranged, or the like by
various kinds of information processing using various
programs stored in the business application program DB 17.
In this example, a case will be described in which the process
flow data including various kinds of data relating to a
process flow (business flow) including a plurality of
business processes is stored in a process flow table PT in
the process flow DB 18. In addition, in this example, a case
5 will be described in which the process flow data generated
for eachprocess flow is uniformlymanagedin one process flow
table PT by the portable terminal managing server 10.
Furthermore, in this example, it is assumed that slip data
(for example, for slip data corresponding to an order
10 acceptance slip, data that is associated with order
acceptance slip header information, order acceptance slip
specification information, delivery date and schedule, and
the like and is storedin a structure that is searchable based
on a key such as a slip number or the like; an order acceptance
15 number, a purchase order number, a shipping number, a storage
and retrieval number, an invoice inquiry, a billing number,
an accounting number, and the like are included in the slip
number) that is generallyusedis includedinthe process flow
data.
20 [0030]
In addition, a configuration may be employed in which
the portable terminal managing server 10 manages the process
flow data, for example, using a plurality of tables for each
type to be described later or for each data of which a part
25 (for example, an orderer or the like) of the content of common
data to be described later is the same.
[0031]
Fig. 3 is an explanatory diagram that illustrates an
example of the stored state of the process flow data in the
process flow DB18. As illustrate din Fig. 3, in this example,
theprocess flow data includes amain key section, a reference
5 key section, a type section, a status section, a common data
section, and a process specific data section. Here, items
(in other words, each 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
10 flow data. In other words, data relating to each business
process configuringthe process flow is storedto be assigned
to each section configuring the process flow data. Inaddition,
the process data relating to a process flow (for
example, a series of the process flow from order acceptance
15 froma companytodelivery) relatingtoa series of businesses
is stored in the same entry (in other words, the same row in
the process table PT) in the process flow table PT. By
employing such a configuration, the correspondence relation
among the process data can be defined.
20 [ 0 0 3 2 ]
Here, the "main key section" is a part, in which main
key data that is data used for uniquely specifyingtheprocess
flow data is stored, oftheprocess flowdata. Inthis example,
the main key section is configured by a process flow number
25 and a process flow specification number. In other words, in
this example, a combination of a process flow number and a
process flow specification number becomes an identifier (ID)
of each process flow data. The main key section is updated
at a time when the process flow data is registered for the
first time. Here, "a time when the process flow data is
registered forthe first time" represents atimewhen anentry
5 (data row) is added to the process flow data, for example,
a time when process data, which belongs to a specific process
flow, having a corresponding other process data that has not
been registered is registered. In addition, the "update"
described here includes the addition of data.
10 [0033]
Inaddition, the "process flow number" is an identifier
used for specifying one piece of process flow data (in other
words, one column in the process flow table PT illustrated
in Fig. 3). The process flow number is assigned to process
15 data having a predetermined item that is the same. In this
example, the same process flow number is assigned to the
process flow data having the same type and orderer among the
process flow data.
[0034]
20 Furthermore, the "process flow specification number"
is an identifier used for specifying specific process flow
data among the process flow data to which the same process
flow number is assigned. In other words, for example, in the
process flow table PT illustrated in Fig. 3, in the business
25 process "order acceptance" in the type "in-stock sales" of
the process flow, process flow data including process data
representing the order acceptance of the business of the
I be uniquely s p e c i f i e d u s i n g a combination of a p r o c e s s flow
number "000001" and a p r o c e s s flow s p e c i f i c a t i o n number
"0010" o r "0020".
5 [0035]
T h e r e a f t e r , t h e " r e f e r e n c e key s e c t i o n " is a p a r t i n
which r e f e r e n c e key d a t a , which is d a t a used f o r s p e c i f y i n g
another p r o c e s s flow d a t a ( o r a n o t h e r p r o c e s s d a t a ) r e l a t i n g
t o t h e process flow such a s an o r i g i n a l t r a n s a c t i o n of s a l e s
10 r e t u r n , is s t o r e d . I n t h i s e x a m p l e , t h e r e f e r e n c e key s e c t i o n
is configured by a r e f e r e n c e number and a r e f e r e n c e
s p e c i f i c a t i o n number. The r e f e r e n c e key s e c t i o n is updated
when t h e process flow d a t a is r e g i s t e r e d f o r t h e f i r s t t i m e .
[ 0 0 3 6 ]
15 In a d d i t i o n , i n t h e r e f e r e n c e number and t h e r e f e r e n c e
s p e c i f i c a t i o n n u m b e r , a ~ p r o c e s s f l o w n u m b e r a n d a p r o c e s s flow s p e c i f i c a t i o n number of a n o t h e r p r o c e s s flow r e l a t i n g t o t h e
I
I
I process flow a r e s t o r e d . However, i n a case where t h e r e is
I no o t h e r process flow r e l a t i n g t o t h e p r o c e s s flow a s i n t h e
~ 20 case of a new t r a n s a c t i o n , d a t a ( i n o t h e r words, t h e p r o c e s s
I
flow number is s t o r e d i n t h e r e f e r e n c e number, and t h e p r o c e s s I flow s p e c i f i c a t i o n number is s t o r e d i n t h e r e f e r e n c e ~ s p e c i f i c a t i o n number) r e p r e s e n t i n g t h e same v a l u e s a s t h o s e
I of t h e main key s e c t i o n of t h e same e n t r y a r e s t o r e d . I n
25 a d d i t i o n , i n a c a s e w h e r e t h e r e f e r e n c e key s e c t i o n r e p r e s e n t s
a n o t h e r p r o c e s s d a t a r e l a t i n g t o t h e p r o c e s s flow, d a t a used
f o r s p e c i f y i n g t h e type of p r o c e s s d a t a is f u r t h e r disposed
in the reference key section.
[0037]
Furthermore, the "type section" is a part in which type
data, which is data representingthetype of process flow such
5 as in-stock sales or sample shipping, is stored. The type
section is updated when the process flow data is registered
for the first time. Here, the kinds of process flows are not
limited to the in-stock sales and the sample shipping. In
addition, it is assumed that processes that are required are
10 determined in advance for each kind of the process flow (in
other words, the kinds and the numbers of included business
processes are different for each kind of the process flow).
[0038]
The "status section" is a part in which status data,
15 which is data (in other words, data representing the progress
statuses of a pluralityofbusiness processes includedinthe
process flow) representing the progress of the process flow
among the process flow data, is stored. In this example, the
status data is set to "0" for an unsettled business process
20 that is needed in the process flow and is set to "1" for a
settled business process, thereby representing the progress
of each business process. In other words, for example, as
illustrated in Fig. 3, in a process flow of the "in-stock
sales", in a case where the business processes included in
25 the process flow are "order acceptance", "shipping",
"delivery", "delivery inspection", and "sales", it is assumed
that process specific data (for example, order acceptance
d a t a ) r e l a t i n g t o t h e b u s i n e s s p r o c e s s "order acceptance" is
r e g i s t e r e d . In such a c a s e , i n t h e s t a t u s d a t a , a p a r t
corresponding t o t h e " s a l e s " is "I", and t h e o t h e r p a r t s a r e
maintainedtobeintheinitialstates ( i n o t h e r words, a s t a t e
5 i n which "0" is s e t ) .
[0039]
In o t h e r words, i n t h i s example, t h e s t a t u s s e c t i o n is
updatedforeachbusinessprocess. I n o t h e r w o r d s , t h e s t a t u s
s e c t i o n is updated when t h e p r o c e s s s p e c i f i c d a t a t o be
10 d e s c r i b e d l a t e r is input,'more p a r t i c u l a r l y , when each
b u s i n e s s p r o c e s s is determined t o have been completed i n
accordance with t h e s a t i s f a c t i o n of a predetermined s t a t u s
change c o n d i t i o n . Here, although t h e s t a t u s change
c o n d i t i o n is not p a r t i c u l a r l y l i m i t e d , i n t h i s example, it
15 is assumed t h a t " a l l t h e p r o c e s s s p e c i f i c d a t a corresponding
t o o n e b u s i n e s s p r o c e s s is input" is s t o r e d i n a p r e d e t e r m i n e d
s t o r a g e a r e a of t h e p o r t a b l e t e r m i n a l managing s e r v e r 10 a s
t h e s t a t u s change c o n d i t i o n .
[0040]
20 In t h i s example, s i n c e p r o c e s s f l o w s o f
m u t u a l l y - d i f f e r e n t kinds a r e s t o r e d i n t h e same t a b l e , t h e r e
is a case where t h e r e is a p a r t , which s t o r e s p r o c e s s d a t a
t h a t is unnecessary f o r a s p e c i f i c p r o c e s s flow, of items
(column i t e m s ) c o n f i g u r i n g t h e t a b l e . In such a c a s e , i n t h e
25 process flow t a b l e , a p a r t s t o r i n g t h e unnecessary p r o c e s s
d a t a becomes empty d a t a , and "0" is s t o r e d i n t h e s t a t u s d a t a
corresponding t o t h e empty d a t a .
[0041]
Inaddition, the "commondata sectionWis apart storing
common data that is data (in other words, data that is common
to business processes included in the same process flow) not
5 depending on a business process such as an orderer or a
shipping destination among the process flow data. The common
data section is updated when the process flow data is
registered for the first time.
[0042]
10 The "process specific data section" is a part storing
the process specificdata that is data uniquetoeachbusiness
process included in the same process flow such as order
acceptance date or data (for example, text data representing
precautions such as "due date requisite arrival" or "fragile
15 goods (attention: fragi1egoods)"registeredineachbusiness
process among the process flow data. The process specific
data section is updated for each business process.
Accordingly, in this example, among the process flow data,
data that depends on a business process is the "process
20 specific data" and data that does not depend on a business
process is the "common data"
[0043]
While the process flow data of this example has been
described as above, the definitions of various terms
25 represented in Fig. 3 will be simply described.
[0044]
First, the "order acceptance" represents a state in
which an order is received froma customer anda contract with
the customer is made. In addition, the "shipping
instruction" represents a state in which an instruction for
shipping a product is made for a warehouseman or a
distribution staff. The "delivery" represents that a
product is shipped from the warehouse and starts to be
transferred. In addition, the "inspection" represents that
the inspectionis completedbythecustomer, andtheownership
of the product is changed over to the customer. The 'sales"
represents a state in which the customer's inspection is
checked, and the amount of claims for the customer is
finalized (the claims are accounted).
[0045]
In addition, the term "inspection" is usedto represent
an "operation ofinspectingwhether or nota suppliedproduct
or service has the specifications (the quantity, the color,
the shape, and the quality as ordered) as ordered" or the
"transition of ownership of assets at the time of completion
ofthe inspection" as well. In addition, in final accounting
(or institutional account) or on an ERP system, in order to
clarify the transition timing ofthe ownership ofthe assets,
an event of "inspection" is defined to be different from the
delivery.
[0046]
In this example, in the process flow DB 18, an update
condition table UT in which update condition data
representing an update condition ofthe process flow data (or
the process flow table PT) is registered may be included.
[0047]
Fig. 4 is an explanatory diagram that illustrates the
stored state of the update condition data that is stored in
5 the update condition table UT in the process flow DB 18. As
illustrated in Fig. 4, in this example, the update condition
data includes a name of the business process, the type of
process flow, and a process flow data update condition.
[0048]
10 Here, the "process flow data update condition"
representsaregistrationconditionofprocessdataaccording
to the type of process flow. In this example, in a case where
process data relatingto a specificbusiness process is added
to the process flow data, the process flow data update
15 condition represent st he typeof processdata (inotherwords,
the type of business process to be completed in the process
flow) to be included in the process flow data as the premise
thereof. In other words, in the case of the update condition
table UT illustrated in Fig. 4, for example, for adding
20 process data relating to the business process "delivery
inspection" to the process flow data of the type "in-stock
I
I sales", it is necessary for the process data relating to the
I business processes "order acceptance", "shipping
I instruction", and "delivery" (in other words, in Fig. 4,
25 business processes in which "1's" are set in cells positioned
in the same column as the business process name "delivery
inspection" and the type "in-stock sales") determined in
advance to be registered in the process flow data. In
addition, the update condition table UT may be configured to
be generated by the supervisor of the backbone information
management system 500 or may be configured to be generated
by users using the portable terminals 31 to 3N.
[0049]
The portable terminalmanaging server10 has a function
of providing various kinds of data stored in the process flow
DB 18 and the other DB 19 in accordance with requests from
predetermined external apparatuses, in this example, the
portable terminals 31 to 3N and the integrated enterprise
systems 100, 200, and 300. In other words, the portable
terminal managing server 10 has a function of the enterprise
server. In other words, the portable terminal managing
server 10 includes an ERP engine.
[0050]
In addition, although not illustrated in the figure,
in this example, the portable terminal managing server 10 is
assumed to have a function as a DWH server having various
functions for realizing a data warehouse. The portable
terminal managing server 10 includes the ERP engine and the
configuration for the function of the DWH server, and
accordingly, information requested as an integrated
enterprise system can be provided also for the integrated
enterprise systems (for example, the integrated enterprise
system 100 having both the enterprise server and the DWH
server, the integrated enterprise system 200 having only the
DWH server, and the integrated enterprise system 300 having
only the DWH server) having mutually different
configurations.
[0051]
5 Each one of the portable terminals 31 to 3N is an
informationprocessingapparatus suchas an I Pad (registered
trademark) including a central processing unit (CPU) , a ROM,
a RAM, a display unit, and the like. In this example, each
one of the portable terminals 31 to 3N is assumed to include
10 various kinds of applications such as a Web browser and the
like used for handling form data. In addition, in this
example, each one of the portable terminals 31 to 3N has a
function of defining a query (a search item, a search key,
an extraction key, and the like) for acquiringnecessary form
15 data (in this example, the process flow data) from the
portable terminal managing server 10, for example, in
accordance with a user's operationinputandtransmittingthe
query to the portable terminal managing server 10.
[0052]
20 In this example, each one of the portable terminals 31
to 3N has a function of communicating with the portable
terminal managing server 10 through the repeater 20 and the
communication network 40 and displaying data acquired from
the portable terminal managing server 10 on the display unit
25 using the function of software such as a predetermined Web
application (Web browser) .
[0053]
Next, the operation of the backbone information
management system 500 of this example will be described with
reference tothe drawings. The contents ofthe operation and
the process that are not particularly related to the present
5 invention may not be presented.
[0054]
Fig. 5 is a flowchart that illustrates an example of
a process flow data providing process performed by the
portable terminal managing server 10 or the like in the
10 backbone information management system 500 of this example.
Here, a case will be described as an example in which the
portable terminal managing server 10 provides process flow
data in accordance with a request from a portable terminal
31 used by a user X.
15 [0055]
In the process flow data providing process, first, the
portable terminal 31 receives a login request according to
a login operation of the user X (Step S101). As this login
operation, for example, an operation of inputting a password
20 set in advance or the like may be considered. When the login
to the portable terminal 31 is permitted, it is permitted to
perform various operations for using various functions
mounted in the portable terminal 31.
[ 0 0 5 6 ]
25 In the state in which the user Xisloggedintheportable
terminal 31, when a predetermined login operation is
performed by the user XI the portable terminal 31 accesses
the portable terminal managing server 10 and performs a login
request (Step S102). In this login request, for example,
predetermined information (for example, a digital
certificate issued to the user X, a user ID and a password,
5 or the like) used for a login determination set in advance
is presented.
LO0571
I
I
When the login request is received, the login managing I
I
unit 12 of the portable terminal managing server 10 performs
I
10 anauthenticationprocess used fordeterminingwhether or not
I ~ the login is permitted (Step S103a). This authentication
process, for example, may be performed using a user ID, a
password, a digital certificate, and the like.
[0058]
15 When the login is determined to be permitted (Y in Step
I
S103b), the loginmanagingunit12 sets the portable terminal
31 to be in a login state. Here, the setting of the portable
terminal 31 to be in a login state represents setting a
software application used for handling form data, which is
20 installed to the portable terminal 31, to be effective (a
usable state). When the login state is set, the process flow
data providing processing unit 13 of the portable terminal
managing server 10 transmits data search screen information
representing a data search screen to the portable terminal
25 31 (Step S104). On the other hand, when the login is
determined not to be permitted (N in Step S103b), the login
managingunit12 endsthe process flow data providingprocess
without s e t t i n g t h e p o r t a b l e t e r m i n a l 31 t o be i n t h e l o g i n
s t a t e . In a d d i t i o n , when t h e l o g i n is determined not t o be
p e r m i t t e d , t h e l o g i n managing u n i t 12 performs a p r o c e s s of
n o t i f y i n g t h e p o r t a b l e t e r m i n a l 3 1 o f an i n d i c a t i o n t h e r e o f .
5 [0059]
When t h e d a t a s e a r c h s c r e e n information is r e c e i v e d ,
t h e p o r t a b l e t e r m i n a l 31 d i s p l a y s a d a t a s e a r c h s c r e e n
r e p r e s e n t e d by t h e r e c e i v e d d a t a s e a r c h s c r e e n information
I ~
on t h e d i s p l a y u n i t included t h e r e i n (Step ,5105).
10 [0060]
Fig. 6 is an e x p l a n a t o r y diagram t h a t i l l u s t r a t e s an
example of t h e d a t a s e a r c h s c r e e n . As i l l u s t r a t e d i n Fig.
6, on t h e d a t a s e a r c h s c r e e n , a s e a r c h i t e m i n p u t a r e a 601
t o w h i c h a n i t e m ( s e a r c h i t e m ) t h a t is a s e a r c h t a r g e t is i n p u t ,
15 a s e a r c h word i n p u t a r e a 602 t o which a keyword ( s e a r c h word)
usedatthetimeofsearchingisinput, a b a c k b u t t o n B 1 p r e s s e d
f o r r e t u r n i n g t o t h e p r e v i o u s s c r e e n , and a s e a r c h b u t t o n B2
p r e s s e d f o r performing a s e a r c h a r e a r r a n g e d .
[0061]
20 On t h e d a t a s e a r c h s c r e e n , t h e u s e r X i n p u t s a s e a r c h
i t e m and a s e a r c h word by o p e r a t i n g an o p e r a t i n g u n i t ( f o r
example, a keyboard d i s p l a y e d on t h e d i s p l a y u n i t on which
a touch panel is arranged) i n c l u d e d i n t h e p o r t a b l e t e r m i n a l
31 and p r e s s e s t h e s e a r c h b u t t o n B2. To t h e s e a r c h i t e m , an
25 i t e m ( f o r e x a m p l e , a n o r d e r acceptance s l i p , a s t o c k , customer,
o r a p r o d u c t n a m e ) c o n f i g u r i n g t h e p r o c e s s f l o w d a t a is i n p u t .
To t h e s e a r c h word, a t e x t s t r i n g ( f o r example, t h e name of
a customer o r t h e name of a product) r e l a t i n g t o t h e p r o c e s s
flow d a t a is i n p u t .
[0062]
When t h e s e a r c h b u t t o n B2 is p r e s s e d i n t h e s t a t e i n
5 which t h e s e a r c h i t e m and t h e s e a r c h word a r e i n p u t , t h e
p o r t a b l e t e r m i n a l 31 p r e s e n t s t h e s e a r c h i t e m and t h e s e a r c h
word, w h i c h h a v e b e e n i n p u t , t o t h e p o r t a b l e terminalmanaging
s e r v e r 10 a s a s e a r c h c o n d i t i o n , t h e r e b y making a r e q u e s t f o r
providing p r o c e s s flow d a t a ( S t e p S106). Here, t h e
10 above-describedsearchconditionis anexample, andany o t h e r
c o n d i t i o n may be used a s long a s a r b i t r a r y p r o c e s s flow d a t a
( o r p r o c e s s d a t a c o n f i g u r i n g t h e p r o c e s s flow d a t a ) c a n b e
searched f o r t h e c o n d i t i o n .
[0063]
15 When t h e r e q u e s t f o r providing p r o c e s s flow d a t a is
r e c e i v e d , t h e p o r t a b l e t e r m i n a l managing s e r v e r 10 s e a r c h e s
f o r t h e p r o c e s s flow d a t a i n accordance with t h e s e a r c h
c o n d i t i o n p r e s e n t e d i n t h e r e c e i v e d providing r e q u e s t by
r e f e r r i n g t o t h e process flow DB 18 (Step S107). In a case
20 where corresponding d a t a is not p r e s e n t i n t h e p r o c e s s flow
DB18, t h e p o r t a b l e t e r m i n a l managing s e r v e r 10, i n Step S107,
r e q u e s t s t h e i n t e g r a t e d e n t e r p r i s e systems 100, 200, and 300
t o a c q u i r e t h e corresponding d a t a and a c q u i r e s t h e
c o r r e s p o n d i n g d a t a fromtheintegratedenterprise systems100,
25 200, and 300.
[0064]
When t h e p r o c e s s flow d a t a is r e t r i e v e d i n accordance
with the search condition, the portable terminal managing
server 10 transmits search result screen information
representing a search result screen that displays the
retrieved process flow data as a result of the search to the
5 portable terminal 31 (Step S108).
[0065]
When the search result screen information is received,
the portable terminal 31 displays the search result screen
representedbythe received search result screen information
10 on the display unit included therein (Step S109).
[0066]
Fig. 7 is an explanatory diagram that illustrates an
example of a search result screen. As illustrated in Fig.
7, on the search result screen, a display area 701 for
15 displaying a search result, a back button B1 pressed for
returning to the previous screen, and an editing button B3
pressed for editing the search result are arranged.
[0067]
Thereafter, whenanoperation forendingtheaccess such
20 as an operation of ending the browser is performedbythe user
X (Y in Step SllO), the portable terminal 31 makes a logout
request for the portable terminal managing server 10 (Step
S111). On the other hand, when an operation of continuing
the access such as pressing the back button B1 is performed
25 (N in Step SllO), the portable terminal 31 proceeds to the
process of Step S105 and displays the data search screen (see
Fig. 6).
[00681
When the search result screen information is
transmitted in Step S108, the login managing unit 12 starts
to measure a time (standby time) during which information is
not transmitted or received to or from the portable terminal
31andmonitors whether the standby time reaches (arrives at)
a predetermined time (for example, 5 minutes, 10 minutes, 30
minutes, or the like) (Step S112).
[0069]
Whenalogoutrequestis receivedduringthemeasurement
of the standby time (Y in Step S113) , the login managing unit
12 stops the measurement of the standby time, requests the
portable terminal 31 to remove history information
(communication history information, operation history
information, and the like) according to the current
communication (Step S114), and performs a logout process for
releasing the login state (Step S115).
[00701
Inaddition, when the standby time is determinedtohave
arrived at the predetermined time (Y in Step S112), the login
managing unit 12 stops the measurement of the standby time,
requests the portable terminal 31 to remove history
information (communication history information, operation
history information, and the like) according to the current
communication (Step S114) , and performs a logout process for
releasing the login state (Step S115).
[0071]
On the other hand, when the request for removing the
history information is received, the portable terminal 31
performs the process of removing history information
accumulated in the current communication with the portable
5 terminal managing server 10 (Step S116).
[0072]
As described above, it is determined whether to permit
login to the portable terminal managing server 10 in
accordance with a login request from the portable terminal
10 31 that can be operated by the login process, and the request
for providing process flow data is accepted in a case where
the login is permitted, and the process of providing the
process flow data inaccordance with the request is performed.
[0073]
15 Byperformingtheprocessofprovidingprocess flowdata
as described above, authentication can be performed both in
Steps SlOl and S103, it is possible to improve the security
atthetimeofprovidingtheprocess flowdata fortheportable
terminal 31.
20 [0074]
Here, a specific example of the above-described
authentication process (Step S103a) will be described. Fig.
8 is a flowchart that illustrates an example of the
authentication process of Step S103a. Fig. 9 is a timing
25 diagram that illustrates a content of the authentication
process. In this example, the authentication process is
performed using a user ID (ERP user ID) that is issued to a
user X by a system supervisor Y of the backbone information
management system 500 through a server supervisor Z of the
portable terminal managing server 10 and a password (ERP
password) assigned to the user X by the system supervisor Y
server supervisor Z ofthe portable terminal managing server
10. In this example, the ERP user ID and the ERP password
areassignedtotheuserx fromthe systemsupervisor Ythrough
the server supervisor Z of the portable terminal managing
10 server 10. Accordingly, the integrated enterprise systems
I
I 100, 200, and 300 and the portable terminal managing server
1 10 respectively maintain ERP user IDS and ERP passwords
assigned to users of this system 500. Here, a case will be
described as an example in which the authentication process
15 is performed using the ERP user ID and the ERP password of
the user X that are issued as a license for the integrated
enterprise system 100.
[00751
When a login request presenting the ERP user ID and the
20 ERP password is received from the portable terminal 31 (Step
SlOOl), the login managing unit 12 of the portable terminal
managing server 10, first, requeststhe authentication ofthe
user X by transmitting authentication request information
includingthe ERP user ID and the ERP password presented from
25 the portable terminal 31 to the integrated enterprise system
100 in the authentication process (Steps S501 and S1002).
[00761
When the authentication request is received, the
integrated enterprise system 100 performs an authentication
process for determining whether or not the user is a
registered user based on the ERP user ID and the ERP password
5 received from the portable terminal managing server 10 by
referring to user information (here, information in which an
ERP user ID, an ERP password, and the like of each user are
associated with each other) stored in a database included
therein and notifies the portable terminal managing server
10 10 of a result of the authentication process (Step S1003).
[0077]
When the notification of the result of the
authentication process is received (Step S502), the portable
terminal managing server 10 determines whether to permit the
15 login in accordance with the received notification (Step
S503) and permits the login of the portable terminal 31 in
a case where the login is determined to be permitted (Step
S1004) .
[0078]
20 After permitting the login, the portable terminal
managing server 10 performs various processes in accordance
with a request (Step S1005) from the portable terminal 31.
In such various processes, when requesting the integrated
enterprise system 100 to perform a process (a process such
25 as a search process, an information providing process, or an
information registering process), the portable terminal
managing s e r v e r 1 0 p e r f o r m s t h e p r o c e s s request by presenting
the ERP user ID and the ERP password presented from the
portable terminal 31 (Step S1006).
[0079]
Then, in a case where the user is determined to be a
5 registered user based on the ERP user ID and the ERP password
that have been presented, the integrated enterprise system
100 performs the requested process.
[0080]
As described above, since the portable terminal
I 10 managing server 10 managed by the server supervisor Z is
configured to perform authentication using the ERP user ID
l and the ERP password issued by the system supervisor Y of the
I backbone information management system 500, in the backbone
I I information management system 500 providing information
15 relating to a form for the portable terminal 31, the security
of the system can be improved by preventing an unauthorized
I behavior based on an illegal license, and the system
supervisor Y and the user X can be protected.
[0081]
20 Next, another specific example of the authentication
process (StepS103a) describedabovewillbedescribed. Fig.
10 is a flowchart that illustrates another example of the
authentication process of Step S103a. Fig. 11 is an
explanatory diagram that illustrates an example of the user
25 informationusedinthis example. Fig. 12is atimingdiagram
thatillustratesanothercontentofanauthenticationprocess.
In this example, the authentication process is performed
usingtheuser ID (ERPuser ID) issuedtotheportable terminal
managing server 10 by the system supervisor Y of the backbone
information management system 500, the password (ERP
password) assigned to the portable terminal managing server
5 10 by the system supervisor Y of the backbone information
management system 500, the user ID issued to the user by the
server supervisor Z ofthe portable terminal managing server
10, and the password issued to the user by the server
supervisor Z ofthe portable terminalmanaging server 10. In
10 thisexample, theERPuser I D a n d t h e E R P p a s s w o r d a r e a s s i g n e d
to the server supervisor Z of the portable terminal managing
server 10 by the system supervisor Y, and the user ID and the
password are assigned to the user X by the server supervisor
Z. Accordingly, the integratedenterprise systems 100, 200,
15 and 300 and the portable terminalmanaging server 10 maintain
the ERP user ID and the ERP password assigned to the server
supervisor Z of this system 500. Here, a case will be
described as an example in which an authentication process
is performed using the ERP user ID and the ERP password that
20 are associated with the user ID assigned to the user X by the
server supervisor Z, which are the ERP user ID and the ERP
password issued as a license of the integrated enterprise
system 100, and the user ID and the password assigned to the
userX fromthe server supervisor Z. Here, it is assumedthat
25 the ERP user ID and the ERP password and the user ID and the
password have one-to-one correspondence. In other words,
the server supervisor Z issues one license (one pair of a user
ID and a password) to the user for one license (one pair of
an ERP user ID and an ERP password) given from the system
supervisor Y.
[0082]
When alogin request presenting a user IDanda password
is received from the portable terminal 31 (Step SlOll), the
login managing unit 12 of the portable terminal managing
server 10 checks whether or not the user is a registered user
registered by the server supervisor Z using the user ID and
the password presented from the portable terminal 31 by
referring tothe user information (here, information inwhich
auser ID, apassword, andthe like ofeachuserareassociated
with each other) stored in a database included therein in the
authentication process (Step S511).
[0083]
When the determination whether the user is a registered
user is made, the portable terminal managing server 10
determines whether to permit login based on a result of the
determination (Step S503) and permits the login of the
portable terminal 31 in a case where the login is determined
to be permitted (Step S1012).
[0084]
After the login is permitted, the portable terminal
managing server 10 performs various processes in accordance
with a request (Step S1013) from the portable terminal 31.
In such various processes, when requesting the integrated
enterprise system 100 to perform a process (a process such
as a search process, an information providing process, or an
information registration process), the portable terminal
managing server 10 specifies the ERP user ID and the ERP
password associated with the user ID presented from the
5 p o r t a b l e t e r m i n a l 3 1 b y r e f e r r i n g t o t h e u s e r i n f o r m a t i o n (see
Fig. 11) stored in a database included therein and performs
the process request by presenting the ERP user ID and the ERP
password that have been specified (Step S1014).
[0085]
10 Then, in a case where the user is determined to be a
registered user by using the ERP user ID and the ERP password
that are presented, the integrated enterprise system 100
performs the requested process.
[0086]
15 As described above, since the portable terminal
managing server 10 managed by the server supervisor Z is
configured to perform authentication using the ERP user ID
and the ERP password issued by the system supervisor Y of the
backbone information management system 500 and the user ID
20 and the password issued to be uniquely associated with the
ERP user ID and the ERP password by the server supervisor Z,
in the backbone information management system 500 providing
information relating to a form for the portable terminal 31,
C
the security of the system can be improved by preventing an
25 unauthorized behavior based on an illegal license, and the
system supervisor Y and the user X can be protected.
[0087]
F i g . 1 3 is a f l o w c h a r t t h a t i l l u s t r a t e s an example of
a p r o c e s s flowdataupdatingprocessperformedbytheportable
t e r m i n a l managing s e r v e r 10 and t h e p o r t a b l e t e r m i n a l 31.
Here, a case w i l l be d e s c r i b e d a s an example i n which t h e
5 process flow d a t a is u p d a t e d i n a c c o r d a n c e w i t h a r e q u e s t from
t h e p o r t a b l e t e r m i n a l 31 used by t h e u s e r X.
[0088]
Steps S201 t o S209 ( i n c l u d i n g Steps S103a and S103b)
o f t h e p r o c e s s flowdataupdatingprocessarethe sameas Steps
10 ,5101 t o S109 (see Fig. 5; S t e p s S103a and S103b a r e included
t h e r e i n ) o f t h e p r o c e s s flow d a t a p r o v i d i n g p r o c e s s d e s c r i b e d
above, S t e p s S218 t o S224 of a b u s i n e s s d a t a updating p r o c e s s
a r e t h e same a s Steps SllO t o S116 ( s e e Fig. 5) of t h e process
flow d a t a providing p r o c e s s d e s c r i b e d above, and t h u s ,
15 d e t a i l e d d e s c r i p t i o n of Steps S201 t o S209 and S218 t o S224
of t h e b u s i n e s s d a t a updating p r o c e s s w i l l not be p r e s e n t e d .
[0089]
A f t e r t h e s e a r c h r e s u l t s c r e e n (see Fig. 7) r e p r e s e n t e d
by t h e s e a r c h r e s u l t s c r e e n information is d i s p l a y e d on t h e
20 d i s p l a y u n i t i n c l u d e d i n t h e p o r t a b l e t e r m i n a l 3 1 i n S t e p s 2 0 9
of t h e process flow d a t a u p d a t i n g p r o c e s s , when t h e p r e s s i n g
of t h e e d i t i n g b u t t o n B3 is r e c e i v e d , t h e p o r t a b l e t e r m i n a l
31 d i s p l a y s an e d i t i n g s c r e e n e n a b l i n g t h e e d i t i n g of t h e
s e a r c h r e s u l t d i s p l a y e d i n t h e d i s p l a y a r e a 701. Fig. 1 4 is
25 an e x p l a n a t o r y diagram t h a t i l l u s t r a t e s an example of t h e
e d i t i n g s c r e e n . A s i l l u s t r a t e d i n Fig. 1 4 , on t h e e d i t i n g
s c r e e n , an e d i t i n g a r e a 901 d i s p l a y i n g a s e a r c h r e s u l t t o be
editable, a back button B1 pressed for returning to the
previous screen, and an update button B4 pressed for
reflectingthe editing result on the process flow data stored
o n t h e p o r t a b l e t e r m i n a l m a n a g i n g s e r v e r 1 0 sidearearranged.
5 [0090]
By performing adding (for example, a new registration
of a slip), removing, changing, or the like of the process
flow data displayed in the editing area 604 by operating the
portable terminal 31 on the editing screen, the user X
10 performs an operation of editing the process flow data
displayed as a result of the search. Then, after the editing
operation ends, in a case where the editing result is to be
reflected on the process flow data stored on the portable
terminal managing server 10, the user X presses the update
15 button B4 by operating the portable terminal 31.
[0091]
When the pressing of the update button B4 is received,
the portable terminal 31 makes an information rewriting
request for requesting the portable terminal managing server
20 10 to reflect the editingresult (Step S21O). In this request,
the edited content, portable terminal managing server
information (for example, a digital certificate issued tothe
portable terminal managing server 10) relating to the
portable terminal managing server 10, and user information
25 (for example, a digital certificate issued to the user X or
the like) relating to the user XI and the like are presented.
[0092]
Whenthe information rewriting request is received, the
portable terminal managing server 10 accesses the process
flow DB 18 and performs a predetermined process (a pre-login
process) before login (Step S211) . In this example, the
5 portable terminal managing server 10 performs a process for
checking predetermined information (login determination
information, for example, a digital certificate issued tothe
portable terminal managing server 10, a digital certificate
issued to the user X, and the like) used for a login
10 determination as the pre-login process.
[0093]
When the login determination information is checkedby
the pre-login process, the portable terminal managing server
10 determines whether or not the login is permitted (Step
15 S212). This determination may be performed, for example,
using an ID, a password, a digital certificate, or the like.
[0094]
In a case where the login is determined tobe permitted,
the portable terminal managing server 10 sets the portable
20 terminal 31 to be in a login state (here, a state in which
an access to the process flow DB 18 is permitted) relating
to the reception of information from the portable terminal
31 (Step S213).
[0095]
25 When the portable terminal 31 is set to be in the login
state (in other words, the login is permitted) the portable
terminal managing server 10 performs a process of rewriting
corresponding process flow data stored in the process data
DB 18 in accordance with the information rewriting request
from the portable terminal 31 set in the login state (Step
S214). Then, the portable terminal managing server 10
5 transmits a rewrite notification used for a notification of
the rewriting according to the edited content to the
integrated enterprise systems 100, 200, and 300 (Step S215).
Thereafter, the integrated enterprise systems 100, 200, and
300 update the process flow DBs 101, 201, and 301 included
10 thereininaccordancewiththereceivedrewritenotification.
In the process flow DBs 18, 101, 201, and 301, the contents
rewritten in accordance with the information rewriting
request from the portable terminal 31 may be configured to
be stored. In other words, a configuration may be employed
15 in which the subject and the time of rewriting the process
flow data are recorded.
[0096]
When the information stored in the process flow DB 18
is rewritten, the portable terminal managing server 10
20 transmits a rewriting notification used for a notification
of the rewriting according to the edited content to the
portable terminal 31 (Step S216).
[0097]
When the rewriting notification is received, the
25 portable terminal 31 displays a rewriting reflection
notification used for notifying the user X of the reflection
of the edited result in a predetermined area of the editing
screen (Step 5217).
[0098]
Thereafter, similarly to the process flow data
providing process (see Fig. 5) described above, the process
5 of Step S218 and subsequent steps is performed.
[0099]
As described above, it is determined whether to permit
the login to the portable terminal managing server 10 in
accordance with a login request from the portable terminal
10 31 that can be operated by the login process (Step S103a),
a rewriting request for the process flow data is accepted in
a case where the login is permitted (Step S210), a pre-login
processisperformedfortheprocess flowDB18 ina case where
therewriting request is accepted (StepS211), andtheprocess
15 of rewriting the process flow data of the process flow DB 18
is performed in the case of the permission (Step S214).
[OlOO]
Byperformingthe process of rewriting the process flow
data as described above, authentication can be performed in
20 Steps S201, S103a, and Step S212 a total of three times, and
accordingly, the securityatthetime of updatingthe process
flow data in accordance with a request from the portable
terminal 31 can be improved. In addition, in a case where
the rewriting of information (data) is performed, by
25 configuring to perform a login determination different from
that of a case where the information is provided, the access
of the portable terminal 31 to various DBs can be limited,
whereby t h e s e c u r i t y a t t h e time of updating t h e p r o c e s s flow
d a t a i n accordance w i t h a r e q u e s t from t h e p o r t a b l e t e r m i n a l
31 can be improved.
[ O l O l ]
5 In t h e example d e s c r i b e d above, while a c o n f i g u r a t i o n
is employed i n which t h e p o r t a b l e t e r m i n a l managing s e r v e r
10 performs a l o g i n d e t e r m i n a t i o n f o r t h e p r o c e s s flow DB 18
e v e r y t i m e when a r e w r i t i n g r e q u e s t is r e c e i v e d by t h e
p o r t a b l e t e r m i n a l managing s e r v e r f r o m t h e p o r t a b l e t e r m i n a l
10 31, a n d d a t a is r e w r i t t e n i n a casewheretheloginispermitted,
a c o n f i g u r a t i o n m a y b e e m p l o y e d i n w h i c h t h e p o r t a b l e t e r m i n a l
managing s e r v e r 10 accumulates e d i t e d c o n t e n t s and
i n f o r m a t i o n ( i n f o r m a t i o n r e q u i r e d f o r a u t h e n t i c a t i o n )
relatingtotheportableterminals 3 1 t o 3 N t h a t a r e r e w r i t i n g
15 r e q u e s t s o u r c e s i n a case where r e w r i t i n g r e q u e s t s a r e
r e c e i v e d fromtheportableterminals 3 1 t o 3N, a n d a r e w r i t i n g
processisperformedfortheprocess f l o w D B 1 8 t h r o u g h a b a t c h
process a t predetermined timing ( f o r example, a t 23 of clock
every d a y ) . In such a c a s e , a t predetermined timing, l o g i n
20 d e t e r m i n a t i o n s a r e made by p r e s e n t i n g t h e information
r e l a t i n g t o t h e p o r t a b l e t e r m i n a l s 3 1 t o 3 N t h a t a r e r e w r i t i n g
r e q u e s t s o u r c e s , and only e d i t e d c o n t e n t s of which t h e
r e w r i t i n g r e q u e s t s o u r c e s areterminalapparatusespermitted
t o l o g i n may be r e f l e c t e d on t h e process flow d a t a i n t h e
25 process flow DB 18.
[0102]
I n o t h e r words, a c o n f i g u r a t i o n m a y b e e m p l o y e d i n w h i c h
4 6
the portable terminal managing server 10 receives an update
request (information rewriting request) of the process flow
data from a portable terminal that is in the login state,
update related information including an update content
5 (edited content) of the received update request and the
terminal information (for example, a digital certificate)
representing the portable terminal that has made the update
request is accumulated (for example, accumulatedina storage
mediumincludedinthe portable terminalmanaging server lo),
10 the process flow data is updated usingthe accumulatedupdate
related information in a batch mode at predetermined timing
(for example, 23 of clock every day or the like), and update
processes (information rewriting) according to the update
requests received fromthe portable terminals that are in the
15 login state are performedtogether. By configuring as such,
the number of accesses made to the process flow DB 18 can be
markedly decreased, and accordingly, the security can be
further improved.
[0103]
20 Fig. 15 is a flowchart that illustrates an example of
a database updating process performed by the portable
terminal managing server 10. In the database updating
process, a process for updating the process flow data stored
intheprocess f l o w D B 1 8 i s p e r f o r m e d i n t h e p o r t a b l e t e r m i n a l
25 managing server 10. In this example, the portable terminal
managing server 10 is assumed to acquire various kinds of
process data collected and arranged by various kinds of
information processing using various programs stored in the
business application program DB 17 and the process flow data
at a predetermined time, and the database updating process
to be described hereinafter is different from that of a case
5 (for example, the process flow data updating process
described above, see Fig. 13) where data is updated in
accordance with an update request fromthe portable terminals
31 to 3N.
[0104]
10 In the database updating process, first, the portable
terminal managing server 10 determines whether or not new
process flow data (new process flow data) has been acquired
(Step S301). Here, in a case where new process flow data is
determined not to have been acquired (N in Step S301), the
15 portable terminal managing server 10 proceeds to the process
of Step S303 to be described later.
[0105]
On the other hand, in a case where new process flow data
is determined to have been acquired (Y in Step S301), the
20 portable terminal managing server 10 registers the acquired
process flow data in the process flow table PT (Step S302).
[0106]
Thereafter, the portable terminal managing server 10
determines whether or not process data (in other words, data
25 relatingtobusiness processes configuringthe process flow)
corresponding to the process flow data, which has been
registered, has been acquired (Step S303).
[0107]
The determination whether the process data acquiredby
the portable terminalmanaging server10 is process data that
has been registered is performed by determining whether or
5 not process flow data having a combination of a process flow
number and a process flow specification number included in
the acquired data is stored in the process flow table PT.
Accordingly, in this example, data (in other words, a process
flow number and a process flow specification number)
10 configuring the main key section is required to be included
in the data (data input by an operator of the business, or
data generated by a business application program) acquired
by the portable terminal managing server 10.
[0108]
15 Here, in a case where it is determined that the process
data corresponding to the process flow data that has been
registered has not been acquired (N in Step S303), the
portable terminalmanaging server10 specifies a storage area
corresponding to the acquired data by referring to the other
20 DB 19, registers the acquired data (Step S304) , and proceeds
to the process of Step S301.
[0109]
On the other hand, in a case where it is determined that
the process data corresponding to the process flow data that
25 has been registered has been acquired (Y in Step S303), the
portable terminal managing server 10 specifies update
condition data corresponding tothe acquired process data by
r e f e r r i n g t o t h e update c o n d i t i o n t a b l e UT corresponding t o
t h e a c q u i r e d p r o c e s s d a t a (Step S305). In t h i s example, t h e
p o r t a b l e t e r m i n a l managing s e r v e r 10 s p e c i f i e s update
c o n d i t i o n d a t a based on t h e kinds of t h e b u s i n e s s p r o c e s s
5 r e p r e s e n t e d by t h e p r o c e s s d a t a and t h e i d e n t i f i c a t i o n
information of t h e p r o c e s s flow ( i n o t h e r words, t h e process
flow number and t h e process flow s p e c i f i c a t i o n number).
[ O l l O ]
When t h e update c o n d i t i o n d a t a is s p e c i f i e d , t h e
10 p o r t a b l e t e r m i n a l managing s e r v e r 10 determines whether o r
not t h e p r o c e s s flow d a t a s a t i s f i e s an update c o n d i t i o n
r e p r e s e n t e d by t h e s p e c i f i e d update c o n d i t i o n d a t a (Step
S306). I n o t h e r w o r d s , theportableterminalmanagingserver
10 determines whether o r not t h e a c q u i r e d p r o c e s s d a t a is
15 r e g i s t e r e d i n t h e p r o c e s s f l o w t a b l e P T a s a p a r t o f t h e p r o c e s s
flow d a t a based on t h e p r o c e s s flow d a t a and t h e update
c o n d i t i o n d a t a . In t h i s example, t h e p o r t a b l e t e r m i n a l
managing s e r v e r 1 0 comparesthe s t a t u s s e c t i o n o f t h e process
flow d a t a corresponding t o t h e a c q u i r e d p r o c e s s d a t a and t h e
20 update c o n d i t i o n d a t a with each o t h e r a n d d e t e r m i n e s t h a t t h e
process flow d a t a s a t i s f i e s t h e update c o n d i t i o n i n a case
where a l l t h e b u s i n e s s p r o c e s s e s s e t t o "1" i n t h e update
c o n d i t i o n d a t a a r e s e t t o "1" i n t h e s t a t u s s e c t i o n a s w e l l .
[ O l l l ]
25 Here, i n a case where it is determined t h a t t h e p r o c e s s
flow d a t a does not s a t i s f y t h e update c o n d i t i o n r e p r e s e n t e d
by t h e s p e c i f i e d update c o n d i t i o n d a t a (N i n Step S306), t h e
p o r t a b l e terminalmanaging s e r v e r 1 0 performs a p r e d e t e r m i n e d
e r r o r process (Step S307) and proceeds t o t h e p r o c e s s of Step
S301. Here, t h e " e r r o r process" is not p a r t i c u l a r l y l i m i t e d
a s long a s it is a p r o c e s s not updating t h e p r o c e s s flow d a t a .
5 Thus, f o r example, t h e e r r o r p r o c e s s may be a p r o c e s s i n which
t h e process d a t a is t e m p o r a r i l y s t o r e d i n a predetermined
s t o r a g e a r e a u n t i l t h e update c o n d i t i o n is s a t i s f i e d o r a
process ( i n o t h e r w o r d s , aprocessofnotifyingthesupervisor
of a n e r r o r , a p r o c e s s o f n o t i f y i n g t h e s u p e r v i s o r o f a c o n t e n t
10 of t h e update c o n d i t i o n t h a t is not s a t i s f i e d , o r t h e l i k e )
f o r c h e c k i n g t h e cause o f t h e a c q u i s i t i o n o f t h e p r o c e s s d a t a
not s a t i s f y i n g t h e update c o n d i t i o n .
[0112]
On t h e o t h e r hand, i n a case where it is determined t h a t
15 t h e p r o c e s s flow d a t a s a t i s f i e s t h e update c o n d i t i o n
r e p r e s e n t e d b y t h e s p e c i f i e d u p d a t e c o n d i t i o n d a t a ( Y i n Step
S306), t h e p o r t a b l e t e r m i n a l managing s e r v e r 10 updates t h e
process flow d a t a r e g i s t e r e d i n t h e process flow t a b l e PT
(Step S308). In o t h e r words, t h e p o r t a b l e t e r m i n a l managing
20 s e r v e r 10 r e g i s t e r s t h e a c q u i r e d p r o c e s s d a t a i n t h e p r o c e s s
flow t a b l e PT.
[0113]
When t h e p r o c e s s flow d a t a is updated, t h e p o r t a b l e
t e r m i n a l managing s e r v e r 10 determines whether o r not a
25 p r e d e t e r m i n e d s t a t u s change conditionrelatingtotheprocess
flow d a t a is s a t i s f i e d i n accordance with t h e update of t h e
process flow d a t a (Step S309). Here, i n a case where it is
determined that the predetermined status change condition is
not satisfied in accordance with the update of the process
flow data (N in Step S309), the portable terminal managing
server 10 proceeds to Step S301.
5 [0114]
On the other hand, in a case where it is determined that
the predetermined status change condition is satisfied in
accordance with the update ofthe process flow data (Yin Step
S309), the portable terminal managing server 10 updates the
10 status data included in the process flow data based on the
satisfied status change condition (Step S310) and proceeds
to the process of Step S301.
[0115]
In this example, the database updating process, for
15 example, ends by an end operation of the supervisor of the
portable terminal managing server 10.
[0116]
Thedatabaseupdatingprocessmaybeaprocessperformed
in real time or a batch process performed for every specific
20 unit time. In addition, the database updating process may
be a process (a near real-time process) having a partial
real-time property such as a process in which real time
processing is performed only during a designated period.
[0117]
25 Fig. 16 is a flowchart that illustrates an example of
a form output process performed by the portable terminal
managing server 10 and the portable terminal 31. In the form
o u t p u t p r o c e s s , a s t h e p o r t a b l e t e r m i n a l managing s e r v e r 10
p r o v i d e s t h e process flow d a t a ( a p a r t of o r t h e w h o l e process
flow d a t a ) f o r t h e p o r t a b l e t e r m i n a l 31, a p r o c e s s of
d i s p l a y i n g a form on t h e d i s p l a y s c r e e n included i n t h e
5 p o r t a b l e t e r m i n a l 31 is performed. For managing l o g i n , t h e
same process a s t h a t o f t h e above-described p r o c e s s flow d a t a
p r o v i d i n g p r o c e s s ( s e e Fig. 5) is performed, and t h u s
descriptionthereofwillnotbepresentedhere. I n a d d i t i o n ,
i n t h e form o u t p u t p r o c e s s , a form having a predetermined
10 format is o u t p u t , which is d i f f e r e n t from t h e process flow
d a t a providing p r o c e s s .
[0118]
In t h i s example, a case w i l l be d e s c r i b e d a s well i n
which t h e p o r t a b l e t e r m i n a l managing s e r v e r 10 updates t h e
15 process flow d a t a i n accordance w i t h a r e q u e s t from t h e
p o r t a b l e t e r m i n a l 31. In t h i s example, a p r o c e s s flow DB 18
u p d a t i n g p r o c e s s ( i n o t h e r words, t h e p r o c e s s of u p d a t i n g t h e
process flow DB 18 i n t h e form o u t p u t p r o c e s s ) d e s c r i b e d here
is one example o f t h e d a t a b a s e u p d a t i n g p r o c e s s ( s e e Fig. 1 5 ) .
20 [0119]
I n t h e f o r m o u t p u t p r o c e s s , f i r s t , t h e p o r t a b l e t e r m i n a l
31 t r a n s m i t s a r e q u e s t f o r a p r o c e s s flow d a t a updating
r e q u e s t i n p u t s c r e e n t o t h e p o r t a b l e terminalmanaging s e r v e r
10, f o r example, i n accordance with an o p e r a t i n g i n p u t of t h e
25 u s e r X using t h e p o r t a b l e t e r m i n a l 31 (Step S501).
[0120]
When t h e r e q u e s t f o r t h e p r o c e s s flow d a t a updating
request input screen is received, the portable terminal
managing server 10 transmits the process flow data updating
request input screen in accordance with the received request
for the process flow data updating request input screen (Step
5 S401).
[0121]
Whentheprocess flowdataupdatingrequestinputscreen
is received, the portable terminal 31 displays the process
flow data updating request input screen on the display screen
10 of the display unit included therein (Step S502).
[0122]
Fig. 17 is an explanatory diagram that illustrates an
example ofthe process flowdataupdatingrequest input screen.
As illustrated in Fig. 17, on the process flow data update
15 requesting input screen, a main key data input area 1201 for
receiving an input of identification information (in this
example, data corresponding to the main key section of the
process flow data, in other words, a process flow number and
a process flow specification number) of an update target, a
20 business process input area 1202 for receiving an input of
the kind of the business process represented by the process
data from the user X, a detailed data input area 1203 for
receiving an input of the content of the other process data,
a back button 1204 for receiving a request for switching the
25 display screen output to the display unit to another display
screen, and an update button 1205 for receiving an update
request of the process flow data based on the content input
to each input area (in this example, the main key data input
area 1201, the business process input area 1202, and the
detailed data input area 1203) are arranged.
[0123]
5 On the process flow data updating request input screen,
the user X operates an operating unit (for example, a display
area orabuttondisplayedonthe display unit onwhich atouch
panel is arranged) included in the portable terminal 31. In
other words, for example, when each input area is pressed by
10 a finger of the user X, the portable terminal 31 starts to
receive an input of text data (including numbers and
characters) for the pressed input area. Then, the portable
terminal 31, for example, displays a keyboard (not
illustrated in the figure) on the display unit on which the
15 touch panel is arranged, receives an input of text data from
the user X, and displays the received text data in a selected
area. In addition, when a selection of the business process
inputarea1202is received, t h e p o r t a b l e t e r m i n a l 3 1 d i s p l a y s
predetermined business process names to be selectable in a
20 pull-down form. The method of inputting the process data is
not limited thereto, and, for example, a configuration may
be employed in which the portable terminal 31 receives a
plurality of pieces of process data arranged in a
predetermined data format at once.
25 [0124]
When the selection of the update button 1205, which is
made by the user X, is received, the portable terminal 31
determines that a process flow data updating request
according to process data configured by data input to each
input area is received (Step S503).
[0125]
5 In a case where the process flow data updating request
(update request) is determined to be received, the portable
terminal 31 transmits the received update request to the
portable terminal managing server 10 (Step S504).
[0126]
10 When the update request is received, the portable
terminal managing server 10 acquires process flow data
corresponding to the received update request among the
process flow data registered in the process flow table PT
(StepS402). Inaddition, at this time, theportable terminal
15 managing server 10 acquires the process flow data including
the main key data (in other words, the data input to the main
key data input area 1201) represented by the update request
as process flow data corresponding to the update request (in
other words, the received process data). Here, the
20 "acquisition" represents temporary storage in a
predetermined storage area for performing a comparison
between the process flow data and the update condition data
or the like in the process to be described later.
101271
25 When the process flow data corresponding to the update
request is acquired, the portable terminal managing server
10 acquires update condition data according to the update
r e q u e s t ( S t e p S403). Here, t h e update c o n d i t i o n d a t a
according t o t h e update r e q u e s t r e p r e s e n t s update c o n d i t i o n
d a t a t h a t can be s p e c i f i e d by t h e b u s i n e s s p r o c e s s and t h e
type ( i n o t h e r w o r d s , abusinessprocessinputtothebusiness
5 process i n p u t a r e a 1202 and t h e type r e p r e s e n t e d by t h e
process flow d a t a a c q u i r e d i n t h e p r o c e s s of Step S402) of
t h e process flow d a t a t h a t a r e r e p r e s e n t e d by t h e update
r e q u e s t (see Fig. 4 ) .
[0128]
10 Whentheupdateconditiondataisacquired, t h e p o r t a b l e
t e r m i n a l managing s e r v e r 10 compares t h e a c q u i r e d process
flow d a t a and t h e update c o n d i t i o n d a t a with each o t h e r (Step
S404) and determines whether o r not t h e update c o n d i t i o n of
t h e p r o c e s s flow d a t a is s a t i s f i e d (Step S405).
15 [0129]
Here, i n a case where one o r more i t e m s set t o "1" i n
t h e update c o n d i t i o n d a t a a r e not set t o "1" i n t h e s t a t u s
s e c t i o n of t h e p r o c e s s flow d a t a , and it is determined t h a t
t h e update c o n d i t i o n o f t h e p r o c e s s flow d a t a is not s a t i s f i e d
20 ( N i n Step S405), t h e p o r t a b l e t e r m i n a l managing s e r v e r 10
g e n e r a t e s an update e r r o r n o t i f i c a t i o n , t r a n s m i t s t h e update
e r r o r n o t i f i c a t i o n t o t h e p o r t a b l e t e r m i n a l 31 (Step S406),
and ends t h e p r o c e s s .
[0130]
25 When t h e update e r r o r n o t i f i c a t i o n is r e c e i v e d ( Y i n
Step S505), t h e p o r t a b l e t e r m i n a l 3 1 d i s p l a y s a n u p d a t e e r r o r
n o t i f i c a t i o n d i s p l a y i n g s c r e e n on t h e d i s p l a y s c r e e n of t h e
display unit included therein based on the received update
error notification (Step S506).
[0131]
Fig. 18 is an explanatory diagram that illustrates an
5 example of the update error notification displaying screen.
As illustrated in Fig. 18, on the update error notification
displaying screen, an update error notification displaying
area 1301displayedto overlap the process flow data updating
request input screen is arranged. Here, in this example, in
10 the update error notification displaying area 1301, in
addition to a fixed phrase used for notifying the user X of
an update error, a detailed display button 1302 used for
receiving a request for displaying a detailed update
condition and a close button 1303 for receiving a request for
15 removing the update error notification displaying area 1301
from the display screen are arranged.
[0132]
In accordance with the reception of the selection of
the detailed display button 1302, which is made by the user
20 X, for example, the portable terminal 31 displays a result
ofthe comparisonbetween the process flow data and the update
condition data in the portable terminal managing server 10
in a form (for example, a comparison table representing a
status section of the process flow data and the process flow
25 data updating condition of the update condition data) that
can be recognized by the user X.
[0133]
On the other hand, i n a case where a l l the items s e t
t o "1" i n the update condition data are not s e t t o "1" i n the
s t a t u s s e c t i o n of the process flow data, and it is determined
t h a t the update condition of the process flow data is
5 s a t i s f i e d (Y i n Step S405), the portable terminal managing
server 10 adds the process data represented by the update
request t o the process flow data and updates the process flow
data (Step S407).
[0134]
10 When the process flow data is updated, the portable
terminal managing server 10 transmits the updated process
flow data t o the portable terminal 31 (Step S408) and ends
the process.
[0135]
15 When the process flow data is received, the portable
t e r m i n a l 3 1 d i s p l a y s t h e formdisplayingscreenonthedisplay
screen of the display u n i t included t h e r e i n based on the
received process flow data (Step S507).
[0136]
20 Fig. 1 9 is an explanatory diagram t h a t i l l u s t r a t e s an
example of a form displaying screen. As i l l u s t r a t e d i n Fig.
19, on the formdisplaying screen, a formdisplayingarea1401
d i s p l a y i n g a formbasedontheprocess f l o w d a t a , a f o r m s t a t u s
displaying area 1402, a back button 1403, and a change button
25 1404 are arranged. I n a d d i t i o n , the p o r t a b l e terminal 31,
f o r example, changes t h e s c a l e of the form displayed i n the
form displaying area 1 4 0 1 i n accordance with an operation of
a keyboard or the like that is included in the portable
terminal 31.
[0137]
Here, in the form displaying area 1401, a part of or
5 the whole process flow data is displayed in a predetermined
display form. In this example, it is assumedthatinformation
used for displaying a part of or the whole process flow data
in a predetermined display form is generated by the portable
terminalmanagingserver10 andistransmittedtotheportable
10 terminal 31, for example, at timing of Step S408 in the form
output process. In addition, a configurationmaybe employed
in which the portable terminal 31 displays a part of or the
whole process flow data, which has been received, in the form
displaying area 1401 in a predetermined display form based
15 on information stored in a storage apparatus included
therein.
[0138]
In addition, the form status displaying area 1402 is
an area for displaying the kind (or a status; hereinafter,
20 referred to as a status) of the form displayed in the form
displaying area 1401. As the statuses of the form, for
example, various statuses such as an order acceptance slip,
a delivery slip, an inspection slip, or an invoice may be
considered.
25 [0139]
The back button 1403 is a button used for receiving a
request for returning the display screen to the process flow
data updating request input screen. In addition, a
configuration may be employed in which, in accordance with
the reception of the selection of the back button 1403 that
ismadebytheuserx, t h e p o r t a b l e t e r m i n a l 3 1 n o t o n l y r e t u r n s
5 the display screen to the process flow data updating request
input screen but also transmits a request for cancelling the
update of the process flow data based on the update request
to the portable terminal managing server 10. In such a case,
in accordance with the selection of the back button 33, the
10 portable terminal 31maybe configuredto display the process
flow data updating request input screen in a state in which
the text data (a selected business process in the business
process input area 1202) input in each input area (in this
example, the main key data input area 1201, the business
15 process input area 1202, and the detailed data input area
1203). By employing such a configuration, the user X can
check the input content in an easy manner.
[0140]
The change button 1404 is a button used for receiving
20 a request for changing the display content in the form
displaying area 1401. Hereinafter, the process of changing
the display content of the form displaying area 1401 will be
described.
[0141]
25 When the form displaying screen is displayed, the
portable terminal 31 determines whether or not a form status
changing request has been received from the user X (Step
S508).
[0142]
In this example, the portable terminal 31, first,
r e c e i v e s t h e s e l e c t i o n o f t h e f o r m s t a t u s d i s p l a y i n g a r e a 1 4 0 2
5 that is made by the user X. Then, when the selection of the
form status displaying area 1402 that is made by the user X
is received, the portable terminal 31 displays a list of form
status names representingthe displayable shapes ofthe form
to be selectable, for example, in a pull-down form.
10 [0143]
It is assumed that the form status names displayed here
are received together with the process flow data from the
portable terminal managing server 10. More specifically,
the portable terminal managing server 10 specifies form
15 status names representing the displayable shapes of the form
based on the data (form shape data) relating to the shape of
the form stored in a predetermined storage area and the
process flow data state (in other words, the input state of
eachcolumnitemoftheprocess flowtablePT). Inotherwords,
20 for example, in a case where the type of process flow data
transmitted to the portable terminal 31 is the "in-stock
sales", and only the process data relating to the business
process "order acceptance" is registered in the process
specific data section, the portable terminal managing server
25 10 specifies onlya "order acceptance s1ip"asthe formstatus
name. In addition, in a case where the process data relating
to the business process "delivery" is registered in addition
t o t h e process d a t a r e l a t i n g t o t h e b u s i n e s s p r o c e s s "order
acceptance", t h e p o r t a b l e t e r m i n a l managing s e r v e r 10
s p e c i f i e s an " o r d e r a c c e p t a n c e s l i p " and a " d e l i v e r y s l i p "
a s t h e form s t a t u s names.
5 [0144]
Fig. 20 is an explanatory diagram t h a t i l l u s t r a t e s t h e
t r a n s i t i o n of a form s t a t u s based on t h e p r o c e s s flow d a t a
s t a t e . As i l l u s t r a t e d i n Fig. 20, images 1501 t o 1504 a r e
assumed t o be t h e shapes of t h e forms (more s p e c i f i c a l l y , t h e
10 s l i p s ) d i s p l a y a b l e i n t h e form d i s p l a y i n g a r e a 1401 based on
t h e process flow d a t a . I n a d d i t i o n , t h e images 1501 t o 1504
a r e e x p l a n a t o r y d i a g r a m s fordescribingthetransitionofthe
form s t a t u s and a r e not s p e c i f i c w r i t i n g examples f o r
achieving t h e r o l e s of v a r i o u s forms.
15 [0145]
Here, t h e image 1504 w i l l be d e s c r i b e d a s an example.
In t h e image 1504, a r e a s 1511, 1512, and 1513 a r e a r e a s ( i n
t h i s example, textstringdisplayingareas) r e p r e s e n t i n g f o r m
s t a t u s names, t h e type of p r o c e s s flow, and names of t h e
20 b u s i n e s s p r o c e s s e s o f t h e p r o c e s s d a t a i n c l u d e d i n t h e p r o c e s s
flow d a t a , r e s p e c t i v e l y . I n t h i s example, t h e form s t a t u s
names corresponding t o t h e kinds o f t h e p r o c e s s d a t a included
i n t h e process flow d a t a a r e d i s p l a y e d i n t h e a r e a 1511.
[0146]
25 In t h i s c a s e , a s i l l u s t r a t e d i n a t r a n s i t i o n from t h e
image 1501 t o t h e image 1504 i n Fig. 20, when p r o c e s s d a t a
corresponding t o each b u s i n e s s p r o c e s s is r e g i s t e r e d f o r one
piece of the process flow data, the number of the kinds of
the form status names (in other words, the displayable shapes
of the forms based on the process flow data) increases. This
represents not "whether there is a form of the next kind" but
5 "the statuses of the forms increases in accordance with the
process flowdata state (inotherwords, thedisplayable kinds
of the forms increases)".
[0147]
Hereinafter, description will be continued for a case
10 as an example in which, before the process of Step S507 in
the form output process, the portable terminal 31 receives
process flow data including the business processes "order
acceptance", "shipping instruction", "delivery", and
"delivery inspection". In addition, in this example, in the
15 process of Step S507, the portable terminal 31 is assumed to
display a form corresponding to the form status name "order
a c c e p t a n c e s 1 i p " c o r r e s p o n d i n g t o t h e b u s i n e s s p r o c e s s "order
acceptance" located on the upper-most side of the business
processes "order acceptance", "shipping instruction",
20 "delivery", and "delivery inspection" in the process flow
represented by the received process flow data in the form
displaying area 1401 (see Fig. 19). The portable terminal
31 may be configured to display a form corresponding to the
business process corresponding to process data newly added
25 to the process flow data in the process of Step S407 in the
form displaying area 1401.
[0148]
In t h e form s t a t u s changing r e q u e s t r e c e i v i n g
determining p r o c e s s ( S t e p S508), i n a case where it is
determined t h a t a form s t a t u s changing r e q u e s t h a s n o t been
received from t h e u s e r X ( N i n Step S508), t h e p o r t a b l e
5 t e r m i n a l 31 proceeds t o t h e p r o c e s s of Step S510 t o be
d e s c r i b e d l a t e r .
[0149]
On t h e o t h e r hand, i n a case where it is determined t h a t
t h e form s t a t u s changing r e q u e s t has been r e c e i v e d from t h e
10 u s e r X (Y i n Step S508), t h e p o r t a b l e t e r m i n a l 31 d i s p l a y s
a form according t o t h e r e c e i v e d changing r e q u e s t i n t h e form
d i s p l a y i n g a r e a 1401 (Step S509). In t h i s example, t h e
p o r t a b l e t e r m i n a l 3 1 r e c e i v e s t h e s e l e c t i o n o f t h e f o r m s t a t u s
name " d e l i v e r y s l i p " corresponding t o t h e b u s i n e s s process
15 "delivery" t h a t is made by t h e u s e r X and d i s p l a y s t h e form
( d e l i v e r y s l i p ) corresponding t o t h e b u s i n e s s p r o c e s s
"delivery" i n t h e form d i s p l a y i n g a r e a 1401. In a d d i t i o n ,
i n t h i s c a s e , t h e p o r t a b l e t e r m i n a l 31 d i s p l a y s t h e form
s t a t u s n a m e " d e l i v e r y s 1 i p " i n t h e formstatusdisplayingarea
20 1402.
[0150]
When t h e form according t o t h e form s t a t u s changing
r e q u e s t is d i s p l a y e d , t h e p o r t a b l e t e r m i n a l 31 determines
whether t o end t h e form o u t p u t p r o c e s s ( S t e p S510). Here,
25 i n a case where it is determined t h a t t h e form o u t p u t p r o c e s s
does not end (N i n Step S510), t h e p o r t a b l e t e r m i n a l 31
proceeds t o t h e p r o c e s s of Step S508.
[0151]
On the other hand, in a case where it is determined that
the form output process ends (Y in Step S510), for example,
in accordance with the reception of a predetermined ending
5 operation that is performed by the user X, the portable
terminal 31 ends the process.
[0152]
As described above, in the above-described embodiment,
a configuration is employed in which the portable terminal.
10 managing server 10 that is a server operated by the ERP and
provides various kinds of data through the communication
network in accordance with requests from the portable
terminals used by users includes the process flow DB 18
storingthe process flow data including various kinds of data
15 relatingtotheprocess flowincludingapluralityofbusiness
processes so as to be inquirable for the portable terminal
31, determines whether to permit login for the portable
terminal 31based on presented user license information when
there is a login request from the portable terminal 31
20 presentingthe user license information (for example, a user
ID and a password) that is license information issued to the
user X from the server supervisor Z of the portable terminal
managing server 10, performs a login process in a case where
the login is determined to be permitted, receives various
25 process requests from the portable terminal 31 that is in the
login state for which the login process has been performed,
performs a predetermined process (for example, various
processes performed in accordance with requests from the
portable terminal 31 such as an inquiry of form data or
registration of form data) in accordance with the received
I process request, and, in a case where a process request for
5 the integrated enterprise system100 exhibiting the function
by communicating with the portable terminal managing server
10 is to be made as the predetermined process, makes the
processrequestbypresentingserverlicenseinformationthat
is server license information (for example, an ERP user ID
10 and an ERP password) as license information issued to the
server supervisor Z andcanuniquely specify the user license
information (corresponding to a case where the specifying can
beperformedbasedonone-to-one correspondence, a case where
the specifying can be performed by using the server license
15 information as the user license information, or the like).
Accordingly, an advantage of improving the security of a
system by preventing an unauthorized behavior based on an
illegal license in a business system (for example, the
backbone information management system 500) providing
20 information relating to a form for the portable terminal 31
and protecting a supervisor of the system and users can be
acquired.
[0153]
In other words, a configuration is employed in which
25 the portable terminal managing server 10 determines whether
to permit login forthe portableterminal31based on the user
license information issued to the user X from the server
supervisor Z and, in a case where a process request is to be
made for the integrated enterprise system 100 in accordance
with the process request from the portable terminal 31 that
is inthe login state, makes the process request by presenting
5 the server license information that is the server license
information as license information issued to the server
supervisor Z and can uniquely specify user license
information. Accordingly, it can be determined whether to
permit login to the portable terminal 31 based on the user
10 license information that can be uniquely specified by the
server license information, and an illegal behavior such as
illegal use of illegal user license information can be
prevented, wherebythe securityofthe systemcanbeimproved,
and the system supervisor and the users can be protected.
15 [0154]
In addition, in the above-described embodiment, in a
case where a configuration is employed in which the server
license information is used as the user license information,
and it is determined whether to permit login to the portable
20 terminal 31 by determining whether the user X is a registered
user based on the server license information presented as the
userlicenseinformationusingtheportableterminalmanaging
server 10, it can be determined whether to permit login to
t h e p o r t a b l e t e r m i n a l 3 l b a s e d o n t h e u s e r l i c e n s e i n f o r m a t i o n
25 using the server license information, and accordingly, an
illegal behavior such as illegal use of illegal user license
information can be prevented, whereby the security of the
users can be protected.
[0155]
Furthermore, in the above-described embodiment, in a
5 case where the configuration is employed in which one piece
of the user license information can be issued to one piece
ofthe server license information and is license information
associated with one piece ofthe server license information,
it is determined whether to permit login to the portable
10 terminal 31 by determining whether the user is a registered
user based on the presented user license information using
the portable terminal managing server 10, and the process
request is made for the integrated enterprise system 100 by
presentingthe serverlicenseinformationassociatedwiththe
15 user license information used for a login determination with
one-to-one correspondence, it can be determined whether to
permit login to the portable terminal 31 based on the user
license information associated with the server license
information with one-to-one correspondence. Accordingly,
20 an illegal behavior such as illegal use of illegal user
license information can be prevented, whereby the security
of the system can be improved, and the system supervisor and
the users can be protected.
[0156]
25 In addition, in the above-described embodiment, since
a configuration is employed in which the portable terminals
31 to 3N are permitted to login only in a case where a regular
login operation determined in advance is received, the
authentication may be configured to be necessary in the
portable terminals 31to 3N, andaccordingly, double ortriple
authenticationmaybe configuredtobenecessary, whereby the
security can be further improved.
[0157]
Furthermore, in the above-described embodiment, since
a configuration is employed in which the portable terminal
managing server 10 performs a logout process for releasing
the login state in accordance with a logout request from any
of the portable terminals 31 to 3N and requests the portable
terminals 31 to 3N to remove communication history
information relating to providing slip data in accordance
with the logout process (for example, Step SS114; see Fig.
5), the communication history information can be removed,
whereby information leakage due to the loss of the portable
terminals 31 to 3N or the like can be prevented.
[0158]
In addition, in the above-described embodiment, since
a configuration is employed in which the portable terminal
managing server 10 measures a time during which information
is not received or transmitted from or to the portable
terminals 31 to 3N that are in the login state and requests
the portable terminals 31 to 3N to remove the communication
history information relating to providing the process flow
data when the measured time arrives at a predetermined time
(for example, Step S112; see Fig. 5), the communication
history information can be removed, whereby information
leakage due to the loss of the portable terminals 31 to 3N
or the like can be prevented.
[0159]
5 While not particularly described in the
above-described embodiment, even in a case where a backbone
information management system 501, for example, including a
data synchronization server 60 as illustrated in Fig. 21 is
used, similarly to the case of the backbone information
10 management system 500, each process described above can be
performed.
[0160]
Fig. 21 is a block diagram that illustrates a
configuration example ofthebackbone informationmanagement
15 s y s t e m 5 0 1 a c c o r d i n g t o a n e m b o d i m e n t o f t h e p r e s e n t i n v e n t i o n .
As illustrated in Fig. 21, the backbone information
management system 501includes: a portable terminal managing
server 10; a data synchronization server 60; a repeater 20;
a plurality of portable terminals 31 to 3N (here, N is an
20 arbitrary positive integer); and integrated enterprise
systems 100, 200, and 300. The portable terminal managing
server 10 and the portable terminals 31 to 3N are
interconnected through the data synchronization server 60,
a communication network 40 such as the Internet, and the
25 repeater 20. The portable terminal managing server 10 is
connected to the integrated enterprise systems 100, 200, and
300 through communication networks 51, 52, and 53 such as a
local area network (LAN) or dedicated communication lines.
In addition, the portable terminals or the integrated
enterprise systems may be configuredto be communicable with
each other through the portable terminal managing server or
5 to be non-communicable with each other. Furthermore, the
portable terminal managing server 10 is connected tothe data
synchronization server 60 through a communication network
such as a LAN or a dedicated communication line.
[0161]
10 The data synchronization server 60 is interposed
between the portable terminal managing server 10 and the
portable terminals 31 to 3 N and has a function for
synchronizing the process data stored in the portable
terminals 31to 3 N and the process data storedina DBincluded
15 therein with each other in accordance with a predetermined
synchronization rule (for example, a rule for synchronizing
predetermined data only). The data synchronization server
60, for example, is configured by an information processing
apparatus such as a WWW server and is managed by the system
20 s u p e r v i s o r o f t h e b a c k b o n e i n f o r m a t i o n m a n a g e m e n t s y s t e m 5 0 1 .
[0162]
Here, a specific example ofthe authentication process
in a case where the configuration ofthe backbone information
management system 501is employedwillbe described. In such
25 a case, the authentication process (Step S103a) and the like
described above are not performed, and, similarly, the
authentication process is performed by the data
Fig. 22 is a flowchart that illustrates an example of
the authentication process performed by the data
5 synchronizationserver 60. Fig. 23is anexplanatorydiagram
that illustrates an example of the user information used in
this example. Fig. 24 is a timing diagram that illustrates
further another content of the authentication process. It
is assumedthatthe authenticationprocess is performedusing
10 a user ID (ERP user ID) assigned to the portable terminal
managing server 10 by a system supervisor YY of the backbone
informationmanagement system 501, a password (ERP password)
assigned to the portable terminal managing server 10 by the
system supervisor YY of the backbone information management
15 system 501, a user ID (DDS user ID) assigned to the user X
by a server supervisor ZZ of the data synchronization server
60, and a password (DDS password) assigned to the user X by
the server supervisor ZZ of the data synchronization server
60. The user information including the ERP user ID, the ERP
'20 password, the DDS user ID, and the DDS password is
synchronized in the data synchronization server 60 and the
portable terminal managing server 10, and the data
synchronization server 60 and the portable terminal managing
server 10 maintain the user information to be common thereto.
25 Here, a case will be described as an example in which the
authentication process is performed using the ERP user ID,
the ERP password, and the like issued as a license of the
i n t e g r a t e d e n t e r p r i s e system 100. In a d d i t i o n , t h e ERP u s e r
I D a n d t h e ERPpasswordandthe DDS u s e r I D a n d t h e DDSpassword
areassociatedwitheachotherwithone-to-onecorrespondence.
I n o t h e r words, it is assumed t h a t t h e s e r v e r s u p e r v i s o r ZZ
5 i s s u e s o n e l i c e n s e (one s e t o f a D D S u s e r IDanda DDSpassword)
t o t h e u s e r f o r one l i c e n s e (one set of an ERP u s e r I D and
an ERP password) given from t h e system s u p e r v i s o r YY.
[0164]
When a l o g i n r e q u e s t p r e s e n t i n g a DDS u s e r I D and a DDS
10 password is r e c e i v e d from t h e p o r t a b l e t e r m i n a l 31' (Step
S1021), t h e d a t a s y n c h r o n i z a t i o n s e r v e r 60, f i r s t , checks
whether o r not t h e u s e r is a r e g i s t e r e d u s e r r e g i s t e r e d by
t h e s e r v e r s u p e r v i s o r ZZ by using t h e DDS u s e r I D and t h e DDS
passwordpresented f r o m t h e p o r t a b l e t e r m i n a l 3 1 b y r e f e r r i n g
15 t o t h e u s e r information ( h e r e , information i n w h i c h a DDS u s e r
I D , a DDSpassword, andthelikeareassociatedwitheachother
f o r each u s e r ) s t o r e d i n t h e d a t a b a s e included t h e r e i n i n t h e
a u t h e n t i c a t i o n p r o c e s s ( S t e p S521).
[0165]
20 In a case where t h e u s e r is a r e g i s t e r e d u s e r , t h e d a t a
s y n c h r o n i z a t i o n s e r v e r 60 s p e c i f i e s t h e ERP u s e r I D and t h e
ERP password a s s o c i a t e d with t h e DDS u s e r I D p r e s e n t e d from
t h e p o r t a b l e t e r m i n a l 3 1 b y r e f e r r i n g t o t h e u s e r information
( s e e Fig. 23) s t o r e d i n t h e d a t a b a s e included t h e r e i n and
25 r e q u e s t s f o r t h e a u t h e n t i c a t i o n o f t h e u s e r X b y t r a n s m i t t i n g
a u t h e n t i c a t i o n r e q u e s t information i n c l u d i n g t h e ERP u s e r I D
and t h e ERP password, which have been s p e c i f i e d , t o t h e
integrated enterprise system 100 (Steps S522 and S1022).
[0166]
When the authentication request is received, the
integratedenterprise system100 performsthe authentication
5 process for determining whether or not the user is a
registered user using the ERP user ID and the ERP password
received fromthe data synchronization server 60 by referring
to the user information (here, information in which an ERP
user ID, an ERP password, and the like of each user are
10 associated with each other) stored in a database included
therein and notifies the data synchronization server 60 of
a result of the authentication process (Step S1023).
[0167]
When the notification of the result of the
15 authentication process is received (Step S523), the data
synchronization server 60 determines whether or not login is
permittedin accordance with the received notification (Step
S524) and permits login to the portable terminal managing
server 10 o f t h e p o r t a b l e t e r m i n a l 3 1 i n a casewhere the login
20 is determined to be permitted (Step S1024).
[0168]
After the login is permitted, the portable terminal
managing server 10 performs various processes in accordance
with a request (Step S1025) from the portable terminal 31.
25 In such various processes, in a case where a process (a search
process, an information providing process, an information
registration process, or the like) is requested to the
integrated enterprise system 100, the portable terminal
managing server10 specifiesanERPuser IDandanERPpassword
associated with the DDS user ID presented from the portable
terminal 31 by referring to the user information (see Fig.
5 23; the same as that maintained in the data synchronization
server 60) stored in the database included therein and
performs the process request by presenting the ERP user ID
and the ERP password that have been specified (Step S1026).
[0169]
10 Then, in a case where the user is determined to be a
registered user by using the ERP user ID and the ERP password
that have been presented, the integrated enterprise system
100 performs the requested process.
[0170]
15 As describedabove, since the configuration is employed
in which the data synchronization server 60 managed by the
server supervisor ZZ performs the authentication process
usingthe ERPuser IDandthe ERPpasswordissuedbythe system
supervisor YY of the backbone information management system
20 501 and the DDS user ID and the DDS password issued with being
uniquely associatedwiththe ERP user ID and the ERP password
by the server supervisor ZZ, in the backbone information
management system 501 providing information relating to a
form for the portable terminal 31, the security of the system
25 can be improved by preventing an illegal behavior based on
an illegal license, and the system supervisor YY and the user
X can be protected.
[0171]
Inaddition, althoughnotparticularlydescribedinthe
above-described embodiment, the portable terminal managing
server 10 performs the above-described processes (see Figs.
5 5, 8, 10, 13, 15, and16) inaccordancewiththeprocessprogram
(portable terminal managing program) stored in the storage
medium included therein.
Industrial Applicability
10 [0172]
The present invention is useful for preventing an
illegal behavior based on an illegal license in a business
system (particularly, the ERP system) providing information
relating to a form for the portable communication terminal
15 and for protecting the system supervisor and the users.
Reference Signs List
[0173]
10 portable terminal managing server
20 20 repeater
31 to 3N portable terminal
4 0 communication network
51, 52, 52 communication network
100, 200, 300 integrated enterprise system
25 110, 310 enterprise server
120, 220 DWH server
500 backbone information management system

WE CLAIM:
1. A p o r t a b l e t e r m i n a l managing s e r v e r t h a t is a s e r v e r
operated by ERP and provides v a r i o u s k i n d s o f d a t a through
5 a communication network i n accordance with a r e q u e s t from a
p o r t a b l e t e r m i n a l used by a u s e r , t h e p o r t a b l e t e r m i n a l
managing s e r v e r comprising:
a p r o c e s s flow d a t a s t o r i n g means t h a t s t o r e s p r o c e s s
flow d a t a i n c l u d i n g v a r i o u s k i n d s o f d a t a r e l a t i n g t o a
10 process flow i n c l u d i n g a p l u r a l i t y of b u s i n e s s p r o c e s s e s so
a s t o be i n q u i r a b l e f o r t h e p o r t a b l e t e r m i n a l ;
a logindeterminingmeansthatdetermineswhether l o g i n
is p e r m i t t e d t o t h e portableterminalbasedonpresenteduser
l i c e n s e information when t h e r e is a l o g i n r e q u e s t from t h e
15 p o r t a b l e t e r m i n a l p r e s e n t i n g t h e u s e r l i c e n s e i n f o r m a t i o n ,
which is l i c e n s e information i s s u e d t o t h e u s e r from a s e r v e r
s u p e r v i s o r of t h e p o r t a b l e t e r m i n a l managing s e r v e r ;
a l o g i n p r o c e s s i n g means t h a t performs a l o g i n p r o c e s s
i n a case where t h e l o g i n is determined t o be p e r m i t t e d by
20 t h e l o g i n determining means;
a p r o c e s s r e q u e s t r e c e p t i o n m e a n s t h a t a c c e p t s v a r i o u s
process r e q u e s t s fromtheportableterminalthat is i n a l o g i n
s t a t e f o r which t h e l o g i n p r o c e s s is performed by t h e l o g i n
p r o c e s s i n g means; and
25 a p r o c e s s performing means t h a t performs a
p r e d e t e r m i n e d p r o c e s s i n accordance with t h e p r o c e s s r e q u e s t
accepted by t h e p r o c e s s r e q u e s t r e c e p t i o n means,
theprocessperformingmeansmakingtheprocess request
by presenting server license information that is server
license information as license information issued to the
server supervisor and can uniquely specify the user license
information in a case where the process request is made for
an integrated enterprise system exhibiting a function by
communicating with the portable terminal managing server as
a predetermined process.
10 2. The portable terminal managing server according to
claim 1,
wherein the server license information is used as the
user license information, and
the login determining unit determines whether login is
15 permitted to the portable terminal by determining whether or
not the user is a registered user based on the server license
information presented as the user license information.
3. The portable terminal managing server according to
20 claim 1,
wherein one piece of the user license information is
issuable for one piece of the server license information and
islicenseinformationassociatedwithonepieceofthe server
license information,
25 the login determining means determines whether login
is permitted to the portable terminal by determining whether
or not the user is a registered user based on the presented
t h e p r o c e s s performing means makes t h e p r o c e s s r e q u e s t
fortheintegratedenterprise s y s t e m b y p r e s e n t i n g t h e s e r v e r
l i c e n s e information a s s o c i a t e d with t h e u s e r l i c e n s e
5 information used by t h e l o g i n determining means with
one-to-one correspondence.
4 . The p o r t a b l e t e r m i n a l managing s e r v e r according t o any
one of claims 1 t o 3, wherein a u s e r I D and a password a r e
10 used a s t h e l i c e n s e i n f o r m a t i o n .
5. A p o r t a b l e t e r m i n a l managing program t h a t causes a
p o r t a b l e t e r m i n a l managing s e r v e r t o perform a process of
providing v a r i o u s k i n d s o f d a t a t h r o u g h a communication
15 network i n accordance with a r e q u e s t f r o m a p o r t a b l e t e r m i n a l
used by a u s e r by o p e r a t i n g ERP, t h e p o r t a b l e t e r m i n a l
managing program causing t h e p o r t a b l e t e r m i n a l managing
s e r v e r i n c l u d i n g a p r o c e s s f l o w d a t a s t o r i n g m e a n s t h a t s t o r e s
process flow d a t a i n c l u d i n g v a r i o u s k i n d s o f d a t a r e l a t i n g
20 t o a p r o c e s s flowincludingapluralityofbusiness processes
so a s t o be i n q u i r a b l e f o r t h e p o r t a b l e t e r m i n a l t o perform:
determining whether l o g i n is p e r m i t t e d t o t h e p o r t a b l e
t e r m i n a l based on p r e s e n t e d u s e r l i c e n s e information when
thereisaloginrequestfromtheportableterminalpresenting
25 t h e u s e r l i c e n s e i n f o r m a t i o n , which is l i c e n s e information
i s s u e d t o t h e u s e r from a s e r v e r s u p e r v i s o r of t h e p o r t a b l e
t e r m i n a l managing s e r v e r ;
li I .
v.n*i.%- #'~-i-*
performing a login process in a
is determined to be permitted in the determining of whether
login is permitted;
accepting various process requests from the portable
5 terminal that is in a login state for which the login process
is performed in the performing of a login process; and
performing a predetermined process in accordance with
the process request accepted in the accepting of various
process requests,
10 in the performing of a predetermined process, the
process request being made by presenting server license
information that is server license information as license
information issued to the server supervisor and can uniquely
specify the user license information in a case where the
15 process request is made for an integrated enterprise system
exhibiting a function by communicating with the portable
terminal managing server as a predetermined process.