public class JITCallHeader extends VdmEntity<JITCallHeader>
Original entity name from the Odata EDM: A_JITCallHeaderType
Modifier and Type | Class and Description |
---|---|
static class |
JITCallHeader.JITCallHeaderBuilder
Helper class to allow for fluent creation of JITCallHeader instances.
|
Modifier and Type | Field and Description |
---|---|
static JITCallHeaderField<String> |
ACTIVE_SUPPLIER
Use with available fluent helpers to apply the ActiveSupplier field to query operations.
|
static JITCallHeaderSelectable |
ALL_FIELDS
Selector for all available fields of JITCallHeader.
|
static JITCallHeaderField<String> |
COMP_GRP_MATL
Use with available fluent helpers to apply the CompGrpMatl field to query operations.
|
static JITCallHeaderField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static JITCallHeaderField<ZonedDateTime> |
CREATION_DATE_TIME
Use with available fluent helpers to apply the CreationDateTime field to query operations.
|
static JITCallHeaderField<String> |
CUSTOMER_PARTNER_DESCRIPTION
Use with available fluent helpers to apply the CustomerPartnerDescription field to query operations.
|
static JITCallHeaderField<LocalDateTime> |
DELIVERY_CREATION_DATE
Use with available fluent helpers to apply the DeliveryCreationDate field to query operations.
|
static JITCallHeaderField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static JITCallHeaderField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static JITCallHeaderField<String> |
EXTERNAL_JIT_CALL_NUMBER
Use with available fluent helpers to apply the ExternalJITCallNumber field to query operations.
|
static JITCallHeaderField<String> |
INTERNAL_JIT_CALL_NUMBER
Use with available fluent helpers to apply the InternalJITCallNumber field to query operations.
|
static JITCallHeaderField<String> |
JIT_CALL_TYPE
Use with available fluent helpers to apply the JITCallType field to query operations.
|
static JITCallHeaderField<String> |
JIT_EXT_SEQUENCE_NUMBER
Use with available fluent helpers to apply the JITExtSequenceNumber field to query operations.
|
static JITCallHeaderField<String> |
JIT_EXT_STATUS_AT_SUPPLIER
Use with available fluent helpers to apply the JITExtStatusAtSupplier field to query operations.
|
static JITCallHeaderField<ZonedDateTime> |
JIT_EXT_STATUS_UPDTD_ON
Use with available fluent helpers to apply the JITExtStatusUpdtdOn field to query operations.
|
static JITCallHeaderField<String> |
JIT_INT_PROCESSING_STATUS
Use with available fluent helpers to apply the JITIntProcessingStatus field to query operations.
|
static JITCallHeaderField<ZonedDateTime> |
JIT_INT_STATUS_UPDTD_ON
Use with available fluent helpers to apply the JITIntStatusUpdtdOn field to query operations.
|
static JITCallHeaderField<String> |
JIT_LIFECYCLE_STATUS
Use with available fluent helpers to apply the JITLifecycleStatus field to query operations.
|
static JITCallHeaderField<ZonedDateTime> |
LAST_CHANGE_DATE_TIME
Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
|
static JITCallHeaderField<String> |
LAST_CHANGED_BY_USER
Use with available fluent helpers to apply the LastChangedByUser field to query operations.
|
static JITCallHeaderField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static JITCallHeaderField<LocalDateTime> |
MATERIAL_AVAILABILITY_DATE
Use with available fluent helpers to apply the MaterialAvailabilityDate field to query operations.
|
static JITCallHeaderField<String> |
MATERIAL_BY_CUSTOMER
Use with available fluent helpers to apply the MaterialByCustomer field to query operations.
|
static JITCallHeaderField<String> |
MATL_USAGE_INDICATOR
Use with available fluent helpers to apply the MatlUsageIndicator field to query operations.
|
static JITCallHeaderField<ZonedDateTime> |
PLANNED_SHIPPING_DATE_TIME
Use with available fluent helpers to apply the PlannedShippingDateTime field to query operations.
|
static JITCallHeaderField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static JITCallHeaderField<ZonedDateTime> |
REQUIREMENT_DATE_TIME
Use with available fluent helpers to apply the RequirementDateTime field to query operations.
|
static JITCallHeaderField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static JITCallHeaderField<String> |
SHIP_TO_PARTY
Use with available fluent helpers to apply the ShipToParty field to query operations.
|
static JITCallHeaderField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static JITCallHeaderLink<JITCallCompGrp> |
TO_JIT_CALL_COMP_GRP_DATA_TP
Use with available fluent helpers to apply the to_JITCallCompGrpDataTP navigation property to query
operations.
|
static JITCallHeaderLink<JITCallRefTextHdr> |
TO_JIT_CALL_REF_TEXT_HDR_TP
Use with available fluent helpers to apply the to_JITCallRefTextHdrTP navigation property to query
operations.
|
static JITCallHeaderField<String> |
VEHICLE_IDENTIFICATION_NUMBER
Use with available fluent helpers to apply the VehicleIdentificationNumber field to query operations.
|
static JITCallHeaderField<String> |
VEHICLE_MODEL
Use with available fluent helpers to apply the VehicleModel field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
JITCallHeader() |
JITCallHeader(String internalJITCallNumber,
String externalJITCallNumber,
String jITCallType,
String shipToParty,
String soldToParty,
String customerPartnerDescription,
String activeSupplier,
String matlUsageIndicator,
String salesOrganization,
String distributionChannel,
String division,
String jITLifecycleStatus,
String createdByUser,
ZonedDateTime creationDateTime,
String lastChangedByUser,
ZonedDateTime lastChangeDateTime,
String jITExtSequenceNumber,
String vehicleIdentificationNumber,
String vehicleModel,
String plant,
String jITExtStatusAtSupplier,
String jITIntProcessingStatus,
String compGrpMatl,
String material,
String materialByCustomer,
LocalDateTime deliveryCreationDate,
ZonedDateTime requirementDateTime,
ZonedDateTime plannedShippingDateTime,
LocalDateTime materialAvailabilityDate,
ZonedDateTime jITExtStatusUpdtdOn,
ZonedDateTime jITIntStatusUpdtdOn,
List<JITCallCompGrp> toJITCallCompGrpDataTP,
List<JITCallRefTextHdr> toJITCallRefTextHdrTP) |
Modifier and Type | Method and Description |
---|---|
void |
addJITCallCompGrpDataTP(JITCallCompGrp... entity)
Adds elements to the list of associated JITCallCompGrp entities.
|
void |
addJITCallRefTextHdrTP(JITCallRefTextHdr... entity)
Adds elements to the list of associated JITCallRefTextHdr entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static JITCallHeader.JITCallHeaderBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<JITCallCompGrp> |
fetchJITCallCompGrpDataTP()
Fetches the JITCallCompGrp entities (one to many) associated with this entity.
|
List<JITCallRefTextHdr> |
fetchJITCallRefTextHdrTP()
Fetches the JITCallRefTextHdr entities (one to many) associated with this entity.
|
static <T> JITCallHeaderField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getActiveSupplier()
Constraints: Not nullable, Maximum length: 10
|
String |
getCompGrpMatl()
Constraints: Not nullable, Maximum length: 40
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
ZonedDateTime |
getCreationDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getCustomerPartnerDescription()
Constraints: Not nullable, Maximum length: 30
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
LocalDateTime |
getDeliveryCreationDate()
Constraints: Not nullable, Precision: 0
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
String |
getDistributionChannel()
Constraints: Not nullable, Maximum length: 2
|
String |
getDivision()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getExternalJITCallNumber()
Constraints: Not nullable, Maximum length: 35
|
String |
getInternalJITCallNumber()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<List<JITCallCompGrp>> |
getJITCallCompGrpDataTPIfPresent()
Retrieval of associated JITCallCompGrp entities (one to many).
|
List<JITCallCompGrp> |
getJITCallCompGrpDataTPOrFetch()
Retrieval of associated JITCallCompGrp entities (one to many).
|
io.vavr.control.Option<List<JITCallRefTextHdr>> |
getJITCallRefTextHdrTPIfPresent()
Retrieval of associated JITCallRefTextHdr entities (one to many).
|
List<JITCallRefTextHdr> |
getJITCallRefTextHdrTPOrFetch()
Retrieval of associated JITCallRefTextHdr entities (one to many).
|
String |
getJITCallType()
Constraints: Not nullable, Maximum length: 1
|
String |
getJITExtSequenceNumber()
Constraints: Not nullable, Maximum length: 35
|
String |
getJITExtStatusAtSupplier()
Constraints: Not nullable, Maximum length: 4
|
ZonedDateTime |
getJITExtStatusUpdtdOn()
Constraints: Not nullable, Precision: 7
|
String |
getJITIntProcessingStatus()
Constraints: Not nullable, Maximum length: 5
|
ZonedDateTime |
getJITIntStatusUpdtdOn()
Constraints: Not nullable, Precision: 7
|
String |
getJITLifecycleStatus()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
ZonedDateTime |
getLastChangeDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
LocalDateTime |
getMaterialAvailabilityDate()
Constraints: Not nullable, Precision: 0
|
String |
getMaterialByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getMatlUsageIndicator()
Constraints: Not nullable, Maximum length: 3
|
ZonedDateTime |
getPlannedShippingDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getPlant()
Constraints: Not nullable, Maximum length: 4
|
ZonedDateTime |
getRequirementDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getShipToParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
Class<JITCallHeader> |
getType() |
String |
getVehicleIdentificationNumber()
Constraints: Not nullable, Maximum length: 35
|
String |
getVehicleModel()
Constraints: Not nullable, Maximum length: 40
|
int |
hashCode() |
void |
setActiveSupplier(String activeSupplier)
Constraints: Not nullable, Maximum length: 10
|
void |
setCompGrpMatl(String compGrpMatl)
Constraints: Not nullable, Maximum length: 40
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDateTime(ZonedDateTime creationDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setCustomerPartnerDescription(String customerPartnerDescription)
Constraints: Not nullable, Maximum length: 30
|
void |
setDeliveryCreationDate(LocalDateTime deliveryCreationDate)
Constraints: Not nullable, Precision: 0
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setDivision(String division)
Constraints: Not nullable, Maximum length: 2
|
void |
setExternalJITCallNumber(String externalJITCallNumber)
Constraints: Not nullable, Maximum length: 35
|
void |
setInternalJITCallNumber(String internalJITCallNumber)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setJITCallCompGrpDataTP(List<JITCallCompGrp> value)
Overwrites the list of associated JITCallCompGrp entities for the loaded navigation property
to_JITCallCompGrpDataTP.
|
void |
setJITCallRefTextHdrTP(List<JITCallRefTextHdr> value)
Overwrites the list of associated JITCallRefTextHdr entities for the loaded navigation property
to_JITCallRefTextHdrTP.
|
void |
setJITCallType(String jITCallType)
Constraints: Not nullable, Maximum length: 1
|
void |
setJITExtSequenceNumber(String jITExtSequenceNumber)
Constraints: Not nullable, Maximum length: 35
|
void |
setJITExtStatusAtSupplier(String jITExtStatusAtSupplier)
Constraints: Not nullable, Maximum length: 4
|
void |
setJITExtStatusUpdtdOn(ZonedDateTime jITExtStatusUpdtdOn)
Constraints: Not nullable, Precision: 7
|
void |
setJITIntProcessingStatus(String jITIntProcessingStatus)
Constraints: Not nullable, Maximum length: 5
|
void |
setJITIntStatusUpdtdOn(ZonedDateTime jITIntStatusUpdtdOn)
Constraints: Not nullable, Precision: 7
|
void |
setJITLifecycleStatus(String jITLifecycleStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setLastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setLastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialAvailabilityDate(LocalDateTime materialAvailabilityDate)
Constraints: Not nullable, Precision: 0
|
void |
setMaterialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setMatlUsageIndicator(String matlUsageIndicator)
Constraints: Not nullable, Maximum length: 3
|
void |
setPlannedShippingDateTime(ZonedDateTime plannedShippingDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setPlant(String plant)
Constraints: Not nullable, Maximum length: 4
|
void |
setRequirementDateTime(ZonedDateTime requirementDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setShipToParty(String shipToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setSoldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setVehicleIdentificationNumber(String vehicleIdentificationNumber)
Constraints: Not nullable, Maximum length: 35
|
void |
setVehicleModel(String vehicleModel)
Constraints: Not nullable, Maximum length: 40
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final JITCallHeaderSelectable ALL_FIELDS
public static final JITCallHeaderField<String> INTERNAL_JIT_CALL_NUMBER
public static final JITCallHeaderField<String> EXTERNAL_JIT_CALL_NUMBER
public static final JITCallHeaderField<String> JIT_CALL_TYPE
public static final JITCallHeaderField<String> SHIP_TO_PARTY
public static final JITCallHeaderField<String> SOLD_TO_PARTY
public static final JITCallHeaderField<String> CUSTOMER_PARTNER_DESCRIPTION
public static final JITCallHeaderField<String> ACTIVE_SUPPLIER
public static final JITCallHeaderField<String> MATL_USAGE_INDICATOR
public static final JITCallHeaderField<String> SALES_ORGANIZATION
public static final JITCallHeaderField<String> DISTRIBUTION_CHANNEL
public static final JITCallHeaderField<String> DIVISION
public static final JITCallHeaderField<String> JIT_LIFECYCLE_STATUS
public static final JITCallHeaderField<String> CREATED_BY_USER
public static final JITCallHeaderField<ZonedDateTime> CREATION_DATE_TIME
public static final JITCallHeaderField<String> LAST_CHANGED_BY_USER
public static final JITCallHeaderField<ZonedDateTime> LAST_CHANGE_DATE_TIME
public static final JITCallHeaderField<String> JIT_EXT_SEQUENCE_NUMBER
public static final JITCallHeaderField<String> VEHICLE_IDENTIFICATION_NUMBER
public static final JITCallHeaderField<String> VEHICLE_MODEL
public static final JITCallHeaderField<String> PLANT
public static final JITCallHeaderField<String> JIT_EXT_STATUS_AT_SUPPLIER
public static final JITCallHeaderField<String> JIT_INT_PROCESSING_STATUS
public static final JITCallHeaderField<String> COMP_GRP_MATL
public static final JITCallHeaderField<String> MATERIAL
public static final JITCallHeaderField<String> MATERIAL_BY_CUSTOMER
public static final JITCallHeaderField<LocalDateTime> DELIVERY_CREATION_DATE
public static final JITCallHeaderField<ZonedDateTime> REQUIREMENT_DATE_TIME
public static final JITCallHeaderField<ZonedDateTime> PLANNED_SHIPPING_DATE_TIME
public static final JITCallHeaderField<LocalDateTime> MATERIAL_AVAILABILITY_DATE
public static final JITCallHeaderField<ZonedDateTime> JIT_EXT_STATUS_UPDTD_ON
public static final JITCallHeaderField<ZonedDateTime> JIT_INT_STATUS_UPDTD_ON
public static final JITCallHeaderLink<JITCallCompGrp> TO_JIT_CALL_COMP_GRP_DATA_TP
public static final JITCallHeaderLink<JITCallRefTextHdr> TO_JIT_CALL_REF_TEXT_HDR_TP
public JITCallHeader()
public JITCallHeader(@Nullable String internalJITCallNumber, @Nullable String externalJITCallNumber, @Nullable String jITCallType, @Nullable String shipToParty, @Nullable String soldToParty, @Nullable String customerPartnerDescription, @Nullable String activeSupplier, @Nullable String matlUsageIndicator, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String division, @Nullable String jITLifecycleStatus, @Nullable String createdByUser, @Nullable ZonedDateTime creationDateTime, @Nullable String lastChangedByUser, @Nullable ZonedDateTime lastChangeDateTime, @Nullable String jITExtSequenceNumber, @Nullable String vehicleIdentificationNumber, @Nullable String vehicleModel, @Nullable String plant, @Nullable String jITExtStatusAtSupplier, @Nullable String jITIntProcessingStatus, @Nullable String compGrpMatl, @Nullable String material, @Nullable String materialByCustomer, @Nullable LocalDateTime deliveryCreationDate, @Nullable ZonedDateTime requirementDateTime, @Nullable ZonedDateTime plannedShippingDateTime, @Nullable LocalDateTime materialAvailabilityDate, @Nullable ZonedDateTime jITExtStatusUpdtdOn, @Nullable ZonedDateTime jITIntStatusUpdtdOn, List<JITCallCompGrp> toJITCallCompGrpDataTP, List<JITCallRefTextHdr> toJITCallRefTextHdrTP)
@Nonnull public Class<JITCallHeader> getType()
getType
in class VdmObject<JITCallHeader>
public void setInternalJITCallNumber(@Nullable String internalJITCallNumber)
Original property name from the Odata EDM: InternalJITCallNumber
The system assigns this number internally and uses it for processing calls.
internalJITCallNumber
- Uniquely identifies a JIT call.public void setExternalJITCallNumber(@Nullable String externalJITCallNumber)
Original property name from the Odata EDM: ExternalJITCallNumber
· Sequenced JIT call (seqJC)The external call number is generally the production number of the vehicle.· Summarized JIT call (sumJC)The external call number does not have a direct reference to the finished product, but is simply a call reference number.
externalJITCallNumber
- Specifies the call number, which clearly identifies a call at the JIT customer.public void setJITCallType(@Nullable String jITCallType)
Original property name from the Odata EDM: JITCallType
•Sequenced JIT call (seqJC)This type of call corresponds to a sequence call in which the external call number produces the reference to the JIT customer's finished product. The external sequence number of the call specifies the position in the OEM's production sequence. You deliver the components groups you have produced to the JIT customer in this sequence.•Summarized JIT call (sumJC)A call of this type contains pairs of date/quantity without reference to the finished product and in which the external call number is a reference number for the call. You control processes, such as the delivery with this reference number.•Internal callYou can create an internal call if you want to produce components groups in advance and store them temporarily. If a customer sends a concrete call, you can switch the completed components groups from the internal call with the components groups from the customer call. As a rule, internal calls are only relevant for the sequenced JIT call process.You can assign a default value for the call type to the JIT customer in Basic data.
jITCallType
- Specifies whether the call in question is a sequenced JIT call (seqJC), a summarized JIT call (sumJC)
or an internal call.public void setShipToParty(@Nullable String shipToParty)
Original property name from the Odata EDM: ShipToParty
shipToParty
- The party who receives delivery of the goods.public void setSoldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
soldToParty
- Sold-To Partypublic void setCustomerPartnerDescription(@Nullable String customerPartnerDescription)
Original property name from the Odata EDM: CustomerPartnerDescription
The system uses this number to automatically determine the ship-to party.
customerPartnerDescription
- Sold-to party number sent in by the customer in delivery schedules.public void setActiveSupplier(@Nullable String activeSupplier)
Original property name from the Odata EDM: ActiveSupplier
activeSupplier
- Partner Description of Supplierpublic void setMatlUsageIndicator(@Nullable String matlUsageIndicator)
Original property name from the Odata EDM: MatlUsageIndicator
The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
matlUsageIndicator
- Defines how the material is used.public void setSalesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
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.
salesOrganization
- 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.public void setDistributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
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.
distributionChannel
- The way in which products or services reach the customer. Typical examples of distribution channels
are wholesale, retail, or direct sales.public void setDivision(@Nullable String division)
Original property name from the Odata EDM: Division
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.
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.public void setJITLifecycleStatus(@Nullable String jITLifecycleStatus)
Original property name from the Odata EDM: JITLifecycleStatus
jITLifecycleStatus
- Indicates the status of the life cycle of the JIT call. The status could be one among In Creation,
Active, Completed, or Cancelled.public void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- User Namepublic void setCreationDateTime(@Nullable ZonedDateTime creationDateTime)
Original property name from the Odata EDM: CreationDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
creationDateTime
- The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).public void setLastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
lastChangedByUser
- User Namepublic void setLastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
lastChangeDateTime
- The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).public void setJITExtSequenceNumber(@Nullable String jITExtSequenceNumber)
Original property name from the Odata EDM: JITExtSequenceNumber
The sequenced JIT call customer transmits the sequence number with a sequenced JIT call. The number can change up until the production go-ahead, if for example, a vehicle has to be reworked after painting. After the production go-ahead you use the sequence number, for example, to package or pick products in the correct sequence.If necessary, there is an upper limit when allocating sequence numbers. In this case the sequence numbers are repeated in specific time intervals.
jITExtSequenceNumber
- Indicates the sequence number that customers allocate to the finished product. Compared with the
external call number, which clearly identifies a product, the sequence number determines the
production sequence at the sequenced JIT call customer.public void setVehicleIdentificationNumber(@Nullable String vehicleIdentificationNumber)
Original property name from the Odata EDM: VehicleIdentificationNumber
vehicleIdentificationNumber
- Unique Identification number , that the OEM assigns the vehicle.public void setVehicleModel(@Nullable String vehicleModel)
Original property name from the Odata EDM: VehicleModel
A vehicle model can be a vehicle type that has not yet been configured. It can also be vehicle type for which some main configuration characteristics have already been created in the system.SAP recommends that you create your vehicle as generally as possible so that configuration changes are still possible to the vehicle during the sales period.You have defined the vehicle type 'Golf'. This vehicle is not a configured vehicle type. If the end customer receives a quotation for a red Gold but would prefer a blue Golf, it is still possible to change the color of the vehicle. If, however, you create the vehicle types 'red Golf' and 'blue Golf' in your system, therefore using predefined characteristics, the changes to the quotation represent changes to the vehicle model and cannot be integrated.
vehicleModel
- Alphanumerical key that clearly identifies the Vehicle model.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setJITExtStatusAtSupplier(@Nullable String jITExtStatusAtSupplier)
Original property name from the Odata EDM: JITExtStatusAtSupplier
Examples for an external status are forecast, production release, shipping release, cancellation and repeat order.If you receive sequenced JIT calls from various customers, the external status information transmitted generally has varying names and formats. The system resets the incoming status information in the external status using a table defined in the basic data. In this way the external status is the status you defined for the production progress at the manufacturer.
jITExtStatusAtSupplier
- Describes the production progress of the finished product at the customer.public void setJITIntProcessingStatus(@Nullable String jITIntProcessingStatus)
Original property name from the Odata EDM: JITIntProcessingStatus
In Customizing, you specify which actions result in which internal processing statuses. When the system processes an inbound JIT call, it determines a new external status. This change of external status triggers a specific supplier action, which in turn, results in a new internal processing status.Examples for internal processing statuses are JIT call generated, component list printed, production completed, and so on.
jITIntProcessingStatus
- Indicates the progress made on a components group at the supplier's site.public void setCompGrpMatl(@Nullable String compGrpMatl)
Original property name from the Odata EDM: CompGrpMatl
With the components group material, you can reproduce a logical link to the data, which is the same for several call components. This can be, for example, the delivery data. The components group material is generally a configurable material and the call components are the corresponding configurable materials. If you only receive a small number of call components, you can also use the call component directly as a components group material. The components group material has the following purposes in the JIT process:It serves to derive the production line, if you enter JIT monitoring or the progress confirmation via the production line.In sequenced JIT calls it is used to determine the packing instructions, if you want to create a delivery with handling units (HUs).It is used to determine the storage locations, if you want to carry out a stock transfer using the action Carry out backflush (BFLU) (see also Carrying out the backflush).
compGrpMatl
- Specifies the material number of the components group that is produced from the call components and
delivered to the customer as a physical object.public void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setMaterialByCustomer(@Nullable String materialByCustomer)
Original property name from the Odata EDM: MaterialByCustomer
The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
materialByCustomer
- The identifier that the customer uses to identify a particular material.public void setDeliveryCreationDate(@Nullable LocalDateTime deliveryCreationDate)
Original property name from the Odata EDM: DeliveryCreationDate
During delivery processing, the system automatically proposes the delivery creation date for all schedule lines with the same goods issue date by taking the earliest of the following dates:The material availability dateThe transportation planning date
deliveryCreationDate
- The day on which you create a delivery.public void setRequirementDateTime(@Nullable ZonedDateTime requirementDateTime)
Original property name from the Odata EDM: RequirementDateTime
requirementDateTime
- Indicates the date and time by when the material requested by the JIT call is required at the customer
supply area.public void setPlannedShippingDateTime(@Nullable ZonedDateTime plannedShippingDateTime)
Original property name from the Odata EDM: PlannedShippingDateTime
plannedShippingDateTime
- Determines the planned shipping date and time of goods.public void setMaterialAvailabilityDate(@Nullable LocalDateTime materialAvailabilityDate)
Original property name from the Odata EDM: MaterialAvailabilityDate
The system uses the material availability date to generate automatic production and purchasing requirements. The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation.The system proposes the material availability date. You can change the date manually in the sales document.The picking date is the same as the material availability date.
materialAvailabilityDate
- The date by which sufficient quantities of the item must be available for picking to begin.public void setJITExtStatusUpdtdOn(@Nullable ZonedDateTime jITExtStatusUpdtdOn)
Original property name from the Odata EDM: JITExtStatusUpdtdOn
jITExtStatusUpdtdOn
- Indicates the date and time on which the external status of the JIT call was last updated.public void setJITIntStatusUpdtdOn(@Nullable ZonedDateTime jITIntStatusUpdtdOn)
Original property name from the Odata EDM: JITIntStatusUpdtdOn
jITIntStatusUpdtdOn
- Indicates the date and time on which the internal processing status of the JIT call was last updated.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<JITCallHeader>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<JITCallHeader>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<JITCallHeader>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<JITCallHeader>
@Nonnull public static <T> JITCallHeaderField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> JITCallHeaderField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<JITCallHeader>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<JITCallHeader>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<JITCallHeader>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<JITCallHeader>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<JITCallHeader>
@Nonnull public List<JITCallCompGrp> fetchJITCallCompGrpDataTP() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<JITCallCompGrp> getJITCallCompGrpDataTPOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_JITCallCompGrpDataTP of a queried JITCallHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<JITCallCompGrp>> getJITCallCompGrpDataTPIfPresent()
If the navigation property for an entity JITCallHeader has not been resolved yet, this method will not
query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setJITCallCompGrpDataTP(@Nonnull List<JITCallCompGrp> value)
If the navigation property to_JITCallCompGrpDataTP of a queried JITCallHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of JITCallCompGrp entities.public void addJITCallCompGrpDataTP(JITCallCompGrp... entity)
If the navigation property to_JITCallCompGrpDataTP of a queried JITCallHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of JITCallCompGrp entities.@Nonnull public List<JITCallRefTextHdr> fetchJITCallRefTextHdrTP() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<JITCallRefTextHdr> getJITCallRefTextHdrTPOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_JITCallRefTextHdrTP of a queried JITCallHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<JITCallRefTextHdr>> getJITCallRefTextHdrTPIfPresent()
If the navigation property for an entity JITCallHeader has not been resolved yet, this method will not
query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setJITCallRefTextHdrTP(@Nonnull List<JITCallRefTextHdr> value)
If the navigation property to_JITCallRefTextHdrTP of a queried JITCallHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of JITCallRefTextHdr entities.public void addJITCallRefTextHdrTP(JITCallRefTextHdr... entity)
If the navigation property to_JITCallRefTextHdrTP of a queried JITCallHeader is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of JITCallRefTextHdr entities.public static JITCallHeader.JITCallHeaderBuilder builder()
@Nullable public String getInternalJITCallNumber()
Original property name from the Odata EDM: InternalJITCallNumber
The system assigns this number internally and uses it for processing calls.
@Nullable public String getExternalJITCallNumber()
Original property name from the Odata EDM: ExternalJITCallNumber
· Sequenced JIT call (seqJC)The external call number is generally the production number of the vehicle.· Summarized JIT call (sumJC)The external call number does not have a direct reference to the finished product, but is simply a call reference number.
@Nullable public String getJITCallType()
Original property name from the Odata EDM: JITCallType
•Sequenced JIT call (seqJC)This type of call corresponds to a sequence call in which the external call number produces the reference to the JIT customer's finished product. The external sequence number of the call specifies the position in the OEM's production sequence. You deliver the components groups you have produced to the JIT customer in this sequence.•Summarized JIT call (sumJC)A call of this type contains pairs of date/quantity without reference to the finished product and in which the external call number is a reference number for the call. You control processes, such as the delivery with this reference number.•Internal callYou can create an internal call if you want to produce components groups in advance and store them temporarily. If a customer sends a concrete call, you can switch the completed components groups from the internal call with the components groups from the customer call. As a rule, internal calls are only relevant for the sequenced JIT call process.You can assign a default value for the call type to the JIT customer in Basic data.
@Nullable public String getShipToParty()
Original property name from the Odata EDM: ShipToParty
@Nullable public String getSoldToParty()
Original property name from the Odata EDM: SoldToParty
@Nullable public String getCustomerPartnerDescription()
Original property name from the Odata EDM: CustomerPartnerDescription
The system uses this number to automatically determine the ship-to party.
@Nullable public String getActiveSupplier()
Original property name from the Odata EDM: ActiveSupplier
@Nullable public String getMatlUsageIndicator()
Original property name from the Odata EDM: MatlUsageIndicator
The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.The same material, but with different uses, can be sold to the same customer in separate items or orders.Enter whether the material is:A spare, or replacement partA samplePart of a series, used in repetitive manufacturing
@Nullable public String getSalesOrganization()
Original property name from the Odata EDM: SalesOrganization
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.
@Nullable public String getDistributionChannel()
Original property name from the Odata EDM: DistributionChannel
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.
@Nullable public String getDivision()
Original property name from the Odata EDM: Division
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.
@Nullable public String getJITLifecycleStatus()
Original property name from the Odata EDM: JITLifecycleStatus
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public ZonedDateTime getCreationDateTime()
Original property name from the Odata EDM: CreationDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
@Nullable public String getLastChangedByUser()
Original property name from the Odata EDM: LastChangedByUser
@Nullable public ZonedDateTime getLastChangeDateTime()
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
@Nullable public String getJITExtSequenceNumber()
Original property name from the Odata EDM: JITExtSequenceNumber
The sequenced JIT call customer transmits the sequence number with a sequenced JIT call. The number can change up until the production go-ahead, if for example, a vehicle has to be reworked after painting. After the production go-ahead you use the sequence number, for example, to package or pick products in the correct sequence.If necessary, there is an upper limit when allocating sequence numbers. In this case the sequence numbers are repeated in specific time intervals.
@Nullable public String getVehicleIdentificationNumber()
Original property name from the Odata EDM: VehicleIdentificationNumber
@Nullable public String getVehicleModel()
Original property name from the Odata EDM: VehicleModel
A vehicle model can be a vehicle type that has not yet been configured. It can also be vehicle type for which some main configuration characteristics have already been created in the system.SAP recommends that you create your vehicle as generally as possible so that configuration changes are still possible to the vehicle during the sales period.You have defined the vehicle type 'Golf'. This vehicle is not a configured vehicle type. If the end customer receives a quotation for a red Gold but would prefer a blue Golf, it is still possible to change the color of the vehicle. If, however, you create the vehicle types 'red Golf' and 'blue Golf' in your system, therefore using predefined characteristics, the changes to the quotation represent changes to the vehicle model and cannot be integrated.
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public String getJITExtStatusAtSupplier()
Original property name from the Odata EDM: JITExtStatusAtSupplier
Examples for an external status are forecast, production release, shipping release, cancellation and repeat order.If you receive sequenced JIT calls from various customers, the external status information transmitted generally has varying names and formats. The system resets the incoming status information in the external status using a table defined in the basic data. In this way the external status is the status you defined for the production progress at the manufacturer.
@Nullable public String getJITIntProcessingStatus()
Original property name from the Odata EDM: JITIntProcessingStatus
In Customizing, you specify which actions result in which internal processing statuses. When the system processes an inbound JIT call, it determines a new external status. This change of external status triggers a specific supplier action, which in turn, results in a new internal processing status.Examples for internal processing statuses are JIT call generated, component list printed, production completed, and so on.
@Nullable public String getCompGrpMatl()
Original property name from the Odata EDM: CompGrpMatl
With the components group material, you can reproduce a logical link to the data, which is the same for several call components. This can be, for example, the delivery data. The components group material is generally a configurable material and the call components are the corresponding configurable materials. If you only receive a small number of call components, you can also use the call component directly as a components group material. The components group material has the following purposes in the JIT process:It serves to derive the production line, if you enter JIT monitoring or the progress confirmation via the production line.In sequenced JIT calls it is used to determine the packing instructions, if you want to create a delivery with handling units (HUs).It is used to determine the storage locations, if you want to carry out a stock transfer using the action Carry out backflush (BFLU) (see also Carrying out the backflush).
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getMaterialByCustomer()
Original property name from the Odata EDM: MaterialByCustomer
The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
@Nullable public LocalDateTime getDeliveryCreationDate()
Original property name from the Odata EDM: DeliveryCreationDate
During delivery processing, the system automatically proposes the delivery creation date for all schedule lines with the same goods issue date by taking the earliest of the following dates:The material availability dateThe transportation planning date
@Nullable public ZonedDateTime getRequirementDateTime()
Original property name from the Odata EDM: RequirementDateTime
@Nullable public ZonedDateTime getPlannedShippingDateTime()
Original property name from the Odata EDM: PlannedShippingDateTime
@Nullable public LocalDateTime getMaterialAvailabilityDate()
Original property name from the Odata EDM: MaterialAvailabilityDate
The system uses the material availability date to generate automatic production and purchasing requirements. The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation.The system proposes the material availability date. You can change the date manually in the sales document.The picking date is the same as the material availability date.
@Nullable public ZonedDateTime getJITExtStatusUpdtdOn()
Original property name from the Odata EDM: JITExtStatusUpdtdOn
@Nullable public ZonedDateTime getJITIntStatusUpdtdOn()
Original property name from the Odata EDM: JITIntStatusUpdtdOn
public String toString()
toString
in class VdmObject<JITCallHeader>
public boolean equals(Object o)
equals
in class VdmObject<JITCallHeader>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<JITCallHeader>
public int hashCode()
hashCode
in class VdmObject<JITCallHeader>
Copyright © 2020 SAP SE. All rights reserved.