Short SAP SD Questions with Answers

 

1. What Happens When You Do Not Enter a Value for a Manual and Mandatory Condition Type?

If a manual and mandatory condition type is left without a value, the pricing procedure will reject the conditions in the sales order. This can prevent the successful processing of the order, requiring manual intervention to resolve the issue.

2. Do Header Condition Types Have an Access Sequence?

No, header condition types do not have an access sequence. They are manually entered or determined automatically through specific pricing configurations.

3. Organizational Structure in SAP SD

Relation Between Company and Sales Organization

- A company can have multiple sales organizations (One-to-Many relationship).
- Sales organizations are linked to plants, and each company can be associated with multiple plants.
- A company's credit control area is linked to sales organizations to manage credit limits and risk. 

What is a Sales Area and Its Components?

A Sales Area is a combination of:
  • Sales Organization: Responsible for sales and revenue generation.
  • Distribution Channel: Determines the way products or services are sold.
  • Division: Represents a product line or business segment.
Each sales document is processed within a specific Sales Area. 

4. What Are Legacy Systems?

Legacy systems refer to existing IT infrastructure or software applications that an organization has used before migrating to SAP. These systems are gradually replaced or integrated into SAP for better functionality and data management.

5. What is a Cutover Strategy in SAP Implementation?

A cutover strategy defines the approach for transitioning from a legacy system to SAP. It involves:
  • Configuration settings (system readiness).
  • Master data migration (customers, materials, vendors).
  • Transaction data transfer (open sales orders, stock levels, pending deliveries).
Before going live, a system copy is created as a production system. After successful validation, the system is activated fully or partially based on the organization's strategy. 

6. What Are Cumulative Condition Records in SAP SD?

Cumulative Condition Records relate to the Condition Update field in condition type configuration (T-Code: V/06). When enabled, the system accumulates condition values over time instead of resetting them with each transaction. 

7. If You Have Three Different Access Sequences for One Condition Record, How Are They Maintained in the Pricing Procedure?

In SAP SD pricing (T-Code: VK11), a condition type is linked to a single access sequence.
  • An access sequence defines the sequence of condition tables used for pricing determination.
  • Multiple access sequences cannot be assigned to a single condition type.
  • The system follows the priority order set within the access sequence to determine pricing. 

8. What Happens in the Access Sequence When You Enable the Exclusive Field for All Access Sequences?

When the Exclusive checkbox is enabled:
  • The system stops searching for further condition records once the first valid record is found.
  • If pricing data exists in the first access sequence, the system does not check subsequent sequences.
This improves performance but requires careful configuration to ensure correct pricing determination. 

9. What is a Delivery Group in SAP SD?

A Delivery Group ensures that multiple items in a sales order are delivered together. Key aspects:
  • All deliveries within a group must have the same Ship-to Party and Shipping Point.
  • Helps consolidate shipments and optimize logistics.
  • Useful in cases where partial deliveries are not allowed. 

10. What Triggers the Automatic Creation of PR (Purchase Requisition) or PO (Purchase Order) in Third-Party Sales?

The Schedule Line Category determines whether a PR is automatically created.
  • The Item Category defines whether the system allows Automatic PO creation.
  • If configured correctly, the system generates PR/PO automatically upon order saving. 

11. What is a Z Transaction in SAP?

A Z Transaction is a custom transaction code that starts with the letter "Z." It is created by copying and modifying a standard SAP transaction to meet business-specific requirements. 

12. Can You Create a Sales Order for 40 Items If the Quotation Was Sent for 30 Items?

Yes, a sales order can be created with a quantity higher than the quotation. However, depending on system settings and business rules, an approval process may be required. 

13. What is the Importance of the Requirement Field in an Access Sequence?

The Requirement field controls whether a condition record should be considered during pricing.
  • The system evaluates a predefined formula assigned to the requirement.
  • If the requirement is not met, the system skips the condition record.
  • This ensures more accurate and flexible pricing determination. 
By implementing optimized pricing procedures and understanding these SAP SD concepts, organizations can improve efficiency and ensure seamless sales order processing.
 

SAP SD Tips

See Also

Get help for your SAP SD problems
SAP SD Forums - Do you have a SAP SD Question?

SAP Sales and Distribution Books
SAP SD Books  - Certification, Interview Questions and Configuration

Delivery Hints
SAP Logistics Execution

SAP Sales and Distribution Tips
SAP SD Discussion Forum and Sales/Distribution Tips

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.