I've been investigating similar behavior in our client's system. However in this case we do want the deliveries to be grouped. This used to happen, but ever since the upgrade from 4.7 to ECC 6.0, every delivery is placed in its own group.
What I've been able to find is that packages are created to process deliveries. Within that package creation process, a check is being done on the BLNRA (Issue document number) field from the line that's currently being processed against the one used when calling the packing routine. If those differ, processing is stopped and the document being processed will be included in a new package, resulting in a new group.
However, there's also a check against the T_VBSK table. The contents of this table are, as far as I could find, the previously processed record. After a record has been added to a package, this value is stored in table XVBSK and later passed onto table PT_VBSK. This last table is passed to the packing routine and used to fill the T_VBSK table.
Now it gets interesting: since 2006, there has been a note implementation (993268) that clears just that PT_VBSK table in include LWFR0F0C. Resulting in an empty T_VBSK, and with no previous records every document is put in its own package and therefore group.
This isn't exactly what you've been looking for, but perhaps it can help in understanding system behavior. What I find strange is that apparently no one has encountered this as a problem... so is this something that should actually happen?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.