Hierarchy

⤷

⤷

IMG Activity
ID | PCO_SAPODA | Settings for Replacement of SAP ODA |
Transaction Code | S_YI3_39000027 | (empty) |
Created on | 20110113 | |
Customizing Attributes | PCO_SAPODA | Settings for Replacement of SAP ODA |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PCO_SAPODA |
Use
If you are using SAP ODA, or intend to do so in the future, instead of using the SAP ODA Connector, you can use the product Plant Connectivity 2.2 to establish the connection to an OPC server.
If you decide to replace the SAP ODA Connector by PCo, you should note that the OPC Substandard OPC AE (Alarms & Events) for SAP ODA is not supported by PCo.
You make the settings for SAP ODA in the ERP system in the IMG under Production Planning for the Process Industry --> Process Management --> SAP ODA (OPC Data Access) --> Make Settings for SAP ODA (transaction COOPC1).
Requirements
- You have created the RFC destination for your PCo agent instance. See also: Define RFC Destination
- If you are already using SAP ODA and have therefore already made settings using the SAP ODA Connector, it is also possible to carry on using these with PCo, including the RFC destination. The following prerequisites must be satisfied:
- You have deactivated the instance of the SAP ODA Connector, i.e. the service must have been stopped or deactivated.
- In the RFC settings for the PCo agent instance, you have entered the same connection data as for the SAP ODA Connector:
- Program ID
- Gateway server
- Gateway service
- You have started the agent instance in the PCo Console.
Standard settings
Activities
With regard to the settings in the ERP system for SAP ODA in conjunction with PCo 2.2, you must note the following:
- Basic Settings
Here you specify the user name and the password for the RFC service. These entries are not relevant to PCo.
- OPC Server
- Enter a name of your choice for the OPC server.
- Specify the RFC destination that you have defined for your PCo agent instance.
- Specify the OPC server ID.
- Depending on which server ID you have selected, the checkboxes for the Synchronous Data Access and Data Access Subscription functions are selected automatically if supported by the selected OPC server. Both are ERP functions. You should remove the selection only if you do not want to use or allow the function in the ERP system.
- It is not necessary to enter anything in the Further Settings area of the screen. You make these settings in PCo. For more information on the settings relevant to SAP ODA in the PCo Console, see the documentation for PCo 2.2 under Integration with the Business Suite --> SAP ODA.
- When you have started the agent instance in the PCO console, you can test the connection to the OPC server and display the namespace.
- OPC Data Access Tag
- Enter a name of your choice for the OPC tag.
- Specify the OPC server that you previously specified in the step Define OPC Server.
- Choose an OPC item ID.
The following settings for the tag are no longer relevant in connection with PCo:
- Access Mode
- Buffer Time
- Deadband
- For more information on the settings relevant to SAP ODA in the PCo Console, see the documentation for PCo 2.2 under Integration with the Business Suite --> SAP ODA.
Example
Business Attributes
ASAP Roadmap ID | 151 | Design interfaces |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PCO_SAPODA | 0 | BYI3000069 | Plant Connectivity (Pco): ABAP part |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20110120 |
SAP Release Created in | 731 |