preview

Analysis Of PDGO Records In The IBM Target Systems From The Hub

Decent Essays

2.2 Assumptions 1. The scope of this document is to provide functional design of an interface that will create, update and inactive PDGO records in the IBM Target System from the Hub. 2. Once the Hub is implemented it will not possible to create a new record within the IBM other than by having it passed through from the Hub. 3. When a new Item record is created in the Hub and passed to the IBM MQ, SOA will be able to insert 1:Many, into the DRM cross reference. This can only happen when the IBM Product is approved. This will establish the relationship between the Hub and the IBM Item number . 4. Some fields that will be sent from the Hub will be over written in the IBM staging table. 5. There will be fields within the IBM PDGO system …show more content…

The application should be capable of handling insert, updates and / or delete operation. 16. IBM will create/expand another column to store the MDM ID which would continue to be used when MDM becomes a sole Hub. 17. IBM initial load: the system should be able to receive messages for heavy load. 18. IBM will provide details and or response from IBM MQ to SOA. 2.3 Dependencies 1. Item cross reference tables in DRM must be updated after data conversion prior to turning the interface on. 2. Item fields will be defined in the Hub to choose from when creating/updating. 3. All applicable Attribute values are defined in the Hub and mapped to the proper field in the IBM staging table. 4. “Unique Item” is a Item classification, key ‘specific’ attributes, packaging type, weight, and labeling. 5. In the Hub, a unique item is equivalent to a (product code + container code). 6. In the IBM, the product group + product code + container group + container code is considered a unique item. 7. In DRM, the x-ref table will display the Hub ID which can have 1 to many (1:M) Product Group, Container Group, Product Code, and Container Code in the IBM. This will allow the IBM to be able to maintain unique items by business unit. 2.4 Security, Integrity and Controls 1. To enforce synchronization between the Hub and the IBM, certain fields in the IBM that receives information from the

Get Access