functional & technical spec.

[Former Member]

Hello to all,

I am new in ABAP. I am learning some ABAP /HR terms .

1] what is one-life cycle experience.

2] how to built technical spec for payroll.

3] bug fixes, SLA ,PRA module ,EBPmodule.

[Former Member]

Rani,

A SDLC (Software Development Life Cycle) contains different steps generally.

1. Requirements gathering.

2. Design/Blue Print

3. Development and Testing (Testing will be of different types again like unit testing, integration test, regression test, UAT etc)

4. Support.

Hope this is help ful.

Thanks,

Naren

[Former Member]

Enterprise Buyer Professional(EBP) module

Purpose

You implement Enterprise Buyer professional edition if you want to use an Internet solution to map the complete procurement process for both direct and indirect materials and services. The process begins with the creation of a shopping cart and ends with the entry of the invoice.

Advantages

Enterprise Buyer shortens the procurement process cycle time and saves your company money. Moving routine purchasing tasks to employees in the user departments reduces the purchasing department’s workload and allows buyers to focus on strategic tasks such as negotiating agreements and analyzing vendors.

Integration

Enterprise Buyer is a separate SAP System that you can use in a heterogeneous system environment. The R/3 System or other ERP (Enterprise Resource Planning) systems can belong to a system environment. The components Financial Accounting and Controlling must exist in the ERP system.

Check this link for more..

http://help.sap.com/saphelp_crm30/helpdata/en/86/f41136def19d0ae10000009b38f839/frameset.htm

Enterprise Service Level Agreement (SLA)

Service Level Agreements (SLA) define the attributes for service products (for example, maintenance, Hotline) that have been agreed upon with the customer in service contracts. The SLA confirms different parameters, such as response time, availability time and system availability.

The SLA effects the pricing for each contract item and the date calculation in the service order, to which the relevant contract items refer.

Check this link for more..

http://help.sap.com/SAPHELP_NW04S/helpdata/EN/43/23fc16cad10d23e10000000a1553f7/content.htm

Production Revenue Accounting (PRA) module

In PRA, you create owners as master records to represent owners in divisions of interest (DOIs), who will receive revenue in subsequent revenue processes in PRA. An owner master record in PRA consists of a business associate (BA) record linked to a vendor record from SAP Core.

In order to create an owner, it is thus necessary to create a business associate, and link the BA to a vendor, or create a BA and also create a vendor in Core. Every owner that you create or use in PRA has to be linked to a business associate record and a vendor.

The main reason that you use vendors from Core is that when you set up an owner in PRA, you will need some of the attributes attached to that vendor in Core, which will not exist in Ownership. So for the overall attributes of the owner, some come from the Core vendor attributes, and some you set up in the BA record when you create it here. The BA type identifies the type of owner (working interest, royalty interest, etc.) that you are creating.

CHeck this link.

http://help.sap.com/saphelp_oil472/helpdata/en/ec/9d2c3adcc8431be10000000a114084/frameset.htm

Also Check this PDF doc.

http://www.sap.com/industries/oil-gas/pdf/01_Production_and_Revenue_Accounting_e.pdf

[Former Member]

Life Cycle:

ASAP Methodology:

Project Preparation:

The first step in ASAP is Project Preparation. In this step the Functional Consultant will analyse the business process and define the system for SAP and will give the time line for the project. The Manpower required and the budgets are also considered in this step.

Blue Print Preparation:

This is second step in ASAP Methodology. In this step the Project Preparation scenarios are finalised. A out line of the Project is given in this step.

Realisation:

In this step actual development is taken place. The ABAPer is responsible for this step.

Testing:

In this step the development done by the abaper is being tested. This is the area where the Unit Test Document is prepared (i.e. Positive Testing and Negative Testing).

GO live and Support:

This is the final stage where the project is running in the live environment. In this step the bugs if any that are found in the go live procedure are fixed and the project will be considered as support project.

[Former Member]

ASAP methodology is used for SAP implementation.

AcceleratedSAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3. Along with that, AcceleratedSAP contains a multitude of tools, accelerators and useful information to assist all team members in implementing R/3. Quality checks are incorporated at the end of each phase to easily monitor deliverables and critical success factors. ASAP is delivered as a PC-based package, so that - if required - an implementation project can begin prior to having an R/3 System installed.

AcceleratedSAP (ASAP): A comprehensive solution for the introduction of the R/3 System in your enterprise. ASAP and most of its tools can be used independently of an R/3 installation.

The ASAP methodology adheres to a specific road map that addresses the following five general phases:

1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and the project work environment is set up;

2. Blueprint, i n which the business processes are defined and the business blueprint document is designed;

3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and data requirements for migration are defined;

4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained; and

5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and post-implementation support is provided.