All Classes and Interfaces
Class
Description
Parameters of UI API invocation when this is to be done
via create process:
The client has to invoke the process as specified by the
properties of this object.
Parameters of UI API invocation when this is to be done
via shellexecute:
The client has to create a file with the given name in a temporary directory,
the contents of the file is given in the variable 'contents'.
An amount of money with a value and an currency ISO code.
A data transfer object which describes an UI API.
A data transfer object to be the parameter of the method IFoundationBF.getNewApplicationFacade()
A complete address of a company.
Masterfile data for company extension data
Masterfile Transfer data object for a company.
DTO to hold processing status information for one CompanyMFDTO.
Masterfile data for company role
Contains data for contacting a person.
CuboidDimensionsDTO with length, width, height and quantityUnit.
Master file data for a currency rate.
Messages for this particular item, e.g. for errors or warnings.
The following messageIdentCodes are used:
"INVALID_DATA_ERROR": One of the ident codes send was not recognized by the engine, e.g. an currency code.
"EMPTY_MANDATORY_FIELD" One of the mandatory Fields is empty "LOCK_WARNING" the service or an updated text can not be locked
The following messageIdentCodes are used:
"INVALID_DATA_ERROR": One of the ident codes send was not recognized by the engine, e.g. an currency code.
"EMPTY_MANDATORY_FIELD" One of the mandatory Fields is empty "LOCK_WARNING" the service or an updated text can not be locked
Client specific request for document categories.
Response for a document categories request.
Data transfer object for a document.
A dto to request one or several LISExpMODocument20DTO.
Data Transfer Object for a get document result.
UI API for the XNSGFoundation
Interface that indicates that the DTO is for an MO that is Generically identifiable
Application facade for LIS
Business facade for LIS, version 2.0
Business facade for common logistics functions.
DTO to implement additional fields not found in the standard DTOs
The fields can have any name or value, but the target system must know how to
handle these fields.
An amount of mone with a value and a currency
DTO for document data that has been stored in an archive system e.g.
DTO for TTCSAreaDependSchedule.
DTO for consignment AreaDependScheduleFilters
DTO for area depend schedule.
DTO for handling unit AreaDependScheduleFilters
DTO for handling AreaDependScheduleFilters
DTO for storage AreaDependScheduleFilters
DTO for order AreaDependScheduleFilters
DTO for order item AreaDependScheduleFilters
DTO for transport AreaDependScheduleFilters
DTO for main data of TTCSAreaDependSchedule.
DTO for binaries e.g. document, images.
A single binary role.
DTO for document data that has been stored in a CES partner server and shall be accessed via VCP.
DTO for consigment messages
Version 2.0
Header data of the consignment.
This DTO describes a consignment item as send e.g. with the EANCOM message DESADV.
Reference fields for identifying a LISConsignment.
Reference fields for identifying a LISConsignment.
DTO with parameters to request a list of consignments
Request DTO for consignment synchronization.
Data Transfer Object for a consignment synchronize result.
DTO for a consignment with all transports.
This DTO describes a consignment item in the handling unit as send e.g. with the EANCOM message DESADV.
Contains a date and a timezone.
DTO for day type schedules.
DTO for the despatch type.
DTO for Dimensions length, width, height and a quantity unit.
DTO for Duration
DTO for equipment types
DTO for an event code list
This DTO describes a eventCodeList entry.
Header data of the event code list.
Event Definition data
Contains alle fields that are necessary to return a collection of
LISEventDefinition20DTOsDTO to export consignment data to partner systems like the Message Engine Logistics.
The consignment header data to be sent to a partner system.
The consignment item data to be sent to a partner system
A list of consignments e.g. as result of a search.
An entry in a consignment list e.g. retrieved by a search request.
DTO to provide the meta data of documents that are connected to the higher level structure.
The handling unit data to be sent to a partner system
DTO to export handling unit transport data to partner systems like the Message Engine Logistics.
DTO to export document data to partner systems like the Message Engine
Logistics.
A single document category.
A unique identifier for a document category.
Texts for a
LISMODocumentCategoryDTODTO for order messages
Version 2.0
The head of a order.
An item of a purchase order.
Contains the result of a quick search.
DTO to export status data
DTO to export trackingevent data to partner systems like the Message Engine Logistics.
A list of exported
LISExpTrackingEventListEntry20DTOsThe event header for the export to a partner system.
DTO to deliver tracking information for a tracking object
DTO to export the events of a tracking object to partner systems like the Message Engine Logistics.
DTO to export transport data to partner systems like the Message Engine Logistics.
DTO for document data which has already been stored in the file system
The reference to file system storage settings in the VCP
This DTO describes a handling unit as send e.g. with the EANCOM message DESADV.
Extension class for
LISHandlingUnit20DTO that adds additional fields
so that the resulting LISHandlingUnitExt20DTO can be used stand alone and
independent from a LISConsignment20DTO (or similar).RequestDTO for handling of handling units, used in
ILISBF20.DTO that bundles a handling unit together to documents.
DTO containing the event code of a milestone and new target date for this milestone.
DTO for locations
The data from the IFTMIN segment SG8/SG9/LOC (21) is not used
because it holds only the GLN but no address data.
DTO which references a material
DTO for the master file materials.
DTO for the material master file items.
DTO for means of transports.
Meta data of a message
A single binary document category.
A document message for multiple tracking objects.
DTO containing the data for an order fulfillment step of type transport
DTO for order messages
Version 2.0
DTO representing an order fulfillment plan
DTO for order fulfillment plan requests.
Result DTO for an order fulfillment request
Abstract DTO as a superclass for classes representing steps in an order fulfillment plan
The head of a order.
An item of an order.
DTO for package structure.
Data transfer object to denote parties, e.g. buyer, seller,
with full address data.
Data transfer object for parties that contain contact information
Data transfer object to denote parties, e.g. buyer or seller,
without address data.
DTO for Peridodic start schedules
Phyiscal transport message.
DTO for physical transport.
DTO denoting a quantity
The request parameters for a quick search.
DTO suppliying the identification information for making requests.
DTO denoting a serivce type of forwarders
Describes terms of delivery.
DTO for text translations.
DTO for a single text translation.
Contains a time.
DTO for Tracking events (envelope)
The request DTO for a tracking event export
DTO containing the event code of a milestone and new target date for this milestone.
DTO for main tracking event data
DTO to receive a list of tracking events
DTO for reference numbers.
DTO for a single reference field with fieldName and the number
Class to hold values for updates of the tracking objects generically
with fieldname
A document message for a tracking object.
DTO with parameters to request the tracking events for a specific tracking object
DTO for TOFConsignment
DTO for CTOFHandlingUnit.
DTO for TOFLCHandling
DTO for TOFLCStorage
DTO for CTOFOrder
DTO for CTOFOrderItem
DTO for CTOFTransportLeg
DTO for reference numbers.
DTO for a single reference field with fieldName and the number
A transport message sent by the supplier or buyer.
DTO for transport legs, Version 2.0
Renamed fields compared to 1.0:
refNumberForwarder => masterWayBillNumber
suppliersRefNumberForwarder => shipperReference
estimatedArrivalDate => expectedArrivalDate
estimatedShippingDate => expectedDepartureDate
actualShippingDate => actualDepartureDate
expectedArrivalDate => plannedArrivalDate
expectedShippingDate => plannedDepartureDate
DTO for transport types
A transport unit message send by a partner
DTO for transport units
DTO with parameters to request details for a specific consignment
DTO denoting a particular warehouse
A quantity with a value and a quantity unit.
A quantity with a value, a quantity unit and a quantity unit type.
Request for setting a block of company master file data.
Response for setting company master file data.
If the response has any errors, at least one company was not created or updated.
If the response has any errors, at least one company was not created or updated.
Request for setting a block of currency rate master file data.
Response for setting currency rate master file data.
Diagnosis log data of a plan, identified by hostcode
A plan for a target time calculation.
Result of a target time calculation
A single step of a target time calculation, identifiable by sequence number or host code
A step of a target time calculation plan
Handling data of a target time calculation step
Transport data of a target time calculation step
Request for target time calculation of multiple plans.
Response of a target time calculation
Subset of UNECE quantity units according to "Recommendation No. 20 - Units of Measure used in International Trade".
Messages for this particular item, e.g. for errors or warnings.
The following messageIdentCodes are used:
"INVALID_DATA_ERROR": One of the ident codes send was not recognized by the engine, e.g. an currency code.
"EMPTY_MANDATORY_FIELD" One of the mandatory Fields is empty "LOCK_WARNING" the service or an updated text can not be locked
The following messageIdentCodes are used:
"INVALID_DATA_ERROR": One of the ident codes send was not recognized by the engine, e.g. an currency code.
"EMPTY_MANDATORY_FIELD" One of the mandatory Fields is empty "LOCK_WARNING" the service or an updated text can not be locked