Jit Purchasing 230 Bpp en Us

EHP4 for SAP ERP 6.0

June 2010

English

Purchasing with JIT Delivery Schedules (230)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Purchasing with JIT Delivery Schedules (230): BPD

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 26


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 26


Contents

1 Purpose........................................................................................................................................ 5

2 Prerequisites................................................................................................................................ 6

2.1 Master Data and Organizational Data...................................................................................6

2.2 Business Conditions..............................................................................................................7

2.3 Roles..................................................................................................................................... 7

3 Process Overview Table...............................................................................................................9

4 Process Steps............................................................................................................................ 10

4.1 Create Scheduling Agreement............................................................................................10

4.2 Maintain Delivery Schedule.................................................................................................12

4.3 Generation of Scheduling Agreement Releases..................................................................14

4.4 Print/Transmit Schedule Release........................................................................................15

4.5 Goods Receipt.....................................................................................................................16

4.6 Invoice Verification..............................................................................................................18

4.7 Self-Billing Invoice Verification with ERS (optional).............................................................20

5 Follow-Up Process..................................................................................................................... 23

5.1 Outgoing Payment...............................................................................................................23

5.2 G/L: Period-End Plant.........................................................................................................23

6 Appendix.................................................................................................................................... 24

6.1 Reversal of Process Steps..................................................................................................24

6.2 SAP ERP Reports...............................................................................................................25

6.3 Used Forms......................................................................................................................... 25

6.4 Support / Closing Considerations........................................................................................27

© SAP AG of 26


Purchasing with JIT Delivery Schedules

1 Purpose

Working with scheduling agreements can shorten processing times and reduce the amount of paperwork you are faced with. One delivery schedule can replace a large number of discrete purchase orders or contract release orders.

Inventories can be reduced to a minimum. You can carry out your manufacturing operations on the Just-in-Time (JIT) principle.

Your vendors require shorter lead times. Smaller deliveries are required, which can be spaced out over a longer period. Delivery scheduling enables vendors to plan and allocate their resources more efficiently.

This process Purchasing with JIT Delivery Schedules (230) works close together with the process Sales with Scheduling Agreements (231): The receiving company uses optionally a self-billing-scenario and transfers the invoice information via EDI to the selling company. In the selling company this information reduces automatically the outstanding open items.

The Self-Billing/ ERS process only works with the ERS customer 100020 and the ERS vendor 300020.

Optional: Self-Billing Process Flow

1. The Customer orders the goods via a MM-delivery schedule (230).

2. The vendor creates a delivery with reference to the SD scheduling agreement/order in the system (231).

3. The vendor posts goods issue of the delivery (231).

4. The vendor creates an initial billing document, which is not sent to the customer (231).

5. The customer receives the materials and creates a goods receipt and references to the delivery note number in the posting (230).

6. The customer creates a self-billing document for the goods received, using the MM ERS functions. (230).

7. The customer transmits the self-billing document to the vendor per EDI (in this case: ALE). The document must include a number that the target system can use to determine an SD document number (for example, the SD delivery) (230).

8. The vendor system reads and checks the transmission, which can contain several IDocs and therefore several deliveries (231).

9. The vendor initiates processing of the transmission, in which the open value from the internal invoice is compared with the value in the self-billing document (231).

10. If the values match, an external reference number is updated in the billing (FI) document (231).

© SAP AG of 26


2 Prerequisites

2.1 Master Data and Organizational Data

SAP Best Practices Standard Values

Essential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and customers.

This master data consists of standardized SAP Best Practices default values, and enables you to go through the process steps of this scenario.

Additional Master Data (Default Values)

You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Master / Org. data

Value Master / Org. data details Comments

Material R230-1 Raw material for external procurement, no batch, no serial number

Material H20 Trading Good for Reg. Trading (reorder point planning)

with serial numbers, no batch

Only use if you have activated the building block Serial Number Management (126).

Material H21 Trading Good for Reg. Trading (reorder point planning)

no Serial no.; batch controlled (Exp. Date)

Only use if you have activated the building block Batch Management (117).

Plant 1000 Plant1

Storage Location

1020 Plant 1000 Shop floor w/o lean WM

Storage Location

1030 Plant 1000 Shipping w/ lean WM

© SAP AG of 26


Master / Org. data

Value Master / Org. data details Comments

Vendor 300020 Vendor domestic 00 ERS

Vendor 300000 Vendor domestic 00 For processing without ERS

Company Code

1000 Company Code 1000

Purchase Organization

1000 Purch. Org. 1000

Purchase group

100 Purch. Group 100 Plant 1000

Purchase group

101 Purch. Group 101 Plant 1000

2.2 Business Conditions The business process described in this Business Process Documentation is part of a bigger chain of integrated business processes or scenarios. As a consequence, you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario:

Business condition Scenario

You have completed all relevant steps described in the Business Process Documentation Prereq. Process Steps (154).

Prereq. Process Steps (154)

2.3 Roles

UseThe following roles must have already been installed to test this scenario in the SAP Netweaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business Role Details Activity

Purchaser SAP_NBPR_PURCHASER-S

Create Scheduling Agreement (ME31L)Maintain Delivery Schedule (ME38)Generate Scheduling Agreement Releases (ME84)Print/Transmit Schedule Release (ME9E)

© SAP AG of 26


Business Role Details Activity

Warehouse Clerk

SAP_NBPR_WAREHOUSECLERK-S

Goods Receipt (MIGO)

Warehouse Clerk

SAP_NBPR_WAREHOUSECLERK-S

Create Material Document (MBST)

Warehouse Manager

SAP_NBPR_WAREHOUSEMANAGER-M

Evaluated Receipt Settlement (MRRL)

Accounts Payable Accountant

SAP_NBPR_AP_CLERK-S

Invoice Verification (MIRO)Cancel Invoice Document (MR8M)

2.3.1 Defining Queries for Personal Object Worklist (POWL)The following queries must be defined to test this scenario in the SAP NetWeaver Business Client (NWBC). You only need these queries if you are using the NWBC interface. You do not need these queries if you are using the standard SAP GUI.

The queries are necessary to access role specific worklists in the SAP NetWeaver Business Client (NWBC).

For more information about the creation of queries, see the section Creation of Queries in Personal Object Worklists (POWLs) in the Quick Guide to Implementing the SAP Best Practices Baseline Package (US) document.

Business Role

Application Object Type

Variant Name

Variant Selections

Selection Criteria

Query Name

Warehouse Clerk

Worklist All Purchasing Documents Ready for Goods Receipt

Plant: 1000

Company Code: 1000

For example, All Purchasing Documents Ready for Goods Receipt

ResultYou can now process the scenario.

© SAP AG of 26


3 Process Overview Table

Process step External process reference

Business condition

Business role

Trans-action code

Expected results

Create Scheduling Agreement

Purchaser ME31L Scheduling agreement created

Maintain Delivery Schedule

Purchaser ME38 Delivery Schedule saved

Generation of Scheduling Agreement Release

Purchaser ME84 Schedule releases generated

Transmit schedule releases

Purchaser ME9E Schedule releases transmitted

Goods receipt Warehouse Clerk

MIGO Goods receipt for the schedule agreement is posted

Invoice Verification Accounts Payable Accountant

MIRO The invoice is verified and posted

Generate credit memo

Accounts Payable Accountant

MRRL Credit memo is generated and posted

© SAP AG of 26


4 Process Steps

4.1 Create Scheduling Agreement

UseThis activity is used to create the scheduling agreement for the material/vendor combination if it has not been maintained yet. If the scheduling agreement is already present in the system you can skip this step.

Procedure1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC Menu Logistics Materials Management Purchasing Outline Agreement Scheduling Agreement Create Vendor known

Transaction Code ME31L

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Purchaser (SAP_NBPR_PURCHASER-S)

NWBC menu Purchasing Outline Agreement Scheduling Agreements Create Scheduling Agreement

2. On the Create Scheduling Agreement: Initial screen, make the following entries:

Field Name User Action and Values Comment

Vendor <Vendor>

Agreement Type LPA

Purch. Organization 1000

Purchasing Group 100

Plant 1000

3. Choose Enter.

4. On the Create Scheduling Agreement: Header Data screen, enter the Validity End date (current date + 2 years).

5. Choose Enter.

6. On the Create Scheduling Agreement: Item Overview screen, make the following entries:


Material For example <R230-1> To avoid locking problems, only use one material in the scheduling agreement.

© SAP AG of 26



If you want to use several materials, you also have to create several scheduling agreements.

Target qty For example <100000>

Net Price 30 for material R230-1

Material H20 = 17.55 13.50Material H21 = 17.55 13.50

If you use the self-billing scenario with process 231 you should use the same prices to avoid differences!

SLoc <storage location> Material R230-1 = 1020

Material H20 = 1030

Material H21 = 1030

7. Choose Enter.

8. On the Create Scheduling Agreement: Item Overview screen, select item 10 and choose Item Details.

9. On the Create Scheduling Agreement: Item 00010 screen, make the following entries:


Tax Code I1

10. Choose Enter.

1. On the Create Scheduling Agreement: Item Overview screen, select item 10 and choose Additional Data.

11. On the Create Scheduling Agreement: Item 00010 Additional Data screen, make the following entries:


Kanban Indicat. X Replenishment Element for Kanban

This setting is only relevant for material R230-1

Creation Profile 0001 14 days JIT and 6 months FRC

JIT Indicator 1 Automatically

If you intend to run the process with scenario 233 – Repetitive Manufacturing (REM) with KANBAN Supply into Production, you need to set the Kanban indicator on the Create Scheduling Agreement: Item 00010 Additional Data screen. This setting is only relevant for material R230-1.

12. Choose Enter.

13. Choose Save.

© SAP AG of 26


14. Go Back (F3) to the SAP Easy Access Screen (SAP GUI) or:Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultYou have created a scheduling agreement.

4.2 Maintain Delivery Schedule

If you use material R230-1, you must run 233 – Repetitive Manufacturing (REM) with KANBAN Supply into Production instead of maintaining delivery schedules manually. The quantities and dates in the current schedule stored in the system thus directly reflect current requirements of materials.

UseScheduling agreement releases provide information to vendors regarding the quantities of a material that are to be delivered and the desired delivery dates. A scheduling agreement release enables you to record the current status of the lines of a delivery schedule stored in the system for a scheduling agreement item and then transmit this status to the vendor.

The following procedure is only relevant for Material H20 and H21. For Material R230-1 delivery schedules will be created via 233 – Repetitive Manufacturing (REM) with KANBAN Supply into Production.

You can use this procedure to verify the delivery schedule that has been generated by 233 – Repetitive Manufacturing (REM) with KANBAN Supply into Production.

PrerequisitesScheduling agreement must be available. Refer to preliminary step Create Scheduling Agreement.



SAP ECC Menu Logistics Materials Management Purchasing Outline Agreement Scheduling Agreement Delivery Schedule Maintain

Transaction Code ME38


© SAP AG of 26



NWBC menu Purchasing Outline Agreement Scheduling Agreements Maintain Scheduling Agreement Schedule

2. On the Maintain Sch. Agmt Schedule: Initial screen, enter the number of the Scheduling Agreement in the dialog box. You can search for the agreement with F4-Help entries like vendor number, agreement type LPA, purchase org 1000 etc.

3. Choose Enter.

4. On the Maintain Sch.Agmt Schedule: Item Overview screen, mark the relevant line of item 010.

5. Choose Delivery Schedule (F2).

6. On the Maintain Sch. Agmt Schedule: Delivery Schedule for Item 00010 screen, choose the next open item line (fields are not grey and open for maintaining) and make the following entries:


Delivery Date <Today’s date> You have to set this data to ensure to make a goods receipt with relation to this agreement.

Scheduled Quantity 100 (for example)

StDelDate <Today’s date> (Same entry as Delivery Date)

Delivery Date <Today’s date + 7> You have to set this data to ensure to make a goods receipt with relation to this agreement.


StDelDate <Today’s date + 7> (Same entry as Delivery Date)

Delivery Date <Today’s date + 14> You have to set this data to ensure to make a goods receipt with relation to this agreement.


StDelDate <Today’s date + 14> (Same entry as Delivery Date)

7. Choose Enter.

8. Confirm the warning message, Can delivery be met? by choosing Enter.

9. Confirm the warning message, Can delivery date be met? (Realistic delivery date: xx.xx.xxxx), by choosing Enter.

10. Confirm the warning message, Deliver Date: next workday is xx.xx.xxxx? by choosing Enter.

11. Save your entries and go Back (F3) to the SAP Easy Access Screen (SAP GUI) or:Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

Result

© SAP AG of 26


You have created the schedule lines for the selected material either manually for material H20 and H21or via 233 – Repetitive Manufacturing (REM) with KANBAN Supply into Production for R230-1.

4.3 Generation of Scheduling Agreement Releases

UseThe schedule lines of a scheduling agreement release contain finalized information for the vendor regarding quantities and delivery dates. The schedule lines are recorded with the aid of the release documentation and can thus be displayed and verified at any time. The release documentation enables you to see which schedules you transmitted to the vendor during the last two weeks, for example, and check the correctness of goods receipts against the relevant schedule lines.



SAP ECC Menu Logistics Materials Management Purchasing Outline Agreement Scheduling Agreement Create SA Release

Transaction code ME84



NWBC menu Purchasing Outline Agreement Scheduling Agreements Generation of Sched. Agmt. Releases

2. On the Create Releases screen, make the following entries:


Forecast and JIT Schedules

<set indicator>

Plant 1000

Material <Material Number> R230-1; H20; H21

Vendor <Vendor>

Scheduling Agreement <Scheduling Agreement Number>

Scheduling agreement number from the previous step

JIT Scheds – Acc. To Strat. In Profile

<set indicator>

FRC Scheds – Acc. To Strat. In Profile

<set indicator>

Test Run <Off>

Display Options – All Items

<set indicator>

Layout 01 SAP

3. Choose Execute.

© SAP AG of 26


4. Choose Exit and go Back (F3) to the SAP Easy Access Screen (SAP GUI) or:Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultSchedule agreement releases have been generated.

4.4 Print/Transmit Schedule Release

UseThis step enables you to output individual SA releases. Schedules are transmitted via EDI, in the Best Practice environment they are printed for better visualization.



SAP ECC Menu Logistics Materials Management Purchasing Outline Agreement Scheduling Agreement Delivery Schedule Print/Transmit

Transaction code ME9E



NWBC menu Purchasing Outline Agreement Scheduling Agreements Message Output: Sch. Agmt. Schedules

2. On the Message Output screen, make the following entries:


Document Number <Scheduling agreement number>

Scheduling agreement from the previous step

Purchasing Organization

1000

Application EL Purch. SchAgrRelease

Processing Status 0 Not processed

3. Choose Execute.

4. On the Message Output screen, mark the relevant scheduling agreement and select Output Message.

5. Go Back (F3) to the SAP Easy Access Screen (SAP GUI) or:Choose Exit (Shift+F3) twice and confirm the Business client message with Yes, to return to SAP Home (SAP NetWeaver Business Client).

Result

© SAP AG of 26


Scheduling Agreement releases have been printed (or transmitted, in case you would have enabled EDI).

When you want to use the Self-Billing scenario, you have to continue now with the process Sales with Scheduling Agreements (231).

Process all paragraphs until 4.8 Billing of internal Invoice, then continue with the remaining paragraphs of 230 and afterward with the remaining of 231.

4.5 Goods Receipt

UseA goods receipt is the physical entry of the goods and materials on-stock. The goods receipt comes from external suppliers or from in-house production. All goods receipts increase the stock.

You have two options to post the goods receipt. To give you both options, this current scenario describes the classic method. The second option of goods receipt is via the Kanban monitor. This is described in 233 – Repetitive Manufacturing (REM) with KANBAN Supply into Production.

Prerequisites The delivery schedule is created and the purchased material is available.



SAP ECC menu Logistics Logistics Execution Inbound Process Goods Receipt for Purchase Order, Order, Other Transactions Enter Goods Receipt for Purchase Order

Transaction code MIGO

2. On the Goods Receipt Purchase Order screen, make the following entries:

Field Name Description User Action and Values Comment

No field name (first field in the main screen area)

Goods Receipt Select the action from the input help

No field name (second field in the main screen area)

Purchase Order Select the document type from the input help.

© SAP AG of 26


3. Choose Enter (SAP GUI) or choose Execute (SAP NetWeaver Business Client).

4. Make the following entries:

Field name Description User Action and Values Comment

GR Goods receipt

101

Field next to Purchase Order

Scheduling Agreement Number

Delivery Note Delivery number: absolutely necessary, when you use the self-billing-scenario 231 together with 230

5. Choose Enter.

In case there is no delivery scheduled today, you get the message: Document 5500000XXX does not contain any selectable items.

Since surplus deliveries are not allowed in this scenario, make sure that you created delivery schedule items for the corresponding date.

6. If material H20 is being used, choose Create Serial No. automatically in Item details (Tab: Serial Numbers).

7. Select the Item OK checkbox at the bottom of the screen.


9.


Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S)

NWBC menu Warehouse Management Receiving Purchase Order

1. Choose the query All Purchasing Documents Ready for Goods Receipt, select your purchasing document and choose Create Material Document.

2. On the Goods Receipt Purchase Order screen, make the following entries:

Field name Description User Action and Values Comment

Delivery Note Delivery number: absolutely necessary, when you use the self-billing-scenario 231 together with 230

3. Choose Enter.

© SAP AG of 26


In case there is no delivery scheduled today, you get the message: Document 55000000XX does not contain any selectable items.

Since surplus deliveries are not allowed in this scenario, make sure that you created delivery schedule items for the corresponding date.

4. If material H20 is being used, choose Create Serial No. automatically in Item details (Tab: Serial Numbers).

5. Select the Item OK checkbox at the bottom of the screen.


ResultThe goods receipt for the delivery schedule was posted.

As soon as the goods receipt is posted, you get a system message regarding the document number of the goods receipt.

Financial postings:

Material Debited Accounts Credited Accounts Cost Element / CO Object

Raw Materials (ROH)

131000 Invt- Raw Material

530000 G/L Price Var

211200 Gds Rcvd/ Inv Rcvd

Trading Goods

(HAWA)

135075 Invt- Trading Goods

530000 G/l Price Var

211200 gds Rcvd/ Inv Rcvd

4.6 Invoice Verification

UseInvoice verification is the final part of the procurement process in Materials Management (MM). It provides the link between the Materials Management component and the Financial Accounting, Controlling, and Asset Accounting components.

Invoice verification in Materials Management completes the materials procurement process.

Prerequisites The goods receipt for the scheduling agreement schedule has already taken place. Billing has arrived from the vendor.

© SAP AG of 26




SAP ECC menu Logistics Materials Management Logistics Invoice Verification Document Entry Enter Invoice

Transaction code MIRO


Business role Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S)

NWBC menu Accounts Payable Posting Invoices Enter Incoming Invoice w/ PO Reference

If you execute the transaction for the first time, enter the company code 1000 in the Enter Company Code dialog box, and choose Enter.

2. On the Enter Incoming Invoice: Company Code 1000 screen, enter the information as specified in the table below:


Transaction Invoice Choose the entry using the input help.

Invoice Date <date mm/dd/yyyy> Today’s date

Purchasing Document number

<scheduling agreement number from previous steps>

On PO reference tab in lower screen area

Item Number of Purchasing Document

<scheduling agreement item number from previous steps>

On PO reference tab in lower screen area

3. Choose Enter.

4. With the purchase order information displayed, enter the invoice amount including taxes and mark the Calculate Tax checkbox and choose the appropriate tax code.


Result1. The invoice is verified and posted.

2. Payment can now take place.

3. The system confirms the posting and displays the document number.

4. The document is stored in the system under this document number.

© SAP AG of 26


Financial postingsMaterial Debited Accounts Credited Accounts Cost Element / CO Object

Raw Materials (ROH)


300020 Vendor Domestic (ERS)

300000 Vendor Domestic 00

Trading Goods

(HAWA)


300020 (for ERS settlement)


4.7 Self-Billing Invoice Verification with ERS (optional)

UseInvoice verification is the final part of the procurement process in Materials Management (MM). It provides the link between the Materials Management component and the Financial Accounting, Controlling, and Asset Accounting components.

Invoice verification in Materials Management completes the materials procurement process.

In this scenario we are using Evaluated Receipt Settlement (ERS).

When you use Evaluated Receipt Settlement (ERS), you agree with the vendor that the latter will not submit an invoice in respect of a purchase order transaction. Instead, the system posts the invoice document automatically on the basis of the data in the purchase order (price) and goods receipts (quantity). This procedure eliminates invoice variances and manual handling.

Prerequisites The goods receipt for the scheduling agreement schedule has already taken place.



SAP ECC menu Logistics Materials Management Logistics Invoice Verification Automatic Settlement Evaluated Receipt Settlement (ERS)

Transaction code MRRL


© SAP AG of 26


Business role Warehouse Manager (SAP_NBPR_WAREHOUSEMANAGER-M)

NWBC menu Warehouse Management Inventory Control Environment Evaluated Receipt Settlement

2. On the Evaluate Reicept Settlement (ERS) with Logistics Invoice Verification screen, enter the information as specified in the table below:


Company Code

1000

Plant 1000

Vendor 300020

Doc. selection

4 1 Document selection per vendor

2 Document selection per purchase order

3 Document selection per order item

4 Document selection per delivery document/service entry

Test Run Deselect Space

3. Choose Execute.

4. You will get a list of the generated Invoice Document Numbers. Notice them to follow the self-billing process in scenario 231: ________________________

Result1. A credit memo is posted.

2. The system creates a message ERS6 for the credit memo, so that the information can be transmitted to the vendor

3. The printout of the credit memo is executed automatically and immediately (see settings in SAP GUI transaction MRM3 for Output Type ERS6 and defaults in your user settings in transaction SU3) Processed output type ERS6 is required for the self-billing process in scenario 231.

4. You also have the possibility to start the printout manually:


SAP menu Logistics Materials Management Logistics Invoice Verification Further Processing Output Messages

Transaction code MR90

© SAP AG of 26



Business role Accounts Payable Accountant (SAP_NBPR_AP_CLERK_DIFM-S)

NWBC menu Account Payable Posting Invoices Messages for Invoice Documents( MR90)

5. On the Output Massages in Logistics Invoice Verification screen, enter the information as specified in the table below:


Output Type ERS6

Processing mode

2 Repeat processing

Invoice Document No.

<document saved in step 4>

Fiscal Year <actual physical year>

Company Code

<your company code>

6. Choose Execute.

7. Mark the line with your document, and choose print preview.

8. The system also creates a message ERS6 for the credit memo, which is transmitted to the vendor via EDI. Further processing is described in the sales scenario 231.

Financial postingsMaterial Debited Accounts Credited Accounts Cost Element / CO Object

Raw Materials (ROH)


300020 Vendor Domestic (ERS)


Trading Goods

(HAWA)


300020 (for ERS settlement)


© SAP AG of 26


5 Follow-Up Process

5.1 Outgoing Payment

For this activity, run the 158 – AP – Accounts Payable scenario document in its entirety, using the master data from this scenario document.

5.2 G/L: Period-End Plant

For this activity, run the 159 – GL – Period End Closing in Financial Accounting scenario in its entirety, using the master data from this scenario document.

© SAP AG of 26


6 Appendix

6.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Delivery

Transaction code ( SAP GUI) ME38

Reversal: Delete Delivery Schedule

Transaction code ( SAP GUI) ME38

Business role Purchaser

Business role menu Purchasing Outline Agreement Schedule Agreements Maintain Sched. Agreement Schedule

Comment Double-click the schedule agreement item and remove the scheduled quantity for the dates you want to cancel.

Goods Receipt

Transaction code ( SAP GUI) MIGO

Reversal: Cancel Material Document

Transaction code ( SAP GUI) MBST

Business role Warehouse Clerk

Business role menu Warehouse Management Consumption and Transfer Create Material Document

Comment Cancel release of document

Invoice Verification

Transaction code ( SAP GUI) MIRO

Reversal: Cancel Invoice Document

Transaction code ( SAP GUI) MR8M

Business role Accounts Payable Accountant

Business role menu Accounts Payable Posting Invoices Cancel Invoice Document

Comment

© SAP AG of 26


6.2 SAP ERP Reports

UseThe table below lists the most frequently used reports that help you to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

ReportsReport title Transaction

Code (SAP GUI)Comment

Stock Overview MMBE A list of stock is displayed.

Purchasing Documents ME3L A list of outline agreements.

Material Documents MB51 A list of the material documents, which were posted for one or more materials.

Invoice Documents MIR5 A List of invoice documents.

GR/IR Account MR11 Maintain GR/IR clearing account.

6.3 Used Forms

UseIn some of the activities of this business process, forms are used. The table below provides details on these forms.

Common form name

Form type Used in process step

Output type Technical name

DLS-Forecast SAP Script LPH1 MEDRUCK

DLS-JIT SAP Script LPJ1 MEDRUCK

© SAP AG of 26


6.4 Support / Closing ConsiderationsInvoice Documents

Transaction Code (SAP GUI)

Comments

MR11The GR/IR clearing account is cleared at the end of a period or fiscal year for those order items that no further goods receipts or invoices are expected for.

© SAP AG of 26

Jit Purchasing 230 Bpp en Us

Documents

Transcript of Jit Purchasing 230 Bpp en Us