Several ways to use T4s to integrate report exceptions (ERROR handling) in SAP system applications in Teamcenter environments

In an enterprise, if both Teamcenter and SAP are on-line, the integration of data and processes between the two is essential, and a simple example is the ability to transfer a part designed in Teamcenter to SAP for the purchase or manufacture of the part. If you are integrating Teamcenter and SAP, the enterprise can develop its own interface or use the T4s (Teamcenter Gateway for SAP) under the Teamcenter platform. However, companies need to take full account of the data transfer process of different I often, because no one can guarantee that each pass is the data is valid, both sides of the system is not a problem.

If you are using T4s to integrate teamcenter and SAP, you can make full use of the T4s log system to report exceptions. T4s's logs fall into the following categories:

If the T4s application appears to be abnormal, you can learn from the transaction log that there is a problem with the link, and then you can get information about that link from the session log. This is written in all the details, without the developer or PLM administrator to customize it, just know how to view the log. You can output the useful information to transaction Log via T4s mapping, which makes the data transfer transparent and the user can see when and where the data can be transferred at any time.

If the T4s data transfer is a task in a process, if the task has an exception, the information about the exception must be displayed to the Teamcenter process window, telling the user what happened. This instance shows that the UOM supported in the ERP system does not include the UOM of the part in the Amcenter, or uom undefined, which is the exception that the data does not conform to the specifications of the ERP system, and in T4s, you can check these exceptions by defining mapping logic. and shown to be used, the specific code is as follows:

# Converte Weight UOM TC 2 ofbiz
switch-exact [string ToUpper $TCUomId] {
{KG} {Set Ofuomid "wt_kg"}
{G} {set Ofuomid "Wt_g"}
{LB} {Set Ofuomid "wt_lb"}
Default {
:: T4x::translog::writecustommappinglog $TransactionId ERROR "Weight UOM (t4ea_string_04) > $TCUomId < not_ Supported (only KG, G and LB supported) "
:: T4x::core::storemessage "Weight UOM (T4EA_WEIGHT_UOM) > $TCUomId < not_supported (only KG, G and LB supported)" Erro R TEXT
Return ERROR
}
}

Definition:: T4x::core::storemessage to display information to the TC's process window,

Definition:: T4x::translog::writecustommappinglog to display information to T4S transaction Log, which can be viewed through the admin GUI of T4s.

Several ways to use T4s to integrate report exceptions (ERROR handling) in SAP system applications in Teamcenter environments