Create a Transaction Journal

Use transaction journal records to capture information stored in sale documents such as orders, invoices, and shipments. This information is processed to update the Partner Unsold Inventory (PUI) records. A PUI record is created for each sale document, reflecting the original product quantity in the sale document.

Required Editions

Available in: Enterprise, Professional, and Unlimited Editions with the Channel Revenue Management add on

User Permissions Needed
To create transaction journals	Channel Partner Inventory Admin User

To track this inventory, create Partner Unsold Inventory (PUI) records by running the Data Processing Engines (DPEs) that accurately calculate the remaining quantity of inventory. This data is used to create the partner unsold inventory and partner unsold inventory ledger records.

Note We recommend that you add the Account, Product, Quantity, Price, and Journal Type information while creating a transaction journal record.

1. From the App Launcher, find and select Transaction Journals.
2. Click New.
3. Search for an existing account or create an account.
4. In the Journal Type field, select Sale Document when selling inventory to a partner.
5. Select the Activity Date.
6. For the Status field, select Pending.
7. Select a product and price type.
8. Enter the quantity of products sold in that transaction.
9. Enter an amount in the Sale Unit Price or Resale Unit Price field.
10. Enter the transaction amount for this transaction.
11. Save the record.

Note When creating a Transaction Journal in an org where both Rebate Management and Channel Partner Inventory Management are enabled:

• Specify the Journal Type for Channel Partner Inventory Management. The Journal Type determines how the Transaction Journal is used within Channel Partner Inventory Management processes. If the Journal Type is left blank during creation, the system defaults the Usage Type to Rebates.
• Configure DPE filtering on Status for Rebates Transaction Journals. Rebates DPEs do not automatically exclude records based on the Transaction Journal Status field. If customers intend to use the Status field (for example, Approved, Rejected, or Pending) to control which records generate aggregates or payouts, they must explicitly configure filters in the Rebates DPE definitions. For example, to ensure that only eligible records are processed and to exclude any status other than Approved (such as Pending or Rejected), include filter logic such as: TransactionJournal.Status = 'Approved'.
• Review legacy records for compatibility. If existing Rebates Transaction Journal records default to a Pending status, note that DPEs do not filter by Status by default and will process all PoS transactions. Ensure that the appropriate DPE filter logic is configured so that the correct records are processed and unintended records are not included or excluded.