Implementation sequence.. Realtime

[Former Member]

Hello experts ................

what is the Exact sequence in configuration ( implementation project)?

Ex) 1.Org structure.. def/ass, 2) masterdata configuration (Sd part) 3) def.. Sd. docs n Itc n Sdlct n assignment 3) in this way....................

could any body help me out...?

[Former Member]

Hi,

just to add as a general approach, any functionality we want to incorporate into the sap system first thing is identify all the required master data. so we setup the org units / configs / create customer/material master data and then go on with the transactions. We also need to make sure if there is dependent config / assignment required to be made with any other modules before executing scenairios for testing.

You can actually refer the ASAP methodology to understand the full context of implementation.

regards

sadhu kishore

[Former Member]

Hello,

Yes... Organisational tructure will be configured first as per the blue print. Then we can check the consistency of the same by creating master datas, we define and assigne the different documents, item categories, shecdule line categories, copying controls...etc as per the reqirements.

Prase

[Former Member]

Hi,

Visit following links:

http://www.sapfans.com/sapfans/asap/be_05_e.htm

http://www.sap-basis-abap.com/sapsd.htm

http://service.sap.com/bestpractices

http://www.sap-basis-abap.com/sapsd.htm

Regards,

Srilatha.

[Former Member]

The below is an illustration of the sequence from Configuration point of view:

SD Configuration:

Enterprise Structure:

1. Maintaining Sales Organization

Sales Organization is an organizational unit responsible for the sale of certain products or services.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization

2. Assigning Sales Organization to Company Code

This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code

3. Maintaining Distribution Channel

Distribution Channel is the way, in which Products or Services reach Customers.

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

4. Assigning Distribution Channel to Sales Organization

This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization

5. Maintaining Division

Division is a way of grouping materials, products, or services.

IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division

6. Assigning Division to Sales Organization

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

7. Setting up Sales Area

All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.

IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area

8. Assigning Sales Organization- Distribution Channel- Plant

Plant is created ny MM Consultant.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant

9. Define Shipping Points

Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.

IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point

10 Assigning Shipping Point to Plant

This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.

IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant

Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.

11. Defining Common Distribution Channels for Master Data

Use

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels

Transaction Code: VOR1

12. Defining Common Divisions for Master DataUse

The purpose of this activity is to define distribution channels which have common master data..

Procedure

Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division

Transaction Code: VOR2

Account Group

1. Maintain Number Range for Account Group

Use

The purpose of this activity is to control number range of Account Group.

Procedure

Access the activity using one of the following navigation options:

IMG --> Financial Accounting (New)  Accounts Receivable and Accounts Payable  Customer Accounts  Master Data  Preparations for Creating Customer Master Data  Create Number Ranges for Customer Accounts  Select the Icon to maintain Number Range

Transaction Code SPRO

Data to be maintained:

No | From | To | Current No | Ext (Tick in Check Box)

01 | 0000000001 | 0000099999 | 0 | No

02 | 0000100000 | 0000299999 | 0 | No

XX | A | ZZZZZZZZZZ | Yes

2. Assign Number Range to Account Group

Use

The purpose of this activity is to maintain number range of Account Group.

Procedure

Access the activity using one of the following navigation options:

IMG --> Financial Accounting (New)  Accounts Receivable and Accounts Payable  Customer Accounts  Master Data  Preparations for Creating Customer Master Data  Assign Number Ranges to Customer Account Groups

Transaction Code SPRO

Data to be maintained:

Group | Name | Number Range

0001 | Sold-to party | XX

0002 | Goods recipient | XX

0003 | Payer | XX

0004 | Bill-to party | XX

3. Define Account Groups with Screen Layout (Customers)

Use

In this step, you determine the account group of the customer.

Procedure

Access the activity using one of the following navigation options:

IMG --> Financial Accounting (New)  Accounts Receivable and Accounts Payable  Customer Accounts  Master Data  Preparations for Creating Customer Master Data  Define Account Groups with Screen Layout (Customers)

Transaction Code SPRO

The groups indicated below are a few examples. There are many groups in Standard SAP & if we require additional Group, it can be copied from appropriate group & maintained.

Group | Name

0001 | Sold-to party

0002 | Goods recipient

0003 | Payer

0004 | Bill-to party

0005 | Prospective customer

0006 | Competitor

Select Sold-to-party  go to Details  Double Click on General data / Company code data / Sales data. It will take to next screen which details Tab Pages of General data / Company code data / Sales data. Double Click on Tab Page for example: Address, Control, Marketing & so on. Here you can maintain whether the field is to be Suppress, Req. Entry, Opt. entry or Display

Pricing Procedure

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Normal Sales Order Cycle:-

Step 1: Sales Document Type

IMG > Sales and Distribution > Sales > Sales Documents >

Sales Document Header:

1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.

2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.

3. Assign Sales Area To Sales Document Types:

A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.

B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.

Sales Document Item:

1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.

2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category

Schedule Line:

1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2:

IMG > Logistic Execution > Shipping > Deliveries >

1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.

3. Define Number Ranges for Deliveries: Ensure to maintain number range.

Step 3:

IMG > Sales and Distribution > Billing >

1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Number Range For Billing Documents: Ensure to maintain number range.

3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.

Note: Ensure that Copy Control settings are done

Sales Order to Sales Order (QT --> OR): VTAA

Sales Order to Delivery (OR --> LF): VTLA

Sales Order to Billing (OR --> F1): VTFA

Delivery to Billing(LF --> F2): VTFL

Billing to Sales Order (F2 --> RE): VTAF

The configuration differs from scenario to scenario & requirement of the client.

Regards,

Rajesh Banka

Reward point if useful.