C_TSCM62_67 SAP Certified Application Associate – Sales and Distribution, ERP 6.0 Ehp7 Practice Questions

This is the classic use case for a requirement routine in output determination. The output determination procedure allows you to assign a requirement to an output condition type. This routine is a piece of pre-written logic that checks certain conditions before the output is proposed. There are standard routines available, and one can be created (VOFM) to check if the sales order net value (VBAP-NETWR) is greater than a certain amount. If the condition is met, the routine allows the output to be processed. Using the access sequence is incorrect as order value is transactional data, not a key for finding a condition record.

Text determination controls which text types are available for different objects (like sales document header or item). A text determination procedure is defined and assigned to an object, such as an item category. This procedure contains the list of allowed text types. If a specific text type is missing from the procedure assigned to the item category of the sales order item, it will not be available for the user to select. This is configured in transaction VOTXN.

In a standard returns process that is delivery-related, the customer returns goods against a returns order and a returns delivery document. Before the company can issue a credit memo (the billing document), it must confirm receipt of the returned goods. This is done by posting a goods receipt (PGR) for the returns delivery. This step updates inventory and serves as the trigger that allows the credit memo request to be billed. Without the PGR, the returns delivery is considered open and is not relevant for billing.

The requirements type is the central control for the Make-to-Order process. It determines how the sales order demand is treated by planning (MRP). A specific MTO requirements type (e.g., KE) will ensure that the sales order creates an individual customer requirement that is visible in MRP and triggers the creation of a planned order linked directly to that sales order. This requirements type is determined via a strategy group in the material master and is ultimately assigned to the transaction via the schedule line category.

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.