Create

post

/fscmRestApi/resources/11.13.18.05/costRollupGroups

Request

Header Parameters
  • 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".
  • 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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Cost Rollup Group Details
Type: array
Title: Cost Rollup Group Details
The Cost Rollup Group Details resource allows users to manage a cost rollup group by adding, modifying, and deleting combinations of cost organizations and books within the group.
Show Source
Nested Schema : costRollupGroups-costRollupGroupDetails-item-post-request
Type: object
Show Source
  • Title: Cost Book
    Maximum Length: 30
    Name of the cost book for the rollup group. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Books task.
  • Title: Cost Book ID
    Value that uniquely identifies the cost book included in the rollup group.
  • Title: Cost Organization ID
    Value that uniquely identifies the cost organization included in the rollup group.
  • Title: Cost Organization Name
    Maximum Length: 240
    Name of the cost organization for the rollup group. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Organizations task.
  • Title: Cost Rollup Group Detail ID
    Value that uniquely identifies the rollup group details. The application generates this value.
  • Title: Cost Rollup Group ID
    Value that uniquely identifies the rollup group for the rollup group details.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • 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".
  • 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.
Body ()
Root Schema : costRollupGroups-item-response
Type: object
Show Source
Nested Schema : Cost Rollup Group Details
Type: array
Title: Cost Rollup Group Details
The Cost Rollup Group Details resource allows users to manage a cost rollup group by adding, modifying, and deleting combinations of cost organizations and books within the group.
Show Source
Nested Schema : costRollupGroups-costRollupGroupDetails-item-response
Type: object
Show Source
  • Title: Cost Book
    Maximum Length: 30
    Name of the cost book for the rollup group. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Books task.
  • Title: Cost Book ID
    Value that uniquely identifies the cost book included in the rollup group.
  • Title: Cost Organization ID
    Value that uniquely identifies the cost organization included in the rollup group.
  • Title: Cost Organization Name
    Maximum Length: 240
    Name of the cost organization for the rollup group. Review and update the value for this attribute using the Setup and Maintenance work area, and the Manage Cost Organizations task.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    User who created the rollup group detail record.
  • Title: Creation Date
    Read Only: true
    Date on which the rollup group detail record was created.
  • Title: Last Update Date
    Read Only: true
    Date on which the rollup group detail record was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    User who last updated the rollup group detail record.
  • Links
  • Title: Cost Rollup Group Detail ID
    Value that uniquely identifies the rollup group details. The application generates this value.
  • Title: Cost Rollup Group ID
    Value that uniquely identifies the rollup group for the rollup group details.
Back to Top

Examples

These examples describe how to create cost rollup groups.

Example 1 cURL Command

Use the following cURL command to submit a request on the REST resource.

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/costRollupGroups"

Example 1 Request Body

The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it updates.

{
    "RollupGroupDescription": "Test RG Desc - 999",
    "RollupGroupName": "Test RG - 999",
    "costRollupGroupDetails": [
        {
            "CostBook": "ZCST-Dallas",
            "CostOrganizationName": "ZCST-Dallas"
        },
        {
            "CostBook": "404-CB",
            "CostOrganizationName": "404-CO"
        }
    ]
}

Example 1 Response Body

The following example includes the contents of the response body in JSON format:

{
           "RollupGroupDescription": "Test RG Desc - 999",
    "RollupGroupName": "Test RG - 999",
            "LastUsedDate": null,
            "CreatedBy": "COST_ACCT_ALL_COST_ORGS",
            "CreationDate": "2023-03-21T03:30:58.765+00:00",
            "LastUpdatedBy": "COST_ACCT_ALL_COST_ORGS",
            "LastUpdateDate": "2023-03-21T03:30:58.766+00:00",
            "links": [
                {
                    "rel": "self",
                    "href": "http://servername/fscmRestApi/resources/version/costRollupGroups/300100573549594",
                    "name": "costRollupGroups",
                    "kind": "item",
                    "properties": {
                        "changeIndicator": "ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000178"
                    }
                },
                {
                    "rel": "canonical",
                    "href": "http://servername/fscmRestApi/resources/version/costRollupGroups/300100573549594",
                    "name": "transferChargeRules",
                    "kind": "item"
                },
                {
                    "rel": "child",
                    "href": "http://servername/fscmRestApi/resources/version/costRollupGroups/300100573549594/child/costRollupGroupDetails",
                    "name": "costRollupGroupDetails",
                    "kind": "collection"
                }
            ]
        }

Example 2 cURL Command

Use the following cURL command to submit a request on the REST resource.

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/costRollupGroups/300100573549594"

Example 2 Request Body

The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it updates.

 {
            "CostBook": "ZCST-Seattle",
            "CostOrganizationName": "ZCST-Seattle"
 }

Example 2 Response Body

The following example includes the contents of the response body in JSON format:

"costRollupGroupDetails": [
        {
            "CostBook": "ZCST-Dallas",
            "CostOrganizationName": "ZCST-Dallas"
        },
        {
            "CostBook": "404-CB",
            "CostOrganizationName": "404-CO"
        }, {
            "CostBook": "ZCST-Seattle",
            "CostOrganizationName": "ZCST-Seattle"
 }
    ]
Back to Top