726 scen overview en fr

7/31/2019 726 Scen Overview en FR

1/10

Invoice Verification

SAP Best Practices for Retail(France)

SAP Best Practices


2/10

Scenario Overview - 1

Purpose

The Logistic Invoice Verification is a part of Material Management (MM). Logistic

Invoice Verification is closely connected with the SAP components Finance (FI)

and Controlling (CO). It provides the information for payment or evaluation of

invoices to these components. All functions of normal invoice verification are

available in logistic invoice verification. Normal invoice verification and logistic

invoice verification can be used alongside each other if needed.

Benefits

Some functions as Unlimited multiple selection are only available in Logistic


An incoming invoice contains a wealth of information

An important question is the reference of the invoice, which uniquely identifies itto a transaction. If there is such a reference, the system calls on its previous

knowledge and proposes the appropriate values during verification of the

invoice

An invoice can be blocked

price negotiations are conducted at least once a year

A part of the conditions agreed with the vendor is applied retroactively instead of

directly with the merchandise invoice.

Purpose and Benefits:


3/10


Key process flows covered

Goods Receipt-Based Invoice Verification with Reference to purchase

order/delivery note without/with Differences

Invoice Verification in Background

Automatic Settlement Accept a quantity/price Variance and Release a Blocked Invoice

Purpose and Benefits:


4/10


Required

SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows

Retail Buyer Invoice Verification

SAPApplications Required:


5/10

Process Flow Diagram

Create PurchaseOrder / Execute

Goods Receipt

Check Invoice

Goods Receipt

Based InvoiceVerification

AutomaticSettlement (ERS,

Consignment,Invoicing Pan)

EnterDialog Invoice(In Mode, Parking, In

the Background)

Purchase Order

Based InvoiceVerification

With Reference toPurchase Order

RetailBu

yerInvoiceVerification

Prepa

ration

If Anomalies

Exist

With Reference toDelivery Note

With Reference toDelivery Note With Reference toPurchase Order

Correcting anInvoice (Accept a

quantity pricevariance, Invoice

reduction forquantity price

variance, Automaticclearing ofvariances)

Post Invoice


6/10


Assignment


VendorDistribution center

Goods receipt

Order number

Goods receipt

quantity

Invoice dataentry

Company Code

Gross amount

Order number

PO


7/10


Financial Accounting

Logistic

Start Invoice Verification

Enter Vendors invoice

Invoice

correct ?

Assign to order / goods

receipt

Transfer accepted

invoices

Post invoice

Correction


8/10


Enter Invoice data

Invoice Verification online

The invoice will be entered and checked online

Invoice Verification in the background

You enter the Invoice data online and the system will verify in the background

Automatic Settlement

Based on predefined rules the invoice will be posted automatically

Assign the invoice to order, goods receipt, delivery note,...

Document parking

You receive an invoice, enter the data in the system, and save the invoice

document. The system does not make any postings. You can change this parked

document. When you have finished changing the document, you can post the

parked document.


9/10

Corrections

Depends on the Situation there are several Corrections possible

Accept a quantity variance

Accept a price variance

Reducing an invoice because of quantity variance

Reducing an invoice because of price variance

Subsequent Debits/Credits

Posting Total-Based Differences

Transfer the invoice to the Financial Accounting


10/10

Legend

Symbol Description Usage Comments

To next / From last Diagram: Leadsto the next / previous page of theDiagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document


Budget Planning: Indicates abudget planning document


Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

DiagramConnection

Hardcopy /Document

Financial

Actuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable Clerk or Sales Representative. This bandcan also identify an organization unit or group,rather than a specific role.

The other process flow symbols in this table go intothese rows. You have as many rows as required tocover all of the roles in the scenario.

Role bandcontains taskscommon to thatrole.

External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.

Flow line (solid): Line indicates the normal sequenceof steps and direction of flow in the scenario.

Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line canalso lead to documents involved in the process flow.

Connects twotasks in a

scenarioprocess or anon-step event

Business Activity / Event: Identifies an action thateither leads into or out of the scenario, or an outsideProcess that happens during the scenario

Does notcorrespond to atask step in thedocument

Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario

Corresponds toa task step inthe document

Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.


Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenario here


Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does notusuallycorrespond to atask step in thedocument;Reflects achoice to bemade after stepexecution

External

to

SAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

726 scen overview en fr

Documents