public static final class ServiceOrder.ServiceOrderBuilder extends Object
Modifier and Type | Method and Description |
---|---|
ServiceOrder.ServiceOrderBuilder |
billToParty(String billToParty)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder |
build() |
ServiceOrder.ServiceOrderBuilder |
confirmation(ServiceOrderConfirmation... value)
Navigation property to_Confirmation for ServiceOrder to multiple
ServiceOrderConfirmation.
|
ServiceOrder.ServiceOrderBuilder |
contactPerson(String contactPerson)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
customerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
ServiceOrder.ServiceOrderBuilder |
defect(ServiceOrderDefect... value)
Navigation property to_Defect for ServiceOrder to multiple ServiceOrderDefect.
|
ServiceOrder.ServiceOrderBuilder |
distributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
ServiceOrder.ServiceOrderBuilder |
division(String division)
Constraints: Not nullable, Maximum length: 2
|
ServiceOrder.ServiceOrderBuilder |
item(ServiceOrderItem... value)
Navigation property to_Item for ServiceOrder to multiple ServiceOrderItem.
|
ServiceOrder.ServiceOrderBuilder |
language(String language)
Constraints: Not nullable, Maximum length: 2
|
ServiceOrder.ServiceOrderBuilder |
payerParty(String payerParty)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
personResponsible(ServiceOrderPersonResp... value)
Navigation property to_PersonResponsible for ServiceOrder to multiple
ServiceOrderPersonResp.
|
ServiceOrder.ServiceOrderBuilder |
pricingElement(ServiceOrderPriceElement... value)
Navigation property to_PricingElement for ServiceOrder to multiple
ServiceOrderPriceElement.
|
ServiceOrder.ServiceOrderBuilder |
purchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
ServiceOrder.ServiceOrderBuilder |
referenceObject(ServiceOrderRefObject... value)
Navigation property to_ReferenceObject for ServiceOrder to multiple
ServiceOrderRefObject.
|
ServiceOrder.ServiceOrderBuilder |
referenceServiceContract(String referenceServiceContract)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
referenceServiceOrder(String referenceServiceOrder)
Constraints: Not nullable, Maximum length: 80
|
ServiceOrder.ServiceOrderBuilder |
referenceServiceRequest(String referenceServiceRequest)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
refServiceOrderTemplate(String refServiceOrderTemplate)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
requestedServiceEndDateTime(ZonedDateTime requestedServiceEndDateTime)
Constraints: Not nullable, Precision: 0
|
ServiceOrder.ServiceOrderBuilder |
requestedServiceStartDateTime(ZonedDateTime requestedServiceStartDateTime)
Constraints: Not nullable, Precision: 0
|
ServiceOrder.ServiceOrderBuilder |
respyMgmtGlobalTeamID(String respyMgmtGlobalTeamID)
Constraints: Not nullable, Maximum length: 40
|
ServiceOrder.ServiceOrderBuilder |
respyMgmtServiceTeam(String respyMgmtServiceTeam)
Constraints: Not nullable, Maximum length: 8
|
ServiceOrder.ServiceOrderBuilder |
respyMgmtServiceTeamName(String respyMgmtServiceTeamName)
Constraints: Not nullable, Maximum length: 40
|
ServiceOrder.ServiceOrderBuilder |
salesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
ServiceOrder.ServiceOrderBuilder |
salesGroupOrgUnitID(String salesGroupOrgUnitID)
Constraints: Not nullable, Maximum length: 14
|
ServiceOrder.ServiceOrderBuilder |
salesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
ServiceOrder.ServiceOrderBuilder |
salesOfficeOrgUnitID(String salesOfficeOrgUnitID)
Constraints: Not nullable, Maximum length: 14
|
ServiceOrder.ServiceOrderBuilder |
salesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
ServiceOrder.ServiceOrderBuilder |
salesOrganizationOrgUnitID(String salesOrganizationOrgUnitID)
Constraints: Not nullable, Maximum length: 14
|
ServiceOrder.ServiceOrderBuilder |
serviceDocGrossAmount(BigDecimal serviceDocGrossAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
ServiceOrder.ServiceOrderBuilder |
serviceDocNetAmount(BigDecimal serviceDocNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
ServiceOrder.ServiceOrderBuilder |
serviceDocTaxAmount(BigDecimal serviceDocTaxAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
ServiceOrder.ServiceOrderBuilder |
serviceDocumentPriority(String serviceDocumentPriority)
Constraints: Not nullable, Maximum length: 1
|
ServiceOrder.ServiceOrderBuilder |
serviceDocumentTemplateType(String serviceDocumentTemplateType)
Constraints: Not nullable, Maximum length: 1
|
ServiceOrder.ServiceOrderBuilder |
serviceObjectType(String serviceObjectType)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
serviceOrder(String serviceOrder)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
serviceOrderDescription(String serviceOrderDescription)
Constraints: Not nullable, Maximum length: 40
|
ServiceOrder.ServiceOrderBuilder |
serviceOrderIsCompleted(String serviceOrderIsCompleted)
Constraints: Not nullable, Maximum length: 1
|
ServiceOrder.ServiceOrderBuilder |
serviceOrderIsRejected(String serviceOrderIsRejected)
Constraints: Not nullable, Maximum length: 1
|
ServiceOrder.ServiceOrderBuilder |
serviceOrderIsReleased(String serviceOrderIsReleased)
Constraints: Not nullable, Maximum length: 1
|
ServiceOrder.ServiceOrderBuilder |
serviceOrderType(String serviceOrderType)
Constraints: Not nullable, Maximum length: 4
|
ServiceOrder.ServiceOrderBuilder |
serviceOrderUUID(UUID serviceOrderUUID)
Constraints: none
|
ServiceOrder.ServiceOrderBuilder |
serviceOrganization(String serviceOrganization)
Constraints: Not nullable, Maximum length: 14
|
ServiceOrder.ServiceOrderBuilder |
shipToParty(String shipToParty)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
soldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
ServiceOrder.ServiceOrderBuilder |
text(ServiceOrderText... value)
Navigation property to_Text for ServiceOrder to multiple ServiceOrderText.
|
String |
toString() |
ServiceOrder.ServiceOrderBuilder |
transactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
@Nonnull public ServiceOrder.ServiceOrderBuilder confirmation(ServiceOrderConfirmation... value)
value
- The ServiceOrderConfirmations to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder defect(ServiceOrderDefect... value)
value
- The ServiceOrderDefects to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder item(ServiceOrderItem... value)
value
- The ServiceOrderItems to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder personResponsible(ServiceOrderPersonResp... value)
value
- The ServiceOrderPersonResps to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder pricingElement(ServiceOrderPriceElement... value)
value
- The ServiceOrderPriceElements to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder referenceObject(ServiceOrderRefObject... value)
value
- The ServiceOrderRefObjects to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder text(ServiceOrderText... value)
value
- The ServiceOrderTexts to build this ServiceOrder with.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrder(@Nullable String serviceOrder)
Original property name from the Odata EDM: ServiceOrder
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrderType(@Nullable String serviceOrderType)
Original property name from the Odata EDM: ServiceOrderType
A transaction type defines the characteristics and attributes of a business transaction (for example, sales order, service request, visit), and determines the controlling attributes (for example, text determination procedure, partner determination procedure, status profile, organizational data profile). A transaction type controls the processing of a specific business transaction.
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrderUUID(@Nullable UUID serviceOrderUUID)
Original property name from the Odata EDM: ServiceOrderUUID
This key is only used internally, and the operation number is always displayed on the interface. However, the operation number is not necessarily unique.
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrderDescription(@Nullable String serviceOrderDescription)
Original property name from the Odata EDM: ServiceOrderDescription
The description can be used during a search for the transaction.
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceObjectType(@Nullable String serviceObjectType)
Original property name from the Odata EDM: ServiceObjectType
You assign one or more business transaction categories to a transaction type.Depending on the leading business transaction category, only specific combinations are possible with other business transaction categories. The business transaction category Sales can only be combined with Activities, for example.
Service, Sales, Activity).this
.@Nonnull public ServiceOrder.ServiceOrderBuilder language(@Nullable String language)
Original property name from the Odata EDM: Language
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceDocumentPriority(@Nullable String serviceDocumentPriority)
Original property name from the Odata EDM: ServiceDocumentPriority
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder requestedServiceStartDateTime(@Nullable ZonedDateTime requestedServiceStartDateTime)
Original property name from the Odata EDM: RequestedServiceStartDateTime
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder requestedServiceEndDateTime(@Nullable ZonedDateTime requestedServiceEndDateTime)
Original property name from the Odata EDM: RequestedServiceEndDateTime
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceDocumentTemplateType(@Nullable String serviceDocumentTemplateType)
Original property name from the Odata EDM: ServiceDocumentTemplateType
If you leave this field blank, the business transaction is not flagged as a template, and can be used as a document for operative business processes.If you enter a template category in the field, the transaction is a business transaction template. You can use templates to save data for complex, but frequently occurring business processes. You can then use the templates as copy templates when creating new business transactions, or include them in existing transactions.During this, depending on the template category, linking data is copied between the template and transactions that are created from it:Template Category B: The link for header and item data between template and transaction is copied.Template Category C: Only the link for item data between template and transaction is copied.Template Category D: No linking data is copied between the template and transaction.
transaction should also be copied.this
.@Nonnull public ServiceOrder.ServiceOrderBuilder purchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number represents the connection between the order from the sold-to party and the sales document generated. Customers can use these numbers in correspondence to help determine specific document information. If a number is used for an order, then you can also print out this number on documents sent to customers (such as the delivery note).
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder customerPurchaseOrderDate(@Nullable LocalDateTime customerPurchaseOrderDate)
Original property name from the Odata EDM: CustomerPurchaseOrderDate
customer created the purchase order.this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrderIsReleased(@Nullable String serviceOrderIsReleased)
Original property name from the Odata EDM: ServiceOrderIsReleased
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrderIsCompleted(@Nullable String serviceOrderIsCompleted)
Original property name from the Odata EDM: ServiceOrderIsCompleted
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrderIsRejected(@Nullable String serviceOrderIsRejected)
Original property name from the Odata EDM: ServiceOrderIsRejected
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder 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
.@Nonnull public ServiceOrder.ServiceOrderBuilder distributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can define data for business partners and products per sales organization and distribution channel. In a sales organization you can deliver to a specific customer through several distribution channels.You can assign a specific distribution channel as an attribute to one or more organizational units. These can be sales organizations or subordinate organizational units for a sales organization such as sales offices.If you work with a selection of sales offices from one sales organization, each of these sales offices can be responsible for a specific distribution channel (for example, wholesale trade, retail trade, direct sales). The attribute "distribution channel" is then assigned to each sales office.When determining the sales area, the system reads for which sales organization an office with a specific distribution channel is assigned and uses this to determine the combination of sales organization and distribution channel.
are wholesale trade, retail trade, or direct sales.this
.@Nonnull public ServiceOrder.ServiceOrderBuilder division(@Nullable String division)
Original property name from the Odata EDM: Division
A division can be used, for example, to display a specific product group.
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder salesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: SalesOffice
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.
products or services within a given geographical area.this
.@Nonnull public ServiceOrder.ServiceOrderBuilder salesGroup(@Nullable String salesGroup)
Original property name from the Odata EDM: SalesGroup
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder shipToParty(@Nullable String shipToParty)
Original property name from the Odata EDM: ShipToParty
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder billToParty(@Nullable String billToParty)
Original property name from the Odata EDM: BillToParty
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder payerParty(@Nullable String payerParty)
Original property name from the Odata EDM: PayerParty
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder contactPerson(@Nullable String contactPerson)
Original property name from the Odata EDM: ContactPerson
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceDocGrossAmount(@Nullable BigDecimal serviceDocGrossAmount)
Original property name from the Odata EDM: ServiceDocGrossAmount
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceDocNetAmount(@Nullable BigDecimal serviceDocNetAmount)
Original property name from the Odata EDM: ServiceDocNetAmount
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceDocTaxAmount(@Nullable BigDecimal serviceDocTaxAmount)
Original property name from the Odata EDM: ServiceDocTaxAmount
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The currency is maintained per sales area in the business partner master. The currency for the customer is created from the business partner master in the document. You can change the currency as long as no follow-up functions (for example, billing document) have been triggered.
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder referenceServiceRequest(@Nullable String referenceServiceRequest)
Original property name from the Odata EDM: ReferenceServiceRequest
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder referenceServiceContract(@Nullable String referenceServiceContract)
Original property name from the Odata EDM: ReferenceServiceContract
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder refServiceOrderTemplate(@Nullable String refServiceOrderTemplate)
Original property name from the Odata EDM: RefServiceOrderTemplate
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder referenceServiceOrder(@Nullable String referenceServiceOrder)
Original property name from the Odata EDM: ReferenceServiceOrder
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder respyMgmtServiceTeam(@Nullable String respyMgmtServiceTeam)
Original property name from the Odata EDM: RespyMgmtServiceTeam
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder respyMgmtServiceTeamName(@Nullable String respyMgmtServiceTeamName)
Original property name from the Odata EDM: RespyMgmtServiceTeamName
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder respyMgmtGlobalTeamID(@Nullable String respyMgmtGlobalTeamID)
Original property name from the Odata EDM: RespyMgmtGlobalTeamID
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder salesOrganizationOrgUnitID(@Nullable String salesOrganizationOrgUnitID)
Original property name from the Odata EDM: SalesOrganizationOrgUnitID
You can assign as many distribution channels and divisions as you want to a sales organization. A specific combination of sales organizations, distribution channels and divisions is known as a sales area.
responsibility of a sales organization can include legal liability for products and the customer's right of recourse.this
.@Nonnull public ServiceOrder.ServiceOrderBuilder serviceOrganization(@Nullable String serviceOrganization)
Original property name from the Odata EDM: ServiceOrganization
this
.@Nonnull public ServiceOrder.ServiceOrderBuilder salesOfficeOrgUnitID(@Nullable String salesOfficeOrgUnitID)
Original property name from the Odata EDM: SalesOfficeOrgUnitID
You can form purchasing groups (for example, departments) in a sales office with specific sales responsibilities.
and services in a particular geographic area.this
.@Nonnull public ServiceOrder.ServiceOrderBuilder salesGroupOrgUnitID(@Nullable String salesGroupOrgUnitID)
Original property name from the Odata EDM: SalesGroupOrgUnitID
You can use purchasing groups to form different areas of responsibility in a sales office.
this
.@Nonnull public ServiceOrder build()
Copyright © 2021 SAP SE. All rights reserved.