Release Notes - SAP Help Portal

Release Notes for

Procurement and Logistics Execution

SAP enhancement package 5 for SAP ERP 6.0

SAP® What's New? – Release Notes

Release Notes for Procurement and Logistics Execution SAP enhancement package 5 for SAP ERP 6.0 of 57

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.



Procurement........................................................................................................ 4

Business Function Subcontractor Mgmt. (Down Payment Chains) ............... 4

LOG_FI_DPC_MM_1: Subcontractor Management (Down Payment Chains) (New)........ 4

Business Function Materials Management - Enhancements in Procurement .......................................................................................................................... 8

LOG_MM_CI_3: Materials Management - Enhancements for Procurement (New) .......... 8

LOG_MM_CI_3: Park and Hold in Service Procurement (New) ....................................... 9

LOG_MM_CI_3: Contract Handling for Invoices (new) .................................................. 11

LOG_MM_CI_3: MDM Catalog Connection for Service Procurement (New) .................. 12

LOG_MM_CI_3: Public Templates in Purchase Orders and Requisitions (New) ............ 13

LOG_MM_CI_3: Entering of Blocking Reasons in Purchase Orders (New) ................... 14

LOG_MM_CI_3: Changing of the Transportation and Loading Group (New) ................. 15

LOG_MM_CI_3: Sources of Supply for Outline Agreement Requisitions (New) ............. 16

LOG_MM_CI_3: Extended Document Flow in MM and SD Documents (New)............... 17

ISR_RETAIL_ENH_MAT_SEARCH: Retail, MM Enh. Mat. Search (New) ..................... 18

LOG_MM_CI_3: Buyer Role (enhanced) ...................................................................... 20

Business Function Outsourced Manufacturing 2 .......................................... 21

LOG_MM_OM_2: Outsourced Manufacturing 2 in ERP Operations (New) .................... 21

LOG_MM_OM_2: Enhancements for Outsourced Manufacturing .................................. 22

LOG_MM_OM_2: Multilevel Subcontracting (New) ....................................................... 24

LOG_MM_OM_2: Third-Party Order Processing for Subcontracting (New) ................... 25

LOG_MM_OM_2: Integration of External Third-Party Order Planning (New) ................. 28

Business Function Procurement - SRM Integration 2 .................................. 31

LOG_MM_P2PSE_2: Procurement - SAP SRM Integration 2 (New) ............................. 31

Business Function Cross-Company-Code Stock Transfer & Actual Costing ........................................................................................................................ 32

LOG_MM_SIT: Business Function MM, Stock in Transit, and Actual Costing (New) ...... 32

LOG_MM_SIT: Cross-Company-Code Stock Transfer and Customer Delivery (New) ... 33

LOG_MM_SIT: Intra-Company-Code Stock Transfer (New) .......................................... 40

LOG_MM_SIT: Movement Types (New) ....................................................................... 46

LOG_MM_SIT: Inbound Delivery with Stock in Transit (New) ........................................ 50

LOG_MM_SIT: Actual Costing for Processes with Stock in Transit (New) ..................... 52

Business Function Expediting Data in Purchase Order ............................... 54

LOG_XPD_EXT_1: Progress Tracking Data in the Purchase Order (New) .................... 54

Additional Release Notes ................................................................................. 56

Enterprise Service for Purchase Order Confirmation (New)........................................... 56

BAPI for Comprehensive Posting of Incoming Invoices (New) ....................................... 57



Procurement

Business Function Subcontractor Mgmt. (Down Payment

Chains)

LOG_FI_DPC_MM_1: Subcontractor Management (Down Payment

Chains) (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0, Enterprise Extension Financials

(EA-FIN 605), you can use the business function Subcontractor Management (Down

Payment Chains) (LOG_FI_DPC_MM_1).

This business function provides you with the following features for enhancing debit-side

and credit-side down payment chains:

Integration of credit-side down payment chains in the purchasing process for purchase

order processing

This simplifies subcontractor management for construction work in key industries that

have to manage this process, which includes construction, real estate management,

generation companies, and public administration.

If you have assigned the item category Service to an item in the purchase order, a

contract for the credit-side down payment chain is created or changed for this order

item when you save (if the relevant Customizing settings have been made). You see a

tab page that lets you access the contract in which the data from the purchase order is

preassigned. In credit-side down payment chains, the contract can be settled as

follows: With an advance payment, several partial invoices taking account of retention

amounts and service charges, a final invoice, and corrections after the final invoice

o Invoices and credit memos can only be entered in the SAP Easy Access menu

under Accounting -> Financial Accounting -> Additional Functions -> Down

Payment Chains -> Credit-Side Down Payment Chains (transaction

/SAPPCE/DPCK01). The logistics invoice verification (transaction MIRO (Enter

Invoice)) is not possible.

o When an invoice is created in the down payment chain, the system enters a

default value for the gross value determined from the service entry sheets that

have been entered and released so far. You can overwrite this default value.

Using message control in Customizing, you can specify that the gross value

cannot just be changed as required.

o If you post or cancel invoices in a down payment chain, the system updates the

commitments of the relevant purchase order item. A cancellation recreates the

commitment items, and a final invoice clears the commitment.

Integration of debit-side down payment chains in the sales process for sales order

processing

When you create or change a sales order, the system checks if a chain type of the

debit-side down payment chain has been assigned to the item category selected for the

sales document item.

o If there is an assignment, the system displays the Down Payment Chain tab

page in the item details of a sales document item and preassigns the chain type.

o If the user has entered all the required data for creating a debit-side down

payment chain, the system creates a debit-side down payment chain contract



when the user saves the sales order.

o You can release billing documents for down payment chains only in the following

transaction of the SAP Easy Access menu: Accounting -> Financial

Accounting -> Additional Functions -> Down Payment Chains -> Release

Billing Documents for Down Payment Chains (transaction

/SAPPCE/DPC_REL_INV).

o If the accounting employee releases the billing document to the debit-side down

payment chain, the system checks if a transaction category is assigned to the

billing type.

o If there is an assignment, the system triggers posting for the corresponding

transaction in the debit-side down payment chain. The employee can enter both

retention amounts and additional costs.

o When the posting is saved, an entry is created in the debit-side down payment

chains and an accounting document is created in Financial Accounting.

o You can cancel billing documents relevant for down payment chains in the

following transaction of the SAP Easy Access menu: Accounting -> Financial

Accounting -> Additional Functions -> Down Payment Chains -> Cancel

Billing Documents Relevant for Down Payment Chains (transaction

/SAPPCE/DPC_CANC_INV).

In the first step, select the billing document for a specific billing date. Detailed

information about the cancellation appears in a log.

You can use a Business Add-In (BAdI) to enhance the posting screen:

o You can use a Business Add-In to design your own tab pages in the contract.

The enhancement of the down payment chains allows an account assignment in

the contract to WBS elements, a cost center, network/activity, or order.

o For down payment chains whose partial invoice is posted as an invoice, you can

create everything from prepayments to final invoices. When you create a partial

invoice, the system proposes the down payments for clearing that are still open.

You can change this proposal, meaning you can choose not to clear the down

payment or only partially clear it. When you create a final invoice, all open down

payments are cleared.

o You can specify the basis for calculating retention amounts: Gross amount or net

amount of posting You can still specify which special G/L transaction the system

should use to update the retention amount category. The special G/L transaction

indicator determines the reconciliation accounts of the general ledger to which

the system posts the retention amounts (security retention amounts and special

retention amounts).

o You can enhance the additional costs function as follows:

- Specify the basis for calculating additional costs: Gross amount or net

amount of posting

- Specify if the update of credit-side and debit-side additional costs should

decrease costs or affect revenues.

o You can enhance the verification function as follows:

- Define a payment block for each verification category. If a verification was

defined with a payment block in the contract and the document does not

arrive within the period specified, the payment block is proposed when the

next posting is created. The user can predefine this.

- Assign documents for a verification category in the contract. The

documents are stored in the DMS.



o You can only release billing documents for down payment chains in the following

transaction: SAP Easy Access -> Accounting -> Financial Accounting ->

Additional Functions -> Down Payment Chains -> Release Billing

Documents for Down Payment Chains (transaction

/SAPPCE/DPC_REL_INV).

- If the accounting employee releases the billing document to the debit-side

down payment chain, the system checks if a transaction category is

assigned to the billing type.

- If there is an assignment, the system triggers posting for the

corresponding transaction in the debit-side down payment chain. The

employee can enter both retention amounts and additional costs.

- When the posting is saved, an entry is created in the debit-side down

payment chains and an accounting document is created in Financial

Accounting.

o You can cancel billing documents for down payment chains in the following

transaction: SAP Easy Access -> Accounting -> Financial Accounting ->

Additional Functions -> Down Payment Chains -> Cancel Billing

Documents Relevant for Down Payment Chains (transaction

/SAPPCE/DPC_CANC_INV). In the first step, select the billing document for a

specific billing date. Detailed information about the cancellation appears in a log.

Effects on Existing Data

The functions of the MM, Integration Materials Management and Financial

Accounting (LOG_MMFI_P2P) business function and the Subcontractor

Management (Down Payment Chains) business function (LOG_FI_DPC_MM_1)

cannot be used simultaneously in a purchase order item. You can activate both

business functions, but you cannot use them in the same purchase order item.

Effects on Customizing

To use the Subcontractor Management (Down Payment Chains) function, you must

activate the Enterprise Extension Financials Extensions (EA_FIN) and the business

function Subcontractor Management (Down Payment Chains)

(LOG_FI_DPC_MM_1).

You make the settings for this function in Customizing for Financial Accounting (New)

under Accounts Receivable and Accounts Payable -> Business Transactions -> Debit-

Side and Credit-Side Down Payment Chains -> Enhance Debit-Side and Credit-Side

Down Payment Chains:

o Integration -> Assign Chain Type to Purchase Order Document

Type

If you have set up the Customizing activity accordingly, you also see the Down Payment Chain tab page for a purchase order item with item catgory Service.

o Define Customer Enhancements -> BAdI: Posting the Down Payment

Chain

You can design a subscreen for posting a new down payment chain transaction.

You can also develop your own update logic for the accounting document.

o Define Customer Enhancements -> BAdI: Customer-Specific Tab

Pages in Contracts

You can design your own tabs in the down payment chain contract.

o Define Customer Enhancements -> Edit Sequence and Titles of Tabs

o Change Message Control



You can determine the type of message the system displays if there are

inconsistencies between a new down payment chain transaction and the

purchase order item.

o Assign Special G/L Indicator to Retention Amount Category

You can specify the G/L reconciliation account to which the system posts the

retention amounts.

o Assign Chain Type to Item Category for Sales Documents

If you have set up the Customizing activity accordingly, you also see the Down

Payment Chain tab page in the sales order under the detailed data for the item

category, and the system predefines the chain type.

o Assign Transaction Category to Billing Type

If you have set up the Customizing activity accordingly, the system posts the

corresponding transaction in the debit-side down payment chain and creates an

accounting document in Financial Accounting.

See also

SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp -> SAP

ERP Enhancement Packages -> ERP Central Component Enhancement Package

5 ->

o Business Functions (SAP Enhancement Package 5 for SAP ERP 6.0) ->

Business Functions in SAP ERP -> Enterprise Business Functions ->

Accounting -> Financial Accounting (FI) -> Accounts Receivable and

Accounts Payable (FI-AP/AR) -> Subcontractor Management (Down

Payment Chains) (LOG_FI_DPC_MM_1)

o SAP ERP Central Component -> Accounting -> Financial Accounting (FI) ->

Accounts Receivable (FI-AR) -> Accounts Receivable and Accounts

Payable (FI-AP/AR) -> Credit-Side and Debit-Side Down Payment Chains



Business Function Materials Management - Enhancements in

Procurement

LOG_MM_CI_3: Materials Management - Enhancements for Procurement

(New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605), the business

function Materials Management - Enhancements for Procurement (LOG_MM_CI_3)

is available.

This business function enables you to make the procurement of materials and services

more efficient, and to optimize the procurement processes between SAP ERP and SAP

SRM.

For more information, see the following release notes:

o Park and Hold in Service Procurement (New)

o Contract Handling for Invoices (New)

o MDM Catalog Integration for Service Procurement (New)

o Public Templates in Purchase Orders and Requisitions (New)

o Entering of Blocking Reasons in Purchase Orders (New)

o Changing of the Transportation and Loading Group (New)

o Sources of Supply for Outline Agreement Requisitions (New)

o Extended Document Flow in MM and SD Documents (New)

o Enhanced Material Search in Purchase Requisitions and

Purchase Orders (New)

o Buyer Role (Enhanced)

See also

SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp -> SAP ERP

Enhancement Packages -> ERP Central Component Enhancement Package 5 ->

Business Functions -> Business Functions in SAP ERP -> Enterprise Business

Functions -> Logistics.



LOG_MM_CI_3: Park and Hold in Service Procurement (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605), business

function Materials Management - Enhancements in Procurement (LOG_MM_CI_3),

you can park and hold purchase orders and purchase requisitions for materials and

services:

o Park purchase requisitions and purchase orders

o Hold incorrect purchase requisitions

Previously, the hold function was available only in purchasing documents for materials.

Purchase orders and purchase requisitions for services could only be saved.

The park function was already available in the Public Sector Management component.

In the business function Materials Management – Enhancements in Procurement

(LOG_MM_CI_3), park and hold are now both available centrally as standard in SAP

ERP, for both purchase orders and purchase requisitions.

You use the park and hold function to provisionally save incomplete documents for final

processing at a later date. This new function is available both for purchasing

documents that you create in SAP ERP itself and for purchasing documents that you

create in an SAP SRM service procurement scenario, with sourcing, reactions to

RFQs/bid invitations (RFx) and virtual shopping carts, and then transport to SAP ERP.

The system analyses and logs your processing steps, for example, on creation of a

purchase order. You can display these results in a message dialog. Depending on the

type of message, you can navigate straight from the message dialog to the relevant

point in the document, and continue processing.

Holding of Purchasing Documents

If you want to create a purchasing document, you may be missing some information at

that point in time, or you may be interrupted when creating the document. In this case,

you can still put, for example, an incomplete purchase order on hold, and finish it at a

later point in time before saving.

A purchasing document can originate in another system and be transported to the ERP

system. In this situation, too, you may need to put the purchasing document on hold

and continue processing it later.

Parking of Purchasing Documents

If you want to create a purchasing document, the document may be complete from the

materials management point of view, but some financial information may still be

missing at that point in time (FI view).

A purchasing document can originate in another system and be transported to the ERP

system. In this situation, too, the purchase document is complete from the materials

management point of view, but is missing financial information.

In both cases, you can then provisionally save (park) the purchasing document and

continue processing it at a later point in time before saving

Effects on System Administration

This function is available in the following transactions:

o Create Purchase Order (ME21N) and Change Purchase Order (ME22N)

o Create Purchase Requisition (ME51N) and Change Purchase Requisition



(ME52N)

Pushbuttons for park and hold have been added to the user interface. The visibility of

these pushbuttons depends on the processing stage of the purchasing document. If

you want to exit the creation process before it is finished, you can choose the relevant

pushbutton, and the system saves accordingly.


Before you can use the park and hold function, you must activate it in Customizing. In

Customizing for materials management, choose Purchasing -> Environment Data -> Activate 'Park and Hold' in Purchasing Documents.

Note

Note that you cannot reverse this setting.

See also

For more information, see SAP Library on SAP Help Portal at http://help.sap.com ->

Business Function Sets and Business Functions -> Enterprise Business

Function -> Logistics and SAP ERP Central Component -> Logistics -> Materials

Management (MM) -> Purchasing (MM-PUR).



LOG_MM_CI_3: Contract Handling for Invoices (new)

Use

As of SAP enhancement package 5 for ERP 6.0 (SAP_APPL 605), business function

Materials Management - Enhancements in Procurement (LOG_MM_CI_3) you can

create invoices with reference to contracts in the following ways:

o Invoice with a direct reference to an ERP contract or SRM central contract.

o Invoice with reference to a limit PO item which contains a reference to a contract.

o Invoice with a reference to a limit PO item without a contract reference with the

option to reference a contract during invoice verification.


The user interface has been enhanced in the following ways:

o A new screen allows you to view the document history for a contract

(Program/Screen: SAPLMMHIPO/0600).

o Six new fields relating to contract information and service selection have been

added to the invoice item list on the tab page PO Reference (Program/Screen:

SAPLMR1M/6310).

o A new tab page called Contract Reference has been added to the following

transactions:

Transaction Program/Screen

MIRO SAPLMR1M/6000

MIR7 SAPLMR1M/6000

MIR4 SAPLMR1M/6000


To enable users to post invoices directly to contracts, you must activate direct posting

to contracts in Customizing activity Activate Direct Posting to Contracts.

You can define the quota arrangement rules for various documents including invoices

in Customizing activity Define Quota Arrangement Usage.

See also

For more information see the main release note for Materials Management -

Enhancements in Procurement (LOG_MM_CI_3) or the SAP Help Portal

under http://help.sap.com -> Business Function Sets und Business Functions ->

Enterprise Business Function -> Logistics -> Materials Management.



LOG_MM_CI_3: MDM Catalog Connection for Service Procurement (New)

Use



you can use MDM catalogs when processing purchase orders, purchase requisitions,

and maintenance orders. This enables you to copy service structures with hierarchies

from the MDM catalog to purchase orders, purchase requisitions, and maintenance

orders.

The function harmonizes the service procurement process between SAP ERP and SAP

SRM and makes it easier to use. Now, the MDM catalog for services with hierarchical

structures is available as a central source of purchasing information.

For the new function, you can use service structures from an MDM catalog, which can

consist of up to five item levels. If select more than five levels, the system issues an

error message. You can copy individual service items or whole service structure from

the MDM catalog to purchasing documents.

As well as copying service items from the MDM catalog to related purchasing

documents, you can also transfer purchasing data from SAP ERP to SAP SRM, to the

MDM catalog.





(ME52N)

o Create Maintenance Order (ME51N) and Change Maintenance Order

(ME52N)

You can use the function Send Purchasing Data to Catalog (MECCM) to transfer the

purchasing data in SAP ERP to SAP SRM.


To set up an MDM Web service for data exchange between SAP ERP and SAP SRM,

you must define the relevant settings in Customizing. In Customizing for Materials

Management, choose Purchasing -> Environment Data -> Web Services: ID

and Description.

See also

For more information, see SAP Library on SAP Help Portal at http://help.sap.com ->

Business Function Sets and Business Functions -> Enterprise Business

Function -> Logistics and SAP ERP Central Component -> Logistics -> Materials

Management (MM) -> Purchasing (MM-PUR).



LOG_MM_CI_3: Public Templates in Purchase Orders and Requisitions (New)

Use



you can create purchase requisitions and purchase orders more efficiently by using

templates.

You can use the following functions:

o Create, use, and delete user-specific templates

o Create, use, and delete public templates, which are available to all users

You can use entered data as a template without having to save the document first.

From the templates you create, you can copy either header and item data or only item

data to a purchasing document.





(ME52N)

In these transactions, there are two additional pushbuttons: Save As Template and

Load from Template.

To create templates that are available to all users, you need the appropriate

authorizations (authorization object Create/Change/Delete Public Templates

M_TEMPLATE).

When you copy a user, the user-specific templates of the user you are copying are also

copied to the new user master record.

See also

SAP Library for SAP ERP on SAP Help Portal under http://help.sap.com/erp -> SAP

ERP Enhancement Packages -> ERP Central Component Enhancement Package

5 -> Logistics -> Materials Management (MM) -> Purchasing (MM-PUR).



LOG_MM_CI_3: Entering of Blocking Reasons in Purchase Orders (New)

Use



you can save the reasons for blocking a purchase order item in purchase orders.

In Customizing for Materials Management, you can create various blocking reasons

with language-dependent texts, which are available in a dropdown box when you block

purchase orders. When you block a purchase order item, you can select a suitable

blocking reason in the item details. You also define in Customizing whether the text for

a blocking reason ID can only be copied unchanged, or whether you can overwrite the

text with your own reason. If you overwrite the text for a blocking reason ID in the

purchase order, you lose the language dependency.


In the transactions ME21N (Create Purchase Order), ME22N (Change Purchase

Order), ME23N (Display Purchase Order), and ME29N (Release Purchase Order),

there are new fields for selecting and displaying a blocking reason when blocking

purchase order items. The system displays the following fields for blocked purchase

order items in the item details on the Purchase Order History tab page:

o Blocking reason ID (BLK_REASON_ID)

o Blocking reason text (BLK_REASON_TXT)


You define the Customizing settings for this function in Customizing for Materials

Management, under Purchasing -> Purchase Order -> Define Blocking Reasons.

See also

For more information, see SAP Library for SAP ERP Central Component on SAP Help

Portal at http://help.sap.com under Logistics -> Materials Management (MM) ->

Purchasing (MM-PUR).



LOG_MM_CI_3: Changing of the Transportation and Loading Group (New)

Use



you can change the transportation group and loading group in a purchase order.

When you create, change, and release a purchase order, you can change the values

for transportation group and loading group that are taken from the purchase order. You

can use the input help for the fields Trans. Group and LoadingGrp on the Shipping

tab page in the item details to display all the valid values that you have defined in

Customizing for Shipping. From these values, you can select a suitable transportation

group and loading group for your purchase order item.


In the transactions ME21N (Create Purchase Order), ME22N (Change Purchase

Order), and ME29N (Release Purchase Order), you can change the values of the

following fields in the item details, on the Shipping tab page:

o Trans. Group (TRAGR)

o LoadingGrp (LADGR)



LOG_MM_CI_3: Sources of Supply for Outline Agreement Requisitions (New)

Use


function Materials Management - Enhancements in Procurement (LOG_MM_CI_3), you

can also select outline agreement requisitions in the reports Assign Source of Supply to

Requisitions (ME56) and Assign and Process Purchase Requisitions (ME57).

If you select the new checkbox Outline Agreement Requisition, you have various

options for displaying outline agreement requisitions for sourcing and then processing

them further in the assignment list:

o You can display outline agreement requisitions without a supplying plant, in

addition to other selected purchase order requisitions, in the result list.

o You can display a result list that contains only outline agreement requisitions, if

you select the checkbox and choose RV (Outl. Agmt Requisn.) as the

document type.

o You can display individual outline agreement requisitions for sourcing, by

selecting the checkbox and entering the ID of the outline agreement requisition in

the Purchase Requisition field.


In the transactions ME56 (Assign Source to Purchase Requisition) and ME57 (Assign

and Process Purchase Requisitions), there is a new checkbox Outline Agreement

Requisition (P_OAREQ). Outline agreement requisitions are included in the results list

of reports only if you select this checkbox.



LOG_MM_CI_3: Extended Document Flow in MM and SD Documents (New)

Use


function Materials Management - Enhancements in Procurement (LOG_MM_CI_3), you

can display all the related purchasing and sales documents in purchase requisitions,

purchase orders, inbound deliveries, and outbound deliveries.

In the item overview, you can use the new pushbutton Extended Document Flow.

This pushbutton enables you to display purchasing and sales documents that are

related to the selected purchasing or sales item. For example, you can display the

sales documents related to a purchase requisition or purchase order item, or the

purchasing documents related to delivery items. You can only call the extended

document flow for deliveries that reference a purchase order.


In the item overview of the following transactions, you can use the new pushbutton

Extended Document Flow:

o ME52N and ME53N for changing and displaying purchase requisitions

o ME22N and ME23N for changing and displaying purchase orders

o VL02N and VL03N for changing and displaying outbound deliveries

o VL32N and VL33N for changing and displaying inbound deliveries



ISR_RETAIL_ENH_MAT_SEARCH: Retail, MM Enh. Mat. Search (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605 and EA-RETAIL

605), the business function Retail, MM Enhanced Material Search with Creation

(ISR_RETAIL_ENH_MAT_SEARCH) is available. With this business function, you can

enable the Enhanced Material Search with Creation function across a wide range of

transactions in SAP Materials Management, SAP Sales and Distribution, and SAP for

Retail.

From a business perspective, the features in this business function are specifically

designed to accelerate order creation for wholesale and retail customers. Enhanced

Material Search with Creation is the only search solution that allows you to find articles

along with their availability and prices in selected plants in one step. In addition, you

can find and create supplier catalog products without an article master with much

greater ease and efficiency.

From a technical perspective, you should experience some performance improvements

by using either the SAP Search Engine Service or SAP NetWeaver Search Engine

Service rather than searching directly using SAP ERP tables.

NOTE: This release note describes features and user interface modifications unique to

Materials Management. Consult release note SAP_APPL_605_EMS_M for more

information on general enhancements shared with Sales and Distribution or with SAP

for Retail.


Customizing

The Configure and Activate Enhanced Search with Creation Customizing activity has

been enhanced with the following:

o Creation Based on Material parameter, which allows you to create a new

material based on an existing material as a template using either a simplified

material creation approach or by way of the Modify Material Creation BAdI

o Creation Based on Catalog Item parameter, which allows you to create a new

material based on a supplier catalog item using either a simplified material

creation approach or by way of the Modify Material Creation BAdI

o Change Based on Material parameter, which allows you to modify a material

master data record using the Material Maintenance application (transaction

MM02).

You can access the Customizing by choosing Materials Management -> General

Settings for Materials Management -> Configure and Activate Enhanced Material

Search with Creation.

Supported Transactions

The following Materials Management transactions are now supported by the Enhanced

Material Search function:

o Create Purchase Order (ME21N)

o Change Purchase Order (ME22N)

o Create Purchase Requisition (ME51N)

o Change Purchase Requisition (ME52N)

o Create Allocation Table (WA01)



o Change Allocation Table (WA02)

New search criteria and result parameters

The following search criteria and result parameters have been added for purchasing

transactions:

o Availability Indicator

o Purchase Order Quantity

o Purchasing Order Price Unit

o Material

o Material Description

o EAN/UPC

o Plant

o Plant Name 1

o Unrestricted/ATP quantity

o Basic Unit of Measure

o Qualifier (Unrestricted stock or ATP stock)

o Purchase Price

o Currency

o Purchase Price Unit

o Purchasing Order Price Unit (Duplicate, but required)

o Old Material Number

o Material Group

o Material Group Description

o Product Hierarchy

o Material Type

o Vendor

o Vendor Name 1

o Vendor Sub Range

o Vendor Material Number

o Vendor Material Group

The following search criteria and result parameters have been added for allocation

table transactions:

o Material

o Material Description

o Material Category

o Material Type

o Material Group



LOG_MM_CI_3: Buyer Role (enhanced)

Use

As of SAP enhancement package 5 for ERP 6.0 (SAP_APPL 605), business function

Materials Management - Enhancements in Procurement (LOG_MM_CI_3), you can

create and process purchase requisitions by using the enhanced Single Processing of

Purchase Requisitions Web Dynpro application.

You start the enhanced Web Dynpro application from the buyer role 1.5 (Business

Package for Buyer 1.5). In this buyer role the Single Processing of Purchase

Requisition iView replaces the previous Create Purchase Requisition iView. In addition

to the previously existing functions you can now create, change, and display purchase

requisitions with service items and limit items. You can enter information about the

account assignment for service items, and you can enter a long text for service items,

service lines, and in the header note.

See also

o Release note LOG_MM_CI_3: LOG_MM_CI_3: Materials Management

- Enhancements for Procurement (New)

o SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp ->

SAP ERP Central Component -> SAP ERP Enhancement Packages -> ERP

Central Component Enhancement Package 5 -> SAP ERP Central

Component -> Logistics -> Materials Management (MM) ->

- Purchasing (MM-PUR) -> Purchasing Requisitions (MM-PUR-REQ)

- External Service Management (MM-SRV) -> Procurement of Services:

Processes -> Maintaining Service Specifications in Purchasing

Document



Central Component Enhancement Package 5 -> SAP ERP Cross-

Application Function -> Roles -> Business Packages (Portal Content) ->

Business Package for Buyer 1.5



Business Function Outsourced Manufacturing 2

LOG_MM_OM_2: Outsourced Manufacturing 2 in ERP Operations (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605), you can use

the business function Outsourced Manufacturing 2 in ERP Operations

(LOG_MM_OM_2). This business function enables you to manage your outsourced

production steps and your subcontracting process more efficiently. This SAP solution

provides full support with batch traceability, multilevel subcontracting, and third-party

order processing for subcontracting, and enables external capacity planning for your

third-party orders.


o Enhancements in Production Planning

o Multilevel Subcontracting

o Third-Party Order Processing for Subcontracting

o Integration of External Third-Party Order Planning

See also


Central Component -> SAP ERP Enhancement Packages -> ERP Central

Component Enhancement Package 5 -> Business Functions (SAP Enhancement

Package 5 for SAP ERP 6.0) -> Business Functions in SAP ERP -> Enterprise

Business Functions -> Logistics -> Materials Management -> Outsourced

Manufacturing 2 in ERP Operations



LOG_MM_OM_2: Enhancements for Outsourced Manufacturing

Use


function Outsourced Manufacturing in ERP Operations (LOG_MM_OM_2), a

detailed batch where-used list is available for the subcontract order with information

about the assignment of finished batches and component batches.

The assignment can be displayed in the batch where-used list upon goods receipt.

Subsequent adjustments to the component consumption (subsequent allocation) can

be made with reference to the finished batch.

If you use SAP Supplier Network Collaboration (SAP SNC), your vendor can also

maintain detailed batch information. The data can then be posted automatically in your

ERP system.

For a detailed display, you must set the Multibatch Evaluation indicator on the initial

screen of the batch where-used list.

Inbound delivery for purchase order

As of enhancement package 4, you can use business function LOG_MM_OM_1 to

maintain and process components (including batch numbers) in the inbound delivery.

As of enhancement package 5, the assignments can be displayed in the batch where-

used list after the goods receipt.

Goods receipt with realtime consumption posting

If realtime consumption posting is set up in the purchasing info record, the goods

withdrawal of the components by the vendor and the goods receipt of the finished batch

are decoupled. You must activate business function LOG_MM_OM_1 for this purpose.

The customer gets information from the vendor about which component batches have

been included in the finished batch. This information can be received by fax or mail, or

automatically using SAP SNC 7.0. The information can be used to update the batch

where-used list and display the exact assignment of component batches and finished

batches.

Goods receipt without realtime consumption posting

If you have not set up realtime consumption posting in the classic subcontracting

process, the information about the assignment of component batches and finished

batches is taken from the material document and updated in the batch where-used list.

SAP SNC Integration

SAP SNC 7.0 allows you to automate the following manual process steps in the ERP

system or let the vendor perform them:

o Separate posting of the component consumption

The relevant component stocks are reduced automatically in the ERP system.

o Maintenance of the assignment of component batches to finished batches or

vendor batches

With the current enhancement package 5, the ERP system can now be updated

automatically with the assignment data from SAP SNC. The assignment data (vendor

batch to component batch) is usually available in the ERP system before the actual

goods receipt.

When posting the goods receipt for the purchase order, the system automatically

defaults the relevant vendor batch (including the corresponding component batches).

The batch is then created in the ERP system from the vendor batch. If several vendor



batches have already been posted for the purchase order, the user can display all

relevant vendor batches using the input help and select the appropriate batch. The

corresponding component batches are determined and defaulted automatically in the

background.

If characteristics for the batches are transferred from SAP SNC, the information can be

stored in the batch master record. You can use the Business Add-In (BAdI)

SNC_WORKORDER_INFORMATION (Adoption of Information from Work

Order) to specify whether:

o The characteristic values should be copied

o The characteristic values should be copied with a new value

o The characteristic values should not be copied

Subsequent allocation for purchase order

If there are still components to be subsequently allocated to a purchase order after

goods receipt, you can specify the relevant finished batch for the additionally withdrawn

components to guarantee a distinct assignment.

You can choose the Batch tab for the item of the finished batch. The input help displays

all batches for which a goods receipt has already been posted. This allows you to

choose the relevant finished batch and assign it the component batches for which an

excess consumption or an underconsumption is to be posted. This guarantees that the

distinct assignment of component batches and finished batches is updated even if

there is a subsequent allocation in the batch where-used list.



LOG_MM_OM_2: Multilevel Subcontracting (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605), you can create

purchase requisitions for different vendors automatically.

The lower-level subcontractor receives the information to send the finished product

directly to the next vendor/subcontractor.

You can monitor the entire supply chain.

Effects on Data Transfer

You can create the procurement proposals for the (end-) product in the planning run of

the APO (Advanced Planning and Optimization) for Production Planning and Detailed

Scheduling (PP/DS). The purchase requisitions are then transferred over the CIF

interface to the interconnected ERP system, as before. In the CIF interface, a check is

carried out to determine whether the current item constitutes a case of multilevel

subcontracting. If so, the system automatically extends the purchase requisition by the

required items according to the bill of materials. You can create a separate purchase

order for each item.

You can track the status of the purchase orders at any time by using the SAP SNC

(Supplier Network Collaboration) system. This requires the purchase orders to be sent

to the SNC system. The vendors can then process the purchase order statuses

themselves. You can display and edit all related purchase orders by using an overview

transaction.


The MRP run is frequently used for generating procurement proposals automatically.

For multilevel subcontracting, you can also create purchase requisitions for the (end-)

product by using the MRP run. After this, you should always execute the report

RM_MLSC_TRIGGER_MLSC_MRP, which then extends the purchase requisitions by

the required items.


Define Special Procurement Types

You can make the Customizing settings for this function in Customizing for Materials

Management under Consumption-Based Planning -> Master Data -> Define Special

Procurement Types.

See also

SAP Library for SAP ERP on SAP Help Portal under http://help.sap.com/erp -> SAP

ERP Enhancement Packages -> ERP Central Component Enhancement Package 5 ->

SAP ERP Central Component -> Logistics -> Materials Management (MM) -> Inventory

Management (MM-IM) -> Special Stock and Special Procurement Forms (MM-IM-PI) ->

Subcontracting.

Release Information LOG_MM_OM_2: Business Function Outsourced

Manufacturing 2 in ERP.



LOG_MM_OM_2: Third-Party Order Processing for Subcontracting (New)

Use


function Outsourced Manufacturing 2 in ERP Operations (LOG_MM_OM_2), you

can use third-party order processing for purchase orders for products that are

finished by a subcontractor and sent straight to the end customer. The system

automatically creates purchase requisitions for subcontractings based on a third-party

order in the Sales Order (SD-SLS-SO) component and passes on the necessary

information (such as delivery address) for shipping to the end customer.

The following features are available in standard third-party order processing:

o You can assign sales order items manually to direct subcontracting shipping by

assigning the relevant item categories.

o The purchase requisition can be created automatically from the sales order if

there is a material that is assigned to the relevant item category group in the

basic view and sales view in the material master.

o The purchase order you created with reference to the purchase requisition

inherits the data from the purchase requisition.

o You can create an inbound delivery with reference to the purchase order.

o You can post the goods receipt directly or the statistical goods

receipt with reference to the inbound delivery for the third-party order.

o After the statistical goods receipt, you can check the component consumption in

the subcontracting cockpit (transaction ME2ON) or in the stock overview

(transaction MMBE).

Note:

Posting the goods receipt for the finished product is not mandatory in standard

third-party order processing, but is possible for statistical reasons. In third-party

order processing for subcontracting, the consumption and goods receipt must be posted since timely consumption posting is not available due to the fact

that the object Cost is missing. There are two variants for posting the (statistical)

goods receipt for the purchase order:

- The subcontractor send the advance shipping notification (ASN) to the end

customer and to the original equipment manufacturer when the materials

are delivered to the end customer. The ASN can automatically create an

inbound delivery in the SAP ERP system of the original equipment

manufacturer, for example. The original equipment manufacturer then

creates a statistical goods receipt based on the inbound delivery

(transaction L32N).

- The goods receipt is only posted in inventory management after an e-mail

or fax from the vendor (transaction MIGO), for example.


You make the Customizing settings for ths function in Customizing for Sales and

Distribution under Sales -> Sales Documents in the following Customizing sections

and activities:

Customizing section Sales Document Item:



o Define Item Categories

Check the item category for subcontracting (direct shipment). You can use the

following default value: Item category TADS (subcontracting (DS))

You can use the standard item category TAS (third-party item) as a copy

template.

o Define Item Category Groups

Check the item category group. You can use the following default value: Item category group BADS (subcontracting (DS))

You can use the standard item category group BANS (third-party item) as a copy

template.

o Assign Item Categories

Enter the following detail data, for example:

- Sales document type: SO (standard order)

- Item category group: BADS (subcontracting (DS))

- Item category: TADS (subcontracting (DS))

- Manually allowed item category in SD document: TAS (third-party

item)

- Manually allowed item category in SD document: TAN (standard item)

- and so on.

Customizing section Schedule Lines:

o Define Schedule Line Categories

Check the schedule line categories. You can use the following default value: Schedule line category DS (subcontracting (DS)).

You can use the standard schedule line category CS as a copy template.


- Purchase order type: NB (purchase requisition)

- Item category: 3 (subcontracting); required value

- Account assignment category: X (all auxiliary account assignments)

- Incompleteness procedure SD document: 31 (schedule line with

purchase requisition)

o Assign Schedule Line Categories

You assign the following schedule line categories to item category TADS, for

example:

- Default schedule line category: DS (subcontracting (DS))

- Manually allowed schedule line category: CS (third-party)

- Manually allowed schedule line category: CB (individual purchase

order)

Note:

To ensure data consistency, if you post the goods receipt (transaction MIGO)

without having created an inbound delivery, you must make sure that the field

selection string for movement type 543 (goods issue from subcontracting stock)

and the G/L account string are synchronized.

- You make the required Customizing settings in Customizing for

Enterprise Controlling under Consolidation -> Integration:

Preparation for Consolidation -> Preparation in the Sender System ->



Further Settings for Business Areas Consolidations -> Financial

Accounting -> Maintain Field Status Groups for G/L

Accounts (transaction OBC4):

- Under Field Status Variants -> Field Status Groups, select the field

status group for your material consumption accounts and choose Edit ->

Field Status -> Explode.

- Double-click to choose the Additional Account Assignment group, and

make sure that the Sales Order field is flagged as a required or optional

entry.

- In transaction SE38, you can use report RM07CUFA (execution for

movement type 543, special stock indicator O (subcontracting stock) and

relevant G/L account) to check the data consistency for the sales order.

See also



Component Enhancement Package 5 -> SAP ERP Central Component ->

Logistics ->

o Sales and Distribution (SD) -> Sales (SD-SLS)

o Materials Management (MM)

Release note LOG_MM_OM_2: Business Function Outsourced

Manufacturing 2 in ERP



LOG_MM_OM_2: Integration of External Third-Party Order Planning (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL_605), business

function Outsourced Manufacturing 2 in ERP Operations (LOG_MM_OM_2), you can

use external capacity planning for third-party orders in third-party order

processing. This lets you take account of the vendor’s capacity restrictions.

In the SAP Enterprise Resource Planning (SAP ERP) back-end system, when you

create the sales order using the item category and corresponding schedule line

categories from Customizing, you determine whether or not a sales order item is a

third-party item for which planning takes places in the SAP Supply Chain Management

system (SAP SCM). You can use a Business Add-In (BAdI) to define customer-specific

criteria for which the system checks if external planning should be executed for a third-

party item and determines the item category accordingly.

The SAP ERP system creates the third-party requisition for planning-relevant items,

blocks it, and transfers the data to SAP SCM. Planning then takes place in the SAP

Advanced Planning and Optimization component (SAP APO). When the planner

releases the third-party order requisition in SAP SCM, the SAP ERP system removes

the block so that you can create a purchase order and complete third-party order

processing.


You have activated the following business functions:

o The Outsourced Manufacturing 2 in ERP Operations business function

(LOG_MM_OM_2) in SAP ERP

o The SCM APO, Third-Party Order Planning in APO business function

(SCM_APO_DRS_PLAN) in SAP SCM

You have set up an integration model in Core Interface (CIF) to transfer the third-party

order requisition data from SAP ERP to SAP APO.

The system checks authorization to unblock the purchase requisition based on the

following objects:

o M_BANF_EKO (Purchasing Organization in Purchase Requisition)

o M_BANF_EKG (Purchasing Group in Purchase Requisition)

o M_BANF_BSA (Document Type in Purchase Requisition)

o M_BANF_WRK (Plant in Purchase Requisition)

You make the Customizing settings in Customizing for Sales and Distribution under

Sales -> Sales Documents in the following Customizing sections and activities:

Customizing section Sales Document Item:

o Define Item Categories

Check the item category for external third-party order planning. You can use the following default value: Item category TPP (third-party item with external

planning). You can use the standard item category TAS (third-party item) as a copy

template.

Note:

You do not necessarily have to define a new item category for Customizing of



external third-party order planning. You can also set up third-party order planning

for the item category TAS (standard third-party item), whereby all standard third-

party items are considered by the SAP ERP system as planning-relevant. The

default Customizing allows a better overview and differentiation of the settings

for standard third-party items.

o Define Item Category Groups

Check the item category group. You can use the following default value: Item category group BTPP (third-party item with external planning).

You can use the standard item category group BANS (third-party item) as a copy

template.

o Assign Item Categories


- Sales document type: SO (standard order)

- Item category group: BTPP (third-party item with external planning)

- Item category: TAN (standard item)

- Manually allowed item category in SD document: TPP (third-party item

with external planning)

- Manually allowed item category in SD document: TAS (third-party

item)

- and so on.

For this assignment in the purchase requisition, you can change the item category manually to TPP in order to enable external planning.

o BAdI: Integration of Third-Party Order Planning You can use this Business Add-In (BAdI) to check, based on customer-specific

criteria, if the sales order item or purchase requisition item is a planning-relevant

third-party item. The system then changes the item category accordingly and

triggers planning in SAP SCM. The BAdI also enables you to determine a vendor

for the third-party item and a material availability date.

Notes:

- In standard third-party order processing, a vendor does not have to be

specified to generate the purchase requisition. A vendor must be specified

for a planning-relevant third-party item, however, otherwise the SAP SCM

planning system cannot determine a vendor location.

- You can trigger the BAdI again by changing the item category manually.

- When you create a sales order, do not confirm the order until you have

entered all data on the material, quantity, value, and date.

Customizing section Schedule Lines:

o Define Schedule Line Categories

You define a schedule line category. You can use the following default value: Schedule line category D1 (third-party item with external planning).

You can use the standard schedule line CS as a copy template.


- Purchase order type: TPP (purchase requisition)

Note: You can define the purchase order type in the Customizing activity

Define Document Types (see below).

- Item category: 5 (third-party); required value

- Account assignment category: X (all auxiliary account assignments)



- External Capacity Planning: Indicator set; required value

- Incompleteness procedure SD document: 31 (schedule line with

purchase requisition)

o Assign Schedule Line Categories

You assign the following schedule line categories to item category TPP:

- Default schedule line category: D1

- Manually allowed schedule line category: CS

In addition, you can make the following Customizing settings under Materials

Management -> Purchasing -> Purchase Requisition:

o Define Document Types

Define a separate document type for your purchase requisition, such as TPP

(purchase requisition for third-party order planning) and assign it the item category third-party.

See also




Component -> Logistics ->

- Sales and Distribution (SD) -> Sales (SD-SLS)

- Materials Management (MM)

o Release note LOG_MM_OM_2: Business Function Outsourced

Manufacturing 2 in ERP

o For more information, see:

- The release note for the business function SCM-APO, Third-Party Order

Planning in APO in SAP Library for SAP SCM on SAP Help Portal at

http://service.sap.com/releasenotes -> SAP Solutions -> SAP Supply

Chain Management -> SAP SCM 7.0 -> Enhancement Package 1

- The documentation for the business function SCM-APO, Third-Party

Order Planning in APO in SAP Library for SAP SCM on SAP Help Portal

at http://help.sap.com/scm -> SAP Supply Chain Management -> SAP

SCM Enhancement Packages -> Enhancement Package 1 ->

Business Functions (SAP Enhancement Package 1 for SAP SCM 7.0)

-> Business Functions in SAP APO -> SCM-APO, Third-Party Order

Planning in APO



Business Function Procurement - SRM Integration 2

LOG_MM_P2PSE_2: Procurement - SAP SRM Integration 2 (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605) you can use

the business function Procurement - SAP SRM Integration 2 (LOG_MM_P2PSE_2).

This business function enables you to structure procurement processes in SAP ERP

and SAP SRM more efficiently.

The following functions are available in this business function:

o Use of central contracts with hierarchical service structures in SAP ERP

o Creation of purchase orders with services items from SAP SRM with the statuses

held and parked

o Integration of invoices with contract references in SAP SRM central contracts

o Use of informatory lines in service structures that are sourced in SAP SRM

o Use of contract limits in SAP ERP-SUS integration

o Use of SRM-MDM catalog connection with complex service structures for

purchase requisitions and purchase orders

For more information about the individual functions, see the release notes on SAP

Service Marketplace at http://service.sap.com/releasenotes under Release Notes ->

SAP Solutions -> SAP SRM -> SAP SRM 7.0 EHP 1:

o SRM_SERVICE_PROC_1: SRM, Service Procurement Innovations

o SRM_SERVICE_PROC_1: Central Contract Management for Service

Procurement (Enhanced)

o SRM_SERVICE_PROC_1: Park and Hold (Enhanced)

o SRM_SERVICE_PROC_1: Transfer of Informatory Lines (New)

o SRM_SERVICE_PROC_1: SRM-MDM Catalog Integration (Enhanced)


If you want to use these functions, you must activate the business function SRM,

Service Procurement Innovations (SRM_SERVICE_PROC_1) in the SAP SRM

system and perform Customizing activity Define Status for Purchase Orders in

Back-End System in Customizing for SAP Supplier Relationship Management under

SRM Server -> Cross-Application Basic Settings -> Service Procurement.

You can integrate the park and hold functions and invoices with contract references in

SAP SRM Contract Management if you activate the business function Materials

Management - Enhancements in Procurement (LOG_MM_CI_3).



Business Function Cross-Company-Code Stock Transfer &

Actual Costing

LOG_MM_SIT: Business Function MM, Stock in Transit, and Actual

Costing (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL 605), you can use

the business function MM, Stock in Transit, and Actual Costing. This business function

allows you to map stock in transit within a delivery process.

Using the new valuated stock in transit and new movement types, you can specify the

transfer of title precisely. When doing this, you can control goods movements both for

sales to external customers, and for stock transfer processes and corresponding

returns between plants belonging to the same company code, or to different company

codes within a group. Throughout the process, you can keep track of material

quantities and material values in a transparent manner, and display them in the stock

overview, the purchase order history, and the corresponding material stock accounts.

All processes with a defined transfer of title proceed with reference an outbound

delivery. For stock transfer processes that include receiving stock in transit, you can set

up the system to create inbound deliveries with reference to an outbound delivery

automatically. You can post inbound deliveries to the receiving plant either in the

standard way, or via the receiving stock in transit.

Using the application component Actual Costing/Material Ledger (CO-PC-ACT), you

can include stock in transit in actual costing across company codes. The transit values

are thereby included in period-end closing automatically. The system displays a

transparent, company-internal cost structure, divided into the different cost

components. In addition, you can see intercompany profit across all levels of the whole

value chain, which enables you to compare actual costs with actual revenue.


o Cross-Company-Code Stock Transfer and Customer Delivery

(New)

o Intra-Company-Code Stock Transfer (New)

o Movement Types (New)

o Inbound Delivery with Stock in Transit (New)

o Actual Costing in Processes with Stock in Transit (New)

See also



Component Enhancement Package 5 ->

o Business Functions (SAP Enhancement Package 5 for SAP ERP 6.0) ->

Business Functions in SAP ERP -> Enterprise Business Functions ->

Logistics -> Materials Management -> MM, Stock in Transit, and Actual

Costing

o SAP ERP Central Component -> Logistics -> Materials Management (MM) ->

Inventory Management (MM) -> Special Stocks and Special Forms of

Procurement (MM-IM) -> Stock Transfer via Stock Transport Order ->

Valuated Stock in Transit



LOG_MM_SIT: Cross-Company-Code Stock Transfer and Customer Delivery (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL_605), Business

Function MM, Stock in Transit, and Actual Costing, you can use stock in transit to

control and record in the system the transfer of title of a material in cross-company-

code stock transfer processes, in the corresponding return stock transfers, and in sales

transactions with external customers.

You can map the following processes:

o Cross-company-code stock transfer with transfer of title at goods issue, and

return with transfer of title at goods receipt via return delivery

o Cross-company-code stock transfer with transfer of title at goods receipt, and

return with transfer of title at goods issue via return delivery

o Cross-company-code stock transfer with transfer of title during transit, and return

with transfer of title during transit

o Delivery with transfer of title at the customer location

The transfer of title depends on the delivery type. The process flow is controlled using

movement types (see also release note LOG_MM_SIT: Movement Types

(New)).

For information about intra-company-code stock transfers and their returns, see release

note LOG_MM_SIT: Intra-Company-Code Stock Transfers (New).


So that the existing cross-company-code process can remain unchanged, you need

new document types and delivery types. The delivery types are delivered as standard

with the corresponding item categories, the schedule line categories, and the

necessary assignments. The new document types, and their assignment to the delivery

types, you need to create yourself.

Note:

For processes with cross-company-code stock in transit (CST), you can copy the new

document types and delivery types from the existing document type and delivery type

that are used in the cross-company-code process without stock in transit.

1. Defining New Document Types and Sales Order Types

o Stock Transfers:

In Customizing for Materials Management, choose Purchasing -> Purchase

Order ->Define Document Types.

For each process, create a new document type as a copy of the document type Standard Purchase Order (NB), for example:

- Document type NBCR for the Stock Transfer to Receiving Valuated BST

process (transfer of title at goods issue)

- Document type NBC2 for the Stock Transfer from Issuing Valuated CST

to Receiving Plant process (transfer of title at goods receipt)

- Document type NBC3 for the Stock Transfer from Issuing Valuated CST

via Receiving Valuated CST to Receiving Plant process (transfer of title

during transit)

Note:



The same document types are used for intra-company-code stock transfers.

Cross-company-code and intra-company-code are differentiated in the vendor's

master data.

o Returns:

For the return processes the same document types are used as for the stock

transfer processes.

To enable the system to find the corresponding delivery type, you must have

flagged the purchase order item in question as a return item in the stock

transport order.

Note:

For customizing reasons, different document types are used for the stock

transfer processes than for intra-company-code returns processes.

o Delivery to Customer Location:

In Customizing for Sales and Distribution, choose Sales -> Sales Documents

-> Sales Document Header -> Define Sales Document Types.

Create the new sales document type Delivery from Issuing Valuated Stock in

Transit (ORNC) as a copy of the sales document type Standard Order (TA).

2. Defining New Delivery Types

In Customizing for Logistics Execution, choose Shipping -> Deliveries -> Define

Delivery Types.

o Stock Transfers:

Ensure that a new delivery type has been created as a copy of delivery type

Cross-Company-Code Replenishment (NLCC) for each process, for example:

- Delivery type NCCR for the Stock Transfer to Receiving Valuated CST


- Delivery type NCC2 for the Stock Transfer from Issuing Valuated CST to

Receiving Plant process (transfer of title at goods receipt)

- Delivery type NCC3 for the Stock Transfer from Issuing Valuated CST via

Receiving Valuated CST to Receiving Plant process (transfer of title during

transit)

o Returns:

Ensure that a new delivery type has been created as a copy of delivery type

Return, Cross-Company-Code Stock Transport Order (NCR) for each process,

for example:

- Delivery type NCRR for the Return Stock Transfer from Originally

Receiving CST to Originally Issuing Plant process (transfer of title at

goods receipt)

- Delivery type NCR2 for the Return Stock Transfer from Originally

Receiving Plant to Originally Issuing Valuated CST process (transfer of

title at goods issue via return delivery)

- Delivery type NCR3 for the Return Stock Transfer from Originally

Receiving CST via Originally Issuing Valuated CST to Originally Issuing

Plant process (transfer of title during transit)


Ensure that for the process Outbound Delivery with Transfer of Title at Customer

Location the new delivery type Delivery from Issuing Valuated Stock in Transit (NCCU) has been created as a copy of the delivery type Outbound Delivery (LF).

3. Assigning the New Delivery Type to New Document Types / Sales Order Types



o Stock Transfers:


Order -> Set Up Stock Transport Order -> Assign Delivery Type and Checking Rule.

For the entries that contain the document type Standard Purchase Order (NB)

and the delivery type Cross-Company-Code Replenishment Delivery (NLCC),

create copies with the following changes (you change the delivery type in the

respective Delivery Type for Stock Transfers Between Two Company Codes

field):

Note:

If you have already created a document type assignment for the intra-company-

code process (delivery type in Delivery Type for Stock Transfers Within a

Company Code field), add the delivery type for cross-company-code deliveries

to the data row in question.

- For each issuing plant of the Stock Transfer to Receiving Valuated CST process, change the document type from NB to NBCR and the delivery

type from NLCC to NCCR.

- For each issuing plant of the process Stock Transfer from Issuing Valuated CST to Receiving Plant, change the document type from NB to

NBC2 and the delivery type from NLCC to NCC2.

- For each issuing plant of the process Stock Transfer from Issuing

Valuated CST via Receiving Valuated CST to Receiving Plant, change the document type from NB to NBC3 and the delivery type from NLCC to

NCC3.

o Returns:


Order ->Returns Order -> Store Return / Return Plant to Plant.

- For each originally issuing plant that you use in the Return Stock Transfer

from Originally Receiving Valuated CST to Originally Issuing Plant process, create an entry with document type NBCR and delivery type

NCRR.


from Originally Receiving Plant to Originally Issuing Valuated CST process, create an entry with document type NBC2 and delivery type

NCR2.


from Originally Receiving CST via Originally Issuing Valuated CST to

Originally Issuing Plant process, create an entry with document type NBC3 and delivery type NCR3.


In Customizing for Sales and Distribution, choose Sales -> Sales Documents

-> Sales Document Header -> -> Define Sales Document Types.

In Shipping, in the detail view, assign the appropriate delivery type, NCCU, to

the sales document type Outbound Delivery from Issuing Valuated Stock in Transit (ORNC).

4. Defining New Item Categories

In Customizing for Sales and Distribution, choose Sales -> Sales Documents ->

Sales Document Item -> Define Item Categories.

o Stock Transfers:

Ensure that for each process a new item category has been created as a copy of



item category Cross-Company-Code Stock Transfer Item Category (NLC), for

example:

- Item category NCCR for the Stock Transfer to Receiving Valuated CST

process

- Item category NCC2 for the Stock Transfer from Issuing Valuated CST to

Receiving Plant process

- Item category NCC3 for the Stock Transfer from Issuing Valuated CST via

Receiving Valuated CST to Receiving Plant process

o Returns:


item category Return, Cross-Company-Code Stock Transfer Item Category (NCRN), for example:

- Item category NCRR for the Return Stock Transfer from Originally

Receiving CST to Originally Issuing Plant process

- Item category NCR2 for the Return Stock Transfer from Originally

Receiving Plant to Originally Issuing Valuated CST process

- Item category NCR3 for the Return Stock Transfer from Originally

Receiving CST via Originally Issuing Valuated CST to Originally Issuing

Plant process


Ensure that the new item category Delivery from Issuing Valuated Stock in Transit (NCCU) has been created as a copy of the item category Standard Item

(TAN).

5. Defining Item Category Determination in Deliveries


Item Category Determination in Deliveries .

o Stock Transfers:

Ensure that for each process, for all entries a copy of the delivery type Cross-

Company-Code Replenishment (NLCC) has been created and altered as

follows:

- Delivery type NLCC has been changed for each entry to delivery type

Stock Transfer to Receiving Valuated CST (NCCR).

Item category Cross-Company-Code Stock Transfer Item Category (NLC)

has been changed for each entry to NCCR.


Stock Transfer from Issuing Valuated CST to Receiving Plant (NCC2).

Item category NLC has been changed for each entry to item category

NCC2.


Stock Transfer from Issuing Valuated CST via Receiving Valuated CST to

Receiving Plant (NCC3).

Item category NLC has been changed for each entry to item category

NCC3.

o Returns:

Ensure that for each returns process, for all entries with delivery type Return, Cross-Company-Code Stock Transport Order (NCR), a copy has been created

and altered as follows:

- Delivery type NCR has been changed for each entry to delivery type



Return Stock Transfer from Originally Receiving CST to Originally Issuing Plant (NCRR).

Item category Return, Cross-Company-Code Stock Transfer Item Category (NCRN) has been changed for each entry to NCRR.


Return Stock Transfer from Originally Receiving Plant to Originally Issuing

Valuated CST (NCR2).

Item category NCRN has been changed for each entry to item category

NCR2.


Return Stock Transfer from Originally Receiving CST via Originally Issuing Valuated CST to Originally Issuing Plant (NCR3).

Item category NCRN has been changed for each entry to item category

NCR3.


Ensure that for all entries with delivery type Outbound Delivery (LF), a copy has

been created and altered as follows:

- Delivery type LF has been changed for each entry to delivery type

Delivery from Issuing Valuated Stock in Transit (NCCU).

- Item category Standard Item (TAN) has been changed for each entry to

item category Delivery from Issuing Valuated SiT (NCCU).

6. Defining New Schedule Line Categories in Deliveries


Schedule Lines -> Define Schedule Line Categories.

See also release note LOG_MM_SIT: Movement Types (New).

o Stock Transfers:

Ensure that for each process a new schedule line category has been created as a copy of schedule line category Cross-Company-Code Replenishment (NC), for

example:

- Schedule line category N1 for the Stock Transfer to Receiving Valuated

CST process, detailed data: Movement type: 683 (Stock Transfer to Receiving Valuated CST)

- Schedule line category N2 for the Stock Transfer from Issuing Valuated

CST to Receiving Plant process, detailed data:

- Movement type = 681 (Stock Transfer to Issuing Valuated CST)

- Movement Type for Issuing Valuated Stock in Transit = 685 (Stock

Transfer from Issuing Valuated CST)

- Specification for Issuing Valuated Stock in Transit = 2 ( Goods Issue

from Issuing Valuated Stock in Transit to Receiving Plant)


CST to Receiving Valuated CST process, detailed data:

- Movement type = 681 (Stock Transfer to Issuing Valuated CST)


Transfer from Issuing Valuated CST)

- Specification for Issuing Valuated Stock in Transit = 1 (Goods Issue

from Issuing Valuated Stock in Transit to Receiving Valuated Stock in

Transit)

o Returns:

Ensure that for each process a new schedule line category has been created as



a copy of schedule line category Return, Cross-Company-Code Replenishment (NS), for example:

- Schedule line category R1 for the Return Stock Transfer from Originally

Receiving Valuated CST to Originally Issuing Plant process, detailed data: Movement type: 693 (Stock Transfer, Return from Originally Receiving

Valuated CST)


Receiving Plant to Originally Issuing Valuated CST process, detailed data: - Movement type = 691 (Stock Transfer, Return from Originally Issuing

Valuated CST)


Transfer, Return to Originally Issuing Valuated CST) - Specification for Issuing Valuated Stock in Transit = 2 ( Goods Issue



Receiving CST to Originally Issuing Valuated CST process, detailed data: - Movement type = 691 (Stock Transfer, Return from Originally Issuing

Valuated CST) - Movement Type for Issuing Valuated Stock in Transit = 695 (Stock

Transfer, Return to Originally Issuing Valuated CST)



Transit)


Ensure that for the process Delivery from Receiving Valuated Stock in Transit

the new schedule line category NU has been created as a copy of schedule line

category Material Requirements Planning (CP), detailed data:

- Movement type = 687 (Goods Delivery to Issuing Valuated Stock in Transit)

- Movement Type for Issuing Valuated Stock in Transit = 601 (Goods Issue

for Delivery)

- Specification for Issuing Valuated Stock in Transit = 3 (Sales-Order-

Related Goods Issue from Issuing Valuated Stock in Transit)

7. Assigning New Schedule Line Categories to the New Item Category


Schedule Lines -> Assign Schedule Line Categories.

o Stock Transfers

Ensure that for each process, new entries have been created as a copy of the

entry with item category Cross-Company-Code Stock Transfer Item Category (NLC) and schedule line category Cross-Company-Code Replenishment (NC)

with the following changes:

- Item category NLC has been changed to item category Stock Transfer to

Receiving Valuated CST (NCCR).

Schedule line category NC has been changed to schedule line category

Stock Transfer to Receiving Valuated CST (N1).

- Item category NLC has been changed to item category Stock Transfer

from Issuing Valuated CST to Receiving Plant (NCC2).


Stock Transfer from Issuing Valuated CST to Receiving Plant (N2).

- Item category NLC has been changed to item category Stock Transfer

from Issuing Valuated CST via Receiving Valuated CST to Receiving Plant (NCC3).




Stock Transfer from Issuing Valuated CST to Receiving Valuated CST

(N3).

o Returns:

Ensure that for each process, new entries have been created as a copy of the

entry with item category Return, Cross-Company-Code Stock Transfer Item

Category Return (NCRN) and schedule line category Return, Cross-Company-

Code Replenishment Return (NS) with the following changes:

- Item category NCRN has been changed to item category Return Stock

Transfer from Originally Issuing CST (NCRR).

Schedule line category NS is changed to the corresponding schedule line

category R1.

- Item category NCRN is changed to item categoryReturn Stock Transfer

from Originally Receiving Plant to Originally Issuing Valuated CST

(NCR2).


category R2.

- Item category NCRN is changed to item categoryReturn Stock Transfer

from Originally Receiving CST to Originally Issuing Valuated CST (NCR3).


category R3.


Ensure that a new entry has been created as a copy of the entry with item category Standard Item (TAN) and schedule line category Material

Requirements Planning (CP) with the following changes:

- Item category TAN has been changed to item category Delivery from

Issuing Valuated Stock in Transit (NCCU).

- Schedule line category CP has been changed to schedule line category

Delivery from Issuing Valuated Stock in Transit (NU).

Note:

To control that the item in a stock transport order or a delivery is relevant for the proof

of delivery, you have defined proof-of-delivery relevance in Customizing for Logistics

Execution, under Shipping -> Deliveries -> Proof of Delivery -> Set POD-Relevance Depending on Delivery Item Category.

See also

o SAP Library for SAP ERP on Help Portal under http://help.sap.com/erp -> SAP

ERP Central Component -> SAP ERP Enhancement Packages -> ERP


Component -> Logistics -> Materials Management (MM) -> Inventory

Management (MM-IM) -> Managing Special Stocks (MM-IM) -> Stock

Transfer Using a Stock Transport Order -> Valuated Stock in Transit

o Release note LOG_MM_SIT: Business Function MM, Stock in

Transit and Actual Costing



LOG_MM_SIT: Intra-Company-Code Stock Transfer (New)

Use


Function MM, Stock in Transit and Actual Costing, you can control and record in the

system the transfer of title of a material in intra-company-code stock transfer

processes, in the corresponding return stock transfers, and in sales transactions with

external customers.

You can map the following processes:

o Intra-company-code stock transfer with transfer of title at goods issue, and return

with transfer of title at goods receipt via return delivery

o Intra-company-code stock transfer with transfer of title at goods receipt, and

return with transfer of title at goods issue via return delivery

o Intra-company-code stock transfer with transfer of title during transit and return

with transfer of title during transit

The transfer of title depends on the delivery type. The process flow is controlled using

movement types (see also release note LOG_MM_SIT: Movement Types (New)).

For information about cross-company-code stock transfers and their returns, see

release note LOG_MM_SIT: Cross-Company-Code Stock Transfers and Customer Deliveries (New).


So that the existing intra-company-code process can remain unchanged, you need new

document types and delivery types. The delivery types are delivered as standard with

the corresponding item categories, the schedule line categories, and the necessary

assignments. The new document types, and their assignment to the delivery types, you

need to create yourself.

Note:

For processes with intra-company-code stock in transit (IST), you can copy the new

document types and delivery types from the existing document type and delivery type

that are used in the intra-company-code process without stock in transit.


o Stock Transfers:


Order ->Define Document Types.

For each process, create a new document type as a copy of the document type Standard Purchase Order (NB), for example:

- Document type NBCR for the Stock Transfer to Receiving Valuated IST


- Document type NBC2 for the Stock Transfer from Issuing Valuated IST to


- Document type NBC3 for the Stock Transfer from Issuing Valuated IST

via Receiving Valuated IST to Receiving Plant process (transfer of title

during transit)

o Returns:

For each process, create a new document type as a copy of the document type



Standard Purchase Order (NB), for example:

- Document type NBRR for the Return Stock Transfer from Originally

Receiving Valuated IST to Originally Issuing Plant process (transfer of title

at goods receipt)

- Document type NBR2 for the Return Stock Transfer from Originally

Receiving Plant to Originally Issuing Valuated IST process (transfer of

title at goods receipt)

- Document type NBR3 for the Return Stock Transfer from Originally

Receiving IST via Originally Issuing Valuated IST to Originally Issuing


To enable the system to find the corresponding delivery type, you must have

flagged the purchase order item in question as a return item in the stock

transport order.



Delivery Types.

o Stock Transfers:

Ensure that a new delivery type has been created as a copy of delivery type Replenishment (NL) for each process, for example:

- Delivery type NLIR for the Stock Transfer to Receiving Valuated IST


- Delivery type NLI2 for the Stock Transfer from Issuing Valuated IST to


- Delivery type NLI3 for the Stock Transfer from Issuing Valuated IST via

Receiving Valuated IST to Receiving Plant process (transfer of title during

transit)

o Returns:

Ensure that a new delivery type has been created as a copy of delivery type Return, Stock Transport Order (NLR) for each process, for example:

- Delivery type NLRR for the Return Stock Transfer from Originally

Receiving Valuated IST to Originally Issuing Plant process (transfer of title

at goods receipt)

- Delivery type NLR2 for the Return Stock Transfer from Originally

Receiving Plant to Originally Issuing Valuated IST process (transfer of title

at goods issue)

- Delivery type NLR3 for the Return Stock Transfer from Originally



3. Assigning the New Delivery Type to New Order Types

o Stock Transfers:


Order -> Set Up Stock Transport Order -> Assign Delivery Type and Checking Rule.

For the entries that contain the document type Standard Purchase Order (NB)

and the delivery type Replenishment Delivery (NL), create copies with the

following changes (you change the delivery type in the respective Delivery Type

for Stock Transfers within a Company Code field):

Note:



If you have already created a document type assignment for the cross-company-

code process (delivery type in Delivery Type for Stock Transfers Between

Two Company Codes field), add the delivery type for intra-company-code

deliveries to the data row in question.

- For each issuing plant of the Stock Transfer to Receiving Valuated IST process, change the document type from NB to NBCR, and the delivery

type from NL to NLIR.

- For each issuing plant of the Stock Transfer from Issuing Valuated IST to Receiving Plant process, change the document type from NB to NBC2,

and the delivery type from NL to NLI2.

- For each issuing plant of the Stock Transfer from Issuing Valuated IST via

Receiving Valuated IST to Receiving Plant process, change the document type from NB to NBC3, and the delivery type from NL to NLI3.

o Returns:


Order ->Returns Order -> Store Return / Return Plant to Plant.


from Originally Receiving Valuated IST to Originally Issuing Plant process, create an entry with document type NBRR and delivery type NLRR.


from Originally Receiving Plant to Originally Issuing Valuated IST process, create an entry with document type NBR2 and delivery type NLR2.


from Originally Receiving IST via Originally Issuing Valuated IST to

Originally Issuing Plant process, create an entry with document type NBR3 and delivery type NLR3.

4. Defining New Item Categories


Sales Document Item -> Define Item Categories.

o Stock Transfers:

Ensure that for each process a new item category has been created as a copy of item category Standard Stock Transfer Item Category (NLN), for example:

- Item category NLIR for the Stock Transfer to Receiving Valuated IST

process

- Item category NLI2 for the Stock Transfer from Issuing Valuated IST to

Receiving Plant process

- Item category NLI3 for the Stock Transfer from Issuing Valuated IST via

Receiving Valuated IST to Receiving Plant process

o Returns:


item category Standard Stock Transfer Return Item Category (NLRN), for

example:

- Item category NLRR for the Return Stock Transfer from Originally

Receiving Valuated IST to Originally Issuing Plant process

- Item category NLR2 for the Return Stock Transfer from Originally

Receiving Plant to Originally Issuing Valuated IST process

- Item categoryNLR3 for the Return Stock Transfer from Originally




Plant process

5. Defining Item Category Determination in Deliveries


Item Category Determination in Deliveries .

o Stock Transfers:

Ensure that for all entries with delivery type Replenishment Delivery (NL), a copy

has been created and altered as follows:

- Delivery type NL has been changed for each entry to delivery type Stock

Transfer to Receiving Valuated IST (NLIR).

Item category Standard Stock Transfer Item Category (NLN) has been

changed for each entry to NLIR.


Transfer from Issuing Valuated IST to Receiving Plant (NLI2).

Item category NLN has been changed for each entry to NLI2.


Transfer from Issuing Valuated IST via Receiving Valuated IST to

Receiving Plant (NLI3).

Item category NLN has been changed for each entry to NLI3.

o Returns:

Ensure that for each returns process, for all entries with delivery type Return,

Stock Transport Order (NLR), a copy has been created and altered as follows:

- Delivery type NLR has been changed for each entry to delivery type

Return Stock Transfer from Originally Receiving Valuated IST to Originally Issuing Plant (NLRR).

Item category Standard Stock Transfer Return Item Category (NLRN) has

been changed for each entry to NLRR.


Return Stock Transfer from Originally Receiving Plant to Originally Issuing

Valuated IST (NLR2).

Item category NLRN has been changed for each entry to item category

NLR2.


Return Stock Transfer from Originally Receiving IST via Originally Issuing Valuated IST to Originally Issuing Plant (NLR3).

Item category NLRN has been changed for each entry to item category

NLR3.

6. Defining New Schedule Line Categories in Deliveries


Schedule Lines -> Define Schedule Line Categories.

See also release note LOG_MM_SIT: Movement Types (New).

o Stock Transfers:

Ensure that for each process, a new schedule line category has been created as

a copy of schedule line category Replenishment Without Materials Planning (NN), for example:

- Schedule line category N4 for the Stock Transfer to Receiving Valuated

IST process, detailed data:

Movement type: 68C (Stock Transfer to Receiving Valuated IST)




IST to Receiving Plant process, detailed data:

- Movement type = 68A (Stock Transfer to Issuing Valuated IST)

- Movement Type for Issuing Valuated Stock in Transit = 681 ( Stock

Transfer from Issuing Valuated IST to Receiving Plant)




IST to Receiving Valuated IST process, detailed data:

- Movement type = 68A (Stock Transfer to Issuing Valuated IST)

- Movement Type for Issuing Valuated Stock in Transit = 68E (Goods

Issue from Issuing Valuated IST to Receiving IST)



Transit)

Note:

In the case of intra-company-code stock transfers and their corresponding return

stock transfers, the Specification for Issuing Valuated Stock in Transit field is

not mandatory.

o Returns:

Ensure that for each process a new schedule line category has been created as a copy of schedule line category Replenishment, Return (NR), for example:


Receiving Valuated IST to Originally Issuing Plant process, detailed data: Movement type = 69C (Stock Transfer, Return from Originally Receiving

Valuated IST)


Receiving Plant to Originally Issuing Valuated IST process, detailed data: - Movement type = 69A (Stock Transfer, Return from Originally Issuing

Valuated IST)

- Movement Type for Issuing Valuated Stock in Transit = 691 ( Stock

Transfer, Return to Originally Issuing Valuated IST from Originally

Receiving Plant)




Receiving IST to Originally Issuing Valuated IST process, detailed data:

- Movement type = 69A (Stock Transfer, Return from Originally Issuing

Valuated IST) - Movement Type for Issuing Valuated Stock in Transit = 69E ( Stock

Transfer Return to Originally Issuing Valuated IST from Originally

Receiving Valuated Stock in Transit) - Specification for Issuing Valuated Stock in Transit = 1 (Goods Issue


Transit)

7. Assigning New Schedule Line Categories to the New Item Category


Schedule Lines -> Assign Schedule Line Categories.

o Stock Transfers

Ensure that for each process, new entries have been created as a copy of the entry with item category Standard Stock Transfer Item Category (NLN) and

schedule line category Replenishment Without Materials Planning (NN) with the



following changes:

- Item category NLN is changed to item category Stock Transfer to

Receiving Valuated IST (NLIR).

Schedule line category NN is changed to schedule line category Stock

Transfer to Receiving Valuated IST (N4).

- Item category NLN is changed to item category Stock Transfer from

Issuing Valuated IST to Receiving Plant (NLI2).


Transfer from Issuing Valuated IST to Receiving Plant (N5).

- Item category NLN is changed to item category Stock Transfer from

Issuing Valuated IST via Receiving Valuated IST to Receiving Plant

(NLI3).


Transfer from Issuing Valuated IST to Receiving Valuated IST (N6).

o Returns:

Ensure that for each process, new entries have been created as a copy of the entry with item category Standard Stock Transfer Return Item Category (NLRN)

and schedule line category Replenishment, Return (NR) with the following

changes:

- Item category NLRN is changed to item categoryReturn Stock Transfer

from Originally Receiving IST to Originally Issuing Plant (NLRR).

Schedule line category NR is changed to the corresponding schedule line

category R4.


from Originally Receiving Plant to Originally Issuing Valuated IST (NLRN).


category R5.


from Originally Receiving IST to Originally Issuing Valuated IST (NLR3).


category R6.

Note:

To control that the item in a stock transport order or a delivery is relevant for the proof

of delivery, you have defined proof-of-delivery relevance in Customizing for Logistics

Execution, under Shipping -> Deliveries -> Proof of Delivery -> Set POD-

Relevance Depending on Delivery Item Category.

See also











LOG_MM_SIT: Movement Types (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL_605), business

function MM, Stock in Transit, and Actual Costing (New), there are new movement

types available for cross-company-code and intra-company-code stock transfers, for

corresponding returns, and for outbound deliveries of materials. You can map the

following processes:

o Stock transfer with transfer of title at goods issue, and return with transfer of title

at goods receipt via return delivery

o Stock transfer with transfer of title at goods receipt, and return with transfer of

title at goods issue via return delivery

o Stock transfer with transfer of title during transit and return with transfer of title

during transit

o Outbound delivery with transfer of title at customer location

For more information on Customizing, see

o LOG_MM_SIT: Cross-Company-Code Stock Transfer and

Customer Delivery (New)

o LOG_MM_SIT: Intra-Company-Code Stock Transfer (New)

The following new movement types are available:

For cross-company-code stock transfers:

o 681 (Stock Transfer to Issuing Valuated Cross-Company-Code Stock in Transit

(CST))

o 683 (Stock Transfer to Receiving Valuated CST)

o 685 (Stock Transfer from Issuing Valuated CST)

For delivery of goods to customers:

o 687 (Delivery of Goods to Issuing Valuated Stock in Transit)

For intra-company-code stock transfers:

o 68A (Stock Transfer to Issuing Valuated Intra-Company-Code Stock in Transit

(IST))

o 68C (Stock Transfer to Receiving Valuated IST)

o 68E (Stock Transfer from Issuing Valuated IST to Receiving Valuated Stock in

Transit)

o 68I (Stock Transfer from Issuing Valuated IST to Receiving Plant)

For cross-company-code returns:

o 167 (Goods Receipt, Return from Valuated Goods Receipt Blocked Stock)

o 169 (Goods Receipt, Return to Valuated Goods Receipt Blocked Stock)

o 691 (Stock Transfer, Return from Originally Issuing Valuated CST)

o 693 (Stock Transfer, Return from Originally Receiving Valuated CST)

o 695 (Stock Transfer, Return to Originally Issuing Valuated CST)

For intra-company code returns:



o 69A (Stock Transfer, Return from Originally Issuing Valuated IST)

o 69C (Stock Transfer, Return from Originally Receiving Valuated IST)

o 69E (Stock Transfer, Return to Originally Issuing Valuated IST from Originally

Receiving Valuated Stock in Transit)

o 69I (Stock Transfer, Return to Originally Issuing Valuated IST from Originally

Receiving Plant)

The following movement types are also relevant:

o 101 (Goods Receipt)

o 107 (Goods Receipt to Valuated Goods Receipt Blocked Stock)

o 109 (Goods Receipt from Valuated Goods Receipt Blocked Stock)

o 161 (Purchase Order Return)

o 417 (Stock Transfer, Storage Location to Delivery)

o 418 (Returns Stock Transfer, Storage Location to Delivery)

o 555 (Scrapping from Blocked Stock in Transit)

o 556 (Returns, Scrapping from Blocked Stock in Transit)

o 559 (Scrapping (or Goods Issue) from Valuated Goods Receipt Blocked Stock

(Adjustment Posting)

o 560 (Returns Scrapping (or Goods Issue Reversal) from Valuated Goods

Receipt Blocked Stock (Adjustment Posting)

o 601 (Goods Issue for Delivery)

The movement type for reversals is typically [movement type +1].

For more information on movement types and their usage, see the documentation for

the Customizing activity Copy, Change Movement Types.

Note on Materials Subject to Batch Management Requirements:

If you transfer materials subject to batch management requirements to another

company code, the system automatically proposes the batch number of the goods

issue batch for the goods receipt into the stock in transit (movement type 107) of the

receiving plant. You can change the batch number proposed by the system as follows:

o Direct change by user

o Change in the Customizing activity for the BAdI: Check Line Before

Adoption in Blocking Tables (MB_CHECK_LINE_BADI)

Note:

When you are booking out the stock in transit in the receiving plant and booking

it into the plant's warehouse stock (movement type 109), it is not possible to

change the batch or the valuation type. If you need to post the material quantity

to a different or a new batch number, you have the following options:

- Manual transfer posting (movement type 309)

- Transfer posting by making a usage decision, if an inspection lot was

generated at goods receipt.

Example:

The schema below shows the following processes (selected examples) with their

movement types:



1. Cross-company-code stock transfer with transfer of title at goods issue

2. Cross-company-code stock transfer with transfer of title at goods receipt

3. Cross-company-code stock transfer with transfer of title during transit

4. Delivery with transfer of title at customer location

5. Cross-company-code return stock transfer with transfer of title at goods receipt via

return delivery

Note: For more information about stock transfers and their corresponding return stock

transfers (cross-company-code and intra-company-code), see SAP Library.

For 1: Plant (A) ------------------[683+107]-> v.CST (B) -[109]-> Plant (B)

For 2: Plant (A) -[681]-> v.CST (A) ----------[685 + 101]-------> Plant (B)

For 3: Plant (A) -[681]-> v.CST (A) -[685+107]-> v.CST (B) -[109]-> Plant (B)

For 4: Plant (A) -[687]-> v.SiT (A) ----------------[601]----------> Customer

For 1R: Plant (A) <----[693+167]-----------v.CST (B) <-[109->169]- Plant (B)

(A) = issuing company code A

(B) = receiving company code B

----[movement type]--->

v.CST = valuated cross-company-code stock in transit

v. SiT = valuated stock in transit

Explanation of process 1, 2, and 3 (cross-company-code stock transfers):

o Transfer of Title at Goods Issue:

- First step: Issuing Plant -> Receiving Valuated CST

In transaction VL02N (Change Outbound Delivery), you post the material

from the unrestricted-use stock of the issuing plant to the valuated cross-

company-code stock in transit of the receiving plant (movement types 683

and 107).

- Second step: Receiving Valuated CST -> Receiving Plant

In transaction MIGO, Goods Receipt, you post the material from the

valuated cross-company-code stock in transit of the receiving plant to the

unrestricted-use stock of the receiving plant (movement type 109).

o Transfer of Title at Goods Receipt:

- First step: Issuing Plant -> Issuing Valuated CST



company-code stock in transit of the issuing plant (movement type 681).

- Second step: Issuing Valuated CST -> Receiving Plant

In transaction VLPOD (Proof of Delivery - Change Outbound Delivery),

you post the material from the valuated cross-company-code stock in

transit of the issuing plant to the unrestricted-use stock of the receiving

plant (movement types 685 and 101).

o Transfer of Title During Transit

- First step: Issuing Plant -> Issuing Valuated CST



company-code stock in transit of the issuing plant (movement type 681).

- Second step: Issuing Valuated CST -> Receiving Valuated CST

In transaction VLPOD (Proof of Delivery - Change Outbound Delivery),

you post the material from the valuated cross-company-code stock in

transit of the issuing plant to the valuated cross-company-code stock in

transit of the receiving plant (movement types 685 and 107).



- Final step: Receiving Valuated CST -> Receiving Plant

In transaction MIGO, Goods Receipt, you post the material from the

valuated cross-company-code stock in transit of the receiving plant to the

unrestricted-use stock of the receiving plant (movement type 109).

Explanation of process 4 (outbound delivery to customer):

o First step (transfer of title at customer location): Issuing Plant -> Issuing Valuated

Stock in Transit

In transaction VL02N, you post the material from the unrestricted-use stock of

the issuing plant to the valuated stock in transit of the issuing plant (movement

type 687).

o Second step, Issuing Valuated Stock in Transit -> Customer

In transaction VLPOD, you post the material from the valuated stock in transit of

the issuing plant to the customer (movement type 601).

Explanation of process 5 (return):

o First step (return with transfer of title at goods receipt via return delivery):

Receiving Plant -> Receiving Valuated Stock in Transit

To trigger a return stock transfer in transaction MIGO, post the goods receipt for

the standard delivery using movement type 109. If a return delivery exists for a

purchase order item that is flagged as a return item, the system then finds

movement type 169 automatically. The system uses this movement type to post

the material from the unrestricted-use stock of the originally receiving plant to the

valuated stock in transit of the originally receiving plant.

o Second step, Receiving Valuated Stock in Transit -> Issuing Plant

In transaction VL02N you post the material from the valuated stock in transit of

the originally receiving plant to the unrestricted-use stock of the originally issuing

plant.

Note:

For each process with a defined transfer of title, you must first create an

outbound delivery (transaction VL10B (Purchase Orders, Fast Display), under

Program -> Execute. You can set up this program to run periodically).


In Customizing for Materials Management, choose Inventory Management and

Physical Inventory -> Movement Types ->Copy, Change Movement Types.

There, you can check the movement types and the possible special stock indicators

that are mentioned in the documentation for the receiving and issuing side. Special

stock indicator T (Stock Transfer or Outbound Delivery via Issuing Stock in Transit) is

new.

See also











LOG_MM_SIT: Inbound Delivery with Stock in Transit (New)

Use


Function MM, Stock in Transit and Actual Costing, you can use condition type SPED

(Stock Transfer Generates Inbound Delivery to specify that inbound deliveries with

reference to an outbound delivery are automatically created for stock transfer

processes with receiving valuated stock in transit. The following functions are available

for inbound deliveries with stock in transit:

o At goods receipt you can post an inbound delivery either in the standard way

(movement type 101), or via the receiving stock in transit to the receiving plant

(movement type 109).

o If the quantity changes during the proof-of-delivery, the system updates the

inbound delivery. In transaction VLPOD (Proof of Delivery), the system displays

the difference (POD Overview tab, Variance from Actual Delivered Quantity

in Sales Unit).

o The new transaction MB5SIT (Display Stock in Transit) allows you to

- display receiving stock in transit for the intra-company and cross-company

process, by entering the inbound delivery number

- display issuing valuated and receiving valuated stock in transit

o If you have created an inbound delivery using condition type SPED, you can post

the material from issuing valuated stock in transit to receiving valuated stock in

transit in transaction VLPOD. To post into the receiving plant, you must use

movement type 109 in transaction VL32N or MIGO.

Note:

If you have to enter a handling unit for the storage location in the receiving plant, post

first into the valuated stock in transit of the receiving plant. From the valuated stock in

transit of the receiving plant, you can then post the goods receipt with reference to the

inbound delivery into the storage location with mandatory handling unit.


To set up inbound deliveries with stock in transit, you need to make the following

settings in Customizing:

1. Check confirmation control key:

In Customizing, choose Materials Management -> Purchasing ->

Confirmations -> Set Up Confirmation Control For the confirmation control key 0004 (Inbound Delivery), the following must be

flagged under Confirmation Sequence:

- Confirmation is GR-Relevant checkbox

- GR with Reference to Confirmation checkbox

2. Define condition type SPED:

In Customizing, choose Logistics Execution -> Shipping -> Basic Shipping

Functions -> Output Control -> Output Determination -> Maintain Output

Determination for Outbound Deliveries -> Maintain Output

Determination Procedure.

Select schema V10000 (Header Output) and choose Control Data. Check that an

entry exists with condition type SPED (Stock Transfer Generates Inbund



Delivery) and Requirement 408 (Stock Transfer Attachment ID).

3. Define delivery type

In Customizing, choose Materials Management -> Purchasing ->

Confirmations -> Define Internal Confirmation Categories.

Check that for confirmation category LA (Inbound Delivery), the new field

Delivery Type Inbound Stock in Transit (SiT) contains a delivery type for the

process with stock in transit (for example Inbound Delivery of Receiving Valuated Stock in Transit (ELST). This delivery type must use an item category (for

example ELST) that uses movement type 109 or another movement type with

posting string reference 109. Check the following:

- In Customizing for Logistics Execution, under Shipping -> Deliveries ->

Define Item Category Determination in Deliveries, check the

item category that is assigned to this delivery type.

- In Customizing, under Logistics Execution -> Shipping -> Deliveries ->

Define Item Categories for Deliveries, check that movement

type 109 or a movement type with posting string reference 109 is assigned

to this item category.

4. Set up condition record

You create inbound deliveries with this item category when processing output

type SPED during the goods issue of an outbound delivery.

In transaction VV22 (Change Output - Condition Records: Shipping), ensure that

the correct condition records for the outbound delivery type used (NCCR, NCC3, NLIR, or NLI3) have been created for output type SPED for output determination.

Output type SPED with role WE (Goods Receiver), medium 8 (Special Function)

and time 4 (Send Immediately (When Saving Application).


- Cross-Company-Code Stock Transfer and Customer

Delivery (New)

- Intra-Company-Code Stock Transfer (New)

See also











LOG_MM_SIT: Actual Costing for Processes with Stock in Transit (New)

Use


function MM, Stock in Transit and Actual Costing (LOG_MM_SIT), you can map

cross-company code stock transfer processes with valuated stocks in transit in the

actual costing multilevel as follows:

o In the legal view, an intercompany profit is displayed that is calculated based on

the actual price of the sender and the purchase price of the receiver.

o In the group view, price differences on the receiver side are rolled up, and the

cost component split transferred to the receiving company code.

o In the profit center view, these processes are not mapped multilevel, meaning

with a profit center change no intercompany profit is displayed. With cross-

company code profit centers, no price differences are rolled up, and no

component split transferred.

The posting of price differences can be made to different revaluation and price

difference accounts or cost components, depending on the reason for the price change.

The following process variants are supported:

o Cross-company code stock transfer order in 1 step procedure

o Returns for cross-company code stock transfer order in 1 step procedure

o Stock transfer order with valuated stock in transit of the sender

o Stock transfer order with valuated stock in transit of the sender and receiver

o Stock transfer order with valuated stock in transit of the receiver

o Returns for stock transfer order with valuated stock in transit of the (original)

receiver

If you perform a parallel valuation in the profit center view, the system creates

additional lines for internal good movements for stock transfers within a company code,

at the time of the transfer of title from the sender to the recipient. This enables you to

display costs and revenues for each profit center. You can influence account

determination for the additional posting lines as follows:

o You can differentiate the accounts for internal stock changes on the sender and

receiver side.

o Using a business add-in (BAdI), you can change the valuation class that the

system uses to determine the relevant accounts.

For the debit and credit of materials, you can control the account determination for

posting price differences depending on the price change reason. To do this, you use

either an account grouping code or, if you want to post to a cost component, an origin

group. Business Application Programming Interfaces (BAPI) are available to you to

automate the debit and credit of materials.


You must have made the following Customizing settings:

o In Customizing of Product Cost Controlling under Product Cost Planning ->

Basic Settings for Material Costing -> Define Cost Component Structure, create a new cost component in your cost component structrue for

the intercompany profit in the legal view.



o Under Delta Profit for Group Costing, set the indicator Company Code for

this cost component.

If necessary you can make the following settings:

o To determine that the account determination for the credit and debit of materials

is dependent on the price change reason, in Customizing for Controlling under

Product Cost Controlling -> Actual Costing/Material Ledger -> Reasons for Price Changes define an account grouping code for each price change

reason. If you want to post to a cost component, assign an origin group to the

reasons for price changes of the account grouping code.

Note

You can also use Business Application Programming Interfaces (BAPIs) for the

debit and credit of materials.

o To overwrite the posting lines automatically created for the account

determination of profit center accounting for processes with valuated stock in

transit, use the Businss Add-In Modification of Account Determination for

Transfer Prices in Customizing for General Ledger Accounting (New) under

Business Transactions -> Parallel Valuation Approaches/Transfer Prices ->

Settings for Internal Goods Movements -> Enhancements for Transfer

Prices -> Modification of Account Determination for Transfer Prices.

o To suppress the automatic creation of posting lines, use Business Add-In

Suppression of Additional Lines for Transfer Prices in Customizing for General

Ledger Accounting (New) under Business Transactions -> Parallel

Valuation Approaches/Transfer Prices -> Settings for Internal Goods

Movements -> Enhancements for Transfer Prices -> Suppression of Additional Lines for Transfer Prices.

See also

Release note LOG_MM_SIT: Business Function MM, Stock in Transit

and Actual Costing (New)

The SAP Library for SAP ERP on the SAP Help Portal under http://help.sap.com/erp -

> SAP ERP Central Component -> Accounting -> Controlling (CO) -> Product

Cost Controlling (CO-PC) -> Actual Costing/Material Ledger (CO-PC-ACT) ->

Selected Functions -> Cross-Company Code Stock Transfer Processes.



Business Function Expediting Data in Purchase Order

LOG_XPD_EXT_1: Progress Tracking Data in the Purchase Order (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0, Enterprise Extension PLM (EA-

PLM 605), you can use the business function PS, Progress Tracking Data in the

Purchase Order (LOG_XPD_EXT_1).

This business function provides the following new functions:

o Display progress tracking data in the purchase order

You can access status information and progress tracking data for tracking the

progress of purchase orders in the purchase order details. The new Progress

Tracking tab page provides the same data as the overview screen of the

Progress Tracking: Purchase Order Selection transaction (EXPD).

- You can use list fields to choose the purchase order item and order

schedule line for which you want the system to display an overview of all

relevant progress tracking data. From the event overview, you can access

the progress tracking subitems and query status information.

- You can use the new Business Add-In (BAdI) BADI_EXPD_MM to specify

which progress tracking profile the system should use to display the

progress tracking data in the purchase order. If you do not implement the

BAdI, the system determines the progress tracking profile from the

personal settings in the user master. Note:

In the purchase order, you can only display progress tracking data. To select

order schedule lines as progress tracking objects and enter or change progress

tracking data, you must use the Progress Tracking: Purchase Order Selection

transaction (EXPD).

o Archive purchase order-related progress tracking data

The system archives all order-related progress tracking data that is displayed on

the Progress Tracking tab page together with the purchase order. Data on the

event scenario assignment and the change time stamp is deleted. When you

display archived purchase orders (ME23N), the system also displays the

archived progress tracking data.

There is a also a new BAdI called EXPD_ENHANCE, with which you can implement

customer-specific enhancements in progress tracking.


The purchasing transactions for changing, displaying, and releasing purchase orders

(ME22N; ME23N; ME29N) provide the new Progress Tracking tab page in the item

details.


The display of progress tracking data in the purchase order item details is not

determined by your own, customer-specific Customizing settings. To create and

change progress tracking data in transaction EXPD, however, you must have made the

required settings in Customizing for Materials Management under Purchasing ->

Purchase Order -> Progress Tracking.

You implement the BAdIs in Customizing for Project System under Progress ->

Business Add-Ins for Progress Tracking.



See also

SAP Library for SAP ERP Central Component on SAP Help Portal at

http://help.sap.com -> Logistics -> Materials Management (MM) -> Purchasing (MM-

PUR) -> Progress Tracking (PS-PRG-TRC).



Additional Release Notes

Enterprise Service for Purchase Order Confirmation (New)

Use

As of SAP enhancement package for SAP ERP 6.0 (SAP_APPL_605), the new

enterprise service PurchaseOrderERPConfirmationRequest is available. You can use

the service to process purchase order confirmations, that is, the service transfers

confirmations of the type order acknowledgement, rough goods receipt, and shipping

notification to the SAP ERP system.

You can use the service to process the following data:

o Header texts

o Item texts

o Confirmed price at item level

o Rejection indicator at item level

o Confirmations

See also

SAP Library on SAP Help Portal at http://help.sap.com/ -> SOA (Documentation

Service Oriented Architecture).



BAPI for Comprehensive Posting of Incoming Invoices (New)

Use

As of SAP enhancement package 5 for SAP ERP 6.0 (SAP_APPL_605), you can use

the new Business Application Programming Interface (BAPI) CreateFormData1

(Invoice Verification: Post Incoming Invoice) in the Materials Management (MM)

component for the business object Incoming Invoice (BBPIncomingInvoice). You

can use this method to hold, park, park as complete, or post incoming invoices.

See also

For more information, see the documentation on the function module:

BAPI_INCOMINGINVOICE_CREATE1 (transaction SE80, function group

MRM_BAPI).

Release Notes - SAP Help Portal

Documents

Transcript of Release Notes - SAP Help Portal