SAP MM Study Notes
S4550 · Cross-Functional Customizing in Materials Management · Unit 2

Unit 2: General Settings

Countries, currencies and exchange rates, units of measurement and calendars are maintained once for the whole client (or even the whole system) and are used by every application. Procurement depends on them for addresses, foreign-currency purchase orders, order and price units, and delivery date scheduling.

Lesson 1 · Checking Countries and Currencies

After this lesson you can

  • Explain what is stored per country and where it is checked
  • Describe exchange rate types, especially type M, translation ratios and reference currencies
  • Distinguish direct and indirect quotation
  • Know the options for expiring currencies and for checking/importing rates

Key concepts

Country settings

Every country in which you have suppliers, customers, plants or company codes must exist in the system. Country definitions are client-level settings that apply to all applications; the system uses them whenever addresses and master data such as business partners are maintained. For each country you maintain:

Group of settingsExamples
General dataCountry key, name, nationality, EU membership, ISO codes, date format and decimal notation, address layout key
Country-specific checksPostal code length and checking rule, bank key and bank account number format, tax number checks, VAT registration
RegionsStates, provinces, counties used in addresses and for tax
Telephone country codesInternational dialling prefix

Note what is not a country attribute: you cannot set a time zone or the length of supplier names per country. If you need to create a completely new country (e.g. after a political change), search for SAP Notes that describe the correct country key set-up — SAP delivers guidance for such cases.

Exchange rate types

Conversion between currencies is driven by exchange rate types, which let you hold several rates for the same currency pair on the same date for different purposes (average, bank buying, bank selling, budget, etc.). Type M (standard translation at average rate) is the default used when documents are posted and cleared — including purchase orders in foreign currency when the buyer does not enter a fixed rate manually. The rate table must contain, for type M, an entry for every foreign currency in combination with every company code currency in use. Exchange rates are maintained at client level; they are valid for all company codes.

SettingPurposeT-code
CurrenciesCurrency keys, ISO codes, decimalsOY03
Exchange rate typesDefine types, reference currency, inversion allowed, etc.OB07
Translation ratiosRatio (e.g. 1:1 or 100:1) per rate type and currency pair; can assign an alternative exchange rate type for a currency pairOBBS
Exchange ratesActual rates per type, currency pair and valid-from dateOB08

Alternative (deviating) exchange rate types: for certain currency pairs you can instruct the system to use a different rate type than M; this is entered in the translation ratio table. Changing translation ratios after go-live can create inconsistencies, so plan them up front. Financial Accounting can additionally assign an exchange rate type per accounting document type.

Reference currency: if many currencies must be converted among each other, you can assign a reference currency (e.g. EUR) to a rate type. You then only maintain each currency against the reference currency, and the system converts A → reference → B in two steps. This drastically reduces the number of rate entries.

Direct and indirect quotation

QuotationDefinitionExample (local currency EUR)
DirectPrice of one unit of foreign currency expressed in local currency1 USD = 0.80 EUR
IndirectPrice of one unit of local currency expressed in foreign currency1 EUR = 1.25 USD

Which notation is used depends on market convention and can be set per client and currency pair. Indirect quotation became widespread with the introduction of the euro, when rates were published relative to EUR; it is now common internationally.

Automatic rate updates and tools

  • Daily rates can be loaded electronically using the IDoc type EXCHANGE_RATE or the report RFTBFF00; SAP also documents how to pull rates from the European Central Bank.
  • FXM_CONVERTER checks conversions with current rates; in the Fiori launchpad this is the Currency Converter app (treasury front-office role).
  • The Import Foreign Exchange Rates app uploads rate files (treasury risk manager role).

Expiring currencies

When a country replaces its currency (as happened when countries joined the euro), you can control how long the old currency remains usable. Under SAP NetWeaver › General Settings › Currencies › Expiring Currencies you define expiry reasons, declare a currency as expiring, decide via warning or error messages how long it may still be used, define special authorizations for continued use, and set up automatic translation into the new currency for follow-on processes.

Process flow

Check translation ratio (alt. rate type?)→Check rate type (reference currency?)→Enter rates (directly or vs. reference currency)→PO in foreign currency uses type M

System steps

  1. Check the country key, formats and checks with OY01 and the country-specific checks with OY17.
  2. In OBBS, locate rate type M with the two currencies; note any alternative rate type and the ratios.
  3. In OB07, check whether that rate type carries a reference currency.
  4. In OB08, enter the rate for the pair — or, if a reference currency is used, enter each currency against the reference currency.
  5. Test with FXM_CONVERTER / Currency Converter, then create a PO in foreign currency (ME21N) to see the proposed rate.

Configuration (IMG)

SPRO › SAP NetWeaver › General Settings › Set Countries › Define Countries in mySAP Systems SPRO › SAP NetWeaver › General Settings › Set Countries › Set Country-Specific Checks SPRO › SAP NetWeaver › General Settings › Currencies › Check Exchange Rate Types SPRO › SAP NetWeaver › General Settings › Currencies › Define Translation Ratios for Currency Translation SPRO › SAP NetWeaver › General Settings › Currencies › Enter Exchange Rates SPRO › SAP NetWeaver › General Settings › Currencies › Expiring Currencies
Practical tip

If a foreign-currency PO shows an unexpected rate, first check OBBS: an alternative rate type for that currency pair overrides M. Also remember the buyer can fix a rate in the PO header (the "Exchange rate fixed" indicator) so invoice verification uses the PO rate.

Exam focus
  • Countries and exchange rates are maintained at client level — not per company code, plant or purchasing organization.
  • Per country you can define, e.g., date format and postal code length — not time zone or supplier-name length.
  • Exchange rate type M is the standard in MM; at least one M entry per foreign currency/company code currency is required.
  • Reference currency = two-step translation; alternative rate type = assigned in translation ratios.
  • Direct quotation: 1 foreign = x local. Indirect: 1 local = x foreign.

Lesson 2 · Defining Units of Measurement

After this lesson you can

  • Explain dimensions, SI units and conversion via numerator/denominator
  • Maintain a new unit of measure with commercial/technical keys and ISO code
  • Know which flag makes a unit usable in purchasing and what the value-based commitment flag does

Key concepts

Units of measure (UoM) are used for display and printing (e.g. on purchase orders) and for converting quantities (kg ↔ g, cm ↔ inch). SAP's definitions follow the International System of Units (SI), which has seven base units from which all others are derived. Units are maintained centrally (transaction CUNI) and are valid for every application in the system.

TermMeaning
DimensionA group of units that measure the same physical quantity and can therefore be converted into one another (length, mass, volume, time …). Each dimension is described by exponents of the seven base dimensions — e.g. volume = length³.
SI unitThe reference unit of a dimension (metre for length, cubic metre for volume). It cannot be changed.
Conversion factorNumerator / denominator (whole numbers) plus an optional exponent and additive constant relating a unit to the SI unit. Example: litre = 1/1000 m³.
Dimensionless unitsUnits such as piece, box, pallet belong to the pseudo dimension AAAADL, which has no SI unit — so no numerator/denominator can be set. Conversions (e.g. 1 box = 12 pieces) are maintained per material in the material master (Units of Measure / additional data).
Internal keyUnique, language-independent key used in the database. Never change the internal keys of delivered units.
Commercial keyExternal, language-dependent key (max. 3 characters) shown in documents.
Technical keyExternal, language-dependent key (max. 6 characters).
ISO codeInternational code required for exchanging documents via EDI/IDoc.
Commercial measurement unit flagMust be set if the unit is to be used in business transactions such as purchasing.

Where units are used in logistics

Units of measure appear as base unit of measure (client level in the material master, the unit in which stock is managed), order unit, order price unit, unit of issue and sales unit. All alternative units of a material are converted to the base unit.

Value-based commitment indicator

If commitments are posted for account-assigned purchase orders, a flag on the unit of measure decides how commitments are reduced:

FlagCommitment behaviour
Not set (quantity-based)Commitment is reduced by quantity; it is cleared once the full quantity is delivered or the delivery-completed indicator is set. Invoice price differences do not change the commitment.
Set (value-based)Commitment is reduced by value. Automatic clearing happens only for items with a valuated goods receipt. Without GR (or with non-valuated GR) and an invoice price below the PO price, the remaining commitment must be cleared manually via the final invoice indicator (in invoice entry or in the PO).

Process flow

Check / create dimension→Create unit in dimension→Numerator / denominator to SI unit→Language-dependent keys & texts→ISO code + commercial flag

System steps

  1. Start CUNI; on the Dimensions tab check that all needed dimensions exist (create new ones with the base-dimension exponents if required).
  2. Choose Units of measurement, select the dimension, and create the unit: internal key, commercial and technical keys and text per language.
  3. Enter numerator, denominator (and exponent) relative to the SI unit; set decimal places for display and rounding.
  4. Set the Commercial meas. unit indicator so the unit can be used in purchasing, and maintain the ISO code (via ISO codes) for EDI.
  5. Decide on the Value-based commitment flag if commitments are used.

Configuration (IMG)

SPRO › SAP NetWeaver › General Settings › Check Units of Measurement
Practical tip

Unit definitions are client-independent; a change in the development client is effective immediately for all clients of that system. Translate the external keys into every logon language used, otherwise users may see unexpected keys on documents.

Exam focus
  • Convertible units belong to the same dimension.
  • EDI needs the ISO code; purchasing needs the Commercial measurement unit flag.
  • Commercial key max. 3 characters, technical key max. 6 characters, both language-dependent.
  • Dimensionless units (AAAADL) have no SI unit; conversion factors are stored per material.
  • The base unit of measure of a material is a client-level field.

Lesson 3 · Setting Up a Factory Calendar

After this lesson you can

  • Explain the three calendar layers: public holidays, holiday calendar, factory calendar
  • Use special rules (e.g. plant shutdown, rebate settlement dates)
  • Assign factory calendars and distinguish them from planning calendars (MD25)

Key concepts

Logistics (MRP, scheduling, delivery date checks in purchasing) and Finance need to know which days are working days. SAP builds this information in three layers, maintained with SCAL:

LayerContent
Public holidaysIndividual holidays with their date rule (fixed date, fixed weekday, Easter-dependent, etc.), religious denomination and the option to make them "guaranteed" — a guaranteed holiday falling on a non-working day is moved to the previous or next working day.
Public holiday calendarA collection of public holidays valid for a country or region, defined according to legal requirements.
Factory calendarBased on one holiday calendar; adds which weekdays are working days, the validity period and special rules.

Special rules declare individual dates or ranges as working or non-working days, e.g. a company-wide vacation shutdown. They are also used to fix the dates on which settlement of end-of-period volume rebate arrangements takes place (e.g. quarterly interim settlements). Supplier-specific special rules (such as the supplier's own shutdown) cannot be defined.

Assignment: a factory calendar is usually assigned to a plant (plant definition). Work centers can carry a different factory calendar if their working days differ. Storage locations and company codes do not have factory calendars.

Calendar definitions are client-independent.

Planning calendar versus factory calendar

A planning calendar (MD25, under Logistics › Production › MRP › Master Data › Planning Calendar) is plant-specific and defines period lengths or cycles — for MRP lot sizing, for planning cycles, for scheduling, and in MM for release creation profiles of scheduling agreements. It is maintained independently: changing the factory calendar does not update planning calendars, so they must be regenerated if necessary.

Process flow

Define public holidays→Group into holiday calendar→Define factory calendar (+ special rules)→Assign to plant / work center

System steps

  1. In SCAL, check or create the public holidays (date rule, guaranteed flag).
  2. Create a holiday calendar for the country/region and assign the holidays; set the validity years.
  3. Create a factory calendar: link the holiday calendar, mark working weekdays, enter special rules (e.g. quarterly rebate settlement days, shutdown weeks).
  4. Assign the factory calendar to the plant in the plant definition (OX10) and, if required, a different calendar to individual work centers (CR02).
  5. If plant-specific periods are needed, create a planning calendar with MD25.

Configuration (IMG)

SPRO › SAP NetWeaver › General Settings › Maintain Calendar SPRO › Enterprise Structure › Definition › Logistics – General › Define, copy, delete, check plant (factory calendar field)
Newer releases (2021–2025)

Recent SAP S/4HANA releases provide a reworked calendar maintenance with SAP Fiori apps for public holidays, holiday calendars and factory calendars, and the classic SCAL maintenance is being phased out. Check the simplification list of your release to see which maintenance tool applies.

Exam focus
  • Special rules exist only in the factory calendar.
  • Factory calendars are assigned to plants and work centers — not to storage locations or company codes.
  • Calendars are client-independent.
  • Planning calendars can be used in release creation profiles (scheduling agreements) and are not updated automatically by factory calendar changes.

Unit summary & exam focus

General settings are cross-application and mostly client-level or client-independent. In MM they surface as addresses and country checks for business partners, the exchange rate (type M) in foreign-currency purchasing, the units on POs and in EDI, and the working-day logic that drives delivery dates and rebate settlement dates.

T-codes in this unit

T-codePurpose
OY01Define countries
OY17Set country-specific checks
OY03Define currencies
OB07Exchange rate types
OBBSTranslation ratios / alternative exchange rate types
OB08Enter exchange rates
FXM_CONVERTERCurrency converter
ME21NCreate purchase order (test of foreign-currency rate)
CUNIUnits of measurement and dimensions
SCALPublic holiday and factory calendar maintenance
OX10Define plant (factory calendar assignment)
CR02Change work center (own factory calendar)
MD25Create planning calendar

Self-check questions

  1. At which organizational level are exchange rates maintained?
    AnswerClient level — they apply to all company codes.
  2. A PO in USD is created for a EUR company code without a manual rate. Which rate is used?
    AnswerThe rate stored under exchange rate type M, unless an alternative rate type has been assigned to the currency pair in the translation ratios.
  3. What is the benefit of a reference currency?
    AnswerYou only maintain each currency against the reference currency; conversions between any two currencies run in two steps via the reference currency.
  4. Which two settings are needed for a new unit of measure to be used in purchasing and in EDI?
    AnswerThe Commercial measurement unit indicator (purchasing) and an ISO code (EDI).
  5. Why can you not enter a numerator/denominator for "carton"?
    AnswerIt is dimensionless (pseudo dimension AAAADL) and has no SI unit; conversions are maintained per material.
  6. Where do you define the dates for quarterly rebate settlement?
    AnswerAs special rules in the factory calendar.
  7. Does changing the factory calendar update the planning calendar?
    AnswerNo — planning calendars (MD25) are maintained independently.