Update a rule for a territory
patch
/crmRestApi/resources/11.13.18.05/territories/{TerritoryVersionId}/child/TerritoryRule/{TerrRuleId}
Request
Path Parameters
-
TerrRuleId(required): integer(int64)
The unique identifier of the territory rule.
-
TerritoryVersionId(required): integer(int64)
The unique identifier of the territory version.
Header Parameters
-
Metadata-Context: string
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version: string
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
RuleNumber: integer
(int64)
Title:
Coverage NumberThe coverage number for the territory. -
RuleOperatorCode: string
Title:
Customer Coverage CodeMaximum Length:30Default Value:INCLUSIONThe code for identifying whether the coverage adds to or removes from the territory's jurisdiction. The accepted values are: EXCLUSION (for rule type EXCLUSION and PARTNER_EXCLUSION) and INCLUSION (for all other rule types, such as REGULAR, INCLUSION, PARTNER_REGULAR, PARTNER_INCLUSION, and INHERITANCE_OVERRIDE). -
RuleTypeCode: string
Title:
CoverageMaximum Length:30Default Value:REGULARThe code for the territory coverage type. If the territory coverage model is sales account centric, the accepted values are: -REGULAR (for coverage based on sales account dimensionality or named accounts) -INCLUSION (for manually included account coverage) -EXCLUSION (for manually excluded account coverage) If the territory coverage model is partner centric, the accepted values are: -PARTNER_REGULAR (for coverage based on partner dimensionality) -PARTNER_INCLUSION (for manually included partner coverage) -PARTNER_EXCLUSION (for manually excluded partner coverage) In case of inheritance, if the coverage is for a recipient territory, then the accepted value is INHERITANCE_OVERRIDE which indicates that the coverage overrides some of the inherited dimensionality. -
TerritoryRuleBoundary1: array
Rule Boundaries
Title:
Rule BoundariesThe rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage. -
TerritoryVersionId: integer
(int64)
Title:
Territory NumberThe unique identifier of the territory version.
Nested Schema : Rule Boundaries
Type:
arrayTitle:
Rule BoundariesThe rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-item-patch-request
Type:
Show Source
object-
TerritoryRuleBndryValue1: array
Rule Boundary Values
Title:
Rule Boundary ValuesThe rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension. -
TerrRuleId: integer
(int64)
Title:
Territory NumberThe identifier of the territory rule.
Nested Schema : Rule Boundary Values
Type:
arrayTitle:
Rule Boundary ValuesThe rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-TerritoryRuleBndryValue1-item-patch-request
Type:
Show Source
object-
AddrElementAttribute1: string
Title:
Additional Attribute 1Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute2: string
Title:
Additional Attribute 2Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute3: string
Title:
Additional Attribute 3Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute4: string
Title:
Additional Attribute 4Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute5: string
Title:
Additional Attribute 5Maximum Length:150Additional address element to support flexible address format. -
AddressCity: string
Title:
CityMaximum Length:60City. -
AddressCountry: string
Title:
CountryMaximum Length:2Country. -
AddressCounty: string
Title:
CountyMaximum Length:60County. -
AddressPostalCode: string
Title:
Postal CodeMaximum Length:60Postal Code. -
AddressProvince: string
Title:
ProvinceMaximum Length:60Province. -
AddressState: string
Title:
StateMaximum Length:60State. -
DimensionMember: string
The name of the territory dimension member.
-
IncludeHierarchyFlag: boolean
Title:
Include HierarchyMaximum Length:1Indicates whether the dimension member is included along with its hierarchy or not. The default value is true. -
TerrRuleBoundaryId: integer
(int64)
Title:
Territory NumberThe identifier of the territory rule boundary.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Root Schema : territories-TerritoryRule-item-response
Type:
Show Source
object-
CreatedBy: string
Title:
Created ByRead Only:trueMaximum Length:255The user who created the territory rule. -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:trueThe date the territory rule was created. -
LastUpdateDate: string
(date-time)
Title:
Last Updated DateRead Only:trueThe date the territory rule was last updated. -
LastUpdatedBy: string
Title:
Last Updated ByRead Only:trueMaximum Length:255The user who last updated the territory rule. -
LastUpdateLogin: string
Title:
Last Update LoginRead Only:trueMaximum Length:255The login of the user who last updated the territory rule. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
RuleNumber: integer
(int64)
Title:
Coverage NumberThe coverage number for the territory. -
RuleOperatorCode: string
Title:
Customer Coverage CodeMaximum Length:30Default Value:INCLUSIONThe code for identifying whether the coverage adds to or removes from the territory's jurisdiction. The accepted values are: EXCLUSION (for rule type EXCLUSION and PARTNER_EXCLUSION) and INCLUSION (for all other rule types, such as REGULAR, INCLUSION, PARTNER_REGULAR, PARTNER_INCLUSION, and INHERITANCE_OVERRIDE). -
RuleTypeCode: string
Title:
CoverageMaximum Length:30Default Value:REGULARThe code for the territory coverage type. If the territory coverage model is sales account centric, the accepted values are: -REGULAR (for coverage based on sales account dimensionality or named accounts) -INCLUSION (for manually included account coverage) -EXCLUSION (for manually excluded account coverage) If the territory coverage model is partner centric, the accepted values are: -PARTNER_REGULAR (for coverage based on partner dimensionality) -PARTNER_INCLUSION (for manually included partner coverage) -PARTNER_EXCLUSION (for manually excluded partner coverage) In case of inheritance, if the coverage is for a recipient territory, then the accepted value is INHERITANCE_OVERRIDE which indicates that the coverage overrides some of the inherited dimensionality. -
TerritoryRuleBoundary1: array
Rule Boundaries
Title:
Rule BoundariesThe rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage. -
TerritoryVersionId: integer
(int64)
Title:
Territory NumberThe unique identifier of the territory version. -
TerrRuleId: integer
(int64)
Title:
Coverage IDThe unique identifier of the territory rule.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : Rule Boundaries
Type:
arrayTitle:
Rule BoundariesThe rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-item-response
Type:
Show Source
object-
CreatedBy: string
Title:
Created ByRead Only:trueMaximum Length:64The user who created the territory rule boundary. -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:trueThe date the territory rule boundary was created. -
Dimension: string
Title:
DimensionRead Only:trueMaximum Length:60The name of the dimension. -
LastUpdateDate: string
(date-time)
Title:
Last Updated DateRead Only:trueThe date the territory rule boundary was last updated. -
LastUpdatedBy: string
Title:
Last Updated ByRead Only:trueMaximum Length:64The user who last updated the territory rule boundary. -
LastUpdateLogin: string
Title:
Last Update LoginRead Only:trueMaximum Length:32The login of the user who last updated the territory rule boundary. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
TerrDimensionCode: string
Title:
DimensionMaximum Length:5The code indicating the territory dimension, such as Geo for Geography Dimension, Prod for Product Dimension, and so on. -
TerritoryRuleBndryValue1: array
Rule Boundary Values
Title:
Rule Boundary ValuesThe rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension. -
TerrRuleBoundaryId: integer
(int64)
Title:
Territory Dimension IDThe unique identifier of the territory rule boundary. -
TerrRuleId: integer
(int64)
Title:
Territory NumberThe identifier of the territory rule.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : Rule Boundary Values
Type:
arrayTitle:
Rule Boundary ValuesThe rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-TerritoryRuleBndryValue1-item-response
Type:
Show Source
object-
AddrElementAttribute1: string
Title:
Additional Attribute 1Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute2: string
Title:
Additional Attribute 2Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute3: string
Title:
Additional Attribute 3Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute4: string
Title:
Additional Attribute 4Maximum Length:150Additional address element to support flexible address format. -
AddrElementAttribute5: string
Title:
Additional Attribute 5Maximum Length:150Additional address element to support flexible address format. -
AddressCity: string
Title:
CityMaximum Length:60City. -
AddressCountry: string
Title:
CountryMaximum Length:2Country. -
AddressCounty: string
Title:
CountyMaximum Length:60County. -
AddressPostalCode: string
Title:
Postal CodeMaximum Length:60Postal Code. -
AddressProvince: string
Title:
ProvinceMaximum Length:60Province. -
AddressState: string
Title:
StateMaximum Length:60State. -
CreatedBy: string
Title:
Created ByRead Only:trueMaximum Length:64The user who created the territory rule boundary value. -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:trueThe date the territory rule boundary value was created. -
DimensionMember: string
The name of the territory dimension member.
-
DimensionMemberHigh: string
Title:
Territory Dimension Member HighRead Only:trueMaximum Length:360The name of the territory dimension member with a high sequence number. -
IncludeHierarchyFlag: boolean
Title:
Include HierarchyMaximum Length:1Indicates whether the dimension member is included along with its hierarchy or not. The default value is true. -
LastUpdateDate: string
(date-time)
Title:
Last Updated DateRead Only:trueThe date the territory rule boundary value was last updated. -
LastUpdatedBy: string
Title:
Last Updated ByRead Only:trueMaximum Length:64The user who last updated the territory rule boundary value. -
LastUpdateLogin: string
Title:
Last Update LoginRead Only:trueMaximum Length:32The login of the user who last updated the territory rule boundary value. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
TerrDimensionCode: string
Title:
DimensionMaximum Length:5The code indicating the territory dimension. For example, AcTyp, Acct, Aux1, Aux2, Aux3, BUnit, CSize, Geo, Indst, OrgTp, Prod, Prtnr, or SChnl. -
TerrDimHighIntgId: string
Title:
Dimension Value RangeMaximum Length:80The unique identifier of the common member of Oracle Business Intelligence (OBI), Territory Management, and Cube with a high sequence number. -
TerrDimIntgId: string
Title:
Dimension ValueMaximum Length:80The unique identifier of the common member of Oracle Business Intelligence (OBI), Territory Management, and Cube. -
TerrRuleBndryValueId: integer
(int64)
Title:
Territory Dimension Member IDThe unique identifier of the territory rule boundary value. -
TerrRuleBoundaryId: integer
(int64)
Title:
Territory NumberThe identifier of the territory rule boundary.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Links
- TerritoryRuleBoundary1
-
Parameters:
- TerrRuleId:
$request.path.TerrRuleId - TerritoryVersionId:
$request.path.TerritoryVersionId
The rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage. - TerrRuleId:
Examples
The following example shows how to create a rule boundary for a territory by submitting a POST request on the REST resource using cURL.
cURL Command
curl -u <username:password> \ -X POST -d
@example_request_payload.json https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545/child/TerritoryRuleBoundary1
Example of Request Body
The following example shows the contents of the request body in JSON format.
{
"TerrDimensionCode":"Indst",
"TerritoryRuleBndryValue1":[
{
"TerrDimIntgId":"ONE VOICE~1100",
"TerrDimensionCode":"Indst"
}]
}
Example of Response Body
The following example shows the contents of the response body in JSON format.
{
"TerrRuleBoundaryId": 300100091635549,
"TerrRuleId": 300100091635545,
"Dimension": "Industry",
"TerrDimensionCode": "Indst",
"TerritoryRuleBndryValue1":[
{"TerrRuleBndryValueId": 300100091635550, "TerrRuleBoundaryId": 300100091635549, "DimensionMember": "Automotive", "DimensionMemberHigh": null,…}
],
"links":[
{"rel": "self", "href": "https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545/child/TerritoryRuleBoundary1/300100091635549",...},
{"rel": "canonical", "href": "https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545/child/TerritoryRuleBoundary1/300100091635549",...},
{"rel": "parent", "href": "https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545",...}
]
}