SAP SD Interviews Questions and answers.
My Intro - Praphul, Teknoleum, Bangalore.
Hi SAPIANS, Fresher & Experts,
This is my small efforts to capture Mostly asked questions by interviewer.
Use: This makes it possible to list or maintain condition records independently of condition type and condition table.
Condition update
Controls whether limit values are relevant for pricing.
E.g.: you can make the use of a particular condition record in the document dependent on a specified total value.
Hi SAPIANS, Fresher & Experts,
This is my small efforts to capture Mostly asked questions by interviewer.
*Vcentric Interview.*
1. Relation between Company code & Sales org.
Company code & Sales org. - One to many
Sales org & distribution channel - Many to many
Sales org & division - Many to many
Shipping Point & Plant - Many to many.
Plant to storage location - Many to many
Plant to Company code - One to Many.
Company to company code- One too many.
Sales office to
sales area – Many to Many.
Sales group to
sales office – Many to Many.
Purchasing
organization to plant – Many to Many.
2. Shipment cost pricing procedure:
- Transportation planning point + Shipping type procedure
group +
Item determination procedure group + Service agent
procedure group.
3. Pricing procedure determination & from where it
comes.
- Sales area + Customer pricing procedure (Customer master/
account group) +
Document pricing procedure (Sales document types.)
4. Difference between F2 & F8.
- F2- Actual or standard Invoice.
F8- Proforma Invoice.
5. Is accounting Key generate in Proforma invoice.
- NO
6. Shipping point determination and from where it comes.
- Shipping Condition (From customer master or sales document
types) +
Loading group (Material master- sales general/plant data) +
Delivery Plant
7. Route determination:
1. Departure zone-it gets determined from shipping point.
(2)Shipping Condition:-it is determined from sales doc. type
or from SP (Customer master).
(3)Transportation Group: - it is determined from Material
master. (Sales general/plant data view)
(4) Transportation Zone: - ship -to -party.
(5) Receiving country.
(6) Weight group (optional).
8. Account determination:
It is a process to determine G/L account while posting
invoices into accounting key.
Condition type (KOFI – without control, KOFK – With Control)
+ Chart of acc + sales org + cus acc grp + mat acc grp + account key
9. Sales document category, delivery Document category,
billing document category.
- For Sales document: Inquiry - A, Quotation - B, Sales
order - C,
RK,CR- K, DR- L, Return order(RE)- H, CS,RO,CF,CI- C, CONR,
CP- H.
Delivery Document: LF- J, Return delivery LR- T
Billing Document: F2 - M, RE or G2 (Cust. credit) - O, F5 or
F8- U.
10. Item Category determination:
- Sales document types + Item category group + Usage +
Higher level Icat.
11. Where is Item category group located and what is the
difference between?
General item category group & Item category group.
- It is located in Material master- sales org2 tab.
Based on Item category group, Item category determines in
Sales document types.
Difference: For Ex. If someone maintain NORM as item
category group, then
NORM can be further classified as Sub items that is Packaging
item, service item or Normal items.
Or Also General item category group Can be maintain in Basic
data view of material, in that case if item category is missing than General
item category group used as item category group in item category determination.
Also you can say item category group would refer to default
item category
General Item category group is used while process inbound
delivery documents.
12. Movement type of return orders: - 651.
14 Tax determination:
- Departure country + Destination Country + Customer
material tax classification.
15. Sold to party is unique, where we configure. Why it is
only one.
Partner function in account group.
16. Account group used to control entire customer master
record, partner function & number range.
17. Subtotal condition:
>The
value of this field determines where the values of subtotals to be captured
i.e. in which table and which field.
>The subtotal field is used to assign
a subtotal key to a step in the pricing procedure. The value of
the condition type, if required in other areas of the system can be copied
through this field. You decide the value of Subtotal field depending
upon what is the value and where you need the value to be carry forwarded.
>Subtotal will be used to store the value of condition
types in some temporary tables and fields for the purpose of further
calculations. (In Alternate Calculation type and Alternate base value type.)
For Example: 1) Subtotal will also be used to update sales
document values into credit management.
2) Subtotal will also be used to update the billing document
values into rebate agreement.
Subtotal for VPRS is B., Profit margin = Base Value – VPRS.
Subtotal for Credit management is A.
Subtotal for Rebate agreement is 7.
18. Requirement condition:
Requirement is a condition which system will check every
time while determining condition type in Sales document.
19. Rebate Conditions: (list of condition types in V/06)
20. Condition types controls (V/06): Interviewers asks about
highlighted field.
Condition Base Value (Right side highlighted) in Condition
Class Field (Ex. Normally we take B for Base Prices for PR00 condition type)
Calculation type:
Normally we take Quantity as C in Calculation type field.
Interviewer asks about 1. Difference between Base Value and
condition type.
2. Condition category (examples: tax, freight, price, and
cost)
Condition types: lets
you differentiate between different kinds of discount; in output determination,
between different output types such as order confirmation or delivery note;
Group condition
Indicates whether the system calculates the basis for the scale value from more than
one item in the document
Condition Index – Update condition index
Specifies whether the system updates one or more condition indices when maintaining condition records.Use: This makes it possible to list or maintain condition records independently of condition type and condition table.
Condition update
Controls whether limit values are relevant for pricing.
E.g.: you can make the use of a particular condition record in the document dependent on a specified total value.
21. Update Group in Credit management: Update
Group
The credit update controls when the values of open
sales orders, deliveries, and billing documents are updated. The open order
value is only updated for schedule lines that are relevant for delivery.
Update group 000012
When a Sales order is created, system increases
open order value from delivery-relevant schedule lines. S066-OEIKW (S066
information structure, OEIKW- Open sales order credit value (schedule lines) goes
up.
When order is delivered, system reduces open
order value from delivery-relevant schedule lines and increases open delivery
value. S066-OEIKW decreases and S067-OLIKW (Open delivery credit value)
increases
When delivery document is billed system reduces
open delivery value and increases open billing document value. S067-OLIKW
decreases and S067-OFAKW (Open billing document credit value) increases
When billing document is released for financial
accounting, system reduces open billing document value and Increases open items
(S067-OFAKW decreases).
In Brief when order is created, value of S066
information structure is increased by the open order value. When order is
delivered, value of S066 information structure gets decreased decreasing the
open order value and value of S067 information structure gets increased
increasing the open delivery value. When delivery is invoiced, value of open delivery
gets decreased and value of open billing documents gets increased again S067
information structure gets affected. When billing documents are released for
accounting value of open invoices gets decreased and value of open items gets
increased. S067 information structure value gets decreased.
Update group 000015
When delivery is created, system increases open
delivery value and open billing document value
When billing document is released for financial
accounting system reduces open billing document value and increases open items.
Update group 000015 does not use open sales
order value, but uses only open delivery, open invoice and accounts
receivable.
Update group 000018
If sales order is not relevant for delivery
system determines Update group 000018. This update group will be always used by
order items which are billed order-related (VBAP-FKREL = B for example).
When sales order is created S067-OLIKW goes up.
When invoice is created S067-OFAKW goes up,
S067-OLIKW goes down
When account posting is done u2013>
S067-OFAKW goes down and A/R goes up.
For Brief and detailed explanation:
22. Differentiate between header pricing and item pricing.
Header pricing calculate all item prices available in
related (Sales) documents.
While item prices represents of particular item prices.
23. Difference between VPRS/SKTO, EK01/EK02, check below
link for better understanding.
VPRS – Cost it cost is mainly used to determine whether the
material is having the standard price or moving average price.
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
In this, using the condition category G,
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
In this, using the condition category G,
SKTO – Cash Discount, statistical condition , both SKTO
and SKTV is Cash Discount Condition Type, The major difference among the 2 is
SKTV is Group Condition.
EK01 – Actual Cost It is used to post actual price.
EK02 – Calculated Costs It is used for statistical posting.
PI01 – Intercompany Invoice.
PR00 – Base Price
K004 Material
discount
K005 Customer/Material
K007 Customer
Discount
K020 Price Group
BO01 Group Rebate
BO02 Material
Rebate
BO03 Customer
Rebate
BO04 Hierarchy
Rebate
BO05 Hierarchy
rebate/mat
24. What is Customer Hierarchy? - https://archive.sap.com/discussions/thread/511946
Customer hierarchy is a hierarchical
organizational structure that consists of higher and lower level nodes. Each
node is assigned within the structure to form a graphical diagram of the
customer’s organization. Example: Reliance industries limited – group of
company like digital, mart etc.
A node is represented by an account group. A
node can be a customer, such as a sold-to party, thus account group 0001. A
node could also be a platform or merely an organizational department; thus, we
have account group 0012. A customer hierarchy can only have a maximum of 26
hierarchy levels. One creates a customer hierarchy by first defining the
hierarchy type. ////
Customer hierarchies are used when a customer has
a complex chain or organizational structure in which all or some of the parts
of this structure will benefit from an agreement made for the customer’s
company as a whole. For example, a large customer may have dependent offices,
each responsible for their own purchasing, and as individuals, they would not
benefit from a global pricing scheme. However, as part of a customer’s
hierarchy, they would still benefit from being associated with the larger
parent company.
Hierarchy nodes, Create transaction code V-12, VDH1N for creation of
Customer Hierarchy.
Menu Path
The menu path here is IMG, Sales and distribution, Master
data, Business partners, Customers, Customer hierarchy, Define hierarchy types.
Transaction Code OVH1.
T-code: OVH1
1) DEFINE HIERARCHY TYPES: IMG-SALES AND DISTRIBUTION-MASTER DATA-BUSINESS PARTNERSCUSTOMERS-CUSTOMER
HIERARCHY---DEFINE HIERARCHY TYPES.
T-code: VOPA
2) Set partner determination for hierarchy categories:
IMG-SALES AND DISTRIBUTION-MASTER
DATA--BUSINESS PARTNERS-CUSTOMERSCUSTOMER
HIERARCHY-SET UP PARTNER DETERMINATION FOR HIERARCHY CATEGORIES
T-code: OVH2
3) Assign Account groups:
IMG--SALES AND DISTRIBUTIONMASTER DATABUSINESS
PARTNERSCUSTOMERSCUSTOMER HIERARCHY---ASSIGN ACCOUNT GROUPS.
T-code: OVH3
4) Assign sales areas:
IMG--SALES AND DISTRIBUTIONMASTER DATA-BUSINESS
PARTNERSCUSTOMERSCUSTOMER HIERARCHY-ASSIGN SALE AREAS
T-code: OVH4
5) Assign hierarchy type for pricing by sales document type:
25. What is KOMK, KOMP, and KOMG?
KOMK Communication Header for Pricing
KOMP Pricing Communication Item
KOMG Allowed Fields for Condition Structures
26. Customer Price group KONDA – T code – OVSL. - Price
group (customer)
a grouping of customers who share the same pricing requirements.
27. Account group for customer OBD2.
28. Difference between VK11 and VK31
VK11 is to maintain a single condition record and VK31 is to maintain a
group of condition records according to the situations.
29. Material Creation MM01
30. Customer Creation: XD01
31. Sales Order creation VA01
31. Create Delivery VL01N
32. Create Billing Document
33. Display Price list. V-48.
Price List - You can define price list types according to
the needs of your own organization. Price list types can be grouped according
to:
- The kind
of price list (for example, wholesale or retail).
33. Difference between ERLA/LUMF?
Both is Item category group but in ERLA header item is
priced and sub item is not priced, but in LUMF header item is not priced and
sub items is priced.
ERLA item category group contains TAQ as header item
category and TAE as sub item category.
LUMF as TAP and TAN.
Hi,Thanks for helping me with the informative post about SAP SD Interviews Questions and Answers as it providing info all about various Questions asked by interviewer.Visit now SAP SD Online Training in Hyderabad if you are looking to learn SAP SD skills.
ReplyDeleteExcellent post
ReplyDeleteSAP Training
SAP Training in Chennai
SAP Training in Bangalore
SAP Training in Hyderabad
SAP Training in Coimbatore
SAP Training in Ameerpet
SAP Training in India