Update a data assignment for a user
patch
/fscmRestApi/resources/11.13.18.05/dataSecurities/{UserRoleDataAssignmentId}
Request
Path Parameters
-
UserRoleDataAssignmentId(required): integer(int64)
The numerical value that uniquely identifies a user data role.
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-
ActiveFlag: boolean
Title:
ActiveMaximum Length:1Default Value:trueIndicates whether the data security access is active. The default value is ACTIVE. -
RoleCommonName: string
Title:
RoleMaximum Length:256The technical name of role where the data security assignment applies to the user. The role must be assigned to the user separately. -
RoleNameCr: string
Title:
Role NameThe name of the role for which the data security assignment is applicable. You must separately assign the role to the user. -
SecurityContext: string
Title:
Security ContextMaximum Length:255The category of data access that is required for the role. The category includes business unit, asset book, and inventory organization. -
SecurityContextValue: string
Title:
Security Context ValueMaximum Length:255The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for a single-part security context or the value for the first part of a multi-part context. -
SecurityContextValue2: string
Maximum Length:
255The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for the second part of a multi-part context. -
SecurityContextValue3: string
Maximum Length:
255The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for the third part of a multi-part context. -
UserName: string
Title:
User NameThe unique identifier for a user defined in the application that allows account access. -
UserRoleDataAssignmentId: integer
(int64)
Title:
User Role Data Assignment IdentifierThe numerical value that uniquely identifies a user data role.
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 : dataSecurities-item-response
Type:
Show Source
object-
ActiveFlag: boolean
Title:
ActiveMaximum Length:1Default Value:trueIndicates whether the data security access is active. The default value is ACTIVE. -
CreatedBy: string
Read Only:
trueMaximum Length:64The user who created the row. -
CreationDate: string
(date-time)
Read Only:
trueThe date and time when the row was created. -
LastUpdateDate: string
(date-time)
Read Only:
trueThe date and time when the row was last updated. -
LastUpdatedBy: string
Read Only:
trueMaximum Length:64The user who last updated the row. -
LastUpdateLogin: string
Read Only:
trueMaximum Length:32The session login of the user who last updated the row. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
RoleCommonName: string
Title:
RoleMaximum Length:256The technical name of role where the data security assignment applies to the user. The role must be assigned to the user separately. -
RoleNameCr: string
Title:
Role NameThe name of the role for which the data security assignment is applicable. You must separately assign the role to the user. -
Rolerf: string
Title:
Role NameRead Only:trueMaximum Length:240The name of the role for which the data security assignment is applicable. You must separately assign the role to the user. -
SecurityContext: string
Title:
Security ContextMaximum Length:255The category of data access that is required for the role. The category includes business unit, asset book, and inventory organization. -
SecurityContextValue: string
Title:
Security Context ValueMaximum Length:255The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for a single-part security context or the value for the first part of a multi-part context. -
SecurityContextValue2: string
Maximum Length:
255The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for the second part of a multi-part context. -
SecurityContextValue3: string
Maximum Length:
255The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for the third part of a multi-part context. -
UserName: string
Title:
User NameThe unique identifier for a user defined in the application that allows account access. -
Userrf: string
Title:
User NameRead Only:trueMaximum Length:100The user name that is a unique identifier of the user who allows account access. The user is defined in the application. -
UserRoleDataAssignmentId: integer
(int64)
Title:
User Role Data Assignment IdentifierThe numerical value that uniquely identifies a user data role.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
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.
Examples
The following example shows how to update a user assignment by submitting a PATCH request on the REST resource using cURL.
curl -i -u "<username>:<password>" -H "Content-Type: application/json" -X PATCH -d <payload> https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/dataSecurities/300100089632748
Example Request Payload
The following example shows the contents of the request body in JSON format:
{
"ActiveFlag": false
}Example of Response Header
The following shows an example of the response header.
Status: HTTP/1.1 200 OK Content-Type : application/vnd.oracle.adf.resourceitem+json application/json
Example of Response Body
The following example shows the contents of the response body in JSON format:
{
"ActiveFlag": false,
"UserRoleDataAssignmentId": 300100089632748,
"Rolerf" : "Financial Analyst",
"Userrf" : "FUSION_APPS_FSCM_ENT_MANAGER",
"SecurityContext" : "Asset book",
"SecurityContextValue" : "VISION LEASE CORPORATE BOOK",
"UserName" : "FUSION_APPS_FSCM_ENT_MANAGER",
"RoleNameCr" : "Financial Analyst",
"links": [
{
"rel": "self",
"href": "https://servername.fa.us2.oraclecloud.com/fscmRESTApi/resources/11.13.18.05/datasecurities/300100089632748",
"name": "datasecurities",
"kind": "item"
},
{
"rel": "canonical",
"href": "https://servername.fa.us2.oraclecloud.com/fscmRESTApi/resources/11.13.18.05/datasecurities/300100089632748",
"name": "datasecurities",
"kind": "item"
},
{
"rel": "lov",
"href": "https://servername.fa.us2.oraclecloud.com/fscmRESTApi/resources/11.13.18.05/datasecurities/300100089632748/lov/DataSecurityAM_UserNameLov1_1",
"name": "DataSecurityAM_UserNameLov1_1",
"kind": "collection"
},
{
"rel": "lov",
"href": "https://servername.fa.us2.oraclecloud.com/fscmRESTApi/resources/11.13.18.05/datasecurities/300100089632748/lov/DataSecurityAM_RoleP1_1",
"name": "DataSecurityAM_RoleP1_1",
"kind": "collection"
}
]
}