EXITS (ENHANCEMENT)

The enhancement concept allows you to add your own functionality to SAP's standard business applications without having to modify the original applications. To modify the standard SAP behavior as per customer requirements, we can use enhancement framework.

There are different ways to implement custom functionality in the SAP standard code. ex: User exits, customer exits, BADI etc.

User exits
These are implemented in the form of subroutines and hence are also known as FORM EXITs. The user exits are generally collected in includes and attached to the standard program by the SAP.
User exits are a type of system enhancement that was originally developed for the R/3 SD (Sales and distribution) module. User-exits are empty subroutines that SAP Developers have provided for you.
You can fill them with your own source code. Technically this is a modification.

Customer exits
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang
your own add-on functionality onto these hooks.
Customer exits are nothing but a include in customer name space will be provided in the function module which starts with CALL CUSTOMER. You can fill them with your own source code. Technically this
is an enhancement. User exits generally refer to SD module while customer exits refer to all modules like MM, SD, PP, FICO etc.
Advantage:
- They do not affect standard SAP source code
- They do not affect software updates
Disadvantage:
- Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System.
Types of Customer Exits
1. Function Module exits
2. Screen exits
3. Menu exits

1. Function Module exits
Function module exits are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly
in the function module, but in the include that is implemented in the function module.
Format: CALL CUSTOMER-FUNCTION '910'
2. Screen Exits:
Allow customer to add fields to a screen via a sub screen in an SAP program. The sub screen is called within the standard screen's flow logic.
Format: CALL CUSTOMER-SUBSCREEN CUSTSCR1
3. Menu exits:
Menu exits allow you to add your own functionality to menus. Menu exits are implemented by SAP and are reserved menu entries in the GUI interface. The developer can add his/her own text and logic for
the menu.
Function codes for menu exits all start with "+".
Format: +CUS (additional item in GUI status)

PURPOSE OF DEFINING ENHANCEMENT CATEGORY

We define an enhancement category for the table to enhance the structures and tables created in ABAP Dictionary.

PURPOSE OF RQUEST ID

The request id is a general purpose request identifier used to group several assignments into one request.the request id can e used for instance when integrating with SAP bussiness object access control

PURPOSE OF TABLE MAINTENANCE GENERATOR

A Database table can be manipulated by a program or through a maintenance view.
the main purpose of table maintenance  view for tables so that the table entries can be created , modified or deleted.

ADVANTAGE AND DISADVANTAGE OF SAP SYSTEM

ADVANTAGES OF SAP SYSTEM

• SAP sytem reduces the possibilty of redundancy errors.
• SAP system provides flexibility.
• SAP System is real Time.
• Integration can be the highest benefit of them.
• There is only One Single Comprehensive Database.

DISADVANTAGES OF SAP SYSTEM

• SAP is very Expensive and time consuming for implementation.
• It requires a company to implement changes.
• very complex.

ENTERPRIZE RESOURCE PLANNING AND ITS ADVANTAGES AND DISADVANTAGES.

ENTERPRIZE RESOURSE PLANNING
A system that automates and integrates all modules of bussiness areas is known as erp system or simply erp.
A ERP system is used to integrate several data sources and processes such as manufacturing , control and distribution of goods in an organization .
A ERP system is primarily module based which implies that it consist of various modular software applications or modules.
these modules of an ERP system are linked to each other by a centralized database.

ADVANTAGES OF AN ERP SYSTEM

•  ERP System helps synchonize data & keep it updated.
• ERP system improves the performance and efficiency of bussiness processing .
• ERP system provides visibility.
• improved customer service and satisfaction.

DISADVANTAGES OF AN ERP SYSTEM

• Customization of the ERP system is limited .
• Once a system is establised , switching costs are very high.

DATA CLASS AND ITS TYPE

The Data class determines in which table space the table is stored when it is created in
the database.

Types of data classes
APPL0 - Master data (data frequently accessed but rarely updated).
APPL1 - Transaction data (data that is changed frequently).
APPL2 - Organizational data (customizing data that is entered when system is
configured and then rarely changed).

The other two types are:
- USR
- USR1 – Intended for customer’s own developments.

DIFFERENCE BETWEEN LSMW AND BDC TOOL

BDC is mainly for any customized application where as lsmw is generally for normal SAP application.
BDC is SAP to SAP communication tool where as Lsmw is a non SAP to SAP Communication Tool.

IMPORTANT TABLES

     1 Customising
1.1 General settings
1.1.1 Countries  
T005   Countries

1.1.2 Currency  
TCURC   Currency codes
TCURR   Wisselkoersen
 TCURT   Currency name
 TCURX   Decimal places for currencies.

1.1.3 Unit of measure  
T006   Units of measure

1.1.4 Calendar functions
 T247   Month names
TFACD   Factory calendar definition
 T015M   Month names
TTZZ   Time zones
 TTZD   Summer time rules
  TTZDF   Summer time rules (fixed annual dates)
 TTZDV   Summer time rules (variable dates)
 TTZDT   Summer time rules texts
 TTZ5   Assign Time Tones to Countries
 TTZ5S   Assign time zones to regions

1.2 Enterprise structure
1.2.1 Definition
 FI T880   Company
T001   Company code CO '
TKA01   Controlling area LO
 T001W   Plant / sales organisation
 T499S   Locations TSPA   Division SD
TVKO   Sales organisation / company code
TVTW   Distribution channel
TVBUR   Sales office
TVKBT   Sales office text
TVKGR   Sales group

                              
TVGRT   Sales group text
T171T   Sales district text
MM T001L   Storage locations
T024E   Purchasing organization
T3001   Warehouse number
TVST   Shipping point
TVLA   Loading point
 TTDS   Transportation

                              
1.2.2 Assignment CO
TKA02   Assign company code to controlling area LO
 T001K   Assign plant (valuation area) to company code
SD TVKO   Sales organisation / company code
TVKOV   Distribution channel / sales organisation
TVKOS   Division to sales organization
TVTA   Sales aria
TVKBZ   Sales office to sales area
TVBVK   Sales group to sales office
TVKWZ  Plants to sales organization MM
 T024E   Purchasing organization / company code
T024W   Plant to Purchase organization
T001K   Link plant ( = valuation area) / company code
TVSWZ   Shipping point to plant  T320   Assignment MM Storage Location to WM Warehouse

1.3 Financial accounting
1.3.1 Company code
T004   Chart of accounts
T077S   Account group (g/l accounts)
 T009   Fiscal year variants
T880   Global company data
T014   Credit control area

1.3.2 Fi document
T010O   Posting period variant
T010P   Posting Period Variant Names
 T001B   Permitted Posting Periods
 T003   Document types
T012   House banks

1.4 Not categorized
 T007a   Tax keys
T134   Material types
 T179   Materials: Product Hierarchies
 T179T   Materials: Product hierarchies: Texts
TJ02T   Status text  TINC   Customer incoterms
 TVFK   Billing doc types
T390   PM: Shop papers for print control

                              
2 Basic data / administration
2.1 Workbench related tables
2.1.1 Data dictionary tables
DD02L   Tables in SAP
 DD02T   Tables description
 DD03L   Field names in SAP
  DD03T   Field description in SAP

2.1.2 Workbench
 TADIR   Directory of R/3 Repository Objects
TRDIR   System table TRDIR
TFDIR   Function Module
TLIBG   Person responsible for function class
TLIBT   Function Group Short Texts
 TFTIT   Function Module Short Text
TSTC   Transaction codes in SAP
 TSTCT   Transaction codes texts
T100   Message text (vb e000)
VARID   Variant data
 D020T   Screen texts
TDEVC   Development class
 TDEVCT  Texts for development classes

2.2 Administration
2.2.1 User administration
 USR01   User master
 USR02   Logon data
USR03   User address data
 USR04   User master authorizations
 USR11   User Master Texts for Profiles (USR10)
UST12   User master: Authorizations
USR12   User master authorization values
 USR13   Short Texts for Authorizations
 USR40   Prohibited passwords
 TOBJ   Objects TOBC   Authorization Object Classes TPRPROF  Profile Name for Activity Group DEVACCESS  Table for development user
  
                              
2.2.2 Batch input queue
APQD   DATA DEFINITION Queue
APQI   Queue info definition

2.2.3 Job processing
TBTCO   Job status overview table
TBTCP   Batch job step overview

2.2.4 Spool
 TSP02   Spool: Print requests
2.2.5 Runtime errors
SNAP   Runtime errors

2.2.6 Message control
 TNAPR   Processing programs for output
NAST   Message status
 NACH   Printer determination

2.2.7 EDI
EDIDC   Control record
 EDIDD   Data record
 EDID2   Data record 3.0 Version
EDIDS   EDI status record
 EDPAR   Convert External <  > Internal Partner Number
 EDPVW  EDI partner types
 EDPI1   EDI partner profile inbound  EDPO1/2/3  EDI partner profile outbound

2.2.8 Change documents
CDHDR   Change document header
 CDPOS   Change document positioned
JCDS   Change Documents for System/User Statuses (Table JEST)

2.2.9 Reporting tree table
SERPTREE  Reporting: tree structure

2.2.10 LIS structure/control tables
TMC4   Global Control Elements: LIS Info Structure

                                
3 MASTER DATA:
3.1 Material master:
MARA   Material master
 MAKT     Material text
MARC   Material per plant / stock
MVKE   Material master, sales data
 MARD   Storage location / stock
 MSKA   Sales order stock
MSPR   Project stock
MARM   Units of measure
 MEAN   International article number
  PGMI   Planning material  
PROP   Forecast parameters
MAPR   Link MARC <=> PROP
MBEW   Material valuation
MVER   Material consumption
 MLGN   Material / Warehouse number
 MLGT   Material / Storage type
MPRP   Forecast profiles
 MDTB   MRP table
MDKP   Header data for MRP document
MLAN   Tax data material master
 MTQSS   Material master view: QM

3.1.1 Basic data text (sap script)
 STXB   SAP script: Texts in non-SAP script format
 STXH   STXD SAP script text file header
STXL   STXD SAP script text file lines

3.1.2 Batches  
 MCHA   Batches
MCH1   Batches
MCHB   Stock: batches

3.2 Customer master data
  KNA1   Customer master
 KNB1   Customer / company
 KNVV   Customer sales data
KNBK   Bank details
KNVH   Customer hierarchy
 KNVP   Customer partners
    
                              
                  
 KNVS   Shipment data for customer
 KNVK   Contact persons
KNVI   Customer master tax indicator

3.3 Vendor
  LFA1   Vendor master
LFB1   Vendor per company code
LFB5   Vendor dunning data
LFM1   Purchasing organization data
LFM2   Purchasing data
 LFBK   Bank details

3.4 Customer – material info record
KNMT   Customer material info record

3.5 Bank data
BNKA   Master bank data
    
                              
4 Characteristics:
4.1 Characteristics:
CABN    Characteristics ( o.a. batch/vendor)
 CABNT    Characteristics description
 CAWN    Characteristics  ( o.a. material)
 CAWNT   Characteristics description
 AUSP    Characteristic Values

4.2 Class types and objects :      
 TCLAO                            Several class types for object
TCLA    Class types ( vb. lfa1 => v10 en 010)
TCLAT    Class type text  TCLT    Classifiable objects
TCLC    Classification status

4.3 Links:
 INOB    Link between Internal Number and Object
KLAH     Class header data  
 KSSK    Allocation Table: Object (vb.matnr) to Class  
 KSML    Characteristics for a class (internal number)
    
                              
5 FI/CO  :
5.1 FI :
5.1.1 Master data
SKA1   Accounts
BNKA           Bank master record

5.1.2 Accounting documents // indices
 BKPF   Accounting documents
 BSEG   item level
 BSID           Accounting: Secondary index for customers        
   BSIK           Accounting: Secondary index for vendors            
  BSIM           Secondary Index, Documents for Material            
 BSIP          Index for vendor validation of double documents    
 BSIS           Accounting: Secondary index for G/L accounts
 BSAD           Accounting: Index for customers (cleared items)    
BSAK           Accounting: Index for vendors (cleared items)    
 BSAS          Accounting: Index for G/L accounts (cleared items)

5.1.3 Payment run REGUH  Settlement data from payment program
REGUP   Processed items from payment program



5.2 CO : TKA01   Controlling areas
TKA02   Controlling area assignment
KEKO   Product-costing header
 KEPH   Cost components for cost of goods manuf.
KALO   Costing objects
 KANZ   Sales order items - costing objects

5.2.1 Cost center master data
 CSKS   Cost Center Master Data
 CSKT   Cost center texts
CRCO   Assignment of Work Center to Cost Center

5.2.2 Cost center accounting
COSP   CO Object: Cost Totals for External Postings
 COEP   CO Object: Line Items (by Period) .
COBK   CO Object: Document header
 COST   CO Object: Price Totals
 
                              
6 Sales and Distribution (SD) :

 VBFA   Document flow (alg.)
 VTFA   Flow shipping documents

6.1 Sales order :
 VBAK   Header data
VBAP   Item data
 VBPA   Partners in sales order
 VBKD   Sales district data
VBEP   Data related to line items, delivery lines

6.2 Billing document :
VBRK   header data
 VBRP   Item data

6.3 Shipping :
 VTTK   Shipment header
 VTTP   Shipment item
 VTTS   Stage in transport
 VTSP   Stage in transport per shipment item
VTPA   Shipment partners
VEKP   Handling Unit - Header Table
VEPO   Packing: Handling Unit Item (Contents)

6.4 Delivery :
LIKP   Delivery header
LIPS   Delivery item

6.5 Pricing :
 KONH    Conditions header
KONP   Conditions items
KONV   Procedure ( billing doc or sales order)
 KOND

6.6 contracts :
 VEDA   Contract data

                              
7 Material Management (MM) :
7.1 Material document
MKPF   material document
MSEG   material document (item level)

7.2 Purchasing

EKKO   Purchase document
EKPO   Purchase document (item level)
 EKPV   Shipping-Specific Data on Stock Tfr. for Purch. Doc. Item
EKET   Delivery schedule
 VETVG   Delivery Due Index for Stock Transfer
 EKES   Order Acceptance/Fulfillment Confirmations
  EKKN   Account assignment in purchasing
EKAN   Vendor address purchasing
EKPA   Partner functions
EIPO   Item export / import data
EINA   Purchase info record (main data)
 EINE   Purchase info record (organisational data)
 EORD   Source list  EBAN   Purchase requisition
 EBKN   Purchase Requisition Account Assignment
      
                              
8 Warehouse Management (WM) :
8.1 Transfer requirement

LTBK   Transfer requirement - header
 LTBP   Transfer requirement - item

8.2 Transfer order
 LTAK   Transfer order - header
 LTAP   Transfer order - item 8.3 Master data - stock positions
LQUA   Quants

8.4 Inventory documents in
WM  LINK   Inventory document header
LINP   Inventory document item
 LINV   Inventory data per quant  
    
                              
9 Quality Management (QM) :  
9.1 Inspection lot / info record

QALS   Inspection lot record
QAMB   Link inspection lot - material document
QAVE   Inspection usage decision  
QDPS   Inspection stages
QMAT   Inspection type - material parameters
QINF   Inspection info record (vendor - material)
QDQL   Quality level  QDPS   Inspection stages

9.2 Quality notification

TQ80   Notification types
QMEL   Quality notification
QMFE   Quality notification – items
QMUR   Quality notification – causes
QMSM   Quality notification – tasks
QMMA   Quality notification – activities
QMIH   Quality message - maintenance data excerpt

9.3 Certificate profile

 QCVMT  Certificate profile characteristic level: texts
QCVM   Certificate profile characteristic level
 QCVK   Certificate profile header
      
                              
10 Production Planning (PP)
10.1 Work center

 CRHH    Work center hierarchy
CRHS    Hierarchy structure
CRHD    Work center header
CRTX    Text for the Work Center or Production Resource/Tool
CRCO    Assignment of Work Center to Cost Center
KAKO    Capacity Header Segment
CRCA    Work Center Capacity Allocation
TC24    Person responsible for the workcenter

10.2 Routings/operations

MAPL    Allocation of task lists to materials
PLAS    Task list - selection of operations/activities
PLFH    Task list - production resources/tools
PLFL    Task list - sequences
PLKO    Task list - header
PLKZ    Task list: main header
PLPH    Phases / suboperations
PLPO    Task list operation / activity
PLPR    Log collector for tasklists
PLMZ    Allocation of BOM - items to operations

10.3 Bill of material
 
STKO    BOM - header  STPO  
BOM - item  STAS  
BOMs - Item Selection
STPN    BOMs - follow-up control  STPU    BOM - sub-item
 STZU    Permanent BOM data  PLMZ    Allocation of BOM - items to operations  MAST    Material to BOM link  KDST    Sales order to BOM link

10.4 Production orders

AUFK    Production order headers
AFIH    Maintenance order header
AUFM    Goods movement for prod. order
 AFKO    Order header data PP orders
      
                              
 AFPO    Order item
RESB    Order componenten    
AFVC    Order operations
AFVV    Quantities/dates/values in the operation
AFVU    User fields of the operation
AFFL    Work order sequence
AFFH    PRT assignment data for the work order(routing)
JSTO    Status profile
JEST    Object status
AFRU    Order completion confirmations            PRT’s voor production orders
AFFH    PRT assignment data for the work order
CRVD_A   Link of PRT to Document
DRAW    Document Info Record
TDWA    Document Types  '
TDWD    Data Carrier/Network Nodes
 TDWE    Data Carrier Type

10.5 Planned orders

PLAF    Planned orders

10.6 KANBAN

PKPS    Kanban identification, control cycle
 PKHD    Kanban control cycle (header data)
PKER    Error log for Kanban containers

10.7 Reservations

 RESB    Material reservations
RKPF    header

10.8 Capacity planning

KBKO    Header record for capacity requirements
 KBED    Capacity requirements records
KBEZ    Add. data for table KBED (for indiv. capacities/splits)

10.9 Planned independent requirements

 PBIM    Independent requirements for material
PBED    Independent requirement data
PBHI    Independent requirement history
PBIV    Independent requirement index
PBIC    Independent requirement index for customer req.      
                              
11 Project system (PS)
11.1 Basic data
PRHI   Work Breakdown Structure, Edges (Hierarchy Pointer)
PROJ   Project definition
PRPS   WBS (Work Breakdown Structure) Element Master Data
RPSCO   Project info database: Costs, revenues, finances
MSPR   Project stock

11.2 Equipment
EQUI    Equipment master data
EQKT    Equipment short text
EQUZ    Equipment time segment
 
12 Plant maintenance
(PM) IHPA   Plant Maintenance: Partners
OBJK   Plant Maintenance Object List
ILOA   PM Object Location and Account Assignment
AFIH   Maintenance order header
    
                              
12.1 Human resources
12.2 Settings

T582A   Infotypes: Customer-Specific Settings

12.3 Master data
T527X   Organizational Units
T528T   Position Texts
T554T   Attendance and Absence Texts
T501   Employee group
T503   Employee group, subgroup
T503K   Employee subgroup
T510N   Pay Scales for Annual Salaries (NA)
T549A   Payroll Accounting Areas
T750X   Vacancy

12.4 Infotypes
PA0001   Org. Assignment
PA0002   Personal Data
PA0006   Addresses
PA0007   Planned Working Time
PA0016   Contract elements
PA0008   Basic pay
PA0105   Communications
PA1007   Vacancies
PA1035   Training
PA2001   Absences  
Other important table
JEST System Status with object number TJ02 System status description.
MRP Related  
MDKP   Header Data for MRP Document MDTB   MRP Table
MDVL   Planning file entry for long term planning
MDVM   Enry in MRP file
PBVPV  Material Index for consumption of planning
REUL   Material stock transfer reservation index
SAFK  Run schedule master data

SAP SMART FORM ARCHITECTURE

DIFFERENCE BETWEEN STRUCTURE AND TABLE IN SAP ABAP

 
  TABLE

• Table can store the data physically but a structure dose not store.
• Table can have primary key but a structure dose not have.
• Table can have the technical attribute but a structure dose not have.

 STRUCTURE

• structure does't contain technical attributes.
• structure does't contain primary key.
• structure does't stores underline database level

DIFFERENCE BETWEEN CLIENT DEPENDENT AND CLIENT INDEPENDENT TABLE

Client dependent : What ever the modification done to an object is reflected to only that client. No other client can have the access to that.

Client Independent : What ever the modification done to an object is reflected to other client. All other client can have access to that object.

Independent = Without mandt field in tables is called independent tables.

Dependent = with mandt field in tables is called dependent tables.

UNDERSTANDING THE COMPONENT OF SAP R/3 ARCHITECTURE

ABAP+Java System Architecture

1. Message Server :It handles communication between distributed Dispatchers in ABAP system.
2. Dispatcher Queue: Various workprocess types are stored in this queue.
3. Dispatcher: It distributes requests to the workprocesses.
4. Gateway :It enables communication between SAP system and between SAP system and external systems.
5. ABAP-Workprocesses:- It separately executes dialog steps in R/3 applications.

Types of workprocesses are given as below:-

6. Memory-pipes: It enables communication between ICM and ABAP workprocesses.
7. Message Server: It handles java dispatchers and server processes.It enables communication within java runtime environment.
8. Enqueue Server:It handles logical locks that are set by the executed Java application program in a server process.
9. Central Services:Java cluster requires a special instance of the central services for managing locks and transmitting messages and data. Java cluster is a set of processes that work together to build reliable system. Instance is group of resources such as memory, work processes and so on.
10. Java Dispatcher: It receives the client requests and forwards to the server process.
11. SDM: Software Deployment Manager is used to install J2EE components.
12. Java Server Processes: It can processes a large number of requests simultaneously.
13. Threading: Multiple Processes executes separately in the background , this concept is called threading. 14. ICM: It enables communication between SAP system and HTTP,HTTPS,SMTP protocol. It means by entering system URL in the browser you can access SAP from browser also.

DIFFERENCE BETWWEN TRANSPARENT TABLE , POOLED TABLE AND CLUSTER TABLE

SAP MODULE INTRODUCTION

SAP's solution includes a number of functional modules, which support transactions to execute key business processes, such as:

• Financial Accounting (FI)
• Financial Supply Chain Management (FSCM)
• Controlling (CO)
• Materials Management (MM)
• Sales and Distribution (SD)
• Logistics Execution (LE)
• Production Planning (PP)
• Quality Management (QM)
• Plant Maintenance (PM)
• Project System (PS)
• Human Resources (HR)

INTRODUCTION TO SAP THE SOFTWARE

In 2000, SAP renamed their solution mySAP and released the latest version of SAP, ECC or Enterprise Core Component, and the most recent release is ECC 6.0. SAP's current release strategy is to provide Enhancement Packs with additional functionality instead of releasing new versions of the software. SAP's Enhancement Pack strategy eliminates major upgrades and allows customers to choose which enhancements to apply to their systems.

INTRODUCTION TO SAP

SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Applications and Products in Data Processing. Over the years, it has grown and evolved to become the world premier provider of client/server business solutions for which it is so well known today. The SAP R/3 enterprise application suite for open client/server systems has established a new standards for providing business information management solutions.
SAP product are consider excellent but not perfect.  The main problems with software product is that it can never be perfect.
The main advantage of using SAP as your company ERP system is that SAP have a very high level of integration among its individual applications which guarantee consistency of data throughout the system and the company itself.
In a standard SAP project system, it is divided into three environments, Development, Quality Assurance and Production.
The development system is where most of the implementation work takes place. The quality assurance system is where all the final testing is conducted before moving the transports to the production environment.  The production system is where all the daily business activities occur.  It is also the client that all the end users use to perform their daily job functions.
To all company, the production system should only contains transport that have passed all the tests.
SAP is a table drive customization software.  It allows businesses to make rapid changes in their business requirements with a common set of programs.  User-exits are provided for business to add in additional source code.  Tools such as screen variants are provided to let you set fields attributes whether to hide, display and make them mandatory fields