If I understand what you're trying to accomplish, you can probably get InventTransPosting to work for you.
The key to InventTransPosting is to properly associate a given InventTrans record (or combination of them) to the proper InventTransPosting record.
InventTransPosting records come in 5 varieties, but the two of core interest are probably just the Physical and Financial, which correspond to the physical and financial updates that can occur to an InventTrans record. If you're doing physical revenue, or have physical or financial charges, those will generate their own InventTransPosting records. The InventTransPostingType indicates each variety.
The primary relationship between InventTransPosting and an InventTrans record is InventTransOrigin. But, since you can have many InventTrans records for a given InventTransId/InventTransOrigin, the relationship must also consider TransDate and Voucher.
The InventTransPosting record for an InventTrans record that is physical updated will join InventTransOrigin == InventTransOrigin, TransDate == DatePhysical, and Voucher == VoucherPhysical. Likewise, for an InventTrans record that is financially updated, InventTransOrigin == InventTransOrigin, TransDate == DateFinancial, and Voucher == Voucher.
Note that due to how InventTrans records can and are often split, two InventTrans records can have the same DatePhysical and VoucherPhysical but with a different DateFinancial and Voucher. That's just how it works, and you have to consider this carefully.
Once you have the InventTransPosting record, the PostingType and LedgerDimension, and OffsetPostingType and OffsetLedgerDimension are primarily what is useful. For example, for an InventTrans record from a sales order that has been invoiced (financial updated), the PostingType will generally be LedgerPostingType::SalesIssue, while the OffsetPostingType will generally be LedgerPostingType::SalesConsump, for the InventTransPosting record of type InventTransPostingType::Financial.
And, of course, LedgerDimension and OffsetLedgerDimension refer to DimensionAttributeValueCombination records.
Hope this helps.
