Vous êtes sur la page 1sur 10

Oracle® Warehouse Management

Cloud
FedEx Parcel Integration
Update 18C
February 2019
Copyright Notice
Oracle® Warehouse Management Cloud FedEx Parcel Integration, Update 18C
Copyright © 2019, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing
restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any
form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless
required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone
licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated
software, any programs installed on the hardware, and/or documentation, delivered to U.S.
Government end users are "commercial computer software" pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,
disclosure, modification, and adaptation of the programs, including any operating system, integrated
software, any programs installed on the hardware, and/or documentation, shall be subject to license
terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup,
redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim
any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC
trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or
registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for
and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to
your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program
website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle
Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. iii
Contents
COPYRIGHT NOTICE ............................................................................................. III

CONTENTS ............................................................................................................. IV

PREFACE................................................................................................................ VI

CHANGE HISTORY .................................................................................................... VI


1. STEPS TO SETUP A FEDEX CARRIER ................................................................. 7

SETTING UP A FEDEX CARRIER ................................................................................... 7


SETTING UP A FEDEX SHIP VIA ................................................................................... 8
SETTING UP A FACILITY ............................................................................................. 9
SETTING UP A FEDEX CARRIER FACILITY .................................................................... 10

iv Copyright © 2019, Oracle and/or its affiliates. All rights reserved.


Send Us Your Comments

Oracle® Warehouse Management Cloud FedEx Parcel Integration, Update 18C

Oracle welcomes your comments and suggestions on the quality and usefulness of this publication.
Your input is an important part of the information used for revision.

• Did you find any errors?


• Is the information clearly presented?
• Do you need more information? If so, where?
• Are the examples correct? Do you need more examples?
• What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate the title and
part number of the documentation and the chapter, section, and page number (if available). You can
send comments to us in the following ways:

• Electronic mail: owms-cloud-comms_us@oracle.com


If you would like a reply, please give your name, address, telephone number, and electronic mail
address (optional).

If you have problems with the software, contact Support at https://support.oracle.com or find the
Support phone number for your region at http://www.oracle.com/support/contact.html.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. v


Preface
This document includes an overview of the Oracle Warehouse Management Cloud (WMS) APIs used for
Material Handling Equipment (MHE) configuration.

Change History
Date Document Revision Summary of Changes

02/2019 -01 Initial release.

vi Copyright © 2019, Oracle and/or its affiliates. All rights reserved.


1. Steps To Setup A FedEx Carrier
The following sections outline the steps for setting up FedEx for Parcel Integration.

1. Define the Carrier


2. Define the ShipVia
3. Define the Facility
4. Define the Carrier Facility

Setting Up A FedEx Carrier

1. You must fill in a valid address that actually exists. You cannot put in invalid data for testing.

Figure 1: Carrier UI

Note: if you put in a city or state it must actually exist in that country. Also note FedEx most likely
does not work in other foreign countries.

1. Make sure FedEx actually exists for the Foreign country you are trying to configure it for. If
you configure it for the United States then it will work.
2. You must set the phone number this is required.
3. All the fields you see filled in this example you should fill them in too.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. 7


Setting Up a FedEx Ship Via

1. Create a Code of your choosing.

Figure 2: Ship Via

2. Carrier must be defined before you can setup your ship via if you have not done this then you
have to go back and setup your carrier to link it to your ship via when you select your carrier.
3. The standard service must match and go with your Carrier. So make sure this makes sense if it
does not then it will not work because you will be sending options to the carrier that simply just
do not exist and then of course you will start getting errors.
4. The carrier webservice label type needs to be set either to ZPL or IMAGE. If you do not set this
field then it defaults to ZPL. If you are trying to print combo doc for packing slips then this will
be a problem and you must set it to IMAGE. If it is set to a ZPL then when our program tries to
read the ZPL code and tries to save it as an image it will fail because it is not an image. For all
other situations currently you would want ZPL and not an image.

8 Copyright © 2019, Oracle and/or its affiliates. All rights reserved.


Setting Up A Facility

1. Choose a code that makes sense for the company you are setting this up for.

Figure 3: Facilities

2. Put in the name of the companies facility location.


3. Choose for it to be a distribution center you would not choose a shop because you will be
shipping packages out from this facility which by definition makes it a distribution facility.
4. Put in the address this is required and it needs to be a real world address. Do not make up an
address that does not exist even for testing purposes.
5. Put in the City required again must be a real city and the city must exist within that state and
country.
6. Put in the State required again must be a real state with in that country.
7. Put in the Zip required again must be a real zip code that corresponds with the rest of the
address.
8. Put in the Country (should be a 2 letter code like US.)
9. Put in the Phone Number this is required.
10. Put in the Email Address this is required.
11. Put in the Priority of 0 if you do not know what to put.
12. Select the correct time zone this is required.
13. Select the parent company if this is a 3PL in which case this would also be required.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. 9


Setting Up A FedEx Carrier Facility

1. Select the facility that you defined in the previous step.

Figure 4: Carrier Facility

2. Select the carrier you defined in the previous step.


3. Integration type should be FedEx Services.
4. The company you are configuring FedEx Webservices for needs to get this information from Fed
Ex when they setup their account.
5. You will need an account number from the company you are configuring this for.
6. You will need the License or Meter Number from the company you are configuring this for. This
will be called the Access Key by FedEx.
7. Interface DB Name is not required for this setup.
8. WSDL Root Path will depend on if you are doing this for testing or production for testing the
path be the same as in the picture.

Testing:

1. $LGF_HOME/data/wsdl/FedEx/ship/test/

Production:

1. $LGF_HOME/data/wsdl/FedEx/ship/prod/
2. Input the Username required.
3. Input the Password required.
4. Hub is not required.

10 Copyright © 2019, Oracle and/or its affiliates. All rights reserved.