public static final class JITCallHeader.JITCallHeaderBuilder extends Object
Modifier and Type | Method and Description |
---|---|
JITCallHeader.JITCallHeaderBuilder |
activeSupplier(String activeSupplier)
Constraints: Not nullable, Maximum length: 10
|
JITCallHeader |
build() |
JITCallHeader.JITCallHeaderBuilder |
compGrpMatl(String compGrpMatl)
Constraints: Not nullable, Maximum length: 40
|
JITCallHeader.JITCallHeaderBuilder |
createdByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
JITCallHeader.JITCallHeaderBuilder |
creationDateTime(ZonedDateTime creationDateTime)
Constraints: Not nullable, Precision: 7
|
JITCallHeader.JITCallHeaderBuilder |
customerPartnerDescription(String customerPartnerDescription)
Constraints: Not nullable, Maximum length: 30
|
JITCallHeader.JITCallHeaderBuilder |
deliveryCreationDate(LocalDateTime deliveryCreationDate)
Constraints: Not nullable, Precision: 0
|
JITCallHeader.JITCallHeaderBuilder |
distributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
JITCallHeader.JITCallHeaderBuilder |
division(String division)
Constraints: Not nullable, Maximum length: 2
|
JITCallHeader.JITCallHeaderBuilder |
externalJITCallNumber(String externalJITCallNumber)
Constraints: Not nullable, Maximum length: 35
|
JITCallHeader.JITCallHeaderBuilder |
internalJITCallNumber(String internalJITCallNumber)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
JITCallHeader.JITCallHeaderBuilder |
jitCallCompGrpDataTP(JITCallCompGrp... value)
Navigation property to_JITCallCompGrpDataTP for JITCallHeader to multiple
JITCallCompGrp.
|
JITCallHeader.JITCallHeaderBuilder |
jitCallRefTextHdrTP(JITCallRefTextHdr... value)
Navigation property to_JITCallRefTextHdrTP for JITCallHeader to multiple
JITCallRefTextHdr.
|
JITCallHeader.JITCallHeaderBuilder |
jITCallType(String jITCallType)
Constraints: Not nullable, Maximum length: 1
|
JITCallHeader.JITCallHeaderBuilder |
jITExtSequenceNumber(String jITExtSequenceNumber)
Constraints: Not nullable, Maximum length: 35
|
JITCallHeader.JITCallHeaderBuilder |
jITExtStatusAtSupplier(String jITExtStatusAtSupplier)
Constraints: Not nullable, Maximum length: 4
|
JITCallHeader.JITCallHeaderBuilder |
jITExtStatusUpdtdOn(ZonedDateTime jITExtStatusUpdtdOn)
Constraints: Not nullable, Precision: 7
|
JITCallHeader.JITCallHeaderBuilder |
jITIntProcessingStatus(String jITIntProcessingStatus)
Constraints: Not nullable, Maximum length: 5
|
JITCallHeader.JITCallHeaderBuilder |
jITIntStatusUpdtdOn(ZonedDateTime jITIntStatusUpdtdOn)
Constraints: Not nullable, Precision: 7
|
JITCallHeader.JITCallHeaderBuilder |
jITLifecycleStatus(String jITLifecycleStatus)
Constraints: Not nullable, Maximum length: 1
|
JITCallHeader.JITCallHeaderBuilder |
lastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
JITCallHeader.JITCallHeaderBuilder |
lastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
JITCallHeader.JITCallHeaderBuilder |
material(String material)
Constraints: Not nullable, Maximum length: 40
|
JITCallHeader.JITCallHeaderBuilder |
materialAvailabilityDate(LocalDateTime materialAvailabilityDate)
Constraints: Not nullable, Precision: 0
|
JITCallHeader.JITCallHeaderBuilder |
materialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35
|
JITCallHeader.JITCallHeaderBuilder |
matlUsageIndicator(String matlUsageIndicator)
Constraints: Not nullable, Maximum length: 3
|
JITCallHeader.JITCallHeaderBuilder |
plannedShippingDateTime(ZonedDateTime plannedShippingDateTime)
Constraints: Not nullable, Precision: 7
|
JITCallHeader.JITCallHeaderBuilder |
plant(String plant)
Constraints: Not nullable, Maximum length: 4
|
JITCallHeader.JITCallHeaderBuilder |
requirementDateTime(ZonedDateTime requirementDateTime)
Constraints: Not nullable, Precision: 7
|
JITCallHeader.JITCallHeaderBuilder |
salesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
JITCallHeader.JITCallHeaderBuilder |
shipToParty(String shipToParty)
Constraints: Not nullable, Maximum length: 10
|
JITCallHeader.JITCallHeaderBuilder |
soldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
String |
toString() |
JITCallHeader.JITCallHeaderBuilder |
vehicleIdentificationNumber(String vehicleIdentificationNumber)
Constraints: Not nullable, Maximum length: 35
|
JITCallHeader.JITCallHeaderBuilder |
vehicleModel(String vehicleModel)
Constraints: Not nullable, Maximum length: 40
|
@Nonnull public JITCallHeader.JITCallHeaderBuilder jitCallCompGrpDataTP(JITCallCompGrp... value)
value
- The JITCallCompGrps to build this JITCallHeader with.@Nonnull public JITCallHeader.JITCallHeaderBuilder jitCallRefTextHdrTP(JITCallRefTextHdr... value)
value
- The JITCallRefTextHdrs to build this JITCallHeader with.public JITCallHeader.JITCallHeaderBuilder internalJITCallNumber(@Nullable String internalJITCallNumber)
Original property name from the Odata EDM: InternalJITCallNumber
The system assigns this number internally and uses it for processing calls.
this
.public JITCallHeader.JITCallHeaderBuilder externalJITCallNumber(@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.
this
.public JITCallHeader.JITCallHeaderBuilder jITCallType(@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.
an internal call.this
.public JITCallHeader.JITCallHeaderBuilder shipToParty(@Nullable String shipToParty)
Original property name from the Odata EDM: ShipToParty
this
.public JITCallHeader.JITCallHeaderBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
this
.public JITCallHeader.JITCallHeaderBuilder customerPartnerDescription(@Nullable String customerPartnerDescription)
Original property name from the Odata EDM: CustomerPartnerDescription
The system uses this number to automatically determine the ship-to party.
this
.public JITCallHeader.JITCallHeaderBuilder activeSupplier(@Nullable String activeSupplier)
Original property name from the Odata EDM: ActiveSupplier
this
.public JITCallHeader.JITCallHeaderBuilder matlUsageIndicator(@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
this
.public JITCallHeader.JITCallHeaderBuilder salesOrganization(@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.
sales organization may include legal liability for products and customer claims.this
.public JITCallHeader.JITCallHeaderBuilder distributionChannel(@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.
wholesale, retail, or direct sales.this
.public JITCallHeader.JITCallHeaderBuilder division(@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.
areas and the business areas for a material, product, or service.this
.public JITCallHeader.JITCallHeaderBuilder jITLifecycleStatus(@Nullable String jITLifecycleStatus)
Original property name from the Odata EDM: JITLifecycleStatus
Active, Completed, or Cancelled.this
.public JITCallHeader.JITCallHeaderBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this
.public JITCallHeader.JITCallHeaderBuilder creationDateTime(@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.
this
.public JITCallHeader.JITCallHeaderBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
this
.public JITCallHeader.JITCallHeaderBuilder lastChangeDateTime(@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.
this
.public JITCallHeader.JITCallHeaderBuilder jITExtSequenceNumber(@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.
call number, which clearly identifies a product, the sequence number determines the production sequence at the sequenced JIT call customer.this
.public JITCallHeader.JITCallHeaderBuilder vehicleIdentificationNumber(@Nullable String vehicleIdentificationNumber)
Original property name from the Odata EDM: VehicleIdentificationNumber
this
.public JITCallHeader.JITCallHeaderBuilder vehicleModel(@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.
this
.public JITCallHeader.JITCallHeaderBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.public JITCallHeader.JITCallHeaderBuilder jITExtStatusAtSupplier(@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.
this
.public JITCallHeader.JITCallHeaderBuilder jITIntProcessingStatus(@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.
this
.public JITCallHeader.JITCallHeaderBuilder compGrpMatl(@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).
delivered to the customer as a physical object.this
.public JITCallHeader.JITCallHeaderBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this
.public JITCallHeader.JITCallHeaderBuilder materialByCustomer(@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.
this
.public JITCallHeader.JITCallHeaderBuilder deliveryCreationDate(@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
this
.public JITCallHeader.JITCallHeaderBuilder requirementDateTime(@Nullable ZonedDateTime requirementDateTime)
Original property name from the Odata EDM: RequirementDateTime
supply area.this
.public JITCallHeader.JITCallHeaderBuilder plannedShippingDateTime(@Nullable ZonedDateTime plannedShippingDateTime)
Original property name from the Odata EDM: PlannedShippingDateTime
this
.public JITCallHeader.JITCallHeaderBuilder materialAvailabilityDate(@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.
this
.public JITCallHeader.JITCallHeaderBuilder jITExtStatusUpdtdOn(@Nullable ZonedDateTime jITExtStatusUpdtdOn)
Original property name from the Odata EDM: JITExtStatusUpdtdOn
this
.public JITCallHeader.JITCallHeaderBuilder jITIntStatusUpdtdOn(@Nullable ZonedDateTime jITIntStatusUpdtdOn)
Original property name from the Odata EDM: JITIntStatusUpdtdOn
this
.public JITCallHeader build()
Copyright © 2020 SAP SE. All rights reserved.