instruction
stringlengths
0
2.86k
input
stringlengths
0
2.21k
output
stringlengths
4
253
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00 HouseserviceStatisticsEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00. HouseserviceAcceptanceEvent
actionTime: DateTime
The timestamp the event was captured. ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00). QslepEvent
actionTime: DateTime
The timestamp when the event was captured NotificationCall
actionTime: date-time
The timestamp when the event was captured CollectionEvent
actionTime: date-time
The timestamp when the event was captured BackofficeEvent
actionTime: date-time
The timestamp when the event was captured CollectionEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] PickPostArrivalEvent
actionTime: DateTime
The timestamp the event was captured. ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00). QslepEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00 HouseserviceTrackingEvent
actionTime: DateTime
The timestamp when the event was captured CollectionEvent
actionTime: DateTime
The timestamp when the event was captured LetterIdRegistrationEvent
actionTime: date-time
The timestamp when the event was captured NotificationCall
actionTime: date-time
The timestamp when the event was captured CollectionEvent
actionTime: date-time
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) DeliveryEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) HandoverToPartnerEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) HandoverZlpEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) Call
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) NotificationEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] ZlpEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] PickpostDeliveryEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] PickPostArrivalEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] BackofficeAcceptanceEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] PickpostAcceptanceEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00. HouseServiceMailpieceTrackingEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00 HouseserviceStatisticsEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00. HouseserviceAcceptanceEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00. AzbWorkTimeEvent
actionTime: DateTime
The timestamp the event was captured. ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00). NsaEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00. IlodgeEvent
actionTime: DateTime
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00 HouseserviceTrackingEvent
actionTime: DateTime
The timestamp when the event was captured LetterIdRegistrationEvent
actionTime: date-time
The timestamp when the event was captured LetterIdRegistrationEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) DeliveryEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) HandoverToPartnerEvent
actionTime: DateTime
The timestamp of the corresponding delivery event, ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset]. IdentitycardMetadata
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] ZlpEvent
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] PickpostDeliveryEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) HandoverZlpEvent
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) Call
actionTime: DateTime
ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00) NotificationEvent
actionTime: DateTime
The timestamp when the event was captured NotificationCall
actionTime: date-time
The timestamp when the event was captured CollectionEvent
actionTime: date-time
AcceptanceEvent
actionTime: DateTime
The timestamp when the event was captured BackofficeEvent
actionTime: date-time
The timestamp the event was captured. As defined by RFC 3339, section 5.6, for example: 2014-05-22T10:42:42.542+00:00. IlodgeEvent
actionTime: DateTime
The timestamp when the customer-order key was captured LabelDetail
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] CollectionDispoboxEvent
actionTime: DateTime
The timestamp the event was captured. ISO-8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] local time (Switzerland, example: 2014-05-22T10:25:29.538+02:00). NsaEvent
actionTime: DateTime
The timestamp when the customer-order key was captured LabelDetail
actionTime: DateTime
The timestamp when the event was captured ISO 8601 [YYYY-MM-DDTHH:MM:SS.MMM+Timezone-Offset] CollectionDispoboxEvent
actionTime: DateTime
Action type: 1 -> Pickup 2 -> Delivery TransportAction
actionType: Int
Type of action required to meet the precondition Example: WEBVIEW TopicPrecondition
actionType: string
The NsaOrderActionType NsaEvent
ORDER
actionType: enum
Action type (To be defined) TransportAction
DELIVERYPICKUPOTHER
actionType: enum
Capture a container activated event. ContainerEvent
activated: ContainerActivatedEvent
Event field set when a container was enabled (after having been disabled). Exactly one of the optional event type must be present. ContainerActivationEvent
activated: ActivationEvent
The person receiving the mail. ZDL : Zustelladresse Verein DET_TYP_D = AS_PDI delivery-address-services
activationcustomer
ActivatedRecipients: object
A range of validity typically known as _IBS/ABS_ glossary
activation: entity
sender-standing-order
activeFrominactiveFrom
Activation: object
service-area-overrule
activeFrominactiveFrom
Activation: object
customer-relation-telecommunication
activeFrom
Activation: object
transport-order
activeFrominactiveFrom
Activation: object
An event code may have multiple configurations - but not at the same time. Within a specific time range, only 1 configuration is valid (no overlapping). mailpiece-aggregate
activeFrominactiveFrom
Activation: object
Activation Object: Information ob und wann Produkt gueltig istAchtung!inactiveFrom entspricht dem "ABS"-Datum plus 1 Tag.Damit ist SYSDATE between "activeFrom" and "inactiveFrom" falsch!Es gilt: "activeFrom" <= SYSDATE < "inactiveFrom" pricing-article
activeFromcurrentinactiveFrom
Activation: object
Activation Object: information if a product is valid logistics-pricing-product
activeFromcurrentinactiveFrom
Activation: object
Activation Object: information if valid billing-customer
activeFrominactiveFrom
Activation: object
location-structure
activeFromcurrentinactiveFrom
Activation: object
Activation Object: Information ob und wann Produkt gueltig ist pricing-product
activeFromblockedcurrentinactiveFrom
Activation: object
clearance-check-activation
activeFrominactiveFrom
Activation: object
Gültigkeit: billing-correspondence-debtor
activeFromdeleteinactiveFrom
Activation: object
recipient-settings-backoffice
activeFromactiveTo
Activation: object
collection-letterbox
activeFrominactiveFrominactiveTo
Activation: object
recipient-settings
activeFrominactiveFrom
Activation: object
delivery-customer-service
activeFrominactiveFrom
Activation: object
billing-partner-incamail
activeFrominactiveFrom
Activation: object
Validity period. The validity's end is optional. delivery-address-services
activeFrominactiveFrom
Activation: object
Activation Object. Contains ABS-Date and blocked attribute. billing-debtor
blockedinactiveFrom
Activation: object
Gültigkeit: billing-costcenter
activeFromdeleteinactiveFrom
Activation: object
address-services-sector
activeFrominactiveFrom
Activation: object
logistics-sales-contract-basic
activeFrominactiveFrom
Activation: object
parcel-delivery-plan-scenario
activeDateisActive
Activation: object
customer-recipient-services-order
activeFromcurrentinactiveFrom
Activation: object
address-services-customer
activeFrominactiveFrom
Activation: object
delivery-plan
activeFrominactiveFrom
Activation: object
recipient-settings
activeFromactiveTo
Activation: object
address-pickup
activeFrominactiveFrom
Activation: object
cost-center
activeFrominactiveFrom
Activation: object
public-transport-functional-location
activeFrom
Activation: object
service.area.plan
activeFrominactiveFrom
Activation: object
logistics-delivery
activeFromcurrentinactiveFrom
Activation: object
delivery-district
activeFrominactiveFrom
Activation: object
vehicle-profile
activeFromactiveTo
Activation: object
billing-agreement
activeFrominactiveFrom
Activation: object
retail-partner-product
activeFrominactiveFrom
Activation: object
location-structure-postcode
activeFrominactiveFrom
Activation: object
Validity of the receiver return shipment Return
activation: Activation
Validity of the product code. ProductCode
activation: Activation
Defines Defines the activation period of the district overrule. Validation rule: The activation range from the district overrule has to be a subset from the district to be overruled. DistrictOverrule
activation: Activation
ContractState
activation: Activation