How can account determination for planned additional procurement costs be controlled based on the condition type? Please choose the correct answer.

Question

Options

• ABy assigning an access sequence to the condition type
• BBy assigning an account key to the condition type
• CBy assigning a condition record to the condition type
• DBy assigning a calculation schema (calculation schemA. to the condition type

• A
  4% (1)
• B
  4% (1)
• C
  13% (3)
• D
  79% (19)

Explanation

Option D is correct because in SAP MM, the calculation schema (pricing procedure) is the central configuration object that governs how planned additional procurement costs (delivery costs) are handled. Within the calculation schema, each condition type is assigned an account key, which then maps to the appropriate GL accounts - making the schema the controlling framework that links condition types to account determination.

Why the distractors are wrong:

• A (Access sequence): Access sequences control how condition records are searched (the lookup hierarchy across condition tables), not how postings are made to accounts.
• B (Account key): Account keys are the bridge to GL accounts, but they are not assigned directly "to the condition type" in isolation - they are assigned to condition types within a calculation schema, making D the more complete and accurate answer.
• C (Condition record): Condition records store actual values (prices, surcharges, percentages) for a condition type. They determine what amount is applied, not which account it posts to.

Memory tip: Think of the calculation schema as the "rulebook" - it's the document where you decide not only which condition types exist, but also what each one does with the money (via account keys). No schema = no rules = no account determination. When in doubt, the schema is almost always the "control" answer in SAP condition technique questions.

No community discussion yet for this question.