Order Status
Revision as of 09:20, 1 June 2022 by Stefanseiler (talk | contribs)
Every type of order has a variety of different statuses which it must run through until it reaches the user. These steps will be shown for every order type to make the statuses of every order more understandable.
The usual order of statuses for a order will look like this:
UI wording
(EN) |
Dev-InternalOrderStatus (new) | Dev-DistributionOrderStatus (old) | Comment |
---|---|---|---|
incomplete-data | incomplete-data | The order is in a preliminary state (e.g. during 3rd-party system integration) and should not be processed until a created-state is reached. | |
preliminary | creation-pending | creation-pending | The order is in a preliminary order and should not be processed untill a created-state is reached |
preorder | created-as-preorder | The order was created but is waiting in the system until the preorder-triggerdate is reached or the preorder is manually triggered | |
created | created | created | The order was created |
adopted | created-by-transferFromOldSystem | This is to be handled as a boolean property of the Internal order | |
waiting for clearance | waiting-for-clearance | waiting-for-approval | this is the status triggering the clearance process. Clearance process agent will look for material and financial cliearance reuiqrements and request the clearance. Both clearance requests (material and financial) can be sent at the same time of one-by-one depending on the presettings material group ("Ask for material clearance ahead of financial clearance"). This entire status will be skipped if no clearance requiredment applies and the order is directly moved to the status cleared. |
cleared | clearance-granted | The order has recieved the clearance grant (material and financial). Immediately after recieving this status, the order will be activated. As a result this status will only be a status-entry, as the order will never stay in this status | |
rejected | clearance-rejected | rejected | The clearance of the order was either materially or financially rejected. Details of the rejection can be found in the clearance process tables |
unprocessable | autofulfillment-failed | skipped | The background fulfillment engine, which triggeres purchase orders, shipment orders, production orders could not successfully process the internal oder. Action is required |
active | active | processed | This order is currently active is fulfillment is in progress (disposition, shipment, procurement, ... is active). Status of these orders can be retrieved at the corresponding business objects. |
cancellation requested | cancellation-requested | cancellation-started | A full or partial cancellation request is running and eventually needs to be cleared by the supply-chain-processors (fulfillment, suppliers, ... ) |
cancellation granted | cancelleation-request-accepted | partially-canceled | The canncellation request was accepted and the entire order or single positions are adapted as filed in the request. The order returns to the status active (if no other cancellation-requests is active). This status will only be a status-entry, as it will never stay in this status |
cancellation rejected | cancellation-request-rejected | cancellation-failed | The cancellation request was rejected, the order stays as it was before the cancellation request. The order returns to the status active (if no other cancellation-requests is active). This status will only be a status-entry, as it will never stay in this status |
cancelled | cancelled | cancelled | The order was cancelled entirely |
<hide in UI> | partially-delivered | The fulfillment team (no matter if internal or external) has informed that goods have been partially shipped and eventually arrived (they dont know). This status iis obsolete and should in both models not be used any more - instead the partially delivered and fully delivered information should be retrieved from the ExpectedDelivery-Objects bound to the internal order. | |
<hide in UI> | delivered | The fulfillment team (no matter if internal or external) has informed that all ordered goods have been shipped and eventually arrived (they dont know).This status iis obsolete and should in both models not be used any more - instead the partially delivered and fully delivered information should be retrieved from the ExpectedDelivery-Objects bound to the internal order. | |
<hide in UI> | receipt-partially-confirmed | At least one of the shipments has arrived. This status is obsolete and should in both models not be used any more - instead the partially delivered and fully delivered information should be retrieved from the ExpectedDelivery-Objects bound to the internal order. | |
<hide in UI> | receipt-confirmed | At expected shipments have arrived. This status is obsolete and should in both models not be used any more - instead the partially delivered and fully delivered information should be retrieved from the ExpectedDelivery-Objects bound to the internal order. | |
completed | completed | finished | The fulfillment of this order has been completed (all goods which were expected have arrived) |
Internal Order / Distribution Order
The actual statuses for a DO are:
- Created, release required: The order has been created. Your team leader has to check and release the order in order for it to reach the responsible user.
- Transferred from old system: If the order was created in a old system and was transferred to this system for clarity.
- Order data incomplete: Some part of data is still missing. Please check the order to fill in the missing information.
- Partly cancelled: It was only possible to cancel some articles. The rest of the order will still be delivered.
- Partly delivered: Some parts of the order have reached their final destination. Check the order details to see what the status of the other parts is.
- Partly confirmed: If some parts were found missing in the order and the user has only partly confirmed the receipt, this status will show.
- Denied: ?
- Skipped: This order was skipped and will be fulfilled later.
- Accepted: The order has been run checked by the system and will be created.
- Creation pending: The system is still working on creating your order.
- Created: The order has been created and has reached the responsible user.
- Delivered: The order is has been delivered.
- Receipt confirmed: When the order has arrived at its final destination, the user can confirm the delivery.
- Done: ??
- Cancellation failed: It was not possible to cancel the order.
- Cancellation started: This will be shown, if the user wants to cancel the order and the system has started running through the cancellation process.
The actual statuses for a PO are:
- ...
The actual statuses for a CO are:
- ...
The actual statuses for a SH are: