Additionals: Using Assortment List IDocs to Transfer Data
Use
You can send data for additionals to a store using the assortment list IDoc. This data cannot, however, be printed in the assortment list.
Integration
The assortment list IDoc contains all the fields relevant to additionals.
Prerequisites
The procedure for additionals must be flagged in Customizing as being relevant for assortment lists.
Features
When an assortment list IDoc is generated, the system checks whether data for additionals needs to be included in the list. Any such data is copied to the assortment list IDoc if the following criteria are fulfilled:
If you have set the corresponding indicator against a procedure for additionals in Customizing, the additionals that belong to this procedure will be adopted in the assortment list.
Triggering events include: creating new articles to be sold with simultaneous assignment of additionals; subsequent assignment of further additionals to an article to be sold; or changes to a text for an additional.
Triggering events include: changing sales prices for articles if the prices are recalculated; or changing sales prices for articles for a promotion.
Entries containing information about changes to additionals are flagged accordingly in the assortment list IDoc.
With local price changes (when a store reduces prices to undercut the local competition, for example), the initiative is store-based. In this case, therefore, responsibility for generating tickets must be assumed by the store retailing system.
To print labels or tickets you require a translator (or converter) that converts the IDoc data from the SAP system to the required printer format. The standard system does not contain any of this type of converters. (See also:
See also:
Assortment: Assortment Lists