PIC Integration with PP and PM Hierarchy
Plant Information Catalog(PIC) provides the functionality to the user to logically group shop floor assets in a hierarchical structure with aliases and hierarchies understandable from a business user’s point of view. The shop floor integration is accomplished through Plant Connectivity(PCo). This is what is present till SP3 of MII 14.0 release.
In SP4 release, Plant Information Catalog(PIC) integration with Production Planning(PP) and Plant Maintenance(PM) hierarchies is getting introduced.
PIC objects can be mapped to the PP and PM objects from the ERP system along with the mapping with the shop floor assets through PCo and InSQLPCo connectors.
InSQLPCo connector is a new connector added in this release and more information could be found in the MII help document:
This completes the top to bottom integration i.e. enterprise or ERP level as top and shop floor as bottom.
For this integration to work, a new Resource Adapter is introduced in MII 14.0 SP4 named ‘MII Plant Information Catalog Connection‘. You would have to give all the necessary ERP system information in this resource adapter for the integration to work. Basically this is the resource adapter which PIC would use to communicate with the ERP system.
You could find the adapter at the following location in the server: Configuration –> Infrastructure –> Application Resources
Here search in the table with name MII Plant Information Catalog Connection and fill the necessary details(as shown in the screen shot).
Once these settings are done in net-weaver, you would be able to browse the PP and PM hierarchies in the Plant Information Maintenance screen.
ERP Objects for PP which would come in the tree here are Plant, Hierarchy, Work Center and Capacity and for PM, the objects are Plant,Functional Location, Equipment, and Measuring Point.
Options are present in the screen for adding or mapping the ERP objects from the PP and PM hierarchies.
One interesting option is of adding ERP Object with children where the ERP object and all its children would be added to PIC and this operation will run in background.
Plant, Hierarchy, Work Center, Functional Location and Equipment can be added as a PIC group or mapped to a PIC group.
Measuring Point can be added as a PIC tag or mapped to a PIC tag.
Capacity cannot be added but it can be mapped to a PIC group.
MII ships some predefined Categories and Property Sets in this release. These predefined objects specifically caters to the ERP Objects which are present in PP and PM hierarchies.
These are the pre-shipped Categories and Property Sets:
|Category||Associated Property Set|
Pre-shipped property sets are non-editable objects.
Pre-shipped categories can be edited by adding more property sets but the pre-shipped property sets cannot be removed from the category.
Whenever you add or map a certain ERP object in PIC, corresponding category and property set is attached to the PIC object.
For example, whenever you add or map a plant ERP object into PIC, the PIC object category would be SAP_Plant and it would contain the property set SAP_Plant .
Properties inside this property set would contain all the information fetched about the ERP plant object.
Similarly for a workcenter ERP object, category is SAP_WorkCenter and property set is SAP_WorkCenter and this is true for all the other ERP objects.
Only exception is the capacity in PP Hierarchy. For capacity no category is present and only property set named SAP_Capacity is present.
The different properties supported for each ERP object can be viewed in the Property Sets Screen by viewing the properties present for each pre-shipped property set object.
Note: Custom RFC are developed in ERP system for this integration to work.
Notes For PP RFCs:
1. 1822818 – This note contains the RFCs
2. 1947335 – This is the correction note on top of Note 1822818.
Notes for PM RFCs:
1. 1897708 – This is the prerequisite note for creating ABAP dictionary objects.
2. 1964478 – This note contains RFCs