Get one segment group

get

/fscmRestApi/resources/11.13.18.05/planningSegmentGroupsV2/{SegmentGroupId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 : planningSegmentGroupsV2-item-response
Type: object
Show Source
Nested Schema : Segments
Type: array
Title: Segments
All segments within a specific segment group.
Show Source
Nested Schema : Segment Group Dimensions
Type: array
Title: Segment Group Dimensions
A set of dimensions used for a segment group.
Show Source
Nested Schema : Segment Group Duplicates
Type: array
Title: Segment Group Duplicates
Segment group used to duplicate a new segment group.
Show Source
Nested Schema : Segment Group Runs
Type: array
Title: Segment Group Runs
Distinct grouping of item-location combinations based on user-defined static or dynamic attributes. This grouping of similar item-location pairs enables more efficient management of inventory and distribution.
Show Source
Nested Schema : Creating Hierarchies for Segmentation
Type: array
Title: Creating Hierarchies for Segmentation
Hierarchies used for segmentation, that's a grouping of item-location combinations. The hierarchies are product, organization, customer, and demand class.
Show Source
Nested Schema : Deleting Hierarchies for Segmentation
Type: array
Title: Deleting Hierarchies for Segmentation
Hierarchies used for segmentation, that's a grouping of item-location combinations. The hierarchies are product, organization, customer, and demand class.
Show Source
Nested Schema : Segment Member Customers List of Values
Type: array
Title: Segment Member Customers List of Values
This list of values includes all customer sites that are associated with the segment group.
Show Source
Nested Schema : Segment Member Demand Classes List of Values
Type: array
Title: Segment Member Demand Classes List of Values
This list of values includes all demand classes that are associated with the segment group.
Show Source
Nested Schema : Segment Member Items List of Values
Type: array
Title: Segment Member Items List of Values
This list of values includes all items that are associated with the segment group.
Show Source
Nested Schema : Segment Member Locations List of Values
Type: array
Title: Segment Member Locations List of Values
This list of values includes all locations that are associated with the segment group.
Show Source
Nested Schema : Segment Members
Type: array
Title: Segment Members
A set of members like items, locations, demand class, or customer sites that are associated with segments.
Show Source
Nested Schema : Segments List of Values
Type: array
Title: Segments List of Values
This list of values includes all segments that are associated with the segment group.
Show Source
Nested Schema : Segment Names List of Values
Type: array
Title: Segment Names List of Values
This list of values includes all segment names that are associated with the segment group.
Show Source
Nested Schema : Segmentation Results
Type: array
Title: Segmentation Results
Result of the segmentation process.
Show Source
Nested Schema : planningSegmentGroupsV2-Segment-item-response
Type: object
Show Source
Nested Schema : Segment Criteria
Type: array
Title: Segment Criteria
Segment criteria used for segmentation.
Show Source
Nested Schema : Segment Data
Type: array
Title: Segment Data
Grouping of item-location combinations on the basis of user-defined, static, or dynamic attributes. Through segmentation, you can better manage the replenishment requirements for many item-location combinations by grouping them into a few segments.
Show Source
Nested Schema : Segment Duplicates
Type: array
Title: Segment Duplicates
Segment used to duplicate a new segment.
Show Source
Nested Schema : planningSegmentGroupsV2-Segment-SegmentCriteria-item-response
Type: object
Show Source
Nested Schema : Segment Plans
Type: array
Title: Segment Plans
Segment plans used for segmentation.
Show Source
Nested Schema : Segment Values
Type: array
Title: Segment Values
Segment values used for segmentation.
Show Source
Nested Schema : planningSegmentGroupsV2-Segment-SegmentCriteria-SegmentPlans-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-Segment-SegmentCriteria-SegmentValues-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-Segment-SegmentDataDelete-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-Segment-SegmentDuplicate-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentGroupDimensions-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentGroupDuplicate-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentGroupExecute-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentGroupHierarchyCreate-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentGroupHierarchyDelete-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentMemberCustomersLOV-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentMemberDemandClassLOV-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentMemberItemsLOV-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentMemberLocationsLOV-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentMembers-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentMemberSegmentsLOV-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentNameLOV-item-response
Type: object
Show Source
Nested Schema : planningSegmentGroupsV2-SegmentResults-item-response
Type: object
Show Source
Back to Top