| Inhaltsverzeichnis anzeigen |  |
|
|
|
Product coding
Product coding is used to add material numbers and/or cost types (in Impact Ordering called control structures) to products. These are used to transfer settlement data to a subsequent SAP system, in order to be able to sort by cost centres and material groups.
By allocating material groups and/or product groups and products to all catalog views, it is possible to switch off the display of the cost types for the user, and so the user is not able to select.
Coding works hierarchically for catalog views. This makes it possible for example to code an entire catalog uniformly by writing the coding at catalog level and passing this down to product groups and products. Coding may be created depending on the customer's requirements for each purchasing company. It is possible to pass on coding to subsidiaries. This means that it is sufficient to code the parent company once in a company master from where all subsidiaries are to use the coding of the parent company.
If the product has no coding, a search will be carried out for a coding entry from the product upwards through the product groups to the catalog. If no entry is found, the fallback cost type from the coding defaults is used, if selected and available.
Fallback rules for cost types correspond to the following scenario:
- if cost type 3 is not set, cost type 2 takes effect
- if cost type 2 is not set, cost type 1 takes effect
Only if no cost type is set, the catalog hierarchy takes effect:
- Coding the product is top priority
- then coding the product group
- then the catalog. Coding for material group 1 (or 2) depends on this. The catalog hierarchy always takes effect here.
See also |