Common

ActiveInactive

This code list is used for the ION Pulse alerting as reference code list to handle the status.

AlertGroups

This code list defines the alert groups. The alert groups are assigned to distribution groups.

• Distribution Group: The distribution group contains the persons to which the alert message is sent. Default distribution groups are specified by the installation for each alert group.
• Document Reference Type: This setting is required to enable a drill-back action from the sent alert message to the application.
• Status: Here you can specify the status for the alert messages that are assigned to this alert group. By default, each delivered alert group is active.

Alerts

This code list defines the alert messages that are supported by the application. The alert messages are assigned to a distribution group or an alert group.

• Alert Group: Each alert message must be assigned to an alert group.
• Distribution Group: Here you can specify a distribution group for the alert message distribution. By default, the distribution group is set by the assigned alert group.
• Document Reference Type: This setting is required to enable a drill-back action from the sent alert message to the application.
• Status: You can specify whether the alert message is active or inactive. Only for an active alert message, a Pulse Alert BOD is created and sent to ION. By default, each alert message is enabled by assigning it to an alert group.

AWSProperties

In this code list, the credentials are stored that are used by the application to access the Amazon Web Services (AWS) S3 and SQS. You can have a maximum of two active or inactive access keys simultaneously.

• Access Key: Specifies the access key used by the application to access AWS S3 and SQS.
• Secret Key: Specifies the secret key used by the application to access AWS S3 and SQS.
• Retry After: Specifies the delay time in seconds for a retry to load the credentials. The default value is 5 seconds delay time. Permitted values are 0 to 60 seconds.
• Maximum Number of Retries: Specifies the maximum number of attempts to load the credentials. The default value is 50. Permitted values are 0 to 200 retries.
• AWS Region Name: Specifies the region name that is used by AWS SQS. The region names are taken from the referenced code list AWSRegions. The default region is US East.
• S3 Root Bucket Name: Specifies the AWS S3 root bucket name. The default value is infor-prd-ae-us-east-1.

AWSRegions

This code list defines the region names that are used by the Amazon Web Services (AWS).

AWSQueues

This code list defines the AWS SQS queues that are used by the application. The code list stores the variables that are used by the Common AWS Interface per folder in the current tenant. The configured queues are created by the job AWSQueuesUpdater in AWS SQS.

• Component Name: Specifies the name of the functional area in the application. Allowed names are AMD, PRM, EXM, SRM, and TFS.
• Subqueue Name: Specifies the name of the sub queue. Allowed values are RES and REQ.
• Visibility Delay: Specifies the time in seconds that a message received from a queue will be invisible to other receiving components. The default value is 30 seconds. Permitted values are 0 to 432000 seconds.
• Message Retention Period: Specifies the time in days that AWS SQS will retain a message, if it is not deleted. The default value is 7 days. Permitted values are 1 to 14.
• Maximum Message Size: Specifies the maximum message size in KB accepted by AWS SQS. The default value is 256 KB. Permitted values are 1 to 256 KB.
• Delivery Delay: Specifies the time in seconds used to delay the first delivery of all messages added to the queue. The default value is 0 seconds. Permitted values are 0 to 900 seconds.
• Message Receipt Timeout: Specifies the maximum time in seconds that a long polling ReceiveMessage request sent to the AWS SQS queue will wait for a message before it returns an empty response. The default value is 10 seconds. Permitted values are 0 to 20.
• Retry After: Specifies the delay time in seconds for a retry request to send to the SQS service. The default value is 5 seconds delay time. Permitted values are 0 to 60 seconds.
• Maximum Number of Retries: Specifies the maximum number of attempts for a request to send to the SQS service. The default value is 50. Permitted values are 0 to 200 retries.

AWSStorages

This code list defines the AWS S3 folders that are used by the functional areas in the application. The code list stores the variables that are used by the Common AWS Interface per folder in the current tenant. The configured folders are created by the job AWSStorageUpdater in AWS S3.

• Component Name: Specifies the name of the functional area in the application. Allowed names are AMD, PRM, EXM, SRM, and TFS.
• Folder Name: Specifies the path of a folder. For example, the folders request and response are used for the printing.
• Expiry after Days: Specifies the days for which the S3 objects are kept in this folder. The default value is 90 days. Permitted values are greater than 0.
• Retry After: Specifies the delay time in seconds for a retry request to send to the S3 service. The default value is 5 seconds delay time. Permitted values are 0 to 60 seconds.
• Maximum Number of Retries: Specifies the maximum number of retries for sending a request to the S3 service. The default value is 50. Permitted values are 0 to 200 retries.

CarrierMasterUpdateFields

: Response folder forThis code list contains the fields that can be updated or not updated by the import of the carrier master data from the ERP system. The fields are shown in the detail view of the Manage Carrier Master page in the application. The update modes used for carrier master data are defined in the code list UpdateModes.

You can make these fields editable:

• Carrier Address List
• Carrier External Attributes
• Carrier DUNS ID
• Carrier Effective from Date
• Carrier E-Mail Address
• Carrier Fax Number
• Carrier Data Last Modified By
• Carrier Name
• Carrier's Person in Charge
• Carrier Phone Number
• Carrier SCAC

CategoriesUnitsOfMeasure

This code list includes categories for units of measure.

CommodityCodesCNImport

Defines settings for the import of the CN Commodity Codes:

• Import Folder: Defines the absolute path to the folder where the import files for the CN Commodity Codes are stored. The value is set automatically by the installation procedure. In an automotive environment, the default path is AUTOCONNECT_HOME/amd/import/CN.
• Import File: Defines the default name for the Commodity Codes import file. Default file name is CN13EN.xml.
• Chapters: Defines the chapters that are imported when importing the CN Commodity Codes. We recommend that you specify the commodity chapters required for your business processes. Importing all chapters results in a large CommodityCodes code list that can cause performance problems of the application.
• Language Codes: Defines the languages that are imported when importing the CN Commodity Codes. Default language codes are DE, EN, FR.
• System Language Code: Defines the system language code that is used when importing the CN Commodity Codes. By default, the system language code is EN.

CommodityCodesHTSImport

Defines settings for the import of the HTS Commodity Codes:

• Chapters: Defines the chapters that are imported when importing the HTS Commodity Codes. We recommend that you specify the commodity chapters required for your business processes. Importing all chapters results in a large CommodityCodes code list that can cause performance problems of the application.
• Max No of Error Lines: Defines the maximum of error lines.
• Accounting Entities: Defines a comma-separated list of accounting entities.

ComponentHostMappings

This code list has an entry for each application server. It specifies the applications that are running on designated servers using designated port numbers. In an on-premises installation, all applications usually run on the same server. Some functions, for example, the Job Manager Service, communicate with the applications. The information that is specified in this code list enables the communication.

system.

• Name: Defines the name of the mapping of the functional area in the application to the specified host. Valid entries are AMD, EXM, PRM, SRM, and TFS.
• Host Name: Fully qualified name of the host. In a cloud environment, this is the name of the load balancer.
• Port: Port number of the host.
• SSL Port: SSL port number of the host for a secured connection.
• Application Context: Name of the application server that is mapped to the specified host.

ContactMasterUpdateFields

This code list contains the fields that can be updated or not updated by the import of the contact master data from the ERP system. The fields are shown in the detail view of the Manage Contact Master page. The update modes used for contact master data are defined in the code list UpdateModes.

You can make these fields editable:

• Birthday
• Contact Accounting Entity
• Contact Communication Channels
• Contact ID
• Department
• Effective from Date
• First Name
• Gender Code
• Job Title
• Last Modified By
• Last Name
• Middle Name
• Note
• Status
• Name Suffix
• Title
• Version

Countries

This code list includes the ISO alpha-2 country codes.

CountrySubdivision

This code list includes country subdivision codes of the United States of America.

Currencies

This code list includes the ISO 4217 currency codes.

You can edit these property values:

VDA Code: VDA code of the currency code.

CustomerMasterUpdateFields

This code list contains the fields that can be updated or not updated by the import of the customer master data from the ERP system. The fields are shown in the detail view of the Manage Customer Master page. The update modes used for customer master data are defined in the code list UpdateModes.

You can make these fields editable:

• Customer Address List
• Customer DUNS ID
• Customer Effective from Date
• Customer E-Mail Address
• External Representative for Customer
• Customer Fax Number
• Internal Representative for Customer
• Customer Name
• Parent Customer Name
• Customer's Person in Charge
• Customer Phone Number
• Customer Tax ID

Customers

This code list includes the customer definitions.

You can edit these property values:

• Time Zone: If there are several customers using the same trading partner, you can specify a time zone. Time zones are defined in the TimeZones code list. This list contains all available time zones. The TimeZonesOwn code list contains the user-specific time zones. User-specific time zones are used to represent system dates such as processing dates of plans or log entry dates. Time zones support is also available for the representation of requirement dates such as shipment dates or arrival dates of goods.
• Language Code: Specify the language in which to print the documents.
• Language Code for Export-Related Documents: Specify the language in which to print the export-related documents.
• Trading Partner: This field contains the trading partner ID. The trading partners are maintained as master data codes.
• Third Party Freight: This field contains a third party entity to which third-party freight charges can be assigned. The ThirdPartyFreight code list includes the list of defined third party entities.
• Pool Point: This field contains the pool point of the customer. A pool point has parameters that are used to build a master shipment in Shipping, a pool point address, a DUNS Number and a Tax ID. The PoolPoints code list includes the list of defined pool points.
• Workflow Name: This field contains the name of the workflow. A workflow summarizes tasks that are assigned to groups of customers. With the Automotive workflow, for example, CarrierRoute and Shipment BODs trigger the creation of a shipper. The Automotive workflow uses these tasks:
  • Print Transport Handling Unit Labels
  • Print Labels
  • Print Packing List Labels
  • Print Packing List
  • Print Waybill
  • Print EDI Waybill
  • Print Packing Slip
  • Carrier Interface Processing
  • Print Movement Certificate
  • Publish ASN
  • Compliance Check
  • Non-Compliance Blocker
  • Print Quick Receive Labels
• Country of Origin: Select the check box to print the country of origin on the packing slip.
• Person in Charge: This field indicates the person at the supplier's location who is responsible for the shipper.
• Customer's Person in Charge: This field indicates the person at the customer's location who is responsible for the shipper.
• Container Aggregation Mode: This field shows how containers are aggregated for label printing.
  Note: A master container is a container on the floor level, level 1, that contains sub containers, for example, a pallet. A master container does not contain shipped goods.
  • No Aggregation: No aggregation is performed.
  • Aggregate Master: Each container with the Master role is aggregated to a Single role container. All items in inner containers are assigned to the Single role container. All inner containers are set to auxiliary containers.
  • Aggregate Single Pallet as Master: Each container with the Single role that is not contained in any outer container and that has assigned the Pallet packaging type in Packaging Information is set to the Master role.
• Pattern for Formatting Customer Container Type: Controls the BMW Container Management Process in Shipping. The field is used 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. The field references the entries of the code list CustomerContainerTypePatterns. See "Configuring layer calculation".
• Master Label Type: This label type is used on a transport handling unit that include inner packaging containing the same item. Normally, it provides information about the transport handling unit and the contained item.
• Mixed Label Type: This label type is used on transport handling units that include inner packaging of different items. Normally, it provides information about the transport handling unit, the supplier and the receiver. Sometimes, it provides a list of the contained items. This is especially the case when the label is a Global Transport Label (GTL) that uses this information in form of a 2D barcode.
• Single Label Type: Generally, this label type is used for a stand-alone inner packaging, which only contains one kind of item. It identifies the container and the item that is contained. According to VDA 4902, this label can also be used for containers for which no label is printed for the inner packaging.
• Waybill Type: A waybill is a transport document that confirms a contract between a carrier and a transport buyer for the transport of goods. Types of waybills are, for example, air waybill, CMR waybill, or rail shipment note. You use the WaybillTypes code list to maintain waybill types.
• EDI Waybill Type: An EDI waybill according to VDA 4912 is a waybill sent through EDI together with an ASN. It contains a summary of the ASN contents.
• Packing List Type: A list of contents of one or more containers, potentially independent of packing slip numbers.
• Packing Slip Type: A packing slip is a document created by shipping personnel that accompanies a shipment and lists the contents of the shipment. You use the PackingSlipTypes code list to maintain packing slip types.
• Minimum Status for Packing Slip Task Processing: The minimum status that is required in Shipping to print the packing slip. The table shows the available statuses.
  Note: The statuses are taken from the TaskProcessingForStatus code list.

  Status	Description
  Complete Shipper	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. All the included shipments have the Shipped status.
  Printable Shipper	For this shipper, the SyncCarrierRoute BOD, SyncShipment BOD, and an optional SyncInvoice BOD have been processed. All of the shipments of the shipper have the Printable status. This status also allows shippers with the status of Complete to be processed.
  Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Invoice.
  No Printing Mode	The task cannot be processed.
  Proforma Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Proforma Invoice, Mixed Pricing or Priced via Invoice.
  Released Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Released status.
  Shipped Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Shipped status.
  Staged Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Staged status.

• ASN Type: Specify the type of Advanced Ship Notice (ASN). An ASN is an EDI formatted electronic notification of pending deliveries, an electronic packing list. The purpose of the ASN is to inform the recipient that the shipment is in transit.
  • AMES-T is a VW-specific process in which the VW TSB Generator is used to print the transport and shipment documents according to the VDA 4939 recommendation.
  • Automatic Transport Document
  • No ASN Type
  • Process ASN after all Invoices
  • Process ASN after all Proforma Invoices
  • Standard
  • Transport Document
  • With Dispatch Order
• ASN Cancellation Supported: If this check box is selected, the ASN cancellation and the ASN replacement are active on the Manage Shippers page in Shipping. This feature addresses suppliers who require the cancellation or the replacement of an ASN that has already been sent to the customer by EDI. The functionality enables suppliers to cancel or replace an ASN in Shipping. The canceled or replaced ASN is sent to Transformation Services. The customer is informed by EDI about the incorrect information that has been sent or the changed data.
• Split Shipment Lines by RAN: If this processing logic is enabled, the item quantities of boxes that contain items with the same item number are split by RAN/Kanban numbers. This configuration is required, for example, for the trading partner Renault.
• Number of Copies:

  This field defines the number of ASN copies that must be created. If Number of Copies is 0, no ASN copy is created. Typically, an ASN must be sent to the receiver of the goods. If it is required in the business scenario, also other parties must be informed about the executed shipment. Up to three ASN copies can be created and sent to different message receivers involved in the supply chain.

  Shipping creates a corresponding number of ASN requests for Transformation Services in addition to the ASN request based on the selected ASN Type. The original ASN is sent to the customer.

• Check Homogeneous Container Structure: If this check box is selected, a special check of the container structure is active. You can enable the check in the TradingPartners and Customers code lists. The options Heterogeneous, Homogeneous, and Unknown are configured on shipment line level in the Homogeneous Pallet field. This function is required, for example, for the trading partners Renault and PSA.
• Code List for Mapping EDI Plant: Select a code list for the mapping of the EDI plant. See the description of the code list MappingsEDIPlant.
• DUNS Number: Specify the Data Universal Numbering System (DUNS) number of the customer. The DUNS 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.
• Pick-Up Process: If this check box is selected, the pick-up process for trading partner A0260 PSA Europe is enabled in Shipping.
• Own E-Mails: The supplier's email address.
• Own Fax No.: The supplier's fax number.
• Customer's Fax No.: The customer's fax number.
• Own Phone No.: The supplier's phone number.
• Customer's E-Mails: The customer's email address.
• Customer's Phone No.: The customer's phone number.
• Calculate CUM for Containers: Enables the calculation of container CUMs for reusable containers in Shipping.
• Manufacturer Number: The manufacturer number is used to process the MAT Label for trading partner A3150 Continental Europe. To enable the usage of the MAT Label, select the label type MAT Label in the customer-specific entries Master Label Type and Single Label Type of the Customers code list.
• Add Container Item to ASN: If enabled, the container item is added to the ASN that is published in Shipping.
  Note: This check box should be selected for all customers who are assigned to trading partner A0101 Chrysler North America.
• Manufacturing Location: The manufacturing location is used to process the MAT Label for trading partner A3150 Continental Europe. To enable the usage of the MAT Label, select the label type MAT Label in the customer-specific entries Master Label Type and Single Label Type of the Customers code list.
• Destination Label Type: This label is used per transport handling unit. It provides the exact destination for the transport handling unit. It does not provide any item information.
• Mixed Load Label Type: Unlike the Mixed Label Type, this label is used to indicate a mixed transport handling unit. Usually, it only contains the MIXED LOAD caption, but no other information. It is used together with a Transport Handling Unit Packing List or a list of type Mixed Master Label.
  Note: This label is different from the B10 and B16 labels. These are, in Shipping terminology, mixed labels.
• Mixed Master Label Type: This label identifies a specific item as part of a transport handling unit. It is used for mixed outer packaging, and usually, multiple labels of type Mixed Master Label are printed.
  Note: Different trading partners use different criteria to determine when a label to be printed. Usually, the label is used together with a Mixed Load Label or a mixed label.
• Item Consolidation Mode: The item consolidation mode allows to consider trading partner-specific definitions of a "mixed pallet" and based on the selected definition to print labels for a mixed pallet.
  • No Label Mode
  • Per Item
  • Per Item and Lot
  • Per Item and Lot and Order
  • Per Item and Lot and RAN or Kanban
  • Per Item and Order
  • Per Item and RAN or Kanban
• Quick Receive Label Type: This label type facilitates the process that covers the receiving of shipments. It usually only contains the shipment or ASN number in the barcode format. It allows to receive a transport handling unit, shipment, or container by scanning a 1D barcode.
  Note: The Quick Receive Label is printed as part of the Print Quick Receive Labels task. Use the Quick Receive Label Mode to configure whether a master shipment label, shipment label, or several transport handling unit labels must be printed.
• Quick Receive Label Mode: This table shows the label modes.

  Label type	Description
  Quick Receive Label per Shipper	This label type is used to facilitate the receiving of shippers.
  Quick Receive Label per Shipment	This label type is used to facilitate the receiving of included shipments.
  Quick Receive Label per Transport Handling Unit	This label type is used when the transport handling unit must be labeled with a Quick Receive Label.

• Minimum Status for Quick Receive Label Task Processing: The table shows the available statuses.
  Note: The statuses are taken from the TaskProcessingForStatus code list.

  Status	Description
  Complete Shipper	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. All the included shipments have the Shipped status.
  Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Invoice.
  No Printing Mode	The task cannot be processed.
  Proforma Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Proforma Invoice, Mixed Pricing or Priced via Invoice.
  Released Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Released status.
  Shipped Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Shipped status.
  Staged Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Staged status.
  Printable Shipper	Note: This status is not applicable to Minimum Status for Quick Receive Label Task Processing.

• Packing List Label Type for Transport Handling Unit : This label type is used for all types of packing lists on the transport handling unit level. Example: Ford’s Mixed Master Load List, which replaces the Mixed Master Label and contains each item of a transport handling unit. The item number and the quantity are printed in a human-readable form and as barcodes.
• Mixed Single Label Type: Some trading partners allow or require the delivery of more than one item in a single inner packaging. In LN and in the application, this requirement may be fulfilled through the use of virtual containers. Additionally, this process requires the Mixed Single Label Type to be selected. The Mixed Single Label contains information about more than one item.
• Pack Label Type: Inner packaging can contain different items, and can contain packs. A pack usually contains a specific item. A pack can be labeled. For this scenario, a Pack Label is required. Example: A container contains a thousand screws, which are packed in twenty bags of fifty screws each. Each of the bags is labeled with a Pack Label, the container with a single label, or, a Mixed Single Label.
• Use Intermediate Containers on ASN: Intermediate containers are containers to which no other role is assigned in the packaging structure. You can select this check box if you are working with at least three genuine packaging levels without auxiliary packaging. The outer level of packaging is represented by the outer master or mixed packaging level. The inner level is represented by the single packaging level. The intermediate level is represented by the intermediate packaging. If this check box is cleared, intermediate containers are declared as auxiliary packaging. All the boxes that are contained are directly assigned to the parent container of this packaging.
• Cost Item for Clause 92: Specifies the cost item for the Chrysler Clause 92 process. Based on the contract for the cost item, Clause 92 allows the supplier to request reimbursement for expendable packaging. Returnable containers should have been used but were not available.
• Expected Delivery Date: This property value can be used to print the earliest expected delivery date on shipping labels and documents. You can choose one of these options:
  • Blank: The expected delivery date is extracted from a single instance of this date in the SyncShipment BOD. In this case, the extracted date is not necessarily the earliest delivery date.
  • Select the Earliest Expected Delivery Date: The delivery date from each shipment line of the SyncShipment BOD is printed as the Expected Delivery Date on the shipping labels and documents for the selected customer.
• Add Julian Day to Route Field in Shipper: If this check box is enabled, the shipper's route is truncated to the last three numeric digits and then concatenated with the Julian Day. This information is then published in the Route field on the Manage Shippers page in Shipping, and in the shipping documents.
• Discrete Quantities in Sequential Production Forecast: This option allows discrete quantities during a sequential production forecast.
• Suppress Lot ID in Outbound Documents: If this check box is selected, the lot ID is included in the ASN and printed on labels.
• Print Tax ID: If this check box is selected, the tax number is included in the print request and printed on the waybill.
• Print "Ship on Behalf of" Address for Customer facing Documents: Select this check box to enable the "Ship on Behalf of" feature for customer-facing documents (such as container labels, packing slips, EDI waybills, etc.) in the direct delivery process. All such documents use the supplier and ship from information from the supplier party and not from the sub-supplier. This includes also identification numbers like DUNS or ID’s given by the end-customer to identify the supplier.
• Print "Ship on Behalf of" Address for Carrier facing Documents: Select this check box to enable the "Ship on Behalf of" feature for carrier-facing documents (for example, the waybill) in the direct delivery process. If this check box is enabled, the waybill documents use the supplier and ship from information from the supplier party and not from the sub-supplier.
• Print "Ship on Behalf of" Address for Customs Documents: Select this check box to enable the "Ship on Behalf of" feature for customs documents in the direct delivery process (for example, the movement certificates used in shipping). The movement certificates use the supplier and ship from information from the supplier party and not from the sub-supplier.
• Use Internal Revision ID: The option defines the information that is shown in the Engineering Change Level field in the shipment lines of a shipper and printed on labels. By default, the option is not selected:

  If disabled, the Engineering Change Level is set to the shipment line reference Revision Number. If not available, the field is set to the shipment line reference Revision Level. If not available, the Engineering Change Level is set to null.

  If enabled, the Engineering Change Level is set to the ShipmentItem/ItemID/RevisionID. If the information is not available, the Engineering Change Level is set to null.

DataExportImportFolders

Defines the paths for the file import and export for each functional area in the application. The value is set automatically by the installation procedure.

• EXM: By default, in an automotive environment the import path for the Shipping is ${AUTOCONNECT_HOME}\exm\import and the export path ${AUTOCONNECT_HOME}\exm\export.
• Printing: By default, in an automotive environment the import path for the printing is ${AUTOCONNECT_HOME}\printing\import and the export path ${AUTOCONNECT_HOME}\printing\export.
• TFS: By default, in an automotive environment the import path for the Transformation Services is ${AUTOCONNECT_HOME}\tfs\import and the export path ${AUTOCONNECT_HOME}\tfs\export.

DistributionGroups

This code list defines the groups of persons who receive an alert message. A group consists of a list of persons who must be defined in the DistributionPersons code list.

• Language Code: Here you must select the language for the alert message. It is only possible to send an alert message in one language to a distribution group.
• Person ID: You can specify up to 20 persons per distribution group who receive the alert message. These persons must be defined in the code list DistributionPersons.

DistributionPersons

This code list defines the persons who receive an alert message. Person ID: Specify the Person ID from IFS that identifies the receiver of an alert message. The person must be an existing user in IFS. The Person ID is not validated here.

• Alerts:
• DistributionPersons:
• DistributionGroups:

DocumentReferenceTypes

This code list is required for workflow drill backs in Infor ION Pulse.

EuropeanUnion

This code list contains a list of country codes and language codes of countries that belong to the European Union.

ExcessTransportationReasonCodes

This code list includes the list of defined reasons for excess transportation. The code list shows the UN/EDIFACT, ASC X12, and VDA codes that are used in the "Authorization for Excess Transportation Charges" (AETC) process.

For an excess transportation, the OEM must authorize the exceeding transportation costs during shipment preparation. Additional information is required in this process:

• The reason for excess transportation
• The responsibility for excess transportation
• The excess transportation authorization number that is given by the OEM

In the detail view of the Manage Shippers page in Shipping, the fields Authorization Number, Reason Code, and Responsibility Code can be managed. The Reason Code field references the ExcessTransportationReasonCodes code list. The Responsibility Code field references the ExcessTransportationResponsibilityCodes code list. The Shipping area publishes the excess transportation information in the ASN.

ExcessTransportationResponsibilityCodes

This code list includes the list of defined responsibilities for excess transportation. The code list shows the UN/EDIFACT, ASC X12, and VDA codes that are used in the "Authorization for Excess Transportation Charges" (AETC) process.

For an excess transportation, the OEM must authorize the exceeding transportation costs during shipment preparation. Additional information is required in this process:

• The reason for excess transportation
• The responsibility for excess transportation
• The excess transportation authorization number that is given by the OEM

In the detail view of the Manage Shippers page in Shipping, the fields Authorization Number, Reason Code, and Responsibility Code can be managed. The Reason Code field references the ExcessTransportationReasonCodes code list. The Responsibility Code field references the ExcessTransportationResponsibilityCodes code list. The Shipping area publishes the excess transportation information in the ASN.

FederalTradeCommissionTypes

This code list defines the country of origin types according to the rules of the Federal Trade Commission:

FreightTerms

This code list defines the freight terms. The freight terms include the valid VDA and EDIFACT codes that are used for the style sheet mapping in Transformation Services.

Incoterms

This code list supports the handling of Incoterms in Shipping. The code list contains all values that are defined for the Incoterms 2010. Each Incoterms value is stored in the Name field and the description of the value in the Short Description field. The field Description is left empty.

In the Shipment Details in Shipping, you can use a Lookup button to select an Incoterms value from the DeliveryTerms field. The field references the code list Incoterms.

ItemConsolidationModes

To consider trading partner-specific criteria for the definition of mixed pallets, you can configure the Item Consolidation Mode field in the Customers and TradingPartners code lists. The definition of a mixed pallet can differ from trading partner to trading partner. For some trading partners, the item type is the significant criterion to decide whether a label for a mixed pallet should be printed. All other criteria such as batch or order number are not considered. For other trading partners, a pallet is "mixed" when it carries only one item type, but various lots. The Item Consolidation Mode makes these discrepancies manageable, because it allows to interpret different shipment lines as equal lines.

This code list defines the selectable criteria for the Item Consolidation Mode field:

• No Label Mode: Per shipment and shipment line number.
• Per Item: Two items are considered equal if the item number is the same. All other properties are ignored.
• Per Item and Lot: Two items are considered equal if the internal item numbers and lots of these two items are the same.
• Per Item and Lot and Order
• Per Item and Lot and RAN or Kanban
• Per Item and Order
• Per Item and RAN or Kanban

ItemMasterUpdateFields

This code list contains the fields that can be updated or not updated by the import of the item master data from the ERP system. The fields are shown in the detail view of the Manage Item Master page. The update modes used for item master data are defined in the code list UpdateModes.

You can make these fields editable:

• Base Unit of Measurement Code
• Commodity Code of Item
• Customs Procedure for Item
• Default Tariff Agreement
• Item Main Description
• Federal Trade Commission Country of Origin
• Federal Trade Commission Type
• Hazardous Material Description
• Hazardous Material ID
• Hazardous Material Indicator
• List of Countries of Origin
• List of Item Descriptions
• List of External Attributes
• NAFTA Cost Method
• NAFTA Country of Origin
• Preference Criterion
• Preferential Trade Agreement
• Special Item Characteristics
• Substantial Transformation Country of Origin

ItemUsage

This code list includes the item usage codes.

You can edit these property values:

Key: Code of the item usage.

ItemUsageVW

This code list includes the item usage codes for the trading partner VW.

You can edit these property values:

Production, Initial Sample, Serial Part: Code of the item usage.

JobAWSQueueUpdater

This code list defines the configuration of the AWSQueueUpdater job. The job creates and updates the AWS SQS queues that are used by the application. The job cannot remove AWS SQS queues. The parameters that are used by the job to create the AWS SQS queues are configured in the AWSQueues code list.

• Name: Defines the name of the AWSQueueUpdater job configuration. The AWSQueueUpdater 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 of type Simple 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 of starting the AWSQueueUpdater job. The default value is 1.
• Job User: Defines the user that is used to run the AWSQueueUpdater job. By default, the user is AMDSystemUser.
• 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.

JobAWSStorageUpdater

This code list defines the configuration of the AWSStorageUpdater job. The job creates and updates the AWS S3 folders that are used by the application. The job cannot remove AWS S3 folders. The parameters that are used by the job to create the AWS S3 folders are configured in the AWSStorages code list.

• Name: Defines the name of the AWSStorageUpdater job configuration. The AWSStorageUpdater 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 of type Simple 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 of starting the AWSStorageUpdater job. The default value is 1.
• Job User: Defines the user that is used to run the AWSStorageUpdater job. By default, the user is AMDSystemUser.
• 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.

JobEXMDataCreator

This code list defines the configuration of the EXMDataCreator job.

• Name: Defines the name of the EXMDataCreator job configuration. The EXMDataCreator 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 Cron expression for the EXMDataCreator job. The default Cron expression is 0 0 0 31 12 ? 2030.
• 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 that is used to run the EXMDataCreator job. By default, the user is EXMSystemUser.
• Small Shipper Count: The small shipper count.
• Pause after Shipper Count Of: The job pauses after the defined shipper count.
• Big Shipment Count: The big shipment count.
• Duration of Break in Seconds: Duration of the break in seconds.
• Existing Shipper Count: The existing shipper count.
• Accounting Entities: Accounting entities for which the job is enabled.

JobInboundMessageCleanup

This code list defines the configuration of the InboundMessageCleanup job.

• Name: Defines the name of the InboundMessageCleanup job configuration. The InboundMessageCleanup 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 Cron expression for the InboundMessageCleanup job. The default Cron expression is 0 0 0 ? * SUN.
• 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 that is used to run the InboundMessageCleanup job. By default, the user is SystemUser.
• Percentage to Clean: Percentage of inbound messages to clean.

JobInboundMessageProcessor

This code list defines the configuration of the InboundMessageProcessor job.

• Name: Defines the name of the InboundMessageProcessor job configuration. The InboundMessageProcessor job entry that has the name "processor_01" 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 of type Simple 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 InboundMessageProcessor job. The default value is 10000.
• 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 that is used to run the InboundMessageProcessor job. The default user is AMDSystemUser.
• 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.

JobSchedulerTriggerTypes

This code list defines the Cron and Simple trigger types for the Job Manager Service that schedules jobs on the Manage Scheduled Jobs page.

JobSRMDataCreator

This code list defines the configuration of the SRMDataCreator job.

• Name: Defines the name of the SRMDataCreator job configuration. The SRMDataCreator 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 Cron expression for the SRMDataCreator job. The default Cron expression is 0 0 0 31 12 ? 2030.
• 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 that is used to run the SRMDataCreator job. By default, the user is SRMSystemUser.
• Small Plan Count: The small plan count.
• Pause after Plan Count Of: The job pauses after the defined plan count.
• Big Plan Count: The big plan count.
• Duration of Break in Seconds: Duration of the break in seconds.
• Existing Plan Count: The existing plan count.
• Accounting Entities: Accounting entities for which the job is enabled.

JobTFSDataCreator

This code list defines the configuration of the TFSDataCreator job.

• Name: Defines the name of the JobTFSDataCreator job configuration. The JobTFSDataCreator 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 of type Simple 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 of starting the TFSDataCreator job. The default value is 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 that is used to run the TFSDataCreator job. By default, the user is TFSSystemUser.
• Small Message Count: The small message count.
• Break after Message Count Of: The job pauses after the defined message count.
• Big Message Count: The big message count.
• Duration of Break in Seconds: Duration of the break in seconds.
• Existing Message Count: The existing message count.
• Customer: Customer for which the job is enabled.
• Ship To ID: Ship to ID for which the job is enabled.
• Accounting Entities: Accounting entities for which the job is enabled.

LabelFormats

This code list includes the label formats Large, Medium, Small, and Z3425.

LanguageCodes

This code list includes the language code definitions.

NAFTACalculationMethods

This code list defines the calculation methods that are used within the NAFTA free-trade zone to calculate the regional value content of goods.

• NC: Net cost method
• NO: Other method

NAFTACountries

This code list defines the countries of origin within the NAFTA free-trade zone.

NAFTAProducers

This code list defines the producer categories that indicate whether the shipper is also the producer of goods. The information is required to complete the NAFTA Certificate of Origin.

• NO(1): Known as an originating good, if the shipper does not produce the goods
• NO(2): Reliance on the producer's written representation that the good is as an originating good, if the shipper does not produce the goods
• NO(3): Completed and signed certificate for the good provided to the exporter by the producer, if the shipper does not produce the goods
• YES: The party shipping the goods is also the producer of the goods.

PriceUnits

This code list includes the quantities of items to which the prices relate.

PrintingIsActive

This code list is used to enable or disable printing for the Transformation Services and the Release Management.

If printing is disabled, no printing activity can be performed in the Transformation Services and the Release Management. By default, printing is enabled.

ShipmentStatusCodes

This code list includes the shipment status codes that are used by Transformation Services to support the Infor Transportation Management integration.

You can edit these property values:

• ASC X12 Code: ASC X12 code of the shipment status code.
• EDIFACT Code: EDIFACT code of the shipment status code.
• VDA Code: VDA code of the shipment status code.

ShipToMasterUpdateFields

This code list contains the fields that can be updated or not updated by the ship to master data from the ERP system. The fields are shown in the detail view of the Manage Ship To Master page. The update modes used for ship to master data are defined in the code list UpdateModes.

You can make these fields editable:

• DUNS ID
• Effective from Date
• Last Import Date
• Name
• Ship To ID
• Tax ID

TimeZones

This code list contains the entire list of time zones that are used by the application.

Time zones support is, for example, available for the representation of requirement dates such as pick-up dates or arrival dates of goods.

TimeZonesOwn

This code list contains the user-specific time zones that are defined for the specified application users.

User-specific time zones are used to represent the system dates such as processing dates of plans or log entry dates.

You can edit these property values:

Time Zone: Shows the user-specific time zone. You can select a time zone from the list of available time zones that are defined in the TimeZones code list.

TradingPartners

This code list includes the trading partner definitions.

You can edit these property values:

• Time Zone: If there are several customers using the same trading partner, you can specify a time zone. Time zones are defined in the TimeZones code list. This list contains all available time zones. The TimeZonesOwn code list contains the user-specific time zones. User-specific time zones are used to represent the system dates such as processing dates of plans or log entry dates. Time zones support is also available for the representation of requirement dates such as shipment dates or arrival dates of goods.
• Language Code: Specify the language in which to print the documents.
• Language Code for Export-Related Documents: Specify the language in which to print the export documents.
• Workflow Name: This field contains the name of the workflow. A workflow summarizes tasks that are assigned to groups of customers. With the Automotive workflow, for example, CarrierRoute and Shipment BODs trigger the creation of a shipper. The Automotive workflow uses these tasks:
  • Print Transport Handling Unit Labels
  • Print Labels
  • Print Packing List Labels
  • Print Packing List
  • Print Waybill
  • Print EDI Waybill
  • Print Packing Slip
  • Carrier Interface Processing
  • Print Movement Certificate
  • Publish ASN
  • Compliance Check
  • Non-Compliance Blocker
  • Print Quick Receive Labels
• Pool Point: This field contains the pool point of the trading partner. A pool point has parameters that are used to build a master shipment in Shipping, a pool point address, a DUNS Number and a Tax ID. The PoolPoints code list includes the list of defined pool points.
• Country of Origin: Select the check box to print the country of origin on the packing slip.
• Person in Charge: This field indicates the person at the supplier's location who is responsible for the shipper.
• Customer's Person in Charge: This field indicates the person at the customer's location who is responsible for the shipper.
• Container Aggregation Mode: This field shows how containers are aggregated for label printing.
  Note: A master container is a container on the floor level, level 1, that contains sub containers, for example, a pallet. A master container does not contain shipped goods.
  • No Aggregation: No aggregation is performed.
  • Aggregate Master: Each container with the Master role is aggregated to a Single role container. All items in inner containers are assigned to the Single role container. All inner containers are set to auxiliary containers.
  • Aggregate Single Pallet as Master: Each container with the Single role that is not contained in any outer container and that has assigned the Pallet packaging type in Packaging Information is set to the Master role.
• Pattern for Formatting Customer Container Type: Controls the BMW Container Management Process in Shipping. The field is used 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. The field references the entries of the code list CustomerContainerTypePatterns. See "Configuring layer calculation" in Shipping.
• Master Label Type: This label type is used on a transport handling unit that include inner packaging containing the same item. Normally, it provides information about the transport handling unit and the contained item.
• Mixed Label Type: This label type is used on transport handling units that include inner packaging of different items. Normally, it provides information about the transport handling unit, the supplier and the receiver. Sometimes, it provides a list of the contained items. This is especially the case when the label is a GTL implementation that use this information in form of a 2D barcode.
• Single Label Type: Generally, this label type is used for a stand-alone inner packaging, which only contains one kind of item. It identifies the container and the item that is contained. According to VDA 4902, this label can also be used for containers for which no label is printed for the inner packaging.
• Waybill Type: A waybill is a transport document that confirms a contract between a carrier and a transport buyer for the transport of goods. Types of waybills are, for example, air waybill, CMR waybill, or rail consignment note. You use the WaybillTypes code list to maintain waybill types.
• EDI Waybill Type: An EDI waybill according to VDA 4912 is a waybill sent through EDI together with an ASN. It contains a summary of the ASN contents.
• Packing List Type: A list of contents of one or more containers, potentially independent of packing slip numbers.
• Packing Slip Type: A packing slip is a document created by shipping personnel that accompanies a shipment and lists the contents of the shipment. You use the PackingSlipTypes code list to maintain packing slip types.
• Minimum Status for Packing Slip Task Processing: The minimum status that is required in Shipping to print the packing slip. The table shows the available statuses.
  Note: The statuses are taken from the TaskProcessingForStatus code list.

  Status	Description
  Complete Shipper	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. All the included shipments have the Shipped status.
  Printable Shipper	For this shipper, the SyncCarrierRoute BOD, SyncShipment BOD, and an optional SyncInvoice BOD have been processed. All of the shipments of the shipper have the Printable status. This status also allows shippers with the status of Complete to be processed.
  Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Invoice.
  No Printing Mode	The task cannot be processed.
  Proforma Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Proforma Invoice, Mixed Pricing or Priced via Invoice.
  Released Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Released status.
  Shipped Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Shipped status.
  Staged Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Staged status.

• ASN Type: Specify the type of Advanced Ship Notice (ASN). An ASN is an EDI formatted electronic notification of pending deliveries, an electronic packing list. The purpose of the ASN is to inform the recipient that the shipment is in transit.
  • AMES-T is a VW-specific process in which the VW TSB Generator is used to print the transport and shipment documents according to the VDA 4939 recommendation.
  • Automatic Transport Document
  • No ASN Type
  • Process ASN after all Invoices
  • Process ASN after all Proforma Invoices
  • Standard
  • Transport Document
  • With Dispatch Order
• ASN Cancellation Supported: If this check box is selected, the ASN cancellation and the ASN replacement are active on the Manage Shippers page in Shipping. This feature addresses suppliers who require the cancellation or the replacement of an ASN that has already been sent to the customer by EDI. The functionality enables suppliers to cancel or replace an ASN in Shipping. The canceled or replaced ASN is sent to Transformation Services. The customer is informed by EDI about the incorrect information that has been sent or the changed data.
• Split Shipment Lines by RAN: If this processing logic is enabled, the item quantities of boxes that contain items with the same item number are split by RAN/Kanban numbers. This configuration is required, for example, for the trading partners Renault and PSA.
• Check Homogeneous Container Structure: If this check box is selected, a special check of the container structure is active. You can enable the check in the TradingPartners and Customers code lists. The options Heterogeneous, Homogeneous, and Unknown are configured on shipment line level in the Homogeneous Pallet field. This function is required, for example, for the trading partners Renault and PSA.
• Code List for Mapping EDI Plant: Select a code list for the mapping of the EDI plant. See the description of the code list MappingsEDIPlant.
• Use License Plate as Container ID: If this check box is selected, the license plate number is used as container ID in Shipping.
• DUNS Number: Specify the Data Universal Numbering System (DUNS) number of the customer. The DUNS 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.
• Item Label Type: The Item Label Type references to the code list LabelTypes that defines all label types. You can use the property ItemLabel of the code list LabelTypes as value in the Item Label Type property of the TradingPartners code list. This type is used for category 1 labels, item labels.
• Pick-Up Process: If this check box is selected, the pick-up process for trading partner A0260 PSA Europe is enabled in Shipping.
• Calculate CUM for Containers: Enables the calculation of container CUMs for reusable containers in Shipping.
• Add Container Item to ASN: If enabled, the container item is added to the ASN that is published in Shipping.
  Note: This check box should be selected for all customers who are assigned to trading partner A0101 Chrysler North America.
• Destination Label Type: This label is used per transport handling unit. It provides the exact destination for the transport handling unit. It does not provide any item information.
• Mixed Load Label Type: Unlike the Mixed Label Type, this label is used to indicate a mixed transport handling unit. Usually, it only contains the MIXED LOAD caption, but no other information. It is used together with a Transport Handling Unit Packing List or a list of type Mixed Master Label.
  Note: This label is different from the B10 and B16 labels. These are, in Shipping terminology, mixed labels.
• Mixed Master Label Type: This label identifies a specific item as part of a transport handling unit. It is used for mixed outer packaging, and usually, multiple labels of type Mixed Master Label are printed.
  Note: Different trading partners use different criteria to determine when a label to be printed. Usually, the label is used together with a Mixed Load Label or a mixed label.
• Item Consolidation Mode: The item consolidation mode allows to consider trading partner-specific definitions of a "mixed pallet" and based on the selected definition to print labels for a mixed pallet.
  • No Label Mode
  • Per Item
  • Per Item and Lot
  • Per Item and Lot and Order
  • Per Item and Lot and RAN or Kanban
  • Per Item and Order
  • Per Item and RAN or Kanban
• Quick Receive Label Type: This label type facilitates the process that covers the receiving of shipments. It usually only contains the shipment or ASN number in the barcode format. It allows to receive a transport handling unit, shipment, or container by scanning a 1D barcode.
  Note: The Quick Receive Label is printed as part of the Print Quick Receive Labels task. Use the Quick Receive Label Mode to configure whether a master shipment label, shipment label, or several transport handling unit labels must be printed.
• Quick Receive Label Mode: This table shows the label modes.

  Label type	Description
  Quick Receive Label per Shipper	This label type is used to facilitate the receiving of shippers.
  Quick Receive Label per Shipment	This label type is used to facilitate the receiving of included shipments.
  Quick Receive Label per Transport Handling Unit	This label type is used when the transport handling unit must be labeled with a Quick Receive Label.

• Minimum Status for Quick Receive Label Task Processing: The table shows the available statuses.
  Note: The statuses are taken from the TaskProcessingForStatus code list.

  Status	Description
  Complete Shipper	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. All the included shipments have the Shipped status.
  Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Invoice.
  No Printing Mode	The task cannot be processed.
  Proforma Invoice	For this shipper, the SyncCarrierRoute BOD has been processed. It has either the Complete or the Processed status. The Priced status of the shipper is Priced via Proforma Invoice, Mixed Pricing or Priced via Invoice.
  Released Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Released status.
  Shipped Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Shipped status.
  Staged Shipment	All the shipments of the pro forma shipper or shipper that are currently available have at least the Staged status.
  Printable Shipper	Note: This status is not applicable to Minimum Status for Quick Receive Label Task Processing.

• Packing List Label Type for Transport Handling Unit : This label type is used for all types of packing lists on the transport handling unit level. Example: Ford’s Mixed Master Load List, which replaces the Mixed Master Label and contains each item of a transport handling unit. The item number and the quantity are printed in a human-readable form and as barcodes.
• Mixed Single Label Type: Some trading partners allow or require the delivery of more than one item in a single inner packaging. In LN and in the application, this requirement may be fulfilled through the use of virtual containers. Additionally, this process requires the Mixed Single Label Type to be selected. The Mixed Single Label contains information about more than one item.
• Pack Label Type: Inner packaging can contain different items, and can contain packs. A pack usually contains a specific item. A pack can be labeled. For this scenario, a Pack Label is required. Example: A container contains a thousand screws, which are packed in twenty bags of fifty screws each. Each of the bags is labeled with a Pack Label, the container with a single label, or, a Mixed Single Label.
• Use Intermediate Containers on ASN: Containers that are assigned no other role in the packaging structure. You can enable this option, if you work with at least three packaging levels without auxiliary packaging. In this scenario, the outer level is the outer master or mixed packaging. The inner level is the inner single packaging. The level between inner and outer level is the "intermediate" packaging. If this option is deenabled, which is the default, "intermediate" containers are declared as auxiliary packaging. All contained boxes are assigned directly to the parent container of this packaging.
• Cost Item for Clause 92: Specifies the cost item for the Chrysler Clause 92 process. Based on the contract for the cost item, Clause 92 allows the supplier to request reimbursement for expendable packaging. Returnable containers should have been used but were not available.

TransportationMethods

This code list includes the general types of carrier transportation used to deliver goods. The transportation method is typically used in North America in ASC X12 EDI.

You can edit these property values:

• EDIFACT Code: EDIFACT code of the transportation method.
• ASC X12 Code: ASC X12 code of the transportation method.
• VDA Code: VDA code of the transportation method.

UnitsOfMeasures

This code list includes the units of measure.

You can edit these property values:

• EDIFACT Code: EDIFACT code of the unit of measure.
• Decimals: Number of decimals that are considered.
• ASC X12 Code: ASC X12 code of the unit of measure.
• VDA Code: VDA code of the unit of measure.
• Category: Category to which the unit of measure belongs.