Page History
| Info | ||
|---|---|---|
| ||
Vendors,Tickets & Contracts > Vendor > Edit or Add Vendor |
| Info | ||||
|---|---|---|---|---|
| ||||
Basic details for the Vendor are located in the Details tab. |
- Click on the Edit button.
- The first tab, Details, will open.
| Circle | Element | Description | ||
|---|---|---|---|---|
| 1 | Name as showshown on on W9W9 | Name on W-9. This field cannot be changed , once saved. | ||
| 2 | Vendor dba Name Name | dba name as appears on W-9. This field will be blank if no dba on W-9 | ||
| 3 | Common Name | Common Name established by MTP that will appear on contracts, delivery orders and reports | ||
| 4 | Vendor URL | Vendor corporate URL. This prints on the contract. Locations may have a separate URL that prints on the e-ticket. | ||
| 5 | Customer Info Number | Vendor corporate customer number. This prints on the contract. Locations may have a separate customer service number that prints on the e-ticket. | ||
| 6 | Vendor TMS Number | This number is system generated and cannot be selected or changed. | ||
| 7 | Legacy Vendor Number | This is the MTP Oracle number and will be blank for new vendors only created in the TMS. | ||
| 8 | Workflow Status | Defaults to Blank.
| ,
| , etc.
|
| 9 | SAP Number | May be blank while awaiting SAP number, however vendor cannot go live until has SAP number. | ||
| 10 | API TypeIf Vendor has an API, Select the appropriate API | API Vendors only. Blank for non-API. | ||
| 11 | Active | If On, this is an Active Vendor. | ||
| 12 | MTP Contract | If On, this is an a MTP Contract and not a Local Contract. | ||
| 13 | CONUS Toggles | If On, this is a CONUS contract vice a OCONUS. | ||
| 14 | Logo | Primary Vendor Logo logo can be linked to tickets and will visually display once linkedon e-ticket after linked. Can override on individual ticket if needed. |