Master Data

Master data forms the basis of sales and distribution processing. Remember that precisely
maintained and classified master data considerably simplifies and accelerates the operative
processing in daily business. A large amount of data is copied from the master records during
business transaction processing.

Before creating master records, check which employee subgroup should maintain the master
data in each case. Note that the master data is also used by other modules, such as the FI and
MM modules, as well as CO and PP, depending on the degree of integration. You should
therefore compare the areas of responsibility.

Note

Make certain to complete settings for most of the master data in the 'Logistics general' chapter.
This includes all of the material master and most of the customer master.

In this process you make the following settings:

 SD data from the customer master

 Control product proposal

In addition to the above, you can include condition records, tax records and texts for master
data. Controls for these records are integrated in the sections "Pricing", "Tax determination"
and "Text determination" found under Basic Functions.

Requirements

Before making the master data configurations, you must have completely defined the
organizational structures.

See the following sections for further information:

 "Organization" --> "Logistics" --> "Sales and distribution"

 "Organization" --> "Assignment" --> "Sales and distribution"

 "Organization" --> "Check" --> "Sales and distribution"

Define Common Distribution Channels

You can use this menu item to define distribution channels which have common master data.
The allocation is valid within a sales organization.
Example

You can, for example, create customer master data for distribution channel "01" and define it
so that it is valid for distribution channels "02" and "03".

Note

The master data shared by several distribution channels applies to conditions and customer and
material master data.

This helps you minimize the cost of creating and maintaining the master data.

You can also update statistics for each distribution channel and division without creating the
master data for the different sub-areas of the organization.

Activities

Define the distribution channel from which master data is to be copied into other distribution
channels

Define Common Divisions

In this step, you define the divisions that common master data should apply to. The definition is
valid within each sales organization.

Example

You can determine, for example, that the conditions which are valid in division "01" also apply
to divisions "05" and "06".

Note

The common master data across various divisions refer to the conditions and the customer
master data.

You thus minimize the effort of entering and managing master data.

In addition, you can extrapolate your own statistics per division without having to create master
data in the different organizational subareas.

Action

For the divisions, define from which other division the master data should be copied

Business Partners
In this section, you make settings in the SAP system regarding master records for business
partners.

In the SAP system, a business partner could be:

 a customer

 a contact person

 a vendor

 an employee in your company (e.g. sales personnel)

You use partner functions to distinguish between the various partners. You can use account
groups to distinguish further between customers. The SAP standard system contains various
partner functions for customers such as sold-to party, ship-to party, payer, etc.

Note

In this section, make certain that you only make those settings for business partners related to
sales and distribution. General controls for business partners is covered in the 'Logistics general'
chapter.

Customers

The SAP System manages customer data in master records.

You can store information relevant to both master data management and transaction
processing in the configuration menu. This includes the following:

 Technical parameters (e.g. assigning customer numbers)

 Classification criteria (e.g. customer group and sales areas)

 Parameters for individual business transaction (e.g. terms of delivery, terms of

payment.)

In the standard SAP System, you can distinguish between the following partner functions for
customers:

 Sold-to party

 Ship-to party

 Payer
  Bill-to party

Note

If you already have or are planning to install the FI module, the accounting aspects of customer
management and the maintenance responsibilities should be coordinated by FI and SD together

Sales

In this menu option, you define various customer attributes which represent classification
profiles and allocations to market segments. You use these customer attributes mainly for
statistical purposes in sales and distribution. They are not used for control.

The SAP System copies the attributes from the master records into the sales documents.

Shipping

In the following menu options, you define various customer attributes. These represent
classification profiles and allocations which influence or control processing in sales and
shipping.

The SAP System checks these attributes during master data maintenance and transfers them
from the master records into the sales and distribution documents.

Billing Document

In the following menu options, you define various customer attributes. These are classification
profiles and allocations which influence billing processing.

The SAP System checks these attributes during master data maintenance and copies them from
the master records into the sales and distribution documents.

Define Customer Groups

In this menu option, you define the customer groups to which a customer can belong.

You specify the customer group for sales data in the customer master record for each sales
area.

The SAP System copies this specification automatically into the sales documents at header and
item level. Here, you will find the customer group on the detail screen for general business
data.

Actions
 1. Specify an alphanumeric key which can have up to 2 characters and a description for
the customer groups.
2. Make sure that the customer groups are entered in the customer master records.

Define Delivery Priorities

You define delivery priorities in this menu option. You can use them to control the delivery of
sales orders or order items and therefore give priority to individual customers.

To do this, select the sales orders due for shipping within shipping processing with the help of
delivery priority. Delivery priority defines the sequence when deliveries are created
automatically (for example, for scarce goods). Specify the delivery priority of a customer in the
shipping data of the customer master data for each sales area.

From the customer master record, the SAP System copies the specification automatically into
the shipping data of an item in the sales document. And from there, it is copied into the header
of the delivery.

Note

If there are several sales departments in your company, you should define clear rules for
handling delivery priorities.

Default settings

In the standard SAP R/3 System, number 1 represents the highest delivery priority. During the
selection, delivery items with priority 1 are proposed first.

Actions

1. Check whether delivery priorities are used in your shipping department, and if so,
which ones. Define the kind of delivery priorities.
2. Specify a number for the delivery priorities between 1 and 99. Enter a description.
3. Make sure that the delivery priorities are maintained in the customer master records

Define Goods Receiving Hours

In this menu option, you define the possible goods receiving hours of your customers. With this
function, you can plan the shipping activities so that the deliveries arrive by the desired
deadline in the right city at the right time.

The goods receiving hours are copied by the SAP System from the customer master record into
the delivery header according to the unloading point and the delivery date.
Actions

1. Check which goods receiving hours apply to your customers.

2. Specify an alphanumeric key which can have up to 3 characters and a description for
the various goods receiving hours.
3. Maintain the goods receiving hours for each day.
4. Make sure that the key of goods receiving hours is entered in the customer master
records for the individual unloading points. You can also maintain the goods receiving
hours for each day manually

Define Billing Schedule

In this step, you define possible billing dates. To do this, store the billing dates in a separate
calendar.

Use the general calendar function to create a calendar in which work days are interpreted as
billing days for the billing calendar.

To define when a customer receives which billing documents, enter the calendar containing the
billing schedules in the master record of the payer

The SAP system copies this specification automatically into the header of SD documents.

Example

If you create a calendar containing only the 15th and 30th of a month as workdays and if you
specify this calendar for the billing schedules of a customer, billing is carried out on precisely
these dates. If you edit the billing due list of a customer for these dates, the SAP system
automatically selects the 15th or the 30th of a month as a billing date.

Actions

1. Check which billing arrangements were agreed with your customers.

2. Define the billing schedules in separate calendars.
3. Make sure that the number of the calendar is entered in the customer master records
of the customers involved.

Transport

Changes to calendar data are not automatically recorded in a correction request.

To transport the calendar data to other systems, use the Transport function in the initial
maintenance screen.
Be careful not to transport individual holidays or calendars, rather only the calendar data in its
entirety. All holidays, and holiday and plant calendars existing in the target system will be
deleted.

Define Terms Of Payment

In this menu option, you define the terms of payment for the customer master records required
for sales and distribution. Specify the terms of payment in the customer master records. From
there, the SAP System automatically copies them into the sales documents at header and item
level.

Depending on the item category, the terms of payment can differ at header and item level (see
the section "Define item categories for sales documents").

Aspects of accounting such as cash discount periods, cash discount rates and due date for net
payment in the invoice are defined and managed in financial accounting (module FI) (see FI
section "Define terms of payment").

Using the defined cash discount rate, the SAP System determines the corresponding cash
discount amount in pricing for SD documents.

Here, you can also store short texts for the terms of payment which are relevant for sales and
distribution. You can then print these short texts on the billing documents.

Bear in mind that the short text for terms of payment in quotations and order confirmations
will only be sent by EDI if the day limit is blank. In billing documents the short text will also be
sent by EDI if the day limit is not blank.

Note

You can agree on terms of payment with the customer in the SD module separately for each
sales area. These agreements may deviate from what is defined in the FI module. The sales area
terms of payment are included in a billing document and are transferred to Accounting where
they may be overwritten. Considering this, you should work together with Financial Accounting
(the FI module) to decide how to maintain terms of payment.

Actions

1. Specify an alphanumeric key with up to four characters for the terms of payment.
2. Enter the explanation as a description.
3. Make sure that the key of the terms of payment is entered in the customer master
records.

Define Incoterms
You define the Incotermsin this menu option. You specify the Incoterms in the customer master
record.

From the customer master records, the SAP System copies the Incoterms automatically into the
sales and distribution documents.

Note

In pricing, you can use the Incoterms to determine freight charges.

Actions

1. Specify an alphanumeric key which can have up to 3 characters and the description
for the Incoterms.
2. If you want a location in the master records to be mandatory, you have to set the
corresponding indicator and also specify part 2 of the Incoterms during master record
maintenance.
3. Make sure that the key of the Incoterms is entered in the customer master records

Item Proposal

In this menu option, you define the defaults for controlling item proposals. These defaults
include technical parameters, such as assignment to a number range and numbering of items.

Item proposals are stored independently of customers. If a customer frequently buys the same
product pallet, you can specify the item proposal number in the customer master record.

The materials of an item proposal can be proposed by the SAP System as an entry tool during
order processing. You can then:

 Copy the materials as they are

 Change the specifications and only copy some materials or partial quantity

Requirements

You can only include the products in a product proposal for which you created a material
master record.

Define Item Proposal Types

In this IMG activity, you define item proposal types. Item proposals are technically stored as
sales documents. They are controlled by item proposal types which you define as sales
document types. You take over an item proposal by copying it into a sales document.
For information on the defaults concerning a sales document type, see the section "Define
sales document types".

SAP Recommendation

If you define your own item proposal types, you should choose keys which start with the letter
Z. SAP reserves these name conventions in the standard system.

Default settings

In the standard SAP R/3 System, the item proposal type "SM" is defined, which fulfils the
requirements of normal processing for business transactions.

Actions

1. Check to what extent you can adopt the defaults for the item proposal types
contained in the standard SAP R/3 System.
2. Adapt an existing item proposal type to your requirements.
3. Create a new item proposal type, if necessary.

Define Number Ranges for Item Proposals

In this IMG activity, you define the number intervals of the number ranges for item proposals.

When creating an item proposal, a unique number identifying the product proposal is assigned
either internally or externally. The number comes from the number range provided for the item
proposal type.

For the type of number assignment, there are two possibilities:

 Internal number assignment

The SAP System automatically assigns a consecutive number from the defined number
range.

 External number assignment

You specify a number from the external number range.

Transport

You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After
the import, only the intervals you export are present. The number statuses are imported with
their values at the time of export.

Dependent tables are not transported or converted.

Actions

1. To define a number range you must create a new number interval:

o Specify an alphanumeric key with up to 2 characters.

o Specify the limits of the number interval. The individual number intervals may
not overlap. Thus, every number can occur only once.

o Flag the number range if it is provided for external number assignment.

2. Store the key of the number range for each item proposal type (see section "Define
item proposal types").

Basic Functions

In this IMG activity, the settings for the central functions in sales and distribution processing are
described in the. By central functions we mean the functions that are used in more than one
area in SD (for example, pricing in quotations, sales orders and billing documents).

Requirements

You must have defined the following:

 Organization and environment

 Master data control and maintenance

 Transaction control in sales, shipping and billing

 Dependencies for further SAP modules or external systems

 Specify the scope of checks and system responses

(Range of the credit limit check and the system response for an overrun in order
processing)
  Check the effects on the organization and define follow-up measures

Sales Documents

In the following menu options, you define the control data for the various document types in
sales. The control data refers to:

 Document types

 Item categories

 Schedule line categories

You also define the following for the sales documents in the subsequent menu options:

 Possible order reasons

 Possible reasons for rejection

 Various blocks

 Various order types

 Number ranges

Sales Document Header

The following sections contain information on controlling the different sales document types.
The sales document types represent the different business transactions in sales, such as inquiry
processing, quotation processing, consignment stock processing.

In addition to the definition and control of the sales document types themselves, you must also
take the following settings into account:

 language conversion

 number ranges

 screen sequence groups

 field selection per document header

 blocks per sales document type

  purchase order types

 reasons for rejection

 usage indicators

 Assignments to the various organizational units

Sales Document Item

Item categories together with the sales document types represent the different business
transactions in the SAP system. The item categories contained in the standard SAP system,
together with sales document types, represent the most common business transactions.

When defining and configuring item categories, take the following into account:

1. Define item categories

You are required to make a large number of controlling specifications (for example,
specifications for the transaction procedure) in the detail screen of the item category.
These control options are described in the section "Define item categories". Note that
the item categories are always closely linked to delivery types and billing types. You
should therefore also take into account the control options that are listed for deliveries
and billing documents. You can specify, for example for each item category, whether the
system is to perform pricing automatically at item level and whether the determined
value should be statistical.

2. Define additional functions at item level

When defining your own item categories or modifying the item categories to your
company-specific requirements, take the following settings into account:

o Group the item categories together in item category groups to make them easier
to handle.

o Specify which item category is proposed in the material master record.

o Specify the usage of the item category.

o Specify which item categories can be used with which document types.

o Specify the field selection for the item categories.

o If necessary, define reasons for rejection.

3. Settings for general sales and distribution functions

You must configure a number of general SD functions for item categories.

o Shipping

In shipping, you can specify the packing control and the picking relevancy, for
example, for each item category.

o Availability check and transfer of requirements

Depending on the item category and MRP type of the material, the system
determines the requirements type or the requirements class which primarily
controls the execution of the availability check and the transfer of requirements
(fine tuning is carried out at schedule line level).

o You can control output determination for each item category.

o You can control partner determination for each item category.

o You can control text determination for each item category.

o You can use your a separate incompletion procedure for each item category.

o For copying control, you can specify which item category can be copied from a
source document into a target document.

o When setting the statistics, you can assign a statistics group for each item
category.

Item categories are only complete defined and processed once you have taken these settings
into account

Schedule Lines

Together with the sales document types and item categories, the schedule line categories
contained in the standard SAP R/3 System cover the most common business transactions.

The SAP System can only copy items of a sales document to a delivery if they have schedule
lines. The control of the schedule lines depends on the schedule line category.

The following menu options describe how you define schedule line categories or adapt them to
the requirements of your organization. You must process the following points to do this:
  You must define schedule line categories or adapt them to your requirements.

 You must allocate the schedule line categories to the item categories depending on the
MRP type.

 If necessary, you must define schedule line types for scheduling agreements.

Define Sales Document Types

The sales document types represent the different business transactions in Sales and perform a
central controlling function for the entire sales order process. The definition and configuration
of sales document types can be divided into three parts:

1. Definition of the sales document types themselves (for example, standard order OR)
2. Definition of additional sales document functions (for example, number ranges)
3. Configurations for general sales and distribution functions (for example, pricing)

1. Defining sales document types

To define sales document types, you must make a large number of controlling
specifications which are listed below. Be careful that the sales document types are not
isolated but are always closely linked with delivery types and billing types. When
defining sales document types, you must therefore take settings into account which are
listed for deliveries and billing documents.
This connection is apparent in the following examples:

o You can allow a billing block to be proposed that must be checked by the billing
department for each sales document type (for example, in the case of returns).

o You can allow a certain delivery type to be proposed for a sales document type
during delivery processing.

o For each sales document type, you can configure the system to automatically
propose the current date as a delivery date.

2. Defining additional sales document functions

When defining your own sales document types or adjusting the standard document
types to your company-specific requirements, take the following settings into account in
addition to the actual sales document types:

o Language conversion

o Number ranges
 o Screen sequence groups

o Blocks for each sales document type

o Order types

o Reasons for rejection

o Usage indicator

o Assignments to the different organizational units

3. Setting general SD functions

You have to configure a number of general SD functions for sales document types.
You can, for example, perform a certain type of pricing for each sales document type. In
this case, process the sales document type and the pricing independently and allocate
the required document pricing procedure for pricing to the sales document type.
You can also propose your own output for each sales document type. To do this,
allocate your own output types and output determination procedures to the sales
document type.
You have finished defining a sales document type when youi have processed the
following general SD functions:

o Pricing

o Output determination

o Incompleteness

o Statistics

o Text determination

o Credit limit

o Shipping requirements

o Scheduling

General procedure when setting up sales document types

You have three options for configuring new sales document types:
 1. Change an existing sales document type.
2. Copy an existing sales document type and changee it according to your requirements.
3. Create a new sales document type.

Recommendation

For small changes, SAP recommends that you copy similar existing sales document types in the
standard SAP R/3 System and make the appropriate changes. Small changes might, for example,
be, a changed description, a different number range or a different increment for the numbering
of items. The name is to start with the letter Z as SAP keeps this range free in the standard
system. This procedure has the following advantages:

 All the specifications of the existing sales document type are copied. In particular, the
data concerning, for example, partner determination, pricing or document flow which
you would otherwise have to edit manually is copied.

 You can test your new sales document types in respect to the settings made without
having to edit the other settings.

 When copying sales document types, item categories and schedule line categories, the
SAP R/3 System automatically creates a log with the copied data. Using the log, you can
check whether all of the copied data applies to your sales document type or whether
you need to make changes.

Actions

1. If you need to make further changes, you should define new sales document types. To
do this, you enter an alphanumeric key with a maximum of four characters for a sales
document type and a textual description for the key.
2. Maintain the specifications on the detail screen according to your requirements.

Define Number Ranges For Sales Documents

In this menu option, you define the number intervals of the number ranges for sales
documents.

When creating a sales document, a unique number is assigned which identifies the sales
document. The number comes from the number range which is provided for the document
type.

There are two possible types of number assignment:

 Internal number assignment

 The SAP System automatically assigns a consecutive number from the defined number
range.

 External number assignment

You specify a number from the external number range.

Transport

You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.

All intervals for the selected number range object are deleted in the target system first. After
the import, only the intervals you export are present. The number statuses are imported with
their values at the time of export.

Dependent tables are not transported or converted.

Actions

1. To define a number range, you have to create a new number interval:

o Specify an alphanumeric key with up to 2 characters.

o Specify the limits of the number interval. The individual number intervals may
not overlap. Thus, every number can only occur once.

o Mark the number range if it is planned for external number assignment.

2. Afterwards, specify the key of the number range for the sales document types (see
the section "Define sales document types").

Assign Sales Area To Sales Document Types

In this menu option, you allocate the allowed order types to each sales area group.

You do not need to make any entries at all if all the sales order types are allowed for each of
your sales areas.

If you wish to check allowed sales document types, you must set up common sales areas. This
means you must define common sales organizations, common distribution channels and
common divisions. If, for example, you have define common divisions, then you must also
define common distribution channels and sales organizations.
Example 1 (simplest case):

Only the sales document type "standard order" (OR) should be allowed for a specific sales area
<0001/01/01> (that means: sales organization 0001, distribution channel 01, division 01). The
following activities are required for this:

1.1) Activity "group together sales organizations":

Sales org. Ref.sales org.

0001 0001

1.2) Activity "group together distribution channel":

Sales org. Distr.ch. Distr.ch. Doc.type

0001 01 01

1.3) Activity "group together divisions":

Sales org. Division Division Doc.type

0001 01 01

1.4) Activity "assign allowed order types to sales areas":

Ref.sales Distr.ch. Division Sales doc.type

0001 01 01 OR

Example 2:

The above settings should also be used for the sales area <0002/01/01>. In addition, the
following activities required:

2.1) Activity "group together sales organizations":

Sales org. Ref.sales org.

0002 0001

2.2) Activity "group together distribution channels":

Sales org. Distr.ch. Distr.ch. Doc.type

0002 01 01

2.3) Activity "group together divisions":

Sales org. Division Division Doc.type
0002 01 01

In the activity "assign allowed order types to sales areas", there is nothing else to do.

Example 3:

The above settings should also be used for the sales area <0002/01/02>. In addition, the
following setting is also required:

3.1) Activity "group together divisions":

Sales org. Division Division Doc.type

0002 02 01

Further activities are not necessary.

Requirement

The sales organizations, distribution channels and divisions which you wish to use for grouping
must be defined.

Activities

1. Enter your group sales organization in the sales organization field.

2. Set the respective group distribution channel in the distribution channel field.
3. Enter your group division in the division field.
4. Set the sales document type permitted for this group sales area during the order
entry in the sales document type field

Define Item Categories

In this menu option, you define item categories for sales documents. The item categories that
are contained in the standard SAP R/3 System together with the sales document types
represent the usual business transactions.

You have the following options for defining your own item categories:

 Copy an existing item category and change it according to your requirements.

 Create a new item category.

Recommendation
If you define your own item categories, the keys should begin with the letter Z since SAP keeps
this range free in the standard system and protects it from being overwritten during release
upgrades.

If you define your own item categories, you should copy similar item categories that are defined
by SAP and make the required changes there. In this case, all the specifications of the existing
item category are copied - even the assignment to the sales document types. In particular, the
data for example concerning partner determination, pricing or document flow which you do not
edit on the detail screen of the item category is also copied. Consequently, you can test the
new item category for the settings made without having to edit the other menu options.

When copying sales document types, item categories and schedule line categories, the SAP
system automatically creates a log with the copied data. Using the log, you can check whether
all of the copied data applies to your item category or whether you must make changes.

Note

If you create or copy a new item category that is to be used for a delivery, you must also define
a delivery item category with the same name. The SAP system automatically transfers the item
category that was found for the sales document item into the delivery item.

Activities

If you only need to make minor changes to the existing item categories (e.g. changed
description), then you change this as appropriate. Minor changes refer to parameters that have
no controlling character.

If you need to make further changes, define a new item category by copying a similar item
category supplied in the standard system and then change this according to your requirements.
In this way, you can for example define an item category for which a certain type of pricing is
carried out, or for which the data must not differ at header and item level but which otherwise
matches an existing item category.

If you want to create an item category, proceed as follows:

1. Enter an alphanumeric key with a maximum of four characters.

2. Maintain the respective specifications of the detail screen.
3. Also consider the additional functions on item category level and the item-specific
settings in the general sales and distribution functions

Define Item Category Groups

Using the item category group, you group together different material types for item category
determination from the SD view. For every material type, you can define a default item
category group which is proposed by the SAP System when you create a material master
record. For more information on setting default values please refer to the section "Define
material type defaults.

In the sales document, the system determines the item category from the item category group
of the material and from the sales document type and proposes this item category in the
document. You assign item categories to sales order types and item category groups elsewhere.
You can find further information on this in the section "Assign item categories".

Actions

If you define your own item category groups, the keys should start with the letter Z, since this
name convention is kept free in the standard SAP System for this purpose.

1. Check whether you can use the item category groups in the standard version.
2. If you want to create new item category groups, you must enter an alphanumeric key
with a maximum of 4 characters as well as a textual description.

Define Item Category Usage

In this menu option, you specify the item category usages which control the usage of an item.
Item category usage controls, for example, the system response if during document processing
an item does not refer to a material but to a text item. Item category usage can also be
maintained via the item categories (detail screen for item categories: Goto -> Item usage).

Default settings

In the standard SAP R/3 System, the following usages are defined:

 Batch split

 Text item

 Service item relevant for billing

 Service item not relevant for billing

Actions

1. Check first whether you can copy the usages in the standard system.
2. If necessary, create a new item category usage by entering an alphanumeric key with
a maximum of four characters and a description.

Assign Item Categories

In this menu option, you can specify which item categories the system proposes during
document processing for each sales document type and item category group. At the same time,
you can specify additional item categories with which the system default can be overwritten.
There is a maximum of three possible alternative item categories.

If, for example, you enter a material with the item category group NORM in a standard order,
the SAP System determines the allowed item category via the assignment of item categories to
sales document types and item category groups.

The system default and the allowed alternatives are always determined from the sales
document type and one or two further criteria. The system default depends on the following
criteria:

 sales document type

 item category group

 item category of the higher-level item

 item category usage

Note

The SAP System automatically copies the item category determined for a sales document item
to the delivery.

Recommendation

Depending on the initial situation you can start the assignment differently:

 When you define a new sales document type, you should specify the proposed and the
allowed item categories for the materials that are represented by the item category
group.

 When you define a new item category, you should specify for which sales document
types an item category is proposed or which item category is possible for the materials
represented by the item category group.

 When you define a new item category group, you are to enhance the assignment of
item categories to sales document types by this new item category group.

Actions

To define item category determination, proceed, for example, as follows:

 1. Choose the sales document type to which you want to assign item categories.
2. Then choose one of the item category groups.
3. Specify all the allowed item categories for the combination of sales document type
and item category group.
If you are dealing with a non-material item, you must specify the corresponding item
usage.
If it is a subitem, specify the item category of the higher-level item.
If it is an item category that is to be proposed in the sales document, you must indicate
the combination of item category, item category group and sales document type as a
default value.
4. If necessary, specify between one and a maximum of three item categories, with
which the system default can be manually overwritten during document processing

Define Schedule Line Categories

The SAP System can only copy those items of a sales document to a delivery for which schedule
lines exist. Control of the schedule lines depends on the schedule line category.

You have the following options for defining your own schedule line categories:

 change an existing schedule line category.

 copy an existing schedule line category and change it according to your requirements.

 create a new schedule line category.

In this menu option, you neither stipulate specifications for the requirement/planning types for
the availability check nor for incompleteness. You edit these functions later on in the respective
menu options. This means that the definition of a schedule line category is only completed once
you have also edited these menu options.

In this menu option, you must make or check the following specifications:

Schedule line category

The schedule line category is has an alphanumeric key with a maximum of two characters as
well as a textual description.

Business data

 Delivery block

When you define a delivery block for a schedule line category, this specification is
copied to the schedule line. The schedule line is then blocked for all delivery types that
 are allocated to this delivery block. Information on the assignment of delivery blocks to
delivery types can be found in the section "Define blocking reasons in Shipping".

 Movement type

Here, you specify a movement type for posting quantities and changes in value to
inventory accounting. The movement type is only relevant to items or schedule lines
which result in a stock movement. It is not relevant, for example, for:

o inquiry items

o quotation items

o order items without inventory management

Do not specify a movement type for goods issue for the schedule lines for returns items.
Instead, specify a goods movement for the return delivery, thus for goods receipt.

 Item relevant for delivery

Schedule lines for order items are relevant for delivery if a physical goods delivery is to
be made. In contrast to this, schedule lines for quotation items are not relevant for
delivery. You indicate the appropriate schedule line category here.

 Requirements

Transfer of requirements can be controlled at schedule line level. Transfer of

requirements is carried out for the transaction if you set the indicator. The indicator
corresponds to the settings for the transfer of requirements for each schedule line
category and can also be set there.

 Availability

The availability check can be controlled at schedule line level. An availability check is
carried out for the transaction, if you set the indicator. The indicator corresponds to the
settings for the availability check for each schedule line category and can also be set
there.

 Purchase order/purchase requisition

A purchase requisition can be automatically created for a schedule line by the SAP
System. For this to occur, you must enter the following data here:

o type of purchase order

 o type of purchase order item

o type of account assignment

o type of document category

At the moment, only purchase requisitions can be created automatically.

Transaction procedure

 Incompletion procedure

The incompletion procedure that you enter here, specifies which fields must be
completed by the user. A corresponding entry is created in the incompletion log for
fields that are not filled during document processing.

Recommendation

 If you define your own schedule line categories, the keys should start with the letter Z
since SAP leaves this range free in the standard system.

 If you define your own schedule line categories, you should copy similar schedule line
categories that are defined by SAP and make the appropriate changes.

In this case, all the specifications of the already existing schedule line category are
copied, including the allocation to the item categories. In particular, the data for
example concerning incompleteness, the availability check and document flow, which
you do not edit in this menu option, is copied. In this way, you can test your new
schedule line categories in respect to the settings that have been made without having
to edit the other menu options.

 When copying sales document types, item categories and schedule line categories, the
SAP System automatically creates a log with the copied data. Using the log, you can
check whether all the copied data applies to your schedule line category or whether you
must make changes.

Default settings

In the standrad SAP R/3 System, the key of the schedule line categories contains the following
information concerning its usage:

First character of the key usage

A inquiry
B quotation
C sales order
D returns
Second character of the key usage
T no inventory management, e.g. services
X no inventory management with goods issue
N no planning
P MRP
V consumption-based planning

Actions

1. Change the schedule line categories according to your requirements if you only need
to make minor changes to the existing schedule line categories. Minor changes are
parameters which have no controlling character. A minor change could be a changed
description.
Define new schedule line categories if you need to make further changes.
2. Maintain the detail screen according to your requirements.
You can, for example, allow the SAP System to create purchase requisitions
automatically for particular schedule line categories.

Assign Schedule Line Categories

In this menu option, you assign schedule line categories to item categories. This allocation of
schedule line categories is carried out depending on the MRP type that is specified in the
material master record for a material. At the same time, you can enter a maximum of three
schedule line categories with which the system default can be manually overwritten during
document processing.

Actions

1. Assign the schedule line categories to the item categories depending on the MRP
type. In this case, indicate the schedule line categories that are to be proposed during
document entry.
2. If necessary, specify schedule line categories with which the automatically
determined schedule line category can be overwritten in the document.

Maintain Copy Control for Sales Documents

In this menu option, you define control data for the document flow of sales documents.
You can specify for a particular sales document type, which document type is to be assigned to
copied reference documents, and which item categories or schedule line categories are to be
copied.

You must also make specifications for copying requirements and data transfer, as well as
quantity and value updates in document flow. This must be done for each copying procedure at
header, item and, if necessary, schedule line level on a detail screen.

Note

If you define new sales document types, item categories or schedule line categories by copying
existing ones, the SAP system automatically copies all specifications for the document flow. You
may want to check the copy controls for newly created sales document types, item categories
or schedule line categories.

Actions

1. Check the document flow defined in the standard SAP R/3 System.
2. Define to what extent you have to modify its specifications to meet your
requirements.
3. Define the document flow for sales documents with reference to sales document
types.
4. Define the document flow for sales documents with reference to billing types.

Note

Make sure to maintain copy control for the following areas:

Sales documents

Deliveries

Billing documents

If you cannot find an entry, check the copy controls in other chapters.

Complete overview of copy control:

In the chapter on sales, you can find copy controls for:

 Sales document by sales document

 Billing document by sales document

In the chapter on deliveries, you can find copy controls for:

 Sales document by delivery

In the chapter on billing, you can find copy controls for:

 Sales document by billing document

 Delivery by billing document

 Billing document by billing document



Basic Functions

In this IMG activity, the settings for the central functions in sales and distribution processing are
described in the. By central functions we mean the functions that are used in more than one
area in SD (for example, pricing in quotations, sales orders and billing documents).

Requirements

You must have defined the following:

 Organization and environment

 Master data control and maintenance

 Transaction control in sales, shipping and billing

 Dependencies for further SAP modules or external systems

 Specify the scope of checks and system responses

(Range of the credit limit check and the system response for an overrun in order
processing)

 Check the effects on the organization and define follow-up measures.

Pricing

The following sections describe how pricing is controlled. Before you set up new control
elements, you should check in how far the control elements defined in the standard version of
the SAP system meet your requirements.
The following aspects are of significance for controlling pricing

 Condition type

Using the condition types, you define which types of prices, discounts, and surcharges
exist in the SAP system. The condition types which are pre-defined in the standard SAP
system include:

o Customer-specific discount

o Freight charge

o Material surcharge

o Price list price

 Condition table

In the condition table, you specify the combination of fields for which you want to
create a condition record.
For example, you can create a condition record for a price which is dependent on:

o Sales organization

o Distribution channel

o Division

o Customer number

 Access sequence

The access sequence is a search strategy with which the SAP system searches for valid
condition records for each condition type during pricing. The access sequence refers to
the fields which are relevant for pricing using the condition tables contained in the
access sequence.
Using the access sequence, you can control that the SAP system first of all searches for a
customer-specific price and then for a price list price.

 Pricing procedure
 In the pricing procedure you specify the condition types which are to be used in pricing.
At the same time, you define the sequence in which the condition types are to be
brought into play.
Which pricing procedure is valid for a business transaction depends on the following
criteria:

o Customer

o Sales document type

o Sales area

You also need to take the following points into account:

 Pricing for a document item depends on its item category. You must make the
appropriate settings for all item categories for which pricing should be carried out.
Pricing is not activated, for example, for free of charge items.

 Also, check how the copying of pricing data is controlled in the SD documents (
document flow).

For example, you specify in the document flow how prices are copied from a sales order
into a billing document.

 In addition, you must define master data fields which are relevant for pricing.

For example, you must specify a price group for a customer if you want to use this price
group for pricing.

 Define the degree of responsibility your employees have for conditions.

 If the cost price is to be determined during pricing, you must classify the item categories
appropriately.

Note

You define pricing for each sales area. You can use sales area assignment to apply the same
pricing rules to more than one sales area. (see Section "Define common master data").

Transport interface
In the transport, all objects which were maintained in Customizing for controlling pricing are
transported. In the correction which is created for the transport, you can check the table
entries and delete any entries which are not to be transported.

Additional information

You will find further information on this subject in the SD "Guide to Pricing and Conditions".

Free Goods

In this IMG activity, you make settings for automatic free goods determination.

Taxes

In the following sections, define the defaults for tax calculation. In pricing the SAP System
automatically calculates the taxes.

The settings for tax determination should agree with those in Financial Accounting (FI module).

You only need tax records for a foreign country if you maintain business relationships with the
foreign country.

To do this, do the following:

 You have to define the valid tax types and the rules of tax calculation for each country
with which you have business contacts.

 You have to define regional codes (city code and county code) if you are using the SAP
System in the USA or Canada, for example.

 You have to allocate delivering plants for tax calculation.

 You have define tax relevancy for each tax type for customers and materials.

Note

In the standard SAP R/3 System, elements are predefined for tax calculation. Therefore, first
check to what extent the elements contained in the standard SAP R/3 System meet your
demands

 Account Assignment/Costing
 In this step, make settings for revenue account determination and assign cost centers
and dunning areas.
  Because the business area belongs to corporate structure, make any relevant
assignments to it in the chapter on corporate structure under sales and distribution.

Availability Check and Transfer of Requirements

Depending on the system configuration, the SAP System can check availability for every item in
a sales document or delivery. Furthermore, it creates MRP records and passes them on to
materials planning. The availbility check is carried out at plant level.

Control elements in Customizing

In addition to other settings, the following control elements are of particular signifiance in SD-
Customizing:

 In general, the requirements class determines the requirements classes for which the
availability check and/or transfer of requirements should be carried out. The global
settings at requirements class level can be differentiated at schedule line level.

 The checking group determines the standard replenishment lead time and (together
with the MRP group) the type of requirement records (e.g. individual records,
summarized records per day) to be created.

 Checking rule

The checking rule determines the scope of the availability check and whether or not the
replenishment lead time should be taken into account.

The MRP groups are defined in materials planning in PP Customizing.

 The system uses the MRP group to determine the relevant requirements type for a
transaction. The requirements type defines whether the transfer of requirements or
availability check should be carried out for the respective transaction. The MRP groups
must be defined in collaboration with SD.

 In Release 3.0, you can enter the strategy group directly into the material master record.
It is usually determined using the MRP group.

Note

The control of the check's scope and the type of requirements records are interdependent.
Specifications in the material master record

You make two particularly significant specifications in the material master record for the
availability check and transfer of requirements:

 Checking group (material master record: Sales/plant data or MRP 2): basically defines
whether the availability check should be carried out for a particular material and the
type of requirements record to be created.

 MRP group (material master record: MRP 1): the system uses this group to determine
the requirements type relevant for a transaction.

 Strategy group: is an alternative to determining requirements using the MRP group. You
can maintain this group directly in the material master record.

The following further control elements in the material master record can also influence the
result of the availability check:

 Planned delivery (MRP 1)

 GR processing time (MRP 1)

 Total replenishment lead time (MRP 2)

Further possibilities for controlling the availability check and transfer of requirements

The availability check and transfer of requirements can in principle be controlled independently
of one another.

When you create a sales document, the transfer of requirements and availability check can be
carried out independently. The way in which these are controlled is dependent on th
requirements class and schedule line category.

When you create a delivery, the availability check can only be carried out in combination with
the transfer of requirements. Requirements, however, can be transferred without the
availability check being carried out.

These control elements apply to sales documents and deliveries alike. The procedure and scope
of the check can, however, be controlled separately for sales documents and deliveries, so that
a different type of availability check is carried out in delivery processing as in sales order
processing, for example. In sales documents, you can block order quantity confirmation (for
certain delivery blocks), for instance.
Further literature
1. For a detailed description of the availability check and transfer of requirements from
the point of view of the user, see the SD Sales and SD Shipping manuals.

2. The PP Master Planning/MRP Guide describes the determination of the requirements

type.

3. For further information on the MRP group, see IMG step "Planning strategy" for
materials planning. The MRP groups are configured under the menu option " Master
data" in materials planning in Production. Requirements type determination is also to
be found here.

Delivery Scheduling and Transportation Scheduling

Shipping activities and transportation can be scheduled automatically in sales documents.

Picking/packing and loading, transportation scheduling and transportation can be planned and
optimized on the basis of the dates determined.

There are two different types of scheduling:

 Delivery scheduling

The SAP System takes into account the pick/pack time and loading time for a
transaction.
You define the type of delivery scheduling for each shipping point.

 Transportation scheduling

The SAP System takes into account the transit time and the transportation scheduling
time for a transaction.
You define the type of transportation scheduling on the basis of the route (see sections
"Route definition" and "Route determination").

You define for each sales document type whether delivery scheduling and/or transportation
scheduling should be carried out.

For the dates to be determined automatically on the basis of the requested delivery for an
order item, you must define both the times and what influences the determination of the date.

You need to carry out the following:

  Define for each sales document type whether scheduling is to be carried out and, if so,
which type.

 Define the indicators for scheduling for each shipping point.

 Define:

o Pick/pack times

o Loading times

o Transit times

o Transportation scheduling times

Output Control

Outputs are an important media for communicating with business partners or with your own
employees in sales processing.

Sales and distribution output can be sent both electronically and by mail. Output control which
is dependent on various criteria allows output to be processed and sent subject to certain
conditions and restrictions.

You have to define the following:

 Rules of output determination

 Print parameters

 When the sending of output is to be initiated

 Material Determination
 In this IMG activity, you define the rules according to which material determination
functions.
 When you create documents, material determination enables you to find certain
materials automatically using a key already stored in the system rather than using the
material number. You do not need to create a material master record for the key
entered in the SD document and which you use to find a material. The assignment of
materials is carried out in master records for material determination. Here, various keys
can be stored for the same material in the system. The key entered can, for example, be
a customer-specific material number or the International Article Number (IAN).
 With material determination, the material entered is replaced automatically by the
material found during document creation. This material determination is dependent on
the sales document and can, for example, be used in a promotion when a product is
 only to be sold with special packaging. During order processing, the system can then
automatically exchange the material with the normal packaging for the material with
the special packaging for a given period of time.

Dynamic Product Proposal

A product proposal is a list of products for a specific customer that is automatically proposed
during sales document processing. You can decide for yourself which materials should be
displayed as product proposals in the sales document. You can also determine the sequence in
which the materials appear in the product proposal.

During sales document processing, the system displays a product proposal in the item overview
according to the customer and the business transaction. It displays the material number,
material description, and historical order quantites in the sales unit last used. To use a material
again, you just have to copy it. The system does not run the standard checks (pricing,
availability, incompletion, material determination, free goods determination and so on) until
you have entered the order quantities.

The product proposal is both an entry help and an aid to sales support and promotions. It is
particularly useful in Telesales, where the employee automatically receives a display of all the
materials that are of interest to a particular customer. This helps them to provide appropriate
advice to the customer quickly and easily. The sales document history enables you to analyse
the purchasing behaviour of a customer and recognize early on if it changes, for instance, when
the customer suddenly stops ordering a product.

The product proposal differs to cross-selling in that it is dependent on the customer and sales
area, and is displayed in the sales document as soon as you have entered a customer. Cross-
selling, on the other hand, is triggered by a material. In other words, the system proposes cross-
selling materials according to the material or a characteristic of the material you have entered.

You can determine the product proposal from different data sources:

 Order history

 Listed materials

 Excluded materials

 Item proposal

 Customer-material info records

 Customer-specific data sources

You can combine materials from these data sources to create a product proposal. The system
then accesses the data sources either online or in the background.

To define a product proposal for sales document processing, you must carry out the following
activities in Customizing:

 Define customer procedure for product proposal

 Define document procedure for product proposal

 Assign document procedure for product proposal to order types

 Maintain table of origin for product proposal

 Define product proposal procedure and determine access sequences

 Maintain procedure determination (in background) for product proposal

 Maintain procedure determination (online) for product proposal

The product proposal procedure determines how the system displays the product proposal in
the sales document. For instance, if the system has accessed the order history, it determines
how many columns should be displayed in the sales document, in which period intervals
thehistoric order quantities should be displayed (for instance, day, week, or month), and most
importantly, the sequence in which the system should access the data sources (for example,
order history, listing, exclusion).

The product proposal procedure depends on the:

 Customer determination procedure

The customer procedure determines which product proposal procedure the system
automatically uses when you create a sales document for a particular customer.
It is specified in the customer master record per sales area.

 Document determination procedure

The document procedure determines which product proposal procedure the system
automatically uses for a certain document type. The document procedure is stored as a
key in the header for the sales document type.

If you use online processing, the product proposal procedure is determined according to the
customer and document determination procedures.

If you use background processing, the product proposal procedure is determined according to
the sales area in the customer master and the customer determination procedure. It does not
use the document determination procedure because the document type is not recognized in
background processing.

Cross Selling

In this stage, make settings for Cross-Selling.

Listing/Exclusion

In this menu option, you define rules according to which material listing or material exclusion
functions in sales processing. With material listing or exclusion you can control which materials
can be sold to each customer. Material listing lists which materials a customer can buy.
Material exclusion lists which materials a customer cannot buy.

Example

A material listing is created for a customer. The customer can only buy the materials contained
in the list. The system does not allow any materials to be entered if they are not contained in
the material listing.

If no records exist for material listing, the sold-to party, for example, can in principle buy the
same materials as the payer. However, if there is a material listing record specific to the sold-to
party, the sold-to party can only buy the materials permitted in the list. These materials do not
have to be identical to those which the payer can buy.

Material listing and material exclusion are controlled using the condition technique which is
described in detail in the examples for pricing and output determination. Further information
on the condition technique can also be found in the manual "SD Pricing and Conditions".

The following elements of the condition technique work together to control material listing and
exclusion:

 The condition table defines the field combination required in a material listing or
material exclusion master record.

 The access sequence is a search strategy with which the system searches for valid
condition records for each condition type. The access sequence refers to the fields for
material listing or material exclusion via the conditions tables contained in the access
sequence. Access sequences A001 for material listing and B001 for material exclusion
are defined in the standard R/3 System.

 The type defines how material listing or exclusion is carried out. Types A001 for material
listing and B001 for material exclusion are defined in the standard R/3 System.
  The procedures define the condition types to be used in material listing and material
exclusion. Procedures A00001 for material listing and B00001 for material exclusion are
defined in the standard R/3 System. The master records for condition types A001 and
B001 only are therefore checked for material listing or exclusion.

Note

In a delivery created with reference to an order, material listing or material exclusion are
carried out on the basis of the underlying sales document type. Material listing or exclusion are
carried out for new items in the delivery if they were activated for the underlying sales
document type. Material listing or exclusion are not carried out for items copied from the sales
order. You must assign an appropriate procedure to the sales document type DL in Customizing
for material listing or exclusion to be carried out in deliveries created without reference to a
sales order (LO).

Actions

Check whether you can adopt the elements of material listing or

exclusion defined in the standard R/3 System. If you need to make modifications, carry out the
following steps:

1. Define the conditions table or copy the existing table and make changes as you
require.

2. If there are not enough fields available, you can extend the list of permitted fields for
material listing and material exclusion using the field catalog.

Bear in mind that fields which you wish to create have to be included in the
communication tables KOMKG, KOMPG or KOMGG.

Notes

For a description of how data is provided in these fields via user exits, see Customizing, Sales
and distribution -> System Modification -> User exits -> User exits in Sales -> User exits in sales
document processing.

3. Define the access sequence and assign a condition table to it.

4. Define the type of material listing or exclusion and assign an access sequence to
them.

5. Define the procedures and assign appropriate types to them.

 6. Assign the procedures for the listing or exclusion to sales document types

Partner Determination

In the following menu options, you define the rules according to which automatic partner
determination is to be carried out.

When creating a customer master record, the SAP System proposes the allowed partner
functions to be maintained. According to the rules defined here, the partners are adopted from
the customer master records of the sold-to parties into the sales and distribution documents.

You have to edit the following points for the function "Partner determination":

 Partner function

You define with the help of the partner function which functions exist for the partners (
customers, vendors, employees, and so on) in your system.

 Partners allowed for each account group

You allocate the permitted partner functions to every account group customer.

 Function conversion

You can define the key of the partner functions according to the language.

 Partner object

Partners are possible in the customer master record and the so-called partner objects in
the sales and distribution documents. Select a partner object and define the rules for
partner determination for this object.

 Partner determination procedures

You define partner determination procedures which contain all the allowed partner
functions for every partner object.

 Procedure allocation

You allocate each partner determination procedure to an actual partner object using a
key, for example, to an account group customer or a sales document type.
Partners are contained both in the customer master records and in the sales and distribution
documents. You define partner determination for each of these objects individually.

The following partner objects exist:

 customer master record

 sales document

o header

o item

 delivery

o header

 billing document

o header

o item

 sales activity

After defining the partner functions, select one partner object after the other and define the
partner determination procedures for the selected object.

Only when you have checked and, if necessary, changed the partner determination for all the
partner objects is the function "Partner determination" completed.

Note on tranport interface

In the transport, all objects maintained for partner determination are transported. In the
correction which is created for the transport, you can check the table entries and delete the
entries which are not to be transported.

Text Control

In this IMG activity, you define the rules for text determination. You must carry out the
following steps:

 Select a text object and define the rules for text determination for this object. Text
objects are, for example, the sales texts in the customer master record or the sales
document header.
  Define the permitted text types for every text object. If the text types contained in the
standard SAP R/3 System are not sufficient, create new ones.

 Define the access sequences. This way, you define how the SAP System should
determine the texts for a text type.

 Group the text types together in text determination procedures. The SAP System then
proposes the text types from the procedure when you maintain a customer master
record or a sales & distribution document. The search for the respective text is carried
out using the access sequence which you have stored for each text type in the
procedure.

 Allocate the text determination procedures so that a procedure applies to the following
criteria in each case:

o account group customer

o sales & distribution document type

o item category

The following text objects exist:

 customer

o central texts

o accounting texts

o texts concerning the contact persons

o sales and distribution texts

 sales document

o header texts

o item texts

 delivery

o header texts

o item texts
  billing document

o header texts

o item texts

 CAS

Select one text object after another and define text types, access sequences, and text
determination procedures for the selected text object.

Only when you have checked the text determination for all text objects and made any
necessary changes, is the function "Text determination" completed.

Transport interface

In the transport, all objects which were maintained in Customizing for controlling text
determination are transported. In the correction which is created for the transport, you can
check the table entries and delete any entries which are not to be transported.

Log of Incomplete Items

In the following IMG activities, you define when a sales document or sales activity should be
regarded as incomplete and how the system should respond when you create a document.

The system can make an entry in the incompletion log for the following data:

 Sales document header data

 Sales document item data

 Sales document schedule line data

 Sales activity data

 Partner data in sales documents, deliveries and sales activities

 Delivery header data

 Delivery item data

Note
Note that different procedures can be assigned to the partners in the documents if they have
different partner functions. However, the required data for a partner function is relevant for all
procedures.

You can generate entries for texts and prices in the incompletion log although there may not be
a procedure defined for this:

The system only makes an entry for texts if it is marked as obligatory in the text determination
settings.

Entries for pricing can be made in the sales document if the PRSOK field in the incompletion
procedure for sales items is copied and set to blank or zero in pricing. This is used for obligatory
prices that are not available in the document, or for errors that occur when converting
quantities and foreign currencies.

The CEPOK field in the incompletion procedure for sales items allows you to make an entry in
the incompletion log if the price deviates from the expected customer price too much.

Special features in the incompletion log for shipping processing

Dynamically determined document characteristics:

During document processing, the system determines field entries in the procedure with the
prefix (table name) 'V50UC'. Unlike other cases, these entries do not correspond to a missing
entry in a database table but, similar to pricing, indicate complex document characteristics. This
kind of incompletion cannot necessarily be processed by filling an empty field. For example, the
log may indicate that the batches of an item have not been assigned completely, so you may
have to change the main item quantities or the split quantities.

Follow-up activities that you can control:

You can use the incompletion log to control follow-up activities such as picking, goods
movement (posting goods issue), and packing (deliveries only).

If the incompletion log determines for a delivery that the follow-up function 'delivery' is not
possible, you cannot save the document. This delivery is not included in collective processing
and the collective processing log contains information to that effect.

Example

For example, the standard system checks whether the "purchase order number" field at header
level in an order is complete.
This field is used in the incompletion procedure for orders. The procedure is assigned to all
those sales document types which need a purchase order number and which therefore should
be checked for completion.

If you do not enter any data in this field when processing a sales document you will receive a
warning.

The order can be saved but its status group means that it will be blocked for all subsequent
functions. Once you have entered the purchase order number in the document, the block will
be lifted.

The relevant specifications for warnings and blocks are defined in the purchase order number
field in the incompletion procedure.

Note on transport interface

In the transport, all objects which were maintained in Customizing for controlling incomplete
documents are transported. In the correction which is created for the transport, you can check
the transport orders in the tables and delete the entries which should not be transported

 Credit Management/Risk Management

 The payment guarantee for the value to be billed plays a central role within Sales. Credit
management effectively allows you to minimise the credit risk.
 Risk management for receivables is another useful tool for setting a payment guarantee
to cover the credit risk.
 Note
 The functionality of the simple credit limit check is covered fully by credit management
which is available from Release 2.2. In the simple credit check you can only set one
system reaction (warning, error, delivery block) when the credit limit is exceeded. Other
functions in credit management are not available.
 It is planned that credit management should be used exclusively at a later date.

Serial Numbers

In this section, you can make settings for serial number management.

Serial number management allows you to distinguish between individual items of a material
that are managed with a single material number.

Example

Company X produces three different types of solar collectors:

 Type A
  Type B

 Type C

There is a material master record for each type in the system. For control purposes, the
company wants to know which customer received which collector type, and which serial
number(s) of the collector type were supplied to the customer, when the individual solar
collectors were delivered.

It is therefore necessary to assign a serial number to the customer delivery in addition to the
material number.

A serial number master record is created with the assignment of the serial number. You can
maintain data fields specific to the serial number in the master record.

At a later date, it may be necessary to enter equipment master records for materials that have
already been serialized and delivered to customers, for example, if the producer of the solar
collectors also has to perform maintenance activities for the customers and therefore wants to
use all the functions available in the equipment master record for a serialized material.

In order to keep this option open at any time, you must define a number range for serial
numbers. The numbers assigned from this number range are not the serial numbers but
reserved keys that stand for the combination of material number and serial number and the
equipment number that may possibly be assigned.

You can also define one or more serial number profiles.

The serial number profile defines how and under which conditions a serial number is assigned
for a material.

Note

A material can only be assigned serial numbers after the required serial number profile has
been entered in the material master for a specific plant.

 Routes
 In this step, you make settings for routes.
 Define Common Distribution Channels
 You can use this menu item to define distribution channels which have common master
data. The allocation is valid within a sales organization.
 Example
 You can, for example, create customer master data for distribution channel "01" and
define it so that it is valid for distribution channels "02" and "03".
 Note
  The master data shared by several distribution channels applies to conditions and
customer and material master data.
 This helps you minimize the cost of creating and maintaining the master data.
 You can also update statistics for each distribution channel and division without creating
the master data for the different sub-areas of the organization.
 Activities
 Define the distribution channel from which master data is to be copied into other
distribution channels.
 Define Common Divisions
 In this step, you define the divisions that common master data should apply to. The
definition is valid within each sales organization.
 Example
 You can determine, for example, that the conditions which are valid in division "01" also
apply to divisions "05" and "06".
 Note
 The common master data across various divisions refer to the conditions and the
customer master data.
 You thus minimize the effort of entering and managing master data.
 In addition, you can extrapolate your own statistics per division without having to create
master data in the different organizational subareas.
 Action
 For the divisions, define from which other division the master data should be copied.

Business Partners

In this section, you make settings in the SAP system regarding master records for business
partners.

In the SAP system, a business partner could be:

 a customer

 a contact person

 a vendor

 an employee in your company (e.g. sales personnel)

You use partner functions to distinguish between the various partners. You can use account
groups to distinguish further between customers. The SAP standard system contains various
partner functions for customers such as sold-to party, ship-to party, payer, etc.

Note
In this section, make certain that you only make those settings for business partners related to
sales and distribution. General controls for business partners is covered in the 'Logistics general'
chapter.

Customers

The SAP System manages customer data in master records.

You can store information relevant to both master data management and transaction
processing in the configuration menu. This includes the following:

 Technical parameters (e.g. assigning customer numbers)

 Classification criteria (e.g. customer group and sales areas)

 Parameters for individual business transaction (e.g. terms of delivery, terms of

payment.)

In the standard SAP System, you can distinguish between the following partner functions for
customers:

 Sold-to party

 Ship-to party

 Payer

 Bill-to party

Note

If you already have or are planning to install the FI module, the accounting aspects of customer
management and the maintenance responsibilities should be coordinated by FI and SD together

Contact Person

You can store different pieces of information to describe the contact persons at the customer
location in more detail. You specify the contact persons at the customer location when you
maintain the customer master record. You also enter data on a contact person, such as the
name and the address, in the customer master record.

You define contact persons in the customer master record on a general level, that is,
independently of organizational units.
You can allocate a contact person to a sales area. To do this, enter the contact person as a
partner functionwith the following data:

 Partner function AP

 Internal number assigned to the contact person

If you enter a sales document in this sales area, the contact person is automatically proposed
by the SAP System. You can still change this specification manually on the partner screen in the
sales document.

Note

Defining contact persons is optional. If you do not want to use this function, you do not have to
process any entries at this point in the configuration menu.

Item Proposal

In this menu option, you define the defaults for controlling item proposals. These defaults
include technical parameters, such as assignment to a number range and numbering of items.

Item proposals are stored independently of customers. If a customer frequently buys the same
product pallet, you can specify the item proposal number in the customer master record.

The materials of an item proposal can be proposed by the SAP System as an entry tool during
order processing. You can then:

 Copy the materials as they are

 Change the specifications and only copy some materials or partial quantity

Requirements

You can only include the products in a product proposal for which you created a material
master record.

Define Item Proposal Types

In this IMG activity, you define item proposal types. Item proposals are technically stored as
sales documents. They are controlled by item proposal types which you define as sales
document types. You take over an item proposal by copying it into a sales document.

For information on the defaults concerning a sales document type, see the section "Define
sales document types".
SAP Recommendation

If you define your own item proposal types, you should choose keys which start with the letter
Z. SAP reserves these name conventions in the standard system.

Default settings

In the standard SAP R/3 System, the item proposal type "SM" is defined, which fulfils the
requirements of normal processing for business transactions.

Actions

1. Check to what extent you can adopt the defaults for the item proposal types
contained in the standard SAP R/3 System.

2. Adapt an existing item proposal type to your requirements.

3. Create a new item proposal type, if necessary.

Define Number Ranges for Item Proposals

In this IMG activity, you define the number intervals of the number ranges for item proposals.

When creating an item proposal, a unique number identifying the product proposal is assigned
either internally or externally. The number comes from the number range provided for the item
proposal type.

For the type of number assignment, there are two possibilities:

 Internal number assignment

The SAP System automatically assigns a consecutive number from the defined number
range.

 External number assignment

You specify a number from the external number range.

Transport

You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After
the import, only the intervals you export are present. The number statuses are imported with
their values at the time of export.

Dependent tables are not transported or converted.

Actions

1. To define a number range you must create a new number interval:

o Specify an alphanumeric key with up to 2 characters.

o Specify the limits of the number interval. The individual number intervals may
not overlap. Thus, every number can occur only once.

o Flag the number range if it is provided for external number assignment.

2. Store the key of the number range for each item proposal type (see section "Define
item proposal types").

 Basic Shipping Functions

 In this step, you specify the shipping point and route determinations which act as an
important base for the whole of shipping processing

Configure Global Shipping Data

Here you can set shipping data on a global basis.

This data includes:

 Type of full delivery check: Here you define whether, a maximum of one delivery may be
created in collective processing (delivery due list) from a sales order or whether several
deliveries per order are allowed.

 Adopt confirmed order quantity: This controls whether the entire quantity or only the
quantity confirmed in the full delivery check should be adopted from an order item
schedule line. This does not affect the delivery date.

 Goods movement posting with overpicking: This makes a goods issue posting of the
delivery quantity possible, even if the picked quantity is greater than the delivery
quantity (the situation in overpicking can also be detected using the error log).

Shipping Point and Goods Receiving Point Determination

For each item, the SAP System determines the shipping point when processing a sales
document. You can change the shipping point in the sales document manually. Shipping points
are maintained in Customizing in Section "Create shipping point".

The specification of a shipping point is required for creating a delivery for an order item.

The automatic determination of the shipping point depends on the following criteria:

 delivering plant of the item

The delivering plant is automatically determined by the SAP System in the sales
document item, on the basis of the ship-to party and the material. You can manually
change the delivering plant of an item.

 Shipping conditions of the sold-to party or the sales document type

 Loading group of the material

In the following menu options, you define the shipping conditions, the loading groups and the
rules for the shipping point determination. In addition, you can specify a shipping condition for
particular sales document types

Define Shipping Conditions

You define shipping conditions in this step. You enter the shipping conditions defined here in
the customer master record in the sales data for each sales area. The SAP system copies the
shipping condition into the sales document header.

Note

You can also determine a shipping condition for each sales document type. This shipping
condition is then used for determining the shipping point in the sales document instead of what
is specified in the customer master record (see the chapter "Determine shipping condition by
sales document type").

Requirements

Shipping point determination can only be carried out by the SAP system if a shipping condition
is contained in the sales document.

Recommendation

 Since the shipping point is a requirement for creating a delivery, mark the shipping
condition in the customer master record as a required entry to make sure that the
 shipping condition is entered and can be copied to a sales document. For more
information on how to mark fields in the customer master record as required, see the
chapter "Define account groups and field selection for customers".

 If you do not make a distinction between the different shipping conditions in your
company, you should work with a standard shipping condition, for example "01", which
is specified in all customer master records.

Actions

1. Check which shipping conditions are used in your company.

2. Specify an alphanumeric key which can have up to 2 positions and a description for
the shipping conditions.

3. Make sure that the shipping conditions are entered in the customer master records.

Define Shipping Conditions by Sales Document Type

In this menu option, you can specify a shipping condition for individual sales document types.

For example, you can define a shipping condition for the transactions of complaint processing
to make sure that return shipments to the customer are always dealt with in the same way.

Note

The specification of a shipping condition for each sales document type overrules the
specification in the customer master record (see the section "Define shipping conditions").

Requirements

The sales document types must be defined before allocation takes place. The defined sales
document types are automatically displayed for maintenance.

Actions

1. Check for which sales document types a shipping condition should be specified.

2. Specify a shipping condition for the sales document types involved.

Define Loading Groups

You define the loading groups in this menu option. You enter the loading groups defined here in
the material master record for the sales data for each plant.
Recommendation

 The shipping point determination can only be carried out by the SAP System if a loading
point is contained in the material master record. Since the shipping point is a
requirement for the creation of a delivery, you should mark the loading point in the
material master record as a required entry to ensure that the loading group is entered
and can be copied into a sales document. For more information on how mark fields in
the material master record as mandatory see the section "Define Material types".

 If you do not distinguish between different loading groups in your company, you should
work with a standard loading group, for example, "0001" which must be specified in all
material master records.

Actions

1. Check which loading groups are used in your company.

2. Specify an alphanumeric key with up to 4 digits and a description for the loading
groups.

3. Make sure that the loading group is entered in the material master records

Assign Shipping Points

In this menu option, you allocate the shipping points to the desired combinations of shipping
condition and loading group for each plant.

Requirements

Before you can allocate the shipping points, you have to define plants, shipping points, shipping
conditions, and loading groups. For information on this subject, see the following menu
options:

 Plants are defined as organizational units of Materials Management (module MM) in

menu option "Create plant".

 You define shipping points as organizational units of sales & distribution in menu option
"Create shipping points".

Actions

1. Check how the shipping points within a plant should be allocated to the shipping
conditions and loading groups.
 2. Make the allocation for the individual plants.

Set an indicator for the shipping point which should appear in the item of the sales
document as a default value. You can specify manually the other shipping points
allocated here in the item of the sales document.

 Assign Goods Receiving Points for Inbound Deliveries

 In this IMG activity, you assign one or several goods receiving points to the combination
plant/storage location. If you assign several, you can specify a priority.
 Requirements
 Before you can assign the goods receiving point, you must define the plant and storage
location. You will find information on this in the structure maintenance of the enterprise
structure, where plants and storage locations in the general logistics and materials
management areas are defined.
 Activities
 Check how the goods receiving points are to be assigned and then assign them.
 Further notes
 Technically, the goods receiving point is represented by the shipping point data
element.

Delivery Scheduling and Transportation Scheduling

Shipping activities and transportation can be scheduled automatically in sales documents.

Picking/packing and loading, transportation scheduling and transportation can be planned and
optimized on the basis of the dates determined.

There are two different types of scheduling:

 Delivery scheduling

The SAP System takes into account the pick/pack time and loading time for a
transaction.
You define the type of delivery scheduling for each shipping point.

 Transportation scheduling

The SAP System takes into account the transit time and the transportation scheduling
time for a transaction.
You define the type of transportation scheduling on the basis of the route (see sections
"Route definition" and "Route determination").
You define for each sales document type whether delivery scheduling and/or transportation
scheduling should be carried out.

For the dates to be determined automatically on the basis of the requested delivery for an
order item, you must define both the times and what influences the determination of the date.

You need to carry out the following:

 Define for each sales document type whether scheduling is to be carried out and, if so,
which type.

 Define the indicators for scheduling for each shipping point.

 Define:

o Pick/pack times

o Loading times

o Transit times

o Transportation scheduling times

Define Routes

In the following IMG activities, you define your routes. The route determines the itinerary and
the means of transport in shipping, and influences transportation scheduling. For example, if
the route includes rail transport, transportation scheduling may have to include the time
required to reserve freight carriages.

Using routes, you can combine sales order items according to shipping criteria.

The system determines routes automatically for a sales order item and can repeat the
procedure for a delivery (see section Route determination).

In order to define routes, proceed as follows:

 Define the modes of transport.

 Define the shipping types.

 Define the transportation connection points and maintain the relevant data on the
detail screen.

 Define the routes and route stages.

You can also maintain the route stages for several stages.

Note for transport interface

The transport includes all objects maintained in Customizing for controlling route definition.

In order to trigger transport, you select all entries to be transported and choose Table view ->
Transport.

You can check the entries and copy or delete them in the transport request.

Save your entries

Route Determination

The SAP System determines routes automatically for each sales document item. It determines
the itinerary and mode of transport in shipping.

Routes are determined depending on the following criteria:

 Country and departure zone (departure zone of the shipping point)

 Shipping conditions agreed in the sales order

The shipping condition is defined in shipping point determination.

 Transportation group of the material

 Country and transportation zone (receiving zone) of the ship-to party

The SAP System copies the route from the sales document item into the delivery at header
level.

To define route determination, you must edit the following points:

 Define transportation zones for each country. These transportation zones can be either
departure zones for the shipping point or receiving zones for the ship-to party.

 Assign the departure zones to the shipping points.

 Define transportation groups for the materials.

 Specify the routes to be selected according to the given criteria in sales processing.

 Define the delivery types for which route determination should be repeated and set the
necessary indicator in the appropriate delivery types.
  Define the weight groups.

Note

Route determination can be repeated by the SAP System when creating a delivery. Delivery
types, for which route determination is to be repeated, should be marked as such in their
definition. In this case, route determination is carried out depending on weight. The route
applies to the entire delivery

Route Schedule Determination

In the following IMG activities, you define how the system determines a route schedule. If only
one route schedule is defined for a certain combination of requirements, then this route
schedule is used.

However, more than one route schedules may be defined for a combination of requirements
for route schedule determination. When a delivery without preceding documents are involved,
the system selects the route schedule with the earliest delivery time for the receiver.

When deliveries based on previous documents are involved (e.g. stock transfer orders), the
system searches for the route schedule that occurs nearest to the date/time of the delivery.
The following search algorithm is used:

o If a route schedule exists for the time specified, it is used for the delivery.

o If no route schedule exists for the time specified, the system searches for
previous route schedule up to the GI time.

o If no route schedule exists from the time of GI up to the time specified, the
system searches for the next route schedule in the future and assigns it to the
delivery.

You need to carry out the following activities for route schedules:

 Use route schedule per shipping point

 Use route schedule per delivery type

 Use route schedule per order type

Define Modes of Transport

In this activity, you define the modes of transport.

You can have the following modes of transport:

 By road

 By air

 By post

Activities

1. Check which modes of transport are relevant for your system.

2. Define the modes of transport by entering an alphanumeric key of maximum two
digits as well as a text description.
3. Assign the mode of transport to a mode-of-transport type. The mode-of-transport
type serves for classification of modes of transport in dangerous goods management.

Note about automatic shipment

Select the entries you want shipped and then choose Table view -> Shipment. You can still
check the contents of these entries and then either transfer them into the transfer order you
created or delete them

Define Shipping Types

In this activity, you define the shipping types in combination with the mode of transport. The
shipping types can include the following:

 Truck

 Truck with trailer

 Plane

 Ship

Activities

1. Define the shipping types. Enter an alphanumeric key of maximum two digits as well
as a text description.
2. Assign one or several modes of transport to each shipping type.
3. Assign the shipping types to a shipping type group, which serves to determine the
pricing procedure for calculating the shipping costs.

Note about automatic shipment

Select the entries you want shipped and then choose Table view -> Shipment. You can still
check the contents of these entries and then either transfer them into the transfer order you
created or delete them.

Define Transportation Connection Points

In this activity you define transportation connection points.

A connection point can be one of the following:

 an airport

 a border crossing

 a railway station

Note

On the detailed screen of a connection point, you can also enter locations as a reference. For
example, you can define a shipping point or a plant as a node. Alternatively, you can refer to an
address. The specification of a location or an address is required.

On the detailed screen, you can also enter an office of exit if you are processing export
activities. For information on this subject, refer to the section "Define customs office and
assign routes". If you want to have the system determine the office of exit for export activities,
maintain the address of the points that are defined as border crossings.

Activities

1. Define which points are relevant for your shipping processes.

2. For each point, enter an alphanumeric key of maximum 10 digits. Also enter a text
description for each point.

3. Maintain the detailed data of the point. For each point, you must either maintain an
address or specify a reference to an existing location.

Note about automatic shipment

Select the entries you want shipped and then choose Table view -> Shipment. You can still
check the contents of these entries and then either transfer them into the transfer order you
created or delete them.

Define Routes and Stages

In this workstep you define routes and route stages. You also have the option of maintaining
the transportation connection point from here.

Definition of routes

Activities

To define the routes, proceed as follows:

1. Check which routes are relevant for you.

2. Define the routes. Enter an alphanumeric key of maximum 6 digits length. Also enter
a text description for each route.

3. If necessary, enter further data for your route. This data includes:

o Shipping type

You can assign a shipping type to the route, to the preliminary leg, and to the
subsequent leg.

o Transportation service agent

o Transit time

o Transit planning lead time

o Factory calendar, work time

Note: You must have already defined the factory calendar before you can work
with it (see section "Define calendar").

o Driving time (transit time minus breaks, distance)

o You can assign a mode of transport to the routes for processing export activities.
For information on this, refer to the section "Define customs offices and modes
of transport".

Further notes

On the route screen there are two additional functions available:

 Check and compare the route values for transit time, driving time, and distance with the
total for the respective values in the route stages.
 Here the system checks whether the value total for the transit time in the stages is
greater or the same as the value in the route. In the case of the driving time and the
distance, the system checks whether for the transit time the values total in the stages is
exactly the same as the value in the route.

 Copying values total in the route stages into the value in the route

To initiate the check, select all the routes that you want to check and then select "Check." After
the check, only those routes remain selected where the system has found inconsistencies
between the values in the route and the values in the stages. You now have the option of
copying the totaled values from the route stages by leaving the routes with inconsistencies as
they are and by selecting "Copy values." The values of the route are overwritten by the values
from the stages.

Definition of route stages

On the screen for the definition of the route stages, you have two display options. Double-
column display shows the beginning point and the destination point of the stage. You select this
display if stages of type 2 (load transfer point) or type 3 (border crossing point) exist. Single-
column display is advisable if the route only contains stages of type 1 (transportation) and no
inconsistencies occur. In single-column display, only the beginning pointis displayed since the
beginning point of the next stage is the destination point of the previous stage. The destination
point does not, therefore, have to be displayed and there is more room for detailed
information, such as the shipping type, transportation service agent, total duration, and so on.

Activities

To define the route stages, proceed as follows:

1. Check which stages are relevant for you.

2. Define the stages.

Enter the beginning point and, if required, the destination point. To enter a point
between the other points, position the cursor on the point in front of which you wish to
insert a new one and select Insert. To create a new point, select Create.

3. Maintain the detailed information of the stage. For example, you can specify the
transportation service agent, the distance, the shipping type, or the driving time.

Further notes
For maintenance of detailed information, you can have values proposed, such as the total
duration, distance, etc. from other routes. The system checks all stages in other routes that
have the same beginning and destination points, and perhaps also have the same shipping type,
transportation service agent, leg indicator, and stage type, if the respective entries were made.
You can display default values for all values of all stages, or only for special stages or for certain
parameters, such as distance and unit. It is possible to select lines as well as columns. If you
select both individual stages as well as individual parameters and default values, values are
proposed only for the intersection selection values. If, for example, you select stage 3 and the
columns for distance and unit, and then choose the value default, the system proposes only the
distance (with unit) for stage 3, if the value was already maintained in another route.

Note about automatic shipment

Select the entries you want shipped and then choose Table view -> Shipment. You can still
check the contents of these entries and then either transfer them into the transfer order you
created or delete them.

 Maintain Stages For All Routes

 In this activity, you can process stages for several routes together. This makes it possible
to maintain the detailed information of stages efficiently.
 Activities
 To maintain stages for several routes, proceed as follows:
 1. On the selection screen, enter the required data or other selection criteria, and select
Execute.
 The system displays all the stages that correspond to your selection criteria. The stages
are sorted by starting and destination points.
 2. When you drill down a stage, the system displays all routes in which this stage is used.
The red traffic light points out that the stage has not yet been processed within this
transaction, that is, the activity you have just started.
 3. Select all the stages of the routes for which you want to maintain the same data and
select change. If you position the cursor on a stage of a route under a stage (at traffic
light level) and select Group, the system will select all the other route stages of the
same stage.
 The system displays a dialog box in which you can maintain the data for all the selected
stages. As soon as you have selected a field and pressed Enter, the system automatically
sets an indicator in the left column. This indicator is only set by the system if the data
has been entered in the fields. If you want to delete an entry from all the selected
stages, leave the respective field blank and set the indicator manually.
 4. After you have made your entries, select Execute.
 You return to the list of stages. The traffic light in the processed stages is now yellow.
 5. Save your entries.
 As soon as you save the data, the lights in the processed stages are green. If you leave
the transaction and call them up again, the lights are reset to red.
Define Transportation Zones

In this activity, you can define transportation zones according to country and depending on
your company's needs. Transportation zones represent delivery recipient (ship-to party) regions
or delivery shipper (vendor) regions.

Use

After taking into account the ship-to party's transportation zone and other factors such as:

 Country of origin and country of destination

 Shipping conditions

 Transportation group,

the system automatically suggests a suitable route during sales order and outbound delivery
processing.

Example

You can define transportation zones according to a country's zip code system.

Activities

Define the transportation zones you need for each country and enter the corresponding
description.

 Maintain Country And Transportation Zone For Shipping Point

 In this IMG activity, you can assign countries and transportation zones that you defined
earlier for each shipping point.
 Activities
 Enter a country key and transportation zone for all relevant shipment stages
 Define Transportation Groups
 In this IMG activity, you define the transportation groups. You specify the transportation
groups defined here in sales/plant data of the material master record. The
transportation group is copied into the delivery item.
 SAP Recommendation
 The system can only carry out route determination if the transportation group is
included in the material master record. As the transportation group is a prerequisite for
route determination, you should select the transportation group in the material master
record as a required-entry field to guarantee the entry. The section "Define material
types" provides information on marking fields in the material master record as required-
entry fields.
  Actions
 1. Check which transportation groups are used in your shipping processing.
 2. Define the transportation groups. Enter an alphanumeric key with up to four digits
and a description for each transportation group.
 3. Make sure that the transportation group is entered in the material master records.
 Define Weight Groups
 Route determination is carried out in the sales order. When creating the delivery, you
can have the system carry out route determination again. In addition to the criteria for
route determination contained in the order item (destination country, departure
country, transporation zone, shipping conditions and transportation group) the system
also takes the weight of the delivery into account. This is where you define
 the weight groups.
 Activities
 1. In the "weight group" column, enter an alphanumeric key.
 2. Enter a description, (e.g. up to what weight this weight group should apply).
 3. In the detail data, assign the exact weights up to which the weight groups are valid
using the corresponding weight units. This involves a to-scale.

Maintain Route Determination

In this activity, you can set the route determination per country of departure/departure zone
and country of destination/receiving zone in the sales order or delivery.

In the sales order, the route determination is dependent upon the following factors:

 Country of departure/departure zone

 Country of destination/receiving zone

 Shipping conditions

 Transportation group

The above list plus the weight group factor make up the factors relevant for determining the
delivery route determination.

To maintain new combinations of departure countries/zones and destination countries/zones,

you can:

 Enter countries and zones into the table manually by choosing New entries.

 Select all possible combinations for a shipping point and a particular destination
country, for example, by choosing New entries and then Enter further combinations.
Simply enter the desired shipping point and destination country in the dialog box and
 choose All combinations. The departure zone and all destination zones defined for the
shipping point and destination country you specified then appear automatically. If you
only specify the shipping point, all destination zones appear for all countries in the table.

In the screen displaying departure countries/zones assigned to destination countries/zones, you

can position the cursor on a shipping point, departure country, departure zone, customer,
destination country or destination zone. The system then goes to the line corresponding to the
cursor position (shipping point 001, for example). If the desired entry does not exist, the system
goes to the next table entry and displays a message to this effect.

To set the route determination in the order, choose Route determination without weight group
(order) for each combination of departure country/zone and destination country/zone. For
delivery route determination, choose Route determination with weight group (delivery). Then
enter a route for a combination of influencing factors (shipping conditions, transport group and
weight group, where necessary).

There are various ways to enter routes:

 Choose New entries to manually enter combinations of influencing factors with the
desired route.

 Choose New entries and then Enter further combinations to display all influencing
factors that do not yet have a corresponding route maintained for them. You can then
enter the routes that you would like to add and choose Delete init. routes. This action
transfers only maintained entries into the table. In other words, entries with no route
maintained (those whose route field is blank), are not transferred.

You can only maintain generic entries during route determination in a delivery. This means you
can enter a route for a line in which you have neither shipping condition nor transportation
group or in which you have only one shipping condition and no transportation group.

Enter a proposed route for determination in the order and an actual route for determination in
the delivery. You can control which routes given in the delivery (actual routes) may overwrite
the routes given in the order (proposed routes) in activity Define allowed actual route by
proposed route.

The entries are displayed in such a way that a line only contains an entry when that entry differs
from the previous one, resulting in a clear, easily comprehensible arrangement of information.
For example, you can easily identify all the entries for shipping condition 01 (As Soon As
Possible) because all the lines under that entry are blank until you come to the next shipping
condition, 02 (Standard).

Further notes
The Customer exit 0VRF001 is also provided to assist you in developing an individual route
determination or modifying the existing route determination.

Define New Route Determination By Delivery Type

In this IMG activity, you determine for each delivery type whether or not route determination
should be repeated by the SAP System when creating a delivery.

If route determination should be repeated, you can have the SAP System check whether the
actual route found for the delivery is allowed instead of the original proposed route (see
section "Define allowed actual routes for each proposed route").

Requirements

The delivery types must already be defined. The defined delivery types are automatically
displayed for maintenance.

Actions

1. Check for which delivery types new route determination is necessary.

2. Specify for each delivery type whether route determination should be repeated and
whether a found actual route should be checked to ascertain whether it is allowed

Define Allowed Actual Route By Proposed Route

In this IMG activity, you specify the allowed actual routes for each proposed route. The
proposed route is the route determined by the system. The actual routes are the permitted
alternative routes which you can enter manually in the sales document in place of the proposed
route found by the system. When route determination is repeated in the delivery, the proposed
route can be replaced by one of the permitted actual routes. You can check the actual routes to
establish whether they are allowed (see section "Specify route determination for each delivery
type").

Requirements

First define the routes.

Activities

1. Check which proposed routes can be replaced by actual routes, if necessary.

2. Enter the permitted actual routes for each proposed route

Route Schedule Determination

In the following IMG activities, you define how the system determines a route schedule. If only
one route schedule is defined for a certain combination of requirements, then this route
schedule is used.

However, more than one route schedules may be defined for a combination of requirements
for route schedule determination. When a delivery without preceding documents are involved,
the system selects the route schedule with the earliest delivery time for the receiver.

When deliveries based on previous documents are involved (e.g. stock transfer orders), the
system searches for the route schedule that occurs nearest to the date/time of the delivery.
The following search algorithm is used:

o If a route schedule exists for the time specified, it is used for the delivery.

o If no route schedule exists for the time specified, the system searches for
previous route schedule up to the GI time.

o If no route schedule exists from the time of GI up to the time specified, the
system searches for the next route schedule in the future and assigns it to the
delivery.

You need to carry out the following activities for route schedules:

 Use route schedule per shipping point

 Use route schedule per delivery type

 Use route schedule per order type

Scheduling With Route Schedule For Shipping Point

Route schedules (previously referred to in the system as delivery phases in this step) describe
the periodic delivery of goods from a shipping point to different ship-to parties and their
unloading points.

Here you specify per shipping point whether this sort of periodicity is generally required.

Requirements

f you want to define route schedules, you must perform the following activities:

1. Define routes
 2. Activate delivery scheduling

Standard settings

The control function without determination of route schedules is delivered with the system.

Further notes

Route schedules can be determined for deliveries, orders and stock transfer orders

Scheduling With Route Schedule For Sales Document Type

Route schedules describe regular outgoing delivery of goods from a shipping point to different
ship-to parties and their unloading points.

This is where you configure whether you want this to apply to a given sales document.

Requirements

If you want to define route schedules, you must complete the following activities:

1. Define routes

2. Activate shipping dates

Standard settings

Controlling without determination of route schedules.

Further notes

Route schedules can only be determined for deliveries.

Scheduling With Route Schedule For Delivery Type

Route schedules describe regular outgoing delivery of goods from a shipping point to different
ship-to parties and their unloading points.

This is where you configure whether you want this to apply to a given delivery type.

Requirements

If you want to define route schedules, you must complete the following activities:
 1. Define routes

2. Activate shipping dates

Standard settings

Controlling without determination of route schedules.

Further notes

Route schedules can only be determined for deliveries.

Define Incompleteness Procedures

In this IMG activity, you define the incompleteness procedures that should apply to the various
incompleteness objects.

In an incompleteness procedure you group together the fields that are to be checked for
completeness. If you have not entered data in one of the fields in the document, the document
is incomplete. Depending on the status group you can block certain subsequent activities for
the document.

For every field in the procedure you also have to define whether a warning message should be
issued during processing if no data is entered in this field. This function does not exist in
delivery processing. When you select the control field, it has no further consequences.

Requirements

You must have defined the status groups to be able to assign them to the fields you have
selected for a procedure (see Define Status Groups section).

Activities

1. Check to what extent you can adopt the defaults for the incompleteness procedures
that are defined in the standard system.

2. Change the specified incompleteness procedures according to your requirements.

Define new incompleteness procedures, if necessary. Bear in mind that you have to do
this for every incompleteness object.

Further notes

Incompleteness procedure 50 is defined for incomplete texts in sales document processing. If

you want to assign your own status group to this procedure, you need to process View V_TVUF
directly with the transaction for Maintain table view. Note that the changes you make in this
transaction affect all sales document categories

 Assign Incompleteness Procedures

 When you perform this IMG activity, you assign the incompletion procedures to the
partner functions, the delivery types and the delivery item categories

Define Status Groups

In this IMG activity, you use status groups to define the status of incomplete sales and
distribution documents. Then assign the status group to the fields in an incompleteness
procedure.

In the status group, you define which functions may be carried out for an incomplete sales and
distribution document, or for the items where a field entry is missing. You use this function to
block a document for delivery, billing, or pricing. In addition, you can check at header level
whether the general data is complete.

Example

Fields that are defined for deliveries do not also have to apply to the billing document. If you
allocate the relevant status group to these fields in the incompleteness procedure, you can
create a billing document for the incomplete sales order but not a delivery.

Activities

1. Check to what extent you can use the defaults for status groups that are defined in
the standard system.

2. Change the existing status groups according to your requirements. Create new
groups, if necessary.

3. Afterwards specify status groups for fields in the incompleteness procedures (see
section Define Incompleteness Procedures).

 Check Delivery Types and Item Categories

 First check the delivery types and item categories that are contained in the standard SAP
R/3 System.
 You have to keep in mind that they cannot be seen in isolation but are closely linked to
sales document types and billing types. Therefore also take into account the actions that
are listed for sales documents and billing documents.
 The definition is only complete if you have also edited the menu options for the
functions. You could, for example, define separate scheduling for your own delivery
 type. In this case, you would have to edit the menu options "Delivery types" and
"Scheduling" in relation to one another.
 Actions
 Check to what extent you can use the defaults that are contained in the standard SAP
R/3 System and to what extent you have to make changes to represent your business
processes.

Define Delivery Types

In this menu option you define your delivery types which represent the different business
transactions in shipping.

You have the following possibilities:

 Change an existing delivery type.

 Copy an existing delivery type and adapt it according to your requirements.

 Create a new delivery type.

In this menu option you do not make specifications concerning the following functions:

 Statistics

 Output

 Text determination

 Route determination

 Picking

You will edit these functions later in the respective menu options.

This means that the definition of a delivery type is only complete when you have edited all of
these menu options.

In this menu you have to make or check the following specifications:

 Delivery type

o Specify an alphanumeric key for a delivery type that can have up to 4 characters.

o Enter text to describe the key.

 Document category

With the document category you allocate a document type to a certain business
transaction. This way, an SD document is clearly identifiable, for example, as a delivery
or a free of charge delivery.
Specify a single-digit alphanumeric key. The keys you may use can be found under
"Possible entries".

 Number assignment

Specify a number range for internal or external number assignment. To define a

common number assignment for different delivery types, you have to specify the same
number range in each case.
To do this, you must already have defined the number ranges. For more information on
this subject, see the section "Define number ranges for delivery types".

 Increment of item numbering

Here you have to specify the increment of the item number assignment. Keep in mind
that items you add when changing a delivery at a later date have to fit into the
consecutive numbering system.

 Sales order required

Here you define whether a delivery with or without order reference is concerned.

 Default order type

Here you determine the dummy order type which is regarded as a default value if
deliveries or delivery items do not have an order reference.
If you create delivery notes without order reference, you have to specify these control
criteria for the system. In deliveries with reference to an order, the SAP System copies
from from the document header of the sales document into the delivery header.

 Requirements for an item independent of an order

You can include items without reference to an order, that is, items independent of an
order, into a delivery. You can, for example, enter packaging materials later.
In the standard SAP R/3 System you can check for items independent of an order,
whether goods issue and the billing document for a delivery have already been posted
completely. If this is the case, you cannot include additional items in the delivery.
  Transaction procedure

You can define the transaction procedure for a sales document type individually:

o Group screen sequence header

Here you determine the screens which the SAP System should display for a
certain transaction (for example, creating a delivery) and the sequence in which
they are displayed.

o Amount of data displayed for items

Here you determine the items to be displayed by the system during document
processing, for example, you can limit the display to all selected items.

o FCODE overview screen

Here you determine the overview screen which is to be displayed first during
delivery processing after you have entered data on the initial screen.
The keys which you can used can be displayed under "Possible entries". At present, you
cannot change the keys in Customizing.

SAP Recommendation

 If you define your own delivery types, the keys should start with the letter Z since SAP
reserve this name convention in the standard system.

 If you define your own delivery types, you should copy similar delivery types defined by
SAP and make the appropriate changes.

In this case, all specifications in the existing delivery type are copied. In particular, data,
for example, concerning partner determination, or document flow is copied, which you
do not edit in this menu option. As a result, you can test your new delivery types with
regard to defaults set here without having to edit the other menu options.

 When copying delivery types and item categories, the SAP System automatically creates
a log with the copied data. Using the log, you can check whether all the copied data
applies to your delivery type or whether you have to make changes.

Actions
  If you only have to make insignificant changes to the existing delivery types, do so as
appropriate.

Insignificant changes include a changed description, a different number range or

another increment for item numbering. They refer to parameters that are not used for
controlling purposes.

 If you have to make further changes, define new delivery types. In this case, you can, for
example, define different output controls for different delivery types. Alternatively you
can define a separate delivery type for a new sales document type.

Define Item Categories for Deliveries

In this menu option you define your item categories for deliveries. In connection with the
delivery types, they represent the different business transactions in the SAP System.

The item categories, together with the delivery types contained in the standard SAP R/3
System, cover the usual business transactions.

You have the following possibilities for defining your own item categories:

 Change an existing item category.

 Copy an existing item category and change it according to your requirements.

 Create a new item category.

In this menu option you do not make specifications concerning the following functions:

 Picking

 Statistics

 Text determination

You will edit these functions later in the respective menu options.

This means that the definition of a delivery item category is only complete if you have edited all
of these menu options.

In this menu option you have to make or check the following specifications:

 Item category
 o Specify an alphanumeric key with up to 4 characters for the item category.

o Enter text to describe the key.

 Material 0

Here you define that it is not necessary to specify a material number for the item
category. For example, you do not have to specify a material number for text items.

 Quantity specifications

Concerning the quantity specifications in a delivery item, you can define the following:

o For delivery quantity 0 you can define different system responses.

o The shortfall of a minimum quantity that you have defined in the material
master record or in a customer-material info record can be checked by the SAP
System. Here you determine the system response in case of a shortfall.

o The SAP System can check whether the original order quantity is exceeded. Here
you define the system response if the original order quantity is exceeded.

 Transaction procedure

You can determine the transaction procedure for an item category individually:

o Group screen sequence

Here you determine the screens which are to be displayed for a certain
transaction (for example, creating a delivery) and the sequence in which they are
displayed.

o Field selection item

Here you determine the fields, depending on the item category, which are to be
displayed by the SAP System on the item screens.
You can display a list of the keys you may use under "Possible entries". Currently, you
cannot change the keys in Customizing.

Note

If you create or copy new item categories for deliveries, you have to compare them with the
item categories for sales documents. The SAP System copies the item category of an order item
into the delivery. Therefore, you must have defined an item category with the same name for
the delivery.

SAP Recommendation

 If you define your own item categories, the keys should start with the letter Z since SAP
reserves this name convention in the standard system.

 If you define your own item categories, you should copy similar item categories defined
by SAP and make the corresponding changes.

In this case, all specifications of the already existing item category are copied as well as
the allocation to the delivery types. In particular, data, for example, concerning text
determination or document flow, which you do not edit in this menu option, is copied.
This way, you can test your new item categories with regard to defaults set here without
having to edit the other menu options.

 When copying sales document types, item categories, and schedule line categories, the
SAP System automatically creates a log with the copied data. Using the log, you can
check whether all copied data applies to your item category or whether you have to
make changes.

Actions

 If you only have to make insignificant changes to the existing item categories, do so as
appropriate.

An insignificant change may be a changed description. Insignificant changes refer to

parameters that are not used for controlling purposes.

 If you have to make further changes, define new item categories.

Define Item Category Determination in Deliveries

In this menu option you define the item category determination for deliveries. The following
applies:

 If an order item or a schedule line is copied into a delivery, the item category is also
copied.

 For items independent of orders in the delivery (for example, packaging material that is
entered in the delivery) or deliveries without reference to an order, the item category is
determined by the SAP System by allocating the item category group to a delivery type.
The respective item category is determined depending on the following criteria:

 Item category group of the material

 Sales document type

For more information on the item category group and on the allocation of the item categories,
see the section "Define item category determination in sales documents".

For each item category, you allocate the allowed delivery types to the item category groups. On
the other hand you can also allocate the item categories to the item category groups for each
delivery type.

If you enter a material with a certain item category group (for example, standard item) in a
delivery with a certain document type, the SAP System automatically finds the allowed item
category by allocating the delivery type to the item category group.

Define the item category that is to be proposed automatically. You can also define the allowed
item categories which you can then specify in the delivery by changing the default.

Note

The SAP System automatically determines the corresponding schedule line category using the
item category of a delivery item independent of an order. The information in the schedule line
category is necessary for the availability check as well as for quantity postings and value
postings in materials management due to the goods movement.

Actions

To define the item category determination, proceed as follows, for example:

 Select the delivery type to which you want to allocate item categories.

 Then select one of the item category groups.

 Specify all allowed item categories for the combination of delivery type and item
category group.

If it is an item category that is to be proposed in the delivery, you have to characterize

the combination of item category, item category group, and delivery type.

Alternatively, you can also make the allocation via the item categories.

Define Item Category Usage

In this menu option, you specify the item category usages which control the usage of an item.
Item category usage controls, for example, the system response if during document processing
an item does not refer to a material but to a text item. Item category usage can also be
maintained via the item categories (detail screen for item categories: Goto -> Item usage).

Default settings

In the standard SAP R/3 System, the following usages are defined:

 Batch split

 Text item

 Service item relevant for billing

 Service item not relevant for billing

Actions

1. Check first whether you can copy the usages in the standard system.
2. If necessary, create a new item category usage by entering an alphanumeric key with
a maximum of four characters and a description.

Define Reasons for Blocking in Shipping

In this step, you define possible delivery blocks and assign them to the appropriate delivery
types.

You set delivery blocks to separate certain transactions (e.g. political instability, insufficient
stock, etc.) from the standard process flow for special reasons and to avoid that further
processing takes place automatically. As a result, the transaction "rests" until the person
responsible reviews the situation, makes a decision and possibly removes the delivery block
manually.

Delivery block in the sales document

In the sales document, you can set delivery blocks on two different levels:

 Delivery block at header level

In sales documents, you can either enter delivery blocks manually at header level
(business data in the sales document header) or they can be proposed automatically by
the system. In the latter case, the delivery block must be entered in the respective sales
document type (see chapter "Define sales document types"). In addition, the delivery
 block in the sales document header is only effective if the delivery block has been
assigned to the respective delivery type.

 Delivery block at schedule line level

You can block individual schedule lines for delivery manually in the sales document. The
delivery block at schedule line level is always effective, regardless of whether the
delivery block is assigned to the corresponding delivery type. Schedule lines can also be
blocked automatically by the SAP System if you have defined an automatic delivery
block for the schedule line category. For this, you must specify the delivery block for a
schedule line category (see chapter "Define and assign schedule line categories"). The
blocking ID is only valid for the schedule line and is not copied into the item. You must
remove the blocking ID manually in order to release the schedule line for delivery.

Delivery block in the delivery

You can also block deliveries for picking and goods issue. This delivery block is always effective,
regardless of whether the delivery block is assigned to the corresponding delivery type.

A delivery block can be combined with certain functions depending on the blocking reason:

 Order block

A delivery block can be controlled such that the system automatically blocks sales
documents for customers who have a delivery block in the customer master record. For
example, you can block sales orders which have a delivery block due to problems
concerning payment.

 Requirements block

In sales order processing, you can block the order quantity from being confirmed using a
delivery block. In this case, the system does not confirm quantities during order
processing. Therefore the system does not transfer requirements so that the quantities
can be used for other orders.

 Delivery due list block

You can use this block to block the creation of deliveries with the delivery due list
function. This block does not block the direct creation of an individual delivery.

 Picking block
  Goods issue block

Actions

1. Check the reasons for which a customer, sales document or schedule line may have to
be blocked for delivery in your company.

2. Define the delivery types to which a block should apply.

3. Agree on the person subgroup that sets the delivery block and the time at which they
do so, if the block is not set automatically by the SAP System.

4. Specify an alphanumeric key for the blocking reasons in shipping with up to 2

characters and a description.

5. Control the delivery blocks by linking them with certain functions, if appropriate.

Define Number Ranges for Deliveries

In this menu option you define the number intervals of the number ranges for deliveries and
groups of deliveries.

When creating a delivery or a group of deliveries, a unique number is assigned which identifies
the delivery or the group. The number is derived from the number range provided for the
document type or the group.

There are two possibilities for the type of number assignment:

 Internal number assignment

The SAP System automatically assigns a consecutive number from the defined number
range.

 External number assignment

You specify a number from the external number range.

Transport

You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After
the import, only the intervals you export are present. The number statuses are imported with
their values at the time of export.

Dependent tables are not transported or converted.

Actions

1. To define a number range you have to add a new number interval:

o Specify an alphanumeric key with up to 2 characters.

o Specify the limits of the number interval. The individual number intervals may
not overlap. Thus, every number can occur only once.

o Mark the number range, if it is provided for external number assignment.

2. Then specify the key of the number range for the delivery types (see section "Define
delivery types") and for the groups of deliveries (see section "Define groups of
deliveries").

 Define Split Criteria for Deliveries

 When deliveries (sales orders or purchase orders, for example) are shipped, you may
not be able to create items for them, depending on various criteria. Normally, a split is
carried out according to ship-to party or route, for example, meaning that the items
from preceding documents are distributed among various deliveries.
 In this activity, you can define other criteria that cause a delivery split.

Subsequent Delivery Split

Example

When you load a delivery at the loading ramp, the system recognizes that the available loading
space is not sufficient for the entire delivery. Shipping documents, goods movement postings
and invoices should be created on the basis of the quantity that was actually loaded. Using the
subsequent delivery split function, you can divide up existing deliveries into various other
deliveries.

Damage caused to data by errors

Check if local adjustments to the system (add-ons, user exits, own data, modification solutions)
respond correctly to the delivery split:
The delivery split uses the document update of delivery processing and calls up the
USEREXIT_SAVE_DOCUMENT and SAVE_DOCUMENT_PREPARE user exits in MV50AFZ1
(SAVE_DOCUMENT for delivery processing). It may also be the case that your own messages or
statistical updates cannot process the new situation correctly. During a subsequent delivery
split, the system simultaneously generates and changes deliveries during in one posting. There
is no collective processing indicator and none of the traditional transaction types (T180-TRTYP)
is set.

User-specific data is copied from the LIKP and LIPS tables. If the data is dependent on quantity
or if the document numbers are not used in your own data, you have to update the data
yourself.

Definition

Split result and split complement

If you call up the split, the system displays the quantities or handling units of one or more
deliveries. After the split, these quantities make up the split result and the rest is called the split
complement. You can enter several split result numbers (sequence numbers ) when calling up
the split. Therefore, you can split a delivery into several split results. However, there is only one
split complement per delivery. As a rule, the quantities of the split result after the split are
processed differently from the quantities of the complement. Split Customizing accounts for
this since some settings for the split result and the complement can be carried out separately.

A split result does not necessarily have to have a new document number. When carrying out
the split, you can specify whether the original document number is to be changed to a
sequence result number, and if so, you can specify the number.

Requirements

1. Deliveries may NOT:

a) Have goods movement posted or be billed

b) Be inbound deliveries

2. Items must:

a) Not have serial numbers assigned

b) Not be an inspection lot (QM)

c) Retain a quantity after the split that is at least as large as the quantity of
potentially unassigned transfer orders (WMS) that are n o t confirmed.
3. If the items are packed, the packed quantity after the split must not be less than the
packed quantity before the split. (In general, you have to call up the split by entering the
shipping units).

4. If the delivery is in a shipment, the following restrictions apply:

a) If the delivery has already been transfered to an external transportation

planning system, the delivery that was split cannot be included in the shipment
nor can the original delivery be eliminated from the shipment. Both situations
can be adapted for the split in Customizing.

b) If both parts in the above example are also packed in handling units belonging
to the shipment, it is not possible to split the delivery. The shipping units have to
remain in the shipment and the new delivery cannot be included in the
shipment.

c) A similar example: both parts were packed in the shipment without an

external transportation planning system. The split cannot take a delivery out of
the shipment, but the split itself it is still possible (controllable error message).

d) Deliveries in a finished shipment cannot be changed and therefore cannot be

split.

5. Special functions for delivery quantities packed in the shipment:

a) Handling units with planning characteristics:

Packed quantities can only be split when you enter a highest-level handling unit.
In particular cases, you might want to be able to enter handling units or delivery
quantities that are only visible on lower packaging hierarchy levels. For example,
you may have already planned the assignment of delivery quantities to a truck.
During loading, however, the boxes are to be scanned and split, if necessary. If
this special function is not active, the system would only interpret the truck as
the highest-level shipping unit and you would not be able to call up the split by
entering the boxes. Split Customizing allows you interpret shipping units as
planning units only. They will then be hidden. However, the above rules
regarding the assignment of split result and complement to the shipment still
apply if their quantities are packed in shipment. Note that the split is not
unpacked. The packed quantity is simply re-distributed among the deliveries that
were split.
If 30 tons were packed in the truck and 29.5 tons is split, the split result contains
the 29.5 tons that are packed in the truck. The split complement contains the 0.5
 tons that are also still packed in the truck. If the packed quantity is smaller than
the quantity of an original item, the packing quantity is first distributed to the
split results (starting with the highest number) and then to the split complement.

b) Packed quantities in transportation chains:

If a delivery is in various shipments and if an item quantity is packed in these
shipments, the split separately reassigns the packing quantities of the individual
shipments during the distribution of packing quantities. In other words, the split
supports multiple packing in transportation chains. As the split quantity entry,
you may use only highest-level shipping units from the same shipment. If an item
weighs 30 tons and if you can fit a maximum of 25 tons in a truck and a
maximum of 27 tons on a ship (the truck plus 2 tons), you may only enter a
maximum of 3 tons (smallest quantity of all the shipments that was not packed)
without entering shipping units (as quantity not packed). You can deactivate the
checks and calculations of this special function in Customizing.

6. Groups of deliveries:

a) The reassignment of deliveries within groups of deliveries formed in SD is

supported and can be customized. Wave picks (group type "W") are the exeption
to this rule. They are subject to the restrictions of WMS groups: deliveries may
not be removed from wave picks by splitting.

b) Split result (and the split complement, if you set it as such) are assigned to one
or two new groups of deliveries. If no group type has been maintained for the
main delivery, a group with group type 'D' is created. The error log of the split is
recorded in split result's group.

c) WMS groups: If there are deliveries in WMS groups (collective processing SO

creation, two-step picking, ...) the new assignments (which can also be
customized) cannot be carried out if processing steps have already been carried
out for the group in WMS. In contrast to ordinary delivery groups, deliveries
cannot be eliminated from WMS groups during the split.

7. Groups of items: Delivery groups / Bills of Material (BOMs)

a) According to your settings, changed or generated items with zero quantities

from BOMs or delivery groups can be deleted.

b) If the BOM still has its target correlation, some cases where items are
automatically correlated, can be customized.
 c) Another control is planned for text items in groups of items.

d) A generalization of this topic is a split of handling units if the delivery contains

items that are not packed or that cannot be packed. If necessary, you can use the
USEREXIT_INSERT_QSET user exit here in connection with
USER_CREATE_OBJECTS_FROM_LIPS, which are both in LV53SFZ1.

8. Prices:

a) The quantity-dependent copying of conditions in the new delivery has the

same control options as when you copy conditions from order to order.

9. Delivery split in a decentralized WM system.

Deliveries were created in an ERP system and distributed to a WM system, where they are split.

a) Outbound deliveries may not be packed directly in the ERP system, not even
as a packing proposal. They may only be packed in the decentralized WM
system, where they may also be packed as split deliveries.

b) The following settings are switched off in the split profile, even if you have
switched them on here already.

- Reassign item numbers in a new delivery

- Delete normal items with quantity 0

- Do not split delivery groups

- Do not delete items from delivery groups if

quantity 0

- Check no. of partial deliveries in delivery

split

10. Delivery split when confirming split outbound deliveries in the ERP system

Split outbound deliveries are created by a delivery split at the point of goods issue
posting in the ERP system.

In addition to the points listed above, the following settings are no longer valid for
confirmation in the ERP system and are switched off in the system.
 a) Check complete delivery in delivery split

b) Control when splitting correlating BOMs

c) Copy automatic text items with quantity 0

d) No 1->1 split

Standard settings

Some error messages appear during the split because the settings in Customizing are not being
observed or cannot be carried out. These error messages can be controlled and the split can be
carried out if the message type is set to a value other than 'E'. The standard system settings are
restrictive: For almost every controllable message the system default is 'E'.

Recommendation

Customize the business processes in such a way that the split result gets the new delivery
number rather than the split complement. Before the split, you should not print out any papers
containing the delivery number.

Activities

Check the add-ons and user exits.

Enter the delivery types that are to be split in the split profile table (-> per delivery type).

 Proof of Delivery
 In this activity, you can make the proof of delivery (POD) settings.
 For each delivery item category, you can define whether it is relevant for the POD
process. We recommend that all item categories that belong to a delivery type be
indicated as relevant for POD.
 You can also define the reasons for deviation in this activity.
 Set the POD-relevant indicator in the Shipping view of the sales area data of the
customer with whom you want to carry out the POD process.
 Set POD-Relevance Depending on Delivery Item Category
 In this activity, you can set the proof of delivery (POD) relevance depending on the
delivery item category.
 We recommend that you flag all item categories that belong to a delivery type as POD-
relevant. After setting the POD-relevant indicator in the customer master, you can
activate the proof of delivery process.
 When the system creates billing documents for the item categories that are marked as
POD-relevant, it copies the verified quantity rather than the delivery quantity.
 Define Reasons for Quantity Differences
  In this activity, you can define the reasons for quantity deviation.
 You can enter a key with a maximum of 4 characters and a descriptive text. You must
also define in the Quantity calculation field whether the quantities that were verified
must be subtracted from the delivery quantity (damage during transport, for instance)
or whether they are to be added to it (overdelivery, for example).
 In other words, the content of the Quantity calculation field also influences the POD
quantity result since it is added to or subtracted from the delivery quantity.
 Reasons must always be indicated in the proof of delivery. Since you may not yet be
aware of the reasons at the time the POD is verified, we suggest that you set up a
"Difference under investigation" reason that can be manually changed when you receive
the POD

Transportation

Transportation processing is a central element in the Logistics chain. The functionality allows
you to control and monitor the entire shipment.

Transportation processing can be used both for goods receipt and goods issue so that all goods
movements can be represented in the system. Incoming shipments are made on the goods
receipt side following the goods purchase order and shipping notification; outgoing shipments
are made on the sales side following the sales order and delivery creation.

Requirements for carrying out transportation processing:

1. For outgoing shipments, the following requirements must be met for transportation
processing:

o The delivery type must be flagged as relevant for transportation in Customizing.

o The underlying deliveries must contain a route.

o The routes of the deliveries must be flagged as relevant for transportation in

Customizing.

o The transportation blocking reason in the delivery header must be blank.

If the above requirements are met, the transportation planning status in the delivery is
set to 'A'.
2. In the case of incoming shipments, the following requirement must be met for
transportation processing:

o The delivery type must be flagged as relevant for transportation in Customizing.

Settings in Customizing
In Customizing, you must take the following settings into account, check them and, if necessary,
redefine them:

 Settings for the actual shipment

 Settings for general sales and distribution functions

1. Settings for the actual shipment

 Define transportation types

 Specify the relevance for transportation of delivery types

 Specify the relevance for transportation of routes

2. Settings for general sales and distribution functions

 You use your own elements for transportation processing in output determination:

o Condition tables, access sequences, condition types and output determination

procedures in the condition technique

o Output types for the partner function SP (forwarding agent)

o Print parameters

o Processing programs and documents

3. Editing texts
Text types and text determination procedures are set up for transportation processing
for the text determination.
4. Organizational structure
You must maintain the transportation planning point for the organizational structure.
5. Authorization objects
Two authorization objects exist for transportation processing:

o V_VTTK_TDS (authorization for transportation planning points)

o V_VTTK_SHT (authorization for shipment type)

6. Number range object

The number range object RV_TRANSPO has been set up for transportation processing.

 Basic Transportation Functions

  In the following menu options, you specify the control for the different groups of
transactions. Furthermore, you define the number ranges for the groups.

Shipments

The shipment document contains the required information for executing a shipment and is the
basis for the shipping activities.

In the following worksteps you define:

 number ranges for the shipment documents

 shipment types with the help of which you can represent in the system the shipment
types that are used in your company

 selection variants for lists of shipments and lists of deliveries that serve as a work list for
generating shipments

Also, you can define the shipping relevance of delivery types, delivery item types and routes,
and also shipment blocking reasons

 Shipment Costs
 In the following menu points you will maintain the control elements that are necessary
for, among other things, carrying out shipment costing, settling shipment costs with the
transportation service agent and forwarding of shipment costs to financial accounting.

Packing

Using the packing function, you can enter information on how the products to be supplied
should be packed or were packed for a delivery.

For the different packaging materials (boxes, packaging containers or pallets), material master
records are created with material type VERP, which contain fields (for example, the allowed
packing weight or volume).

Individual items or subsets of an item can be packed into a shipping material with the help of a
handling unit, which in turn can be packed into other shipping units in a multi-level procedure.
You can control, for each delivery item category, whether the item can be packed at all and
whether it must be packed.

To be able to use the packing function, you must set the configurations for the following points:

 Define number ranges of the handling units

  Define packing control per item category

Billing Documents

In the following menu options, you define the control data for the various document types
used in billing.

Furthermore, you define the following for the sales documents in the subsequent menu
options:

 Various blocks

 Groups of billing documents

 Number ranges

 Matchcodes

Define Billing Types

In this menu option you define your billing types that represent the different business
transactions in billing.

You have the following options:

 Change an existing billing type.

 Copy an existing billing type and change it to suit your requirements.

 Create a new billing type.

In this menu option, you do not make specifications concerning the following functions:

 Statistics

 Account determination

 Pricing

 Output

 Text determination

You will edit these functions later in the appropriate menu options.
This means that the definition of a billing type is only complete once you have edited all of
these menu options.

In this menu option you have to make or check the following specifications:

 Billing type

o Specify an alphanumeric key for the billing type with up to 4 characters.

o Enter a description of the key.

 Document category

With the document category you allocate a document type to a certain business
transaction. This way, a sales & distribution document is clearly identifiable, for
example, as an invoice or a cancellation document.
The document category has to correspond with the specification of the transaction
group.

Specify a single-digit alphanumeric key.

The keys you can use may be displayed under "Possible entries".

 Number assignment

Specify a number range for number assignment. For billing documents numbers can
only be assigned internally by the SAP System. To define a common number assignment
for different billing types, you have to specify the same number range in each case.
To do this, the number ranges must have been defined beforehand. For more
information on this subject, see the section "Define number ranges for billing types".

 Increment of item numbering

Here you have to specify the increment of item number assignment. The item numbers
are then not copied unchanged from the delivery or the order. Instead, the items
receive a new numbering. This way you avoid items with the same number being
included in collective invoices.

 Posting block

Here you determine whether a billing document with this billing type is to be blocked
automatically by the SAP System for transfer to financial accounting.
 If this is the case, you have to release the billing document manually at a later point in
time to start data transfer.

 Transaction procedure

With the transaction group you define the transactions with which you can edit this
billing type in billing.
The transaction group which is allocated to a transaction has to correspond to the
document category you allocated to the respective billing type.

The keys you may use are listed under "Possible entries". Currently, you cannot change
the keys in Customizing.

 Cancellation

Here you define the cancellation document which is to be proposed automatically by

the SAP System if you want to cancel a billing document.
You can only specify a cancellation document that you defined beforehand.

You also have to define the copy rules (see section "Define document flow for
transactions").

SAP Recommendation

 First check the billing types contained in the SAP standard version.

 If you define your own billing types, the keys should start with the letter Z since SAP
keeps this name convention free in the standard system.

 If you define your own billing types, you should copy similar billing types defined by SAP
and make the appropriate changes.

In this case, all specifications of the existing billing type are copied. In particular data, for
example, concerning partner determination, pricing, or document flow is copied which
you do not edit in this menu option. This means you can test your new billing types
concerning the defaults set here without having to edit the other menu options.

 When copying billing types, the SAP System automatically creates a log with the copied
data. With the log, you can check whether all copied data applies to your billing type or
whether you have to make changes.

Actions
  If you only have to make insignificant changes to the existing billing types, do so as
appropriate.

Insignificant changes may be a changed description or another number range. They

refer to parameters which are not used for controlling purposes.

 If you have to make more extensive changes, define new billing types. You can then, for
example, define various account assignments for different billing types.

Check settings

You can use the report SDCHECKVOFA to check your Customizing settings for the billing types.
Only some of the settings are checked. For the billing type, for example, a check is made to see
that a cancellation document type has been entered with the right document category. An
invoice has the document category M. The cancellation document type for invoices must have
the document category N.

You can see more information on these additional checks in the report documentation.

Define Number Range For Billing Documents

In this menu option you define the number intervals of the number ranges for billing
documents and groups of billing documents.

When creating a billing document or a group of billing documents, a unique number is assigned
which identifies the billing document or the group. The number is derived from the number
range which is provided for the document type or the group.

Number assignment for billing documents can only be carried out internally, that is, the SAP
System automatically assigns a consecutive number from the defined number range.

Transport

You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.

All intervals for the selected number range object are deleted in the target system first. After
the import, only the intervals you export are present. The number statuses are imported with
their values at the time of export.

Dependent tables are not transported or converted.

Actions
 1. To define a number range, you have to create a new number interval:

o Specify an alphanumeric key with up to 2 characters.

o Specify the limits of the number interval. The individual number intervals may
not overlap. Thus, every number can occur only once.

2. Specify the key of the number range for the billing types

Invoice Lists

Using the invoice list, you can group together several billing documents or several collective
invoices at the end of a period specified in the customer master to form a new document. The
invoice list is sent to and settled by a common payer.

Billing documents, which can be individual or collective invoices, form the basis for an invoice
list. A separate billing index is created for them.

In this menu option, you specify for each billing type the invoice list type with which invoice lists
should be created. You also set special features for printing invoice lists and pricing.

Default settings

Two types of invoice lists were created in the standard version:

LR for billing documents/debit memos

LG for credit memos

You set up an invoice list just as you would a billing document type in the previous step. In this
step, you assign invoice list types to invoices and set special features for output determination
and conditions.

Maintain Copying Control For Billing Documents

In this menu option, you define control data for the document flow of billing documents.

You can specify for a particular billing type which document type is to be assigned to copied
reference documents and which item categories are to be copied.

You must also make specifications for copying requirements and transferring data, as well as
quantity and value updates in document flow. Do this for each copying procedure at header
and item level on the appropriate detail screen.
Note

If you define new sales document types, item categories or schedule line categories by copying
existing ones, the SAP system automatically copies all specifications for the document flow. You
may want to check the copying controls for newly created sales document types, item
categories or schedule line categories.

Actions

1. Check the document flow defined in the standard system.

2. Define to what extent you have to modify its specifications to meet your
requirements.

3. Define the document flow for billing documents with reference to sales document
types.

4. Define the document flow for billing documents with reference to deliveries.

5. Define the document flow for billing documents with reference to billing types.

Note

Make sure that you maintain copy control for the following areas:

Sales documents

Deliveries

Billing documents

If you cannot find an entry, check the copying controls in other chapters.

Complete overview of copying control:

In the chapter on Sales, you can find copying controls for:

 Sales documment to sales document

 Billing document to sales document

In the chapter on deliveries, you can find copying controls for:

 Sales document to delivery

In the chapter on Billing, you can find copying controls for:

 Sales document to billing document

 Delivery to billing document

 Billing document to billing document

Check settings

You can use the report SDCHECKTVCPF to check your copying control settings. This is not a
complete check. A check is carried out, for example, to see that the billing quantity is properly
maintained during invoice receipt related billing. For more information, refer to the report
documentation.

Define Blocking Reason For Billiing

In this menu option you define the possible blocking reasons for billing documents.

Define the possible block indicators in this menu option and allocate them to the billing types
concerned.

The following blocks are possible:

 You can block a customer for billing.

If a customer is to be blocked for billing, enter the block indicator in the block data of
the customer master record. The specification in the customer master record and
therefore also the block for billing documents applies either to all or only to individual
sales areas.
The SAP system copies the specification from the customer master record into the sales
document. For the customer in the sales area in question, you cannot create billing
documents if the block applies to this customer's billing type.

 You can manually block individual sales documents for billing.

Sales documents can also be blocked automatically for billing by the SAP system. In the
standard SAP system credit memo request and debit memo request, for example, are
automatically provided with a billing block. To set a billing block automatically when
creating certain sales documents, you have to define a billing block for the sales
document type. To do this, you specify the billing block for this sales document type
(see section "Define sales document types").
 You will find the indicator for the billing block in the general business data in the order
header. If a sales document is blocked for billing, you cannot create a billing document if
the block applies to the billing type of this document. You can only create the billing
documents, if you have removed the block indicator manually.

 You can block individual items of a sales document manually for billing.

The items can also be blocked automatically for billing by the SAP system. For this to
occur, you have to define a billing block for the corresponding item category which is
then set automatically when the sales document is created. To do this, specify the billing
block for an item category (see section "Define item categories for sales documents").
The indicator only applies to the item and is not copied into the header of the sales
document. You will find it in the general business data of an item. You have to delete
the block manually to release the item for billing.

Actions

1. Check why a customer, a sales document or an item have to be blocked for billing.

2. Define the billing types to which a block should apply.

3. Agree on the group of persons that sets the billing block and when this is done, if this
block is not set automatically by the SAP system.

4. Specify an alphanumeric key for blocking reasons in billing, that can have up to 2
characters, and a description.

5. Allocate the billing types concerned to the blocks

Assign Invoice List Type To Each Billing Type

Using the invoice list, you can group together several billing documents or several collective
invoices at the end of a period specified in the customer master to form a new document. The
invoice list is sent to and settled by a common payer.

Billing documents,which can be individual or collective invoices, form the basis for an invoice
list. A separate billing index is created for them.

In this menu option, you specify for each billing type the invoice list type with which the invoice
lists should be created.

Default settings
 1. In the standard version of the SAP R/3 System, two new condition types were created
for the invoice list:

o Condition type 'RL00' for the del credere

o Condition type 'MW15' for relevant tax

2. Two types of invoice lists were created in the standard version:

o LR for billing documents/debit memos

o LG for credit memos

3. For output determination in the invoice list, two new condition types were created:

o LR00 - invoice list

o RD01 - single invoice invoice list

4. For output determination in the invoice list, two new output determination
procedures were created:

o V30000 - invoice list output

o V30001 - invoice list item output

To be able to group together billing documents in invoice lists, certain data in the documents
must match. This data is checked using the copying requirements. Copying requirement '16' is
used in the standard version.

Actions

The invoice list is controlled using the condition technique. A separate output determination is
carried out for the invoice list which is also controlled using the condition technique. Check first
whether the configuration contained in the standard version is sufficient for the condition
technique. If you want to make company-specific modifications or use your own condition
components, you must carry out the following steps:

1. Create a condition type.

2. Create an access sequence.

3. Create a condition table.

 4. Create a pricing procedure.

5. Specify for each billing type the invoice list type with which the invoice lists should be
created. Enter this on the detail screen of a billing type in the field "Invoice list
category".

If you make changes in the output determination, you must maintain the same elements of the
condition technique analogously to the invoice list:

1. Create a condition type.

2. Create an access sequence.

3. Create a condition table.

4. Create a pricing procedure.

5. Allocate the output type and the output determination procedure to the respective
billing types.

Note

Billing types which should be used in the invoice list must be configured accordingly on the
detail screen in Customizing, regardless of whether you make changes to the condition
technique, or whether you work with the configurations of the standard version.

Additional information

For a detailed description of the condition technique, see the chapters on "Pricing" and on
"Output Determination" in the Implementation Guide

Maintain Conditions For Invoice Lists

In this step, you maintain special condition types for invoice lists.

Default settings

1. Two new condition types have been created for invoice lists in the SAP standard
version:

o Condition type 'RL00' for the del credere

o Condition type 'MW15' for the related tax

Note

A detailed description of the condition technique can be found in the chapter "Pricing" in the
Implementation Guide.

Maintain Output For Invoice Lists

In this step, you define output types for invoice lists.

1. Two new condition types have been created for determining output in invoice lists:

o LR00 - invoice list

o RD01 - single invoice invoice list

2. Two new output determination procedures have been created for determining output
in invoice lists:

o V30000 - Invoice list output

o V30001 - Invoice list item output

To be able to group together billing documents in invoice lists, certain data in the documents
must match. This data is checked using the copying requirements. Copying requirement '16' is
used in the standard version.

Note

A detailed description of output determination can be found in the chapter "Output

determination" in the Implementation Guide

Payment Cards

Payment Card Processing in the SAP System offers you a wide range of functions in Sales and
Distribution and Financial Accounting. It contains the basic tools you need to handle payment
cards in a variety of business processes.

In the following steps, you set payment card functions for:

 Master records, sales orders, deliveries, and billing documents

 Authorization and settlement

 Payment functions and accounting documents

Rebate Processing

This chapter describes how to make settings for rebate processing.

A rebate is a price reduction which is granted to a customer in the form of a credit memo
depending on the sales of a period. The basis for a rebate can be defined in various ways (for
example, customer, customer/material pricing group). You can define a rebate on the basis of
an agreement, the so-called rebate agreement, with your customer. Rebate processing in the
R/3 System can currently meet the following requirements:

1. Creating rebate agreements

2. Creating accruals in the billing document

3. Settling rebate agreements

4. Deleting accruals

The settings for rebate processing also require corresponding adjustments in Customizing for
account determination.

Note

If you do not want to carry out rebate processing in a certain sales organization, you should
switch it off for performance reasons. You can do this when configuring the sales organizations
for rebate processing, following the description in the Control of Rebate Processing section.

Bear in mind the following points regarding rebate processing in Customizing:

1. Requirements in the condition technique

2. General requirements for rebate processing

3. Extension of the account keys

4. Table maintenance

5. Billing index with subsequent installation

If you want to set up rebate processing in a certain client, you must transport the following
objects:

 Condition types for rebate (Tables T685, T685A, T685T)

 Access sequences for rebate (Table T682*)

  Rebate agreement types (Tables T6B1, T6B1T)

 Condition type groups (Tables T6B2, T6B2T, T6B2F)

 Number ranges for rebate agreement categories (should be maintained manually)

 Order types B1 and B2 (Tables TVAK, TVAKT)

 Item categories B1N (Tables TVAP, TVAPT)

 Assignment of item categories to item category groups (Table T184, B1*, B2*)

 Billing types B1 and B2 (Tables TVFK, TVFKT)

 Copy sales order to billing document (Table TVCPF, B1* and B2*)

Rebate Agreements

A rebate agreement is an agreement with the customer to which condition records are
allocated. This guarantees that rebate agreements, like price agreements, depend on a large
number of different criteria (for example, customer, material, rebate group) and can be
handled in various ways. Different calculation types and scale bases can be used. Rebate
agreements can also be entered and changed later, that is, after the start date of the validity
period.

The rebate agreement contains essential data on the agreement, such as the validity period or
the rebate amount, and can be created to include scales.

When maintaining and configuring rebate agreements, you have to consider the following:

 Agreement types

 Condition type groups

 Number ranges

Condition Technique For Rebate Processing

Rebate processing is used in pricing, which means that the same components in the condition
technique have to be maintained for both rebate processing and pricing. You can find more
detailed information on pricing by going to Sales and Distribution - Basic Functions - Pricing

 Pricing

Actions
 Maintain field catalog

 Maintain access sequence

The access sequences have to belong to category 1 (rebate-relevant accesses)

 Maintain condition types

Condition types must belong to condition class C (end-of-period rebate) Maintain

condition tables The agreement number is always adopted in the condition table key for
rebate processing. This makes it possible to implement several rebate agreements for
one condition type with variable keys. User-defined pricing procedures are not copied
for rebate processing. Rebate calculating is integrated into the pricing procedure for
billing documents. Note that the rebate basis in the SubTo field (Condition subtotal)
contains entry 7 (value takeover in field KOMP-BONBA).

 Account Determination For Rebates

 Rebate processing requires special settings in account determination.
 There are, for example, user-defined account keys for sales deductions and accruals,
user-defined access sequences and condition types.
 Actions
 Check first whether you can copy the elements contained in the standard system for
rebate processing and for account determination. If you want to extend or modify the
settings, you must carry out the following steps:
 For rebate processing, you must edit the following elements:
 1. Create an access sequence.
 2. Include a condition table.
 3. Define corresponding condition types.
 4. Pricing procedure
 Rebate types which should be taken into account during pricing must be included in the
corresponding pricing procedures in Pricing.
 During order entry and billing, accruals are set up and updated as cumulative sales.
Depending on the configuration, the accruals set up may or may not be displayed in the
sales order. In the standard system, the pricing procedure can be set such that the
rebate condition type in the sales order appears as a statistical condition type at the end
of the price screen. If the volume rebate condition type should not be displayed( e.g. for
reasons of performance), this can be controlled using requirements in the pricing
procedure.
 For account determination, you must edit the elements of condition technique and
create accounts for the accrual if required.
 To edit the condition technique for account determination, you must consider the
following points:
 1. Create an access sequence.
  2. Define corresponding condition types.
 3. Define the pricing procedure.
 Maintain the account key and assign the condition types.
 Maintain the G/L account assignment and ensure that the G/L account is used in second
place for accruals
 Activate Rebate Processing
 In this menu option, you activate rebate processing for sales organizations and billing
types.
 Actions
 1. Relevance to volume-based rebate for each sales organization
 For each sales organization, you have to specify whether rebate processing can be
carried out or not. Deactivate rebate processing for a certain sales organization if you do
not want to carry it out.
 2. Relevance to volume-based rebate for each billing type
 The qualification for rebate must be defined for every billing type.
 Caution:
 The 'relevant for rebate' field must be marked for every billing type you want to update
the business volume valid for rebate. That also applies to the billing types with which
you create the rebate credit memos (e.g. billing type B1 - rebate credit memo).
 Note
 The customers for whom rebate processing is to be carried out must be selected in field
'rebate' in the master record for sales data in billing.
 Define material rebate group
 You define rebate groups in this IMG activity. These group materials together and can
serve as the key field in rebate agreements for the conditions to be assigned
 Recalculate Subtotals For Rebate Processing
 When you reset rebate processing or alter the pricing procedures or pricing, the
subtotal from which you wish to calculate the rebate may not be available in the billing
documents.
 In this step, you can start report RV15B003 which adds the subtotal to the appropriate
billing documents.
 Note
 Afterwards, you must restructure the billing index. (See the related step in this chapter).

Create Billing Index

The rebate index is used internally to settle rebate agreements that have been created
retrospectively and in order to display the drill-down (the billing documents involved) for
rebate agreements.

The rebast index must then be reorganized if you want to change one of the following factors
for rebate processing:

 Creation or inclusion of new accesses for rebate processing

  New rebate relevance of sales organizations

 New rebate relevance of billing types

 New rebate relevance of payers

Actions

 Set the parameters to define the scope of the reorganization.

o You can only select certain billing documents.

o You can delete all entries in the specified selection of billing documents. If
performance is very bad during deletion, contact your database administrator.

 Enter the parameters for the program run.

o Enter the date and time of the first program run.

o Enter the maximum runtime per repetition. After the time specified, the
program stops and is run again a few days later.

o Specify after how many days the program should run again.

Intercompany Billing

During a business transaction in which the sales organization belongs to another company
code than the delivering plant, an intercompany sale from stock is carried out. In this case,
intercompany billing is carried out between both company codes with the help of an
intercompany billing document. Intercompany sales and distribution processing allows a
company to sell goods from a plant which is allocated to another company code.

The system checks the company codes of the sales organization and of the delivering plant and
automatically carries out intercompany billing processing for different outcomes. Two billing
documents are created in this case:

 A customer billing document which is sent from the sales organization to the customer
who receives the goods.

 An intercompany billing document which is sent from the delivering plant to the sales
organization.

The difference between the customer billing document and the intercompany billing document
remains in the selling company as a contribution margin.
To be able to use intercompany billing for the intercompany sale from stock, you must set the
configurations to the following points:

 Specify per sales order type whether intercompany billing is possible.

 Allocate corresponding organizational data for intercompany billing to the plants with
which intercompany sales and distribution processing is to be carried out.

 Specify a customer number to represent the sales organization.

Default Settings

For controlling intercompany sales from stock, the following configurations have been set in
Customizing:

1. Billing type

For the definition of the billing document, the billing type II (intercompany billing) was
included.

2. Condition type

Condition types PI02 for condition rates to be determined in percent and PI01 for
condition rates with fixed amounts have been included for calculating intercompany
billing prices.

3. Access sequences

For carrying out intercompany billing, access sequences PI01 and PI02 have been set up.

4. Table maintenance

The system checks the allowed combinations of sales organization, distribution channel
and plant by means of the table TVKWZ.

 Define Order Types For Intercompany Billing

 In this menu option, you specify for each sales document type whether intercompany
billing is possible for intercompany sale of stock.
 Actions
 Specify the billing type for intercompany billing "IV" for each sales document type for
which you want to use intercompany billing

Assign Organizational Units By Plant

In this menu option, you allocate a sales organization, distribution channel and division to the
plants for which intercompany sales processing is possible. The delivering plant uses these
specifications to process intercompany billing.

Using the specifications which you make here, the delivering plant creates the intercompany
invoice together with the internal customer number of the sales organization which placed the
order.

The internal customer number is specified in the Customizing configuration menu for sales and
distribution in the menu option Sales organization.

Note

For internal processing of the transactions, the same organizational units are maintained for
the plants concerned in stock transport order and intercompany sale of stock. In this case, the
data is maintained for intercompany sale of stock in SD, the data for the stock transport order
in purchasing. For more information on the stock transport order, see the Implementation
Guide for Purchasing in the chapter on the stock transport order (see section "Configure Stock
Transport Orders").

Actions

Allocate appropriate organizational data for inter-company billing to the plants, with which
intercompany sales and distribution processing should be carried out in the fields "Sales
organisation IV", "Distribution channel IV" and "Division IV".

 Define Internal Customer Number By Sales Organization

 In this menu option, you assign an internal customer number for intercompany billing to
your sales organization. In intercompany billing, the intercompany billing document is
created for this customer number which represents your sales organization. The
intercompany billing document is assigned via the internal customer number of your
sales organization.
 Actions
 1. Create a customer number that represents your sales organization.
 2. Enter this customer number for the corresponding sales organization.
 Automatic Posting To Vendor Account (SAP-EDI)
 In this activity, you set up automatic posting to vendor account for intercompany billing
with SAP-EDI direct to financial accounting.
 EDI outbound processing for intercompany billing links to EDI inbound processing for
invoice receipt in FI and posting to vendor account is carried out in the selling company
code.
 prerequisites:
 Before making the settings in Customizing you must create a vendor master record that
represents the delivering company code. This vendor master record must be created in
"Selling company code".
 You also need an output condition record (transaction VV31) for output type "RD04"
and the customers for intercompany billing.
 Customizing settings:
 1. Message type:
 Message type RD04 is set for posting to vendor account in intercompany billing.
(TA:V/040)
 2. Message determination procedure:
 Message determination procedure V40000 is valid for billing type IV.
 3. Message control:
 In the administration of EDI processing, a partner agreement must be defined for
message control of inbound and outbound processing, since sender and receiver data
are needed. The outbound process code is used to initiate a function module version 5
(function module version 3.0 for initiating inbound processing).
 Process code outbound: SD08.
 For further information on settings for messages, see the IMG section "messages".
 4. Outbound processing:
 a) Partner agreement (transaction WE20)
Partner number : Specify customer number IV
Partner type : KU
 b) Message controlling:
Partner number : Customer number IV
Partner type : KU
Partner role : RE
Application : V3
Message type :RD04
Message:
Message category:INVOIC
Message variant: FI
Outbound options:
Outbound code : SD08 INVOIC Intercompany billing,
 c) Outbound parameters:
Outbound options:
Receiver port : e.g. SAPP30 EDI MM development
IDoc cat. : INVOIC01
Basis IDoc cat. : INVOIC01
 5. Inbound processing (transaction SBPT) for customer
 a) Inbound parameters:
Partner number : Specify vendor number
Partner type : LI
Partner functions:
Message category : INVOIC invoice / billing document
 Output variant : FI
Process code :INVF
 6. Check assignment of process code and processing function modules.
Transaction: WE42 >>Basis >> Control>> Process code inbound >> Processing with funct.
modules>>With or w/o ALE
Code :INVF
Identification:idoc_input_invoice_fi (INVOIC FI invoice receipt)
or
code FI03 up to 3.0E
Identification:idoc_input_invoice_fi
 7. Vendor:
A vendor must be assigned per company code and customer for intercompany billing
(transaction WEL1)

Example:
Data:
Delivering company code: 0001
Customer: 0000000001, created in delivering company code
Selling company codekreis: 0099
Vendor: ALECRED01, created om selling company code

Settings:
Application: V3
Logical address 00010000000001
is made up of:
 a) 4 place delivering company code : 0001
 b) 10 place customer number : 0000000001
 Target:
Company code: 0099
Vendor : ALECRED01
 Note
 The logical address must contain 14 digits. If the customer number does not contain 10
digits, zeros must be put before it.
 If the logical address is not correctly maintained in table EDILOGADR, error message: "
Company code could not be determined for intermediate document XXXXX" appears.
 8. Account assignment:
 You can set an indicator that determines whether account assignments are to be copied
from the customer billing document during creation of posting to vendor account in the
selling company code
 This affects the following account assignments:
 9. Projects
 10. Profit center
 11. Cost center
  12. Profitability segment
 13. Business area
 a) Partner Profit Center (delivering profit center)
 The same settings must be made for the internal credit memo.
 Billing Plan
 You can store a detailed billing plan instead of a single billing date at item level in the
sales document during order processing.
 The billing plan specifies the time at which the given amount or percentage rate should
be billed. This form of invoice creation plays an important role, for example, in settling
rental contracts on a periodic basis and in milestone billing for projects with predefined
billing dates.
 Each billing plan has a unique billing plan number which is assigned internally by the
system.
 The following sections describe the settings in Customizing for the billing plan.

Define Billing Plan Types

In this step, you define billing plan types which contain the basic control data for the billing
plan.

In order processing, the billing plan type uses specific rules for date determination, for example,
to propose the period of a billing plan from which the dates of the billing plan can be
determined.

In the standard SAP R/3 System, billing plan types are set up for milestone billing and for
periodic billing. The difference between these two kinds of billing plans is the fact that the total
value to be billed is either distributed between the individual dates of the billing plan, or is
billed periodically as a total value for each date until a predefined end date is reached.

The billing plan type is determined from the document item category and the relevancy for
billing. You make the corresponding allocation in a separate step.

The billing plan type is displayed in the billing plan, but you cannot change it there.

The billing plan type includes the following control data:

 Horizon (periodic billing)

The horizon specifies the last date for periodic billing, up to which dates should be set. It
is always determined from a rule which can be entered in the billing plan type as a
default value. The current date (=CPU date) serves as baseline date for this rule. As a
result, when date determination is carried out again, the horizon is constantly extended
into the future, and the billing dates are also dynamically shifted into the future.
  Reference billing plan number (milestone billing)

For each billing plan type, you can store the number of a billing plan as a reference.
When this billing plan type is used for order processing, the dates are copied according
to this reference, redetermined on the basis of the current rules, and placed in the
billing plan.

 Online order

This field controls whether the billing dates are automatically determined and copied
into the billing plan or whether they must be entered manually.

 In advance (periodic billing)

Here you control, whether billing should be performed in arrears or in advance, for
example, whether rent which is billed on the 15th of every month is billed in arrears.

Requirements

You must define the rules for date determination.

Standard settings

The standard SAP R/3 System contains a billing plan type for milestone billing (01) and for
periodic billing (02). Different overview screens exist for both billing plan types (see the field
'FCODE OvervScrn').

Actions

1. To create a billing plan type you must enter an alphanumeric key with a maximum of
2 digits and a textual description.
2. Maintain the detail screen for the billing plan type by entering the relevant control
data.

 Define Date Descriptions

 In this step, you define date descriptions. These are the textual descriptions for the
respective billing dates in the billing plan. The descriptions are only used for
differentiating between the billing dates and have no controlling function.
 The date descriptions are entered for the date categories and are then found with the
billing plan dates in the order document and printed.
 Example
 In the billing plan, the distinction is made for example between billing dates for rent or
maintenance.
 Actions
  1. Enter an alphanumeric key with a maximum of 4 digits together with a language ID
and textual description for the date description that you want to create.
 2. Enter the date description for the date categories for which you want to use the
description.

Define And Assign Date Categories

In this step, you can assign one or more date categories to each billing plan type or create new
date categories.

The date category controls at billing date level,

o whether the billing date is a fixed date,

o whether and, if necessary, which billing block the billing date has,

o with which billing type the billing date is to be billed,

o the billing rule which specifies how the value to be billed for a date is to be
determined. Billing rule 2 of the standard SAP R/3 System ('Value-based
milestone billing') specifies, for example, that the entire invoice value is
distributed between the dates and a part of the total value is billed for each
date.

The date category also specifies the description for the billing date.

Since you can have several date categories for a billing plan type, you must specify, in a further
step, a default date category for each billing plan type.

Note

The date category 'final settlement' is not proposed in the SAP standard delivery and must be
entered manually in order processing.

As of Release 3.0C, you can, in working with milestone billing, assign milestones to dates in the
billing plan if no network is opened.

It is necessary, however, that you assign milestones manually when maintaining the billing plan.
In order to assign milestones, you must specify a value in the fixed date indicator different from
the initial value. If the additional fixed value (as of Release 3.0C) for fixed

date is empty (''), this assignment is no longer possible.

Requirements
The billing blocks, billing types and date descriptions must be maintained when you enter the
corresponding control data.

Standard settings

The standard SAP System contains date categories for periodic billing and milestone billing.

Actions

1. To create new date categories, enter an alphanumeric key with a maximum of 2

characters together with a textual description.
2. Assign the date category to the billing plan types which should be able to use the date
category.
3. Specify which date category is to be defaulted for which billing plan type.

 Maintain Date Proposals For Billing Plan Types

 The date proposal specifies a sequence of dates which can be used during order
processing as a reference for date determination. The date proposal is only relevant for
the billing plan type Milestone billing (periodic billing = blank).
 When you create a billing plan with milestone billing, the dates are copied according to
the reference, redetermined on the basis of the current rules, and placed in the billing
plan.
 Action
 To maintain the date proposal for milestone billing, go to the detail screen of the date
proposal and select the function 'Maintain dates'.
 Assign Billing Plan Types To Sales Document Types
 As of Release 3.0E, you can define a billing plan at header level valid for all items that
are assigned to it.
 In this step, you assign a billing plan type to a sales document type. This assignment is
necessary if you want to use a header billing plan for a specific sales document type.
 All document items with the same billing plan type (controlled in the item category) are
assigned to the header billing plan. To display this assignment, mark the Header billing
plan field in the item billing plan. This can be reversed manually if you want to define
your own billing plans for specific items. After reversing this assignment, you can
maintain the item billing plan separately.
 Note
 An item which has been partially billed can be detached from the header but no long
attached.
 Recommendation
 Action
 Assign a billing plan type to the sales document types for which you want to use a
header billing plan.
 Assign Billing Plan Types To Item Categories
  In this IMG activity, you assign a billing plan type and billing relevance 'I' (relevant for
order-related billing/billing plan) to the item categories for which you want to create a
billing plan. This assignment is necessary for creating a billing plan for the relevant order
items.
 Standard settings
 In the standard system, item category MVN is configured for periodic billing and item
category TAO is configured for milestone billing.
 Activities
 Specify 'I' for billing relevance and enter a billing plan type for item categories for which
you want to enter a billing plan

Define Rules For Determining Dates

A baseline date (for example, current date, beginning of contract) forms the basis of every date
determination rule. A period to be defined is added to this baseline date.

You define the rules for date determination on the basis of the following ates:

 The possible baseline date is predefined by a fixed value range (for example current
date, beginning of the contract) and cannot be changed.

 You can define the period in any way by specifying a number with a corresponding time
unit.

 If you use a calendar ID to define a rule, the system determines the next possible
workday starting from the baseline date. If you use a calendar ID, you may NOT specify a
period.

Note

in order to define a rule, you must maintain at least one baseline date.

Example

If a date determination rule takes the baseline date to be the contract start date, the period to
be 6 and the time unit to be months, then the system determines the date starting from the
agreement start date plus 6 months.

Actions

1. Enter an alphanumeric key with a maximum of 2 characters together with a textual

description for the rule. The description can, for example, contain the date
determination in short form.
2. Specify the baseline date.
 3. Specify either a period with a time unit or a calendar ID.

 Electronic Data Interchange

 In the steps in this section, you define the configurations necessary for using EDI.
 Using the EDI interface, documents (for example, sales order documents) can be
exchanged by different partners, such as sold-to parties, ship-to parties and so on. An
open interface permits the exchange of incoming and outgoing EDI messages with the
SAP System.
 Incoming EDI messages (for example, inquiries, sales orders, order modifications by the
customer, and shipping notifications) are converted by the respective EDI format (for
example, ANSI X12, EDIFACT) into an intermediate document and archived. The
structure of this intermediate document is defined by SAP and represents an SAP
standard application interface: the same structure is used both for incoming and
outgoing messages. When an incoming EDI message has been converted into an
intermediate document, the intermediate document is converted into an SAP document
(for example, sales order document) by the application. Outgoing EDI messages are
processed in reverse sequence: the application converts the order document into an
intermediate document which is then converted into the respective EDI format and sent
off. The structure is independent of the respective EDI standard (for example, EDIFACT
and ANSI X12).
