C-TS462-2021 Sample Questions & Answers

This statement is false. In addition to the general 'Customer' role (FLCU01), the Business Partner must be extended to the specific Sales Area (Sales Organization, Distribution Channel, Division) in which the sales order is being created. Without the sales area-specific data (e.g., shipping conditions, billing information, partner functions), the system cannot process the sales document.

The partner determination procedure defines which partner functions are used in a transaction. This procedure is assigned to the sales document type. If the 'Ship-to Party' (WE) function is missing from this procedure, or if it is not configured to be sourced from the 'Sold-to Party' master data, it will not be determined automatically.

The availability check is controlled by the combination of the checking group (from the material master) and the checking rule (hard-coded for the SD transaction, e.g., 'A' for sales order). This combination determines the scope of the check, which defines exactly which stock elements (like safety stock) and receipt/issue elements (like production orders) are included in the ATP calculation.

SAP Revenue Accounting and Reporting (RAR) is the standard solution for complex revenue recognition scenarios like IFRS 15. The integration is triggered by settings in the sales item category. This creates a revenue contract in RAR, and the performance obligation (POB) can be configured for time-based recognition, allowing revenue to be posted correctly each month, independent of the billing document.

Default delivery and billing blocks can be set directly in the sales document type configuration to be automatically applied when a document of this type is created.

The assignment to a specific number range interval (either internal or external) is a key setting defined directly within the sales document type configuration.

Route determination is configured based on a combination of factors. The system uses the departure country/zone (from the shipping point) and the destination country/zone (from the ship-to party) as the primary key. Within this entry, it finds a specific route based on the shipping conditions and transportation group. This setup allows for granular control over route proposal.

The incompleteness procedure is used to define which fields in a sales document are mandatory. By including pricing-related fields (like net value) in the procedure and assigning it to the document type/item category, you can configure the system to prevent saving the document until the data is complete, thereby ensuring pricing was successful.

Condition exclusion is the standard SAP functionality designed for this purpose. By placing the two condition types into different exclusion groups and then setting a rule (e.g., 'Best condition between groups' or 'Exclude B if A exists'), you can declaratively manage which discount takes precedence without custom coding (requirement routine). This is the most efficient and maintainable solution.

The Customer-Material Information Record (CMIR) is specifically designed to store data for a unique combination of a customer and a material. It allows you to define customer-specific material numbers, descriptions, and, critically, default values for fields like delivering plant, delivery priority, and shipping conditions, which will override other master data defaults.

This combination is correct for standard Third-Party Processing. The item category (e.g., TAS) triggers the process. The schedule line category (e.g., CS) is the engine that automates the creation of the purchase requisition by specifying the PR Order Type and the Account Assignment Category (e.g., 'X' for third-party). This ensures the sales order item is linked directly to a procurement document for fulfillment.