Manufacturing Events 
Use
Manufacturing event is a generic term for events that are provided by different applications. The Manufacturing Data Access interface can be used to exchange events. Every application that is registered at the interface as a service can provide events and subscribe to them.
For more information, see Manufacturing Data Access .
For more information on how to define the data access in PI sheets and manufacturing cockpits, see Type 0: Definition of Manufacturing Data Access .
Prerequisites
OPC Events
To use events of the services ODA (OPC Data Access) and OAE (OPC Alarms/Events), you must first have created a subscription in Customizing.To do so, go to Customizing for Process Management and choose SAP ODA (OPC Data Access) .
For more information about SAP ODA, see SAP OPC Data Access .
Features
The following services provide events:
MDA: Generic services
PSH : PI sheet
PMC : Manufacturing cockpit
ODA: OPC Data Access
OAE: OPC Alarms/Events
The following services can access events:
MSG: Create process message automatically See also: Creating Process Messages Automatically
PSH: PI sheet See also: Type 0: Definition of Manufacturing Data Access
PMC: Manufacturing cockpit See also: Type 0: Definition of Manufacturing Data Access
Addresses are used to access events. They start with the name of the service. The remaining address parts depend on the service. You can use value help to select events.
Service MDA
This service offers the generic services BROADCAST and REDIRECT.
Using BROADCAST , you can define user-specific events. A generic data point is available for this to which you can write any value. The value change of this data point is published as an event. Other services can subscribe to this event.
The address for the propagation of the event is made up as follows:
Event |
Address |
Event to be propagated individually |
MDA:BROADCAST.SEND.<Category> <Category> can be replaced by any character string. Note that the entry is case-sensitive. MDA:BROADCAST.SEND . DPV Service MDA, the user-defined event DPV is to be published. |
The address for the subscription to the event is made up as follows:
Event |
Address |
An event that was propagated individually |
MDA:BROADCAST.<Category> <Category> can be replaced by the character string that you have used for event propagation. Note that the entry is case-sensitive. MDA:BROADCAST.SEND . DPV Service MDA, the user-defined event DPV is to be subscribed. |
Parameters of MDA Events
The following parameters can be transferred as data points together with the event. The address is made up as follows:
Parameter |
Address |
The system logon from which the event was sent |
MDA:BROADCAST.PARAM.SESSION |
The terminal from which the event was published |
MDA:BROADCAST.PARAM.TERMINAL |
The time stamp for which the event was published |
MDA:BROADCAST.PARAM.TIMESTAMP |
The user who published the event |
MDA:BROADCAST.PARAM.USER |
The value of the data point that is transferred with the event |
MDA:BROADCAST.PARAM.VALUE |
Example
Example for BROADCAST
The fill level of tank #333 is to be recorded in a manufacturing cockpit. The up-to-date fill level is to be published as an event by pressing a button. In the address MDA:BROADCAST.SEND. <Category> , <Category> was replaced by DPV meaning data point value .
In the cockpit definition, you define the following characteristics in the sequence specified:
Characteristic |
Characteristic Value |
|
PPPI_DATA_REQUEST_TYPE |
Simple data request |
|
PPPI_DATA_POINT_NAME |
Tank #333 |
|
PPPI_OUTPUT_CHARACTERISTIC |
PPPI_DATA_POINT_NAME |
|
PPPI_INPUT_REQUEST |
Record fill level |
|
PPPI_DATA_POINT_VALUE |
0 |
|
PPPI_VARIABLE |
VAR_DPV |
|
PPPI_REQUESTED_VALUE |
PPPI_DATA_POINT_VALUE |
|
PPPI_DATA_ACCESS |
Manufacturing Data Access |
|
PPPI_BUTTON_TEXT |
Publish |
|
PPPI_FUNCTION_DURING_DISPLAY |
Permitted |
|
PPPI_EXPORT_DATA |
MDA:BROADCAST.SEND.DPV |
|
PPPI_STRING_VARIABLE |
VAR_DPV |
In transaction CO69 – Create Process Messages Automatically , a process message is to be created automatically whenever the event propagated in the example above is sent. You define the following in transaction CO69:
Option Event-Driven Start as the start condition
Address MDA:BROADCAST.DPV as the event
Service PSH
The service PSH offers the following events. The event address is made up as follows:
Event |
Address |
PI sheet was completed |
PSH:<No. of PI sheet>.COMPLTD PSH:100000000000004711.COMPLTD Service PSH, PI sheet 100000000000004711 was completed |
PI sheet was created |
PSH:<No. of PI sheet>.CREATED PSH:100000000000004711.CREATED Service PSH, PI sheet 100000000000004711 was created |
Maintenance was started |
PSH:<No. of PI sheet>.LOGIN PSH:100000000000004711.LOGIN Service PSH, user logged on to maintain PI sheet 100000000000004711 . |
Maintenance was exited |
PSH:<No. of PI sheet>.LOGOFF PSH:100000000000004711.LOGOFF Service PSH, user logged off from PI sheet 100000000000004711 . |
Data was reported |
PSH:<No. of PI sheet>.REPORTD PSH:100000000000004711.REPORTD Service PSH, data of PI sheet 100000000000004711 was reported. |
Data was saved |
PSH:<No. of PI sheet>.SAVED PSH:100000000000004711.SAVED Service PSH, PI sheet 100000000000004711 was saved. |
Global variables were changed |
PSH:<No. of PI sheet>.VARCHGD PSH:100000000000004711.VARCHGD Service PSH, global variables in PI sheet 100000000000004711 have changed. |
Service PMC
The service PMC offers the following events. The event address is made up as follows:
Event |
Address |
Manufacturing cockpit was started |
PMC:<Plant>. <Cockpit name>.LOGIN PMC:0001.MYCOCKPIT.LOGIN Service PMC, user logged on to maintain cockpit MYCOCKPIT . |
Manufacturing cockpit was exited |
PMC:<Plant>. <Cockpit name>.LOGOFF PMC:0001.MYCOCKPIT.LOGOFF Service PMC, user logged off from cockpit MYCOCKPIT . |
Global variables were changed |
PMC:<Plant>. <Cockpit name>.VARCHGD PMC:0001.MYCOCKPIT.VARCHGD Service PMC, global variables in cockpit MYCOCKPIT have changed. |
Service ODA
The service ODA offers the following events. The event address is made up as follows:
Event |
Address |
Value change of an OPC Data Access subscription occurred |
ODA:<Plant>. <OPC item>.VCHD ODA:0001.MYITEM.VCHD Service ODA, OPC item MYITEM, value has changed. |
Service OAE
The service OAE offers the following events. The event address is made up as follows:
Event |
Address |
Event of an OPC Alarms/Events subscription occurred |
OAE:<Plant>. <OPC subscription>OAE:0001.MYSUBSCRIPTION Service OAE, OPC subscription MYSUBSCRIPTION was triggered. |
Parameters of OPC Events
The following parameters can be transferred as data points together with the event. The address is made up as follows:
Parameter |
Address |
Acknowledgement cookie |
OAE:<Plant>. <OPC subscription>.ACKC OAE:0001.MYSUBSCRIPTION.ACKC |
Event was acknowledged |
OAE:<Plant>. <OPC subscription>.ACKD OAE:0001.MYSUBSCRIPTION.ACKD |
Acknowledgement required |
OAE:<Plant>. <OPC subscription>.ACKR OAE:0001.MYSUBSCRIPTION.ACKR |
Status "active" of event condition |
OAE:<Plant>. <OPC subscription>.ACTV OAE:0001.MYSUBSCRIPTION..ACTV |
Event condition |
OAE:<Plant>. <OPC subscription>.CND OAE:0001.MYSUBSCRIPTION.CND |
Event date |
OAE:<Plant>. <OPC subscription>.DATE OAE:0001.MYSUBSCRIPTION.DATE |
Event message text |
OAE:<Plant>. <OPC subscription>.MSG OAE:0001.MYSUBSCRIPTION.MSG |
Severity |
OAE:<Plant>. <OPC subscription>.PRIO OAE:0001.MYSUBSCRIPTION.PRIO |
OPC limitation |
OAE:<Plant>. <OPC subscription>.QL OAE:0001.MYSUBSCRIPTION.QL |
OPC subquality |
OAE:<Plant>. <OPC subscription>.QS OAE:0001.MYSUBSCRIPTION.QS |
OPC quality |
OAE:<Plant>. <OPC subscription>.QUAL OAE:0001.MYSUBSCRIPTION.QUAL |
Event text |
OAE:<Plant>. <OPC subscription>.RT OAE:0001.MYSUBSCRIPTION.RT |
Event subcondition |
OAE:<Plant>. <OPC subscription>.SCND OAE:0001.MYSUBSCRIPTION.SCND |
Event source |
OAE:<Plant>. <OPC subscription>.SRC OAE:0001.MYSUBSCRIPTION.SRC |
Event time |
OAE:<Plant>. <OPC subscription>.TIME OAE:0001.MYSUBSCRIPTION.TIME |