sc process+wm

EHP5 for SAP ERP 6.0

June 2011

English

Subcontracting (138)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Subcontracting (138): BPD

Copyright

© Copyright 2011 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, 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 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 Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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 40


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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 TEXTKeys 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 40


ContentsSubcontracting..................................................................................................................................... 6

1 Purpose........................................................................................................................................ 6

2 Prerequisites................................................................................................................................ 7

2.1 Master Data and Organizational Data...................................................................................7

2.2 Business Conditions............................................................................................................10

2.3 Preliminary Steps................................................................................................................11

2.3.1 Initial Requirement Situation........................................................................................11

2.3.2 Execute MRP...............................................................................................................14

2.4 Roles................................................................................................................................... 14

3 Process Overview Table.............................................................................................................16

4 Process Steps............................................................................................................................ 19

4.1 Assign Purchase Requisition / Create Subcontract Order...................................................19

4.2 Create Subcontract Order Manually (w/o MRP) (Optional).................................................20

4.3 Approval of Purchase Orders..............................................................................................21

4.4 Create Outbound Delivery Request.....................................................................................22

4.4.1 Stock Monitoring for Vendor.........................................................................................24

4.5 Pick Confirmation (optional)................................................................................................25

4.6 Generate Transfer Order (optional).....................................................................................25

4.7 Confirm Transfer Order (optional).......................................................................................26

4.8 Post Goods Issue................................................................................................................27

4.9 Posting In-time Consumption of Components (Optional Step)............................................28

4.10 Receive Goods from Subcontracting PO.........................................................................29

4.11 Invoice Receipt from Subcontracting PO.........................................................................31

4.11.1 Review Invoice Receipt from Subcontracting PO.........................................................32

4.12 Output Messages in Case of Invoice Reduction (Optional)..............................................34

4.13 Post Outgoing Payment...................................................................................................34

5 Follow-up Processes.................................................................................................................. 36

5.1 G/L: Period-End Closing in Financial Accounting................................................................36

6 Appendix.................................................................................................................................... 37

6.1 Reversal of Process Steps..................................................................................................37

6.2 SAP ERP Reports...............................................................................................................39

6.3 Used Forms......................................................................................................................... 40

6.3.1 Procurement.................................................................................................................40

6.3.2 Goods Movements.......................................................................................................40

© SAP AG of 40


Subcontracting

1 PurposeThe MM Subcontracting process involves sending raw components to a vendor for specific manufacturing processes and receiving the value-added finished material back into inventory.

A subcontract purchase requisition is either generated via the Material Requirements Planning (MRP) process or manually by a requestor. A Purchaser validates the accuracy of the purchase requisition and converts it into a purchase order. The purchase order is subject to approval based on predefined parameters prior to being issued to a vendor.

The consumption of sent components is recorded upon receipt of the value-added finished material. The vendor sends the invoice for the services provided which is paid during the normal payment cycle

On goods delivery, the scenario focuses on the following activities:

Purchase order creation based on a scheduled purchase requisition created by last MRP run

Optional: manual purchase order creation

Purchase order approval (if required)

Outbound delivery

Goods issue for delivery and shipment to subcontractor.

On goods receipt, the scenario focuses on the following activities:

Goods receipt for purchase order delivered by subcontractor

Component reservations and consumption of component quantities as provision of material

Invoice receipt by line item

Invoice verification and validation of tax expenses

Outgoing payment

As of enhancement package 4, you can post the real-time consumption of components. This can be useful in situations where the subcontracting process lasts longer, and you want to more precisely track component usage by subcontractors.

The necessary steps for posting in-time consumption are covered in this document.

To use this feature, you must make additional settings in Customizing and create additional master data. For more information, see step 4.9 in this document and also the appendix in the configuration guide 138_BB_ConfigGuide_EN_US.doc

© SAP AG of 40


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

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 R13 Raw material as subcontracting component with line item, NORM (PD planning), no batch, no serial number

See sections Business Conditions and Preliminary Steps








See sections Business Conditions and

© SAP AG of 40


Master / org. data


Preliminary Steps







Material S21 Semi finished Good for Trading / Repetitive manufacturing with line item category NORM (PD planning), no batch, no serial number


Material S22 Semi finished Good for Reg. Trading / production with line item category NORM (PD planning), phantom assembly, no batch, no serial number


Material S23 Semi finished Good for Reg. Trading / production with line item category NORM (PD planning), for subcontracting process, no batch, no serial number








Material S24 Semi finished Good for Reg. Trading / production with line item category NORM (PD planning), subcontracting, no serial number, batch controlled (FIFO strategy)


© SAP AG of 40


Master / org. data


Material S25 Semi finished Good for External procurement with line item category NORM (PD planning), subcontracting, no serial number, no batch


Plant 1000 Plant 1

Plant 1100 Plant 2

Storage Location

1020 Plant 1000 Shop floor w/o lean WM

Storage Location

1030 Plant 1000 Shipping w/ lean WM

Storage Location

1040 Plant 1000 Shipping w/o lean WM

Storage Location

1050 Plant 1000 Stores w/ lean WM

Storage Location

1060 Plant 1000 Returns

Storage Location

1120 Plant 1100 Shop floor w/o lean WM

Storage Location

1130 Plant 1100 Shipping w/ lean WM

Storage Location

1140 Plant 1100 Shipping w/o lean WM

Storage Location

1160 Plant 1100 Returns

Shipping Point 1000 Plant 1000 Shipping Point 1000

Shipping Point 100R Plant 1000 Shipping Point 100R

Shipping Point 1100 Plant 1100 Shipping Point 1100

Shipping Point 110R Plant 1100 Shipping Point 110R

Sales organization

1000

Distribution channel

10

Division 10

Vendor 300007 Vendor Domestic 07-Subcon.

Company Code

1000 Company Code 1000

Purchase 1000 Purch. Org. 1000

© SAP AG of 40


Master / org. data


Organization

Purchase group

100 Group 100 Plant 1000

Purchase group


Purchase group


Purchase group


Purchase group


Purchase group


Purchase group


Purchase group


Purchase group

200 Purch. Group 200 Plant 3000

Purchase group


Purchase group


Purchase group


2.2 Business ConditionsThe 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 steps described in the Business Process Documentation Prerequisite Process Steps (154). These process steps include the step Roll MM Period to Current Period. Perform this activity if the MM period in the system is not set to the current period. Usually, this activity has to be done once a month.

Prerequisite Process Steps (154)

To run through this scenario, the materials must be available in stock. If you use trading goods (HAWA) you can either:

Procurement w/o QM (130)

© SAP AG of 40


Business condition Scenario

Run through the procurement w/o QM (130) process or

Create stock using transaction MIGO (for more information, see Preliminary Steps).

To run through this scenario, the materials must be available in stock. If you use finished goods (FERT) you can either:

run through the Make-to-Stock Production - Discrete Industry (145) process (for material F126) or

create stock using transaction MIGO (for more information, see Preliminary Steps).

Make-to-Stock Production - Discrete Industry (145) (material F126)

2.3 Preliminary Steps

2.3.1 Initial Requirement Situation

UseThe MRP run only creates purchase requisitions if the demand is bigger than the available quantity. You can check the requirement situation in the Stock/Requirement List. If necessary, you can reduce the quantity of unrestricted use by posting a goods issue.

To create demand, use BB109, step 4.1 Sales Order Entry.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP system Logistics Materials Management Material Requirements Planning (MRP) MRP Evaluations Stock/Requirements List

Transaction code

MD04

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

Business role Production Planner

(SAP_NBPR_PRODPLANNER_S)

Business role menu

Production Evaluation Reporting Display Stock/Requirements Situation

2. Fill in the material number and the plant and go on with the process.

Field name User action and values Comment

© SAP AG of 40


Material S23

Plant Plant_1(1000)

In the view Stock/Requirement List, you can see the MRP elements. If there are purchase orders you can cancel them by running the 130 – Procurement to stock step 5.1. Only if the stock is too high, go on with the following step in this scenario. Otherwise go to step 4.2 or 4.3.

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


SAP system Logistics Materials Management Inventory Management Goods Movement Goods Movement (MIGO)

Transaction code

MIGO


Business role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK_S)

Business role menu

Warehouse Management Consumption and Transfers Other Goods Movement

2. On the Goods Issue Other screen, enter the following data:


Executable Action Goods Issue

Reference Document Other

Movement Type 562

Plant ( Where tab) 1000

Storage Location (Where tab)

Lean WM&HU (1050)

Material (Material tab) Barrel (Subcontract) (S23)

Quantity in Unit of Entry (Quantity tab)

Fill in the necessary quantity to fall below the sum of plant stock and firmed receipts.

Document date <actual day><actual day>

Posting date <actual day><actual day>

In case of batch management, the batch number has to be entered on the Batch tab.

In case of serial number management, the serial numbers has to be entered on the Serial numbers tab. Push Find. On the Display Material Serial Number screen, push Execute. On the Display Material Serial Number: Serial Number List screen, select the Serial numbers and choose Choose.

© SAP AG of 40


3. Choose Save and note the material document number: ______________________.

Result1. The unrestricted use stock of the material was reduced.

2. Financial postings:

Posting Key Account Description Amount (example) Currency

99 133000 Invt – S/Finshd Gds 825.00 USD

81 399130 Invt – Initial (Sem) 825.00 USD

© SAP AG of 40


2.3.2 Execute MRP

UseTypically, MRP is scheduled as a nightly batch job. To monitor the progress of the batch job, choose Show scheduling from the initial screen of this transaction. This activity needs to be carried out only for material S23.

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


SAP ECC Menu Logistics → Production → MRP → Planning → Total Planning → As Background Job

Transaction code

MDBT



(SAP_NBPR_PRODPLANNER_S)

Business role menu Production Job Planning MRP Run In Batch

2. On the Total Planning: Variants screen, select a BP variant (Yxxx) and choose Start Immediate.

ResultThe system generates planned orders, purchase requisitions, and exception messages. To generate a report for this activity, use the transaction code MD06 (Logistics → Production → MRP → Planning → Evaluations → MRP List - Collective Display) with plant #1000 and MRP controller 100.

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 Documentation 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

Employee (Professional User)

SAP_NBPR_EMPLOYEE_S Assignment of this role is necessary for basic functionality.

Production Planner SAP_NBPR_PRODPLANNER_S MD04 Check Requirement

© SAP AG of 40


Business role Technical name Process step

Situation,

MDBT Execute MRP

Production Supervisor

(SAP_NBPR_PRODPLANNER_M)

Purchasing Manager

SAP_NBPR_PURCHASER_M ME28 Approve Purchase Orders

Purchaser SAP_NBPR_PURCHASER_S ME21 Create Subcontract Order,

ME57 Assign Purchase Requisition,

ME9F

Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_S LT03 Create Transfer Order,

LT12 Confirm Transfer Order,

VL02N Create Outbound Delivery,

ME2O Stock Monitoring for Vendor,

MIGO Post Goods Receipt

Accounts Payable Accountant

SAP_NBPR_AP_CLERK_S MIRO, MIR5 Invoice Verification

© SAP AG of 40


3 Process Overview Table

Process step External process reference

Business condition

Business role Transaction code

Expected results

Initial requirement situation

– – Production Planner

MD04, MIGO

Stock of unrestricted use is reduced

Execute MRP – – Production Planner

MDBT The system generates planned orders, purchase requisitions, and exception messages. To generate a report for this activity, use transaction code MD06 (Logistics → Production → MRP → Planning → Evaluation)

Assign Purchase Requisition and Create Purchase Order

– This activity assigns a purchase requisition for planned subcontracting and creates a purchase order.

Purchaser ME57 Purchase order is created

Create Subcontract order manually

– – Purchaser ME21N PO is created

Approve Purchase Orders

– All the purchase orders that require release by

Purchasing Manager

ME28 Purchase orders are approved

© SAP AG of 40



Business condition


Expected results

Release Authorization person are listed and need to be approved. (Consider: The value, resulting from pricing, for a particular condition in total should exceed 500.00 USD)

Create Outbound Delivery Request

– Create External Procurement and Initial Stock Posting (optional)

Warehouse Clerk

MB1C Delivery is created

Stock Monitoring for Vendor

Enter storage location in which you have to post the stock for the components

Warehouse Clerk

ME20 The system generates a delivery pick list for shipping

Pick Confirmation (optional)

– Materials are picked for deliveries

Warehouse Clerk

VL02N Picking quantities are confirmed.

Generate Transfer Order (optional)

– Transfer is generated automatically. If not, this activity generates the transfer order

Warehouse Clerk

LT03 The transfer order is generated

Confirm Transfer Order

– This activity confirms the transfer order

Warehouse Clerk

LT12 The transfer order is confirmed

Post Goods Issue

– Delivery is ready to ship.

Warehouse Clerk(Shipping)

VL02N Material document transferring components from storage

© SAP AG of 40



Business condition


Expected results

location to stock at vendor.

Posting In time consumption of Components

Posting to Vendors consumption stock

Warehouse Clerk

MIGO Material Document is created transferring components from Vendor stock to Vendor consumption

Receive Goods from Subcontracting PO

– Receipt of goods from vendor

Warehouse clerk (Material Receiver)

MIGO Material document and accounting document showing receipt of purchased material and consumption of components

Invoice Receipt from Subcontracting PO

– Capture Invoice received

Accounts payable

MIRO Invoice document and accounting document

Output Messages in case of invoice reduction (optional)

Output messages for invoice reduction

Accounts Payable Accountant

MR90 Messages have been outputted.

Post Outgoing Payment

See Accounts Payable (outgoing payment) (158) scenario

See scenario no. 158



© SAP AG of 40


4 Process Steps

4.1 Assign Purchase Requisition / Create Subcontract Order

UseIn this activity a purchase requisition for planned subcontracting is assigned and a corresponding purchase order is created.



SAP ECC Menu

Logistics Material Management Purchasing Purchase Requisition Follow on functions Assign and Process

Transaction code

ME57


Business role Purchaser (SAP_NBPR_PURCHASER_S)

Business role menu

Purchasing Purchase Requisitions Purchase Requisitions Assign and Process Purchase Requisitions

2. On the Assign and Process Purchase Requisitions screen, enter the following values:

Field name Description User action and values Comment

Plant 1000

Purchasing Group 100

Scope of list ALV

Item category L (Subcontracting)

Material S23

3. Choose Execute.

4. Select the requisition lines from the Item Overview section on the screen.

5. Choose Edit Items to edit the line details that are at the bottom of the screen.

6. Choose Assign Source of Supply.

A yellow triangle is indicated for purchase requisitions where the system could not assign a clear source of supply. In this case, select the requisition Open item detail. In the Assign Source of Supply tab, the system displays a list of sources. Select supplier 300007 and choose Assigned source. Take care that the supplier has assigned a customer number in the master record (view control).

© SAP AG of 40


7. Select the line of the purchase requisition already assigned with a source from the Item Overview section.

8. To save the requisition changes, choose Save.

9. On the Assignments sub-page, select the checkbox of the source, then choose Create purchase order (a red and white button in the upper left).

10. On the Create Purchase Order screen, from the Document Overview section (on the left), select the requisition number from the list.

11. To extract the requisition information into the Purchase Order, choose Adopt.

If the PO is subject to Evaluated Receipt Settlement, in the Item Details section Invoice tab, enter I0 in the Tax Code field.

12. Choose Save and record the PO number: ____________________________.

ResultThe system generates a subcontract PO to vendor.

4.2 Create Subcontract Order Manually (w/o MRP) (Optional)

UseThis activity creates a purchase order for consumables. This activity is only required if you do not convert an existing purchase requisition as described in Assign Purchase Requisition / Create Subcontract Order.

You can store purchase order data as template for frequently used data. To save the data to a template, choose Save as Template. To load data from a template, choose Load from Template.



SAP ECC Menu

Logistics Materials Management Purchasing Purchase Order Create Vendor/Supplying Plant Known

Transaction code

ME21N



Business role menu

Purchasing Purchase Orders Purchase Orders Create Purchase Order

2. On the Initial screen, make the following entries and choose Enter:

© SAP AG of 40



PO type NB Standard PO

Purchasing Organization 1000

Purchasing Group 100

Company Code 1000

Vendor 300007

3. On the item line, make the following entries:


Item Category L

Material S23

Quantity Enter a quantity

Plant 1000

4. Choose Enter.

5. Save your entries. Record the PO number.

ResultThe PO is created.

4.3 Approval of Purchase Orders

UseAll the purchase orders that require release by an authorized person are listed and need to be approved.

Only POs with a value higher than 500.00 USD can be released in this transaction. POs with a value under this amount do not need to be released. For POs under this amount, this step can be skipped.



SAP ECC Menu Logistics Material Management Purchasing Purchase Order Release Collective Release

Transaction code

ME28

2. On the Release (Approve) Purchasing Documents screen, enter the following values:

© SAP AG of 40



Release Code 01

List with items X Check the checkbox

You need a release code for PO when the document type is NB or FO and the purchase group is 100, 101, 102, 103 and the value is greater than $500.00.

3. Choose Execute.

4. A list of all POs requiring release by this release code are displayed.

5. Select the PO line that you want to release.

6. Choose Release and then choose Save.


Business role Purchasing Manager (SAP_NBPR_PURCHASER_M)

Business role menu

Purchasing Approval Purchasing Documents Release Purchase Order - List

1. Enter in the Search criteria Release code 01 and press Apply.

2. Select your purchase order and press Release purchase order.

3. The purchase order is released.

4.4 Create Outbound Delivery Request

UseThis activity creates an outbound delivery request for components to be shipped to the vendor.

PrerequisitesThe scenario only runs, if there is enough stock for the material to be provided to the vendor. You have two options:

1. External Procurement

For this activity, run the 130: Procurement to Stock scenario document in its entirety, using the master data from this scenario document.

2. Initial Stock Posting (optional)

Procedure

© SAP AG of 40


Initial stock must be created for the following materials. You can use MMBE (or in NWBC, use the menu path Purchasing ® Materials and Stock ® Stock Overview) to check stock level.

Material Initial Stock

RAW13 (R13 13,500

RAW14 (R14) 13,500

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


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

Transaction Code

MB1C


Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK_S)

Business role menu

Warehouse Management Consumption and Transfers Other Goods Receipts

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


Movement Type 561

Plant 1000

Storage Location 1050

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


Material Material from the list

Quantity From the list

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

Result1. You have posted initial stock.


Material Debited Accounts

Credited Accounts Cost Element / CO Object

Raw Material (ROH) 131000 Initial stock entry

399100 Invent.-raw mat 1

none

Semi finished Material (HALB)

133000 Initial Stock entry

300130 Inventory Semi finished Mat

none

© SAP AG of 40


4.4.1 Stock Monitoring for Vendor1. Access the transaction choosing one of the following navigation options:


SAP ECC Menu

Logistics Material Management Purchasing Purchase Order Reporting SC Stocks per Vendor

Transaction code

ME2O



Business role menu

Warehouse Management Shipping Delivery Due Monitoring Subcontracting Stock for Vendor

2. On the SC Stock Monitoring for Vendor screen, enter the following values:


Vendor 300007 Sub Contract Services

Plant 1000

3. Choose Execute.

4. Check the required materials R13 and R14 choose Create Delivery.

5. Enter the storage location 1050 in which you have to post the stock for the components, and confirm with Continue (Enter).

6. In the Delivery for SC Vendor: Display message window, the system issues 2 messages: Delivery/ies XXXXXXXX has been saved and 1 Delivery/ies has been saved. Confirm with Continue (Enter) . Make a note of the delivery document number: __________

ResultThe system generates a delivery pick list for shipping.

Use transaction code VL03N (or in NWBC, use the path Warehouse Management Shipping Display Outbound Delivery) to display the delivery created in the previous step. Check the OverallWMStatus field in the Picking tab. If WM Trnsf order reqd appears, it means picking process has to be done by transfer orders via Warehouse Management System.

Option A: Is the transfer order required for the picking process?

If NO, go to 4.5.

© SAP AG of 40


If YES, go on with 4.8.

4.5 Pick Confirmation (optional)

UseThis activity picks, packs, and ships the relevant components to the vendor and this step is performed only if a WM transfer order is not required for picking.



SAP ECC Menu

Logistics Logistics Execution Outbound Process Goods issue for Outbound Delivery Outbound Delivery Change Single Document

Transaction code

VL02N




Business role menu

Warehouse Management Shipping Outbound Delivery Change Delivery

For NWBC: Select the respective delivery and choose Change.

2. On the Change Outbound Delivery screen, enter the delivery document number from the earlier section and choose Enter.

3. On the Delivery for Subcon. XXXXXXXX Change: Overview screen, choose the Picking tab, then enter the picked quantity equal to the delivery quantity.

4. Check the entries and choose Save.

ResultThe components are picked and ready to be shipped to the vendor. Proceed with step 4.8 to post the goods issue.

4.6 Generate Transfer Order (optional)

UseThis activity generates the transfer order.

This step should be skipped if the transfer order is generated automatically by the system. If a transfer order is not created, you can use this step to create one.

Procedure

© SAP AG of 40


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


SAP ECC Menu

Logistics Logistics Execution Outbound Process Goods Issue for Outbound Delivery Picking Create Transfer Order Single Document

Transaction code

LT03



Business role menu

Warehouse Management Consumption and Transfers Create Transfer Order for Delivery

2. On the Create Transfer Order for Delivery Note: initial Screen, enter the following values then choose Enter.


Warehouse Number

110 Lean WM (without stocks)

Delivery Delivery Number from step 4.4

3. Choose the Generate TO Item button and then choose Save.

ResultThe transfer order is generated.

4.7 Confirm Transfer Order (optional)

UseThis activity confirms the transfer order. This step should be skipped if the transfer order is confirmed automatically by the system. If a transfer order is not confirmed automatically, you can use this step to confirm one.



SAP ECC Menu

Logistics Logistics Execution Outbound Process Goods Issue for Outbound Delivery Picking Confirm Transfer Order Single Document In One Step

Transaction code

LT12



© SAP AG of 40


Business role menu

Warehouse Management Shipping Transfer Order Confirm Transfer Order

2. On the Confirm Transfer Order initial Screen, enter the following values then choose Standard.


TO Number Generated in step 4.7

Warehouse Number 110

3. Check all materials and choose Confirm Internally.

4. Save your entries.

ResultThe transfer order is confirmed.

4.8 Post Goods Issue

UseThis activity posts the issue of goods.



SAP ECC Menu

Logistics Logistics Execution Outbound Process Goods issue for Outbound Delivery Change Single Document

Transaction code

VL02N

2. On the Change Outbound Delivery screen, enter the delivery document number and choose Post Goods Issue.

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



Business role menu Warehouse Management Shipping Outbound Delivery

3. Choose the Due for Post Goods Issue tab.

4. In the Shipping Point field, enter 100R and choose Apply.

5. Select your delivery and choose Goods Issue

ResultThe system generates a delivery note to the vendor.

© SAP AG of 40


4.9 Posting In-time Consumption of Components (Optional Step)

If you do not want to perform steps for posting in-time consumption of components, go directly to the Receive Goods from Subcontracting PO step.

UseSince enhancement package 4, you can post in-time consumption components To use this, activate the business function LOG_MM_OM_1 (Outsourced Manufacturing). You can then post the consumption of Subcontracting components in-time (ongoing) before posting the final goods receipt.

This feature is useful when the subcontracting process takes a longer time and when you want to post a regular update of the stock situation of your subcontractor. The costs of the consumption are allocated in real time to an internal CO order. This CO has to be settled like any other production order during period-end closing.

The necessary additional configuration settings that must be done manually are described in the appendix of the configuration guide for this scenario. In the configuration guide an additional material S138 is created for this purpose.

You must perform this step before the goods receipt posting described in Receive Goods from Subcontracting PO using the master data modified/ created as described in the configuration guide appendix.

In this activity, the warehouse clerk receives a notification about the consumption of subcontracting components. The clerk then generates a goods issue referring to Subcontracting PO.

The controlling document can be viewed on the Production Order header by choosing Goto Documented Goods Movements.

PrerequisiteTo use the In-time Consumption Posting of subcontracting components, the flag RT-Consumption (Real-time-Consumption in the info record (View 'Purch.Org.Data 1) of the Subcontracting PO material must be set. If the flag RT-Consumption is set, the inbound delivery processing for Subcontracting PO's is not possible.

© SAP AG of 40




SAP ECC menu

Logistics Materials Management Purchasing Inventory Management Goods Movements Goods Issue For Purchase Order GI for Purchase Order (MIGO)

Transaction code

MIGO




Business role menu

Warehouse Management Consumption and Transfers Other Goods Movement

2. Make the following entries:


Purchase Order <Purchase Order number> From earlier step

Movement Type 543 Special stock O

3. Verify the quantity, and then choose Item OK.

4. Choose Check.

5. When the system responds with the message Document is OK, choose Post.

6. Verify the posting by using the transaction ME2COMP (Component consumption history)

ResultThe system generates a goods issue document number. Record the number here: __________The transaction ME2COMP can be used for monitoring the consumption of subcontracting components ordered by Subcontracting PO number.

4.10 Receive Goods from Subcontracting PO

UseThe vendor delivers the manufactured products and GR is to be posted for them in the system.



© SAP AG of 40


SAP ECC Menu

Logistics Materials Management Purchasing Purchase Order Follow on functions Goods Receipt

Transaction code

MIGO

2. Select Goods Receipt and Purchase Order from the two list boxes on top of the screen


Business role Warehouse Clerk (SAP_NBPR_WAREHOUSELCERK_S)

Business role menu Warehouse Management Receiving

3. On the Purchase Order Goods Receipt tab, select your Purchase Order and choose Post Goods Receipt.

2. Select the checkbox in the header data to print the material document via Output Control. Choose Collective Slip.

3. If an entry in the Delivery Note field is requested, enter the delivery note number.

4. Make sure that the movement type is 101.

5. Choose storage location 1050 – on the Where tab.

6. On the bottom of the screen, select the Item OK checkbox and choose Post. Make a note of the material document number: __________

If you performed the Posting In-time Consumption of Components (Optional Step) step and then try posting goods receipt for purchase order, the system displays two line items for manufactured product: one for the purchase order (with Movement type 101) and other for the Internal order created along with the Subcon PO ( with Movement type 521).

You must specify the storage location (for example 1050) for internal order item with MT 521 (line item 2). Choose Check at the bottom of the screen and then choose Post.

Only the Goods receipt for manufactured products is posted and no goods issue are recorded since you already posted the goods issue for components in the Posting In-time Consumption of Components (Optional Step) step.

Result1. Goods receipt is posted.



Credited Accounts

Cost Element / CO Object

Semifinished Product (HALB)

133000 Inv.chg.sale own prd

211200 Unfinished products

none

Semifinished Product (HALB)

520085 Extacty for gds/svc

650085 GR/IR clrg.ext. proc.

TR 1201 Purch & Stores 1 610000 Ext.acty for gds/svc

© SAP AG of 40



Credited Accounts

Cost Element / CO Object

Raw Material (ROH)

131000 Invent.-raw mat 1

510085 Cons Subctr

none

4.11 Invoice Receipt from Subcontracting PO

UseThe invoice verification is done in this activity.



SAP ECC Menu

Logistics Materials Management Purchasing Purchase Order Follow on functions Logistics Invoice Verification

Transaction Code

MIRO


Business role Accounts Payable Accountant (SAP_NBPR_AP_CLERK_S)

Business role menu

Accounts Payable Posting Invoicing Enter Incoming Invoice w/PO Reference

1. On the Enter Incoming Invoice: Company Code XXXX screen, select 1 Invoice from the Transaction dropdown menu, then enter the following values then choose enter:

Field name Description User action and values

Comment

Invoice date <date of document>

Amount <value of document>

Tax amount <value of document>

Reference <invoice number of vendor>

Purchase Order/Scheduling Agreement

Enter PO number

Layout Invoice reduction Optional entry, if Invoice Reduction is necessary

2. Having the PO information extracted, enter invoice amount and tax rate.

© SAP AG of 40


3. If an invoice reduction is necessary, select the value Vendor Error in the Correct ID field. After this the system displays two more fields: In the Invoice amount in document currency of vendor invoice field enter the amount from the invoice. In the field Qty invoiced in vendor invoice in PO order units you have to enter the quantity from the invoice. Due to this data, the invoice reduction is calculated by the system and you get the information message amount reduced in invoice is now XXX,XX USD.

4. Save your entries.

Result1. Invoice is posted.


Accounting type

G/L Act/Mat/Ast/Vndr Amount (example)

Currency

K 300007 Vendor 07 – Subcontracting / 69190 Walldorf

59.50 USD

S 211200 GR/IR-clearing – external procurement

59.50 USD

93 (Debit) or

83 (Credit)

530030

530030

Gain from inv. receipt small differences (MM)

Loss from invoice receipt small differences (MM)

only in case of small differences

USD

40 213500 Invoice Reduction Only in case of Invoice Reduction

USD

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

Posting key

G/L Act/Mat/Ast/Vndr Amount (example) Currency

21 211000 National_Vendor1 /69190 Walldorf

Only in case of Invoice Reduction

USD

50 213500 Invoice Reduction Only in case of Invoice Reduction

USD

4.11.1 Review Invoice Receipt from Subcontracting PO

UseThe invoice verification is done in this activity using the list overview on invoice documents.



© SAP AG of 40


SAP ECC Menu

Logistics Materials Management Logistics Invoice Verification Further Processing Display List of Invoice Documents

Transaction code

MIR5


Business role Accounts Payable Manager

(SAP_NBPR_AP_CLERK_M)

Business role menu

Accounts Payable Reporting Display List of Invoice Documents

2. On the Enter Incoming Invoice: Company Code XXXX screen, select 1 Invoice from the Transaction dropdown menu, then enter the following values then choose enter:

Field name Description User action and values

Comment

Company Code Company Code 1 (1000)

Document date <date of document>

Origin and Status Flag Invoices Verified online

Remark: Could not be used in NWBC

Button Follow-On Documents

Display of all Invoice Documents Data entry View

2. Choose Execute.

3. Having the information extracted, verify Invoice Documents.

4. On the Display list of Invoice Documents list screen, choose your invoice by selecting the corresponding line.

5. Choose Follow-On Documents to display subsequent documents.

If more than one subsequent document exists, in the dialog box, choose the document type. Select the line and choose Choose.

ResultInvoice documents were reviewed and assigned GL-Accounts were validated.

© SAP AG of 40


4.12 Output Messages in Case of Invoice Reduction (Optional)

UseWhen posting an invoice with reduced values, messages are not automatically output. If you want to output these messages, you must start the output manually. Alternatively you may also change the customizing settings for message type REKL to allow automatic output when saving the invoice.



SAP ECC menu

Logistics Materials Management Logistics Invoice Verification Further Processing Output Messages

Transaction code

MR90


Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK_S)

Business role menu Accounts Payable Posting Invoices Output Messages

2. On the Output messages in Logistics Invoice Verification screen, make the following entries:


Output Type REKL Complaint

Processing Mode

1 First processing

Invoice Document

<Document number from previous step>

Fiscal Year <Current fiscal year>

Company Code 1000

3. Choose Execute.

4. Select your document and choose Process.

4.13 Post Outgoing Payment

Accounts Payable (158)

UseIn this activity, you post the outgoing payment.

© SAP AG of 40


ProcedureUsing the master data from this document, complete all the activities described in the Business Process Documentation of the scenario: Accounts Payable (158) (the Post Payments Using the Payment Program task and the Post Manual Outgoing payment task).

© SAP AG of 40


5 Follow-up Processes

5.1 G/L: Period-End Closing in Financial Accounting

G/L: Period-End Plant (159)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 40


6 Appendix

6.1 Reversal of Process Steps

In 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.

Create Return Purchase Order

Transaction code ( SAP GUI)

ME21N

Reversal: Change Purchase Order


ME22N


Business role menu

Purchasing Purchase Order Purchase Order

Comment If the shown purchase order number is wrong, enter the relevant PO by choosing Other Purchase Order. Select the relevant items or select all items by choosing Select All. After that push the delete button and save the purchase order.

Create Outbound Delivery for Purchase Order


VL10B

Reversal: Change Purchase Order


VL02N


Business role menu Warehouse Management Shipping Outbound Delivery Change Delivery

Comment Cancel return delivery

Convert Assigned Requisitions to Purchase Orders


ME57

© SAP AG of 40


Reversal: Reverse a Purchase Order


ME22N


Business role menu

Purchasing Purchase Order Purchase Order

Comment If the shown purchase order number is wrong, enter the relevant PO by choosing Other Purchase Order. Select the relevant items or select all items by choosing Select All. After that push the delete button and save the purchase order.

Approval of Purchase Orders


ME28

Reversal: Cancel Release of Purchase Order


ME28

Business role Purchasing Manager (SAP_NBPR_PURCHASER_M)

Business role menu

Purchasing Approval Purchasing Documents

Comment Select the release Code 01 and set Cancel Release. Fill the document number into the field document number (optional). In the following view Release Purchasing Documents with Release Code 01 select the PO line and choose Cancel Release.

Receive Goods from Vendor to the Purchase Order


MIGO

Reversal: Cancel Material Document


MBST


Business role menu

Warehouse Management Consumption and Transfers Cancel Material Document

Comment If the material document number is not known, you can find it out by watching into the PO item line tab Purchase Order History (Transaction code ME22N: Materials Management → Purchasing → Purchase Order

© SAP AG of 40


→ Change).

Invoice Receipt by Line Item


MIRO

Reversal: Cancel Invoice Document


MR8M

Business role Accounts Payable Accountant (SAP_NBPR_AP_CLERK_S)

Business role menu

Accounts Payable Posting Invoices Cancel Invoice Document

Comment If the invoice number is not known, you can find it out by watching into the PO item line tab Purchase Order History (Transaction code ME22N: Materials Management → Purchasing → Purchase Order → Change).

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)

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

codeComment

Collective Conversion MD15 A list of possible planned orders.

Release Purchasing Documents

ME28 A list with all purchasing orders.

Purchasing Group Analysis

MCE1 A list with summarized data.

Vendor Analysis MCE3 Direct access to vendor-related data.

© SAP AG of 40


Report title Transaction code

Comment

MRP List MD05 The stock/requirements situation at the time of the last planning run.

6.3 Used Forms

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

6.3.1 ProcurementCommon form name

Form type Used in process step

Output type

Technical name

Purchase Order SmartForm Step 4 NEU YBUS_MMPO

6.3.2 Goods MovementsCommon form name Form type Used in

process step Output type

Technical name

Goods Receipt (individual slip)

SmartForm Step 4 WE01 YBUS_MMGR1

Goods Receipt (individual slip with inspection text)


Goods Receipt (collective slip)


© SAP AG of 40