on 01-26-2008 7:32 AM
Dear All,
Can somebody send me some tickets ( Level 1,2, not critical) with solutions or some write ups in any topic in SD which can help me out in the interview? I'm a certified consultant, but during Siemens classes we were not exposed to real time situations. I would really be thankful and reward points to all of you. You can send me anything that can help me out understanding SD / facing the interview.
Regards,
Soumya
Email: soumya1@inbox.com
Hi Soumya,
1. What is an EDI invoice, how it reflects in SAP R3 system?
Quite generally, you create an invoice by a normal way, but after this you
generate an output (print document) in the form of an IDOC. This IDOC can
be sent to the customer. The process is similar to the standard print
output of the invoice. The IDOC should be of a message type INVOIC. The
function module is IDOC_OUTPUT_INVOIC.
There is also a self-billing process with the invoice creation. In this
case the customer sends the IDOC for himself. This IDOC must be processed
via EDI on SD side, and then the SD invoice will be created. To learn this
process, please call the function module IDOC_INPUT_SBINV in the
transaction SE37 and the press the button "Function Module Documentation".
The SBINV process can be realized via EDI only.
2. What is meant by Explosion in SD?
It is related to Bill of Material where one parent item is linked with
several child items. For creation/edit/display, T-Code is CS01/02/03
3. What is the usage of configuration profile in variant configuration?
You maintain the configuration parameters for a configurable general
maintenance task list in the configuration profile.
The settings that you make here also concern the BOM explosion for the
piece of material. In addition, at least one class, whose class type allows
variant configuration, must be assigned to each configuration profile. The
class contains the characteristics that the system proposes for
characteristic evaluation when you create a maintenance or service order.
4. What do you mean by tickets? Could you please give me some examples of
tickets?
Tickets in SD can be considered as the problems which the end user or the
employees in the company face while working on R/3. Tickets usually occur
during the implementation or after the implementation of the project.
There can be numerous problem which can occur in the production support and
a person who is working in the support has to resolve those tickets in the
limited duration, every ticket has the particular deadline alert so your
responsibility is to finish it before that deadline.
End user is not able to
1. Create Sales order for a customer from a new plant, since shipping point
determination is not happened. (Without shipping point the document becomes
INCOMPLETE and he will not be able to proceed further like DELIVERY,
BILLING).
He raises a ticket and the priority is set in one of the below
1.Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and
identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change
and Request one more Transport to BASIS for QA client. The End user will
test the same by creating a sales order for the new plant and approve it.
Finally u requests a transport to move the changes to PRODUCTION.
Once the change is deployed in production the TICKET is closed.
What I have given is a small ex. You would get some real issues with
severity HIGH in your day-day support
1. KOFO error?
2. Defecit in sales order stock?
3. PGI is not possible?
4. Shipping conformation is not possible.
5. Picking or packing PGI is not possible.
5. What is the difference between sales process and business process?
BUSINESS PROCESS: Sequentially and logically related series of processes
and functions for an internal or external target group to deliver a defined
good or service. The R/3 Reference Model provides sample business processes
in scenarios as EPCs.
6. What is the difference between transit time and transportation time?
Transit time: is the time taken by the material to reach customers place.
Transportation time: is the time taken to schedule the materials by
shipping company.
7. What is the difference between free goods and bonus buy?
Free goods are either inclusive or exclusive if a customer orders for 10
products he will get 1 free for that no price is charged this is exclusive
scenario
If a customer orders 10 products he will get 9+1 for 1 product he will not
charged this inclusive scenario
For bonus buy if a customer orders regularly 10 products in one occasion if
he orders 1000 products he will be given less price than the price he will
get for 10 products this bonus buy scenario
Or
Free goods are considered to be merchandise, moveable belongings or
personal property. Free goods are those which economists are not interested
in because in free goods doe not offer the opportunity for creating a cost
for usage. The best example of free goods is air because there is no
scarcity of air. Economists are interested only in goods, which can be
manipulated to create cost for usage. Free goods are plentiful; you have as
much as you want without a chance for future cost to society.
A bonus buy refers to any product manufactured or otherwise made available
for purchase at a lower cost for a certain period of time. A bonus buy can
relate to food, cars, stocks, bonds, insurance, bank loans or almost any
product you can think of.
Examples of Bonus buys are: buy one and get one free, 20% original price,
and 15% Reduced Mortgage today.
8. What is the difference between static and dynamic in credit management?
SIMPLE CREDIT CHECK: Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value: Sales Order has been saved but not delivered
Open Item: Sales Order has been saved, Delivered, Billed & Transferred to
FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1, 00,000/-
Suppose Doc.Value + Open Item Value is Rs.1, 10,000/-
Here credit limit exceeds then system reacts.
Options: A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular
customer.
STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit
Control Area.
A) Credit Checking Groups: Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Category: Based on the risk Categories Company will decide how much
credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit
limit
1) Open Doc.Value / Sales Order Value : Which is save but not delivered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transferred to FI but not received from the
customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3
months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type (OR) + credit Check (0) + Credit Group (01)
Credit Limit Check for Delivery Type: Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
9. Difference between 4.6 version and 4.6c, 4.7ee
There are so many differences between the versions in different objects
1. In the customer master in 4.6 version there is no partner function tab
in the customer in xd01 t-code and also there is no CIN tab in that version
but it is there in the 4.7 EE version
This is the major change from the 4.6cc to 4.7EE
2. in 4.7EE there is some settings that are related for CIN which cannot be
done in 4.7EE that means they need some patches for doing the configuration
setting for the CIN
But we can do the same in the 6.0 versions
These are the some of the settings that are differed in the two versions
and in that two objects
10. Where is rebate define for quantity REBATE
Rebate:
Following explains how to create a rebate agreement, test it using a sales
order and billing it. Then settling it partially or fully using a rebate
credit memo. Please use the basic procedure and tweak your IMG settings
according to your unique requirements.
Rebate processing:
1. First requirement is that the rebate processing must be active for
a. the customer ( check in customer master) ,
b. for the billing type ( check in IMG > Billing > rebate processing >
active rebate processing > select billing documents for rebate processing.
)
c. For the sales organization:
( check in IMG > Billing> rebate processing > active rebate processing >
Active rebate processing for sales org. )
2. Next create a rebate agreement for this use T-code VB01. For the rebate
agreement type you can choose either 0001
( group rebate ) or 0002 material rebate or 0003 ( customer rebate ) etc
b. Enter your rebate conditions. Dont forget to enter the accrual rate
here.
3. Now test your rebate functionality: create a sales order for the
particular customer, sales org (ensure that the billing type used in your
sales order is relevant for rebate). Create outbound delivery, transfer
order to do picking and post goods issue.
4. Now go to Tcode VB03 and check your rebate by choosing conditions,
selecting the condition line and choosing payment data. You will see that
the accruals and business volume are updated when accounting doc is created
for billing.
5. Settling your rebates:
Once your rebates have been accrued you need to settle the rebate.
For this first release the rebate for settlement by using Tcode VB02. As a
trial basis choose B (you can choose other settings based on your
requirement) and choose Create manual accrual. Now enter the amount to be
paid and save the rebate agreement.
6. Next display your rebate agreement using Tcode VB03.
Enter your rebate agreement number. Next choose rebate payments > Rebate
documents and select partial settlement. Click on the choose button to note
down your credit request number.
7. Use Tcode VA02 and release the billing block for your credit request.
(Use item overview tab)
8. Now use VF01 to create a rebate credit memo by entering the credit memo
request number and save it
9. Now release the credit memo to accounting using vf02.
Quantity Rebate:
In rebate agreement details we will define the rebate basis whether it is
the quantity rebate or volume based rebate.
11. What is solution manager? What is purpose of it? In support what type
of tool we can use? What is change?
SAP Solution Manager is a centralized, robust solution management toolset
that facilitates technical support for distributed systems with
functionality that covers all key aspects of solution deployment,
operation, and continuous improvement. It combines tools, content, and
direct access to SAP to increase the reliability of solutions and lower
total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution
environment is performing at its maximum potential. The toolset addresses
your entire IT environment, supporting SAP and non-SAP software and
covering current and forthcoming SAP solutions. As part of SAP Net Weaver,
SAP Solution Manager is included in the annual maintenance fee for SAP
solutions.
SAP Solution Manager targets both technical and business aspects of your
solutions, focusing strongly on core business processes. It supports the
connection between business processes and the underlying IT infrastructure.
As a result, it eases communication between your IT department and your
lines of business. And it ensures that you derive the maximum benefits from
your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation SAP Solution Manager provides content
that accelerates implementation. Configuration information and a
process-driven approach to implementation speed the blueprint,
configuration, and final preparation phases. SAP Solution Manager enables
efficient project administration and centralized control of cross-component
implementations.
Global rollout The toolset eases process standardization and
harmonization across organizations and locations by providing proven
methodologies and all necessary functionality. You can more easily
implement standardized settings at local sites, because configuration
settings needn't be re-entered into local components.
Synchronization of custom settings With SAP Solution Manager, you can
maintain consistency as you customize your heterogeneous IT environment. It
enables safer administration of customization, less error-prone replication
of custom settings, and simpler consistency checks. SAP Solution Manager
reduces manual synchronization efforts by automatically distributing custom
settings to various systems simultaneously, and by centrally managing all
requests to synchronize settings.
Testing SAP Solution Manager speeds test preparation and execution. It
provides a single point of access to the complete system landscape and
enables centralized storage of testing material and test results to support
cross-component tests.
IT and application support The support desk included in SAP Solution
Manager helps you manage incidents more efficiently and eases the
settlement of support costs. Centralized handling of support messages makes
the support organization more efficient.
Solution monitoring SAP Solution Manager performs centralized,
real-time monitoring of systems, business processes, and interfaces, which
reduces administration effort. It can even monitor intersystem
dependencies. Proactive monitoring helps you avoid critical situations,
while automatic notifications enable fast response to issues.
Service-level management and reporting SAP Solution Manager allows easy
definition of service levels and provides automated reporting. Service
reporting covers all systems in the solution landscape and provides a
consolidated report containing the information you need to make strategic
IT decisions.
Service processing SAP Solution Manager makes appropriate service
recommendations and delivers SAP support services. These include SAP
Safeguarding, which helps you manage technical risk; SAP Solution
Management Optimization, which helps you get the most from your SAP
solutions; and SAP Empowering, which helps you manage your solutions.
http://blogs.ittoolbox.com/sap/support/archives/introduction-to-sap-support-10712
12. How can we define sales order type
In VOV8 either u can copy rename or create
13. What is gap analysis and when it will be use in the time of project?
Business blue print stage is called as is process. Fit gap means, before
implementing the SAP all the business data is in the form of documents, we
cannot keep this data as is in the SAP. There should be a gap. So by
filling this gap, we make configuration with the help of these documents.
This is called as fit gap analysis. In this stage, we should analysis the
gap between as is and is as process
Cut Over Plans:
Detailed plans need to be developed for cutting over from the old system(s)
to the new. Parallel runs of what will happen over the conversion period
using test data, convert and watch for a period after wards to ensure
nothing unexpected happens.
Train Users:
Well trained users will support and defend the system on site. Unsupportive
users will continually undermine the system and eventually it will be
replaced. Therefore the more effort you put into helping the users master
the system early the better. Fit gap means, before implementing the SAP all
the business data is in the form of documents, we cannot keep this data as
is in the SAP. There should be a gap. So by filling this gap, we make
configuration with the help of these documents. This is called as fit gap
analysis.
GAP Analysis
A through gap analysis will identify the gaps between how the business
operates ad its needs against what the package can can't do. For each gap
there will be one of three outcomes which must be recorded and actioned,
GAP must be closed and customized software can be developed close the gap,
GAP must be closed but software cannot be written therefore a workaround is
required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information
technology, gap analysis is the study of the differences between two
different information systems or applications (ex; existing system or
legacy system with Client and new is SAP), often for the purpose of
determining how to get from one state to a new state. A gap is sometimes
spoken of as "the space between where we are and where we want to be." Gap
analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print
stage
The Gaps can differ from company to company. Most commonly, however,
missing functionality is industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new
intellectual property management and media advertising management
functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods
where they wanted 'Buy one get 2 different products free'.
2 gaps are, In customer master data the client requirement needs legacy
customer number which can be solved with User exit.,
In sales order we need customer Phone number, We can use user exit
These 2 are gaps, which we cant, find in Standard SAP
1. if client want new field in customer master like nearest fire station ..
2. order will be uploaded directly with out va01. Through BDC... bcoz lot
of orders if they get daily, they can opt these...
Movement type 1 uses when a material have two movement types.. like example
101 and 261.. one is incoming raw material and going for production...
14. What is the difference between rebate and discount?
Rebate is a partial repayment, whereas a refund is a repayment of the total
purchase price and Discount is reduction in Price
Or
Rebate: an incentive to be given to a customer. Clubbed with qty purchased
by a customer within the period specified (say one month)-conditional.
Discount: unconditional, to be given to a customer on account of heavy
purchase by one single billing. From the price List (Base price).
15. What is the Purpose of a Sales Organization in SAP?
Sales org. represents the highest elements in SD. Sales org. is responsible
for
Sales, services, negotiation or Revenue generation and physical
distribution of products.
16. What is the purpose of Distribution Channel?
The Mechanism or route through which the products are placed in the market.
17: What is the purpose of Division?
Division is the one which sells identical or similar products.
18. A Sales organization can be assigned to more than one Company code.
State true or false?
False. Sales org. cannot be assigned to more than one company code.
19. Can you create a Sales Order without having a Sales Group defined in
the Org Structure?
NO. We cannot create a sales order without having sales group.
20. What is sales area
Sales area is the combination of
Sales org. + Distribution channel + Division.
21. Can you assign one plant to more than one Sales Organization?
Yes, we can assign plant to more than one sales org.
22. Explain process of stock transport orders in SAP?
Stock transport is the process of transporting stock within the plant
from one storage location to another. Stock transport is a replenishment
Delivery.
23. What is a Scheduling Agreement? Give a business case where it is used?
It is the agreement between customer and company. It contains delivery
Schedule.
24. Can you check availability during Standard SAP Quotation Process?
Yes, we can check for availability during std. quotation process.
25. What are the different movement types, and where will you assign the
movement type
631, 632, 633, 634, 601, 602, 651, 561
Movement types will be assigned to schedule lines
26. How billing date determined in the billing document?
Once the PGI is done, goods will move to the customer on the
Specific delivery date, from this the billing date is determined.
27. How the account posting will done by the system, explain what is
credited and what is debited when customer billing passed to accounts?
Through revenue account determination.
28. What are the different billing types available in standard system?
A) Periodic billing
B) Milestone billing
29. What are the columns in a pricing procedure?
The following fields determine the pricing procedure. And the columns are
as follows. There are total 16 fields which determine the pricing
procedure.
1) Step
2) Counter type
3) Condition type
4) Description
5) From
6) To
7) Manual
😎 Mandatory
9) Statistical
10) Print out
11) Sub to
12) Requirement
13) Alternation calculation type
14) Alternation condition based value
15) Account keys
16) Accurals.
30: how system will Determine Shipping Point?
Delivery plant + shipping condition from CMR - SH + Loading group from
Material Master.
31. If Same Purchase Order no is used in multiple Sales Orders, Is it
possible to warn the User? If yes How?
The same purchase order no. is entered system throw a warning message.
32: Which Item Category in Standard SAP is used for Free of Charge items &
Text Items?
TANN. TXT.
33. Is it Possible to copy Sales Order to a Production Order? If yes
explain in which situation you can do that?
In Make to order scenario it is possible
35. How do you release a Sales Order blocked for Credit Hold. ?
Go to T-code VKM1 and give the sales document no. to release the sales
order
from credit hold.
36. How do you create Sales BOM, What is the purpose of Sales BOM?
Go to cs01 to create sales BOM. Sales BOM is to explode the sub items in
the
Sales order along with the main item
37 When does the invoice status will change?
When invoice is released for posting to account, then status of invoice
changes.
38. What is the structure of a customer master record?
General data
Company code data
Sales area data
39. Account group controls
a) Fields selection
b) Partner functions
c) screen sequence
d) Number range assignment
40. Name any 4 Material types in SAP R3?
a) hawa-trading goods
b) fert- finished goods
c) roh-raw material
d) halb- semi finished goods
41. How system will determine the delivery plant in sales organization?
a) Customer material Information record
b) Customer master
c) Material mater
42. Which other areas in SAP SD are condition technique used?
a) Output determination
b) material determination
c) Revenue account determination
d) text determination
Handling tickets is called Issue Tracking system. The errors or bugs
forwarded by the end user to the support team are prioritized under three
severity High, Medium and Low. Each and every severity as got its time
limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line
to the customer or the organization where SAP is already implemented for
which the person should be very strong in the subject and the process which
are implemented in SAP at the client side to understand, to analyze, to
actuate and to give the right solution in right time. This is the job of
the support consultant.
The issues or the tickets (problems) which are raised is taken care of on
priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail
(RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work
group (by name).
4. Once the calls came to the work group the support consultant or the team
need to send an IR (Initial Response) to the user depending upon the
priority of the calls. (Top, High, Med, Low, None)
5. Then the error is fixed, debugged by the support consultant or the team.
Then after testing properly by generating TR (Transport Request through the
basis admin)
6. Then it is informed to the end user/customer/super user about the
changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any
configuration or customization is required to solve the issue, then the
consultant have to work on DEV Client, then the end user will test it in
the QA client and after approval the BASIS consultant has to transport it
to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or the
employees in the company face while working on R/3. Tickets usually occur
during the implementation or after the implementation of the project. There
can be numerous problems which can occur in the production support and a
person who is working in the support has to resolve those tickets in the
limited duration, every ticket has the particular deadline alert so your
responsibility is to finish it before that deadline.
To begin with, we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a new plant, since shipping point
determination is not happened. (Without shipping point the document becomes
INCOMPLETE and he will not be able to proceed further like DELIVERY,
BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and
identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change
and Request one more Transport to BASIS for QA client. The End user will
test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once
the change is deployed in production the TICKET is closed. What I have
given is a small example. You would get some real issues with severity HIGH
in your day-day support.
Examples like shipping point determination is not determined...possible
reasons could be shipping point not assigned in org structure, shipping
point determination not maintained (shipping cond + loading group + plant)
etc..
1. Someone coming back to us that they cannot create a delivery note for
xyz company or cannot use VA01 transaction.
SOL : Basically authorization issues...usually we analyse what rights he
would require and pass on the same to basis team to give the adequate
authorization.
2. Sometimes endusers are not completely aware of the business process
leading to not performing a step which is required in the flow of
material/documents and surely leading errors in subsequent steps.
We need to figure out the same and take necessary action to fix the flow in
some cases and surely get the user gear up to the correct process.
3. In many cases we have to analyse why a particular document was not
created either manually or through automated process. Example be like why
the delivery document creation failed ?
4. Cases are also raised related to customized development where it does
not perform as required like a particular should have been in the report
but is not there..or any sort of bugs etc.
It requires to analyse the development and find the casue of the issue.
5. Enhancements..they usually contribute the most in support projects. I
feel in software industry we cannot have a complete
specification..something is surely misinterpreted or missed out, which is
usually realised after few months of go live. They are usually classified
as enhancements ..leading to small modifications or developments.
Case 1 :
Material: X
Plant : Y
Stock in Storage Location - A : 1 Unit
Stock in Storage Location - B : 1 Unit
Sales Order N0 1111111111 is created against storage location A &
Sales Order N0 2222222222 is created against storage location B &
In Case 1
I am able to do availbility check for Both the sales order as stocks are
available in both the storage location
In Case 2
Carried out availability check for sales order 1111111111 - Shedule lines
were generated against stocks in Storage Location A.
Now I transfer the stock from Storage - A through 309 movement to some
other material no - Z
Problem / Issue.
Since no stock is availble in Storage - A , Sales Order which was created
for Storage A pulls the stock from storage B for availablity to promise.
Now In this case I am not able to carry out availabilty check for Sales
Order 2222222222 inspite having stocks in storage - B as it has been
confirmed/pulled by sales order 1111111111.
Looking for following solution.
[1] I dont want Availability check at Plant level - I need at Storage
Section Level.
[2] As soon as 309 movement is carried out or stock is moved out to any
other storage or Plant then - Shedule lines for Sales Order 1111111111
should get deleted automatically as the material in storage location is no
more available.
Solution:
ATP at SL level, you need to insert the SL at item level of the sales
order. This will restrict the search.
2. For automatic recheck of ATP, I can suggest a batch job of V_V2
transaction .
Case 2: Back Order
1. When a sales order is created by end user there is no material
available.
I checked this by checking schedule line the confirmed quantity shows 0 qty
at schedule line.
Soln: Backorder processing
Logistics-SD-sales-Environment-backorders-backorder processing-enter sales
order number
2.END USER GOT A PROBLEM WHEN CREATING A SALES ORDER FOR MAKE TO ORDER
QUANTITY ENTERED IN SALES ORDER IS NOT PICKED AUTOMATICALLY AND IS ALSO NOT
PICKED WHEN ENTERED MANUALLY
SOLN:- SOLVED BY GOING TO MM02 SALES/GENERAL PLANT VIEW
CHANGE AVAILABILITY CHECK TO INDIVIDUAL REQUIREMENT (02) FROM DAILY
REQUIREMENT (01) IN MATERIAL MASTER
3.In the client site complete SAP system got struck by giving error: short
dump
When creating a sales order it didnt allow me to save any order
Soln:I solved it first by going to lt22 and came to know its due to short
dump
Caused by S687 Infostructure
Goto img->logistics general->logistics data warehouse->updating->updating
control->Activate update chhose sales and distibution
double click on u r infostructure radio button and select asynchronous only
synchronous is not recommended.
Here s687 is selected synchronous which gave the error.
4. When customer returned goods.client want to make a gate pass by which u
can track the material returned or received
Soln: Go to Tcode LECI and enter the details about the truck like
time,licence plate,driver and save & print it.
There could be many such cases.
Handling tickets is called Issue Tracking system. The errors or bugs
forwarded by the end user to the support team are prioritized under three
severity High, Medium and Low. Each and every severity as got its time
limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line
to the customer or the organization where SAP is already implemented for
which the person should be very strong in the subject and the process which
are implemented in SAP at the client side to understand, to analyze, to
actuate and to give the right solution in right time. This is the job of
the support consultant.
The issues or the tickets (problems) which are raised is taken care of on
priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail
(RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work
group (by name).
4. Once the calls came to the work group the support consultant or the team
need to send an IR (Initial Response) to the user depending upon the
priority of the calls. (Top, High, Med, Low, None)
5. Then the error is fixed, debugged by the support consultant or the team.
Then after testing properly by generating TR (Transport Request through the
basis admin)
6. Then it is informed to the end user/customer/super user about thechanges which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any
configuration or customization is required to solve the issue, then the
consultant have to work on DEV Client, then the end user will test it in
the QA client and after approval the BASIS consultant has to transport it
to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or the
employees in the company face while working on R/3. Tickets usually occur
during the implementation or after the implementation of the project. There
can be numerous problems which can occur in the production support and a
person who is working in the support has to resolve those tickets in the
limited duration, every ticket has the particular deadline alert so your
responsibility is to finish it before that deadline.
To begin with, we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a new plant, since shipping point
determination is not happened. (Without shipping point the document becomes
INCOMPLETE and he will not be able to proceed further like DELIVERY,
BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and
identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change
and Request one more Transport to BASIS for QA client. The End user will
test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once
the change is deployed in production the TICKET is closed. What I have
given is a small example. You would get some real issues with severity HIGH
in your day-day support.
1. What is the main difference of revenue key for e.g.:- ERL and accrual
key e.g.:- ERU
A. ERL Sales Revenues and ERU - Accrual.
2. How many number of user exits are there in credit management
A. Check in IMG-SDSYSTEM MODIFICATIONS-USER EXITS-USER EXITS FOR
CREDIT CHECK & RISK MANAGEMENT
3. What makes delivery create if the cash sales order type is order related
billing?
A. IN VOV8 IN SHIIPING IMMEDIATE DELIVERY AS "X"
4. How does the billing knows how many items in the total quantity have
been delivered by the third party
A1. In the item category billing relevance 'f'
A2. I think its through MIRO transaction where we will be entering the
invoice sent by the vendor (CHECK)
5. What are the fields that can be changed before saving a billing
document?
A. We can change the 1) billing date 2) pricing 3) account determination of
billing before an accounting document is created
6. If we change pricing in billing, will it automatically copy in the sales
order and other documents if no how we do it?
A. IF WE MAINTAIN COPY CONTROL SETTINGS FROM BILLING TO SALES DOCUMENT F2
TO OR (CHECK)
7. What exactly makes automatic purchase requisition to be created? i
answer schedule line category and automatic purchase order tick, but he
denied the answer kindly explain?
A1. in the schedule line category we have to put the order type NB,5,1
A2. In schedule line category in the field order type as "NB" item category
as third party and acct assignment. Category as "third party".
8. If we are changing freight rate in the billing, in what circumstance we
do it?
A. DZJDN B
Regards,
Chandramohan M
Reward points please
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chandra,
I have no words to express. This will do for the time being. I will practice these situations on my system. Thanks a lot. Loads of god wishes to you.
Regards,
Soumya
soumya1@inbox.com
Hi,
Well, I don't know whether you are experienced in SAP. If not, then I don't think that you would need to require to go thru "tickets" and their solutions. No doubts it's helpful if you are planning to prepare yourselves for a job before getting into it.
As far as Interview questions are concerned, interviewers know that till what level you must be knowing. Well, they may ask you questions answers for which you should or ought to know.
Questions asked from me were:
-All determinations
-Special Business Process
-Pricing procedure (16 columns with their explanations)
-Intercompany Sales
-Menu Paths thru SPRO
-Free Goods
-Org structure and their assignments
-"Where-are fields" questions
-Sales Docs, It Cat, SLC settings
All the best.
Regards
SD
Edited by: Samier Danish on Jan 26, 2008 2:08 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Samier,
Thanks for your reply. These are exactly the topics I have been facing questions in the interview. But can you send me some notes / write-ups on that? please?
Could you explain:
1. Which all determinations you mean?
2. Can you give me examples of special business processes?
3. and I would really appreciate if you could give me some support tickets with answer; I want to know what sort of problems users face while processing sales documents....
You can send me to my email : soumya1@inbox.com
Regards,
Soumya
Hi,
- All determinations means It Cat determination, Plant, Shipping Pt., Route determination etc.
- Sp Business Process can be Consignment, Cash Sales, Rush Order etc.
If you have system in your place, it's better to go for "Documentaion" in SPRO. Trust me I prepared from there right from Consignment to Intercompany Sales.
Regards
SD
Thanks. But I still need some tickets.....can anybody help me out?
Regards,
Soumya
email: soumya1@inbox.com
User | Count |
---|---|
100 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.