{"id":3069,"date":"2011-04-29T08:20:04","date_gmt":"2011-04-29T00:20:04","guid":{"rendered":"http:\/\/www.sivecochina.com\/en\/?p=3069"},"modified":"2014-10-22T09:26:14","modified_gmt":"2014-10-22T09:26:14","slug":"coswin_tips_tricks-integration_tools","status":"publish","type":"post","link":"https:\/\/newsletter.bluebeecloud.com\/en\/tips-tricks\/coswin_tips_tricks-integration_tools\/","title":{"rendered":"COSWIN: Integration tools"},"content":{"rendered":"
There are 4 basic methods for interoperability and integration in COSWIN.<\/div>\n

 <\/p>\n

1.Plug-ins<\/strong><\/div>\n

 <\/p>\n

Which are extensions to programs or even new modules that can connect to other data sources (another server) and process or create new data.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

These programs are integrated seamlessly into the COSWIN module and execute into the application server. For example a plug-in may open a web service connection to SAP and capture a purchase order that has been created in SAP, write the details to COSWIN and process the data as if created with COSWIN. The plug-ins may or may not neeed a user interaction \u2013 in this case, their existence is completely hidden to the final user.<\/div>\n

 <\/p>\n

2.Interface tables<\/strong><\/div>\n

 <\/p>\n

<\/div>\n
The COSWIN database has two main parts to it, the database proper and within the modules the interface tables. The interface tables act as a buffer and a listener, so that if there is data outside of COSWIN that needs to be imported it will be picked up by the interface table and processed according to the table logic. Interface tables work in both directions: data from COSWIN that has to be communicated to a process or an application outside will likewise pass through the interface table to be picked up by the target process.<\/div>\n

 <\/p>\n

3.Clic-Clac & EDI<\/strong><\/div>\n

 <\/p>\n

<\/div>\n
Clic-Clac is a native COSWIN tool that can read data from text files, almost all the common applications such as Excel can export in .txt format compatible with Clic-Clac.<\/div>\n

 <\/p>\n

It is used to load or modify large volumes of data such as equipment registers or stock item reference data. The original data is imported into the COSWIN database in the format of multiple lines. It can be done in batch mode and once injected to COSWIN becomes normal COSWIN data as if entered by keyboard.<\/div>\n

 <\/p>\n

EDI is an optional module that allows importing in COSWIN transactions that have been collected by external computer applications. This is very useful when you have data collected by other applications or hardware such as handheld terminals, BAS system, stores management for manufacturing etc.<\/div>\n

 <\/p>\n

EDI works on a variety of transactions:<\/strong><\/div>\n

 <\/p>\n

Work Order, Job Requests, Issues of items or parts. The interface is very user-friendly.<\/div>\n

 <\/p>\n

 \u2022 Via dictionaries the user chooses the data destination of the input files
\n \u2022 EDI controls the data integrity
\n \u2022 The memorized parameterization can be run in one or several steps
\n \u2022 EDI can be controlled by an external program<\/div>\n

 <\/p>\n

4.Web Services<\/strong><\/div>\n

 <\/p>\n

COSWIN also offers Web Services that will give outside applications control over selected COSWIN data and functionality and vice versa.<\/div>\n

 <\/p>\n

<\/div>\n
Web services are more sophisticated and comprehensive in their potential integration between applications. For instance, following an incident in COSWIN maintenance and the need for say parts, COSWIN would raise a purchase request at \u2460 Via a COSWIN plugin at \u2461 the data would be sent to another application, say Oracle Purchase or Procurement module \u2462 Oracle has its own processing\/validation rules and the purchase request will be transformed into an order in Oracle \u2463 The order is then sent back to COSWIN via Web Services \u2464 and this will trigger the creation of an identical order in COSWIN\u2465.<\/div>\n","protected":false},"excerpt":{"rendered":"
There are 4 basic methods for interoperability and integration in COSWIN.<\/div>\n

 <\/p>\n

1.Plug-ins<\/strong><\/div>\n

 <\/p>\n

Which are extensions to programs or even new modules that can connect to other data sources (another server) and process or create new data.<\/div>\n

 <\/p>\n

<\/div>\n

 <\/p>\n

These programs are integrated seamlessly into the COSWIN module and execute into the application server. For example a plug-in may open a web service connection to SAP and capture a purchase order that has been created in SAP, write the details to COSWIN and process the data as if created with COSWIN. The plug-ins may or may not neeed a user interaction \u2013 in this case, their existence is completely hidden to the final user.<\/div>\n

 <\/p>\n

2.Interface tables<\/strong><\/div>\n

 <\/p>\n

<\/div>\n
The COSWIN database has two main parts to it, the database proper and within the modules the interface tables. The interface tables act as a buffer and a listener, so that if there is data outside of COSWIN that needs to be imported it will be picked up by the interface table and processed according to the table logic. Interface tables work in both directions: data from COSWIN that has to be communicated to a process or an application outside will likewise pass through the interface table to be picked up by the target process.<\/div>\n

 <\/p>\n

3.Clic-Clac & EDI<\/strong><\/div>\n

 <\/p>\n

<\/div>\n
Clic-Clac is a native COSWIN tool that can read data from text files, almost all the common applications such as Excel can export in .txt format compatible with Clic-Clac.<\/div>\n

 <\/p>\n

It is used to load or modify large volumes of data such as equipment registers or stock item reference data. The original data is imported into the COSWIN database in the format of multiple lines. It can be done in batch mode and once injected to COSWIN becomes normal COSWIN data as if entered by keyboard.<\/div>\n

 <\/p>\n

EDI is an optional module that allows importing in COSWIN transactions that have been collected by external computer applications. This is very useful when you have data collected by other applications or hardware such as handheld terminals, BAS system, stores management for manufacturing etc.<\/div>\n

 <\/p>\n

EDI works on a variety of transactions:<\/strong><\/div>\n

 <\/p>\n

Work Order, Job Requests, Issues of items or parts. The interface is very user-friendly.<\/div>\n

 <\/p>\n

 \u2022 Via dictionaries the user chooses the data destination of the input files
\n \u2022 EDI controls the data integrity
\n \u2022 The memorized parameterization can be run in one or several steps
\n \u2022 EDI can be controlled by an external program<\/div>\n

 <\/p>\n

4.Web Services<\/strong><\/div>\n

 <\/p>\n

COSWIN also offers Web Services that will give outside applications control over selected COSWIN data and functionality and vice versa.<\/div>\n

 <\/p>\n

<\/div>\n
Web services are more sophisticated and comprehensive in their potential integration between applications. For instance, following an incident in COSWIN maintenance and the need for say parts, COSWIN would raise a purchase request at \u2460 Via a COSWIN plugin at \u2461 the data would be sent to another application, say Oracle Purchase or Procurement module \u2462 Oracle has its own processing\/validation rules and the purchase request will be transformed into an order in Oracle \u2463 The order is then sent back to COSWIN via Web Services \u2464 and this will trigger the creation of an identical order in COSWIN\u2465.<\/div>\n","protected":false},"author":1,"featured_media":8349,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,259],"tags":[26],"_links":{"self":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/3069"}],"collection":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/comments?post=3069"}],"version-history":[{"count":2,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/3069\/revisions"}],"predecessor-version":[{"id":8550,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/posts\/3069\/revisions\/8550"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media\/8349"}],"wp:attachment":[{"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/media?parent=3069"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/categories?post=3069"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsletter.bluebeecloud.com\/en\/wp-json\/wp\/v2\/tags?post=3069"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}