EXF batches DO affect the accumulator, they can seriously flood it and make a mess if say, the person shooting the batch enters an amount far above what they actually need to fill the shelf. If a TL shoots a batch for an endcap that can hold three ottomans and they enter an arbitrary amount like 100 for the requested amount, the system is programmed to think that 100 ottomans are NEEDED to fill the floor, even though that's definitely not the case.
In this example, if there are 5 ottomans located in the backroom, it will pull all 5 and place them in an EXF batch, of which three will fit on the endcap (assume the home location is already full). The other two ottomans are backstocked. Next time the hourly CAFs roll around, the system still has a demand for 95 ottomans, so it will pull those two, and they won't fit (assuming none have sold), so they'll be backstocked again and pulled again in the next CAF, backstocked, pulled, etc. Theoretically this will happen until the demand of the accumulator is met and the value is back at zero.
Granted, this can easily be fixed by a backroom team member who is sick of seeing these ottomans come out in the pulls only to backstock them repeatedly. He would do a subt-9999 to "reset" the accumulator value back down to zero, the demand would disappear and they would stop coming out in the CAFs.
The moral of the story is, an EXF can create extra, unnecessary work if it is not properly done by someone who knows how they are affecting store systems.
EXF's do not affect shelf capacity. I don't think there is anyway to change shelf capacities at the store level - they are set by people at headquarters, the same people who make planos/SPLs.
Also, subtracting a high amount doesn't affect any score that I know about.
[mod]NEVER perform any OUTS/research/EXF function if you do not know what you're doing and how it affects store processes![/mod]