interview Q&A

[Former Member]

What is condition type ? what are the important fileds in condition type?

Why access sequence is required in a condition type?

What are the roles & responsibilities of SD consultant ?

Phases of implementation ? where the functional consultant involves in the project?

What is the Business scenario of your client?

What is MTO( Make-To-Order) and ATP(Available-To-Promise)?

When company wants to upgrade from SAP-R/3 4.6c to SAP-R/3 4.7EE? what could be the changes?

What are the configuration changes in billing document?

What is output determination?

What is functional specification? How its format will be?

Before go live who will do the testing?

How and who will give the enduser training ? and end user traing consists of?

Client wants to maintain certain price and discount for first 3 orders only and from the next order price is normal? Where can we do this configuration?

What are requisites for doing the collective delivery?

How the intercompany sales done?

What is the item category for third party sales ? explain the third party sales process?

What is BOM?Explain?

can anyone please answers these questions in detail.

My email id :loloravi@gmail.com,saratmatturi@lycos.com

Reagards

Parasad

[Former Member]

condition type is the basic primary pricing element for the business such as base price discountf frieght et

access sequence is the search strategy for finding the condition record for the condition type

[reazuddin_md]

Prasad,

So many q's at a time,Testing patience of SDNers.

By seeing ur q list.Everyone will think before they post the answer.

Better post q's 3-5 at a time.Dont post questionnaire.

Will try to answer few q's.

BoM: Combination of products together known as BoM.

<b>https://www.sdn.sap.com/irj/sdn/profile?userid=3558505

https://www.sdn.sap.com/irj/sdn/profile?userid=3558505</b>

Phases of Implementation:

<b>https://www.sdn.sap.com/irj/sdn/profile?userid=3558505</b>

Client wants to maintain certain price and discount for first 3 orders only and from the next order price is normal? Where can we do this configuration?

<b>Condition update & Condition supplement</b>

How the intercompany sales done?

<b>https://www.sdn.sap.com/irj/sdn/profile?userid=3558505</b>

What are requisites for doing the collective delivery?

Criteria:

<b>Shipping point

Deliery date

Ship to party

Incoterms</b>

What is the item category for third party sales ? explain the third party sales process?

Item cat:TAS

Sales order- VA01 --raised by the customer for which we dont have the stock

PR-ME53N- based on item cat,system automatically generate PR

PO-ME21N- wrt to PR purchasing org will raise PO to the vendor

MIGO-Goods Receipt - Vendor supply the goods and we receive these goods

MIRO-Invoice Receipt - after receivign goods vendor sends invoice to the company

VL01n-Delivery to customer-received goods will be delivered to the customer

VF01-Billing to customer -Company issues invoice to the customer

*Hope it helps

[Former Member]

Dear pokuru prasad,

You can get the answer of most of your queries in www.sap-img.com.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details

[Former Member]

<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.

It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

<b>Roles & Responsibility 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>Phases of Implementation</b>:

Phase 1: Project Preparation - The purpose of this phase is to provide initial planning and preparation for your SAP project.

Phase 2: Business Blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run its business within the SAP System. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. The Business Blueprint document represents the business process requirements of the company. It is the agreed statement of how the company intends to run its business within the SAP System.

Phase 3: Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope).

Phase 4: Final Preparation - The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.

Phase 5: Go Live & Support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.

Additionally:

Some additional Infomation on ASAP methodology:

Phase 1 - Project Preparation

Change Charter - Goals and objectives of Organizational Change&#61550; Management

Project Plan - This is a first cut focusing on milestones and&#61550; Work Packages; details to come.

Scope - Sets the initial definition of the&#61550; project; input from sales cycle.

Project Team Organization - Sets the who&#61550; of the project: Standards & Procedures - Sets the why and how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities

Cutover Plan - The details of how to move to the production environment and go live

Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

<b>For Scenarios, check the link as below</b>:

Link: http://help.sap.com/

Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.

Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on ...........

Most of your questions will be answered in the link above.

Regards,

Rajesh Banka

Reward suitable points.

• How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).