This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide.
This element will be returned only for non-history orders. For history orders no modifications allowed.
Modification Type If it is 'N', ModificationType can be performed on order without override. If it is 'Y', modification can be performed only in override mode. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table.
This element will be returned only for non-history orders. For history orders no modifications allowed.
Modification Type If it is 'N', ModificationType can be performed on order without override. If it is 'Y', modification can be performed only in override mode. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. This table stores description in different languages. A localized description. An extended localized description. Locale for which the extended description is stored. Short description. This field indicates the alternate ItemID, which can be passed instead of the actual ItemID. This is an alias for the ItemID. The currency in which the unit cost is specified. The country of origin being requested. Indicates if credit has been issued upon receipt of the returned goods. The item ID for the buyer. The item description of the buyer organization. The Export Commodity Control Number for a commodity contained in the shipment, as indicated on the Waybill. The harmonized code, if applicable. The ISBN number, if applicable. Is the line returnable. The description of the item. The identifier for the item. The ITEM_ID, UOM, and PRODUCT_CLASS form the unique inventory identifier for an order line. The ITEM_ID, UOM and ORGANIZATION_CODE form the unique item identifier for the Product Management module. The short description of the item. The weight of the item. The unit of measure used for weight. The item identifier for the manufacturer. The item description for the manufacturer. The name of the manufacturer. The National Motor Freight Classification - A way of classifying goods for the purposes of transportation. The National Motor Freight Classification - A way of classifying goods for the purposes of transportation. The description of the NMFC. National Motor Freight Classification is a way of classifying goods for the purposes of transportation. The product class. This field is used as an inventory identifier. The product line for the item Number of days within which the item must be returned for it to be accepted as a return on the system. The Schedule B commodity codes - A 10-digit numeric codes used to identify products that are exported to other countries. The item ID of the supplier (if this is a PO or the line is being drop-shipped and the supplier is known upfront). The item description of the supplier (if this is a PO or line is being drop-shipped and the supplier is known upfront). The product code classification for the purposes of taxation. The UPC Code of the item. The unit cost of the item. The unit of measure.
Contains information about order line pricing and quantity details.
The actual pricing quantity Sum of line totals of all the bundle components. Components having price for information purposes are ignored from this calculation. The discount percentage used to arrive at the unit price. This field is assumed to be applied on the list price. This field is also only informational, and not used by the application. The total invoiced amount for the line. The invoiced pricing quantity. This flag indicates whether price information passed on the line is for information only. If it is 'Y' then line total will not be considered in order total. Invoiced amount for such lines will always be 0. If it is not passed or passed as 'N' then line price is considered in order total. Pass 'Y' in this field to use the price program's prices. The grand total for the line. the list price of the item. This is an informational field. The pricing quantity. The pricing quantity conversion factor. This field is used for finding Pricing_Quantity, using Ordered_Quantity. The pricing UOM for the order line. If "PricingUOM" is not passed it will be defaulted from Catalog. If "PricingUOM" is passed and different from inventory uom, "PricingQtyConversionFactor" attribute will be used for pricing quantity conversion. If "PricingQtyConversionFactor" is not passed it will be considered as zero. Represents the quantity that can be used for pricing the item. Typically, the price programs are based on the total purchase quantity. But if some quantity is cancelled because of inventory shortage (non customer fault), the pricing quantity (which is based on the ordered quantity) changes, but repricing_quantity is not changed. The retail price of the item. this is an informational field. The amount which should be settled before it is actually invoiced. The quantity which should be settled before it is actually invoiced. The Tax Exemption Certificate applied to this order line. This flag indicates whether this order line is taxable or not. This field is for informational purposes only. Currently, it is not used in any tax calculations. If not passed, this flag is defaulted to that of item in the catalog, if exists, else it is defaulted to "N". The unit price for the order line. This table stores information regarding awards that are created out of the promotions. A single promotion can result in to multiple awards. The amount of discount that was applied as a part of this award. A flag indicating if the award is applied. A unique identifier for the award. The primary key of the YFS_PROMOTION_AWARD table. The type of award. If the award is denied, the reason for the denial. A description for the award. Reason this promotion was applied. This identifies the promotion that is added to this order. The promotion this award belongs to. This table stores information about Options associated with a Service Order Line The amount which has been invoiced Short Description for the Option added to the Item The unique identifier for the Option Item. Total amount for the line option. Unit Of Measure of the Option Item Primary key for YFS_ORDER_LINE_OPTION table. For future use. Option is currently priced based on ordering unit of measure. Quantity used for using this option This table stores the information about the work orders to be done at a node on an inventory item or a license plate. The quantity for which work order is completely confirmed. The quantity removed due to exceptions. The quantity for which the work order is created. The status of the work order. The primary key of the YFS_WORK_ORDER table. The work order number. Identifies a work order within the context of a node and enterprise Number of work orders generated for this order line. This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. The enterprise that is associated with this order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Generic table used to store instructions associated with various entities in the system Free-form text indicating any additional information related to the instruction type or otherwise. Categorization of instructions so that they can be grouped together for reference. For example, you may have instructions of type Pick, Pack, and Ship for an order. The URL relating to and/or containing the instructions. You could have an instruction exceeding the limits of a single record. Sequence number is used to provide a way to store a link between such instructions. Number of instructions. This table stores dynamic order references that can be passed to the createOrder API and returned by the getOrderDetails API. Database extensibility of the order tables should be used instead of this table to store implementation specific order fields. Name of the attribute. Value of the attribute. This table stores information about kitted component items. A kit is a collection of items that form a unit. For example, a home theatre system is a unit consisting of component items such as a DVD player, TV, CD player, etc.
Contains information about the quantities for a kit line in Transactional Unit Of Measure.
Component quantity. The number of components required to one kit. UOM on which all the transactional quantities are specified. Component quantity. Cross reference to the customer item. Customer item description. Department that deals with this item. Description for the item. The unique identifer for the component item. short description for the item. Weight of the item. Unit of measure of the ITEM_WEIGHT attribute. The number of components required to one kit. Component Product Class. Cross reference to the supplier ietm. Supplier item description. UPC code for the item. Unit cost of the component item. Component Unit Of Measure. Total number of kit lines fetched. This table stores information about the product items included in a stand-alone service line The unique identifier for the Product Item. The item ID, UOM and OrganizationCode form the unique item identifier for Product Item. Product item quantity Unit of measure of the product item. Generic table to store addresses attached with another entity This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. Identifies the type of address. Part of unique key The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Identifies the type of address. Part of unique key Primary key attribute of YFS_ENTITY_ADDRESS. Link to the entity table Link to the entity's parent table. Denormalized data to allow faster access of records for all addresses attached with the parent. In case of an order line address, this would store order header key Identifies the entity to which this address is attached to Link to YFS_PERSON_INFO table that stores the actual address Number of additional addresses applicable to this order line. This table stores custom and milestone dates for orders Actual Date It is a data attribute to store committed dates from supplier. The unique identifier for a date type for which additional dates are stored Expected Date Order header link Order line link If post release, link to the order release Requested Date This table stores the requested inventory attributes of an item on a order line . The Batch Number that has been specifed in the Order Line. Lot Attribute 1 used to specify the details of the lot. Lot Attribute 2 used to specify the details of the lot. Lot Attribute 3 used to specify the details of the lot. The Lot key reference that has been specifed in the Order Line. The Lot Number that has been specifed in the Order Line. The Lot manufacturing date that has been specifed in the Order Line. The Revision Number that has been specifed in the Order Line. The Tag number that uniquely identifies the Inventory attributes of the Item.
Describes the Sourcing Controls attached to a OrderLine.
If this attribute is populated, inventory availability for that node is overridden based on the value. The node for which either sourcing or procurement has been suppressed when either Suppress Sourcing or Suppress Procurement flags are set to Yes. Free-form reason text indicating any additional information. Flag determines whether to ignore this Node for procurement consideration. Node will not be used by scheduling as a procure from node. Flag determines whether to ignore this Node for sourcing consideration. Node will not be used by scheduling as a ship node. Generic table used to stores notes associated with various entities in the system The identifier of the order modification audit that caused this record. If the notes were entered because of customer contact by phone, the phone no can be stored in this column. If the contact is by email, email ID can be stored here. The time at which the customer contact occurred. The contact type like Phone call, email etc. The values will be selected from common code of code type "CONTACT_TYPE" The user who made the contact. The default value will the logged in user. The customer satisfaction level. Detailed Notes. Priority of the note. 1 is High, 0 is Low. The reason for which the notes are logged. Like "CustomerContact" etc. The values will be selected from common code of code type "NOTES_REASON" The sequence of the note. Transaction for which these notes are applicable. Specifies the name of the Transaction Number Of Notes This table stores reservations that are available for the order line. The batch number that has been specified on the reservation. The inventory demand type used by the reservation. This field is only used internally. For all user-created reservations, this will be defaulted from the document params. The reserved item. The lot number that has been specified on the reservation. The ship node at which the item has been reserved. The first date on which the reserved inventory is available. The reserved item's product class.
The quantity reserved.
 The date when the reserved inventory is needed, such as the shipping date. The revision number that has been specified on the reservation. The tag number that has been specified on the reservation. This field is calculated based on the tag identifiers. The reserved item's unit of measure. Specifies the unique identifiers of the bundle parent order line for this order line. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the service request details for the order line.
This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the service request details for the order line.
Contains information about the request details for which this delivery or service request is created.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the service request details for the order line.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the delivery request details for the order line.
Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the child relationships of the order lines.
Contains information about the parent order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the child order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. The child order line key of the relationship. The order header key of the related order lines. The primary key for the YFS_ORDER_LINE_RELATIONSHIP table. The parent order line key of the relationship. The type of relationship between order lines.
Contains information about the parent relationships of the order lines.
Contains information about the parent order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the child order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. The child order line key of the relationship. The order header key of the related order lines. The primary key for the YFS_ORDER_LINE_RELATIONSHIP table. The parent order line key of the relationship. The type of relationship between order lines. This table stores order line scheduling information for order lines. An order line can have multiple order line schedules. Any change in sourcing related attributes like ship node, reciving node, lot number etc. inserts a record into this table.
Contains information about the transaction quantity for the schedule.
Quantity. UOM on which all the transactional quantities are specified. The batch number that has been specified on the scheduled order line. The date the scheduled order line is expected to be delivered by. The date the scheduled order line is expected to ship by. The lot number that has been specified on the scheduled order line. The node that is used as either forwarding or merge location. The order header that is associated with this scheduled order line. The order line that is associated with this scheduled order line. The primary key for the YFS_ORDER_LINE_SCHEDULE table. The node from which the scheduled order line should be procured if it cannot be sourced from the ship node specified on the order line. Quantity. The node that will receive the scheduled order line, if applicable. The revision number that has been specified on the scheduled order line. The number of the scheduled order line. The date the scheduled order line should be shipped by. The ship node fulfilling this scheduled order line. The tag number that has been specified on the scheduled order line.
Contains information about the price and total amount details for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are invoiced for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are not invoiced for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are invoiced for the order line represented in Enterprise Currency.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are not invoiced for the order line represented in Enterprise Currency.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line. This table stores any additional charges or discounts that can be added to an order line. Charge amount. Link to YFS_CHARGE_CATEGORY. Link to YFS_CHARGE_NAME. Link to YFS_CHARGE_NAME table. Fixed charge amount for this order/invoice line. When the line charge is associated with an order line, this amount will be invoiced on the first invoice for this order line. Charge per unit for the item on this order/invoice line. Invoiced charge amount. Applicable only to charges for an Order line. This is the charge per line which has already been invoiced. Invoiced charge per unit. Describes if the charge is billable. Default: N Describes if the charge is discountable. Default: N Any additional reference related to this line charge. Remaining charge amount. Remaining charge per line. Remaining charge per unit. This table stores tax related information for various entities in the system. The charge category for which tax is being charged. For example, Labeling or Handling. Charge name for which tax is being charged. For example, Price Ticket. Link to YFS_CHARGE_NAME table. Tax amount invoiced. Reference 1 Reference 2 Reference 3 Remaining tax. The tax amount. Tax cannot be less than zero. The tax name. Percentage amount for tax calculation The amount of this tax which had been invoiced. The total amount of this tax. The amount of this tax that has not been invoiced. Tax name. This table stores status-quantity break up for each line-schedule. Similar to order lines, a kit line can be broken into multiple schedules
Contains information about the quantities for kit detail in Transactional Unit Of Measure.
Quantity. UOM on which all the transactional quantities are specified. Link to YFS_ORDER_KIT_LINE table. Quantity. Ship by date for the kit line. Tag number. Expected delivery date. Expected shipment date. Ship by date. Tag number. Quantity currently in this status. Total quantity which has ever been moved into this status. If there is a cyclic status (for example, backorder which can happen multiple times), this attribute does not provide useful information. UOM on which all the transactional quantities are specified. The order header that is associated with this order release status record. The order line that is associated with this order release status record. The order line schedule that this order release status record is associated with. The order release that is associated with this order release status record. The primary key for the YFS_ORDER_RELEASE_STATUS table. The pipeline that this release line belongs to. The node to which the order line is to be shipped. The node at which the order line will be fulfilled. This field indicates the status of the order release. The date when the last positive quantity was moved into this status. Description of the order line status. The quantity currently in this status. This field is not currently used. The total quantity to ever be moved into this status. If you have a cyclic status (for instance backorder, which can happen multiple times), this column will not provide useful information. The minimum order line quantity that must be fulfilled in an order release before it is shipped. Invoiced quantity on the order line. Total quantity that can be cancelled from the line. The quantity of the the line item that has been ordered. If part of line is cancelled, this number is reduced appropriately. If an order line is returned, this number is not reduced. Quantity which was ordered during order creation. This is not modified after order confirmation. Received quantity on the order line. Remaining quantity. Quantity which should be settled before it is actually invoiced. Shippped quantity on the order line. Quantity which has been split from this line due to substitutions, price negotiations etc. Quantity on the order line in the current status. Quantity which was over or under received. UOM on which all the transactional quantities are specified. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The table stores product information. The unique identifier for the item. The unit of measure for item quantity. The order line number. The sub line number. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The table stores product information. The unique identifier for the item. The unit of measure for item quantity. The order line number. The sub line number. This table stores contains all the hold types defined for an order This table stores the log notes when status of a hold type changes Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type log. Primary key for YFS_ORDER_HOLD_TYPE_LOG table. The reason text associates to this order hold type. This is the user who can approve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier for the transaction which applied the hold type on order . Transaction name which created the hold type. User who modified the record. Hold type. Timestamp when this hold type was added to the order. Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type. Primary Key of YFS_ORDER_HEADER. Order line link The reason text associates to the order hold type. This is the user who can resolve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier of the transaction which applied the hold type on order . Transaction name which created the hold type.
Only applicable for published data of Delete Order event, which can be raised by the deleteOrder API. Action = DELETE will be published to indicate that the order line will be deleted.
The date when this line will be allocated. This is calculated at order creation time, based on the node processing time. This field is not used from version 50 onwards. The ALLOCATION_LEAD_TIME field is used instead. The number of days it will take any node to ship the item after a ship advice is sent. It is defaulted from the Rule Set Field Name (YFS_RULES.LEAD_TIME). The release process will this value, or the scheduled node's lead time (setup at ship node level), whichever is greater. This field is not currently used. Displays a warning message if CannotScheduleBeforeDate or CannotScheduleAfterDate fields have a Non-Null value. The quantity avialable through modification rules for making a stop delivery request for this line. A flag to indicate if the order line is awaiting for a Delivery service association. Mark For Node as identified by the buyer for eg: it could be a person,store,DC Receiving node as identified by the buyer for eg:Store,DC Number this flag indicates whether the product line can be associated with service lines. The customers carrier account number. The carrier service code for this order line. The order header that is associated with this chained order line. If this line is chained from another order line, this key will point to the parent order line's header record. The order line that is associated with this chained order line. If this line is chained from another order line, this key will point to the parent order line. It is a data attribute to store the quantity that is committed by supplier. A user defined variable that can be used for condition building in process modeling. A user defined variable that can be used for condition building in process modeling. This field is used by Sterling Multi-Channel Selling Solution so that Visual Modeler can be opened with existing options. The buyer PO line number. The buyer's PO number. This field indicates who will pay the freight. Sterling Multi-Channel Fulfillment Solution understands values such as SUPPLIER, ENTERPRISE and MARKETPLACE to mean that each of these organizations will pay for the freight. You could however pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The delivery method for the product line. This field can be used for line classification and reporting purposes. This field indicates whether any order lines are dependant on the parent order line. This field can only be specified for the parent line. If this field is specified, it is defaulted on all of the dependant lines. This field is ignored if it is specified on a dependant line. The order line key that this order line is associated with. This field will indicate which order line is the parent of the the order line for line dependencies. The order header that is associated with this derived order line. If this line was derived from another order line, this key will point to the parent order line's header record. The order line that is associated with this derived order line. If this line was derived from another order line, this key will point to the parent order line. The order release that this derived order line is associated with. If this line was derived from another order line, this key will point to the parent order release record. the identifier of the distribution group that is used to determine the ship node(s) that will ship the order line. If not provided, the seller organization's default distribution rule ID is used. If provided, it must be a valid ID for the Seller organization. The minimum order line quantity that must be fulfilled in an order release before it is shipped. Indicates Freight Terms for the line. The method of fulfilling the order line during scheduling. This field can be matched with the corresponding field in the YFS_SOURCING_RULE_HDR table and the appropriate sourcing rule can be selected. Thie field indicates when inventory for the product line will be available. This flag indicates whether the order line is a gift item.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the line has associated delivery lines. Valid only for product lines.
Indicates if order line has lines derived from it.
Default: N
Valid Values: Y or N
Indicates if the line has associated service lines. Valid only for product lines. This attribute is not in use in prior to Sterling Supply Chain Applications 7.1. If you want to use deprecated functionality, set the rule 'Use deprecated hold Functionality'. If the rule is not set, this flag is set/reset by the application. Application sets this flag to 'Y' if order line has any hold types. Flag is reset to 'N' if there are no hold types on order line. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order line. This field is not currently used. The expiration date of the import license number. The import license number to be used. A flag to indicate if the order line should be backordered upon creation. If passed as 'Y', the line will be backordered even if inventory is available. This flag is ignored if reservation is mandatory. The total extended price which has already been invoiced. Invoiced quantity on the order line. Invoiced quantity on the order line. Indicates if Order line is bundle parent line or not.

Valid Values: Y or N
This flag indicates whether the pre-defined node on the line is firm. If IsFirmPredefinedNode is marked as N, then the node on the line is ignored during scheduling. If not passed, the value defaults to Y. This field indicates what kind of item is on the order line. The collection of items that form a unit. For example, a home theatre system is a unit consisting of kit components, such as a DVD player, TV, CD player, etc. The quantity that is used to compute ordered quantity for bundle component line. It can be specified only for bundle components. If specified ordered quantity will be set to KitQty*OrderedQty of the bundle parent. The order line sequence number. The line type. This field can be used in process modeling for pipeline determination, or for doing conditional processing for this line. Maximum order line status among all records that belong to an order. Description of maximum order line status among all records that belong to an order. The node where two or more order lines that are to be delivered together should be merged before the final delivery. This field is required when the DependancyShippingRule is set to '02'. Additionally this field will indicate forwarding location for zone skipping. Minimum order line status among all records that belong to an order. Description of minimum order line status among all records that belong to an order. The preferred minimum ship by date of the available supply that order line can allocate against. This only applies to the order line or kit line with time-sensitive item. If order line is in more than one status then this flag will be returned as "Y". Total quantity that can be cancelled from the line. The order header that this order line is associated with. The primary key for the YFS_ORDER_LINE table. The quantity of the line item that has been ordered. If part of the line is cancelled, this number is reduced appropriately. If an order line is returned, this number is not reduced. The line from which this line was created (split process). The quantity which was ordered at order creation. This is not modified after order confirmation. The sum of all the line level charges. The code indicating the type of packlist to be used for the line. Lines requiring different pack lists are not mixed in a single order release. This flag indicates whether this line is a parent of a dependency group. The code for personalization. This flag indicates whether this line needs personalization. This field is used internally. The pipeline that this order line belongs to. The order line number. The procurement node that is associated with this order line. The order line should be procured from that node if the products or services cannot be sourced from the shipnode specified on the order line. The promised end date of the appointment. The promised start date of the appointment. This field is passed out in the Tax calculation user exits. The receiving node that is associated with this order line. Remaining quantity. The requested cancel date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The requested delivery date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The requested ship date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The reservation ID. If this item was reserved before order creation, pass an ID to associate the line with the reservation. This flag indicates whether this line can be created without a reservation. If set to Y, creation of this line or any quantity addition to this line will be allowed only if the quantity can be reserved. If a ProcureFromNode is also present on the line, then the reservation will be carried out on the procure from node. The reservation identifier. If this item was reserved before order creation, pass an ID to associate the line with the reservation. The reason for returning the order line. Long description of the return reason code. Short description of the return reason code. The carrier to be used for this line. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. The reason for which schedule has failed on this order line. The segment of the inventory. The segment type of the inventory. The serial number of the item. The ship node that is associated with this order line. If provided, all releases will be made against this node. The ship to identifier. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. The ship to address that is associated with this order line. If not provided, it is defaulted from order header. This field is not currently used. It is a consolidation group id that is used as a standard do not mix constraint.Releases belonging to same shipment consolidation group may consolidate to same shipment This field is not currently used. The quantity which has been split from this line due to substitutions, price negotiations etc. Status description of the order line. Quantity on the order line in the current status. The sub line number. Substituted ItemID. This field is only populated if the item on the Order line is substituted.

Valid Values: Y or N
Substituted Item UOM. This field is only populated if the item on the Order line is substituted. The timezone in which the promised appointment has been recorded. The transaction discrepancy quantity.
Indicates if data is fetched from the history table rather than the regular table.
Default: N
Valid Values: Y or N
Number of Order Lines in the Order. This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide. The currency code in which this order is being processed. All price fields are assumed to be in this currency. The Enterprise's default currency code. The date which was used to determine the conversion rate. The conversion rate from the order's original currency to the Enterprise's currency. This is not used internally within Sterling Multi-Channel Fulfillment Solution. This field is provided so that reports can be built in a standard currency for an Enterprise using SQLs. The grand total for the order. Includes all line charges and taxes. Generic table used to store instructions associated with various entities in the system Free-form text indicating any additional information related to the instruction type or otherwise. Categorization of instructions so that they can be grouped together for reference. For example, you may have instructions of type Pick, Pack, and Ship for an order. The URL relating to and/or containing the instructions. You could have an instruction exceeding the limits of a single record. Sequence number is used to provide a way to store a link between such instructions. Number of instructions. Generic table used to stores notes associated with various entities in the system The identifier of the order modification audit that caused this record. If the notes were entered because of customer contact by phone, the phone no can be stored in this column. If the contact is by email, email ID can be stored here. The time at which the customer contact occurred. The contact type like Phone call, email etc. The values will be selected from common code of code type "CONTACT_TYPE" The user who made the contact. The default value will the logged in user. The customer satisfaction level. Detailed Notes. Priority of the note. 1 is High, 0 is Low. The reason for which the notes are logged. Like "CustomerContact" etc. The values will be selected from common code of code type "NOTES_REASON" The sequence of the note. Transaction for which these notes are applicable. Specifies the name of the Transaction Number Of Notes This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Generic table to store addresses attached with another entity This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. Identifies the type of address. Part of unique key The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Identifies the type of address. Part of unique key Primary key attribute of YFS_ENTITY_ADDRESS. Link to the entity table Link to the entity's parent table. Denormalized data to allow faster access of records for all addresses attached with the parent. In case of an order line address, this would store order header key Identifies the entity to which this address is attached to Link to YFS_PERSON_INFO table that stores the actual address The number of additional addresses associated with the order.
Currency of the Order
Currency of the Order's Enterprise
Date for which the conversion rate between currencies is used
Conversion rate between currencies
Total Amount
Total Charges in Enterprise currency
Total Discount in Enterprise currency
Grand total Tax Amount for the order in Enterprise currency
Grand total amount for the Order in Enterprise currency
Order Header Level Charges in Enterprise currency
Order Header Level Discount in Enterprise currency
Order Header Level Tax in Enterprise currency
Order Header Level Total amount in Enterprise currency
Sub Total amount for all the lines in Enterprise currency
Grand Charges in Enterprise currency Grand Discount in Enterprise currency Grand Tax in Enterprise currency Grand Total in Enterprise currency Header Charges in Enterprise currency Header Discount in Enterprise currency Header Tax in Enterprise currency Header Total in Enterprise currency Line Sub Total in Enterprise currency This table stores dynamic order references that can be passed to the createOrder API and returned by the getOrderDetails API. Database extensibility of the order tables should be used instead of this table to store implementation specific order fields. Name of the reference's name-value pair. Value assigned to the corresponding name. This table stores details about the customer's payment methods. The key to this table is posted in YFS_CHARGE_TRANSACTION table. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Awaiting charge amount on this payment method. Awaiting authorization amount on this payment method. The bill to address that is associated with this payment. Can be passed if different from the bill to address on the order. The sequence in which the payment method is to be used for charging. The cheque number. The cheque reference. The expiration date for the credit card. The credit card name. The credit card number. The credit card type group. The account number of the customer. The customer PO account number. The four digits of the credit card number that should be displayed. If not passed, it is defaulted to be the last four digits of the credit card number. The four digits of the customer account number that should be displayed. If not passed, it is defaulted to be the last four digits of the customer account number. The four digits of the payment reference 1 that should be displayed. If not passed, it is defaulted to be the last four digits of the payment reference 1. The four digits of the stored value card that should be displayed. If not passed, it is defaulted to be the last four digits of the stored value card number. The first name of the credit card holder.
The funds available to be charged on this payment method as determined by the GetFundsAvailable user exit, if it was invoked.
Indicates if the GetFundsAvailable user exit was invoked for this payment method.
 This flag indicates whether the payment type is incomplete. The last name of the credit card holder. The maximum amount that can be charged on this payment method. However, if UnlimitedCharges=Y, this amount will not be considered. The middle name of the credit card holder. The primary key for the YFS_PAYMENT table The payment reference 1. The payment reference 2. The payment reference 3. The payment type of this payment method. The total amount requested for authorization on this payment method. The total amount requested for charging on this payment method. Flag to indicate more charging has to be suspended. The stored value card number. The total amount auhorized on this payment method. The total amount charged on this payment method. The total refunded amount on this payment method. Indicates if there is a limit to the amount that can be charged on the payment method. If not passed, defaults to Y. This table stores information about financial transactions associated with order processing. Every action carried out on an order which may have an impact on financial components is logged in this table Stores detail about amount collected against the invoice Amount collected by the Invoice Collection for the linked Order Invoice. Timestamp when the record was created. Invoice number Classifies an invoice. For example, Orders, Returns, Debit Memo, Credit Memo, Info etc Not used internally. Can be updated externally by custom logic to group invoices together Link to invoice Link to a return release if invoice is created for a return Link to a shipment if invoice was created for a shipment Grand total for the invoice This table stores detailed information about authorizations and charges made against a credit card. This information would typcially be returned by credit card interface programs such as CyberSource or PaymentTek. The authorization amount. AVS Autorization code. The authorization code. The authorization return code. The authorization return flag. The authorization return message. The authorization time. The CVV authorization code. The charge transaction that is associated with this credit card transaction. The primary key for the CREDIT_CARD_TRANSACTION table. The internal return code. The internal return flag The internal return message. The parent key. The reference 1. The reference 2. Authorization request Id. The amount of the transaction. The time at which the transaction request was made. The return code for the transaction. The flag returned by the transaction. The message returned by the transaction. The transaction type. This table stores details about the customer's payment methods. The key to this table is posted in YFS_CHARGE_TRANSACTION table. The sequence in which the payment method is to be used for charging. The cheque number. The cheque reference. The expiration date for the credit card. The credit card name. The credit card number. The credit card type group. The account number of the customer. The customer PO account number. The four digits of the credit card number that should be displayed. If not passed, it is defaulted to be the last four digits of the credit card number. The four digits of the payment reference 1 that should be displayed. If not passed, it is defaulted to be the last four digits of the payment reference 1. The four digits of the stored value card that should be displayed. If not passed, it is defaulted to be the last four digits of the stored value card number. The first name of the credit card holder. This flag indicates whether the payment type is incomplete. The last name of the credit card holder. The maximum amount that can be charged on this payment method. However, if UnlimitedCharges=Y, this amount will not be considered. The middle name of the credit card holder. The primary key for the YFS_PAYMENT table The payment reference 1. The payment reference 2. The payment reference 3. The payment type of this payment method. The total amount requested for authorization on this payment method. The total amount requested for charging on this payment method. This field indicates whether further payment processing will be allowed on this payment method. If this value is set to 'Y', further payment processing will not be allowed on this payment method. The stored value card number. The amount that has been refunded to a new payment method based on this payment's payment type refund preferences. The total amount auhorized on this payment method. The total amount charged on this payment method. The total refunded amount on this payment method. Indicates if there is a limit to the amount that can be charged on the payment method. If not passed, defaults to Y.
The order to which these funds were transferred. This information is only valid for charge transactions where ChargeType is TRANSFER_OUT
The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
The order from which these funds were transferred. This information is only valid for charge transactions where ChargeType is TRANSFER_IN.
The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
The identifier of the order modification audit that caused this record. The date and time until which the authorization specified by the authorization ID is applicable. For authorization requests, this field holds the identifier of the authorization that was made. For charge requests, this field holds the authroization ID to be used for charging the amount. The amount that could be charged to the buyer if the order was fulfilled. At the time of fulfillment, a negative entry is made in this column and positive entry in the DEBIT_AMOUNT column. The primary key for the YFS_CHARGE_TRANSACTION table. The type of charge that is being applied to the order. The date and time when the charge was realized. The amount that was actually charged or refunded to the buyer. The amount that should be charged or refunded to the buyer. This field is used internally by the application to keep track of the amount which has been posted in the invoices as "collected". The date and time when the charge request was processed. This flag indicates whether the request was created for a precharge or a payment method whose payment type has the ChargeInsteadOfAuth flag turned on. The amount that is authorized for the order. The order header that is associated with this charge transaction. The key to the invoice that was created for this record, if applicable. Invoices are created for shipments, returns, or debit and credit memos. The payment method that is associated with this charge transaction. The amount that is requested for the charge or authorization of record of types "REQUEST_CHARGE" and "REQUEST_AUTHORIZATION". Once the request is processed, the actual amount will be shown as "CreditAmount" or "OpenAuthorizedAmount", for charge and authorization requests respectively. This field holds the amount for which a pre-settlement (settlement before invoice) is requested. Charge requests will be created for this amount. This field indicates the status of this record. The reason code for the current status of a charge transaction. Transaction Date. The Order Header Key of the order that funds are being transferred from. The Order Header Key of the order that funds are being transferred to. The user exit call status of this record. The status will be "INVOKED" if the transaction fails during or after the user exit call, otherwise the value will be blank. Total Credits Total Debits Total Open Authorizations Total Open Bookings Total amount of funds transferred in from other orders. Total amount of funds transferred out to other orders. This table stores custom and milestone dates for orders Actual Date It is a data attribute to store committed dates from supplier. The unique identifier for a date type for which additional dates are stored Expected Date Order header link Order line link If post release, link to the order release Requested Date This table stores information about Order Product and Service Associations This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated product line. Prime line number of the associated product line. Sub line number of the associated product line. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated service line. Prime line number of the associated service line. Sub line number of the associated service line. Flag to indicate whether to hold schedule till completion Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours This table stores relationship between order lines. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated product line. Prime line number of the associated product line. Sub line number of the associated product line. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated service line. Prime line number of the associated service line. Sub line number of the associated service line. The type of relationship between order lines. This table stores information regarding promotions that are associated to an order or any of its lines. If the promotion is denied, the reason for the denial Description of the promotion A flag indicating if the promotion is applied This identifies the promotion that is added to this order. The primary key of the YFS_PROMOTION table. The type of promotion. Like DISCOUNT, BOGO. This table stores information regarding awards that are created out of the promotions. A single promotion can result in to multiple awards. The amount of discount that was applied as a part of this award. A flag indicating if the award is applied. A unique identifier for the award. The primary key of the YFS_PROMOTION_AWARD table. The type of award. If the award is denied, the reason for the denial. A description for the award. Reason this promotion was applied. This identifies the promotion that is added to this order. The promotion this award belongs to. This table stores special services supported by various carriers that can be used when shipping packages. Examples of special services are signature required upon delivery of the package, Saturday pick-up and Saturday delivery. This table stores the special services supported by Carriers.
The code identifying the Special Service to be performed on the Order. SpecialServicesCode must be defined in the configuration
This table stores contains all the hold types defined for an order This table stores the log notes when status of a hold type changes Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type log. Primary key for YFS_ORDER_HOLD_TYPE_LOG table. The reason text associates to this order hold type. This is the user who can approve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier for the transaction which applied the hold type on order . Transaction name which created the hold type. User who modified the record. Hold type. Timestamp when this hold type was added to the order. Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type. Primary Key of YFS_ORDER_HEADER. Order line link The reason text associates to the order hold type. This is the user who can resolve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier of the transaction which applied the hold type on order . Transaction name which created the hold type. Stores the relationship between a set of answers and the entities which provided these answers. Stores each answer for an answer set. The answer set for this answer. Primary key of answer tran. The answer for the question. Identifier for the question that this answer is for. Number of answer sets in the Order. Primary key of answer set tran. The person info record this answer set is stored for. The name of the table which stores the record of the primary owner of this answer set. The key for the primary owner of this answer set.
The question type that this answer set is for.
 Number of answer sets in the Order.
Contains information about the price and total amount details for the order line.
Total Charges
Total Discount
Grand total Tax Amount for the order
Grand total amount for the Order
Order Header Level Charges
Order Header Level Discount
Order Header Level Tax
Order Header Level Total amount
Sub Total amount for all the lines
Grand Charges Grand Discount Grand Tax Grand Total Header Charges Header Discount Header Tax Header Total Line Sub Total
Contains information about the price and total amount details that are not invoiced for the order.
Grand Charges Grand Discount Grand Tax Grand Total Header Charges Header Discount Header Tax Header Total Line Sub Total This table stores charges that are applied at the header level. The amount of the charge. The charge category. For example, Labeling or Handling. The name of the charge. For example, Price Ticket. Primary key for a charge name. Applicable only to charges for an Order. This is the amount which has already been invoiced. Describes if the charge is billable. Default: N Describes if the charge is discountable. Default: N Reference information about this charge. Remaining Charge Amount This table stores tax related information for various entities in the system. The charge category for which tax is being charged. For example, Labeling or Handling. Charge name for which tax is being charged. For example, Price Ticket. Primary key for a charge name. Tax amount invoiced. Reference 1 Reference 2 Reference 3 Remaining Tax The tax amount. Tax cannot be less than zero. The tax name. Percentage amount for tax calculation This flag indicates if a charge can be taxed. The amount of this tax which had been invoiced. The total amount of this tax. The amount of this tax that has not been invoiced. Tax name. This table stores status-quantity break up for each line-schedule. Similar to order lines, a kit line can be broken into multiple schedules Quantity. UOM on which all the transactional quantities are specified. Link to YFS_ORDER_KIT_LINE table. Quantity. Ship by date for the kit line. Tag number. The date the scheduled order line is expected to be delivered by. The date the scheduled order line is expected to ship by. The node that will receive the scheduled order line, if applicable. The date the scheduled order line should be shipped by. The ship node fulfilling this scheduled order line. The tag number that has been specified on the scheduled order line. Quantity currently in this status. Total quantity has ever been moved into this status. If there is a cyclic status (for example, backorder which can happen multiple times), this column does not provide useful information. UOM on which all the transactional quantities are specified. The order header that is associated with this order release status record. The order line that is associated with this order release status record. The order line schedule that this order release status record is associated with. The order release that is associated with this order release status record. The primary key for the YFS_ORDER_RELEASE_STATUS table. The pipeline that this release line belongs to. The node that will receive the scheduled order line, if applicable. The ship node fulfilling this scheduled order line. This field indicates the status of the order release. The date when the last positive quantity was moved into this status. Description of the order status. The quantity currently in this status. This field is not currently used. The total quantity to ever be moved into this status. If you have a cyclic status (for instance backorder, which can happen multiple times), this column will not provide useful information. A return order for which this exchange order was created. This information is only valid for exchange orders. The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
An exchange order created for this return order. This information is only valid for return orders. The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores information regarding a stop delivery request for an order. This table stores information regarding a stop delivery request's detail.
Contains information about the quantities for a stop delivery detail in Transactional Unit Of Measure.
The requested quantity in the transactional UOM for this stop delivery request detail. The successful quantity in the transactional UOM for this stop delivery request detail. UOM on which all the transactional quantities are specified. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Comments made in regards to this Stop Delivery Request Detail. The quantity requested to stop delivery. The primary key for the YFS_STOP_DEL_REQ_DTL table. The quantity that was successfully stopped. The total number of StopDeliveryRequestDetail elements returned. Comments made in regards to this Stop Delivery Request. The date and time the stop request was made. The primary key for the YFS_STOP_DEL_REQ_HDR table. The ID for this stop delivery request. The total number of StopDeliveryRequest elements returned.
Only applicable for published data of Delete Order event, which can be raised by the deleteOrder API. Action = DELETE will be published to indicate that the order will be deleted.
The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The bill to address that is associated with this order. Mark For Node as identified by the buyer for eg: it could be a person,store,DC The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. Receiving node as identified by the buyer for eg:Store,DC Number This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. This flag indicates whether the order needs to be cancelled in case of inventory shortage. If not specified, most restrictive rule will be used from customer preference or scheduling rule. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. This flag indicates whether the order was created by a node. This field is used during blind return creation at the nodes. Timestamp when the record was created. User who created the record. The PO number of the customer's customer. In some situations, this may need to be printed on the actual packaging. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. This flag indicates whether this order is to be used as the default template. For this order to be used as a default template, the document type of the order being created should be configured to set the template document type as this orders document type. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. This field can be used for order classification and reporting purposes. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
This flag indicates whether the order has any derived children. This flag indicates whether the order has any derived parent.
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. This flag indicates whether the complete line needs to be shipped. If not specified, most restrictive rule will be used from customer preference or scheduling rule. This flag indicates whether the complete order line needs to be shipped from a single ship node. If not specified, most restrictive rule will be used from customer preference or scheduling rule. This flag indicates whether the complete order needs to be shipped. If not specified, most restrictive rule will be used from customer preference or scheduling rule. This flag indicates whether the complete order needs to be shipped from a single ship node. If not specified, most restrictive rule will be used from customer preference or scheduling rule. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. Timestamp when the record was last modified. User who modified the record. If order is in more than one status then this flag will be returned as "Y". Negotiation Status Negotiation Status Description This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used This field indicates what scheduling will first optimize on. If not specified scheduling rule will be used to determine optimization type. This flag indicates whether the order has reached the end of its processing lifecycle. The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. This field is used by Sterling Multi-Channel Selling Solution. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The payment rule that is associated with this order. All decisions on payment handling are controlled by this rule. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. This field is used by Sterling Multi-Channel Selling Solution. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. The date that this order should be purged from the history table. If set, this date will override the date determined based on the History Purge Lead Days. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. This flag indicates whether the sale transaction has been voided. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The ship node at which this order will be fulfilled. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. The ship to address that is associated with this order. This field is used by Sterling Multi-Channel Selling Solution. This field is used by Sterling Multi-Channel Selling Solution. This field is used by Sterling Multi-Channel Selling Solution. This attribute will be used to determine node for sourcing. Status of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. Indicates a team that can manage this order. Default is Null. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
This table stores details on funds distributed between 2 charge transaction records. The primary key for the YFS_CHARGE_TRAN_DIST table. The amount that was distributed to the charge transaction record, DistributedToChargeTranKey, from the charge transaction record, DistributedFromChargeTranKey. The charge transaction that is associated with this charge transaction distribution. This is the charge transaction that distributed funds. The charge transaction that is associated with this charge transaction distribution. This is the charge transaction that funds were distributed to. The order that is associated with this charge transaction distribution. This table stores information about financial transactions associated with order processing. Every action carried out on an order which may have an impact on financial components is logged in this table The identifier of the order modification audit that caused this record. The date and time until which the authorization specified by the authorization ID is applicable. For authorization requests, this field holds the identifier of the authorization that was made. For charge requests, this field holds the authroization ID to be used for charging the amount. The amount that could be charged to the buyer if the order was fulfilled. At the time of fulfillment, a negative entry is made in this column and positive entry in the DEBIT_AMOUNT column. The primary key for the YFS_CHARGE_TRANSACTION table. The type of charge that is being applied to the order. The date and time when the charge was realized. The amount that was actually charged or refunded to the buyer. The amount that should be charged or refunded to the buyer. This field is used internally by the application to keep track of the amount which has been posted in the invoices as "collected". The date and time when the charge request was processed. This flag indicates whether the request was created for a precharge or a payment method whose payment type has the ChargeInsteadOfAuth flag turned on. The amount that is authorized for the order. The order header that is associated with this charge transaction. The key to the invoice that was created for this record, if applicable. Invoices are created for shipments, returns, or debit and credit memos. The payment method that is associated with this charge transaction. The amount that is requested for the charge or authorization of record of types "REQUEST_CHARGE" and "REQUEST_AUTHORIZATION". Once the request is processed, the actual amount will be shown as "CreditAmount" or "OpenAuthorizedAmount", for charge and authorization requests respectively. This field holds the amount for which a pre-settlement (settlement before invoice) is requested. Charge requests will be created for this amount. This field indicates the status of this record. The reason code for the current status of a charge transaction. The Order Header Key of the order that funds are being transferred from. The Order Header Key of the order that funds are being transferred to. The user exit call status of this record. The status will be "INVOKED" if the transaction fails during or after the user exit call, otherwise the value will be blank. This table stores information about financial transactions associated with order processing. Every action carried out on an order which may have an impact on financial components is logged in this table The identifier of the order modification audit that caused this record. The date and time until which the authorization specified by the authorization ID is applicable. For authorization requests, this field holds the identifier of the authorization that was made. For charge requests, this field holds the authroization ID to be used for charging the amount. The amount that could be charged to the buyer if the order was fulfilled. At the time of fulfillment, a negative entry is made in this column and positive entry in the DEBIT_AMOUNT column. The primary key for the YFS_CHARGE_TRANSACTION table. The type of charge that is being applied to the order. The date and time when the charge was realized. The amount that was actually charged or refunded to the buyer. The amount that should be charged or refunded to the buyer. This field is used internally by the application to keep track of the amount which has been posted in the invoices as "collected". The date and time when the charge request was processed. This flag indicates whether the request was created for a precharge or a payment method whose payment type has the ChargeInsteadOfAuth flag turned on. The amount that is authorized for the order. The order header that is associated with this charge transaction. The key to the invoice that was created for this record, if applicable. Invoices are created for shipments, returns, or debit and credit memos. The payment method that is associated with this charge transaction. The amount that is requested for the charge or authorization of record of types "REQUEST_CHARGE" and "REQUEST_AUTHORIZATION". Once the request is processed, the actual amount will be shown as "CreditAmount" or "OpenAuthorizedAmount", for charge and authorization requests respectively. This field holds the amount for which a pre-settlement (settlement before invoice) is requested. Charge requests will be created for this amount. This field indicates the status of this record. The reason code for the current status of a charge transaction. The Order Header Key of the order that funds are being transferred from. The Order Header Key of the order that funds are being transferred to. The user exit call status of this record. The status will be "INVOKED" if the transaction fails during or after the user exit call, otherwise the value will be blank. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide. This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide. The currency code in which this order is being processed. All price fields are assumed to be in this currency. The Enterprise's default currency code. The date which was used to determine the conversion rate. The conversion rate from the order's original currency to the Enterprise's currency. This is not used internally within Sterling Multi-Channel Fulfillment Solution. This field is provided so that reports can be built in a standard currency for an Enterprise using SQLs. The grand total for the order. Includes all line charges and taxes. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. This table stores description in different languages. A localized description. An extended localized description. Locale for which the extended description is stored. Short description. This field indicates the alternate ItemID, which can be passed instead of the actual ItemID. This is an alias for the ItemID. The currency in which the unit cost is specified. The country of origin being requested. Indicates if credit has been issued upon receipt of the returned goods. The item ID for the buyer. The item description of the buyer organization. The Export Commodity Control Number for a commodity contained in the shipment, as indicated on the Waybill. The harmonized code, if applicable. The ISBN number, if applicable. Is the line returnable. The description of the item. The identifier for the item. The ITEM_ID, UOM, and PRODUCT_CLASS form the unique inventory identifier for an order line. The ITEM_ID, UOM and ORGANIZATION_CODE form the unique item identifier for the Product Management module. The short description of the item. The weight of the item. The unit of measure used for weight. The item identifier for the manufacturer. The item description for the manufacturer. The name of the manufacturer. The National Motor Freight Classification - A way of classifying goods for the purposes of transportation. The National Motor Freight Classification - A way of classifying goods for the purposes of transportation. The description of the NMFC. National Motor Freight Classification is a way of classifying goods for the purposes of transportation. The product class. This field is used as an inventory identifier. The product line for the item Number of days within which the item must be returned for it to be accepted as a return on the system. The Schedule B commodity codes - A 10-digit numeric codes used to identify products that are exported to other countries. The item ID of the supplier (if this is a PO or the line is being drop-shipped and the supplier is known upfront). The item description of the supplier (if this is a PO or line is being drop-shipped and the supplier is known upfront). The product code classification for the purposes of taxation. The UPC Code of the item. The unit cost of the item. The unit of measure.
Contains information about order line pricing and quantity details.
The actual pricing quantity Sum of line totals of all the bundle components. Components having price for information purposes are ignored from this calculation. The discount percentage used to arrive at the unit price. This field is assumed to be applied on the list price. This field is also only informational, and not used by the application. The total invoiced amount for the line. The invoiced pricing quantity. This flag indicates whether price information passed on the line is for information only. If it is 'Y' then line total will not be considered in order total. Invoiced amount for such lines will always be 0. If it is not passed or passed as 'N' then line price is considered in order total. Pass 'Y' in this field to use the price program's prices. The grand total for the line. the list price of the item. This is an informational field. The pricing quantity. The pricing quantity conversion factor. This field is used for finding Pricing_Quantity, using Ordered_Quantity. The pricing UOM for the order line. If "PricingUOM" is not passed it will be defaulted from Catalog. If "PricingUOM" is passed and different from inventory uom, "PricingQtyConversionFactor" attribute will be used for pricing quantity conversion. If "PricingQtyConversionFactor" is not passed it will be considered as zero. Represents the quantity that can be used for pricing the item. Typically, the price programs are based on the total purchase quantity. But if some quantity is cancelled because of inventory shortage (non customer fault), the pricing quantity (which is based on the ordered quantity) changes, but repricing_quantity is not changed. The retail price of the item. this is an informational field. The amount which should be settled before it is actually invoiced. The quantity which should be settled before it is actually invoiced. The Tax Exemption Certificate applied to this order line. This flag indicates whether this order line is taxable or not. This field is for informational purposes only. Currently, it is not used in any tax calculations. If not passed, this flag is defaulted to that of item in the catalog, if exists, else it is defaulted to "N". The unit price for the order line. This table stores information regarding awards that are created out of the promotions. A single promotion can result in to multiple awards. The amount of discount that was applied as a part of this award. A flag indicating if the award is applied. A unique identifier for the award. The primary key of the YFS_PROMOTION_AWARD table. The type of award. If the award is denied, the reason for the denial. A description for the award. Reason this promotion was applied. This identifies the promotion that is added to this order. The promotion this award belongs to. This table stores information about Options associated with a Service Order Line The amount which has been invoiced Short Description for the Option added to the Item The unique identifier for the Option Item. Total amount for the line option. Unit Of Measure of the Option Item Primary key for YFS_ORDER_LINE_OPTION table. For future use. Option is currently priced based on ordering unit of measure. Quantity used for using this option This table stores the information about the work orders to be done at a node on an inventory item or a license plate. The quantity for which work order is completely confirmed. The quantity removed due to exceptions. The quantity for which the work order is created. The status of the work order. The primary key of the YFS_WORK_ORDER table. The work order number. Identifies a work order within the context of a node and enterprise Number of work orders generated for this order line. This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. The enterprise that is associated with this order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Generic table used to store instructions associated with various entities in the system Free-form text indicating any additional information related to the instruction type or otherwise. Categorization of instructions so that they can be grouped together for reference. For example, you may have instructions of type Pick, Pack, and Ship for an order. The URL relating to and/or containing the instructions. You could have an instruction exceeding the limits of a single record. Sequence number is used to provide a way to store a link between such instructions. Number of instructions. This table stores dynamic order references that can be passed to the createOrder API and returned by the getOrderDetails API. Database extensibility of the order tables should be used instead of this table to store implementation specific order fields. Name of the attribute. Value of the attribute. This table stores information about kitted component items. A kit is a collection of items that form a unit. For example, a home theatre system is a unit consisting of component items such as a DVD player, TV, CD player, etc.
Contains information about the quantities for a kit line in Transactional Unit Of Measure.
Component quantity. The number of components required to one kit. UOM on which all the transactional quantities are specified. Component quantity. Cross reference to the customer item. Customer item description. Department that deals with this item. Description for the item. The unique identifer for the component item. short description for the item. Weight of the item. Unit of measure of the ITEM_WEIGHT attribute. The number of components required to one kit. Component Product Class. Cross reference to the supplier ietm. Supplier item description. UPC code for the item. Unit cost of the component item. Component Unit Of Measure. Total number of kit lines fetched. This table stores information about the product items included in a stand-alone service line The unique identifier for the Product Item. The item ID, UOM and OrganizationCode form the unique item identifier for Product Item. Product item quantity Unit of measure of the product item. Generic table to store addresses attached with another entity This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. Identifies the type of address. Part of unique key The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Identifies the type of address. Part of unique key Primary key attribute of YFS_ENTITY_ADDRESS. Link to the entity table Link to the entity's parent table. Denormalized data to allow faster access of records for all addresses attached with the parent. In case of an order line address, this would store order header key Identifies the entity to which this address is attached to Link to YFS_PERSON_INFO table that stores the actual address Number of additional addresses applicable to this order line. This table stores custom and milestone dates for orders Actual Date It is a data attribute to store committed dates from supplier. The unique identifier for a date type for which additional dates are stored Expected Date Order header link Order line link If post release, link to the order release Requested Date This table stores the requested inventory attributes of an item on a order line . The Batch Number that has been specifed in the Order Line. Lot Attribute 1 used to specify the details of the lot. Lot Attribute 2 used to specify the details of the lot. Lot Attribute 3 used to specify the details of the lot. The Lot key reference that has been specifed in the Order Line. The Lot Number that has been specifed in the Order Line. The Lot manufacturing date that has been specifed in the Order Line. The Revision Number that has been specifed in the Order Line. The Tag number that uniquely identifies the Inventory attributes of the Item.
Describes the Sourcing Controls attached to a OrderLine.
If this attribute is populated, inventory availability for that node is overridden based on the value. The node for which either sourcing or procurement has been suppressed when either Suppress Sourcing or Suppress Procurement flags are set to Yes. Free-form reason text indicating any additional information. Flag determines whether to ignore this Node for procurement consideration. Node will not be used by scheduling as a procure from node. Flag determines whether to ignore this Node for sourcing consideration. Node will not be used by scheduling as a ship node. Generic table used to stores notes associated with various entities in the system The identifier of the order modification audit that caused this record. If the notes were entered because of customer contact by phone, the phone no can be stored in this column. If the contact is by email, email ID can be stored here. The time at which the customer contact occurred. The contact type like Phone call, email etc. The values will be selected from common code of code type "CONTACT_TYPE" The user who made the contact. The default value will the logged in user. The customer satisfaction level. Detailed Notes. Priority of the note. 1 is High, 0 is Low. The reason for which the notes are logged. Like "CustomerContact" etc. The values will be selected from common code of code type "NOTES_REASON" The sequence of the note. Transaction for which these notes are applicable. Specifies the name of the Transaction Number Of Notes This table stores reservations that are available for the order line. The batch number that has been specified on the reservation. The inventory demand type used by the reservation. This field is only used internally. For all user-created reservations, this will be defaulted from the document params. The reserved item. The lot number that has been specified on the reservation. The ship node at which the item has been reserved. The first date on which the reserved inventory is available. The reserved item's product class.
The quantity reserved.
 The date when the reserved inventory is needed, such as the shipping date. The revision number that has been specified on the reservation. The tag number that has been specified on the reservation. This field is calculated based on the tag identifiers. The reserved item's unit of measure. Specifies the unique identifiers of the bundle parent order line for this order line. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the service request details for the order line.
This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the service request details for the order line.
Contains information about the request details for which this delivery or service request is created.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the service request details for the order line.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the delivery request details for the order line.
Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the child relationships of the order lines.
Contains information about the parent order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the child order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. The child order line key of the relationship. The order header key of the related order lines. The primary key for the YFS_ORDER_LINE_RELATIONSHIP table. The parent order line key of the relationship. The type of relationship between order lines.
Contains information about the parent relationships of the order lines.
Contains information about the parent order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the child order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. The child order line key of the relationship. The order header key of the related order lines. The primary key for the YFS_ORDER_LINE_RELATIONSHIP table. The parent order line key of the relationship. The type of relationship between order lines. This table stores order line scheduling information for order lines. An order line can have multiple order line schedules. Any change in sourcing related attributes like ship node, reciving node, lot number etc. inserts a record into this table.
Contains information about the transaction quantity for the schedule.
Quantity. UOM on which all the transactional quantities are specified. The batch number that has been specified on the scheduled order line. The date the scheduled order line is expected to be delivered by. The date the scheduled order line is expected to ship by. The lot number that has been specified on the scheduled order line. The node that is used as either forwarding or merge location. The order header that is associated with this scheduled order line. The order line that is associated with this scheduled order line. The primary key for the YFS_ORDER_LINE_SCHEDULE table. The node from which the scheduled order line should be procured if it cannot be sourced from the ship node specified on the order line. Quantity. The node that will receive the scheduled order line, if applicable. The revision number that has been specified on the scheduled order line. The number of the scheduled order line. The date the scheduled order line should be shipped by. The ship node fulfilling this scheduled order line. The tag number that has been specified on the scheduled order line.
Contains information about the price and total amount details for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are invoiced for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are not invoiced for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are invoiced for the order line represented in Enterprise Currency.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are not invoiced for the order line represented in Enterprise Currency.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line. This table stores any additional charges or discounts that can be added to an order line. Charge amount. Link to YFS_CHARGE_CATEGORY. Link to YFS_CHARGE_NAME. Link to YFS_CHARGE_NAME table. Fixed charge amount for this order/invoice line. When the line charge is associated with an order line, this amount will be invoiced on the first invoice for this order line. Charge per unit for the item on this order/invoice line. Invoiced charge amount. Applicable only to charges for an Order line. This is the charge per line which has already been invoiced. Invoiced charge per unit. Describes if the charge is billable. Default: N Describes if the charge is discountable. Default: N Any additional reference related to this line charge. Remaining charge amount. Remaining charge per line. Remaining charge per unit. This table stores tax related information for various entities in the system. The charge category for which tax is being charged. For example, Labeling or Handling. Charge name for which tax is being charged. For example, Price Ticket. Link to YFS_CHARGE_NAME table. Tax amount invoiced. Reference 1 Reference 2 Reference 3 Remaining tax. The tax amount. Tax cannot be less than zero. The tax name. Percentage amount for tax calculation The amount of this tax which had been invoiced. The total amount of this tax. The amount of this tax that has not been invoiced. Tax name. This table stores status-quantity break up for each line-schedule. Similar to order lines, a kit line can be broken into multiple schedules
Contains information about the quantities for kit detail in Transactional Unit Of Measure.
Quantity. UOM on which all the transactional quantities are specified. Link to YFS_ORDER_KIT_LINE table. Quantity. Ship by date for the kit line. Tag number. Expected delivery date. Expected shipment date. Ship by date. Tag number. Quantity currently in this status. Total quantity which has ever been moved into this status. If there is a cyclic status (for example, backorder which can happen multiple times), this attribute does not provide useful information. UOM on which all the transactional quantities are specified. The order header that is associated with this order release status record. The order line that is associated with this order release status record. The order line schedule that this order release status record is associated with. The order release that is associated with this order release status record. The primary key for the YFS_ORDER_RELEASE_STATUS table. The pipeline that this release line belongs to. The node to which the order line is to be shipped. The node at which the order line will be fulfilled. This field indicates the status of the order release. The date when the last positive quantity was moved into this status. Description of the order line status. The quantity currently in this status. This field is not currently used. The total quantity to ever be moved into this status. If you have a cyclic status (for instance backorder, which can happen multiple times), this column will not provide useful information. The minimum order line quantity that must be fulfilled in an order release before it is shipped. Invoiced quantity on the order line. Total quantity that can be cancelled from the line. The quantity of the the line item that has been ordered. If part of line is cancelled, this number is reduced appropriately. If an order line is returned, this number is not reduced. Quantity which was ordered during order creation. This is not modified after order confirmation. Received quantity on the order line. Remaining quantity. Quantity which should be settled before it is actually invoiced. Shippped quantity on the order line. Quantity which has been split from this line due to substitutions, price negotiations etc. Quantity on the order line in the current status. Quantity which was over or under received. UOM on which all the transactional quantities are specified. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The table stores product information. The unique identifier for the item. The unit of measure for item quantity. The order line number. The sub line number. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The table stores product information. The unique identifier for the item. The unit of measure for item quantity. The order line number. The sub line number. This table stores contains all the hold types defined for an order This table stores the log notes when status of a hold type changes Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type log. Primary key for YFS_ORDER_HOLD_TYPE_LOG table. The reason text associates to this order hold type. This is the user who can approve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier for the transaction which applied the hold type on order . Transaction name which created the hold type. User who modified the record. Hold type. Timestamp when this hold type was added to the order. Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type. Primary Key of YFS_ORDER_HEADER. Order line link The reason text associates to the order hold type. This is the user who can resolve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier of the transaction which applied the hold type on order . Transaction name which created the hold type.
Only applicable for published data of Delete Order event, which can be raised by the deleteOrder API. Action = DELETE will be published to indicate that the order line will be deleted.
The date when this line will be allocated. This is calculated at order creation time, based on the node processing time. This field is not used from version 50 onwards. The ALLOCATION_LEAD_TIME field is used instead. The number of days it will take any node to ship the item after a ship advice is sent. It is defaulted from the Rule Set Field Name (YFS_RULES.LEAD_TIME). The release process will this value, or the scheduled node's lead time (setup at ship node level), whichever is greater. This field is not currently used. Displays a warning message if CannotScheduleBeforeDate or CannotScheduleAfterDate fields have a Non-Null value. The quantity avialable through modification rules for making a stop delivery request for this line. A flag to indicate if the order line is awaiting for a Delivery service association. Mark For Node as identified by the buyer for eg: it could be a person,store,DC Receiving node as identified by the buyer for eg:Store,DC Number this flag indicates whether the product line can be associated with service lines. The customers carrier account number. The carrier service code for this order line. The order header that is associated with this chained order line. If this line is chained from another order line, this key will point to the parent order line's header record. The order line that is associated with this chained order line. If this line is chained from another order line, this key will point to the parent order line. It is a data attribute to store the quantity that is committed by supplier. A user defined variable that can be used for condition building in process modeling. A user defined variable that can be used for condition building in process modeling. This field is used by Sterling Multi-Channel Selling Solution so that Visual Modeler can be opened with existing options. The buyer PO line number. The buyer's PO number. This field indicates who will pay the freight. Sterling Multi-Channel Fulfillment Solution understands values such as SUPPLIER, ENTERPRISE and MARKETPLACE to mean that each of these organizations will pay for the freight. You could however pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The delivery method for the product line. This field can be used for line classification and reporting purposes. This field indicates whether any order lines are dependant on the parent order line. This field can only be specified for the parent line. If this field is specified, it is defaulted on all of the dependant lines. This field is ignored if it is specified on a dependant line. The order line key that this order line is associated with. This field will indicate which order line is the parent of the the order line for line dependencies. The order header that is associated with this derived order line. If this line was derived from another order line, this key will point to the parent order line's header record. The order line that is associated with this derived order line. If this line was derived from another order line, this key will point to the parent order line. The order release that this derived order line is associated with. If this line was derived from another order line, this key will point to the parent order release record. the identifier of the distribution group that is used to determine the ship node(s) that will ship the order line. If not provided, the seller organization's default distribution rule ID is used. If provided, it must be a valid ID for the Seller organization. The minimum order line quantity that must be fulfilled in an order release before it is shipped. Indicates Freight Terms for the line. The method of fulfilling the order line during scheduling. This field can be matched with the corresponding field in the YFS_SOURCING_RULE_HDR table and the appropriate sourcing rule can be selected. Thie field indicates when inventory for the product line will be available. This flag indicates whether the order line is a gift item.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the line has associated delivery lines. Valid only for product lines.
Indicates if order line has lines derived from it.
Default: N
Valid Values: Y or N
Indicates if the line has associated service lines. Valid only for product lines. This attribute is not in use in prior to Sterling Supply Chain Applications 7.1. If you want to use deprecated functionality, set the rule 'Use deprecated hold Functionality'. If the rule is not set, this flag is set/reset by the application. Application sets this flag to 'Y' if order line has any hold types. Flag is reset to 'N' if there are no hold types on order line. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order line. This field is not currently used. The expiration date of the import license number. The import license number to be used. A flag to indicate if the order line should be backordered upon creation. If passed as 'Y', the line will be backordered even if inventory is available. This flag is ignored if reservation is mandatory. The total extended price which has already been invoiced. Invoiced quantity on the order line. Invoiced quantity on the order line. Indicates if Order line is bundle parent line or not.

Valid Values: Y or N
This flag indicates whether the pre-defined node on the line is firm. If IsFirmPredefinedNode is marked as N, then the node on the line is ignored during scheduling. If not passed, the value defaults to Y. This field indicates what kind of item is on the order line. The collection of items that form a unit. For example, a home theatre system is a unit consisting of kit components, such as a DVD player, TV, CD player, etc. The quantity that is used to compute ordered quantity for bundle component line. It can be specified only for bundle components. If specified ordered quantity will be set to KitQty*OrderedQty of the bundle parent. The order line sequence number. The line type. This field can be used in process modeling for pipeline determination, or for doing conditional processing for this line. Maximum order line status among all records that belong to an order. Description of maximum order line status among all records that belong to an order. The node where two or more order lines that are to be delivered together should be merged before the final delivery. This field is required when the DependancyShippingRule is set to '02'. Additionally this field will indicate forwarding location for zone skipping. Minimum order line status among all records that belong to an order. Description of minimum order line status among all records that belong to an order. The preferred minimum ship by date of the available supply that order line can allocate against. This only applies to the order line or kit line with time-sensitive item. If order line is in more than one status then this flag will be returned as "Y". Total quantity that can be cancelled from the line. The order header that this order line is associated with. The primary key for the YFS_ORDER_LINE table. The quantity of the line item that has been ordered. If part of the line is cancelled, this number is reduced appropriately. If an order line is returned, this number is not reduced. The line from which this line was created (split process). The quantity which was ordered at order creation. This is not modified after order confirmation. The sum of all the line level charges. The code indicating the type of packlist to be used for the line. Lines requiring different pack lists are not mixed in a single order release. This flag indicates whether this line is a parent of a dependency group. The code for personalization. This flag indicates whether this line needs personalization. This field is used internally. The pipeline that this order line belongs to. The order line number. The procurement node that is associated with this order line. The order line should be procured from that node if the products or services cannot be sourced from the shipnode specified on the order line. The promised end date of the appointment. The promised start date of the appointment. This field is passed out in the Tax calculation user exits. The receiving node that is associated with this order line. Remaining quantity. The requested cancel date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The requested delivery date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The requested ship date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The reservation ID. If this item was reserved before order creation, pass an ID to associate the line with the reservation. This flag indicates whether this line can be created without a reservation. If set to Y, creation of this line or any quantity addition to this line will be allowed only if the quantity can be reserved. If a ProcureFromNode is also present on the line, then the reservation will be carried out on the procure from node. The reservation identifier. If this item was reserved before order creation, pass an ID to associate the line with the reservation. The reason for returning the order line. Long description of the return reason code. Short description of the return reason code. The carrier to be used for this line. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. The reason for which schedule has failed on this order line. The segment of the inventory. The segment type of the inventory. The serial number of the item. The ship node that is associated with this order line. If provided, all releases will be made against this node. The ship to identifier. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. The ship to address that is associated with this order line. If not provided, it is defaulted from order header. This field is not currently used. It is a consolidation group id that is used as a standard do not mix constraint.Releases belonging to same shipment consolidation group may consolidate to same shipment This field is not currently used. The quantity which has been split from this line due to substitutions, price negotiations etc. Status description of the order line. Quantity on the order line in the current status. The sub line number. Substituted ItemID. This field is only populated if the item on the Order line is substituted.

Valid Values: Y or N
Substituted Item UOM. This field is only populated if the item on the Order line is substituted. The timezone in which the promised appointment has been recorded. The transaction discrepancy quantity.
Indicates if data is fetched from the history table rather than the regular table.
Default: N
Valid Values: Y or N
Number of Order Lines in the Order. Generic table used to store instructions associated with various entities in the system Free-form text indicating any additional information related to the instruction type or otherwise. Categorization of instructions so that they can be grouped together for reference. For example, you may have instructions of type Pick, Pack, and Ship for an order. The URL relating to and/or containing the instructions. You could have an instruction exceeding the limits of a single record. Sequence number is used to provide a way to store a link between such instructions. Number of instructions. Generic table used to stores notes associated with various entities in the system The identifier of the order modification audit that caused this record. If the notes were entered because of customer contact by phone, the phone no can be stored in this column. If the contact is by email, email ID can be stored here. The time at which the customer contact occurred. The contact type like Phone call, email etc. The values will be selected from common code of code type "CONTACT_TYPE" The user who made the contact. The default value will the logged in user. The customer satisfaction level. Detailed Notes. Priority of the note. 1 is High, 0 is Low. The reason for which the notes are logged. Like "CustomerContact" etc. The values will be selected from common code of code type "NOTES_REASON" The sequence of the note. Transaction for which these notes are applicable. Specifies the name of the Transaction Number Of Notes This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Generic table to store addresses attached with another entity This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. Identifies the type of address. Part of unique key The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Identifies the type of address. Part of unique key Primary key attribute of YFS_ENTITY_ADDRESS. Link to the entity table Link to the entity's parent table. Denormalized data to allow faster access of records for all addresses attached with the parent. In case of an order line address, this would store order header key Identifies the entity to which this address is attached to Link to YFS_PERSON_INFO table that stores the actual address The number of additional addresses associated with the order.
Currency of the Order
Currency of the Order's Enterprise
Date for which the conversion rate between currencies is used
Conversion rate between currencies
Total Amount
Total Charges in Enterprise currency
Total Discount in Enterprise currency
Grand total Tax Amount for the order in Enterprise currency
Grand total amount for the Order in Enterprise currency
Order Header Level Charges in Enterprise currency
Order Header Level Discount in Enterprise currency
Order Header Level Tax in Enterprise currency
Order Header Level Total amount in Enterprise currency
Sub Total amount for all the lines in Enterprise currency
Grand Charges in Enterprise currency Grand Discount in Enterprise currency Grand Tax in Enterprise currency Grand Total in Enterprise currency Header Charges in Enterprise currency Header Discount in Enterprise currency Header Tax in Enterprise currency Header Total in Enterprise currency Line Sub Total in Enterprise currency This table stores dynamic order references that can be passed to the createOrder API and returned by the getOrderDetails API. Database extensibility of the order tables should be used instead of this table to store implementation specific order fields. Name of the reference's name-value pair. Value assigned to the corresponding name. This table stores details about the customer's payment methods. The key to this table is posted in YFS_CHARGE_TRANSACTION table. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Awaiting charge amount on this payment method. Awaiting authorization amount on this payment method. The bill to address that is associated with this payment. Can be passed if different from the bill to address on the order. The sequence in which the payment method is to be used for charging. The cheque number. The cheque reference. The expiration date for the credit card. The credit card name. The credit card number. The credit card type group. The account number of the customer. The customer PO account number. The four digits of the credit card number that should be displayed. If not passed, it is defaulted to be the last four digits of the credit card number. The four digits of the customer account number that should be displayed. If not passed, it is defaulted to be the last four digits of the customer account number. The four digits of the payment reference 1 that should be displayed. If not passed, it is defaulted to be the last four digits of the payment reference 1. The four digits of the stored value card that should be displayed. If not passed, it is defaulted to be the last four digits of the stored value card number. The first name of the credit card holder.
The funds available to be charged on this payment method as determined by the GetFundsAvailable user exit, if it was invoked.
Indicates if the GetFundsAvailable user exit was invoked for this payment method.
 This flag indicates whether the payment type is incomplete. The last name of the credit card holder. The maximum amount that can be charged on this payment method. However, if UnlimitedCharges=Y, this amount will not be considered. The middle name of the credit card holder. The primary key for the YFS_PAYMENT table The payment reference 1. The payment reference 2. The payment reference 3. The payment type of this payment method. The total amount requested for authorization on this payment method. The total amount requested for charging on this payment method. Flag to indicate more charging has to be suspended. The stored value card number. The total amount auhorized on this payment method. The total amount charged on this payment method. The total refunded amount on this payment method. Indicates if there is a limit to the amount that can be charged on the payment method. If not passed, defaults to Y. This table stores information about financial transactions associated with order processing. Every action carried out on an order which may have an impact on financial components is logged in this table Stores detail about amount collected against the invoice Amount collected by the Invoice Collection for the linked Order Invoice. Timestamp when the record was created. Invoice number Classifies an invoice. For example, Orders, Returns, Debit Memo, Credit Memo, Info etc Not used internally. Can be updated externally by custom logic to group invoices together Link to invoice Link to a return release if invoice is created for a return Link to a shipment if invoice was created for a shipment Grand total for the invoice This table stores detailed information about authorizations and charges made against a credit card. This information would typcially be returned by credit card interface programs such as CyberSource or PaymentTek. The authorization amount. AVS Autorization code. The authorization code. The authorization return code. The authorization return flag. The authorization return message. The authorization time. The CVV authorization code. The charge transaction that is associated with this credit card transaction. The primary key for the CREDIT_CARD_TRANSACTION table. The internal return code. The internal return flag The internal return message. The parent key. The reference 1. The reference 2. Authorization request Id. The amount of the transaction. The time at which the transaction request was made. The return code for the transaction. The flag returned by the transaction. The message returned by the transaction. The transaction type. This table stores details about the customer's payment methods. The key to this table is posted in YFS_CHARGE_TRANSACTION table. The sequence in which the payment method is to be used for charging. The cheque number. The cheque reference. The expiration date for the credit card. The credit card name. The credit card number. The credit card type group. The account number of the customer. The customer PO account number. The four digits of the credit card number that should be displayed. If not passed, it is defaulted to be the last four digits of the credit card number. The four digits of the payment reference 1 that should be displayed. If not passed, it is defaulted to be the last four digits of the payment reference 1. The four digits of the stored value card that should be displayed. If not passed, it is defaulted to be the last four digits of the stored value card number. The first name of the credit card holder. This flag indicates whether the payment type is incomplete. The last name of the credit card holder. The maximum amount that can be charged on this payment method. However, if UnlimitedCharges=Y, this amount will not be considered. The middle name of the credit card holder. The primary key for the YFS_PAYMENT table The payment reference 1. The payment reference 2. The payment reference 3. The payment type of this payment method. The total amount requested for authorization on this payment method. The total amount requested for charging on this payment method. This field indicates whether further payment processing will be allowed on this payment method. If this value is set to 'Y', further payment processing will not be allowed on this payment method. The stored value card number. The amount that has been refunded to a new payment method based on this payment's payment type refund preferences. The total amount auhorized on this payment method. The total amount charged on this payment method. The total refunded amount on this payment method. Indicates if there is a limit to the amount that can be charged on the payment method. If not passed, defaults to Y.
The order to which these funds were transferred. This information is only valid for charge transactions where ChargeType is TRANSFER_OUT
The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
The order from which these funds were transferred. This information is only valid for charge transactions where ChargeType is TRANSFER_IN.
The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
The identifier of the order modification audit that caused this record. The date and time until which the authorization specified by the authorization ID is applicable. For authorization requests, this field holds the identifier of the authorization that was made. For charge requests, this field holds the authroization ID to be used for charging the amount. The amount that could be charged to the buyer if the order was fulfilled. At the time of fulfillment, a negative entry is made in this column and positive entry in the DEBIT_AMOUNT column. The primary key for the YFS_CHARGE_TRANSACTION table. The type of charge that is being applied to the order. The date and time when the charge was realized. The amount that was actually charged or refunded to the buyer. The amount that should be charged or refunded to the buyer. This field is used internally by the application to keep track of the amount which has been posted in the invoices as "collected". The date and time when the charge request was processed. This flag indicates whether the request was created for a precharge or a payment method whose payment type has the ChargeInsteadOfAuth flag turned on. The amount that is authorized for the order. The order header that is associated with this charge transaction. The key to the invoice that was created for this record, if applicable. Invoices are created for shipments, returns, or debit and credit memos. The payment method that is associated with this charge transaction. The amount that is requested for the charge or authorization of record of types "REQUEST_CHARGE" and "REQUEST_AUTHORIZATION". Once the request is processed, the actual amount will be shown as "CreditAmount" or "OpenAuthorizedAmount", for charge and authorization requests respectively. This field holds the amount for which a pre-settlement (settlement before invoice) is requested. Charge requests will be created for this amount. This field indicates the status of this record. The reason code for the current status of a charge transaction. Transaction Date. The Order Header Key of the order that funds are being transferred from. The Order Header Key of the order that funds are being transferred to. The user exit call status of this record. The status will be "INVOKED" if the transaction fails during or after the user exit call, otherwise the value will be blank. Total Credits Total Debits Total Open Authorizations Total Open Bookings Total amount of funds transferred in from other orders. Total amount of funds transferred out to other orders. This table stores custom and milestone dates for orders Actual Date It is a data attribute to store committed dates from supplier. The unique identifier for a date type for which additional dates are stored Expected Date Order header link Order line link If post release, link to the order release Requested Date This table stores information about Order Product and Service Associations This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated product line. Prime line number of the associated product line. Sub line number of the associated product line. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated service line. Prime line number of the associated service line. Sub line number of the associated service line. Flag to indicate whether to hold schedule till completion Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours This table stores relationship between order lines. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated product line. Prime line number of the associated product line. Sub line number of the associated product line. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. Order line key of the associated service line. Prime line number of the associated service line. Sub line number of the associated service line. The type of relationship between order lines. This table stores information regarding promotions that are associated to an order or any of its lines. If the promotion is denied, the reason for the denial Description of the promotion A flag indicating if the promotion is applied This identifies the promotion that is added to this order. The primary key of the YFS_PROMOTION table. The type of promotion. Like DISCOUNT, BOGO. This table stores information regarding awards that are created out of the promotions. A single promotion can result in to multiple awards. The amount of discount that was applied as a part of this award. A flag indicating if the award is applied. A unique identifier for the award. The primary key of the YFS_PROMOTION_AWARD table. The type of award. If the award is denied, the reason for the denial. A description for the award. Reason this promotion was applied. This identifies the promotion that is added to this order. The promotion this award belongs to. This table stores special services supported by various carriers that can be used when shipping packages. Examples of special services are signature required upon delivery of the package, Saturday pick-up and Saturday delivery. This table stores the special services supported by Carriers.
The code identifying the Special Service to be performed on the Order. SpecialServicesCode must be defined in the configuration
This table stores contains all the hold types defined for an order This table stores the log notes when status of a hold type changes Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type log. Primary key for YFS_ORDER_HOLD_TYPE_LOG table. The reason text associates to this order hold type. This is the user who can approve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier for the transaction which applied the hold type on order . Transaction name which created the hold type. User who modified the record. Hold type. Timestamp when this hold type was added to the order. Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type. Primary Key of YFS_ORDER_HEADER. Order line link The reason text associates to the order hold type. This is the user who can resolve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier of the transaction which applied the hold type on order . Transaction name which created the hold type. Stores the relationship between a set of answers and the entities which provided these answers. Stores each answer for an answer set. The answer set for this answer. Primary key of answer tran. The answer for the question. Identifier for the question that this answer is for. Number of answer sets in the Order. Primary key of answer set tran. The person info record this answer set is stored for. The name of the table which stores the record of the primary owner of this answer set. The key for the primary owner of this answer set.
The question type that this answer set is for.
 Number of answer sets in the Order.
Contains information about the price and total amount details for the order line.
Total Charges
Total Discount
Grand total Tax Amount for the order
Grand total amount for the Order
Order Header Level Charges
Order Header Level Discount
Order Header Level Tax
Order Header Level Total amount
Sub Total amount for all the lines
Grand Charges Grand Discount Grand Tax Grand Total Header Charges Header Discount Header Tax Header Total Line Sub Total
Contains information about the price and total amount details that are not invoiced for the order.
Grand Charges Grand Discount Grand Tax Grand Total Header Charges Header Discount Header Tax Header Total Line Sub Total This table stores charges that are applied at the header level. The amount of the charge. The charge category. For example, Labeling or Handling. The name of the charge. For example, Price Ticket. Primary key for a charge name. Applicable only to charges for an Order. This is the amount which has already been invoiced. Describes if the charge is billable. Default: N Describes if the charge is discountable. Default: N Reference information about this charge. Remaining Charge Amount This table stores tax related information for various entities in the system. The charge category for which tax is being charged. For example, Labeling or Handling. Charge name for which tax is being charged. For example, Price Ticket. Primary key for a charge name. Tax amount invoiced. Reference 1 Reference 2 Reference 3 Remaining Tax The tax amount. Tax cannot be less than zero. The tax name. Percentage amount for tax calculation This flag indicates if a charge can be taxed. The amount of this tax which had been invoiced. The total amount of this tax. The amount of this tax that has not been invoiced. Tax name. This table stores status-quantity break up for each line-schedule. Similar to order lines, a kit line can be broken into multiple schedules Quantity. UOM on which all the transactional quantities are specified. Link to YFS_ORDER_KIT_LINE table. Quantity. Ship by date for the kit line. Tag number. The date the scheduled order line is expected to be delivered by. The date the scheduled order line is expected to ship by. The node that will receive the scheduled order line, if applicable. The date the scheduled order line should be shipped by. The ship node fulfilling this scheduled order line. The tag number that has been specified on the scheduled order line. Quantity currently in this status. Total quantity has ever been moved into this status. If there is a cyclic status (for example, backorder which can happen multiple times), this column does not provide useful information. UOM on which all the transactional quantities are specified. The order header that is associated with this order release status record. The order line that is associated with this order release status record. The order line schedule that this order release status record is associated with. The order release that is associated with this order release status record. The primary key for the YFS_ORDER_RELEASE_STATUS table. The pipeline that this release line belongs to. The node that will receive the scheduled order line, if applicable. The ship node fulfilling this scheduled order line. This field indicates the status of the order release. The date when the last positive quantity was moved into this status. Description of the order status. The quantity currently in this status. This field is not currently used. The total quantity to ever be moved into this status. If you have a cyclic status (for instance backorder, which can happen multiple times), this column will not provide useful information. A return order for which this exchange order was created. This information is only valid for exchange orders. The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
An exchange order created for this return order. This information is only valid for return orders. The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order has any hold types or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores information regarding a stop delivery request for an order. This table stores information regarding a stop delivery request's detail.
Contains information about the quantities for a stop delivery detail in Transactional Unit Of Measure.
The requested quantity in the transactional UOM for this stop delivery request detail. The successful quantity in the transactional UOM for this stop delivery request detail. UOM on which all the transactional quantities are specified. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Comments made in regards to this Stop Delivery Request Detail. The quantity requested to stop delivery. The primary key for the YFS_STOP_DEL_REQ_DTL table. The quantity that was successfully stopped. The total number of StopDeliveryRequestDetail elements returned. Comments made in regards to this Stop Delivery Request. The date and time the stop request was made. The primary key for the YFS_STOP_DEL_REQ_HDR table. The ID for this stop delivery request. The total number of StopDeliveryRequest elements returned.
Only applicable for published data of Delete Order event, which can be raised by the deleteOrder API. Action = DELETE will be published to indicate that the order will be deleted.
The identifier of the scheduling rule to be used while checking inventory availability. If not passed, the allocation rule with the ID 'SYSTEM' for the enterprise is used. If the allocation rule with the ID 'SYSTEM' is not found, the allocation rule with the ID 'SYSTEM' for the enterprise 'DEFAULT' is used. The smallest expiration date of currently valid expirations. This field is used by Sterling Multi-Channel Fulfillment Solution payment processing agents. Any transaction having a financial implication will set this date to current system date. This field is used as a trigger by payment processing agents to create charge and authorization reqeusts. The date on which the order will automatically be cancelled. If not provided, it is defaulted as null on order creation. This date can be set or reset at any point in time by calling changeorder API. The identifier of the bill to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the BillToID can represent the CustomerID of the customer. Otherwise, the BillToID can represent the PersonID of the bill to address or the BuyerOrganizationCode of the buyer organization. The bill to address that is associated with this order. Mark For Node as identified by the buyer for eg: it could be a person,store,DC The buyer organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. Receiving node as identified by the buyer for eg:Store,DC Number This is the User Id of the customer for which order is created. This field maps to User_Id field of YFS_Customer_Contact. This flag indicates whether the order needs to be cancelled in case of inventory shortage. If not specified, most restrictive rule will be used from customer preference or scheduling rule. The account number of the customer with the carrier. The carrier service code for this order. Specifies the chaining type of the order. This flag indicates whether the actual freight charges should be passed on to the customer. If set to 'Y', invoicing picks up charges from shipments and uses that to invoice the customer. This flag indicates whether the order was created by a node. This field is used during blind return creation at the nodes. Timestamp when the record was created. User who created the record. The PO number of the customer's customer. In some situations, this may need to be printed on the actual packaging. The E-mail ID of the customer. The PO number of the customer. For purchase orders, this can be used for storing the purchase order number of the purchasing system if that number is not already stored as part of the order number. This flag indicates whether this order is to be used as the default template. For this order to be used as a default template, the document type of the order being created should be configured to set the template document type as this orders document type. The organization that pays the freight charges. For example, SUPPLIER, ENTERPRISE, and MARKETPLACE. However, you could pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. This field can be used for order classification and reporting purposes. The order classification attribute. This field can be used for reporting purposes. Sterling Multi-Channel Fulfillment Solution has no logic based on this field. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. This flag indicates whether the order is yet to be confirmed. Order lines can only be deleted from the system in draft stage. Date used to driver order processing. '01' represents ReqShipDate, '02' represents ReqDeliveryDate. The system or sales person who created the order. The enterprise that is associated with this order. The channel through which this order was created. This field indicates the exchange type of the order. The payment processing logic is dependent on this attribute. Indicates Freight Terms for the order.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the order has any delivery lines.
Default: N
Valid Values: Y or N
This flag indicates whether the order has any derived children. This flag indicates whether the order has any derived parent.
Indicates if the order has any product lines.
Default: N
Valid Values: Y or N
Indicates if the order has any service lines.
Default: N
Valid Values: Y or N
This attribute is deprecated as of Sterling Supply Chain Applications 7.1. If you want to use pre 7.1 functionality, set the rule 'Use pre 7.1 hold Functionality'. If it is used pre 7.1 mode, it will indicate if order is on hold. If order is on hold, default configuration will stop the shceduling and release process for the order. If the rule is not set, this flag is set/reset by the application. Application sets HoldFlag to 'Y' if order or any order line has any hold types. Flag is reset to 'N' if there are no hold types on order and on all order lines. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order.
Default: N
Valid Values: Y or N
The reason code for putting the order on hold. This flag indicates whether the complete line needs to be shipped. If not specified, most restrictive rule will be used from customer preference or scheduling rule. This flag indicates whether the complete order line needs to be shipped from a single ship node. If not specified, most restrictive rule will be used from customer preference or scheduling rule. This flag indicates whether the complete order needs to be shipped. If not specified, most restrictive rule will be used from customer preference or scheduling rule. This flag indicates whether the complete order needs to be shipped from a single ship node. If not specified, most restrictive rule will be used from customer preference or scheduling rule. Maximum order status based on all records that belong to an order. Description of maximum order status based on all records that belong to an order. Minimum order status based on all records that belong to an order. Description of minimum order status based on all records that belong to an order. Timestamp when the record was last modified. User who modified the record. If order is in more than one status then this flag will be returned as "Y". This field provides details on notifications based on the notification type. For example, for notification type 'e-mail' this would be the e-mail address. This field is not used within the application. This field is not used within the application. It is published with events so that external decisions can be made based on it. This field is not currently used This field indicates what scheduling will first optimize on. If not specified scheduling rule will be used to determine optimization type. This flag indicates whether the order has reached the end of its processing lifecycle. The date on which the order was taken. If not passed during order creation, it is defaulted to current system date. The primary key for the YFS_ORDER_HEADER table. The name given to the order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This indicates what, if any, specific purpose this order was created for. The only valid value is 'EXCHANGE' which means the order is created for exchange purpose. But, the system may create an order with OrderPurpose of REFUND for internal use. The order classification attribute. This field can be used for reporting purposes or to build conditions for modeling your business process. Sterling Multi-Channel Fulfillment Solution has no default logic based on this field. This field is used by Sterling Multi-Channel Selling Solution. Total tax amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The total amount at the time of the order creation. This field is not updated later in the cycle and can be used to track changes made since the order creation. The sum of the other charges at the header level. The payment rule that is associated with this order. All decisions on payment handling are controlled by this rule. The information about the payment status of the order. The amount of funds available for the exchange order. This is the same as the total order amount of the return order. The code that describes the personalization required for the order. The price program that is associated with this order. This field is used by Sterling Multi-Channel Selling Solution. The priority code of the order. External logic can be built for prioritizing orders. The numeric priority code as opposed to alphanumeric field PRIORITY_CODE. The date that this order should be purged from the history table. If set, this date will override the date determined based on the History Purge Lead Days. This field is passed out in the tax calculation user exits. The node an order is to be shipped to. The requested cancel date. If this date is in the future, the order will be scheduled only up to this date. If this date is in the past, the order can be scheduled for shipping today as long as it has not been cancelled already. The order line level cancel date overrides this attribute. The requested delivery date. This date is stamped on order lines (as requested delivery date) during order creation if no requested delivery date was passed at the order line level. The date the customer has requested the order to be shipped on. Based on the 'Driver Date' parameter of the document type, the ship date or delivery date will be calculated based on transit time calculations (if not passed at order creation). This flag indicates whether the return was initiated by the gift recipient. This field is only used by return orders. The return order header key for which this exchange order was created. The carrier assigned to the order. This flag indicates whether the sale transaction has been voided. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. This field is provided for allowing custom searches. You can decide at implementation time what should be stored in this field. The seller organization that is associated with this order. This must be a valid organization defined in Sterling Multi-Channel Fulfillment Solution. The ship node at which this order will be fulfilled. The identifier of the ship to customer. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. The ship to address that is associated with this order. This field is used by Sterling Multi-Channel Selling Solution. This field is used by Sterling Multi-Channel Selling Solution. This field is used by Sterling Multi-Channel Selling Solution. This attribute will be used to determine node for sourcing. Status description of the order. This flag indicates whether the buyer is extempt from paying taxes. The buyer's tax exemption certificate. The tax jurisdiction of the buyer. The identifier of the buyer. Indicates a team that can manage this order. Default is Null. The terms code of the order. This is passed on to the invoice and published with the invoice. the sum of all the credit and debit memos issued against this order. The seller's vendor identifier, as defined by the buyer.
Indicates if data should be retrieved from the history table rather than the regular table.
Default: N
Valid Values: Y or N
This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. This table stores description in different languages. A localized description. An extended localized description. Locale for which the extended description is stored. Short description. This field indicates the alternate ItemID, which can be passed instead of the actual ItemID. This is an alias for the ItemID. The currency in which the unit cost is specified. The country of origin being requested. Indicates if credit has been issued upon receipt of the returned goods. The item ID for the buyer. The item description of the buyer organization. The Export Commodity Control Number for a commodity contained in the shipment, as indicated on the Waybill. The harmonized code, if applicable. The ISBN number, if applicable. Is the line returnable. The description of the item. The identifier for the item. The ITEM_ID, UOM, and PRODUCT_CLASS form the unique inventory identifier for an order line. The ITEM_ID, UOM and ORGANIZATION_CODE form the unique item identifier for the Product Management module. The short description of the item. The weight of the item. The unit of measure used for weight. The item identifier for the manufacturer. The item description for the manufacturer. The name of the manufacturer. The National Motor Freight Classification - A way of classifying goods for the purposes of transportation. The National Motor Freight Classification - A way of classifying goods for the purposes of transportation. The description of the NMFC. National Motor Freight Classification is a way of classifying goods for the purposes of transportation. The product class. This field is used as an inventory identifier. The product line for the item Number of days within which the item must be returned for it to be accepted as a return on the system. The Schedule B commodity codes - A 10-digit numeric codes used to identify products that are exported to other countries. The item ID of the supplier (if this is a PO or the line is being drop-shipped and the supplier is known upfront). The item description of the supplier (if this is a PO or line is being drop-shipped and the supplier is known upfront). The product code classification for the purposes of taxation. The UPC Code of the item. The unit cost of the item. The unit of measure.
Contains information about order line pricing and quantity details.
The actual pricing quantity Sum of line totals of all the bundle components. Components having price for information purposes are ignored from this calculation. The discount percentage used to arrive at the unit price. This field is assumed to be applied on the list price. This field is also only informational, and not used by the application. The total invoiced amount for the line. The invoiced pricing quantity. This flag indicates whether price information passed on the line is for information only. If it is 'Y' then line total will not be considered in order total. Invoiced amount for such lines will always be 0. If it is not passed or passed as 'N' then line price is considered in order total. Pass 'Y' in this field to use the price program's prices. The grand total for the line. the list price of the item. This is an informational field. The pricing quantity. The pricing quantity conversion factor. This field is used for finding Pricing_Quantity, using Ordered_Quantity. The pricing UOM for the order line. If "PricingUOM" is not passed it will be defaulted from Catalog. If "PricingUOM" is passed and different from inventory uom, "PricingQtyConversionFactor" attribute will be used for pricing quantity conversion. If "PricingQtyConversionFactor" is not passed it will be considered as zero. Represents the quantity that can be used for pricing the item. Typically, the price programs are based on the total purchase quantity. But if some quantity is cancelled because of inventory shortage (non customer fault), the pricing quantity (which is based on the ordered quantity) changes, but repricing_quantity is not changed. The retail price of the item. this is an informational field. The amount which should be settled before it is actually invoiced. The quantity which should be settled before it is actually invoiced. The Tax Exemption Certificate applied to this order line. This flag indicates whether this order line is taxable or not. This field is for informational purposes only. Currently, it is not used in any tax calculations. If not passed, this flag is defaulted to that of item in the catalog, if exists, else it is defaulted to "N". The unit price for the order line. This table stores information regarding awards that are created out of the promotions. A single promotion can result in to multiple awards. The amount of discount that was applied as a part of this award. A flag indicating if the award is applied. A unique identifier for the award. The primary key of the YFS_PROMOTION_AWARD table. The type of award. If the award is denied, the reason for the denial. A description for the award. Reason this promotion was applied. This identifies the promotion that is added to this order. The promotion this award belongs to. This table stores information about Options associated with a Service Order Line The amount which has been invoiced Short Description for the Option added to the Item The unique identifier for the Option Item. Total amount for the line option. Unit Of Measure of the Option Item Primary key for YFS_ORDER_LINE_OPTION table. For future use. Option is currently priced based on ordering unit of measure. Quantity used for using this option This table stores the information about the work orders to be done at a node on an inventory item or a license plate. The quantity for which work order is completely confirmed. The quantity removed due to exceptions. The quantity for which the work order is created. The status of the work order. The primary key of the YFS_WORK_ORDER table. The work order number. Identifies a work order within the context of a node and enterprise Number of work orders generated for this order line. This table stores all order documents in the system. These orders can be further classified into various types of documents. For example, ORDERS, PLANNED ORDERS and any other future types that Sterling Multi-Channel Fulfillment Solution may provide. The document type that is associated with this order. For example, Sales Order document (0001), Planned Order document (0002), Return Order document (0003) , and Purchase Order document (0005). This field determines the order's fulfillment cycle and controls the inventory and payment updates performed on the order. The enterprise that is associated with this order. The number of the order, which can be passed during order creation or generated based on a system rule setting. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Generic table used to store instructions associated with various entities in the system Free-form text indicating any additional information related to the instruction type or otherwise. Categorization of instructions so that they can be grouped together for reference. For example, you may have instructions of type Pick, Pack, and Ship for an order. The URL relating to and/or containing the instructions. You could have an instruction exceeding the limits of a single record. Sequence number is used to provide a way to store a link between such instructions. Number of instructions. This table stores dynamic order references that can be passed to the createOrder API and returned by the getOrderDetails API. Database extensibility of the order tables should be used instead of this table to store implementation specific order fields. Name of the attribute. Value of the attribute. This table stores information about kitted component items. A kit is a collection of items that form a unit. For example, a home theatre system is a unit consisting of component items such as a DVD player, TV, CD player, etc.
Contains information about the quantities for a kit line in Transactional Unit Of Measure.
Component quantity. The number of components required to one kit. UOM on which all the transactional quantities are specified. Component quantity. Cross reference to the customer item. Customer item description. Department that deals with this item. Description for the item. The unique identifer for the component item. short description for the item. Weight of the item. Unit of measure of the ITEM_WEIGHT attribute. The number of components required to one kit. Component Product Class. Cross reference to the supplier ietm. Supplier item description. UPC code for the item. Unit cost of the component item. Component Unit Of Measure. Total number of kit lines fetched. This table stores information about the product items included in a stand-alone service line The unique identifier for the Product Item. The item ID, UOM and OrganizationCode form the unique item identifier for Product Item. Product item quantity Unit of measure of the product item. Generic table to store addresses attached with another entity This table stores relevant personal information and addresses. Addresses are typically organization address, ship node address, customer address, and so forth. Personal information is required in cases where person to person contact needs to be established; for example, taking appointments or speaking during negotiations. The key of this table is posted in various tables to allow access to people and address information The address line 1 field. The address line 2 field. The address line 3 field. The address line 4 field. The address line 5 field. The address line 6 field. Identifies the type of address. Part of unique key The alternate email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The beeper number at which the person or a predesignated employee of the organization referred to in the address can be called. The city in the address. The company this person is associated with. The country in the address. The day time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The day time phone at which the person or organization referred to in the address can be called. The primary department in charge of procurement. The email address at which the person or a predesignated employee of the organization referred to in the address can be contacted. The evening time fax at which the person or a predesignated employee of the organization referred to in the address can be notified. The evening time phone at which the person or organization referred to in the address can be called. The first name of the person. Indicates whether the address is commercial, residential or none. Values of this field can be Y -Commercial address.N - Residential address. undefined for Null. The job title of the person. The last name of the person. The middle name of the person. The mobile phone at which the person or a predesignated employee of the organization referred to in the address can be called. The alternate phone number at which the person or a predesignated employee of the organization referred to in the address can be called. The unique identifier for a person. The primary key for the YFS_PERSON_INFO table. The state in the address. The suffix for a person, such as Jr., or Sr. The tax geo code for this location. Intended for future use. The title for the person such as Ms., Mr., or Dr.. The zip code in the address. Identifies the type of address. Part of unique key Primary key attribute of YFS_ENTITY_ADDRESS. Link to the entity table Link to the entity's parent table. Denormalized data to allow faster access of records for all addresses attached with the parent. In case of an order line address, this would store order header key Identifies the entity to which this address is attached to Link to YFS_PERSON_INFO table that stores the actual address Number of additional addresses applicable to this order line. This table stores custom and milestone dates for orders Actual Date It is a data attribute to store committed dates from supplier. The unique identifier for a date type for which additional dates are stored Expected Date Order header link Order line link If post release, link to the order release Requested Date This table stores the requested inventory attributes of an item on a order line . The Batch Number that has been specifed in the Order Line. Lot Attribute 1 used to specify the details of the lot. Lot Attribute 2 used to specify the details of the lot. Lot Attribute 3 used to specify the details of the lot. The Lot key reference that has been specifed in the Order Line. The Lot Number that has been specifed in the Order Line. The Lot manufacturing date that has been specifed in the Order Line. The Revision Number that has been specifed in the Order Line. The Tag number that uniquely identifies the Inventory attributes of the Item.
Describes the Sourcing Controls attached to a OrderLine.
If this attribute is populated, inventory availability for that node is overridden based on the value. The node for which either sourcing or procurement has been suppressed when either Suppress Sourcing or Suppress Procurement flags are set to Yes. Free-form reason text indicating any additional information. Flag determines whether to ignore this Node for procurement consideration. Node will not be used by scheduling as a procure from node. Flag determines whether to ignore this Node for sourcing consideration. Node will not be used by scheduling as a ship node. Generic table used to stores notes associated with various entities in the system The identifier of the order modification audit that caused this record. If the notes were entered because of customer contact by phone, the phone no can be stored in this column. If the contact is by email, email ID can be stored here. The time at which the customer contact occurred. The contact type like Phone call, email etc. The values will be selected from common code of code type "CONTACT_TYPE" The user who made the contact. The default value will the logged in user. The customer satisfaction level. Detailed Notes. Priority of the note. 1 is High, 0 is Low. The reason for which the notes are logged. Like "CustomerContact" etc. The values will be selected from common code of code type "NOTES_REASON" The sequence of the note. Transaction for which these notes are applicable. Specifies the name of the Transaction Number Of Notes This table stores reservations that are available for the order line. The batch number that has been specified on the reservation. The inventory demand type used by the reservation. This field is only used internally. For all user-created reservations, this will be defaulted from the document params. The reserved item. The lot number that has been specified on the reservation. The ship node at which the item has been reserved. The first date on which the reserved inventory is available. The reserved item's product class.
The quantity reserved.
 The date when the reserved inventory is needed, such as the shipping date. The revision number that has been specified on the reservation. The tag number that has been specified on the reservation. This field is calculated based on the tag identifiers. The reserved item's unit of measure. Specifies the unique identifiers of the bundle parent order line for this order line. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the service request details for the order line.
This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the service request details for the order line.
Contains information about the request details for which this delivery or service request is created.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the service request details for the order line.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the delivery request details for the order line.
Flag to indicate whether to hold schedule till completion header Key of the Order for which Association is defined Primary key for YFS_ORDER_PROD_SER_ASSOC table. Quantity used for using this option Quantity used for using this option Product quantity for which service quantity is stored in ServiceQuantity attribute Service Capacity to be used for delivering (or servicing )product quantity mentioned Specifies the service time offset between services in Hours
Contains information about the child relationships of the order lines.
Contains information about the parent order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the child order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. The child order line key of the relationship. The order header key of the related order lines. The primary key for the YFS_ORDER_LINE_RELATIONSHIP table. The parent order line key of the relationship. The type of relationship between order lines.
Contains information about the parent relationships of the order lines.
Contains information about the parent order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number.
Contains information about the child order line for the relationship.
The primary key for the YFS_ORDER_LINE table. The order line number. The sub line number. The child order line key of the relationship. The order header key of the related order lines. The primary key for the YFS_ORDER_LINE_RELATIONSHIP table. The parent order line key of the relationship. The type of relationship between order lines. This table stores order line scheduling information for order lines. An order line can have multiple order line schedules. Any change in sourcing related attributes like ship node, reciving node, lot number etc. inserts a record into this table.
Contains information about the transaction quantity for the schedule.
Quantity. UOM on which all the transactional quantities are specified. The batch number that has been specified on the scheduled order line. The date the scheduled order line is expected to be delivered by. The date the scheduled order line is expected to ship by. The lot number that has been specified on the scheduled order line. The node that is used as either forwarding or merge location. The order header that is associated with this scheduled order line. The order line that is associated with this scheduled order line. The primary key for the YFS_ORDER_LINE_SCHEDULE table. The node from which the scheduled order line should be procured if it cannot be sourced from the ship node specified on the order line. Quantity. The node that will receive the scheduled order line, if applicable. The revision number that has been specified on the scheduled order line. The number of the scheduled order line. The date the scheduled order line should be shipped by. The ship node fulfilling this scheduled order line. The tag number that has been specified on the scheduled order line.
Contains information about the price and total amount details for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are invoiced for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are not invoiced for the order line.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are invoiced for the order line represented in Enterprise Currency.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line.
Contains information about the price and total amount details that are not invoiced for the order line represented in Enterprise Currency.
The amount of the charges for this line. The total of the discount amounts. The price for this line before taxes, charges, and discounts are accounted for. The total amount for this line. The total option price for this line. The quantity used to calculate the extended price. The amount of taxes for this line. The price for one unit of this line. This table stores any additional charges or discounts that can be added to an order line. Charge amount. Link to YFS_CHARGE_CATEGORY. Link to YFS_CHARGE_NAME. Link to YFS_CHARGE_NAME table. Fixed charge amount for this order/invoice line. When the line charge is associated with an order line, this amount will be invoiced on the first invoice for this order line. Charge per unit for the item on this order/invoice line. Invoiced charge amount. Applicable only to charges for an Order line. This is the charge per line which has already been invoiced. Invoiced charge per unit. Describes if the charge is billable. Default: N Describes if the charge is discountable. Default: N Any additional reference related to this line charge. Remaining charge amount. Remaining charge per line. Remaining charge per unit. This table stores tax related information for various entities in the system. The charge category for which tax is being charged. For example, Labeling or Handling. Charge name for which tax is being charged. For example, Price Ticket. Link to YFS_CHARGE_NAME table. Tax amount invoiced. Reference 1 Reference 2 Reference 3 Remaining tax. The tax amount. Tax cannot be less than zero. The tax name. Percentage amount for tax calculation The amount of this tax which had been invoiced. The total amount of this tax. The amount of this tax that has not been invoiced. Tax name. This table stores status-quantity break up for each line-schedule. Similar to order lines, a kit line can be broken into multiple schedules
Contains information about the quantities for kit detail in Transactional Unit Of Measure.
Quantity. UOM on which all the transactional quantities are specified. Link to YFS_ORDER_KIT_LINE table. Quantity. Ship by date for the kit line. Tag number. Expected delivery date. Expected shipment date. Ship by date. Tag number. Quantity currently in this status. Total quantity which has ever been moved into this status. If there is a cyclic status (for example, backorder which can happen multiple times), this attribute does not provide useful information. UOM on which all the transactional quantities are specified. The order header that is associated with this order release status record. The order line that is associated with this order release status record. The order line schedule that this order release status record is associated with. The order release that is associated with this order release status record. The primary key for the YFS_ORDER_RELEASE_STATUS table. The pipeline that this release line belongs to. The node to which the order line is to be shipped. The node at which the order line will be fulfilled. This field indicates the status of the order release. The date when the last positive quantity was moved into this status. Description of the order line status. The quantity currently in this status. This field is not currently used. The total quantity to ever be moved into this status. If you have a cyclic status (for instance backorder, which can happen multiple times), this column will not provide useful information. The minimum order line quantity that must be fulfilled in an order release before it is shipped. Invoiced quantity on the order line. Total quantity that can be cancelled from the line. The quantity of the the line item that has been ordered. If part of line is cancelled, this number is reduced appropriately. If an order line is returned, this number is not reduced. Quantity which was ordered during order creation. This is not modified after order confirmation. Received quantity on the order line. Remaining quantity. Quantity which should be settled before it is actually invoiced. Shippped quantity on the order line. Quantity which has been split from this line due to substitutions, price negotiations etc. Quantity on the order line in the current status. Quantity which was over or under received. UOM on which all the transactional quantities are specified. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The table stores product information. The unique identifier for the item. The unit of measure for item quantity. The order line number. The sub line number. This table stores order line information, including item details and shipping information. Multiple lines can be created for a single order defined in the YFS_ORDER_HEADER table. The table stores product information. The unique identifier for the item. The unit of measure for item quantity. The order line number. The sub line number. This table stores contains all the hold types defined for an order This table stores the log notes when status of a hold type changes Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type log. Primary key for YFS_ORDER_HOLD_TYPE_LOG table. The reason text associates to this order hold type. This is the user who can approve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier for the transaction which applied the hold type on order . Transaction name which created the hold type. User who modified the record. Hold type. Timestamp when this hold type was added to the order. Primary key for YFS_ORDER_AUDIT table. This can be used to view the modification types that would have added this hold type. Primary Key of YFS_ORDER_HEADER. Order line link The reason text associates to the order hold type. This is the user who can resolve or reject this hold. This field maps to User_Id field of YFS_Customer_Contact. Status of the order hold type. Description of hold type status. The unique identifier of the transaction which applied the hold type on order . Transaction name which created the hold type.
Only applicable for published data of Delete Order event, which can be raised by the deleteOrder API. Action = DELETE will be published to indicate that the order line will be deleted.
The date when this line will be allocated. This is calculated at order creation time, based on the node processing time. This field is not used from version 50 onwards. The ALLOCATION_LEAD_TIME field is used instead. The number of days it will take any node to ship the item after a ship advice is sent. It is defaulted from the Rule Set Field Name (YFS_RULES.LEAD_TIME). The release process will this value, or the scheduled node's lead time (setup at ship node level), whichever is greater. This field is not currently used. Displays a warning message if CannotScheduleBeforeDate or CannotScheduleAfterDate fields have a Non-Null value. The quantity avialable through modification rules for making a stop delivery request for this line. A flag to indicate if the order line is awaiting for a Delivery service association. Mark For Node as identified by the buyer for eg: it could be a person,store,DC Receiving node as identified by the buyer for eg:Store,DC Number this flag indicates whether the product line can be associated with service lines. The customers carrier account number. The carrier service code for this order line. The order header that is associated with this chained order line. If this line is chained from another order line, this key will point to the parent order line's header record. The order line that is associated with this chained order line. If this line is chained from another order line, this key will point to the parent order line. It is a data attribute to store the quantity that is committed by supplier. A user defined variable that can be used for condition building in process modeling. A user defined variable that can be used for condition building in process modeling. This field is used by Sterling Multi-Channel Selling Solution so that Visual Modeler can be opened with existing options. The buyer PO line number. The buyer's PO number. This field indicates who will pay the freight. Sterling Multi-Channel Fulfillment Solution understands values such as SUPPLIER, ENTERPRISE and MARKETPLACE to mean that each of these organizations will pay for the freight. You could however pass any other value which is a valid shipment charge type as understood by the carrier by which the shipment is transported. See YFS_SHIPMENT_CONTAINER.carrier_payment_type for additional information. The delivery method for the product line. This field can be used for line classification and reporting purposes. This field indicates whether any order lines are dependant on the parent order line. This field can only be specified for the parent line. If this field is specified, it is defaulted on all of the dependant lines. This field is ignored if it is specified on a dependant line. The order line key that this order line is associated with. This field will indicate which order line is the parent of the the order line for line dependencies. The order header that is associated with this derived order line. If this line was derived from another order line, this key will point to the parent order line's header record. The order line that is associated with this derived order line. If this line was derived from another order line, this key will point to the parent order line. The order release that this derived order line is associated with. If this line was derived from another order line, this key will point to the parent order release record. the identifier of the distribution group that is used to determine the ship node(s) that will ship the order line. If not provided, the seller organization's default distribution rule ID is used. If provided, it must be a valid ID for the Seller organization. The minimum order line quantity that must be fulfilled in an order release before it is shipped. Indicates Freight Terms for the line. The method of fulfilling the order line during scheduling. This field can be matched with the corresponding field in the YFS_SOURCING_RULE_HDR table and the appropriate sourcing rule can be selected. Thie field indicates when inventory for the product line will be available. This flag indicates whether the order line is a gift item.
Indicates if this order has chained or related lines.
Default: N
Valid Values: Y or N
Indicates if the line has associated delivery lines. Valid only for product lines.
Indicates if order line has lines derived from it.
Default: N
Valid Values: Y or N
Indicates if the line has associated service lines. Valid only for product lines. This attribute is not in use in prior to Sterling Supply Chain Applications 7.1. If you want to use deprecated functionality, set the rule 'Use deprecated hold Functionality'. If the rule is not set, this flag is set/reset by the application. Application sets this flag to 'Y' if order line has any hold types. Flag is reset to 'N' if there are no hold types on order line. In this mode based on hold type configuration, certain transactions may not be allowed to process. This flag should not be passed when rule is configured to use 7.1 functionality. There are no validations for this but value can be reset by the application based on hold types on order line. This field is not currently used. The expiration date of the import license number. The import license number to be used. A flag to indicate if the order line should be backordered upon creation. If passed as 'Y', the line will be backordered even if inventory is available. This flag is ignored if reservation is mandatory. The total extended price which has already been invoiced. Invoiced quantity on the order line. Invoiced quantity on the order line. Indicates if Order line is bundle parent line or not.

Valid Values: Y or N
This flag indicates whether the pre-defined node on the line is firm. If IsFirmPredefinedNode is marked as N, then the node on the line is ignored during scheduling. If not passed, the value defaults to Y. This field indicates what kind of item is on the order line. The collection of items that form a unit. For example, a home theatre system is a unit consisting of kit components, such as a DVD player, TV, CD player, etc. The quantity that is used to compute ordered quantity for bundle component line. It can be specified only for bundle components. If specified ordered quantity will be set to KitQty*OrderedQty of the bundle parent. The order line sequence number. The line type. This field can be used in process modeling for pipeline determination, or for doing conditional processing for this line. Maximum order line status among all records that belong to an order. Description of maximum order line status among all records that belong to an order. The node where two or more order lines that are to be delivered together should be merged before the final delivery. This field is required when the DependancyShippingRule is set to '02'. Additionally this field will indicate forwarding location for zone skipping. Minimum order line status among all records that belong to an order. Description of minimum order line status among all records that belong to an order. The preferred minimum ship by date of the available supply that order line can allocate against. This only applies to the order line or kit line with time-sensitive item. If order line is in more than one status then this flag will be returned as "Y". Total quantity that can be cancelled from the line. The order header that this order line is associated with. The primary key for the YFS_ORDER_LINE table. The quantity of the line item that has been ordered. If part of the line is cancelled, this number is reduced appropriately. If an order line is returned, this number is not reduced. The line from which this line was created (split process). The quantity which was ordered at order creation. This is not modified after order confirmation. The sum of all the line level charges. The code indicating the type of packlist to be used for the line. Lines requiring different pack lists are not mixed in a single order release. This flag indicates whether this line is a parent of a dependency group. The code for personalization. This flag indicates whether this line needs personalization. This field is used internally. The pipeline that this order line belongs to. The order line number. The procurement node that is associated with this order line. The order line should be procured from that node if the products or services cannot be sourced from the shipnode specified on the order line. The promised end date of the appointment. The promised start date of the appointment. This field is passed out in the Tax calculation user exits. The receiving node that is associated with this order line. Remaining quantity. The requested cancel date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The requested delivery date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The requested ship date. If not provided, this field is defaulted from the order header during order creation. Refer to the YFS_ORDER_HEADER table for more details. The reservation ID. If this item was reserved before order creation, pass an ID to associate the line with the reservation. This flag indicates whether this line can be created without a reservation. If set to Y, creation of this line or any quantity addition to this line will be allowed only if the quantity can be reserved. If a ProcureFromNode is also present on the line, then the reservation will be carried out on the procure from node. The reservation identifier. If this item was reserved before order creation, pass an ID to associate the line with the reservation. The reason for returning the order line. Long description of the return reason code. Short description of the return reason code. The carrier to be used for this line. Value of SCAC and Service code. Link to YFS_SCAC_AND_SERVICE table. The reason for which schedule has failed on this order line. The segment of the inventory. The segment type of the inventory. The serial number of the item. The ship node that is associated with this order line. If provided, all releases will be made against this node. The ship to identifier. If a customer definition representing the buyer organization exists within Sterling Multi-Channel Fulfillment Solution, the ShipToID can represent the CustomerID of the customer. Otherwise, the ShipToID can represent the PersonID of the ship to address or the receiving node of the order. The ship to address that is associated with this order line. If not provided, it is defaulted from order header. This field is not currently used. It is a consolidation group id that is used as a standard do not mix constraint.Releases belonging to same shipment consolidation group may consolidate to same shipment This field is not currently used. The quantity which has been split from this line due to substitutions, price negotiations etc. Status description of the order line. Quantity on the order line in the current status. The sub line number. Substituted ItemID. This field is only populated if the item on the Order line is substituted.

Valid Values: Y or N
Substituted Item UOM. This field is only populated if the item on the Order line is substituted. The timezone in which the promised appointment has been recorded. The transaction discrepancy quantity.
Indicates if data is fetched from the history table rather than the regular table.
Default: N
Valid Values: Y or N