public static final class ServiceOrderTemplate.ServiceOrderTemplateBuilder extends Object
@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder item(ServiceOrderTemplateItem... value)
value
- The ServiceOrderTemplateItems to build this ServiceOrderTemplate with.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder personResponsible(ServiceOrderTmplPersonResp... value)
value
- The ServiceOrderTmplPersonResps to build this ServiceOrderTemplate with.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder referenceObject(ServiceOrderTmplRefObject... value)
value
- The ServiceOrderTmplRefObjects to build this ServiceOrderTemplate with.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder text(ServiceOrderTmplText... value)
value
- The ServiceOrderTmplTexts to build this ServiceOrderTemplate with.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder serviceOrderTemplate(@Nullable String serviceOrderTemplate)
Original property name from the Odata EDM: ServiceOrderTemplate
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder serviceOrderTemplateUUID(@Nullable UUID serviceOrderTemplateUUID)
Original property name from the Odata EDM: ServiceOrderTemplateUUID
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 ServiceOrderTemplate.ServiceOrderTemplateBuilder serviceOrderType(@Nullable String serviceOrderType)
Original property name from the Odata EDM: ServiceOrderType
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.
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcOrdTmplDescription(@Nullable String srvcOrdTmplDescription)
Original property name from the Odata EDM: SrvcOrdTmplDescription
The description can be used during a search for the transaction.
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder 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.
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcDocTemplateSearchTermText(@Nullable String srvcDocTemplateSearchTermText)
Original property name from the Odata EDM: SrvcDocTemplateSearchTermText
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder serviceDocumentType(@Nullable String serviceDocumentType)
Original property name from the Odata EDM: ServiceDocumentType
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 ServiceOrderTemplate.ServiceOrderTemplateBuilder language(@Nullable String language)
Original property name from the Odata EDM: Language
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder serviceDocumentPriority(@Nullable String serviceDocumentPriority)
Original property name from the Odata EDM: ServiceDocumentPriority
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcDocTmplValdtyStartDateTime(@Nullable ZonedDateTime srvcDocTmplValdtyStartDateTime)
Original property name from the Odata EDM: SrvcDocTmplValdtyStartDateTime
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcDocTmplValdtyEndDateTime(@Nullable ZonedDateTime srvcDocTmplValdtyEndDateTime)
Original property name from the Odata EDM: SrvcDocTmplValdtyEndDateTime
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcOrdTmplIsReleased(@Nullable String srvcOrdTmplIsReleased)
Original property name from the Odata EDM: SrvcOrdTmplIsReleased
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcOrdTmplIsCompleted(@Nullable String srvcOrdTmplIsCompleted)
Original property name from the Odata EDM: SrvcOrdTmplIsCompleted
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder srvcOrdTmplIsRejected(@Nullable String srvcOrdTmplIsRejected)
Original property name from the Odata EDM: SrvcOrdTmplIsRejected
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder 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.
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder 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.
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder 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 ServiceOrderTemplate.ServiceOrderTemplateBuilder 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.
this
.@Nonnull public ServiceOrderTemplate.ServiceOrderTemplateBuilder 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 ServiceOrderTemplate build()
Copyright © 2021 SAP SE. All rights reserved.