import { Entity, DefaultDeSerializers, DeSerializers, DeserializedType } from '@sap-cloud-sdk/odata-v2';
/**
 * This class represents the entity "A_OutbDeliveryDocFlow" of service "API_OUTBOUND_DELIVERY_SRV".
 */
export declare class OutbDeliveryDocFlow<T extends DeSerializers = DefaultDeSerializers> extends Entity implements OutbDeliveryDocFlowType<T> {
    /**
     * Technical entity name for OutbDeliveryDocFlow.
     */
    static _entityName: string;
    /**
     * Default url path for the according service.
     */
    static _defaultServicePath: string;
    /**
     * All key fields of the OutbDeliveryDocFlow entity
     */
    static _keys: string[];
    /**
     * Delivery Version.
     * Maximum length: 4.
     * @nullable
     */
    deliveryversion?: DeserializedType<T, 'Edm.String'> | null;
    /**
     * Preceding sales and distribution document.
     * Number that uniquely identifies the preceding sales, delivery, or billing document (for example, the quotation from which you created a sales order).
     * Maximum length: 10.
     */
    precedingDocument: DeserializedType<T, 'Edm.String'>;
    /**
     * Document Category of Preceding SD Document.
     * Specifies the sales document category of the preceding sales, delivery, or billing document.
     * Maximum length: 4.
     * @nullable
     */
    precedingDocumentCategory?: DeserializedType<T, 'Edm.String'> | null;
    /**
     * Preceding Item of an SD Document.
     * Maximum length: 6.
     */
    precedingDocumentItem: DeserializedType<T, 'Edm.String'>;
    /**
     * Subsequent Sales and Distribution Document.
     * Number that uniquely identifies the subsequent sales, delivery, or billing document (for example, the sales order that you create from a previous quotation).
     * Maximum length: 10.
     * @nullable
     */
    subsequentdocument?: DeserializedType<T, 'Edm.String'> | null;
    /**
     * Referenced quantity in base unit of measure.
     * Specifies how much of an item quantity has already been processed in a subsequent document. The referenced quantity is expressed in basic stock units.
     * A sales order item has an order quantity of 100 pieces. You create two delivery notes against the order: the first for 20 pieces, the second for 80 pieces. In the first case, the referenced quantity is 20 pieces; in the second case, 80 pieces.
     * @nullable
     */
    quantityInBaseUnit?: DeserializedType<T, 'Edm.Decimal'> | null;
    /**
     * Subsequent Item of an SD Document.
     * Number that uniquely identifies the item in the subsequent document (for example, in a sales order that you created from a quotation).
     * Maximum length: 6.
     * @nullable
     */
    subsequentDocumentItem?: DeserializedType<T, 'Edm.String'> | null;
    /**
     * Quantity is calculated positively, negatively or not at all.
     * Indicates whether, during copying, the quantity or value in thetarget document has a negative effect, positive effect, or no effect at all on the quantity still to be completed in the source document.
     * The system uses this indicator to determine how the quantity in the source document is affected. For example, if youCreate a quotation item for 100 pieces,Copy the quotation into a sales order, andCreate a sales order item for 80 pieces,the copying has a positive effect on the quotation. In effect, you have added 80 pieces to the quotation quantity that is now considered complete. 20 pieces in the quotation remain to be completed.If you do not make an entry in this field, or set indicator 0, the source document is not blocked, which allows you to create several target documents at once (for example, when using EDI and frequent contract releases).While the source document (such as quotation or quantity contract) is being processed, it is blocked. For instance, if you are working on a quantity contract, no one can create a release order for that contract.In sales documents, for example, you can expect the following results:Quotation   -> Sales order: positiveContract    -> Return: negativeSales order -> Sales order: no effectIn billing documents, for example, you can expect the following results:Delivery    -> Invoice: positiveDelivery    -> Cancellation: negativeDelivery    -> Pro-forma invoice: no effect.
     * Maximum length: 1.
     * @nullable
     */
    sdFulfillmentCalculationRule?: DeserializedType<T, 'Edm.String'> | null;
    /**
     * Document Category of Subsequent Document.
     * The document category of the sales document that you have created from a preceding document (for example, a delivery note that has been created from a sales order).
     * Maximum length: 4.
     */
    subsequentDocumentCategory: DeserializedType<T, 'Edm.String'>;
    /**
     * ID: MM-WM Transfer Order Confirmed.
     * Indicates whether the transfer order in the warehouse management (WM) system is confirmed.
     * @nullable
     */
    transferOrderInWrhsMgmtIsConfd?: DeserializedType<T, 'Edm.Boolean'> | null;
}
export interface OutbDeliveryDocFlowType<T extends DeSerializers = DefaultDeSerializers> {
    deliveryversion?: DeserializedType<T, 'Edm.String'> | null;
    precedingDocument: DeserializedType<T, 'Edm.String'>;
    precedingDocumentCategory?: DeserializedType<T, 'Edm.String'> | null;
    precedingDocumentItem: DeserializedType<T, 'Edm.String'>;
    subsequentdocument?: DeserializedType<T, 'Edm.String'> | null;
    quantityInBaseUnit?: DeserializedType<T, 'Edm.Decimal'> | null;
    subsequentDocumentItem?: DeserializedType<T, 'Edm.String'> | null;
    sdFulfillmentCalculationRule?: DeserializedType<T, 'Edm.String'> | null;
    subsequentDocumentCategory: DeserializedType<T, 'Edm.String'>;
    transferOrderInWrhsMgmtIsConfd?: DeserializedType<T, 'Edm.Boolean'> | null;
}
//# sourceMappingURL=OutbDeliveryDocFlow.d.ts.map