SAP PIPO Job Description
SAP PIPO Job Description
Must be able to combine business processes with PI development tools. Involved in all phases of
the lifecycle including;
POC, blueprinting, mapping, design, configuration, testing, go-live, and support.
Demonstrates the ability to translate business needs into solution architecture requirements and
delivering middleware solutions for
Interfaces between various SAP and non-SAP applications.
Responsible for supporting and independently completing project tasks, Identifies key drivers of a
defined, straight forward problem and proposing solutions.
Create and maintain technical specifications from functional/business requirements for all
integration/development work.
Experience in working in an onshore / offshore model.
Strong skills in SAP PI/ABAP design and development. Knowledge in SAP PI versions 7.1/7.4
capabilities and configuration.
Experience in connecting PI to both SAP and multiple NON-SAP systems.
Experience with PI components such as System Landscape Directory - SLD, Enterprise Service
repository - ESR, Integration Directory - ID
Expertise in Java, XSLT and ABAP mapping. Process Design with BPM, BRM.
EDI experience with various EDI documents (i.e., PO, ASN, Invoice, etc.) integrating with SAP
and non-SAP.
Experience in integrating PI heterogeneous partners (A2A, B2B, M2M)
PI Development Team
Responsible for understanding and co-ordinating with functional consultant before developing any
interface.
Responsible for writing the technical specification of all the interfaces.
Development in Enterprise Services Repository.
Configuration in Integration Builder & Having Knowledge of all the node functions.
Responsible for co-ordinating when SIT and UAT is going on.
Responsible for making any changes in interface only if there is proper CR for this.
Responsible for error or alert handling & should have a proper and clear understanding in case of
any issue.
PI Support Team
Primary responsibility of PI support team to make sure Production system is up and running.
They are responsible for any issue occurred in Production system raised by customer to be
solved within the SLA.
If it is data issue they should try to check and process the message as per the requirement.
Responsible for handling incidents and tickets causing service disruption in the PI landscape
They should not change the mapping if any message failed with mapping error. They should
highlight it and take help from development team to fix the issue.
Any changes should not be carried out directly in production.
They should keep monitoring the system and if they see any issue or alerts or message failed,
they should take the necessary actions.
Responsible to maintain the monitoring report of PI message flow includes successful as well as
failed.