User Tools

Site Tools


tnt2:sysdoc:manifest

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
tnt2:sysdoc:manifest [2019/10/25 09:30]
hubbe
tnt2:sysdoc:manifest [2019/10/25 09:31] (current)
hubbe
Line 30: Line 30:
 When the manifest has been successfully imported into the TnT2 database the next step is to find a valid Purchas Order to match with the manifest. This is done through the PurchasOrderImporter (POImporter) service. Te POImporter is a modular service with a possibility to connect to different PO source systems, currently the implemented modules are: When the manifest has been successfully imported into the TnT2 database the next step is to find a valid Purchas Order to match with the manifest. This is done through the PurchasOrderImporter (POImporter) service. Te POImporter is a modular service with a possibility to connect to different PO source systems, currently the implemented modules are:
  
-  * Maximo+  * SIB Integration platform
  
 The POImporter checks the XML manifest for the required PONum, and looks the PO up in the source system. If there'​s an error the service will set the manifest to the error state and wait for user action through the TnT2 Client, otherwise the PO data is added to the manifest in the database. The POImporter checks the XML manifest for the required PONum, and looks the PO up in the source system. If there'​s an error the service will set the manifest to the error state and wait for user action through the TnT2 Client, otherwise the PO data is added to the manifest in the database.
tnt2/sysdoc/manifest.txt ยท Last modified: 2019/10/25 09:31 by hubbe