paragon sd configuration

110
SD Configuration Document SD Configuration Document Last changed on: Last changed by: XX Team Version: Page 1 of 110

Upload: deepak-chandra

Post on 06-Dec-2015

127 views

Category:

Documents


43 download

DESCRIPTION

SAP SD CONFUIURATION

TRANSCRIPT

SD Configuration Document

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 1 of 110

SD Configuration Document

1 Organisation Structure

Config-ID and Title: SD00001Define sales organisation

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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: Last changed by: XX Team Version: Page 2 of 110

SD Configuration Document

Now, select one sales organisation and click on for entering address and other details.

Last changed on: Last changed by: XX Team Version: Page 3 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 4 of 110

SD Configuration DocumentConfig-ID and Title: SD00002

Distribution channelOrganization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: A channel through which saleable materials or services reach customers.

A distribution channel can be assigned to one or more sales organizations

Transaction Code: SPRO

Menu Path: IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel

Client dependent settings: Yes

Click on the and the below mentioned screen appearsLast changed on: Last changed by: XX Team Version: Page 5 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 6 of 110

SD Configuration Document

Config-ID and Title: SD00003Define Division

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 7 of 110

SD Configuration Document

Click on the and the below mentioned screen appears

Double click on the Define division and below shown screen appears

Last changed on: Last changed by: XX Team Version: Page 8 of 110

SD Configuration DocumentConfig-ID and Title: SD00004

Define Sales officeOrganization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: A channel through which saleable materials or services reach customers.

A distribution channel can be assigned to one or more sales organizations

Transaction Code: SPRO

Menu Path: IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Maintain sales office

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 9 of 110

SD Configuration DocumentConfig-ID and Title: SD00005

Define shipping pointOrganization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 10 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 11 of 110

SD Configuration Document

Complete list of shipping points are attached.

Shp point.xls

Config-ID and Title: SD00006Assign sales organisation to company code

Organization/Area: SD

ERP Responsible: SD Team

File SD_Config.doc

Last changed on: Last changed by: XX Team Version: Page 12 of 110

SD Configuration DocumentName:

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Config-ID and Title: SD00007Assign distribution channel to sales organisation

Organization/Area: SD

Last changed on: Last changed by: XX Team Version: Page 13 of 110

SD Configuration DocumentERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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: IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign distribution channel to sales organisation.

Client dependent settings: Yes

Config-ID and Title: SD00008Assign division to sales organisation

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Last changed on: Last changed by: XX Team Version: Page 14 of 110

SD Configuration DocumentResponsibility: 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: IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organisation.

Client dependent settings: Yes

Complete list of division assignments is attached

Sales org-div.xls

Config-ID and Title: SD00009Setup sales area

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

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

Last changed on: Last changed by: XX Team Version: Page 15 of 110

SD Configuration Documentdistribution channel and division.

Transaction Code: SPRO

Menu Path: IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Setup sales area.

Client dependent settings: Yes

Complete list of sales area is attached

Sales Area.xls

Config-ID and Title: SD00010Assign sales office to sales area

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Last changed on: Last changed by: XX Team Version: Page 16 of 110

SD Configuration DocumentDescription: One sales office can belong to several sales areas at the same time.

Transaction Code: SPRO

Menu Path: IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales office to sales area.

Client dependent settings: Yes

Sales area-sales office.xls

Config-ID and Title: SD00011Assign sales organisation with distribution channel and plant

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Last changed on: Last changed by: XX Team Version: Page 17 of 110

SD Configuration DocumentDescription: 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: IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organisation – distribution channel - plant

Client dependent settings: Yes

List attached

Sales Org-Dist Chn-Plant.xls

Config-ID and Title: SD00012Assign sales area to credit control area

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this step, you assign the sales area with the credit control area.

Transaction Code: SPRO

Menu Path: IMG -> Enterprise Structure -> Assignment -> Sales and Last changed on: Last changed by: XX Team Version: Page 18 of 110

SD Configuration DocumentDistribution -> Assign sales area with the credit control area

Client dependent settings: Yes

Config-ID and Title: SD00013Assign business area to plant and division.

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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 -> Sales and

Last changed on: Last changed by: XX Team Version: Page 19 of 110

SD Configuration DocumentDistribution -> Business Area Account Assignment

Client dependent settings: 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: Last changed by: XX Team Version: Page 20 of 110

SD Configuration Document

plant-div-BA.XLS

Config-ID and Title: SD00014Assign shipping point to plant.

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 21 of 110

SD Configuration Document

Click on to assign the shipping point

Last changed on: Last changed by: XX Team Version: Page 22 of 110

SD Configuration Document

Config-ID and Title: SD00015Define Common distribution channel

Organization/Area: SD

ERP Responsible: SD Team

File SD_Config.doc

Last changed on: Last changed by: XX Team Version: Page 23 of 110

SD Configuration DocumentName:

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Config-ID and Title: SD00016Define Common divisions

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Last changed on: Last changed by: XX Team Version: Page 24 of 110

SD Configuration DocumentHeader

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

Client dependent settings: Yes

Config-ID and Title: SD00017Define Terms of Payment.

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

HeaderLast changed on: Last changed by: XX Team Version: Page 25 of 110

SD Configuration DocumentDescription: 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

Client dependent settings: Yes

Click to define the terms of payment.

Click on this and then click to view details of the payment terms

Last changed on: Last changed by: XX Team Version: Page 26 of 110

SD Configuration Document

List of Payment terms

List of Payment terms.XLS

2 Sales

Last changed on: Last changed by: XX Team Version: Page 27 of 110

SD Configuration Document

Config-ID and Title: SD00019Define Sales Document Types

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: 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: Last changed by: XX Team Version: Page 28 of 110

SD Configuration Document

Config-ID and Title: SD00020Assign Sales Area to Sales Document Types

Organization/Area: SD

Last changed on: Last changed by: XX Team Version: Page 29 of 110

SD Configuration DocumentERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

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

Transaction Code: SPRO

Menu Path: IMG -> Sales and Distribution -> Sales -> Sales Documents Sales Documents Header Assign Sales Area to Sales Document Types

Client dependent settings: Yes

Click on to assign the permitted sales area.

Last changed on: Last changed by: XX Team Version: Page 30 of 110

SD Configuration Document

Double Click on the Assign sales order types permitted for sales area

Last changed on: Last changed by: XX Team Version: Page 31 of 110

SD Configuration Document

sales area-sales order.XLS

Config-ID and Title: SD00021Define Item Categories

Organization/Area: SD

Last changed on: Last changed by: XX Team Version: Page 32 of 110

SD Configuration DocumentERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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: IMG -> Sales and Distribution -> Sales -> Sales Documents Sales Documents Item Define Item categories.

Client dependent settings: Yes

Click on to see the details of the item category.

Last changed on: Last changed by: XX Team Version: Page 33 of 110

SD Configuration Document

Config-ID and Title: SD00026Assign Item Categories

Organization/Area: SD

Last changed on: Last changed by: XX Team Version: Page 34 of 110

SD Configuration DocumentERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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: IMG -> Sales and Distribution -> Sales -> Sales Documents Sales Documents Item Assign Item categories.

Client dependent settings: Yes

Item categories are assigned with the sales order types to make the system understand how the order should work.

Last changed on: Last changed by: XX Team Version: Page 35 of 110

SD Configuration Document

Config-ID and Title: SD00027Define Schedule line category

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Last changed on: Last changed by: XX Team Version: Page 36 of 110

SD Configuration DocumentResponsibility: SD Team Status: Open / Closed

Header

Description:

Transaction Code: SPRO

Menu Path: IMG -> Sales and Distribution -> Sales -> Sales Documents Schedule Lines Define Schedule Line Categories

Client dependent settings: Yes

Click on to define the schedule line categories.

Last changed on: Last changed by: XX Team Version: Page 37 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 38 of 110

SD Configuration Document

Click on the to view the schedule line.

Config-ID and Title: SD00028Assign Schedule line category

Last changed on: Last changed by: XX Team Version: Page 39 of 110

SD Configuration DocumentOrganization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description:

Transaction Code: SPRO

Menu Path: IMG -> Sales and Distribution -> Sales -> Sales Documents Schedule Lines Assign Schedule Line Categories

Client dependent settings: Yes

Click on to assign the schedule line categories.

You assign the schedule line categories with the item categories.

3 Pricing

Config-ID and Title: SD00030Pricing

Last changed on: Last changed by: XX Team Version: Page 40 of 110

SD Configuration DocumentOrganization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: The following sections describe how pricing is controlled

Transaction Code: SPRO

Menu Path: IMG -> Sales and Distribution -> Basic Functions -> Pricing

Client dependent settings: 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 TypesLast changed on: Last changed by: XX Team Version: Page 41 of 110

SD Configuration Document

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 customer-specific 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: Last changed by: XX Team Version: Page 42 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 43 of 110

SD Configuration DocumentCondition tables are client independent

To create a new condition type, double click on the “Maintain condition type” line.

List of Condition type

Cond type DescriptionZABT Abatement

Last changed on: Last changed by: XX Team Version: Page 44 of 110

SD Configuration Document

ZAM6 Rule 6 (3) B

ZASSIN A/R Assessable Va

ZASV Assessable ValZCD Prc - Cr & DrZDIM Manual DiscountZDIP Dis.ZDIS 100% of excise

ZEXPSale price - Exports

ZFRT FreightZHEC Sec Edu Cess

ZINTInt. Co. price AFS

ZMRP MRP - AFSZPR0 PriceZPRC PriceZPRS Cost - Depot

ZRUBBase for tax on cess

ZSAF Sale price - AFSZSFT ST price

ZSINInt. Co. pric NonAFS

ZSLPSale price - Falcon

ZSOS Sale price - SOS

ZSPTSale price - Tyres

ZSSCSocial Security Cess

ZSTFStck Transfer Rate

ZTCS TCSZTOC Tax on CessZTOV Add. tax on VatJCST CSTJLST LSTJEXP ExciseJCES Edu Cess

To maintain the details of a condition type select the condition type and click on .

Last changed on: Last changed by: XX Team Version: Page 45 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 46 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 47 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 48 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 49 of 110

SD Configuration Document

ure

ZCRDRFCr and Dr Note - Fal. & Tyre

ZINCNS ConsignmentZINEXP Export SaleZINFAC Factory SalesZINFAL Falcon SalesZININT Intercompany SalesZINMIS Miscellaneous

ZINRUBIntercompany Rubber sale

ZINSOSPricing proc. sale of service

ZINSTO Stock TransferZINTYR Tyre Sales

ZSMPLSamples & Replacements

ZSTONF Stock Transfer - AFS

To configure the pricing procedure you have to select the pricing procedure and double

click on .

Last changed on: Last changed by: XX Team Version: Page 50 of 110

SD Configuration Document

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 doesn’t 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: Last changed by: XX Team Version: Page 51 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 52 of 110

SD Configuration Document

In this option you specify the determination of pricing procedure for this type of sales document.

Last changed on: Last changed by: XX Team Version: Page 53 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 54 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 55 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 56 of 110

SD Configuration Document

4 Revenue Determination

Config-ID and Title: SD00032Revenue Account Determination

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 57 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 58 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 59 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 60 of 110

SD Configuration Document• Plant

The system determines the revenue account through condition tables.

Last changed on: Last changed by: XX Team Version: Page 61 of 110

SD Configuration Document

The above shown screen shot shows the standard condition tables for determining the revenue account determination.

Last changed on: Last changed by: XX Team Version: Page 62 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 63 of 110

SD Configuration Document

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:

o chart of accounts/sales org./acct. group. cust./acct. group mat./account key

Last changed on: Last changed by: XX Team Version: Page 64 of 110

SD Configuration Documento 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: Last changed by: XX Team Version: Page 65 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 66 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 67 of 110

SD Configuration Document

To define the account determination procedure double click on the line.

Last changed on: Last changed by: XX Team Version: Page 68 of 110

SD Configuration Document

KOFI00 is the standard procedure for account determination.

Usage: C: Account DeterminationApplication: 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: Last changed by: XX Team Version: Page 69 of 110

SD Configuration Document

You define your account keys in this menu option and allocate them to the condition types in the pricing procedures.

Last changed on: Last changed by: XX Team Version: Page 70 of 110

SD Configuration DocumentWith 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: Last changed by: XX Team Version: Page 71 of 110

SD Configuration Document

In this option you assign the account keys with the pricing procedure.

Last changed on: Last changed by: XX Team Version: Page 72 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 73 of 110

SD Configuration Document

1. PRGN

Last changed on: Last changed by: XX Team Version: Page 74 of 110

SD Configuration Document

5. Allocation Run type

Config-ID and Title: SD00035Allocation

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Allocation Run

Transaction Code: J3AS

Menu Path: Arun DetailArun type

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 75 of 110

SD Configuration Document

Double click on the Arun type to display the detailed view.

Last changed on: Last changed by: XX Team Version: Page 76 of 110

SD Configuration Document

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 etcIn 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: Last changed by: XX Team Version: Page 77 of 110

SD Configuration Document

Requirement Selection

Config-ID and Title: SD00035Allocation

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Allocation Run

Transaction Code: J3AS

Menu Path: Arun DetailSelectionRequirement Selection

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 78 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 79 of 110

SD Configuration Document

Stock Selection

Config-ID and Title: SD00035Allocation

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Description: In this section you make settings for Allocation Run

Transaction Code: J3AS

Menu Path: Arun DetailSelectionStock Selection

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 80 of 110

SD Configuration Document

Select the stock selection and click on the .

Last changed on: Last changed by: XX Team Version: Page 81 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 82 of 110

SD Configuration Document

Cross Applications

Config-ID and Title: SD00035Allocation

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Description: In this section you make settings for Allocation Run

Transaction Code: J3AS

Menu Path: Cross applicationsPO Handling

Client dependent settings: Yes

Now select the Define allocation for Stock transport order AFS

Last changed on: Last changed by: XX Team Version: Page 83 of 110

SD Configuration Document

In this section assign the STO order type with the Allocation run type which has been created earlier.

Last changed on: Last changed by: XX Team Version: Page 84 of 110

SD Configuration Document

Set up stock transport order

Config-ID and Title: SD00035Set up Stock Transport Order

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 85 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 86 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 87 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 88 of 110

SD Configuration Document

Assign document type, one step procedure

Last changed on: Last changed by: XX Team Version: Page 89 of 110

SD Configuration Document

Logistics execution

Config-ID and Title: SD00035Logistic Execution (Delivery)

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: 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

Client dependent settings: Yes

Click on the icon .

Last changed on: Last changed by: XX Team Version: Page 90 of 110

SD Configuration Document

In this screen the shipping point is assigned with Shipping conditions, Loading group and plant

Last changed on: Last changed by: XX Team Version: Page 91 of 110

SD Configuration Document

Logistics execution

Config-ID and Title: SD00035Logistic Execution (Delivery)

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Logistics Execution

Transaction Code: SPRO

Menu Path: IMG -> Logistics Execution Shipping DeliveriesDefine Delivery types

Client dependent settings: Yes

Click on the icon .

Last changed on: Last changed by: XX Team Version: Page 92 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 93 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 94 of 110

SD Configuration Document

Logistics execution

Config-ID and Title: SD00035Logistic Execution (Delivery)

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Logistics Execution

Transaction Code: SPRO

Menu Path: IMG -> Logistics Execution Shipping DeliveriesDefine Item categories

Client dependent settings: Yes

Click on the icon

Last changed on: Last changed by: XX Team Version: Page 95 of 110

SD Configuration Document

Double click on the Item categories to define.

Last changed on: Last changed by: XX Team Version: Page 96 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 97 of 110

SD Configuration Document

Logistics execution

Config-ID and Title: SD00035Logistic Execution (Delivery)

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Logistics Execution

Transaction Code: SPRO

Menu Path: IMG -> Logistics Execution Shipping DeliveriesDefine Item category determination in deliveries

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 98 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 99 of 110

SD Configuration Document

Logistics execution

Config-ID and Title: SD00035Logistic Execution (Delivery)

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Logistics Execution

Transaction Code: SPRO

Menu Path: IMG -> Logistics Execution Shipping Copying controlSpecify copy control for delveries

Client dependent settings: Yes

Last changed on: Last changed by: XX Team Version: Page 100 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 101 of 110

SD Configuration Document

To define the header levels select the line and click on

Last changed on: Last changed by: XX Team Version: Page 102 of 110

SD Configuration Document

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: Last changed by: XX Team Version: Page 103 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 104 of 110

SD Configuration Document

6 Billing

Config-ID and Title: SD00036Billing

Organization/Area: SD

ERP Responsible: SD Team

File Name:

SD_Config.doc

Responsibility: SD Team Status: Open / Closed

Header

Description: In this section you make settings for Logistics Execution

Transaction Code: SPRO

Menu Path: IMG -> Sales and Distribution Billing

Client dependent settings: Yes

Click on to define the billing types

Last changed on: Last changed by: XX Team Version: Page 105 of 110

SD Configuration Document

Double Click on the line item to define the billing types

Last changed on: Last changed by: XX Team Version: Page 106 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 107 of 110

SD Configuration Document

To define the relevant copy control, double click on the relevant line item.

Last changed on: Last changed by: XX Team Version: Page 108 of 110

SD Configuration Document

Last changed on: Last changed by: XX Team Version: Page 109 of 110

SD Configuration Document

Item Level Copy Control

Last changed on: Last changed by: XX Team Version: Page 110 of 110