Вы находитесь на странице: 1из 12

Tips for interview: How to face.

Important Tips for Interview for SAP SD


Let me share some important tips for interview for SAP SD:

1. Please be through with the projects you have mentioned in your resume.
2. Remember all the versions you have worked upon.
3. If your projects are in Indian scenario be thorough with CIN/Excise VAT and pricing
procedure.
4 For offshore client specially in Europe and NASA prepare yourself for Warehouse/Lean
warehouse
5. Third party billing / Intercompany / Make to order are important topics.
6. Cost booking that is accounting enteries after PGI and Billing should be known to you.
7. Mug up all the determinations.
8. Remember your last ticket.
9. Have general awareness about ALE/EDI/IDOC, as this provides added advantage. (not
very tough)
10. Please be through with your basics, the process, the pricing and the master data.
11. People who are thorough with route, transportation, shipping always have an added
advantage.

The MOST IMPORTANT THING:

Do not try to fool your interviewer, say exactly and only what is asked do not show your
excitement and do not speak too much if you know the topic too well, and say a straight NO
if you have not worked on something, or don't know about something, pls pls pls don't not go
for flukes otherwise you will end up in soup.

What I understand is most of the companies especially in the US are looking for a
candidates with
1) good communication skills (SAP is all about interacting with the client, users and
team)
2) good business knowledge
3) are you able to convince the client

That comes in next round when you are interviewed to be deputed for any US/Europe project,
in this round take care of the
following:
1. Speak slow, I mean normal, because usually Indians speak english too fast.
2. Listen to them carefully, if you are not able to understand their question request them to
repeat it, rather than assuming it to be something else and giving a wrong reply.
3. Again I should repeat prepare yourself for warehouse, I mean even general knowledge will
help.
4. Say a straight no when you don't know or have not worked on the topic.
5. Always be strong on SD MM FI integrations
What the job responsibilites would be for the Support Consultant? If the Consultant is
working in Offshore Support, How the business interaction would be there between the
Consultant and Customer? How the Customer Queries were handled successfully
sitting from his location.

Job responsibility of a Support consultants is to handle routine tickets, which can be incident
(routine problems), change tickets (need configuration change, therefore a change request),
normally a support consultant can only advice a change but can't do it , because there is
always a change advisory board on client end to evaluate and implement the adviced change.

Business intercation between users and customer can be through mail box utilities, outlook,
even telecons and some companies also allow chat.

Usually the customer provides with the number of the document and client/company code
and other necessary info. about the process which is facing problem, the consultant tracks the
project by logging in to development server and search out for causes, the solution is then
sent to user, maybe with snapshot if required.

For those people who asks for tickets:


1. Tickets are normally raised by end user and carry a priority.
2. Those who are asking SAP gurus to tell them about tickets, pls note that most of the
problems except for the basic questions discussed in this group are the tickets themselves,
tickets are nothing but the routine incidents the SAP consultants get, if you regularly read the
mails in the group you will soon start recognizing tickets.

And the most important thing "Believe in yourself and God, as there is always somebody
there to help you".

What is the team size? Duration of the project.

Hardly the team of the sd will be 4 to 5 and entire team of the project will be around 20-24
(all modules like fi/co, sd, mm, pp, hr, qm, pm). If its big project, it will be around 40. Team
size means the employees who you are working on sap r/3 implementation.

For the project completion it will take around 8-10 months to get into golive. After that, post
implementation for 3 months. After that supporting it depends as project time line for every
company is different. *-- Suresh Kumar

SAP SD Interview Questions


Following are some SD Interview questions that might be asked.
1. What is the purpose of
• Text determination

In a business process it is essential that business partners exchange the


information throughout the logistics chain. In Sales and Distribution the
exchange of information is supported by Text
Any Texts in Masterial Master/Material Determination/Order/Delivery , etc is
meant to convey messages to the subsequent documents for compliance. e.g.
"Give Top Priority" message mentioned in Order is meant for Production
Dept.

• account determination

Account determination: For transferring financial and costing information to


proper financial docs.

Account Determination:is integration between Finance and SD. The A/P along
with Account Keys need to be allocated accordingly with combination of
Account Determination Group for Customer and Material if required.

• partner determination

Partner determination: For determing who is is legally resposible for Account


Recievable, who the goods are going to and whatever else you waana drive
through this functionality. It is to identify which type of Partner it is so that if
required for same Customer different Partner Functions may be required e.g
Only One Sold To Party per Customer. More than One Ship to Party/ Bill to
Party/ Payer possible. Accordingly different Masters will have to be created.
Useful for despatch of Material in case of Ship to Party, sending Bill in case of
Bill to Party and payment follow up/Dunning in case of Payer.

• output determination : Output determination: What kind of output does a


sales/delivery/billing document create and who gets it, where?. For example A
partner might get an EDI notification for a sales order just confirmed, whereas
a financial/leasing company gets the invoice. What type of Output (Fax/Mail,
etc) is required, where and in what Format (ABAP Customisation may be
required in some cases especially Invoices).

• storage location determination

Storage Location Determination: depends on Plant, Shipping Point and


Storage Conditions

2. What are the five imp fields to be maintained in account determination

Five fields for Account Determination are:

1. Sales Organisation,
2. Distribution Chanel,
3. Chart of Accounts,
4. Account assignment group for Customer & material
5. Account Keys.
4. What is meant by transfer of data from legacy code to sap

What it means is you want to transfer the entire customer and materials and all other
information from Older (legacy system) to new SAP system. You can do it using many tools,
most noticeably MDMs. Before installation of SAP, Data maintained by Company is called
Legacy Data. At the time of installation, it is required to transfer Data from Legacy to SAP
like Masters (Material/Customer, etc). It can be done in various ways like BDC, LSMW, etc.

What do you do really in pricing determination, and what are the main differences
between one pricing procedure determination to the others, which data control these
differences.

Pricing is determined by combination of

1. Sales Organisation,
Sales area=1+2+3
2. Distribution Channel,
3. Division,
4. Customer Pricing Procedure and
5. Document Pricing Procedure.

6. What type of reports generally a support consultant maintain and report

Depends on Customer requirements.

8. What is the purpose of shipping point determination not menu path

So that Shipping Point is determined automatically once the settings for the same are done.

9. What and where types of copy controls we change

Copy Control: is basically meant so that Data is copied from preceding Document to
subsequent one. What subsequent Document is required is to some extent determined by
Customer Requirements as well as Document Types. e.g. In general case of Standard Order,
it will be Copy Control (Order to Delivery) from OR to LF .

Type of copy controls:

Copy control is maintained to execute the subsequent document when created with
reference to the source document.

There are 3 type of copy control and they have some sub types.

1. Copy control for Sales document- it has 1 sub type i.e


sales docu. To sales doc.

2. Copy control for Delivery document – it has 1 types –

sales docu to dely document

3. Copy control for Billing


document- it has types-
Sales doc. To billing docu,
Dely document to billing document,
Billing document to billing document.

10. How to and where to maintain copy controls


Copy control: When we create document with reference, the data gets copied from
the reference document to the subsequent document (Or from source document to
target document) and to enable this we must maintain copy control between these
documents.

The copy control is maintained between (>)

Sales document QT > OR

Item category AGN > TAN

Sch. Cate BN > CP

Types of Copy control:

1. Copying control for sales document


a. Sales document to sales document

Eg: In to QT, or QT to OR

b. Billing document to sales document

Eg:Returns or Invoice correction request

2. Copying control for delivery document

Here we maintain copy control for header and item levels only as the delivery
document do not have schedule lines.

Sales Document Delivery document


Or LF
Ro Lf
CS DV
Re Lr

3. Copying control for Billing document


a. Sales document to billing document

Sales Document Billing document


CS (cash sales) BV
Cr (credit memo reqst) G2
Dr (Debit memo reqst) L2

b. Delivery document to Billing Document

Delvy Document Billing document


LF F2
LO F2
LR RE

c. Billing document to billing document

Billing Document Billing document


F2 S1
L2 S1
G2 S2
RE S2
F2 G2
F2 L2

In short: copy control is maintained to execute the subsequent document when


created with reference to the source document.

There are 3 type of copy control and they have some sub types.

4. Copy control for sales document- it has 1 sub type i.e sales docu. To sales doc.
5. Copy control for delivery document – it has 1 types – sales docu to dely document
6. Copy control for billing document- it has types- sales doc. To billing docu, dely
document to billing document, billing document to billing document.

11. What is purpose of maintaining common distribution channels and common


divisions

Common Distribution Channel and Common Divison are maintained so that if any
master data like customer or material maintained with respect to one distribution
channel can be used in other DCh. It prevents the multiplication of master records.

Eg: A customer is created for say sales area 1000/20/00 then the same customer can
be used in sales area 1000/30/00 if we maintain 20 as common distribution channel.
Hence no need for extending the customers...the same for materials also.

What is the difference between the Avaialbility check 01 (Daily requirement) and 02
(Individual Requirement) in material master?

01 and 02 are the checking group. Availability check is carried out with the help of these
checking group and checking rule. Checking group 01 and 02 are maintained on the material
master.

01 - Individual requirement -For this system generates transfers the requirement for each
order to the MRP .So that MM can either produce or procure.

02- Collective requirement.-In this all the requirements in a day or in a week are processed at
a time. System stores all requirements and passes on to the MRP in MRP run.In this system
performance is high however you can not do the backorder processing whereas in other you
can do.

Some SAP SD Interview Questions 2


Some of the interviewed questions and answers are as follows:

What is the movement type you used in consignment process?


### 632, 633, 634, 631

Can team size be 40 in a project? Is there any generalized team size no. for any project?
If we tell my team size is 40 in that what no. we can say sd people are?
## Team size cant be forty, Theres no genralized size of team. Never
40 sd consultants work together on same project.

What is ALE?
## Application Linking and Enabling - Generally ABAPers work on it.
What is meant by condition technique: can we say it is the combination of condition
types, access sequence and condition tables?
## yes

Where do we can find pricing procedure indicator in sd ?


## Pricing procedure is where we maintain all Conditions (like PR00, K004, mwst, kp00,
etc) v/08

Where do we assign calender in the master records?


## In IMG screen Global Settings.

What is the importance of customer account groups?


## We maintain the customer account to maintain payment terms and incoterms. Lets say, if
SP is only booking order but the goods should deliver in foreign country and for which SP is
not going to bare the excise and other taxes then the SH party or payer will take the
responsibity then the tax is calculated based on account groups.

What are incoterms? Where do we fix them? Where do you find in regular process?
## Incoterms or international comm. terms and u find in CMR (Customer Master Records) -
Sales area Data - billing Tab.

How can you make some of the fields as key field in generic tables?
## Some fields in all tables have a indicator on it.To see, then go to SE11, display VBAK, u
will find MANDT on top, if you see after description 2 tick marks, those are key fields.
Gernerally, these key fields are used in writing any Program or Interface. The key fields will
extract data of non key fields .

What is the standard group condition routine in condition type, what is its importance?
## Its better u read Group Conditions in PR00.

How do you control entry possibility of condition values at order through condition type
settings?
## You can maintain the maximum and minimum value for all conditions.

What are the customizing settings in pricing procedure for tax condition type?
## Check out the standard pricing procedure RVAA01 - MWST.

A bunch of data need to be imported. A huge no.of creations are required, how it is
possible in SAP?
## thru LSMW, BAPI.

What is the difference between PGI cancellation and returns order?


## PGI cancellation is done before the transportation of goods. But return order means
its already transported reached customer during transit if materil is spoiled or broke or the
goods r not delivered as per customer requested date.then customer send the goods baack to
company.

What is the integrated areas in SD AND FI, SD AND MM, SD AND PP in both
implementation and support projects?
## SD & FI - Possible in Account Determination, for posting the conditions to revelant G/l
account like all prices goes to one particular g/l account. Also in Credit Management, Taxes.

SD & MM - Possible in Batches, Material Requirement Planning.

SD & PP - Possible in Material Requirement planning.

Link Between SAP SD, MM & FI

Explain What Is IDOC


Explain to me about Idoc?

IDoc (for intermediate document) is a standard data structure for electronic data interchange
(EDI) between application programs written for the popular SAP business system or between
an SAP application and an external program. IDocs serve as the vehicle for data transfer in
SAP's Application Link Enabling (ALE) system.

IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-
contained text file that can then be transmitted to the requesting workstation without
connecting to the central database.

Another SAP mechanism, the

Business Application Programming Interface (BAPI) is used for synchronous


transactions.
A large enterprise's networked computing environment is likely to connect many
geographically distributed computers to the main database. These computers are likely to use
different hardware and/or operating system platforms. An IDoc encapsulates data so that it
can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which
may then be broken down into more specific categories called message types. Greater
specificity means that an IDoc type is capable of storing only the data required for a
particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a
shipping transaction process, an IDoc may be generated that includes the data fields required
to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs
are generated in the sending database and passed to the ALE communication layer. The
communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination
specified by the customer model.

The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external
system.
What are the main advantages if IDOC?

IDoc is the data Format used by the SAP in data transfer using ALE /EDI methods. They
provide more data security.

An IDoc is an intermediate document used to send data in two ways, that is internal and the
external point for you.

In BW, IDoc is a transfer mode, when you create a Infosource you can select the transfer
mode as PSA or IDOC. Its the method provided for backward compatibility. In older
version the hirerchies where loaded using IDOC transfer method. Now its possible with
PSA but still that method is available to load the hierarchies.

An example in SD:
For creating sales documents (sales order) through IDOCS you will have to use the. In that
click basic type and enter order05(IDOC type) and select via message type T code WE19
then enter ORDERS(message type), click execute.

You will get to see many fields.here you have to enter the datas that you enter in the VA01
screen in order to create sales order. The datas such as material name, date, qty, P.O no etc.
After entering all the datas, you click standard inbound the IDOC would be created by the
system.You can see the created order by going in to VA03 screen.

Next time when you create the IDOC, in same tcode WE19 screen, click existing IDOC
and enter the IDOC which you created in the above step and just change the P.O no.Sytem
will create new sales order through new IDOC

Before doing all you need to maintain the partner profile in T code WE20. For this Discuss
with EDI consultant.

Important Tips for Interview for SAP SD

Let me share some important tips for interview for SAP SD:

1. Please be through with the projects you have mentioned in your resume.
2. Remember all the versions you have worked upon.
3. If your projects are in Indian scenario be thorough with CIN/Excise VAT and pricing
procedure.
4 For offshore client specially in Europe and NASA prepare yourself for Warehouse/Lean
warehouse
5. Third party billing / Intercompany / Make to order are important topics.
6. Cost booking that is accounting enteries after PGI and Billing should be known to you.
7. Mug up all the determinations.
8. Remember your last ticket.
9. Have general awareness about ALE/EDI/IDOC, as this provides added advantage. (not
very tough)
10. Please be through with your basics, the process, the pricing and the master data.
11. People who are thorough with route, transportation, shipping always have an added
advantage.

The MOST IMPORTANT THING:

Do not try to fool your interviewer, say exactly and only what is asked do not show your
excitement and do not speak too much if you know the topic too well, and say a straight NO
if you have not worked on something, or don't know about something, pls pls pls don't not go
for flukes otherwise you will end up in soup.

What I understand is most of the companies especially in the US are looking for a
candidates with
1) good communication skills (SAP is all about interacting with the client, users and
team)
2) good business knowledge
3) are you able to convince the client

That comes in next round when you are interviewed to be deputed for any US/Europe project,
in this round take care of the
following:
1. Speak slow, I mean normal, because usually Indians speak english too fast.
2. Listen to them carefully, if you are not able to understand their question request them to
repeat it, rather than assuming it to be something else and giving a wrong reply.
3. Again I should repeat prepare yourself for warehouse, I mean even general knowledge will
help.
4. Say a straight no when you don't know or have not worked on the topic.
5. Always be strong on SD MM FI integrations

What the job responsibilites would be for the Support Consultant? If the Consultant is
working in Offshore Support, How the business interaction would be there between the
Consultant and Customer? How the Customer Queries were handled successfully
sitting from his location.

Job responsibility of a Support consultants is to handle routine tickets, which can be incident
(routine problems), change tickets (need configuration change, therefore a change request),
normally a support consultant can only advice a change but can't do it , because there is
always a change advisory board on client end to evaluate and implement the adviced change.

Business intercation between users and customer can be through mail box utilities, outlook,
even telecons and some companies also allow chat.

Usually the customer provides with the number of the document and client/company code
and other necessary info. about the process which is facing problem, the consultant tracks the
project by logging in to development server and search out for causes, the solution is then
sent to user, maybe with snapshot if required.

For those people who asks for for tickets:


1. Tickets are normally raised by end user and carry a priority.
2. Those who are asking SAP gurus to tell them about tickets, pls note that most of the
problems except for the basic questions discussed in this group are the tickets themselves,
tickets are nothing but the routine incidents the SAP consultants get, if you regularly read the
mails in the group you will soon start recognizing tickets.

And the most important thing "Believe in yourself and God, as there is always somebody
there to help you".

What is the team size? Duration of the project.

Hardly the team of the sd will be 4 to 5 and entire team of the project will be around 20-24
(all modules like fi/co, sd, mm, pp, hr, qm, pm). If its big project, it will be around 40. Team
size means the employees who you are working on sap r/3 implementation.

For the project completion it will take around 8-10 months to get into golive. After that, post
implementation for 3 months. After that supporting it depends as project time line for every
company is different.

For free online training follow the link:

http://www.magnatraining.com/sap/sap-tutorials/sap-sd/sap-credit-management