Get all supplies

get

/fscmRestApi/resources/11.13.18.05/replenishmentPlans/{PlanId}/child/PlanningSupplies

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
  • Used as a predefined finder to search the collection.

    Format ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables

    • PrimaryKey Finds the supply according to the value that identifies the supply.
      Finder Variables
      • PlanId; integer; Value that uniquely identifies the plan associated with the supply.
      • SimulationSetId; integer; Value that uniquely identifies the simulation set associated with the supply.
      • SourceTablePrimary; string; Name of the table where the supply is stored. This value is always MSC_SUPPLIES.
      • TransactionId; integer; Value that uniquely identifies a supply.
    • TransactionIdFinder Finds a specific supply in the plan.
      Finder Variables
      • TransactionId; integer; Value that identifies the supply.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • Action; string; Value that indicates the action recommended by planning. A list of accepted values is defined in the lookup type ORA_MSC_ACTIONS.
    • ActualStartDate; string
    • AssetNumber; string; Number that identifies the asset associated with a maintenance work order.
    • BillSequenceId; integer; Value that uniquely identifies the sequence in which a component is used within an operation.
    • BmtOption; integer; Contains one of the following values: 1 or 2. If 1, then the buyer is responsible for the transportation of the purchased item. If 2, then the buyer isn't responsible for the transportation of the purchased item. This attribute applies only to purchased items.
    • Buyer; string; Name of the buyer associated to the item.
    • BuyerManagedTransportation; string; Contains one of the following values: Yes or No. If Yes, then the buyer is responsible for the transportation of the purchased item. If No, then the buyer isn't responsible for the transportation of the purchased item. This attribute applies only to purchased items.
    • ClusterId; integer; Value that uniquely identifies the cluster.
    • ClusterName; string; Name of the cluster.
    • CreatedBy; string; User who created the order.
    • CreationDate; string; Date when the user created the order.
    • Customer; string; Name of the customer associated with the drop ship purchase order.
    • CustomerSite; string; Code associated with a specific customer ship-to location.
    • DaysPastDue; number; Number of days that the supply date is in the past.
    • DestOrgCode; string; Abbreviation that identifies the destination organization for an order.
    • DestinationTimeZone; string; Time zone associated with the entity that's receiving the order. The destination entity can be a customer or an organization.
    • EarliestStartDate; string; Earliest date on which a supply can start based on the lead times of all its upstream supplies, or its planning time-fence date, or based on the constrained capacity of a resource or supplier. This date is calculated by constraint-based plans
    • ExcessReductionAtSrc; number; Percentage value by which the inventory excess at the source location is reduced.
    • ExpenseDestinationTransfer; string; Contains one of the following values: Yes or No. If Yes, then the transfer is to an expense destination. If No, then the transfer isn't to an expense destination.
    • ExpirationDate; string; Date when the existing lot associated with the supply expires.
    • FirmDate; string; Date when supply is due. This attribute is a fixed value that can't be rescheduled by planning and is only populated when the firm status is firm.
    • FirmPlannedType; integer; Value that indicates whether the order is firmed or not. Valid values are 1 or 2. If 1, then the order is firm. If 2, then the order isn't firm. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_FIRM_STATUS.
    • FirmQuantity; number; Fixed quantity of supply. This attribute value can't be changed by planning and is only populated when the firm status is firm.
    • FirmStartDate; string; Date when supply begins. This attribute is a fixed value that can't be rescheduled by planning and is only populated when the firm status is firm.
    • FirmStartQuantity; number; User-specified start quantity of a supply. This attribute value can't be changed by planning and is only populated when the firm status is firm.
    • FirmStatus; string; Status that indicates whether the order is firm or not. Valid values include Firm and Not firm. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_FIRM_STATUS.
    • HoldDate; string; Date on which the on-hand inventory lot is no longer on hold.
    • ImplementAs; integer; Value that indicates the type of order to be implemented. Valid values are 1: None, 2: Purchase requisition, 3: Work order, or 5: Internal requisition. A list of accepted values is defined in the lookup type ORA_MSC_WORKBENCH_IMPLEMENT_AS.
    • ImplementDate; string; Date when the order is released.
    • ImplementDockDate; string; Date when the material should be on the receiving dock when the order is released.
    • ImplementEmployeeId; integer
    • ImplementFirm; integer; Value that indicates whether the order is firm or not. Valid values are 1: Firm and 2: Not Firm. A list of accepted values is defined in the lookup type MSC_YES_NO.
    • ImplementFirmOption; string; Status to use when the order is released. Valid values include Firm and Not firm. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_FIRM_STATUS.
    • ImplementJobName; string; Job name of the work order to be created when the order is released.
    • ImplementLocation; string; Value that identifies the deliver-to location to use when the order is released.
    • ImplementOrderType; string; Value that indicates the type of order to use when the order is released. A list of accepted values is defined in the lookup type ORA_MSC_WORKBENCH_IMPLEMENT_AS.
    • ImplementQuantity; number; Quantity of the order that's released.
    • ImplementShipDate; string; Date when the order is shipped.
    • ImplementShipMethod; string; Value that indicates the shipping method to use when the order is released. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
    • ImplementShippingMethod; string; Value that indicates the shipping method to use when the order is released, or is a concatenation of carrier name, method of transportation, and service level to use when the order is released. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
    • ImplementSourceOrganization; string; Source organization used for the order that's released.
    • ImplementStatus; string; Status of the order to use when the order is released. Valid Values are Unreleased or Released.
    • ImplementStatusCode; integer; Abbreviation that identifies the status to use when the order is released. Valid values are 1 or 3. If 1, then the order isn't released. If 3, then the order is released.
    • ImplementSupplier; string; Name of the supplier for the order that's released.
    • ImplementSupplierSite; string; Abbreviation that indicates the specific supplier ship-from location to use when the order is released.
    • ImplementedQuantity; number; Cumulative quantity that has been released to date.
    • InitExcessAtSource; number; Initial excess quantity at the source location before inventory rebalancing.
    • InitShortageAtDest; number; Initial shortage quantity at the destination location before inventory rebalancing.
    • Item; string; Name of the item associated with the supply.
    • ItemDescription; string; Description of the item that's associated with the supply.
    • LastUpdateDate; string; Date when the order was most recently updated.
    • LastUpdatedBy; string; User who most recently updated the supply.
    • LatestStartDate; string; Latest date on which a supply can start. This date is computed by offsetting the lead time of the supply from its need-by date. This date is calculated by constraint-based plans.
    • LineNumber; string; Number that identifies the order line.
    • Lot; string; Number that identifies the lot of the on-hand supply.
    • MakeOrBuy; string; Value that indicates whether the item is a manufactured item or a purchased item. Valid values include Make or Buy. A list of accepted values is defined in the lookup type ORA_MSC_PLANNING_MAKE_BUY.
    • MarkForReleaseOption; string; Value that indicates the release status of the order. Valid values are 1: Marked For Release or 2: Not Marked For Release. When marking or not marking orders for release, the request body must include only the MarkForReleaseOption attribute.
    • Message; string; Text of the error message, if any, encountered when creating or updating a supply.
    • NeedByDate; string; Date when the supply quantity is needed.
    • OldDockDate; string; Date when the order was originally to arrive at the receiving dock. This attribute value is extracted from the source application.
    • OldDueDate; string; Date when the order was originally due. This attribute value is extracted from the source application.
    • OrderNumber; string; Number that identifies the order associated with the supply.
    • OrderQuantity; number; Quantity associated with the supply.
    • OrderStatus; string; SCM Cloud transactional status of a work order, purchase order, or transfer order supplies that are referred to by the planning process.
    • OrderType; integer; Abbreviation that identifies the type of order. A list of accepted values is defined in the lookup type MSC_ORDER_TYPE.
    • OrderTypeText; string; Type of order such as on hand, purchase order, or work order. A list of accepted values is defined in the lookup type MSC_ORDER_TYPE.
    • OrgCurrencyCode; string; Abbreviation that identifies the base currency of the organization.
    • Organization; string; Name of the organization associated with the order.
    • OrganizationTimeZone; string; Time zone associated with an organization.
    • OriginalItemName; string; Name of the requested item associated with the demand.
    • OriginalNeedByDate; string; Date when the order was originally needed. This value is extracted from the source application.
    • PlanId; integer; Value that uniquely identifies the plan.
    • Planner; string; Abbreviation that identifies the planner responsible for the item.
    • PlannerDescription; string; Description of the planner responsible for the item.
    • PlanningMakeBuyCode; integer; Abbreviation that indicates whether the item is manufactured or purchased. Valid values are 1 or 2. If 1, then the item is a manufactured item. If 2, then the item is a purchased item. A list of accepted values is defined in the lookup type ORA_MSC_PLANNING_MAKE_BUY.
    • ReleaseErrors; string; Errors that are generated in the release process.
    • ReleaseStatus; integer; Code that indicates the release status of the order. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_RELEASE_STATUS.
    • ReleaseStatusText; string; Value that indicates the release status of the order. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_RELEASE_STATUS.
    • ReleaseTimeFenceCode; integer; Abbreviation that identifies the point in time inside which planned orders with certain criteria are automatically released as work orders or purchase orders. A list of accepted values is defined in the lookup type ORA_MSC_TIME_FENCE_TYPES.
    • ReplInvRebalanceFlag; integer; Indicates whether or not the planned order is created by inventory rebalancing.
    • ScheduleName; string; Name of the supply schedule associated with an order.
    • ScheduledShipDate; string; Date when the order is scheduled to be shipped.
    • SegmentName; string; Name of the segment used for a set of items.
    • SellingPrice; number; Selling price of an item on the order line.
    • ShipCalendar; string; Shipping calendar associated with the order.
    • ShipMethod; string; Value that indicates the shipping method used to ship the order. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
    • ShipTo; string; Abbreviation that identifies the specific ship-to location.
    • ShippingMethod; string; Value that indicates the shipping method used to ship the order, or is a concatenation of carrier name, method of transportation, and service level associated with the order. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
    • ShortageReductionAtDest; number; Percentage value by which the inventory shortage at the destination location is reduced.
    • SimulationSetId; integer; Value that uniquely identifies the simulation set used in the plan, if any.
    • SourceOrganization; string; Organization that will source the order.
    • SourceTimeZone; string; Time zone associated with the entity that's sourcing the order. The sourcing entity can be a supplier or an organization.
    • SourceType; integer; Value that identifies the type of planned order to be created. Valid values are 1, 2, or 3. If 1, then a planned make order is created. If 2, then a planned buy order is created. If 3, then a planned transfer order is created.
    • Subinventory; string; Subinventory code associated with the supply.
    • SuggestedDockDate; string; Date when the order is recommended to arrive at the receiving dock.
    • SuggestedDueDate; string; Date when a supply is expected to be completed.
    • SuggestedOrderDate; string; Date when an order is recommended to be placed.
    • SuggestedShipDate; string; Date when the order is recommended to be shipped.
    • SuggestedStartDate; string; Date when work on the order is recommended to begin.
    • Supplier; string; Name of the source supplier.
    • SupplierSite; string; Abbreviation that indicates the specific supplier location from where the item is being sourced.
    • TransactionId; integer; Value that uniquely identifies the supply transaction. This value is internally generated by the application.
    • TransitLeadTime; number; Number of days that the supply is in transit between two locations.
    • UOM; string; Name of the unit of measure associated with the order quantity.
    • UOMCode; string; Abbreviation that identifies the unit of measure associated with the order quantity.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 : replenishmentPlans-PlanningSupplies
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : replenishmentPlans-PlanningSupplies-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 80
    Value that indicates the action recommended by planning. A list of accepted values is defined in the lookup type ORA_MSC_ACTIONS.
  • Title: Actual Start Date
    Read Only: true
  • Title: Asset
    Read Only: true
    Maximum Length: 80
    Number that identifies the asset associated with a maintenance work order.
  • Value that uniquely identifies the sequence in which a component is used within an operation.
  • Title: Buyer-Managed Transportation
    Read Only: true
    Contains one of the following values: 1 or 2. If 1, then the buyer is responsible for the transportation of the purchased item. If 2, then the buyer isn't responsible for the transportation of the purchased item. This attribute applies only to purchased items.
  • Title: Buyer
    Read Only: true
    Name of the buyer associated to the item.
  • Read Only: true
    Maximum Length: 200
    Contains one of the following values: Yes or No. If Yes, then the buyer is responsible for the transportation of the purchased item. If No, then the buyer isn't responsible for the transportation of the purchased item. This attribute applies only to purchased items.
  • Value that uniquely identifies the cluster.
  • Name of the cluster.
  • Read Only: true
    Maximum Length: 64
    User who created the order.
  • Read Only: true
    Date when the user created the order.
  • Title: Customer
    Maximum Length: 4000
    Name of the customer associated with the drop ship purchase order.
  • Title: Customer Site
    Maximum Length: 4000
    Code associated with a specific customer ship-to location.
  • Title: Days Past Due
    Read Only: true
    Number of days that the supply date is in the past.
  • Title: Destination Time Zone
    Read Only: true
    Maximum Length: 100
    Time zone associated with the entity that's receiving the order. The destination entity can be a customer or an organization.
  • Read Only: true
    Maximum Length: 18
    Abbreviation that identifies the destination organization for an order.
  • Title: Earliest Start Date
    Read Only: true
    Earliest date on which a supply can start based on the lead times of all its upstream supplies, or its planning time-fence date, or based on the constrained capacity of a resource or supplier. This date is calculated by constraint-based plans
  • Percentage value by which the inventory excess at the source location is reduced.
  • Read Only: true
    Maximum Length: 100
    Contains one of the following values: Yes or No. If Yes, then the transfer is to an expense destination. If No, then the transfer isn't to an expense destination.
  • Title: Expiration Date
    Date when the existing lot associated with the supply expires.
  • Title: Firm Date
    Date when supply is due. This attribute is a fixed value that can't be rescheduled by planning and is only populated when the firm status is firm.
  • Title: Firm Status
    Value that indicates whether the order is firmed or not. Valid values are 1 or 2. If 1, then the order is firm. If 2, then the order isn't firm. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_FIRM_STATUS.
  • Title: Firm Quantity
    Fixed quantity of supply. This attribute value can't be changed by planning and is only populated when the firm status is firm.
  • Date when supply begins. This attribute is a fixed value that can't be rescheduled by planning and is only populated when the firm status is firm.
  • Title: Firm Start Quantity
    User-specified start quantity of a supply. This attribute value can't be changed by planning and is only populated when the firm status is firm.
  • Read Only: true
    Maximum Length: 200
    Status that indicates whether the order is firm or not. Valid values include Firm and Not firm. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_FIRM_STATUS.
  • Title: Hold Date
    Read Only: true
    Date on which the on-hand inventory lot is no longer on hold.
  • Title: Implement Order Type
    Value that indicates the type of order to be implemented. Valid values are 1: None, 2: Purchase requisition, 3: Work order, or 5: Internal requisition. A list of accepted values is defined in the lookup type ORA_MSC_WORKBENCH_IMPLEMENT_AS.
  • Title: Implement Date
    Date when the order is released.
  • Title: Implement Dock Date
    Date when the material should be on the receiving dock when the order is released.
  • Title: Implemented Quantity
    Cumulative quantity that has been released to date.
  • Title: Implement Firm
    Value that indicates whether the order is firm or not. Valid values are 1: Firm and 2: Not Firm. A list of accepted values is defined in the lookup type MSC_YES_NO.
  • Read Only: true
    Maximum Length: 200
    Status to use when the order is released. Valid values include Firm and Not firm. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_FIRM_STATUS.
  • Title: Implement Work Order Number
    Maximum Length: 120
    Job name of the work order to be created when the order is released.
  • Title: Implement Location
    Maximum Length: 400
    Value that identifies the deliver-to location to use when the order is released.
  • Read Only: true
    Maximum Length: 4000
    Value that indicates the type of order to use when the order is released. A list of accepted values is defined in the lookup type ORA_MSC_WORKBENCH_IMPLEMENT_AS.
  • Title: Implement Quantity
    Quantity of the order that's released.
  • Title: Implement Ship Date
    Date when the order is shipped.
  • Maximum Length: 30
    Value that indicates the shipping method to use when the order is released. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
  • Title: Implement Shipping Method
    Maximum Length: 400
    Value that indicates the shipping method to use when the order is released, or is a concatenation of carrier name, method of transportation, and service level to use when the order is released. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
  • Title: Implement Source Organization
    Maximum Length: 100
    Source organization used for the order that's released.
  • Read Only: true
    Maximum Length: 200
    Status of the order to use when the order is released. Valid Values are Unreleased or Released.
  • Title: Implement Status
    Abbreviation that identifies the status to use when the order is released. Valid values are 1 or 3. If 1, then the order isn't released. If 3, then the order is released.
  • Title: Implement Supplier
    Maximum Length: 360
    Name of the supplier for the order that's released.
  • Title: Implement Supplier Site
    Maximum Length: 300
    Abbreviation that indicates the specific supplier ship-from location to use when the order is released.
  • Initial excess quantity at the source location before inventory rebalancing.
  • Initial shortage quantity at the destination location before inventory rebalancing.
  • Title: Item
    Maximum Length: 300
    Name of the item associated with the supply.
  • Title: Item Description
    Read Only: true
    Maximum Length: 240
    Description of the item that's associated with the supply.
  • Read Only: true
    Date when the order was most recently updated.
  • Read Only: true
    Maximum Length: 64
    User who most recently updated the supply.
  • Title: Latest Start Date
    Read Only: true
    Latest date on which a supply can start. This date is computed by offsetting the lead time of the supply from its need-by date. This date is calculated by constraint-based plans.
  • Title: Line Number
    Read Only: true
    Maximum Length: 100
    Number that identifies the order line.
  • Links
  • Title: Lot
    Read Only: true
    Maximum Length: 80
    Number that identifies the lot of the on-hand supply.
  • Read Only: true
    Maximum Length: 100
    Value that indicates whether the item is a manufactured item or a purchased item. Valid values include Make or Buy. A list of accepted values is defined in the lookup type ORA_MSC_PLANNING_MAKE_BUY.
  • Value that indicates the release status of the order. Valid values are 1: Marked For Release or 2: Not Marked For Release. When marking or not marking orders for release, the request body must include only the MarkForReleaseOption attribute.
  • Read Only: true
    Text of the error message, if any, encountered when creating or updating a supply.
  • Title: Need-by Date
    Read Only: true
    Date when the supply quantity is needed.
  • Title: Old Dock Date
    Read Only: true
    Date when the order was originally to arrive at the receiving dock. This attribute value is extracted from the source application.
  • Title: Old Due Date
    Read Only: true
    Date when the order was originally due. This attribute value is extracted from the source application.
  • Title: Order Number
    Read Only: true
    Maximum Length: 4000
    Number that identifies the order associated with the supply.
  • Title: Order Quantity
    Read Only: true
    Quantity associated with the supply.
  • Read Only: true
    Maximum Length: 200
    SCM Cloud transactional status of a work order, purchase order, or transfer order supplies that are referred to by the planning process.
  • Abbreviation that identifies the type of order. A list of accepted values is defined in the lookup type MSC_ORDER_TYPE.
  • Title: Order Type
    Maximum Length: 4000
    Type of order such as on hand, purchase order, or work order. A list of accepted values is defined in the lookup type MSC_ORDER_TYPE.
  • Title: Organization
    Maximum Length: 49
    Name of the organization associated with the order.
  • Title: Organization Time Zone
    Read Only: true
    Maximum Length: 100
    Time zone associated with an organization.
  • Read Only: true
    Abbreviation that identifies the base currency of the organization.
  • Title: Requested Item
    Read Only: true
    Maximum Length: 4000
    Name of the requested item associated with the demand.
  • Title: Original Need-by Date
    Read Only: true
    Date when the order was originally needed. This value is extracted from the source application.
  • Value that uniquely identifies the plan.
  • Title: Planner
    Read Only: true
    Maximum Length: 10
    Abbreviation that identifies the planner responsible for the item.
  • Title: Planner Description
    Read Only: true
    Maximum Length: 100
    Description of the planner responsible for the item.
  • Title: Make or Buy
    Read Only: true
    Abbreviation that indicates whether the item is manufactured or purchased. Valid values are 1 or 2. If 1, then the item is a manufactured item. If 2, then the item is a purchased item. A list of accepted values is defined in the lookup type ORA_MSC_PLANNING_MAKE_BUY.
  • Read Only: true
    Maximum Length: 400
    Errors that are generated in the release process.
  • Title: Release Status
    Code that indicates the release status of the order. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_RELEASE_STATUS.
  • Read Only: true
    Maximum Length: 80
    Value that indicates the release status of the order. A list of accepted values is defined in the lookup type ORA_MSC_ORDER_RELEASE_STATUS.
  • Read Only: true
    Abbreviation that identifies the point in time inside which planned orders with certain criteria are automatically released as work orders or purchase orders. A list of accepted values is defined in the lookup type ORA_MSC_TIME_FENCE_TYPES.
  • Indicates whether or not the planned order is created by inventory rebalancing.
  • Title: Scheduled Ship Date
    Read Only: true
    Date when the order is scheduled to be shipped.
  • Title: Schedule Name
    Read Only: true
    Name of the supply schedule associated with an order.
  • Title: Segment
    Read Only: true
    Maximum Length: 120
    Name of the segment used for a set of items.
  • Read Only: true
    Selling price of an item on the order line.
  • Read Only: true
    Maximum Length: 15
    Shipping calendar associated with the order.
  • Maximum Length: 30
    Value that indicates the shipping method used to ship the order. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
  • Title: Shipping Method
    Maximum Length: 4000
    Value that indicates the shipping method used to ship the order, or is a concatenation of carrier name, method of transportation, and service level associated with the order. Review and update the value for this attribute using the Maintain Supply Network Model task, and the Interlocation Shipping Networks tab.
  • Title: Ship To
    Read Only: true
    Maximum Length: 4000
    Abbreviation that identifies the specific ship-to location.
  • Percentage value by which the inventory shortage at the destination location is reduced.
  • Value that uniquely identifies the simulation set used in the plan, if any.
  • Title: Source Organization
    Maximum Length: 49
    Organization that will source the order.
  • Title: Source Time Zone
    Read Only: true
    Maximum Length: 100
    Time zone associated with the entity that's sourcing the order. The sourcing entity can be a supplier or an organization.
  • Value that identifies the type of planned order to be created. Valid values are 1, 2, or 3. If 1, then a planned make order is created. If 2, then a planned buy order is created. If 3, then a planned transfer order is created.
  • Title: Subinventory
    Read Only: true
    Maximum Length: 40
    Subinventory code associated with the supply.
  • Title: Suggested Dock Date
    Read Only: true
    Date when the order is recommended to arrive at the receiving dock.
  • Title: Suggested Due Date
    Read Only: true
    Date when a supply is expected to be completed.
  • Title: Suggested Order Date
    Read Only: true
    Date when an order is recommended to be placed.
  • Title: Suggested Ship Date
    Read Only: true
    Date when the order is recommended to be shipped.
  • Title: Suggested Start Date
    Read Only: true
    Date when work on the order is recommended to begin.
  • Title: Supplier
    Maximum Length: 4000
    Name of the source supplier.
  • Title: Supplier Site
    Maximum Length: 4000
    Abbreviation that indicates the specific supplier location from where the item is being sourced.
  • Value that uniquely identifies the supply transaction. This value is internally generated by the application.
  • Title: Transit Lead Time
    Read Only: true
    Number of days that the supply is in transit between two locations.
  • Read Only: true
    Maximum Length: 200
    Name of the unit of measure associated with the order quantity.
  • Title: UOM
    Read Only: true
    Abbreviation that identifies the unit of measure associated with the order quantity.
Back to Top