utilities_building_blocks_china_cross_compamt_transfer_141_bpp.doc

SAP ECC 6.0 EhP3

August 2008

English

Internal Procurement Cross-Company Stock Transfer (141)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf

Business Process Documentation

Germany

© SAP AG of 23

SAP Best Practices Internal Procurement Cross-Company Stock Transfer (141): BPD

Copyright

© Copyright 2008 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. 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 23


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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 23


Contents

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

2 Prerequisites................................................................................................................................ 5

2.1 Master Data and Organizational Data...................................................................................5

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

2.3 Preliminary Steps..................................................................................................................7

2.3.1 Initial Stock Posting........................................................................................................7

2.4 Roles..................................................................................................................................... 8

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

4 Business Processes...................................................................................................................10

4.1 Creating Purchase Order.....................................................................................................10

4.2 Creating Outbound Delivery for Purchase Order.................................................................11

4.3 Posting Goods Issue for Delivery........................................................................................12

4.4 Checking Status of Stock Transfer......................................................................................13

4.5 Creating Billing Document (optional)...................................................................................14

4.5.1 Printing out Billing Document Manually (optional)........................................................15

4.6 Displaying Billing Document (optional)................................................................................15

4.7 Posting Goods Receipt for Stock Transport Order..............................................................16

4.8 Invoice Receipt by Line Item...............................................................................................18

4.9 Outgoing Payment (Cross-Company).................................................................................20

5 Appendix.................................................................................................................................... 20

5.1 Reversal of Process Steps..................................................................................................20

5.2 SAP ERP Reports...............................................................................................................21

5.3 Used Forms......................................................................................................................... 22

5.3.1 Procurement................................................................................................................. 22

5.3.2 Goods Movements.......................................................................................................22

© SAP AG of 23


Internal Procurement Cross-Company Stock Transfer

1 PurposeThis document describes the business process of cross-company stock transfer. The scenario supports the following functions for cross-company deliveries:

Partner functions

Customer for cross-company delivery (company code 1010 orders material from company code 1000)

Stock transport order for specific plant

Stock transport order - assign delivery type

Stock transport order - purchasing document type

Field selection for movement types

Permissible partner roles per account group

Additional views in the material master for material to be delivered

Conditions for the relevant material

Vendor for supplying plant

2 Prerequisites

2.1 Master Data and Organizational DataSAP 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 usually 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

© SAP AG of 23


You can also use customized values for any material or organizational data for which you have created master data. For more information about creating 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 H11 Trading Good for Reg. Trading with line item category NORM (PD planning)

no Serial no.; no batch

See sections Business Conditions and Preliminary Steps.

Material R13 Raw material as subcontracting component with line item, NORM (PD planning), no batch, no serial number

See sections Business Conditions and Preliminary Steps

Plant 1000 Plant 1 Shipping plant

Plant 1010 Plant3 Receiving plant

Storage Location

1020 Plant 1000 Shop floor w/o lean WM

Storage Location

1030 Plant 1000 Shipping w/ lean WM

Storage Location

1050 Plant 1000 Stores w/ lean WM

Storage Location

1010 Plant 1010 Receiving storage location

Vendor 491000 NATIONAL_PROD_PLANT_VENDOR

Purch. Org. 1010

Vendor 491100 NATIONAL_DIST_PLANT_VENDOR

Purch. Org. 1010

Vendor 493000 NATIONAL_PROD_PLANT_VENDOR

Purch Org 1010

Company Code

1000 Company Code 1000

Company Code

1010 Company Code 1010 Special Company code for Cross-company

Purchase Organization

1000 Purch. Org. 1000

Purchase Organization

1010 Purch. Org. 1010 Purch Organization for cross company

Purchase group

100 Group 100 Plant 1000

Purchase 101 Group 101 Plant 1000

© SAP AG of 23


group

Purchase group


Purchase group


Purchase group


Purchase group


Purchase group


Purchase group


Purchase group

101 Purch. Group 300 Plant 1010

2.2 Business ConditionsThe business process described in this Business Process Procedure 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 Procedure Prereq. Process Steps (154).

Prereq. Process Steps (154)

2.3 Preliminary Steps

2.3.1 Initial Stock Posting

UseThe purpose of this activity is to post initial stock from needed material, for example, H11 (R13) if there is no stock available. If there is enough stock, skip this step.

Prerequisites Material H11 (R13) must be maintained in plant 1000 / storage location 1030 (shipping Lean WM) and plant 1010 / storage location 1050 (stock Lean WM).

Procedure1. Access the activity using one of the following navigation options:

© SAP AG of 23


SAP ECC menu Logistics Materials Management Inventory Management Goods Movement Goods Receipt Other

Transaction code MB1C

2. On the Enter Other Goods Receipts: Initial screen, enter the following data then choose Enter:

Field name Description User action and values Note

Movement Type 561

Plant 1000

Storage Location Shipping 1030

3. On the Enter Other Goods Receipts: New Items screen, enter the following data then choose Enter:

Field name Description User action and values Note

Material H11 (R13)

Quantity 100 You can enter a different quantity.

4. On the Enter Other Goods Receipts: Collective Processing screen, save your settings.

ResultYou have stock from material H11 (R13).

2.4 Roles

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

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

Business role Technical name Process step

Buyer SAP_BPR_PURCHASER-S Create Purchase Order (ME21N)

© SAP AG of 23


Business role Technical name Process step

Warehouse Clerk

SAP_BPR_WAREHOUSESPECIALIST-S

Create Outbound Delivery for PO (VL10B),

Post Goods Issue for Delivery (VL02N),

Check Status of Stock Transfer (MMBE),

Post Goods Receipt for Stock Transport Order (MIGO)

Sales Billing SAP_BPR_SALESPERSON-S2 Create Billing Document(VF04)

Accounts Payable Accountant 1

SAP_BPR_AP_CLERK-S1 Invoice Receipt by Line Item(MIRO)

3 Process Overview TableProcess step External

process reference

Business condition

Business role

Trans-action code

Expected results

Create Purchase Order(Process)

Buyer ME21N The system creates the purchase order

Create Outbound Delivery for Purchase Order(Process)

The system creates a delivery number for the stock transport order.

Warehouse Manager

VL10B The system creates a delivery number for the stock transport order

Pick Outbound Delivery(Process)

Warehouse Manager

VL02N On the Picking tab, the delivery gets the picking status Fully picked

Post Goods Issue for Delivery(Process))

Warehouse Manager

VL02N The system runs the goods issue with the message Replen. Cross-company <xxxxxxx> has been saved

Check Status of Stock Transfer(Process)

Warehouse Manager

MMBE You get an overview of the stock in transit

Post Goods Receipt for Stock

Warehouse MIGO The system posts the goods

© SAP AG of 23


Process step External process reference

Business condition

Business role

Trans-action code

Expected results

Transport Order(Process)

Manager receipt for the purchase order to the unrestricted stock of the receiving plant

4 Business Processes

4.1 Creating Purchase Order

Procedure

1. 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 Purchase Order Create Vendor/Supplying Plant Known

Transaction code ME21N

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

Business role (Name) SAP_BPR_PURCHASER-S (Buyer)

Business role Menu Purchasing Purchase Orders Create Purchase Order

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

Field name Description User action and values

Comment

Order type Standard PO Order type NB

Vendor for example: 491000

Production Plant 1000

Org. data tab Choose

Purchasing org. 1010 Purchasing Organization 1010

Purchasing group

for example: 100 Group 100

Company code 1010 Company Code (1010)

Expand "Item overview"

Choose If item overview window is not visible

Material for example: H11 Or for example: R13

© SAP AG of 23


Order quantity for example: 10 Any other quantity

Delivery date <Default value>

Default value is Today.

If you take a date later than “at the end of the next week”, be sure to select the right date in step Create Outbound Delivery for Purchase Order

Net price Any Will be maintained from existing info record; Can be maintained manually if required ( you can describe conditions f. Example: Freight)

Currency CNY

Plant 1010 Inter Company Processing Plant (Plant from an other Company Code, receiving plant)

Storage location for example: 1050 (plant 1010)

Warehouse Lean WM in plant 1010

3. Choose Enter.

4. Choose Save (Ctrl +S) to save the purchase order.

ResultThe system creates the purchase order for cross company stock transfer.

4.2 Creating Outbound Delivery for Purchase Order

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


SAP ECC menu Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Create Collective Processing of Documents Due for Delivery Purchase Orders

Transaction code VL10B


Business role (name) SAP_BPR_WAREHOUSESPECIALIST-S (Warehouse Clerk)

Business role menu Warehouse Management Shipping Purchase Orders Due for Delivery

2. On the Purchase orders, fast display screen, make the following entries:

© SAP AG of 23


Field name Description User action and values Comment

Shipping point 1000

Delivery date Delete values

Rule for determining default value for delivery creation date

3 Due for shipment by the end of next week (+ past-due delivs)

Purchase orders tab

Supplying plant 1000

3. Choose Execute (F8).

4. Select items in overview screen and choose Create delivery in background (Shift + F7).

ResultThe system creates a delivery number for the stock transport order. The Show/hide delivery (Shift+F8) pushbutton displays/hides the delivery created by the program. See also the Log for delivery creation (Ctrl+F4). From here, you can display the created document number for the SD delivery by choosing Documents. Record the created number for the SD delivery.

4.3 Posting Goods Issue for Delivery

Procedure



SAP ECC menu Logistics Sales and Distribution Shipping and Transportation Post Goods Issue Outbound Delivery Single Document

Transaction code VL02N



Business role menu Warehouse Management Shipping Change Delivery

2. On the Change Outbound Delivery screen, enter the outbound delivery number and choose Enter.

3. Select the item line and go to the header Edit Incompleteness.

4. Select the item line and go to the header Environment Availability.

5. On the Replen.Cross-Company XXXXXXXX Change: Overview screen, make sure that the issuing storage location on the Picking tab page is 1030 (dispatch store) and choose Save.

© SAP AG of 23


6. You return to the Change Outbound Delivery screen. Choose the button Post Goods Issue.

ResultThe system runs the goods issued with the message Replen. Cross-company <xxxxxxx> has been saved.

The goods issue document (TF to stck in trans.) for the selected batch item can be seen in Display Outbound Delivery (Ctrl+F1) and Enter under Environment Document flow (F7).

4.4 Checking Status of Stock Transfer1. Access the transaction choosing one of the following navigation options:


SAP ECC menu Logistics Materials Management Inventory Management Environment Stock Stock Overview

Transaction code MMBE


Business role (name) SAP_BPR_WAREHOUSESPECIALIST-K (Warehouse Monitoring)

Business role menu Warehouse Management Inventory Control Stock Overview

2. On the Display of Stock in Transit screen, make the following entries:


Material number

H11 (R13) Material number of the material from the purchase order

Plant 1010 Inter Company Processing Plant (receiving plant)

3. Choose Execute (F8).

4. Choose Detailed Display. See stock type On-Order stock.

ResultYou get an overview of the stock in transit. This covers all of the material that has left the supplying plant and has not yet reached the receiving plant.

4.5 Creating Billing Document (optional)

UseIn this step the vendor (plant 1000) issues the invoice to the customer (plant 1010).

© SAP AG of 23


Procedure



SAP ECC menu Logistics Sales and Distribution Billing Billing document Process Billing Due List

Transaction code VF04

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

Business role Sales Billing(SAP_BPR_SALESPERSON-S2)

Business role menu Sales Billing Create Billing Document

2. (NWBC:Choose Billing due list ( Ctrl+F12) )

3. On the Process Billing Due List screen, make the following entries:

Field Description User action and values Comment

Billing date from From, for example, yesterday to one month from today

Sold-to party For example: 493000 Inter company customer

Delivery-related Select

Intercompany Billing

Select Must be set to get the cross company documents

4. Choose DisplayBillList.

5. On the Maintain Billing Due List screen, the system displays the delivery notes waiting to be billed.

6. Select the delivery you created earlier and choose button Individual billing document.

7. The Intercompany (IV) Create: Overview of Billing Items screen appears. To check the document, go to header Edit Log. A system message No error log created appears.

8. Choose Save. A system message Document 9xxxxxx has been saved appears.

9. Choose Back.

ResultA billing document has been created and the postings to FI and CO have been made.

The printout of the invoice is executed automatically and immediately (see settings in SAP GUI transaction VV33 for output type RD00 and defaults in your user settings in transaction SU3).

© SAP AG of 23


4.5.1 Printing out Billing Document Manually (optional)

UseYou have the possibility to start the printout manually.

ProcedureOption 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Sales and distribution Billing Billing document Display


1. Go to transaction VF03, in the screen Display Billing Document: From the menu choose Billing document Issue Output to

2. Mark the line with the message type RD00

3. Choose Print.


Business role Sales Billing

(SAP_BPR_SALESPERSON-S2)

Business role menu Sales Billing

1. Choose All Billing Documents tab page (refresh the current query if necessary).

2. Mark your billing document.

3. Choose Print Invoices.

4.6 Displaying Billing Document (optional)

UseIn this step the customer invoice will be reviewed regarding financial postings and pricing.

Procedure



SAP ECC menu Logistics Sales and Distribution Billing Billing document Display



Business role Sales Billing(SAP_BPR_SALESPERSON-S2)

Business role menu Sales Billing Create Billing Document

© SAP AG of 23


2. On the Display Billing Document screen, make the following entry:

Field Description User action and values Comment

Billing document The number of the external billing document you created previously

3. Choose Enter.

4. On the Invoice 900000xx (F2) Display: Overview of Billing Items screen, choose Accounting.

5. In the List of Documents in Accounting dialog box, choose the invoice 9000xxxx.

The goods were delivered from a plant that belongs to company code 1010. Nevertheless, the company code field in the accounting document shows that the customer invoice was posted in company code 1000. The original order was also entered for sales organization 1000.

6. Go back to the Invoice 900000xx (F2) Display: Overview of Billing Items screen.

7. On the Invoice 900000xx (F2) Display: Overview of Billing Items screen, choose Goto Header Header.The header data of the billing document is now displayed. In the Pricing procedure field, you can see that pricing procedure YBAA01 is used. The billing type IV is shown in the header.

8. Go back to the Invoice 900000xx (F2) Display: Overview of Billing Items screen.

9. Select the item and choose Pricing conditions header.The pricing conditions are then displayed.

You can see here that in pricing procedure YCAA01, the total comprises conditions PR00 (price), PI02 (Inter-company %) and MWST (Tax).

10. Choose Back。

4.7 Posting Goods Receipt for Stock Transport Order

Procedure



SAP ECC menu Logistics Materials Management Inventory Management Goods Movement Goods Receipt For Purchase Order PO Number Unknown

Transaction code MIGO


© SAP AG of 23



Business role menu Warehouse Management Receiving Other Goods Movement

2. On the Goods receipt Purchase order - <user name> screen, make the following entries:


Movement type List field GR Goods receipt 101 (here: Goods receipt for purchase order into warehouse/stores)

Reference document List field Outbound delivery

Document date <current date>

Posting date <current date>

Delivery note Enter the no. Delivery note from plant 1000

Entry is mandatory.

Bill of lading <optional> Enter the document number of bill of lading from plant 1000.

Enter Helpful to set the values first.

Item Detail: Where tab page

Choose

Storage location 1050 (Storage Lean WM) If not yet entered during creation of the purchase order

Item OK X Has to be flagged.

3. Choose Check.

4. Confirm messages.

You can ignore the message Document flow for delivery can not be updated, or for example, For batch xyz of material C10150, no class could be determined.

5. Choose Post or Save (Ctrl + S).

In NWBC，you can select any purchase order in tab All Open Purchase Orders, then choose Post Goods Receipt, in the screen Goods Receipt Purchase Order, seclect Restart from the toolbar, and you can post goods receipt to outbound delivery.

Result

© SAP AG of 23


The system posts the goods receipt for the purchase order to the unrestricted stock of the receiving plant (you can check this in transaction MMBE).

4.8 Invoice Receipt by Line Item

UseThe invoice verification is done here.

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


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

Transaction code MIRO


Business role Accounts Payable Accountant 1 (SAP_BPR_AP_CLERK-S1)

Business role menu Accounts Payable Invoice Enter Incoming Invoice

2. On the Enter Incoming Invoice: Company Code XXXX screen, select the Basic data sub-screen and make the following entries:


Invoice date Date of the invoice (for example: today)

Reference (Fictive) Invoice no. of the delivering plant

Amount Invoice (overall) amount (incl. Tax) of a the (fictive) invoice

Calculate tax X

Tax amount The system posts here the VAT tax of the PO amount

3. Go to the tab strip PO reference and make the following entries:


Purchase Order/Scheduling agreement

Relevant Purchase Order Number

Layout Invoice reduction

4. Choose Enter to get the PO data in the Item screen. Make sure that all relevant PO data are listed in the Item screen.

© SAP AG of 23


5. Choose Simulate to simulate the invoice values. A dialog box Simulate Document in CNY (Document currency) appears. Check that the balance has the amount ‘0’ and choose Back.

6. In case of messages. Clear messages are warnings and red messages are show stoppers. Fix red messages and choose Post to save the transaction. A message appears that will confirm posting and also advise if it is blocked for payment.

7. Choose Post to post the invoice.

Result 1. The invoice is booked. The system also executes the financial postings in dependency to the

data of the goods receipt and due to the input during invoice verification. The Goods Receipt / Invoice Receipt account is balanced, price differences are either booked on the inventory accounts (if the price control indicator in the material master is Moving price average and enough stock to cover the invoiced quantity is available) or on accounts for pricing differences (if the price control indicator in the material master is Standard price or not enough stock to cover the invoiced quantity is available). Document balances are booked due to tolerance limits (Price variance, small differences).

2. Financial postings

Posting key G/L Description Comment

31 (Credit) Example:

491000

Vendor

86 (Debit) 14010101 Goods Receipt / Invoice Receipt

40 (Debit) 22210101 Domestic Input tax or Depending on Tax Code

93 (Debit) or

83 (Credit)

64015001

64015002

Gain from inv. receipt small differences (MM)

Loss from invoice receipt small differences (MM)

Only in case of Small Differences

86 (Debit) or

96 (Credit)

86 (Debit) or

96 (Credit)

64015101 or

64015001

64015102 or

64015102

Price differences (expense) external products (for raw material and trading goods)Price differences external material revenue (for raw material and trading goods)

Price differences (expense) external products (for Semi finished products)Price differences external material revenue (for Semi finished products)

Depending whether you have positive or negative pricing differences and depending of material type

40 19990603 Invoice Reduction Only in case of Invoice Reduction

In case of Invoice Reduction the system creates a second financial document:

© SAP AG of 23


Posting key G/L Description Comment

21 Example:

491000

Vendor Only in case of Invoice Reduction

50 22210101 Input Tax Only in case of Invoice Reduction

50 19990603 Invoice Reduction Only in case of Invoice Reduction

4.9 Outgoing Payment (Cross-Company)

For this activity, run the 158 – AP – Accounts Payable scenario document in its entirety, using the master data from this scenario document. In this case there will be no real payment but an internal clearing.

The outgoing payment process will be described but not performed because the FI postings for Cross-company billing is not part of the solution.

5 Appendix

5.1 Reversal of Process StepsCreating a Purchase Order

Transaction code ( SAP GUI) ME21N

Reversal: Change Purchase Order

Transaction code ( SAP GUI) ME22N

Business role Buyer (SAP_BPR_PURCHASER-S)

Business role menu Purchasing Purchase Orders Change Purchase Order

Comment

© SAP AG of 23


Create Outbound Delivery for Purchase Order

Transaction code ( SAP GUI) VL10B

Reversal: Change Outbound Delivery

Transaction code ( SAP GUI) VL02N

Business role Warehouse Clerk (SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Warehouse Management Shipping Change Outbound Delivery

Comment Cancel Delivery

Post Goods Receipt for Stock

Transaction code ( SAP GUI) MIGO

Reversal: Cancel Material Document

Transaction code ( SAP GUI) MBST

Business role Warehouse Clerk (SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Logistics Materials Management Inventory Management Material Document MBST Cancel/Revers

Comment Cancel Goods receipt

5.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 BPP 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)

Note that the descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

ReportsReport title Transaction code Comment

Material Documents MB51 A list of the material documents that

© SAP AG of 23


were posted for one or more materials.

Warehouse Stock MB52 A List of the warehouse stock is displayed

Stock Overview MMBE A list of stock is displayed.

Execute Report KE30 A report concerning Plan/Actual Activities.

5.3 Used Forms

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

5.3.1 ProcurementCommon form name

Form type Used in process step

Output type

Technical name

Purchase Order SmartForm Step 4 NEU /SMBA0/AA_MMPO

5.3.2 Goods MovementsCommon form name

Form type Used in process step

Output type

Technical name

Goods Receipt (individual slip)

SmartForm Step 4 WE01 /SMBA0/AA_MMGR1

Goods Receipt (individual slip with inspection text)


Goods Receipt (collective slip)


© SAP AG of 23