HC shoes Network May 19 hearing, the future is technology era, Jinjiang Sports shoes To the impact of high-end enterprise market, it must be a breakthrough in technology. It is gratifying, Jinjiang many Shoe Technological innovation has been to put on the development agenda, the implementation of breakthrough science and technology strategy. Reporter was informed that the technical innovation, Guohui (China) Co., Ltd walk in the forefront of the industry, and achieved great results.

Year, Guohui another heavy attack, the twelfth in the recent China (Jinjiang) International Shoes Expo “Jinjiang City, investment and technology innovation project signing ceremony”, the Guohui with the State Sports General Administration of Sports Science Institute signed a “finite element technology in sports shoe design application”, the project mainly through a common international finite element technology for enterprises of different Sole (Manifested as different materials, different structures) of athletic shoes slip damping performance and performance modeling and analysis, sports shoes, and slip of the damping of the optimum design to achieve the increase shoes, shock absorption, slip Comprehensive performance and grip needs. At the same time, a finite element technology in R & D approach shoes, sports shoes to become an important technique for research and development, ultimately to enhance the technology content of sport shoes purposes.

According to the State General Administration of Sport Sports Science Institute of the person in charge of the project using the finite element analysis software, sports shoes soles of structural design and material selection for the feet and the sole contact with the static analysis, feet and soles stress and displacement distribution in the structure design to test the feasibility of sole, and further optimize the structure provides a theoretical basis, to fill the shoes of our industry in the application of finite element analysis of gaps in the field.

In fact, this is not the Guohui and the General Administration of Sport Sports Science Institute for the first time Cooperation As early as 2007, Guohui will contract with a “shock absorber shoes science and technology cooperation projects”, the State Sports General Administration of Sports Science Institute of the experts of their own design and used Guohui CBA exercise equipment on the G-TECH . DRC double shock absorption technology, shaped air cushioning technology, the two damping technology for improvement, and breakthroughs. In three years of good cooperation based on the two sides once again with the signing of science and technology R & D project “Finite Element Technology in athletic footwear design application” of the cooperation agreement.

Since its inception, Guohui technological innovation have been tireless quest, which operates the CBA exercise equipment is known for prime technology, sponsored by a large number of professional basketball in the same event, Guohui advantage of company resources to actively use the Professional basketball equipment, CBA way for technological innovation: siphon dry technology, armor protection systems, anion aromatic fabric, Aircool, dandelion ultra-light shoes shaped air cushion technique, Coolness (oxygen protection system) and many other innovative technologies to lead industry technology trends.

Addition, Guohui or “China basket, volleyball shoes, professional sports draft national standard units” and “professional sports Clothing General technical specifications and protective equipment standards for the drafting of the national unit “, and has participated in the” Test methods for footwear to help shape national standards degeneration, “” Shoes , With outer soles of athletic shoes without leaving traces of the national standard test method “,” Footwear Test methods for whole shoe wear the national standard, “the three national standard drafting, sports products in China a major force can not be ignored.

Far, Guohui already has nine patents in 2009 alone there are three declared national patent, including the two inventions, a practical new technologies, utility model patent “thermostat shoes,” was named Quanzhou City Excellent Patent Award. Last year, Quanzhou Guohui intellectual property identified as pilot units.

Firmly grasp the “technological innovation” concept, which is Guohui development of the company’s technology provides a solid backing.

1. MS Great Plains platform overview. GP workstation is written in C Shell, named Great Plains Dexterity. It was designed in earlier 1990th, when DB and OS platform independence was the paradigm. However, when Microsoft acquired Great Plains Software seven years ago, Microsoft Dexterity was kind of de-emphasized and GP itself was open for .Net platform and for Microsoft Visual Studio C# and VB developers, especially via eConnect. Plus, GP is available on Microsoft SQL Server DB platform only. Saying these, Microsoft Great Plains version 10.0 and 9.0 should be considered as committed to Microsoft technologies: SQL Server, .Net, Windows, MS Office: Sharepoint, Excel, etc.

2. Cross Platform SQL Queries. If you do it from Microsoft SQL Server 2005 or 2000 side, the construction you typically use is Linked Server, where you should first try ODBC connection to Linux World. If you are on Oracle, then similar construction will allow you to hook up MS SQL Server

3. Web Services. eConnect allows you to open GP objects for non-Microsoft developer via XML web services – you can either use eConnect interface directly or wrap it in custom web service interface

4. eConnect excurse. The core of eConnect is set of MS SQL Server encrypted stored procedures, allowing you manipulate GP master records and work transactions: SOP Entry, POP Receivings, Customers, Vendors to name a few. eConnect has restrictions of GP architecture, one of the typical FAQ is why we can not post GP batches in eConnect? Well, this is the restriction, but you can break it utilizing Albaspectrum posting server. eConnect was dedicated initially to eCommerce software developers, to enable GP ERP platform as backoffice accounting for e-commerce front end

5. Integration technology. Here again eConnect comes to the scenes. GP Integration Manager, which is rather traditional Great Plains integration tool, was recently redesigned partially in eConnect and so IM performance was substantially increased. IM can read tab and comma delimited text files as well as ODBC compliant queries. When you are programming integration, be sure that you select eConnect destination connector as preferred, versus deploying regular destination connector (old-fashioned connectors use GP workstation as OLE Server to validate Great Plains business logic directly in GP screens, which obviously slows down the performance)

1. Hardware Requirements. Microsoft publishes hardware requirements on Partner and Customer source for its Dynamics product line. You should think about hardware requirements from the number of simultaneous users, the role of GP server – if it is dedicate for Great Plains or you plan it to serve additional tasks, such as be Active Directory server or Domain controller for example. We saw public companies, who utilized Microsoft Small Business Server to serve all company systems in one box, to give you amazing example

2. OS Software requirements. Latest Windows server is recommended. You can try 64 bit Windows 2003 server R2 or if at the time of reading Microsoft releases newest server – more likely it is supported and recommended

3. Microsoft Great Plains Implementation Steps. You begin with Microsoft Dynamics GP reseller selection, where you should be comfortable with functional and technical expertise, user training capability, data conversion expertise, and probably overall number of installations to verify the background. When you are done with MBS partner selection, you should concentrate on Great Plains modules selection: majority of GP modules, such as General Ledger, Inventory Control, Manufacturing, Accounts Receivables, Bank Reconciliation, Accounts Payable, Sales Order Processing, Purchase Order Processing, Payroll and HR are Microsoft Dexterity applications. The other set of modules are coming from Microsoft Dynamics GP Business Portal and Sharepoint: Requisition Management former eRequisition, Order Management former eOrder, employee selfservice, Electronic Document Delivery, Key Performance Indicators, here we are talking about Microsoft Great Plains Business Portal 10.0 or 3.0. When you are done with modules selection you can move on to GP installation and test environment with potential user training

4. Data conversion dilemma. Ideally you would like all your historical ERP data to be converted and imported to GP. However this might not be practical, due to high cost and time consumption. We recommend you to consider masters record conversion: customers, vendors, employees, GL chart of accounts and then do GL initial balances transaction entry to close old period in legacy accounting and begin new fiscal period in Microsoft Great Plains. Try to consider the idea of having your legacy accounting system to be available in transition period for data inquiry and lookup

5. Users Training. Future GP users should be involved in Great Plains Chart of account design, especially in its segmentation – GP allows you to sort accounting records by account segment in FRx financial reporting. Then users should participate in modules setup: SOP, POP, RM, PM, Project Accounting, Service Management Suite.

6. Custom Business Logic and Reporting needs covering. If you have specific EDI, data integration needs, industry compliance reports, please check with your MBS partner on the best way to cover these needs. In GP wide range of customization and programming tools is available: Great Plains Dexterity, ReportWriter, MS SQL Server Reporting Services or SRS, GP SDK for Visual Studio Developer (C# and VB.Net are the most popular programming languages), eConnect, Integration Manager, VBA with Modifier, Extender, SQL Views and Stored Procedures to name some

7. GP Version Upgrade. Version update is handled by GP Utilities, however you should know some facts about upgrade to GP 10.0. At this time, December 2007, GP 10.0 Service Pack 1 is available, you should apply it prior to launching upgrade process. Prior to SP 1 upgrade path was available from 9.0 SP2 or GP 8.0 SP5. Upgrade process from technical side replaces GP workstation: Dynamics.dic, Dex.ini, Dex.exe and then it launches utilities. Utilities copy the table, which got new structure in the new version to temp database, then it drops and recreates the table and moves data back from temporary database. In certain situation, this version upgrade process has vulnerability to bugs, typically fixed in Service Packs

8. Other FAQ. What is DEX_ROW_ID? – it is used by Microsoft Dexterity engine and you typically should not include it into data conversion scripts. How do I backup and transfer specific GP table? You use select * into statement, then you drop DEX_ROW_ID and to restore you use insert into select * from construction

1. Great Plains Dexterity. This is Integrated Development Environment or IDE with its own programming language sanscript. Dexterity was designed specially for Great Plains Dynamics in earlier 1990th and this is one of the reasons why Dex is a bit “old-fashioned” and if you are software programmer, you should not expect to begin programming in Dexterity over night. If you are thinking about creation GP extension for the open market, then you should know that most of the extensions are written in Microsoft Dexterity. In order to understand the internal side of Dex, please take a look at Dynamics.set file, where all the products are listed. You begin Dex project by opening Dynamics.dic dictionary and adding or modifying resources in it: forms, reports, windows, fields, scripts, etc. Some Dex hints – copy Dex.ini from your GP workstation folder to your Dexterity application directory – this will allow you to launch Dex in debugging mode. Since version 7.0 Dex can call Microsoft COM objects.

2. eConnect. This tool opens you the access GP work transactions (SOP Invoice, POP Purchase Order, GL record, FA depreciation to name few examples) and master records (customer, vendor, employee, Fixed Asset, General Ledger account). Initially eConnect was designated to eCommerce developers by opening Sales Order Processing, Inventory and Receivables Management modules, but later on it was extended to cover most of the GP objects. You can call eConnect from your Microsoft Visual Studio C# or VB.Net projects, as internal logic of eConnect (business objects) is written in MS SQL Server encrypted stored procedures

3. VBA/Modifier. If you are comfortable with VBA scripting (remember MS Excel modifications?), you can add some logic to existing GP windows, such as SOP Entry screen, where you can put new button with Modifier and then attach VBA script to this field. If you plan to hit GP database from Modifier-added buttons and field, you should deploy ADO technology, where more likely you will have to hardcode user ID and password. Modifier allows you to include GP Dexterity sanscript scriplets into the VBA code – this allows you to use Continuum for VBA technology to switch GP modules and manipulate Dexterity objects across your multi-module GP workstation, however this technique is very complex and typically causes expensive version upgrade work

4. SQL Scripting. One of the most popular routines, where you deploy SQL stored procedures is Electronic Document Interchange or EDI. EDI has header, body and trailer and you deploy such SQL constructions as CAST, CONVERT to address fixed length fields EDI formatting

5. GP Integration. Microsoft Dynamics GP Integration Manager should be considered first – it is possible to extend IM with VBA scripting and fields translation table (you can create translation table in Excel and then import it to Integration Manager). If IM doesn’t do the job, consider eConnect, SQL scripts and Dexterity. Please, be aware – IM validates GP business logic and this prevents you from all the possible errors in integration. SQL scripting, in opposite doesn’t validate GP logic and by not doing so – it may compromise your data integrity

6. Modification Upgrade. Obviously you should expect some complication in GP version update if you deploy custom GP development technologies. In the case of Great Plains Software Dexterity alternative logic, you should keep Dynamics.dic or Extract.dic with modification scripts in them – Dex developer should be able to upgrade your custom logic. Talking about Modifier with VBA – if you do not deploy Continuum modules switch tricks, upgrade should be straightforward. IM typically is GP version proof. To give you additional version update considerations – Great Plains versions 7.5 and earlier: 7.0, 6.0, 5.5, 5.0, 4.0 and 3.2 were available on alternative DB platforms: Btrieve (later on this DB was renamed into Pervasive SQL Server), Ctree/Faircom, and respectively, if you are on these legacy platforms, your modified logic might deploy programming constructions, specific to these DB platforms only – if you are thinking to upgrade to recent GP version (10.0 or 9.0) – you should come through custom logic porting to Microsoft SQL Server 2005 and 2000

7. GP Reporting tools. ReportWriter is Dexterity module and it is seamlessly integrated in GP workstation interface and GP security model. Report Writer reports are stored in Reports.dic. RW is typically used when you need to modify GP existing reports: SOP Invoice Long Form (place your company Logo is classical example). Crystal Reports – you should consider good report design practice to offload report record set creation to MS SQL Server stored procedure or SQL view. SRS or Microsoft SQL Server Reporting Services – in our opinion this tool is competitor to CR and you should be aware to use similar strategy – placing record set selection logic to SQL stored procs. You can also deploy MS Excel and MS Access to do reporting for GP – please research ODBC connection options for these tools

8. GP modules licensing consideration. Depending on your GP version – GP professional, standard or business ready, you should be aware that custom modules might require additional purchases, please contact you Microsoft Business Solution partner or MBS ISV

9. Data conversion consideration. If you are switching from legacy MRP, such as Accpac, MYOB, PeopleSoft, Oracle EBusiness Suite/Financials/Applications, JD Edwards, QuickBooks, PeachTree, MAS 90/2000 to GP, data migration and massage might be required. We recommend you to keep legacy accounting system for data inquiry and lookup and do not do historical ERP data conversion to Great Plains. However if historical transactions migration is required, please contact us for the data cleansing quote