The error codes, that appear while sending PLD data with eBiss UPS modul are listet here:
https://www.pld-certify.ups.com/CerttoolHelp/PLD0200/WebHelp_pld0200/pld0200_errorcodes.htm
The error codes, that appear while sending PLD data with eBiss UPS modul are listet here:
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.
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:
The upgrade from eBiss 2 to eBiss 3 is to be classified as costly if one or more of the following circumstances is given:
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.
In case , you are working at a client machine and cannot see any trace log within the tracelog-window, but you can see the trace log while working on the eBiss Server, this problem will be solved by configuring the used firewall port.
Please adjust the Client-Server Port and the Remote Callback-port from server towards Client in the eBiss 3 configurator‘s connection settings. If the Remote Callback-port is set to Null, the port will be negotiated automatically by the system.
eBiss-Server
Following port configuration in eBiss.Service.exe.config to be put:
<add key="eBiss.RemotingPort" value="9998" />
eBiss-WinClient
in eBiss.WinClient.exe.config :
<add key="eBiss.ServerURL" value="tcp:%%//%%localhost:9998/eBiss.ApiServer" />
For example, if you set a selection in a rule that selects a typed value (incl. whole trees), you can save it as $$VariableName on the right-hand side. Later on, you can access this structure directly in the entire document and carry out further work with it.
For example, save the entire folder document:
Rule: /Orders => $$doc
Call it later in a mapping:
Rule: $doc/@SupplerGLN
or better and faster with the XVar function:
Rule: XVar (‘ doc’)/@SupplierGLN
or the total of the item quantities stored in the document:
Rule: sum (XVar (‘ doc’)/Items/@Quantity)
For more information, see the variables help.
The more intensively the eBiss converter is used over time, the easier it is to loose track of how and where alterations and adaptions have made the eBiss System to your particular eBiss.
At Pranke, too, we are often asked to make adjustments or extensions to an existing eBiss system. If that system has reached a certain complexity and is not really well maintained, it’s quite a challenge to even find out where to start. A manual analysis of a system is very time-consuming and by no means a matter of course.
In order to better cope with such situations, we developed a new module for eBiss 3 which we called eBiss Analytics. With this module it is possible to make both statistical and analytical statements about an existing eBiss 3 system. This is why it comes with these two characteristics.
Statistical considerations refer to the volume of messages received and sent. These can be automatically sent to selected recipients. During the System analysis, the system-specific parameters are evaluated and prepared in an appropriate form (e. g. as sequence diagram and/or structured list) in a separate namespace within the DokuWiki provided with eBiss.
DeliveryNote referes to the printed document, while Despatch Advise actually means the DESADV, which (in theory) can have a different number.
In EDIFACT these are also different RFF qualifiers, namely AAK for DESADV and DQ for DeliveryNote.
Since eBiss 3 version 3.0.134, you can connect to the United Parcel Service (UPS) portal.
The license-managed eBiss module provides you with a UPS send channel with which you can set up the connection to the UPS Portal. The UPS-Url and authentication credentials are required for setup. Furthermore, you can define the validation of the sender/receiver in the module and unpack compressed files directly.
Want more information about our UPS module? We are happy to advise you.
It is common practice in the industry to sell lots. Normally, the pre-order phase is interactive between buyer and seller. With EDI, the lots in the ORDRSP are then resolved directly and treated individually. Some manufacturers also have EANs for these shopping lots, but these do not usually appear in the messages.
There are possibilities to process this lot topic in some enterprise resource planning systems. However, this usually only takes place in close cooperation with, for example, Intersport dealers with the dedicated Intersport merchandise management solution.
See also: 7143 Item ty43 Item type identification code (Code: SG)
eBiss 3 is faster, more intuitive, more stable and more versatile. Change the train! Numerous small and large improvements make the work easier for users and administrators. An overview of the improvements and new features can be found on eBiss 3: What’s new?
Customers receive the eBiss 3 license as part of their maintenance contract at no additional cost.
If you want our support for the upgrade, you can choose between three different upgrade options or eBiss 3 migration packages:
Fon.: +49 (0)721 20380-123
E-Mail:sales(at)pranke.com
For software developers (WWS, ERP systems) with update experience
Fixed price: 300 €
Ideal for systems with max. 2 knots
Fixed price: 1.950 €
For complex multi-node systems
Fixed price: 2.800 €
plus travel expenses (280 €/day)
To provide you with an optimal experience, we use technologies such as cookies to store and/or access device information. If you consent to these technologies, we may process data such as browsing behavior or unique IDs on this website. If you do not give or withdraw your consent, certain features and functions may be affected.