We've seen multiple instances recently where very large journals (15,000+ vouchers) have partially posted. For instance, a journal that contains vouchers with Ledger as the account type and Bank as the offset account type. The ledger portion posted as expected, but nothing posted to the Bank accounts. The journal status remains unposted. Scenarios like this require significant cleanup, including custom script development to eventually mark the partially posted journal as 'Posted'. This seems to happen when users post these large journals interactively instead of using batch posting.

Regardless of the posting method, F&O should execute a roll back routine in an instance such as this where the entire journal is rolled back when posting can't be completed by the system. All enterprise-level ERP systems that I'm aware of perform a rollback when a transaction can't be fully committed/posted.