FulfillmentTOrderItem, TFulfillmentItem Class

public abstract class Fulfillment<TOrderItem, TFulfillmentItem>
where TFulfillmentItem : EnterpriseOneEntityObject

Public MustInherit Class Fulfillment(Of TOrderItem, TFulfillmentItem As EnterpriseOneEntityObject)

generic<typename TOrderItem, typename TFulfillmentItem>
where TFulfillmentItem : EnterpriseOneEntityObject
public ref class Fulfillment abstract

[<AbstractClassAttribute>]
type Fulfillment<'TOrderItem, 'TFulfillmentItem when 'TFulfillmentItem : EnterpriseOneEntityObject> =  class end

Type Parameters

TOrderItem

The type of the order item.

TFulfillmentItem

The type of the fulfillment item.

Fulfillment usually is the process in which one document is fulfilled by creating another. For example, a Store Order can be fulfilled by issuing a Store Transaction.

Actually the document lines of the source (order) document are fulfilled with the lines of the target (fulfillment) document. E.g. the Store Order Lines are fulfilled with the Store Transaction Lines.

Sometimes, a document can have multiple different sets of lines. For example, a Service Activity document can have Materials and Services lines. Each set of lines defines a different fulfillment.

For example, the Service Activity to Sales Order generation can define two different fulfillments:

• ServiceActivityMaterials To SalesOrderLines
• ServiceActivityServices To SalesOrderLines

The base class is very generic and can represent fulfillment for which the order item can be any class, not just an entity class. For example, if we want to display a form, which is not bound, but contains values, which should later be fulfilled with a real entities. In this case, it is useful to define fulfillment, which is bound to that class as order item. Example of such process could be the Stock Holds To Store Order Lines fulfillment process. In this process, the UI allows the user to select products and enter quantities to sell directly from a stock holds report.

Reference