slide1
Download
Skip this Video
Download Presentation
SAP TERP10 Preparation Practice 3 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur

Loading in 2 Seconds...

play fullscreen
1 / 23

SAP TERP10 Preparation Practice 3 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur - PowerPoint PPT Presentation


  • 95 Views
  • Uploaded on

SAP TERP10 Preparation Practice 3 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur Tax Reg. No.: 63673852-3-22 Bank account: 50400113-11065546 Location: 1st Széchenyi str. 7666 Pogány, Hungary Tel: +36-309-015-488 E-mail: [email protected] Content of the Practice.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' SAP TERP10 Preparation Practice 3 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur' - leigh


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

SAP TERP10 Preparation

Practice 3

Dr. Gábor Pauler, Associate Professor, Private Entrepeneur

Tax Reg. No.: 63673852-3-22

Bank account: 50400113-11065546

Location: 1st Széchenyi str. 7666 Pogány, Hungary

Tel: +36-309-015-488

E-mail: [email protected]

content of the practice
Content of the Practice
  • Checking Home Assignment 2: Purchase Info Records
  • 2.Procurement Scenario (Continued)
    • 2.7.Invoice Processing
      • 2.7.1.MM: Enter Vendor Invoice (Szállítói Számla):MIRO
      • 2.7.2.MM: Display Invoice Document and Order History:MIRO
      • 2.7.3.FI:Check subledger account of vendor:FBL1N
      • 2.7.4.FI: Payment:F-58
      • 2.7.5.Checking paid items:FBL1N
    • 2.8.Cross-module integration of MM:Procurement
    • 2.9.MM Reporting:
      • 2.9.1.MM:List display:ME2L
      • 2.9.2.MM:LIS standard analysis:MCE3
    • 2.10.Procurement: Business Process Diagram (BPD)
      • 2.10.1.BPD Elements
      • 2.10.2.Procurement: Process Overview
    • 2.11.Procurement: Advanced Database Diagram (ADD)
      • 2.10.1.ADD Elements
      • 2.10.2.Procurement: Data Stream Overview
  • Home Assignment 3: LIS Flexible report
  • References
  • Object/GUI Symbols
2 procurement 2 7 invoice processing
2.Procurement: 2.7.Invoice Processing
  • 2.7.Invoice processing (Szállítói Számlakezelés)
    • 2.7.1.MM: Enter Vendor Invoice (Szállítói Számla):MIRO
      • Plot: Vendor submits an invoice of 55,000 EUR (500 € * 110 PC Gearing-0005) + 10,450 EUR (19 % VAT)
      • 2.7.1.1.PROC: Invoice Verification (Számlaellenőrzés)
        • 2.7.1.1.1.Receive VendorInvoice: byanymedia (fax, e-mail, EDI, etc.)
        • 2.7.1.1.2.Formal Invoice Check: allrequiredfieldsarefilled(quantity, unit price, tax)
        • 2.7.1.1.3.ContentCheck:comparing(quantity, unit price, tax)between:
          • 2.7.1.1.3.1.Vendor Invoice (Szállítói Számla) and its
          • 2.7.1.1.3.2.Referenced Document (Előd-bizonylat): It can be:

 2.7.1.1.3.2.1.ALT:Purchase Order (Megrendelés): Always settles the

whole order, irrespective to partial delivery

 2.7.1.1.3.2.2.ALT:Delivery Note (Fuvar Értesítés):

 2.7.1.1.3.2.3.ALT:Goods Receipt (Anyagbevételi Bizonylat): Always

settles only that part of the order what was received on it, thequantity

cannot be more!

        • 2.7.1.1.4.ALT:In case of variance: invoice gets blocked and re-valuated:
          • 2.7.1.1.4.1.ALT:If material is Mmoving average price valued: in material master, moving average price is recalculatedInvoice is re-valued with new price × altered quantity
          • 2.7.1.1.4.2.ALT:If material is Sstandard valued: Invoice is re-valued with altered quantity
        • 2.7.1.1.5.ALT:If everything is OK: invoice is posted to SAP FI and CO:
          • 2.7.1.1.5.1.Goods Receipt/Invoice Receipt, GR/IR Account: stores provisional liability originated from issuing goods receipt. Then is cleared with
          • 2.7.1.1.5.2.Invoice Receipt (Számlabizonylat): is issued as proof of liability towards vendor
          • 2.7.1.1.5.3.Vendor Reconciliation Account (Beszállítói elszámoló számla): will have a new open item
          • 2.7.1.1.5.4.Accounting document (Könyvelési bizonylat): is prepared
          • 2.7.1.1.5.5.Purchase Requistion History (Beszerzési igény történet): is updated with invoice document
2 procurement 2 7 invoice processing 2 7 1 enter vendor invoice
2.Procurement: 2.7.Invoice Processing: 2.7.1.Enter Vendor Invoice

Click

  • 2.7.1.2.LO|MM|Logistics invoice verification|Documententry|MIRO Enter Invoice|
    • 2.7.1.2.1.SCR:Start:
      • DDN:Company = 1000
    • 2.7.1.2.2.SCR:Main:
      • 2.7.1.2.2.1.TAB:Basic data:

 TBX:Invoice date = Now

 TBX:Posting date = Now

 TBX:Amount = 59500 EUR

 CHK:Calculate tax = True

 DDN:Tax code = VA (domestic

input tax 19%)

      • 2.7.1.2.2.2.TAB:PO Reference

 DDN:Reference document = 1

(Purchase order)

 TBX:Reference document

number = 4500017376

 KEY:Enter:Amount with tax

recomputed correctly!

    • 2.7.1.2.2.3.BTN:Save( )
      • Take note of assigned Invoice document ID:

Click

Click

Click

ME29N:

Release

PurOrd

45000

17376

Click

Click

MIGO:

Goods

Receipt

from

PurOrd:

45000

17376

Quant:

100pc

Storage:

0110

Click

Click

Click

Click

MIGO:

Transfer

Posting:

Gearing

-Name

Quant:

100pc

Storage:

0110

Click

Click

MIRO:

Invoice

from PO

45000

17376

Value:

€59500

5105608882

2 procurement 2 7 invoice processing 2 7 2 practice display invoice documents
2.Procurement: 2.7.Invoice Processing: 2.7.2.Practice:Display Invoice Documents
  • 2.7.2.MM: Display Invoice Document and Order History:MIRO
    • 2.7.2.1.LO|MM|Logistics invoice verification|Documententry|MIRO Enter Invoice|
      • 2.7.2.1.1.SCR:Start:
        • DDN:Company = 1000
      • 2.7.2.1.2.SCR:Main:
        • DDN:Transaction = 1(Invoice)
        • TBX:Invoice number = 5105608882
        • 2.7.2.1.2.1.Invoice documents|Display|

 BTN:Follow-on documents:

 LIN:Accounting documents:

 SCR:Displaydocument:One can

see that accounting documents generated

have separate ID from invoice ID, to enable

partial settlement of an invoice:

 Take note Accounting doc ID:

        • 2.7.2.1.2.2.TAB:PO Reference

 FRM:Item overview:

 LIN:Purchase order = 4500017376

 FRM:Item detail:

 Purchase order, goods movement,

invoice documents should appear in list,

and status should be invoiced!

  • 2.7.3.FI:Check subledger account of vendor:FBL1N
    • 2.7.3.1.Accounting|FI|Accounts payable|Account|FBL1N Diplay/Change line items|
      • 2.7.3.1.1.SCR:Start
        • DDN:Vendor Account = 100304
        • DDN:Company Code = 1000
        • RAD:Open items = True:Show unpaid items, select this!
        • RAD:Cleared items = False:Show paid items
        • BTN:Run( ):
      • 2.7.3.1.2.SCR:Main:Check amount due!

5100000000

2 procurement 2 7 invoice processing 2 7 4 payment
2.Procurement: 2.7.Invoice Processing: 2.7.4.Payment
  • 2.7.4.FI: Payment:F-58
    • 2.7.4.1.DEF:Payment
      • 2.7.4.1.1.ALT:Manual outgoing payment:
        • Select payment method and bank 
        • Select items to pay 
        • Calculate payment with cash discounts 
        • Post payment document 
        • Print payment medium
      • 2.7.4.1.2.ALT:Automatic outgoing payment
    • 2.7.4.2.Accounting|FI|Accounts payable|Document entry|Outgoing|F-58 Post+Print Forms
      • 2.7.4.2.1.SCR:Header data
        • DDN:Company code = 1000
        • DDN:Payment method = C(Check)
        • DDN:House bank = 1000 (Comp1000)
        • DDN:Check lot number = 0001
        • DDN:Printer for forms = LOCAL(Standard local printer)
        • CHK:Print immediately = True
        • 2.7.4.2.1.1.BTN:Enter payments:

 TBX:Amount = 59500

 DDN:Vendor = 100304

        • 2.7.4.2.1.2.BTN:Process open items:

 Check open positions list!

        • 2.7.4.2.1.3.BTN:Save( )

 Take note of assigned Payment

document ID:

MIGO:

Goods

Receipt

from

PurOrd:

45000

17376

Quant:

100pc

Storage:

0110

Click

Click

Click

Click

MIGO:

Transfer

Posting:

Gearing

-Name

Quant:

100pc

Storage:

0110

Click

Click

Click

Click

MIRO:

Invoice

from PO

45000

17376

Value:

€59500

Click

F-58:

Paymnt

€59500

Vendor

100304

1500000000

content of the practice1
Content of the Practice
  • Checking Home Assignment 2: Purchase Info Records
  • 2.Procurement Scenario (Continued)
    • 2.7.Invoice Processing
      • 2.7.1.MM: Enter Vendor Invoice (Szállítói Számla):MIRO
      • 2.7.2.MM: Display Invoice Document and Order History:MIRO
      • 2.7.3.FI:Check subledger account of vendor:FBL1N
      • 2.7.4.FI: Payment:F-58
      • 2.7.5.Checking paid items:FBL1N
    • 2.8.Cross-module integration of MM:Procurement
    • 2.9.MM Reporting:
      • 2.9.1.MM:List display:ME2L
      • 2.9.2.MM:LIS standard analysis:MCE3
    • 2.10.Procurement: Business Process Diagram (BPD)
      • 2.10.1.BPD Elements
      • 2.10.2.Procurement: Process Overview
    • 2.11.Procurement: Advanced Database Diagram (ADD)
      • 2.10.1.ADD Elements
      • 2.10.2.Procurement: Data Stream Overview
  • Home Assignment 3: LIS Flexible report
  • References
  • Object/GUI Symbols
2 procurement 2 7 invoice processing 2 8 mm cross module integration
2.Procurement: 2.7.Invoice Processing: 2.8.MM Cross-Module Integration
  • 2.8.Cross-module integration of MM:Procurement
    • 2.8.1.Financial accounting (FI): Invoice accounting documents:
      • Account 160000:Reconciliation account for all vendors, paired with that
      • Sub-ledger creditor accounts are defined for each vendor at vendor master
    • 2.8.2.Sales&Distribution (SD): Sales order
      • Can result in purchase requisition if sold finished products and its parts through BOM ar not in stock
    • 2.8.3.Production Planning(PP):
      • Can result purchase requistions if semi-finished goods or raw material are not in stock
    • 2.8.4.Maintenance( MT):
      • Goods receipt can contain reference to a BOM: eg. a raw material is ordered andelivered because BOM of finished product requires it
      • Maintenance can hold back spare parts from these
    • 2.8.5.Warehouse Management System (WMS)
      • While inventory management only contains material type and quantity info
      • It adds handling and storage place allocation data
2 procurement 2 9 reporting 2 9 1 list displays
2.Procurement: 2.9.Reporting: 2.9.1.List Displays
  • 2.9.MM Reporting:
    • 2.9.1.MM:List display:ME2L
      • 2.9.1.1.DEF:List dislay tools in SAP:
        • SE16ListView: Character-based table display tool, simple, older
        • ALV Grid: Flexible graphic table display with standardized controls
      • 2.9.1.2.LO|MM|Purchasing|Purchase order|List display|ME2L By vendor|
        • 2.9.1.2.1.SCR:Start
          • DDN:Plant = 1000
          • DDN:Purchasing organization = 1000
          • DDN:Document date = 01.01.2003 .. Now
          • DDN:Scope of list = BEST_ALV(Informa-

tion structure to show)

          • BTN:Run( )
        • 2.9.1.2.2.SCR:ALV Grid
          • 2.9.1.2.2.1.Simple operations: Toolbar

 BTN:Show detail( )

 BTN:Filter( )

 BTN:Short( )

 BTN:Totals( )

 BTN:Subtotals( )

 BTN:Change layout( )

 BTN:Save layout( )

          • 2.9.1.2.2.2.Complex operations: Settings|Layout|Change|

 TAB:Short order

 BTN:Add/Remove field( )

          • 2.9.1.2.2.3.BTN:Save( )

 TBX:Name = Layout-Name

MIGO:

Transfer

Posting:

Gearing

-Name

Quant:

100pc

Storage:

0110

Click

Click

Click

Click

Click

Click

Click

Click

MIRO:

Invoice

from PO

45000

17376

Value:

€59500

F-58:

Paymnt

€59500

Vendor

100304

Click

Click

Click

Click

Click

Click

Click

ME2L:

PO list

byven-

dors for

Plant

1000

Click

Click

Click

Click

Click

2 procurement 2 9 reporting 2 9 2 standard analysis 1
2.Procurement: 2.9.Reporting: 2.9.2.Standard Analysis 1
  • 2.9.2.MM:LIS standard analysis:MCE3
    • 2.9.2.1.DEF: Logistic Information System, LIS(Logisztikai Információs rendszer)
      • On-Line Analitical Processing (OLAP) system of logistical managerial reporting
      • 2.9.2.1.1.LIS Data sources:
        • 2.9.2.1.1.1.Master data

 Material

 Vendor

 Purchase info record

        • 2.9.2.1.1.2.Documents(transaction data):

 Purchase requisition/order

 Material documents

 Incoice documents

 Payment documents

      • 2.9.2.1.2.LIS Structure:
        • 2.9.2.1.2.1.DEF:Information structure

 Building block of PURCHIS

 Statistical table collected from transaction data and updated regularly

 It has predefined field structure from 3 functional type of fields:

 2.9.2.1.2.1.1.DEF:Characteristics (Karakterisztika): Possible

aggregation hierarchy levels of transaction data:

 Client|Company|Plant|Storage|Material

 2.9.2.1.2.1.2.DEF:Period units (Periódus): Possible aggregation

hierarchy levels of time:

 Period|Month|Week|Day

 2.9.2.1.2.1.3.DEF:Key figures (Kulcsmutató): Aggregates of

transactional data field in a given level of hierarchy

 Count, Sum, Avg, Max, Min

        • 2.9.2.1.2.2.DEF:Analysis (Elemzés): An OLAP data cube computed from source data defined by:

 2.9.2.1.2.2.1.DEF:Object of analysis (Elemzés tárgya):Set of

characteristics and period units aggregate by

 2.9.2.1.2.2.2.DEF:Selections (Kiválasztás):Set of key figures to

aggregate

2 procurement 2 9 reporting 2 9 2 standard analysis 2
2.Procurement: 2.9.Reporting: 2.9.2.Standard Analysis 2

 2.9.2.1.2.2.3.DEF:Initial/Drill-down lists (Lefúrás): show detailed level

data behind aggregated ones

 ALT:StandardAnalysis(SztendredElemzés):predefinedby SAP

 ALT:Flexible Analysis (Rugalmas Elemzés):can be edited on GUI

    • 2.9.2.1.2.3.DEF:Functions (Funkciók):Statistics can be performed on analysis results:

 2.9.2.1.2.3.1.DEF:ABC analysis (ABC Elemzés): helpstoselect top

10% of most important (Category A) elements

 2.9.2.1.2.3.2.DEF:Classification (Osztályozás): classifiesmultivariate

observationsintopredefinedgroupswithDiscriminantAnalysis

(Diszkriminancia Elemzés)

 2.9.2.1.2.3.3.DEF:Segmentation (Szegmentáció): classifies

multivariateobservationsinto K groupswithK-MeanClustering (K-közép

Klaszterezés) and computesgroupaverages

 2.9.2.1.2.3.4.DEF:Plan/Actual comparison (Terv/Tény eltérés):

parallel charting of planned and factualdata

 2.9.2.1.2.3.5.DEF:Cumulated frequencies (Kumulált gyakoriságok):

helpstoidentifyveryhigh/lowOutliers (Kilógó elem) from a variable

 2.9.2.1.2.3.6.DEF:Correlation (Korreláció):  measures

independence (around0)/ parallel movement (+1) / countermovement

(-1) of 2 cardinalvariables,  itcan show onlyMonotonic (Monoton)

connections

 2.9.2.1.2.3.7.DEF:Time series (Idősorok): Basis/ChainRates

(Bázis/Láncviszonyszám) tomeasurerelativechange, Movingaverages

(Mozgóátlagok) tosmoothsmallwaves

  • 2.9.2.1.3.LIS Parts:
    • 2.9.2.1.3.1.Sales Information System(SIS)
    • 2.9.2.1.3.2.Purchasing Information System(PURCHIS)
    • 2.9.2.1.3.3.Inventory Controlling(INVCO)
    • 2.9.2.1.3.4.Transportation Information System(TIS)
    • 2.9.2.1.3.5.Shop Floor Information System(SFIS)
    • 2.9.2.1.3.6.Quality Management Information System(QMIS)
    • 2.9.2.1.3.7.Plant Maintenance Information System(PMIS)
2 procurement 2 9 reporting 2 9 2 standard analysis 3
2.Procurement: 2.9.Reporting: 2.9.2.Standard Analysis 3

Click

Click

  • 2.9.2.2.LO|LO controlling|Purchasing information system| Standard analyses|MCE3 Vendor|
    • 2.9.2.2.1.SCR:Start
      • DDN:PurchOrg = 1000
      • DDN:Months = 01.2004..Now
      • BTN:Run( )
    • 2.9.2.2.2.SCR:ListView
      • 2.9.2.2.2.1.COL:Vendor: Characteristicscolumn: ID of vendor

 Settings|Characteristic display|

 |Key and text:ShowsvendorID

 DoubleClick|Change co-

lumn width:extend column

      • 2.9.2.2.2.2.Edit|

 |Choose key fig.s:select fields to show

      • 2.9.2.2.2.3.COL:PO Value:Key figure

column:Value of PurchaseOrder

 Edit|ABC-analysis:classifies vendors by:

 DDN:Strategy = Total % PO value

 In 3 categories:

 A = 70%,

 B = 20%,

 C = 10%

 BTN:Graphics:Draws diagram

 Record most important ven-

dor:

      • 2.9.2.2.2.4.Extras|

 |Select log: shows which information

structures were used by which reporting

operation

Click

Click

Click

MIGO:

Transfer

Posting:

Gearing

-Name

Quant:

100pc

Storage:

0110

Click

Click

Click

Click

Click

MIRO:

Invoice

from PO

45000

17376

Value:

€59500

Click

Click

Click

Click

Click

Click

Click

F-58:

Paymnt

€59500

Vendor

100304

Click

ME2L:

PO list

byven-

dors for

Plant

1000

Click

Click

MC3E:

Standard

analysis

forven-

dors of

Plant

1000

Vendor-Paul

content of the practice2
Content of the Practice
  • Checking Home Assignment 2: Purchase Info Records
  • 2.Procurement Scenario (Continued)
    • 2.7.Invoice Processing
      • 2.7.1.MM: Enter Vendor Invoice (Szállítói Számla):MIRO
      • 2.7.2.MM: Display Invoice Document and Order History:MIRO
      • 2.7.3.FI:Check subledger account of vendor:FBL1N
      • 2.7.4.FI: Payment:F-58
      • 2.7.5.Checking paid items:FBL1N
    • 2.8.Cross-module integration of MM:Procurement
    • 2.9.MM Reporting:
      • 2.9.1.MM:List display:ME2L
      • 2.9.2.MM:LIS standard analysis:MCE3
    • 2.10.Procurement: Business Process Diagram (BPD)
      • 2.10.1.BPD Elements
      • 2.10.2.Procurement: Process Overview
    • 2.11.Procurement: Advanced Database Diagram (ADD)
      • 2.10.1.ADD Elements
      • 2.10.2.Procurement: Data Stream Overview
  • Home Assignment 3: LIS Flexible report
  • References
  • Object/GUI Symbols
2 procurement 2 10 business process diagram bpd 2 10 1 bpd elements
2.Procurement: 2.10.Business Process Diagram(BPD): 2.10.1.BPD Elements

Proc:A

EndProc:A

FOR:A

EndFOR:A

IF:B

ElseIF:B:

EndIF:B

Sql:

Step:

Decl:

Sql:Query

unit price

Step:

Add Item

Step:Enter

quantity

Step:

Scan Item

Proc:Che-

ck barcode

  • Proc:Restock
  • BarCode
  • Quantity
  • InvoiceID

Step:Record

Customer data

  • Decl:
  • TempName
  • TempAdress

IF:New

Customer?

IF:Barcode OK?

FOREACH

Item

ElseIF:Barcode?

Step:Isuue Invoice

Step:Ask cus-

tomer data

EndIF:New Cust?

EndIF:Barcode?

IF:Price is OK?

EndIF:Price?

  • Proc:Invoicing
  • CustomerID
  • InvoiceID

ElseIF:Price?

Sql:Query

Customers

Step:Com-

pute totals

Step:

Give Item

EndFOR:Item

EndProc:

Invoicing

  • Business Process Diagram (BPD): describes a process with given input, output, responsibilities, time- and resource consumption.
    • It is a flowchart laid out in a 2-dimensional coordinate system:
      • Time: it is not really a physical time, but a nonlinear timescale broken by uniquely named breakpoints (Töréspont) or milestones (Mérföldkő) of the process
      • Roles (Szerepek): discrete (Diszkrét beosztású) coordinate axis representing uniquely named units of the organization (not actual people, because they can be fired!)or partners (suppliers(Beszállító),customers, etc.)resposible for activities
    • Activities (Tevékenység)of the process are represented by blocks of flowchart. Length of blocks is proportional to their time requirement, while other resource consumptions (workforce, hardware, etc.) can be described in blocks’ text. They can be:
      • Pairs of blocks (Blokkpárok) describing process control. They can be nested into each other. Nested pairs are always tabulated (like program code) for clarity:
        • Procedure header /footer with parameter list and type icons. Boldfaced (Félkövér) parameters are given by referece, others by value
        • Cycle condition /footer with cycle variable
        • Conditon header /Else branch /footer with condition
      • Single blocks (Egyedi blokkok) describing:
        • Declaration of local vars with type icons,Process step ,SQL query
    • There are four types of arrows (Nyíl) joining blocks:
      • Yes branch of condition (), No branch of condition (), they are always drawn before blocks to visualize their nesting hierarchy, Step forward (), Feedback (Visszacsatolás) (),only this one can step backward in time (of course logically)
2 procurement 2 10 business process diagram 2 10 2 process overview 1
2.Procurement: 2.10.Business Process Diagram: 2.10.2.Process Overview 1
  • We overview Procurement Process describing data dependencies across transactions:
    • Precondition (Előfeltétel): , Data dependency (Adatfüggés): 

ME9F:

Display

Message

PurOrd

45000

17376

ME21N:

Create

PurOrd

from

Requis:

10013873

from

Vendor:

100304

PurOrg:

1000

ME29N:

Release

PurOrd

45000

17376

MIGO:

Goods

Receipt

from

PurOrd:

45000

17376

Quant:

100pc

Storage:

1010

MMF1:

Create

finished

material

Giga

Bike-

Name

MMB1:

Create

semi-

finished

material

Base

Bike-

Name

MMR1:

Create

raw.mat

Carb

Frame

/Wheel

/Chain-

Name

MMH1:

Create

trading

good

Gearing-

Name

XK01:

Create

vendor

Vendor

-Name

ME11:

Create

Purchas

Info.rec

Carb

Frame/

Wheel/

Chain/

Gearing

-Name

MIGO:

Transfer

Posting:

Gearing

-Name

Quant:

100pc

Storage:

1010

ME51N:

Create

Purchas

Requis

Gearing

-Name

100 +

10 for

CostCtr

4280

MIRO:

Invoice

from PO

45000

17376

Value:

€59500

F58:

Paymnt

€59500

Vendor

100304

Material

type =

HAWA

(Trading good)

ensured by

MMH1

Valuation

class =

3100

(Trading good)

Account grp =

KRED

(Auto numbered)

Vendor ID =

Empty!

Reconciliation

account =

161010

(Foreign vend)

G/L account =

410000

(Raw material)

Cost ctr =

4280 (Test lab)

(only for 10PC)

Date = Now+1wk

(Allow some time

for delivery)

PostDate = Now

(Pre-deadline

delivery)

Delivery note =

* (None)

Stock type =

002 (Qual.insp)

ME2L:

PO list

byven-

dors for

Plant

1000

MC3E:

Standard

analysis

forven-

dors of

Plant

1000

2 procurement 2 11 advanced database diagram add 2 11 1 add elements 1
2.Procurement: 2.11.Advanced Database Diagram(ADD): 2.11.1.ADD Elements 1

EntityName

EntityNameID

Text

Integer

Fraction

Binary

Date

Time

Image

Sound

Movie

ReqForeignKey

OptForeignKey

Modifier

Modified

Status

MasterEntity

MasterID

MasterName

  • Entities are ordered into a 2 dimensional grid where colums are Dimensions (Dimenzió) of the problem and rows are Hierarchic levels (Hierarchikus szint) of dimensions:
    • There are standard dimensions can be found in any system: Time, Space, Person, Organization, Partner,etc
    • There are problem specific dimensions: SD, MM, PP, FI, CO, PS
  • Entityrelationship diagram (Egyedkapcsolati diagram) (ERD): is usedtorepresent design of a RelationalDatabase System (RDS)
  • EntitesareroundedcornerboxeswithEntity-Nameatthe top. Bluebackgrounddenotescodetable/masterentitieswithminimaldatachangeintime, yellowdenotesrelational/trans-actionentities: irrevocabledatachangesintime
  • Attributesarelistedwiththeirdatatypeicons:

( , , , , , , , , )and names:italicmeansop-tional-, normalmeansrequired-, boldmeansauto-filledattribute

  • Data attributesarepurple, primarykeysareorangepromptedby ( ), foreignkeysareolivepromptedby( ), auto-filledsystemlog-gingattributesareblack
  • 1:many relations aredenotedby ( ) con-nectingprimary-andforeignkeys:
    • Independent side of relation

is denotedon ERD with

dashed line ( ), depen-

dentwithsolid ( )

    • Itsreferentialintegritycheck

is denotedwith ( ),

unswitchabilitywith ( ),

cascadedeletedisabled

with ( ).

2 procurement 2 11 advanced database diagram add 2 11 1 add elements 2
2.Procurement: 2.11.Advanced Database Diagram(ADD): 2.11.1.ADD Elements 2

Residence

ResidID

StartDate

EndDate

PersonID

AddressID

Modifier

Modified

Status

Person

PersonID

NaturalID

GivenName1

GivenName2

SurName

MaidenName

BirthPlace

MotherName

BirthDate

Modifier

Modified

Status

Address

AddressID

Door

Floor

HouseNum

StreetName

Tel

Fax

StreetTypeID

ZipID

CountryID

Modifier

Modified

Status

  • ChkNewCust
  • FormName
  • naturalID
  • GivenName1
  • GivenName2
  • VSurName
  • MaidenName
  • BirthPlace
  • MothersName
  • BirthDate
  • ResStartDate
  • ResEndDate
  • Door
  • Floor
  • HouseNum
  • Tel
  • StreetName
  • StreetType
  • Zip
  • Store data
  • NaturalID
  • TextBox
  • OptionButtons
  • NumberBox
  • CheckBox
  • Date
  • Time
  • PictureShow
  • SoundPlayer
  • MoviePlayer
  • ReqForgnKey
  • OptForgnKey
  • QueryButton
  • Decision
  • Question?

MainForm base entity

  • Elements of GUI diagram:
  • Form(Űrlap) block:
  • Form name at top in blue
  • Followed by various type of data controls(Adatmeg-jelenítő kontroll) with their caption and cotrol type icon. All of them are linked to a specific data type ex-cept the NumberBox, which can show both inte-ger and fraction number
  • Boldface controls auto-filled, normals are requ-ired, italics are optional
  • Underlining means form section break(Űrlap szek-ció törés): different form sections have different table or query data source (see example later)
  • Form may contain buttons launching query/other form
  • Popup Form (Felugró):
  • It contains yes/no question and belongs to a conditi-onal block pair on BPD
  • Example of form sections:
  • 1Personcan residemanyAddress (in time),and 1Addresscan be resided by manyPersons (Resi-dence is relation entity)
  • Lets assume we have a check new customer ac-tivity on BPD we want to support with database at CheckNewCust form.
  • Its content 1:1 connec-ted to Person, therefore it will be the base entity (Bázisegyed) data sour-ce of main form section goes until BirthDate
  • Person is1:manyrelated to Residence, so data of the latter cannot go on the same form section, but it will be base entity of subform (Segédűrlap)
  • Residence is many:1 related to Address, so data of latter can be joi-ned to subform section, being its joined entity (Csatolt egyed)
  • As data source of 1form section can be 1 table/ query, Address and Re-sidence are queried into 1view(Nézet) datasource

SubForm base entity

SubForm joined entity

Sql:Select

StartDate,

EndDate,

Door,

Floor,

From

(

Residence R

Inner Join

Address A

On

R.AddressID=

A. AddressID);

  • Data Source (Adatforrás) connector: bidirectional data connection of a form section and a table/SQL query:
  • Cannot Create record:( )/can:( )
  • Cannot Read record:( )/can:( )
  • Cannot Update record:( )/can:( )
  • Cannot Delete record:( )/can:( )

SubForm datasource SQL query

2 procurement 2 11 advanced database diagram 2 11 2 data stream overview
2.Procurement: 2.11.Advanced Database Diagram: 2.11.2.Data Stream Overview
  • Click for enlarged view: ProcurementADD.docx and for animated guide: ProcurementPrezi.exe
content of the practice3
Content of the Practice
  • Checking Home Assignment 2: Purchase Info Records
  • 2.Procurement Scenario (Continued)
    • 2.7.Invoice Processing
      • 2.7.1.MM: Enter Vendor Invoice (Szállítói Számla):MIRO
      • 2.7.2.MM: Display Invoice Document and Order History:MIRO
      • 2.7.3.FI:Check subledger account of vendor:FBL1N
      • 2.7.4.FI: Payment:F-58
      • 2.7.5.Checking paid items:FBL1N
    • 2.8.Cross-module integration of MM:Procurement
    • 2.9.MM Reporting:
      • 2.9.1.MM:List display:ME2L
      • 2.9.2.MM:LIS standard analysis:MCE3
    • 2.10.Procurement: Business Process Diagram (BPD)
      • 2.10.1.BPD Elements
      • 2.10.2.Procurement: Process Overview
    • 2.11.Procurement: Advanced Database Diagram (ADD)
      • 2.10.1.ADD Elements
      • 2.10.2.Procurement: Data Stream Overview
  • Home Assignment 3: LIS Flexible report
  • References
  • Object/GUI Symbols
home assignment 3 lis flexible report
Home Assignment 3: LIS Flexible Report
  • RepeatABC-analysis of vendorsatPurchOrg = 1000classifyingvendors by:
    • Strategy = AbsolutePO value
    • In 3 categories:
      • A = 60%,
      • B = 35%,
      • C = 5%
  • Send a screenshot of resulting diagram (5points)
references
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
Object Symbols

Partner (Partner)

Anyag (Material)

Sarzs (Batch)

Bevitt anyag (Partner material)

Készlet (Inventory)

Raktár (Deposit)

Gyári szám (Serial number)

Darabjegyzék (Bill of materials)

Szortiment (Sortiment)

Anyagmeghatá-rozás (Material Identification)

Árazás (Pricing)

Engedmény (Allowance)

Fizetési mód (Payment Method)

Számla (Invoice)

Bizonylat (Voucher)

Értékesítés támogatás (Sales Promotion)

Direkt mail (Direct mail)

Ajánlat (Offer)

Árazás (Pricing)

Rendelés (Order)

Validáció (Validation)

Szerződés (Contract)

Szállítás (Transport)

Hitel (Credit)

Ütemezés (Scheduling)

Szerviz (Service)

Vevőszolgálat (Customer Service)

Kattintás (Click)

Dupla kattintás (Double Click)

Adatbevitel (Write)

Csak olvasható (Read Only)

  • Cég (Company)
  • Gyár (Plant)
  • Értékesítési szervezet (Sales Department)
  • Üzletkötő csoport (Sales Representative Group)
  • Értékesítési integráció (Sales Integration)
  • Csatorna (Channel)
  • Földrajzi hely (Geographic Location)
  • Kiszállítási hely (Delivery Location)
  • Szállítási mód (Transportation Mode)
  • Rakodási pont (Loading Point)
  • Árucsoport (Product Group)
  • Értékesítési terület (Sales Area)

Click

Right

Click

gui symbols
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
ad