public static class BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder extends Object
@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder serviceDocumentItmRelationUUID(@Nullable UUID serviceDocumentItmRelationUUID)
Original property name from the Odata EDM: ServiceDocumentItmRelationUUID
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder serviceDocItmRltnSqncNumber(@Nullable String serviceDocItmRltnSqncNumber)
Original property name from the Odata EDM: ServiceDocItmRltnSqncNumber
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder businessSolutionOrderUUID(@Nullable UUID businessSolutionOrderUUID)
Original property name from the Odata EDM: BusinessSolutionOrderUUID
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder businessSolutionOrder(@Nullable String businessSolutionOrder)
Original property name from the Odata EDM: BusinessSolutionOrder
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder businessSolutionOrderItem(@Nullable String businessSolutionOrderItem)
Original property name from the Odata EDM: BusinessSolutionOrderItem
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
The key is formed by linking all of the key fields together without any gaps. The key fields are defined for objects of this type in the Business Object Repository.
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder salesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder serviceDocSuccessorBusObjType(@Nullable String serviceDocSuccessorBusObjType)
Original property name from the Odata EDM: ServiceDocSuccessorBusObjType
Business objects in the BOR are identified by the object type (for example BUS2032) and a descriptive English name (for example, SalesOrder). Both means of identification must be unique among all object types.Business objects are often addressed using the descriptive name from external applications, while internally in the BOR they are mostly identified using the object type. Initially, only the internal key was used, but the extensive use of business objects has given rise to the need for addressing them using names. For compatibility reasons, both identifiers are now used.The object type can have a maximum of 10 characters.Examples:BUS2032BUS6026
this
.@Nonnull public BusSolnOrdItmFUPSalesOrder.BusSolnOrdItmFUPSalesOrderBuilder 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 BusSolnOrdItmFUPSalesOrder build()
Copyright © 2020 SAP SE. All rights reserved.