SAP SD

Install > Connections

Prerequisuites:-
 Gear > Options > Interaction design > Visualization >
”Show keys within dropdown list”
 Extras > setting > display technical names

OTC cycle

Inquiry:-
 Walmart(Buyer) wants to purchase some laptops from Dell
company,they will raise a RFI(Request for Information) to Dell.
 Dell in return will file a Inquiry, that will contain details like
Quantity, start date, price etc.This will generate a Inquiry
number which we will send it to the buyer.

Quotation:-
After an inquiry is send to Walmart, if Walmart agrees with the
inquiry they request for a Quotation from Dell wrt inquiry number.

Inquiry vs Quotation

Inquiry
 Informal
 No Terms and condition/promises
Quotation
 Formal
 Terms and condition(adhered to legally)
 Validity dates

Presales
Inquiry(VA11):-
VA11 | Logistics>Sales and Distribution>Sales>Inquiry>Create
 Initial screen> Inquiry type, Org data(Sales Org, Distribution
channel, Division)
 Overview > S2P, S2P, Item overview(Material, Qty)

Quotation(VA21)
VA21| Logistics>Sales and Distribution>Sales>Quotation >Create
 Initial screen> Quotation type, Org data(Sales Org,
Distribution channel, Division)
>> Create with reference > Inquiry, copy, validity(to, from dates)

Sales Order Flow

Walmart want the product so they will create a purchase order, Dell
on other hand will create a Sales Order, and after that generate an
Purchase Order Number and send it to Walmart.

SO Hands On:-
VA01 | Logistics>Sales and Distribution>Sales>Order >Create
 Initial screen> Order type, Org data(Sales Org, Distribution
channel, Division)
>> Create with reference > Quotation, copy, validity(to, from
dates)>Save

2
VA03 – Display Document > Document Flow

Delivery:- 21/11
Del creation date,
Types – Picking, Packing(optional), PGI
1. Picking – Goods are picked and loaded from the inventory
2. PGI(Post Goods issue) - Goods are accounted for.

Hands-on:-
Delivery from Order number
VA01 > sales document > Deliver
Error:-

Fix:- Goto VA02 > Select line item > Schedule line items
Copy the date

3
Header > Sales Document > Deliver > Change dates(future date)
Delivery create|Overview = Picking tab > Del Qty = Picked Qty;
PGI>Save> 800..

4
Billing(Invoice):-

VF01/ Logistics|Sales|Billing|Billing Document|VF01 Create Billing

Create Billing Document | enter document number > Enter
Invoice(F2)> save . Eg 900..

Master Data 22/11

 Customer= SD
 Material= MM
 Vendor= MM
 Pricing= MM,SD,CRM
 Asset= Fi
 Condition records

# Master data vs Transactional data

Master data Transactional data
 Permanent Transient
 Used again & again Time bound
 Changes very little

5
Customer Master:-
 Sales Data = VD01
 Finance Data = FD01
 General view =

VD01_CreateCustomer >
Initial screen
 Account group – 000,1Customer - 56789
 Sales Area – sales org, Dist chn, Div
General data =
 Address
 Contact person
Sales area data =
 sales- customer group, currency,
 shipping - shipping conditions, order combination, max partial
deliveries, over del. Tolerance, complete delivery
 Billing – invoice dates, invoice list dates, incoterms, tax
classification
 Save

FD01_Finance view of customer(Done by FICO)

6
  Customer,Company code >>
Account management = recon. Account(given by fico cons)

Some technical terms:-

1>Extension
 View – using already existing customer and creating another
view for it is called extending the view
 Org Data – using existing customer for different sales
org(VD01)
2>Create with reference

3>Field Changes
VD02> do some changes> save
VD02 > environment > account changes > all fields (we will get all
inf here about the changes)
4>Additional Data
Extras> additional data

7
Hover over a field > F1 > technical information > field name(find
out)
Cmod>Goto>Text enhancements>keywords>Change(field name)

Material Master
Lifecycle – creation, changes, transaction, discontinued(archived)
Departments – Sales, Purchasing, Quality, MRP(plans how many
items needs to be manufactured), Financial

Controlling Parameter:-
 Customer master = Customer A/C Grp
 Materials = Material Types(FERT – Finished goods, DIEN -
Service)
Create Material= MM01
Material, Industry type, Material type > View >
{Basic Data1, Sales 1,sales 2, Sales:General, MRP1,Storage
1,Accounting}
>Org level> (Plant, Stor. Location, Sales Org,Dis chan)>>

8
Basic data 1

 Description
 Mat Grp
 Gross weight – weight along with packaging
 Net weight
 EAN/UPC - European Article number, Universal Product code

Sales: Sales Org 1

 Basic unit of measure

9
  Sales unit
 Delivering plant
 Material Group
 Tax classification
 Min Order Qty, Min Del Qty >>Enter

Sales: General/Plant = Tran grp , Loading grp

MRP1 = MRP type

10
Accounting1 = valuation class, price control(standard price,
moving avg)
Save.

Extension – MM01

Material Master – Grouping and Categorization

Product hierarchy = 18 characters, mm01 >sales org 1 done using

ABAP customization
Sales org 2 > product hierarchy > click, select (next level) > click,
select (next level)

11
How to define own material group = spro > logistics > material
master > settings for key fields > new entries
How to define own material group(sales) = spro > logistics >
material master > settings for key fields > Data relevant to sales
and distribution > define material groups

Path = spro > logistics > Material master > settings for key fields >
data relevant to sales and distribution > Define product hierarchies
> Maintain product hierarchies > new entries
Add > save (back) start again 1111... add > save 11112222 repeat
Basic data 1 > product hierarchy > select + next level

Customer account group

Tcode – VD01_CreateCustomer
How to check customer account group = VD02 > Extras >
Administrative data
Path = Logistics – General> business partner > customers>
control> Define Account group and field selections for customers

>>every section has list of sections defined

12
  Suppressed means not visible.

 Ext means mandatory field

13
  If we don’t give sales area, then sales area data will not be
available in create customer:General data

Q.How to block Customer Master

 Defaultry in payments
 Compliance Issue
 Tcode: VD05- to block a customer
Enter Customer, Sales Org, Distribution channel,Division > Order
Block(selected sales area), Delivery Block, Billing Block

14
->Order block must be assigned to a sales document type.

 VD06 – to mark a customer for deletion

 Can we delete a customer? No. But we can archieve the
customer(flag for deletion- VD06)

Sales Order - Deep Dive

15
Part1:-
Structure of Sales Document
Sales Document/SO - could be QT,IN,OR,Con etc..
Header, Line Items, Schedule Line Items

In document header we have sales, shipping, Billing

document,payment cards.
 Schedule line items represents schedule of the delivery.
 Path to navigate to the line items
> Select line items > Schedule line items button
> Goto > Header, Item.

Order Number(S) PO Number(P)

Typically numeric Purchase Order Num
Set to auto increment Given by Customer
Used for unique identification Cust used for Ref

Net value – Total value of sales Order

PO Date – Used in backdate, creation date <> Po date

16
Buyer(Req) > Reseller(Sold To,Ship To, Payer, Bill To 2X) >
Distributor(S2P...) > Seller(S2P...)

Part 2:-
Header > Sales > Req deliv date, Complete div, Deliv block,
Billing block,
Billing Block = To ensure that proper deliv is done.
Creation date(Unchangable), PO date, Deliv date, Pricing date
Inco terms(International Commerce terms):-
 Freely definable
 Specifies title transfer
 Specifies transportation and shipping terms
 Has 2 parts= standard inco terms
 Example= CFR(cost and freights), CIF(cost insurance
freights), EXW(from plants),FOB(Free on boards)
Payment Term
 Determines How seller will get payed
 Configured by FICO consultant
 Example = payable immediately, within x days

Part 3:-

Reason for rejection:-

 Delete line item is not a preferred way.
 Goto reason for rejection tab, select line items and give a valid
reason for rejection.
Document Flow:-
Allows navigation to any documents >> Q > SO > Del > Invoice
C.S.O > Shipping > Order Combination

17
  Order Combination:- CSO > Shipping, used to combine
multiple orders
 Text – extra pieces of information, that can flow from master to
transactional data and from one transaction to another
transaction.
 Additional data is created by ABAP consultant, we can put
things in brackets
Q>Can we delete Sales Order? Yes
Sales document > Delete, but not in case of consequent document.
Q>Why is data replicated between Header and Line Items?
Data can be over-ridden at line item level.

Enterprise Struture
To represent the structure of company in SAP
 Company and company codes:-
SD -> Sales, finance and logistics
Finance =
Highest Org Lvl = Company, each company has legal entity(ofc in
diff countries) called company codes.
Company does accounting ar company codes level.
Sales =
Highest level in sales = Sales Org represents sales policies in
particular geography or zone.(Pricing, returns ...)
One Company code can have one or more than one sales org.
Sales Org -> Dist Channel, Division
1. Distribution channel – determines how to sell the
product(direct/agencies)
2. Division – Represents a group of products for the purpose of
pricing, reporting etc
Sales area = Sales org + Dist Chn + Div -> Sales Office

18
Sales Offices(optional) = Sales office > Sales Group > Sales
Personnel
Logistics =
Highest level = Plants
 Plant is a place where goods are manufactured, services are
performed/evaluated.
 One company code can have multiple plants, but one plant
can be assigned to only one company code.
 Plant can have multiple storage locations.SL is a place where
goods of different kinds are stored.
 Sales Org + Distributional channel ->(assigned) Plant
 Warehouse Doors represents shipping point

Scenario:-

19
  Company and company codes will be made using FICO
consultant, as it requires GL account.
 Sales consultant will be created by Sales Org, Div, Dist
Channel, Sales Office, Sales Group
 Plant will be created by MM consultant.

Definition:-

Sales Org= spro > Enterprise structure > definition> sd > sales
org> copy,delete and delete sales org(don’t create new)
Assignment is the connection of the boxes
 copy,delete and delete sales org > copy (0001 – sales org
‘always’- west) > ok/create request(Transport request - TR) >
save
 Define sales org > position > details(button) > address(b)

Distribution channel = spro > Enterprise structure > definition> sd

> DC > copy,delete and check DC > choose > from 01 to AG

20
Division = spro > Enterprise structure > definition> Logistics
General > copy,delete and check Div > choose > from 01 to XR

Sales Office = spro > Enterprise structure > definition> sd > Sales
Office > copy,delete and check S.O. > copy/ new entries. Bay area

Sales Group = (same) consumables

Plant = spro > Enterprise structure > definition> Logistics General >
define, copy, delete plant > copy(b) > from 0001 to newj > create
request.
Define plant > choose > position > details > address

Storage location = spro > Enterprise structure > Material

management > maintain storage location
Plant – newj > select pre-existing or a new SL or delete preexisting

Warehouse(op) = spro > Enterprise structure > definition> logistics

execution> define, copy, delete warehouse number>copy>from001
to wh1

Shipping point(op) = spro > Enterprise structure > definition>

logistics execution> define, copy, delete shipping point> from 0001
to sens(sensitive eq)

Assignment:-
1>Assign Sales Org to company code=

21
Path = spro>Assignment > SD >
 Assign SO to CC > position > Cocd 1000
 Distribution channel to Sales Org (Delete unnecessary
assignments)
 Assign divisions to sales org (Delete unnecessary
assignments)
 Set up sales area > sales area > (Delete unnecessary
assignments)
 Assign sales office to sales area > sales area > delete
unnecessary entries and add new entries >Sales area>
Dis Chl, Div, SOff(baya)
 Assign sales group to sales office> sales office> new
entries> sales group
 Assign sales org, distribution channel, plant > sales
org,Mat,Plant (Delete unnecessary assignments)

Path= Enterprise structure>Assignment>Logistics Execution>

 Assign warehouse to plant/SL> plant > use existing
entries/new entries
 Assign shipping point to plant > find newj > check/assign

Goto SE01(Transport Organiser)> transport > Request status>

check-Modifiable, Release> Display- List of customization done

Common Distribution Channel and Divisions

*Common DC is for Customer/Mar, conditions & Material Master

22
Path = spro> Enterprise Structure> assignments> SD> set up sales
area> MBar selections > by content > sales org, Div (1000,00)> exists
but still we cant create customers?

Path= spro> Sales and Distribution > master data > define common
Distribution channel; Division
Common DC> position> sales org, DC>

DeRef -> Change the DCh-conds and CGH-cust to 13 for SOrg 1000
and Dch 13(3rd row).
Earlier since it was referring to 10 (DCh-Conds & DCh-Cust/Mt), we
were not able to create customer.

23
Create Customer > VD01
Condition records > VK11 > material with release status
Summary:-
1. Master data proliferation(creating master data for all sales area is
not necessary)
2. Common distribution channel and division
3. Only master data for S.Org/ Ref DC/ Ref Div

# Why is Enterprise Structure required?

 Reporting – sales, sales office/group > Company code= both
internally and externally
 Operational – coupon, discount
Both of these is done on Company code level.

#Sales document type 29/11

Business Process
Coal powerstation = consignment, contract
Software
Servers

Document type
Represents the characteristics of a business process.
In SD there are 3 business process involved :- Sales, Delivery and
Billing.
Categories
 Sales- Inquiry, Quotation, Order, Consignment, Contract
 Delivery- Regular D, Exp D, Returns
 Billing- Invoice, Credit, Debit, Invoice corrections
-> Doc type is all the variations possible in category type

Doc type template

24
It’s a place where all categories(S,D,B) are configured > SPRO.
Set of properties that define Sales Doc type.
 Sales:- Path = spro> img> SD> sales doc> sales doc header
>define sales doc type
 Delivery:- ..Logistics execution> Shipping> deliveries> Delivery
types
 Billing:- ..SD> Billing Documents> Billing types

Copy Doc Type

If we want to create our own doc type we create a copy from pre-existing
Doc type.
Change Doc type of Quotation > Copy >>

Namespace > ZHQT; Y,Z = Customer Reserved Namespace

25
Number Ranges
Int Number range (05) – system generates automatically within
certain range
Ext Number range (02) – user gives value manually
Path = spro > SD> sales> sales doc> Sales Document Header >
Define Number Ranges for Sales Document >>> view intervals, edit
interval, view status

Sales Doc type Configuration 1

26
General control:-

Click on the field/ press F1 to get help.

1>Reference mandatory:-

27
2>Check division=
02= no error
Create SO> F8 > Chk division
3>Check purchase order number= chk for duplicate PO number

Transaction Flow
Quotation messages = B-> Check at item level

Increase the selection date.

Sales document > Delivery > Administration > Delivery type

Shipping
 Delivery type = LF
 Delivery block = creates a field in create SO: initial screen.
 Shipping condition = overrides from customer master.
 Immediate delivery = system creates delivery without going
thru tcode VL04/ VL01N (rush Orders), “immediate delivery
block is set to A”.

Billing
 Del-rel billing type – invoice created with ref to Del
 Order-rel billing type- invoice created with ref to order
 Intercompany bill type – whn delivering plant belongs to other
plant

28
  Billing block – creates a field in CSO

Requested delivery date/pricing date..

Lead time in days= add working days in Req deliv date

#Bill of Material (BOM)

Top level part PC

Components

29
mm01- Material creation
Pc-101
1 Retail
Fert(Finished Mat), Dien(Service)
Basic data 1, sales org 1,2,General, MRP 1, General plant storage,
Accounting
Give org lvl details(plant SL, sales org).
 Basic data 1 = des, basic unit of measure, material group
 Sales: sales org 1 = Tax classification
 Sales org 2 = Item category group
 Sales General plant = Trans grp, loading grp
 MRP 1 = mrp type- nd
 Accounting 1 = valuation class, standard price

Check Mat in se16 > Mara table

Create BOM > CS01
Mat, Plant, BOM usage
Multi level BOM – Super BOM(hierarchies)
Components of PC –101 = Mon, CPU, EXT, PR, MP

30
Component of CPU – mem

Error:-

31
MM02> basic data> additional data> select language

VA01>
 Line items is controlled by Item Category(TAN)
 OR in germany is TA
 In quotation line items, QT is equivalent to AG(AGN)
Item category path= spro > img > SD > sales> sales document>
sales document item> define item category

32
Line items can be Bill Rel, Price Rel, Del Rel, Sch Line Rel

Structure scope=> A,B = explodes single/multi level BOM.

Steps =>
VA01>> if we put line items PC-101, item cat: TAN
1. To check TAN > spro > SD > sales > sales doc > sales doc
item> define item categories> select TAN> display view>
structure scope and application is not defined
2. Path> mm02 = pc 101> sales org 2> item category group is
set to NORM change to LUMF> save
3. Va01> enter MON 101, plant> error > click ok for all

33
4.mmo2>mon 101(do for all remaining material)> basic data>
additional data> enter lang de
5.Again va01 will work fine now> pc 101 will now explode to all
components but CPU is not exploded to Mem, becoz item category
is TAN, change to TAP or TAQ( structure scope= A, Application =
SD01). It is getting autoassigned.
 The controlling parameter in deciding Item category is Sales
Doc Type+ Item cat group+ HIgher lvl item cat+ usage
 Spro > img> sd > s > sales doc item> assign item
categories[V0V4]>position> Or,lumf >TAP (since for 1st
line item PC 101 is also TAP)

HL is higher Lvl Item. Select MON-101> F8

34
# Schedule line category
 A schedule line is a schedule of delivery.
 Schedule line tab contain requested Del date and expected
Del date.
 Schedule line category contains confirmed quantity and dates

Schedule line category controls

 Sales doc type config = V0V8
 Item Cat Config = V0V7
 Schedule line cat = V0V6
 Item category determination = V0V4

35
  Schedule line category determination = V0V5
V0V6 – Schedule Line Category

Delivery Block
 Doc type – Del block – blocks Del of entire order
 Schedule line category – Del block – block del of line items
 Item category – No del block

Movement type
 Represents a change in value
 Configured by MM consultant
 Movement type in SAP is a 3-digit code that is used to identify the
type of material movement in the system. The movement type is
used to determine the type of transaction being executed, such as
goods receipt, goods issue, transfer posting, or stock transfer.
 The movement type is an important part of the material
management (MM) module in SAP, as it helps to keep track of the
flow of goods in the system.

36
  To schedule line CP, set movement type as 601
 Steps= VA01> schedule line for item “button”(CP) > picked >
VL02N>PGI>Document flow
 The movement type that is conf in schedule line is used when
delivery is PGI, becoz that’s where change of value is happening.
3rd Party Scenario
3rd party drop ship – suppose a order came for US company code and
they don’t have the product, so they hired some vendor for them, who
will arrange the product and deliver it directly to the customer, so here
the vendor is the 3rd party who is doing the shipment.
 Item category=TAS, Schedule line cat = CS(doesnot have a
movement type), Order type=NB(Pur ord)

#Availability and Transfer of Requirement

37
Availability is the process to chk goods are available to be
delivered.
Availability can be turned on/off at Schedule line item level, if turned
on Sales order can be turned to MRP.
Transactional flow =
Requirement ~Demand = TOR(Tranfer of Requirement) = (Sales
Order to MRP)
MRP= Material requirement Planning.
 Purchase request – Purchase Order
 Planned Order – Production Order(Req to produce some
goods)

 Every sales order transfers Requirement to MRP

 Flow = VA01 > MD04(req are turned to MRP)

38
# Delivery Document and Billing Document type
Del document type = LF and LR
Del item category = TAN, TAP, TAS
Del Doc type=

Path= spro > Logistics execution >shipping> deliveries > define

delivery type/ define item category

Important Fields:-

39
  Define delivery type > LF >
 Document category = Del
 Number system= int, ext, item no. Increment
BOM only exist at sales document level, but whn it comes to del
BOM loses its heirarchy, it gets flattened out and gets converted to
delivery group(it groups the BOM together)
 Order Ref= Order Required
For for delivery we always need a sales doc ref(LF/LR) > VLO1N

Del Item Category

Path = same
Relevant for picking= Picking tab will be editable in CSO,or else
grayed out.
BOM items should not be picked as it is component but should be
delivered.

40
While del PC 101 wont show but while billing it shows up!
 TAD and TAS are service & 3rd party, both these items are not
relevant for delivery.

Billing
Path = spro > sd > Billing > Billing document
Important billing document types =
F2 – Standard Invoice
F5 – Order related proferra Invoice
F8 – Del related P Invoice
L2 – Debit Memo
G2 – Credit Memo
RE – Credit for return

Custom declaration @custom office = F8,F5 - at borders of country

we have to declare the value of the goods, here we create a
proforma invoice(dummy), not posted to A/C
Commercial/Tax Invoice = F2- gets posted in the account.
Flow = OR > LF > F2 >>
 CR > G2(Memo) “charged more to cust
 DR > L2(Debit Memo) “charged less
 RE > LR(VA01) > RE(Credit for returns) “return request

41
Flow = VA01- enter details - deliver > VL01N(change selection
month) - create subsequent order – create transfer order > VL02N
– PGI > VF01 – F2
Posting not done > VF02 > green flag > posting period not open>
use tcode OB52
Credit memo
 VF03 > click on line item > conditions > check for tax%
 VA01 > order type – CR > create with ref(always) > enter
Billing doc > overview screen > keep billing block empty >
dclick line items > conditions > give the price u want to return
in amount field >sales tab|order reason > sales document >
billing
Debit memo = VA01> dr.. Same procedure > billing
Return request = VA01 > re.. > deliver > billing

#Billing Configurations
Path= sales>Billing>Define billing types

42
Create billing type ZF88 >> create order > VF02 - billing type -
ZF88 > “No accounting document generated” > VF02 > flag
Cancel a invoice>>
VF02 > invoice number > Billing document > cancel > save

Invoice list>>
There will be a large list of invoices, each will generate separate
acct document. SAP in return will assign a separate reference
number to each document type.
We can mark customers to view Invoice list
> display customer > sales area data > Billing document tab >
InvoiceListDates > mark relevant option
1. How to create billing document?
2. Why are billing Documents used
3. Accounting documents
4. Invoice cancellations
5. Invoice Lists
6. Reference Numbers

Copy Controls – Possible Data flows

43
Requirement and data transfer
Copy Controls – Standard Requirement Routines
VTAA = position > targt(or) Source(qt) > display > copying
requirement= 001 dclick

Custom Routines:-
001 – 600= Standard SAP > Copy and create new routine
601 – 999= Custom> Possible to modify
To modify = VOFM > copying requirements > Orders > Create

#Pricing

44
Theory
Condition Technique – to handle all complex scenario in pricing
Theory
#Condition Technique
7 steps
1. Field Catalog = fields(mat, mat grp, cust, cust grp)
2. Condition table = subset of fields catalog
3. Access sequence = (mat+cust grp) + (mat+cust grp+Di
Chn) = 2 tables
4. Condition type= type of calculation(price, dis%, tax,
frieght)
5. Pricing procedure = all condition type come together
6. Pricing procedure determination = sales area +
DPP(document PP) + CPP(customer PP)
7. Condition record = easy access -> users

Configuration 11/12
Path= VOk0 ; Spro > img > sd > basic functions > Pricing >
Pricing control
Environment > condition table > field catalog|display
Condition type > access sequences(we access the condition
tables)
Condition type > Condition type > Definition = determines the
types of calculation, PR00

Configuration 2
Pricing Procedures – RVAA01
Determination is done on basis of : Sales Area,
DocumentPricingProcedure, Customer PP.

45
Doc PP = Sales Doc > Transactional flow > DPP
CPP = Customer Master > sales area data > sales tab > CPP
Condition type= VK11> PR00(condition type)> Mat, des, amt,
unit.
VA01 > select line item> coin icon > analysis tab

Pricing Hands On

 Create Customer > XD01> acct grp, comp code, sales area, reference cust >
customer created!
 DPP > VOk0> Pricing procedure > Doc PP > maintain > new entry > 7, des.
 CPP > VOk0> Pricing procedure > Cust PP >

Other Configuration=
New sales doc type
New Item category

Pricing hands-On Configuration

VOk0= environment > condition table > field catalog

46
*
 Condition table
 Access sequence
 Condition type
->Assign access sequence to condition type
 Create pricing procedure
 Assignments
 Vd02 > enter customer > sales tab > CuPP
 VOV8 > DoPP
 VOk0 > pricing procedure> new entries > sales area+CuPP+DoPP
-> Create condition records:- VK11
VK11 > ZS03 > key combination > mat/cust > enter different material and their
prices
Assign customer/group:- same way
-> Now test it
VA01 > input details > material line items > price will be taken automatically >
analysis

Pricing Procedure
VOk0> PP>position > RVA001> tree-control>copy the procedure> make new
Structure = Pricing. Discounts, Tax, Freights

47
Subtotals
To add values of multiple condition types, ex multiple discount on same product.
Suppose customer wants original freights + discount.
Most used subtotal = 1-6, we can also add combination from FRM-TO field.

Manual Flag (Manual discount)

Header condition type.
VA02 > Enter details > material line items > Pricing > analysis > add a manual
discount(RB00- already exists in cond type)

Required Flag
If we mark Pricing Procedure for PB00 in ZV0001 as required, and we don’t assign
value to it while making an order, an error will popup.

Statistical flag
It is not used in calculating the price, it’s a dummy condition type, it wont affect the
pricing.

Requirement Routine
It checks for requirement, suppose if Pricing assigned with 2, so the pricing will be
calculated

48
Alternate Calculation Routine
Cal type is a small routine that can be used to compute the value of a condition type.
Tax vendors = they ensure they have updated codes for all jurisdiction

#SD-FI Interface

49
Account Determination

 Comes under SD-FI integration like credit management

Types =
 Revenue
 Reconn

Dual Entry Accounting=

 The amount of credit and debit has to be equal.
 Every transaction needs to have equal amount of credit and debit.
During OTC, when is an account affected?

We initiate the account during delivery using the movement type, since it is linked to
account.

Account Determination – Scenario & Master Data

Condition type
Path = spro > sd > basic functions > account assignment/costing >revenue account
determination> check master data relevant for account assignment
VD02> enter customer > billing documents > accounting tab > acct assessment group > 01
MM02 > enter material > sales org 2 > acct assingment group > 01.
The source Is SD, so the revenue flow is in right buckets, based on the requirement of FI

50
Account determination Configuration
 We want to distribute our sales to different accounts according to certain
criteria.
Path = spro > sd > basic functions > account assignment/costing >revenue account
determination> define dependencies of revenue account > field catalog
>create table > select table > order reason> generate.
3. spro... define dependencies..>define access sequence..> copy ZOFI> Accesses > new
entries > check fields
4. define condition type> create condition> assign ConditionType to AccessSequence
5.Account determination procedure> procedures – ZOFI00 > control data- zofi(CT)
6. Account determination procedure – assignment > select billing doc type- F2 ,billing type -
ZJAR >
Change billing type, for ZJAR(Billing Type) assign KOFI00(AccountDeterminationProcedure)
7.Assign G/L account > select - table(790) - Order Reason>

VA01>
order type- ZRAJ, org data> overview page> save > document flow > select accounting
document >display document

Credit management

51
Types- Simple Credit Management,

52