An output type has an access sequence involving two conditions tables; the second access is a generalization of the first access. The first access has no effect.
Example:
We configured output determination with one condition type, containing two condition tables, the first based on Shipping Point and Loading Point and the second on shipping point alone.
When creating a delivery, the loading point is blank and therefore does not find a match in the first condition table and therefore goes to the second table and finds a match in the shipping point. Output is determined and a printer identified.
Going to the Delivery header screen in the delivery and entering a loading point does seem to redetermine the output, which is great, for if you go to the delivery output screen in the delivery and then go through the menu 'Goto > Output Determination > Details' the result indicated that the new determination including the loading point has been found.......great so far.
However, when you go to the communication screen, the printer name has not changed as was expected, seeing that the determination had changed and that the record for each condition table was set up with different printer names.
In the general, first access, the 'Exclusive condition access' flag was not set.
As a result, even when the initial (specific) step is successful, the access sequence is continued, and the general access is performed; this general access overwrites the specific access.
Here it is also important that the keys of the found outputs are identical. The key consist of application, output type, object key, language, partner function, and partner type. The access is overwritten if the key fields are identical. In the condition records you can create differences in the key fields with the fields language, partner function, and partner number.
In the detail screen of the access sequence for the first (special) access set the indicator: 'Exclusive condition access'.
No comments:
Post a Comment