Transaction calculation

webMethods B2B provides a usage-based subscription model to align costs with the actual usage of services. This usage-based model ensures that you pay for the services that you actively use, which offers better cost control and efficiency.

webMethods B2B measures the following metrics:

Number of transactions
The number of transactions or transaction count is measured by dividing the payload size in bytes by 5120 bytes, which is a 5 KB fragment. Payloads that exceed 5 KB incur an additional transaction for each subsequent 5 KB fragment. The transaction count is rounded up to the next integer.

If a transaction has attachments, the attachments are included in the calculation of the payload size. The attachments are measured separately from the original document. However, if EDI attachments are configured for processing, the EDI attachments are measured as separate transactions and documents.

Message disposition notifications (MDNs) are not measured as part of the total usage.

Number of documents for each payload
webMethods B2B measures the number of documents that are created for each payload, functional acknowledgment, and message delivery notification.

Examples for XML and flat file measurement

XML document size 10 KB
For an inbound XML document of size 10 KB, the document size 10 KB is divided by 5 KB. The transaction count is 2 transactions.
XML document size 11 KB with two attachments: 1 KB and 4 KB
For an inbound XML document of size 11 KB that includes two attachments of 1 KB and 4 KB, the document size of 11 KB is divided by 5 KB and results in 3 transactions, which are three 5 KB fragments. The attachments of 1 KB and 4 KB add up to 5 KB, which results in 1 transaction. The total transaction count is 4 transactions.

The following equation shows how the number of transactions is calculated for documents with attachments:

11 5 + 1 + 4 5 = 4 transactions

Flat file document size 10 KB with two attachments: 1 KB and 4 KB
For an inbound flat file document of size 10 KB that includes two attachments of 1 KB and 4 KB, the document size of 10 KB is divided by 5 KB, which results in 2 transactions. The attachments of 1 KB and 4 KB add up to 5 KB, which results in 1 transaction. The total transaction count is 3 transactions.

Examples for EDI document

EDI documents with attachments and a functional acknowledgment (FA) response are treated as separate transactions. The following list explains the transaction calculation for an X12 document:

  • An X12 document of size 1 KB that includes an attachment of 1 KB and functional acknowledgment of 230 bytes results in 3 transactions. The X12 document, attachment, and functional acknowledgment are measured as 1 transaction each.
  • An X12 document of size 6 KB that includes an attachment of 6 KB and functional acknowledgment of 230 bytes results in 5 transactions.

    The following equation shows how the number of transactions is calculated for documents with attachments:

    6 5 = 1.2 rounded up to 2 transactions

    So, a 6 KB document is measured as 2 transactions, a 6 KB attachment is measured as 2 transactions, and functional acknowledgment response as 1 transaction. The total transaction count is 5 transactions.

Examples for EDI batch document

For EDI batch document, webMethods B2B determines the transaction count by the number of individual payloads within the batch and the size of the payloads.

X12 batch document with 3 payloads of 1 KB each
An X12 batch document that includes 3 payloads of 1 KB each results in 3 transactions. Each payload of 1 KB counts as 1 transaction.
X12 batch document with 3 payloads of 10 KB each
An X12 batch document that includes 3 payloads of 10 KB each results in 6 transactions. Each payload of 10 KB counts as 2 transactions.