Electronic Manifesting - UPS.com

Electronic Manifesting 

Package Level Detail (PLD 0200) 

NOTICE 

Document Version 1.4 

Last Updated 04/05/04 

The use, disclosure, reproduction, modification, transfer, or transmittal if this work for any purpose in any 

form or by any means without the written permission of United Parcel Service is strictly prohibited. 

© 2004 United Parcel Service of America, Inc. All Rights Reserved.

Electronic Manifesting Documentation Electronic Manifesting – Revision 1.4 


Table of Contents 

Introduction ................................................................................................................................................... 3 

Technical Overview ..................................................................................................................................... 3 

High Level Process Flow ............................................................................................................................ 5 

Frequently Asked Questions (FAQs) ........................................................................................................ 7 

Create the Request Message .................................................................................................................. 10 

Request/Response Parameter Keys....................................................................................................... 10 

Example of a Request Message.............................................................................................................. 11 

Send the Request Message..................................................................................................................... 14 

Receive a Response Message................................................................................................................ 14 

Parse the Response Message................................................................................................................. 19 

Error Codes ................................................................................................................................................ 20 

© Copyright 2004 United Parcel service of America, Inc. All Rights Reserved. Last Revised 04/05/04 

Page 2 of 22

Electronic Manifesting Documentation Document Version 1.4 


Introduction 

**** Please Note that this document is for use with PLD 0200 or later. **** 

UPS Electronic Manifesting brings your e-commerce site into the new millennium by digitizing your shipping 

procedures and allowing you to send an electronic shipment manifest to UPS rather than a detailed paper manifest. 

This powerful tool gives your business the flexibility of alternate billing options, reference number tracking 

capabilities and other feature benefits. Additionally, Electronic Manifesting can increase the accuracy and efficiency 

of your shipping operation by transmitting advance notice of shipping information via fax or e-mail to shippers, 

receivers or third parties. 

Technical Overview 

Timely and Accurate PLD 

To insure timely receipt of PLD (Package Level Detail) information, customers 

using UPS Host solutions need to upload at the time of driver pickup. 

Uploading at the time of driver pickup enables full shipment visibility for 

information based services such as Quantum View®, (Quantum View Manager, 

Quantum View Data, Quantum View Notify, Brokerage and UPS Tracking) and 

insures high quality service that you've come to expect from UPS. 

The Electronic Manifesting tool may be easily integrated into your existing e-commerce solutions to enhance your 

businesses shipping capabilities. Have your IT organization work with UPS to integrate the Electronic Manifesting 

tool into your business to take advantage of the following technical benefits: 

� A sophisticated IT solution for your business - The Electronic Manifesting tool allows your detailed 

shipment information to be sent in the form of a data stream to the UPS Host system. Integrating the 

Electronic Manifesting tool into your existing systems requires advanced knowledge of leading edge 

programming languages (e.g., C++, Java, Visual Basic, Active Server Pages or Perl). To fully integrate this 

tool your business should leverage e-commerce technical skills to communicate with UPS. Communicating 

through the Electronic Manifesting tool includes working with UPS to develop a solution that includes: 

� Making an Internet connection with UPS 

� Pulling shipping data for the HTTPS request message from your other systems 

� Building an HTTPS request message and sending the data stream to UPS 

� Receiving and parsing an HTTPS response message from UPS 

� Integrating that response back into your e-commerce solutions 

� Seamless and easy integration into your existing e-commerce solutions - The Electronic Manifesting 

tool enables you to develop an application that requests data from UPS servers and parses the response. The 

Electronic Manifesting tool technical documentation provides file specifications for each request message. 

Additional examples of valid formatted electronic manifests are provided to aid in your development. 

Follow the steps within the documentation to seamlessly integrate your shipping data with UPS file 

standards. The next step for the developer is to integrate this raw data into your web or electronic 

commerce-enabled solutions. Due to the complexity involved in sending electronic shipping manifests the 

initial development time is estimated to be approximately 80 hours. A large part of that estimate is the 

electronic manifest data certification process. 

• Ensured security of sensitive corporate shipping data - Due to the sensitive corporate data 

being transmitted over the Internet, this tool requires a Secured Sockets Layer (SSL). Applications 

that are connected to the Internet can connect directly to the tool via HTTPS at the standard SSL 


Page 3 of 22



port 443, using a TCP/IP socket or a URL connection. The encrypted request and response 

messages are also transmitted through port 443. 

• Hardware or software requirements are kept to a minimum - The Electronic Manifesting Tool 

is an Application Programming Interface (API) residing on a UPS server that allows access to 

Common Gateway Interface (CGI) programs at UPS. UPS software does not have to be installed 

on the system hosting the e-commerce application. The tool is not platform-specific and can 

operate with any programming language that supports standard HTTPS protocol. 


Page 4 of 22



High Level Process Flow 

Outlined below is a high level Process Flow of Integrating Electronic Manifesting: 

Process Flow Integrating PLD with Electronic Manifesting 

Review Online Documentation at 

http://www.ups.com/uoltools/manifest/i 

ntroman.html to begin coding HTTP 

requests 

Keys: 

Notify 

eDeployment/ECSSS 

Approval of 

Production 

Migration Test file 

& Shipping Labels 

Customer 

eDeployment 

team/ECSSS 

Register at 

MYUPS.com 

Create Socket 

connection to 

UPS 

Uploading to 

Production 

Environment 

� Review Online Documentation To Begin Coding HTTP Requests - Please review the documentation at 

http://www.ups.com/uoltools/manifest/introman.html regarding Electronic Manifesting Integration. Please 

document any questions that you may have concerning the Electronic Manifesting Integration. 

� MY UPS.com – Prior to using the UPS SPF Certification Tool you must register at www.MYUPS.com. You 

are required to create a unique User I.D. and password that will be authenticated when you log into the UPS 

SPF Certification Tool. If you are currently registered at MYUPS.com, you must register again in order to 

receive electronic book numbers from the UPS SPF Certification Tool and begin testing. 

� Please note: This User I.D. is permanent and cannot be altered. Please ensure that the I.D. you create is 

acceptable to all parties that will be using it. Dashes, hyphens, and other special characters should not be used. 

The length of your I.D. and password should not exceed 10 characters. DO NOT ADD ANY ACCOUNTS 

ON THE ACCOUNT SUMMARY PAGE AT MYUPS.COM. MAIN ACCOUNT IS ENTERED AT 

THE UPS SPF CERTIFICATION TOOL. ACCOUNTS ARE ADDED AT THE UPS SPF 

CERTIFICATION TOOL ONLY AFTER THE MAIN ACCOUNT IS APPROVED FOR 

PRODUCTION. 

� Review Online Electronic Manifesting License Agreement – Please review and accept the Electronic 

Manifesting license agreement at https://www.pld.ups.com/emagree. 

� PLD Test using the UPS SPF Certification Tool – The UPS SPF Certification Tool is a new browser- based 

Internet product used to certify customers for the latest version of PLD. You will use the UPS SPF Certification 

Tool at https://www.pld.ups.com/ct to guide you through the necessary steps to build a compliant global PLD 


Page 5 of 22 

Review Online Electronic 

Manifesting License at: 

https://www.pld.ups.com/emagree 

PLD Test 

Go to UPS SPF Certification Tool 

https://www.pld.ups.com/ct 

2 Week PLD 

Monitoring 

Period 

Turnover to 

Production 

Support Desk



file for a test upload. (Note: Customers must complete steps 1-5. ConnectShip Customers – Complete 

ONLY steps 1 & 2 and then US customers email edeploypld@ups.com and non-US customers contact your 

ECSSS) 

These steps include building test cases to ensure that the test files contain accurate PLD formatting and 

validation of origin/destination country pairs to Shipment Charge Types, Packaging Types (container types), 

services and accessorials. 

Frequently Asked Questions have been included within the tool to address many common concerns. 

� Create connection to UPS – You will be required to create an HTTP socket connection to the UPS server 

(must be SSL enabled). It is required to have a socket connection opened to Port 443 and SSL enabled. Your 

proxy administrator should be able to assist you with setting up this connection. 

� Notify eDeployment/ECSSS – After successful completion of the certification, US customers please email the 

eDeployment team at edeploypld@ups.com and non-US customers please contact your ECSSS. You have 

completed the certification when all five steps are marked as completed. A screen appears following the 

completion of Step 5 announcing: “Congratulations! You have completed certification…” At this point, you 

will be required to complete the production migration test. 

� Approval of Production Migration Test File & Shipping Labels – Once you submit your production 

migration test file, which is the last phase of PLD testing, for US customers an eDeployment integrator will be 

assigned to review and approve your PLD file if the file is error-free. For non-US customers your ECSSS will 

review and approve your PLD file if the file is error-free. At this time any shipping labels, the manifest and 

other corresponding shipping documents will be compared to the SPF file for congruency. You will be 

informed of your file and corresponding paperwork being approved. Upon receipt of this approval, you can 

proceed with the next steps in the process flow. 

� Begin Uploading in Production – For US customers, an eDeployment integrator will walk you through the 

migration to the Production environment. For non-US customers, your ECSSS will walk you through the 

migration to the Production environment. From this point forward, UPS will be billing you on your PLD files. 

Timely and Accurate PLD 

To insure timely receipt of PLD (Package Level Detail) information, customers using UPS Host 

solutions need to upload at the time of driver pickup. 

Uploading at the time of driver pickup enables full shipment visibility for information based 

services such as Quantum View®, (Quantum View Manager, Quantum View Data, Quantum 

View Notify, Brokerage and UPS Tracking) and insures high quality service that you've come to 

expect from UPS. 

� 2 Week PLD Monitoring Period – Once you have been migrated to production, for US customers, the UPS 

eDeployment team will monitor your PLD files for a minimum of two weeks. For non-US customers, the 

ECSSS will monitor your PLD files for a minimum of two weeks. This is done to ensure that you are 

comfortable with the PLD upload process. You will be able to view any errors that occur during this time 

period via the response reports that are generated from your PLD upload to UPS. These errors should be 

discussed between an eDeployment integrator and you to assure quality PLD files. 

� Turnover to Production Support Desk – After the completion of the two-week monitoring period, you will be 

asked to direct any Production questions or issues to the Production Support desk. 


Page 6 of 22



Frequently Asked Questions (FAQs) 

Review Online 

Documentation 

& Begin coding 

HTTP Requests 

Review Online 

Electronic 

Manifesting 

License at: 

https://www.pld. 

com/emagree 

PLD Test 

Go to UPS SPF 

Certification Tool 

https://www.pld. 

ups.com/ct 

Create Socket 

Connection to 

UPS 

Q. Is there any other documentation I need to review, besides the online 

documentation? 

A. The only documentation that you will need to use for the Electronic Manifesting 

integration is the online documentation. The PLD documentations can be found on 

the Certification Tool web site at https://www.pld.ups.com/ct . 

Q. Who do I contact if I have questions regarding how to code the HTTP requests? 

A. For the US, you will need to send an email that will be routed to the UPS tech 

support group. The email address is edeploynonpld@ups.com. Please indicate in 

this form the exact problem you are experiencing during this step. 

For International, you will need to contact your ECSSS. 

Q. What happens if I have not agreed to the Electronic Manifesting License 

Agreement? 

A. Please contact your UPS Account Representative if you have not agreed to the terms 

of the Electronic Manifesting license agreement. You will not be able to be placed 

in production with this product until the details of the license agreement have been 

resolved. 

Q. What is the difference between a fatal error and a non-fatal error? 

A. Fatal and Non-fatal errors are generated after a PLD file is uploaded containing 

errors related to the PLD file specifications and/or UPS business rules. Each type of 

error results in a different outcome and requires a different course of action. 

• Fatal errors will prevent the PLD file from being uploaded successfully. You 

will need to make corrections and re-upload the file whether you are in 

Development (Testing) or Production. Fatal errors are distinguished by the 

following: An error code of ‘5491’ – PLD file contains Fatal Errors. Correct 

errors and resubmit. 

• Non Fatal errors will also prevent the PLD file from being uploaded successfully 

in Development (Testing). If you are in Development (Testing), you will need 

to make corrections and re-upload the file. If you are in production, you will 

need to note the error, but will not need to re-upload the file. You should make 

the necessary corrections so that the errors do not occur in the future. Non-fatal 

errors are distinguished by the following: An error code of '5481' - PLD File 

submitted with above errors. Correct for next upload. 

It should be noted that the entire PLD file is either accepted or rejected. If you 

upload a PLD file with non - fatal error only, the entire PLD file (all of the 

records contained in the file) will be accepted. If you upload a PLD file with 

fatal errors, the entire PLD file (even the records that did not contain fatal 

errors) will be rejected. 

Q. Who can I contact with questions on how to enable SSL tunneling? 

A. UPS does not provide support in setting up SSL tunneling. You will need to speak to 

your proxy administrator to verify if you have this feature. 

Q. What happens if I do not have SSL tunneling or a socket connection opened 

Port 443? 

A. You will not be able to proceed with the integration process without these two 

requirements. You will need to speak to your proxy administrator to verify if you 

have this feature. 


Page 7 of 22



Approval of 

Production 

Migration Test 

File & Shipping 

Labels 

Uploading to 

Production 

Environment 

2 Week PLD 

Monitoring 

Period 

Q. How do you obtain book numbers for an additional shipper number? 

A. Once you are approved, you may add additional shipper numbers by logging into the 

UPS SPF Certification Tool and clicking on the 'Add UPS Account' button. You 

may add 100 account/shipper numbers per User I.D. 

Q. How long does it take to get my file approved upon completing the UPS SPF 

Certification Tool and submitting a production migration test file? 

A. The timeframe will depend on the amount of services that you are testing for but 

generally it should take approximately 1-2 days. If you are having an international 

PLD file approved, this process can take up to 3-4 days to verify all the information 

within the file and the external documentation required by Customs. 

Q. What is required when I am ready to go into production? 

A. Once your file is approved, you will be informed of your ability to upload PLD 

electronically. You will then begin uploading your PLD files electronically to the 

UPS Billing Department. You will then be providing the Summary Manifest or 

Summary Barcode to your UPS Package Car Driver. 

Q. What causes a Return Code and message of ‘3005’, Already Processed? 

A. This error occurs when you upload the same file twice. Three fields are used to 

determine if a file is unique or not. They are: PickupDate, BookNumber, and 

PageNumber. You do not have to re-upload PLD files if it only contains non-fatal 

errors. 

This error prevents you from uploading a duplicate file, which would result in you 

getting double billed. It also prevents you from uploading multiple files for a single 

Pick- up Date without incrementing the Book number and/or Page number. 

Q. What causes a Return Code and message of ‘6249’? Is only one PickupDate 

allowed in a file? 

A. This error occurs when you have more than one PickupDate in the PLD file. This 

usually happens when you send up two or more days worth of shipments. By 

combining all of the shipments into one PLD file, this will populate the file with 

multiple PickupDates. Instead, you need to send up a separate file for the shipments 

sent out on each individual PickupDate. 

Q. When does UPS need PLD uploaded? 

A. To insure timely receipt of PLD (Package Level Detail) information, customers 

using UPS Host solutions need to upload at the time of driver pickup. 

Q. Why is it so important to upload at the time of driver pickup? 

A. Uploading at the time of driver pickup enables full shipment visibility for 

information based services such as Quantum View®, (Quantum View Manager, 

Quantum View Data, Quantum View Notify, Brokerage and UPS Tracking) and 

insures high quality service that you've come to expect from UPS. 

Q. What is the purpose of the 2 week monitoring period? 

A. During this period, an integrator will be assigned to monitor your production PLD 

files. We want to ensure that you are comfortable with this process of uploading 

PLD. We also ensure that your book and page numbers are configured properly for 

the live environment, allowing the UPS billing department to be able to accurately 

track and bill your shipments. 


Page 8 of 22



Turnover to 

Production 

Support Desk 

Q. When would I contact the Production Support desk? 

A. Once you have been in production and your files have been monitored for the 2week 

error-free period, you will be a Production Support customer. 


Page 9 of 22



Create the Request Message 

**** Please Note that this document is for use with PLD 0200 or later. **** 

To send a request to the PLD Upload tool, an application writes a stream of data out to the tools via a TCP/IP socket 

or a URL connection. The datastream must be in the form of an HTTP request message. 

To connect to the PLD Upload tool, open www.pld-certify.ups.com and then post to /hapld/tos/kdwhapltos. The 

connection must be made to a tool using SSL, on port 443. 

Note: This connection address is for testing only. Once an application has completed PLD certification testing, the 

production hostname will be provided by a UPS PLD specialist. 

The next table lists the parameters to use in the body of the request message. The Request/Response Parameter Key 

defines the codes used in the table. 

When you write the request message, be aware that some characters you may want to include in the parameters of 

your message can cause problems during transmission. These characters include spaces, ampersands, punctuation 

marks, and so on. A process called url-encoding encodes these characters in a way that allows them to be 

interpreted as data, rather than programming delimiters or other commands. 

Make sure you do url-encode the characters in your message parameters. The rules for url-encoding are: 

• ASCII characters a through z, A through Z, and 0 through 9 remain the same; 

• the space character is encoded as a plus sign (+); 

• all other characters are encoded as %XY, where % is the percent sign, and XY is the two-digit hexadecimal 

representation of the lower eight bits of the character. 

Make sure you don’t url-encode the equal signs (=) or ampersands (&) that are part of the syntax of your message. 

For example, don’t url-encode the equal sign between name-value pairs, or the ampersands that are name/value pair 

delimiters. 

Request/Response Parameter Keys 

Field Type: Required 

In each request message and its corresponding response message, not every field may be required. For each field in 

the request/response message, the Required column in the Input and Output Parameter tables describes whether the 

field is required or not. The following table describes each of the required field codes: 

Required Description 

Conditional (C) This field is required only if a specified condition is present; otherwise, this field is 

optional. The conditions to determine whether this field is required or optional are 

stated in the description of the input or output parameter. 

Not Used (N) This code indicates that the field will not be used in the input or output message 

format. The character N is followed by a description of when the field is not used. 

Optional (O) Input Parameters 

For optional fields, if a value is not provided, the field name should not be included 

in the input data stream. 

Output Parameters 

For optional fields, if a value is not provided, the field will be empty in the output 

data stream. 

Required (R) For fields that are required, a value other than blank spaces must be provided. 


Page 10 of 22



Example of a Request Message 

This example displays a complete request message for the PLD Upload. 

In the example, use to show where you must insert a new line or carriage return. All other white space line 

feeds are used for readability. The boundary string defined in the main Content-type: header field is BOUNDARY. 

This means that each data segment in the request message will be separated by the string – BOUNDARY, and that 

the end of the message will be denoted by the string – BOUNDARY --. 

Content Length Calculation: 

The Content-length of the main header is 1040, indicating that the total length of the entire message is 1040 bytes. 

To calculate this for the example below, count each byte starting with the “-“ of the “--BOUNDARY” line. 

Continue counting everything up to and including the last of the last line in this example. Please remember 

that all are counted as 2 bytes. This area is highlighted below. 

POST /hapld/tos/kdwhapltos HTTP/1.1 

Host: www.pld-certify.ups.com 

Content-type: multipart/mixed; boundary=BOUNDARY 

Content-length: 1040 

 

--BOUNDARY 

Content-type: application/x-www-form-urlencoded 


 

AppVersion=1.0&AcceptUPSLicenseAgreement=Yes&ResponseType=application/x-ups-pld&VersionNumber= 

V4R1&UserId=useridvalue&Password=passwordvalue 

 

--BOUNDARY 

Content-type: application/x-ups-binary 


 

020082 2.0 2002101700000000000010500 000000001*AA0A1754 US 

1234567002000001*BA1z1234560100002352 00001+0000000000000010 +000 

0000000000000LBS01PRE10 3INUSD000001*CA18ATTENTION 

DELIVERY 234 SOME LOCAL ST SO 

ME CITY NJ 07652 US12015551212 *PA1z1234560100002352 

02+0000010 +0000010 

*SA000004 

 

--BOUNDARY-- 


Page 11 of 22



The Content-length of the first data segment is 140, indicating that there are 140 bytes in the message body of this 

data segment. To calculate this for the example below, start the byte count with the “A” in “AppVersion” and 

continue up to the “e” of “passwordvalue”. Do not count the of this line. This area is highlighted below. 





 

--BOUNDARY 



 



 

--BOUNDARY 



 

020082 2.0 2002101700000000000010500 000000001*AA0A1754 US 

1234567002000001*BA1z1234560100002352 00001+0000000000000010 +000 




02+0000010 +0000010 

*SA000004 

 

--BOUNDARY-- 


Page 12 of 22



The Content-length of the second data segment is 719, indicating that there are 719 bytes in the message body of this 

data segment. This data segment is your PLD information. To calculate this for the example below, start the byte 

count with the “0” of the “020082” line and continue to the end of the PLD information at “4” of the “*SA000004” 

line. Do not count the in this line. This area is highlighted below. 





 

--BOUNDARY 



 



 

--BOUNDARY 



 

020082 2.0 2002101700000000000010500 000000001*AA0A1754 US 

1234567002000001*BA1z1234560100002352 00001+0000000000000010 +000 




02+0000010 +0000010 

*SA000004 

 

--BOUNDARY-- 


Page 13 of 22



Send the Request Message 

To send the request message, an application writes it to the PLD tool via a secured socket (SSL) connection. An 

application can create the request message in a buffer, and then write the contents of the buffer out to the tool. The 

exact syntax used to write to write the buffer out to the tool varies, depending on the programming language and the 

API set used. 

Receive a Response Message 

The following is a list of specific examples of response messages for the PLD Upload tool. The response messages 

follow the general response message format described in Parse a Response Message. 

Examples: 

� 0000 - 0000Successful upload, no warning messages. Control and Status Reports are returned. 

� 6930 - 5481Successful upload with warning messages. Error, Control and Status Reports are 

returned. 

� 6931 - 5491Failed upload due to errors in the PLD data. Error and Status Reports are returned. 

� 6931 - xxxxFailed upload due to errors in the input parameters. Status Report is returned. 

The data segment application/x-ups-psmpld contains the response type (successful, warning, error or 

severe error). The data segment application/x-ups-pld contains the reports. 

Examples of Response Messages 

Successful upload, no warning messages. Control and Status Reports. 

HTTP/1.1 200 OK 

Server: IBM-HTTP-Server/1.0 

Date: Mon, 25 Nov 2002 20:21:15 GMT 

Connection: close 

Accept-Ranges: bytes 

Content-Type: multipart/mixed; boundary=BOUNDARY 

Content-Length: 1251 

--BOUNDARY 

Content-type: text/html 


 

 

UPS Internet Software 

 

 

UPS Internet Software, Copyright UPS 1998 

 

 

--BOUNDARY 

Content-type: application/x-ups-psmpld 


UPSOnLine%1.0%0000%0000Successful completion - No errors found. 

--BOUNDARY 

Content-type: application/x-ups-pld 



Page 14 of 22



000200000758300000640 KDGPLCR1 United Parcel Service 

11/25/02 Page:1 PLD Contr 

ol Report 04:09 PM 

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

------------------------------------------------------------- Pickup D 

ate: 20010302 Sequence#:000001234567001 Number of Records:00000001 

Shipper #:123123 Book/Page #:1234567001 Shipme 

nts:000001 Packages:00000001 10000008800000000Successful completion 

- No errors found. 

--BOUNDARY-- 

Successful upload with warning messages. Error, Control and Status Reports. 

HTTP/1.1 200 OK 







--BOUNDARY 



 

 


 

 


 

 

--BOUNDARY 



UPSOnLine%1.0%6930%5481PLD File submitted with above errors. Correct for 

next upload. 

--BOUNDARY 



000300001967300000640 KDGPLRS1 United Parcel Service 

11/25/02 Host A 

ccess 08:05 AM 


Page 15 of 22



PLD Error Report PAGE 1 

-------- 

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

- Err Error 

Code/ Message/ 

Tracking Seg Field 

Field Number ID Name 

Contents ---------------------------- 

--------------------------------------------------- 6715 

Invalid 1z Service Level for the chosen UPS services 1Z123555 

0100000069 *PA PackageTrackingNumber 1Z1235550100000069 

5481 PLD File submitted with above errors. Corr 

ect for next upload. 200000640 KDGPLCR1 Un 

ited Parcel Service 11/25/02 Page:1 

PLD Control Report 04:09 PM 

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

---------- Pickup Date: 20010302 Sequence#:000001234567001 Number o 

f Records:00000001 

Shipper #:123123 Book/Page # 

:1234567001 Shipments:000001 Packages:00000001 10000008800015481PLD 

File submitted with above errors. Correct for next upload. 

--BOUNDARY-- 

Failed upload due to errors in the PLD data. Error and Status Reports. 

HTTP/1.1 200 OK 







--BOUNDARY 



 

 


 

 


 

 

--BOUNDARY 



Page 16 of 22




UPSOnLine%1.0%6931%5491PLD File contains Fatal Errors. Correct errors 

and resubmit. 

--BOUNDARY 



000200001798300001680 KDGPLRS1 United Parcel Service 

11/25/02 Host A 

ccess 08:05 AM 

PLD Error Report PAGE 1 

-------- 

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

- Err Error 

Code/ Message/ 

Tracking Seg Field 

Field Number ID Name 

Contents ---------------------------- 

--------------------------------------------------- 9102 

This field is required. 1Z355500 

0000000008 *AA BookNum 

5612 This field must be numeric. 

1Z3555000000000008 *AA BookNum 

9121 Value 

does not match the first *AA segment Book & Page. 

Header PLDSequenceNumber 000009665869012 

5491 PLD File contains Fatal Errors. Correct errors 

and resubmit. 10000008800025491PLD File contains Fatal E 

rrors. Correct errors and resubmit. 

--BOUNDARY— 


Page 17 of 22



Failed upload due to errors in the input parameters. Status Reports Only. 

HTTP/1.1 200 OK 







--BOUNDARY 



 

 


 

 


 

 

--BOUNDARY 



UPSOnLine%1.0%6931%6503UserId is invalid. 

--BOUNDARY 



00010000010910000008800026503UserId is invalid. 

--BOUNDARY-- 


Page 18 of 22



Parse the Response Message 

To identify the boundary string separating the data segments in the response message: 

1. Verify that the main header contains the content-type header field. 

2. Verify that the Content-type of the main header is multipart/mixed. 

3. Extract the boundary string from the main header’s content-type field. The boundary string separating 

the data segments will be this boundary string preceded by two dasher (--). The terminating boundary 

string preceded by and followed by two dashes (--). 

To parse the data in each segment take these steps: 

1. Locate the beginning of the data segment. 

2. Search for the next occurrence of the boundary string, indicating the beginning of a new data segment. 

3. Verify that this occurrence of the boundary string is not the terminating boundary string. 

4. Identify the Content-type of the data segment. 

5. Verify that the Content-type header field is in the segment. 

6. Store the Content-type of the data segment’s message body. 

7. Identify the Content-length of the data segment. 

8. Verify the Content-length of the data segment’s message body. 

9. Read the message body into a buffer, using the Content-length obtained in the previous step. 

10. Parse the output parameters out of the data segment, using the Content-type obtained in Step 5 above. 


Page 19 of 22



Error Codes 

Reason Codes 

Message Text 

Description 

Reason Code Reason Text 

6800 

Input AppVersion is required. AppVersion variable in the request message is not 

set. 

6801 

Input AppVersion is invalid. AppVersion variable in the request message is set, 

but invalid (e.g. AppVersion = 5.0). 

6802 

Input AcceptUPSLicenseAgreement 

is required. 

AcceptUPSLicenseAgreement variable in the 

request message is not set. 

6803 

InputAcceptUPSLicenseAgreement 

is invalid. 

AcceptUPSLicenseAgreement variable in the 

request is not set to Yes or yes. 

Input ResponseType is required. ResponseType variable in the request message is 

not set. 

6804 

6805 

6806 

Note: For some functions, when the 

ResponseType is not set, unpredictable 

responses may be produced. 

Input ResponseType is invalid. ResponseType variable in the request message is 

set but invalid. 

Note: For some functions, when the 

ResponseType is invalid, unpredictable 

responses may be produced. 

Input format is invalid. This error occurs when the input request is 

incorrectly formatted, for example when the HTTP 

headers or name-value pairs are incorrectly 

formatted. 

HTTP Comm. Error Codes 

Error Code Description 

200 request completed. 

201 object created, reason = new URI. 

202 async completion (TBS). 

203 partial completion 

204 no info to return. 

300 server couldn’t decide what to return. 

301 object permanently moved. 

302 object temporarily moved. 

303 redirection w/ new access method. 

304 if-modified-since was not modified. 

400 invalid syntax. 

401 access denied. 

402 payment required. 

403 request forbidden. 

404 object not found. 

405 method is not allowed. 


Page 20 of 22



Error Code Description 

406 no response acceptable to client found. 

407 proxy authentication required. 

408 server timed out waiting for response. 

409 user should resubmit with more info. 

410 the resource is no longer available. 

411 couldn’t authorize client. 

500 internal server error. 

501 required not supported. 

503 error response received from gateway 

504 timed out waiting for gateway. 

600 unspecified HTTP communication error. 

610 unable to connect to HTTP server. 

620 unable to connect through proxy. 

650 user abort. 

904 invalid request application data length. 

905 invalid request info length. 

906 invalid request info length. 

907 invalid application message ID. 

910 error opening file. Check working directory. 

920 out of memory 

930 system exception 

935 invalid timeout parameter. 

940 missing multipart boundary string. 

950 invalid HTTP content length field. 


Page 21 of 22



This page intentionally left blank. 


Page 22 of 22

Electronic Manifesting - UPS.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?