public static final class FunctionalLocation.FunctionalLocationBuilder extends Object
@Nonnull public FunctionalLocation.FunctionalLocationBuilder classification(FunctionalLocationClass... value)
value
- The FunctionalLocationClasss to build this FunctionalLocation with.@Nonnull public FunctionalLocation.FunctionalLocationBuilder longText(FunctionalLocationLongText value)
value
- The FunctionalLocationLongText to build this FunctionalLocation with.@Nonnull public FunctionalLocation.FunctionalLocationBuilder partner(FunctionalLocationPartner... value)
value
- The FunctionalLocationPartners to build this FunctionalLocation with.@Nonnull public FunctionalLocation.FunctionalLocationBuilder warranty(FunctionalLocationWarranty... value)
value
- The FunctionalLocationWarrantys to build this FunctionalLocation with.@Nonnull public FunctionalLocation.FunctionalLocationBuilder functionalLocation(@Nullable String functionalLocation)
Original property name from the Odata EDM: FunctionalLocation
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder functionalLocationLabelName(@Nullable String functionalLocationLabelName)
Original property name from the Odata EDM: FunctionalLocationLabelName
The functional location label can be changed where necessary. The system then automatically creates a labeling history and prevents historical labels from being reused without this first being checked. The labeling history also enables the interpretation of historical location labels in non-changeable documents outside the SAP System.You can assign one primary and several alternative labels to a functional location.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder functionalLocationName(@Nullable String functionalLocationName)
Original property name from the Odata EDM: FunctionalLocationName
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder funcLocationStructure(@Nullable String funcLocationStructure)
Original property name from the Odata EDM: FuncLocationStructure
Number of hierarchy levels of a technical systemKey length of the levelsSeparators (hyphens)
label. It establishes the following factor:this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder functionalLocationCategory(@Nullable String functionalLocationCategory)
Original property name from the Odata EDM: FunctionalLocationCategory
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder superiorFunctionalLocation(@Nullable String superiorFunctionalLocation)
Original property name from the Odata EDM: SuperiorFunctionalLocation
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder superiorFuncnlLocLabelName(@Nullable String superiorFuncnlLocLabelName)
Original property name from the Odata EDM: SuperiorFuncnlLocLabelName
The functional location label can be changed where necessary. The system then automatically creates a labeling history and prevents historical labels from being reused without this first being checked. The labeling history also enables the interpretation of historical location labels in non-changeable documents outside the SAP System.You can assign one primary and several alternative labels to a functional location.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder technicalObjectType(@Nullable String technicalObjectType)
Original property name from the Odata EDM: TechnicalObjectType
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder authorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
With an entry in this field, you allocate the master record of this object to a group to which only certain users have access for processing the data. The users that have access authorization have the appropriate entry in their user master record.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder grossWeight(@Nullable BigDecimal grossWeight)
Original property name from the Odata EDM: GrossWeight
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder grossWeightUnit(@Nullable String grossWeightUnit)
Original property name from the Odata EDM: GrossWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder operationStartDate(@Nullable LocalDateTime operationStartDate)
Original property name from the Odata EDM: OperationStartDate
The content of the field is used by the system - when calculating the mean time between failure - to calculate the length of time without malfunctions occuring during operation until the first breakdown.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder inventoryNumber(@Nullable String inventoryNumber)
Original property name from the Odata EDM: InventoryNumber
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder acquisitionValue(@Nullable BigDecimal acquisitionValue)
Original property name from the Odata EDM: AcquisitionValue
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder currency(@Nullable String currency)
Original property name from the Odata EDM: Currency
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder acquisitionDate(@Nullable LocalDateTime acquisitionDate)
Original property name from the Odata EDM: AcquisitionDate
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder assetManufacturerName(@Nullable String assetManufacturerName)
Original property name from the Odata EDM: AssetManufacturerName
This field is currently for informational purposes only.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder manufacturerPartNmbr(@Nullable String manufacturerPartNmbr)
Original property name from the Odata EDM: ManufacturerPartNmbr
of the same category.this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder manufacturerCountry(@Nullable String manufacturerCountry)
Original property name from the Odata EDM: ManufacturerCountry
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder manufacturerPartTypeName(@Nullable String manufacturerPartTypeName)
Original property name from the Odata EDM: ManufacturerPartTypeName
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder constructionMonth(@Nullable String constructionMonth)
Original property name from the Odata EDM: ConstructionMonth
Enter the month of construction as a two-digit figure.Month: January -> Entry: 01Month: July -> Entry: 07Month: December -> Entry: 12
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder constructionYear(@Nullable String constructionYear)
Original property name from the Odata EDM: ConstructionYear
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder manufacturerSerialNumber(@Nullable String manufacturerSerialNumber)
Original property name from the Odata EDM: ManufacturerSerialNumber
You can use the serial number as a complement to the manufacturer part number.You buy three technical objects of the same type from a manufacturer. The part number assigned by the manufacturer to the three objects is "T-4711" in each case. You cannot differentiate between the technical objects using just the part number.However, the manufacturer can allocate an individual serial number to each individual object, which then compliments the manufacturer part number:Manufacturer part number: T-4711Serial number of object 1: 001Serial number of object 2: 002Serial number of object 3: 003
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder maintenancePlant(@Nullable String maintenancePlant)
Original property name from the Odata EDM: MaintenancePlant
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder assetLocation(@Nullable String assetLocation)
Original property name from the Odata EDM: AssetLocation
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder assetRoom(@Nullable String assetRoom)
Original property name from the Odata EDM: AssetRoom
The field is used for informational purposes, and can be used as a sort criterion in reports (for example, the inventory list).
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder plantSection(@Nullable String plantSection)
Original property name from the Odata EDM: PlantSection
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder workCenter(@Nullable String workCenter)
Original property name from the Odata EDM: WorkCenter
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder workCenterInternalID(@Nullable String workCenterInternalID)
Original property name from the Odata EDM: WorkCenterInternalID
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder workCenterPlant(@Nullable String workCenterPlant)
Original property name from the Odata EDM: WorkCenterPlant
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder aBCIndicator(@Nullable String aBCIndicator)
Original property name from the Odata EDM: ABCIndicator
The following ABC indicators are possible:A - ImportantB - Less importantC - Relatively unimportantAccording to these criteria, "A" materials are those materials that are of greatest importance for the production operations of a company.Examples of use for ABC indicators are vendor master records, material master records, and master records of technical objects.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder maintObjectFreeDefinedAttrib(@Nullable String maintObjectFreeDefinedAttrib)
Original property name from the Odata EDM: MaintObjectFreeDefinedAttrib
You can enter a company-specific sort term in this field for the technical object. You can also define a matchcode for the field.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder businessPartnerName1(@Nullable String businessPartnerName1)
Original property name from the Odata EDM: BusinessPartnerName1
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder cityName(@Nullable String cityName)
Original property name from the Odata EDM: CityName
The city name is saved redundantly in another database field in upper- case letters, for search help.If the Postal regional structure ('city file') is active, the city name is checked against the Cities defined in the regional structure.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder houseNumber(@Nullable String houseNumber)
Original property name from the Odata EDM: HouseNumber
It is printed in the Street line.Other supplementary street information can be entered in the House number supplement or one of the Street2, Street3, Street4 or Street5 fields. See Print the Street address.A house number (e.g. 117) or a house number with supplement (e.g. 117a), or a house number range (e.g. 16-20), can be maintained in this field.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder postalCode(@Nullable String postalCode)
Original property name from the Odata EDM: PostalCode
If different postal codes are maintained for the PO Box and Street address of an address, this field contains the Street address postal code.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder streetName(@Nullable String streetName)
Original property name from the Odata EDM: StreetName
The street name is saved, redundantly in upper case in another database field, for search help purposes.There are other fields for address parts which can be printed above or below the street. See Print the Street address.The house number and other supplements are usually maintained in their own fields. See Formatting the Street line.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder region(@Nullable String region)
Original property name from the Odata EDM: Region
The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder country(@Nullable String country)
Original property name from the Odata EDM: Country
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key.The country keys are determined at system installation in the global settings.The definition of the country key in the SAP system does not have to match political or government entities.Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.
postal code or bank account number.this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder phoneNumber(@Nullable String phoneNumber)
Original property name from the Odata EDM: PhoneNumber
If the telephone number consists of a company number and an extension, the extension must be entered in the field extension.Telephone number, as it must be dialed from within the country.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder faxNumber(@Nullable String faxNumber)
Original property name from the Odata EDM: FaxNumber
If the fax number consists of a company number and an extension, the extension must be entered in the field extension.Fax number, as it is to be dialed from within the same country.Enter the fax number.The following rules apply for the format of telephone and fax numbers:The length of the entries in the field Telephone and Extension (Fax and Extension) cannot be more than 24 characters in total.Leading spaces are not allowed in the field Telephone or Fax or in the field Extension.Valid characters are:Numbers (0123456789)Letters (ABCDEFGHIJKLMNOPQRSTUVWXYZ)Following other characters: /, (, ), - *, # and " " (space), but not as a leading space.If an + is entered as the first character, the system checks whether the specified number starts with a country code. If so, a warning message is displayed because the country code is automatically determined by the system and should not be stored in the Telephone number (Fax number) field.If an & is entered as the first character, the automatic check and formatting of the telephone number (fax number), as well as the determination of the country code, is suppressed.Enter the following for the number "01234/567-0":Fax: 01234/567Extension: 0Enter the following for the number "01234/567-891":Fax: 01234/567Extension: 891For the number "012-345-678" (678 as extension) enter the following:Fax: 012-345Extension: 678In the following cases, enter the complete number (without country dialing code) in the field Fax:No part of the number can be considered as an extension.You are not sure which part of the number can be considered as an extension.If the address has several fax numbers, the first fax number is flagged as the standard fax number.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder masterFixedAsset(@Nullable String masterFixedAsset)
Original property name from the Odata EDM: MasterFixedAsset
Accounting.this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder fixedAsset(@Nullable String fixedAsset)
Original property name from the Odata EDM: FixedAsset
Using the asset sub-number, you can:Provide for separate management of later acquisitions to assets.Represent complex fixed assets with their component parts.In contrast to the main asset number, the asset sub-number must be numerical.
Accounting.this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder wBSElementExternalID(@Nullable String wBSElementExternalID)
Original property name from the Odata EDM: WBSElementExternalID
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder settlementOrder(@Nullable String settlementOrder)
Original property name from the Odata EDM: SettlementOrder
Order settlement can involve the settling of orders to other orders.When this is the case, a settlement order can be proposed from the technical object.This order is usually an internal order from Controlling (CO).
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder constructionMaterial(@Nullable String constructionMaterial)
Original property name from the Odata EDM: ConstructionMaterial
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder maintenancePlannerGroup(@Nullable String maintenancePlannerGroup)
Original property name from the Odata EDM: MaintenancePlannerGroup
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder maintenancePlanningPlant(@Nullable String maintenancePlanningPlant)
Original property name from the Odata EDM: MaintenancePlanningPlant
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder mainWorkCenterPlant(@Nullable String mainWorkCenterPlant)
Original property name from the Odata EDM: MainWorkCenterPlant
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder mainWorkCenter(@Nullable String mainWorkCenter)
Original property name from the Odata EDM: MainWorkCenter
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder mainWorkCenterInternalID(@Nullable String mainWorkCenterInternalID)
Original property name from the Odata EDM: MainWorkCenterInternalID
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder catalogProfile(@Nullable String catalogProfile)
Original property name from the Odata EDM: CatalogProfile
In Plant Maintenance and Customer Service, the catalog profile is proposed in the notification if:A notification is created without a reference object orThe reference object entered (equipment or functional location) does not contain a catalog profile
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder equipmentInstallationIsAllowed(@Nullable Boolean equipmentInstallationIsAllowed)
Original property name from the Odata EDM: EquipmentInstallationIsAllowed
It is possible to structure functional locations in such a way that the higher levels are only used for structuring purposes and will not allow the installation of equipment. Installation is then only allowed from a particular level.Flag this field if you want to allow the installation of equipment at this functional location.A functional location might have the following structure:Level 1 Conveyor installation not allowedLevel 2 Stage A installation not allowedStage B installation not allowedLevel 3 Motor 1 installation allowedMotor 2 installation allowedConveyor belt 1 installation allowedand so on.
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder onePieceOfEquipmentIsAllowed(@Nullable Boolean onePieceOfEquipmentIsAllowed)
Original property name from the Odata EDM: OnePieceOfEquipmentIsAllowed
If you wish to allow the installation of only a single piece of equipment at this functional location, flag this field.
installed at a functional location at the same time.this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder 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 FunctionalLocation.FunctionalLocationBuilder 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
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder 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 FunctionalLocation.FunctionalLocationBuilder organizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: OrganizationDivision
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
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder 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 FunctionalLocation.FunctionalLocationBuilder functionalLocationHasEquipment(@Nullable String functionalLocationHasEquipment)
Original property name from the Odata EDM: FunctionalLocationHasEquipment
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder funcnlLocHasSubOrdinateFuncLoc(@Nullable String funcnlLocHasSubOrdinateFuncLoc)
Original property name from the Odata EDM: FuncnlLocHasSubOrdinateFuncLoc
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder funcnlLocIsMarkedForDeletion(@Nullable Boolean funcnlLocIsMarkedForDeletion)
Original property name from the Odata EDM: FuncnlLocIsMarkedForDeletion
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder funcnlLocIsDeleted(@Nullable Boolean funcnlLocIsDeleted)
Original property name from the Odata EDM: FuncnlLocIsDeleted
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder functionalLocationIsActive(@Nullable Boolean functionalLocationIsActive)
Original property name from the Odata EDM: FunctionalLocationIsActive
this
.@Nonnull public FunctionalLocation.FunctionalLocationBuilder funcnlLocIsDeactivated(@Nullable Boolean funcnlLocIsDeactivated)
Original property name from the Odata EDM: FuncnlLocIsDeactivated
this
.@Nonnull public FunctionalLocation build()
Copyright © 2020 SAP SE. All rights reserved.