A mapper representing custom fields in an entity. Custom fields are represented by their field names and the corresponding values. A custom field can be added or updated using setCustomField method.
The current ETag version of the entity in the remote system. The ETag identified the version of the in the remote system. It will be automatically set in the "if-match" header of update requests and can be set as a custom header for delete requests. When no ETag is provided by the remote system the value of this variable defaults to "*".
Route. Route by which the delivery item is to be delivered to the customer. You can use the route in a delivery to represent the following situations: One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document. Maximum length: 6.
Actual Goods Movement Date. You can preset the posting date for goods movement with the actual goods movement date. For example, if the posting should occur in a previous period or month, you can do so with this default. If the goods movement date is not filled in, the system automatically uses the current date.The posting date for the material document is filled using the actual goods movement date. The document date shown on the material document is the current date.
Time of Goods Issue (Local, Relating to a Plant).
Bill of Lading. Identifies the number of the bill of lading with which the goods are to be transported. Maximum length: 35.
Billing Date. Date on which billing is processed and posted to Accounting. When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
Complete Delivery Defined for Each Sales Order?. Indicates whether a sales order must be delivered completely in a single delivery or whether the order can be partially delivered and completed over a number of deliveries.
Confirmation Time. Time at which the proof of delivery (POD) is confirmed for a delivery. The POD confirmation time is the same as the POD verification time if the ship-to party verifies the receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.
Name of Person Who Created Object. Maximum length: 12.
Date on Which Record Was Created.
Entry time. The time of day at which the document was posted and stored in the system.
Customer Group. Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics. Maximum length: 2.
Delivery Block (Document Header). Indicates if an entire sales document (a sales order, for example) is blocked for delivery. The system can propose a delivery block on header level according to sales document type. Users can also enter a block manually. A block in the header applies to the entire sales document.The system only proposes a delivery block at header level if delivery blocks have been assigned to the corresponding delivery type using the Define Reasons for Blocking in Shipping and the Assign Blocking Reasons to Delivery Types configuration steps.Additional InformationUsers can also block a sales document manually at schedule line level.The settings made in these configuration steps do not influence any delivery blocks set at schedule line level.The system can block delivery automatically for certain sales document types (for example, sales orders without charge) where it is important that someone checks the details before shipping takes place. Maximum length: 2.
Delivery Date. The date by which the delivery should be received by the customer. The system can use predefined time estimates to calculate the delivery date for goods issue. The estimates take into account the time needed for the following activities:Arranging transportationPicking and loading the goodsTransporting the delivery from your warehouse to the customerYou can change the date manually during delivery processing.
Delivery. The number that uniquely identifies the delivery. Maximum length: 10.
External Identification of Delivery Note. The supplier's reference number appears in the delivery note's external identification. When you create an inbound delivery manually or when the supplier creates a notification (per EDI), the external identification number can have a maximum of 35 characters.Please note:Only 16 reference characters are used for invoice verification. Therefore, we recommend that you use no more than 16 characters in the external identification number. Maximum length: 35.
Delivery Type. A classification that distinguishes between different types of deliveries. The delivery type determines how the system processes a delivery. For example, depending on the delivery type, the system determines which screens to present and which data to request from the user. Maximum length: 4.
Delivery has Status 'In Plant'.
Delivery Priority. The delivery priority assigned to an item. You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria. Maximum length: 2.
Time of delivery. The time at which the item should arrive at the customer site. The time is proposed for the scheduled day of delivery. You can store information about the customer's goods receiving hours in the customer master record of the ship-to party. This information includes receiving hours for each working day and for each of the customer's unloading points.The system may propose an arrival time from the customer master record. If the customer allows deliveries during a certain time slot, the system proposes the earliest time in the slot. You can change the proposed time manually in the sales order.If you schedule a delivery for a Monday and the customer has receiving hours between 8am and 12am, the system proposes 8am as the earliest possible arrival time.
Delivery Version. Maximum length: 4.
Depreciation percentage for financial document processing. Enter the percentage of the document value that is covered by the assigned financial document and is to be written off against the total value of the financial document. In general, the financial document covers the full amount of a document, that is, 100%.In exceptional cases, business partners may agree that only part of the amount is to be covered by a corresponding financial document.This means that only part of the amount is written off against the total value of the financial document.For example, if a business transaction has been defined such that 30% of the document value is covered by credit management and the remaining amount by a corresponding letter of credit, you should enter the value 70.If you do not enter a value, or if you enter the value '0,00 %', the system uses the value '100.00 %', that is, the document value fully coverd by the assigned financial document.
Distribution Status (Decentralized Warehouse Processing). This field displays the processing status of the delivery in terms of decentralized Warehouse Management System processing. This field cannot be changed manually. Instead, the system determines the status using delivery items' warehouse numbers and the delivery processing status. In the central system, this field may contain the following characteristics:' ': delivery is not relevant for distribution to a decentralized WM System.'A': delivery is relevant for distribution in the decentralized system. When the delivery is saved, an IDoc is created. The system then uses this IDoc to distribute the delivery in the decentralized system.'B': delivery was distributed in the decentralized system and is currently being processed there.'C': processing of the delivery in the decentralized system is complete. Any changes are confirmed in the central system.'D': The delivery is planned for distribution in the decentralized system. You can trigger distribution using the delivery monitor.'E': The delivery was subsequently split in the decentralized system. In this case, no further changes can be made to the document in the central system.'F': Change management was subsequently switched off. For example, because the central system was temporarily not available. The delivery can no longer be changed in the central system.This field may contain the following characteristics in the decentralized Warehouse Management System:'A': delivery is being processed.'C': processing of this delivery in the decentral system is complete. The delivery is confirmed in the central system via goods issue or goods receipt posting. The delivery can no longer be changed in the decentral system.'E': The delivery was split in the decentralized system. The delivery can then be changed, however, only changes to the delivery quantity are returned to the central system.'F': Change management was subsequently switched off. The delivery can only be changed in the decentralized system. Only changes to the delivery quantity are reported back to the central system.Statuses 'B' and 'D' do not occur in this system. Maximum length: 1.
Document Date in Document. The document date is the date on which the original document was issued.
Type of External Identification. Maximum length: 1.
ID for External Transport System. Maximum length: 5.
Customer Factory Calendar. The factory calendar that determines the workdays for a particular unloading point at the customer site. The system proposes the factory calendar from the information about unloading points in the customer master record of the ship-to party.You cannot change the calendar during sales order and delivery processing. If you enter a date that does not comply with the specified calendar, the system gives you a warning message before you can continue. Maximum length: 2.
Goods Receipt/Issue Slip Number. Specifies a number which - in addition to the material document number - uniquely identifies a goods receipt/issue slip. This number can be assigned both internally and externally. If number assignment for goods receipt/issue slips is active in the plant, you can proceed as follows:You enter a number manually.You do not enter a number. In this case, the system automatically assigns a number.NoteThis GR/GI slip number has only been designed for use in those countries (for example, Italy) whose legislation requires specification of this number for goods that leave the plant and are transported on public roads.In other countries, the material document number printed on the GR/GI slip (in the standard system) is usually sufficient. To enter external documents, you can use the field Material slip or Delivery note. Maximum length: 10.
Time of Goods Issue (Local, Relating to a Plant).
Handling Unit Placed in Stock. This field shows whether at least one handling unit in the delivery is in WM stock. If an additional handling unit of the delivery has been placed in WM stock, goods issue cannot be posted for the delivery. Maximum length: 1.
Incompletion Status (Header). The incompletion status of general header information in the sales document. General information includes business, shipping, and billing data. The status tells you if general header information is complete. You cannot copy sales documents with missing information into other sales documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later. Maximum length: 1.
Post Header Incomplete Status for Goods Movement. Incomplete status of the billing-related header data in the sales document. This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time. Maximum length: 1.
Billing Incompletion Status (Header). The completion status of billing-related header information in the sales document. The status tells you if billing-related header information is complete. Incomplete sales documents cannot be billed. For example, if a sales order contains no information about terms of payment, you cannot create an invoice for it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later. Maximum length: 1.
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.
Delivery Incompletion Status (Header). The incompletion status of delivery-related header information in the sales document. The status tells you if delivery-related header information is complete. Missing information affects further processing. For example, a sales order that contains no information about Incoterms cannot be delivered.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later. Maximum length: 1.
Total Weight. The total gross weight of all items in the delivery. The system calculates the gross weight for each item by multiplying the delivery quantity by the gross weight per sales unit from the sales order. If there is no related sales order, the system uses the gross weight from the material master record.
Net Weight. The total net weight of all items in the delivery. The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record.You can change the net weight manually in the delivery document.
Header Incomplete Status for Packaging. Incomplete status of the billing-related header data in the sales document. This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time. Maximum length: 1.
Header Incomplete Status for Picking/Putaway. Incomplete status of the billing-related header data in the sales document. This status indicates whether the billing-related header data is incomplete. Incomplete sales documents cannot be billed. For example, you cannot create an invoice for a sales document that does not specify the terms of payment.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time. Maximum length: 1.
Volume. The total volume of all items in the delivery. The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record.You can change the volume manually in the delivery document.
Volume Unit. Unit referring to the volume of the material. If you specify a volume, you have to enter the corresponding volume unit here. Maximum length: 3.
Unit of Weight. Unit referring to the gross weight or net weight of the material. If you specify a weight, you must enter the corresponding unit of weight here. Maximum length: 3.
Incoterms (Part 1). Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC). Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example. Maximum length: 3.
Incoterms (Part 2). Additional information for the primary Incoterm. If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston"). Maximum length: 28.
Billing Date for Intercompany Billing.
Financial doc. processing: Internal financial doc. number. Internal number of a financial document that is mapped to a trade finance transaction. The number is assigned by the system. You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance. Maximum length: 10.
Delivery Within one Warehouse. Together with the warehouse number, this indicator provides information on deliveries for one warehouse number. Maximum length: 1.
Export indicator. Indicates whether the delivery will be exported. Maximum length: 1.
Date of Last Change.
Name of Person who Changed Object. Maximum length: 12.
Loading Date. The date by which picking and packing must be completed so that the goods are ready for loading and for the delivery to reach the customer on time. Any special packaging materials required for loading must also be available by this date. If items in the same delivery have different loading dates, the earliest date appears in the document header.The system uses predefined time estimates to calculate the loading date. The estimates take into account the following information:Shipping pointRouteLoading groupYou can change the loading date manually.
Loading Point. The exact physical location where the loading of a delivery item takes place (for example, the number of a specific loading bay). Maximum length: 2.
Loading Time (Local Time Relating to a Shipping Point).
Means of Transport ID. Classifies a shipment of goods. You can specify the truck with which the goods are to be transported. Maximum length: 20.
Means of Transport. The means of transport is a packaging material in the category 'means of transport' or 'transport equipment'. Maximum length: 40.
Means-of-Transport Type. Key which specifies how the goods are transported. This key identifies the means of transport type. The means of transport type is a packaging material type in the category 'means of transport' or 'transport equipment'.All available trucks are assigned to the means of transport type LKW.Available ships of means of transport type ship.If the goods are to be transported by road, enter the means of transport type LKW. Maximum length: 4.
Order Combination Indicator. Indicates whether you are allowed to combine orders during delivery processing. The system proposes the indicator from the customer master record. You can change the value manually in the sales document at both header and item level.
Order Number. Key that uniquely identifies an order within a client. Maximum length: 12.
Confirmation Status (All Items). Represents the combined delivery confirmation status of all items in the sales document. The system confirms delivery for each schedule line after checking availability. The confirmation means that the system is able to confirm that a quantity is available for delivery on a certain day. The confirmation does not reflect when the goods are shipped to or received by the customer. Maximum length: 1.
Delivery-Related Billing Status (All Items). The billing status of the sales or delivery document. The status message tells you if the document is completely billed, partly billed, or is not relevant for billing. Maximum length: 1.
Goods Movement Status (All Items). Indicates if, and to what extent, the delivery has left your premises. The status tells you whether the delivery has already left your warehouse, is still being processed, or whether processing has not yet begun. Maximum length: 1.
Intercompany Billing Status (All Items). Maximum length: 1.
Packing Status (All Items). The packing status indicates whether there are items that are relevant for packing and, if so, where these items are completely or only partially packed. Maximum length: 1.
Status of Pick Confirmation. The confirmation status of the outbound delivery indicates whether picking must be explicitly confirmed for the delivery or whether picking has already been confirmed. The confirmation status is only relevant if you are not using WM transfer orders for picking. Maximum length: 1.
Picking Status/Putaway Status (All Items). Overall status for picking or putting away the delivery Displays whether the delivery has been completely picked or put away, whether it is in the process of being picked/put away, or whether it has just started. Maximum length: 1.
POD Status on Header Level. Proof of delivery status (POD status) for the entire delivery. The status informs you whether the ship-to party reported a POD for this delivery:This status can have the following values:' ' Not relevant for the POD process'A' Relevant for the POD process'B' Differences were reported'C' Quantities were verified and confirmedIf all item quantities of a delivery are reported with no differences, the process is confirmed automatically. If differences are reported, the proof of delivery must be confirmed manually. Maximum length: 1.
Overall Processing Status (Header/All Items). The processing status of the entire sales document. The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete. Maximum length: 1.
Status of Warehouse Management Activities (All Items). Displays the status of processing in the warehouse management system (WM). The status line tells you whether a transfer order for WM is required or not, and, if required, whether it is confirmed or still open for processing. Maximum length: 1.
Delivery Incompletion Status (All Items). The incompletion status of shipping-related item information in the sales document. If shipping-related item information is missing from the sales order, the system marks the status as incomplete. You cannot ship an item that has incomplete shipping information. For example, if an item contains no information about a shipping point, you cannot ship it.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later. Maximum length: 1.
Total Incomplete Status of all Items: Post Goods Movement. Incompletion status of item data in the sales document that affects shipping. If shipping-related item data from the sales order is missing, the system sets the status to incomplete. An item with incomplete shipping data cannot be transmitted. If an item does not, for example, contain any specifications on the shipping point, you cannot transmit it.If you attempt to save a document where data is missing, the system will point out that the document is incomplete. You can then call up a list of the fields with missing specifications and complete them. However, you can also save the incomplete document and supply the missing data at a later time. Maximum length: 1.
Incompletion Status (All Items). The incompletion status of general item information in the sales document. General item information includes business, shipping, and billing data. The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later. Maximum length: 1.
Totals Incomplete Status for all Items: Packaging. Incomplete status of the item data in the sales document that is relevant for shipping. If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time. Maximum length: 1.
Totals Incomplete Status for all Items: Picking. Incomplete status of the item data in the sales document that is relevant for shipping. If shipping-related item data from the sales order is missing, the system will set the status to incomplete. You cannot ship an item with incomplete shipping data. For example, if no shipping point has been specified for an item, that item cannot be shipped.If you try to save a document and data is still missing, the system will inform you that the document is incomplete. You can then either retrieve a list of the fields concerned and enter the missing data, or you can save the incomplete document and enter the missing data at a later time. Maximum length: 1.
Payment Guarantee Procedure. Contains the permitted forms of payment guarantee for the payer and document type. Controls the sequence in which the system assigns forms of payment guarantee to sales document items. In risk management for receivables, depending on payment guarantee category, the system accesses the form of payment guarantee using the following rules:Payment cards are activated once you have specified a payment card in the documentDocumentary payment guarantees are immediately activedExternal export credit insurance is activated once a valid contract is available. Maximum length: 6.
Picked Items Location. Identifies the specific location in the loading area where, after picking, an item is assembled for packing and loading. If your warehouse procedures require it, you can arrange for picked items to be assembled in boxes, trays, or bins in the loading area, prior to packing and loading. The location you specify in this field appears on the picking list. Maximum length: 20.
Picking Date. The date by which picking must begin for the delivery item to reach the customer on time. If the items in a delivery have different picking dates, the system displays the earliest picking date in the delivery document header. You can use the picking date as a selection criterion for processing picking lists.Picking can only begin when the goods are available. The picking date therefore depends on the material availability date.
Picking Time (Local Time, with Reference to a Plant). Date on which picking must begin in order for the delivery item to reach the customer in time. If the items in a delivery do not all have the same picking date, the system displays the earliest picking date in the delivery document header. You can use the picking data as a selection criterion for processing picking lists.Picking cannot begin until the goods are available. This means that the picking date depends on the material availability date.
Planned Goods Movement Date. The date on which the goods must physically leave the shipping point to reach the customer on time. When the goods physically leave the shipping point, the system automatically creates a goods issue document to account for the outgoing inventory. The bill that you subsequently send to the customer must correspond to the movement of inventory. The goods issue date enables the accounting department to relate the movement of goods to the bill.The system automatically calculates the goods issue date by taking into account the following factors:The requested delivery dateThe pick/pack timeThe loading timeThe transit timeYou can change the date manually during delivery processing.
Date (Proof of Delivery). Date when the proof of delivery (POD) was confirmed for a delivery. The POD date is the same as the verification date if the ship-to party verifies receipt of the goods with no differences. In such a case, the delivery is automatically confirmed at the same time.However, if differences are reported, the POD date is set when manual confirmation occurs.
Route. Route by which the delivery item is to be delivered to the customer. You can use the route in a delivery to represent the following situations: One or more legsConnection between point of departure and destination pointTarget areaYou can predefine different standard routes in the system. These are dependent on:Where the delivery comes fromWhere the delivery is going toUnder what conditions the delivery is to take placeYou can use the route as a selection criteria for:Collective processing of deliveriesSelecting deliveries for transportation planningRoute as a Connection Between Departure Point and Destination PointIn the delivery, you can specify that it takes one of these routes:NA: North AtlanticPA: PacificWhich ship is to carry the delivery is not determined until transportation planning.Route as a Target AreaA country can be divided into different delivery areas:R1: NorthR2: North-WestR3: North-EastR4: East, and so onEnter the corresponding route in the delivery. In transportation planning, you can select deliveries destined for one or more target areas.If routes and route determination have been defined using the Define Routes and Maintain Route Determination configuration steps in the Configure Your Solution app, the system can propose a route automatically. If alternative entry values are defined for your system, you can change the route manually in the document. Maximum length: 6.
Receiving Plant for Deliveries. Receiving plant (for customer number) for a delivery. How this field is filled and interpreted depends on the document category/delivery type. You can distinguish between the following cases:Delivery from stock transport orderRecipient of the delivery/ordering plant from the stock transportorderShipping notificationThe shipping notification may refer to several recipients. In thiscase, the field is empty.Rough goods receiptPlant for which you create the rough goods issue.For the remaining deliveries, the field contains the customer's plant number, provided that this customer has been maintained. Maximum length: 4.
The remote state of the entity. Remote state refers to the last known state of the entity on the remote system from which it has been retrieved or to which it has been posted. It is stored as map, where the keys are stored in the format of VDM properties.
Route Schedule. Planning of weekly customer deliveries from one shipping point to different ship-to parties and their unloading points in one route. You can use a route schedule to determine the day (Monday through Sunday) and the time when a customer delivery leaves the shipping point.You can define different route schedules in the system. The system can automatically propose a route schedule depending on the following criteria:the shipping point from which the delivery is sentthe ship-to party and the unloading point to which the delivery is sentthe transportation group of the deliverythe shipping condition of the deliverythe calender week in which the delivery leaves the shipping pointIn addition, you can use route schedules to create work packages from deliveries that are collectively processed in shipping, for example by using Process delivery in the picking transaction. Maximum length: 10.
Sales District. A geographical sales district or region. Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level. Maximum length: 6.
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.
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.
SD Document Category. A classification for the different types of documents that you can process, for example, quotations, sales orders, deliveries, and invoices. The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations). Maximum length: 4.
Ship-To Party. The party who receives delivery of the goods. Maximum length: 10.
Shipment Blocking Reason. Indicates the reason why the delivery is blocked for transportation planning. Deliveries for which as shipment blocking reason has been entered are not selected during a transportation planning run.You can enter a shipment blocking reason in the delivery. When you create a delivery, a shipment blocking reason is proposed on the basis of the delivery type.A delivery can be blocked for transportation planning until a quality control check has been performed.Returns should always be blocked for transportation planning. Maximum length: 2.
Shipping Conditions. General shipping strategy for the delivery of goods from the vendor to the customer. You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments. Maximum length: 2.
Shipping Point / Receiving Point. The physical location (for example, a warehouse or collection of loading ramps) from which you ship the item. You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually. Maximum length: 4.
Shipping Type. Shipping type (for example, by road or rail) that has been selected for the transportation of the goods for the shipment legs. During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination. Maximum length: 2.
Sold-To Party. The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders. Maximum length: 10.
Special Processing Indicator. Indicator that results in a special processing form for a shipment or a special calculation form for shipment costs. Examples for special processing are express shipments or special tariffs. You can search for the indicator using a matchcode and enter the selection data for the field.By setting the status "planned", the special processing indicator is copied from the respective deliveries into the shipment header, provided:the special processing indicator is the same in all deliveriesthe special processing indicator is not already filled in the shipment header. Maximum length: 4.
Statistics Currency. Maximum length: 5.
Account Number of Supplier. Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system. Maximum length: 10.
One-to-many navigation property to the InbDeliveryItem entity.
One-to-many navigation property to the InbDeliveryPartner entity.
One-to-many navigation property to the InbDeliveryHeaderText entity.
Overall Block Status (Header). Overall blocked status. The value of this field is calculated according to the following values:Overall header delivery block status + overall header billing block status + header credit check status. Maximum length: 1.
Overall Status of Credit Checks. Maximum length: 1.
Total Number of Packages in Delivery. The total number of packages for all items in the delivery. The system determines the number of packages. It considers only packages at the highest level, i.e. packages that are not packed into another package. Maximum length: 5.
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.
Transportation Group. A grouping of materials that share the same route and transportation requirements. Transportation groups are used for automatic route scheduling during sales order and delivery note processing.Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery. Maximum length: 4.
Transportation Planning Date. The date by which you must arrange transportation so that the delivery can reach the customer on time. The system can propose the transportation scheduling date from predefined time estimates. Estimates may be based on the route. If items in a delivery have different transportation scheduling dates, the system displays the earliest date in the document header. You can change the date manually.If, for example, you plan to use an external carrier for trucking, you must arrange for a truck to be available when the goods are ready for loading.
Transportation Planning Status (Header). Indicates the extent to which transportation planning has been performed. This characteristic controls the selection of deliveries to make up shipments in transportation planning. It is used a selection criterion for finding deliveries.The indicator is set by the system on the basis of the leg indicator (preliminary, subsequent, direct, return) in the headers of the shipment documents to which the delivery has been assigned.Blank - Not relevantDelivery is not to be processed in transportationplanning. This is the case when:- the delivery type is not relevant for transportation, or- the route is not relevant for transportation (only foroutbound deliveries; not required forinbound deliveries), or- a shipment block has been set in the delivery (only foroutbound deliveries: not required for inbound deliveries)A - Not yet plannedDelivery is to be processed in transportation planning.It has not yet been assigned to a shipment document.B - Partially plannedDelivery is to be processed in transportationplanning. The delivery has already beenassigned to at least one shipment document but thetransportation chain is not complete (see status C).C - Completely plannedDelivery has been assigned to one or moreshipment documents in transportation planning. Dependingon the leg indicator in each shipment header, the delivery isconsidered to be completely planned if- it exists in a direct leg or a return leg or- it exists in a preliminary, main, subsequent leg or- each stage assigned to the delivery connects to asubsequent stage, thus connecting the pointof departure with the destination of the delivery withno gaps in transportation (as of Release 4.6A). Maximum length: 1.
Transp. Planning Time (Local, Relating to a Shipping Point).
Unloading Point. Specifies the point at which the material is to be unloaded (for example, ramp 1). Maximum length: 25.
Warehouse Number / Warehouse Complex. Number that identifies a complex, physical warehouse structure within the Warehouse Management system. All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number. Maximum length: 3.
Door for Warehouse Number. Organizational unit that belongs underneath a warehouse. Doors can be defined for different purposes (both at the same and different times):for goods issuefor goods receiptfor cross docking processesfor flow-throughs. Maximum length: 3.
Staging Area for Warehouse Complex. Organizational unit that is on a hierarchical level below a warehouse. Staging areas can be used for different purposes (at the same time, if necessary):o Goods issueo Goods receipto Cross-docking processeso Direct distribution. Maximum length: 10.
Static representation of the actualDeliveryRoute property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the actualGoodsMovementDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the actualGoodsMovementTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields selector.
Static representation of the billingDocumentDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billOfLading property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the completeDeliveryIsDefined property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the confirmationTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the createdByUser property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryBlockReason property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryDocument property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryDocumentBySupplier property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryDocumentType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryIsInPlant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryPriority property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deliveryVersion property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the depreciationPercentage property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the distrStatusByDecentralizedWrhs property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the documentDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the externalIdentificationType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the externalTransportSystem property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the factoryCalendarByCustomer property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the goodsIssueOrReceiptSlipNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the goodsIssueTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the handlingUnitInStock property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the hdrGeneralIncompletionStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the hdrGoodsMvtIncompletionStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerBillgIncompletionStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerBillingBlockReason property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerDelivIncompletionStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerGrossWeight property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerNetWeight property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerPackingIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerPickgIncompletionStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerVolume property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerVolumeUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the headerWeightUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsClassification property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsTransferLocation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the intercompanyBillingDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the internalFinancialDocument property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isDeliveryForSingleWarehouse property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isExportDelivery property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangedByUser property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangeDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the loadingDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the loadingPoint property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the loadingTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the meansOfTransport property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the meansOfTransportRefMaterial property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the meansOfTransportType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the orderCombinationIsAllowed property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the orderId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallDelivConfStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallDelivReltdBillgStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallGoodsMovementStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallIntcoBillingStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallPackingStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallPickingConfStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallPickingStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallProofOfDeliveryStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallSdProcessStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallWarehouseActivityStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ovrlItmDelivIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ovrlItmGdsMvtIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ovrlItmGeneralIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ovrlItmPackingIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ovrlItmPickingIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paymentGuaranteeProcedure property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the pickedItemsLocation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the pickingDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the pickingTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plannedGoodsIssueDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the proofOfDeliveryDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the proposedDeliveryRoute property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the receivingPlant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the routeSchedule property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the salesDistrict property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the salesOffice property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the salesOrganization property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the sdDocumentCategory property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shipmentBlockReason property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shippingCondition property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shippingPoint property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shippingType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shipToParty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the soldToParty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the specialProcessingCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the statisticsCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplier property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the totalBlockStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the totalCreditCheckStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the totalNumberOfPackage property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toDeliveryDocumentItem for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toDeliveryDocumentPartner for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toDeliveryDocumentText for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the transactionCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the transportationGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the transportationPlanningDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the transportationPlanningStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the transportationPlanningTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the unloadingPointName property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the warehouse property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the warehouseGate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the warehouseStagingArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the InbDeliveryHeader entity.
Default url path for the according service.
Technical entity name for InbDeliveryHeader.
All key fields of the InbDeliveryHeader entity.
Mapping of all key field names to the respective static field property InbDeliveryHeader.
ETag version identifier accessor.
The ETag version identifier of the retrieved entity, returns undefined if not retrieved
Returns a map of all defined fields in entity to their current values.
Entity with all defined entity fields
Custom field value getter.
The name of the custom field
The value of the corresponding custom field
Returns a map that contains all entity custom fields.
A map of all defined custom fields in the entity
Returns all updated custom field properties compared to the last known remote state.
A map containing all updated custom properties, with their new values
Returns all changed properties compared to the last known remote state. The returned properties does not include custom fields. Use getUpdatedCustomFields, if updated custom fields are needed.
Entity with all properties that changed
Validates whether a custom field exists in the entity.
The name of the custom field to update
A boolean value, that indicates whether a custom field is defined in entity
Sets all retrieved custom fields in entity.
Extracted custom fields from a retrieved entity
A boolean value, that indicates the existence of the field in entity
Validates whether a field name does not conflict with an original field name and thus can be defined as custom fields.
Field name to check
Boolean value that describes whether a field name can be defined as custom field
Sets a new custom field in the entity or updates it. Throws an error, if the provided custom field name is already defined by an original field in entity.
The name of the custom field to update
The value of the field
The entity itself, to facilitate method chaining
Initializes or sets the remoteState of the entity. This function is called on all read, create and update requests. This function should be called after initializeCustomFields, if custom fields are defined.
State to be set as remote state
The entity itself, to facilitate method chaining
Set the ETag version identifier of the retrieved entity.
The returned ETag version of the entity
The entity itself, to facilitate method chaining
Overwrites the default toJSON method so that all instance variables as well as all custom fields of the entity are returned.
An object containing all instance variables + custom fields.
Returns an entity builder to construct instances InbDeliveryHeader.
A builder that constructs instances of entity type InbDeliveryHeader.
Returns a selectable object that allows the selection of custom field in a get request for the entity InbDeliveryHeader.
Name of the custom field to select
A builder that constructs instances of entity type InbDeliveryHeader.
Returns a request builder to construct requests for operations on the InbDeliveryHeader entity type.
A InbDeliveryHeader request builder.
This class represents the entity "A_InbDeliveryHeader" of service "API_INBOUND_DELIVERY_SRV". This service is part of the following communication scenarios: Delivery Processing Integration (SAP_COM_0106). See https://api.sap.com/api/API_INBOUND_DELIVERY_SRV;v=0002 for more information.