We provide IT Staff Augmentation Services!

Pi Developer Resume

4.00/5 (Submit Your Rating)

SUMMARY:

Confidential has over nine years of experience in Designing, Configuration and Implementation of SAP NetWeaver PI (Process Integration) and EDI including one year training in SAP. She has excellent technical and configuration knowledge about Adapters like AS2, IDoc, HTTP, RFC, JDBC, SOAP, FILE, and XI Adapters. She is experienced in Designing, Configuration and Monitoring. Experienced in ALE configurations, Includes Port Definitions, RFC destinations, creating Logical System and Partner Profile generation. She gained good experience in PI every day configuration issues like creating RFC destinations on both R/3 and PI side, Configuration of IDOC’s. Good knowledge in developing Classical and Interactive Reports. Expert in developing data dictionary objects like Tables, Views, Data elements, Domains, Search helps. Good knowledge in Session Method and Call Transaction Method and LSMW using BDC. She gained knowledge in designing and developing custom layouts using SAP scripts and Smart Forms.

TECHNICAL SKILLS:

Hardware: Trouble Shooting and Assembling

ERP Applications: SAP

Netweaver: Components PI

Databases: Oracle, Sql Server 2008

Languages: C, XML, XSLT

PROFESSIONAL SAP EXPERIENCE:

Confidential

PI Developer

Responsibilities:

  • Analysis, Design, Mapping, Development, Testing and production support of maps and components for B2B integration using PI and Biz Link Mapper and creating technical documentation for the existing code.
  • Excellent skills in TRADACOMS,ANSI X12 EDI,UN/EDIFACT,XML Standards.
  • Used Seeburger AS2 Adapter for EDI Transactions like 850,855,856 etc.
  • Message processing done in Seeburger AS2 adapter using modules Classifier, Converter and Splitter.
  • Experienced in developing interfaces and maps
  • Well experienced in Client communication, gathering requirements.
  • Integration of EDI transactions into ERP Systems like SAP R/3.
  • Experienced in HPQC Testing.
  • Excellent skills in FILE,DATABSE,EMAIL,XML Data,Sterling,AS2,FTP,SMTP,HTTP,HTTPS and IDOC Standards.

Confidential, Brown, Chicago

Technology Support

Responsibilities:

  • Working as a PI Developer.
  • Interfaces Developed.
  • Worked on Integration Engine Monitoring and Runtime workbench monitoring.
  • Created JCO Lookups.
  • Worked closely with functional team by doing Testing.
  • Change Pointers developed for Vendor Master
  • Developed RFC’s.
  • Worked on Reports.
  • Created RFC Destinations, Port and Partner Profile.

Confidential

Responsibilities:

  • Developed the Accelerated maps for some EDI signals.
  • Prepared the mappings in generalized manner, which can be useful for the clients using EDI.
  • Almost 60% of the mapping will be same for all the customers so that we can directly import the mappings into IR and need to do necessary changes in the mappings according to the customer requirement.

Confidential, Seattle

Team Member

Responsibilities:

  • Working as a PI Developer.
  • Interfaces Developed.
  • Worked on Integration Engine Monitoring and Runtime workbench monitoring.
  • Worked closely with functional team by doing Testing.

Confidential

Team Member

Responsibilities:

  • Working as a PI Developer.
  • Interfaces Developed.
  • Created & imported software component versions in XI and assigned business specific namespaces.
  • Components in Integration Repository. Assigned development software component version to Business system in SLD and also Created Business services in SLD.
  • Created namespaces for IDoc - to-file, IDoc-to-Soap (Flexware), SOAP (Flexware)-to-JDBC (SQLServer).
  • Created source and target data structure (target DataType) according to the required fields.
  • Created Message types and Message interfaces for target system in the integration objects.
  • Created the message mappings, interface mappings in mapping objects.
  • Created RFC destination, port, and partner profiles in the SAP r/3 system for IDOC scenarios.
  • Created RFC destination, port, and loading metadata using different t-codes in the XI system.
  • I have checked the Integration Directory for sender service whether it is using the right sender logical system/client or not.
  • Created corresponding configuration objects (sender agreement & channel not needed for Idoc scenario's) for these scenario's and activated.
  • Monitoring & error handling these IDocs through SM59, SXI MONITOR, IDX5, Service-Adapter specific identifiers.
  • It is a role to Integration Flexware Product with SAP system.
  • Created SLD objects that they are software catalog and system catalog by following the instructions given by my Team lead (Naming Conventions for XI Content Packages Used for Certification).
  • Created Product name, software component name & version for the FlexWare product.
  • Created Technical system and its category is third party.
  • Created client for the technical system that is called business system.
  • Imported following BAPI’S into the Integration Repository (IR).
  • Created Namespaces in the software component version and created corresponding interface objects (data types, message types, message interfaces), mapping objects (message mapping, Interface mapping).
  • Created corresponding configuration objects (sender communication channel, receiver communication channel in the business system, sender agreement, receiver determination, interface determination and receiver agreement) for the above scenarios.
  • I have used SOAP adapter at sender side and RFC adapter at receiver side.
  • Generated corresponding wizdel (WSDL) files for the scenarios.
  • Using these wizdel files FlexWare successfully communicates the SAP system.
  • Written RFCs for the following:
  • To get account balance and outstanding balance of a customer.
  • Over due amount information.
  • Account information after every fortnight to customer.
  • Debtors Balance
  • Stock Checking
  • Collection Plant wise, Dealer wise.
  • Written Custom IDOCs.
  • Configuration at SAP:
  • IDOC Ports.
  • RFC destinations to connect to 3rd party systems
  • Message Controls.
  • Scheduling SAP programs.
  • Configured ALE-MESSAGE CONTROL extensively to send IDocs whenever a Sales Order is created satisfying a business condition.
  • Automatic generation of IDocs whenever changes happened to master data.
  • Setting up SAP-ALE (IDoc) Interface by generating Partner Profiles, Maintaining distribution model, Message types for applications like Material Master, Vendor Master, and Customer Master etc.
  • Created Ports (XML-HTTP).
  • Extensively used Message Control.

We'd love your feedback!