Key terms used throughout Rootstock Sales Order functionality and related articles.
Terminology
High Volume Sales Order Entry UI: Also referred to as High Volume SO Entry UI or HV SO Entry UI, it is a UI display designed specifically for SO Headers with a big number of SO Lines (12+). Using this UI, the SO Header needs to be saved before SO Lines can be added. The structure of the UI is the same as with Normal SO Entry UI, the main difference is that the SO Lines are incorporated to the page as a related list, as opposed to embedded into the Visualforce page (which provides easier access to certain buttons for the SO Lines). In order to add or view all the details for a specific line, it is necessary to click on the hyperlink below the Line column of this related list.
NOTE It is possible to switch between Normal and HV SO Entry UIs by updating URL parameter isstandalone. See for below example that it is currently equal to zero. This means it is using the Normal SO Entry UI.
To change from Normal to HV SO Entry UI, update the URL parameter to isstandalone=1 and click Enter, this will load the page in HV SO Entry. If the parameter is not present, as is the case for below example, add it as &isstandalone=1
To change from HV to Normal SO Entry UI, update the URL parameter to isstandalone=0 and click Enter, this will load the page in Normal SO Entry. If the parameter is not present, add it as &isstandlone=0
Sales Order Header: Also referred to as SO Header, Sales Order or SO Entry, is the main object for the Sales Order process. It provides detail not only the Customer and general order details but also group products (and their components) that are to be included in this customer's purchase request. It can be used as the launchpad to initiate other functionalities such as Sales Order Fulfillmentand Configuration Session.
Customer: Entity for which the Sales Order Header is created, and to which Services or Goods are sold. The customer is defined as a RootstockCustomer, which is always connected to a Salesforce Account record.
Pricing Customer: Customer that is used to look up customer-specific pricing and discounts when deriving product prices (using the Price Discount Logic). Qualifying Customers for Pricing purposes are those that are defined as Related Customers to the Customer linked to the Sales Order Header.
Invoicing and Credit Customer: Optional 'financial' Customer used for Credit and Invoicing purposes. If the Customer Master is defined with an Invoicing and Credit Customer, then no billings (SO Invoice / Credit Memos) are created for the Customer, as everything is billed to its Invoicing and Credit Customer instead, and Credit checks will be done against the Invoicing and Credit Customer.
Product Type: Nature of the Product, each product type has different processing behaviors. Product Types supported by Rootstock are: Configured, Stock, Kit, Service, Miscellaneous, Entitlements (which can reference Entitled-To Products, and are not directly used on SO Lines) and Recurring Services (this last is managed by ourSales Contracts Overview functionality).
Effective Product Type: Products with Type 'Configured' or 'Stock' can be set to behave as Stock or Configured (respectively) on SO Line to Line basis, by checking related boxed on Sales Order Line > Additional section > Inventory tab, before the SO line is firmed. If a SO Line for a Configured Product is set to Stock This Time, the effective Product Type would be 'Stock', and the other way around for Stock products, which would have an effective Product Type of 'Configured' when the Configured This Time option is checked. Effective Product Types drive the behavior of the SO Lines in terms of available SO Line Components, behavior when the SO Line is firmed, etc.
Product: Good or service to be sold. Depending on its product type, may reference an Inventory Item that is Make-To-Order or Made-To-Stock, multiple Inventory Items to be fulfilled as a bundle, Service Items that do not involve inventory movements, etc.
Configured Product: A product with Configured Product Type, which is a made-to-order SO Line, and for which a Work/Labor Order is created when the SO Line is Firmed. The type of shop-floor order created depends on the Item Type defined on the Engineering Item for the Inventory Item on the SO Line.
Allocations: In regards to setting Inventory aside for a future material issue. For allocations to be available during Sales Order processes, they would need to be activated on. See details on Allocation Logic:
Division Master > Advanced Options tab > Allocations Active field
SO Control > Order Processing tab > Order Line Allocations Active
Auto-Allocations: Additionality, Sales Order Lines can be auto-allocated when a Sales Order Line is firmed (given that there is enough available material within the demands Project/Site/Item). See details on Sales Order Lines - Auto-Allocation Processing.
Sales Order Line: Also referenced to as SO Line. Particular line item to be included to a given Sales Order Header, for which there can be multiple ones. Each Sales Order Line must reference a Product.
Sales Division: Division that manages the process of selling goods to the customer. In Rootstock, it is possible to define a division as the Centralized Sales Division, which would restrict all the selling activity to it (Products and Sales Orders would only be maintained in this Sales Division). If not using centralized sales, any Division with a SO Control record can be considered a Sales Division and have Product and Sales Orders created for it.
Inventory Division: Division from where the Inventory Item/s included to a SO Line (as per Product settings) are to be issued/shipped from. The Inventory Division may be different for each SO Line, and different than the Sales Division for the SO Header. Products can be directly related to Inventory Items (such as Configured and Stock Product Types), or to multiple Inventory Items (such as Kit Product types), have a Default Inventory Division (Product Master > Inventory tab), and have multiple available Inventory Divisions to choose from on SO Lines.
Firm: It refers to the SO Line being firmed, therefore confirmed, and that for each of its Sales Order Line Demand records there are inventory requirements created (if the Product Type allows this). It also enables the SO Line to be eligible for Sales Order Fulfillmentsteps.
Sales Order Line ComponentsEntities that form part of the Sales Order Line. They can be of different nature (Demand, Labor, Material, Non-Inventory..)
Sales Order Line Demands: Depending on the SO Line's Product Type, the SO Line may have one, more than one, or no Sales Order Line Demands at all. These Line Demands are Inventory requirements of goods to supply to the customer. Once the SO Line is Firmed, these requirements are 'confirmed' and, depending on the SO Line Product Type and setup details not only of the Product but also of the Inventory Item, may generate a Work Order/Labor Order, a Direct Purchasing Purchase Order Header/Line or are to be included in MRP calculations (to generate Purchase Requisitions or Planned Work Orders as supply for these Line Demands).
Configured Sales Order Material: Inventory based line component that is required to configure the Inventory Demand or Line Demand for this SO Line. When a Configured SO Line is Firmed, it creates a Work Order to manufacture the SO Line Demand Inventory Item, Configured Sales Order Materials are added as Work Order Components to said Work Order.
Configured Sales Order Labor: Shop floor required action to configure the Inventory Demand or Line Demand for this SO Line. When a Configured SO Line is Firmed, it creates a Work Order to manufacture the SO Line Demand Inventory Item, Configured Sales Order Labor are added as Work Order Operation to said Work Order.
NIC: Non-Inventory based components associated with a SO Line. They carry cost and price details, as Labor and Material components, and when the SO Line is processed through SO Fulfillment, generate NIC Issue transactions. When a Configured SO Line is Firmed, NIC Components are added as Work Order Non-Inventory Components to said Work Order, with no processing purposes, as a reference-only list of entries that reference Sales Order Line NICs.
Direct Purchase: Is the Purchase Order generated from a firmed Sales Order Line demand. It can be set to auto-create this purchase when the SO Line is flagged as Firmed, or can be created manually from the SO Header > Direct Purchasing tab. Direct Purchases support drop-shipping so that the address of the Customer is transferred to the Purchase Order. Additionally, the Direct Purchased Purchase Item can be configured to create a Direct Sales for an Inter/Intra System Product:
Intra-System: References a buy/sell between Rootstock Divisions (within the same Rootstock Company). For details see Inter Company Direct Purchase.
Charge: In terms of shipping Sales Order contents, is the cost involved in necessary steps for the readiness of a shipment. Supported charges types are Packing, Handling, and Shipping.
SO Header Default Project: Default Project used to initiate the Project field when manually creating SO Lines. It can be changed at any time, and this would affect SO Lines added after the change. The project can be overridden at the Sales Order Line level.
SO Line Project: This is the project associated with the SO Line, and that will be carried throughout the Sales Process and used as a cost tracking tool when fulfillment transactions are performed. The Line Project cannot be updated for Configured or Configured-This-Time Firmed SO Lines, for other types of SO Line, changes are not allowed when the Line has been initiated in Allocation or Issue step.
SO Line Issue project: This is the project associated with the SO Line Demand, and which will be used to define inventory availability and to fetch inventory from when issuing said Inventory item. It can be updated before the SO Line is firmed on Sales Order Line Componentsbutton. If the Inventory item linked to the SO Line is considered a Home Project Item, the Issue Project will default to the Home Project.
Normal Sales Order Entry UI: Also referred to as Normal SO Entry UI, it is a UI display designed for easy accessibility to addition and detail review of SO Lines. It is structured in two parts, Header and Item Lines section (where the SO Lines are contained). Each SO Line has an Additional and a Component button, as well as a tool to add Note & Attachments.
