The data is being integrated between SAP ERP and Oracle’s Primavera Enterprise Project Portfolio Management (P6 EPPM). It removes slowness of processer, duplicate efforts, manual or unnecessary work and variable reporting issue.
SAP consolidate orders and project data from SAP ERP with P6 EPPM. SAP EPC synchronizes work order data from Plant Maintenance or project data from Project System with project data in P6 EPPM by creating or updating data in P6 EPPM, Plant Maintenance, or Project System.
This blog gives mapping and business rules of SAP Enterprise Project Connection’s sample Oracle Primavera solution.
Project Planner: – Planners creates work orders in plant management or projects.
Scheduler: – Scheduler creates and maintains the project schedules in project management system.
Executive: – Executive is responsible for operational, maintenance or efficiencies and effectiveness of resources.
There are two types of orders which is created manually in P6 EPPM.
A. Turnaround: – This must be created manually. Turn around orders are mapped in P6 where the project ID is combination of planning plant value and revision code value. Turn around orders are designed in case of low priority value and revision code is assigned to it.
B. Maintenance: – This order must be created manually. Turn around orders are designed in case of low priority value. This is called Maintenance as the project ID is maintenance planning plant value.
Becoming Familiar with Transfer Order Transaction
Object Correspondence: – The Object Correspondence diagram shows the levelling of plant maintenance and P6 EPPM at order level. The Work Order Header and Operations Object from Plant maintenance maps to the Start Milestone Activities and
System of Record: – As the name suggest, this recognize the system from where we get the object. Ownership is always important for establishing business rules and system behavior as it find out the authoritative code in case of difference of objects in Plant Maintenance and P6 EPPM.
Object Identity: – The object use key attributes in order to find whether the object is already there in target system so that in can be updated. You will need to create the object in case it is not in the system.
Field Level Mapping: – Identifies the set of data which comprises an object by identifying what fields SAP EPC will amend during data transfers.
Business Rules: – You will need to identify the process and time to modify the target system. The Object Correspondence and object identity can only be used for getting an understanding of what the same objects look like in source and target system.