SRT: Knowledge Base


Developers Guide

Introduction

This manual is an expansion of the general manual. General points will not be mentioned or explicated here, but technical possibilities will be covered.

Preliminary

The Magento and the Shopware Interface help themselves with the SOAP functionality. Therefore there are further access data needed, especially for the Shops.

  • SOAP WSDL Key [ normally dynamic determined]
  • API Group (all rights given ->Admin)
  • API Username
  • API Password

1. Configuration

1.1 Configuration possibilities of the Automatic Mode

The following parameter can be applied for the automated data alignment. A combination is possible (Example: debugger.exe katexport artikelexport…)

Parameter Module Description
katexport Artikelexport Category alignment
artikelexport Artikelexport Item export
artikelimport_images Artikelexport Entire alignment incl. image export
artikelexport_geaendert Artikelexport Changed article
artikel_geaendert_images Artikelexport Changed article with images
preis_bestand Preis- und Bestand Article inventory / Article price
preis Preis- und Bestand Only price alignment
bestand Preis- und Bestand Only quantity inventory
sonderpreise Aktionspreis Bargain/Special offer price
kundenexport Kundenexport Customer alignment
kundenexport_geaendert Kundenexport Changed customers
bestellimport Bestellimport Import of the ordering
zubehoer_artikel C/U/Z Modul Accessory article
up_selling C/U/Z Modul Up-Selling
cross_selling C/U/Z Modul Cross-Selling
staffelpreise Staffelpreise Quantitative rebate
kundenimport Kundenimport Import of customers
docs_export Dokumentenverwaltung Transfer of the relative documents/technical PDFs
details Will be conducted at the end. Export is dependent on the configuration

1.2 Transformation of a SageDB to MySQL/MSSQL

The migration of SageDB to a MySQL or MSSQL is only necessary in case of buying an ordering-import. In standard the SageDB can be readout, but it is write-protected.

The interface needs a write authorization on the Database for the ordering-import module. You will get the necessary authority through the migration of SageDB.

  1. Install a MySQL/MSSQL-environment (advisable with administration surface)
  2. Start Sage and establish a new „Server“ (Menü->Datei->Serververwaltung)
  3. Jump to mandatory administration and select the desired mandatory with a right click.
  4. Select the option „migrieren“ and follow the installation instruction.

Tip: In an installation of a network all PC-names or IP’s (not allowed to be dhcp) must be added to Apache MySQL.

INSERT INTO user (Host, User, Password, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv, Create_view_priv, Show_view_priv, Create_routine_priv, Alter_routine_priv, Create_user_priv, Event_priv, Trigger_priv, ssl_type, ssl_cipher, x509_issuer, x509_subject, max_questions, max_updates, max_connections, max_user_connections) VALUES (‚WORKGROUP‘, ‚root‘, “, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, ‚Y‘, “, “, “, “, 0, 0, 0, 0);

1.3 Connection of different Database Forms

Database call Database Connection String
ODBC ODBC Provider=SQLOLEDB;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername; Password=myPassword;
MSSQL 2000, MSSQL2000 Microsoft MS SQL <-2005 Server=myServerName\theInstanceName;Database=myDataBase;Trusted_Connection=True;
MSSQL 2005, MSSQL2005 Microsoft MS SQL <-2008 Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
MSSQL 2008, MSSQL2008 Microsoft MS SQL >-2008 Data Source=myServerAddress;Initial Catalog=myDataBase;User Id= myUsername;Password=myPassword;
SQL Server Compact Edition SQL Server Compact Edition Data Source=MyData.sdf;Persist Security Info=False;
SQLBase SQLBase DataSource=myServerAddress;UserId=myUsername;Password=myPassword;
Mimer SQL Mimer SQL Database=myDataBase;Protocol=local;User Id=myUsername;Password=myPassword;
Postgre SQL Postgre SQL Server= myServerAddress;Port=5432;Database=myDataBase;User Id=myUsername;Password=myPassword;
SQL Azure SQL Azure Server=tcp:[serverName].database.windows.net;Database=myDataBase;User ID=[LoginForDb]@[serverName];Password= myPassword;Trusted_Connection=False;Encrypt=True;
MySQL MySQL Server=myServerAddress;Port=1234;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Access MS Access (mdb, accdb) Driver={Microsoft Access Driver (*.mdb, *.accdb)}; Dbq=C:\mydatabase.accdb; Uid=Admin;Pwd=;
Oracle Oracle Data Source=username/password@myserver/myservice: dedicated/instancename;
Informix Informix Database=myDataBase;Host=192.168.10.10;Server=db_engine_tcp;Service=1492; Protocol=onsoctcp;UID=myUsername; Password=myPassword;
Interbase Interbase Driver={Easysoft IB6 ODBC};Server=localhost;Database=localhost:C:\mydatabase.gdb; Uid=myUsername;Pwd=myPassword;
Pervasive Pervasive Server Name=myServerAddress;Database Name=myDataBase;User ID= myUsername; Password=myPassword;
Sybase Advantage Database Sybase Provider=Advantage OLE DB Provider;User ID=adssys;Data Source=MyDataDictionaryPath;Advantage Server Type=ADS_REMOTE_SERVER;
Sybase Adaptive Server Enterprise Sybase Driver={Adaptive Server Enterprise};server=myServerAddress;port=myPortnumber; db=myDataBase;uid=myUsername;pwd=myPassword;
IBM UniData, IBM, IBM UniVerse IBM DATA SOURCE=myDataSource;LOCATION=myLocation;USER ID=myUsername;PASSWORD=myPassword;
IBM DB2 IBM DB2 DataSource=myServerAddress;UserID=myUsername;Password=myPassword; DataCompression=True;
Progress Progress DataSourceName=myDSN;HostName=myServerAddress;Database=myDataBase;LogonID=myUsername; Password=myPassword;PortNumber=2055;
Paradox Paradox; Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\myDb;Extended Properties=Paradox 5.x;
Ingres Ingres Provider=MSDASQL;DRIVER=Ingres;SRVR=xxxxx;DB=xxxxx;Persist Security Info= False;Uid=myUsername;Pwd=myPassword; SELECTLOOPS=N;Extended Properties= „SERVER=xxxxx; DATABASE=xxxxx; SERVERTYPE= INGRES“;
Lightbase Lightbase User=myUsername;Password=myPassword;UDB=USERBASE;Server=myServerAddress;
Firebird Firebird User=SYSDBA;Password=masterkey;Database=SampleDatabase.fdb;DataSource=localhost; Port=3050;Dialect=3; Charset=NONE;Role=;Connection lifetime=15;Pooling=true; MinPoolSize=0;MaxPoolSize=50;Packet Size=8192;ServerType=0;
Teradata Teradata Data Source=myServerAddress;User ID=myUsername;Password=myPassword;
DBMaker DBMaker Provider=DMOLE43;User ID=myUserName;Password=myPassword;Data Source=myDatabaseName;
VistaDB VistaDB Data Source=D:\folder\myVistaDatabaseFile.vdb3;Open Mode=ExclusiveReadWrite;
Netezza DBMS Netezza DBMS Driver={NetezzaSQL};servername=myServerAddress;port=myPortNumber;database=myDataBase; username=myUsername; password=myPassword;
FileMaker FileMaker Driver=FileMaker Pro;AllAsText=0;ApplicationUsingThreads=1;FetchChunkSize=100;FileOpenCache=0; IntlSort=0;MaxTextlength=255;ServerAddress=127.0.0.1; TranslationOption=0;UseRemoteConnection=1;
SharePoint SharePoint Provider=Microsoft.ACE.OLEDB.12.0;WSS;IMEX=2;RetrieveIds=Yes; DATABASE=http://pp1webofficelivecom.officelive.com/Documents/;LIST={5999B8A0-0C2F-4D4D-9C5A-D7B146E49698};

2. Configuration of XML Structures / Modules

In this section, the establishment and the structure of XML will be explained. For the protection of the modules’ flexibility, every module was outsourced in a XML before.

You can find the configurationdata for the export under

„{Installation path/_Struktur/xml/module/}“ and for the import „{Installation path/_Struktur/xml/import/}“.

2.1 Export of the Informations in the Shop

The XML module-data include different SQL-statements. In a change in the parameter sequence you have to pay attention to the online interface which also must be adapted.

If there are only the entries which must be changed, a reconfiguration of the online-interface is not necessary.

Parameter/Feldname Bezeichnung Datentyp
Nummer Categories alphanumerisch
Bezeichnung Category name alphanumerisch
0 Parent Zahl
‚langtext‘ Long-text alphanumerisch
‚1‘ Status Zahl
Nummer.jpg Category image description alphanumerisch
KategorienSortierung Sorting keys Zahl
MetaKeywords Meta keywords alphanumerisch
MetaTitle Meta titel alphanumerisch
MetaDesc Meta description alphanumerisch
suchbegriff Search term alphanumerisch
katSeo Seo Keywords alphanumerisch
sprache LanguageID Zahl
FF1 FF1 alphanumerisch
FF2 FF2 alphanumerisch

2.1.1 Example on Category Export

<MODUL_KATEGORIEN>

select g.Nummer AS KatID, g.Bezeichnung AS KatName, ‚0‘ as Parent, ‚Langtext‘ as Langtext, ‚1@’+g.Nummer as Aktiv_Sortierung, (g.Nummer+‘.jpg‘) AS Kategorie_Bild, g.Nummer AS Kategorie_Sortierung, ‚KeyWords‘ AS Kategorie_MetaKeywords, ‚MetaDesc‘ AS Kategorie_MetaDesc, ‚MetaTitle‘ AS Kategorie_MetaTitle, ‚Suchbegriff‘ AS Kategorie_Suchbegriffe, “ AS Kategorie_SEO, ‚2‘ AS Kategorie_Sprache_Store, “ AS KategorieFF1, “ AS KategorieFF2 FROM gruppen as g where (g.ID = ‚AG‘) AND (g.PARENT is NULL) ORDER BY g.Nummer

</MODUL_KATEGORIEN>

2.1.2 Example on Article Export

<ARTIKEL_MIT_FILTER>

select “ as Artikel_Typ, “ AS Artikel_Kategorie_ID, “ AS Hersteller_ID, “ AS Artikel_Artikelnr, “ AS Artikel_Menge, “ AS Artikel_Preis,“ AS Artikel_Preis1, “ AS Artikel_Preis2, “ AS Artikel_Preis3,“ AS Artikel_Preis4, “ AS Artikel_Gewicht, “ AS Artikel_Status , “ AS Artikel_Steuersatz, Artikelnummer AS Artikel_Bilddatei, “ AS Artikel_VPE, “ AS Artikel_Lieferstatus, “ AS Artikel_Startseite, “ AS SkipImages, “ AS Artikel_Bezeichnung, “ AS Artikel_Text, “ AS Artikel_Kurztext, “ AS Artikel_TextLanguage, “ AS Artikel_MetaTitle, “ AS Artikel_MetaDescription, “ AS Artikel_MetaKeywords, “ AS SuperAttribut, “ AS Aktiv, “ as AttributSet, “ AS Artikel_Variante_Von, “ AS Merkmal, “ AS Auspraegung FROM TABELLE  Artikelnummer like ‚$AktionMitFilter‘ AND getdate()>’$srtTimeStamp‘

</ARTIKEL_MIT_FILTER>

Parameter/Feldname Bezeichnung Datentyp
Artikel_Typ Articletype for Magento

–          Configurable

–          Simple

–          Bundle

–          Grouped

 

Other: 0

alphanumerisch
Artikel_Kategorie_ID Category assignment alphanumerisch
Hersteller_ID Producer alphanumerisch
Artikel_Artikelnr Article number

 

Additional option: EAN

Article number + „@“ + EAN

alphanumerisch
Artikel_Menge Stock Zahl
Artikel_Preis Price (List price, unit price) Zahl
Artikel_Preis1 Price for group 1 Zahl
Artikel_Preis2 Price for group 2 Zahl
Artikel_Preis3 Price for group 3 Zahl
Artikel_Preis4 Price for group 4 Zahl
Artikel_Gewicht Article weight Zahl
Artikel_Status Article status

 

Magento: 1-4

Other: 1

Zahl
Artikel_Bilddatei Articlenumber (Quantity: unbounded) alphanumerisch
Artikel_VPE Packaging unit (ml, l, Stk) alphanumerisch
Artikel_Lieferstatus Deliver status alphanumerisch
Artikel_Startseite Display on the homepage Boolean
SkipImages Leap image editing for certain article Boolean
Artikel_Bezeichnung Article description (Shop: Name) alphanumerisch
Artikel_Text Article long-text (Shop: Long Description alphanumerisch
Artikel_Kurztext Article short-text (Shop: Short Description alphanumerisch
Artikel_TextLanguage Languageid Zahl
Artikel_MetaTitle Metainformation title alphanumerisch
Artikel_MetaDescription Metainformation description alphanumerisch
Artikel_MetaKeywords Metainformation search terms alphanumerisch
SuperAttribut SuperAttribute (Magento type: Configurable) is a filter-possibility in the Shop

 

alphanumerisch
Aktiv Status aktive/inaktive Boolean
AttributSet Magento: the relative attribute-set which bundles the attributes alphanumerisch
Artikel_Variante_Von Parent/Main/Configurable Article number: Server for the assignment of the subordinate article „Variante“ Zahl
Merkmal Article attribute

 

If multiple, then must be divided with an „@“

e.g.: color@size

alphanumerisch
Auspraegung Article specification

If multiple, then must be divided with an „@“

e.g.: blau@12

alphanumerisch
$AktionMitFilter Special feature: filter function alphanumerisch
$srtTimeStamp Special feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

2.1.3 Example on Special Offer Prices

<MODUL_ACTIONSPREISE>

select “ AS Artikel_Artikelnr, “ AS Artikel_Anzahl, “ AS Aktionspreis, “ VonDatum, “ BisDatum, “ FreiFeld1, “ FreiFeld2 FROM Tabelle where  Artikelnummer like ‚$AktionMitFilter‘

</MODUL_ACTIONSPREISE>

Parameter/Feldname Bezeichnung Datentyp
Artikel_Artikelnr Article number alphanumerisch
Aktionspreis Special offer price Zahl
VonDatum Special offer valid from Datum
BisDatum Special offer valid to Datum
FreiFeld1 FreiFeld1 alphanumerisch
FreiFeld2 FreiFeld2 alphanumerisch
$AktionMitFilter Special feature: Filter function alphanumerisch

 

2.1.4 Example on Cross-Selling

<MODUL_CROSS_SELLING>

select ‚cross_sell‘ AS Xsell_Type, “ AS Artikel_Artikelnr, “ AS Xsell_Artikel_Artikelnr, “ AS FreiFeld1, “ AS FreiFeld2, “ AS FreiFeld3, “ AS FreiFeld4 FROM TABELLE WHERE  Artikelnummer like ‚$AktionMitFilter‘ AND getdate()>’$srtTimeStamp‘

</MODUL_CROSS_SELLING>

Parameter/Feldname Bezeichnung Datentyp
Xsell_Type Type: ‚cross_sell‘ alphanumerisch
Artikel_Artikelnr Article number alphanumerisch
Xsell_Artikel_Artikelnr Reference article number alphanumerisch
FreiFeld1 FreiFeld1 alphanumerisch
FreiFeld2 FreiFeld2 alphanumerisch
FreiFeld3 FreiFeld3 alphanumerisch
FreiFeld4 FreiFeld4 alphanumerisch
$AktionMitFilter Special feature: Filter function alphanumerisch
$srtTimeStamp Special feature: In diese Variable wird der akt. Wert eingetragen, sobald der Export durchgelaufen wird. Die Datei mit den aktuellen werden befindet sich in der timestamp.xml Datum

2.1.5 Example on Up-Selling

<MODUL_ARTIKEL_UP_SELLING>

select ‚up_sell‘ AS Xsell_Type, “ AS Artikel_Artikelnr, “ AS Xsell_Artikel_Artikelnr, “ AS FreiFeld1, “ AS FreiFeld2, “ AS FreiFeld3, “ AS FreiFeld4 FROM TABELLE WHERE  Artikelnummer like ‚$AktionMitFilter‘ AND getdate()>’$srtTimeStamp‘

</MODUL_ARTIKEL_UP_SELLING>

Parameter/Feldname Bezeichnung Datentyp
Xsell_Type Typ: ‚up_sell‘ alphanumerisch
Artikel_Artikelnr Artikelnummer alphanumerisch
Xsell_Artikel_Artikelnr Referenz Artikelnummer alphanumerisch
FreiFeld1 FreiFeld1 alphanumerisch
FreiFeld2 FreiFeld2 alphanumerisch
FreiFeld3 FreiFeld3 alphanumerisch
FreiFeld4 FreiFeld4 alphanumerisch
$AktionMitFilter Special feature: Filterfunktion alphanumerisch
$srtTimeStamp Special feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

2.1.6 Example on Accessory Article

<MODUL_ARTIKEL_UP_SELLING>

select ‚up_sell‘ AS Xsell_Type, “ AS Artikel_Artikelnr, “ AS Xsell_Artikel_Artikelnr, “ AS FreiFeld1, “ AS FreiFeld2, “ AS FreiFeld3, “ AS FreiFeld4 FROM TABELLE WHERE  Artikelnummer like ‚$AktionMitFilter‘ AND getdate()>’$srtTimeStamp‘

</MODUL_ARTIKEL_UP_SELLING>

Parameter/Feldname Bezeichnung Datentyp
Xsell_Type Type: related‘ alphanumerisch
Artikel_Artikelnr Article number alphanumerisch
Xsell_Artikel_Artikelnr Reference article number alphanumerisch
FreiFeld1 FreiFeld1 alphanumerisch
FreiFeld2 FreiFeld2 alphanumerisch
FreiFeld3 FreiFeld3 alphanumerisch
FreiFeld4 FreiFeld4 alphanumerisch
$AktionMitFilter Special feature: Filter function alphanumerisch
$srtTimeStamp Special feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

2.1.7 Example on Customer Export

<MODUL_KUNDEN>

select “ AS customers_id_ustidnr, “ AS customers_gender, “ AS customers_firstname, “ AS customers_lastname, “ AS customers_dob, “ AS customers_email_address, “ AS customers_telephone, “ AS customers_fax, “ END AS customers_group, “ AS customers_company, “ AS customers_street_address, “ AS customers_postcode, “ AS customers_city, “ AS customers_countries_iso_code, “ AS customers_password, “ Freifeld1, “ Freifeld2, “ Freifeld3, “ Freifeld4, “ Freifeld5 FROM tabelle WHERE Nummer like ‚$AktionMitFilter‘

</MODUL_KUNDEN>

Parameter/Feldname Bezeichnung Datentyp
customers_id_ustidnr Customer number alphanumerisch
customers_gender Gender alphanumerisch
customers_firstname Name alphanumerisch
customers_lastname Surname alphanumerisch
customers_dob Birth alphanumerisch
customers_email_address E-Mail alphanumerisch
customers_telephone Phone alphanumerisch
customers_fax Fax number alphanumerisch
customers_group Customer group Zahl
customers_company Firm alphanumerisch
customers_street_address Street alphanumerisch
customers_postcode Postcode Zahl
customers_city City alphanumerisch
customers_countries_iso_code Country code (ISO Standard) alphanumerisch
customers_password Customer password alphanumerisch
Freifeld1 Freifeld1 alphanumerisch
Freifeld2 Freifeld2 alphanumerisch
Freifeld3 Freifeld3 alphanumerisch
Freifeld4 Freifeld4 alphanumerisch
$AktionMitFilter Special feature: Filter function alphanumerisch
$srtTimeStamp Special feature: The actual value will be entered in this variable as soon as the export will be ran through. The data with the actual value is in the

timestamp.xml

Datum

 

2.1.8 Example timestamp.xml

The explanation of the verification date is marked with the attribute „FORMAT_TIMESTAMP“. The description of the format begins in row 19.

2.2 Details / Individual Expansion

In the export module, XML-Tags are defined with “DETAILS”, which can be used for subsequent transactions. These tags need the same quantity of parameters and are free configurable.

3. Import

3.1 Ordering-Import

The Ordering-Import is subdivided in 2 processes. First of all the orderings will be imported online in the „\_Struktur\xml\import\orders\opentrans_xml.xml“ and afterwards they will be specified for the relative ERP through „opentrans_xslt.xsl“.

The last step is the importing of the data over the image of XML „xml_into_DB.xml“.

Process order
opentrans_xml.xml -> opentrans_xslt.xsl -> opentrans_xslt_xml.xml -> xml_into_DB.xml

Tip Ordering-Import (Data format)

The ERP New Classic Line, MOS-Tangram, AFS-Software and Lexware XML can archive a data in standard in file INSTALLATION PATH/_STRUKTUR/Bestellung. The establishment of the created data is as the following: DATUM.XML, DATUM.TXT or DATUM.CSV.

3.2 Characteristics of the Ordering-Imports

3.2.1 Characteristic (Sage) New Classic Line

The orderings will be provided for the import as XML File. To import the generated XML, the following steps must be obeyed.

  1. Open the ERP
  2. Select the menu item job-processing -> Webshop
  3. Select Webaufträge aus Datei übernehmen
  4. Push the button F2
  5. Data will be imported

3.2.2 Characteristics of the ERP Sage

In the product-line Sage PC-Kaufmann / Sage GS-Auftrag / Sage GS-Office / Sage GS-Quantum / Sage Office Line the same tables will be used as in the Sage GS Shop import. If the functionalities are deactivated, the following commands must be discharged on the Database.

  1. In the table „sg_sys_objektdaten“ it is about the entry with
    DatenObjectIndex = „bghia_etpsn“. It proofs if this mandatory was newly applied and therefore may not be used with GS-Shop. Please remove the date
  2. The three terms for the GS-Shop activations are: There must be a minimum of one GS-Shop article, customer and procedure.

Alternative:

  • UPDATE sg_sys_objektdaten SET DatenObjektWert = “ WHERE DatenObjektIndex = ‚bghia_etpsn‘;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‚1‘ WHERE DatenObjektIndex = ‚GsShop_sg_auf_artikel@onlineartikel‘;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‚1‘ WHERE DatenObjektIndex = ‚GsShop_sg_adressen@onlinekunde‘;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‚1‘ WHERE DatenObjektIndex = ‚GsShop_sg_auf_fschrift@ausshop‘;
  • UPDATE sg_sys_objektdaten SET DatenObjektWert = ‚1‘ WHERE DatenObjektIndex = ‚GsShop_GssMigratedProductCount‘;
  • UPDATE sg_auf_artikel SET onlineartikel = 1 WHERE SG_AUF_ARTIKEL_PK = (SELECT SG_AUF_ARTIKEL_FK FROM sg_auf_fpos ORDER BY SG_AUF_FSCHRIFT_1_FK DESC LIMIT 1);
  • UPDATE sg_adressen SET onlinekunde = 1 WHERE SG_Adressen_PK=(SELECT SG_Adressen_FK FROM sg_kunden LIMIT 1);
  • UPDATE sg_auf_fschrift SET ausshop = 1 WHERE SG_AUF_FSCHRIFT_PK = (SELECT SG_AUF_FSCHRIFT_1_FK FROM sg_auf_fpos ORDER BY SG_AUF_FSCHRIFT_1_FK DESC LIMIT 1);

3.2.1 Characteristic Lexware

The Ordering-Import through the Lexware XML structure occurs over the e-Business module. Normally you can reach the settings on the Homepage in the menu Extras over the options in the section Configurations – Sale – eBusiness.

3.3 Mapping of opentrans-XML

The opentrans_xslt.xsl is appropriate for the simplified configuration. Hereby it is possible to set fast and new pay- and ordering-conditions.

Example:
<xsl:when test=“ORDER_HEADER/ORDER_INFO/DELIVERY_METHOD = ‚prepayment’“>
<SHIPPING_METHOD>10</SHIPPING_METHOD>
</xsl:when>

The XML-Tag <DELIVERY_METHOD> will be read out of the „opentrans_xml.xml“ and reconverted. Thereby „prepayment“ change to VersandID 10.

4. Automatic Mode / Service

4.1 Installation

To install the interface as a service please start:

„Start -> All Programs -> Microsoft Visual Studio 2008 -> Visual Studio Tools -> Open Visual Studio Command Prompt“ [Image Command Prompt]

entwickler_Auomatik_1

Image: Command Prompt

Afterwards jump to the SRT „Dienst.exe“ in the open Visual Studio Commando Shell. The “Dienst.exe” reside in the installation register.

entwickler_Auomatik_2

Step 2:

When arrived in the correct register, please export the command Installutil Dienst.exe.

 

Step 3:

Start the service under System Control/Service/srtDienst

 

4.2 Un-installation

For the un-installation you must enter the following command in the Visual Studio Commando Shell. Installutil /u Dienst.exe

Related Articles