Paragon SD Configuration

SD Configuration Document
SD Configuration
Document
Last changed on:
Last changed by: XX Team
Version:
Page 1 of 110
1 Organisation Structure
Config-ID and Title:
Responsibility:
Organization/Area:
SD00001
Define sales organisation
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
A organizational unit in Logistics that structures the company according

to its sales requirements.
A sales organization is responsible for selling materials and services.
Transaction Code:
SPRO
Menu Path:
IMG -> Enterprise Structure -> Definition -> Sales and

Distribution -> Define, copy, delete, check sales organisation
Client dependent settings:
Yes
Last changed on:
Version:
Page 2 of 110
Now, select one sales organisation and click on

details.
Last changed on:
for entering address and other
Version:
Page 3 of 110
Last changed on:
Version:
Page 4 of 110
Responsibility:
Organization/Area:
SD00002
Distribution channel
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
A channel through which saleable materials or services reach
customers.
Description:
A distribution channel can be assigned to one or more sales

organizations
Transaction Code:
SPRO
Menu Path:

Distribution -> Define, copy, delete, check distribution channel
Yes
Click on the
and the below mentioned screen appears
Last changed on:
Version:
Page 5 of 110
Last changed on:
Version:
Page 6 of 110
Responsibility:
Organization/Area:
SD00003
Define Division
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
An organizational unit based on responsibility for sales or profits from

saleable materials or services
Transaction Code:
SPRO
Menu Path:
IMG -> Enterprise Structure -> Definition -> Logistics General ->
Define, copy, delete, check division
Yes
Last changed on:
Version:
Page 7 of 110
Click on the
and the below mentioned screen appears
Double click on the Define division and below shown screen appears
Last changed on:
Version:
Page 8 of 110
Responsibility:
Organization/Area:
SD00004
Define Sales office
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
A channel through which saleable materials or services reach
customers.
Description:
A distribution channel can be assigned to one or more sales

organizations
Transaction Code:
SPRO
Menu Path:

Distribution -> Maintain sales office
Yes
Last changed on:
Version:
Page 9 of 110
Responsibility:
Organization/Area:
SD00005
Define shipping point
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
The shipping points in your company or edit shipping points that already
exist. In order to adapt the functional scope of a shipping point to the
organization in your company.
Transaction Code:
SPRO
Menu Path:
IMG -> Enterprise Structure -> Define -> Logistics Execution ->
Define, copy, delete, check shipping point
Yes
Last changed on:
Version:
Page 10 of 110
For sales transactions, the system will use the shipping points.
Double click on the shipping points to configure the same. All shipping point codes are
identical to plant codes.
The list of configured shipping point is mentioned.

Last changed on:
Version:
Page 11 of 110
Complete list of shipping points are attached.
Shp point.xls

Organization/Area:
SD00006
Assign sales organisation to
company code
SD
ERP Responsible:
SD Team
File
Last changed on:
SD_Config.doc
Version:
Page 12 of 110
Responsibility:
Name:
Status:
SD Team
Open / Closed
Header
Description:
This establishes a link between the SD and FI systems. A sales

organization belongs to just one company code.
Transaction Code:
SPRO
Menu Path:
IMG -> Enterprise Structure -> Assignment -> Sales and

Distribution -> Assign sales organisation to company code
Yes

Organization/Area:
Last changed on:
SD00007
Assign distribution channel to
sales organisation
SD
Version:
Page 13 of 110
Responsibility:
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Closed
Header
Description:
As many distribution channels as desired can belong to a sales

organization. In addition, a distribution channel can be valid for several
sales organizations.
Transaction Code:
SPRO
Menu Path:

Distribution -> Assign distribution channel to sales organisation.
Yes

Organization/Area:
SD00008
Assign
division
organisation
SD
ERP Responsible:
SD Team
File
Name:
Last changed on:
to
sales
SD_Config.doc
Version:
Page 14 of 110
Responsibility:
SD Team
Status:
Open / Closed
Header
Description:
As many divisions as desired to a sales organization. Any one division

can belong to several sales organizations.
Transaction Code:
SPRO
Menu Path:

Distribution -> Assign division to sales organisation.
Yes
Complete list of division assignments is attached
Sales org-div.xls
Responsibility:
Organization/Area:
SD00009
Setup sales area
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Last changed on:
A sales area can be assigned for any combination of sales organization,
Version:
Page 15 of 110
distribution channel and division.
Transaction Code:
SPRO
Menu Path:

Distribution -> Setup sales area.
Yes
Complete list of sales area is attached
Sales Area.xls
Responsibility:
Organization/Area:
SD00010
Assign sales office to sales
area
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Last changed on:
Version:
Page 16 of 110
Description:
One sales office can belong to several sales areas at the same time.
Transaction Code:
SPRO
Menu Path:

Distribution -> Assign sales office to sales area.
Yes
Sales area-sales
office.xls
Responsibility:
Organization/Area:
SD00011
Assign sales organisation with
distribution channel and plant
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Last changed on:
Version:
Page 17 of 110
Description:
In this step, assign any number of plants to a combination of sales

organization and distribution channel. A plant can be assigned more
than once.
Transaction Code:
SPRO
Menu Path:

Distribution -> Assign sales organisation distribution channel plant
Yes
List attached
Sales Org-Dist
Chn-Plant.xls
Responsibility:
Organization/Area:
SD00012
Assign sales area to credit
control area
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
In this step, you assign the sales area with the credit control area.
Transaction Code:
SPRO
Menu Path:
Last changed on:

Version:
Page 18 of 110
Distribution -> Assign sales area with the credit control area
Yes
Responsibility:
Organization/Area:
SD00013
Assign business area to plant
and division.
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Revenue accounting in Financial Accounting and value postings for

goods movements in Inventory Accounting can be represented
separately for each business area.
Transaction Code:
SPRO
Menu Path:
Last changed on:
Version:
Page 19 of 110
Distribution -> Business Area Account Assignment
Yes
Click on
to do the business area assignment with plant and division.
Click on
to assign the business area with plant and division.
Last changed on:
Version:
Page 20 of 110
plant-div-BA.XLS
Responsibility:
Organization/Area:
SD00014
Assign shipping point to plant.
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Revenue accounting in Financial Accounting and value postings for

goods movements in Inventory Accounting can be represented
separately for each business area.
Transaction Code:
SPRO
Menu Path:
IMG -> Enterprise Structure -> Assignment -> Logistics Execution

Assign shipping point to plant
Yes
Last changed on:
Version:
Page 21 of 110
Click on
to assign the shipping point
Last changed on:
Version:
Page 22 of 110

Organization/Area:
SD00015
Define Common
channel
SD
ERP Responsible:
SD Team
File
Last changed on:
distribution
SD_Config.doc
Version:
Page 23 of 110
Responsibility:
Name:
Status:
SD Team
Open / Closed
Header
Description:
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.
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution -> Master data -> Define common
distribution channels
Yes
Responsibility:
Last changed on:
Organization/Area:
SD00016
Define Common divisions
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Version:
Page 24 of 110
Header
Description:
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.
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution -> Master data -> Define common
divisions
Yes
Responsibility:
Organization/Area:
SD00017
Define Terms of Payment.
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Last changed on:
Version:
Page 25 of 110
Description:
In this 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.
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution -> Master data -> Business
Partners Customers Billing Document Terms of Payment
Yes
Click
to define the terms of payment.
Click on this
Last changed on:
and then click
to view details of the payment terms
Version:
Page 26 of 110
List of Payment terms
List of Payment
terms.XLS
2 Sales
Last changed on:
Version:
Page 27 of 110
Responsibility:
Organization/Area:
SD00019
Define Sales Document Types
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
The sales document types represent the different business transactions

in Sales and perform a central controlling function for the entire sales
order process.
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution -> Sales -> Sales Documents
Sales Documents Header Define Sales Document Types
Yes
Click on
and go to sales document header
Click on
and go to Define document types and click on
List of Order types are mentioned below
Last changed on:
Version:
Page 28 of 110

Organization/Area:
Last changed on:
SD00020
Assign Sales Area to Sales
Document Types
SD
Version:
Page 29 of 110
Responsibility:
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
In this menu option, you allocate the allowed order types to each sales
area group.
Transaction Code:
SPRO
Menu Path:
Sales Documents Header Assign Sales Area to Sales
Document Types
Yes
Click on
to assign the permitted sales area.
Last changed on:
Version:
Page 30 of 110
Double Click on the Assign sales order types permitted for sales area
Last changed on:
Version:
Page 31 of 110
sales area-sales
order.XLS

Organization/Area:
Last changed on:
SD00021
Define Item Categories
SD
Version:
Page 32 of 110
Responsibility:
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Item category defines sales relevant features of document items

including planning, pricing, billing or commission relevance .
Transaction Code:
SPRO
Menu Path:
Sales Documents Item Define Item categories.
Yes
Click on
to see the details of the item category.
Last changed on:
Version:
Page 33 of 110

Organization/Area:
Last changed on:
SD00026
Assign Item Categories
SD
Version:
Page 34 of 110
Responsibility:
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
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
Transaction Code:
SPRO
Menu Path:
Sales Documents Item Assign Item categories.
Yes
Item categories are assigned with the sales order types to make the system
understand how the order should work.
Last changed on:
Version:
Page 35 of 110

Organization/Area:
SD00027
Define Schedule line category
SD
ERP Responsible:
SD Team
File
Name:
Last changed on:
SD_Config.doc
Version:
Page 36 of 110
Responsibility:
SD Team
Status:
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:
Schedule Lines Define Schedule Line Categories
Yes
Click on
to define the schedule line categories.
Last changed on:
Version:
Page 37 of 110
In the schedule lines you assign the movement types, the system will use while the
goods are delivered or taken back. You also mention whether the line item is
relevant for delivery or not.
Last changed on:
Version:
Page 38 of 110
Click on the
to view the schedule line.

Last changed on:
SD00028
Assign Schedule line category
Version:
Page 39 of 110
Responsibility:
Organization/Area:
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:
Schedule Lines Assign Schedule Line Categories
Yes
Click on
to assign the schedule line categories.
You assign the schedule line categories with the item categories.
3 Pricing
Last changed on:
SD00030
Pricing
Version:
Page 40 of 110
Responsibility:
Organization/Area:
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
The following sections describe how pricing is controlled
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution -> Basic Functions -> Pricing
Yes
Condition Tables
In this activity, you define price dependencies. You can make prices, surcharges, and discounts
dependent on almost all the fields in a document. You define these dependencies using the
condition tables. In a condition table, you define the combination of fields for which you can
create condition records.
Condition Types
Last changed on:
Version:
Page 41 of 110
Price elements are represented in the SAP system by condition types. Price elements can be, for
example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in
condition records.
Access Sequence
The access sequence is a search strategy which the SAP System uses to search for condition
records valid for a condition type.
For example, you can define for a price that the SAP System first searches for a customerspecific price and then for a price list price.
Pricing Procedure
A pricing procedure defines how values posted in the SAP system are calculated.
A pricing procedure can consist of the following types of rows:
Base rows, which contain the amount or quantity to which overhead is applied
Calculation rows, which contain a percentage rate to be applied to the base lines
Totals rows, which contain a sum of base amounts and calculated amounts
Define Condition table
Last changed on:
Version:
Page 42 of 110
To create a new condition table double click on the Create condition tables line.
Here you to give the number of the new condition table. SAP has reserved the condition table
number range till 900. The customised condition table should start after 900.
Define Condition type

Last changed on:
Version:
Page 43 of 110
Condition tables are client independent
To create a new condition type, double click on the Maintain condition type line.
List of Condition type
Cond
type
ZABT
Description
Abatement
Last changed on:
Version:
Page 44 of 110
ZAM6
ZASS
ZASV
ZCD
ZDIM
ZDIP
ZDIS
ZEXP
ZFRT
ZHEC
ZINT
ZMRP
ZPR0
ZPRC
ZPRS
ZRUB
ZSAF
ZSFT
ZSIN
ZSLP
ZSOS
ZSPT
ZSSC
ZSTF
ZTCS
ZTOC
ZTOV
JCST
JLST
JEXP
JCES
Rule 6 (3) B
IN A/R
Assessable Va
Assessable Val
Prc - Cr & Dr
Manual Discount
Dis.
100% of excise
Sale price Exports
Freight
Sec Edu Cess
Int. Co. price
AFS
MRP - AFS
Price
Price
Cost - Depot
Base for tax on
cess
Sale price - AFS
ST price
Int. Co. pric
NonAFS
Sale price Falcon
Sale price - SOS
Sale price Tyres
Social Security
Cess
Stck Transfer
Rate
TCS
Tax on Cess
Add. tax on Vat
CST
LST
Excise
Edu Cess
To maintain the details of a condition type select the condition type and click on
Last changed on:
Version:
Page 45 of 110
Condition types can be defined as taxes, discounts, prices etc. This helps the pricing
procedures how to treat the condition types.
Prices are always quantity based.
Discounts can be percentage or fixed amount
Surcharges are percentage based.

The condition type which will be used as an AFS pricing (for e.g. the condition
record which will be maintained with grid value, requirement category etc) should
be marked as AFS condition type.
Last changed on:
Version:
Page 46 of 110
Access sequences are client-independent
To create new access sequences double click on the Maintain Access Sequence line
The access sequences are attached with the condition types.
Last changed on:
Version:
Page 47 of 110
The condition tables are attached in the access sequences for the condition type to pick
up the value.
To attach the condition table select the access sequence and double click on Accesses.
In the above screen shot 10 is the access number and 5 is the condition table.
Exclusive indicator is marked because if the system finds any value in the first access
sequence then the system will not go to the next one.
To find out the fields which is there in the condition table, then select the line and click on
.
Last changed on:
Version:
Page 48 of 110
Clicking on
you can define and assign pricing procedures
To define the pricing procedure, double click on the Maintain Pricing Procedure.
List of Pricing procedures
Proced
Description
Last changed on:
Version:
Page 49 of 110
ure
ZCRDRF
ZINCNS
ZINEXP
ZINFAC
ZINFAL
ZININT
ZINMIS
ZINRUB
ZINSOS
ZINSTO
ZINTYR
ZSMPL
ZSTONF
Cr and Dr Note - Fal.

& Tyre
Consignment
Export Sale
Factory Sales
Falcon Sales
Intercompany Sales
Miscellaneous
Intercompany Rubber
sale
Pricing proc. sale of
service
Stock Transfer
Tyre Sales
Samples &
Replacements
Stock Transfer - AFS
To configure the pricing procedure you have to select the pricing procedure and double
click on
Last changed on:
Version:
Page 50 of 110
Step:
This number determines the sequence of the conditions within a procedure
Cntr: Access number of the conditions within a step in the pricing procedure. During automatic
pricing, the system takes into account the sequence specified by the counter.
Ctyp:
Condition type
Description: Description of the condition type

Fro:
Condition step, the value of which is the basis for percentage surcharges.
To:
Condition step up to which the condition values of the previous steps are totalled.
Percentage surcharges are calculated on the basis of the total.
Man: Marking this denotes whether the condition type has to be entered manually or automatic
while creation of sales orders.
Mdt: Marking this check box denotes that particular condition type is mandatory and the
system doesnt allow to save until and unless that condition type exists in the sales order.
Stat:
Marking this field denotes that the value of the condition type will not be posted to FI.
P:
Controls issue of condition lines when printing documents such as order confirmations or
invoices.
SubTo: Controls whether and in which fields condition amounts or subtotals (for example, a
customer discount or the cost of a material) are stored.
Reqt:
A possible requirement would be, for example, that a difference should be made between
document currency and local currency.
AltCty: Alternative formula to the formula in the standard system that determines a condition.
Last changed on:
Version:
Page 51 of 110
AltCBV: Formula for determining the condition basis as an alternative to the standard.
ActKy: The account key enables the system to post amounts to certain types of revenue
account.
Accrls: With the aid of the account key, the system can post amounts to certain types of accruals
accounts.
Determines which pricing procedure the system should apply when you create a sales
document for the customer
Last changed on:
Version:
Page 52 of 110
In this option you specify the determination of pricing procedure for this type of sales
document.
Last changed on:
Version:
Page 53 of 110
In this section you assign the document pricing procedure with the sales order types. On
the basis of that the system will up the appropriate pricing procedure while creation of
sales orders.
Last changed on:
Version:
Page 54 of 110
In this option you define the which pricing procedure the system should pick up with the
combination of sales area, document pricing procedure and customer pricing procedure.
Last changed on:
Version:
Page 55 of 110
Last changed on:
Version:
Page 56 of 110
4 Revenue Determination
Responsibility:
Organization/Area:
SD00032
Revenue
Determination
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
Account
SD_Config.doc
Open / Closed
Header
Description:
A process to establish the revenue accounts to which prices,

discounts, and surcharges are posted.The system uses
conditions to determine the appropriate accounts. the control of
revenue account determination for transferring billing values from
the SD module to the FI module. Revenue account determination
is carried out using the condition technique.
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution -> Basic Functions -> Account
Assignment / Costing
Yes
Last changed on:
Version:
Page 57 of 110
Click on
to define the revenue account determination
To determine the revenue account the system checks the account assignment groups in the
material master as well as in the customer master.
Last changed on:
Version:
Page 58 of 110
A group of materials with the same accounting requirements is maintained in the material account
assignment group. This is used by the system when creating an accounting document from a billing
document to determine the revenue or sales deduction account.
Last changed on:
Version:
Page 59 of 110
Account assignment group for the customer is the group to which the system automatically posts
the sales documents. The system uses the account assignment group as one of the criteria
during the automatic determination of revenue accounts. The system automatically proposes
the account assignment group from the customer master record of the payer.
In this menu option, you define the dependencies of revenue account determination. To do this,
you can store the combination of criteria on which account determination should depend in an
account determination table.
You can select the following criteria for an account determination table:
Condition type
Chart of accounts
Account group customer
Account group material
Account key
Sales organization
Distribution channel
Last changed on:
Version:
Page 60 of 110
Plant
The system determines the revenue account through condition tables.
Last changed on:
Version:
Page 61 of 110
The above shown screen shot shows the standard condition tables for determining the revenue
account determination.
Last changed on:
Version:
Page 62 of 110
Recommendation: It is recommended that the standard condition tables should be used until
and unless there is a very specific business requirement to create a customised condition table
for determining revenue account.
In this section you define a new field for determining revenue if the field is not available as
shown in the below screen shot.
Last changed on:
Version:
Page 63 of 110
In this menu option, you define access sequences and account determination types for automatic revenue
account determination.
Using the access sequence, you define
with which condition tables the SAP System is to access condition records
in which sequence the condition tables are to be read
with which field contents the condition records are to be read
In the account determination type, you define the control data access sequence and validity date.
Default settings
Five access sequences are defined in the standard SAP R/3 System, for example, the access
sequences:
chart of accounts/sales org./acct. group. cust./acct. group mat./account key
Last changed on:
Version:
Page 64 of 110
o
chart of accounts/sales org./account keys
In the standard SAP R/3 System, an account determination type is stored with the key "KOFI".
With these entries, you can initiate automatic account determination to be carried out by the SAP System.
Last changed on:
Version:
Page 65 of 110
The standard access sequence is called KOFI. All the condition tables are attached to
this access sequence.
Recommendation: It is recommended to use the standard access sequence for determining of
revenue account.
To define the condition tables in the access sequence select the access sequence and
click on
To view the fields of the condition tables select the condition table and click on
Last changed on:
Version:
Page 66 of 110
In this menu option you define your account determination procedures and allocate them to the
billing types.
In an account determination procedure, you define the sequence in which the SAP System
should read the account determination types used for revenue account determination.
You allocate the account determination procedures to the billing types for which a corresponding
account determination is to be carried out.
Last changed on:
Version:
Page 67 of 110
To define the account determination procedure double click on the line.
Last changed on:
Version:
Page 68 of 110
KOFI00 is the standard procedure for account determination.

Usage: C: Account Determination
Application: V: Sales and Distribution
Recommendation: It is recommended that the standard procedure should always be used

for account determination.
In this option, you define the assignment of account determination with the Billing types (Invoice
document types).
Last changed on:
Version:
Page 69 of 110
You define your account keys in this menu option and allocate them to the condition types in the
pricing procedures.
Last changed on:
Version:
Page 70 of 110
With the account keys, you group together similar accounts in financial accounting. Using the
account key, the SAP System finds the desired G/L accounts.
This way you can allocate a separate account key to each condition type within a pricing
procedure to implement detailed revenue account determination.
For example, you can allocate a freight condition to a freight revenue account, or a surcharge for
packaging costs to a corresponding account for packaging revenues
As mentioned earlier (Pricing Procedure), the account keys are the keys with which the system
posts the value to the FI.
Last changed on:
Version:
Page 71 of 110
In this option you assign the account keys with the pricing procedure.
Last changed on:
Version:
Page 72 of 110
In this menu option, you allocate G/L accounts for revenue account determination. You have to
make the allocation for every access sequence you have defined beforehand.
A variety of criteria is valid for a G/L account, depending on the key combination. For the key
combination "Customer account determination group/Account key" a G/L account depending
upon the following criteria, for example, is given:
Application (key for SD application)
Account determination type
Chart of accounts (from the module FI)
Sales organization
Customer account determination group
Account key
Double click on one of the condition table and then you can assign the G/L accounts
In this there are 1 chart of accounts.

Last changed on:
Version:
Page 73 of 110
1. PRGN
Last changed on:
Version:
Page 74 of 110
5. Allocation Run type
Responsibility:
Organization/Area:
SD00035
Allocation
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
In this section you make settings for Allocation Run
Transaction Code:
J3AS
Menu Path:
Arun DetailArun type
Yes
Last changed on:
Version:
Page 75 of 110
Double click on the Arun type to display the detailed view.
Last changed on:
Version:
Page 76 of 110
Here, you can define your own set of validations like at the time of Allocation run system should
not consider or system should select the sales order stock also etc
In the requirement check it has been defined that the system should not consider the sales order
which has been blocked for credit.
Last changed on:
Version:
Page 77 of 110
Requirement Selection
Responsibility:
Organization/Area:
SD00035
Allocation
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
J3AS
Menu Path:
Arun DetailSelectionRequirement Selection
Yes
Last changed on:
Version:
Page 78 of 110
Here customized rule type can be defined where by the system will not only consider the
sales orders but also another type for which customizing is done.
.
Last changed on:
Version:
Page 79 of 110
Stock Selection
Responsibility:
Organization/Area:
SD00035
Allocation
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Description:
Transaction Code:
J3AS
Menu Path:
Arun DetailSelectionStock Selection
Yes
Last changed on:
Version:
Page 80 of 110
Select the stock selection and click on the
Last changed on:
Version:
Page 81 of 110
Select the stock selection and double click on the allowed segments. The ZSMT stock
selection has been created for the allocation run for Stock transport order.
In the above screen we have only selected CLABS and KALAB, this s because at the
time of allocation run the system will check the unrestricted use stock (CLABS) and for
MTO scenario system will only check the stock(KALAB) assigned at the sales order.
Last changed on:
Version:
Page 82 of 110
Cross Applications
Responsibility:
Organization/Area:
SD00035
Allocation
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Description:
Transaction Code:
J3AS
Menu Path:
Cross applicationsPO Handling
Yes
Now select the Define allocation for Stock transport order AFS
Last changed on:
Version:
Page 83 of 110
In this section assign the STO order type with the Allocation run type which has been
created earlier.
Last changed on:
Version:
Page 84 of 110
Set up stock transport order
Responsibility:
Organization/Area:
SD00035
Set up Stock Transport Order
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Description:
In this section you make settings for Stock Transport Orders
Transaction Code:
SPRO
Menu Path:
Materials ManagementPurchasingPurchase Order Set up

stock traport order
Yes
Last changed on:
Version:
Page 85 of 110
5
Click on
to define the shipping data for plants.
System displays all the plants which have been created in the system.
Last changed on:
Version:
Page 86 of 110
Double click on the plant code and system displays the below screen
Define the sales area for which the stock transport will be created.
Create the plant as a customer in the golden master client with the sales area which you
mention in the above screen.
Last changed on:
Version:
Page 87 of 110
Assign delivery type with checking rule
In the above screen the PO type is assigned with supplying plant, delivery type and
checking rule.
Last changed on:
Version:
Page 88 of 110
Assign document type, one step procedure
Last changed on:
Version:
Page 89 of 110
Logistics execution
Responsibility:
Organization/Area:
SD00035
Logistic Execution (Delivery)
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
In this section you make settings for Logistics Execution
Transaction Code:
SPRO
Menu Path:
IMG -> Logistics Execution Shipping Basic shipping

functionsShipping point and goods receiving point
determination Assign shipping point
Yes
Click on the icon
Last changed on:
Version:
Page 90 of 110
In this screen the shipping point is assigned with Shipping conditions, Loading group and
plant
Last changed on:
Version:
Page 91 of 110
Logistics execution
Responsibility:
Organization/Area:
SD00035
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:
IMG -> Logistics Execution Shipping DeliveriesDefine

Delivery types
Yes
Click on the icon
Last changed on:
Version:
Page 92 of 110
Last changed on:
Version:
Page 93 of 110
Last changed on:
Version:
Page 94 of 110
Logistics execution
Responsibility:
Organization/Area:
SD00035
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:

Item categories
Yes
Click on the icon
Last changed on:
Version:
Page 95 of 110
Double click on the Item categories to define.
Last changed on:
Version:
Page 96 of 110
Last changed on:
Version:
Page 97 of 110
Logistics execution
Responsibility:
Organization/Area:
SD00035
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:

Item category determination in deliveries
Yes
Last changed on:
Version:
Page 98 of 110
Last changed on:
Version:
Page 99 of 110
Logistics execution
Responsibility:
Organization/Area:
SD00035
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:
IMG -> Logistics Execution Shipping

controlSpecify copy control for delveries
Yes
Last changed on:
Version:
Copying
Page 100 of 110
The copy control of delivery is maintained in the combination of sales document type and
delivery type. The copy control is configured in 2 levels mentioned below
Header
Item
Last changed on:
Version:
Page 101 of 110
To define the header levels select the line and click on
Last changed on:
Version:
Page 102 of 110
To define the item level, select the target and source document type and click on
Select the appropriate item category and click on
Last changed on:
Version:
Page 103 of 110
Last changed on:
Version:
Page 104 of 110
6 Billing
Responsibility:
Organization/Area:
SD00036
Billing
SD
ERP Responsible:
SD Team
SD Team
File
Name:
Status:
SD_Config.doc
Open / Closed
Header
Description:
Transaction Code:
SPRO
Menu Path:
IMG -> Sales and Distribution Billing
Yes
Click on
to define the billing types
Last changed on:
Version:
Page 105 of 110
Double Click on the line item to define the billing types
Last changed on:
Version:
Page 106 of 110
Last changed on:
Version:
Page 107 of 110
To define the relevant copy control, double click on the relevant line item.
Last changed on:
Version:
Page 108 of 110
Last changed on:
Version:
Page 109 of 110
Item Level Copy Control
Last changed on:
Version:
Page 110 of 110

Paragon SD Configuration

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Paragon SD Configuration

Enviado por

Direitos autorais:

Formatos disponíveis

SD Configuration Document

Last changed on:

Last changed by: XX Team

A organizational unit in Logistics that structures the company according

IMG -> Enterprise Structure -> Definition -> Sales and

Client dependent settings:

Last changed on:

Last changed by: XX Team

Now, select one sales organisation and click on

Last changed on:

Last changed by: XX Team

for entering address and other

Last changed on:

Last changed by: XX Team

A distribution channel can be assigned to one or more sales

IMG -> Enterprise Structure -> Definition -> Sales and

Client dependent settings:

and the below mentioned screen appears

Last changed on:

Last changed by: XX Team

Last changed on:

Last changed by: XX Team

An organizational unit based on responsibility for sales or profits from

Client dependent settings:

Last changed on:

Last changed by: XX Team

and the below mentioned screen appears

Last changed on:

Last changed by: XX Team

A distribution channel can be assigned to one or more sales

IMG -> Enterprise Structure -> Definition -> Sales and

Client dependent settings:

Last changed on:

Last changed by: XX Team

Client dependent settings:

Last changed on:

Last changed by: XX Team

The list of configured shipping point is mentioned.

Last changed by: XX Team

Complete list of shipping points are attached.

Config-ID and Title:

Last changed on:

Last changed by: XX Team

This establishes a link between the SD and FI systems. A sales

IMG -> Enterprise Structure -> Assignment -> Sales and

Client dependent settings:

Config-ID and Title:

Last changed by: XX Team

As many distribution channels as desired can belong to a sales

IMG -> Enterprise Structure -> Assignment -> Sales and

Client dependent settings:

Config-ID and Title:

Last changed on:

Last changed by: XX Team

As many divisions as desired to a sales organization. Any one division

IMG -> Enterprise Structure -> Assignment -> Sales and

Client dependent settings:

Complete list of division assignments is attached

Config-ID and Title:

A sales area can be assigned for any combination of sales organization,

Last changed by: XX Team

IMG -> Enterprise Structure -> Assignment -> Sales and

Client dependent settings:

Complete list of sales area is attached