SAP TERP10 Preparation

Presentation 9
Dr. Gbor Pauler, Associate Professor, Private Entrepeneur
Tax Reg. No.: 63673852-3-22
Bank account: 50400113-11065546
Location: 1st Szchenyi str. 7666 Pogny, Hungary
Tel: +36-309-015-488
E-mail: pauler@t-online.hu

Content of the presentation

7. Sales Scenario
7.1. Plot of Scenario
7.1.1. SD:Create Customer Master
7.1.2. SD:Create Product-specific condition
7.1.3. SD:Create Customer-specific condition
7.1.4. SD:Create Sales Order
7.1.5. PP:Manufacture Sales Order
7.1.6. SD:Create delivery
7.1.7. FI:Enter Incoming payment
7.2. SD:Organizational levels
7.3. Create Master data
7.3.1. DEF: Data sources of SD documents
7.3.2. SD:Create Customer Master:CName at Comp1000, SlsOrg1000,
Chn10, Div01:XD01
7.3.3. SD:Extend Customer Master:CName, Chn20:VD01
7.3.4. SD:Display Customer Master:CName:XD03
7.3.5. SD:Create Product-specific condition:MiniBike-Name:MM02
7.3.6. SD:Create Customer-specific condition:CName:VK31
7.4. SD:Sales order process
7.4.1. PROC:Order-to-cash backward scheduling milestones
7.4.2. DEF:Sales Order Document Flow by Milestones
7.4.3. SD:Create Sales Order:CName, 500PC MiniBike-Name, Plant1000,
SalOrg1000, Chnl10:VA01
7.4.4. MM:Check MRP Status:MiniBike-Name, BaseBike2-Name,
Plant1000:MD04
7.4.5. MM:Run MRP:MiniBike-Name, Plant1000:MD02
References
Object Symbols
GUI Symbols

7. Sales Scenario: 7.1.Plot of Scenario

7.1.Plot of Scenario
7.1.1.SD:Create Customer Master: CName
7.1.1.1.Organization: Company=1000, SalesOrg=1000,
Channel=10, 12, Division=00
7.1.1.2.Address: Mega Bike Gmbh. Customer-Name,
Stresemanstr.360, 22761 Hamburg, DE
7.1.1.3.Financials: VAT Reg.No.=DE123456789,
Account=140000, SalesDistr=000001(North),
ShipCond=01(Standard), Incoterms=EXW Hamburg,
PayTerm=0001(Immediate), Tax=1(VAT Assesible)
7.1.2.SD:Create Product-specific condition:
MiniBike-Name|Division=00: PR00: 1-499PC 2500EUR,
500PC- 2300EUR
7.1.3.SD:Create Customer-specific condition:
Customer CName:PR00: 1-499PC 2400EUR, 500PC2200EUR
7.1.4.SD:Create Sales Order:
Name-Order:500PC MiniBike-Name by customer CName

7. Sales Scenario: 7.2.SD:Organizational levels

7.2.SD:Organizational levels
7.2.1.Client
7.2.1.1.Company: Clnt:Comp = 1:m
7.2.1.1.1.Sales Area: Comp:SalAr = 1:m
Combination of:
7.2.1.1.1.1.Sales Org: SalOrg:SalAr = 1:m
Assigned to 1 company: Comp:SalOrg = 1:m
Negotiates Sales conditions (razsi kondci)
Carries responsibility for Customer recourse (Vevi visszru)
It has min 1, max any number of:
7.2.1.1.1.2.Distribution channel:SalOrg:Chn=1:m,Chn:SalAr=1:m
7.2.1.1.1.3.Division: Product or service group: Div:SalAr = 1:m
7.2.1.1.2.Plant: Comp:Plnt = 1:m
7.2.1.1.2.1.Storage: Can be assigned to one plant:Plnt:Stor=1:m
7.2.1.1.2.2.Shipping point: Can be assigned to more plants:
Plnt:ShipPnt = m:m
7.3.Create Master data
7.3.1.DEF: Data sources of SD documents
7.3.1.1.Customer master
7.3.1.1.1.TAB:General data
7.3.1.1.2.TAB:Sales area related
7.3.1.1.2.1.Partner functions:
Sold-to-party

7. Sales Scenario: 7.3.Create Master data

7.3.1.3.DEF:Customer-material info record (Vev rendelsi knyve)
FK:Customer
FK:SalesOrg
FK:Channel
FK:Material
FK:Customer material number
FK:Condition
Material description at customer
Shipping details
7.3.1.4.DEF:Condition master (Eladsi kondci adatok)
7.3.1.4.1.Price
7.3.1.4.1.1.Types
Material (Anyagr): calculated price of material in product costing
Customer (Fogyaszti): individual discount price for customer
Price list (Listar): base price modified by a factor at group of products
7.3.1.4.1.2.Can be specified by any combination of
Cust group|Customer
Material group|Material
Pricing group
7.3.1.4.2.Surcharge(Felr)
7.3.1.4.3.Discount(Diszkont)
7.3.1.4.4.Tax
7.3.1.4.5.Freight cost(Fuvarkltsg)
7.3.1.4.6.Incoterms
7.3.1.5.DEF:Output master (Papr-alap bizonylati adatok)
Electronic/paper documents send to external party:
Output type: Based on a given SAP doc
Media: EDI, fax, e-mail, etc, tools to send
Partner function to send to
Conditions to send at
Time periods to send
7.3.1.6.Customizing control tables

7. Sales Scenario: 7.3.Create Master Data: 7.3.2.Customer 2

Click
Click
Click
Click

C
Clliicck
k

C
Clliicckk

C
Clliicckk

7.3.2.SD:Create Customer Master:CName at Comp1000,

SlsOrg1000, Chn10, Div00:XD01
LO|SD|Master data|Business parners|Customer|
St
Complete
MM
e SD Create|XD01
7.3.2.1.SCR:Start
pXD01:
DDN:Account group = KUNA(Ext.Numb.Assig):
7. Create
Customer number/name is given manually!
3Customr
DDN:Customer = CName
.CName
DDN:Company code = 1000
Comp:
M
1000
DDN:Sales organization = 1000
aSalAr:
DDN:Distribution channel = 10
s1000/
DDN:Division = 00
10/00
tVD01:
7.3.2.2.SCR:Main
eExtend
7.3.2.2.1.TAB:Address
rCustomr
TBX:Name = Mega Bike Gmbh.
CName
TBX:Search term = Mega Bike
Comp:
d1000
TBX:Address = Stresemanstr. 360
SalAr:
a
TBX:City = 22671 Hamburg
1000/
t12/00
DDN:Country = DE (Germany)
aXD03:
7.3.2.2.2.TAB:Control
7. Display
TBX: VAT.Reg.No = DE123456789
3Customr
7.3.2.2.3.TAB:Payment transaction|KEY:Enter
.CName
7.3.2.2.4.TAB:Marketing|KEY:Enter
2
7.3.2.2.5.TAB:Unloading point|KEY:Enter
MM02:
.
7.3.2.2.6.TAB:Export data|KEY:Enter
Create
7.3.2.2.7.TAB:Contact person|KEY:Enter
Prod
7.3.2.2.8.BTN:Company code data
4
Spec
Condit
7.3.2.2.8.1.TAB:Account management
.
MiniDDN:Reconciliation account =
C
Bike140000(Trade recieveables domestic)
u
Name
7.3.2.2.8.2.TAB:Paym trans|KEY:Enter
>500PC
s
2300EUR
7.3.2.2.8.3.TAB:Corresponden|KEY:Enter
t
7.3.2.2.8.4.TAB:Insurance|KEY:Enter

Click
Click
Click
Click
Click
Click
Click
Click
Click
Click

CCli
licckk

7. Sales Scenario: 7.3.Create Master Data: 7.3.2.Customer 2

St

7.3.2.2.9.BTN:Sales area data

MM
e SD
7.3.2.2.9.1.TAB:Sales
DDN:Sales district = 000001(North)
pXD01:
DDN:Currency = EUR
7. Create
DDN:Price group = 01(Bulk customer)
3Customr
CName
DDN:Cust.price proc. = 2(Standard with
.Comp:
sales tax)
M
1000
7.3.2.2.9.2.TAB:Shipping
aSalAr:
1000/
DDN:Shipping conditions = 01 (Standard)
s10/00
DDN:Delivering plant = 1000
tVD01:
7.3.2.2.9.3.TAB:Billing documents
eExtend
DDN:Incoterms = EXW(Ex Works) Hamburg
rCustomr
CName
DDN:Terms of Payment = 0001(Immediately
Comp:
payable without deductions)
Click
Click
d1000
FRM:Taxes|COL:Tax
=
1(Tax
relevant)
SalAr:
a
1000/
7.3.2.2.9.4.TAB:Partner funct.|KEY:Enter
t12/00
7.3.2.2.10.BTN:Save(
)
a
7. XD03:7.3.3.SD:Extend Customer Master:CName, Chn20:VD01
LO|SD|Master data|Business parners|Customer|
3Display
.Customr Create|VD01 Sales and Distr
2CName 7.3.3.1.SCR:Start
DDN:Account group = KUNA(External assignment)
MM02:
.
Click
Click
DDN:Customer = CName
Create
Click
Click
Prod
DDN:Sales organization = 1000
4
Spec
Click
Click
DDN:Distribution channel = 12
Click
Condit
.
Click
DDN:Division
=
00
MiniC
Click
Click
Bike7.3.3.1.1.FRM:Reference
to
Click
u
Click
Name
DDN:Customer
=
CName
>500PC
s
DDN:Sales organization = 1000
2300EUR
t
DDN:Distribution channel = 10
o
DDN:Division = 00
m
7.3.3.2.SCR:Main
e
7.3.3.2.1.BTN:Save( )

C
Clliicckk

C
Clilicckk

Click
Click

C
Clilicckk
C
Clilicckk

7. Sales Scenario: 7.3.Create Master Data: 7.3.4.Display Customer

7.3.4.Practice:SD:Display Customer Master:CName:XD03

LO|SD|Master data|Business parners|Customer|Display|XD03
St
MM
e SD Complete
pXD01:
7.3.4.1.SCR:Start
7. Create
DDN:Customer = CName
3Customr
.CName
DDN:Company = 1000
Comp:
M
1000
DDN:Sales organization = 1000
aSalAr:
1000/
s10/00
DDN:Distribution channel = 12
tVD01:
DDN:Division = 00
eExtend
rCustomr 7.3.4.2.SCR:Main
CName
Comp:
7.3.4.2.1.BTN:Sales area data
d1000
aSalAr:
7.3.4.2.1.1.TAB:Sales
1000/
t12/00
Check DDN:Customer group = Empty: It should dentify a
aXD03:
7. Display
particular group of customers for the purpose of pricing or
3Customr
generating statistics
.CName
2
7.3.4.2.1.2.TAB:Billing documents
MM02:
.
Create
Check DDN: Terms of payment = 0001(Pay immediately
Prod
4
Spec
without deduction): it sets cash discount to zero and makes
Condit
.
Minipayment due immediately
C
Bikeu
Name
7.3.4.2.2.BTN:Company code data
>500PC
s
2300EUR
t
7.3.4.2.2.1.TAB:Account management

7. Sales Scenario: 7.3.Create Master Data: 7.3.5.Create Product-specific condition

7.3.5.SD:Create Product-specific condition:MiniBike-Name:MM02

LO|SD|Master data|Products|Material|Other|MM02 Change
St
MM
e SD 7.3.5.1.SCR:Start
DDN:Material = MiniBike-Name
pXD01:
7. Create
BTN:Select view|SCR:Views:SalesOrg1
3Customr
BTN:OrgLevel|SCR:OrgLevel
.CName
Comp:
DDN:Plant = 1000
M
1000
aSalAr:
DDN:SalesOrg = 1000
s1000/
10/00
DDN:Channel = 10 Valid only for this channel!
tVD01:
7.3.5.2.SCR:Main
eExtend
Customr
r
7.3.5.2.1.TAB:SalesOrg1
CName
Comp:
DDN:Division = 00
d1000
Quant Amount
aSalAr:
7.3.5.2.1.1.BTN:Conditions|SCR:Condition
PR00
1000/
t12/00
1
2500
DDN:Valid
from = Now
aXD03:
500
2300
DDN:Valid
to = 31.12.9999
7. Display
3Customr
FRM:Scales
CName

C
Clilicckk

7.3.5.2.2.BTN:Save( )
C
Clilicckk

.
2
MM02:
.
Create
Prod
4
Spec
Condit
.
MiniC
Bikeu
Name
>500PC
s
2300EUR
t

C
lickk
Clic
C
lickk
Clic

C
lickk
Clic
C
Clilicckk
C
Clilicckk
C
Clilicckk
C
Clilicckk

C
Clilicckk

C
Clilicckk
C
Clilicckk

7.Sales Scenario: 7.3.Create Master Data: 7.3.6.Create Customer-specific condition

7.3.6.SD:Create Customer-specific condition:CName:VK31

St
MM
e SD LO|SD|Master data|Conditions|VK31 Create
7.3.6.1.SCR:Main
pXD01:
7. Create
7.3.6.1.1.FRM:Left
3Customr
7.3.6.1.1.1.LIN:Prices
.CName
Comp:
LIN:Individual|DoubleClick
M
1000
SalAr:
a
7.3.6.1.2.FRM:Right
s1000/
10/00
7.3.6.1.2.1.FRM:Head
tVD01:
LIN:Cnty Sorg Dchl Cust Mater|BTN:New
eExtend
Customr
r
7.3.6.1.2.2.FRM:Item
CName
Comp:
DDN:SalesOrg
= 1000
d1000
Cond
Mat
Amnt Per Unit Valid from Valid to
aSalAr:
DDN:Channel
=
10
1000/
PR00 MiniBike-Name 2400 1PC
Now 31.12.9999
t12/00
DDN:Customer
=
CName
aXD03:
Quant Amount
FRM:Custmr/Material
with release
status
Display
7.
iicckk
1
2400
l
Customr
l
3CName
CC
C
Clliic
ckk
500
2200
.

Click
Click

MM02:
2
ProdSpec
.
Condit
MiniBike4
Name
.
>500PC
2300EUR
C
u
VK31:
CustSpec
s
Condit
t
MiniBikeo
Name
>500PC
m

BTN:Scales( )|FRM:Scales

7.3.6.1.3.BTN:Save( )

Click
Click
Click
Click

Click
Click
Click
Click
Click
Click

icckk
C
Clli

Content of the presentation

7. Sales Scenario
7.1. Plot of Scenario
7.1.1. SD:Create Customer Master
7.1.2. SD:Create Product-specific condition
7.1.3. SD:Create Customer-specific condition
7.1.4. SD:Create Sales Order
7.1.5. PP:Manufacture Sales Order
7.1.6. SD:Create delivery
7.1.7. FI:Enter Incoming payment
7.2. SD:Organizational levels
7.3. Create Master data
7.3.1. DEF: Data sources of SD documents
7.3.2. SD:Create Customer Master:CName at Comp1000, SlsOrg1000,
Chn10, Div01:XD01
7.3.3. SD:Extend Customer Master:CName, Chn20:VD01
7.3.4. SD:Display Customer Master:CName:XD03
7.3.5. SD:Create Product-specific condition:MiniBike-Name:MM02
7.3.6. SD:Create Customer-specific condition:CName:VK31
7.4. SD:Sales order process
7.4.1. PROC:Order-to-cash backward scheduling milestones
7.4.2. DEF:Sales Order Document Flow by Milestones
7.4.3. SD:Create Sales Order:CName, 500PC MiniBike-Name, Plant1000,
SalOrg1000, Chnl10:VA01
7.4.4. MM:Check MRP Status:MiniBike-Name, BaseBike2-Name,
Plant1000:MD04
7.4.5. MM:Run MRP:MiniBike-Name, Plant1000:MD02
References
Object Symbols
GUI Symbols

7.Sales Scenario: 7.4.SD:Sales order process: 7.4.1.Milestones

7.4.SD:Sales order process
7.4.1.PROC:Order-to-cash backward scheduling milestones
7.4.1.1.Pre-sales/CRM
7.4.1.1.1.Mailing campaign
7.4.1.1.2.Tracking lost sales
7.4.1.2.Sales Order
Sales Order Date
7.4.1.3.Availability check
Done at sales order date
7.4.1.3.1.Modes
01:Daily check
02:Individual reqirement: recommended for finished products
7.4.1.3.2.Scope
Current stock
Available To Promise (ATP)
7.4.1.4.MRP
Material Availability Date = Loading Date Max(Pick/Pack Time,
Transp.Lead Time)
(9.1)
7.4.1.5.Procurement
7.4.1.5.1.ALT:Production
Production Order Datei = Material Availability Datej Prod.Timei (9.2)
Where: i, j = 1..m components, j-main component, i-sub component
7.4.1.5.2.ALT:Purchasing
Purchase Order Datei = Mater.Avail.Datej Inbound Deliv.Timei (9.3)
Where: i, j = 1..m components, j-main component, i-sub component
7.4.1.6.Shipping
Transport Plan Date = Loading Date Transp.Lead Time (9.4)
Loading Date = Goods Issue Date Loading Time
(9.5)
Goods Issue Date = Required Delivery Date Transit Time(9.6)
Required Delivery Date
(9.7)
7.4.1.7.Billing

7.Sales Scenario: 7.4.Order process: 7.4.2.Document flow 1

7.4.2.DEF:Sales Order Document Flow by Milestones
All documents have header and item parts
They inherit data from each other through the process
One ascendant document can have multiple descendants (eg. 1 sales order can
generate more deliveries) formin a document hierarchy
7.4.2.1.Optional pre-sales documents
Contact
Inquiry
Quotation
Contract
Sceduling Agreement
7.4.2.2.Sales Order
7.4.2.2.1.Header
Reference to ascendent pre-salesdocument
Sales area
Customer Master
Shipping
Billing
7.4.2.2.2.Item
Material Master
Conditions
7.4.2.2.3.Schedule lines
Date, Quantity
7.4.2.2.4.Incompletion log
Mandantory fields set at customizing
Left empty by user
7.4.2.3.Shipping
7.4.2.3.1.Create Outbound Delivery:
7.4.2.3.1.1.Header:Can reference 1 or more sales orders
Shipping point
Due date
Ship-to-party
7.4.2.3.1.2.Item

7.Sales Scenario: 7.4.Order process: 7.4.2.Document flow 2

7.4.2.3.2.Picking:
7.4.2.3.2.1.Header
Can reference 1 or more outbound deliveries
Assign warehouse to delivery
Create Transfer Requests Transfer Order MM:Good movements
7.4.2.3.2.2.Item
Material, Quantity, Stock type/Area/Bin to pick from
7.4.2.3.3.Packing:Creates Shipping Unit hierarchy:
Container
Pallet
Carton
Can contain mutliple items from multiple deliveries
7.4.2.3.4.Goods issue posting:
MM: Re-run MRP
FI:Material stock account decrease
FI:Transfer data for billing due list
7.4.2.3.5.Transport planning
7.4.2.3.6.Shipment monitoring
7.4.2.4.Billing
7.4.2.4.1.Billing document:
FI:Increase Accounts receiveable
FI:Create invoice
FI:Track incoming payments
CO:Update reporting systems
7.4.2.4.1.1.Header
Reference to multiple deliveries
Destination country|Payer
Due date
7.4.2.4.1.2.Item
Material, Quantity, Value, Tax
7.4.2.5.Payment
7.4.2.5.1.FI:Update G/L accounts:
7.4.2.5.1.1.Debit: Payment,

7.Sales Scenario: 7.4.Order process: 7.4.3.SD:Create Sales Order

Click
Click
Click
Click

7.4.3.SD:Create Sales Order:CName, 500PC MiniBikeName, Plant1000, SalOrg1000, Chnl10:VA01

St
LO|SD|Sales|Order|VA01 Create
MM
e SD
7.4.3.1.SCR:Start
pVD01:
Extend
DDN:Order type = OR(Standard order)
Customr
CName
DDN:SalOrg = 1000
7. Comp:
DDN:DistChan = 10
31000
SalAr:
.1000/
DDN:Division = 00
212/00
7.4.3.2.SCR:Main
.XD03:
7.4.3.2.1.FRM:Head
-Display
Customr
4CName
DDN:Standard order = Empty!
.
MM02:
DDN:Sold-to-party = CName
C
ProdSpec
LIN Number
Material = Name-Order
Order quantity
TBX:PO
Condit
u
Mini01 MiniBike-Name
500PC
s
7.4.3.2.2.TAB:Sales
Biket
Name
DDN:Req. deliv.date = Now + 2 month
>500PC
o
7.4.3.2.2.1.FRM:Item
2300EUR
m

C
Clliicckk

KEY:Enter:Autofills master+payment data

SCR:Availability check
Ignore deliv. not possible warning!
BTN:Continue
BTN:Conditions( )
13340
TAB:Conditions|First empty line|

Enter
Enter

k
liicck
CCl

VK31:
r
CustSpec
Condit
MiniBikem
Name
a
>500PC
s
2200EUR
tVA01:
eCreate
rSales
Order
CName
7. Mini3BikeName

Click
Click
Click
Click
Click
Click

C
Clliicckk

7.Sales Scenario: 7.4.Order process: 7.4.5.MM:Run MRP

7.4.4.Practice:MM:Check MRP Status:MiniBike-Name, BaseBike2Name, Plant1000:MD04

St
MM
e SD LO|MM|Inventory|Environment|Stock|MD04 Stock/Req list
MD04:
p
7.4.4.1.SCR:Start
Check
7. MRPstat
DDN:Material = MiniBike-Name, BaseBike2-Name
4
Mini/
Base.
DDN:Plant = 1000
Bike2O
Name
7.4.4.2.SCR:Main
r
MD02:
Re-run
d
LIN:Sales order, MiniBike-Name, -500PC
MRP
e
MiniLIN:No dependent requirements yet!: BaseBike2-Name or any
r
Bike7. Name
other components
MD04:
4
7.4.5.Practice:MM:Run MRP:MiniBike-Name, Plant1000:MD02
Stck/Req
List.
5
LO|PP|MRP|Planning|MD02 Single item, multi level|
Mini/
Base.
7.4.5.1.1.SCR:Start
Bike2M
Name
R
DDN:Material = MiniBike-Name
MD04:
P
Create
DDN:Plant = 1000
7. Prod.
Order
4
DDN:Processing key = NETCH(Only net change)
Base.
Bike2DDN:Create purchase req. = 2(In opening period)
Name
6
500PC
.
DDN:Delivery schedules = 3(Apply)
MD04:
S
Create
DDN:Create MRP list = 1(Create list)
t
Prod.
Order
o
DDN:Planning mode = 3(Delete and recreate plan)
Minic
BikeDDN:Scheduling = 1(Basic dates will be determined)
k
Name
500PC

References
http://www.sap-img.com/abap.htm
http://erpgenie.com/
http://help.sap.com/search/sap_trex.jsp
http://sap.ittoolbox.com/groups/technical-functional/sap-abap/

Object Symbols
Partner (Partner)
Anyag (Material)
Sarzs (Batch)
Bevitt anyag
(Partner material)
Kszlet (Inventory)
Raktr (Deposit)
Gyri szm (Serial
number)
Darabjegyzk (Bill
of materials)
Szortiment
(Sortiment)
Anyagmeghatrozs (Material
Identification)
razs (Pricing)
Engedmny
(Allowance)
Fizetsi md
(Payment Method)
Szmla (Invoice)
Bizonylat

rtkests
tmogats (Sales
Promotion)
Direkt mail (Direct
mail)
Ajnlat (Offer)
razs (Pricing)
Rendels (Order)
Validci (Validation)
Szerzds
(Contract)
Szllts (Transport)
Hitel (Credit)
temezs
(Scheduling)
Szerviz (Service)
Vevszolglat
(Customer Service)
Kattints (Click)
Dupla kattints
(Double Click)
Adatbevitel (Write)
Csak olvashat
(Read Only)

k htt
liicck iiggh kk
CCl RRCClliicc

Cg (Company)
Gyr (Plant)
rtkestsi
szervezet (Sales
Department)
zletkt csoport
(Sales
Representative
Group)
rtkestsi
integrci (Sales
Integration)
Csatorna (Channel)
Fldrajzi hely
(Geographic
Location)
Kiszlltsi hely
(Delivery Location)
Szlltsi md
(Transportation

GUI Symbols
To make GUI usage descriptions more short and straightforward,
we will use standardized denotions of GUI controls, which can be
nested into each other:
DEF:-definition,
PRC:-process,
ALT:-alternatives,
CYC:-cycle,
-follows,
-(dis)advantage,
Aaa|Bbb|-Menu/Submenu,
SCR:-Screen,
FRM:-Frame,
ID-UniqueID,
BTN:-Button,
TXB:-Textbox,
DDN:-Dropdown,
TAB:-Page tab,