| \n\nNumber\n\n | \n\nSystem-generated unique identifier of the purchase line.\n\n |
| \n\nSupplier\n\n | \n\nSupplier for which the shopper places the order.For a non-catalog intake, if the shopper provides a supplier name for which a supplier record doesn’t exist, a new supplier record is manually created with some of these details:\n\n- Legal name, according to the name provided by the shopper.\n- Onboarding status of the supplier. An onboarding playbook is triggered for new suppliers as part of Supplier Lifecycle Operations, to guide the registration process for the new supplier contact.\n- Relationship status of the supplier\n- Preferred status of the supplier\n\nThe contact details provided by the shopper for the supplier is also displayed as a record in the **Vendor Contacts** related list. This record is created with the help of the vendor contact creation API from Supplier Lifecycle Operations. For more information, see [Fields in the Create New Supplier Case form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/supplier-lifecycle-operations/new-supplier-case.md).\n\n |
| \n\nProduct category\n\n | \n\nProduct category that is sourced through this purchase line.\n\n |
| \n\nSupplier product\n\n | \n\nSupplier product for which the purchase line is created.This field isn’t displayed if the product type is handling fees.\n\n |
| \n\nProduct name\n\n | \n\nName of the supplier product. For a non-catalog purchase, the information is taken from the **Describe the product** or **Describe the service** fields.\n\nThis field isn’t displayed if the product type is handling fees.\n\n |
| \n\nProduct example\n\n | \n\nReference URL that the shopper provides. For a non-catalog purchase, this information is obtained from the **Do you have an example of what you're looking for?** field on ShoppingHub.\n\nThis field isn’t displayed if the product type is handling fees.\n\n |
| \n\nSupplier contacted?\n\n | \n\nIndicates if the shopper has already contacted the supplier.For a non-catalog purchase, this field is set to true if the shopper selects **I've contacted them already**.\n\nThis field isn’t displayed if the product type is handling fees.\n\n |
| \n\nSupplier contact\n\n | \n\nName of the supplier contact for this supplier.\n\n |
| \n\nSupplier contact email\n\n | \n\nRegistered email ID for this supplier contact.\n\n |
| \n\nNon-catalog purchase?\n\n | \n\nIndicates if a non-catalog intake workflow is initiated. The value is true when a shopper uses the **Don't see what you need?** option on ShoppingHub.\n\nThis field isn’t displayed if the product type is handling fees.\n\n |
| \n\nState\n\n | \n\nCurrent status of the purchase line.**Note:** This is a read-only field.\n\n |
| \n\nPurchase\n\n | \n\nParent purchase associated with this purchase line.\n\n |
| \n\nSourcing request\n\n | \n\nSourcing request associated with this purchase line.\n\n |
| \n\nSourcing event\n\n | \n\nSourcing event associated with this purchase line.\n\n |
| \n\nNegotiation\n\n | \n\nNegotiation associated with this purchase line.\n\n |
| \n\nPurchase requisition\n\n | \n\nPurchase requisition associated with this purchase line.\n\n |
| \n\nShort description\n\n | \n\nBrief description that is visible to the shopper on ShoppingHub.This field isn’t displayed if the product type is handling fees.\n\n |
| \n\nPurchase reason\n\n | \n\nReason for the purchase that the shopper provides before checkout.For a non-catalog purchase, this information is obtained from the **Why do you need this?** field on ShoppingHub.\n\nThis field isn’t displayed if the product type is handling fees.\n\n |
| \n\nHandling fee\n\n | \n\nCharges added for a specific supplier when a rule is triggered as a result of certain configurable conditions for a purchase requisition being met. For more information on handling fees, see [Handling fees](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/handling-fees.md).This field is displayed only if the product type is handling fees.\n\n |
| \n\nSpecific requirements\n\n | \n\nRequirements that the shopper specifies. For a non-catalog purchase, this information is given in the **Any specific requirements** field on ShoppingHub.\n\n |
| \n\nPurchasing Details\n\n |
| \n\nSpend categorization\n\n | \n\nIndicates whether negotiation with the supplier is addressable or not.\n\n |
| \n\nNegotiated by\n\n | \n\nIndicates who is responsible for negotiation.\n\n |
| \n\nProduct type\n\n | \n\nIndicates whether the ordered product type is a good, service, or handling fee.\n\n |
| \n\nGoods receipt required\n\n | \n\nIndicates if a receipt is required in addition to the invoice. This field is visible only if the product type is **Good**.\n\n |
| \n\nOne-time pricing\n\n | \n\nIndicates if the pricing created for a service can be reusable in subsequent purchase requests. When created in the context of a sourcing request or negotiation for a service, the default value is **Yes**.This field is visible only if the product type is **Service**.\n\n |
| \n\nExpected delivery date\n\n | \n\nExpected date for the delivery that the shopper requests.**Note:** This date can be in the past, present, or future. For the date to be in the past, the **After the fact** field in the associated purchase requisition table must be set to Yes.\n\n |
| \n\nAcknowledgment type\n\n | \n\nIndicates if receipt of confirmation is necessary and the type of receipt. The available options are **Milestones**, **Service Acknowledgment**, and **Two Way Match**.This field is displayed as **Invoice** if the product type is handling fees.\n\n**Note:** If you’re an existing customer continuing with the Source-to-Pay Common Architecture \\(sn\\_shop\\) plugin, and skipping the Shopping Hub \\(sn\\_spend\\_uib\\) plugin, service acknowledgment is replaced with invoice acknowledgment for you.\n\n |
| \n\nMilestone payout type\n\n | \n\nIndicates the type of milestone payout. The options available are **Amount** and **Percentage**.This field is visible only if the acknowledgment type is set to **Milestones**.\n\n |
| \n\nStart date\n\n | \n\nExpected start date of the service that the shopper provides.**Note:** This date can be in the past, present, or future. For the date to be in the past, the **After the fact** field in the associated purchase requisition table must be set to Yes.\n\n |
| \n\nEnd date\n\n | \n\nExpected date to end providing the service to the shopper.**End date** is calculated as: **Start date**+\\[**Term length**\\***Term value**\\].\n\n**Note:** This date can be in the past, present, or future. For the date to be in the past, the **After the fact** field in the associated purchase requisition table must be set to Yes.\n\n |
| \n\nTerm length\n\n | \n\nDuration of the term. When the shopper selects a time frame, the order is considered a blanket type order.\n\n |
| \n\nTerm value\n\n | \n\nType of the term. The options are **Days**, **Weeks**, **Months**, and **Years**.\n\n |
| \n\nMaximum budget\n\n | \n\nMaximum budget that the shopper provides for this purchase.\n\n |
| \n\nPurchased quantity\n\n | \n\nQuantity of the product that the shopper wants to purchase.\n\n |
| \n\nEstimated tax\n\n | \n\nTax estimate for the product based on the price and delivery location.\n\n |
| \n\nEstimated shipping\n\n | \n\nShipping cost estimate for the product based on the delivery location.\n\n |
| \n\nTotal line amount\n\n | \n\nTotal price of the purchased goods and services, including estimated tax and shipping.\n\n |
| \n\nNet amount\n\n | \n\nAmount included as a cost allocation on the purchase order. This doesn’t include any estimates.\n\n |
| \n\nTotal individual units\n\n | \n\nNumber of fixed assets that are created depends on this value.\n\n |
| \n\nIndividual unit cost\n\n | \n\nCost of the individual unit.\n\n |
| \n\nSupplier Bid Details\n\n |
| \n\nSupplier's lead time \\(days\\)\n\n | \n\nNumber of days that the supplier takes to deliver the goods or provide the service. Based on this, the delivery date for goods and the start and end dates for services vary.\n\n |
| \n\nUnit\n\n | \n\nUnit in which the product is provided by the supplier.\n\n |
| \n\nSupplier's quantity\n\n | \n\nQuantity that the supplier can provide.\n\n |
| \n\nStarting unit cost\n\n | \n\nCost per unit of the product prior to negotiation.\n\n |
| \n\nNegotiated unit cost\n\n | \n\nCost per unit of the product after negotiation.\n\n |
| \n\nTotal bid amount\n\n | \n\nSupplier's quantity multiplied by negotiated unit cost. It reflects the total bid amount from that particular supplier for that purchase line.\n\n |
| \n\nNegotiated savings\n\n | \n\nTotal savings through negotiation. This is calculated as: \\(Starting unit cost - Negotiated unit cost\\) x Supplier's quantity\n\n |
| \n\nSupplier notes\n\n | \n\nAdditional notes about the supplier, if any.\n\n |
| \n\nDelivery Details\n\n |
| \n\nFields in the Delivery Details section map to the information from delivery location details that the shopper provides. Shipping method is displayed as a read-only field here. However, this section isn’t displayed if the product type is handling fees.\n\n |
| \n\nAccounting Details\n\n |
| \n\nProduct category\n\n | \n\nCategory to which the supplier product belongs.\n\n |
| \n\nCapex account\n\n | \n\nLedger account to post the capital expenses of this product after the purchase completion.\n\n |
| \n\nExpense account\n\n | \n\nLedger account to post the operational expenses of this product after the purchase completion.\n\n |
| \n\nPayment schedule\n\n | \n\nIndicates the schedule of payments to the supplier.\n\n |
| \n\nPre-payments required\n\n | \n\nIndicates if pre-payments can be credited to the supplier against this purchase.\n\n |
| \n\nLegal entity\n\n | \n\nInternal legal entity that incurs the cost of this purchase.\n\n |
| \n\nCost center\n\n | \n\nCost center that incurs the cost of this transaction.\n\n |
\n