SAP Introduction: Packages, Languages, ERP Components, Architecture, and Key Tables

SAP Introduction:
Package: It is a collection of executable programs, functions and actions.

Ex: MS-Office, ATM, Railway Reservation etc
Language: It is a collection of executable statements/instructions to the system
Ex: C,C++ Language ,JAVA etc.
ERP: Enterprise Resource Planning.
Ex: SAP, Oracle, People soft, JD Edwards, BAAN,SIBEL etc.
Enterprise-Well established organization
Resource Planning
Man HR
Material MM
Machine Engineering
Money Finance
Method Planning
Single Tier Architecture: Standard system: ex:PC
Two Tier Architecture: Client-Server: Multi Viewer concept developed by IBM.
Data Base layer

Application layer
Server
PC1 PC1
PC1 PC1 PC1
1 1
1 1 1
Client
Three Tier architecture: Data base, Application & Presentation
Data base server

Data base layer
s server
Application Application Application
layer layer layer
PC1 PC1 PC1 PC1 PC1 PC1 PC1 Client

1 1
1 Application 1 1 1 1
SAP: System products in Data processing.
IDES : Internet Demonstration Evaluation System
Functional: SD,MM ,FI,CO,PP,PM,HCM
BASIS: Trouble shooting, Network Administration
Technical: ABAP, Advance Business Application programming
Is SAP a programming language: that runs in the SAP ABAP runtime environment, created and used
by SAP for the development of Application programs including Reports.
Package is a development object that stores the object such as menus, screens, functional modules,
transactions etc.
ÐzzzáSAP SD Tables and Structure:Table view t code(SM30,SE54/55/56/57)
Purpose
This wiki page will discuss about SAP tables and structures used in SAP Sales and Distribution. This can be used a
ready reference for writing FS or for data analysis.
Sales Document
Table/Structur Description
e
VBAK Sales Document: Header Data
VBAP Sales Document: Item Data
VBKD Sales Document: Business Data/Sales district data
VBPA Partners
VAKPA Partner index
VBFA Document Flow
VBEP Sales Document: Schedule Line / Data related to line items, delivery lines
VBAKUK Sales Document: Header and Status Data
VBUP Sales Document: Item Status
VBUK Header Status and Administrative Data
VBBE Sales Requirements: Individual Records
VBBS Summarized requirements
VBUV Incompletion log
VBLB Forecast delivery schedules

e
VMVA Matchcodes
VEDA Contract Data
VBKA Sales activity
Logical Database
AK V Sales documents
Delivery Document
Table/Structure Description
LIKP Delivery Document: Header data
LIPS Delivery Document: Item data
Shipping
e
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
Billing Document
e
VBRK Billing: Header data
VBRP Billing: Item data

Customer Master
e
KNA1 Customer Master: General Data
KNB1 Customer Master: Company Code Data
KNB4 Customer Payment History
KNB5 Customer Master: Dunning data
KNBK Customer Master: Bank Details
KNBW Customer Master: Wwithholding tax types
KNKA Customer Master: Credit Mgmt.
â Customer Master: Credit Control Area Data - credit limits
KNVA Customer Master: Loading/Unloading Points
KNVD Customer Master: Record sales request form/documents
KNVH Customer Hierarchies
KNVI Customer Master: Tax Indicator
KNVK Customer Master: Contact Partner
KNVL Customer Master: Licenses
KNVP Customer Master: Partner Functions
KNVS Customer Master: Shipping Data
KNVT Customer Master: Record Texts for Sales
KNVV Customer Master: Sales Data
KLPA Customer/Vendor Link
Material Master
e
MARA General Material Data
MVKE Sales Data for Material
MARC Plant Data for Material
MARD Storage Location Data for Material

e
MAKT Short texts
MARM Conversion factors
MVKE Sales data - for each sales organization and distribution channel
MLAN Sales data - for each country
MAEX Export licenses
MBEW Valuation data
MLGN Warehouse management inventory data
MLGT Warehouse management inventory type data
MVER Consumption data
MAPR Pointers for forecast data
MCHA Batches
MCH1 Cross-plant Batches
MCHB Batch stocks
KNMTK Header table - for increased performance
KNMT Data table
Bill of Material (BOM)

e
MAST Material assignment to BOM
EQST Equipment assignment to BOM
KDST Sales order assignment to BOM
DOST Document assignment to BOM
STST Standard object assignment to BOM
TPST Functional location assignment to BOM
STKO BOM header data
STZU Time-independent STL data

e
STAS BOM item selection
STPO BOM item data
STPU BOM sub-item data
Logical Database for Material Master

e
CKM Material master
MSM Material master
Pricing
e
KOMK Pricing Communications:

Header (Structure)
KOMP Pricing Communication: Item (Structure)
KONV Conditions: Transaction Data
KONP Conditions: Item
KONH Conditions: Header
KOND Contracts
VEDA Contract Data
Output
e
NAST Output: Message Status
Text
e
STXH Texts: Header
STXL Texts: Line
Others
e
JSTO PP status
SADR Address
TCOD
E Description Functional Area
1 SE54 Generate table view BC - Table Maintenance Tool
2 SE11 ABAP Dictionary Maintenance BC - Dictionary Maintenance
3 SM30 Call view Maintenance BC - Table Maintenance Tool
4 SE16 Data Browser BC - Workbench Utilities
5 SE55 Internal table view maintenance BC - Table Maintenance Tool
call
6 SE56 table view display DDIC call BC - Table Maintenance Tool
7 SE57 Internal table view deletion call BC - Table Maintenance Tool
8 SE38 ABAP Editor BC - ABAP Editor
9 SE80 Object Navigator BC - Repository Browser
10 SE37 ABAP Function Modules BC - Function Builder
11 SE93 Maintain Transaction Codes BC - Workbench Tools: Editors, Painters,
12 VA01 Create Sales Order SD - Sales
13 ST22 ABAP Dump Analysis BC - Syntax, Compiler, Runtime
14 RSA3 Extractor Checker BC - BW Service API
15 SU01 User Maintenance BC - User and Authorization Managemen
16 SLIS FI-SL Spec.Purpose Ledg. FI - Information System
Info.System
17 ST05 Performance Trace BC - Performance Analysis (Transaction S
18 SE14 Utilities for Dictionary tables BC - Activation Program, Conversion Pro
MC, SPDD
19 SE16N General table Display CO - Controlling
20 SE51 Screen Painter BC - Screen Painter
21 SM31 Call view Maintenance Like SM30 BC - Table Maintenance Tool
22 MIGO Goods Movement MM - Inventory Management
23 MIRO Enter Incoming Invoice MM - Invoice Verification
24 CATS CATS: Cross-Application Time CA - Time Sheet
25 PFCG Role Maintenance BC - ABAP Authorization and Role Manag
TCOD
E Description Functional Area
26
SD-SLS General TCodes

S.No Tcode Description
1 VA01 Create Sales Order
2 VA02 Change Sales Order
3 VA03 Display Sales Order
4 VOV8 Document Type Maintenance
5 VA05 List of Sales Orders
6 VOV7 Maintain Item Categories
7 VA21 Create Quotation
8 VA41 Create Contract
9 V_V2 Updating Sales Documents by Material
10 VA00 Initial Sales Menu
11 VOV4 Table TVEPZ Assign Sched.Line Cat.
12 VOV6 Maintain Schedule Line Categories
13 VA11 Create Inquiry
14 VA22 Change Quotation
15 VF05 List Billing Documents
Basic Functions TCodes (SD-SLS-GF)

7 VA05N List of Sales Orders
8 OVA2 Incompletion log
9 V.23 Release Orders for Billing
10 OVAZ C SD Tab. VAKZ Order Type/Organiz.
11 OVAH /nse38/Variable Messages
12 VA25 Quotations List
14 V.15 Display Backorders
15 V.02 List of Incomplete Sales Orders
Billing TCodes (SD-BIL)

1 VF01 Create Billing Document
2 VF02 Change Billing Document
3 VF04 Maintain Billing Due List
4 VF03 Display Billing Document
5 VTFL Delivery to bill copying control
6 VF11 Cancel Billing Document
7 VTFA Order to bill copying control
8 VFX3 List Blocked Billing Documents
9 VTAA Order to order copying control
10 VTLA Order to delivery copying control
11 VTAF Bill. doc. to order copying control
12 VF06 Batch billing
13 VF44 Revenue Recognition: Worklist
14 VF21 Create Invoice List
15 VTFF Bill to bill copying control
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Billing TCodes (SD-BIL)

Conditions TCodes (SD-MD-CM)
1 VK11 Create Condition
2 VKOA Accnt Determination
3 V/06 Condition Categories: SD Pricing
4 VK12 Change Condition
5 V/08 Conditions: Procedure for A V
6 VK13 Display Condition
7 VBOF Rebate: Update Billing Documents
8 VBN1 Free goods - Create (SD)
9 V/LD Execute pricing report

10 VBO2 Change Rebate Agreement
11 VB11 Create Material Substitution
12 VK31 Condition Maintenance: Create
13 VB01 Create Material Listing/Exclusion
14 VCH1 Create Batch Search Strategy
15 V/03 Create Condition Table (SD Price)
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Conditions TCodes (SD-MD-CM)

Basic Functions TCodes (SD-SLS-GF)
7 VA05N List of Sales Orders
8 OVA2 Incompletion log
9 V.23 Release Orders for Billing
10 OVAZ C SD Tab. VAKZ Order Type/Organiz.
11 OVAH /nse38/Variable Messages
12 VA25 Quotations List
14 V.15 Display Backorders
15 V.02 List of Incomplete Sales Orders
.... ......... ...........................................................
.... ......... ...........................................................

View the full list of SAP SD Basic Functions TCodes (SD-SLS-GF)

Output Determination TCodes (SD-BF-OC)
1 NACE WFMC: Initial Customizing Screen
2 VF31 Output from Billing Documents
3 VV31 Create Output : Billing
4 VV11 Create Output: Sales
5 VV21 Create Output: Shipping
6 VV32 Change output: Billing
7 NACT WFMC: Maintain Condition Types
8 NACR WFMC: Maintain Output Condition Rec.
9 VV22 Change output: Shipping
10 CMD1 Create Output: Direct Procurement
11 VV12 Change output: Sales
12 VP01 Maintain Print Parameters
13 VV33 Display Output: Billing
14 VP01SHP Print parameter maintenance shipping
15 NACZ WFMC: Procedure
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Output Determination TCodes (SD-BF-OC)

Account Determination TCodes (SD-BF-ACT)
1 VOFM Configuration for Reqs, Formulae
2 VARA Archiving
3 VORA Archiving Control for Sales Doc.
4 OVZ9 SD Cust. Control Availability Check
5 VOTXN Maintain Text Customizing
6 OVZG SD Customers: Requirements Classes

7 VORR Archiving Control for Billing Docs
8 OVZ2 C SD Tab. MVF Avail. check control
9 OVZH SD Customizing: Requirements Types
10 OVZI SD Cust: Assignment Req/Transaction
11 VUA2 Maintain Doc.Type Incompletion Proc.
12 OVZJ Default Values for Availability
13 OVRF C SD Table TVSM Material Stats Grps
14 V/12 Account Determination: Create Table
15 VOK1 Account Determination: Customizing
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Account Determination TCodes (SD-BF-ACT)

Material Maintenance TCodes (SD-MD-MM)
1 OVKK C RV Table T683V "ProcedrDeterminatn
2 VOFA Billing Doc: Document Type
3 VOR2 Joint Master Data: Division
4 V/07 Maintain Access (Sales Price)
5 VOR1 Joint Master Data: Distr. Channel
6 OVAK Sales Order Type Assignment
7 OVK1 C SD Table V_TST "Tax Catg./Country"
8 OVT0 C SD Table 077D "Accnt Grp Customer"
9 OVK3 C SD Table TSKD "Cust.Tax Indicator"
10 OVX6 Plants->Sales org./distr.channel
11 OVXC Shipping point -> Plant
12 OVK4 C SD Table TSKM "Mat.Tax Indicator"
13 V/40 Maintain Condition Type Appl V3
14 OVAO C SD View TVKO_AU "SlsOrgDoc.Types"
15 OVLZ Scheduling by Shipping Point

.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Material Maintenance TCodes (SD-MD-MM)

Free Goods TCodes (SD-BF-FG)
1 VBKD Bonus Buy: Condition Types
2 VBKA Bonus Buy: Access Sequences
3 VBK1 Create Bonus Buy
4 VBG1 Create Material Grouping
5 VBK6 Delete Bonus Buy
6 VBKB Bonus Buy: Create Condition Table
7 VBK2 Change Bonus Buy
8 VBG2 Change Material Grouping
9 VBK0 Bonus Buy Selection
10 VBK3 Display Bonus Buy
11 VBG3 Display Material Grouping
12 VBKC Bonus Buy: Display Condition Table
13 VBKF Bonus Buy: Schema Determination
14 VBKE Bonus Buy: Calculation Schema
15 VBKG Bonus Buy: Field Catalog
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Free Goods TCodes (SD-BF-FG)

Basic Functions TCodes (SD-BIL-GF)
2 VTFA Order to bill copying control
3 VTAA Order to order copying control
4 VTLA Order to delivery copying control

5 VTAF Bill. doc. to order copying control
6 VTFF Bill to bill copying control
7 OVKP SD Table TVKD "Customer detrm procdr
8 OVUR Revenue Realization: Unbilled Rec.
9 OVEP Rev. recognition: Ind. Item Categ.
10 VOKF Configuration Release of CustPrice
11 OLVF C SD Billing Menu
12 OVRM C SD Tab. TVFK BillingDoc: DocTypes
13 OVFV C SD Tab.TVPR
14 OVACT Revenue Recognition: Activations
View the full list of SAP SD Basic Functions TCodes (SD-BIL-GF)

Credit Management TCodes (SD-BF-CM)
1 OVA8 Automatic Credit Checks
2 VKM3 Sales Documents
3 VKM1 Blocked SD Documents
4 VKM4 SD Documents
5 VKM5 Deliveries
6 OVAD Delivery Type Assignment
7 VKM2 Released SD Documents
8 OVFL Assign credit contrl area/sales area
9 OVA7 Credit Relevancy of Item Categories
10 OVB8 Criteria for Creating a Requirement
11 OVA6 Credit Groups for Document Types
12 OVB5 Req. for Creating a Purch.Requisit.
13 OVFD Forms of payment guarantee
14 OVFJ Determine payment guarantee proced.
15 VOKR Configuration of Credit Release
.... ......... ...........................................................

.... ......... ...........................................................
View the full list of SAP SD Credit Management TCodes (SD-BF-CM)

Basic Functions TCodes (SD-FT-PRO)
1 VEIW Create file INTRA/EXTRA/KOBRA
2 LEER Create long-term VenDecl. (customer)
3 UPDA Foreign Trade: Mater data transfer
4 VX11N Create financial document
5 VPM4 Merge: Japan - Import Code Number
6 VE01 INTRASTAT: Selection Dispatch to EU
7 VEFU Foreign Trade: Add INTRASTAT Data
8 VINK Import Processing: Quota Number
9 LEMA Dun long-term vendor decl. (vendor)
10 VI49 Foreign Trade Data Control in Doc.
11 ENGR Periodic Declarations
12 VI29 Incompletion - Foreign Trade Data
13 CAAT Foreign Trade Atrium
14 VX22 Change license data (old)
15 ENPA FT: Enjoy: Period-end Closings
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Basic Functions TCodes (SD-FT-PRO)

Availability Check TCodes (SD-BF-AC)
2 VARA Archiving
3 CO09 Availability Overview

6 CO06 Backorder Processing
8 OVZG SD Customers: Requirements Classes
9 VORR Archiving Control for Billing Docs
10 OVZ2 C SD Tab. MVF Avail. check control
11 OVZH SD Customizing: Requirements Types
12 OVZI SD Cust: Assignment Req/Transaction
13 VUA2 Maintain Doc.Type Incompletion Proc.
14 OVZJ Default Values for Availability
15 OVRF C SD Table TVSM Material Stats Grps
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Availability Check TCodes (SD-BF-AC)

Basic Functions TCodes (SD-BF)
4 OVA8 Automatic Credit Checks
5 VARA Archiving
6 CO09 Availability Overview
7 VKM3 Sales Documents
9 VKM1 Blocked SD Documents
10 VF31 Output from Billing Documents
12 VKM4 SD Documents
13 CO06 Backorder Processing
14 VV31 Create Output : Billing

.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Basic Functions TCodes (SD-BF)

Information System TCodes (SD-IS)
1 MCTA SIS: Customer Analysis - Selection
2 MCTC SIS: Material Analysis - Selection
3 MCTE SIS: Sales Org. Analysis - Selection
4 MCTI SIS: Sales Empl. Analysis Selection
5 MCV9 Call Up List of Incomplete Documents
6 MCTG SIS: Sales Office Analysis Selection
7 MCTK SIS: Shipping Pt. Analysis Selection
8 MCSA SIS: Create Evaluation
9 MCSC SIS: Display Evaluation
10 MCV5 Call Up Price List w.Stepped Display
11 MCVCHECK01 SIS: Update Group Check
12 MCTV03 SIS: Address List - Selection
13 MCTV05 SIS: Customer Potential Analysis
14 MCV6 Call Up Indiv. Customer Prices List
15 MCTV01 SIS: Sales Activity - Selection
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Information System TCodes (SD-IS)

SD General TCodes
1 VA01 Create Sales Order
2 VA02 Change Sales Order
3 VF01 Create Billing Document

7 VF02 Change Billing Document
9 VA03 Display Sales Order
10 VF04 Maintain Billing Due List
14 VF03 Display Billing Document
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD General TCodes

Sales Activities TCodes (SD-CAS-SA)
1 VC/2 Customer Master Data Sheet
2 VC01N Edit Sales Activity
3 VC01 Create Sales Activity
4 VC/1 List of Customers
5 VC00 Sales Support
6 VC02 Change Sales Activity
7 VC03 Display Sales Activity
8 V+23 Create Business Partner
9 VC/A Sales Activity Description 01
10 VV51 Create Output for Sales Activity
11 VV52 Change Output: Sales Activity
12 VV53 Display Output: Sales Activity

13 VC/H Sales Activity Description 08
14 VC/C Sales Activity Description 03
15 VC/J Sales Activity Description 10
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Sales Activities TCodes (SD-CAS-SA)

POS Interface TCodes (SD-POS)
1 WPMA POS Download: Manual Request
2 WPER POS interface monitor
3 WPUK POS simulation
4 WPMU POS download: change message
5 WDLS Delete Error Messages
6 WLB1 Investment Buying Reqrmnt Determntn
7 WLB3 Autom. opt. PO-based load building
8 WVFB Inbound store order processing
9 WPMI POS download: initialization
10 WLB2 Investment buying analysis
11 WPER2 POS: Analysis/Auxiliary Reports
12 WVFI Simulation: Store Physical Inventory
13 WVFD Process phys. inventory doc. further
14 WPUW Goods movements simulation
15 WPED Sales Audit Editor
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD POS Interface TCodes (SD-POS)

Revenue recognition TCodes (SD-BIL-RR)
1 VF44 Revenue Recognition: Worklist

2 VF46 Revenue Recognition: Cancellation
3 VF45 Revenue recognition: Revenue report
4 VF47 Revenue Recognition:ConsistencyCheck
5 VF48 Revenue Recognition: Compare Report
6 VF42 Update Sales Documents
7 VF43 Revenue Recognition: Posting Doc.
View the full list of SAP SD Revenue recognition TCodes (SD-BIL-RR)

Electronic Data Interchange TCodes (SD-EDI)
1 VOE4 SD EDI Conversion
2 VOE2 SD EDI Customer/Vendor
3 W_PRICAT_MAINTAIN Maintain Price Catalog
4 VPRICAT Maintain and Create Price Catalog
5 SMME Output control Message Block Table
6 VOE1 Maintain EDPST
7 W_SYNC Select, Process Price Catalog
8 VOE3 SD EDI Partner Functions
9 VPRE PRICAT manual creation
10 WPRI6 Templ.for Non-R/3 Fields at CatItem
11 WPRI PRICAT on the Internet
12 WPRI7 Templ. for Non-R/3 Fields at QtyItem
13 W_PRICAT_ASSIGN_002 Assignment ILN Mat.Gr. SAP Mat. Gr.
14 W_PRICAT_ASSIGN_003 Assignment SAP Mat. Gr. - Purch.Gr.
15 W_GROUP_MAINTAIN Maintain Vendor-Group Assignment
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Electronic Data Interchange TCodes (SD-EDI)
Basic Data TCodes (SD-CAS-BD)
1 OVBR Assignment to Item Category
2 OVBS Rule Table for Determining Dates
3 OV3Z Determine Prod. Allocation Hierarchy
4 OV1Z Define Product Allocation Procedure
5 OV4Z Product Allocation Control
6 OV7Z Create Characteristics for Rem.Alloc
7 OV2Z Define Product Allocation Object
8 OV5Z Maintain Consumption Periods
9 OV9Z Suitable Statistical Structures
10 OV8Z Check Settings
11 VIM6 Customer Exits: Data Selection
12 S_ALR_87006587 IMG Activity: SIMG_CFMENUOLSDRESKX
13 S_ALR_87006681 IMG Activity: SIMG_CFMENUOLSDVOK0
14 S_ALR_87006228 IMG Activity: SIMG_CFMENUOLSDOVAD
15 VMG5 Create Material Group 5
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Basic Data TCodes (SD-CAS-BD)

Payment Cards TCodes (SD-BIL-IV-PC)
1 VCC1 Payment Cards: Worklist
2 OV9A Card Authorization Requirements
View the full list of SAP SD Payment Cards TCodes (SD-BIL-IV-PC)

Master Data TCodes (SD-MD)
3 V/06 Condition Categories: SD Pricing
4 VK12 Change Condition

5 V/08 Conditions: Procedure for A V
6 OVKK C RV Table T683V "ProcedrDeterminatn
7 VOFA Billing Doc: Document Type
8 VK13 Display Condition
9 VBOF Rebate: Update Billing Documents
10 VOR2 Joint Master Data: Division
11 V/07 Maintain Access (Sales Price)
12 VBN1 Free goods - Create (SD)
13 V/LD Execute pricing report
14 VBO2 Change Rebate Agreement
15 VB11 Create Material Substitution
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Master Data TCodes (SD-MD)

Sales Support TCodes (SD-CAS)
1 VC/2 Customer Master Data Sheet
2 VC01N Edit Sales Activity
3 VC01 Create Sales Activity
4 OVBR Assignment to Item Category
5 OVBS Rule Table for Determining Dates
6 VC/1 List of Customers
7 OV3Z Determine Prod. Allocation Hierarchy
8 VC00 Sales Support
9 OV1Z Define Product Allocation Procedure
10 OV4Z Product Allocation Control
11 VC05 Sales support monitor
12 VC02 Change Sales Activity

13 VC03 Display Sales Activity
14 OV7Z Create Characteristics for Rem.Alloc
15 OV2Z Define Product Allocation Object
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Sales Support TCodes (SD-CAS)

Sales Promotions TCodes (SD-CAS-SP)
1 VC01N_M Edit Mailing
2 VC06 Parallel Processing for Address List
3 VC10 Report Tree - Select Addresses
4 OVCB Structure of Reporting View
5 VC01N_DRAG_MAILING Edit Sales Activity
6 OVCD Definition of Reporting View
7 OVCC Assign View to User
8 OVCE Control Update of Perform.Measures
9 VVCB Maintain Activity Authorization
View the full list of SAP SD Sales Promotions TCodes (SD-CAS-SP)

Extended Rebate TCodes (SD-BIL-RB-ENH)
1 RBT_ENH_VB7 Settlement Extended Rebate Agreement
2 RBT_ENH_ACT Update of Indirect Sales
3 RBT_ENH_GEN Generation of the Update
4 RBT_ENH_VB8 List of Rebate Agreements
5 RBT_ENH_PLAN Update of Indirect Planning Data
6 RBT_ENH_VB3 Comparison: Bill. Docs and Stats
7 RBT_ENH_REBUILD Reorganization of Infostructure S469
View the full list of SAP SD Extended Rebate TCodes (SD-BIL-RB-ENH)

Self-Billing Proced. TCodes (SD-BIL-IV-SBI)
1 VSB1N Self-Billing Proc. Inbound Monitor
2 VSB1 SB Proc. Inbound Monitor - Old
3 VSBSMS SBWAP Reporting
4 OVD4 SD Self-Billing: General Parameter
5 OVD6 SD Self-Billing: Tolerance Groups
6 OVD8 SD Self-Billing: Tolerances Definitn
7 OVD5 SD Self-Billing: EDI Partner
8 OVD7 SD Self-Billing:Sold-To Party Params
View the full list of SAP SD Self-Billing Proced. TCodes (SD-BIL-IV-SBI)

Pricing and Conditions TCodes (SD-BF-PR)
1 DL10 Download
2 DL12 Change condition download profile
3 DL11 Create download profile
4 DL13 Display condition download profile
5 V_NLN Creation of Price Lists
View the full list of SAP SD Pricing and Conditions TCodes (SD-BF-PR)
Additional Material Functions TCodes (SD-MD-MM-CS)
1 MATERIAL_INFO Material Information
2 WSD_KEYWORD Keyword maintenance
3 WSD_CBP Close-By Plants Application
4 WSD_REFMAT Definition reference materials
View the full list of SAP SD Additional Material Functions TCodes (SD-MD-MM-CS)
POS Interface - Outbound TCodes (SD-POS-OUT)
1 WPER2 POS: Analysis/Auxiliary Reports
2 WDL_COPY_FILL IDoc Copy Management Customizing
3 WDL_COPY IDoc Copy Management

4 WRF_MATGRP_INIT_DLD Article Hierarchy Initial Download
5 WRF_MATGRP_REQ_DLD Article Hierarchy Direct Download
View the full list of SAP SD POS Interface - Outbound TCodes (SD-POS-OUT)
Word Processing TCodes (SD-BF-TP)
1 V/85 View V_TVKO_NAC
View the full list of SAP SD Word Processing TCodes (SD-BF-TP)

Foreign Trade TCodes (SD-FT)
1 VEIW Create file INTRA/EXTRA/KOBRA
2 LEER Create long-term VenDecl. (customer)
3 UPDA Foreign Trade: Mater data transfer
4 VX11N Create financial document
5 VPM4 Merge: Japan - Import Code Number
6 VE01 INTRASTAT: Selection Dispatch to EU
7 VEFU Foreign Trade: Add INTRASTAT Data
8 VINK Import Processing: Quota Number
9 LEMA Dun long-term vendor decl. (vendor)
10 VI49 Foreign Trade Data Control in Doc.
11 ENGR Periodic Declarations
12 VI29 Incompletion - Foreign Trade Data
13 CAAT Foreign Trade Atrium
14 VX22 Change license data (old)
15 ENPA FT: Enjoy: Period-end Closings
.... ......... ...........................................................
.... ......... ...........................................................
View the full list of SAP SD Foreign Trade TCodes (SD-FT)

Complaints Processing TCodes (SD-BIL-IV-CP)
1 CMP_PROCESSING Complaints Processing
2 CMP_REASON Customizing for Complaints Reasons
3 WCMP_PROCESSING Complaints Processing
4 WCMP_MASS Mass Complaints Processing
View the full list of SAP SD Complaints Processing TCodes (SD-BIL-IV-CP)

CPE in SD TCodes (SD-BF-CPE)
1 VCPE_FA_GCM Formula Master Data Maintenance
2 MCPE_WB CPE Formula Workbench for MM
3 MCPE_DOC Commodity Pricing in MM Documents
4 MCPE_MD Commodity Pricing Master Data for MM
View the full list of SAP SD CPE in SD TCodes (SD-BF-CPE)

Enterprise SOA TCodes (SD-BF-AC-SOA)
1 ATPC01 Maintain number range for PAR
View the full list of SAP SD Enterprise SOA TCodes (SD-BF-AC-SOA)

SD API Interface, LORD TCodes (SD-SLS-API)
S.No Tcode Descripti
1 S_EBJ_98000358
View the full list of SAP SD SD API Interface, LORD TCodes (SD-SLS-API)
Customer Scheduling Agreement TCodes (SD-SLS-OA-
SCH)
1 ESDP Maintain Tolerance Profile
ll list of SAP SD Customer Scheduling Agreement TCodes (SD-SLS-OA-SCH)
Movement types:
1.601-Goods issue
2.602-Reverse issue
3.651-Return order
4.631-Consignment Fill
5.633-Consignment issue
6.634-Consignment Return
7.632-Consignment Pickup
8. 561 - Receipt per initial entry of stock balances into unrestricted use
9.641-Stock transport order two step(Intra company) 671-Cross company
10.647-Stock transport order one step(Intra company) 677-Cross company
11.643- stock transport order for two step(Inter company) 673- Cross company
12.645-stock transport order for one step (Inter company)-675-Cross company
13.MIGO-Goods issue against purchase order-351
14.MIGO-Goods Receipt against purchase order-101
15.Goods Transfer-MB1B-453
16.161-Return MIGO
Purpose of SAP Movement Types

Movement Type: 101 is used for Goods Receipt against Purchase Order.
Movement Type: 102 is Reversal of Material Document created with Movement type:
101.
Movement Type: 122 is used to Return goods to Vendor.
Movement Type: 123 is used when movement 122 document is cancelled.
Movement Type: 161 is used when you return goods to vendor against a Purchase
Order for unknown reasons.
Movement Type: 201 is used to do Goods Issue against Cost Center.

Movement Type: 221 is used to do Goods Issue against Projects.
Movement Type: 261 is used to do Goods Issue against Order.
Movement Type: 311 is used to do Transfer Posting between Storage Locations in

One Step.
Movement Type: 321 is used to Transfer Goods From Quality to UnRestricted Stock.
Movement Type: 322 is used to Transfer Goods From UnRestricted Stock to Quality.
Movement Type: 343 is used to Transfer Goods From Blocked to UnRestricted

Stock.
Movement Type: 344 is used to Transfer Goods From UnRestricted Stock to

Blocked.
Movement Type: 349 is used to Transfer Goods From Blocked to Quality Stock.
Movement Type: 350 is used to Transfer Goods From Quality Stock to Blocked.
Movement Type: 411 is used to do Transfer Own Stock to Own.
Movement Type: 501 is used to do Goods Receipt without Purchase Order.
Movement Type: 511 is used to do Free of Charge Goods Receipt.
Movement Type: 551 is used to do Goods Issue for Scrapping.

Movement Type: 561 is used for initial entry of stock (e.g., in SAP implementation
project).
Movement Type: 562 is used for reversal of initial entry of stock.
Movement Type: 601 is used to do Goods Issue against Delivery.
Movement Type: 641 is used to Transfer Goods to Stock in Transit.
Movement Type: 651 is used For Return Delivery of Goods
Movement Type: 701 is used to do Goods Receipt against Physical Inventory in

Unrestricted.
Movement Type: 702 is used to do Goods Issue against Physical Inventory in

Unrestricted.

Quality Inspection.
Movement Type: 704 is used to do Goods Issue against Physical Inventory in Quality
Inspection.

Blocked Stock.
Movement Type: 708 is used to do Goods Issue against Physical Inventory in

Blocked Stock.
Integration:
SD-MM-FICO-PP=Material Master
SD-FI=VKOA
SAP FI MM SD PP Integration
Step-1 Generating Purchase Requistion (PP AND MM involved)
Step-2 Making Inquiries - (MM)
Step-3 Raising Purchase Order (MM)
Step-4 Release of Purchase Order (MM)
Step-5 Goods received from Vendor (MM & FI)
Raw material account - dr

GR/IR clearing ac

Step-6 Invoice Verification and quality Assurance (FI & MM)

GR/IR clearing ac
TO Vendor
Step-7 Goods issue for consumption (MM FI & PP)

Rawmaterial Consumption Dr
TO Rawmaterial Inventory Account

Step-8 Production Receipt (FI MM & PP)

Finished Goods Inventory Account
to Change in Stock

Step-9 Finished goods delivered to Customer (MM SD & FI)

Change in stock ac
to Finished goods inventory

Step-10 Raising invoice on customer (SD & FI)

Customer ac -
to Sales

Step-11 Receipt of payment from customers (SD & FI)
SAP FICO Reference Books:
SAP Fi
Link Between SAP SD, MM and FI

This page is going to provide you an idea how Sales and Distribution Module links/interacts with different other module
like, Material Management (Procurement), Finance & Controlling.
The link between SD and MM

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination
takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales
order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
The link between SD and FI

1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the
bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer. Here
movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI.
Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc)
created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and
4. Also MTO (Make To Order) scenario : when you create sales order with item category individual requirement
Purchase requisition will be created for this Sales order with Account assignment M and refere to your sales order and
when you create GR this stock will be assigned to sales order.
SD link points with other modules

SD module is highly integrated with the other modules in SAP.
The following provides a brief idea, how SD is linked to other mondules in a said process:
Sales Order
Link Points Module Involved in the Link
Availability Check MM
Credit Check FI
Costing CO/MM
Tax Determination FI
Transfer of PP/MM
Requirements
Delivery and Goods Issue -
Integration Points Module
Availability Check MM
Credit Check FI
Reduces stock MM
Reduces Inventory FI/CO
Requirement PP/MM
Eliminated
Integration points between SD and Other modules

Integration Points Module Involved
Sale organization to company code SD, FI
Division SD, MM
Plant SD, MM. PP
Shipping point SD, MM
Storage location SD, MM
Sales Represenative Commission ( if HR personal number are SD, HR

used )
Customer master SD, FI
Material Master SD, MM, PP, FI, CO
Output Master SD, ABAP
Pricing procedure SD, FICO
Request transport SD, BASIS
Profile Management (PFCG) SD, BASIS
Sales Order
Pricing SD, FI, CO
Transfer of requirement SD, PP,MM
Taxes SD, FI
Integration Points Module Involved
Availability check SD, MM
Credit management SD, FI
Delivery
Availability Check SD, MM
Credit Check SD, FI
Physical Inventory SD, MM
Inventory Value FI, CO
Picking SD, MM, WM
Packing SD, MM
Shipping SD, TM (Transportation)
Billing SD, FI, CO
Account Determination SD, FI, CO
Custom reports SD, ABAP
Resource related billing SD, FICO, PS
Introduction
A user exit is a place in a software program where a customer can arrange for their own tailor-made program to be
called. In R/3, some user exits use Include statements to include customer program enhancements that are called from
the program. Other user exits use tables that are accessed through customization.
Warning
Documentation below is copied from SPRO activities documentation and SAP library :
 SAP Help - User Exits in Sales Document

 SAP Help - User Exits for Billing
 SAP Help - Transferring new SD fields to Accounting
 SAP Help - User Exits in Transportation
 SAP Help - User Exits for Billing Plan
Relevant Information
CMOD Customer Exits
Include It is reserved for customers, for which you need a modification key
Routines
Sales Related Exits
Customer Exits
Enhancement Code Description
SDAPO001 Activating Sourcing Subitem Quantity Propagation
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
Include Routines
Include Description
MV45ATZZ For entering metadata for sales document processing
MV45AOZ For entering additional installation-specific modules for sales document processing
Z which are called up by the screen and run under PBO (Process Before Output) prior
to output of the screen.
MV45AIZZ For entering additional installation-specific modules for sales document processing.
These are called up by the screen and run under PAI (Process After Input) after data
input (for example, data validation).
MV45AFZZ For entering installation-specific FORM routines and for using user exits, which may
and be required and can be used if necessary.
MV45EFZ1
For more details see Help link above.
Billing Related Exits
Customer Exits
Enhancement Description
code
SDVFX001 User exit header line in delivery to accounting
SDVFX002 User exit for A/R line in transfer to accounting
SDVFX003 User exit cash clearing in transfer to accounting
SDVFX004 User exit G/L line in transfer to accounting
SDVFX005 User exit reserves in transfer to accounting
SDVFX006 User exit tax line in transfer to accounting
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference number)
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lists
V61A0001 Customer enhancement: Pricing
Delivery related exits
Customer Exits
Code
V50PSTAT Delivery: Item Status Calculation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50R0001 Collective processing for delivery creation

Code
V50R0002 Collective processing for delivery creation
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50S0001 User Exits for Delivery Processing
V53C0001 Rough workload calculation in time per item
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53W0001 User exits for creating picking waves
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
V02V0001 Sales area determination for stock transport order
V02V0002 User exit for storage location determination
V02V0003 User exit for gate + matl staging area determination (headr)
V02V0004 User Exit for Staging Area Determination (Item)
Include Routines
Include Description
MV50AFZ1 User Exits for Delivery Processing
MV50AFZ2 User Exit for Batch Quantity Allocation
MV50AFZ3 LIPS-KOQUI (Picking is subject to confirmation) determination
MV50AFZ The user exits in this include can be used to fill the condition tables for material
K listing and material exclusion (KOMKG and KOMPG) and product selection (KOMKD
and KOMPD) with own data.
MV50AFZL In delivery creation process for sales orders there is the possibility to restrict the delivery
creation to some order items. If these order items are member of a delivery group, but not
all items of this delivery group are includes in the restriction range of the order item nubers,
you can specify in this routine what to do.
MV50AFZP This user exit can be used to modify change mode of pricing screens in delivery processing.
MV50AFZZ Users Exit for Batch Determination; LIPS-LGORT determination

User Exits for Transportation
Include Routines
Include Description
MV56AOZ You can include your own modules in this program, to be processed in shipment processing
Z screens during PBO.
MV56AIZZ You can include your own modules in this program, to be processed in shipment processing
screens during PAI.
MV56AFZY You can include your own FORM routines in this program. They can contain your own
adjustments for shipment processsing.
MV56AFZZ This program contains pre-defined FORM routines, in which you can carry out your own
adjustments for transportation processing.
For additional information, see SAP Help link above.
User Exits for Price Determination

Routine Module Include Description
Pool or
Function
Group
USEREXIT_PRICING_PREPARE_TKOMK SAPLV60A RV60AFZZ This user exit allows you to copy

additional fields for pricing in the
TKOMK
communication structure (header
fields), which have not been
provided in
the standard SAP system. These
fields can also be used for pricing in
the
billing document. This user exit is
described in detail in the "New fields
in
pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP SAPLV60A RV60AFZZ This user exit allows you to copy

additional fields for pricing in the
TKOMP
communication structure (item
fields), which have not been
provided in the
standard SAP system. These fields
can also be used for pricing. This
user
exit is described in detail in the
"New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION SAPMV61A MV61AFZ You can use this user exit to adjust
Pool or
Function
Group
A the display of individual lines in the

condition
screen by changing the display
attributes of the screen fields. This
does not
include the display of subtotals. This
user exit is also used in order
processing.
USEREXIT_FIELD_MODIFIC_KZWI SAPMV61A MV61AFZB You can change the display of

subtotals in the condition screen by
changing
the display attributes of the screen
fields.
This user exit is also used in order
processing.
USEREXIT_FIELD_MODIFIC_KOPF SAPMV61A MV61AFZB You can adjust the display of

subtotals in the condition screen to
your requirements
by changing the display attributes of
the screen fields.
processing.
USEREXIT_FIELD_MODIFIC_LEER SAPMV61A MV61AFZB You can adjust the display of blank

lines in the condition screen to your
requirements
by changing the display attributes of
the screen fields.
processing.
USEREXIT_PRICING_CHECK SAPMV61 MV61AFZ You can install additional checks to

A the standard checks of condition
lines (e.g.
maximum/minimum value).
USEREXIT_PRICING_RULE SAPLV61A RV61AFZA In the standard SAP system, it is

predefined which condition
categories and classes
can be copied or recalculated per
pricing type. You can change the
predefined standard
procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE SAPMV61A MV61AFZ You can use this user exit to change
A the pricing type that has been
Pool or
Function
Group
predefined in the
copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT SAPLV61A RV61AFZB This field is used in the formulas and

therefore initialized before the loop
for the pricing
procedure starts.
USEREXIT_XKOMV_BEWERTEN_END SAPLV61A RV61AFZB Within a loop for the price

components during pricing, specific
values can be transferred
into the communication structures in
pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN SAPLV61A RV61AFZB In change mode, you can change the

dynamic part of the condition record
(KONVD) that
is always redetermined (i.e. it is not
stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MAN SAPLV61A RV61AFZB You can use this user exit to change
U the ready-for-input fields of the
manually entered
condition record in add mode in the
condition screen.
USEREXIT_XKOMV_FUELLEN SAPLV61A RV61AFZB This user exit is always called up

during a redetermination of all or
individual price
components. You can change the
work fields of the condition line.
However, this only
applies to conditions that have been
determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP SAPLV61A RV61AFZB This user exit is always called up

during a redetermination of all or
individual price components.
You can change the work fields of
the condition line. However, this
only applies to conditions
that have been determined via a
condition record. This may include
subtotals, manually entered
conditions or conditions that have
been calculated with a formula.
USEREXIT_PRICING_COPY SAPLV61A RV61AFZA You can change the KONV fields for
Pool or
Function
Group
copied price components.
Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a full screen to a
subscreen. The full screen is included in the SAPMV61A module pool, the subscreen, however, in program SAPLV69A.
Therefore, instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For reference, see OSS
note 313569.
User Exits for Partner Determination

Partner determination contains the following user exits for your use
User Exit Description
EXIT_SAPLV09A_00 You can use this user exit to control whether an address that was entered manually
1 and has already been used in other documents (referenced), should be referenced
again if it changes or whether a new address shold be created (duplicated).
EXIT_SAPLV09A_00 Call up this user exit if a customer has not been maintained in the current sales area.
2
EXIT_SAPLV09A_00 Use this user exit to control the origin of partners in the partner determination procedure
3 (origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this user exit is automatically
called up during partner determination.
EXIT_SAPLV09A_00 Use this user exit to integrate your own check in a program, that runs before the partner
4 is saved in the document.
For more detailed information, see the program documentation for each ofthe user exits.
User Exits For Credit Checks

If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define
them in the following user exits:
User Exit LVKMPTZZ
LVKMPFZ USER_CREDIT_CHECK1
1
2
3
User Exit for availability check
User exit Include Description
USEREXIT_AVAIL_CHECK_CREDI MV45AFZF This user exit allows you to determine whether the system
T should or should not
carry out an availability check after a blocked document has
been released or after
a new credit check.
User Exit for Risk Management for Receivables

User exit Description
RVKMPUS Using this user exit, you can define new forms of payment guarantee.
2
User Exits for Billing Plan

RV60FUS1 SAPLV60F Billing Plan: Distribute Difference
BILLING_SCHEDULE_DELTA
For milestone billing a percentage value is fully invoiced for each billing deadline. In the case
of deviations between
the original item value and any later changes, you can use the user exit to determine
whether the difference should
be stored in the final invoice or sent to the next deadline.
USEREXIT_MOVE_FIELD_TO_FPLT : This user exit allows you to create your own
fields in table FPLT.
USEREXIT_MOVE_FIELD_TO_FPLA : This user exit allows you to create your own
fields in table FPLA.
RV60FUS2 SAPLV60F Billing plan: Prepare pricing
USEREXIT_PRICING_PREPARE_TKOMX
This user exit is used to copy or create an additional field in the definitive communication
structure for pricing.
The user exit is also often used to change the duration of a billing plan deadline. You can do
this by overwriting
the following fields:
tkomp-anz_tage (Number of days in a deadline)
tkomp-anz_monate (Number of months in a deadline)
tkomp-anz_jahre(Number of years in a deadline)
tkomp-anz_wochen (Number of weeks in a deadline)
RV60FUS3 SAPLV60F Bill. Plan: Deadline Proposal From Source
USEREXIT_DATE_PROPOSAL
In the standard release deadlines are set according to a template in the billing plan. This grid
entry list sets the deadlines
for each day but you can adjust the template with the user exit so that the grid entry list
could, for example, follow a monthly
pattern instead.
Modification report for billing plan SDFPLA02
This report enables you to update the header data for a billing plan with the result that new
billing plan deadlines are determined
and set in the billing plan.
In this way you can, for example, set the goods issue date as the starting date for the billing
plan.
Additions to billing plan with transaction SMOD
User exit SDVAX001
In the standard release the billing plan type is determined from the item category of the
sales document and set in the billing plan.
You can also use the user exit to determine the billing plan type dependent on data from the
order header, order item, etc.
User exit V60F0001
This user exit is for changing the deviating billing date (FPLT-AFDAT).
RV60FUS4 SAPLV60F field preparation field selection for screen
RV60FUS5 This userexit can be used to split date lines TKOMK for Header fields
RV60FUST User Part for Billing Plan - Data Definition
Additional User Exits in Billing Document

USEREXIT_FILL_VBRK_VBRP RV60AFZC Fill in the fields in VBRK/VBRP tables
USEREXIT_NUMBER_RANGE_INV_DAT RV60AFZC Determine the number range for internal document

E RV61AFZB number
User exits for printing
User Exits For Product Allocation Processing*

User exit Includ Description
e
SDQUX0001 Function module exit for enhanced check in SD product allocation

User Exits For Availability Check
USEREXIT_PLANT_SELECTION RV03VFZZ The user exits named here are planned for projects that are to
be carried out in agreement
with SAP development as they may only be used in
consultation with SAP. SAP provides no
guarantee if they are used without our advice in program is
an exception to this rule
USEREXIT_ADD_FIELD_TO_HEADE FV45VFZZ
R
USEREXIT_ADD_FIELD_TO_LINE
USEREXIT_DELIVERY_GROUPS FV45VFZY
USEREXIT_MVERF_INIT
USEREXIT_QUOTA_KEY_VALUE
USEREXIT_AVAILABILITY_IN RV03VFZZ This user exit is used to adjust the flow during plant transfer.
USEREXIT_AVAILABILITY_OUT A list of permitted plants, where
USEREXIT_DARA_REFRESH this material is created, is determined and checked in the
USEREXIT_PLANT_SELECTION standard R/3 delivery. A dialog box
appears where you can select the plants. The user exits allow
you to modify the plant table
so that plant selection takes place in advance for every
flagged selection and a dialog box
becomes unnecessary.
User Exits For Component Supply Processing

USEREXIT_CHECK_VBLB- MV45AFZC These user exits are available for checking customer reserve fields
USR01 from VBLB-USR01 to
USEREXIT_CHECK_VBLB- VBLB-USR05. The reserve fields are used in the component
USR02 supplier industry. The system
USEREXIT_CHECK_VBLB- calls them in the screen flow logic for header data in forecast and
USR03 JIT delivery schedules
USEREXIT_CHECK_VBLB-
USR04
USEREXIT_CHECK_VBLB-
USR05
Function module V450001 is available as an SAP extension for the component supplier industry. It contains the
following user exits:
EXIT_SAPLVED4_004 General - You can use this user exit to overwrite the standard method with which the
system determines the recipient of messages (either at sales document level or in the
customer master record). You can define a special recipient for an incoming document that
has just been processed.
EXIT_SAPLV45L_001 For delivery schedules - The system checks an incoming delivery schedule against the
current/old delivery schedule to determine if there are any differences.
EXIT_SAPLVED4_004 General - You can use this user exit to overwrite the standard method with which the
system determines the recipient of messages (either at sales document level or in the
customer master record). You can define a special recipient for an incoming document that
has just been processed.
EXIT_SAPLV45L_002 For delivery schedules - With this user exit, you can change the VBLB structure (sales
document: delivery schedule data), before the system copies delivery schedule data to the
corresponding internal table.
EXIT_SAPMV45L_001 Planned delivery schedules - This user exit allows you to process schedule lines generated
automatically in a planning delivery schedule..
EXIT_SAPMV45L_002 Planned delivery schedules - This user exit allows you to modify the calendar used in a
delivery schedule split.
EXIT_SAPMV45A_005 For delivery orders (MAIS) - This user exit enables you to control how the system copies
packing proposals into the outbound delivery order.
EXIT_SAPLVED4_001 For delivery orders (MAIS) - These user exits allow you to change the workflow
EXIT_SAPLVED4_002 parameters for processing inbound EDI messages.
EXIT_SAPLVED4_003
EXIT_SAPLVED4_005
EXIT_SAPLVED4_006
EXIT_SAPLVED4_001 For the self-billing procedure - You can use these user exits for the standard self-billing
EXIT_SAPLVED4_005 procedure.
EXIT_SAPLVED4_006
EXIT_SAPLVED5_002 For the self-billing procedure -You can use these user exits for the self-billing procedure
EXIT_SAPLVED5_003 with invoice creation.
EXIT_SAPLVED5_004
User Exits For Resource-Related Billing

You can use the following user exits for resource-related billing before Release 4.5A:
 RV45HFZZ enhancement

 USEREXIT_INV_REQ_ITEM

 USEREXIT_INV_REQ_ITEM_PARTNER
You can use the following user exits for resource-related billing as of Release 4.5A:
 V46H0001 enhancement
 EXIT_SAPLV46H_001

 EXIT_SAPLV46H_002User Exits For Billing
 USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)

The internal number range used in the standard system is specified in the billing type table and can be changed in this
user exit. This user exit is only called when the billing documents is created.
 USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into
communication structure KOMKCV (header fields).
 USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into
communication structure KOMPCV (item fields).
 USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
 USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the
new billing document with deviating or additional data.
 USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
 USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
 User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:


 USEREXIT_RELI_XVBPAK_AVBPAK

 USEREXIT_NEWROLE_XVBPAK_AVBPAK

 USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
 EXIT_SAPLV60B_001: Change the header data in the structure acchd

You can use this exit to influence the header information of the accounting document. For example, you can change the
business transaction, "created on" date and time, the name of the person who created it or the transaction with which
the document was created.
 EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT
structure is filled in with data from document header VBRK.
 EXIT_SAPLV60B_003: Change the customer line in costing

The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
 EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item
(such as quantity specifications) with this exit.
 EXIT_SAPLV60B_005: User exit for accruals

Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
 EXIT_SAPLV60B_006: Change the control line ACCIT

You can use exit 006 to add information to the control line.
 EXIT_SAPLV60B_007: Change the installment plan

You can use exit 007 to add information to the installment plan
parameters in the GL account item.
 EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD

After the accounting document is filled in with data, you can use exit 008 to change the document once again.
 EXIT_SAPLV60B_010: Item table for customer lines

You can use exit 10 to influence the contents of customer lines before they are created.
 EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account
determination
You can use this exit to change inbound parameters in order to influence account determination. User Exits For
General Billing Interface
 USEREXIT_AVBPAK_CPD (in Include RV60AFZB)
With this user exit for the general billing interface, deviating address data for different partner functions can be copied
from the interface.
 USEREXIT_AVBPAK_ADD (in Include RV60AFZA)
With this user exit for the general billing interface, new partner functions can be copied from the interface.
 USEREXIT_XVBAPF_KEY (in Include RV60AFZA)
With this user exit for the general billing interface, a key field can be added in the aggregrated flow.
 USEREXIT_XVBAPF_KEY_CANC (in Include RV60AFZA)
Special user exit for the general billing interface with which a key field can be added in the aggregrated flow.
User Exits For Sales Support
In Sales Support, you can use the following SAP enhancements:
 MCV2001 - Expand LIS fields for sales activities/sales promotions. This enhancement contains the following
user exit:
 EXIT_SAPLMCV2_001
 V43MLIS - Expand LIS fields for address lists. This enhancement contains the following user exit:
 EXIT_SAPLV43M_007
 V43K0001 - Enhancement for linking to calendar. This enhancement contains the following user exit:
 EXIT_SAPLV43K_001
 V43ADATA - Change sales activity data in dialog. This enhancement contains the following user exit:
 EXIT_SAPMV43A_007
User Exits For Lists
User Exits in Program RVKPR002 (Customer Expected Price)

RVKPRFZ1 This allows the list structure of individual fields to be filled on header and item levels.
RVKPRFZ2 This allows the sort sequence for the first issue of the list to be defined.
RVKPRFZ1 This allows you to deposit your own user codes.
RVKPRFZ1 This allows you to create your own list headings.
There are two additional user exits for listing sales documents, which influence the way in which the communication
structure is filled. These user exits do not affect the structure of the list but the way in which the data is transferred and
how the new additional fields are filled.
 CUSTOMER_FILL_1
 CUSTOMER_FILL_2
User Exits for Payment Cards
Include MV45AFZH contains the user exit AUTHORIZATION_VALUE_SPLIT.

You can use this user exit to initiate the system to create several authorizations in the sales order at the same time. This
might be appropriate when different shipping points are assigned to the items and therefore several shipments will be
created for a sales order.
More information can be found here:
 Note 381348 - Using user exit, customer exit, VOFM in SD
 sd
Enterprise Structure:
Definition:
1. Financial Accounts: Define company, credit control area, company code, Business area,
Functional area, Maintain Consolidate Business Area, Profit Centre.
2. Controlling: Controlling Area, cost centers, operating concern
3. Logistic General: Define Valuation level,Plant,Location & Division
4. Sales & Distribution: Sales org,Distribution channel, maintain Sales Office & maintain Sales
Group
5. Material Management: Maintain Storage Location & Purchase org
6. Logistic Execution: Define Warehouse, shipping point, maintain Loading group,
Transportation planning point
7. Plant Maintenance: Maintain Plant Maintenance plant
Assignment:
Financial Accounting:
1. Assign company to company code

2. Assign company code to Credit control Area
3. Assign company to Financial Management Area
4. Assign Profit centre to company code
5. Assign business area to consolidate business area
Controlling:
1.Assign company code to controlling area
2.Assign controlling to operating concern
Logistic General:
1. Assign plant to company code

2. Assign business area to plant/valuation area and Division.
3. Data comparison with sales plant/val area-Division-Business area
SD:
1. .Assign Sales organization to company code

2. Assign Distribution channel to sales organization
3. Assign Division to sales organization
4. Setup sales area
5. Assign Sales office to sales area
6. Assign sales office to sales group
7. Assign sales organization-Distribution channel-Plant
8. Assign sales area to credit control area
9. Business Area Account Assignment-Define rules by sales area, Assign business area to
plant & Division, Assign Business area by sales area
Material Management:
1. Assign purchasing organization to company code

2. Assign Purchasing organization to plant
3. Assign Standard purchasing organization to plant
4. Assign Purchase organization to reference purchase organization
Logistics Execution:
1. Assign warehouse number to plant and storage location

2. Assign Shipping point to plant
Plant Maintenance: Assign Maintenance plant to Maintenance plant
Company code assign to fiscal year and chart of accounts:
1.Financial account-GL accounts-Master data-preparation-Assign company code to chart of

accounts.
2.Financial account-Financial account global setting-fiscal year-assign fiscal year to company code
Create Account Groups:
1.Financial accounts-accounts receivable and payable-customer accounts-master data-preparing for

creating customer master-define account groups,2.Define number ranges for customer
master,3.assign number ranges to customer account groups.
Partner Determination procedure: T code
1.IMG-SD-Basic functions-Partner Determination-Set partner determination-setup partner

determination for customer master-Partner determination procedure-1.Partner function in
procedure,2.Partner determination procedure & assignment,3.Account groups & functional
assignment.
Create customer Master:XD01/VD01/FD01
Easy access-Logistics-SD-Master data-Business partner-Customer-create/change/display
1.General-Address/Control data/payment transaction/Marketing /Uploading points/Export

data/contact persons
2.Company code:Account Management(Reconciliation account)/payment transaction(terms of

paymet,payment method,payment history record check box,/correspondence/insurance
3.Sales area-Sales/shipping/Billing doc/Documents/partner function
Sales-sales district/sales group/sales office/customer group/price group/customer pricing procedure
Shipping-Delivery priority/shipping condition/Delivery plant, check box(POD, order combination,

complete delivery req by law)
Billing-Invoice Date, invoice listing date,inco terms,payment terms, credit control area,Account
assignment group,MWST Tax,payment guarantee payment,check(rebate, price determination)
Maintain Material at company code level: OMSY
Quantity/Value updating of Material: OMS2
Material Master:MM01/MM02/MM03
Easy access-Logistics-Material Management- Material-Create
Material Master View:

Basic data1:Base unit of measure, Division, product allocation,X-plant material status,Item category
group, Gross weight,Net weight, Material group pack material.
Sales org 1: Base unit of measure,X-Disribution chain status,D-Specific Distribution status,Material

Group,Delivery plant,Division, cash discount check box
Sales org2:Material statistic group,Item category group,Material pricing,Account assignment

group,reference pricing material.
Sales:General/plant:Availability check,Transportation group,Loading group
Accounting1:Valuation class, price control,Moving price,standard price
Purchasing: Purchasing group, Material group
MRP1: MRP type, MRP Controller, MRP group, Lot size, Max lot size
MRP2: procurement type
MRP3: Total RLT, Strategy group
MRP4: Replenishment quantity
Sales documents Header: VOV8
IMG-SD-Sales-Sales documents-Sales documents Header
Sales doc item category-VOV7
Schedule line category-VOV6
Inquiry:VA11
Quotation:VA21
Sales order:VA01
Scheduling Agreement-VA31
Contract-VA41
Back order-V_RA(SD),CO06(Material)
Rescheduling-V_V2
Eassy access-Logistics-SD-Sales-Inquiry/Quotation/Order
Pricing:
IMG-SD-Basic functions-Pricing-pricing control-Condition type
Condition record:VK11
Condition table:V/3, to save as package and workbench request
Access sequence:V/07 save as package in workbench request
Condition type:V/06
Pricing procedure: V/08
Determine pricing procedure: OVKK
Exclusion group:
Condition supplement:
Condition scale:
Pricing scale:
Minimum order:
Group condition:
Shipping point determination:OVL2
Basic Functions:
1.Account determination: It is the process of determining G/L accounts while posting invoice
values into accounting.
While creating invoice in background system generate accounting document. The accounting
document is Customer A/C Debit to………….Revenue A/C Credit.
.For customer accounts system picks G/L A/C from Reconciliation A/C
.For the revenue accounts system determine GL accounts from Revenue A/C determination.
.Revenue A/C determination is Integration between SD and FI.
.Revenue A/C determination is also based on condition technique.
Configuration steps:
Define account assignment group for customer and material: IMG-SD-Basic functions-account
assignment/costing-Revenue account determination-check Master data relevant for account
assignment-Define material/customer account assignment group.
Create table:01,02,03,04,05
01: Sales org/chart of accounts/ Account assign of Customer/Account assign of Material
Maintain access sequence for account determination: KOFI
Define account determination type: KOFI
Define account determination procedure: KOFI00

Assign account determination procedure:
Step(10) counter(0) condition type(KOFI) Requirement(3) without CO
Step(20) counter(0) condition type(KOFK) Requirement(2) with CO
Define account keys:ERL,ERS,ERB,WMS.ERF etc
Assign account Keys:
Procedure(ZVAA01) step(80) counter(0) condition type(KOFI) account key(ERL)
Assign GL accounts:VKOA
Application(V) condition type(KOFI) chart of accounts(ACIA) sales or() account assign of customer(01)
account assign material(01) Account keys(ERL) GL accounts() Provisional accounts()
Provisional accounts will be use for settlement of rebate accounts. I e accurals.
In customer Master Data , Billing section, maintain Account document Reconciliation A/C and
payment Transaction tab, check Payment History record.
And sales are section, billing tab, check account assignment Group.
Material Master- sales org 2-check account assignment goup.
2. Reconcialition account Determination: It is the process of determining Reconciliation accounts

while posting invoice values into accounting.
While creating invoice in background system generate accounting document. The accounting
document is Customer A/C Debit to………….Revenue A/C Credit.
For customer accounts system determines G/L A/C from customer master Reconciliation A/C.
But if client requirement reconciliation account should not be determine from customer master, it
should be determine based on some other combination like Plant & Division, then we will configure
reconciliation A/C determination.
Configuration:
1.SPRO-SD-Basic functions-account assignment coasting-Reconciliation A/C determination-Manintain

condition table(maintain condition table as per client req. plant & Division)-Plant/Division-Generate-
save it.
2.Maintain Access sequence:KOAB
3.Maintain condition type: KOAB
4.Maintain A/C determination procedure: KOFIAB
5. Assign A/C determination procedure: KOFIAB with F2
6. Assign GL A/C : Double click on our table(Plant/Division):
Application(VB) Condition type (KOAB) chart of accounts() plant() Division() GL accounts() Provisional
account()
Provisional A/C will use for condition types are accurals, for rebate settlement.
7.Alternative Reconciliation accounts:
GL A/c() and Alternative GL A/C()
3.Cash Settlement Account Determination: It is the process of determining GL accounts while

creating case sale invoice.
When we create cash sales invoice,Cash settlement account Dr to…………….Revenue A/C cr.
Configuration:
1. Cash settlement A/C determination: Maintain condition table: create condition table with sales
org
2. Maintain field catalog:
3. Maintain Access sequence: CASH
4. Maintain condition type: CASH
5. Maintain account determination procedure:KOFIAC
6. Assign Account determination procedure: Billing type(BV) and Account determination

procedure(KOFIAC)
7.Assign GL A/C: Application(VC) condition type(CASH) chart of accounts() sales org() GL A/c()
4.Delivery Scheduling:
It is the process of determining Delivery dates and confirmed quantities into sales document.
System consider the below parameters while performing delivery scheduling.
1.Pick Pack time: It is the time taken pick the material from storage location and to pack it.(maintain
in shipping point)
2.Loading time: It is the time taken to do the process of loading the goods into trucks for dispatch.
( maintain in shipping point)
3.RLT: It is the time taken Manufacturing the product. System consider RLT if stock is not available.
(Replenishment Lead Time-Material Master, MRP3 view)
4.Transist Time: It is the time taken deliver the goods from plant to customer. (Maintain this in
Route determination)
5.Transportation Lead time: It is the time taken to arrange the mode of Transportation for
dispatching it to customer.
Whenever we create a sales order, 1st system will perform “Backward Scheduling” If backward
scheduling fails then system will perform “Forward Scheduling”.
.Backward scheduling is always based on customer requested Delivery date.
.Forward Scheduling is always based on Today’s date.
If the propose date is beyond today date, backward scheduling fail.
Configuration:IMG-SD-Basic fucntions-Delivery scheduling and Transportation scheduling

.Define scheduling by sales documents type:
Sales doc type(OR) Dlv scheduling() Transportstion scheduling() backward scheduling()
.Define scheduling by shipping point: Maintain Pickpack and Loading time here
.Maintain working hours
.Maintain Duration
4.Route determination:
Departure zone/country from Shipping point
Shipping condition from Sold to party
Transportation group from Material Master
Transportation zone/Destination country from ship to party
Delivery group of Material Master –If re determined in the delivery doc.
Define mode of transport: IMG-SD-Basic functions-Define route-Define mode of transport:
Define shipment type:
Define transportation connection point:
Define route and stages:
Create venoder:Logistics-SD-Master data-Business partner-Forwarding agent-create V.11
Define route determination:
Maintain country and transportation zone for shipping point:
Define transportation group:
Maintain route determination:
Go to VA01 and check route existed or not
5.Partner Determination procedure:
Define partner function:IMG-SD-Basic functions-Partner determination-setup partner determination:
Define partner determination procedure:
Assign partner functions in partner determination procedure:
Partner determination procedure assignment:
Assign partner functions to account group:

6.Output determination:
IMG-SD-Basic functions-Output determination-Output determination using condition technique-

Maintain output determination for sales/delivery/billing documents:V/57
Maintain condition table: select sales org
Maintain output type:V/30
Maintain access sequence:
Output condition type;BA00(order)
Access condition () If we check system will determine output type from condition technique, if we
unckeck system will determine output from customer master with help of DB0001.
Can not change: If we check, system will not change output type.
Multiple issuing: If we check, system will allow multiple printout and mails in sales doc
Partner indep output: If we check, each output will be send to all partners(Quotation, & order will
send sold to party, delivery will send ship to party ,invoice will send to bill to party)
Do not write processing log: If we check system will not display the log info while issuing outputs.
Change output: Only for output mail configuration, if we want to send different format of mail.
Default values: Whether to send the output with some back ground job or some application of
Transaction or send immediately while saving the transaction.
Transmission medium: 1-Printout, 2-Fax, 5- External send (Email), 6-EDI(SAP to non sap)
A-ALE(SAP to another SAP system)
Assign output types to partner functions:
Maintain output determination:
Step(10) counter() condition type() requirement(2)
Allocate sales document Header: V/43: sale doc type(OR) and output procedure()
Allocate sales document Item: V/69
Maintain condition records:VV11(sales),VV21(delivery),VV31(Billing)
Easy access-Logistics-SD-Master data-output-Sales doc-vv11
T.code: NACE= Output control(V1-sales,V2-Delivery,V3-Billing)
NAST=Output table
7.Text Determination:
IMG-SD-Basic functions-Text control-Text types:

Define Text determination procedure:
Assign Text ID to Text determination procedure:
Assign Text determination procedure for account group:
Maintain Text in the customer Master:XD02,sales area-Extras-text
Text determination procedure for sales doc Header:
Define Text type:
Define access sequence:
Define Text determination procedure:
Assign Text ID in text procedure:
Assign access sequence for text ID’s:
Assign document type to text determination procedure:
8.Copy Control: VOFM
Sales documents to sales documents: VTAA
IMG-SD-sales-sales documents-Maintain copy control for sales documents: Header, item & schedule
line
Sales doc to sales doc: VTAA
Sales doc to delivery doc: VTLA
Sales doc to billing doc: VTFA
Delivery doc to billing doc: VTFL
Billing doc to Billing doc: VTFF
Billing doc to sales doc: VTAF
9.Incompletion Log:
IMG-SD-Basic functions-Log of incompletion items-define status group: OVA0: Which function will
carried out incompletion procedure in SD.
Here you can check, General, Delivery,Billing,Pricing,Goods Movement,Picking/Putaway,Pack
Define incompletion procedure: OVA2
Group: A-Sales Header
B-Sales Item
C-Sales Schedule line
D-Partner
F-Sales Activity
G-Delivery Header
H-Delivery Item
Assign incompletion procedure for sales/delivery/billing: VUA2
Assign Procedure to Sales Header,sales Item, Sales schedule line, Delivery Header & item etc.
10.Bill of Material (BOM):
Configure BOM item:CS01
Easy access- Logistics-production-Master data-Bill of Material
Above structure: Item category:ERLA, item category: TAQ(Header level),TAE(sub item), delivery and
billing carried at header level,sub item treated as text item
Below structure:item category :LUMF, item category: TAP(header level),TAN(sub item),delivery and
billing carried at sub item, header item is text item.
11.Material determination: It is the process of submitting one product in place of other product.
Reason for substitution: a. If the product is discontinued and coming with new product
b.If the product is not available
C.Combo packs (Promotional activity)
Item category System Header Pricing: TAX and TAPS
Item category System Item Pricing: TAPA and TAN
Define condition table: Sales org & Material-Generate
Access sequence: A001
Define condition types: A001
Define material determination procedure (A00001): Step(10) counter() condition type(A001)

Requirement()
Assign procedure to sales doc type: OV14: sales doc type(OR) and Procedure(A00001)
Define substitution reasons: OVR0
Substitution reason (0005) strategy() outcome() substitution strategy()
Strategy: (Blank-Automatic, A-Substitute products are displayed for selection,B-General material

determination with selection, without ATP)
Strategy: Product selection in the background is performed on the basis of availability check.
Outcome: (Blank-Item will be replaced, A- Substitute products are displayed as sub items, B-As in A
but only when creating the item in sales)
substitution strategy-(A- Substituted by product services)
Maintain the condition record for material determination: VB11
Logistics-SD-Master data-Products-Material determination: VB11
The result of MRP indicator: OVZ9
MRP indicator in Material determination: If we check MRP indicator, if stock of substituted item is
not available then system will try to submit another material in sales doc.
If you want to see MRP indicator in Material master, Go to VB11 and enter material, select line
Material and double click, You will get new screen Alternative Material and MRP indicator.
Item Proposal: VA51
Listing of materials for which customer regularly place order, and calling the list while creating sales
order.
Item proposal will save the time of end users who is creating sales order.
Logistics-SD-Master data-products-item proposal-VA51,create sales doc type PV.
You can enter list of materials and save. Go to VA01 and check.
Create product proposal: VOV8-MS
XD02: check item proposal check box in customer master sales area section
Material Listing & Exclusion:
Listing: Listing is Allowing customer to buy only listed materials
Exclusion: Restricting materials which customer is not eligible to buy.
Maintain condition table for Listing & Exclusion: select customer/material-Generate
Maintain access sequence:A001 for listing, B001 for exclusion
Maintain Listing/Exclusion types: A001 for listing, B001 for exclusion
IMG-SD-Basic fucntions-Listing/Exclusion-procedure for maintain Listing/Exclusion: A00001 for

Listing, B00001 for Exclusion
Active listing/Exclusion sales doc type: OV04:
Sales order(OR) Listing(A00001) Exclusion(B00001)
Maintain condition records for Listing/Exclusion:VB01:
Material(XXXX) Description
Logistics-SD_Master data-products-Listing/Exclusion:VB01
Cross selling: It is the process of selling additional products along with main products.
IMG-SD-Basic functions-Cross selling-Define determination procedure for cross selling-create

condition table: OV46:sales org/plant
Maintain access sequence: OV41
Define condition types: OV42
Maintain procedure for cross selling: OV43
Define customer procedure for cross selling:
Define document procedure for cross selling:
Assign document procedure for cross selling to sales document:
Define cross selling procedure:
Assign cross selling procedure:
Maintain condition records: VB41
Logistics-SD-Master data-products-cross selling-VB41
Go to XD02: Assign product proposal in sales area section in customer master.
Customer Master-Sales Area section-sales tab-PP customer procedure(B-Cross selling)
Customer Material Info Records: VD51: customer place the order with own material code, we can
create CMIR.
Logistics-Logistics execution-Master data-Customer material information-create:
Credit Management: SD+FI
It is the process of managing credit limits of the customers.
Every company has Credit Management Department, this credit Department will manage the credit
limits of the customers.
Role and Responsibilities of credit Management Department:
a. They Fix credit limits to the customers
b. Monitoring the day to day transactions and any of the customer credit limits exceeds then they
block the next transaction.
c. Releasing the order which is blocked for credit.
Credit Management can be configured two ways:
A.Simple credit check, B. Automatic Credit check

Simple credit check: OVAK
IMG-SD-Basic functions-Credit Management/Risk Management-Simple credit limit check: sales doc

type+credit check+credit group.
Update group:12,15 & 18, Update group controls, which sales documents updated in credit
Management.
Define credit control area: OB45, Update group 12,15,18
Assign company code to credit control area: OB38
FD32:check payment history
V/08: In pricing procedure,put net value of subtotal value is A, pricing will connected with credit
Management.
B. Automatic credit check:
Define credit control area: OB45
Assign permitted credit control area to company code: IMG-Financial accounting-Accounts

receivable/payable-credit Management-credit control accounts-assign permitted credit control area
to company code:
Assign company code to credit control area:
Define Risk categories: OB01(IMG-FI-Define Risk category):High,Medium & Low risk
Define preliminary settings for credit Management:
Define Text ID’s for credit Management: OBT3
Maintain Text ID’s for central text in credit Management: OBT3Z
Define credit Representative Group: OB02
Define Groups:
Define credit Representatives: OB51
FD32, Specify customer number and credit control area.
Define credit limit check by sales documents type: OVAK(IMG-SD-Basic functions-credit

Management)
Define credit limit check by Delivery order: OVAD
Define credit limit check by item category: OVA7
Define credit groups: OVA6(credit group for sales order,delivery,PGI)
Define automatic credit control: OVA8: Credit control area+risk category+credit group
VKM3-for release credit limit

VKM4-for sales & delivery doc
VKM5-for release delivery doc.
Automatic credit control fields: OVA8:
Item check= If we check this, then system will perform credit check while entering the line item in
sales document.
Diviation%= After releasing the order which is blocked for credit ,if user is changing the value in that
order then system will again block the order for credit.The control is Diviation in %.
If we want to allow increasing up to some% then maintain the % value.
Number of days=After releasing the order which is blocked for credit, if there is no further process
within the number of days mentioned here,then system will again block the order for credit.
Credit limit seasonal factor: This will be used to increase or decrease the credit limits to the entire
customers during a particular period.
Statistic=If we check statistic, then system will update all open order, open delivery, open invoice
and open item value in credit check(FD32).
Reaction= This field controls how system should respond, if order is blocked for credit, i.e whether
to give warning message or error message or no message.
Status/Block= If we check this then while creating sales order if customer credit limit exceed then
system will block the order for credit.
If we uncheck this even a customer credit limit exceed system will not block the order for credit.
Open orders: IF we check this then only system will perform credit check while creating order and if
customer credit limit is exceed then system will block the order.
If we uncheck this then system will not perform credit check in sales order and system will not block
order.
Open deliveries: If we check this then only system will perform credit check while creating delivery
document. The blocked order value will not be update into credit Management(FD32).
Dynamic=If we check this , then system will update all open order, open delivery, open invoice and
open item value in credit check, but any open order if the delivery creation date is exceeding horizon
date that order will not be updated in credit Management(FD32).
Document value=If we check this and if we maintain max document value then while creating sales
order if sales order value exceeds Max.Doc value then system will block the order for credit, the
reason is document value is exceeds.
Critical fields=If we check this then while creating sales order,if user changes any of the critical fields
then system will block the order for credit even though the customer have enough balance.
Critical fields are(payment terms,fixed value date and additional value days) in credit Management.
Next Review date=If we check this while creating sales order system will check order date with next
review date if the sales order date is exceed next review date then system will block the order for
credit .The reason is review date Has been passed.We maintain next review date in FD32 status
view.
Open items=If we check this then if we maintain max open item % then while creating order system
will check is there any open item existing for this customer or not, if yes then it accumulate the value
of open items and system will also check is any of the open item is overdue or not, if is there any
overdue item then system will do accumulate the values of overdue item and calculate the %
between overdue item and open item value.If this% exceed Max open item% then system will block
the order for credit.
Oldest open item=It is nothing but overdue item, if we check oldest open item then while creating
sales order system checks for this customer is any one of the previous invoice is overdue or not, if
yes then system will block the next transaction.
Payer=Payer is checked, If customer have multiple payers.
Payer check is only applicable only for open item and oldest open item.
If we check payer, then system considers the invoices of only that particular payer while performing
open item check and oldest open item check.
If we uncheck payer then system consider the invoices of the all payers who are in a group, while
performing open item and oldest open item.
High dunn level=Dunning is the process of sending reminders to the customers, whose payment is
delayed. Dunning configuration done in FI consultant.
User1,user2 & user3=If client’s requirement related to credit Management is not fulfilling with
standard configuration then we use user exits.
Transfer of Requirement/Availability check:
Transfer or Requirement: SD+MM+PP
TOR will help to transfer the sales order requirements to MRP.
If we don’t transfer the requirements, then the employees at the plant will not know the information
of sales order requirement, and the result is even if stock is getting emptied they will not start the
production.
If we are not transfer the sales order requirement to MRP, system could not be able to perform
availability check.
 When we create sales order, first system determines requirement type into sales document
in procurement tab and requirement type will help to determine requirement class.
 Requirement class controls how to transfer the sales order requirements to MRP.
Prerequisite for Transfer of Requirement:
1. Schedule line category: Icheck Requirement & assembly availability check
2. Requirement class: Check Requirement and availability check

3.Requirement type should be determined into sales document.
 Criteria to determine requirement type in sales doc:

1.Strategy group(MRP3 view), 2.MRP Group(MRP1), 3.Item category+MRP type(MRP1)
4.Item category.
ATP Quantity=Warehouse stock+ Planned Receipts-Planned issue
System creates a demand with MRP by Requirement type 041.
1.Define Requirement classes: OVZG(IMG-SD-Basic functions-Availability check & Transfer of

Requirements-Transfer of Requirements-Define Requirement classes=41/11/KE/KEB
2.Define Requirement type: OVZH:KE/41/11/KEB
3.Determination of Requirement type: Item category+MRP type
4.Define procedure for each schedule line category: Check requirement and availability check
5.Block quantity confirmation in delivery block: If we check confirmation block then while creating
sales order system will cancel the confirmed quantity.
6. Maintain requirements for Transfer of Requirements: OVB8: Requirement number (101) in TOR,If
order is blocked for credit, system automatically cancel the confirmation.
7.Maintain requirements for Assembly and purchase order: OVB5: Requirement number (102) in
TOR, If order is blocked for credit in IPO & third party, system will not generate PR.
Availability check: SD+MM+PP+CO:
It is the process of checking the stock availability of the material while creating sales order.
Prerequisite to perform Availability check:
1.Availability check field in material master: General/plant Data view in material master: This filed
also called as checking group.
01-Daily requirement: If we maintain 01 then system cumulates the sales order quantities on that
particular date and update in single line in MD04.
02-If we maintain 02 the each sales order quantity will be update in MD04 along with the sales order
number.
KP: If we maintain KP in availability check the system will not perform availability check.
2. Schedule line category: If we check Requirement & assembly availability check in schedule line
category then only system will perform availability check.
3. Requirement class: Check Requirement and availability check
4 .Requirement type should be determined into sales document.

Criteria to determine requirement type in sales doc:
1. Strategy group (MRP3 view), 2.MRP Group(MRP1), 3.Item category+MRP type(MRP1)
4. Item category.
Configuration for availability check:
A. Availability check with ATP:

B. Availability check with product allocation: When shortage of material
C. Rule based Availability check: Many plant will perform
Define checking group: OVZ2(IMG-SD-Basic-Availability check-Availability check with ATP Logic-
1.Checking group: In define checking group we have actual controls of how to update sales order
quantities in MRP. I. e total records per day or single records
For 01 we maintain “B” Total records per day
For 02 we maintain “A” Single records
2.Define material block for other users:If multiple users are performing availability check for same
material and in the same plant same time, then system will perform availability check for 1 st user and
block availability check for other users.
A-order, B- Delivery
3.Define checking groups default values: if we maintain checking group system automatically
determines it while creating material master.
Material type with plant and availability check.
4.Carryout control for Availability check: OVZ9: Scope of check is also called as availability check
control.
We can configure scope check in the combination of (checking group+ checking rule)
If we want to configure availability check in order then checking rule is A.
If we want to configure availability check in Delivery then checking rule is B.
Stocks: Include safety stock, Stock in Transfer, Include quality inspection stock and include blocked
stock
In/Outward Movements: Include purchase order,Incl Purchase requisition, incl sales requirements,
incl deliveries, inc planned order, incl production orders
Replenishment lead time: () Check without RLT.
5. Define procedure by requirement class: OVZ0: We have to requirement and availability check
here.41,KEB,40 etc…
6. Define procedure for each schedule line: In “CP” requirement and availability check
7. Determine procedure for each delivery item category: This configuration step controls whether
to perform availability check in delivery or not.
The below scenario we have to perform availability check in Delivery:
a. When we create delivery W/O reference

b. Adding new line item in delivery
c. Increase the quantity in Delivery
d. STO Delivery
8. Define default settings: If we check fixed date and quantity, system will not allow to change
the delivery dates and confirmed quantities while creating sales order.
Availability check rule: This field will help to propose POPUP in case of shortage of stock.
9. Checking rule for updating back orders:
Pricing:
Pricing is based on condition technique.
Condition technique is the process of determining condition records in sales documents.
Condition technique is consist of condition records.
Condition records will be stored in condition table.
Condition table will be placed in access sequence from most specific to most general.
Access sequence will be assigned to condition type.
Condition type will be placed in pricing procedure.
Condition Records (Vk11): Condition records is Master data of pricing, we also called as pricing
Master.
Condition table: V/03, Condition table is the combination of fields which will help to maintain
the condition record.
Combination: 1.Customer/Material, 2.Pricelist/Material, 3.Material
Access sequence: V/07, It is a search strategy which will search for valid condition record from
the most specific to most general.
Exclusive indicator: If you check exclusive indicator, if system find valid condition record at any
of the combination then system will immediately come out of the search strategy and determine
the price in to sales document.
If you uncheck exclusive indicator, if system find valid condition record, system will not come out
of the search strategy. It will continues search in other combinations, if system find valid
condition record in other combination then it will determine all the condition records into sales
document.
If it is a base price, active the last one deactivate previous one.

If it is a discount then it will activate all.
Condition type: V/06, It control the type of the pricing components, i.e whether it is a base price
or discount or surcharge.
Base price PR00:10000
Discount (K004):500
Gross price: 9500
Surcharge:200
Net price:9700
Net+Excise tax:100
Total:9800,
Pricing Procedure: V/08, It is a procedure which consist of all the relevant condition types, which
are placed in a sequence.
Configuration od Base price: PR00
a.Condition table: SPRO-SD-Basic functions-Pricing-pricing control-condition table: Manintain table

number above 500(Up to 500 number is standard) .
Field catalogue: Filed catalogue consist of allowed fields to create condition table, while creating
condition table we need to select the fields from filed catalogue.
Go to field catalogue, put crusher here and select(Customer/Material),(Pricelist/Material),(Material)

one by one using page up and down select double click on technical and medium to move selected
fields after selecting click on generate icon.
We can save condition table in package. If you save in local object, it can not be transfer from server
to another server and system will not generate transport request.
Basis consultant will provide package.
Cross client: The configuration and customization we do in one client will automatically update in
other clients within a server.
Cross client is also called as client independent.
b. Define Access sequence: In access sequence we place the condition tables from
most specific to most general. Access sequence configuration is also cross client.
c. Define condition type:V/06
d. Define pricing procedure: V/08, these are 16 steps
e. Assign pricing procedure or pricing procedure determination: OVKK.
Sales are+customer pricing procedure+document pricing procedure+pricing
procedure+ condition type.
F. Maintain condition records:VK11
G: Maintain price list:IMG-SD-Basic fucntions-Pricing-Maintain price relevant master

data filed-define price list:
Discount: K004-Material discount
K005-Customer/Material discount
K007-Customer discount
KF00: Fright charges(Surcharger), condition table: Inco term 1& 2
MWST- Tax, condition table: Select country-Departure-Generate and FTXP: Maintain Tax.
Header condition: Header condition is the condition which is applicable to all the line items in the
sales document.
HA00: Header discount%
HB00: Header fixed amount
HD00: Header fright
HM00: Order Value
a.Header condition should be always processed manually
b.Header condition doesn’t have access sequence
C.It is always placed between base value and gross value.
Group condition: If we check this header condition amount will be distributed among all the line
items in proportionate to value of the line item.
If we unckeck this then header condition amount will be proposed to all the line item in sales
document.
HA00: Header discount%, it is group condition as well as header condition
HB00: Header fixed amount, it is group condition as well as header condition
HD00: Header fright, only header condition
HM00: Order Value, it is group condition as well as header condition
Header fright condition: Fright condition type should be always placed between gross value and net
value. It is only applicable for header condition.
Order value: We use HM00 if we want to change total order value manually in sales document.
Statistical condition type: Any condition type if it is statistical then it will have two effects.
a.The value of condition type will not have any effect on net value.
b.The value of condition type will not be posted into accounting.
VPRS: The cost of the product which we maintain in material master, Accounting 1 view will be
determined into sales document with the help of “VPRS” condition.
SKTO: Cash discount, We maintain cash discount % in define payment terms, that cash discount%
will be determined into sales document with the help of SKTO condition type.
KUMU: Cumulative condition: It will be used in only BOM concept, KUMU condition type will help to
cumulate the value of components and display the value in main item.
Rebate condition:
a. Group Rebate: Condition type: BO01
b. Material Rebate condition type: BO02
c. Customer Rebate condition type: BO03
d. Independent sales value: condition type: BO06
Intercompany condition type: PI01 is intercompany price (amount) condition types determine in
intercompany sales order.
PI02 is intercompany percentage
IV01 is intercompany price condition type determine in intercompany invoice.
IV02 is intercompany percentage
Some more condition type:
EDI1-Customer expected price
EDI2-Customer expected value
AMIW-Minimum sales order value
AMWZ-Minimum value surcharge
Exclusion Group: Grouping of multiple condition type into one and allow the system to propose best
discount or the least discount.
Configuration:
IMDG-SD-Basic functions-pricing-Pricing condition exclusion-condition exclusion for group of

condition-define condition exclusion group:Z001
Assign condition exclusion group: exclusion group(Z001) condition type(ZR00)
Maintain condition exclusion for pricing procedure:
S.No(01) Cont excl pro(A) Exclusion group1() Exclusion group2()
Condition exclusion procedure:
A-Best condition between condition type
B- Best condition with condition type
C-Best condition between two exclusion groups
D-Exclusive
E-Least favourable with the condition
F-Least favourable with the exclusion groups

L-Least favourable with condition types
Condition supplement: When Business wants to give certain discount irrespective of customer and
material till certain period, then we can map the business scenario with condition supplement
feature.
Step 1: Define new pricing procedure and include conditions that are going to participate as a
condition supplement for base price.
PR00,K004,K005,K007
Step 2: Assign new pricing procedure in condition type
Step 3: VK11:PR00 and select line item and go to ---condition supplement –Maintain condition
records for K004,K005,K007.
Step 4:VA01 raise sales order, you can check whether our condition supplement exit or not.
Group condition: If we check group condition then group condition amount will be distributed
among all the line items in propionates to the value of line item.
a.If we want to consider total document value then maintain group condition routine as “1”
b.If we want to consider group of materials value then maintain group condition routine as “3”
Ex 1: Configuration for group condition total document value:
The client requirement is any order if the total document value reaches 1000000 then they want to
propose 20000 discount.
Step1: condition table: Sales organization-generate
Step 2:Access sequence: click on exclusive
Step3: Define condition type: calculation type(B), check group condition, Maintain group condition
routine(1), scale basis(B) Value scale –save it.
Step4: Pricing procedure: Placed condition type in pricing procedure
Step5: Assign pricing procedure determination
Step6: Maintain condition records:Vk11-condtion type-20000 and select this then go to scale and
click on and scale value is 1000000 save it
Go to Va01, you can check .
Ex 2: Group condition concept for group of materials:
The client requirement is they have 3 materials X,Y,Z. While creating sales order if these material
value reaches 1000000 then they want to offer 20000 discount.
Step1: condition table: Select Material pricing group-generate
Step 2:Access sequence: click on exclusive

Step3: Define condition type: copy K004,calculation type(B), check group condition, Maintain group
condition routine(3), scale basis(B) Value scale –save it.
Step4: Pricing procedure: Placed condition type in pricing procedure
Step5: Assign pricing procedure determination
Create X,Y,Z material in material master,sales org 2 view maintain pricing procedure(01)
Step6: Maintain condition records:Vk11-maintain -20000 and select this then go to scale and click on
and scale value is 1000000 save it
Step 7: VK11: Material X-10000,Y-10000 and Z-10000 save it.
Go to Va01, you can check .
Dump error: ST05,ST22
Configuration eror:SCAT
FBL5N
F-28
Business process:
1.Inquiry(IN): whenever Customer inquiry about the product, we create inquiry doc in SAP.
Ex: Phone ,Email, walk-in,website,tender notice etc.
2.Quotation(QT): After creating inquiry doc in SAP, in return we create quotation doc with reference
to inquiry and send this quotation to customer.
Quotation doc consist of customer details, Material details,pricing, specification details,validity

details and terms & conditions.
3.sales order(OR):Finally if customer satisfy, he will place the order.
Order is an agreement between company and customer for supplying the goods to customer.
Sales order is consist of customer details, material details, delivery details, quantity details, pricing,
terms and conditions etc.
While creating sales order system will perform various activities in the background.
Partner determination, Availability check, TOR, Pricing, credit management, ouput determination,
text determination etc.
4.Delivery: In delivery we have 3 activities: Picking, packing and PGI.
When we do PGI system will perform various activities in background.
1. Stock update
2. Inventory Account document generates

3. It update in doc flow
4. It update in credit Management
5. It update in LIS
6. It update in Billing due list
5. Invoice: After PGI, we create invoice, and dispatch the goods to customer along with invoice copy.
When we create invoice, in the background system will perform various activities.
1. Revenue account document generates
2. Profitability account document generates
3. Cost centre document generates
4. It update LIS
5. It update Document flow
6. It update in credit Management
6. Return order (RE): Customer will return the goods if the goods are damaged, expire or defective.
Whenever customer finds damaged or defective goods, he will inform to sales office, sales office
people will send the employee to cross check the damaged or defective goods.
After cross checking sales employee will prepare return note.
After preparing return note, the employee will submit the return note to sales office. Then SAP end
user create return order with reference to invoice and Mention the reason for returns.
When customer delivers the return goods, we create return delivery with reference to return order.
We create return invoice with reference to return order.
7.Credit Memo request (CR): We use credit memo request, If we want to deduct the amount from
customer outstanding without receiving the goods back from customer.
Scenario: 1.Users mistakenly over charges the previous invoice,
The goods are totally damage in customer place and which are not in a position to take back.
Revenue A/C Dr………..Customer A/C Cr.
8.Debit Memo request (DR): We do debit memo request, If we want to add some amount to
customer outstanding without physical movement of goods.
Scenario: 1.Users mistakenly under charges the previous invoice
2.Charging interest to customer for late payment

Customer A/C Dr……………..Revenue A/C Cr
9. Invoice correction request (RK): We use this if end-user do a mistake in previous invoice, the
mistake can be overcharged or undercharged.
By using this invoice correction request, we can either deduct the amount from customer
outstanding or add customer outstanding.
10.Cash Sale(CS or BV): Cash sale process is also called as Counter sale process. i.e the customer will
walk into outlets, pick the materials and go to the customer, pay the cash, take the bill and leave the
counter.
11.Rush order(RO): Pay the money, pick the material and invoice later.
12.Free of charge Delivery(SD): Whenever we are sending sample to customers without raising
invoice then we do free of charge delivery.
13. Subsequent free of charge delivery (SDF): Replacing the goods to customer
Whenever customer returns the goods, we deduct the amount from customer outstanding. Instead
of deducting the amount from customer outstanding. if we want to replace the goods to customer
without charging then we do subsequent delivery free of charge.
14.Quantity contract(QC): It is an agreement between company and customer for supplying the
goods for a particular quantity within a specific validity period.
QC=VA41
15. Value Contract-WK1:
16.Value contract-WK2:
17.Scheduling agreement-SA:VA31:
18.Consignment Fill(CF): Consigning fill up is just dumping the stock at Consignment Agent place
without transferring ownership and without raising invoice.
CF KBN 631 E1
The effect of 631 is:
a.I will reduce the stock from unrestricted stock and stock will be added to consignment stock.
b.No inventory accounting doc generates because CF process is not relevant for invoice.
19.Consignment issue(CI): When consignment agent sell the goods to their customers then
consignment agent will inform to company.
CI KEN 633 CI
f. Stcok will be reduced from consignment stock and inventory A/C will generate.
g. Cost of goods A/C Dr to ……..inventory A/C Cr.
20.Consignmnet Return(CONR): When end customer returns the goods to Consignment agent , then
consignment agent will inform same to company , then we do consignment returns.
CONR KRN 634 DO
a. Stock will be reduced from Consignment stock

b. Inventory accounting document will generate and accounting entry is Inventory A/C Dr
to………..Cost of Goods A/C Cr.
21.Consignment Pickup(CP): If consignment agent request to take back the consignment stock, then
we do consignment pickup .When we do return delivery in consignment pickup , the stock will be
reduced from consignment stock and added back to unrestricted stock.
CP KAN 632 F1
The effect of 632 movement type is:
a.Stock will be reduced from consignment stock and added to unrestricted stock.
b.Inventory accounting document will not generate because CP is not relevant for invoice.
22.Third party sales(SD+MM):
Scenarios:
a. Stock is not available,
b. not manufacturing these products
C. Problem in manufacturing unit
1.Third party sales with shipping notification:
Item category: TAS
Item category group: BANS, material type: HAWA
Billing relevance F control that 3rd party without shipping notification, If MIRO is not created then
system will not allowed to create invoice to customer, Item category TAS(order related billing
according to invoice quantity) is MIRO.
Billing Relevance G control that 3rd party with shipping notification, If MIGO is not created then
system will not allowed to create invoice to customer, item category TAS (Order related billing
according to Delivery quantity) is MIGO.
Create PO automatically: If you maintain ALE data for purchase order in sales organization, while
creating sales order in 3rd party and IPO, system automatically generate purchase order.
In Schedule line category: CS

Order type:NB: It will be help to generate purchase requisition automatically in the background
while creating sales order in 3rd party.
Item category(5): Item category 5 control that even we do MIGO in 3 rd party with shipping
notification system will treated as dummy MIGO and stock will not be update.
Account Assignment category(1): It control that whether to generate inventory accounting

document or not while doing MIGO and PGI.
Copy Control order to invoice(OR-F2) :Billing quantity F and it will help to copy the quantity from
MIRO to invoice while creating invoice to customer in 3 rd party.
Billing quantity E and it will help to copy the quantity from MIRO to invoice while creating invoice to
customer in 3rd party.
3rd party without shipping notification: XD01>MM01>VA01>XK01>ME21N>MIRO>VF01
In VF01,reference quantity will copy from order, but actual quantity will copy from MIRO.
T.code: Table:SE16N.
3rd party with shipping notification: XD01>MM01>VA01>XK01>ME21N>MIGO>VF01
3rd party return order:
Item category group TASG,copy control RE-RE, copy requirement as (28) VBRK/VBRP:002
Billing quantity (F) plus/Minus(+),pricing type (D).
23.IPO: XD01>MM01>VA01>XK01>ME21N>MIGO>MIRO>VLO1N>VF01
Sales order-purchase order-Goods receipt-Invoice receipt-Delivery-invoice to customer.
Requirement type KEB,special stock indicator is E.
Requirement class is KEB
Item category is TAB(Billing relevance is A), Item category group is BANC.
Schedule line category is CB(Movement type(601),order type is NB, Item category (0), Account
assignment (E),check item relevant for delivery and purchase requisition delivery scheduling)
24.Make to order: When customer place the order with own requirement, will start the process of
Manufacturing of products.
Configuration:
1.XD01
MM01:Item category is 0001.Strategy group is 20(MRP3)
VA01: Check Requirement type is KE in procurement tab. Requirement class is 40.
Item category is TAK and Special stock indicator is “E”, controls that after manufacturing finished
goods the stock will be reserved to particular sales order number.
Account assignment category “E: control that when we take finished goods in stock and we do
delivery in MTO then accounting doc will not generate.
VA01>MB1C>MMBE>VL01N>VF01
25.Stock Transfer order:
A. Intra company STO process: Transferring the stock from one plant to another plant within the
company. It is transfer from Depot to Depot.
One step process: Receiving plant will raise PO to supply plant, Supplying plant will do delivery with
reference to PO, stock will be added to receiving plant.
Two steps process: Receiving plant will raise PO to supplying plant, supplying will do delivery with
reference to PO, Stcok will be showing as stock in transit, after doing MIGO, stock will be added to
receiving plant.
Configuration:
1.Receiving plant as customer in supplying sales area
2.Extended Material both plants with purchasing view
3.Define shipping data for plants: SPRO>MM>purchasing>PO>setup Stock Transport order>define

shipping data for plants
4.Assign delivery type and checking rule: we assign delivery type NL and checking rule B to the
combination of purchase order type UB and supplying plant.
5.Assign document type, one step procedure, under delivery Tolerance
Process 1: ME21N
2.VL01D: enter shipping point
.Check MD04 in stock
3.VOV7: Item category NLN: Maintain billing relevance D(Performa billing)
VOV8: Doc type (DL), maintain customer pricing procedure(A)
Copy control-VTFL-position(F8-NL)-maintain copy requirement(009)delivery related proforma

invoice for header.
4.VF01:Billing type F8
5.MIGO:
Check stock MD04.
Intra company STO Inter company STO

Movement type two step 641 643
Movement type One step 647 645
Order type/PO type UB NB
Delivery type NL NLCC
Item category NLN NLC
Schedule line category NN NC
Intra company Return STO Intercompany Return STO

Movement type two step 671 673
Movement type One step 677 675
Order type/PO type UB NB
Delivery type NLR NCR
Item category NLRN NCRN
Schedule line category NR NS
Two step: ME21N>VL10D>VF01>MIGO
One step:ME21N>VL10D>VF01>MIRO is not require
STO Return: ME21N>VL10D(without PGR)>MIGO>VL02N(PGR)
Intercompany STO: ME21N>VL10D>VF01(intercompany billing type IV)>MIGO
Inter STO Return:ME21N>VL10D>VF01(inter company billing type IG)>MIGO
IG-Inter company credit Memo.
26. Intercompany sales: Customer place the order to the company, If stock is not available ordering
company will send transfer of requirement to supplying company and supplying company will deliver
the goods to customer, send invoice to the ordering company, ordering company will raise invoice to
supplying company.
XD01>MM01>VA01>MB1C>MMBE>VL01N>VF01>VF04
Configuration:
1.create customer with ordering company company code, sales org or, distribution channel and
division.
2.Create Material Master with Finished Goods. And extended material both the plants.
3.Create internal customer with supplying company, sales org, Distribution channel and division.
4.Assign internal customer with ordering company sales organization: IMG-SD-Billing-Inter

company billing-Assign internal customer with ordering company sales org.
5.Assign Delivering plant with ordering company sales line:IMG-Enterprise Strcuture-Assign plant,
sales org and Division.
6.Create sales order:VA01-assign delivering plant in order. Check PI01 condition is determined or
not.
In pricing, maintain pricing procedure with PR00, Maintain condition records for PR00
Assign Supplying company sales area to pricing procedure ICAA01 with PI01,Maintain condition
records for PI01.PI01 is reference condition for IV01.
7.Delivery:VLO1N, Picking, packing and PGI
8.VF04: Raise invoice from supplying company to ordering company , IV01 condition type, reference
condition type is PI01.Biling type is IV, uncheck delivery related invoice, check Inter company billing.
9.VF01:normal invoice raised from ordering company to customer
1.Difference between Configuration and customization?
Configuration: It is the process of mapping your business process/requirements with already existing
SAP standards. i.e going in SPRO.
Customization: It is the process of mapping your business process with some changes(as per your
requirement) as against existing in standard SAP & there by developing your own customized
screens/reports i.e Z reports.
Customization is oftenly termed as a development or developed report(Z report). S
2.Difference between Invoice and billing doc?
Ans: Invoice is a document indicating to deliver goods and Billing is receipt of payment.
Bill means we have to pay the amount against bill invoice means we have to receive the amount
against the invoice.
3.Difference between alternative calculation type and base type?
Profit margin:11: Alt cal
Gross weight 12 & Net weight 13: Alt base type,
Conditional base value: When a value is derived for a condition type, based on certain calculations
this value is taken as base.
Condition value: For the number of units ordered depending on the condition amount mentioned
this value is derived.
4. Difference between Performa invoice and normal invoice?
Answer:
Performa Invoice:
 Performa invoice is a document that is used for the documentation purposes.

 This is the mirror image of the original invoice that would be created in future date.
 Performa invoices are used in export businesses for documentation purposes before goods
movement, but the original invoice will be created during goods movement.
 Goods issue is not required before you created a delivery related pro forma invoice.
 You can create as many pro forma invoices as you like for a sales order or a delivery
because the billing status in the sales or delivery is not updated.
 Data from the pro forma invoice is not passed on to financial accounting.
 It is generally created in Export sales and mainly in STO.
 Exmaple:Quotation
Normal invoice: Which is issued by the sellers to the buyer to request payment of goods
delivered.
5.Difference between GL accounts and reconciliation account?
GL: Ledger account
Reconciliation: Sub Ledger account
6.Difference between Accounting key and accrual Key in Pricing procedure?
Accounting Key: Different type of GL account, posting amount to revenue account
Accrual key: Different type of GL accounts for accrual or provisional, which are posting certain type
of rebate accurals.
Accrual accounting which requires recording revenues when they are earned and not when they are
received in cash, and recording expenses when they are incurred and not when they are paid.
Rebate: Return of a portion of a purchase price by a seller to a buyer, usually on purchase of a

specified quantity or value, of goods within a specified period
7. Difference between rebate and discount?.
Discount: Discount is the reduction offered by a seller to the buyer from the purchase price of goods
or services.
Rebate: Rebate is refund or return of currency value that a seller of goods provides to the buyer for
various different reasons. To promote high quantity purchases or receive early payments before a
certain due date.
8.Difference between Direct and Indirect Tax?
Direct Taxes are non-Transferable taxes paid by the tax payer to the government and indirect Taxes
are transferable taxes where the liability to pay can be shifted to others.
Direct Tax: Income Tax,corporate tax,wealth tax and inheritance tax
Indirect Tax: VAT , those paid by consumers when they buy goods and services.GST,sales Tax,Service
Tax,Custom Duty, Excise Duty.
9.Difference between Provisional accounts and accrual ?

Provisional accounts: Provisional means that something is conditional or interim or subject to change
or alteration. Therefore , the provisional financial statement are one that is subject to change. Ex
Bad Debts, sales allowances and inventory obsolescence.
A provision is an amount that you put in aside in your accounts to cover a future liability.
In accounting, accrued expenses and provisions are separated by their respective degrees of
certainty, All accrued expenses have already been incurred but not yet paid. By contrast, provisions
are allocated toward probable, but not certain, future obligations.
Determinations:
1.Item category determination: Sales doc type+Item category group+item uasage+Higher level item
category
2. Schedule line category determination: Item category+MRP type
3. Pricing determination: Sales area+customer pricing procedure+doc pricing procedure
4. Shipping point deter: Shipping condition+Loading group+plant
6.Storage location: Shipping point+ Storage condition+plant(Mala)
7. Storage Location: Situation+storage condition+plant(Reta)
8.Credit control area determination: Company code+credit group+risk category
9.Route determination: Departure zone of shipping point+shipping condition+Transportation

group+Tranportation zone or destination point.
10.Account determination: Chart of accounts+sales org+customer account group(Customer Master-

sales area-billing tab)+Material account group(MM-Sales org2)+Account key
11.Plant Determination: 1st- Customer material info records, 2nd Customer Master, 3rd Material
master.
12.requirement type determination: item category +MRP type
13. Business Area determination: Plant/Valuation area or sales area or Item division+Plant
14.Output determination: Output determination at sales doc level, delivery level, billing level
15.Warehouse determination: Warehouse number+plant+storage location
16.Availability check determination: Customer requested delivery date
17.Tax Determination:Destination country of ship to party+Departure country of Shipping point+Tax

classification for customer from customer master+Tax classification of material master
18.Batch Determination: Define condition table,Batch Determnation access sequence,Batch Strategy

type,Batch search procedure,Batch search Procedure activation.
Prerequisite for batch Determination process in MM:
1.Material must be Batch Managed (Purchasing view)
2.The Material should be classified with class

3.Batch level has to be set:Client/plant/Material level
ABAP :
SE11: Create table
SE38: ABAP Editor
SE37: Function builder
SE91: Create Message
SE93: Create T code
SE80: Functional group
SM30: Maintain table.
SE41: PF status
SE71:SAP Script
SE24: Class/Change display
IDOC: Transfer data from sap to non sap, sap to sap and non sap to sap.
Outbound IDOC:
1.Port create: SALE- Basic settings-Define Logical sys(T.code BD54)- create logical sys(SS800-Logical
systems 800)& (SS810-Logical sys810) and assign logical systems(Assign to 800 & 810)
2.RFC Destination:SM59-ABAP connection-create-Technical setting & loon security , click-remote

logon &connection text & save.-SSSS
3Create port-We21:Transactional RFC-create and enter(port no.A000000055)
4.BD64-DIstibution model-click on change-select Distribution model-create model view & save-add

message type(sender-SS800 & Receiver-SS810-Message-DEBMAS- you can see below row in
Distribution model, you can expend tree structure)-SSSS
5.partner profile:WE20: select partner type LS- click on create-SS810& save-go to outbound
parameter and enter message,port , basic type etc.
Inbound IDOC:
1.Go to 810 client,.WE20-partner profile- select partner type LS- click on create-SS800& save-go to
Inbound parameter and enter message type DEBMAS,Process code-DEBM
2.Go to 810 client,.WE42-Inbound process code-T codes-information purpose
BD10: Send material
BD11: Get Material
BD12: Send Customer
BD13:Get customer
BD14:Sned vendor
BD15: Get Vendor
BD16: Send cost center
BD17:Get cost center
BD87: Reprocess IDOC
3.Go to 800 client,BD12-To Transfer customer master data-customer no.195
WE42:
4.Go to 800 client,WE05-you can check IDOC status
5. Client 800,Se38: Do you have any error in IDOC, you can check here:SE38-BD74
We can reprocess error IDOC (status51) using program RBDAGAIN,BD87
Then process code, inbound process code is we42.
Where can you solve IDOC issue: BD64
BAPI: Business Application program interfaces: Transfer data from SAP to SAP, SAP to non sap, non
SAP. SE37.
1.Crate BAPI structure: SE11
2.
LSMW: upload data from only legacy system to SAP system, not possible to sap to sap, sap to non
sap
Master Data:
Customer Master: You can view customer list through transaction code VC/1.
Material Master:MM60
LSMW: Legacy system Migration Workbench:
T.code: LSMW
1.To create project name:Project name:ZSSSS & execute
2.Go to click on recording-VA01 etc-enter-click on default all & save
Process step: click on execute:
2.Maintain object attribute:Batch input recording click(VA01 will save)
3.Maintain source structure: click & change- create & save
4.Manintain Source field: enter fields and save
5.Maintain structure relation: change & save
6.Maintain Field mapping & conversion rule:select fields name & assign one by one
7.Maintain field value and transaction:
8.Specify file: click on Legacy and assign file and save
9.Assign file:click on assign file & save
10.
ABAP:
SE01-Correction & Transport req
SE09-Workbench organizer
SE10-Customizing organizer
How to change package name of an object:SE38,SE11- Go to from menu-Object dictionary entry-

display and change icon-package no-create the TR by pressing create request-click yes.
GST Configuration:
1.Assign Tax Procedure to country: OBBQ
2.Define Tax Access sequence: OBQ2
3.Define condition types(Tax):OBYZ(CGST,UGST,SGST,IGST)
4.Create Account Keys:OBCN
5.Define Tax Procedure:OBQ3

6.Assign GL to account keys & GL:OB40
7.Create Tax codes in country IN:FTXP
8.Maintain Tax codes for excise duties using condition technique:SM30 table:J_1ICONDTAX
9.Maintain Tax condition Records:FV11
Tax ID G2 cannot be checked(there are Several/no tax records)
Message no.VK242.
This is because we did not maintain any Tax percent Rate in FTXP.This will not affect tax
determination in PO.
Tax conditions for USA:UTX1,UTX2,UTX3
Copy Control: VOFM: Copy controls are used when we are creating a document with reference to
another document.
Purpose of copy control:
 It will help to copy the data from source document to target document.
 It controls whether to create a document with reference to another document or not.
Sales doc to sales doc:VTAA
IN-QT,QT-OR,RE-SDF,OR-RE,QC-OR,WK1-OR,WK2-OR
Sales doc to Delivery doc:VTLA
OR-LF,RE-LR,CF-LF,CI-LF,CP-LR,COND-LR,DL-LO,FD-LF,RO-LF,CS-BV,DS-LF,SDF-LF
Sales doc to Invoice:VTFA
CS-BV,RE-RE,CR-G2,DR-L2,OR-F2,OR-F5
Delivery to Invoice:VTFL
LF-F2,LF-F8,LO-F8
Invoice to sales doc:VTAF
F2-RE,F2-CR,F2-RK
Invoice to Invoice:VTFF
F2-S1
1.VTAA (Sales to sales)
Copy requiremnets(001):Header same customer
002-Header different customer

003-Material reservation
21-Billing Header
302-do not copy item
303-Always an Item
501-Scheduled quantity
() copy item
() complete reference
2.VTLA:
Copy requirements (003): Delivery to invoice standard req
Same all req
Requirement 11-without PGI, we can do invoice.
3.VTFA:
Header:
Copy requirement(001)-Header/Order related
002-Item/order related
003-Header/Delivery related
004-Delivery related item
005-cancellation Header
006-Cancellation item
007-Header/order proforma invoice
008-Item/ order proforma
009-Delivery rel proforma Header
010-Delivery rel proforma Item
011- Header/Delivery related W/O GI
012-Order related/third party item
14-Header Delivery rel Intercompany Billing
15-Item Delivery rel intercompany Billing

016-Invoice list
Reference number()
A-Purchase order
B-Sales order number
C-Delivery number
D-External delivery number
E-Current Billing document number
F-External delivery number if available.
Assignment number()
A-Purchase order number
Same as above.
() Copy item number: System indicate copy the item number from source doc to target doc
Item:
Copy requirement(012) In order to Billing the item to copy requirement is(012)
Data VBRK/VBRP(001):
001-Invoice split
002-Order related Credit Memo req
003-Single invoice
005-Intercompany billing
Billing Quantity(F):
C-Order quantity
D-Delivery quantity
E-Goods receipt quantity less invoice quantity
F-Invoice quantity less invoiced quantity
Pricing type():
A-Order quantity less invoiced quantity
B-Delivery quantity less invoiced quantity
D-Copy pricing elements unchanged

G-Copy pricing elements unchanged and redetermine tax
Business Process:
SAP SD :
Customer Groups: Domestic Customer, Export Customer,Modern Trade,
GSK Pharmaceuticals:
GlaxoSmithKline plc (GSK) is a British multinational pharmaceutical company headquartered
in Brentford, London.[3] Established in 2000 by a merger of Glaxo Wellcome and SmithKline
Beecham, GSK was the world's seventh largest pharmaceutical company as of 2015,
after Johnson & Johnson, Pfizer, Novartis, Merck, Hoffmann-La Roche and Sanofi.[n 1][4]
Pharmaceuticals[edit]
GSK manufactures products for major disease areas such as asthma, cancer, infections,
diabetes and mental health. Its biggest-selling products in 2013
were Advair, Avodart, Flovent, Augmentin, Lovaza, and Lamictal; its drugs and vaccines earned
£21.3 billion that year. Other top-selling products include its asthma/COPD inhalers Advair,
Ventolin, and Flovent; its diphtheria/tetanus/pertussis vaccine Infanrix and its hepatitis B vaccine;
the epilepsy drug Lamictal, and the antibacterial Augmentin. [7]:220
Medicines historically discovered or developed at GSK and its legacy companies and now sold
as generics include amoxicillin[73] and amoxicillin-clavulanate,[74] ticarcillin-clavulanate,[75] mupirocin,
[76]
and ceftazidime[77] for bacterial infections, zidovudine for HIV infection, valacyclovir for herpes
virus infections, albendazole for parasitic infections, sumatriptan for migraine, lamotrigine for
epilepsy, bupropion and paroxetine for major depressive
disorder, cimetidine and ranitidine for gastroesophageal reflux
disorder, mercaptopurine[78] and thioguanine[79] for the treatment of leukemia, allopurinol for gout,
[80]
pyrimethamine for malaria,[81] and the antibacterial trimethoprim.[79]
Among these, albendazole, amoxicillin, amoxicillin-clavulanate, allopurinol, mercaptopurine,
mupirocin, pyrimethamine, ranitidine, thioguanine, trimethoprim and zidovudine are listed on the
World Health Organization's list of essential medications. [82]
Malaria vaccine[edit]
In 2014, GSK applied for regulatory approval for the first malaria vaccine.[83] Malaria is
responsible for over 650,000 deaths annually, mainly in Africa. [84] Known as RTS,S, the vaccine
was developed as a joint project with the PATH vaccines initiative and the Bill and Melinda Gates
Foundation. The company has committed to making the vaccine available in developing
countries for five percent above the cost of production. [9]
As of 2013 RTS,S, which uses GSK's proprietary AS01 adjuvant, was being examined in a
Phase 3 trial in eight African countries. PATH reported that "[i]n the 12-month period following
vaccination, RTS,S conferred approximately 50% protection from clinical Plasmodium falciparum
disease in children aged 5-17 months, and approximately 30% protection in children aged 6-12
weeks when administered in conjunction with Expanded Program for Immunization (EPI)
vaccines."[85] In 2014, Glaxo said it had spent more than $350 million and expected to spend an
additional $260 million before seeking regulatory approval. [86][87] A second generation malaria
vaccine is being evaluated in Phase 2 clinical trials. [88]
Consumer healthcare[edit]
GSK's consumer healthcare division, which earned £5.2 billion in 2013, sells oral healthcare,
including Aquafresh, Maclean's and Sensodyne toothpastes; and drinks such as Horlicks, Boost
and a chocolate-flavoured malt drink sold in India. GSK also previously owned
the Lucozade and Ribena brands of soft drinks, but they were sold in 2013 to Suntory for
£1.35bn.[55] Other products include Abreva to treat cold sores; Night Nurse, a cold remedy;
Breathe Right nasal strips; and Nicoderm and Nicorette nicotine replacements.[89] In March 2014 it
recalled Alli, an over-the-counter weight-loss drug, in the United States and Puerto Rico because
of possible tampering, following customer complaints.[90]

SAP Introduction: Packages, Languages, ERP Components, Architecture, and Key Tables

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Introduction: Packages, Languages, ERP Components, Architecture, and Key Tables

Uploaded by

Copyright:

Available Formats

SAP Introduction:

Package: It is a collection of executable programs, functions and actions.

Ex: SAP, Oracle, People soft, JD Edwards, BAAN,SIBEL etc.

Enterprise-Well established organization

Single Tier Architecture: Standard system: ex:PC

Two Tier Architecture: Client-Server: Multi Viewer concept developed by IBM.

Data Base layer

Three Tier architecture: Data base, Application & Presentation

Data base server

PC1 PC1 PC1 PC1 PC1 PC1 PC1 Client

Functional: SD,MM ,FI,CO,PP,PM,HCM

BASIS: Trouble shooting, Network Administration

Technical: ABAP, Advance Business Application programming

ÐzzzáSAP SD Tables and Structure:Table view t code(SM30,SE54/55/56/57)

VBAK Sales Document: Header Data

VBAP Sales Document: Item Data

VBKD Sales Document: Business Data/Sales district data

VAKPA Partner index

VBFA Document Flow

VBAKUK Sales Document: Header and Status Data

VBUP Sales Document: Item Status

VBUK Header Status and Administrative Data

VBBE Sales Requirements: Individual Records

VBBS Summarized requirements

VBUV Incompletion log

VBLB Forecast delivery schedules

VEDA Contract Data

VBKA Sales activity

LIKP Delivery Document: Header data

LIPS Delivery Document: Item data

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

VBRK Billing: Header data

VBRP Billing: Item data

KNA1 Customer Master: General Data

KNB1 Customer Master: Company Code Data

KNB4 Customer Payment History

KNB5 Customer Master: Dunning data

KNBK Customer Master: Bank Details

KNBW Customer Master: Wwithholding tax types

KNKA Customer Master: Credit Mgmt.

â Customer Master: Credit Control Area Data - credit limits

KNVA Customer Master: Loading/Unloading Points

KNVD Customer Master: Record sales request form/documents

KNVH Customer Hierarchies

KNVI Customer Master: Tax Indicator

KNVK Customer Master: Contact Partner

KNVL Customer Master: Licenses

KNVP Customer Master: Partner Functions

KNVS Customer Master: Shipping Data

KNVT Customer Master: Record Texts for Sales

KNVV Customer Master: Sales Data

KLPA Customer/Vendor Link

MARA General Material Data

MVKE Sales Data for Material

MARC Plant Data for Material

MARD Storage Location Data for Material

MAKT Short texts