As companies begin to understand more about service-oriented architecture (SOA) and the benefits it provides to the business — namely, its ability to reuse existing IT assets and nimbly adapt technology to evolving business needs and processes — IT architects are now looking at how to best create and provision services. Companies with core ABAP development groups are especially seeking a concrete service development roadmap. They want to find out how they can use an individual programming language in an SOA environment, which emphasizes openness and standards. First and foremost, it is critical that IT teams understand SOA's basic principles — that it's a means of creating loosely coupled services that allow for separating the description of the service, its actual implementation, and its binding. This separation is, after all, the pillar of SOA's flexibility. But to take the next step and actually create services, IT architects must understand how a typical service development cycle happens. With SAP NetWeaver Process Integration (SAP NetWeaver PI, formerly called SAP NetWeaver XI) 7.1, ABAP teams will find all the capabilities they need to develop services — starting with defining a service in the Enterprise Services Repository (ESR), implementing it in ABAP, configuring its service endpoints, and publishing it in an easily accessible services registry.

This article will walk you through these steps. It's important to note that the majority of services SAP has delivered through enhancement packages are implemented in ABAP. This comes as no surprise, really, as ABAP-based development is renowned for its power, simplicity, and efficiency (see sidebar).

Why ABAP and SOA Are a Great Fit It's true that service-oriented architecture, by nature, is intended to make the programming language used irrelevant. SOA is designed to work with any open standard, so programmers should be able to use their environment of choice when developing services. Those proficient in ABAP, then, can continue to use it in an SOA environment. In fact, ABAP's a natural fit for SOA, for several reasons: • ABAP is optimized for business applications to allow high levels of scalability in transaction handling and data size. • ABAP offers powerful transport and change-management features supporting the development of complex applications even in large development teams.

• The ABAP Development Workbench is a powerful and integrated development environment. Develop a Service in ABAP in 5 Steps Perhaps the best way to illustrate the process of providing services is to walk through a typical business scenario.

Consider an employee working with SAP Supplier Relationship Management (SAP SRM) who wants to create new vendor data within the SRM system as well as search for existing vendors. Since this functionality is also frequently used within other applications like SAP ERP or SAP Customer Relationship Management (SAP CRM), the employee wants to implement this functionality as an enterprise service. Developing the service involves five steps: • Model the service interface in the ESR • Generate the provider proxy • Implement the service's operations • Configure the endpoint in SAP NetWeaver Administrator • Publish the service definition to the Services Registry Importantly, these steps incorporate SAP's best-practice recommendation for a 'contract first' way of developing services. The first step in this process involves defining the service interface, or contract, in a central repository — the ESR, in this case. Only then do we move to implementing the actual functionality. We're not simply wrapping functionality with services standards to make it available as a Web service. Rather, we are centrally defining exactly what criteria the service needs to fill before we implement the operations.

XI/PI: A Guide to Using SAP XI SOAP Adapter. I have webservice to File scenario. Like i have to create the operation mapping in sap pi using web services.

In other words, we're not simply wrapping functionality with services standards to make it available as a Web service. Rather, we are starting from a business perspective and centrally defining exactly what criteria the service needs to fill — determining what request and response messages are necessary to fulfill the business requirement — before we implement the operations. System Prerequisites The business example highlighted in this article involves the following system prerequisites: • SAP NetWeaver Process Integration (SAP NetWeaver PI) 7.1 • Vendor management functionality available in an application like SAP Supplier Relationship Management (SAP SRM) Please note that the additional vendor management functionality requirement is specific to the example highlighted within this article.

Step #1: Model the Service Interface in the ESR Once you determine the granularity of the service you want to create — that is, how broad your required piece of functionality must be in order to address your business need — you can create the service interface for managing vendor data. Because the service is to be used for two tasks — creating and searching for vendor data — we design the interface with two operations: an asynchronous one for creating new vendor data and a synchronous one for searching by vendor ID. This ability to create service definitions with multiple operations is new as of SAP NetWeaver PI 7.1. We'll design the interface in the ESR of SAP NetWeaver PI 7.1, which is the central repository and modeling environment for enterprise service objects and process and service definitions. The ESR stores data that is relevant for configuring, installing, and deploying services, but does not provide runtime or platform-specific data.

The following designtime objects, then, need to be created: data types, message types, and the service interface and its operations. When available as a service, these objects can be reused — so you won't have to re-create them. In our example, we must start by creating the inbound, stateless service interface — which we'll name ManageVendor — with two operations: • The asynchronous CreateVendor operation references the already existing message types CreateVendor_MT for the request message and CreateVendor_FMT as the standard fault message type, which is used for handling any application-specific errors that may occur on the inbound side. This fault message, in turn, references the data types Vendor_DT and ExchangeFaultData. • The synchronous SearchVendor operation is based on the request and response message types SearchVendor_ReqMT and SearchVendor_ResMT and also the fault message type.

The underlying data types are Vendor_Req and Vendor_DT. Figure 1 shows the service interface as it is created in the ESR. The design of the service interface corresponds to a generated Web Services Description Language (WSDL) file.

Figure 2 shows an excerpt of the WSDL file that corresponds to the interface in Figure 1. Here you can see the two operations, CreateVendor and SearchVendor. An excerpt of the WSDL definition that corresponds to the service interface shown in Figure 1 Once you finish creating these objects, change lists are automatically created in the ESR. These change lists then must be activated; click the change list tab and choose Activate. Then proceed to the back-end system for proxy generation.

Step #2: Generate the Provider Proxy The objects we just created in the ESR are language independent. So to create language-specific objects, we will need to create a proxy object. In this next step, we'll go from the metadata definition to the language-specific definition. ESR objects are mapped to platform-specific proxy objects. Provider proxies can only be generated for objects in the ESR — the inbound ManageVendor service interface, in our case.

We will create and implement the proxies in the ABAP back-end system, in which the service will be running. To generate the provider proxy for ManageVendor, use the following process steps: • Go to transaction SE80 in the ABAP Development Workbench and start the Enterprise Services Browser.

The browser will connect to the ESR and display its software component versions, including the one in which the example ManageVendor service interface was created. • Expand the respective nodes of the component versions and the namespace, open the context menu of ManageVendor, and choose Create Proxy. • In the subsequent pop-up window, specify a package and a prefix, and choose Enter. • Based on the prefix that you specify, valid ABAP names are proposed. You can change the proposed names as required.

• The proxy is then generated automatically. The proxy's Properties tab, which is displayed after the generation completes, gives information about the generated proxy interface, such as the implementing proxy class, as well as the generated service definition (see Figure 3). The Properties tab displays information about the generated proxy interface and the service interface When the proxy is generated, all the underlying objects, as well as the WSDL file of the Web service based on that proxy, are generated automatically. This means that the service creation process is significantly simpler compared to SAP NetWeaver 7.0; the extra step of running the Service Definition Wizard to turn the provider proxy into a Web service is no longer necessary. The ABAP objects, though, including the class, interface, and data dictionary (DDIC) type, are not created in the system until you activate the proxy. The ABAP class of a service provider uses an ABAP interface and contains the implementation of the service provider methods.

A service provider class has one method for each operation modeled in the ESR. So for an application to use a proxy, the service provider methods will need to be filled with coding. Step #3: Implement the Service's Operations By double-clicking the interface provider class ZVCL_MANAGE_VENDOR, which is visible under the Properties tab in Figure 3, you can display the two operations, ManageVendor and SearchVendor. Then, double- click the method name ZXXII_MANAGE_VENDOR_XX~ CREATE_VENDOR to open the editor window. Here you will be asked to insert the implementation of the operation. Provide the coding required for your operation, then save and activate it.

Note that the coding could be a call to existing functionality, such as a BAPI or a function module. This would allow IT architects to use stable and mature functionality in a service-based way — without re-creating the actual implementation. Repeat this step for the second operation. The proxy now contains the business functionality required to run the service.

It does not, however, have an endpoint configuration yet. Step #4: Configure the Endpoint in SAP NetWeaver Administrator We'll now move to the WS Configuration section of SAP NetWeaver Administrator to configure the endpoint (see Figure 4). First, select the service definition ZManageVendor that was automatically created during proxy generation, and choose Create Endpoint. An endpoint contains a single runtime configuration. You can create different endpoints to define different runtime behaviors for the same service definition.

Under the Security tab you can also assign security settings, such as transport security and authentication, to the Web service. Configuring the endpoint in SAP NetWeaver Administrator After saving your settings, the runtime configuration with a port type will be available on the back-end system and can be integrated into an application. Remember, though, that so far this information is only available in the physical ABAP system where the service is running. For a consuming application to be able to discover the service, the service needs to be made available in a more easily accessible place. Step #5: Publish the Service Definition to the Services Registry The Services Registry is a UDDI v3-based registry that contains all the information required to run a service; it's an accessible place for discovering services available in your landscape.

To publish your newly created service, go to transaction WSPUBLISH in your ABAP system and select the service definition you want to publish. Simply select the registry to which you want to publish the service, and then choose OK. The service will then be listed in the registry and can be discovered by potential consumers (see sidebar).

Kavitha Krovi SAP XI/PI Tech Architect Consultant Profile Summary A successful XI/PI Architect Consultant, with 8 years of SAP Exp., focus on expansion of architecture with ESOA, active on the assignments, involved in designing the solutions with a role of lead consultant and capable in proven methodologies Skillful in Designing, implementations of Large Enterprise applications for EAI/B2B projects using ESOA Technologies Experience SAP Net Weaver XI/PI 7.1 Tech Architect with 8 years of implementation experience. Experienced in E SOA (Enterprise Service Oriented Architecture), ESR, SAP EAI, solution Approach. Proficient in Documenting business requirements, performing application design activities like writing functional designs & technical designs, Post implementation support, Test, and deploy activities. Completed 5 full life cycle middleware projects in different roles ranging from technical reviews, and module consultant to expert guidance in integration. Experience in complete Life cycle Implementation of XI projects i.e. From installation phase of XI to the production with Go-Live phase. Exposure to BPM tools, IBM SOA products for SAP Technologies SAP XI expertise is supported by strong technical expertise in ABAP.

Seize experience in functional modules – MDM, CRM, SRM, SCM, MM, BI, SD, MM, HR and FI. EXPERIENCE SUMMARY Company Name From To Designation Accenture-Chemical Industry, MI Aug’08 March’09 Lead PI Architect Specialist Accenture–Automotive&Finance Apr ‘08 July’08 Integration&Conversion Architect Accenture-HealthCare&Insurance Mar’08 Apr’08 Net weaver Lead. Accenture-Chemical Industry, TX Oct’07 Dec’07 XI Admin/Tec Arch. Accenture-Manufacturing, OH June’07 Oct’07. XI Tech Arch. EarthLink, Atlanta, GA Sep’06 June‘07. Lead/Senior XI Developer SwarovskiNorthAmericaLtd., RI.

July’06 Sep’06 SAP XI Tech. Lead Ferrero Polska, New York May’05 June’06. SAP-XI Tech.Consultant Master Foods, Atlanta Oct’04 Apr’05 SAP XI Developer Sauer-Dan Foss, Chicago, IL Mar’04 Sep’04. XI Designer, Configurer Bombardier, MicroSol, India May’02 Dec’03 Portal Content Developer CAREER SUMMARY SAP XI/PI & ESOA Application Architect Involved in Integration Architecture, Technical designs, Functional designs, Integration requirement specifications. Involved in the Implementation of ESOA with XI as a Central hub. Expert in troubleshooting and resolving existing performance and production problems and building complex technical architectures Successfully played the role of Integration Architect and Team Lead in various projects.

Strong XI BASIS Knowledge and involved in SAP WEB AS administration activities like configuring additional server node and installing dialog instance for J2EE Engine for load balancing, taking backup and recovery of SAP WEB AS(JAVA), administrating J2EE Engine through Visual Administrator and Config Tool, administering system landscape through SAP Net Weaver Administrator( NWA), configuring and viewing logs & traces. Configured the XI Landscape in SLD viz. Adding all the Systems in the System Landscape browser and creating Technical systems for the Web AS ABAP and Web AS JAVA. As a successful XI/PI-Tech Architect Consultant, making a positive difference to the client’s business by helping them maximize opportunities and avoid risks by utilizing my IT and business management skills towards ESOA while establishing myself firmly in the field of enterprise solutions. Actively involved in the community meetings for PI and contributed PI advanced Topics. Establish relations with all PI resources (Colleagues and Non colleagues) by solving their PI issues in KT.

Industry Expertise: Manufacturing, Health, Chemical, Customer Service, Retail, Financial Services, Sales, Communications & High Tech Proficient at SAP XI Graphical Mapping, basic/advanced functions, Proxies. Expertise in configuring XI sender & receiver adapters – Web Services, CIDX, File, RFC, XI, JMS, JDBC, IDOC, SOAP, Mail and HTTP. Configured Alerts for Application Errors and triggered them in Business Scenarios. Proficiency in carry out complex assignments which requires the development of new or improved procedure using BPM Qualified in plans, schedules, conducts, execute or co ordinates detailed phase of major programs. Implemented Challenging Tasks like configuration, designing, advanced mapping functions, debugging integration scenarios and developing complicated data definitions. Worked with Quality Assurance team for code review process involved in Assembly, unit and integrated testing. 2 years of experience in development of content for the Enterprise Portal 5.0, 6.0 beneath, have done architecture and prototyping of Net weaver products to create Enterprise Portal Project using WebDynpros.

2+ years in Application Development experience using SAP ABAP/4. Strengths Leadership skills – worked as ‘Team Leader’ managing a team size of 12. Analytical Capability in defining As-Is Processes and proposing To-Be Processes. Excellent communication and presentation skills. Self-motivated and enjoy working in a technically challenging environment. Strong focus on problem resolution.

Ability to learn new skills/tools on demand and deliver excellent productivity/results in short time. Share ideas, be creative and work in a fast paced environment. QUALIFICATION SUMMARY Master’s Degree in Information Technology Allahabad University, India. Bachelor’s Degree in Computer Science Nagarjuna University, India. ENCE DETAILS EXPERIENCE DETAILS SAP-XI Project Profile: Client: Chemicals-NEA-MCR1 Project- Saginaw, MI.

Industry: Chemical,Financial and Manufactring Duration: Aug’08 to March’09 Role: RICEF-Lead-PI Architect Specialist Description: Dow is a leader in science and technology, providing innovative chemical, plastic and agricultural products and services to many essential consumer markets. Dow Chemical current operates the majority of its corporate business functions on an SAP R/2 platform with aging technical infrastructure.

The Alliance has led to the creation of four IT development centers of expertise located globally and staffed with professionals from both Accenture and Dow, who work together to handle all development and support for more than 600 Dow applications. Each of the centers bears responsibility for a portfolio of applications; all share responsibility for SAP technology. Project Scope: To deploy SAP NetWeaver for the global corporate entity, including Financials, Sales and Distribution, Materials Management, Human Capital Management, and Business Intelligence (BW, BW-BPS, SEM-BCS, and Analytics).

Customer Procure to Pay; Hire to Retire; Order to Cash; Plan to Distribute are the Scope of processes. Dow Scope includes – ECC 6.0, SRM, SCM, PI, FI and EP. Modules worked for: • MN- Maintenance Next – Implemented MM, PM, QM and PP. • PN- Purchasing Next – for SD and PN • LP – Lead People – all HR Data – ESS, MSS, HR • FF – Finance - AP, AR, GL, CostCenter etc Responisbilities • Involved in Go-Live (Development, Implementation and Testing Phases) for Release 2&3 of Business Partner, Employee, Contractor on-boarding, Legacy Interface & Seconded Employees and PN interfaces. • Implemented Functional, Technical Design, Code Reviews, and Testing for Purchasing Next, Lead People interfaces like Employee, Contractors, HR Attributes, BP, Order Create, Order Response, and ASN. • Work as an expert AS and lead in the PI space for the RICEF Team.

• Work with and help RICEF TL/LAS and Integration lead AS to make sure architectural direction, design, build and testing happens properly for PI based interfaces which technically provides a solid, high performance and flexible infrastructure for these interfaces at the same time meeting cost and time deadlines. • This includes guidance on when to use and when not to use PI, providing architectural guidance, helping with complex designs, builds and testing. • Working closely with client counterparts, functional teams, tech management and RICEF Teams of North America, China and India. • Understanding the scope of work, architectural directions and close coordination with the Integration Lead AS is the key here.

• Also PSC is starting some PI support rotations for some of the existing projects going live where you might have to play a role in participating in that rotation as well as leading and helping RICEF TL with that activity. • As a PI Lead Specialist, involved in the code Review Process/design/Component, Assembly, Pre-Prod and Product Testing for LP, PN, MN and FF interfaces. Scrum Process Template Visio. Client: Accenture-Autobahn- Detriot, MI.

Industry: Automotive & Finance Duration: April’08 to Jul’08 Role: SAP Net weaver - Integration & Conversion Architect Lead. Description: GMAC Financial Service is a global services company, which maintains a diversified portfolio of business operations in Automotive Finance, Dealer and Personal Line Insurance, Real Estate Finance, Commercial Finance and Operates in approximately 40 countries. The current state is: Inefficiencies in closing the books and preparing external financial reports, No automated connectivity of multiple general ledgers, resulting in duplicate entry, No daily general ledger closes.

GMAC has burning issues: Inconsistent processes, Lack of transparency due to multiple disconnected systems, No common chart of accounts, and lack of top-down guidance on structure and utilization. The Business challenge: § Enable GMAC corporate and operating segments to process and deliver financial business information using common business processes, standards and tools. § Define a common Chart of Accounts (“COA”) at a transactional level that meets both US and local GAAP requirements. § Implement a common financial platform (i.e., SAP) for all GMAC operating segments. My Responsibilities: § For Plan and Define Phase - Responsible as Integration Architect with in the Accenture Technology Team to develop an extensive external evaluation and feedback with regards to the company’s current practices and defined leading practices that could be adopted to address the challenges presented.

§ Help the client to identify for Specific departmental needs and priorities. § Review Current Processes all SAP Enablers, Identify Key Global Changes, Highlight current problems, Identify inefficient and uncommon processes Organizational changes, Process changes, System changes. Onyx X10 Crack.

§ Integrate improvements, Decide best SAP enablers, Define organizational consequences. § Lead the Integration Architecture, Interface Architecture, Data Migration and Testing. § Exploit ADM Tools to provide Estimation on Integration. Closely work with Client PM Team Member to provide PI Estimation using ADM tools. Client: HelathCare and Insurance-CSI, Cincinnati, OH. Industry - Manufacturing Duration: March’08 to April’08.

Role: SAP Net weaver - Support Road Map/Blue Print. Description: The client is the world’s leading designer, manufacturer and distributor of prescription frames and sunglasses in the premium and luxury segments. Its distribution network covers all of the world’s key markets both wholesale and retail. In the retail business, the Group enjoys the largest and most efficient network in the industry, with approximately 5,500 sun and optical stores worldwide.