Product transaction query
Items that are defined for each product on a notice are used in the product transaction query to search for product activity or history. You can define a date range and the types of transactions that are searched. These items are located by the Product Transaction Query:
| Transaction type | Description |
|---|---|
| Requisition lines | Unreleased or released requisitions where a Purchase Order or Shipment has not been created. |
| Purchase order lines | Non Stock or Special items that were not fully canceled and inventory items where the quantity was not fully received or canceled. The search is performed for each company within the procurement group/item lifecycle management group, where the PO date falls within the query date range. |
| Inventory | Inventory locations that have stock on hand for each company within the item group/item lifecycle management group/procurement group. |
| Par locations | Par locations for each company within the item group//item lifecycle management group/procurement group. |
| In transit transfers |
Direct transfers are not shown. They are already reflected in the Inventory balances. |
| Issues |
|
| Procurement templates | Matches on item for the procurement group/item lifecycle management group. |
| Sourcing event lines | Matches on non-service items for all companies within procurement group/item lifecycle management group/sourcing group, where the event line is not closed or canceled. |
| Contract lines | Matches on non-service items for the procurement group/item lifecycle management group, where the contract line is not inactive or closed. |
| Equipment | Matches on the model number or the serial number of the product
in . This is a separate query based on whether the Equipment field is selected on the notice. |
How responders and task are assigned to a notice by the product transaction query
The product transaction query cross references the transaction information against the key organization structure that is defined in Item Lifecycle Management. Using location information, the responders are assigned to the organization structure and tasks are automatically assigned to the responder. If you have task instructions on a product, those are associated automatically. If a responder is not defined for that particular location, the query continues up the organization hierarchy to find the responder assigned.
If a transaction has a location not defined in the organization structure, then a task is created with no one assigned to it. The task must be assigned to a responder before the notice is released.
The organization is added to the Organization structure with no parent. An email is sent to the coordinator suggesting that they "re-parent" the organization within the structure.