Pp-Pi-Pcs Interface - Linking of Process Control Systems
Pp-Pi-Pcs Interface - Linking of Process Control Systems
RI3URFHVV&RQWURO6\VWHPV
6
&
3
,
3
3
3
3
/
(
+
5HOHDVH%
®
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&RS\ULJKW
© Copyright 1998 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
SAP AG further does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within these materials. SAP AG shall not be liable for any special,
indirect, incidental, or consequential damages, including without limitation, lost revenues or lost
profits, which may result from the use of these materials. The information in this documentation is
subject to change without notice and does not represent a commitment on the part of SAP AG for
the future.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL® and SQL-Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
OSF/Motif® is a registered trademark of Open Software Foundation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated.
UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.
ADABAS® is a registered trademark of Software AG.
SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAP ArchiveLink®, SAPaccess®, SAPmail®,
SAPoffice®, SAP-EDI®, R/3 Retail®, SAP EarlyWatch®, SAP Business Workflow®, ALE/WEB,
Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAP
AG.
,FRQV
,FRQ 0HDQLQJ
Caution
Example
Note
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&RQWHQWV
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
3URFHVV0HVVDJHVDQG3URFHVV0HVVDJH&DWHJRULHV
3UHGHILQHG3URFHVV0HVVDJH&DWHJRULHV
Characteristics of the Message Category PI_CRST .................................................................. 9
Characteristics of the Message Category PI_OPST ................................................................ 10
Characteristics of the Message Category PI_PHST ................................................................ 11
Characteristics of the Message Category PI_PHACT.............................................................. 12
Characteristics of the Message Category PI_SRST ................................................................ 13
Characteristics of the Message Category PI_SRACT.............................................................. 14
Characteristics of the Message Category PI_OPUST ............................................................. 15
Characteristics of the Message Category PI_PHUST.............................................................. 16
Characteristics of the Message Category PI_CONS ............................................................... 17
Characteristics of the Message Category PI_PROD ............................................................... 18
Characteristics of the Message Category PI_QMSMR ............................................................ 19
([SODQDWLRQRIWKH3URFHVV0HVVDJH&KDUDFWHULVWLFV
&RQWURO5HFLSHV
3URFHVV,QVWUXFWLRQVDQG3URFHVV,QVWUXFWLRQ&DWHJRULHV
&RPPXQLFDWLRQYLD5)&
7UDQVIHURI&RQWURO5HFLSHVIURP5333,WR&RQWURO6\VWHP
'RZQORDGRIDOO&RQWURO5HFLSHV,QLWLDWHGE\5333,
'RZQORDGRIDOO&RQWURO5HFLSHV,QLWLDWHGE\WKH&RQWURO6\VWHP
'RZQORDGRID6SHFLILF&RQWURO5HFLSH
$XWKRUL]DWLRQ&KHFN'XULQJ'RZQORDG
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7UDQVIHURI*HQHUDO&KDUDFWHULVWLF'DWD
'RZQORDGRI'HWDLO'DWDRQ&KDUDFWHULVWLFV
Explanation of the Interface Parameters .................................................................................. 38
'RZQORDGRI$OORZHG9DOXHVIRU&KDUDFWHULVWLFV
Explanation of the Interface Parameters .................................................................................. 41
$XWKRUL]DWLRQ&KHFN'XULQJ'DWD7UDQVIHU
7UDQVIHURI3URFHVV0HVVDJHVIURPWKH&RQWURO6\VWHPWR5333,
,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
$XWKRUL]DWLRQ&KHFN'XULQJ3URFHVV0HVVDJH8SORDG
(UURU+DQGOLQJ
7UDQVIHURI3URFHVV0HVVDJHVIURP5333,WRWKH&RQWURO6\VWHP
,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
$SSHQGL[3,3&66DPSOH5HFLSH
1RWHVRQWKH6DPSOH5HFLSH
3URFHVV,QVWUXFWLRQV*HQHUDO3DUW
3URFHVV,QVWUXFWLRQV3KDVHV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
APHASE_1 ............................................................................................................................... 60
APHAR_1 ................................................................................................................................. 61
AREAD1 ................................................................................................................................... 62
,QWHUIDFH7DEOHVRIWKH&RQWURO5HFLSHIRUWKH6DPSOH2UGHU
Table CRHE: Control Recipe Header....................................................................................... 64
Table CRFT: Process Instructions ........................................................................................... 65
Table CRFV: Process Instruction Characteristics .................................................................... 67
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO
6\VWHPV
Many different types of control system are used in the process industry. While some production
lines are controlled by fully-automated, sophisticated process control systems, others are still
mainly manually-operated with a low level of automation.
SAP has designed the PI-PCS interface to link PP-PI with manually-operated, partially-
automated, and fully-automated lines. In SAP Customizing, you can adapt this interface to meet
individual requirements by:
• Defining information for control (control recipes)
• Defining information from control (process messages)
The interface thus enables flexible linking of systems. It meets the degree of automation of the
line by offering the possibilities of:
• Complete process link
• External entry of control recipe data.
The PI-PCS interface described here is used to transfer all the information relevant to production.
If the SAP Quality Management component is to be installed, you can use the QM-IDI interface.
Confirmation of order-related data via the PI-PCS interface replaces order-related confirmations
via PP-PDC.
The PI-PCS interface enables the download of control recipes to the lower-level control system
and the upload of process-related data in the form of process messages. In addition, it can be
used to download general data on characteristics that make up control recipes and process
messages.
&RQWUROUHFLSHV are used for transferring the following data:
• Process and control parameters
• Texts with instructions for the line operator in the case of lines that are manually
operated (either fully or partially)
• Information on process messages that are to be returned
3URFHVVPHVVDJHV supply information on:
• Status of process orders
• Consumption and production of materials
• Status of resources
• Selected process events
They are used for creating electronic batch and production records, and for updating the process
order and material stocks.
You can transfer the following JHQHUDOFKDUDFWHULVWLFGDWD to an external system:
• Technical data such as the format and characteristic group
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
3URFHVV0HVVDJHVDQG3URFHVV0HVVDJH&DWHJRULHV
3URFHVV0HVVDJHVDQG3URFHVV0HVVDJH&DWHJRULHV
3URFHVVPHVVDJHV supply information on:
• Status of process orders
• Consumption and production of materials
• Status of resources
• Selected process events
The information contained in a process message is specified via the process message
characteristics assigned to the message and their values.
Each process message refers to a SURFHVVPHVVDJHFDWHJRU\ defined in SAP Customizing. A
process message category describes:
• Information contained in a process message by assigning process message
characteristics
• Subsequent processing of the message by assigning destinations
There are two different kinds of process message category:
• Predefined by SAP
• Defined by the users according to their specific information requirements, when the
SAP System is set up
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
3UHGHILQHG3URFHVV0HVVDJH&DWHJRULHV
3UHGHILQHG3URFHVV0HVVDJH&DWHJRULHV
The message categories predefined by SAP are used for the integration of process data into the
R/3 logistics components:
• Production Planning
• Materials Management (Inventory Management)
• Quality Management
The table below lists message categories that are predefined by SAP together with the business
transactions they trigger in the above-mentioned components.
Process messages consist of process message characteristics. For information on the
characteristics of predefined message categories, choose the relevant message category. The
process message characteristics marked as 5HT (required) describe the minimum scope of the
respective message.
For more information on the exact structure of the messages in different business scenarios as
well as the processing logic for the different messages, see the R/3 Library 333URFHVV
0DQDJHPHQW
3URFHVVPHVVDJHFDWHJRULHVSUHGHILQHGE\6$3
0HVVDJH %XVLQHVVWUDQVDFWLRQ
FDWHJRU\
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B&567
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B&567
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B2367
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B2367
Message category PI-OPST is used for documentation only. Time events are confirmed at phase
level. The operation status is updated in accordance with the status of the subordinate phases.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B3+67
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B3+67
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B3+$&7
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B3+$&7
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B6567
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B6567
&KDUDFWHULVWLF 0HDQLQJ 5
H
T
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B65$&7
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B65$&7
&KDUDFWHULVWLF 0HDQLQJ 5
H
T
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B23867
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B23867
&KDUDFWHULVWLF 0HDQLQJ 5H
T
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B3+867
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B3+867
&KDUDFWHULVWLF 0HDQLQJ 5
H
T
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B&216
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B&216
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B352'
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B352'
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B40605
&KDUDFWHULVWLFVRIWKH0HVVDJH&DWHJRU\3,B40605
The message category PI_QMSMR is used to report summarized measured inspection results.
The inspection results are displayed as default values in the QM inspection results record.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH3URFHVV0HVVDJH&KDUDFWHULVWLFV
([SODQDWLRQRIWKH3URFHVV0HVVDJH&KDUDFWHULVWLFV
)RUPDWVRIWKHSURFHVVPHVVDJHFKDUDFWHULVWLFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
([SODQDWLRQRIWKH3URFHVV0HVVDJH&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH3URFHVV0HVVDJH&KDUDFWHULVWLFV
For more information on characteristic formats, see Transfer of Process Messages from the
Control System to R/3 PP-PI [Page 45].
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&RQWURO5HFLSHV
&RQWURO5HFLSHV
In the control recipe, the information required to execute a process order is transferred to the
executing control system.
The following data is defined in a control recipe:
• Required control and process parameters
• Texts with instructions for the line operator in the case of partially or completely
manually operated lines,
• Process messages to be returned to PP-PI
A control recipe is assigned exactly one destination at process control level. If several process
control systems are involved in the execution of a process order, separate control recipes can be
created and sent to the respective control system. More than one control recipe can be
transferred per process order to the same control address.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
3URFHVV,QVWUXFWLRQVDQG3URFHVV,QVWUXFWLRQ&DWHJRULHV
3URFHVV,QVWUXFWLRQVDQG3URFHVV,QVWUXFWLRQ
&DWHJRULHV
Control recipes consist of process instructions.
Every process instruction used in a control recipe refers to a SURFHVVLQVWUXFWLRQFDWHJRU\
defined in SAP Customizing. Process instruction categories are defined when the System is set
ue.They are adjusted to the degree of automation of the line. Process instruction categories
specify:
• The information contained in a process instruction via the assignment of process
instruction characteristics
• The process instruction type
The following types of process instruction are relevant to external control systems:
• Process parameter
• Process data request
• Process message subscription
• Process data calculation formula
For examples of the different types of process instruction, see the R/3 Library333URFHVV
0DQDJHPHQW
3URFHVV3DUDPHWHU
In control recipes for automated control systems, process instructions of this type are used to
transfer control and process parameters to the control system.
With production lines that are manually operated (either fully or partially), process parameters
contain instructions for the line operator.
3URFHVV'DWD5HTXHVW
Process data requests refer to planned events. They define which messages with up-to-date
process data are to be transferred from the control system to R/3 PP-PI. They specify:
• Categories of the process messages that must be created
• Process message characteristics that must be contained in the messages
• Information that the control system must provide in the messages as characteristic
values
• Additional data (characteristic values) that is not known to the control system and has
to be included in the messages when they are created
3URFHVV0HVVDJH6XEVFULSWLRQ
Process message subscriptions specify that process control is to send a message every time a
specific event occurs, for example, a goods receipt.
Process message subscriptions contain information on:
• The message category to be used
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
3URFHVV,QVWUXFWLRQVDQG3URFHVV,QVWUXFWLRQ&DWHJRULHV
3URFHVV'DWD&DOFXODWLRQIRUPXOD
Process instructions of this type define that a value is to be calculated and reported when a
control recipe is processed. They are used in control recipes that are to be processed by the line
operator in a manually operated line.
The process data calculation formula specifies:
• The value to be calculated
• The formula to be used for the calculation
• The process message to be used to report the calculated value
For examples on how to use process instruction categories for the R/3 PI sheet, see the R/3
Library 333URFHVV0DQDJHPHQW.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
&RPPXQLFDWLRQYLD5)&
&RPPXQLFDWLRQYLD5)&
PP-PI and the control system communicate with each other via Remote Function Call (RFC).
RFC is a method of communication developed by SAP which provides convenient data transfer
between different systems. The communication partners swap data using Common Program
Interface Communication (CPI-C). Due to the RFC technology on the R/3 level, the application
does not require communication handling. On the control computer level, SAP supports the
automatic generation of an RFC example program with a code generator. The function module in
SAP R/3 with which data is to be exchanged is used as the basis for the generation of the
example program. The generated programs support synchronous RFCs but do not support
transactioncal RFCs. Where the transactional RFC is neede (see below), the program must be
adjusted accordingly. Afterwards, they must be compiled and linked in the control computer and
can then be used for the actual application as an Application Program Interface (API).
5)&IXQFWLRQPRGXOHVRIWKH3,3&6LQWHUIDFH
&DOO
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
&RPPXQLFDWLRQYLD5)&
Characteristic data and values are downloaded as synchronous RFCs. All other calls from PP-PI
to the control system and from the control system to PP-PI are carried out as transactional RFCs
(tRFC). The tRFC ensures that each call is carried out once only. The sequence of the calls is
not changed. If the target system is not active when the call takes place, the RFC is repeated
according to a repetition rate or duration that can be set by the user. The current status of a tRFC
can be checked any time via the log file.
5)&PRGHRIWKHIXQFWLRQPRGXOHV
)XQFWLRQQDPH 5)&SURJUDPRQFRQWUROOHYHO
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7UDQVIHURI&RQWURO5HFLSHVIURP5333,WR&RQWURO6\VWHP
7UDQVIHURI&RQWURO5HFLSHVIURP5333,WR&RQWURO
6\VWHP
There are three different ways of transferring control recipes from R/3 PP-PI to the control
system:
• Download of all control recipes for a specific control system, initiated by R/3 PP-PI
• Download of all available control recipes, initiated by the control system
• Download of a specific control recipe, initiated by the control system
6HHDOVR
Authorization Check During Download [Page 33]
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
'RZQORDGRIDOO&RQWURO5HFLSHV,QLWLDWHGE\5333,
'RZQORDGRIDOO&RQWURO5HFLSHV,QLWLDWHGE\5333,
Here, PP-PI calls the corresponding API of a control system as soon as one control recipe has
been created for the control system. This way, any number of control recipes can be transferred
in one function call. The function module used to carry out the tRFC is
CONTROL_RECIPE_DOWNLOAD.
The table below lists the data exchanged via the interface of the function module from the point
of view of PP-PI. For more detailed information on the interface parameters, see Explanation of
the Interface Parameters [Page 34]
([SRUW3DUDPHWHUV
7DEOHV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
'RZQORDGRIDOO&RQWURO5HFLSHV,QLWLDWHGE\WKH&RQWURO6\VWHP
'RZQORDGRIDOO&RQWURO5HFLSHV,QLWLDWHGE\WKH&RQWURO
6\VWHP
Here, the download is initiated by the control system. The control system calls the function
module CONTROL_RECIPE_PULL in R/3 PP-PI which in turn starts the download of all available
control recipes for the control system. The download is carried out via a tRFC using the function
CONTROL_RECIPE_DOWNLOAD.
The interface of CONTROL_RECIPE_DOWNLOAD is described in Download of all Control
Recipes Initiated by R/3 PP-PI [Page 29]
The following table lists the data exchanged via the function module CONTROL_RECIPE_PULL
from the point of view of PP-PI:
,PSRUW3DUDPHWHUV
([FHSWLRQ
1DPH 'HVFULSWLRQ
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
'RZQORDGRID6SHFLILF&RQWURO5HFLSH
'RZQORDGRID6SHFLILF&RQWURO5HFLSH
In this case, the function CONTROL_RECIPE_AVAILABLE informs the control system that a new
control recipe has been created. From the point of view of PP-PI, the following data is
transferred:
([SRUW3DUDPHWHUV
7DEOHV
1DPH 'HVFULSWLRQ
CRHE Control recipe header
The following table lists the data exchanged via the function module
CONTROL_RECIPE_PULL_SINGLE from the point of view of PP-PI:
,PSRUW3DUDPHWHUV
For more detailed information on the interface parameters, see Explanation of the Interface
Parameters [Page 34].
The following exceptions can be triggered:
([FHSWLRQ
1DPH 'HVFULSWLRQ
CONTROL_RECIPE_NOT_FOUND Control recipe does not exist
CONTROL_RECIPE_STATE_NOT_VALID Control recipe status does not permit
download
DESTINATION_NOT_VALID Invalid address for this type of communication
DESTINATION_UNKNOWN Address not known
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
'RZQORDGRID6SHFLILF&RQWURO5HFLSH
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
$XWKRUL]DWLRQ&KHFN'XULQJ'RZQORDG
$XWKRUL]DWLRQ&KHFN'XULQJ'RZQORDG
Depending on the download procedure you use, the R/3 System carries out an authorization
check before transferring control recipes to a control system. The authorization check has been
implemented as follows:
• Download of all control recipes initiated by the R/3 System
No authorization check is carried out.
• Download of all or specific control recipes initiated by the control system
The R/3 System checks the authorization of the R/3 user with which the control
system requests control recipes. The system only transfers control recipes if the user
has the corresponding authorization for authorization object. C_CREX_WRK.
For more information on authorizations, see the Implementation Guide (IMG) for 3URFHVV
0DQDJHPHQW.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7DEOH6WUXFWXUHV
7DEOH&5+(
7DEOH&5)7
7DEOH&5)9
Table CRFV contains the process instruction characteristics and their values. The characteristic
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
value is always transferred as left-justified in the 30-CHAR field ATWRT. With characteristic
format NUM, ATWRT contains the characteristic value in floating-point format.
7DEOH7/,1(6
Table TLINES is used to transfer texts for the line operator in partially or fully manually operated
lines. You can define any number of text lines for a process instruction characteristic.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7UDQVIHURI*HQHUDO&KDUDFWHULVWLF'DWD
7UDQVIHURI*HQHUDO&KDUDFWHULVWLF'DWD
Characteristics and their values are transferred in the control recipe as described above.
Additional information on the characteristics, such as input template and format, are not
transferred in the control recipe.
If, for example, the control system is to display characteristic values or proposes them for input,
the control system requires this additional information to process the characteristics correctly.
For this reason, you can use the PI-PCS interface to transfer the following general characteristic
data to the control system alongside the control recipe:
• Detail data on process message or process instruction characteristics, such as format
and characteristic group
• Allowed input values of process instruction or process message characteristics
(similar to the possible entries function in the R/3 System)
This data is stored in the characteristic definition in Customizing for 3URFHVV0DQDJHPHQW.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
'RZQORDGRI'HWDLO'DWDRQ&KDUDFWHULVWLFV
'RZQORDGRI'HWDLO'DWDRQ&KDUDFWHULVWLFV
You can use function module PROC_CHAR_GET_LIST_WITH_DETAIL to transfer detail data on
process instruction and process message characteristics to a control system. Here, the download
is initiated by the control system. The data is downloaded as a synchronous RFC.
The following data is transferred at the interface (from the function module’s point of view):
,PSRUW3DUDPHWHUV
7DEOHV
1DPH 'HVFULSWLRQ
([FHSWLRQV
1DPH 'HVFULSWLRQ
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7DEOH6WUXFWXUHV
&+$5$&7(5,67,&B/,67
&+$5$&7(5,67,&B7(;76
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
'RZQORDGRI$OORZHG9DOXHVIRU&KDUDFWHULVWLFV
'RZQORDGRI$OORZHG9DOXHVIRU&KDUDFWHULVWLFV
You can use function module PROC_CHAR_HELPVALUES_GET to transfer allowed values for
a characteristic to a control system. Characteristic value download is initiated by the control
system. The data is downloaded as a synchronous RFC.
The characteristic values are determined based on the following settings made for the
characteristic:
• Allowed individual values and value ranges
• The check table or function allocated to it
• The foreign key dependency allocated to it
Matchcodes assigned to a characteristic are not taken into account.
In addition, you can use this function module to check the validity of a single characteristic value.
In this case, the control system transfers the value to be checked as a selection criterion. The
value is valid if the function module returns the same value in the results table.
The following data is transferred at the interface (from the function module’s point of view):
,PSRUW3DUDPHWHUV
7DEOHV
1DPH 'HVFULSWLRQ
SELECTION_FOR_HELPVALUES Selection criteria restricting the search range
They are not taken into account if individual
values or value ranges have been defined in the
characteristic itself.
HELPVALUES Allowed values found, text included
VALUES_FOR_FIELD Allowed values found, text not included
DESCRIPTION_FOR_HELPVALUES Structure description of table HELPVALUES
DETAILED_VALUE_INFORMATION Detail information on allowed values defined as
individual values or value ranges in the
characteristic itself.
([FHSWLRQ
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
'RZQORDGRI$OORZHG9DOXHVIRU&KDUDFWHULVWLFV
1DPH 'HVFULSWLRQ
CHARACTERISTIC_NOT_VALID Characteristic not valid
VALUES_CAN_NOT_BE_ Unable to determine allowed values
DETERMINED
NO_AUTHORITY No authorization to display characteristic data
CONTROL_RECIPE_NOT_VALID Control recipe not valid
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7DEOH6(/(&7,21B)25B+(/39$/8(6
The control system fills this table if you want to restrict the value range that is used to select
allowed values. The table is structured as follows:
7DEOH+(/39$/8(6
PP-PI uses this table to transfer characteristic values that are QRW defined as individual values or
value ranges in the characteristic itself but have been determined using the check table or
function, or the foreign key dependency allocated there. It also transfers additional information on
the values, such as language-dependent short text.
If a matchcode has been assigned to the characteristic, this is not taken into
account when determining allowed values.
Table HELPVALUES has no fixed structure as the information transferred may vary from
characteristic to characteristic and search help to search help. For this reason, the table structure
is transferred dynamically in table DESCRIPTION_FOR_HELPVALUES.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7DEOH9$/8(6B)25B),(/'
This table contains the same characteristic values as table HELPVALUES without the additional
information. Therefore, the table structure only consists of the field for the characteristic value.
For performance reasons, this table should be used since characteristic values are accessed
without defining the structure.
7DEOH'(6&5,37,21B)25B+(/39$/8(6
This table describes the structure of entries in table HELPVALUES. The structure of table
HELPVALUES is transferred dynamically as the information transferred varies from characteristic
to characteristic and search help to search help.
Table DESCRIPTION_FOR_HELPVALUES comprises the following fields:
7DEOH'(7$,/('B9$/8(B,1)250$7,21
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
PP-PI uses this table to transfer allowed values that have been defined in the characteristic itself
(as individual values or value ranges). The table is structured as follows:
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
$XWKRUL]DWLRQ&KHFN'XULQJ'DWD7UDQVIHU
$XWKRUL]DWLRQ&KHFN'XULQJ'DWD7UDQVIHU
Before transferring characteristic data to a control system, the R/3 System checks the
authorizations of the R/3 user with which the control system requests data. The following
authorizations must have been assigned to the user:
• To transfer detail data on characteristics
Display authorization for object C_CABN
• To transfer allowed characteristic values and validate characteristic values
Authorization for authorization object C_PROCCHAR as well as the relevant
authorization for authorization object C_CREX_WRK
For more information on authorizations, see the Implementation Guide (IMG) for 3URFHVV
0DQDJHPHQW.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7UDQVIHURI3URFHVV0HVVDJHVIURPWKH&RQWURO6\VWHPWR5333,
7UDQVIHURI3URFHVV0HVVDJHVIURPWKH&RQWURO6\VWHP
WR5333,
Using an RFC, any number of process messages can be transferred from the control system to
PP-PI. To transfer messages, call the PP-PI function module PROCESS_MESS_UPLOAD.
Transfer is always initiated by the control system.
Several messages can be transferred simultaneously via the interface. In order to reduce the
system load, a control system should be capable of collecting process messages and transferring
them in groups at reasonable time intervals.
As of Release 4.0A, the process messages can be uploaded using a transactional RFC (tRFC).
This type of message upload also is the prerequisite for certification as of Release 4.0A.
However, message upload using a synchronous RFC (sRFC) is still supported for existing links
to control systems.
For this reason, the message transfer process varies as follows:
• In an sRFC, the results of message processing are returned to the control system in
the same function call. To do so, the RCODE field of interface tables MSHID and
MSEL is used.
• In a tRFC, the control system must also transfer the RFC destination of the RFC
partner program as an additional parameter to PP-PI. Function module
PROCESS_MESS_UPLOAD runs asynchronously to the call.
PP-PI then initiates a tRFC to the RFC destination of the RFC partner program to
transfer the processing results. To do so, it calls function module
PROCESS_MESS_GET_RETURN_CODE and transfers interface tables MSHD and
MSEL to the control system.
6HHDOVR
Error Handling [Page 50]
Authorization Check During Process Message Upload [Page 49]
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
,QWHUIDFH3DUDPHWHUV
,QWHUIDFH3DUDPHWHUV
The table shows the data that is exchanged via the RFC interface from the point of view of PP-PI:
For more detailed information on the interface parameters, see Explanation of the Interface
Parameters [Page 54]
,QWHUIDFH3DUDPHWHUVRI352&(66B0(66$*(B83/2$'
,PSRUW3DUDPHWHUV
7DEOHV
([FHSWLRQ
1DPH 'HVFULSWLRQ
INTERNAL_ERROR Internal error
NO_RFC_DESTINATION Parameter RFC_DESTINATION_
FOR_TRFC contains no value although the
function call was carried out using tRFC
,QWHUIDFH3DUDPHWHUVRI352&(66B0(66B*(7B5(7851B&2'(
With the following exceptions, the interface of function module
PROCESS_MESS_GET_RETURN_CODE is identical to that of PROCESS_MESS_UPLOAD:
• It does QRW contain import parameter RFC_DESTINATION_FOR_TRFC.
• It does QRW contain exception NO_RFC_DESTINATION.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7DEOH6WUXFWXUHV
7DEOH06+'
7DEOH06(/
Table MSEL contains the process message characteristics and their values. The characteristic
value is always transferred as left-justified in the 30-CHAR field ATWRT. With characteristic
format NUM, ATWRT contains the characteristic value in floating-point format.
7DEOH7/,1(6
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
PDW K
Transferring a text for a characteristic is useful only if the characteristic has been defined in PP-
PI as a characteristic with a long text.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
$XWKRUL]DWLRQ&KHFN'XULQJ3URFHVV0HVVDJH8SORDG
$XWKRUL]DWLRQ&KHFN'XULQJ3URFHVV0HVVDJH8SORDG
Before transferring process messages from a control system, the R/3 System checks the
authorizations of the R/3 user with which the control system transfers messages. The user
requires the authorization for process message creation in authorization object C_MESS_WRK.
Otherwise, the process messages are rejected.
For more information on authorizations, see the Implementation Guide (IMG) for 3URFHVV
0DQDJHPHQW.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
(UURU+DQGOLQJ
(UURU+DQGOLQJ
0HVVDJH+HDGHU
If a process message cannot be processed correctly by PROCESS_MESS_UPLOAD, the return
code for this message is set to a value not equal to 0 (field RCODE in table MSHD).
5HWXUQFRGHVRQPHVVDJHKHDGHUOHYHO
5HWXUQ 0HDQLQJ
FRGH
0HVVDJH&KDUDFWHULVWLFV
If inconsistencies or errors are discovered when the message characteristics are checked, the
return code of the corresponding characteristic is set to a value not equal to 0 (field RCODE in
table MSEL).
5HWXUQFRGHVDWPHVVDJHFKDUDFWHULVWLFOHYHO
5HWXUQ 0HDQLQJ
FRGH
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
(UURU+DQGOLQJ
If one of the errors listed above occurs, the corresponding process message cannot be
processed. The return code at message header level is set to 99.
,QWHUQDO(UURUV
If errors occur during message processing that are not due to faulty or inconsistent interface
data, the exception INTERNAL_ERROR is triggered. In this case, none of the process messages
transferred are processed.
3URFHVVLQJRI7UDQVDFWLRQDO5)&
f the control system does not transfer an RFC destination to PP-PI in a transactional message
upload (parameter RFC_DESTINATION_FOR_TRFC), the results of message processing cannot
be transferred to the control system. In this case, PP-PI raises exception
NO_RFC_DESTINATION. The system does not process the process messages transferred.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7UDQVIHURI3URFHVV0HVVDJHVIURP5333,WRWKH&RQWURO6\VWHP
7UDQVIHURI3URFHVV0HVVDJHVIURP5333,WRWKH
&RQWURO6\VWHP
Using the function PROCESS_MESS_DOWNLOAD, any number of process messages can be
transferred from PP-PI to the control system. The transfer is always initiated by PP-PI.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
,QWHUIDFH3DUDPHWHUV
,QWHUIDFH3DUDPHWHUV
The following data is exchanged via the RFC interface (from the point of view of PP-PI):
([SRUW3DUDPHWHUV
Table Parameters:
1DPH 'HVFULSWLRQ (QWULHV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
7DEOH6WUXFWXUHV
7DEOH06+'
7DEOH06(/
Table MSEL contains the process message characteristics and their values. The characteristic
value is always transferred as left-justified in the 30-CHAR field ATWRT. With characteristic
format NUM, ATWRT contains the characteristic value in floating-point format.
7DEOH7/,1(6
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
([SODQDWLRQRIWKH,QWHUIDFH3DUDPHWHUV
PDW K
Transferring a text for a characteristic is useful only if the characteristic has been defined in PP-
PI as a characteristic with a long text.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
$SSHQGL[3,3&66DPSOH5HFLSH
$SSHQGL[3,3&66DPSOH5HFLSH
To give you an idea of how the interface can be designed, SAP has created a sample recipe for
you. The sample recipe only uses process instructions and characteristics that are defined in the
SAP reference client and are therefore available in each customer system. You will find the sample
recipe as recipe 5 of recipe group COLORS both in the certification system and the IDES system.
The message categories and process instruction categories as well as their characteristics used in
the sample recipe correspond to those in the Customizing documentation. So do the message and
process instruction characteristics defined by SAP.
In the following you will find:
• Notes on the process instructions used in the sample recipe
• The control recipe in the form of interface tables CRHE, CRFT, and CRFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
1RWHVRQWKH6DPSOH5HFLSH
1RWHVRQWKH6DPSOH5HFLSH
Recipe 5 in recipe group COLORS describes the process required to produce paint Y-300. A total
of 13 ingredients are used during various process phases to produce:
• Y-300: yellow paint in cans and
• P-300: paste.
Some of these ingredients serve as catalysts. During later processing steps, they are recorded as
output materials with negative quantities (see 300-160 catalyst 01).
The production process itself consists of 4 operations each comprising several phases. The
process is controlled by a single control system (control recipe destination 02). This means that
only one control recipe has to be created.
The process instructions are arranged in such a way that the control recipe consists of a first
general part that applies to the whole process. This general part contains information such as:
• General order data
• A list of all materials
• Process message subscriptions for process messages that are to be transferred to
PP-PI during the production process
The general part is followed by a part that contains process instructions specific to phases such as:
• Parameters for individual phases
• Requirements for specific measurement readings.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
3URFHVV,QVWUXFWLRQV*HQHUDO3DUW
3URFHVV,QVWUXFWLRQV*HQHUDO3DUW
Control recipe destination 02 is configured in such a way that the process instructions contained in
the general part are automatically generated under process instruction number 0000 in the first
phase (1010) when you create the control recipe.
The general part contains process instructions of the following categories:
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
3URFHVV,QVWUXFWLRQV3KDVHV
3URFHVV,QVWUXFWLRQV3KDVHV
Control recipe destination 02 has been configured in such a way that a process instruction of
category APHASE_1 (type 1 - process parameter) with number 0000 is generated for each phase
when you create a control recipe.
Apart from process parameter APHASE_1 created for each phase, the following additional process
instructions are allocated to some phases contained in the sample recipe:
• APHAR_1
• AREAD1
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
$3+$6(B
$3+$6(B
7\SH3URFHVV3DUDPHWHU
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
$3+$5B
$3+$5B
7\SH3URFHVV3DUDPHWHU
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
$5($'
$5($'
7\SH3URFHVV'DWD5HTXHVW
Process instruction AREAD1 is used to request a measurement reading or the value of a data
point defined in the control system. The value is to be transferred as process message DPREAD
to PP-PI. The process instruction contains definitions of those characteristics the message is to
comprise. The values of the following message characteristics are already defined in the process
instruction and can therefore be transferred directly to the process message:
• PPPI_PROCESS_ORDER
• PPPI_DATA_POINT_NAME
• PPPI_UNIT_OF_MEASURE
• PPPI_OPERATION
• PPPI_PHASE
All other characteristics of the process message to be created are assigned as values to the
process instruction characteristic PPPI_REQUESTED_VALUE. Their values have to be assigned
by the control system and must also be included in the message.
A process instruction of category AREAD1 that requests the result of a density measurement is
contained in phase 1030 (Transfer to reactor unit). In phases 2010 (prepare reaction basic
substances) and 2030 (reaction), the pH values at the end of these phases are requested.
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
,QWHUIDFH7DEOHVRIWKH&RQWURO5HFLSHIRUWKH6DPSOH2UGHU
,QWHUIDFH7DEOHVRIWKH&RQWURO5HFLSHIRUWKH6DPSOH
2UGHU
The same control recipe destination has been allocated to all phases of the sample recipe. For
this reason, you can create exactly one control recipe after you have released the corresponding
order. The following tables are transferred to the control system:
• Table CRHE, control recipe header
• Table CRFT, process instruction
• Table CRFV, process instruction characteristics
Table TLINES is not transferred to the control system as the control recipe contains no long
texts.
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5+(&RQWURO5HFLSH+HDGHU
7DEOH&5+(&RQWURO5HFLSH+HDGHU
3DUW
3DUW
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)73URFHVV,QVWUXFWLRQV
7DEOH&5)73URFHVV,QVWUXFWLRQV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)73URFHVV,QVWUXFWLRQV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
000000616 F_MEASURE
100000000 00000040 0001 PPPI_MATERI 300-130 CHAR
000000616 AL
100000000 00000040 0002 PPPI_MATERI 0050 CHAR
000000616 AL_ITEM
100000000 00000040 0003 PPPI_MATERI Pyridin CDE CHAR
000000616 AL_SHORT_T
EXT
100000000 00000040 0004 PPPI_OPERA 1000 CHAR
000000616 TION
100000000 00000040 0005 PPPI_PHASE 1010 CHAR
000000616
100000000 00000040 0006 PPPI_MATERI 1.5300000000 NUM
000000616 AL_QUANTITY 000000E+03
100000000 00000040 0007 PPPI_UNIT_ KG CHAR
000000616 OF_MEASU
RE
100000000 00000050 0001 PPPI_MATERI 300-140 CHAR
000000616 AL
100000000 00000050 0002 PPPI_MATERI 0060 CHAR
000000616 AL_ITEM
100000000 00000050 0003 PPPI_MATERI Hydrochloric CHAR
000000616 AL_SHORT_T Acid
EXT
100000000 00000050 0004 PPPI_OPERA 1000 CHAR
000000616 TION
100000000 00000050 0005 PPPI_PHASE 1010 CHAR
000000616
100000000 00000050 0006 PPPI_MATERI 2.3000000000 NUM
000000616 AL_QUANTITY 000000E+03
100000000 00000050 0007 PPPI_UNIT_O KG CHAR
000000616 F_MEASURE
100000000 00000060 0001 PPPI_MATERI 300-150 CHAR
000000616 AL
100000000 00000060 0002 PPPI_MATERI 0070 CHAR
000000616 AL_ITEM
100000000 00000060 0003 PPPI_MATERI Natriumhydrog CHAR
000000616 AL_SHORT_T encarbonat
EXT
100000000 00000060 0004 PPPI_OPERA 1000 CHAR
000000616 TION
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
000000616 TION
100000000 00000250 0003 PPPI_PHASE_ R_1111 CHAR
000000616 RESOURCE
100000000 00000250 0004 PPPI_PLANT_ 1100 CHAR
000000616 OF_RESOUR
CE
100000000 00000250 0005 PPPI_PHASE_ Analyze and CHAR
000000616 SHORT_TEXT adjust
100000000 00000250 0006 PPPI_EXTER ADJUST1 CHAR
000000616 NAL_PHASE
100000000 00000260 0001 PPPI_PHASE 1020 CHAR
000000616
100000000 00000260 0002 PPPI_PARAM MIX_TIME CHAR
000000616 ETER_NAME
100000000 00000260 0003 PPPI_PARAM 1.5000000000 NUM
000000616 ETER_VALUE 000000E+01
100000000 00000260 0004 PPPI_UNIT_O MIN CHAR
000000616 F_MEASURE
100000000 00000270 0001 PPPI_PHASE 1030 CHAR
000000616
100000000 00000270 0002 PPPI_OPERA 1000 CHAR
000000616 TION
100000000 00000270 0003 PPPI_PHASE_ R_1111 CHAR
000000616 RESOURCE
100000000 00000270 0004 PPPI_PLANT_ 1100 CHAR
000000616 OF_RESOUR
CE
100000000 00000270 0005 PPPI_PHASE_ Transfer to CHAR
000000616 SHORT_TEXT reactor unit
100000000 00000270 0006 PPPI_EXTER TRANSFER1 CHAR
000000616 NAL_PHASE
100000000 00000280 0001 PPPI_DATA_R SIMPLE CHAR
000000616 EQUEST_TYP
E
100000000 00000280 0002 PPPI_MESSA DPREAD CHAR
000000616 GE_CATEGO
RY
100000000 00000280 0003 PPPI_PROCE Y-300/PCS1 CHAR
000000616 SS_ORDER
100000000 00000280 0004 PPPI_DATA_P DENSITY_RE CHAR
000000616 OINT_NAME AD
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
E
100000000 00000310 0002 PPPI_MESSA DPREAD CHAR
000000616 GE_CATEGO
RY
100000000 00000310 0003 PPPI_PROCE Y-300/PCS1 CHAR
000000616 SS_ORDER
100000000 00000310 0004 PPPI_DATA_P PH1_END_OF CHAR
000000616 OINT_NAME _PHASE
100000000 00000310 0005 PPPI_REQUE PPPI_DATA_P CHAR
000000616 STED_VALUE OINT_VALUE
100000000 00000310 0006 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE DATE
100000000 00000310 0007 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE TIME
100000000 00000310 0008 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE TIME
100000000 00000310 0009 PPPI_UNIT_O CHAR
000000616 F_MEASURE
100000000 00000310 0010 PPPI_OPERA 2000 CHAR
000000616 TION
100000000 00000310 0011 PPPI_PHASE 2010 CHAR
000000616
100000000 00000320 0001 PPPI_PHASE 2020 CHAR
000000616
100000000 00000320 0002 PPPI_OPERA 2000 CHAR
000000616 TION
100000000 00000320 0003 PPPI_PHASE_ R_1121 CHAR
000000616 RESOURCE
100000000 00000320 0004 PPPI_PLANT_ 1100 CHAR
000000616 OF_RESOUR
CE
100000000 00000320 0005 PPPI_PHASE_ Add mixture CHAR
000000616 SHORT_TEXT from operation
100
100000000 00000320 0006 PPPI_EXTER CHARGE2 CHAR
000000616 NAL_PHASE
100000000 00000330 0001 PPPI_PHASE 2030 CHAR
000000616
100000000 00000330 0002 PPPI_OPERA 2000 CHAR
000000616 TION
100000000 00000330 0003 PPPI_PHASE_ R_1121 CHAR
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
000000616 RESOURCE
100000000 00000330 0004 PPPI_PLANT_ 1100 CHAR
000000616 OF_RESOUR
CE
100000000 00000330 0005 PPPI_PHASE_ Reaction takes CHAR
000000616 SHORT_TEXT place!
100000000 00000330 0006 PPPI_EXTER REACTION1 CHAR
000000616 NAL_PHASE
100000000 00000340 0001 PPPI_PHASE 2030 CHAR
000000616
100000000 00000340 0002 PPPI_PARAM PH_VALUE CHAR
000000616 ETER_NAME
100000000 00000340 0003 PPPI_PARAM 6.5000000000 NUM
000000616 ETER_VALUE 000000E+00
100000000 00000340 0004 PPPI_PARAM 6.0000000000 NUM
000000616 ETER_VALUE 000000E+00
_
MIN
100000000 00000340 0005 PPPI_PARAM 7.0000000000 NUM
000000616 ETER_VALUE 000000E+00
_
MAX
100000000 00000350 0001 PPPI_DATA_R SIMPLE CHAR
000000616 EQUEST_TYP
E
100000000 00000350 0002 PPPI_MESSA DPREAD CHAR
000000616 GE_CATEGO
RY
100000000 00000350 0003 PPPI_PROCE Y-300/PCS1 CHAR
000000616 SS_ORDER
100000000 00000350 0004 PPPI_DATA_P PH1_END_OF CHAR
000000616 OINT_NAME _PHASE
100000000 00000350 0005 PPPI_REQUE PPPI_DATA_P CHAR
000000616 STED_VALUE OINT_VALUE
100000000 00000350 0006 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE DATE
100000000 00000350 0007 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE TIME
100000000 00000350 0008 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE TIME
100000000 00000350 0009 PPPI_UNIT_O CHAR
000000616 F_MEASURE
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH
6$3$* 333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
RY
100000000 00000440 0002 PPPI_PROCE Y-300/PCS1 CHAR
000000616 SS_ORDER
100000000 00000440 0003 PPPI_OPERA 4000 CHAR
000000616 TION
100000000 00000440 0004 PPPI_INSPEC 000000000000 CHAR
000000616 TION_LOT
100000000 00000440 0005 PPPI_INSPEC 10 CHAR
000000616 TION_
CHARACTERI
STIC
100000000 00000440 0006 PPPI_REQUE PPPI_NUMBE CHAR
000000616 STED_VALUE R_OF_
INSPECTIONS
100000000 00000440 0007 PPPI_REQUE PPPI_INSPEC CHAR
000000616 STED_VALUE TION_
SHORT_TEXT
100000000 00000440 0008 PPPI_REQUE PPPI_INSPEC CHAR
000000616 STED_VALUE TION_
RESULT
100000000 00000440 0009 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE DATE
100000000 00000440 0010 PPPI_REQUE PPPI_EVENT_ CHAR
000000616 STED_VALUE TIME
100000000 00000450 0001 PPPI_PHASE 4020 CHAR
000000616
100000000 00000450 0002 PPPI_OPERA 4000 CHAR
000000616 TION
100000000 00000450 0003 PPPI_PHASE_ R_1140 CHAR
000000616 RESOURCE
100000000 00000450 0004 PPPI_PLANT_ 1100 CHAR
000000616 OF_RESOUR
CE
100000000 00000450 0005 PPPI_PHASE_ Receive CHAR
000000616 SHORT_TEXT mixture from
operation
100000000 00000450 0006 PPPI_EXTER CHARGE2 CHAR
000000616 NAL_PHASE
100000000 00000460 0001 PPPI_PHASE 4030 CHAR
000000616
100000000 00000460 0002 PPPI_OPERA 4000 CHAR
000000616 TION
-XQH
333,3&6,QWHUIDFH/LQNLQJRI3URFHVV&RQWURO6\VWHPV 6$3$*
7DEOH&5)93URFHVV,QVWUXFWLRQ&KDUDFWHULVWLFV
-XQH