Tenneco Automotive Exhaust

Transcription

1 INFOR Tenneco Automotive Exhaust (TG) AutoMap TABLE OF CONTENTS General Information Transaction Sets and Versions Tenneco Automotive Exhaust's Destination Codes Commodity Code File Security Communication Method Implementation Identification Code File Master File Entry for Tenneco Automotive Exhaust Model Year EDI Code File Type Codes Frequency Codes Type Codes Frequency Codes Requirement File - Clear Flags CUM Required Prior ASNs ASN Cancellation Procedure Mandatory Fields /2005 1

2 ASN Header Maintenance Screen ID Numbers Screen Reference # Screen ASN Detail Maintenance Screen ASN Detail Reference Numbers Screen ASN Container Review Screen AutoMap Features and Preferences Activate or Deactivate Keywords - Change Error Types (Warning - Terminal) Auto-Transmit Flag for Remove Company and Network Combinations How to Use This Document General Information Security Implementation ASNs AutoMap Features and Preferences /2005 2

3 General Information General Information Transaction Sets and Versions The Tenneco Automotive Exhaust module supports the following transaction sets: 830 Material Release Version ASN Version Shipping Schedule Version Functional Acknowledgement Version 4010 The 830 (Material Release) contains planning requirements. The 856 (ASN) is required to be transmitted for each shipment when the truck leaves the plant. The ASN must be received before the shipment. The 862 (Shipping Schedule) contains firm ship requirements. The 997 (Functional Acknowledgement) is required to be transmitted to acknowledge the received 830s and 862s, within the time fame defined by Tenneco Automotive Exhaust. Tenneco Automotive Exhaust's Destination Codes Cambridge, ON Ligonier, IN Litchfield, MI Marshall, MI Seward, NE Smithville, TN /2005 3

4 General Information Commodity Code File MAINTAIN COMMODITY MASTER FILE Company Number... xx Commodity Code Description... SPECIAL HANDLING Description SPECIAL HANDLING Schedule B Check Digit... 0 Hazardous Material Description... HAZARDOUS MATERIAL DESCRIPTION HAZARDOUS MATERIAL DESCRIPTION HAZARDOUS MATERIAL DESCRIPTION HAZARDOUS MATERIAL DESCRIPTION 9999 HAZARDOUS MATERIAL DESC. F1=Help F10=Delete F12=Return Description - If the special handling code is used or sent, enter the code in the first three positions in the second description field. Transmitted in TD4*01 in the ASN file. Hazardous Material Description - If the hazardous material class code is used or sent, enter the hazardous material code in the first four positions in line five. Transmitted in TD4*03 in the ASN file. 5/2005 4

5 Security Security Communication Method Tenneco Automotive Exhaust communicates through the ACM (Advanced Communications Module) component. Enter security requirements (identification codes, passwords, etc.) before attempting to receive or transmit. Network security is entered one time, but may be accessed by multiple trading partners. For more information on ACM, see Chapter 17 of the AutoRelease main manual. 5/2005 5

6 Implementation Implementation Identification Code File The identification code file is used when taking the option to "split" a file received from Tenneco Automotive Exhaust, and also when transmitting ASNs. The identification code file is used differently by different manufacturers. Company Number OEM Code Plant ID - xx - TG - Your DUNS Number Press Enter to display remaining fields: OEM ID - Tenneco's DUNS Number plus suffix ( TA) Corporate ID Remit to Duns # Transmission Mode Smart Labels Pallet Staging Bar Code File Transfer Variable Unwrap Print Automatic print of 997 AutoMap - Not used by Tenneco Automotive Exhaust - Not used by Tenneco Automotive Exhaust - P - N - N - N - Y or N - N - Y Errors that occur during the "split" that indicate a code is missing from the identification code file are referring to plant ID or OEM ID. AutoMap - Enter Y to place data in the AutoMap files (during the split). Master File Entry for Tenneco Automotive Exhaust The entry of each master file is NOT explained in this document. Only the master files that require unique entry, to accommodate specific business practices for this trading partner are noted. Model Year Tenneco Automotive Exhaust does not send model year. Therefore, the requirement and price files must be entered leaving the model year fields blank. 5/2005 6

7 Implementation EDI Code File 830 Type Codes C - Firm D - Planning 830 Frequency Codes C - Daily F - Flexible M - Monthly W - Weekly 862 Type Codes C - Firm 862 Frequency Codes C - Daily Requirement File - Clear Flags The requirement master clear flags should not be marked. Keywords are used to determine what to clear based on purpose codes. CUM Required Prior Tenneco Automotive Exhaust does not send CUM Required Prior. Therefore it must be entered manually before going live. The CUM Required Prior is used to calculate ahead and behind figures and to round to package quantity. Enter the CUM Required Prior when entering a Tenneco Automotive Exhaust manual requirement or while testing. To enter, press F5 or select a part from the Manual Requirements Entry screen.4/2002 Page 9 5/2005 7

8 ASNs ASNs ASN Cancellation Procedure Call Tenneco Automotive Exhaust to cancel, then re-send only changes that were made to the ASN. Mandatory Fields ASN Header Maintenance Screen Purpose Code - Transmitted in the BSN 01. Valid codes include: O - Original 00 R - Replace 05 Equipment Description - Transmitted in the TD3 01. Valid codes include: RR - Rail Car TL - Trailer Equipment Initial - Transmitted in the TD3 02. Ship Date - Transmitted in the DTM 02. Ship Time - Transmitted in the DTM 03. SCAC Pick up - Transmitted in the TD5 03. Conveyance Code - Transmitted in the TD5 04 and REF 02. Valid codes include: AE - Air Express M - Motor P - Private Carrier Note: When the conveyance code is AE, the reason code, responsibility code and AETC must be entered in the AETC field. The AETC may be entered at shipper entry time or in the AETC field on the Reference Number window in ASN Maintenance. - The first position is the reason code - The second position is the responsibility code A = Customer plant/receiving location S = Supplier authority - The remaining 13 positions contain the AETC The reason code is transmitted in the ETD 01 segment. The responsibility code is transmitted in the ETD 02 segment. The0 conveyance code is transmitted in the ETD 03 segment. The AETC Code is transmitted in the ETD 04. Example: HA ETD*H*A*AE* /2005 8

9 ASNs ID Numbers Screen Supplier ID - Transmitted in the N1 04. Reference # Screen Conveyance Bill - Transmitted in the TD3 03. ASN Detail Maintenance Screen Cust Part # - Transmitted in the LIN 03. Qty. Ship - Transmitted in the SN1 02 and CTT 02. Ship Gross - Transmitted in the MEA 03. Qty Package - Transmitted in the CLD 02. CUM Shipped - Transmitted in the SN1 04. Unit/Mea - Transmitted in the SN1 03. Valid codes include: EA - Each LB - Pound ASN Detail Reference Numbers Screen Release # - Transmitted in the PRF 02. ASN Container Review Screen Cust Part # - Transmitted in the LIN 03. Container Description - Transmitted in the TD1 01. Container Qty - Transmitted in the TD1 02 and CLD 01. 5/2005 9

10 AutoMap Features and Preferences AutoMap Features and Preferences Some features and preferences within AutoMap can be maintained by the user, such as: Keywords may be activated or deactivated The auto-transmit 997 function may be turned on or off Company and VAN combinations may be added or removed. Activate or Deactivate Keywords - Change Error Types (Warning - Terminal) Keywords activate special processing to accommodate Tenneco Automotive Exhaust practices. To view keywords used by Tenneco Automotive Exhaust: 1. Access the AutoMap Menu. 2. Take the Process Keywords options. 3. Select the trading partner with 7 (keyword options). 4. Keywords are displayed for the selected trading partner. 5. Select the keyword to be changed with 1 (select). The error maintenance screen displays. The fields that can be changed include: Error Type - The error type may be W (warning) or T (terminal). T (terminal) - When the create and transmit ASNs option is taken the ASN records are checked for missing fields that may cause the ASNs to be rejected. If terminal errors are found, (errors that will cause the ASN to be rejected according to OEM specifications) the program ends, the ASN Verification Report prints and a break message is displayed. Terminal errors must be corrected before taking the create and transmit option again. W (warning) - When the create and transmit ASNs option is taken the ASN data is verified. If only warning errors are found, the ASN Verification Report prints and a break message is displayed that gives the user the option to continue with errors or to cancel. Error Message - The message that is displayed when this error is encountered may be changed. Active - The keyword may be active (Y) or inactive (N). 5/

11 AutoMap Features and Preferences Auto-Transmit Flag for 997 Maps are created to automatically transmit a 997 to the trading partner upon receipt of a file. Some trading partners do not require a 997 and prefer not to receive them. To turn off the 997 auto-transmit flag, follow the steps below. 1. From the AutoMap main menu choose option 5, Map Maintenance and press Enter. 2. From the Map Maintenance screen Press F7 (Job Controls). 3. From the Maintain Job Controls screen, select *SYSTEM with 1 and press Enter. 4. From the System Controls screen press F15 (Archive by Trading Partner). 5. In the System Controls window, change the Auto Transmit 997 flag from Y to N. 6. Press Enter. Remove Company and Network Combinations When ACM is not enabled, each transaction set must be associated with a VAN and an AutoRelease company number in map maintenance. During the initial installation of a map, all company number and network combinations found on your system are entered into map maintenance by the system. The user may delete all that are not used. To delete a keyword: 1. Select map maintenance 2. Select the trading partner with 1 3. Select the transaction set with 1 4. Remove company/network combinations that are not needed. (The first 5 are displayed on the Transaction Maintenance Screen. The rest may be accessed with F4=Prompt.) 5/

12 How to Use This Document How to Use This Document This document provides information regarding unique instructions required to implement this trading partner's unique business practices. There is a separate document called "AutoMap Manual" which describes those procedures which apply to all trading partners (NOT unique for each trading partner) such as the daily procedures, job controls, etc. General Information The general information section of this document describes transaction sets, how they apply to this trading partner and other miscellaneous information. Security The security section of the document explains the network(s) used by this trading partner, and specific information about how to create the trading partner cross reference file. Implementation Requirements received via AutoMap are processed into the AutoRelease master files to perform shipping, ASN and invoicing functions. Therefore, enter all master files in the same manner as required when processing data from the AutoRelease menus. Exception: Special AutoMap processing needs are handled via keywords in AutoMap. Therefore, clear flags and special processing flags (F20) should not be marked. The entry of each master file is NOT explained in this supplement. Only those that require specific fields marked to accommodate specific business practices for this trading partner are noted. The master files required during the process from the AutoMap Requirement Display, are the same files that are required when processing from the VL0 menus: Machine Readable - customer and destination Parts Cross Reference Requirement Master These files must be entered to successfully process data into the requirement and load files. 5/

13 How to Use This Document ASNs All AutoMap trading partners transmit ASNs to the trading partner by using option 3 (ASNs) from the AutoMap menu. The ASN section of each trading partner document describes the ASN cancellation procedure and mandatory ASN fields for a specific trading partner. A complete description of the common options can be found in the ASN section of the AutoMap manual. AutoMap Features and Preferences In AutoMap, keywords are unique for the business practices of the trading partner. This section describes how to access keywords, whether there are optional or conditional keywords for this trading partner, and how to activate and deactivate keywords. All maps are created to automatically transmit a 997 to the trading partner upon receipt of a file. Some trading partners do not require a 997 and prefer not to receive them. Procedures to turn the "Auto Transmit 997 Flag" on or off are described. Each transaction set must be associated with a VAN and an AutoRelease company number in map maintenance. During the initial installation of a map, all company and network combinations, found on your system, are entered into map maintenance by the system. How to remove the company/network combinations that are not used is explained in this section. How to add new company/network combinations is explained in this section. 5/