import { Entity, DefaultDeSerializers, DeSerializers, DeserializedType } from '@sap-cloud-sdk/odata-v2'; import { CustProjSlsOrdItem, CustProjSlsOrdItemType } from './CustProjSlsOrdItem'; import { CustProjSlsOrdPartner, CustProjSlsOrdPartnerType } from './CustProjSlsOrdPartner'; import { CustProjSlsOrdText, CustProjSlsOrdTextType } from './CustProjSlsOrdText'; /** * This class represents the entity "A_CustProjSlsOrd" of service "CPD.SC_PROJ_ENGMT_CREATE_UPD_SRV". */ export declare class CustProjSlsOrd extends Entity implements CustProjSlsOrdType { /** * Technical entity name for CustProjSlsOrd. */ static _entityName: string; /** * Default url path for the according service. */ static _defaultServicePath: string; /** * All key fields of the CustProjSlsOrd entity */ static _keys: string[]; /** * Commercial Project ID. * Identifies a customer or internal project. * Maximum length: 40. */ customerProject: DeserializedType; /** * Sales Order. * Maximum length: 10. * @nullable */ salesOrder?: DeserializedType | null; /** * Sold-to Party. * The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders. * Maximum length: 10. * @nullable */ soldToParty?: DeserializedType | null; /** * Net Value of the Sales Order in Document Currency. * The total value of all items in the sales document, after any discounts and surcharges are taken into account. The value is expressed in the document currency. * @nullable */ totalNetAmount?: DeserializedType | null; /** * SD Document Currency. * The currency that applies to the document (for example, to a sales order or an invoice). * The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document. * Maximum length: 5. * @nullable */ transactionCurrency?: DeserializedType | null; /** * Customer Reference. * Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order). * The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note). * Maximum length: 35. * @nullable */ purchaseOrderByCustomer?: DeserializedType | null; /** * Customer Reference Date. * The date that appears on the customer's purchase order. This date can be, for example, the date on which the customer created the purchase order. * @nullable */ customerPurchaseOrderDate?: DeserializedType | null; /** * Sales Office. * A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area. * When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record. * Maximum length: 4. * @nullable */ salesOffice?: DeserializedType | null; /** * Sales Group. * A group of sales people who are responsible for processing sales of certain products or services. * By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record. * Maximum length: 3. * @nullable */ salesGroup?: DeserializedType | null; /** * Terms of Payment Key. * Key for defining payment terms composed of cash discount percentages and payment periods. * It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record. * Maximum length: 4. * @nullable */ customerPaymentTerms?: DeserializedType | null; /** * Account Assignment Group for this Customer. * The account assignment group to which the system automatically posts the sales document. * The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document. * Maximum length: 2. * @nullable */ customerAccountAssignmentGroup?: DeserializedType | null; /** * Billing Block in SD Document. * Indicates if the entire sales document is blocked for billing. * The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing. * Maximum length: 2. * @nullable */ headerBillingBlockReason?: DeserializedType | null; /** * Sales Organization. * An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims. * You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area. * Maximum length: 4. * @nullable */ salesOrganization?: DeserializedType | null; /** * Distribution Channel. * The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales. * You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area. * Maximum length: 2. * @nullable */ distributionChannel?: DeserializedType | null; /** * Division. * A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service. * A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions. * Maximum length: 2. * @nullable */ organizationDivision?: DeserializedType | null; /** * One-to-many navigation property to the [[CustProjSlsOrdItem]] entity. */ toCustProjSlsOrdItem: CustProjSlsOrdItem[]; /** * One-to-many navigation property to the [[CustProjSlsOrdPartner]] entity. */ toCustProjSlsOrdPartner: CustProjSlsOrdPartner[]; /** * One-to-many navigation property to the [[CustProjSlsOrdText]] entity. */ toCustProjSlsOrdText: CustProjSlsOrdText[]; } export interface CustProjSlsOrdType { customerProject: DeserializedType; salesOrder?: DeserializedType | null; soldToParty?: DeserializedType | null; totalNetAmount?: DeserializedType | null; transactionCurrency?: DeserializedType | null; purchaseOrderByCustomer?: DeserializedType | null; customerPurchaseOrderDate?: DeserializedType | null; salesOffice?: DeserializedType | null; salesGroup?: DeserializedType | null; customerPaymentTerms?: DeserializedType | null; customerAccountAssignmentGroup?: DeserializedType | null; headerBillingBlockReason?: DeserializedType | null; salesOrganization?: DeserializedType | null; distributionChannel?: DeserializedType | null; organizationDivision?: DeserializedType | null; toCustProjSlsOrdItem: CustProjSlsOrdItemType[]; toCustProjSlsOrdPartner: CustProjSlsOrdPartnerType[]; toCustProjSlsOrdText: CustProjSlsOrdTextType[]; } //# sourceMappingURL=CustProjSlsOrd.d.ts.map