Scribd
Upload
11 views3 pages

Advanced SQL I.6 FS Bridges

The document outlines the specifications for bridges that process records from input tables to populate or update records in destination tables. There are bridges for item, item set detail, LPN detail, LPN lock, pallet, and LPN records. Each bridge processes records from the input table in order and either inserts new records, updates existing matching records, or deletes records in the destination table. Errors are logged and input records are emptied after processing.

Uploaded by

Olivier Comte
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
11 views3 pages

Advanced SQL I.6 FS Bridges

The document outlines the specifications for bridges that process records from input tables to populate or update records in destination tables. There are bridges for item, item set detail, LPN detail, LPN lock, pallet, and LPN records. Each bridge processes records from the input table in order and either inserts new records, updates existing matching records, or deletes records in the destination table. Errors are logged and input records are emptied after processing.

Uploaded by

Olivier Comte
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

-- Advanced SQL Training

Functionnal Specifications of the Bridges:

------------------
-- Bridge items --
------------------

Records of input table Z_INPT_ITEM will be processed in order to populate or update


records in the table Z_ITEM.
The result must be equivalent to processing the records one by one in ascending
INPT_ID order.
If there is a matching record (same REFERENCE), Z_ITEM.DESCRIPTION should be
updated by the new Z_INPT_ITEM.DESCRIPTION.
If not, a new Z_ITEM sould be inserted.

- Phase 2:
After processing, the input table should be emptied without any possibility of
deleting record belonging to a concurrent process.
A DB error should impact only the record that have trigerred it, not the others.
These errors should be logged into Z_ERR_ITEM if any.

----------------------
-- Bridge item sets --
----------------------
Records of input table Z_INPT_ITEM_SET_DETAIL will be processed in order to
populate or update records in the table Z_ITEM_SET_DETAIL.
The result must be equivalent to processing the records one by one in ascending
INPT_ID order.
Quantities in the input table replace existing quantities in Z_ITEM_SET_DETAIL
(they are not additive).
A null or zero quantity means that this detail should be removed from the set.

- Phase 2:
After processing, the input table should be emptied without any possibility of
deleting record belonging to a concurrent process.
A DB error should impact only the record that have trigerred it, not the others.
These errors should be logged into Z_ERR_ITEM_SET_DETAIL if any.

------------------------
-- Bridge LPN details --
------------------------
Records of input table Z_INPT_LPN_DETAIL will be processed in order to populate or
update records in the table Z_LPN_DETAIL.
LPN_NUMBERs that are not in Z_LPN are created with default values.

The result must be equivalent to processing the records one by one in ascending
INPT_ID order.
Quantities in the input table replace existing quantities in Z_LPN_DETAIL (same
LPN, same ITEM).
A null or zero quantity means that this item should be removed from the LPN.
- Phase 2:
After processing, the input table should be emptied without any possibility of
deleting record belonging to a concurrent process.
A DB error should impact only the record that have trigerred it, not the others.
These errors should be logged into Z_ERR_LPN or Z_ERR_ITEM_SET_DETAIL if any.

----------------------
-- Bridge LPN locks --
----------------------
Records of input table Z_INPT_LPN_LOCK will be processed in order to populate or
update records in the table Z_LPN_LOCK.
LPN_NUMBERs that are not in Z_LPN are created with default values.
The result must be equivalent to processing the records one by one in ascending
INPT_ID order.
Adding an existing lock codes for the same LPN does nothing but it is not an error.
Adding a null LOCK_CODE to a LPN means that all lock codes are removed from this
LPN.

- Phase 2:
After processing, the input table should be emptied without any possibility of
deleting record belonging to a concurrent process.
A DB error should impact only the record that have trigerred it, not the others.
These errors should be logged into Z_ERR_LPN or Z_ERR_LPN_LOCK if any.

-------------------
-- Bridge pallet --
-------------------
Records of input table Z_INPT_PLT will be processed in order to populate or update
records in the table Z_LPN.
LPN numbers in LPN_NUMBER or PLT_NUMBER that are not in Z_LPN are created in Z_LPN
with default values (if needed).
The result must be equivalent to processing the records one by one in ascending
INPT_ID order.

- Phase 2:
After processing, the input table should be emptied without any possibility of
deleting record belonging to a concurrent process.
A DB error should impact only the record that have trigerred it, not the others.
These errors should be logged into Z_ERR_LPN if any.

----------------
-- Bridge LPN --
----------------
Records of input table Z_INPT_LPN will be processed in order to populate or update
records in the table Z_LPN.
LPN numbers in LPN_NUMBER that are not in Z_LPN are created in Z_LPN with default
values (if needed).
The result must be equivalent to processing the records one by one in ascending
INPT_ID order.
Existing records (matching LPN_NUMBER) should be updated (LOCATION_ID and
LPN_STATUS). New records are inserted.
The LPN_STATUS 99 is special: it means that the LPN should be deleted.

- Phase 2:
After processing, the input table should be emptied without any possibility of
deleting record belonging to a concurrent process.
A DB error should impact only the record that have trigerred it, not the others.
These errors should be logged into Z_ERR_LPN if any.

- Phase 3:
When deleting a pallet, the deletion must be propagated to every contained LPN
recursively without triggering any error.
When changing the status or the location of a pallet, this change should be
propagated to every contained LPN recursively.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy