Paccar - Infordiscrete.support.infor.com/dynaList/ar_sw9/TPdocs/OEMsup/arOEMSup... · Paccar...

INFOR

TABLE OF CONTENTS

Paccar(PA)

Traditional

General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Transaction Sets and Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Special Print Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Shipping - KANBAN Number and Build Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Electronic Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Business Practice Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Price Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Communication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Identification Code File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

997 Record (Trading Partnership Record Required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Trading Partnership File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Steps to Create Default Values:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Initial Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11SUPPID 997 Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Required Changes for 810 and 856 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Required Changes for 855 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Required Changes for the SUPPID 997 Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Required Changes for 832 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Required Changes for 141 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

7/2009 1

AutoRelease: Paccar

Required Changes for 810 and 856 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Required Changes for 855 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Required Changes for the SUPPID 997 Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Changes for Testing Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Machine Readable - Customer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Machine Readable - Destination File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Parts Cross Reference File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16OEM Miscellaneous Information FIle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Model Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18CUM Required Prior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Requirement Master File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Requirement File - Clear Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Paccar/Peterbilt 862 - Load Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19File Archiving / Auto Print and Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Miscellaneous Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Paccar Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Destination File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Matching Shipper and Invoice Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Separate Shipper and Invoice Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Mexican Shipments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

VL0 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Print Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Shift Exception - 862 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25830 Special Processing - Application Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Special Processing - Duplicate VINs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Special Processing - Multiple Release Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Special Processing - KANBAN Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Special Processing - Purchase Order Line Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

VL44 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Application Advice Menu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

VL38 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Receiving Advice Menu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

VL35 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29P.O. Acknowledgement (History) Menu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

VL36 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Remittance Advice Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Menu Pictorial Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

VL55 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Text Message Menu (864) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

7/2009 2

AutoRelease: Paccar

VL7 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Price Catalog Menu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Using the Price Catalog Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Create Price Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Maintain Price Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Price Catalog List / Verification (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Create and Transmit Price Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Price Catalog Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Create Price Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Catalog ID Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Maintain Price Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Catalog Header Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Detail Maintenance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Other Charges Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

VL73 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Product Service Claim Menu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Maintain Product Service Claim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Header Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45F2 - Maintain Claim Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46F4 - Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Claim Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Print Product Service Claims . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Create and Transmit Product Service Claims. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Purge Product Service Claim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Reactivate Product Service Claim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

ASNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Maintain ASNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

ASN Maintenance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Electronic Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Maintain Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Invoice Header Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Line Item Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Miscellaneous Charge Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

File Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Destination Master File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Machine Readable File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

How to Use This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

7/2009 3

AutoRelease: Paccar

VL0 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66ASNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Electronic Invoice Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

7/2009 4

AutoRelease: Paccar General Information

General Information

Transaction Sets and VersionsThe Paccar module supports the following transaction sets:

• 141 Product Service Claim Response Version 4010• 142 Product Service Claim Version 4010• 810 Electronic Invoice Version 4010• 820 Remittance Advice Version 4010• 824 Application Advice Version 4010• 830 Material Release Version 4010• 832 Price Catalog Version 4010• 850 Purchase Order Version 4010• 855 Purchase Order Acknowledgment Version 4010• 856 ASN Version 4010• 861 Receiving Advice Version 3050• 862 Shipping Schedule Version 4010• 864 Text Message Version 4010• 997 Functional Acknowledgement Version 3060

The 141 (Product Service Claim Response) is transmitted to Paccar to accept, adjust, deny, or suspend a warranty claim.

The 142 (Product Service Claim) contains warranty claim information.

The 810 (Electronic Invoice) is required to be transmitted to Paccar when required.

The 820 (Remittance Advice) is issued indicating a payment amount and the supporting invoice data such as the invoice numbers, part numbers, quantities, purchase order numbers, etc.

The 824 (Application Advice) reports errors of content in the file received from Paccar.

The 830 (Material Release) contains planning requirements and is NOT shipped against.

The 832 (Price Catalog) is transmitted to Paccar when required.

The 850 (Purchase Order) contains requirements received from the Paccar Parts Division.

The 855 (Purchase Order Acknowledgement) is used to acknowledge the receipt of the 850 and to accept it with or without changes.

7/2009 5


The 856 (ASN) is required to be transmitted for each shipment when the truck leaves the plant.

The 861 (Receiving Advice) reports discrepancies of the ASN and the actual shipment.

The 862 (Shipping Schedule) contains firm ship requirements.

The 864 (Text Message) is text transmitted to the supplier from Paccar.

The 997 Functional Acknowledgement is required to be transmitted to acknowledge the received requirements, within the time frame defined by Paccar. A 997 is also received to acknowledge the transmitted 856.

Special Print RequirementsWhen multiple part numbers are shipped in the same container on one shipper, the total number of containers is required on the first line item. All other line items using this container will have a container quantity of “0.”

Paccar 866s - Multiple line items for the same part number with the same purchase order number are combined. Individual RANs and VINs are listed following the line item on both shippers and invoices.

RAN / KANBAN Print - When a file is received without the REF*DP segment a summary line with the RAN/KANBAN range is printed on shippers and invoices. When the REF*DP segment is received the KANBAN numbers are printed.

Shipping - KANBAN Number and Build StationKANBAN Number - The KANBAN number (received on the 862) is processed into the RAN field and can be viewed at shipper entry.

Build Station - The build station is received and stored, but it cannot be viewed. It prints on the bar code labels. The Load Sheet may be sorted by build station. Paccar requires only one build station per pallet.

Electronic InvoicesThe "invoice create" option accumulates multiple line items with the same:

• Purchase Order Number

• Release Price

• Unit of Measure

• Customer Part Number

One IT1 segment is created for these line items.

7/2009 6


Business Practice NotesPaccar emergency orders are handled via telephone or fax. Returnable containers are transmitted as separate line items on the ASN for KANBAN requirements only. Suppliers are paid from the paper invoice.

Price CatalogsWhen entering Parts price catalogs, users must enter a destination abbreviation on the Maintain Price Master File screen. To access this screen, choose option 6, File Maintenance Menu, from the AutoRelease main menu and then choose option 10, Price.

7/2009 7

AutoRelease: Paccar Security

Security

Communication MethodPaccar uses the GEIS or Advantis network.

The Trading Partnership file can be changed to interconnect with other networks.

Identify the network being used with the option "Maintain Network Selection" and enter security requirements (identification codes, passwords, etc.) before attempting to receive or transmit. Network security for each network is entered one time, but may be accessed by multiple trading partners. Network security may be accessed from an AutoRelease VL0 menu or from within AutoMap (Map Maintenance). Requirements can be received from the network, from any OEM "receive" menu that uses the same network or, if a mapped trading partner, from the AutoMap mailbox monitor. All OEMs received from the same network are received at one time regardless of which "receive" option is used.

GEIS Network Implementation Note: When establishing a trading partnership with the GEIS network, the following data is required in your User Profile:

Wrap Data? YES-80Start New Record on New Interchange? YES

7/2009 8

AutoRelease: Paccar Implementation

Implementation

Identification Code FileThe Identification Code file is used when taking the options to Split and Breakdown a file received from Paccar, and when transmitting ASNs and electronic invoices. The Identification Code file is used differently by different manufacturers.

Initial Record (Trading Partnership Record REQUIRED)

Company Number - xxOEM Code - PAPlant ID - Supplier CodeOEM ID - Paccar's DUNS Number (137361242)Corporate ID - Your DUNS NumberRemit to Duns Number - Not used by PaccarVAT Code - Tax IDTransmission Mode - PSmart Labels - NPallet Staging - NBar Code File Transfer - NVariable Unwrap Print - Y or NAutomatic Print of 997 - Y or NAutoMap - N

The corporate ID field contains your DUNS number to be returned as the sender ID in the electronic invoice file in the ISA 06 segment.

Errors that occur during the Split that indicate a code is missing from the identification code file are referring to OEM ID.

Errors that occur during the Breakdown that indicate a code is missing from the identification code file are referring to plant ID or corporate ID.

7/2009 9


997 Record (Trading Partnership Record Required)Paccar requires consecutive ISA and GS control numbers in the EDI enveloping. To accomplish this a second identification file record must be entered with SUPPID 997 as the plant ID. Without this record, the control number is created based on date and time.

Company Number - xxOEM Code - PAPlant ID - SUPPID 997OEM ID - Not used by PaccarCorporate ID - Not used by PaccarRemit to Duns Number - Not used by PaccarVAT Code - Tax IDTransmission Mode - PSmart Labels - Y or NPallet Staging - NBar Code File Transfer - NVariable Unwrap Print - Y or NAutomatic print of 997 - Y or NAutoMap - N

Trading Partnership FileMachine readable records must be entered before the trading partnership records can be created, because destinations are validated.

The Trading Partnership file is used to enter data to be used in the "enveloping" of the electronic file being transmitted instead of using the identification code file and the hard-coding within the programs. When a trading partner changes their enveloping, the change may be made, by the user, in the Trading Partnership file, instead of waiting for a program change.

Press F14 (Trading Partnership File) after entering the appropriate data in the identification code file.

Steps to Create Default Values:1. Press F6 (Add) from the ISA List Screen.

2. Abbreviations may be entered. Paccar requires a separate record for each destination. The first record created is a template and is copied and modified to create each required record; and is then deleted. Therefore, it is recommended to leave the customer and destination records blank at this time.

3. Press Enter.

4. Enter the code representing the data format (A for ISA). Press Enter. The ISA Detail Screen displays.

5. Press F7 (Infor defaults).

7/2009 10


Initial RecordFive ISA records are created:

• One GS record is created (810) for the Production Invoice ISA record.

• One GS record is created (855) for the Production PO ACKN ISA record (for Parts & Service only).

• One GS record is created (856) for the Production ASN ISA record.

• One GS record is created (832) for the Production Price ISA record.

• One GS record is created (141) for the Production Service Claim ISA record.

One Communication record is created for each ISA (GEIS).

Press Enter or F12 (Return) to display the ISA List Screen to access the three ISA records.

The five ISA records created for Paccar are intended to be used to create individual records for each destination. The Production Invoice record is the template to create 810 records for each ship-to destination. The Production PO ACKN record is the template to create 855 records for each Parts and Service ship-to destination. The Production ASN record is the template to create 856 records for each ship-to destination. The Production Price catalog record is the template to create 832 records for each ship-to destination. The Production Service Claim record is the template to create 141 records for each ship-to destination.

Modifications are needed to the ISA and GS records. No modifications are needed for the communication record.

SUPPID 997 Record• One ISA record is created.

• One GS record is created (997).

• No communication record is created.

The ISA defaults are displayed for the Functional Acknowledgement. No modifications are needed to the ISA record or the GS record. The default for the Processing Option on the GS Detail Screen is P.

No communication record is need; outbound communications use the same enveloping as inbound communications.

Steps 6-14 must be repeated for each transaction set and destination combination.

6. Each template record must be copied and modified for each Paccar destination and transaction set. Enter “3” next to the template record to copy.

7. Press Enter.

8. Enter the customer (optional) and destination (required) abbreviations.

9. Press Enter.

10. Select the copied record with “1.”

7/2009 11


11. Press Enter. The ISA Detail Screen displays.

ISA Detail Screen

Required Changes for 810 and 856 RecordsUser Defined Description - Enter the name of the destination plant

Sender Information - Enter your DUNS number. This name is strictly for reference.

Required Changes for 855 RecordsUser Defined Description - Enter the name of the destination plant.

Sender Information - Enter your DUNS number or communication ID.

Receiver Information - Enter Paccar Parts & Service DUNS number (137361242).

Maintain Trading Partnership File

Company Number.......... 01 (A)ISA/(C)ICS/(E)EDIFACT: AOEM Code................ PASupplier ID............. 1234567899Customer Abbrv(O)....... PACCARDestination Abbrv(O).... PACDST

User Define Description: _____________________________

Qualifier/InformationAuthorization: 00 __________ Active (Y)/(N): YSecurity: 00 __________Sender: 01 123456789Receiver: 01 137361242 Hexadecimal CodeControl Standards ID: U Sub Element Separator: 6EVersion Identifier: 00200 Data Element Separator: 5C Segment Terminator: 0DComputer Generated ISA Control Number: _

F7=Update Infor Defaults F8=OEM Commun. F10=GS Level

7/2009 12


Required Changes for the SUPPID 997 RecordSender ID - Leave blank. The system creates the sender ID from the

incoming receiver ID.

Receiver ID - Leave blank. The system creates the receiver ID from theincoming sender ID.

Required Changes for 832 RecordsSender ID - Enter the corporate ID (your DUNS number)

12. Press F10 (GS Level). The GS List Screen displays. There is one GS record for each of the ISA records (141, 810, 855, 856, 832).

13. Select each transaction set record with “1” (one at a time) to display the GS Detail Screen with the default data.

14. Press Enter.

GS Detail Screen

Maintain Functional Identifier

Company Number.......... 13OEM Code................ PASupplier ID............. 123456Customer Abbrv(O).......Destination Abbrv(O)....Transaction Type........ 810

Non Repeating TransactionFunctional Identifier: IN Control Number: _Application Sender: 123456___________Application Receiver: 137361242________ ST Control#: _________Responsible Agency Code: X_Version/Release/Industry: 004010_____(T)est/(P)roduction: PAcknowledge Requested: N

Last Date Used: 0/00/00Last Time Used:Number Times Used: Processing Option: _Computer Generated Group Control Number: _ P=Print Before Sending

F12=Return

7/2009 13


Processing Option - The default is blank; an unwrapped file is not to be viewed before the transmission. (Optional).

Or

Change to “P” to activate an unwrapped file to be viewed before the transmission.

Required Changes for 141 RecordsApplication Sender - Enter your supplier code.

Application Receiver - Enter the destination DUNS number.

Required Changes for 810 and 856 RecordsApplication Sender - Enter your DUNS number

Application Receiver - Enter the destination's DUNS number

Required Changes for 855 RecordsApplication Sender - Enter your supplier code

Application Receiver - Enter Paccar Parts & Service DUNS number (097248199)

Required Changes for the SUPPID 997 RecordSender ID - Leave blank. The system creates the sender ID from the

incoming receiver ID.

Receiver ID - Leave blank. The system creates the receiver ID from the incoming sender ID.

Changes for Testing OnlyTest/Production - The default is P. When transmitting a production ASN file,

PRIN010 is placed in the ISA08 and the GS03 segments. Change to T when transmitting a test ASN file, PRIN070 is placed in the ISA08 and the GS03 segments.

Press Enter. Press F12 twice to return to the ISA List Screen.

Repeat steps 5-6 for every Paccar ship-to destination and for each transaction set.

When completed, delete the templates (the records with no destination abbreviations).

7/2009 14


Press Enter to return to the GS List Screen.

Press F12 twice to return to the ISA List Screen.

Set-up is complete.

Machine Readable - Customer FilePaccar is the parent company for Peterbilt and Kenworth. Requirements received from Peterbilt and Kenworth via Paccar, are associated with a separate OEM identification number and therefore, require separate customer abbreviations in the Machine Readable file.

The parts must be entered in the parts cross reference file using the appropriate customer abbreviation and the appropriate customer part number. Each company (Paccar, Peterbilt and Kenworth) defines their own, unique, customer part number.

The Machine Readable file must be entered before the Trading Partnership file (accessed from the Identification Code file) can be created.

Destinations and DUNS numbers for Paccar:

• Peterbilt: Denton 096445069Nashville 048120083

• Kenworth: Chillocothe 065986200Seattle KW 009249509Ste. Therese KW 241771534Renton KW 793330598

7/2009 15


Machine Readable - Destination File

OEM Consideration Flag - Enter “Y” in this field if this Paccar destination requires multipleparts cross reference records per engineering revision level. Thisflag is checked during the requirement "print". A space followedby the engineering revision level is appended to the customer part number. This part is now recognized by both the customerpart number and the engineering revision level from processingthrough to ASNs. This flag is checked again during the "ASNCreate" and the engineering revision level is removed to transmitthe customer part number back to Paccar in the ASN file.

Parts Cross Reference FilePaccar may require multiple parts cross reference records per engineering revision level. The Paccar customer part number with each engineering revision level must be entered in the parts cross reference file. (There may be as many records as there are engineering revision levels). The Customer Part Number field must contain the customer part number as transmitted by Paccar followed by a space and the engineering revision level.

DESTINATION ABBREVIATION RECORD

Company Number .............. xxOEM Code .................... PAIdentification Number ....... xxxxxxDock Location ............... __________

Destination Abbreviation .... xxxxDestination Description ..... _______________P O Destination ............. _________ERS Destination ............. _ (Y/N)OEM Consideration ........... Y (Y/N)Electronic Invoices ......... _ (Y/N)Line Set .................... _ (Y/N)Clear By Destination ........ _ (Y/N)Type of FBO ................. _ (M/S)

7/2009 16


Note: The OEM considerations flag in the machine readable destination file must contain “Y” to add the engineering revision level to the 30th position of the customer part number transmitted by Paccar so this part's cross reference record is recognized.

In the Customer part number field enter: xx-xxxxx y, where “xx-xxxxx” represents the customer part number as transmitted by Paccar and “y” Represents the engineering revision level.

OEM Miscellaneous Information FIlePaccar sends replacements by Purchase Order and Schedule Number that process into the REQTIM field. Therefore, in the OEM Miscellaneous Information file, enter “862” in the Clear Transaction Set including Purchase Order field. Only requirements with the same Purchase Order number and Schedule Number are cleared. Access the OEM Miscellaneous Information file through option 13, OEM Miscellaneous Info, on the File Maintenance main menu.

PART CROSS REFERENCE MAINTENANCE

GENERAL FORMAT

Company ..................... xxCustomer Abbreviation ....... xxxxxxCustomer Part Number ........ xx-xxxxx yDestination Abbreviation .... ______ (O)

Bar Code Part Number ...... ______________________________Internal Part Number ...... xxxxxx

OEM MISCELLANEOUS INFORMATION MAINTENANCE Company Number ....... VK OEM Code ............. PA Destination Abbrev ... Model Year ............... Clear 830s w/ Purpose Codes GM Message File .......... Clear 862s w/ Purpose Codes GS ASN/UNH DESADV Ver Lvl. Combine Daily 866s ........ (Y/N) Next Avail Adjust # ...... Caterpillar Facility Code . Use DUNS in ISA/UNB Seg... N (Y/N) Caterpillar Proprietary ID GM DESADV Packaging Info.. (Y/N) Caterpillar 830 10-10-10... (Y/N) Appl Receiver ID .... IBM Supplier Code.......... Clear Transaction Set including GM Invoice Message File... Purchase Order.... 862 GM Invoice Location Code.. Process EDI Dock........... (Y/N) GM Duns in ISA/UNB Seg.... (Y/N) Direct Supply Contract #... GS/UNH Invoice Ver. Lvl... F1=Help F10=Delete F12=Return

7/2009 17


Model YearPaccar does not send model year. Therefore, the requirement and price files must be entered leaving the model year field blank.

CUM Required PriorPaccar does not send CUM required prior so it must be entered manually before going live so the system can include ahead or behind figures in the package quantity. The CUM required prior is entered using the option Enter Manual Requirements. CUM required prior can be entered using F5 from the Entry Screen or it may be entered directly on the Header Screen.

Requirement Master FileThe Customer Part Number field must contain the customer part number as transmitted by Paccar followed by a space and the engineering revision level.

JTDMAINT2 REQUIREMENT MASTER ENTRY CHANGE Company 10 Customer PACCAR Part D5701299 Destination CHLCTH MY Customer Part # .... L29-1053-100 A OEM Code ....... PA Supplier Code ...... 20480AA OEM Division ... Customer # ......... 101160 Destination # ...... 163 Commodity Code ..... AUTO Unit of Measure .... EA Controlling Source . Price Code ......... E Dock Code .......... Trailer Capacity ... Container Part # ... D5701 Package Quantity ... 9 _________ MRP _________ _______ Reports _______ ________ Clear ________ 866 862 830 850 866 862 830 850 866 862 830 X 850 Process P.O.s Planner # ........ 0000 Balance Out Code ... Product Code . Weekly Ship Code . Final Release Code . Analyst # .... Rack ID .......... User #1 .. User #2 .. User #3 .. .00000 Remarks .. F1=Help F7=OEM Info F8=REQB F9=REQC F10=Delete F11=File Maint F12=Return F19=Fab/Mtl F20=Special Process

7/2009 18


Requirement File - Clear FlagsPaccar sends complete 830 files. Therefore, clear flags must be marked for the 830 transaction sets:

866 862 830 850 _ _ X _

This entry is subject to change based on the files Paccar transmits to your company. Do not mark the clear flags for 862s.

Note: Do not select clear flags with X if requirements are transmitted only once for any given transaction set.

Paccar/Peterbilt 862 - Load SheetAn 866 load sheet can be printed for Paccar/Peterbilt 862 Line Sequence requirements. On the Summary Load Sheet selection enter the Paccar OEM code (PA), select summary load sheet, use F7 (sort order) and select 866 Load Sheet.

File Archiving / Auto Print and Process(Option 10 on the VL0 menu)

When ACM is not enabled, this option is used to store miscellaneous data that is needed if using file archiving (accessed from the Requirement Processing Menu) and if using auto receive.

Miscellaneous Screen

No. of days to Archive - Enter the number of days to archive files received from Paccar.Files must be saved at least one day. Archived files are files that are stored for a given number of days. The number ofdays is NOT based on calendar days. Only the number of dayswhen a communication session takes place is counted. Then thearchived files are removed during the next shift.

PACCAR MISCELLANEOUS INFORMATION

Company 01

File Archiving / Auto ProcessNumber of days to archive .. ___Auto Print (Y/N)?........... _Auto Process (Y/N).......... _

F3=Exit F10=Delete

7/2009 19


Auto Print (Y/N)? - Enter “Y” if using auto receive and Breakdown (scheduled through file maintenance from the Communications menu), toperform an automatic print after the Breakdown. Enter “N” if not using auto receive, or, if using auto receive and Breakdown, if theprint option is not to be run automatically after the Breakdown.

Auto Process (Y/N) - Enter “Y” if using auto receive and Breakdown (scheduledthrough file maintenance from the Communications menu), and ifalso using auto print, to perform an automatic process after theReceive, Breakdown and Print.

Note: Only error free requirements are processed. Errors mustbe corrected and the "print" and "process" options must be takenmanually to process the remaining data.

Enter “N” if not using auto receive, or, if using auto receive, Breakdown and auto print, if the process option is not to be runautomatically after the print.

7/2009 20


Paccar ServiceDestination FilePaccar Parts and Service requires the Supplier Type field to filled in.

Enter an 'S' in the Supplier Type field for Paccar Parts and Service destinations.

SCD6300B MAINTAIN DESTINATION MASTER FILE Company Number ............ XX TEST COMPANY Destination Number ........ 2441 Name 1 ..... FOB ............... Name 2 ..... Distributor Code .. Address 1 .. Ford Dest Code ......... Address 2 .. ASN/DESADV (B/C/N/O/V/Y) Address 3 .. GM Msg/Temp Msg Code ... / City/State . GM Std Loc/Ford Rt Cd 2. Zip Code ... Carrier Preference ..... Country .... Route Code / HMRS (Y/N). Honda Destination ...... Arrival/Ship Dates (A/S) ..... Supplier Type (P/S) .... S Delivery Travel Time (Hrs/Min) ASN Unit of Measure .... Delivery Travel Time (Days) .. JIT Location (Y/N) ..... Bar Code Verif (Y/N/C/S) Available Ship Days (X = Select) Print Invoices (Y/N) ... S M T W H F S Create Invoices (Y/N) .. Payment Type: Coll PP PPI Oth Names: Alt. Description... Dealer Code ....... F1=Help F10=Delete F12=Return Cat Europe Ult Dest ..

7/2009 21


Paccar service may require one invoice per purchase order number.

Enter “Y” if a separate invoice is required for each purchase order.

Matching Shipper and Invoice NumbersWhen more than one purchase order number is associated with one shipper, the first invoice number will match the shipper number; invoices for subsequent purchase orders use the next invoice number, based on the next shipper number in the forms control file. This results in unassigned shipper numbers. All line items with NO purchase order number are grouped together and assigned one invoice number.

Warning: Invoice numbers are not reassigned, if the purchase order number is changed after the extract.

When reprinting invoices from history, only the last invoice is available to print.

Separate Shipper and Invoice NumbersEach invoice number is assigned based on the next invoice number in the forms control file. There may be a single shipper with multiple invoices associated with it.

MAINTAIN DESTINATION MASTER FILE

Print Remarks (Y/N): _ Shipper _ Invoice _ Acknowledgement

Remark: _______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ASN Transmit Windows: Before Hours: __ Mins.: __ After Hours: __ Mins.: __

Multi-Company Pool Bill Destination? (Y/N): _Print Part Description on Invoices (Y/N): _Travel Time: Set Prior to Current Date? (Y/N)...: _ Set Holiday to Next Ship Day? (Y/N): _Remove no-charge returnable containers from invoice? (Y/N) _Funds Type ....... ___ Funds Type Description ... _________Tax Exempt ....... ____________________ One P.O. Per Invoice (Y/N) YF1=Help F12=Return

7/2009 22


Mexican ShipmentsWhen shipping to Paccar Parts Mexico, the “MXTAXID” application control record is required to print the Tax ID Number on customs invoices. Add the application control record as shown below. For more information on adding control records, see Chapter 11 of the AutoRelease main manual.

Company: Company CodeApplication Name: *ALLKeyword: MXTAXIDLength: 15Decimal: BlankInfor Data: Enter the Tax ID Number

7/2009 23

AutoRelease: Paccar VL0 Menu

VL0 Menu

Many options are identical from trading partner to trading partner. Those options are explained once in the AutoRelease manual. Only options unique to this trading partner, exceptions or unique business practices are explained in this document, as described in the chart on the next page.

Print MethodPrint Method: Mandatory

Paccar is coded to use the mandatory "print" method, which affects the Breakdown, Print and Process options.

The Requirement Edit List prints the detail requirements in line sequence order rather than requirement date order.

PACCAR EDIMENU: VL0PA

----------------------------------------------------PACCAR

VARIABLE LENGTH TELECOMMUNICATIONS MENU----------------------------------------------------

1. Receive Data 11. Application Advice Menu (824)2. Split Network Data into OEM files 12. Receiving Advice Menu (861)3. Breakdown Variable Data 13. P.O. History Menu (850)4. Print Requirements (830,850,862) 14. Remittance Advice Menu (820)5. Print Functional Acknowledgment (997) 15. Acknowledge Received Data6. Process Requirements (830,850,862) 16. Text Message Menu (864)7. Maintain Network Security 17. Price Catalog Menu (832)8. Maintain Network Selection 18. Product Service Claim (142)9. GEISCO Miscellaneous Menu10. Maintain Miscellaneous File

23. Return to V/L Telecommunications Menu24. Return to Main Menu

Option __

7/2009 24


Shift Exception - 862 RequirementsPaccar 862 requirements are not removed during the "shift". These requirements are removed during the "ASN Extract." Also during the "extract", the CUM shipped is forced into the 862 CUM required prior so they are equal. This also occurs when a shipping adjustment is made. If the requirement is not shipped complete, the "net" requirement in the load file is adjusted by the quantity shipped.

830 Special Processing - Application Control FilePaccar sends a full file every Monday with a frequency of D. The current week's requirements are not included in the file. Clear flags are marked, so the current week's requirements would be removed when the new file is processed, without the following application control records.

The application control records are used to change the 830 frequency of the current week's requirements from D (daily) to W (weekly) to retain them. Both application control records must be entered. The application control file is accessed from the System Maintenance Menu (RC20).

Application Name: *ALLKeyword: SAVCURRQLength: 1Decimal: BlankInfor Data: Enter “Y” to retain the current week's requirements. Enter “N” to remove the current

week's requirements.

Application Name: *ALLKeyword: CHGFRQPALength: 1Decimal: BlankInfor Data: Enter “Y” to change the 830 frequency from D (daily) to W (weekly) during the

process. Enter “N” to retain the 830 frequency of D (daily) instead of changing to W(weekly) during the process.

Special Processing - Duplicate VINs Paccar's VIN is a Month/Day/Truck sequence number. Shipping History is checked during the "process" for duplicate VINs (Vehicle Identification Numbers). Requirements with VINs already shipped in the last 10 months are deleted. Deleted requirements are listed on the Removed Requirements Edit List report that prints during the "process". VINs are repeated from year to year. They are not considered to be duplicates if the requirement dates are 10 months or more apart.

7/2009 25


Special Processing - Multiple Release NumbersPaccar transmits multiple release numbers in the FST segment that may differ from the release number received in the BSS segment. The Paccar "process" does NOT consider release number, so all valid release numbers are processed.

Special Processing - KANBAN Number When requirements are received with KANBAN numbers, shipping history is checked. If the KANBAN number exists in shipping history, the requirement is not processed. Requirements not processed are listed on the requirements removed report that is printed at Breakdown time.

Special Processing - Purchase Order Line Number Note that because the PO Line Number for 850 transactions is 11 digits long and the PO Line Number field in the JITB (detail) record is only five digits long, the PO Line Number is placed in the VIN Number field in the record and appears on the Requirement Edit List report under the VIN Number heading. The PO Line Number also displays on the ASN Maintenance screen as the Job Sequence Number.

7/2009 26


VL44 Menu

Application Advice Menu Overview(Option 11 on the VL0 Menu)

This option displays, prints and purges the Application Advice (824) file received from Paccar. When this data is no longer current, it may be purged.

Paccar transmits an 824 for both 810s and 856s.

The Application Advice reports errors of content in the file received from the supplier. The functional acknowledgement indicates that the file was, in fact, received and that it was syntactically correct. The Application Advice takes the checking procedure a step further and reports if specific content errors were found. The Application Advice may state that the transmission was accepted with errors or that the transmission was rejected.

The Transaction Sets Received Audit Report, which is printed during the Breakdown, identifies the transaction sets received by each company.

During the Breakdown, all data received in the 824 file is placed in the universal Application Advice files VPX824A - VPX824H.

MENU: VL44PA---------------------------------------------------------

PACCARAPPLICATION ADVICE

---------------------------------------------------------

1. Display Application Advice2. List Application Advice3. Purge Application Advice

23. Return to V/L Communications Menu24. Return to Main Menu

Option __

7/2009 27


VL38 Menu

Receiving Advice Menu Overview(Option 12 on the VL0 menu)

This Receiving Advice menu (VL38PA) is used to display, print, and purge the Receiving Advice (861) file received from Paccar. The 861 is a discrepancy report providing information to notify the supplier when the ASN data is not the same as the data recorded by Paccar when the shipment is actually received. Discrepancies are not processed into the requirement or load files. Adjustments must be made manually (when necessary) from the Manual Requirement/Shipping Adjustments Menu (RC8). When this data is no longer current, it may be purged.

The Transaction Sets Received Audit Report, which is printed in the Breakdown, identifies the transaction sets received by each company.

During the "process," all data received in the 861 file is placed in the universal Receiving Advice files VPX861A - VPX861H.

MENU: VL38PA---------------------------------------------------------

PACCARRECEIVING ADVICE MENU

---------------------------------------------------------

1. Display Receiving Advice2. List Receiving Advice3. Purge Receiving Advice


Option __

7/2009 28


VL35 Menu

P.O. Acknowledgement (History) Menu Overview(Option 13 on the VL0 menu)

The Paccar P. O. Acknowledgement Menu is used to inquire into the 850 file received from Paccar. An 850 record can be selected to be maintained to create a purchase order acknowledgement (855) to be transmitted to Paccar. This is the same data from the 850 Edit List that is placed on hold during the "print" from the Paccar VL0PA menu.

During the "process," all data received in the 850 file is placed in the universal files VPX855A - VPX855Y.

The Paccar 850 represents requirements received from the Paccar Parts Division. These requirements are processed into the requirement and load files. (The "Process PO" field in the requirement A record must be marked to process into the requirement file and the report flag must be marked to process into the load file).

When the "Create/Transmit P.O. Acknowledgements" option is taken, the 855 is created. When 855s are purged, the 850 is removed from this work file and no longer displays on the maintenance screen. This does not affect the requirement or load files.

MENU: VL35PA----------------------------------------------------

PACCARP.O. ACKNOWLEDGEMENT MENU

----------------------------------------------------

1. Maintain Purchase Orders2. List Purchase Orders3. Create/Transmit P.O. Acknowledgements4. Reactivate P.O. Acknowledgements5. Purge P.O. Acknowledgements


Option __

7/2009 29


VL36 Menu

Remittance Advice Overview(Option 14 on the Vl0 menu)

The Remittance Advice menu (VL36PA) is used to display, print and purge the Remittance Advice (820) file received from Paccar. The 820 is issued when a check is issued indicating the payment amount and the invoice data supporting the payment, such as the invoice numbers, part numbers, quantities, purchase order numbers, etc. When this data is no longer current, it may be purged. The Transaction Sets Received Audit Report, which is printed during the Breakdown, identifies the transaction sets received by each company. During the Breakdown, all data received in the 820 is placed in the universal remittance advice files VPX820A - VPX820L.

MENU: VL36PA----------------------------------------------------

PACCARREMITTANCE ADVICE MENU

----------------------------------------------------

1. Display Remittance Advice2. List Remittance Advice3. Purge Remittance Advice


Option __

7/2009 30


Menu Pictorial Overview

Selection Screen

1=Select 6=Detail Print 8=Summary Print

Header Screen

F5=Dates F6=Names Enter=Detail

Line Item Screen

1=Select

RMR Header Screen

F7=Item Data

Enter 1

Enter

Enter 1 (Type = RMR)

7/2009 31


VL55 Menu

Text Message Menu (864) Overview(Option 16 on the VL0 menu)

This option is used to display, list and purge the Paccar Text (864).

The Transaction Sets Received Audit Report, which is printed during the Breakdown, identifies the transaction sets received by each company.

During the Breakdown, all data received in the 864 file is placed in universal text message files: VPH864A - VPH864F.

MENU: VL55PA----------------------------------------------------

PACCARTEXT MESSAGE MENU

----------------------------------------------------

1. Display Text Messages2. List Text Messages3. Purge Text Messages


Option __

7/2009 32


VL7 Menu

Price Catalog Menu Overview(Option 17 on the VL0 menu)

Traditionally coded trading partners use the price catalog menu (VL7) to create, maintain, display, print, purge and reactivate the price catalog (832) for Paccar.

Many menu options are identical from trading partner to trading partner. Those options are explained in the appropriate chapter of the AutoRelease manual. Only options and features unique to this trading partner, exceptions or unique business practices are explained in this document.

Data sent in 832 files is stored in files named VPX832A - VPX832C.

Paccar requires the supplier to use the 832 to convey pricing information to Paccar. It is the supplier's responsibility to transmit price catalog information when there is a price change, or when required by Paccar.

Three ship-to locations are affected by this practice:

• Kenworth DUNS Number 091741934

• PeterBuilt DUNS Number 009120734

• Paccar Corporate DUNS Number 048341267

MENU: VL7----------------------------------------------------

PACCARPRICE CATALOG MENU

----------------------------------------------------

1. Create Price Catalog2. Maintain Price Catalog3. Price Catalog List / Verification4. Create and Transmit Price Catalog5. Purge Price Catalog6. Reactivate Price Catalog


Option __

7/2009 33


Using the Price Catalog Menu OptionsCreate Price Catalog

1. Create the Price Catalog file using option 1.

2. Verify or change Catalog ID information.

3. Press Enter.

4. Enter selection criteria to retrieve data from master files.

5. Select the parts to be included in this Catalog.

6. Press F10 (Build Catalog). Data is retrieved from master files.

Maintain Price Catalog1. Add or maintain Price Catalog information using option 2.

2. Select a Price Catalog from a list of all Price Catalogs.

3. The Header, Catalog Detail List and Detail Maintenance screens are used to manually update and add fields.

Price Catalog List / Verification (Optional)1. To verify the catalog before transmitting it take option 3.

2. Enter the catalog number and version number.

3. Press Enter.

Or

1. Press F4 to display a list of catalogs and select one.

2. Press Enter. A report prints listing terminal and warning errors. Terminal errors must be corrected using option 2 before transmitting.

Create and Transmit Price Catalog1. To transmit a catalog to Paccar take option 4.

2. Enter the catalog number and version number.

3. Press Enter.

Or

1. Press F4 to display a list of catalogs and select one.

2. Press Enter.

3. Before the catalog is transmitted it is verified by the system and a report prints. If errors were found correct the errors using option 2 (Maintain Price Catalog).

4. After errors are corrected take the transmit option again to complete the transmission.

7/2009 34


Price Catalog Flow

Create Price Catalog

Maintain Price Catalog

Price CatalogList / Verification

Create a new catalog or add to an existing one. (Data is retrieved from master files.)

Press F10 to build the catalog.

Change header and or detail information of an existing catalog.

OR

Manually enter all detail to create a price catalog. (Data is NOT retrieved from master files).

To verify the catalog before transmitting take option 3. Enter the catalog number and version number. Press ENTER.

OR

Press F4 to display a list of catalogs to select from. Press ENTER.

A report prints listing terminal and warning errors. Terminal errors must be corrected before transmitting.

7/2009 35


Create, verify and transmit a Price Catalog to Paccar.

The catalog is verified by the systembefore it is transmitted. If errors werefound, correct the errors and retransmit the catalog.

Remove transmitted price catalogs fromthe VPX832A and VPX832B files.

Reactivate catalogs with a status of “T”to ‘O” so that they may beretransmitted.

Create & Transmit Price Catalog

Purge Price Catalog

Reactivate Price Catalog

7/2009 36


Create Price Catalog(Option 1 on the VL7 menu)

This option is used to create price catalog records by retrieving data from AutoRelease master files. A screen prompts for the company number. The Catalog ID screen is displayed.

Catalog ID Screen

Header data is defaulted and can be changed.

Catalog Number - Required. Paccar's catalog number is a 1-9 position, alpha-numeric number: catalog number-year-month-date. The default catalog number format is “ccyymmdd,” where “cc” is catalog, “yy” is year, “mm” is month, and “dd” is date.

Catalog Version - Required. User-defined version number. The default is “1.”

Catalog Effective Date - Required. Today's system date is the default. The effective date may be changed.

Catalog Expiration Date - Optional. Supplier's price catalog expiration date.

Catalog Purpose - Required. Valid codes include:PC - Price Catalog0 8 - Price Synchronization

F3 - Exit - Returns to menu.

F4 - Prompt - Displays Price Catalogs previously entered. A previously entered price catalog may be accessed to add records. Catalog records cannot be changed or deleted using this option.

CATALOG ID SCREEN

OEM Code ................ PACompany ................. 01

Catalog Number .......... 20010921091803Catalog Version ......... 1Catalog Effective Date .. 092101Catalog Expiration Date . 000000Catalog Purpose ......... PC

F3=Exit F4=Prompt ENTER=Continue

7/2009 37


Enter - Continue - Displays the Selection screen where the selection criteria for this catalog is entered. At the Selection screen, press Enter again and the Catalog Build screen displays. All part numbers for the Catalog Number selected are listed. A single part number may be selected with 1, or select all parts with F9. Press F10 - BuildCatalog. A catalog work file has been created. The Catalog IDscreen is re-displayed.

Maintain Price Catalog(Option 2 on the VL7 menu)

This option is used to change price catalog records that were entered using the option "Create Price Catalog" or to enter records manually. A manually entered record is when all detail is entered manually. No data is retrieved from the AutoRelease master files.

From the Price Catalog List screen, select a record with 1 to display the Header screen. Or, after entering the catalog number and version on the Price Catalog Maintenance screen, press F6 to display the Header screen and add a record.

Catalog Header Screen

Catalog Number - Required. Paccar requires a unique alpha-numeric (1-9 position) catalog number. The default catalog number format is “ccyymmdd,” where “cc” is catalog, “yy” is year, “mm” is month,and “dd” is date. Transmitted in the BCT segment.

VLD7014B CATALOG HEADER MAINTENANCECompany 13 OEM PA ACTION CODE O------------------------------------------------------------------------------Catalog Number ..... 20010921145515 Supplier ID ....... 108429028________Catalog Version .... 1 Effective Date .... 9/21/xxCatalog Purpose .... PC Expiration Date ... 0/00/00Quote Facility Code. 00 Unit of Measure ... EACurrency ........... ___Caterpillar Receiving Mailbox (CMS only): _________Contact Name........_______________________________________________________________________________Contact Number......_______________________________________________________________________________

F3=Exit F12=Return

7/2009 38


Supplier ID - Defaults from the identification code file. The supplier code entered in the requirement A record finds a match in the Plant ID field in the identification code file and retrieves the Supplier ID.Transmitted in the N1 segment.

Catalog Version - User-defined version number of the supplier's price catalog. Not maintainable. Transmitted in the BCT segment.

Effective Date - Required. Enter the effective date that applies to all line items for this catalog number. An effective date for individual line items may be entered on the detail screen. Transmitted in the DTM segment.

Catalog Purpose - Required. Valid codes include:PC - price catalog08 - price synchronization

Transmitted in the BCT segment.

Expiration Date - Enter the expiration date if it applies to all line items for this catalog number. An expiration date for individual line items may be entered on the Detail Screen. Transmitted in the DTMsegment.

Quote Facility - 00 is the default. Enter your OEM assigned supplier facility codeCode if it is different than 00. Transmitted in the N1*BY segment.

Unit of Measure - Required. The unit of measure defaults from the detail record for each line item. If a unit of measure is not entered on the detail record it defaults from the header record. Transmitted in the CTP segment.

Currency - Valid codes include:USD - US dollarsCAD - Canadian dollarsMXP - Mexican pesosCaterpillarReceiving Mailbox

(CMS only) - Not used by Paccar.

Contact Name - Not used by Paccar.

Contact Number - Not used by Paccar.

Enter - When using F6 from the Price Catalog Maintenance screen to add a catalog, press Enter. The Catalog detail list is displayed.

7/2009 39


Detail Maintenance ScreenPress Enter from the header screen or select a record with “1” from the Catalog Detail List screen to display the detail maintenance screen.

Records in the work file may be added, deleted or changed. Some fields contain detail data retrieved from other files or transmitted in segments.

In-House Part# - Required. Internal part number entered in the parts cross reference file. Transmitted in the LIN*VP segment.

Customer Part - Required. Paccar's part number. Transmitted in the LIN*BP segment.

Engineering Rev Lvl - Not used by Paccar.

Effective Date - Defaults from the price file. An effective date entered or changed on this screen, applies ONLY to this line item. Not transmitted.

CATALOG DETAIL MAINTENANCECompany 13 OEM PA Action Code O------------------------------------------------------------------------------Catalog Number ..... 20010921152004 Cust Abbrev ....... PACCARCatalog Version .... 1 Dest Abbrev ....... PACDSTCatalog Purpose .... PC Model Year ........ _____Plant ID ........... 05036AE Purchase Order .... ________________

In-House Part ...... I-PAC8237_______Customer Part ...... PAC8237______________________Engineering Rev Lvl. ________________ Unit Price (6 dec). 137.373737Effective Date ..... 0/00/00 Price Type Qual.... ___Expiration Date .... 0/00/00 Quantity .......... 1Minimum Qty ........ ________________ Unit of Measure ... __Charge Amt (2 Dec) . .00 Maximum Qty ....... _______________Reason Qualifier ... ___ Minimum Order Amt.. .000000Reason Code ........ ___ Order Multiple .... ______________Reference Detail ... VMRS Code ......... ___________________________________________________________________________________________

F3=Exit F10=Delete F12=Return F14-Chrg/Allw

7/2009 40


Price Type Qual - Valid price type qualifiers include:CAT- Catalog PriceTRF- Transfer Price

Transmitted in the PRI segment.

Unit Price (6) - Enter the unit price. This field accepts seven whole numbers,however, Paccar accepts ONLY five whole numbers and six decimal positions. If entering decimal positions, enter the pricewith the decimal point. If entering a whole number (no decimalplaces) it is not necessary to enter the decimal point. Transmitted in the CTP segment.

Expiration Date - Defaults from the price file. An expiration date entered or changed on this screen, applies only to this line item. Not transmitted.

Quantity - Number of units used to calculate the extended price. This field is fifteen positions long, however, Paccar accepts only five positions. Transmitted in the CTP segment.

Minimum Qty - Not used by Paccar.

Unit of Measure - Unit of measure defaults from the Header Screen. A unit of measure entered or changed on this screen, applies ONLY to this line item. Transmitted in the CTP segment.

Charge Amt (2) - Not used by Paccar.

Maximum Qty - Not used by Paccar.

Reason Qualifier - Not used by Paccar.

Minimum Order Amt - Not used by Paccar.

Reason Code - Not used by Paccar.

Order Multiple - Not used by Paccar.

Reference Detail - Not used by Paccar.

VRMS Code - Vehicle Maintenance Registration System code. Transmitted in the REF segment.

F14 - Chrg/Allow - Displays the charge maintenance screen, where charges orallowances associated with a line item may be entered ormaintained.

7/2009 41


Other Charges ScreenPress F14 (Allowance/Charge) from the Catalog Detail Maintenance screen to display the Other Charges screen.

The charge allowance screen is used to enter or maintain other charges associated with the price catalog, to identify a service, promotion, or allowance; to specify a charge amount or percentage; or to update an existing one. All other charges associated with the price catalog are displayed. After other charges have been entered, press F6 to create (or update) the changes.

Allw/Chg - Allowance or charge. Enter a valid code:A - AllowanceC - Charge

SS Code - Discount/Surcharge or "special service" charge. Valid codes include:H670 - Tire Federal Excise Tax

Amount - Not used by Paccar

Quantity - Not used by Paccar

Unit Charge - Enter a numeric value up to 6 decimals. Paccar accepts up to 3 decimals. SIx decimals are rounded to 3 by the system after theyentered.

OTHER CHARGES Alw/SeqNo Chg SS Code Amount Quantity Unit Charge

1 C H670______ ______.00 __________ ______________ 2 _ __________ ______.00 __________ ______________ 3 _ __________ ______.00 __________ ______________ 4 _ __________ ______.00 __________ ______________ 5 _ __________ ______.00 __________ ______________ Bottom

F6=Add/Update F12=ReturnRecords Added/Updated.

7/2009 42


VL73 Menu

Product Service Claim Menu Overview(Option 18 on the VL0 menu)

This menu allows users to accept, adjust, or reject product service claims for warranty repairs. These claims are sent on the 142 (inbound) and 141 (outbound) transaction sets.

MENU: VL73PA ---------------------------------------------------- PACCAR PRODUCT SERVICE CLAIM MENU ---------------------------------------------------- 1. Maintain Product Service Claim 2. Print Product Service Claim 3. Create and Transmit Product Service Claim 4. Purge Product Service Claim 5. Reactivate Product Service Claim 23. Return to V/L Telecommunications Menu 24. Return to Main Menu Option __

7/2009 43


Maintain Product Service Claim(Option 1 on the VL73 menu)

This option displays the Product Service Claim Review screen. This screen lists all current service claims received. Use this screen to access claim header information (option 1), delete a selected claim (option 4), or print a selected claim (option 6).

VLD7311A PRODUCT SERVICE CLAIM REVIEW Options: 1=Select 4=Delete 6=Print Product Service Trans Receive Op Co Issue Duns Dest Duns Claim Number Date Date EQ KF 097248199 097248199 13302-3252,H600 9/05/03 9/22/03 KF 097248199 097248199 13302-6846,T420 9/05/03 9/22/03 KF 091741934 091741934 13311-2601,W008 8/05/03 8/22/03 KF 091741934 091741934 13311-5148,A875 8/05/03 8/22/03 KF 091741934 091741934 13304-6530,C975 8/05/03 8/22/03 KF 091741934 091741934 13312-3816,O996 8/05/03 8/22/03 KF 091741934 091741934 13305-5777,M140 8/05/03 8/22/03 KF 091741934 091741934 13303-5763,M140 8/05/03 8/22/03 KF 091741934 091741934 13311-5369,S050 8/05/03 8/22/03 KF 091741934 091741934 13304-2824,C663 8/05/03 8/22/03 KF 091741934 091741934 13381-6871,T195 8/05/03 8/22/03 KF 091741934 091741934 13310-5147,A875 8/05/03 8/22/03 KF 091741934 091741934 13303-5745,M140 8/05/03 8/22/03 KF 091741934 091741934 13304-6525,C975 8/05/03 8/22/03 More... F3=Exit F17=Top F18=Bottom

7/2009 44


Header ScreenThe Product Service Claim/Response Header screen is accessed from the Product Service Claim Review screen. The header screen lists detailed information about each claim. Use this screen to view claimant and vehicle information and update parts and repair information.

Action Code - Valid values include:O - Original - Indicates the claim is new. This is the defaultvalue.H - Hold- Indicates the claim is on hold.T - Transmitted- Indicates the claim response has been sent.F - Follow-Up- Indicates the claim is in follow-up status.

PRODUCT SERVICE CLAIM/RESPONSE Company: 01 HEADER INFORMATION OEM: PA Action Code................. O O=Original H=Hold T=Transmitted F=Follow Up Claim Status Code........... Modified - See Detail Product Service Claim No.... 13302-6846,T420 Issue ID....... 097248199 Cust. Abbv.......... PACSRV Dest. ID....... 097248199 Dest. Abbv.......... SRVDST Supplier ID.... 01692AA Corp. ID............ KAF429028 Claim Date..... 8/05/03 Receive Date... 8/22/03 Claim Response Date. 0/00/00 Original Response Purpose Code....... 00 Original Claim Amount....... 68.78 33.66 Currency Code...... USD US Dollars F2=Maintain Claim Hdr F4=Names F12=Return Enter=Detail

7/2009 45


F2 - Maintain Claim HeaderPress F2 (Maintain Claim Header) from the header screen to access the Product Service Total Claim Response screen. Use this screen to accept, accept with amendments, reject, or deny claims. This screen is also accessible from the Allowance/Charge screen, the Baseline Item Data screen, and the Allowance/Charge detail screen.

Complete the screen as follows:

1. In the Claim Status Code field, enter the appropriate claim status as described below or press F4 for a list of values. This is a mandatory field.

• A claim status of “7” (Approved as Submitted) indicates the claim is accepted as is. Users can not make changes to claim amounts. This status sends a commitment to pay the claim in full.

• A claim status of “6” (Approved as Amended) indicates the claim is accepted with amendments. Users can adjust parts and labor costs and special charges. This is the only status that allows such changes. This status sends a commitment to pay the claim as adjusted.

• All other statuses reject, deny, or suspend the claim for some purpose. These statuses send zero dollar amounts for the parts and labor costs and the total claim value.

2. In the Claim Response Code field, enter the appropriate claim response or press F5 for a list of values. Or enter a claim response description in the Description field if the appropriate code is not listed. Up to 80 characters may be entered.

3. Press Enter to save changes or F12 to cancel.

User-defined fields are stored in the Claim Header file for suppliers’ use.

............................................................................... : VLD7312PA1 PRODUCT SERVICE TOTAL CLAIM RESPONSE : : : : : : Action Code...... O O=Original H=Hold T=Transmitted F=Follow Up : : Claim Number..... 13302-3252,H600 : : Total Claim Amt.. 266.56 : : : : Claim Status Code... 6 : : Claim Response Code. CDR : : Description......... : : : : Currency Code....... USD : : : : ------------------------ User Defined Fields ----------------------------- : : : : A: B: C: D: : : E: F: : : G: : : : : F4=Status Code F5=Response Code F6=Reset Claim F12=Return Enter=Accept : : : :.............................................................................:

7/2009 46


F4 - NamesPress F4 (Names) to display claimant names and addresses.

Claim DetailPress Enter from the header screen to display the Claim Detail screen. Use this screen to view or edit specific claim details, including vehicle, registered owner, repair problem, repair cost, and payment memo information.

Option 1: Vehicle - Accesses the VIN number, model number, warrantied mileage, repair date, and repair order number of the warrantied vehicle.

Option 2: Name/Address - Accesses the name and address of the vehicle's registeredowner.

Option 3: Problem - Accesses the vehicle problem and service contract information.

Option 4: Repair/Cost Info - Accesses part and labor charges, American Trucking Association (ATA) codes, and repair dates and times.

Option 5: Response - Accesses custom payment information, such as credit memo numbers.

CLAIM DETAIL Options: 1=Vehicle 2=Name/Address 3=Problem 4=Repair/Cost Info 5=Response Service Opt Claim Number Authorization No Recall Number 13311-5369,S050 Bottom F3=Exit F12=Return F17=Top F18=Bottom

7/2009 47


Print Product Service Claims(Option 2 on the VL73 menu)

This option displays the Product Service Claim Listing screen. Use this screen to print a specified subset of claims from the history file. Users can filter by issuer and destination IDs, claim number and date ranges, transmit codes, or a combination of these items. Complete the appropriate fields and press Enter. Claims are printed to the selected printer.

PRODUCT SERVICE CLAIM LISTING Enter the following or leave blank for ALL: Issuer ID ............... _________________ Destination ID .......... _________________ From To Claim Number ______________________________ ______________________________ Claim Date . 0/00/00 0/00/00 Receive Date 0/00/00 0/00/00 Options: 1=Select Opt Transmit Codes _ O - ORIGINAL _ H - HELD _ T - TRANSMITTED

F3=Exit

7/2009 48


Create and Transmit Product Service Claims(Option 3 on the VL73 menu)

This option displays the Review Product Service Claim for Transmission screen. This screen lists all current claims available for transmission. Only claims with an Action Code of "O" (original) or "F" (follow-up) and an assigned claim status code can be transmitted. Use this screen to transmit claims. For more information on assigning claim status codes, see the section "F2 - Maintain Claim Header."

To transmit a claim, select the claim with a "1" and press Enter. The claim is checked for errors before transmission. If no errors are found, the 141 is created and sent to Autent. If the Autent transmission is successful, the claim is updated with an Action Code of "T" (transmitted). If errors are found, an error message is displayed, an error report is created, and the transmit job is terminated.

REVIEW PRODUCT SERVICE CLAIM (141) FOR TRANSMISSION Company: 01 Option: 1=Select Create Total Opt A/C Issue DUNS DEST DUNS Reference Number Date Adj Amount _ O 097248199 097248199 13302-6846,T420 8/05/03 33.66 Bottom

F12=Return Enter = Create Selection File

7/2009 49


Purge Product Service Claim(Option 4 on the VL73 menu)

This option displays the Purge Paccar Product Service Claim screen. Use this screen to purge transmitted claims by claim number or date range. Transmitted claims have an Action Code of "T."

Reactivate Product Service Claim(Option 5 on the VL73 menu)

This option displays the Reactivate Paccar Product Service Claim screen. Use this screen to reactivate claims that have been previously transmitted.

PURGE PACCAR PRODUCT SERVICE CLAIM Enter the following: From To Claim Number .. ______________________________ ________________________________ - OR - Send Date ..... 0/00/00 0/00/00 - OR - Received Date . 0/00/00 0/00/00

REACTIVATE PACCAR PRODUCT SERVICE CLAIM Enter the following: From To Claim Number .. ______________________________ _______________________________ - OR - Send Date ..... 0/00/00 0/00/00 - OR - Received Date . 0/00/00 0/00/00 F3=Exit

7/2009 50

AutoRelease: Paccar ASNs

ASNs

Traditionally coded trading partners use a VL8xx menu (where xx is the OEM code) to transmit ASNs to the trading partner. Many options are identical from trading partner to trading partner. Those options are explained one time only in the AutoRelease manual. Only options unique to this trading partner, exceptions or unique business practices are explained in this document.

See the How to Use this Document section for organizational details about AutoRelease and trading partner documents.

MENU: VL8PA-------------------------------------------------

PACCAR ADVANCE SHIPPING NOTIFICATIONS-------------------------------------------------

1. Maintain ASNs2. List ASNs3. Create/Transmit ASNs4. Purge ASNs5. Reactivate ASNs

23. Return to V/L Advance Shipping Notifications Menu24. Return to Main Menu

Option __

7/2009 51


Maintain ASNs(Option 1 on the VL8 menu)

ASN Maintenance Screen

Sequence Number - Assigned by the system.

Company - Displays the company number that was previously entered.

Action Code - The action code places the corresponding two-digit code in theBSN 01 segment in the ASN file.O- Original 00R- Replace 05H- Hold Record will not be included in transmission

Paccar does not accept retransmitted ASNs with the same shipper number as a previously transmitted ASN. Therefore, note that for retransmitted ASNs the letter “A” is appended to the shipper number in the BSN segment, the shipper number in the REF BM segment, and the shipper number in the REF PK segment.

ASN MAINTENANCESequence number 7609 Company 01 Action Code _------------------------------------------------------------------------------Shp# ........ ______ OEM ............ PA Cust Abrv . ______Ship Date.... ________ ASN ............ _ Dest Abrv . ______Ship Time.... _____ Net Weight...... _______Arrival Date. ________ Tare............ _____ Carrier.... ____Arrival Time. _____ Container Qty... _____ Equip Desc. __Qty Shp...... ________ Cont. Desc...... _____ Equip Init. ____Unit of Mea.. ___ Conv. Code...... __ Line Feed.. _________Tran type.... ___ Dock Code....... __________

Pool Code....... _______Job Sequence.... _________________Chassis/KANBAN#. _______________

Plant ID... _________________ Haz. Mater. _________________P.O. # .... _______________ In-House Prt#. _______________P.O. Line#. _____ Cust Prt # ... ______________________________P.O. Date.. ________ Pro Number.... ________________Conv Bill # _______________ Pool Bill #... ___________

F10=Delete F12=Return

7/2009 52


Many fields on the ASN Screen default from various master files. However, many of them can be changed at shipper entry time.

Shp # - Shipper number assigned by the system when the shipper was created.

OEM - “PA” for Paccar.

Cust Abrv - User-assigned abbreviation that must be entered in the machinereadable file to return the correct customer code on the ASN.

Ship Date - Date of shipment in the MM-DD-YY format. Defaults from shipper entry time.

ASN - Defaults from the destination file. The ASN code can be changed at shipper entry time. Paccar uses the ASN Code of “V” forvariable length without bar code verification.

Dest Abrv - User-assigned abbreviation that must be entered in the machinereadable file to return the correct destination code in the ASN file.

Ship Time - Time entered at shipper entry time (HH-MM) in military format. If no time was entered the ship time is defaulted from the system time when the "extract" option is taken.

Net Weight - Total weight of parts, calculated by multiplying the quantity shipped times the net weight per part entered in the parts cross reference file. It can be changed at shipper entry time.

Arrival Date - Defaults from shipper entry time.

Tare - The weight of the container(s) which is calculated based on thecontainer and pallet weights entered in the container file. The tareweight can be changed at shipper entry time.

Carrier - Carrier abbreviation (SCAC Code) which defaults from the carrierabbreviation field in the carrier file.

Arrival Time - Defaults from shipper entry time.

Container Qty - The number of containers which is calculated by dividing the quantity shipped by the package quantity entered in the requirement A record. It can be changed at shipper entry time.

7/2009 53


Equip Desc - The equipment description further describes the conveyance code. It defaults from the carrier file. Valid codes:TL - TrailerRR - RailcarQty Shp - Number of pieces shipped.

Cont. Desc - The container description must be a valid AIAG standard description consisting of 3 alpha characters followed by 2 numeric characters. This defaults from the container file. The container code can be changed at shipper entry time.

Equip Init - Equipment initial (equipment owner's code) defaults from the carrier file.

Unit of Mea - Defaults from ASN unit of measure field in the destination file. Itcan be changed at shipper entry time.

Conv. Code - AIAG standard code which describes the method of conveyance.Defaults from the carrier file. It can be changed at shipper entrytime. Valid codes include:A - AirC - ConsolidationG - PiggybackJ - MotorM - Motor (Common Carrier)T - Best WayX - Intermodal (Piggyback)AE - Air ExpressLT - Less than trailer loadPG - Pooled PiggybackLine Feed - Code representing the position on the assembly line.Defaults from the requirement C record. Transmitted in the REF*LF segment.

Tran Type - Transaction type associated with the record. Defaults from the requirement B record.

Dock Code - Code representing the dock at the destination location if a dock code was transmitted. Defaults from the requirement A record. The destination abbreviation with the dock code must be enteredin the machine readable destination file to transmit the correctdestination location code in the ASN file.

Pool Code - OEM defined identification code of the pool location. Defaults from the carrier file if pool carrier code is marked with “P.”

7/2009 54


Job Sequence - Processed from 830 into the VIN # field. Defaults from therequirement B record. Note: If the transaction type is 850 then this field contains the PO Line Number.

Chassis/KANBAN# - The entry in this field defaults from the requirement B record. If achassis number was received on the 830, it is processed into theRAN field. If a KANBAN number was received on the 862, it isprocessed into the RAN field. (There is never a case when thereis both a chassis number and a KANBAN number).

Plant ID - Supplier code assigned by Paccar. This is entered in the suppliercode field in the requirement A record and the plant ID field in theidentification code file.

Haz. Mater. - Special handling instructions or hazardous codes entered in the Chrysler ship from field in the requirement A record (F7) defaultsto this field.

P.O. # - Purchase order number issued by Paccar. Defaults from therequirement B record.

In-House Prt# - Internal part number entered in the parts cross reference file.

P.O. Line# - Purchase order line number assigned by Paccar. Defaults from the requirement B record.

Cust Prt # - Paccar's part number.

P.O. Date - Purchase order date issued by Paccar. Defaults from the requirement B record. Transmitted in the PRF*04 segment.

Pro Number - The PRO number is supplied by the freight carrier and may be entered here or on the Update ASN Info screen when the Create/Transmit option is taken.

Conv Bill # - Defaults from the conveyance number field at shipper entry timeif a trailer number was entered. The first 4 positions represent thealphanumeric prefix, and the last 6 positions represent the trailernumber. If there is no prefix, input blanks in the first 4 positions. Ifthere was no entry at shipper time, the shipper number is defaulted. The prefix is transmitted in the second element of theTD3 segment and the trailer number is transmitted in the thirdelement of the TD3 segment.

7/2009 55


Pool Bill # - If a pool bill number is entered, it is placed in the BSN02 and theREF BM segments in the ASN file. If there is no pool bill number,the shipper number is placed in these segments. When a suppliercreates a separate shipper for each part to meet Paccar's requirement of one part per invoice, the pool bill number must be entered so multiple parts can be sent in one ASN file.

7/2009 56

AutoRelease: Paccar Electronic Invoices

Electronic Invoices

Traditionally coded trading partners use a VL75xx menu (where xx is the OEM code) to transmit electronic invoices to the trading partner. Many options are identical from trading partner to trading partner. Those options are explained one time only in the AutoRelease manual. Only options unique to this trading partner, exceptions or unique business practices are explained in this document.

See the How to Use this Document section for organizational details about AutoRelease and trading partner documents.

MENU: VL75PA-----------------------------------------

PACCAR ELECTRONIC INVOICES-----------------------------------------

1. Electronic Invoice Maintenance2. Print Invoice Register3. Create/Transmit Invoices

4. Purge Transmitted Invoices5. Reactivate Transmitted Invoices

23. Return to Electronic Invoice Processing Menu24. Return to Main Menu

Option __

7/2009 57


Maintain Invoices(Option 1 on the VL75 menu)

Invoice Header Screen

Data on the electronic invoice screens may come from the file where it was originally processed or entered, or it may have been changed at ship time or through invoice maintenance.

Action Code - Valid codes include:O or blank - OriginalH - HoldT - Transmit

Customer Abbv - User-defined abbreviation which is also entered in the requirement master and the machine readable file.

Invoice Date - Defaults to the system date when adding an Invoice. The format is MM-DD-YY.

Dest. Abbv - User-defined abbreviation which is also entered in the requirement master and the machine readable file.

Ship Date - The date (MM-DD-YY) the shipment was made.

Supplier ID - Defaults from the supplier code field in the requirement A record which is the same as the plant ID in the identification code file.This is used to obtain the corporate ID to be transmitted in theISA 06.

Shipper Number - Bill of lading or shipper number associated with this invoice.

Ship to ID - OEM assigned code representing the destination plant.

PACCAR ELECTRONIC INVOICE MAINTENANCE

Company Number.. 01 Invoice Number......... 3112

HEADER INFORMATION UPDATE

Action Code...... __ Customer Abbv.. ______Invoice Date..... _______ Dest. Abbv..... ______Ship Date........ _______ Supplier ID.... ___________Shipper Number... _______ Ship to ID .... ___________

F12=Return

7/2009 58


Line Item Selection Screen

Press Enter from the header screen to display the line item selection screen. This screen lists all line items for this invoice. A line item can be selected to be viewed or maintained or can be deleted.

1 Select - Enter 1 next to the record to display or maintain.

4 Delete - Enter 4 next to the record to delete the selected record. A confirmation window is displayed. Enter to delete or press F12 to return without deleting.

F6 - Add Part - Displays a blank line item record to add a part.

F7 - Add Misc Chrg - Displays the Miscellaneous Charge Screen to add a chargepertaining to the entire invoice. A miscellaneous charge may beattached to a specific line item from the detail screen.

ELECTRONIC INVOICE DETAIL REVIEW

Company Number: 13Invoice Number: 225

Enter '1' to select or '4' to delete line item:

Sel Type Part Number Price Line # Seq # _ ITEM 413 3.000 1

Bottom

F12=Return F6=Add Part F7=Add Misc Chrg

7/2009 59


Detail ScreenPress Enter from the header screen when manually adding an invoice, or use F6 (Add Part0 to display a blank line-item record to add a part.

Data on the electronic invoice screens may come from the file where it was originally processed or entered, or it may have been changed at ship time or through invoice maintenance.

Our Part # - In-house part number.

Qty Ship - The quantity entered here is multiplied by the unit price on this screen to obtain the invoice price. After this data is transmitted to Paccar, Paccar uses the qty ship to obtain the total price of parts shipped plus miscellaneous charges. Paccar combines the unit price and the miscellaneous charge and multiplies this by the qty ship to obtain the total price. Paccar does not use the quantity entered on the miscellaneous charge screen.

Cust Part # - Paccar's part number entered in the parts cross reference file.

Unit Price - The price for a single part. If entering decimal positions, enter the price with the decimal point and up to six decimal positions. Ifentering a whole number (no decimal places) it is not necessaryto enter the decimal point.



VLD751PA2 HEADER INFORMATION ADD or UPDATE

Action Code...... ________ Customer Abbv.. PACCAR_________Invoice Date..... 3/13/00 Dest. Abbv..... PADEST_________Ship Date........ 3/13/00 Supplier ID.... 123456_________Shipper Number... ___225 Ship to ID .... 123456789______

VLD751PA3 LINE ITEM INFORMATION

Our Part#... _______________ Qty Ship.......... ________Cust Part#.. ______________________________ Unit Price.(6dec). ____.000P.O. Number. _______________ Unit of Measure... __PO Line # .. _____ Basis Unit Price.. EADON......... CR-R083412 Funds Type........ ___

F12=Return F7=Add Misc Charge

7/2009 60


P.O. # - Purchase order number assigned by Paccar. If the Paccar parts requirements are not received through EDI, enter “N/A” in thefield.

Unit of Mea - Unit of measure abbreviation retrieved from the unit of measure cross reference file, when the reprint invoice prompt is answered with N. The unit of measure can be changed. A warning message is displayed if the unit of measure entered here does not match the unit of measure entered in the unit of measure cross reference file.

P O Line # - Purchase order line item number assigned by Paccar and sent on the 862.

DON - Dealer Order Number. Dealer PO number assigned by dealer.

Funds Type - Received from the price file when the shipper is created. Valid currency codes include:4010 Parts Destinations USD - United States CAD - CanadaMXN - MexicoNo- 4010 DestinationsUSD - United StatesCAD - CanadaAll other 4010 DestinationsUSD - United States

F7 - Add Misc Chrg - Displays the Miscellaneous Charge Screen to add acharge pertaining to a specific line item. (A miscellaneous chargemay be attached to the entire invoice from the line item selectionscreen).

7/2009 61


Miscellaneous Charge ScreenPress F7 (Add Miscellaneous Charge) from the line item selection screen to apply the miscellaneous charge to the entire invoice. Or press F7 from the detail screen to apply the miscellaneous charge to a line item.

Quantity - The miscellaneous charge quantity MUST match the quantity entered in the Qty Ship field on the line item detail. When calculating the invoice price on the Infor system, thequantity shipped is multiplied by the unit price and the chargequantity is multiplied by the charge entered on the miscellaneouscharge screen. However, when Paccar receives this data, theycombine the unit price and the amount of the charge, thenmultiply that total by the quantity shipped on the line item screen.The miscellaneous charge quantity is not used by Paccar.

Charge - Amount of the miscellaneous charge. If entering decimal positions, enter the price WITH the decimal point and up to six (6) decimal positions. If entering a whole number (no decimal places) it is not necessary to enter the decimal point.

U of M - Unit of measure (hard coded).

P.O. # - Purchase order number assigned by Paccar.



VLD751PA2 HEADER INFORMATION ADD

Action Code...... Customer Abbv.. PACCARInvoice Date..... 3/13/xx Dest. Abbv..... PADESTShip Date........ 3/13/xx Supplier ID.... 123456Shipper Number... 224 Ship to ID .... 123456789

VLD751PA4 MISC CHARGE INFORMATION

Qty ....... ________ Charge ___________ U of M ... ___Allowance _ Special Charge Cd __________ Tax Code .. ____ Method of Handling __F12=Cancel

7/2009 62


Special Chg Cd - Miscellaneous charge code. Valid miscellaneous charge codes include:Parts DivisionB750 - Core chargeD240 - FreightD360 - GST TaxD500 - HandlingH650 - Excise tax - OriginH670 - FET TiresH850 - TaxZZZ - Miscellaneous chargeNon-Parts DivisionC040 - DeliveryC870 - Expediting feeE820 - Non-returnable containersF190 - Palletizing chargeF560 - Premium transportationG510 - Returnable containersH680 - Governmental Tax - Used by Paccar Ste. Therese

Tax Code - Defaults from the Tax file. If the special charge code is H850 validcodes include:PST - Provincial State TaxHST - Harmonized Sales TaxQST - Quebec Sales Tax

Meth/Handling - 4010 Destinations 04 -Off invoice 06 - To be paid by customer All other destinations02 - Off invoice06 - to be paid by customer

7/2009 63


File SetupDestination Master FileIn the Destination Master file, set the Print Invoices and Create Invoices flags to “Y” as shown below.

SCD6300B MAINTAIN DESTINATION MASTER FILE Company Number ............ 01 TEST COMPANY Destination Number ........ 456 Name 1 ..... FOB ............... Name 2 ..... Distributor Code .. Address 1 .. Ford Dest Code ......... Address 2 .. ASN/DESADV (B/C/N/O/V/Y) V Address 3 .. GM Msg/Temp Msg Code ... / City/State . GM Std Loc/Ford Rt Cd 2. Zip Code ... Carrier Preference ..... Country .... Route Code / HMRS (Y/N). Honda Destination ...... Arrival/Ship Dates (A/S) ..... S Supplier Type (P/S) .... Delivery Travel Time (Hrs/Min) ASN Unit of Measure .... Delivery Travel Time (Days) .. JIT Location (Y/N) ..... Bar Code Verif (Y/N/C).. Available Ship Days (X = Select) Print Invoices (Y/N) ... Y S M T W H F S Create Invoices (Y/N) .. Y Payment Type: Coll PP PPI Dealer Code ....... F1=Help F10=Delete F12=Return Cat Europe Ult Dest ....

7/2009 64


Machine Readable File In the Destination Abbreviation Record of the Machine Readable file, set the Electronic Invoices flag to “Y” as shown below.

DESTINATION ABBREVIATION RECORD Company Number .............. 01 OEM Code .................... EA Identification Number ....... Dock Location ............... Destination Abbreviation .... Destination Description ..... P O Destination ............. ERS Destination ............. (Y/N) OEM Consideration ........... (Y/N) Electronic Invoices ......... Y (Y/N) Line Set .................... (Y/N) Clear By Destination ........ (Y/N) Type of FBO ................. (M/S) Chrysler PAB/Non-PAB Combine. (Y/N) Send Prev CUM on ASN/DESADV . (Y/N) Exclude from APNAT calc ..... (Y/N) Place on Credit Hold ........ (Y/N) Ship Direct ................. (Y/N)

7/2009 65

AutoRelease: Paccar How to Use This Document

How to Use This DocumentThis document provides information regarding unique instructions required to implement this trading partner's unique business practices. Check the chapters in AutoRelease that describe the common functions and procedures performed by all trading partners, such as the daily procedures, security, ASN options, etc.

General InformationThe general information section of this document describes transaction sets and versions, how they apply to this trading partner and other miscellaneous information.

SecurityThe security section of the document explains the communication method used by this trading partner and network profile, when applicable.

ImplementationThe trading partner documents provide information that may be pertinent only to this trading partner. The implementation section covers master file entry that is unique to this trading partner. However, all required master files must be entered according to the instructions in the "AutoRelease User's Manual."

Files and fields that are unique for all trading partners include the identification code file, trading partnership file, model year, requirement master clear flags and CUM required prior.

VL0 MenuTraditionally coded trading partners use a VL0xx menu (where xx is the OEM code) to perform daily procedures (from the “receive” through the “process”). Many of the options on the VL0 menus are identical from trading partner to trading partner. Those options are explained one time only in the AutoRelease manual.

Daily Procedures Describes the Receive, Split, Breakdown, Print, Process, and transmit 997

Security Describes all security selection and maintenance options and VAN menus

7/2009 66


The VL0 section of each trading partner document illustrates the menu for this specific trading partner, but describes ONLY exceptions and unique business practices such as:

• The print method (mandatory or optional) is identified.

• Special processing for a common option for this specific OEM is identified.

• Fields that print on the edit list but are not processed are identified.

• Options that are not commonly used by other trading partners are described in detail.

A complete description of the common options can be found in the Daily Procedures chapter of AutoRelease.

ASNsTraditionally coded trading partners use a VL8xx menu (where xx is the OEM code) to transmit ASNs to the trading partner. Many of the options on the VL8 menus are identical from trading partner to trading partner. Those options are explained one time only in the AutoRelease manual.

ASN (VL8) Options Describes the standard procedures for transmitting ASNs without bar code.

ASN with Bar Code Options Describes the standard procedures for transmitting ASNs with bar code.


• Valid action codes are identified.

• The ASN Maintenance screen is displayed with valid field descriptions.

• ASN extract exceptions and special processing relating to ASNs for this specific trading partner are identified.

• Options that are not commonly used by other trading partners are described in detail.

A complete description of the routine options can be found in the ASN (VL8) Options chapter of AutoRelease.

7/2009 67


Electronic Invoice MenuSome traditionally coded trading partners use a VL75xx menu (where xx is the OEM code) to transmit electronic invoices to the trading partner. Many of the options are identical from trading partner to trading partner. Those options are explained one time in the AutoRelease manual.

Electronic Invoices Describes invoice maintenance, print invoice register, create and transmit, purge, and reactivate transmitted invoices menu options.


• Invoice header screen and valid field descriptions

• Invoice line item screen

• Invoice line item information screen and valid field descriptions

• Miscellaneous charge screen and valid field descriptions

• Options that are not commonly used by other trading partners are described in detail

A complete description of the common options can be found in the Electronic Invoices chapter of AutoRelease.

7/2009 68

Paccar - Infordiscrete.support.infor.com/dynaList/ar_sw9/TPdocs/OEMsup/arOEMSup... · Paccar...

Documents

Transcript of Paccar - Infordiscrete.support.infor.com/dynaList/ar_sw9/TPdocs/OEMsup/arOEMSup... · Paccar...