Direct Creation of Worklist Entries
In the procedure described inWorklist Generation the entries in the worklist are created on the basis of the change pointer for condition changes (message category CONDBI) within worklist creation (transaction MEI4). However when creating worklist entries directly, change pointers are no longer needed. When you change a condition and create new conditions entries are now created directly in the worklist. This means that the previous performance-intensive process step of creating a worklist from change pointers is now eliminated. You also no longer need to update change pointers for condition pointers if these are not going to be used in other processes.
If change pointers for condition changes are eliminated, the dataset for change pointers is reduced considerably. A change pointer generally consists of several entries in table BDCP or BDCP2.
The following differences occur:
Customizing for worklist creation described above, which determines which condition types are to be included in the worklist (table T6I1), is also valid for direct creation.
The extra data for a worklist entry consists of header data for the conditions, which improve performance in subsequent processing and variable customer fields, which enable selective subsequent processing. The filling of customer fields is determined by the system table T6I2S. The filling of customer fields can, however, also be manipulated using the BAdI WIND_UPDATE.
For each document type, you can determine the types of condition changes (amount change, validity, relevancy to costing etc.) for which worklist entries are created. Customer-specific filter criteria can also be created using the BAdI WIND_UPDATE, which is dependent on the filter criterion Document type.
The following example illustrates the possibilities of the BadI:
Due to changing purchasing conditions, perishable articles are recalculated at regular intervals therefore sales prices do not need to be updated using the pricing worklist process. In this case, use the article type as an additional filter criterion for the Pricing application (document category 10). When you change the basic purchase price for a perishable article, the system does not generate a worklist for this document category because of the filter criteria set in place.
If you want to use the worklist in conjunction with the procedure for direct creation of worklist entries, there are two different cases to distinguish between:
For each document category, determine the types of condition changes for which you want worklist entries to be created as filter criteria. Different types of condition changes (scope of change) relevant for this application are delivered as standard for the individual document categories. The scope of change delivered for direct entry is identical to the scope of change for updating change pointers for this application.
The filling of variable customer fields for the worklist entries is preset by system table T6I2S in the delivery status. If you want to proceed differently to the default setting, you need to create a suitable implementation for the BadI.
The check for existing document indices (table S111) that is possible in the worklist creation procedure using change pointers, now needs to be implemented in the BadI WIND_UPDATE as an additional filter criterion (see Sample Coding for the BadI).
If direct creation of worklist entries is set for all document categories used, you do not need to create change pointers from the message category CONDBI. Deactivate the message category CONDBI in ALE Customizing.