About Revision Order In OSM
The new version of the order includes all of the data relevant to the order, not just changed data.
A revision Order can have :-Change ,Remove ,ADD in existing Data.
Steps In OSM for Revision Order :-
1. OSM Check for Order Amendable or not, in the Amendable tab of Order you can check it .
2. OSM checks in-flight orders for a matching value to an order key,in the Amendable tab of Order you can check it how to find the Order Key and Version
3. Now OSM check the base order allowed to be amended.
3.1. Order Should not be in Not Started, Completed, or Aborted state(OLP).
3.2. Check for PONR, should not passed the point of no return.
3.3. Check for Version , Lower version will get ignored .
If a revision cannot be processed, or if the order life-cycle has not allowed the revision,
the revision order is set to the Failed state, and the base order continues to be processed.
4. Analyzing order data
4.1 At order Level , revision order data and the base order data .
4.2 At task level , OSM compares task data for each task in the order process to further validate the compensation requirements for DO,REDO,UNDO .
4.3 Check for significance data .
5. For orchestration orders, the order components of the orchestration plan are analyzed to determine which order components need to be redone, undone, or done for the first time (amend do).
The tasks of the sub-processes run for each of those order components to be compensated are also analyzed.
6. Any order components with data that has changed as a result of the revision are redone.
Any order components that have been processed but are no longer required in the revision are undone in reverse dependency sequence.
Any order components that are inserted as new requirements are fulfilled
The new version of the order includes all of the data relevant to the order, not just changed data.
A revision Order can have :-Change ,Remove ,ADD in existing Data.
Steps In OSM for Revision Order :-
1. OSM Check for Order Amendable or not, in the Amendable tab of Order you can check it .
2. OSM checks in-flight orders for a matching value to an order key,in the Amendable tab of Order you can check it how to find the Order Key and Version
3. Now OSM check the base order allowed to be amended.
3.1. Order Should not be in Not Started, Completed, or Aborted state(OLP).
3.2. Check for PONR, should not passed the point of no return.
3.3. Check for Version , Lower version will get ignored .
If a revision cannot be processed, or if the order life-cycle has not allowed the revision,
the revision order is set to the Failed state, and the base order continues to be processed.
4. Analyzing order data
4.1 At order Level , revision order data and the base order data .
4.2 At task level , OSM compares task data for each task in the order process to further validate the compensation requirements for DO,REDO,UNDO .
4.3 Check for significance data .
5. For orchestration orders, the order components of the orchestration plan are analyzed to determine which order components need to be redone, undone, or done for the first time (amend do).
The tasks of the sub-processes run for each of those order components to be compensated are also analyzed.
6. Any order components with data that has changed as a result of the revision are redone.
Any order components that have been processed but are no longer required in the revision are undone in reverse dependency sequence.
Any order components that are inserted as new requirements are fulfilled
No comments:
Post a Comment