Assortment List Message Types 
Assortment List Message Types
Definition
Determines the version of the assortment list you wish to generate (that is, what kind of data is included and how current the information is).
Use
Message Types
The following types of assortment lists are available:
This includes all articles and related data that are currently valid as of the date when the assortment list was generated. If you generate the full version on July 31 and send it to additional recipients on September 1, the assortment list will not include any changes made in August.
This message type is executed by a batch job via the assortment list type parameters.
This includes only those articles for which changes have occurred since the last message was created. Using the above example, the assortment list would only show the changes made in August.
This message type is executed by a batch job via the assortment list type parameters.
This includes the last full version together with all subsequent changes, and therefore shows the current status. Using the above example, the assortment list would be valid as of August 1. This is useful, for example if you want to print the current version at any time. Mixed versions are particularly appropriate for SAP Store, so that store orders and the store assortment are always based on the latest information.
Article data is sorted using the sorting criteria in the assortment list profile. For example, newly listed articles will appear in the appropriate sections (as opposed to all new articles appearing at the end of the list).
It is a good idea to have a mixed version created automatically every time a change version is generated. This way, you will have only one assortment list: a mixed version, which includes the most current data.
With this message type you select the articles and recipients you want, then trigger the assortment list request manually. This allows you to create a customized subset of the assortment list.
This is the same as manually creating a full version. You would use this, for example, if you have a new store and are establishing the assortment in that store for the first time.
Initialization assortment lists may only contain valid data ¾ no error or warning messages. If errors or warnings exist, then the assortment list will not be generated until you resolve the problems. For troubleshooting reports, see
Structure
How articles are arranged in an assortment list depends on the sorting method used. The sorting method used in each case can be defined in the assortment list type. Sorting takes place before the data is prepared and therefore determines which data on an article is read first. The sorting method also determines the structure of the assortment list and the page headers displayed.
The following sorting methods are available in the standard system:
Articles are sorted first by vendor, then by merchandise category, and finally by article number.
If the sorting methods available as standard do not meet all your requirements, you can code your own sorting methods. A customer enhancement (user exit) exists for this purpose.
Some sorting methods allow an article to appear multiple times. For example, if you sort by vendor, the same article will appear for every vendor for which it is valid. If you sort by layout area, the same article will appear for every layout area for which it is valid. In change versions, however, the assortment list only displays those articles, which have changed their relationships. For example, if an article is supplied by a new vendor as well as existing vendors, the article will only appear for the new vendor, since the article’s relationship to the old vendors is unchanged.
To reduce the time needed for generating the assortment list, see also
Splitting the Print Run from the IDoc Run.