Sorry, this entry is only available in Deutsch. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.

Die Verwaltung synchronisierter Verzeichnisse ist mit eBiss 3 möglich.

Man benötigt dazu jeweils einen Harddisk ChannelReceiver, den passenden ChannelSender und einen FileEventListener.

Damit nur jeweils geänderte Dateien übertragen werden, prüfen die EventListener auf das ArchivFlag, nur wenn eine Datei geändert wurde, erhält sie das ArchivFlag.
Die Dateien werden abgeholt, übermittelt und auf der anderen Seite wieder geschrieben.

Konfiguration des  EventListeners:

OnlyCheckFilesWithArchiveFlag prüft auf Dateien mit Archive Flag. Anders als sonst, wird auch auch geprüft, dass keine versteckten Dateien ausgelöst werden, außerdem muss sich die Datei auch noch exclusiv öffnen lassen, sonst schlägt der EventListener nicht an. (Man kann das im LogDebug nachverfolgen).

 

 Neue FileHandling Methode im HarddiskReceiveChannel:

Stellen Sie den Channel so ein, dass er exclusiv lockt:

Neue Einstellung im Harddisk ChannelSender für FileExists Handling:

Eine funktionierende Beispielkonfiguration ist in StandardTemplates unter DirectorySync zu finden.

 

Zusätzlich zu den vorgestellten neuen Eigenschaften gibt es noch zwei Erweiterungen. Zum einen prüft der HarddiskChannelSender auf ein gesetztes ArchiveFlag beim Schreiben und falls er das findet (Datei wurde auch beiden Seiten geändert), wird die neue Datei mit einem Zähler daneben gelegt, damit die Benutzer die Möglichkeit haben die Änderungen zusammenzuführen.

Man kann dem HarddiskReceiver nun ein MaxKB Limit mitgeben, damit nicht alle Daten sofort abgeholt werden (Im Falle grosser Verzeichnisse). Dann nimmt er so lange Dateien, bis die Grenze zum ersten mal überschritten ist, aber eben mindestens eine Datei.

Zusätzlich hat man die Möglichkeit mit der neuen JobBox MEssageContentRemover, den Inhalt grosser Dateien direkt wieder aus dem MessageStore zu entfernen.

 

 

 

 

IT terms
Cross Docking Procedure in which goods pre-picked for a final destination in a distribution warehouse are only redistributed at package level.
CRP program The Cyclic Replenishment Program is a procedure for the regular replenishment of articles.
EAN The international (formerly European) article number is an internationally unique article identification.
EANCOM A subset of EDIFACT, carried by EAN.UCC, specifically for retail and consumer goods.
EAN International The umbrella organisation for the allocation of article and company identifications looks after various standards, including EANCOM.
EAN.UCC The umbrella organization of EAN International and UCC.
EDI Electronic Data Interchange is a generic term for the structured exchange of data between applications.
EDIFACT Electronic Data Interchange For Administration, Commerce and Transport is an internationally standardized basic standard of EDI, supported by UN and ISO.
GLN The Global Location Number is an internationally unique identification of a company and is assigned by the EAN.UCC.
GTIN The Global Trade Item Number is the successor of the EAN and UPC.
Material EDI The profile of the DTB for data exchange between producer and supplier.
NCTS The New Computerized Transit System is a computerized transit system in Europe in connection with customs.
PLV The passive contract processing.
SSCC The Serial Shipping Container Code is an EAN package identifier.
Subset A subrange of a standard, e.g. EANCOM from EDIFACT.
UPC The Universal Product Code is an equivalent of the EAN in the USA.
VAN The Value added network is a value-added service, i.e. networks with additional services to the pure connection.
WWS profile EANCOM application profile for lifestyle retail
XML/EDI Electronic Data Interchange using eXtensible Markup Language describes electronic data interchange using XML or approaches such as ebXML, Bizztalk, but not yet a standard.

Information on bank details can be provided in segment FII.

This is located in segment group 2 and is usually indicated after the NAD segment for the invoicing party as follows:

 

Financial Institution Information (Bankverbindung)

Financial Institution Information (Bankverbindung)

Complete Ruleset

Insert the following code via clipboard into the desired segment group 2 and add your corresponding information:

EBISS_MAP_ITEMS<XmlSerializerRoot><TypeReferences><Type Name=”eBiss.ClassLib.Maps.Mapping” Assembly=”eBiss.ClassLib, Version=3.2.186.21404, Culture=neutral, PublicKeyToken=null” /><Type Name=”eBiss.ClassLib.Maps.MappingRule” Assembly=”eBiss.ClassLib, Version=3.2.186.21404, Culture=neutral, PublicKeyToken=null” /><Type Name=”eBiss.ClassLib.Maps.MappingRuleSet” Assembly=”eBiss.ClassLib, Version=3.2.186.21404, Culture=neutral, PublicKeyToken=null” /><Type Name=”eBiss.ClassLib.Maps.MapSelector” Assembly=”eBiss.ClassLib, Version=3.2.186.21404, Culture=neutral, PublicKeyToken=null” /><Type Name=”eBiss.ClassLib.Maps.RuleCollection” Assembly=”eBiss.ClassLib, Version=3.2.186.21404, Culture=neutral, PublicKeyToken=null” /><Type Name=”System.Collections.ArrayList” Assembly=”mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ /><Type Name=”System.Collections.Generic.List`1[[System.Object, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]” Assembly=”mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ /><Type Name=”System.Version” Assembly=”mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ /></TypeReferences><Classes><Class Type=”System.Collections.Generic.List`1[[System.Object, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]” RefId=”0-List`1″><Properties><Ref-Property Name=”Item-0″ Ref=”1-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRuleSet” RefId=”1-MappingRuleSet”><Properties><Data-Property Name=”ValidateCreatedObjects” Val=”false” /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”RuleSetBehaviour” Val=”0″ /><Data-Property Name=”MaxLoops” Val=”10000″ /><Data-Property Name=”Description” Val=”Financial Institution Information (Bankverbindung)” /><Data-Property Name=”Name” Val=”rs_FII” /><Data-Property Name=”Selection” Val=”.” /><Data-Property Name=”Target” Val=”FII” /><Ref-Property Name=”Rules” Ref=”1612-RuleCollection” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.RuleCollection” RefId=”467-RuleCollection”><Properties><Ref-Property Name=”Item-3″ Ref=”1-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.RuleCollection” RefId=”1612-RuleCollection”><Properties><Ref-Property Name=”Item-0″ Ref=”1613-MappingRule” /><Ref-Property Name=”Item-1″ Ref=”1616-MappingRuleSet” /><Ref-Property Name=”Item-2″ Ref=”1630-MappingRuleSet” /><Ref-Property Name=”Item-3″ Ref=”1656-MappingRule” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1613-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3035″ /><Data-Property Name=”Target” Val=”@DE_3035″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”‘BF'” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”Description” Val=”BF = Beneficiary’s bank. Identifies the account servicer for the beneficiary or the payee.” /><Ref-Property Name=”Parent” Ref=”1-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRuleSet” RefId=”1616-MappingRuleSet”><Properties><Ref-Property Name=”Parent” Ref=”1-MappingRuleSet” /><Data-Property Name=”ValidateCreatedObjects” Val=”false” /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”RuleSetBehaviour” Val=”0″ /><Data-Property Name=”MaxLoops” Val=”10000″ /><Data-Property Name=”Description” Val=”ACCOUNT IDENTIFICATION ” /><Data-Property Name=”Name” Val=”rs_DG_C078″ /><Data-Property Name=”Selection” Val=”.” /><Data-Property Name=”Target” Val=”DG_C078″ /><Ref-Property Name=”Rules” Ref=”1617-RuleCollection” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.RuleCollection” RefId=”1617-RuleCollection”><Properties><Ref-Property Name=”Item-0″ Ref=”1618-MappingRule” /><Ref-Property Name=”Item-1″ Ref=”1621-MappingRule” /><Ref-Property Name=”Item-2″ Ref=”1624-MappingRule” /><Ref-Property Name=”Item-3″ Ref=”1627-MappingRule” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1618-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3194″ /><Data-Property Name=”Target” Val=”@DE_3194″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;AcountHolderNumber&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”Description” Val=”Account holder number (IBAN)” /><Ref-Property Name=”Parent” Ref=”1616-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1616-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1621-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3192″ /><Data-Property Name=”Target” Val=”@DE_3192″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;AcountHolderName&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1616-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1616-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1624-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3192_2″ /><Data-Property Name=”Target” Val=”@DE_3192_2″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;AcountHolderName&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1616-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1616-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1627-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_6345″ /><Data-Property Name=”Target” Val=”@DE_6345″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;CurrencyCodeISO-Alpha3&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1616-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1616-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRuleSet” RefId=”1630-MappingRuleSet”><Properties><Ref-Property Name=”Parent” Ref=”1-MappingRuleSet” /><Data-Property Name=”ValidateCreatedObjects” Val=”false” /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”RuleSetBehaviour” Val=”0″ /><Data-Property Name=”MaxLoops” Val=”10000″ /><Data-Property Name=”Name” Val=”rs_DG_C088″ /><Data-Property Name=”Selection” Val=”.” /><Data-Property Name=”Target” Val=”DG_C088″ /><Ref-Property Name=”Rules” Ref=”1631-RuleCollection” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.RuleCollection” RefId=”1631-RuleCollection”><Properties><Ref-Property Name=”Item-0″ Ref=”1632-MappingRule” /><Ref-Property Name=”Item-1″ Ref=”1635-MappingRule” /><Ref-Property Name=”Item-2″ Ref=”1638-MappingRule” /><Ref-Property Name=”Item-3″ Ref=”1641-MappingRule” /><Ref-Property Name=”Item-4″ Ref=”1644-MappingRule” /><Ref-Property Name=”Item-5″ Ref=”1647-MappingRule” /><Ref-Property Name=”Item-6″ Ref=”1650-MappingRule” /><Ref-Property Name=”Item-7″ Ref=”1653-MappingRule” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1632-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3433″ /><Data-Property Name=”Target” Val=”@DE_3433″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;InstitutionNameIdentification&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1635-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_1131″ /><Data-Property Name=”Target” Val=”@DE_1131″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;25&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”Description” Val=”25 = Bank identification” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1638-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3055″ /><Data-Property Name=”Target” Val=”@DE_3055″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;5&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”Description” Val=”5 = ISO (International Organization for Standardization)” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1641-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3434″ /><Data-Property Name=”Target” Val=”@DE_3434″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;InstitutionBranchNumber&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1644-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_1131_2″ /><Data-Property Name=”Target” Val=”@DE_1131_2″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;25&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”Description” Val=”25 = Bank identification” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1647-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3055_2″ /><Data-Property Name=”Target” Val=”@DE_3055_2″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;5&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Data-Property Name=”Description” Val=”5 = ISO (International Organization for Standardization)” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1650-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3432″ /><Data-Property Name=”Target” Val=”@DE_3432″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;InstitutionName&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1653-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3436″ /><Data-Property Name=”Target” Val=”@DE_3436″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;InstitutionBranchPlace&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1630-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1630-MappingRuleSet” /></Properties></Class><Class Type=”eBiss.ClassLib.Maps.MappingRule” RefId=”1656-MappingRule”><Properties><Data-Property Name=”Name” Val=”r_DE_3207″ /><Data-Property Name=”Target” Val=”@DE_3207″ /><Data-Property Name=”IsDisabled” Val=”false” /><Data-Property Name=”Selection” Val=”&quot;CountryCodeISO-Alpha3&quot;” /><Data-Property Name=”SelectionMode” Val=”1″ /><Data-Property Name=”ValueRequired” Val=”false” /><Ref-Property Name=”Parent” Ref=”1-MappingRuleSet” /><Ref-Property Name=”RuleSet” Ref=”1-MappingRuleSet” /></Properties></Class></Classes></XmlSerializerRoot>

The customer transmits umlauts in the article description. Is it possible to insert a rule here so that the umlaut is converted to UE?

There is currently no specific mapping function in eBiss which converts umlauts. But you can use the Replace() function.

Is it possible to include a rule in the mapping – is the field not filled, then set a “1”?

Yes, with an alternative selector.

Sorry, this entry is only available in Deutsch. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.

Es folgt eine kurze Step-By-Step Erklärung wie man den Kommunikationskanal einstellt um den TSL/SSL Zugang zu eGate zu nutzen.

  1. Öffnen Sie im eBiss im Menü links unter der Gruppe Kommunikation die Kommunikationskanäle
  2. eGate Empfangs Kanal
    1. Öffnen Sie Ihren eGate Empfangskanal – Pop3 receive Channel
      In den Einstellungen ändern Sie bitte den Port auf “995” und die Authentifizierung auf “Basic”
      Bitte achten Sie darauf, dass Ihre Login-Daten für eGate richtig eingetragen sind.
    2. Öffnen Sie nun die erweiterten Einstellungen und stellen Sie das SSL Handling auf “Implizit”
  3. Wiederholen Sie diese Konfiguration auch im eGate Senden Kanal – SMTP send channel, bis auf den Port, dieser muss 25 sein.
    Achten Sie auch hier auf die korrekten Zugangsdaten für eGate
    Erweiterte Einstellungen -> SSL handling “implizit”

 

The error codes, that appear while sending PLD data with eBiss UPS modul are listet here:

PLD 0200 Error Codes

https://www.pld-certify.ups.com/CerttoolHelp/PLD0200/WebHelp_pld0200/pld0200_errorcodes.htm

As a rule, the containerizer generates the UNB segment. However, if the UNB segment is to be influenced in an Edifact document, the UNB segment must be triggered in the corresponding mapping with a rule record and the desired data element must be operated with a mapping rule. The remaining UNB data elements are then created/operated by the containerizer.

Attention

The default setting of the syntax version number is 3. The EDIFACT containerizer in eBiss checks the syntax version number. If it is greater 3, the date format in the UNB segment will be adapted. In addition, a * is set in UNA segment instead of a space. Finally, you must ensure that the outgoing Edifact document corresponds to the syntax version according to ISO 9735:1998

In the requested case, you need a mapping rule like in this snapshot:

UNB Segment im Mapping

UNB Segment in mapping

Upgrading from eBiss 2 to eBiss 3 is expensive if one or more of the following situations apply:

  1. The amount of data in the. /MessageStore exceeds  several Gb.
  2. There are plugins that have been developed by themselves and use special functions in eBiss.
  3. NHIBERNATE is used for database integration.
  4. The authorization concept for eBiss Service and/or database users should be changed.
  5. eBiss 3 is to be set up on a new environment.
  6. Another database server is to be used.

Generally, we recommend to set up eBiss 3 as a new instance, based on the settings of the existing eBiss 2 system. This means that any problems can be detected and dealt with without endangering the running operation.  Once all possible scenarios within the new instance have been tested and found to be good, this new instance can be put into operation and the old eBiss 2 system can be deactivated at the same time. That is to say, you make a cut and keep the historical news in the old system and start with a “virgin” new system.

The DBCopy tool delivered with eBiss 3 is ideally used for this purpose, because it allows the extraction of all relevant system settings without having to read the data-heavy messages or article master tables.