0% found this document useful (0 votes)
136 views18 pages

SAP TERP10 Preparation: Pauler@t-Online - Hu

This document provides instructions for practicing tasks in SAP TERP10 Preparation related to material planning and bill of materials (BOM) creation. It includes steps to create BOMs for different bike models like BaseBike, BaseBike2, GigaBike and MiniBike. It also describes checking a multi-level BOM for the GigaBike model to see its network of interlinked BOMs.

Uploaded by

vkeie0206
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
136 views18 pages

SAP TERP10 Preparation: Pauler@t-Online - Hu

This document provides instructions for practicing tasks in SAP TERP10 Preparation related to material planning and bill of materials (BOM) creation. It includes steps to create BOMs for different bike models like BaseBike, BaseBike2, GigaBike and MiniBike. It also describes checking a multi-level BOM for the GigaBike model to see its network of interlinked BOMs.

Uploaded by

vkeie0206
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 18

SAP TERP10 Preparation

Practice 4
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: [email protected]
Content of the Practice
Checking Home Assignment 3: LIS Flexible Report
3.Material Planning Scenario
3.3.Creating/Modifying master data (Continued)
3.3.2.Bill Of Material (BOM) (Continued)
3.3.2.3.Create BOM:BaseBike-Name:CS01
3.3.2.4.Create BOM:BaseBike2-Name:CS01
3.3.2.5.Create BOM:GigaBike-Name:CS01
3.3.2.6.Create BOM:MiniBike-Name:CS01
3.3.2.7.Check multi-level BOM: CS12
3.3.3.Routings
3.3.3.1.Definition
3.3.3.2.Create work center: XYScrew
3.3.3.3.Create routing:BaseBike-Name:CA01
3.3.3.4.Practice:Create routing:BaseBike2-Name:CA01
3.3.3.5.Home Assignment:Create routing:GigaBike-
Name:CA01
3.3.3.6.Home Assignment:Create routing:MiniBike-
Name:CA01
References
Object Symbols
GUI Symbols
3.3.2.Bill Of Material: 3.3.2.3.Create BOM:CS01
3.3.2.3.Create BOM:BaseBike-Name:CS01
Step 3.3.1.Material master data creation
MM

PP
LO|PP|Master|BOM|BOM|Material BOM|CS01|
MM02:
Modify 3.3.2.3.1.SCR:Start
finished DDN:Material = BaseBike-Name
material
GigaBike- DDN:Plant = 1000
Name DDN:BOM usage = 1(Production)
MMF1: TBX:Valid = 01.01.CurrYear
Create
finished 3.3.2.3.2.SCR:Main
material Item ItemCategory Component Quantity
MiniBike-
Name 0010 L(Stock item) CarbFrame-Name 1 PC
MMB1: 0020 L(Stock item) Wheel-Name 2 PC
Create
semi 0030 L(Stock item) Chain-Name 1 PC
finished
material 0040 L(Stock item) Gearing-Name 1 PC
Base- BTN:Save( )
Bike2-
Name 3.3.2.4.Practice: Create BOM:BaseBike2-Name:CS01
MMR1: LO|PP|Master|BOM|BOM|Material BOM|CS01 Create|
Create 3.3.2.4.1.SCR:Start If you get an error message here:
raw Material type ROH cannot be u-
material DDN:Material = BaseBike2-Name sed with item type L(stock item),
Alu-
Frame- DDN:Plant = 1000 then launch the transaction:
Name DDN:BOM usage = 1(Production) SPRO|SAP IMG|Logistics
CS01:
3.3.2.Create BOMs

TBX:Valid = 01.01.CurrYear general|Material master|Basic


Create settings|Material types|Define
BOM 3.3.2.4.2.SCR:Main
Base- Item ItemCategory Component Quantity attributes of material types|
Bike- LIN:ROH select
Name 0010 L(Stock item) AluFrame-Name 1 PC BTN:Show Detail, in SCR:Detail:
CS01: 0020 L(Stock item) Wheel-Name 2 PC FRM:Quantity/Value update:
Create
BOM 0030 L(Stock item) Chain-Name 1 PC CHK:In all valuation areas=True
Base- BTN:Save
Bike2- 0040 L(Stock item) Gearing-Name 1 PC SCR:Customizing reqest
Name BTN:Save( )
3.3.2.Bill Of Material: 3.3.2.5.Practice:Create BOM:CS01
3.3.2.5.Practice: Create BOM:GigaBike-Name:CS01
Step 3.3.1.Create Materials
MM

PP
LO|PP|Master|BOM|BOM|Material BOM|CS01 Create|
MMB1: 3.3.2.5.1.SCR:Start
Create
semi DDN:Material = GigaBike-Name
finished DDN:Plant = 1000
material
Base- DDN:BOM usage = 1(Production)
Bike2- TBX:Valid = 01.01.CurrYear
Name 3.3.2.5.2.SCR:Main
MMR1:
Create Item ItemCategory Component Quantity
raw 0010 L(Stock item) BaseBike-Name 1 PC
material
Alu- 0020 L(Stock item) Pedal 2 PC
Frame- 0030 L(Stock item) Brakes 2 PC
Name 0040 L(Stock item) Handlebar 1 PC
CS01:
3.3.2.Create BOMs

Create
0050 L(Stock item) Saddle 1 PC
BOM BTN:Save( )
Base- 3.3.2.6.Practice: Create BOM:MiniBike-Name:CS01
Bike-
Name LO|PP|Master|BOM|BOM|Material BOM|CS01 Create|
CS01: 3.3.2.6.1.SCR:Start
Create
BOM DDN:Material = MiniBike-Name
Base- DDN:Plant = 1000
Bike- DDN:BOM usage = 1(Production)
Name
CS01: TBX:Valid = 01.01.CurrYear
Create 3.3.2.6.2.SCR:Main
BOM
Giga- Item ItemCategory Component Quantity
Bike- 0010 L(Stock item) BaseBike2-Name 1 PC
Name 0020 L(Stock item) Pedal 2 PC
CS01:
Create 0030 L(Stock item) Brakes 2 PC
BOM 0040 L(Stock item) Handlebar 1 PC
Mini- 0050 L(Stock item) Saddle 1 PC
Bike-
Name BTN:Save( )
3.3.2.Bill Of Material: 3.3.2.7.Check multi-level BOM: CS12
3.3.2.7.Check multi-level BOM: CS12
Step 3.3.1.Materl.3.3.2.Create BOMs
MM

MMR1: PP DEF: Hierachic view of network of interlinked BOMs


Create LO|PP|Master|BOM|Reporting|BOM Explosion|Material BOM|CS12
raw Multi level BOM|
material 3.3.2.7.1.SCR:Start
Alu-
Frame- DDN:Material = GigaBike-Name
Name
CS01:
DDN:Plant = 1000
Create DDN:BOM application = PP01(Production)
BOM BTN:Select view( )
Base-
Bike- CHK:Variable list = True
Name BTN:Run( )
CS01:
Create SCR:Tabular multilevel BOM in DataView
BOM Goto|Graphics|
Base-
Bike2- SCR:Graphic multilevel BOM
Name 3.3.2.7.2.SCR:Main:
CS01:
Create Tabular multilevel BOM in ALVGrid
BOM
Giga-
Bike-
Name
CS01:
Create
BOM
Mini-
Bike-
Name
CS12:
Check
Multi
Level
BOM
Giga-
Bike-
Name
Content of the Practice
Checking Home Assignment 3: LIS Flexible Report
3.Material Planning Scenario
3.3.Creating/Modifying master data (Continued)
3.3.2.Bill Of Material (BOM) (Continued)
3.3.2.3.Create BOM:BaseBike-Name:CS01
3.3.2.4.Create BOM:BaseBike2-Name:CS01
3.3.2.5.Create BOM:GigaBike-Name:CS01
3.3.2.6.Create BOM:MiniBike-Name:CS01
3.3.2.7.Check multi-level BOM: CS12
3.3.3.Routings
3.3.3.1.Definition
3.3.3.2.Create work center: XYScrew
3.3.3.3.Create routing:BaseBike-Name:CA01
3.3.3.4.Practice:Create routing:BaseBike2-Name:CA01
3.3.3.5.Home Assignment:Create routing:GigaBike-
Name:CA01
3.3.3.6.Home Assignment:Create routing:MiniBike-
Name:CA01
References
Object Symbols
GUI Symbols
3.Material Planning: 3.3.Master data: 3.3.3.Routings
3.3.3.Routings
3.3.3.1.DEF: Routing (Mveleti terv):Description of a production process of a
material with the following content:
Material ID: Which material (FERT: Finshed product, HALB: Semi-finished
product) is manufactured
Plant ID: In which plant
DEF: Standard Sequence (Sztenderd lpssor): One product can be
produced in alternate versions requiring different routings, but there is a
standard one
DEF: Process step ID (Lps ID): Primary key of process step inside
Sequence
Description: Text description of the step
DEF: Routing group (Mveleti csoport): Groups of similar steps in a
lenghty routing
DEF: Group counter (Csoportszmll): Primary key of step inside routing
group
DEF: Work center (Munkalloms):Responsible position in the organiza-
tion for the step.
DEF: Standard value (Idnorma): Amount of time neccessary for the step
DEF: Base quantity (Alapmennyisg): How much units of material are
processed together in a step
DEF: Production resource usages (Erforrs Igny): How to share tools,
machinery
DEF: Paralel Sequences (Alternatv szekvencik): References to
alternative routings depend on type of manufacturing process:
Make to stock (Raktrra termels)
Special orders (Egyedi megrendelsre termels)
DEF: Export options(Exportlsi lehetsgek)
Routings can be transferred from SAP ERP to separate SAP APO,
SAP SCM products in Production Process Model (PPM) format
3.Material Planning: 3.3.Master data: 3.3.3.Routings: 3.3.3.2.WorkCenters
3.3.3.2.Creation of WorkCenters
Mls 3.3.CO Master data
MM

CO
PP 3.3.3.2.1.Basic problem:
OKKS:
Account.
area
In an ideal world, girl bike meets
with boy bike and soon small baby =
=1000
bikes will born:
In the reality, bike is made in operations, which have labour and machine costs:
KP04: PGScr PGUnsk GigaBike-
Planner 833EUR 5.33EUR/h Paul
profile= 240pc/h 40h/week 2500EUR/pc
Z_ALL 0.66EUR/h 15kg/pc
KS01:
Create 83EUR/pc
cost ctr 01.5kg/pc
Prod
Paul
N2
KL01:
Create
act.type
PGScr t = 15sec
PGUnsk
3.3.3.2.2.Basic terms in FI and CO master data neccessary to model production:
KP26: 3.3.3.2.2.1.FI:Controlling Area (Kltsgszmitsi kr): Set of Plants using
Set
Tariffs General Ledger (Szmviteli Szmlakeret, G/L) of a given country = 1000 (EU)
3.3.3.2.2.1.1.CO:Valuation class (Kltsgnem): groups of similar G/L
Accounts eg. = 639000 (Machine cost)
3.3.3.2.2.1.1.1.CO:Activity Type (Teljestmnyfajta): subgroups of
valuation classes eg. Screw machine (PGScr), Unskilled worker
(PGUnsk) stb.
3.3.3.2.2.1.2.CO:Cost center (Kltsghely) virtual or real part of company
organization where cost occours eg.= 4280 (Quality inspection)
3.3.3.2.2.1.2.1.CO:Tariff(Tarifa): data of activity types at cost centers:
Measure unit, eg. h (Hour)
Planned/ Real capacity in measure units
Distribution method of capacity in time
Fixed cost (independed from quantity of activity)
3.Material Planning: 3.3.Master data: 3.3.3.Routings: 3.3.3.2.WorkCenters
3.3.3.2.3.FI Set controlling area:
Mls 3.3.CO Master data
MM

CO
PP Accounting|FinAcct|GenLedg|Master data|Profit
OKKS: center| OKKS Set Controlling Area = 1000 (CO
Account. Europe, in EUR with INT(International) type G/L)
area 3.3.3.2.4.CO Set planner profile: Accounting|Control-
=1000 ling|Cost ctr acct|Planning| KP04 Set planner
KP04: profile = SAPALL (Plans everything)
Planner 3.3.3.2.5.CO Create cost center: Accounting|Cont-
profile= rolling|Cost center accounting|Master data|Cost
Z_ALL
center|Individual processing|KS01 Create
KS01: 3.3.3.2.5.1.SCR:Start:TBX:CostCtr = ProdName
Create
cost ctr TBX:Valid = 01.01.ActualYear
Prod BTN:Master data
Paul 3.3.3.2.5.2.TAB:Basic data: DDN:Comp=1000
KL01: TBX:Name,TBX:Descript. = Bike assembly
Create TBX:Person responsible = Name
act.type DDN:Cost ctr category = 1 (Production)
PGScr DDN:Hierachy area = H1420 (Production)
PGUnsk
DDN:Profit ctr = 1000 (Motors),BTN:Save ( ) Katt
KP26: 3.3.3.2.6.CO Create activity types: Accounting|Cont-
Set rolling|Cost center acctng|Master data|Activity
Tariffs
type|Individual processing|KL01 Create
3.3.3.2.6.1.Screw machine:
SCR:Start: TBX:Activity type = XYScr Katt
DDN:Valid = 01.01.
CurrYr, BTN:Master
TAB:Basic data:
Name=Screw.mach.
MeasUnit=H(Hour)
N2 CostCtrCat=1(Prod)
ATypCat=1(Manual)

Katt
AllocCostElem=
639000(Machine cost)
3.Material Planning: 3.3.Master data: 3.3.3.Routings: 3.3.3.2.WorkCenters
3.3.3.2.6.2.Unskilled worker: XYUnsk same as the
Mls 3.3.CO Master data
MM

CO
PP
last one, except: Name = Unskilled worker,
OKKS: AllocationCostElement=638100 (Production)
Account.
area 3.3.3.2.7.CO Set tariffs of activity types:Accounting|
=1000 Controlling|Cost center acctng|Planning|
KP04: Activity output/prices|KP26 Change
Planner SCR:Start: DDN:Version = 0 (Plan/Actual),
profile= DDN:From period = 1, DDN:To period = 12,
Z_ALL
DDN:Fiscal year = CurrYear
KS01: DDN:CostCtr = ProdName
Create
cost ctr DDN:Activity type = XYScr,
Prod DDN:To activity type = XYUnsk
Paul BTN:View ( ) SCR:Overview:
KL01: COL:Activity type|LIN1-2: Select activity
Create
act.type types: XYScr, XYUnsk
PGScr COL:Plan, Capacity|Lin1-2: Set their planned
PGUnsk performance and capacity to 40H/week
KP26: 50weeks/year = 2000H(we plan Jan to Dec),
Set COL:Distribution key 1, 2|LIN1-2: Set = 1
Tariffs PGScr
(Automatic even allocation among periods) 833EUR PGUnsk
COL:Fixed price(Price of every started 240pc/h 5.33EUR/h
0.66EUR/h 40h/week
hour)|Lin1-2 = 0EUR
COL:Variable price|Lin1, 2=0,66, 5,33EUR/H
COL:PlanPrice|Lin1-2 = 1(Automatic) N2
COL:Plan Quant, Avg price|Lin1-2 = True
BTN:Save ( ) other cells are auto-filled!
BTN:Monthly breakup( ): it shows planned
performance/ capacity allocated into months
Katt
3.Material Planning: 3.3.Master data: 3.3.3.Routings: 3.3.3.2.WorkCenters
Setting the tariffs, it is highly advised to follow the Uniform Measure Unit Rule
Mls 3.3.CO Master data
MM

CO
PP (Mennyisgi egysg-egyeztetsi szably): we should create as much activity
OKKS: types with the same measure unit as possible as mixing measure units
Account. rapidly increases the chance of errors. Eg. capacity of screw machine could
area be measured in pieces. But its capacity is limited by the 40 hour-weekly work
=1000 time of unskilled worker handling that. Therefore, capacity of screwing machine
KP04: in pieces could be determined as 50weeks/year 40H/week / 15sec But, if a
Planner new type of bolt introduced taking longer time to screw, we can recompute the
profile= whole thing! So it is better solution to measere capacity of machine in hour also.
Z_ALL
Another danger of error is Basis (Vettsi alap) of measure units: if we plan on
KS01: yearly level (Jan.. Dec), we have to give capacities in yearly level. In case the
Create
cost ctr lenght of planning period is modified by something (eg. Jan..Jun), SAP WILL
Prod NOT recompute automatically capacities proportionated to 6 month period!
Paul 3.3.3.2.8.PP Create Work Center (Munkahely): positions in a Company|Plant,
KL01: which can use several activity types at a given cost center (eg. we need
Create unskilled workforce to operate screw machine). They will be part of Routings.
act.type Lets create work center XYScrew (Screw machine + its staff):
PGScr Logistics|Production|Master|Work center|Work center|CR01 Create:
PGUnsk
SCR:Start: DDN:Plant = 1000(Hamburg),
KP26: TBX:Work center = XYScrew,
Set DDN:WorkCtrCat = 0001(Machine)
Tariffs
BTN:Basic data:
DDN:Responsible person = 101,
CR01:
3.3.PP master data

Create DDN:Usage = 009(All task lists)


work CHK:Backflush=True(Retrograde)
center DDN:StandardValue=SAP1(Normal)
PGScrew TAB:Costing:
DDN:Valid=01.01.CurrYr
DDN:CostCtr=ProdPaul
N
LIN:Setup=XYUnsk,H,True
2
LIN:Mach.=XYScr,H,True
LIN:Labor=XYUnsk,H,True
(CHK:Ref.Indicator=True
at all 3 lines to autoupdate)
Content of the Practice
Checking Home Assignment 3: LIS Flexible Report
3.Material Planning Scenario
3.3.Creating/Modifying master data (Continued)
3.3.2.Bill Of Material (BOM) (Continued)
3.3.2.3.Create BOM:BaseBike-Name:CS01
3.3.2.4.Create BOM:BaseBike2-Name:CS01
3.3.2.5.Create BOM:GigaBike-Name:CS01
3.3.2.6.Create BOM:MiniBike-Name:CS01
3.3.2.7.Check multi-level BOM: CS12
3.3.3.Routings
3.3.3.1.Definition
3.3.3.2.Create work center: XYScrew
3.3.3.3.Create routing:BaseBike-Name:CA01
3.3.3.4.Practice:Create routing:BaseBike2-Name:CA01
3.3.3.5.Home Assignment:Create routing:GigaBike-
Name:CA01
3.3.3.6.Home Assignment:Create routing:MiniBike-
Name:CA01
References
Object Symbols
GUI Symbols
3.3.Master data: 3.3.3.Routings: 3.3.3.2.Create routing:BaseBike-Name:CA01
Step 3.3.2.Create BOMs

3.3.3.3.Create routing:BaseBike-Name:CA01
MM

PP
LO|PP|Master|Routing|Routing|Standard routing|CA01 Create|
CS01:
Create 3.3.3.3.1.SCR:Start
BOM DDN:Material = BaseBike-Name
Base- DDN:Plant = 1000
Bike2-
Name TBX:Key date = 01.01.CurrYear, KEY:Enter
CS01: 3.3.3.3.2.SCR:Head
Create DDN:Usage = 1(Production): alternatives are producing non-functioning
BOM product sample demo (eg. open version of gear shift)
Giga-
Bike- DDN:Status = 4(Released): can be readily used
Name 3.3.3.3.2.1.BTN:Operations
CS01: Step Standard Times of Operation WorkCtr ControlKey Description
Create 0010 |DoubleClick: XY PP01(Normal) Stage material
BOM Setup = 30 MIN XYUnsk(Wage hour) Screw
Mini-
Bike- 0020 |DoubleClick: XY PP01(Normal) Assembly
Name Machine = 15 MIN PGScr(Mach.hr.) Screw
CS12: Labor = 45 MIN XYUnsk(Wage hour)
Check 0030 |DoubleClick: XY PP99(Milestone Delivery
Multi Labor = 24 MIN XYUnsk(Wage hour) Screw put to stock!!!!)
Level
BOM 3.3.3.3.2.2.BTN:Save( ) Click
Giga- STS:Take note of Routing ID: 50001315 Click
Bike- Click
Name Click
CA01:
3.3.3.Create Routings

Click
Create Click
Routing Click
Base-
Bike-
Name
CA01:
Create
Routing
Base-
Bike2-
Name
3.3.Master data: 3.3.3.Routings: 3.3.3.2.Practice:Create routing:BaseBike-Name:CA01
3.3.3.4.Practice:Create routing:BaseBike2-Name:CA01
Step 3.3.2.Create BOMs
MM

PP
LO|PP|Master|Routing|Routing|Standard routing|CA01 Create|
CS01: 3.3.3.4.1.SCR:Start
Create
BOM DDN:Material = BaseBike2-Name
Base- DDN:Plant = 1000
Bike2-
Name TBX:Key date = 01.01.CurrYear
CS01: 3.3.3.4.2.BTN:Copy From
Create DDN:Reference material = BaseBike-Name
BOM TBX:Key date = 01.01.CurrYear, KEY:Enter
Giga-
Bike- DDN:Status = 4(Released), KEY:Enter
Name 3.3.3.3.2.1.BTN:Save( )
CS01:
Create
STS:Take note of Routing ID: 50001316
BOM
Mini-
Bike-
Name
CS12:
Check
Multi
Level
BOM
Giga-
Bike-
Name
CA01:
3.3.3.Create Routings

Create
Routing
Base-
Bike-
Name
CA01:
Create
Routing
Base-
Bike2-
Name
3.3.Master data: 3.3.3.Routings: 3.3.3.4.Home Assignment: Create routings
3.3.3.5.Home Assignment:Create routing:GigaBike-Name:CA01
Step 3.3.2.Create BOMs
MM

PP (2.5points)
CS01: LO|PP|Master|Routing|Routing|Standard routing|CA01 Create|
Create
BOM 3.3.3.5.1.SCR:Start
Mini-
Bike- DDN:Material = GigaBike-Name
Name DDN:Plant = 1000
CS12:
Check TBX:Key date = 01.01.CurrYear
Multi 3.3.3.5.2.BTN:Copy From
Level
BOM DDN:Reference material = BaseBike-Name
Giga-
Bike- TBX:Key date = 01.01.CurrYear, KEY:Enter
Name
DDN:Status = 4(Released), KEY:Enter
3.3.3.Create Routings

CA01:
Create 3.3.3.4.2.1.BTN:Save( )
Routing
Base- STS:Take note of Routing ID: 50001317
Bike-
Name 3.3.3.6.Home Assignment:Create routing:MiniBike-Name:CA01
CA01: (2.5points)
Create LO|PP|Master|Routing|Routing|Standard routing|CA01 Create|
Routing
Base- 3.3.3.6.1.SCR:Start
Bike2-
Name DDN:Material = MiniBike-Name
CA01: DDN:Plant = 1000
Create
Routing TBX:Key date = 01.01.CurrYear
Giga- 3.3.3.6.2.BTN:Copy From
Bike-
Name DDN:Reference material = BaseBike-Name
CA01:
Create TBX:Key date = 01.01.CurrYear, KEY:Enter
Routing DDN:Status = 4(Released), KEY:Enter
Mini-
Bike- 3.3.3.5.2.1.BTN:Save( )
Name
STS:Take note of Routing ID: 50001318
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
Cg (Company) Partner (Partner) rtkests
Gyr (Plant) Anyag (Material) tmogats (Sales
rtkestsi Sarzs (Batch) Promotion)
szervezet (Sales Bevitt anyag Direkt mail (Direct
Department) mail)
zletkt csoport (Partner material)
(Sales Kszlet (Inventory) Ajnlat (Offer)
Representative Raktr (Deposit) razs (Pricing)
Group) Gyri szm (Serial Rendels (Order)
rtkestsi number) Validci (Validation)
integrci (Sales Darabjegyzk (Bill Szerzds
Integration) of materials) (Contract)
Csatorna (Channel) Szllts (Transport)
Fldrajzi hely Szortiment Hitel (Credit)
(Geographic (Sortiment) temezs
Location) Anyagmeghat- (Scheduling)
Kiszlltsi hely rozs (Material Szerviz (Service)
(Delivery Location) Identification) Vevszolglat
Szlltsi md razs (Pricing)
(Transportation (Customer Service)
Mode) Engedmny Kattints (Click)
Rakodsi pont (Allowance) Dupla kattints
(Loading Point) Fizetsi md (Double Click)
rucsoport (Product (Payment Method) Adatbevitel (Write)
Group) Szmla (Invoice) Csak olvashat
rtkestsi terlet Bizonylat (Read Only)
(Sales Area) (Voucher)
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,
CHK:-Checkbox (any of them can be checked)
RAD:-Radiobox (one can be checked only),
LIN:-Tableline,
KEY:-Hotkey,
WRN:-Warning box
ERR:-Errorbox

You might also like