Edit Order Viewer
Select a row to edit an order. The Details form can be edited only if:
- The current user is authorized to edit the scenario, or the user is a part of the share.
- The user has security access to edit Orders.
You can save changes to the worksheet using the Save Changes option. The data in the form is validated before saving the worksheet. If validation is failed for any field, a notification is sent to the user, and no changes are saved. These validations are performed:
- Any required fields for which data is not populated is displayed as ‘Required’.
-
If the source location is not as base level (only applicable for transactional data of type Transfer not part of the engine), this error message is displayed:
Source Location must be at base level -
If the destination location is not as base level (only applicable for transactional data of type Transfer not part of the engine), this error message is displayed:
Destination Location must be at base level -
If the Delivery/Receipt/End Date is outside the cycle period horizon, this error message is displayed:
Delivery/Receipt/End date must fall within the Cycle Period horizon -
If the Ship/Start Date is after the Delivery/Receipt/End Date, this error message is displayed:
Ship/Start date must be on or before the Delivery/Receipt/End date
Validations are performed when saving the order to ensure that the business key of the order remains unique based on transactional data, item, location, ship/start date, and reference. If a duplicate business key is identified, the order will not be saved and the following error message issued to the user:
Unable to Add/Edit the Order. Duplicate Order with business key ({Item}, {Location},
{Date}, {Transactional Data}, {Reference}) already exists. Note: the reference field can be
used to differentiate records with the same combination of (Item, Location, Date and
Transactional Data).
This process is not saving the scenario, but for applying Order changes to the editable scenario. Unsaved edits can be discarded using the ‘Refresh’ icon.
Order Viewer Details
| Field Name | Description |
|---|---|
|
Order |
The Order definition display name. |
|
Source Measure |
The Source measure description of the Order definition record. |
|
Destination Measure |
The target destination measure description where the Order data is based. |
|
Quantity |
Indicates the value of the Order data record entered by the user. Validated for numerical entry. |
|
Reference |
A text reference for the Order data record. For example, to indicate a unique reference in an external system. Allows for NULL value. |
|
Critical Flag |
Read only field, set to a value of 'None'. |
|
Note |
A large text note for the Order data record. Allows for NULL value. |
|
Custom Field 1 |
A custom text reference for the Order data record. For example, indicate a unique reference in an external system. Field is displayed only if Order data definition is configured to display this custom field. Field label populates the display name else displays the custom field name. |
|
Custom Field 2 |
A custom text reference for the Order data record. For example, indicate a unique reference in an external system. Field is displayed only if Order data definition is configured to display this custom field. Field label populates the display name else displays the custom field name. |
|
Custom Field 3 |
A custom text reference for the Order data record. For example, indicate a unique reference in an external system. Field is displayed only if Order data definition is configured to display this custom field. Field label populates the display name else displays the custom field name. |
|
Custom Field 4 |
A custom text reference for the Order data. For example, indicate a unique reference in an external system. Field is displayed only if Order data definition is configured to display this custom field. Field label populates the display name else displays the custom field name. |
|
Custom Field 5 |
A custom text reference for the Order data. For example, indicate a unique reference in an external system. Field is displayed only if Order data definition is configured to display this custom field. Field label populates the display name else displays the custom field name. |
|
ERP Order Number |
Populated with the ERP order number on imported transactional data. |
|
ERP Line Number |
Populated with the ERP Line number on imported transactional data. |
|
ERP Sub Line Number |
Populated with the ERP Sub Line number on imported transactional data. |
|
ERP Scheduled Line Number |
Populated with the ERP Scheduled Line number on imported transactional data. |
|
ERP Order Status |
Populated with the ERP order Status on imported transactional data. |
|
SCP Order Number |
Populated with the SCP order number on imported transactional data. |
|
SCP Sequence Number |
Populated with the SCP Sequence number on imported transactional data. |
|
SCP Order Status |
Populated with the SCP order Status on imported transactional data. |
Location/Date and Item Fields specific to Type = Transfer
| Field Name | Description |
|---|---|
|
Source |
Selected from a list of base level locations in the current context derived using the Transfer In Source location Attribute in the Engines Supply Allocation Mapping. |
|
Destination |
Selected from a list of base level locations in the current context derived using the Transfer In Destination location Attribute in the Engines Supply Allocation Mapping. |
|
Transport Method |
List of Transportation methods. Selected from a list of Transport methods in the current context derived using the Transfer In Transfer Method Attribute in the Engines Supply Allocation Mapping. The List is filtered based on the Source and Destination defined. |
|
Item |
Displays Item for Order. Item field is not editable. |
|
Ship Date |
Indicates the Ship date of the transactional data record. When Transactional data Enable Lead Time = On If modified, the Receipt Date is updated based on Ship Date + Lead Time. When Transactional data Enable Lead Time = Off There is no link between Ship Date and Receipt date, and consequently the Receipt Date is not updated. |
|
Receipt Date |
When Transactional data Enable Lead Time = On If modified, the Ship Date is updated based on Receipt Date - Lead Time. When Transactional data Enable Lead Time = Off or Transactional data is of type Sum There is no link between Ship Date and Receipt date, and consequently the Ship Date is not updated. |
|
Need Date |
Need Date of item. |
Location/Date and Item Fields specific to Type = Purchase
| Field Name | Description |
|---|---|
|
Location |
Selected from a list of base level Locations in the current context derived using the Purchase row Location Attribute in the Engines Supply Allocation Mapping. If the context is the base Location then the field is pre-populated. |
|
Supplier |
A list of Supplier (attribute) defined in the location hierarchies for the cycle within the current context. Filtered list based on the value in the Location field. Select from the ‘Purchase’ row of Supply Allocation Mapping for Supplier Attribute. |
|
Item |
Indicates the item of the Purchase Order. Selected from a list of base level items in the current context derived using the Purchase Item Attribute in the Engines Supply Allocation Mapping. If the context is the base Item then the field is pre-populated. |
|
Ship Date |
Indicates the Ship date of the transactional data record. When Transactional data Enable Lead Time = On If modified, the Delivery Date is updated based on Ship Date + Lead Time. When Transactional data Enable Lead Time = Off There is no link between Ship Date and Delivery date, and consequently the Delivery Date is not updated. |
|
Delivery Date |
When Transactional data Enable Lead Time = On If modified, the Ship Date is updated based on Delivery Date - Lead Time. When Transactional data Enable Lead Time = Off or Transactional data is of type Sum There is no link between Ship Date and Delivery date, and consequently the Ship Date is not updated. |
|
Need Date |
Need Date of item |
Location/Date and Item Fields specific to Type = Production
| Field Name | Description |
|---|---|
|
Process Item |
Selected from a list of Process Items in the current context derived using the Processes Process Item Attribute in the Engines Supply Allocation Mapping. If the context is at a valid Process Item then the field is pre populated. |
|
Process Location |
Selected from a list of Process Locations in the current context derived using the Processes Location Attribute in the Engines Supply Allocation Mapping. If the context is the base Location then the field is pre-populated. If Process Item is not defined, then the Process Location drop down is empty. |
|
Process Version |
List of Process Versions applicable for the Process Item@Process Location selected. If Process Location and Process Item are not defined, the list is empty. Select from Processes Process Version attribute in the Engines Supply Allocation Mapping. |
|
Item |
Not displayed for Transactional data of type Production. Set ICONST and disabled/hidden. |
|
Start Date |
Indicates the Start date of the production process. If Transactional data Enable Lead Time = On If modified, the End Date is updated based on Start Date + Lead Time. If Transactional data Enable Lead Time = Off If edited, there is no link between Start Date and End date, and consequently the End Date is not updated. |
|
End Date |
Indicates the End date of the production process. When Transactional data Enable Lead Time = On If modified, the Start Date is updated based on End Date - Lead Time. When Transactional data Enable Lead Time = Off or Transactional data is of type Sum There is no link between Start Date and End date, and consequently the Start Date is not updated if the End Date is modified. |
|
Need Date |
Need Date. |
Location/Date and Item fields specific to Transactional Data not assigned to Engine and is of type Transfer
| Field Name | Description |
|---|---|
|
Source Location |
Displays the base Location for the transactional data. Upon editing the standard location hierarchy selector is presented and a base location must be selected. |
|
Destination Location |
Displays the base Location for the transactional data. Upon editing the standard location hierarchy selector is presented and a base location must be selected. |
|
Item |
Displays the base Item for the transactional data. |
|
Ship Date |
Indicates the Ship date of the transactional data record. When Transactional data Enable Lead Time = On If modified, the Delivery Date is updated based on Ship Date + Lead Time. When Transactional data Enable Lead Time = Off If edited, there is no link between Ship Date and Delivery date, and consequently the Delivery Date is not updated. |
|
Delivery Date |
Indicates the delivery date for the transactional data When Transactional data Enable Lead Time = On If modified, the Ship Date is updated based on Delivery Date - Lead Time. When Transactional data Enable Lead Time = Off or Transactional data is of type Sum There is no link between Ship Date and Delivery date, and therefore the ship Date is not updated when the delivery date is edited. |
|
Need Date |
Need Date of item. |
Fields specific to Transactional Data not assigned to Engine and is of type Sum
| Field Name | Description |
|---|---|
|
Name |
Pre-populated based on the Transactional Data measure selected. |
|
Measure |
Derived from the transactional data name. For type Sum it is the measure the transaction data is based. |
|
Item |
Displays the base Item for the transactional data. |
|
Location |
Displays the base Location for the transactional data. On editing the standard location hierarchy selector will be presented and a base location must be selected. |
|
Date |
Date for the Sum Transaction. |