sap sd clarified points

[Former Member]

1.Part of the Management Team that is Involved in Preparation of Blue

Print and Business Process, Flow Diagram for identify the gaps to meet

the Business Requirement.

2.Responsible for defining Enterprise Structure including various

Organizational units like Sales Organization Distribution Channel,

Division, Sales Offices, Sales Group, Sales District and Assigning

them to each other so as to Accurately reflect the organization

structure and Sales Area.

3.Designed the SD. Technical Structure Mapped and configured the SAP

Organization Structure from the Stage of Inquiry, Quotation, Sales

Order, to handle various combinations of Business Processes.

4.Material Determination, Material Listing/Exclusion, Item Proposal.

5.Configured Sales Document Types and Assigned to Item Category Groups.

6.Defining Pricing Procedures with Associated Condition Types, Access

Sequences for Automatic Pricing during Sales Order Processing and

Billing Stage.

7.Setting up of Material Pricing Group and Price List Type.

8.Communicate with Client in Building further understanding of the

underlying cause from a Business Process.

9.Continuous interaction with the management to facilitate the to

modify and adopt best Business Practices

10.Escalate any issue as to the inability to meet Client Requirement

to the Team Leader. Strict adherence to the company quality policies

and update the necessary document like Knowledge Base and Transition

Plan.

[Former Member]

<b>Role of Functional Consultant</b>:

A functional consultant evaluates the demands in talking with the customer's representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views.

Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case.

The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts.

The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct.

During go live he assists the technical staff by testing the behaviour of the system.

After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements.

The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense.

Role of a Functional Consultant in an End To End Implementation

When you talk about the role of a Functional consultant in an end to end implementation, I think it won't be possible for me or anybody to define everything but I will try to summarize it:

1. Functional consultant is expected to generate knowledge about the current business process, design current business flows, study current business processes and its complication, in all we can say getting through with current business setup. Flow diagrams and DFD are prepared, most of the time in Vision format, all this forms the part of AS IS document.

2. Everything configured has to be documented as per their categories in the form of predefined templates, these have to be then approved by the team leads or who ever the consultant is reporting to.

3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per my experience in implementation, it is a simultaneous process.

4. Before starting configuring future business processes in SAP, the DFD/ERD are prepared, this documentation is called TO BE, which can be also siad as the result of mapping and gap analysis.

5. Sometimes Functional consultants are also expected to prepare test scripts for testing the configured scenarios.

6. End user manual and user training is also expected from F.Consultants.

The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodlogy, dates and schedules, working hours which have been predicided are formally defined.

ASAP, it won't be possible for me to explain it here, but all I can tell you about it is that it is SAP standard implementation methodology, which SAP prescribes but is not mandatory for any company to follow, such as IBM follow some blue Methodlogy, some companies follow typical SDLC steps, ASAP stands for Accerlated SAP, you can find all the steps on SAP site, through google, reading it from there won't give you a great knowledge about ASAP but will obviously get you to know the definitions of various term.

<b>What is the Difference between Consultant & End users?</b>

SAP consultant role is to build the system, changes & modification/updation in currently installed SAP system for the end users.

SAP End user only use the SAP system just to fetch some info, or to create new thing. So a end user is just using the final product which it is meant for and consultnat design the product/updation and modification.

The roles and responsibilities of end users is working in easy access menu they will not have authorizations of using img settings if they get doubt they will send query to the implemented company and just entering day to day transactions.

<b>Roles and Responsibilities of End User</b>:

Using the software at the end or after the implementation is an End User.

In sap HR , we do come across entire Org Management creation by an end user after the Personnel strucutre is created. OM objects like creation of Org Unit means functional area or dpt , creation Job and Position and its occupancy is with in the limits of an enduser. Initiallly the OM is created by sap consultant . In course of time a new department has appeared in the company of the client .. this has to be created by the enduser rather than depending up on the implementor... similarly new job and position..like this small things are always done by the enduser.

The entire work of OM is purely depends upon the enduser.

After from this running periodical payroll and Ensuring of the Time schedules ( Work Schedules) of each employee is done from sap easy access by an enduser and the show run of payroll everymonth is by the enduser only. Like this lot of roles are there for an end user.

Whatever the problems come across during the enduser utilisation of sap ...that will reach as ticket to the support team

<u><b>SD Configuration</b></u>:

<b>Enterprise Structure</b>:

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

<b>Pricing Procedure</b>

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.

<b>Normal Sales Order Cycle</b>:-

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.

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

Regards,

Rajesh Banka

Reward Suitable Point. By rewarding points, even you earn a point.

[Former Member]

hi,

Thankyou for your posting Sap SD clarified points.

regards,

srinivasan

[Former Member]

hi

You have listed the roles & responsibilities of a sd consultant who had worked on a implementation project.

what is u r requirement ?

the list is self explanatory what are the tasks done by a consultant.

regards

prashanth

[Former Member]

hi,

can u please let us know what is ur requirement exactly

REgards,

Murali