The Inventory Receipt Transaction Record View allows users to record the receipt of inventory purchased from an outside entity. This transaction allows multiple line items to be received into a single site. The 'Include open Receipt transactions in Available balances' preference will determine whether Available balances are updated before the transaction is posted. Once the transaction is posted, it will update the On Hand lot balance of the item(s).

Software Version: 2021.??.?? and newer

Page Header

Header Toolbar

Toolbar Icons	Description
Create AP Invoice	When clicked, a new AP Invoice transaction will be created that contains all the items and quantities (including those with negative quantities and/or those that may not reference the Purchase Order) from the current Receipt transaction. The AP Invoice transaction will open in a new tab and if the user has "Full" rights to the Invoice Record View they can make any edits and or Approve/Post the Receipt. The AP Invoice must be manually posted. Because this operation creates the Invoice using the current line items and quantities it should only be clicked once all the items and quantities have been correctly entered on the Receipt. After the Invoice transaction has been auto-created, it will need to be manually updated if any changes are made to the source Receipt.
Delete	Deletes the transaction, batch, or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. _{WARNING: Records cannot be recovered once they are deleted!}
More Actions	Displays a drop down menu of related actions. The list of options includes: IQ: PO Transactions - Opens an inquiry with all the Purchase Orders, AP Invoices, AP Credit Memos, and Inventory Receipts with this Purchase Order assigned. RV: Purchase Order - Opens the record view of the Purchase Order
New	Allows users to select the type of transaction or record they want to add. The list contains all the 'Active' Invoice and Credit Memo Transaction Class IDs displayed as [TransactionType] - [ClassID]. For example: "Invoice - Home Office". Note: The Transaction Class will not display after the Transaction Type if the Class ID is named "Default"
Notes	Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled. Note Types of "Purchase Order" saved to the Vendor will default on the Purchase Order Notes. Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes.
Print	Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed. When clicked, all the Reports assigned to the Functional Area of Purchasing, that launch from the Print Dialog, are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.
Save	Saves the changes made to the record.
Save & Close	Saves your changes and closes the page.

Home Tab

Fields	Description
INV#: [TransID] PO#: [PO] REQ#: [REQ#] Vendor Name
Description	Error rendering macro 'excerpt-include' : No link could be created for 'Description - Header'. This is text box that defaults as blank and is not required but If entered, it must be <=150 characters. If a 'PO #' is entered/selected for this transaction, and the PO contains a 'Description', the Description from the PO will populate here, but can be overwritten. This is always editable even after the transaction is posted. Database Field: ERPx_APTransactionHeader.Description
Doc Date	Identifies the date of the transaction. This is a date picker to assign/edit a date for the invoice/credit memo. This defaults to today's date and is required. If missing, the message "Doc Date is required." will be displayed on Save. The Doc Date must be on or before the GL Date when Approving or Posting the Invoice/Credit Memo. If not, the message "The GL Date must be on or after the Doc Date." will be displayed on Save. This is editable while the transaction is in a Status of "New". Database Field: ERPx_APTransactionHeader.TransactionDate
Doc No	Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This is a text box to enter the document number your Vendor assigned to the invoice/credit memo. This defaults to blank, is required, must be unique by Vendor, and must be <= 50 characters. This is editable while the transaction in a status of "New". If missing, the message "Doc No is required." will be displayed on Save. If not unique, the message "Duplicate Doc No's are not allowed. Please enter a valid Doc No." will be displayed on Save. Database Field: ERPx_APTransactionHeader.DocNumber
Payment Terms ID	Identifies the Payment Terms assigned to the transaction. This is a single-select lookup that defaults from the Payment Terms assigned to the Vendor. This is required and if missing, the message "Payment Terms are required when approving or posting transactions." will be displayed on Save. This is editable while an Invoice is in a status of "New", but not editable on Credit Memos. Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms. Database Fields: ERPx_MFPaymentTerms.PaymentTermName, APTransactionHeader.PaymentTermSK
PO #	A Purchase Order # (aka PO #) is the unique identifier of a Purchase Order. This is a single select lookup, that defaults as blank, and is not required. This is editable when the transaction is in a Status of "New". The lookup contains a blank value, the current assigned value, and a list of all 'applicable' Purchase Orders, for the assigned Vendor. The conditions used to determine which Purchase Orders are 'applicable' include: All Purchase Orders that are assigned to the Vendor saved on the transaction header. All Purchase Orders containing line items assigned to the Vendor saved on the transaction header. Purchase Orders with a Status of: New will be included if the Purchasing Preference 'First Status PO's are visible to AP Invoices and IM Receipts' is set to "New". Released will always included Closed will never be included Purchase Order Type - would it be better to always include these and give a message indicating why they can't be selected or hide them? Single Invoice and Receipt - only PO's that have not had a posted AP Invoice will be included Multiple Invoices and Receipts - all PO's will be included Database Fields: ERPx_APTransactionHeader.PurchaseOrderSK, ERPx_APPoHeader.PurchaseOrderID
Reference	Identifies the Reference entered for the transaction. This is text box that defaults to blank and is not required, but if entered, it must be <=100 characters. This is always editable even after the transaction is posted. The Reference will not default from the Reference on a linked Purchase Order. These are treated as separate reference fields. A Reference number is used to record an additional tracking number that associates this transaction to another system. For example, if a transaction was imported from a 3rd party system this could be used to store the unique identifier from that system's transaction. Database Field: ERPx_APTransactionHeader.Reference
Site Name	Error rendering macro 'excerpt-include' : No link could be created for 'Site'. This is single select lookup that is required and defaults in the following sequence: From the Site assigned to the linked PO (if a PO # is entered for this transaction) From the 'Default Site' on the Transaction Class This is editable while the transaction is in a Status of "New". The Site can be changed, it is not restricted to the Site on the linked Purchase Order. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. This lookup contains a list of all active Sites. Database Fields: ERPx_APTransactinHeader.SiteSK, ERPx_MFSite.SiteID,
Status	Identifies the Status of the transaction. This is a single-select lookup that is required. It defaults as "New" and is always editable. The Statuses that apply to transactions in this Record View include: New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist. Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned. Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted". If this transaction is linked to an Inventory Receipt, when it is saved with a Status of either 'Approved' or 'Ready to Post', a warning message will appear if any of the linked line items have a quantity that is different from the linked Receipt. This is just a warning and will not prevent the transaction from posting. Database Fields: ERPx_APPoHeader.TransactionStatusEN
Vendor Name	Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View. This is a single-select lookup that is required. It defaults as blank and is editable when the transaction is in a Status of "New". The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Vendors. Database Fields: Database Field: ERPx_APTransactionHeader.VendorSk, ERPx_APVendor.VendorName

Properties Tab

Fields	Description
Group: 1
Discount Date	Identifies the Discount Date of the transaction. This is a date picker that defaults as [Doc Date] + [Payment Terms Discount Days] and is required on transactions with a 'Payment Terms' that contain a Discount. For Payment Terms that do not include a discount it is blank and disabled. This but can be overwritten to any date that is both: >= the 'Doc Date'. If not, the message "The Discount Date must occur on or after the Doc Date." will be displayed on Save. <= the 'Due Date' If not, the message "The Discount Date must occur on or before the Due Date." will be displayed on Save. This is always editable, even after the transaction is Posted. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Note: Changing this for a posted transaction will only have an effect if the transaction has an open/unapplied balance. The Discount Date represents the last date that Payment Term Discounts apply. Database Field: ERPx_APTransactionHeader.DiscountDate
Due Date	Identifies the Due Date of the transaction. This is a date picker that that defaults as [Doc Date] + [Payment Terms Due Days] and is always editable, even after the transaction is Posted. This but can be overwritten to any date that is both: >= the 'Doc Date'. If not, the message "The Due Date must occur on or after the Doc Date." will be displayed on Save. >= the 'Discount Date' If not, the message "The Due Date must occur on or after the Discount Date." will be displayed on Save. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Note: Changing this for a posted transaction will only have an effect if the transaction has an open/unapplied balance. The Due Date represents the date the transaction must be paid by. Database Field: ERPx_APTransactionHeader.DueDate
GL Date	Identifies the date the transaction posted (or will post) to the general ledger. This is an date picker that defaults as blank and is required to Approve or Post the transaction. If it has not been manually assigned, it will be automatically set to match the 'Doc Date' when the transaction is saved with a Status of either Approved or Ready to Post. The GL Date must be on or after the Doc Date when Approving or Posting the transaction. If not, the message "The GL Date must be on or after the Doc Date." will be displayed on Save. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.GLDate
Pmt./Apply Hold	Identifies if the transaction is on hold for payments and applications. Invoices on hold will not be visible when building AP Payment Batches. Credit Memos on hold cannot be selected to apply against open Invoices. This is a single select lookup that defaults as blank but can be changed to "Yes". A blank value means the transaction is not on a Payment Hold A "Yes" value mean the transaction is on a payment Hold. This is always editable, even after the transaction is Posted. Note: Changing this for a posted transaction will only have an effect if the transaction has an open/unapplied balance. Invoices on hold will not be selected for payment when building AP Check Batches. Credit Memos on hold cannot be selected to apply to open Invoice Database Field: ERPx_APTransactionHeader.IsOnApplicationHold
Group: 2
Created	Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required. Database Field: ERPx_APTransactionHeader.CreatedDate
Created By	Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required. Database Field: ERPx_APTransactionHeader.CreatedBy
Last Updated	Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required. Database Field: ERPx_APTransactionHeader.LastUser
Last Updated By	Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required. Database Field: ERPx_APTransactionHeader.LastUpdated
Group: 3
Currency ID	Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency ID' on the 'Properties' tab of the Purchase Order Record View. This is not editable on the transaction. The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars. Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APTransactionHeader.CurrencySK
Linked Receipt Transaction ID	Identifies the transaction ID for the Receipt transaction that is linked to this transaction. This is not required and not editable. This will be populated if a Receipt was created from the AP Invoice/Credit Memo or if the AP Invoice/Credit Memo was created from the Receipt. If a Receipt was linked but was either deleted or voided, the link will be removed.
Transaction Class ID	The unique identifier of the Transaction Class. This is required and comes from the 'Purchase Order Class' selected when the Purchase Order was initially created. This is not editable. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPx_APTransactionHeader.TransactionClassSK, ERPx_APTransactionClass.TransactionClassID
Transaction SK	Identifies the SK value of the Transaction. This is a non-editable text box that is informational only. Database Field: ERPx_APTransactionHeader.POHeaderSK
Vendor ID	Identifies the ID of the Vendor account that is assigned to the transaction. This defaults from the 'Vendor ID' for the Vendor assigned to the Purchase Order. It can only be edited from the 'Vendor ID' field on the 'Properties' tab of the Vendor Record View, for the Vendor attached to the Purchase Order. Vendor IDs are used as a short description and unique identifier for Vendor records. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Vendor IDs the 3-3-2 method would be recommended. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK
Vendor SK	Identifies the SK value of the Vendor. This is a non-editable text box that is informational only. Database Field: ERPx_APTransactionHeader.VendorSK

Attributes Tab

Fields	Description
Attributes	A non editable text box that shows the name of the Attribute. Attributes are user-definable fields that are used on master files and transactions and are editable from the Attributes List View. The Attribute will only be displayed if the Applies property on the Assign Attribute Rules by page is set to either "Yes - Required" or "Yes - Not Required". Attributes set to "No" will not be displayed. The Attributes displayed here are setup and assigned in the Attributes section of the Company module (Company → Setup → Attributes → Sales Order).
Required	A non editable text box that shows whether the Attribute Value is required or not. If the Attribute Value is required, it will display "Yes". If it is optional, it will display as blank. This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → AP Purchasing → Transactions hyperlink).
Value	Identifies the value assigned to the corresponding attribute. Because Attributes are configurable as either Text, List, Date, or Date/Time the data entry is either a text box, lookup, or date picker. The value defaults to blank and is only required if the Attribute's 'Applies' property is set to "Yes - Required" in the Assign Attribute Rules page. Attribute Values for Master Flies are always editable. Attribute Values for transactions are always editable for unposted transactions. This is editable if the Transaction Class property 'Allow Attribute Edit After Approval' is set to "Yes".

Page Details

Toolbar Icons	Description
Add Item	Adds a blank line in the grid to allow for data entry. If a valid Item ID is entered, the line will be saved. If not, the 'Item Lookup' window will open allowing users to search for the Item.
Column Filter Show/Hide	Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column.
Excel	Exports the contents of the grid to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view, or excluded columns, only the contents in the grid will be exported.
Group By Show/Hide	Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total.
Help	Opens the online WIKI help page for the current page.
More Actions	Displays a drop down menu of related actions. The list of options includes: IQ: PO Lines - Opens an inquiry with all the Purchase Order, AP Invoice, AP Credit Memo, and Inventory Receipt lines with this Purchase Order assigned. RV: Item - Open the item Record View for the selected item
Quick Column Filter	Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text.
Saved Layouts	Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected. Please note that existing saved grid layouts will display the Filter Row as hidden by default.
Remove Items	Removes the selected line(s). When clicked, you are prompted with the message "Are you sure you want to delete n item(s)? Okay or Cancel". This cannot be done on transactions with a Status of 'Approved', Ready to Post', 'Posted', 'Closed', 'Void', or 'Replaced'.
Fields	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Amount	Identifies the Extended amount of the line item. This is required and is calculated as [Quantity] * [Price] for each transaction line. This can only be edited by changing the Quantity and/or Price of the transaction line. Positive lines represent a purchase and negative lines represent a purchase credit. Database Field: ERPx_APTransactionLine.ExtendedAmount
Distributed To	Identifies how the (extended) amount of the line item was, or will be, applied. Identifies the name of a Project, Employee, Fisherman, Tender or Fisherman Loan. This is a single-select lookup that defaults as blank and is not required. If a 'PO #' is entered/selected for this transaction, and the PO Line Item is Distributed, this will default from the PO Item's 'Distributed To' value but can be overwritten. This is editable while the transaction is in a Status of "New". The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fishermen, Tenders, Loans, and Projects. Database Fields: ERPx_APVendor.VendorName, ERPx_MFEmployee.EmployeeName, ERPx_GLProject.ProjectDescription, ERPx_APPoLine.DistributedToSk
Item	Identifies the Item, displayed as Item ID: Item Description. This is a text box that is required. It defaults as blank and is not editable once the line item has been saved to the transaction. When the 'Add Item' icon is clicked, users may enter all or part of an Item ID or Description and hit the Enter key on the keyboard. If a complete Item ID was entered, the line item will be saved, if not, the Item Lookup dialog box will open with a list of items containing the data entered. From the 'Item Lookup' dialog box, users may check the checkbox next to one or multiple item(s) to add to the transaction using the Save & Close button. Items represent objects that you sell, produce, and/or purchase that are tracked within the system. They are used on Sales, Inventory, Fisherman Accounting and Purchasing transactions. Database Fields: ERPx_IMItem.ItemID:ItemDescription, ERPX_APTransactionLine.ItemSK
Item Type	Error rendering macro 'excerpt-include' : No link could be created for 'Item Type'. This defaults from the Item Type assigned to the Item ID and is not editable. Database Fields: ERPx_IMItemType.Description, ERPx_IMItem.ItemTypeSK, ERPX_APTransactionLine.ItemSK
Ln.	Identifies the Line # for each Transaction Line Item. The Line # sets the sort of the items on grids, list views, inquiries, and reports. Database Field: ERPx_APTransactionLine.LineNumber
PO Item Description Should this be called Vendor Item Description?	Error rendering macro 'excerpt-include' : No link could be created for 'Line Item Description'. This is text box that defaults as blank and is not required but If entered, it must be <=100 characters. If a 'PO #' is entered/selected for this transaction, and the PO Line Item contains a 'PO Item Description', this will default from the PO Item Description' but can be overwritten. This is editable while the transaction is in a Status of "New". When AP Invoices, Credit Memos, and IM Receipts are loaded from a PO, this will default as the 'PO Item Description' on those transactions. Linked Database Field: ERPx_APTransactionLine.VendorItemDescription
PO Ln.	Identifies the Purchase Order line item that the AP Invoice/Credit Memo line item is linked to. This is a single-select lookup that is not required. If a 'PO #' is entered/selected for this transaction, as line items are added to the AP Invoice/Credit Memo, if they are also on the Purchase Order, this will default from the Purchase Order's 'Ln.' as [PO#]: [Ln]. This is editable while the transaction is in a Status of "New". The lookup contains a blank value, the current assigned value, and a list of all the Purchase Order Line Numbers (from the PO # assigned to this transaction) that matches the selected Item ID. When AP Invoices, Credit Memos, and IM Receipts are loaded from a PO, this will default from the 'Ln.' of the Purchase Order Item. Linked Database Field: ERPx_APTransactionLine.PoLnSK
Price	Identifies the price of the line item.This is a numeric text box that defaults to 0 and is formatted to the Item's 'Price Decimals'. For line items linked to a Purchase Order Line Item, this defaults from the Purchase Order Item's 'Price' but can be edited. Prices must be >= 0.00, negative prices are not allowed. This is editable while the transaction is in a Status of "New". Database Field: ERPx_APTransactionLine.Price
Purchase GL Account	Identifies the GL Account the purchase line will post to. This is a single-select lookup that is required. This is defaults and is conditionally editable based on: For line items that are NOT distributed to a Fisherman, Tender, or Loan, this is editable while the transaction is in a Status of "New" and defaults in the following sequence: From the 'Purchase GL Account' assigned to the Purchase Order Line if a Purchase GL Account was specified on the PO. From the Item's default "Purchases" account if one has been setup. From the Vendors default "Purchases" account if one has been setup. For line items distributed to a Fisherman, Tender, or Loan this is NOT editable and defaults in the following sequence: From the Fishermen, Tender, or Loans default "Settlement Accrual" account if one has been setup From the Fisherman Accounting Preferences default "Settlement Accrual" account When AP Invoices and/or Credit Memos are loaded from a PO, the 'Purchase Account' will default from the current Purchase Account assigned to the Purchase Order Item. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' GL Accounts where the "Use in AP" checkbox has been assigned. Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APTransactionLine.AccountSK
Quantity	Identifies the quantity of the line item.This is a numeric text box that defaults to 0 and is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the line items UOM. For line items linked to a Purchase Order Line Item, this defaults as [PO Line Ordered Qty] - [Invoiced Quantity] or 0.00 whichever is greater. The [Invoiced Quantity] only refers to the Quantity from "Posted" AP Invoices and Credit Memo lines. It does not include unposted or voided transactions. For AP Invoice transactions, a positive 'Quantity' represents a purchase and a negative quantity represents a credit. Negative quantities are allowed provided the transactions total 'Amount' is greater than or equal to 0.00. For AP Credit Memo transactions, a positive 'Quantity' represents a credit and a negative quantity represents a purchase. Negative quantities are allowed provided the transactions total 'Amount' is greater than or equal to 0.00. Database Field: ERPx_APTransactionLine.Quantity
UOM	Identifies the unit of measure that the units are stored in (Box, Bag, Case, Each, Tote, etc.) for a line item or on the transaction. This is a single-select lookup that defaults from the Item's default "UOM-PO". This is required and is editable while the transaction is in a Status of "New". If a 'PO #' is entered/selected for this transaction, and the PO Line Item is on the Purchase Order, this will default from the PO Item's UOM but can be overwritten. The lookup contains a blank value and all 'Active' UOMs on the selected Item's UOM Schedule. When AP Invoices and Credit Memos are loaded from a PO, the 'UOM' will default from the Purchase Order Item's UOM. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. Database Fields: ERPx_IMUOM.UOMName, ERPx_APPoLine.QuantityUOMSK

Page Header

Header Toolbar

Home Tab

Attributes Tab

Page Details

Related Topics

Page Definitions

Technical Details

New IM Receipt Record View

Page Header

Header Toolbar

Home Tab

Attributes Tab

Page Details

Related Topics

Page Definitions

Technical Details