SAP Certified Application Associate – Sales and Distribution, ERP 6.0 Ehp7 Free Sample Questions

For the system to automatically generate a purchase requisition from a sales order, a crucial link is the assignment of the sales document's item category to the purchasing document type. This is done in customizing under Sales and Distribution -> Sales -> Sales Documents -> Schedule Lines -> Assign Schedule Line Categories. If the schedule line category is correct but the PR is not created, this assignment is the most likely missing configuration step. The other options are incorrect; transaction groups are not the primary control, the scenario states the item category is correct, and the 'Automatic PO' in the vendor master is for converting PRs to POs, not creating PRs from sales orders.

The strategy for selecting specific batches during the sales and delivery process is controlled by Batch Determination, which uses the condition technique similar to pricing. You define a batch search strategy (e.g., for SD) and create condition records that specify the sort rule, such as sorting by Shelf Life Expiration Date (SLED) in ascending order. This ensures that when a delivery is created, the system automatically proposes the oldest batches first. Shipping point determination, delivery item category, and material master MRP views do not control the batch picking logic.

This status message specifically indicates that the system successfully found a valid condition record via the access sequence, but a prerequisite for its activation was not met. This is the exact function of a requirement routine (assigned in the 'Requirement' column of the pricing procedure). If the logic within the routine returns a false value, the condition is found but not set. A statistical flag would make it non-net-value-relevant but still active. Condition exclusion would deactivate it with a different indicator (often 'Y'). An invalid validity period would prevent the condition record from being found at all.

This scenario describes periodic billing, which is handled via billing plans. The correct setup involves: 1) A sales document type suitable for contracts (e.g., WV). 2) An item category (e.g., WVN) that is relevant for order-related billing and has a billing plan type assigned. 3) The assigned billing plan type must be configured for periodic billing (e.g., monthly invoices). Service contracts are typically not delivery-relevant. Schedule line categories are involved but the primary control is the billing plan assignment on the item category.

The company code represents an independent accounting unit (a legal entity). The sales organization is responsible for sales. Assigning a sales organization to a company code creates the critical link between the sales activities (SD) and financial accounting (FI). This ensures that all revenues, receivables, and other financial postings resulting from sales transactions are correctly recorded in the books of the corresponding legal entity. While this assignment indirectly influences other processes, its primary purpose is the SD-FI integration.

Standard revenue account determination (VKOA) uses a condition technique based on access sequences. The key fields in the standard access sequences are combinations of Application, Condition Type, Chart of Accounts, Sales Organization, Customer Account Assignment Group, Material Account Assignment Group, and Account Key. The Billing Document Type itself is not used as a key field in the standard condition tables for determining the G/L account; instead, the account determination procedure is assigned to the billing document type.

This is the standard functionality of Material Determination. It uses the condition technique to find and propose substitute materials. You create a condition record (VB11) for a specific determination type, specifying the original material (M-01) and the substitute material (M-02) along with a substitution reason. This reason code controls whether the substitution is automatic or requires user confirmation. This configuration is then activated for the relevant sales document type. Listing/Exclusion controls what can be sold, not what can be substituted.

The specific billing type for intercompany billing (standard is IV) is assigned in customizing based on the sales document type of the original customer order. This is done under Sales and Distribution -> Billing -> Intercompany Billing -> Assign Organizational Units By Plant. Here, you define the internal customer number per sales organization and then, in 'Define Internal Customer Number By Sales Organization', you can assign the specific intercompany billing type (ZIV in this case) to the ordering sales organization. This ensures that when the intercompany billing document is created, it uses the correct type.

True. While copy control (VTFA) defines the rules for data transfer from one order to one invoice, the ability to consolidate multiple orders is controlled by ensuring that key header fields are identical across the orders. These fields include the Payer, Billing Date, and Destination Country, among others. The copy control routines check these fields, and if they match, the system can combine the orders into one invoice during a collective billing run (VF04).