Transaction Groups are used to categorise various transaction types. Charges will then apply based on the quantities or values of these grouped transactions according to the definition established in Publisher Client Charge maintenance.

Transaction Groups Codes are user defined and established on TMSPS/TGC, either as locational based, transactional based or for external charges. The transaction selection allows a comprehensive selection of data available on the Transaction, Customer, Title and Warehouse files. The following are a few examples of transaction groups, which may incur different charge rates.

• Type of Transaction (document type, document sub type, and picking method).This is used to determine orders such as Normal invoices, credits, releases etc.
• Source of order can be used to group orders that are entered via the Internet, telephone and others.
• Priority of orders can be used to determine a high priority, which would relate to premium service.
• Order size would be used to determine smaller orders, which would require more labour per order and therefore a higher charge.
• Destination of goods shipped may determine the charges by distance etc.

An example of a transaction group is Book Club transactions. In this instance a Transaction Group is established for the various Book Club transactions that can be processed on behalf of a client, like normal sales, claims and possibly re-invoicing.

For normal sales, the warehouses to be included are nominated, the document type that indicates a normal sale is nominated for selection and any backorder reasons and types of sale to be excluded are entered in the respective value fields.

Invoice only transactions where there is no inventory handling involved, for example drop shipments could attract a different charge from indent titles or normal sales.

For claims, the warehouses that process claims may vary from the sales warehouses, the document type will differ from sales but perhaps the backorder reason codes and types of sale to be excluded are the same as for sales. Returns could fall into various categories where each requires a transaction group as the fee structure varies according to the handling required.

• Mint Returns fit for resale
• Non mint Returns fit for remainder
• Non-mint Returns not fit for remainder and to be pulped
• Returns to be sent back to customers
• Returns that raise a claim.

Add a transaction group definition

1. In the menu, expand Publishing Modules > 3rd Party Logistics > Maintenance and double-click 3PL Transaction Group Maintenance. PSM020 Transaction Group Maintenance panel appears.
2. Click Add. PSM010 Publisher Client Maintenance panel appears in add mode.
3. Enter the new transaction group code and select the appropriate group code type as setup in TMSPS/TGC-TYP (sales based, transactional based or yearly stock based).
4. Click OK to add the selection options and its values for the new transaction group code.
5. Enter the selection option and the values for each the fields to be included or excluded in the definition.
6. Page down and repeat step 5 until the last page.
7. Click OK. Transaction group definition is added.