The article master record is the data record that contains all the basic information that is required for an article in the system and organizes this data according to various criteria.


Single articles are articles that don't have any characteristics in common with other articles, for example unscented cleaning agents. Generic articles with variants are articles that only differ from one another in certain characteristics values, for example, colors or sizes.
Structured articles are made up of several different articles. You must enter components and quantities which are used for the components in the structured articles.
The display is a number of single articles or variants of one or more generic articles, which is purchased as an individual article, and therefore has as an article number and purchasing price, and purchase price conditions. The manufacturer or vendor prepares the display.
A sales set is a number of single articles or variants of one or more generic articles, which is sold as an individual article, and therefore has an own article number and sales price, and sales price conditions.
Purchasing sets are already purchased as sets, are managed as a set right through the supply chain, or managed on component level in inventory management. They can be sold as a set or as individual components.
A prepack consists of a number of variants of one or more generic articles, is purchased as an individual article, and therefore has an article number, a purchase price and purchase price conditions. Unlike displays, the components of a prepack must belong to the same merchandise category as the prepack itself.

The figure Article Maintenance Views shows significant views of the article master. Further details will be discussed later in the Article Master Configuration lesson.
The basic data of an article incorporates all client-wide data of an article, which is valid regardless of the vendors who supply the article or the sites in which the article is carried. The following belong to the basic data: units of measure, GTINs (EAN/UPC), article groupings, control data for internal processes (for example, assortment list types), validity data, different texts, characteristics from merchandise categories and possibly other freely definable classification data.
In listing, you determine in which sites an article is to be carried and in which period inbound deliveries can be received and sales are possible.
In the purchasing data, a connection is created between articles and vendors/purchasing organizations.
Sales data controls the sale of an article in a distribution chain. The sales data contains sales prices and internal control data for shipping.
Important logistics data for the distribution centers and stores is recorded in the logistics views. It includes requirements planning parameters and forecasting data.
The POS (Point of Sale) data contains POS-specific control data in addition to till receipt texts.
In addition to article specific data, an article master record contains data from other areas that are relevant for the article, such as purchasing, logistics, or sales. These areas are called user departments in the article master. Unnecessary data storage is avoided when all data is stored in a single database object.
The Retail article master is a comprehensive object, which pulls together data from all relevant areas of the system. This ensures that once the article views have been fully maintained, the article can be used right away in all processes, from (requirements) planning, to purchasing, logistics, and sales. All the data can be maintained in just one transaction, the (integrated) article maintenance. When data from different departments in the organization is pulled together, it requires to select and create data for various organizational levels, or areas of validity.

Possible organizational data entries for the individual views:
There are no restrictions to basic data. This data is stored using only the article number itself as a key field.
You can restrict the listing when you access the article master: sales organization and distribution channel .
In order to be able to create purchasing data, you must enter a purchasing organization and a vendor. Within the purchasing data maintenance, you have the option of restricting the validity to a site for creating a site-specific purchasing info record.
* Unlike the other areas of validity, the vendor subrange (VSR) is no data retention level, but an attribute in the purchasing info record. However, in order to have the system pull the right default data for a new purchasing info record from the VSR view in the vendor master, you have to specify the vendor subrange right away in the entry screen of the article master.
Sales data can only be maintained for the combination sales organization - distribution channel. Additionally, sales data can be maintained at site level or price list level (wholesale customers), which you can choose within the sales view. There, you can also select a site group. However, take note that the data that is entered at site group level is not stored at this level - it is stored at the individual site level. So, doing this can lead to an increased volume of data in your system.
The logistics data can be maintained for one distribution center or one store, or for the reference sites. If it is maintained for the reference sites, then it is relevant for all sites. Reference sites are defined in Customizing. There is a reference distribution center and a client-wide valid reference store or reference stores at distribution chain level. Don't specify one particular site or distribution center in the initial screen; instead always maintain the data of the reference site. In the Logistics: Store view, you can additionally maintain the data on distribution chain level, given a corresponding reference site was defined in customizing beforehand.
You must enter at least a distribution chain to completely maintain the POS data.
The data that is maintained in a view can be valid for various organizational levels. Optionally, you can select a site within the POS view to maintain site-specific control data. If you access the POS view client-wide, only the till receipt texts can be maintained, but no POS control data.

Due to the large amount of data in the article maintenance, templates are available when you create article master records.
Reference articles provide default values when you create and enhance article data. All data that has been created for the reference articles can be made available, except GTINs, consumption values, forecast values, and prices and conditions (for purchasing and sales).
The merchandise category reference article is a template for all articles created in that merchandise category. The merchandise category reference article is automatically determined from the merchandise category when the new article is created. You can override this merchandise category reference article by explicitly specifying another article as a template.

When all user departments (views) of an article master record are maintained, it is ready to be used in logistics processes: The stores will be informed about the new article (assortment list), purchase orders can be created, goods movements including physical inventory can be posted, and sales transactions are possible.





