<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/ec/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the Electronic Commerce package</Title>
	</Header>
	<GlossaryEntry ID="000061" Version="B60asy04" ContextApps="ec"><Term>acknowledgment</Term>
		<Definition>The notification of the receipt of an order or a change to an existing order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000024" Version="B60asy04" ContextApps="ec"><Term>address code ID</Term>
		<Definition>A code used to provide information about the coding system used to produce the address/partner code ID.</Definition>
		<SimpleSection><List><ListIntro>For example, in EDIFACT:</ListIntro>
				<ListItem>SA: denotes a code determined by the supplier</ListItem>
				<ListItem>ZZ: denotes a code determined by mutual consultation</ListItem>
				<ListItem>EN: denotes coding according to EANCOM The address/partner code ID is a qualifier (qualifier 1) used to convert business partners, sales office codes or purchase office codes, and warehouse codes.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000027" Version="B60asy04" ContextApps="ec"><Term>address type</Term>
		<Definition>A code that identifies the type of location, address, or business partner. For example: invoice-to or ship-from. The address/partner type is a qualifier (qualifier 2) used to convert business partners.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000090" Version="B60asy04" ContextApps="ec"><Term>ANSI</Term>
		<Definition>This acronym stands for American National Standards Institute. ANSI is the central body responsible for the identification of a single consistent set of voluntary standards called American National Standards. ANSI is also the US representative to nontreaty standards organizations.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000083" Version="B60asy04" ContextApps="ec"><Term>appl_comm</Term>
		<Definition>A subdirectory that contains generated messages that must be read by an internal company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000081" Version="B60asy04" ContextApps="ec"><Term>appl_from</Term>
		<Definition>The directory that stores all messages generated by EDI. This directory is where your translation/communication software will retrieve files for export. This directory is not included in a multicompany (internal EDI) network.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000085" Version="B60asy04" ContextApps="ec"><Term>appl_text</Term>
		<Definition>A directory of temporary files that are used to build up text blocks. Records exist in this directory if a message contains any text fields.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000082" Version="B60asy04" ContextApps="ec"><Term>appl_to</Term>
		<Definition>The directory that stores all messages to be received into the SSA ERP application. This directory is where the translation/communication software will write files that must be processed and imported by EDI.</Definition>
		<SimpleSection><Paragraph>This is not included in multicompany (internal EDI) network.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000100" Version="B60adoc0" ContextApps="ec"><Term>application error</Term>
		<Definition>In Electronic Commerce, a type of error that occurs while processing incoming EDI messages. For example, an application error can occur when the message mentions an invalid item.</Definition>
		<SimpleSection><Paragraph>An application error can be linked to a ERP application field, a field identifier, and an application-error-code description.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000044" Version="B60asy04" ContextApps="ec"><Term>carriage condition</Term>
		<Definition>A code that describes the terms and conditions for (Dutch) national bills of ladin g according to AVC (General Transportation Conditions), and international bills of lading according to CMR (Convention de Marchandises Route part).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000096" Version="B60adoc1" ContextApps="ec"><Term>change reason</Term>
		<Definition>A means used to identify the reason for a change to a sales or purchase order, for example, a contract limitation, feasibility issue, or transportation limitation. A change reason is identified by a code.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000097" Version="B60asy04" ContextApps="ec"><Term>change type</Term>
		<Definition>A user-defined code that can be used to identify types of changes made to orders, such as a price change or quantity increase.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000063" Version="B60asy04" ContextApps="ec"><Term>character conversion</Term>
		<Definition>The rules that state how characters from the ERP application are translated before they are placed in a message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000016" Version="B60asy04" ContextApps="ec"><Term>character conversion code</Term>
		<Definition>A code used to define how characters from the application environment should be transferred to the ASCII files. For example, characters can be converted to uppercase, or specific punctuation marks can be ignored in an EDI message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000046" Version="B60asy04" ContextApps="ec"><Term>charge category</Term>
		<Definition>A code used to indicate the type of costs in the EDI message</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>Total costs incurred.</ListItem>
				<ListItem>Cash on delivery charges.</ListItem>
				<ListItem>Transport costs.</ListItem>
				<ListItem>Transport costs up to a specified point/location.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000076" Version="B60asy04" ContextApps="ec"><Term>code in the application</Term>
		<Definition>A code used in the ERP application that must be translated before sending the message: for example, the order type or the business partner (customer or supplier) code.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000077" Version="B60asy04" ContextApps="ec"><Term>code in the message</Term>
		<Definition>A standard code used in a specific EDI message that must be translated to or from a value in your ERP application: for example, the EDI message contains a unit of measure that can differ from the one used in SSA ERP. This unit of measure must be translated to ensure that the correct unit of measure is transmitted in the EDI message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000086" Version="B60adoc0" ContextApps="ec"><Term>Command</Term>
		<Definition>In Electronic Commerce, a directory used for semaphores.</Definition>
		<SimpleSection><Paragraph>Use the semaphore, or flagging, mechanism to communicate with third-party translation/communication software to ensure that the third-party software and ERP EDI do not attempt to access files at the same time. This semaphore mechanism uses the creation and deletion of empty files in this subdirectory to indicate when certain processes are active or can be activated.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000041" Version="B60adoc0" ContextApps="ec"><Term>communication channel</Term>
		<Definition>The method of communication to which a number in a message may refer, such as telephone, fax, or telex.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000011" Version="B60asy04" ContextApps="ec"><Term>connect frequency</Term>
		<Definition>The number of times the connection with a specific network should be established.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000012" Version="B60asy04" ContextApps="ec"><Term>connect times</Term>
		<Definition>The time the connection with a specific network is established.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000040" Version="B60asy04" ContextApps="ec"><Term>contact function</Term>
		<Definition>A code that specifies the purpose of various contacts.</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>Dangerous goods contact.</ListItem>
				<ListItem>Notification contact (person or department to be notified if goods will arrive).</ListItem>
				<ListItem>Information contact.</ListItem>
				<ListItem>Principal that places order or contract.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000075" Version="B60asy04" ContextApps="ec"><Term>conversion setups</Term>
		<Definition>A code that defines the layout of the ASCII file that contains the message data. This code contains information on the mapping of data elements between ERP application tables and the ASCII files. Although predefined conversion setups are available, you can create your own custom conversion setups.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000065" Version="B60asy04" ContextApps="ec"><Term>conversion setups (definitions)</Term>
		<Definition>The method used to translate EDI messages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000064" Version="B60asy04" ContextApps="ec"><Term>conversion setups (names)</Term>
		<Definition>A code for the basic translation of the message header (global overhead) and one or more codes for the way(s) in which messages can be translated. The code is defined for each organization, message, and direction (and field type).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000066" Version="B60asy04" ContextApps="ec"><Term>conversion setups (relationships)</Term>
		<Definition>The relationships between the levels that represent the different sections of the EDI message (overhead, header, line, and footer).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000078" Version="B60asy04" ContextApps="ec"><Term>conversion table</Term>
		<Definition>A ERP application table that stores different code conversion values and their relationships between an external code (code in message) and the code in the ERP application.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000028" Version="B60asy04" ContextApps="ec"><Term>countries</Term>
		<Definition>The geographical regions by which you can classify business partners (customers and suppliers).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000059" Version="B60asy04" ContextApps="ec"><Term>currencies</Term>
		<Definition>The legal tender (generally used monetary unit) of a country.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000055" Version="B60asy04" ContextApps="ec"><Term>dangerous goods regulations</Term>
		<Definition>The regulations for the transport of dangerous goods</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>European agreement for the International Carriage of Dangerous Goods by Road (ADR).</ListItem>
				<ListItem>International agreement for the Transport of Dangerous Goods by Air (IATA).</ListItem>
				<ListItem>International regulations for the Transport of Dangerous Goods by Rail (RID).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000026" Version="B60asy04" ContextApps="ec"><Term>dates/times</Term>
		<Definition>A code that indicates (by organization) the shipping/collect dates.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000080" Version="B60asy04" ContextApps="ec"><Term>defaults.edi file</Term>
		<Definition>An ASCII file that contains EDI data.</Definition>
		<SimpleSection><List><ListIntro>The file contains the following data:</ListIntro>
				<ListItem>Networks.</ListItem>
				<ListItem>Messages supported by application.</ListItem>
				<ListItem>Messages supported by organization.</ListItem>
				<ListItem>Organizations.</ListItem>
				<ListItem>Code tables.</ListItem>
				<ListItem>Conversion setups.</ListItem>
				<ListItem>EDI expressions.</ListItem>
				<ListItem>Processing sessions for supported outgoing messages.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000047" Version="B60asy04" ContextApps="ec"><Term>dimension qualifier</Term>
		<Definition>A code used to specify the physical size of the units in consignments</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>Gross dimensions (including packaging).</ListItem>
				<ListItem>Load meters (length required for goods in a vehicle over its entire width and height).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000034" Version="B60adoc0" ContextApps="ec"><Term>discount</Term>
		<Definition>In Electronic Commerce, a means to record late payment surcharges and reductions and their associated descriptions. The discount is represented by a code.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000114" Version="B60asy04" ContextApps="ec"><Term>discount method</Term>
		<Definition>A code that indicates the way in which discounts are calculated if multiple discount levels are used.</Definition>
		<SimpleSection><List><ListIntro>Discounts are calculated according to one of the following amounts:</ListIntro>
				<ListItem>Gross: the discount is calculated over the gross amount.</ListItem>
				<ListItem>Net: the discount is calculated over the net amount. The net amount is calculated from the gross amount minus discounts at previous levels.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000004" Version="B60asy04" ContextApps="ec"><Term>EDI messages</Term>
		<Definition>An electronic document (for example, an electronic order acknowledgment) that consists of an organization and a message.</Definition>
		<SimpleSection><Paragraph>Incoming and/or outgoing messages are processed in specific libraries invoked by EDI communication sessions (for example, in the Sales Control (SLS), Sales Invoicing (SLI), Accounts Payable (ACP), Cash Management (CMG), Purchase Control (PUR), Inventory Handling (INH), and Electronic Data Interchange (EDI) modules).</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000079" Version="B60asy04" ContextApps="ec"><Term>EDI standard</Term>
		<Definition>A protocol defined at national and international levels to define the process, procedures, and format of electronically transmitted data (messages) between two business partners.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000005" Version="B60asy04" ContextApps="ec"><Term>EDIFACT</Term>
		<Definition>This acronym stands for Electronic Data Interchange for Administration, Commerce, and Transport. A worldwide organization developing standards for electronic data interchange.</Definition>
		<SimpleSection><Paragraph>There are other similar organizations (for example, Odette), each using its own subset of standard EDIFACT messages.</Paragraph>
			<Paragraph>When you define messages, you can use the naming convention that coincides with the standard naming conventions to which you are accustomed.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000092" Version="B60asy04" ContextApps="ec"><Term>electronic data interchange (EDI)</Term>
		<Definition>The computer-to-computer transmission of a standard business document in a standard format. Internal EDI refers to the transmission of data between companies on the same internal company network (also referred to as multisite or multicompany). External EDI refers to the transmission of data between your company and external business partners.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000053" Version="B60asy04" ContextApps="ec"><Term>equipment qualifier</Term>
		<Definition>A code used to identify types of equipment that will be used as a result of the EDI message, such as container, pallets, and trailer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000067" Version="B60asy04" ContextApps="ec"><Term>evaluation expressions</Term>
		<Definition>The expression that indicates which lines of a conversion setup definition are executed and which are not and which fields in the ASCII field are filled and which are not.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000006" Version="B60asy04" ContextApps="ec"><Term>file layout</Term>
		<Definition>A format that indicates for incoming messages whether the data for the message will reside in a single file or in multiple files. In a single file, the <GUIRef href="/baanerp/ec/edi/ecedi0105s000#ecedi005.ipos" role="formfield">Level Identification Position</GUIRef> field indicates the position of the level identifier (as defined within the conversion setup), which identifies the record in the ASCII file (for example, header, header text, and line).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000111" Version="B60adoc0" ContextApps="ec"><Term>forwarding agent</Term>
		<Definition>An organization that provides transport services. You can link a default forwarding agent to both ship-to business partners and ship-from business partners. In addition, you can print sales and purchase orders on a packing list, sorted by forwarding agent.</Definition>
		<SimpleSection><Paragraph>For ordering and invoicing, you must define a forwarding agent as a business partner.</Paragraph>
			<Paragraph>Synonym: carrier</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000098" Version="B60asy04" ContextApps="ec"><Term>functional syntax error</Term>
		<Definition>A code that uses the functional syntax editing of the message to identify an external syntax error.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000069" Version="B60asy04" ContextApps="ec"><Term>generated messages</Term>
		<Definition>The outgoing messages that exist in ASCII files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000071" Version="B60asy04" ContextApps="ec"><Term>generated reference numbers</Term>
		<Definition>The unique references generated when outgoing messages are created.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000058" Version="B60asy04" ContextApps="ec"><Term>government actions</Term>
		<Definition>The activities carried out by government agencies with respect to transactions or transportation.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000057" Version="B60asy04" ContextApps="ec"><Term>government agencies</Term>
		<Definition>A code that represents government agencies involved in transactions or transport, such as customs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000056" Version="B60asy04" ContextApps="ec"><Term>government involvement indicator</Term>
		<Definition>A code that indicates whether an activity is required or completed on behalf of the government.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000031" Version="B60asy04" ContextApps="ec"><Term>item code ID</Term>
		<Definition>A code used to provide information about the coding system used to produce the item code ID.</Definition>
		<SimpleSection><List><ListIntro>For example, in EDIFACT:</ListIntro>
				<ListItem>SA: denotes a code determined by the supplier</ListItem>
				<ListItem>ZZ: denotes a code determined by mutual consultation</ListItem>
				<ListItem>EN: denotes coding according to EANCOM</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000099" Version="B60asy04" ContextApps="ec"><Term>item code system</Term>
		<Definition>An external, alternate way of coding items. Coding systems can be general standard systems (such as EAN) or systems that are dependent on a specific business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000022" Version="B60asy04" ContextApps="ec"><Term>item status</Term>
		<Definition>A code that informs the supplier about the status of the item.</Definition>
		<SimpleSection><List><ListIntro>Statuses can include, for example:</ListIntro>
				<ListItem>New item.</ListItem>
				<ListItem>Obsolete item.</ListItem>
				<ListItem>Current item/production.</ListItem>
				<ListItem>Production design adjusted since previous delivery.</ListItem>
				<ListItem>Current item/spare parts.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000101" Version="B60asy04" ContextApps="ec"><Term>kind of charge</Term>
		<Definition>A code that identifies the type of charge associated with the message, such as surcharge, freight, handling, or setup.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000116" Version="B60asy04" ContextApps="ec"><Term>lot identification</Term>
		<Definition>The lot identification code is a qualifier (qualifier 1) used with the lot code (tdsls041.clot or tdpur041.clot). The lot code ID indicates whether the lot code transferred in the EDI message is the internal lot code (whltc100.clot) or the business partner's lot code (whltc100.ltbp).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000115" Version="B60asy04" ContextApps="ec"><Term>lot selection</Term>
		<Definition>A code used to indicate special conditions regarding the delivery of lot items on order lines.</Definition>
		<SimpleSection><List><ListIntro>You can determine how lot numbers are assigned by selecting one of the following methods:</ListIntro>
				<ListItem>Any: the selection of lots on delivery is not subject to any special conditions. More than one lot can be used.</ListItem>
				<ListItem>Same: any lot can be selected for delivery, but the entire delivery must be drawn from the same lot.</ListItem>
				<ListItem>Specific: only one specific lot can be used.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000050" Version="B60asy04" ContextApps="ec"><Term>measurement qualifier</Term>
		<Definition>A code used to specify the type of measurement referred to in an EDI message, such as gross size, gross weight, and net weight.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000038" Version="B60asy04" ContextApps="ec"><Term>message function</Term>
		<Definition>A code that describes (by organization) the purpose of various messages, such as acknowledgment, modification, addition, and reminder. The code determines the meaning of a field in a received EDI message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000102" Version="B60asy04" ContextApps="ec"><Term>message status</Term>
		<Definition>A code that identifies the current status of outgoing messages based on predefined status values.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000068" Version="B60asy04" ContextApps="ec"><Term>messages to be generated</Term>
		<Definition>The EDI messages that are marked for generation but have not yet been included in ASCII files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000009" Version="B60asy04" ContextApps="ec"><Term>network</Term>
		<Definition>A code that identifies a communication network used to manage data flow through an intermediary (such as communication through a Value Added Network (VAN) via an EDI-translator) or directly, without translation, to a sister company that uses the same software.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000013" Version="B60asy04" ContextApps="ec"><Term>network addresses</Term>
		<Definition>A code used to identify users/business partners in a network. Generally, these addresses are assigned by the network manager.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000118" Version="B60asy04" ContextApps="ec"><Term>order list</Term>
		<Definition>A document that contains the items that have been selected for purchase. Eventually, order lists are converted to sales orders or purchase requisitions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000017" Version="B60asy04" ContextApps="ec"><Term>order type</Term>
		<Definition>A code used to determine the character or function of an order and, consequently, of the message.</Definition>
		<SimpleSection><List><ListIntro>Examples:</ListIntro>
				<ListItem>Normal order versus return order</ListItem>
				<ListItem>Invoice versus credit note</ListItem>
			</List>
			<Paragraph>The classification that determines which sessions (in which sequence) are part of the order procedure. You can also assign one of the following categories to the order type: cost order, collect order, return order, and subcontracting order.</Paragraph>
			<List><ListIntro>Order type codes are required in the ERP EDI messages that relate to a single order. EDI messages that relate to single orders include messages that process:</ListIntro>
				<ListItem>Orders (ANSI X12 850, UN/EDIFACT ORDERS).</ListItem>
				<ListItem>Order changes (ANSI X12 860, UN/EDIFACT ORDCHG).</ListItem>
				<ListItem>Order acknowledgments (ANSI X12 855 and 865, UN/EDIFACT ORDRSP).</ListItem>
				<ListItem>Invoices (ANSI X12 810, UN/EDIFACT INVOIC).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000003" Version="B60asy04" ContextApps="ec"><Term>organization</Term>
		<Definition>A code that represents a set of standards (such as ANSI X12, UN/EDIFACT, and VDA) used in EDI communication.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000008" Version="B60asy04" ContextApps="ec"><Term>outgoing messages by session</Term>
		<Definition>The messages that are created by specific ERP sessions, by organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000023" Version="B60asy04" ContextApps="ec"><Term>packing code ID</Term>
		<Definition>A code used to record packing codes and their descriptions.</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>Box</ListItem>
				<ListItem>Pallet</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000051" Version="B60asy04" ContextApps="ec"><Term>packing types</Term>
		<Definition>A code used to describe packing methods, such as bulk (liquid or solid), container, palletized, box, and drum/barrel.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000033" Version="B60asy04" ContextApps="ec"><Term>period</Term>
		<Definition>A code used to record (by organization) types of time periods and their associated description. For example: days, weeks, and quarters.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000049" Version="B60asy04" ContextApps="ec"><Term>plus/minus indicators</Term>
		<Definition>A code used to add a plus or minus sign to a value in an EDI message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000103" Version="B60asy04" ContextApps="ec"><Term>receipt discrepancy</Term>
		<Definition>A code that identifies hether the quantity on the shipment notice message was more than or less than the actual quantity received, or that no advanced shipment notice was received at the time the goods were received.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000074" Version="B60asy04" ContextApps="ec"><Term>received batch reference</Term>
		<Definition>A unique identifier associated with a particular network so that traceability and historical analysis can occur.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000073" Version="B60asy04" ContextApps="ec"><Term>received error messages</Term>
		<Definition>The warnings or errors that result from processing incoming EDI messages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000070" Version="B60asy04" ContextApps="ec"><Term>received messages</Term>
		<Definition>The data that consists of the most important header data in messages received from business partners. This data has been successfully processed and updated into the ERP application.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000015" Version="B60asy04" ContextApps="ec"><Term>reference number</Term>
		<Definition>The numbering system used to identify outgoing messages. This number uniquely identifies the message and is created when an EDI message is generated. Because the actual data belonging to the message is distributed over multiple ASCII levels, this number is also used to identify which parts of the message belong together.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000025" Version="B60asy04" ContextApps="ec"><Term>reference number type</Term>
		<Definition>A code that indicates the document associated with a particular number.</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>ON: Order Number</ListItem>
				<ListItem>WB: Waybill Number</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000110" Version="B60asy04" ContextApps="ec"><Term>sales contract</Term>
		<Definition>A code that identifies a specific sales agreement. You can also link the customer, contract data, and sales representative to a sales contract code.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000072" Version="B60asy04" ContextApps="ec"><Term>saved messages to be received</Term>
		<Definition>The saved EDI message data that is read when processing incoming EDI messages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000104" Version="B60asy04" ContextApps="ec"><Term>schedule quantity type</Term>
		<Definition>A code that identifies whether the scheduled message quantities are actual or cumulative.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000018" Version="B60asy04" ContextApps="ec"><Term>schedule release frequency</Term>
		<Definition>The frequency of the schedule releases for goods to be delivered.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000020" Version="B60asy04" ContextApps="ec"><Term>schedule status</Term>
		<Definition>A code that informs the supplier about the degree to which the customer is committed and adds an instruction to an order.</Definition>
		<SimpleSection><List><ListIntro>One of the following instructions is added:</ListIntro>
				<ListItem>Firm order: the supplier can deliver.</ListItem>
				<ListItem>Fabrication: the supplier can start production.</ListItem>
				<ListItem>Raw material: the supplier can buy raw materials.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000105" Version="B60asy04" ContextApps="ec"><Term>schedule type</Term>
		<Definition>A code that identifies whether the current schedule for the message is based on customer production, delivery, planned delivery, planned shipment, or shipment.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000021" Version="B60asy04" ContextApps="ec"><Term>schedule-release category</Term>
		<Definition>A code that indicates if a schedule must be regarded as a change to or a substitute for a previous schedule. If you change a schedule, you can adjust the previous instruction before the date and time indicated. If you substitute a schedule, you can replace the previous instruction using the date and time indicated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000106" Version="B60asy04" ContextApps="ec"><Term>shipment status</Term>
		<Definition>A code that identifies whether the shipment status of the message is scheduled or canceled.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000054" Version="B60asy04" ContextApps="ec"><Term>shipper-supplied equipment indicator</Term>
		<Definition>A code used to describe equipment that may or may not be provided by the shipper (principal).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000088" Version="B60asy04" ContextApps="ec"><Term>store_recv</Term>
		<Definition>A directory that logs all received messages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000089" Version="B60asy04" ContextApps="ec"><Term>store_sent</Term>
		<Definition>A directory that logs all sent messages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000002" Version="B60asy04" ContextApps="ec"><Term>supported EDI messages</Term>
		<Definition>The incoming and/or outgoing messages that are supported by the application. These messages can be active (actually used within the company) or not.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000007" Version="B60asy04" ContextApps="ec"><Term>supported messages by business partner</Term>
		<Definition>The EDI messages used by specific business partners. Only after a business partner and a specific message (incoming and/or outgoing) have been linked can the business partner communicate with your ERP application with that particular message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000036" Version="B60asy04" ContextApps="ec"><Term>tax code</Term>
		<Definition>A code that indentifies the tax rate and which determines how SSA ERP calculates and registers tax amounts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000035" Version="B60asy04" ContextApps="ec"><Term>tax code ID</Term>
		<Definition>A code used to provide information about the coding system used to produce the tax code ID.</Definition>
		<SimpleSection><List><ListIntro>For example, in EDIFACT:</ListIntro>
				<ListItem>SA: denotes a code determined by the supplier</ListItem>
				<ListItem>ZZ: denotes a code determined by mutual consultation</ListItem>
				<ListItem>EN: denotes coding according to EANCOM</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000048" Version="B60asy04" ContextApps="ec"><Term>temperature qualifier</Term>
		<Definition>A code used to indicate the type of temperature referred to in an EDI message.</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>Transport temperature</ListItem>
				<ListItem>Storage temperature</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000042" Version="B60asy04" ContextApps="ec"><Term>terms of delivery function</Term>
		<Definition>A code used to describe the terms of delivery or transport.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000060" Version="B60asy04" ContextApps="ec"><Term>terms of payment/late payment surcharges</Term>
		<Definition>The conditions of payment for a transaction between business partners.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000039" Version="B60asy04" ContextApps="ec"><Term>time zone specifier</Term>
		<Definition>A code that indicates the time zone that applies to the specified date and time in the message, such as the supplier's time zone.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000087" Version="B60asy04" ContextApps="ec"><Term>trace</Term>
		<Definition>A directory that contains the created log (trace) files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000014" Version="B60asy04" ContextApps="ec"><Term>trace file</Term>
		<Definition>A file that contains process data about read or created ASCII files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000093" Version="B60asy04" ContextApps="ec"><Term>transaction set</Term>
		<Definition>A complete business document such as a purchase order, invoice, or sales order. A transaction set is synonymous with document or message.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000052" Version="B60asy04" ContextApps="ec"><Term>transport stage</Term>
		<Definition>A code used to describe types of transportation, for example, used in pre-carriage, main carriage, and post-carriage.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000032" Version="B60asy04" ContextApps="ec"><Term>transport type</Term>
		<Definition>A code used to record the various means of transport and their associated descriptions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000107" Version="B60asy04" ContextApps="ec"><Term>transportation method</Term>
		<Definition>A code that identifies whether the goods associated with the message will be shipped by road, rail, sea, air, or other.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000019" Version="B60adoc0" ContextApps="ec"><Term>type of delivery specifier</Term>
		<Definition>A code that specifies a change in an order line (Transcom) or the reason for calling off an order (Odette).</Definition>
		<SimpleSection><List><ListIntro>Types of delivery include:</ListIntro>
				<ListItem>Extra unplanned delivery.</ListItem>
				<ListItem>Delivery required for sample inspection.</ListItem>
				<ListItem>Backorder.</ListItem>
				<ListItem>Urgent delivery.</ListItem>
				<ListItem>Cancellation of previous order.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000045" Version="B60asy04" ContextApps="ec"><Term>type of monetary amount</Term>
		<Definition>A code that describes the type of amount in the EDI message.</Definition>
		<SimpleSection><List><ListIntro>For example:</ListIntro>
				<ListItem>Payable amount</ListItem>
				<ListItem>Customs value</ListItem>
				<ListItem>Invoice amount</ListItem>
				<ListItem>Insured value</ListItem>
				<ListItem>Sample value (value of (free) sample)</ListItem>
				<ListItem>Goods value</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000043" Version="B60asy04" ContextApps="ec"><Term>type of supplementary information</Term>
		<Definition>A code used to specify various types of information in an EDI message, such as bill of lading remarks, general information, or special service request.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000094" Version="B60asy04" ContextApps="ec"><Term>VAN</Term>
		<Definition>A company that provides communications services for EDI, such as line speed conversion and protocol matching.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000095" Version="B60adoc0" ContextApps="ec"><Term>VDA</Term>
		<Definition>Acronym for Verband der Automobilindustrie; A standard for automotive electronic interchange of business transactions in Germany. This particular standard uses a fixed length field/record format.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000109" Version="B60asy04" ContextApps="ec"><Term>warehouse</Term>
		<Definition>A code that identifies the warehouse address for a business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000091" Version="B60asy04" ContextApps="ec"><Term>X12</Term>
		<Definition>The ANSI standard for interindustry electronic interchange of business transactions within the US. The accredited subcommittee of American National Standards Institute has a mandate to develop standard data formats for business transactions with cross-industry applications.</Definition>
	</GlossaryEntry>
</Glossary>
