How SAP Retail Listing Works – From Assortment Module to Site Availability
You receive a step-by-step overview of the SAP Retail listing concept, showing the exact procedures and technical updates required to make an article available for business transactions; omitted updates can block sales. Read community notes: Solved: Listing with assortment modules
Key Takeaways:
- Listing ties articles to assortments and specific sites: the process assigns articles to assortment headers, links assortments to sites, and records validity periods that determine where an article can be sold or purchased.
- Assortment module drives the workflow: create assortment, add articles, assign target sites, run approval/release, and trigger updates that make listing data active for downstream processes.
- Affected data areas include material master views (general, plant, sales), assortment/listing records, and site stock/master data; released listings set flags and dates that the system reads for availability and purchasing checks.
- Availability check combines listing status with master data and inventory: the system verifies site-level listing flag, plant/purchase info, current stock and ATP/availability rules before allowing sales or purchase transactions.
- Common control points and exceptions include site-specific blocks, overlapping validity windows, assortment hierarchy rules, and custom enhancements or interfaces that must update POS/availability and be monitored via logs and discrepancy reports.
Core Concepts of the Listing Process
Listing in SAP Retail shows you how the fundamental listing concept acts as the gateway for article master data to be utilized in specific retail sites, enabling controlled publication of item data, validity and site-specific behavior.
Defining the Listing Framework
Framework rules let you assign listings to assortments, set site scope, validity dates and status; the listing concept clarifies the gateway role so you control where and when articles appear in each retail site.
The Relationship Between Articles and Assortments
Articles link to assortments so you publish article master data to target retail sites, managing price, availability and site assignment through listing entries.
You treat the listing as the single point where the exploration of the fundamental listing concept which acts as the gateway for article master data to be utilized in specific retail sites becomes operational: listings decide which article attributes, prices and availability are exposed per site and you maintain validity dates and statuses at listing level.
Executing SAP Listing Procedures
Procedures give you a detailed look at the step-by-step listing procedures used to link articles to modules and organizational levels; consult the SAP guide Assortment Management and Listing to map articles, set assortments, and confirm site scope with module-to-site mapping.
Manual vs. Automated Listing Methods
Manual methods let you assign articles via the UI at module and organizational levels for precise control; automated rules and batch jobs apply listings across many sites in one run-automation speeds rollouts but can propagate errors if rules are misconfigured.
Managing Validity Periods and Assortment Assignments
Periods for listings let you set start/end dates per article-module-organization so you control promotional windows and seasonal assortments; always check overlaps and activate correct assignments to avoid mismatches across sites.
You follow the step-by-step listing procedures used to link articles to modules and organizational levels: select the article, choose the target module, pick organizational nodes (company code, sales organization, distribution channel, plant/site), enter start and end dates, assign to an assortment, save and activate. After that run propagation or batch listing jobs and validate site availability reports; overlapping validity ranges or wrong org-level selection can list items at incorrect sites and require manual correction, so audit assignments before mass activation.
Technical Architecture: Tables Updated During Listing
Listing writes directly to MARA, MVKE and MARD so you keep material, sales, and stock records synchronized; CDHDR/CDPOS record change logs to preserve data integrity throughout the process.
Primary Listing Tables and Data Storage
Primary tables include MARA (material master), MVKE (sales org), MARM (units), and MARD (plant stock); you must track user IDs and timestamps to prevent inconsistent site availability.
Verification of Master Data Records
Check MARA fields (MATNR, MTART, MATKL) and links to MVKE (VKORG, VTWEG) using change logs so you validate statuses, distribution channels, and activation dates before publish.
You should run SE16N queries on MARA, MVKE and MARD, reconcile MATNR/VKORG/LGORT entries, and inspect CDHDR/CDPOS for user/timestamp audit trails; any missing MATNR, duplicate records, or zero stock in MARD can prevent site availability or trigger rollback procedures.
Determining Article Availability at the Site Level
SAP evaluates an article’s listing status in the assortment module to determine if you can purchase or sell it at a site; consult Listing with Assortment Modules for rules, and note the system enforces site publish flags before permitting transactions.
Validation of Purchasing and Sales Eligibility
You validate eligibility by checking listing indicators and purchase/sales flags in the assortment module; the system blocks orders if the article’s listing status is inactive at that site.
Site-Specific Constraints and Requirements
Site constraints include catalog assignments, regional approval statuses and inventory rules that override global listings; you must align site master data so the article’s sales availability matches local requirements.
Local teams must map site master data, catalog assignments, stock thresholds, and regional approval statuses so the system applies site rules. Analysis of how SAP determines whether an article is available for purchase or sale at a given site based on its listing status shows the assortment module enforces site publish flags and inventory constraints before orders proceed.
Final Words
Now you have a final summary of the listing lifecycle, tracing the path from the initial assortment module to confirmed site availability for retail operations, showing how assortment setup, listing approvals, pricing, and inventory checks lead to live site status for stores and e-commerce channels.
FAQ
Q: What is the listing concept in SAP Retail and how does it relate to assortments and sites?
A: Listing is the mechanism that controls whether an article is permitted for sale or purchase at a specific site by linking article master data to assortments and site assignments. An assortment defines a collection of articles for a set of sites or a trading area. A listing entry ties an article (or article group) to an assortment and a site with attributes such as listing type (sale, purchase), validity dates, allowed quantities, and status flags. The material master remains the central record for the article, while assortment and listing data determine the article’s operational presence at individual sites.
Q: What are the step-by-step procedures for creating, approving, and activating a listing in SAP Retail?
A: Create the assortment header with scope and target sites, maintain basic assortment attributes and time validity. Add assortment lines by assigning articles or article groups to the assortment and set line-level attributes such as listing type, validity period, and stocking/procurement flags. Submit listing lines to the configured approval workflow or change the listing status to “ready for approval.” Route listing for approval; approvers inspect attributes, site assignments, and conflicts before setting the status to “approved.” Activate approved listings by releasing them for distribution; the release triggers replication to site systems or ERP/retail distribution layers. Verify replication status and update any missing attributes or mapping errors, then monitor site acceptance and operational flags that permit sales or procurement at the site.
Q: Which SAP tables and master-data records are typically updated during the listing process?
A: The listing process updates a combination of master-data tables and retail-specific assignment records. Material master tables such as MARA and industry-relevant segments (for sales/plant data) are referenced and may get linked fields updated. Plant- and storage-location tables such as MARC and MARD record site-specific settings and stock but are not the primary listing store. Assortment and listing header/line tables in the Retail Assortment module hold the actual assignment records and status fields; approval and workflow tables capture status history and user actions. Replication or distribution queues and partner interfaces record messages and transfer results to POS or decentralized site systems. Custom or industry solutions can add mapping tables for integration with merchandising or promotion systems.
Q: How does SAP determine whether an article is available for purchase or sale at a given site during runtime?
A: The system evaluates a sequence of checks to determine site availability. The listing check verifies that an active listing entry exists for the article and site with a matching listing type and valid dates. The material master is checked for block indicators and site-specific procurement/sales settings. Source-of-supply and procurement assignments are consulted for purchase availability, and sales-organization/plant data or POS mapping is consulted for sales. Inventory availability for the site (on-hand and reserved quantities) is read from site stock records to decide immediate availability. Business rules and configuration settings such as forced-listing enforcement, exclusion lists, and price/condition dependencies are applied to finalize the decision. If any required listing or site flag is missing or a blocking indicator is set, the system prevents sale or purchase according to the configured enforcement level.
Q: How do the assortment module, listing records, and site availability interact during a typical sales or ordering transaction?
A: A typical flow begins with the assortment module providing the list of articles eligible for a set of sites; approved listing records ensure those articles are active for the specific site. At transaction runtime (POS sale or order entry) the system queries the listing assignment for the article-site pair and checks validity and status. The transaction engine next verifies material master block flags and site-specific procurement/sales settings, then reads site stock levels to determine fulfilment feasibility. If the listing and master-data checks pass and stock or replenishment rules permit fulfilment, the transaction proceeds. If any check fails, the transaction is blocked or flagged for backorder or alternative sourcing, and exception handling routes the item through approval, substitution, or replenishment processes.