Shipping

ASNTypes

This code list includes the Advanced Ship Notice (ASN) definitions.

CarrierDefaults

In this code list, a default carrier interface is defined on a certain hierarchy/accounting entity level.

The code list is required for the Carrier Interface Processing in Shipping.

CarrierExchangeFolders

In this code list, the Data Exchange Folder for the carrier interface types is defined. The default exchange folder is ${TEMP}.

The code list is required for the Carrier Interface Processing in Shipping.

CarrierInterfaceTypes

To support special options of some carrier interface types, a carrier variant is used. The Shipping area receives this information in the TransportationServiceCode element of the CarrierRoute BOD. In this code list, the Default Service Variant is defined for the carrier interface types.

The code list is required for the Carrier Interface Processing in Shipping.

CarrierMappingIdentifiers

In this code list, the Carrier Interface Type is defined. The task type Carrier Interface Processing uses the code list CarrierMappingIdentifiers to determine the carrier interface type. Supported carrier interface types are Yodel, DPD, GLS, TNT, and UPS.

The code list is required for the Carrier Interface Processing in the Shipping area.

CarrierVariantsDPD

Defines the variants for the DPD Carrier Interface. The service variant codes for the DPD Carrier Interface are implemented as entries of the code list.

The code list is required for the Carrier Interface Processing in the Shipping area.

CarrierVariantsGLS

Defines the variants for the GLS Carrier Interface. The service variant codes for the GLS Carrier Interface are implemented as entries of the code list.

The code list is required for the Carrier Interface Processing in the Shipping area.

CarrierVariantsTNT

Defines the variants for the TNT Carrier Interface. The service variant codes for the TNT Carrier Interface are implemented as entries of the code list.

The code list is required for the Carrier Interface Processing in the Shipping area.

CarrierVariantsUPS

Defines the variants for the UPS Carrier Interface. The service variant codes for the UPS Carrier Interface are implemented as entries of the code list.

The code list is required for the Carrier Interface Processing in the Shipping area.

CarrierVariantsYodel

Defines the variants for the Yodel Carrier Interface. The service variant codes for the Yodel Carrier Interface are implemented as entries of the code list.

The code list is required for the Carrier Interface Processing in the Shipping area.

CommodityCodes

A list of commodity codes that are delivered by the customs authority is included in this code list. The code list contains, for example, CN codes (Combined Nomenclature of the European Union) or HTS codes (Official Harmonized Tariff Schedule from the US government).

ComplianceArchiveLog

Number of days after which old compliance log entries are set to the status Archived. By default, the number of days are 30.

ComplianceBasisIsActive

ComplianceListUpdate

Defines the parameters that are required and used by the update process of sanctions lists, the SanctionsListsUpdater:

• Maximum Retries: Maximum number of retries to update the sanctions lists before the status is set to Error. The default value is 10 retries.
• Delay before Retry (in Seconds): Time in seconds after which the task to update the sanctions lists is processed again, if it has the status Waiting. The default value is 60 seconds.
• Connection Timeout (in Seconds): Time-out, in seconds, to establish the connection to an online source server that is used to download sanctions lists. The default value is 10 seconds.
• Read Timeout (in Seconds): Time-out, in seconds, for reading from an online source server that is used to download sanctions lists. The default value is 10 seconds.
• Initialize Empty Lists: Activates the first automatic sanctions lists update to initially update the sanctions lists. By default, the initialization of empty sanctions lists is activated. The empty initialization files of the sanctions lists are included in the installation or update files, that is, in the respective .war files. For the sanctions lists update, the source files are downloaded to the folder /exm/sanctionslists/downloaded/.

ComplianceScoringDetails

Defines the scoring parameters that are used for compliance checks. Several points are specified to weight the parts of an address that match, or do not match, parts of a sanctions list address. Points are specified for each parameter.

For matching parts of an address: The points count is positive when a part of an address is contained in the sanctions list address.

For missing parts of an address: The points count is negative when a part of an address is not contained in the sanctions list address.

You can use these parameters to influence how much weight is given to each part of an address:

• Name Part Matching: The default weight is 6 points.
• Street Part Matching: The default weight is 4 points.
• City Part Matching: The default weight is 3 points.
• Postal Code Part Matching: The default weight is 3 points.
• Country Subdivision Part Matching: The default weight is 2 points.
• Country Part Matching: The default weight is 2 points.
• Country Code Part Matching: The default weight is 8 points.
• Address Other Part Matching: The default weight is 2 points.
• Name Part Missing: The default weight is -4 points.
• Street Part Missing: The default weight is -2 points.
• City Part Missing: The default weight is -2 points.
• Postal Code Part Missing: The default weight is -2 points.
• Country Subdivision Part Missing: The default weight is 0 points.
• Country Part Missing: The default weight is -2 points.
• Country Code Part Missing: The default weight is -4 points.
• Address Other Part Missing: The default weight is -1 points.

ComplianceScoringResult

Defines the parameters that control the handling of the compliance check results:

• Threshold Yellow Match: Defines the threshold in percent after which the scoring result is interpreted as yellow match. The default value is 40 percent.
• Threshold Red Match: Defines the threshold in percent after which the scoring result is interpreted as red match. The default value is 75 percent.
• Maximum Number of Matching Entries: Maximum number of matching entries to be provided as part of a scoring result. If set to 0, all matches are provided as result of the scoring. The default value is 5.
• Block on Red Match: Block shipper in case of red matches. If the parameter is activated, the shipper must be blocked. The task Compliance Check sets the shipper's processing status to Block. The task Non-Compliance Blocker blocks each subsequent task and sets the shipper's processing status to Blocked. Both tasks must be defined in the workflow. If the parameter is deactivated, the shippers are processed in the usual way. The task Non-Compliance Blocker does not change the processing status of the shipper and all subsequent tasks such as sending the ASN are performed. By default, blocking shippers in case of red matches is activated.
• Block on Yellow Match: Block shipper in case of yellow matches. If the parameter is activated, the shipper must be blocked. The task Compliance Check sets the shipper's processing status to Block. The task Non-Compliance Blocker blocks each subsequent task and sets the shipper's processing status to Blocked. Both tasks must be defined in the workflow. If the parameter is deactivated, the shippers are processed in the usual way. The task Non-Compliance Blocker does not change the processing status of the shipper and all subsequent tasks such as sending the ASN are performed. By default, blocking shippers in case of yellow matches is deactivated.

ContainerAggregationMode

This code list includes the modes in which containers are aggregated for the label printing.

CustomerContainerTypePatterns

The entry No. of Layers to Add of this code list is used by the BMW Container Management. In this business process, the entry helps to calculate the number of layers in the container structure. The resulting value is attached as a two-digit number to the customer container ID. The calculation is only performed, if the option No. of Layers to Add is selected from the drop-down list Pattern for Formatting Customer Container Type in the Customers or TradingPartners code list.

DataIdentifiers

This code list includes the data identifiers that are used to define data identifier sets for trading partners. A data identifier is the code for a specific piece of information to be printed on labels of trading partners such as shipment date or packing slip number. The data identifier sets control the entire information that is printed on labels for specific trading partners.

DataIdentifiersSets

This code list includes the data identifier sets for trading partners. The data identifier sets control the entire information that is printed on labels for specific trading partners.

DestinationLabelTypes

This code list defines the destination label types.

DocumentPrintingModes

This code list defines the document print modes. The code list is used as referenced code list for the WaybillTypes code list.

• None: No printout
• PrintPerShipper: Print per shipper
• PrintPerShipment: Print per included shipment

EDIPlantMappingFord

The EDI plant information is mapped from a 2-character code that is used in VDA messages to a 5-character value. The 5-character value of the Ford plant and the information whether a mapping exists are evaluated from the code lists EDIPlantMappingFord and MappingsEDIPlant. The mapping is used to create a print request and to select the correct InterFormNG print template. The mapping has been implemented for labels of the trading partner A0060 Ford Europe.

The mapping of the EDI plant information in the code list EDIPlantMappingFord includes these code entries:

• Name: Short code of the EDI plant that is sent in the VDA message.
• Mapped EDI Plant: The corresponding code that is specified in the A0060 Ford Europe plant list.
• Short Description: The name of the plant that is specified in the A0060 Ford Europe plant list.

Example: Name = "50", Mapped EDI Plant = "0095A", Short Description = "Ford FCSD Cologne".

See the description of the code list MappingsEDIPlant.

EDIWaybillTypes

This code list includes the EDI waybill types.

FlexFieldAllowList

This code list with a trading partner hierarchy defines which user area fields sent by Infor LN are to be captured. These user area fields allow for the publication and printing of the related data for subsequent shipping tasks and documents, such as labels, packing slips, EDI waybills, waybills, and ASN.

JobCarrierRouteProcessor

This code list defines the configuration of the CarrierRouteProcessor job that processes CarrierRoute BODs in the Shipping area.

• Name: Defines the name of the CarrierRouteProcessor job configuration. The CarrierRouteProcessor job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job CarrierRouteProcessor. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the job runs every 10 seconds: 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the CarrierRouteProcessor job. By default, the user is EXMSystemUser.
• Number of Records to Fetch: Defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

JobComplianceLogArchiver

This code list defines the configuration of the job ComplianceLogArchiver. The job archives the compliance log entries in the Shipping area. The job configuration controls the time at which old compliance log entries are set to the Archived status.

• Name: Defines the name of the ComplianceLogArchiver job configuration. The ComplianceLogArchiver job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job ComplianceLogArchiver. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. The default Cron expression is 0 0 23 1/1 * ? *.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job UserShippingComplianceLogArchiver job. By default, the user is EXMSystemUser.
• Number of Records to Fetch: Defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

JobConsignmentProcessor

This code list defines the configuration of the ConsignmentProcessor job that processes shippers in the Shipping area.

• Name: Defines the name of the ConsignmentProcessor job configuration. The ConsignmentProcessor job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job ConsignmentProcessor. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the job runs every 10 seconds: 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the ConsignmentProcessor job. By default, the user is EXMSystemUser.
• Number of Records to Fetch: Defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

JobEXMReorganization

This code list defines the configuration of the EXMReorganization job. The job deletes transactional data in the Shipping area.

• Name: Defines the name of the EXMReorganization job configuration. The EXMReorganization job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job EXMReorganization. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the reorganization is deactivated: 0 0 0 31 12 ? 2099.
• Job User: Defines the user of the Shipping area that is used to run the EXMReorganization job. By default, the user is EXMSystemUser.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Delete Shipment Older than Days: Number of days for which shipments should be kept, starting yesterday (-1 = no deletion).
• Delete Invoices Older than Days: Number of days for which invoices should be kept, starting yesterday (-1 = no deletion).
• Delete Warehouse Containers Older than Days: Number of days for which warehouse containers should be kept, starting yesterday (-1 = no deletion).
• Delete Task Instances Older than Days: Number of days for which tasks should be kept, starting yesterday (-1 = no deletion).
• Delete in One Transaction (Standard): Number of objects deleted in one transaction (default = 1000).

JobExpiredLockRemover

This code list defines the configuration of the ExpiredLockRemover job that removes expired locks in the Shipping area. The job handles object locks in cases a process is interrupted after obtaining a lock.

• Name: Defines the name of the ExpiredLockRemover job configuration. The ExpiredLockRemover job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job ExpiredLockRemover. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. The default Cron expression is 0 0/1 * * * ? *.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the ExpiredLockRemover job. By default, the user is EXMSystemUser.
• Lock Expiry Time (in Seconds): Defines the expiry time for locks in seconds. By default, the expiry time is 1200 seconds.
• Number of Records to Fetch: Defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

JobInvoiceProcessor

This code list defines the configuration of the job InvoiceProcessor that processes invoices in the Shipping area.

• Name: Defines the name of the InvoiceProcessor job configuration. The InvoiceProcessor job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job InvoiceProcessor. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the job runs every 10 seconds: 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the InvoiceProcessor job. By default, the user is EXMSystemUser.
• Number of Records to Fetch: Defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

JobSanctionsListsUpdater

This code list defines when and how often the Job Manager starts the update process of sanctions lists SanctionsListsUpdater in the Shipping area:

• Name: Defines the name of the SanctionsListsUpdater job configuration. The SanctionsListsUpdater job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job SanctionsListsUpdater. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. The default Cron expression is 0 0 23 1/1 * ? *.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the SanctionsListsUpdater job. By default, the user is EXMSystemUser.

JobShipmentProcessor

This code list defines the configuration of the job ShipmentProcessor that processes shipments in the Shipping area:

• Name: Defines the name of the ShipmentProcessor job configuration. The ShipmentProcessor job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job ShipmentProcessor. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the job runs every 10 seconds: 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the ShipmentProcessor job. By default, the user is EXMSystemUser.
• Number of Records to Fetch: Defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

JobTaskInstanceProducer

This code list defines the configuration of the TaskInstanceProducer job that processes the job task instances in the Shipping area.

• Name: Defines the name of the TaskInstanceProducer job configuration. The TaskInstanceProducer job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job TaskInstanceProducer. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the job runs every 10 seconds: 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the TaskInstanceProducer job. By default, the user is EXMSystemUser.

JobWarehouseContainerProcessor

This code list defines the configuration of the WarehouseContainerProcessor job that processes warehouse containers in the Shipping area and prints the warehouse container labels.

• Name: Defines the name of the WarehouseContainerProcessor job configuration. The WarehouseContainerProcessor job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.
• Job Trigger Type: Specifies the job type that triggers the scheduled job. By default, the job is a Cron job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job WarehouseContainerProcessor. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. By default, the job runs every 10 seconds: 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user of the Shipping area that is used to run the WarehouseContainerProcessor job. By default, the user is EXMSystemUser.

LabelCategories

This code list defines the label categories for warehouse containers:

• Master/Mixed Label
• Mixed Single Label
• Pack Label
• Quick Receive Label
• Single Label

LabelTemplateMapping

If a trading partner information is not available in the PackageLabel BOD, the Shipping area receives the PackageLabelTemplateCode from LN. The code is used to assign the correct trading partner from the code list LabelTemplateMapping. The property value Item Label Type of this trading partner is used as label type.

For example: PackageLabelTemplateCode=abc; code list LabelTemplateMapping: abc=A9100.

This code list has been implemented to support the Line-side Labeling process in the Shipping area. See the description of the code list PackageLabelDocumentTypes.

LabelTemplatePrintoutMappings

This code list defines the label categories to be printed based on the PackageLabelTemplateCode element of the PackageLabel BOD imported in the Shipping area. These codes for the package label template are included:

• MML: Master/Mixed Label
• MSL: Mixed Single Label
• PAL: Pack Label
• QRL: Quick Receive Label
• SIL: Single Label

LabelTypes

This code list includes the label type definitions.

MappingsEDIPlant

This code list contains the names of the code lists that define a mapping of the EDI plant information. See the description of code list EDIPlantMappingFord.

MaterialEntryReasonCodes

This code list includes the reason codes for material entries of the trading partner Fiat Chrysler Automobiles (FCA).

MergeShipments

This code list is used to activate the merging of shipments in the Shipping area:

• Name: Defines the name of the MergeShipments configuration. The MergeShipments job entry that has the name "parameter" is used as the default configuration.
• Active: Activates the merging of shipments. The merging of shipments is deactivated by default.
• Line Number Creation Mode: The default setting Renumber Based on Previous Maximum Line Number renumbers new shipment lines starting with the preceding shipment's maximum line number.
• Line Number Increment: : Increment that is used to renumber new shipment lines.
• Line Number Separator: Separator for line numbers.

MixedLoadLabelTypes

This code list defines the mixed load label types.

MixedMasterLabelTypes

This code list defines the mixed master label types.

MixedSingleLabelTypes

This code list defines the mixed single label types.

MovementCertificates

This code list contains the Movement Certificates EUR.1, EUR-MED, A.TR., NAFTA, and FormA that are supported by the Shipping area. Each Movement Certificate has these property values:

• Default Language: Default language of the Movement Certificate.
• Additional Language: Four additional fields to define used languages.
• Max. Number of Line Item Lines: The maximum number of lines that are printed in line item fields.
• Number of Used Text Fields: Number of used text fields.
• Default Text 1–10: Fields to define default text entries.
• Label for Text 1–10: Fields to define text labels.

MovementCertificatesDefaultTexts

This code list contains default texts for Movement Certificates. The description is a text that relates to a specific document and describes the target field. The set names start with "I18N_".

MovementCertificatesIsActive

In Shipping, the Movement Certificates tab is shown on the Manage Shippers page, if the task Print Movement Certificates is defined in the task list and this parameter is activated. By default, the Movement Certificates tab is disabled.

PackageLabelDocumentTypes

When importing the PackageLabel BOD, the Shipping area checks whether labels must be printed for a specific document type. The incoming BOD is checked against the active document types, which are stored in the code list PackageLabelDocumentTypes.

This code list has been implemented to support the Line-side Labeling process in the Shipping area. See the description of code list LabelTemplateMapping.

PackagingIsActive

Activates the Manage Packaging application in the Shipping area, if the check box is selected. By default, the parameter is deactivated.

PackingListTypes

This code list includes the packing list types.

PackingSlipTypes

This code list includes the packing slip types.

PackLabelTypes

This code list includes the pack label types.

PoolPoints

Shipping area.

This code list includes the list of defined pool points. A pool point has parameters that are used to build a master shipment in the Shipping area. These parameters are the pool point address, the DUNS Number and the Tax ID:

• Automatically Create Master Shipment: If this check box is selected, master shipments are created automatically. Shippers are assigned the same master bill of lading number if they fulfill these criteria: They have the same pool point ID, the same trading partner, and a specified time frame.
• Start of Shipment Date Time Frame (Hours): Start date of the time frame that is constitutive for the creation of master shipments. The specified hours are subtracted from the shipment date of the master shipment.
• End of Shipment Date Time Frame (Hours): End date of the time frame that is constitutive for the creation of master shipments. The specified hours are added to the shipment date of the master shipment. The specified values indicate that shippers with shipping dates within this time frame can be combined into a master shipment. These shippers can be sent to the pool point using the same truck.
• Name: The name of the pool point's address.
• 'Attention of' Name: This field contains the name of the person the request is directed to.
• Unit: Name of the unit
• Floor: Number of the floor
• Building: Number of the building
• Building Name: Name of the building
• Post Office Box: Post office box
• Street: Name of the street
• Postal Code: Postal code of the address
• City: Name of the city
• Country: Name of the country
• Country Subdivision: Name of the country subdivision
• DUNS Number: The Data Universal Numbering System number is a unique nine-digit code that is used to identify companies and group entities within an organization. It is issued at a company's request by the business information provider, Dun & Bradstreet.
• Tax ID: The tax ID is a number used to identify legal persons or businesses. The tax authorities assign the tax numbers to the registered businesses. Your business partners must provide their tax number. Business partners without a tax number are considered to be private persons.

Example: Start of Shipment Date Time Frame (Hours) = "0", End of Shipment Date Time Frame (Hours) = "3". In this example, the shipment time of the master shipment is assumed to be 12 AM. Shippers with a shipment time from 12 AM to 3 PM are consolidated to one master shipment. To include shippers with a shipment time of 11 AM in the master shipment, specify "1" in the Start of Shipment Date Time Frame (Hours) field. The specified value is subtracted from the shipment time of the master shipment. Therefore, the shippers that are scheduled for 11 AM are included.

PreferenceCriteria

This code list contains the NAFTA Preference Criteria. NAFTA Preference Criteria are grouped into categories identified on the NAFTA Certificate of Origin by letters "A" through "F". The preference criterion is used to certify the country of origin and the preference status when shipping goods within NAFTA countries.

PreferentialTradeAgreements

This code list contains the preferential trade agreements between countries. These agreements levy the customs duty on items or allow the export or import of goods without custom charges.

You can use the entry Without Preference, if no preferential trade agreement is required to export goods to the country of destination. On the Manage Shippers page in the Shipping area, no movement certificate is shown for such an item.

You can use the entry Preference without known Agreement, if you currently do not know the required preferential trade agreement for an item. You can specify the required preferential trade agreement for such an item later on the Manage Shippers page in the Shipping area. The status of the related shipper in the Shipping area cannot be set to Complete, unless a valid preferential trade agreement is selected.

Each preferential trade agreement has these property values:

• Document Type: Name of the preferential trade agreement form.
• Based on Preferences: The check box is selected if the agreement is based on preferences.
• Protocol: The protocol that is used. The field is for information only.
• Default Language: Default document language of the preferential trade agreement form.
• Direction: Direction of the preferential trade agreement which are Bidirectional, Partial Bidirectional, or Unidirectional. The field is for information only.
• Cumulation Rule: Rules of origin and cumulation. The field is for information only.
• Tariff Program Code: Tariff Program Code (USA). The field is for information only.
• Currency: The currency of the preferential trade agreement form. The field is for information only.
• Mandatory Amount: The defined mandatory amount of items. The field is for information only.
• Default Text 1–10: Fields to define default text entries.

QuickReceiveLabelModes

This code list defines the printing modes for quick receive labels.

• None: No printing mode
• PerConsignment: Quick receive label is printed per shipper.
• PerShipment: Quick receive label is printed per included shipment.
• PerTHU: Quick receive label is printed per transport handling unit.

QuickReceiveLabelTypes

This code list defines the quick receive label types:

• None
• Quick Receive Label

SequenceAdditionalItems

A mapping of the customer item number and Audi's logistics item number can be specified in this code list. The mapping is used in the Shipping area and supports the Audi sequencing process. The customer item number must be specified in the Name field.

ShipmentLineCreationModes

This code list defines the method of numbering new shipment lines for the merging of shipments:

• Add Shipment Number as Prefix: The old shipment number is used as a prefix concatenated with the old shipment line number together with the separator from code list MergeShipments to build the new shipment line number.
• Renumber Based on Previous Maximum Line Number: New shipment lines are renumbered starting with the preceding shipment's highest line number. If the shipment line numbers of the shipment to merge to are not numeric, the shipment line numbers are renumbered from scratch. Otherwise, the highest shipment line number of the shipment to merge to is increased by a line number increment. This value is set to the new shipment line number. The line number increment is defined in the code list MergeShipments. The value of the line number increment is by default 10.
• Renumber from Scratch: New shipment lines are renumbered from scratch. When you select the option or the option Renumber Based on Previous Maximum Line Number, and line numbers are not numeric, a numeric numbering is used. The first new shipment line number is the increment value plus the increment value. The line number increment is by default 10. The subsequent shipment line number is calculated by adding the increment value to the highest shipment line number of the previously merged shipment.

ShipmentTypes

This code list includes the shipment types that are used, for example, by the trading partner Fiat Chrysler Automobiles (FCA).

ShippingAddressHandling

In the Shipping area, the Attention of Name field can be used as Ship To Name information for printouts. From release 11.0.3, customers can choose to use the Ship To Name as the default or the Attention of Name:

• If the parameter is deactivated, the Ship To Name is used for printing.
• If the parameter is activated, the Attention of Name is used for printing.

ShippingMeansOfTransportDefault

Defines the default value of a means of transport in a shipper. The default value is set to License Plate Number.

ShippingPrintouts

You can use this code list to manually configure print tasks in the Shipping area:

• Max. Number of Retries: Specifies the maximum number of retries to process a print request. By default, the maximum number of retries to process a print request is 100.
• Delay Before Retry (in Seconds): Specifies the delay time in seconds for a retry.
• Max. Number of Labels per Print Job: By default, the maximum number of labels per print request is set to 50. The parameter allows to define a different maximum number of labels per print request.
• Proforma Invoice Waiting Time (Seconds): Specifies the wait time in seconds for a proforma invoice.

ShippingTasks

You can use this code list to manually configure an automatic time-out for shipping tasks in the Shipping area.

Timeout for Shipping Tasks (in Seconds): Time-out to abort the task execution automatically after a predefined time. The default time-out for shipping tasks is 3,600 seconds.

SpecialItemCharacteristics

This code list defines the entries for the Special Item Characteristics field in the detail view of the Manage Item Master page. The field is used to store special item characteristics such as vehicle safety information. For example, Nissan distinguishes important items of type A from important items of type B. This information can typically not be imported from the ERP system. The information is required for label printing in the Shipping area. You can manage the field in the detail view of the Manage Shippers and Manage Warehouse Containers pages in the Shipping area. Currently, you can select these special characteristics definitions that suppliers of Nissan must comply with:

• OBD: Nissan Mexico OBD, items with special characteristics that are related to emissions regulations (on-board diagnostics)
• PIA: Nissan Mexico Important Part A, important safety-related items for steering control, braking system, or fuel system integrity
• PIB: Nissan Mexico Important Part B, important items for collision safety such as occupant protection during collision, post collision safety, or transmitting information necessary for safe driving

TaskProcessingForStatus

This code list defines the statuses that enable task processing in the Shipping area. The code list serves as referenced code list in the Customers and the TradingPartners code lists.

TaskProcessingTimeouts

This code list defines the task processing wait times for proforma invoices and ASNs:

• Proforma Invoice Waiting Time (Seconds): Specifies the default wait time of 300 seconds for a proforma invoice.
• ASN Waiting Time (in Seconds): Specifies the default wait time of 600 seconds for an ASN.

ThirdPartyFreight

This code list defines the address and contact information for any third party entity that is responsible for freight charges:

• Name: View or specify the name of the third party entity.
• 'Attention of' Name: This field shows an additional name.
• Unit: This field shows the unit name.
• Building: This field shows the building name.
• Post Office Box: This field shows the post office box
• Street: This field shows the street name.
• Address Lines 1-6: This field shows the address line details.
• Postal Code: This field shows the postal code.
• Country: This field shows the country.
• Country Subdivision: This field shows the name of the country subdivision.
• Phone: This field shows the phone number.
• Fax: This field shows the fax number.
• Emails: This field shows the email address(es).

THUPackingListTypes

This code list defines packing list types for transport handling units.

TransportationCodeCarrier

This code list defines the carrier transportation code:

• Bordereau Number
• License Plate Number

WaybillTypes

This code list includes the waybill types. For each waybill type, the parameter Waybill Printing Mode can be configured. The parameter enables to split printouts per shipment. The Waybill Printing Mode offers these settings:

• Print per Shipment: The waybill print task is split into print jobs for each included shipment.
• Print per Shipper: The waybill is printed per shipper.
• No printout: The waybill task does not create any print jobs for this waybill type.

The code list DocumentPrintingModes is used as referenced code list for the print modes.

For the GALIA waybill, the default setting is Print per Shipment. For all other waybill types, the default setting is Print per Shipper.

WorkflowNames

This code list includes the workflow names that are used in the Master Data setup.