import { Entity, DefaultDeSerializers, DeSerializers, DeserializedType } from '@sap-cloud-sdk/odata-v2'; import { ProductionSupplyAreaAddress, ProductionSupplyAreaAddressType } from './ProductionSupplyAreaAddress'; import { ProductionSupplyAreaText, ProductionSupplyAreaTextType } from './ProductionSupplyAreaText'; /** * This class represents the entity "A_ProductionSupplyArea" of service "API_PRODUCTIONSUPPLYAREA_SRV". */ export declare class ProductionSupplyArea extends Entity implements ProductionSupplyAreaType { /** * Technical entity name for ProductionSupplyArea. */ static _entityName: string; /** * Default url path for the according service. */ static _defaultServicePath: string; /** * All key fields of the ProductionSupplyArea entity */ static _keys: string[]; /** * Production Supply Area. * Maximum length: 10. */ productionSupplyArea: DeserializedType; /** * Plant. * Key uniquely identifying a plant. * Maximum length: 4. */ plant: DeserializedType; /** * Storage Location. * Maximum length: 4. * @nullable */ storageLocation?: DeserializedType | null; /** * Person responsible for one or more supply areas. * Person responsible for processing materials and for monitoring stocks at the supply area. * You define the key for the person responsible in Customizing for MRP, under, Master data -> Define MRP controllers. * Maximum length: 3. * @nullable */ productionSupplyAreaRespPerson?: DeserializedType | null; /** * Unloading Point. * Specifies the point at which the material is to be unloaded (for example, ramp 1). * Maximum length: 25. * @nullable */ unloadingPointName?: DeserializedType | null; /** * Factory calendar key. * Key that uniquely identifies the factory calendar that is valid for this plant. * Maximum length: 2. * @nullable */ factoryCalendar?: DeserializedType | null; /** * Grouping for Shift Definition and Sequences (Consumer). * Gibt die Indicates the shift grouping of the consuming work center. * You use the shift grouping and the shift sequence to specify the working times of the consuming work center in detail. The system calculates the calendar buffer from this information.You can specify the shift grouping in the calculation profile and in the PSA. The shift grouping you specify in the PSA overrides the shift grouping you may have entered in the calculation profile.If you do not specify any data for the working time for the consuming work center, the system uses the data that you have maintained for the supplier (supply source). In this case, the calendar buffer calculated by the system is 0. * Maximum length: 2. * @nullable */ shiftGrouping?: DeserializedType | null; /** * Key for Shift Sequence (Consumer). * Shows the key of the shift sequence that you have created for the consuming work center. * You use the shift grouping and the shift sequence to specify the working times of the consuming work center in detail. The system calculates the calendar buffer from this information.You can specify the shift sequence in the calculation profile and in the PSA. The shift sequence you specify in the PVB overrides one that you may have entered in the calculation profile.If you do not specify any data for the working time for the consuming work center, the system uses the data that you have maintained for the supplier (supply source). In this case, the calendar buffer calculated by the system is 0. * Maximum length: 4. * @nullable */ shiftSequence?: DeserializedType | null; /** * Pull Interval in Workdays. * Time interval between the transfer of requirements from the consumer (demand source) to the supply source or the interval between the times of delivery by the supply source to the consumer. * The pull interval is used as a buffer in the control cycle calculation. It increases the number of kanban containers in the control cycle.The pull interval in hours/minutes takes priority over the pull interval in days, i.e. the system uses the pull interval in hours/minutes as soon as you specify this value, irrespective of what you have specified for the pull interval in days.You can specify the pull interval in the calculation profile, in the PSA, and in control cycle maintenance. If you have specified the pull interval more than once, at different points, the system takes this interval into account with the following priorities:1: Control cycle maintenance2: PSA3: Calculation profileThe person who replenishes the PSA arrives at 8 a.m. every day to pick up empty kanbans (kanban cards) and leave behind full ones. In this case, the pull interval amounts to 1 day. * @nullable */ pullIntervalInWorkdays?: DeserializedType | null; /** * Pull Interval in Minutes. * Time interval between the transfer of requirements from the consumer (demand source) to the supply source or the interval between the times of delivery by the supply source to the consumer. You can enter the minutes up to the maximum value 59999999. * The pull interval is used as a buffer in the control cycle calculation. It increases the number of kanban containers in the control cycle.The pull interval in minutes takes priority over the pull interval in days, i.e. the system uses the pull interval in minutes as soon as you specify this value, irrespective of what you have specified for the pull interval in days.To enable the pull interval in minutes to be used in the kanban calculation, it is necessary to define a factory calendar and shift sequences for the control cycle calculation.You can specify the pull interval in the calculation profile, in the PSA, and in control cycle maintenance. If you have specified the pull interval more than once, at different points, the system takes this interval into account with the following priorities:1: Control cycle maintenance2: PSA3: Calculation profileYour production works on a single-shift basis from 8.00 hrs to 16.00 hrs. This information in stored in the shift sequence.The person who replenishes the PSA arrives at 8 hrs and 12 hrs every day to pick up empty kanbans (kanban cards) and leave behind full ones. In this case, the pull interval amounts to 4 hours. * @nullable */ pullIntervalInMinutes?: DeserializedType | null; /** * (Automotive) Unloading Point. * Describes the unloading point that is communicated to the vendor in the corresponding release order (forecast delivery schedule, JIT delivery schedule, or kanban summarized JIT call). * Unloading points in the goods receipt process are understood to be the place where delivered goods are physically unloaded.The unloading point entered is transmitted to the vendor in the forecast delivery schedule, the JIT delivery schedule, or the kanban summarized JIT call.The unloading point is copied from the referenced scheduling agreement or summarized JIT call for the (Automotive) goods receipt process. You can use it as a selection criterion.You must enter the plant and the storage location before you can enter the Automotive unloading point in an MM scheduling agreement item.The permissible (Automotive) unloading points are determined from the staging areas, which you can maintain in Customizing for Logistics Execution.Staging areas were originally organizational units for Logistics Execution. They are now used - described as (Automotive) unloading point - to represent unloading points in the Automotive environment.NoteThe following terms are used synonymously:Unloading point (Automotive) <-> Staging area (Logistics Execution)Unloading zone (Automotive) <-> Door (WM/Logistics Execution)For further information on the use of (Automotive) unloading zones, see the SAP Library under SAP Automotive -> MM Scheduling Agreement Enhancements.The following example describes how you can use (Automotive) unloading points in MM scheduling agreement items:Warehouse number 001 is assigned to the combination plant 0001/storage location 0001 in Customizing for the Enterprise Structure, under Assignment -> Logistics Execution -> Assign warehouse number to plant/storage location.The staging areas (or Automotive unloading points) A1, A2, and A3 have been created in Customizing for Logistics Execution, under Warehouse Management -> Master Data -> Define material staging areas.Plant 0001 and storage location 0001 have been entered in the MM scheduling agreement item.ResultThe system determines the warehouse number and then the corresponding staging areas (or Automotive unloading points) from the plant/storage location combination.Unloading points A1, A2, and A3 are proposed when you use the input help when editing scheduling agreements.The unloading point selected is transmitted to the vendor in the delivery schedule. * Maximum length: 10. * @nullable */ unloadingWarehouseStagingArea?: DeserializedType | null; /** * Address for Supply Area. * Maximum length: 10. * @nullable */ productionSupplyAreaAddressId?: DeserializedType | null; /** * Last Change Timestamp. * @nullable */ lastChangeDateTime?: DeserializedType | null; /** * Loading Point. * Maximum length: 20. * @nullable */ automotiveLoadingPoint?: DeserializedType | null; /** * One-to-one navigation property to the [[ProductionSupplyAreaAddress]] entity. */ toProductionSupplyAreaAddress?: ProductionSupplyAreaAddress | null; /** * One-to-many navigation property to the [[ProductionSupplyAreaText]] entity. */ toProductionSupplyAreaText: ProductionSupplyAreaText[]; } export interface ProductionSupplyAreaType { productionSupplyArea: DeserializedType; plant: DeserializedType; storageLocation?: DeserializedType | null; productionSupplyAreaRespPerson?: DeserializedType | null; unloadingPointName?: DeserializedType | null; factoryCalendar?: DeserializedType | null; shiftGrouping?: DeserializedType | null; shiftSequence?: DeserializedType | null; pullIntervalInWorkdays?: DeserializedType | null; pullIntervalInMinutes?: DeserializedType | null; unloadingWarehouseStagingArea?: DeserializedType | null; productionSupplyAreaAddressId?: DeserializedType | null; lastChangeDateTime?: DeserializedType | null; automotiveLoadingPoint?: DeserializedType | null; toProductionSupplyAreaAddress?: ProductionSupplyAreaAddressType | null; toProductionSupplyAreaText: ProductionSupplyAreaTextType[]; } //# sourceMappingURL=ProductionSupplyArea.d.ts.map