How can you control the account determination for planned delivery costs based on the condition type?

Question

Options

• AAssign an account key in the condition record
• BAssign an account key in the access sequence
• CAssign an account key in the condition type
• DAssign an account key in the calculation schema

• A
  3% (1)
• B
  5% (2)
• C
  80% (32)
• D
  13% (5)

Explanation

Assigning an account key directly in the condition type is the correct way to control account determination for planned delivery costs, because the condition type is the configuration object that defines the behavior and posting logic for a specific cost element - linking it to a G/L account via the account key at this level applies consistently wherever that condition type is used.

Why the distractors are wrong:

• A (condition record): Condition records store pricing values (rates/amounts), not account assignment logic - they don't have an account key field for this purpose.
• B (access sequence): The access sequence defines the search strategy for finding condition records (which tables to search, in what order); it has no role in G/L account determination.
• D (calculation schema): While the schema (pricing procedure) is where condition types are arranged and can reference account keys, the account key is assigned to the condition type itself, not the schema row - the schema just inherits it.

Memory tip: Think "Condition type = Cost behavior = Control" - all three Cs go together. The condition type is the master definition of how a cost behaves, so it's the natural home for controlling where that cost posts in accounting.

No community discussion yet for this question.