CONFIGURATION DOCUMENT

Contents

1. ENTERPRISE STRUCTURE CONFIGURATION................................................................ 3

1.1 Create Factory Calender (Tcode SCAL) ........................................................................ 3
1.2 Create Plant ......................................................................................................... 5
1.3 Assignment Of Plant to Company codes ......................................................................... 11
1.4 Purchase Organisation ................................................................................................ 12
1.5 Storage Location ................................................................................................... 16

2. MATERIAL MASTER BASIC SETTING ............................................................................. 19

2.1 Maintain Company Codes for Materials Management .......................................................... 19
2.2 Material Type Configuration ........................................................................................ 21
2.3 Material group Configuration ....................................................................................... 25

3. PURCHASING CONFIGURATIONS................................................................................... 27
3.1 Purchase Group Configuration ...................................................................................... 27
3.2 PR document Type Configuration .................................................................................. 28
3.3 PO document Type Configuration .................................................................................. 30
3.4 Output Message Settings PO ......................................................................................... 32
3.5 Price determination Process ........................................................................................ 32

4. VALUATION CLASS & ACCOUNT CATEGORY REFERENCE CONFIGURATION ................ 46

4.1 Account Category Reference ........................................................................................ 46
4.2 Valuation class configuration ....................................................................................... 48

5. SCREEN LAYOUT FOR MIGO .......................................................................................... 49

6. MOVING AVERAGE PRICE VARIANCE IN GR .................................................................. 51

7. VENDOR ACCOUNT GROUPS & NO RANGE ASSIGNMENT ........................................... 53

7.1 Vendor account Groups .......................................................................................... 53
7.2 Vendor account Number Range Assignment ................................................................. 55

8 OUTPUT FORM ASSIGNMENT ..................................................................................... 59

8.1 PO Message Type Form Assignment ........................................................................... 59
 CONFIGURATION DOCUMENT
9 STO-MM CONFIGURATION FOR YO6 DOCUMENT TYPE ............................................. 63
9.1 STO Schema Determination ..................................................................................... 64
 CONFIGURATION DOCUMENT
1. Enterprise Structure Configuration

In this section, you will learn how to portray the specific organizational structure of your business in the R/3
System.

To help you portray your company structure, different Accounting, Logistics and Human Resources organization
units are provided.

First analyze the structures and procedures in your company, and then match them to the SAP structures. There
are various organization elements defined as examples in the standard version. Normally these would not cover all
your needs. Extend the elements as required.

During the clarification stage, work with the structures delivered by SAP. In order to obtain a high degree of
indentification and acceptance from project members and user departments from the start, you may have to
change some of SAP's terminology.

You should limit the number of persons authorized to maintain organization elements. Define the authorization
profiles accordingly. As soon as your organization units are ready, access should be locked so that no other
changes can be made.

1.1 Create Factory Calender (Tcode SCAL)

Select the change button highlighted above.

 CONFIGURATION DOCUMENT

Click on the Create button.

Save
 CONFIGURATION DOCUMENT
1.2 Create Plant

Node: Define, copy, delete, check plant

Transaction Code/Menu Path: SPRO > Enterprise Structure > Definition > Logistics General >
Define Copy Delete Check Plant
Client Dependency: Client Specific
Description: In this IMG Activity a new Plant is copied from an existing Plant

Define, copy, delete, check plant

The plant is an operating area or branch within a company.

The plant is embedded in the organizational structure as follows:

 The plant is assigned to a single company code. A company code can have several plants.

 Several storage locations in which material stocks are managed can belong to a plant.

 A single business area is assigned to a plant and to a division.

 A plant can be assigned to several combinations of sales organization and distribution channel.

 A plant can have several shipping points. A shipping point can be assigned to several plants.

 A plant can be defined as a maintenance planning plant.

A plant has the following attributes:

 A plant has an address.

 A plant has a language.

 A plant belongs to a country.

 A plant has its own material master data. You can maintain data at plant level for the following views on a
material master record in particular: Purchasing, Storage, Sales, Accounting etc.

The plant plays an important role in the following areas:

 material valuation

If the valuation level is the plant, the material stocks are valuated at plant level. If the valuation level is the
plant, you can define the material prices for each plant. Each plant can have its own account
determination.
 CONFIGURATION DOCUMENT
 inventory management

The material stocks are managed within a plant.

Further notes

Choose "Administer" or "Copy, delete, check plant" to work on a plant. The system changes the plant table and all
dependent Customizing and system tables where the plant occurs as a key. For more, see Copy/Delete/Check /
Edit Project IMG.

Recommendation

Plant 0001 is already preset in all dependent tables. SAP recommends that you change only the attributes and not
this number. For further settings, this enables you to access the sample entries, considerably reducing the time
required for maintenance. To create new plants, use the Extended Copyer to make copies of Plant 0001.

Activities

1. Create your plants and their respective local data, referring closely to the reference (plant 0001)
provided by SAP.
2. You can also copy, delete or check environment data.
3. You the Project IMG view to work on the data the system has changed. The generated project view is
retained so you can do this work later.

Create Plant 1100 (Oppo Edapalli Warehouse)

 CONFIGURATION DOCUMENT

Copying the Plant from existing Plant 0001 create new plant 1100
 CONFIGURATION DOCUMENT

Save
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
Create Plant 1200 (Oppo Electronics Kerala Corprate Office)

Create Plant 2100 (Oppo PoP Warehouse Muppathadam)

 CONFIGURATION DOCUMENT

All three plants created

1.3 Assignment Of Plant to Company codes

Node: Define, copy, delete, check plant

Transaction Code/Menu Path: SPRO > Enterprise Structure > Assignment > Logistics General >
Assign Plant to Company code
Client Dependency: Client Specific
Description: Plant assignment to Company code
TR # generated

In the IMG activity "Assignment Plant - Company Code" you assign each plant to a company code.

A plant can only belong to one company code.

Note

Complete functionality of the system can only be ensured if the plants assigned to a company code are only those
situated in the same country as the company code.

Requirements

Before you can assign plants to company codes, you must define the valuation control.

You may change the valuation control in the production system only after contacting your SAP consultant.
Changes may cause inconsistencies in documents.

Actions

Assign your plants to company codes.

 CONFIGURATION DOCUMENT

1.4 Purchase Organisation

Node: Define, copy, delete, check plant

Transaction Code/Menu Path: SPRO > Enterprise Structure > Definition > Materials Management
> Purchase Organisation
Client Dependency: Client Specific
Description: Purchase Organisation

In this step, you set up your purchasing organizations.

From the Materials Management and Purchasing view, the purchasing organization is responsible for all
purchasing activities (including the processing of requests for quotations and purchase orders, for example).
 CONFIGURATION DOCUMENT
The purchasing organization is integrated within the organizational structure as follows:

 A purchasing organization can be assigned to several company codes.

(= Corporate-group-wide purchasing).

 A purchasing organization can be assigned to one company code.

(= Company-specific purchasing).

 A purchasing organization can also exist without being assigned to a company code.

o Since each plant must be assigned to a company code, the latter can be determined via the plant
at the time of each procurement transaction even if the procuring purchasing organization has not
been assigned to a company code.

 A purchasing organization must be assigned to one or more plants.

(= Plant-specific purchasing).

 A purchasing organization can be linked to one or more other purchasing organizations.

(= reference purchasing organization)
For more on this topic, refer to Assign Purchasing Organization to Reference Purchasing Organization.

 A purchasing organization can be divided into several purchasing groups that are responsible for different
operational areas.

 Each purchasing organization has its own info records and conditions for pricing.

 Each purchasing organization has its own vendor master data.

Possible organizational forms

You can organize your purchasing function in the following ways:

 Corporate-group-wide purchasing

 Company-specific purchasing

 Plant-specific purchasing

All of these forms can co-exist within a single client.

Corporate-group-wide purchasing:

A purchasing organization is responsible for the purchasing activities of different company codes.
In this case, you do not assign a company code to the purchasing organization, but specify the company code
concerned for each individual purchasing transaction. You assign plants from different company codes to the
purchasing organization.

Company-specific purchasing:
 CONFIGURATION DOCUMENT
A purchasing organization is responsible for the purchasing activities of just one company code.
In this case, you assign a company code to the purchasing organization. The purchasing organization may procure
only for this company code. You assign only plants of the company code concerned to the purchasing
organization.

Plant-specific purchasing:

A purchasing organization is responsible for the purchasing activities of one plant.

In this case, you assign the plant and the company code of the plant to the purchasing organization. The
purchasing organization may procure for this plant only.
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT

1.5 Storage Location

Node: Define, copy, delete, check plant
Transaction Code/Menu Path: SPRO > Enterprise Structure > Definition > Materials management
> Storage Location
Client Dependency: Client Specific
Description: Storage Location

A storage location is the place where stock is physically kept within a plant.

A storage location has the following attributes:

 There may be one or more storage locations within a plant.

 A storage location has a description and at least one address.

 It is possible to store material data specific to a storage location.

 Stocks are managed only on a quantity basis and not on a value basis at storage location level.

 Physical inventories are carried out at storage location level.

 Storage locations are always created for a plant.

CONFIGURATION DOCUMENT
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
See Table T001L

2. MATERIAL MASTER BASIC SETTING

2.1 Maintain Company Codes for Materials Management

Node: Fiscal Year Maintenance for Company code for Materials

Management
Transaction Code/Menu Path: SPRO > Logistics General > Materials Master > Basic Settings >
Maintain Company codes for materials mangement
Client Dependency: Transportable
Description: Fiscal Year Maintenance for Company code for Materials
Management

In this IMG activity, you maintain your company codes. There are two situations in which you do this:

 When setting up company codes for materials management

 When changing the Allow backposting or Disallow backposting indicators

To create a material master record, the control record must exist for the company code for which you want to
create your master record.
 CONFIGURATION DOCUMENT
To set up a company code, enter the current period here. Alternatively, you can do this with the period closing
program.
 CONFIGURATION DOCUMENT

2.2 Material Type Configuration

Node: Define Attributes of Material Type

Transaction Code/Menu Path: SPRO > Logistics General > Materials Master > Basic Settings >
Material Type
Client Dependency: Transportable
Description: Attributes of Material Type

Whenever you create a material master record, you must assign it to a material type. This requires you to first
define the attributes of each material type. You do this in this IMG activity.

Material types are used in the following neighboring areas, where they are also configured in Customizing:

 Profit Center Accounting

 Sales and Distribution ( availability check)

 Valuation and Account Assignment ( valuation classes)

CONFIGURATION DOCUMENT
CONFIGURATION DOCUMENT
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT

2.3 Material group Configuration

Node: Define Material groups

Transaction Code/Menu Path: SPRO > Logistics General > Materials Master > Settings for Key
fields > Define Material groups
Client Dependency: Transportable
Description: Define Material groups

In this IMG activity, you define material groups. With material groups you group materials with the same attributes
or purpose.

You can use material groups to:

 Limit the scope of analyses

 Systematically search for material master records via matchcodes

Note
 CONFIGURATION DOCUMENT
In the component Sales and Distribution (SD), you can assign material groups to divisions.

Actions

1. Define your material groups.

2. Assign each material to a material group.
 CONFIGURATION DOCUMENT
3. PURCHASING CONFIGURATIONS

3.1 Purchase Group Configuration

Node: Create Purchase Groups

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Create Purchase
Groups
Client Dependency: Transportable
Description: Create Purchase Groups

In this step, you can create purchasing groups.

A purchasing group can be an individual or a group of individuals.

 CONFIGURATION DOCUMENT

3.2 PR document Type Configuration

Node: Define Document Types

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Purchase
Requisitions > Define Document types
Client Dependency: Transportable
Description: Define Document Types for Purchase Requisition

The SAP System manages purchase requisitions as documents. You can group requisitions into any number of
document types.

In this step, you can do the following:

 Create new document types

 Define the item interval

 Define allowed follow-on document types

 Assign document types to a number range group

 Define number range interval

 Choose type of number assignment (internal or external)

You maintain the associated number ranges in the step Define Number Ranges under "Purchasing".

 Define Detailed Settings for Serial Numbers

Standard Settings

The following settings are defined as standard, and SAP recommends that you use them:

 Document type: NB for standard purchase orders

Number ranges:

o internal from 0000000001 to 0999999999

o external from 1000000000 to 1999999999

 Document type: TB for transport orders

Number ranges:
 CONFIGURATION DOCUMENT
o internal from 0000000001 to 0999999999

o external from 1000000000 to 1999999999

 CONFIGURATION DOCUMENT

3.3 PO document Type Configuration

Node: Define Document Types

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Purchase Order >
Define Document types
Client Dependency: Transportable
Description: Define Document Types for Purchase Order

The SAP system manages purchase orders as documents. You can group purchase orders in as many document
types as you like.

In this work step, you can do the following:

 Create new document types

 Define item interval

 Determine allowed follow-on document types

 Assign document types to a number range group

 Define number range interval

 Select type of number assignment

o Internal

o External

 Select update group

The update group controls how data from the document header is updated to the statistics file.

 Define detailed settings for serial numbers

Default Settings

The following document types/number ranges are defined as standard:

 Document type: NB for standard purchase orders

Number ranges:
 CONFIGURATION DOCUMENT
o internal from 4500000000 to 4599999999

o external from 4100000000 to 4199999999

 Document type: TB for transport orders

Number ranges:

o internal from 4500000000 to 4599999999

o external from 4100000000 to 4199999999

 CONFIGURATION DOCUMENT

3.4 Output Message Settings PO

3.4.1 Message Type

Node: Maintain Message Type for PO

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Messages>Output
Control > Message Type >Define Message Types for PO >
Maintain Message Type for PO
Client Dependency: Transportable
Description: Maintain Message Type for PO

3.4.2 Message Determination Schema

Node: Define Message Determination Schema for PO

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Messages>Output
Control > Message Determination Schema >Define Message
Determination Schema for PO
Client Dependency: Transportable
Description: Define Message Determination Schema for PO

3.5 Price determination Process

 CONFIGURATION DOCUMENT
The following steps describe how the price determination process is controlled.

Before you set up the price determination facility in the SAP System, you should do the following:

 Check the dependencies under which prices, discounts, and surcharges are arrived at.
For example, determine whether different conditions apply to individual material groups and the basis on
which surcharges and discounts are calculated.

 Then bring your pricing dependencies into line with the criteria for price determination in the SAP System.

 After this, work through the following sections.

3.5.1 Account Key definition

Node: Define Transaction/Event Key

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Conditions>Price
Determination Process > Define Transaction Event Keys
Client Dependency: Transportable
Description: Define Transaction/Event Key

In this step, you define transaction/event keys for condition types involving provisions.

To enable the system to find the relevant account for provisions (for accrued delivery costs or miscellaneous
provisions, for example), you must assign a transaction/event (internal processing) key to each condition type that
is relevant to provisions in the step Define Calculation Schema.

If purchase account management is active within a company code, you must specify the transaction/event key in
the field 'AccKy'. If not, you make this specification in the field 'Provis.'.

Via "Transaction/Event Key Usage" and "Usage of Transaction Key in Purchase Account Management", you can
determine the calculation schemas in which these keys are used.

3.5.3 Schema Group for Purchase Organization

Node: Schema Group for Purchase Organization
Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Conditions>Price
 CONFIGURATION DOCUMENT
Determination Process > Define Schema Group > Schema Group
for Purchase Organization
Client Dependency: Transportable
Description: Schema Group for Purchase Organization
 CONFIGURATION DOCUMENT

For STO
 CONFIGURATION DOCUMENT

3.5.4 MM condition Types Configuration

Node: MM Condition Types
Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Conditions>Price
Determination Process > Define Condition Types
Client Dependency: Transportable
Description: MM Condition Types

In this step you define condition types.

The condition types are used to represent pricing elements such as prices, discounts, surcharges, taxes, or
delivery costs in the SAP System. These are stored in the system in condition records.
For condition types for which you wish to maintain conditions with their own validity period, you must specify an
access sequence. In this way, you stipulate the fields the SAP System is to check in its search for a valid condition
record.

Example:

An access sequence has been assigned to condition type PB00 so that prices can be maintained in purchasing
info records and contracts.

No access sequence has been assigned to condition type RC00 because it does not have a validity period of its
own. In the standard system, it is always maintained simultaneously with the price and is valid for the period of the
price.

Note

In a price calculation schema (which may also be termed a "pricing procedure"), you collect together all the
condition types that are automatically to be taken into account by the SAP System in the process of price
determination with regard to a business transaction.

Note that you can only also enter manually the condition types that are contained in the calculation schema.

You can alter the result of the price determination process in the purchasing document manually. You can limit the
change options for a condition type in this step.
 CONFIGURATION DOCUMENT

ZFR2 – Transportation Inv.

Copied from FRB2
 CONFIGURATION DOCUMENT

ZCUS - Customs copied from JCV1

 CONFIGURATION DOCUMENT

ZCLE – Clearing Charges

 CONFIGURATION DOCUMENT

3.9.8 Oppo Pricing Schema – Configuration

Node: Define Calculation Schema
Transaction Code/Menu Path: SPRO > Materials Management > Purchasing> Conditions>Price
Determination Process > Define Calculation Schema
Client Dependency: Transportable
Description: Define Calculation Schema

In this step, you define the calculation schemas.

In the MM area, a calculation schema - a framework of steps used to calculate or determine something - is used
among other things to calculate costs, prices, period-end rebates, and taxes.

Note

This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.

In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in
which sequence.
In the price (or cost) determination process, the SAP System automatically determines which calculation schema is
valid for a business transaction and takes into account, one after another, the condition types it contains.
 CONFIGURATION DOCUMENT
Standard settings

The following calculation schemas are predefined in the standard system. You should not change these schemas.

RM0000 and RM1000

Control the price determination process in POs, quotations, and scheduling agreements.

Both calculation schemas require 2 condition types for the gross price: one for automatic price determination
(standard: PB00) and one for manual maintenance (standard: PBXX).

RM0001 and RM1001

Determine which condition types you can enter in purchasing document headers with time-dependent conditions
(e.g. contracts).

RM0002, RM1002

Determine which additional condition types you can enter in purchasing document items with time-dependent
conditions or in the purchasing info record.

RMMP00

Defines the condition type for determining the market price which can be entered for each material.

RM2000

Controls the delivery cost determination process in stock transport orders and stock transport scheduling
agreements.
 CONFIGURATION DOCUMENT

Schema for Purchasing- ZRM000

 CONFIGURATION DOCUMENT

Schema for STO- ZRM200

 CONFIGURATION DOCUMENT

3.9.9 Inco Terms Configuration

Node: Define Inco Terms

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing>Vendor Master >
Check Inco term
Client Dependency: Transportable
Description: Check Inco term

"Incoterms" are international rules for the interpretation of the most commonly used terms of foreign trade.

In particular, the Incoterms regulate

 the division of costs, and

 the transfer of risks.

Standard settings

The standard SAP R/3 system includes the following Incoterms:

 CFR Cost and Freight

 CIF Cost, Insurance and Freight

 CIP Carriage and Insurance Paid To

 CPT Carriage Paid To

 DAF Delivered At Frontier

 DDP Delivered Duty Paid

 DDU Delivered Duty Unpaid

 DEQ Delivered Ex Quay (Duty Paid) etc.

CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
4. Valuation Class & Account Category reference Configuration

4.1 Account Category Reference

Node: Account Category reference
Transaction Code/Menu Path: SPRO > Materials Management > Valuation and Account
Assignment> Account Determination > Account Determination
Without Wizard > Define Valuation Classes > Account Category
reference
Client Dependency: Transportable
Description: Account Category reference

In this step, you define which valuation classes are allowed for a material type.

If a user creates a material, he must enter the material's valuation class in the accounting data. The ERP system
uses your default settings to check whether the valuation class is allowed for the material type.

The valuation class is a group of materials with the same account determination. If a transaction is to be posted to
different accounts depending on the valuation class, create an account determination for each valuation class in
the step Create automatic postings.

The valuation classes allowed depend on the material type. Several valuation classes are generally allowed for
one material type. A valuation class can also be allowed for several material types.

The link between the valuation classes and the material types is set up via the account category reference.

The account category reference is a combination of valuation classes. Precisely one account category reference is
assigned to a material type.
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
4.2 Valuation class configuration

Node: Valuation Class

Transaction Code/Menu Path: SPRO > Materials Management > Valuation and Account
Assignment> Account Determination > Account Determination
Without Wizard > Define Valuation Classes > Valuation Class
Client Dependency: Transportable
Description: Valuation Class
 CONFIGURATION DOCUMENT

5. Screen Layout for MIGO

Node: Field Selection for MIGO

Transaction Code/Menu Path: SPRO > Materials Management > Inventory Management &
Physical Inventory> Settings for Goods Movements (MIGO)
Client Dependency: Transportable
Description: Field Selection for MIGO

In this step, you maintain all the settings for field selection by movement type. This step replaces the activity Define
Screen Layout for the Enjoy transactions. The settings from Define Screen Layout are adopted in these settings
automatically so that you do not need to maintain new entries here.

You can specify for each field whether it is an optional entry or a mandatory entry. In the table, you see all fields
that are visible. You can access the setting Field Invisible by deleting the appropriate entry from the table.

There is no distinction between different special stock indicators in these entries. Special stock fields are always
suppressed automatically.

Standard settings
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
6. Moving Average Price variance in GR

Node: Tolerance Limits

Transaction Code/Menu Path: SPRO > Materials Management > Inventory Management &
Physical Inventory> Goods Receipt > Set Tolerance Limits
Client Dependency: Transportable
Description: Tolerance Limits

In this step, you set the tolerance limits for goods receipts.

When processing a goods receipt, the system checks each item to determine whether the goods receipt varies
from the purchase order or the material master data.

The different types of variances are defined by tolerance keys. For each tolerance key, tolerance limits can be set
per company code.

The following variances are checked in Inventory Management:

 Variance in the purchase order price quantity

(Explanation)
For this variance, two tolerance keys are provided:

o Tolerance key B1 (error message)

You use tolerance key B1 to define the maximum percentage variance. If the variance is greater
than the maximum variance, the system creates an error message. The user cannot post the
goods receipt.

o Tolerance key B2 (warning message)

Tolerance key B2 defines the percentage variance from which a warning message is to be
issued. It is possible to post the goods receipt.

 Variance for the moving average price of the material

CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT

7. Vendor Account Groups & No Range Assignment

7.1 Vendor account Groups

Node: Define Vendor Account groups
Transaction Code/Menu Path: SPRO > Logistics General > Business Partner > Vendors > Control
> Define Account Groups & Field selection
Client Dependency: Transportable
Description: Define Vendor Account groups

In this step, you define account groups for vendors. When creating a vendor master record, you must specify an
account group. You use the account group to determine

 which fields are ready to accept input and which fields require entries when master records are created
and changed

 whether the account is a one-time account

 whether the data retention levels "sub-range" and/or "plant" are allowed for a vendor master record

Account groups allow you to group together accounts according to the above criteria. You define the account
number interval and the number assignment type using number ranges.
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT

7.2 Vendor account Number Range Assignment

Node: Define Vendor Account Number Range Assignment

Transaction Code/Menu Path: SPRO > Logistics General > Business Partner > Vendors > Control
> Define Number Ranges for Vendor Master Records
Client Dependency: Transportable
Description: Define Number Ranges for Vendor Master Records

In this step, you define the number intervals of the number ranges for vendor master records.

When a vendor master record is created, a unique number identifying the master record is assigned. The number
comes from the number range provided for the account group.

There are two ways in which numbers can be assigned:

 Internal number assignment

Here the SAP R/3 System automatically assigns a consecutive number from the number range defined.
 CONFIGURATION DOCUMENT
 External number assignment

Here you specify a number from the external number range.

CONFIGURATION DOCUMENT
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
8 Output Form Assignment
8.1 PO Message Type Form Assignment
Node: Message Type
Transaction Code/Menu Path: SPRO > Materials mangement > Messages > Output Control >
Message Types > Define Message types for PO
Client Dependency: Transportable
Description: PO Message Type Form Assignment
CONFIGURATION DOCUMENT
CONFIGURATION DOCUMENT
CONFIGURATION DOCUMENT
 CONFIGURATION DOCUMENT
9 STO-MM Configuration for YO6 document Type

Node: Assign Delivery type & Checking rule

Transaction Code/Menu Path: SPRO > Materials mangement > Purchasing > Purchase Order >
Set up STO > Assign Delivery type & Checking rule
Client Dependency: Transportable
Description: YO6 Document Type

In this step, you specify whether an SD delivery is to be created in the case of a PO with a certain combination of
supplying plant and document type. You can also specify which delivery type is to be used.
The delivery type in Sales and Distribution (SD) determines how a delivery is handled. In the standard system, the
delivery type 'NL' is used for stock transfers between plants of same company code.
 CONFIGURATION DOCUMENT

9.1 STO Schema Determination

Node: Define Schema Determination

Transaction Code/Menu Path: SPRO > Materials Management > Purchasing > Conditions>
Define Price Determination Process
Client Dependency: Transportable
Description: Define Schema Determination
CONFIGURATION DOCUMENT