Saturday, October 15, 2011

0 Transaction Codes

Sales Order:
VA01 – Create Sales Order
VA02 – Change Sales Order
VA03 – Display Sales Order
Inquiry:
VA11 – Create Inquiry
VA12 – Change Inquiry
VA13 – Display Inquiry
Quotation:
VA21 – Quotation Creation
VA22- Change Quotation
VA23 – Display Quotation
Delivery:
VL01N – Create Delivery Document
VL02N – Change Delivery Document
VL03N – Display Delivery Document
Billing:
VF01 – Create Billing Document
VF02 – Change Billing Document
VF03- Display Billing Document
Material:
MM01 – Create Material
MM02 – Change Material
MM03 – Display Material
Purchase Requisition :
ME51N – Create Purchase Requisition
ME52N – Change Purchase Requisition
ME53N – Display Purchase Requisition
Request For Quotation : (RFQ)
ME41 – RFQ Creation
ME42 – Change RFQ
ME43 – Display RFQ
Purchase Order:
ME21N – Create Purchase Order
ME22N – Change Purchase Order
ME23N - Display Purchase Order
Vendor Evaluation:
ME61 – Create Vendor Evaluation
ME62 – Change Vendor Evaluation
ME63 – Display Vendor Evaluation
Material Document:
MB01 – Create Material Document (Goods Receipt for purchase order)
MB02 - Change Material Document
MB03 - Display Material Document

Vendor:
XK01 – Create Vendor
XK02 – Change Vendor
XK03 – Display Vendor
Vendor creation for MM Module Wise:
MK01 – Create Vendor
MK02 – Change Vendor
MK03 – Display Vendor
Vendor creation for FI Module Wise:
FK01 – Create Vendor
FK02 – Change Vendor
FK03 – Display Vendor
Customer :
XD01 – Create Customer
XD02 – Change Customer
Xd03 – Display Customer
Customer creation for SD Module Wise:
VD01 – Create Customer
VD02 – Change Customer
VD03 – Display Customer
Customer creation for FI Module Wise:
FD01 – Create Customer
FD02 – Change Customer
FD03 – Display Customer
Cost:
KS01 – Create Cost Center
KS02 – Change Cost Center
KS03 – Display Cost Center
Profit:
KE51 –Create Profit Center
KE52 – Change Profit Center
KE53 – Display Profit Center
Accounting:
FB01 – Create Accounting Document Number
FB02 – Change Accounting Document Number
FB03 – display Accounting Document Number
Banking:
FI01 – Create Bank Details
FI02 – Change Bank Details
FI03 – Display Bank Details
BOM:
CS01 – Create BOM
CS02 – Change BOM
CS03 – Display BOM


Recipe:
C201 – Create Recipe
C202 – Change Recipe
C203 – Display Recipe
Batch:
MSC1N – Create Batch
MSC2N – Change Batch
MSC3N – Display Batch
Process Order:
COR1 – Create Process Order
COR2 – Change Process Order
COR3 – Display Process Order
Production Order:
CO01 – Create Production Order
CO02 – Change Production Order
CO03 – Display Production Order

0 LINK BETWEEN THE SD AND MM FLOW


1.First The customer prepare the purchase requisition with required goods and he send to request for quotation(RFQ) to different vendors.
2. Once we receive the quotation from the customer then as a vendor we need to check whether we can deliver the goods with customer conditions or not
3. : Once we finish the inquiry then as a vendor we need prepare the quotation
4.Once we prepare the quotation as a vendor we need to send quotation to the particular customer

5.Once we receive the quotations from different vendors as a customer we analysis all the quotations and finally we select one vendor
6.After vendor evaluation as a customer we need to raise the purchase order
7. Once we receive the purchase order from customer then as a vendor we need to raise the sales order.
8.while raising sales order we should know the partner functions
Sold-To-Party – who as raised the purchase order
Ship-To-Party – where we need to deliver the goods
Bill-to-party – to whom we have to give the bill
Payer – who is going to pay the money
9. After raising the sales order as a vendor we need to deliver the goods
10. Deliver the goods
11.Here we receive the goods with goods receipt as a customer we need to analysis the goods receipt
12.As a vendor we need to prepare the bills
13. While delivering the goods we need to send the billing document
14.Once we receive the goods and bills from the vendor as a customer we need to verify all the good . if there is any problem in the goods then they inform to vendor.
15.If we receive all the goods then as a customer we need to inform the finance guy
16. Once we deliver the goods with billing vendor finance guy will interact with the customer finance guy .
17.Finally the finance guys interact for the finance settlements

0 MM FLOW

Purchase Requisition: First The customer prepare the purchase requisition with required goods
Request For Quotation : As a customer we need to send RFQ to different vendors
Vendor Evaluation : Once we receive the quotations from different vendors as a customer we analysis all the quotations and finally we select one vendor
Purchase Order : After vendor evaluation as a customer we need to raise the purchase order

Goods Receipt: .Here we receive the goods with goods receipt as a customer we need to analysis the goods receipt
Invoice Verification: Once we receive the goods and bills from the vendor as a customer we need to verify all the good . if there is any problem in the goods then the customer inform to vendor.
Finance : Once we receive the goods with billing customer finance guy will interact with the vendor finance guy for finance settlements

Friday, October 14, 2011

0 SD FLOW


SD FLOW:




Inquiry: (VA11) Once we receive the quotation from the customer then as a vendor we need to check whether we can deliver the goods with customer conditions or not

Quotation :(VA21) Once we finish the inquiry then as a vendor we need to send quotation to the particular customer

Sales Order: (VA01) Once we receive the purchase order from customer then as a vendor we need to raise the sales order, while raising sales order we should know the partner functions
Sold-To-Party – who as raised the purchase order
Ship-To-Party – where we need to deliver the goods
Bill-to-party – to whom we have to give the bill
Payer – who is going to pay the money

Goods Delivery : (VL01N) After raising the sales order as a vendor we need to deliver the goods

Billing:(VF01) While delivering the goods we need to send the billing document

Finance: Once we deliver the goods with billing vendor finance guy will interact with the customer finance guy for finance settlements

2 Object Delivery Methodologies:

Object Delivery Methodologies:

1. Function people are designing the functional document.
2. Once the functional specification is ready then they are placing functional specification in share folder or particular tool.
3. Once they place the functional specification share folder then immediately the project lead or team receiving a mail.
4. As a team lead once receive the mail then as per the resource availability he is going to assign to some particular employee.
5. As a technical consultant once we receive the object TS or TD then as a technical consultant we need to start the analysis.
6. While analyzing the object if we found any gaps Issues then we need to maintain all the gaps in issue log sheet issue log sheet is a template.
7. Once the analysis is done then we need to communicate with the functional owner for the above gaps.
8. For getting the solution for the above gaps we need to raise the request for the FS walk through.
9. Once all issues are clarify then as a senior technical consultant we need to design the technical specification or technical document.
10. Once we finish the TS design then as a design we need to do the self review and send for peer review.
11. Once finish the self and peer reviews then we need to send TS of sign off.
12. Once TS is sign off then as a TS designing we need to start the development or we are assigning to some junior consultant.
13. While doing the coding we need to follow the client naming and coding standards.
14. While doing the coding we need to apply the optimization techniques and modularization techniques and Inline comments.
15. Once we finish the coding as a developer we need to prepare the code review check list.
16. Once you design the code review check list as a developer you need to do the self review and send for peer review.
17. As a developer we need to prepare UTP (Unit Test Plane) and UTR (Unit Test Report).
18. Once you finish the UTP and UTR design then as a developer you need to do the self review and sent of peer review.
19. Once the above all peer reviews are sign-off then as a developer we need to inform to the team lead with program name and transport request number.

Thursday, October 13, 2011

0 SAP-R/3 Architecture:

SAP-R/3 architecture is a 3 tire architecture
Here we have 3 systems
1.Database Server
2.Application Server
3.Presentation Server










Database Server:
Is a place where we store all the data
One data base server we have so many application servers
Application Server:
1.Application server act as a mediator in between the presentation and database servers
2.It is temporary memory area
One application server we have so many presentation servers
Presentation Server:
Presentation server means client system(end user)

0 Introduction to SAP

SAP was founded in 1972 in walldorf , Germany. It stands for System Application Product In Data Processing over the year it grows and evolved to becomes the world premier provider for client/server business solutions for which it is so well today
History of SAP:
1. In between 1970-1972 5 IBM formal employs released the R1(Real Data process) version but it’s works only on UNIX operating system

2. In the year 1982 R2 version was released but it support main frame system only(IBM Main frames only)
3. In the year 1992 R3 version was released it is the platform independent it will work on any operating system.
In SAP we have 3 areas like
1.Basis
2.Functional
3.Technical
Basis : (we have 2 areas)
1.Admin
2.Security
they provide the security and authorization
Functional:
Function peoples are communicate with the client for the requirement
In the function we have more than 48 areas
Some of the function areas are
1.PP(Production Planning)
2.MM(Material Management)
3.FI(Finance Accounting)
4.SD(Sales and distribution)
5.PS(project System)
6.CO(Controlling)
7.HR(Human Resources)
8.PM(Plant maintenance)
9.QM(Quality Management)
Technical:
Technical peoples are design the code as for the client requirement
They are may technical areas like
ABAP, BI, BO, XI,PI,WEBDYNPRO and so on.

1.
1.

Tuesday, October 11, 2011

0 List of Transaction codes used in abap

transaction code:
transaction code is the collection of the screens where we can develop our object, sap provided there own transaction code for each and every concept those are called standard transaction codes .
if you want we can provide our own transaction code those are called custom transaction codes

List of Transaction codes used in abap:


SE01 – Transport Organizer (Extended view)

SE03 – Transport Organizer Tools

SE09 – Transport Organizer

SE10 – Transport Organizer

SE11 - ABAP/4 Dictionary

SE12 - ABAP/4 Dictionary Display

SE13 –Dictionary Technical Settings

SE14 - ABAP/4 Dictionary: Database Utility

SE15 – Object Navigator

SE16 – Data Browser : Initial Screen

SE16N - General Table Display

SE17 – General Table Display

SE18 – BADI Builder :Initial Screen For Definitions

SE19 - BADI Builder : Initial Screen For Implementations

SE21 – Package Builder: Initial Screen

SE24 – Class Builder : Initial Screen

SE29 – Application Packets

SE30 – Run Time Analysis : Initial Screen

SE32 – SAP

SE33 – Context Builder : Initial Screen

SE35 – Maintain Dialog Modules

SE36 – Logical Database Builder

SE37 – Function Builder : Initial Screen

SE38 –ABAP Editor : Initial Screen

SE39 – ABAP Splitscreen Editor : Initial Screen

SE41 – Menu Painter : Initial Screen

SE43 – Area Menu Maintenance

SE51 - Screen Painter: Initial Screen

SE54 – Generate table Maintenance Dialog : Initial Table/ View Screen

SE55 - Generate table Maintenance Dialog : Initial Table/ View Screen

SE56 - Generate table Maintenance Dialog : Initial Table/ View Screen

SE57 - Generate table Maintenance Dialog : Initial Table/ View Screen

SE61 – Document Maintenance :

SE62 –Short Text Conversion – Activation

SE63 –Translation

SE71 – Form Painter

SE72 – Style : Request

SE73 – SAP Script Font Maintenance : Initial Screen

SE74 – SAP Script Format Conversion

SE75 – SAP Script Settings

SE76 – SAP Script From Translation

SE77 – SAP Script Style Conversion

SE78 –Administration For Graphics

SE80 – Object Navigator

SE81&SE82 - Application Hierarchy : Display

SE83 –Display Reuse Library

SE84 – Object Navigator

SE85 – Object Navigator

SE90 – Object Navigator

SE91 –Message Maintenance : Initial Screen

SE92 - Maintain system log messages

SE93 –Transaction Code Creation

SM12 - Lock table entries (unlock locked tables)

SM04 – User List

SM30 - Maintain Table Views : Initial Screen

SM31 - Maintain Table Views

SM32 –Table Maintenance

SM35 – Batch Input : Session Overview

SM36 –Define Background Job

SM37 –Simple Job Selection

SM50 – Process Over View

SM51 – SAP Servers

ST01 – System Trace

ST02 – Tune Summary

ST05 – SQL Trace

ST22 – ABAP Run Time Error

WEDI - EDI Menu. IDOC and EDI base.

WE02 – IDOC List

WE07 - IDOC Statistics

SPRO – Customizing : Execute Project

SU01 – Display User Name

SMOD – SAP enhancements

COMD – Project Management For SAP Enhancements

SHDB – Recording Overview

SMARTFORMS – For Smart Form Creation

NACE –Conditions For Output Control

LSMW –Legacy System Migration Workbench

SP01 – Output Control: Spool Request Selection Screen

SP02 – Output Control : Spool Request List

SO10 – Standard Text
AL11 - Application server path
 

SAP-ABAP Copyright © 2011 - |- Template created by Vishnu - |- Powered by Blogger Templates