Validity check is called frequently for distribution model
[ALE_MODEL_INFO_GET] [BMODEL_INT_VALID_GET] [content validity] [MMODEL_INT_VALID_GET] [performance] [period of validity] [TBD06] [validity] [validity sensor]
- Addr Communication cannot be add/modify for future validitySymptom Address communication data cannot be add/modify for the future validity. Other terms BAS_communication, AM 892, Internal error, ADTEL ADDR_COMM_MAINTAIN Reason and Prerequisites When trying to add or modify communication data (telephone,...
Symptom
You use an ALE interface to generate and send IDocs. If you use a very complex distribution model (transaction DB64) with a large number of recipients and filter conditions, you will benefit from reducing the number of calls for reading the distribution model.
Other terms
Performance, TBD06, MMODEL_INT_VALID_GET, BMODEL_INT_VALID_GET, ALE_MODEL_INFO_GET
Reason and Prerequisites
The distribution model is checked several times each time the ALE interface is called, depending on data filtering and recipient determination.
Solution
The distribution model is only determined again if the sender changes recipient relationships.
Use the Note Assistant to implement the attached correction instructions.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}