Tue. Jul 5th, 2022

ABAP or ABAP OO development are very crucial in addressing any solution holes, RICEFs or custom development on any SAP project. I think it is very important to know a lot of different programming aspects during an SAP execution project and follow certain guidelines that can make an SAP ABAP professional very successful in your career.

What is SAP? Why do we need ERP? Beginner Tutorial - YouTube

The first part of any ABAP development project start out with meeting the end users or business experts and understand the business requirements that need to be implemented in the SAP system during the realization phase. A best approach is to conduct workshops to assemble all the business requirements. Make sure that if any SAP function consultants may take place than they are in the meetings as well. After all the business requirements are collected payroll system hong kong, the SAP functional consultant or business expert will write reveal functional specification. Review the functional specification prior to the document has every piece of information, different business scenarios and expected goals clearly defined. A well defined functional specification should contain UML diagrams and test case scenarios. It is important to have an official signoff on the functional specification before continuing with design and development.

In ideal case, your SAP Project Lead or ABAP Development Manager should have created a programming standards and guidelines document. Review this document so you follow the naming promotions for function adventures, classes, book objects, software components, name spaces and proxies (if using SAP XI or PI), program input/output guidelines, etc just to name a few. Following the guideline for the project helps maintain a regular html coding approach and also helps other functional and technical analysts to see and debug your code. ABAP objects naming gets started with Unces if it will be moved to SAP production system and Ymca if it will not be moved into the production system.

The test case documents are published by the business experts or functional SAP consultants in most SAP execution projects. But on some SAP execution projects a programmer may be asked to write test cases. Before writing a test case review the functional specification document thoroughly and review the written test case with the business users or functional consultants. Get a sign-off as mentioned in most steps in this article. As an ABAP Development Manager for a variety of SAP execution projects, my goal has been to keep my team motivated and always cover the team against any change of scope on the development tasks. Having a sign-off at each phase of a SAP custom development or enhancement tasks always helps the SAP execution team and project management team keep in synchronize which is a vital to complete the SAP execution in time and budget.

See the functional specification and list all the development objects that has to be needed to implement the mandatory functionality in the SAP system. First step is to draw a flowchart and review with technical and business experts. The technical design document ought to include a technical overview, list of new database objects, ABAP objects that can be reused, a data model and class diagram (if using ABAP OO classes). It is highly recommended to have a rough prototype in the sandbox system (Development system if no SAP sandbox system is available) if the development being done is complex or if the end deliverable is not well defined. You should then review your prototype with functional experts and business users. Make sure that the ABAP Development team lead or manager signs off on the prototype. If effort required to complete the ABAP programming task is not presented and approved by the senior project management then this would be a good time to get the development estimate and timeline approved.

During this step you will be creating development objects and implementing the code in the SAP development system. Before you begin, if prototype was done in the sandbox system then analyze the prototype and design specification. Remember that quality and reusability of existing ABAP objects are more important than strictly following the design specification. Determine which existing book objects can be reused for this topic. If new book objects or classes needs to be created then ensure that these objects can be extended and reused for other development tasks. It may require extra effort to develop objects that are reusable and flexible. This one time effort for building reusable ABAP objects over the course of a development project can potentially save a lot of work for programming similar objects that could otherwise utilize already built objects. Review your approach with an SAP technical team lead or a development manager on your project before deviating from the technical design specification and implementing your own ideas. If you are involved in SAP XI (now Process Integration) related tasks or creating enterprise services then this is the best area enabling you to recycle existing objects. Review the message types that already exist within your SAP business unit and see if any existing messages can be extended with new fields. Review with the team lead whether the communication should be synchronous or asynchronous before you generate proxies.

By admin

Leave a Reply

Your email address will not be published.