Content Comparison

...

1. Allow delete the association from revised ACC.

   1. Remove ASCC/BCC record from DB.
      - The way we are currently taking for rev=1. Unlike ACC/ASCCP/BCCP, ASCC/BCC is removed from DB.
      - History of this action is stored in Log table.

   2. Mark as deleted state.
      - What if add/delete multiple times for the same association. Do we allow the records that have the same den and from_acc/to_asccp?
      - When inserting an association, we may able to use the previous record if it exists.
      - Should we include the CCs of deleted state states in the new release?

   3. Questions
      - How to generate backward compatibility. What if the developer misses the insert?
      - If there are BIE references(for End-user CCs, Extensions), block the deletion.
      - Uplift

      1. for {a.} logic should be changed. b/c we are using GUID for matching key. but we can not keep the removed record's GUID.

      2. for {b.} deleted state association is not available in BIE.

2. Move to (refactor).

   1. based ACCs.
      e.g.
      Production Order Line Base. Details
      - Status Line Base. Details (target from acc)
      - Line Base. Details (o)
      -Line Identification Base. Details (o)

   2. The ACCs that is basing the target ACC.
      e.g.
      Production Order Line Base. Details (o)
      - Status Line Base. Details (target from acc)
      - Line Base. Details
      -Line Identification Base. Details
      - If there are multiple ACCs that are basing the target ACC, it can not be available.
      e.g. Maintenance Order Line Base / Shipment Request Order Line Base / Shop Floor Control Base Line Base ...

   3. Are we allow the move to only {a.} ? if there is only one {b.}, should we allow it?

...