• Home
• ››Shipping Add On for B1
• ››Installation Guide for V33 Shipping

 

 

Configuring Add-on Settings

---

First published on: 04/01/2024/4:22 pm

 

 

Global settings are configurable from the Add-on Settings window. Shipping carrier settings may be configured using the “Configure Carriers” buttons.

General Settings

 

The General section of the add-on settings applies globally to the current SAP Business One company.

 

Field	Description
Configure Carriers (button)	Use this button to enable/disable carriers, and to configure connection details. Carriers must be configured before they can be used in address validation.
Documents Workflow (button)	Use this button to select the document workflow. It needs to be configured according to the integration with the carrier software. The options are: Sales Order --> Delivery Sales Order --> A/R Invoice Delivery --> A/R Invoice
Apply Shipping & Handling Fees	Use this section to configure additional shipping and handling fees. Sub-options:  As Flat Fee / as % of Shipping: This option indicates if charge will be fixed fee or based on a % of the actual freight charge. Per Package/Per Order: Set this option to indicate if the shipping and handling fees are per package or per order. Apply fees to: Select which additional expense to add the S&H charges to. Options in this list box are defined in the Additional Expenses setup. Amount: Indicates the fixed fee or the percentage to be applied.
Confirm import of shipping charges	Select this checkbox to receive a confirmation to apply shipping charges when clicking the Import Shipment button on a marketing document.  If unchecked, the shipping charges will be applied automatically.

 

 

Configure Carriers

To configure shipping carriers, press the Configure Carriers button. If a carrier is already set up, press the golden arrow drill-down to open the Edit Carrier Setup screen. Otherwise, use the “Add New Carrier” button to open the Carrier Configuration Details screen to create a new entry. 

 

On the Edit Carrier Setup details screen, fill in all fields that are relevant for the Carrier.

 

The Additional Properties section may be used to define special properties required by the carrier. For example, Public Key info or other carrier-specific settings.

 

Screenshots of setting up a FedEx Carrier is shown below:

1. Use the “Add New Carrier” button or press the golden arrow drill-down to open carrier details.

 

Fill in all information provided by the carrier, including any additional properties.

 

 

 

Field	Description
Code	Text field. Unique ID for the Carrier.
Name	Text field. Unique name for the Carrier, as displayed to Admins.

Carrier Type	Drop-down. Displays list of available shipping carriers. Out-of-the-box supported options are: FedEx UPS USPS
Account Number	Text field. As supplied by the carrier vendor.

User Id	Text field. As supplied by the carrier vendor.
Password	Text field. As supplied by the carrier vendor.
Developer Key	Text field. As supplied by the carrier vendor.
Meter Number	Text field. As supplied by the carrier vendor.
Access Key	Optional. Text field. As supplied by the carrier vendor.
Web Service URL	Text field. As supplied by the carrier vendor. Used to obtain address validation.

Enabled	Drop-down. When enabled, this carrier may be used to configure address validation. Options are: Y – Yes, enabled. N – No, not enabled.
Tracking URL	Text field. As supplied by the carrier vendor. Links to the vendor’s online tracking website.

Additional Properties

Additional properties may be used to assign extra details required by the carrier vendor. For example, a public key or extra account information.

 

Configure Documents Workflow

To configure the documents workflow press the Documents Workflow button. You will be presented with a new screen with three options. You must select the one that will be used for the integration with the carrier software.

 

Depending on the selected workflow, the Import Shipment and Shipping Details buttons will be enabled or disabled.  These buttons can be found on the V33 Shipping tab of marketing documents in SAP Business One.  The table below outlines the scenarios based on the workflow selected.

 

Document Workflow	Marketing Document	Import Shipment	Shipping Details
Sales Order -> Delivery	Sales Order	Yes	Yes
	Delivery Note	Yes (Add Mode)	Yes
	Invoice	No	Yes
Sales Order -> Invoice	Sales Order	Yes	Yes
	Delivery Note	No	Yes
	Invoice	Yes (Add Mode)	Yes
Delivery > Invoice	Sales Order	No	No
	Delivery Note	No	Yes
	Invoice	Yes (Add Mode)	Yes

 

Creating an ODBC Connection

To fully install Vision33 Shipping, the add-on must be configured to communicate with the external shipping application. This is completed via creating an ODBC connection that the shipping application will retrieve information about orders that are to be shipped.

 

To set up an ODBC connection, complete the following steps:

1. (Windows 7, 8 or 10) Open Administrative Tools. To do this, in the Start menu, search for “Administrative Tools”
2. Open “Data Sources (ODBC)”. Go to the “System DSN” tab (marker 1 below) and press the “Add…” button (marker 2 below).

 

3. In the “Create New Data Source” window, scroll to the bottom and select SQL Server. Press the “Finish” button to continue.

 

 

4. Fill in the details, as shown below. Note “Name” must be alpha-numeric only (no spaces or underscores), and “Description” is optional. Select a “Server” from the drop-down.

 

5. Configure the SQL Server Authentication details and press “Next”.

 

6. Press “Next”.

 

7. Press “Finish”.

 

8. Press the “Test Data Source” button to ensure the connection was successfully created. If a connection is confirmed, close all windows (Press OK).

 

HANA Specific Instructions for V33 Shipping

Create Shipping ROLE

--Create role for use with all V33SHIP HANA Users--Create role for use with all V33SHIP HANA Users

--Permit Canned Roles for  V33SHIPROLE for ODBC/JDBC Access

--Execute in HANA Studio --

CREATE ROLE V33SHIPROLE;

GRANT RESTRICTED_USER_ODBC_ACCESS, RESTRICTED_USER_JDBC_ACCESS TO V33SHIPROLE;

CALL _SYS_REPO.GRANT_ACTIVATED_ROLE ('sap.hana.ide.roles::CatalogDeveloper', 'V33SHIPROLE');

--End Execute –

Create Shipping User

--Create User - Change password to something else - new user should be created for each MTE Tenant/Customer

--Execute in HANA Studio --

CREATE RESTRICTED USER V33SHIPDUS password V1si0nE3 NO FORCE_FIRST_PASSWORD_CHANGE;

ALTER USER V33SHIPDUS DISABLE PASSWORD LIFETIME;

--End Execute –

 

Grant Access to Required Tables

--Grant objects for user depending on Tenant/Customer

--Execute in HANA Studio --

GRANT SELECT,UPDATE,DELETE ON ""<SBODEMOUS>"."ODLN" TO "V33SHIPDUS" WITH GRANT OPTION; 

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."ORDR" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."OSHP" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."RDR12" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."OCRD" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."OCPR" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."@V33_SHIP_PLD" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."DLN12" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."DLN7" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT,UPDATE,DELETE ON "<SBODEMOUS>"."OPKG" TO "V33SHIPDUS" WITH GRANT OPTION;

--End Execute –

 

Create Views Within Company Schema

Using SYSTEM (or equivalent) User in New Schema that Point to the Company Database Tables

 

V33_VW_ORDERADDR

--Execute in HANA Studio --

CREATE VIEW "<SBODEMOUS>"."V33_VW_ORDERADDR" (

"DOCNUM",

"CARDNAME",

"ADDR1",

"ADDR2",

"ADDR3",

"CITY",

"STATE",

"ZIP",

"COUNTRY",

"CONTACT",

"PHONE",

"E_MAIL",

"E_MAILYNE",

"E_MAILE",

"TRNSPCODE",

"TRNSPNAME",

"DOCTOTAL",

"DECVALUE",

"DECIND",

"BILLING",

"ACCOUNTNUMBER",

"RESIDENTIAL",

"CODYN",

"CUSTREFNUM" ) AS select

"ORDR"."DocNum" AS "DOCNUM",

"ORDR"."CardName" AS "CARDNAME",

"RDR12"."StreetS" AS "ADDR1",

"RDR12"."BlockS" AS "ADDR2",

"RDR12"."BuildingS" AS "ADDR3",

"RDR12"."CityS" AS "CITY",

"RDR12"."StateS" AS "STATE",

"RDR12"."ZipCodeS" AS "ZIP",

(case when "RDR12"."CountryS" like 'USA' then ''

else "RDR12"."CountryS" end) AS country,

"OCPR"."Name" as "CONTACT",

"OCPR"."Tel1" as "PHONE",

(ifnull("OCPR"."E_MailL",

"OCRD"."E_Mail")) as "E_MAIL",

(case when (ifnull("OCPR"."E_MailL",

"OCRD"."E_Mail")) > ''

then 'Y' else ''

end) as "E_MAILYNE",

(case when (ifnull("OCPR"."E_MailL",

"OCRD"."E_Mail")) > '' then 'E-MAIL' else '' end) as "E_MAILE",

"@V33_SHPSVCTYPES"."U_SvcCode" as "TrnspCode",

"OSHP"."TrnspName" AS "TRNSPNAME",

"DocTotal" AS "DOCTOTAL",

"U_V33_ShpDecVal" as "DECVALUE",

(CASE WHEN "ORDR"."U_V33_Insurance" = 'Y'

THEN 'Y'

ELSE 'N'

END) AS "DECIND",

(case when "ORDR"."U_V33_ShpAcctNo" > '' then 'FREIGHT COLLECT' else '' end) as "BILLING",

"ORDR"."U_V33_ShpAcctNo" as "ACCOUNTNUMBER", (case when "ORDR"."U_V33_ShpComRes" = 'R' then 'Y' else 'N'

end) as "RESIDENTIAL",

"ORDR"."U_V33_Cod" as "CODYN",

"ORDR"."NumAtCard" as "CUSTREFNUM"

from "<SBODEMOUS>"."ORDR"

INNER JOIN "<SBODEMOUS>"."OSHP" ON "ORDR"."TrnspCode" = "OSHP"."TrnspCode"

LEFT OUTER JOIN "<SBODEMOUS>"."RDR12" ON "ORDR"."DocEntry" = "RDR12"."DocEntry" INNER JOIN "<SBODEMOUS>"."OCRD" ON "ORDR"."CardCode" = "OCRD"."CardCode"

LEFT OUTER JOIN "<SBODEMOUS>"."OCPR" ON "ORDR"."CntctCode" = "OCPR"."CntctCode"

AND "ORDR"."CardCode" = "OCPR"."CardCode"

LEFT JOIN "<SBODEMOUS>"."@V33_SHPSVCTYPES" on "<SBODEMOUS>"."@V33_SHPSVCTYPES"."Code" = "<SBODEMOUS>"."OSHP"."U_V33_SvcCode"

where "ORDR"."DocStatus" = 'O';

--End Execute –

 

 

If the document workflow selected is Delivery Notes à Invoices, then the view should be something like this:

--Execute in HANA Studio --

CREATE VIEW "<SBODEMOUS>"."V33_VW_DELIVERYADDR" ( "DOCNUM",

 "CARDNAME",

 "ADDR1",

 "ADDR2",

 "ADDR3",

 "CITY",

 "STATE",

 "ZIP",

 "COUNTRY",

 "CONTACT",

 "PHONE",

 "E_MAIL",

 "E_MAILYNE",

 "E_MAILE",

 "TRNSPCODE",

 "TRNSPNAME",

 "DOCTOTAL",

 "DECVALUE",

 "DECIND",

 "BILLING",

 "ACCOUNTNUMBER",

 "RESIDENTIAL",

 "CODYN",

 "CUSTREFNUM" ) AS select

 "ODLN"."DocNum" AS "DOCNUM",

 "ODLN"."CardName" AS "CARDNAME",

 "DLN12"."StreetS" AS "ADDR1",

 "DLN12"."BlockS" AS "ADDR2",

 "DLN12"."BuildingS" AS "ADDR3",

 "DLN12"."CityS" AS "CITY",

 "DLN12"."StateS" AS "STATE",

 "DLN12"."ZipCodeS" AS "ZIP",

 (case when "DLN12"."CountryS" like 'USA'

then ''

else "DLN12"."CountryS"

end) AS country,

 "OCPR"."Name" as "CONTACT",

 "OCPR"."Tel1" as "PHONE",

 (ifnull("OCPR"."E_MailL",

 "OCRD"."E_Mail")) as "E_MAIL",

 (case when (ifnull("OCPR"."E_MailL",

 "OCRD"."E_Mail")) > ''

then 'Y'

else ''

end) as "E_MAILYNE",

 (case when (ifnull("OCPR"."E_MailL",

 "OCRD"."E_Mail")) > ''

then 'E-MAIL'

else ''

end) as "E_MAILE",

 --"OSHP"."TrnspCode" AS "TRNSPCODE",

 "@V33_SHPSVCTYPES"."U_SvcCode" as "TrnspCode",

 "OSHP"."TrnspName" AS "TRNSPNAME",

 "DocTotal" AS "DOCTOTAL",

 "U_V33_ShpDecVal" as "DECVALUE",

 (CASE WHEN "ODLN"."U_V33_Insurance" = 'Y'

THEN 'Y'

ELSE 'N'

END) AS "DECIND",

 (case when "ODLN"."U_V33_ShpAcctNo" > ''

then 'FREIGHT COLLECT'

else ''

end) as "BILLING",

 "ODLN"."U_V33_ShpAcctNo" as "ACCOUNTNUMBER",

 (case when "ODLN"."U_V33_ShpComRes" = 'R'

then 'Y'

else 'N'

end) as "RESIDENTIAL",

 "ODLN"."U_V33_Cod" as "CODYN",

 "ODLN"."NumAtCard" as "CUSTREFNUM"

from "<SBODEMOUS>"."ODLN"

INNER JOIN "<SBODEMOUS>"."OSHP" ON "ODLN"."TrnspCode" = "OSHP"."TrnspCode"

LEFT OUTER JOIN "<SBODEMOUS>"."DLN12" ON "ODLN"."DocEntry" = "DLN12"."DocEntry"

INNER JOIN "<SBODEMOUS>"."OCRD" ON "ODLN"."CardCode" = "OCRD"."CardCode"

LEFT OUTER JOIN "<SBODEMOUS>"."OCPR" ON "ODLN"."CntctCode" = "OCPR"."CntctCode"

AND "ODLN"."CardCode" = "OCPR"."CardCode"

LEFT JOIN "<SBODEMOUS>"."@V33_SHPSVCTYPES" on "<SBODEMOUS>"."@V33_SHPSVCTYPES"."Code" = "<SBODEMOUS>"."OSHP"."U_V33_SvcCode"

where "ODLN"."DocStatus" = 'O' WITH READ ONLY

--End Execute –

 

 

For both V33_VW_DELIVERYADDR and V33_VW_ORDERADDR, if you need the service type populated automatically in the carrier software, then you need to complete the UDFs in the OSHP table and modify the view in order to use them in the mapping.

 

 

The view should look like this

 

               "@V33_SHPSVCTYPES"."U_SvcCode" as "TRNSPNAME", 

 

The FedEx software can create mappings depending on the contents of the view. It is especially important for the UPS WorldShip software to have the correct values to automatically populate this field.

 

V33_VW_DELIVERYPKGINFO

--Execute in HANA Studio --

CREATE VIEW "<SBODEMOUS>"."V33_VW_DELIVERYPKGINFO" ( "DOCNUM",

 "PACKAGETYP",

 "WEIGHT",

 "LENGTH",

 "WIDTH",

 "HEIGHT",

 "PACKAGENUM",

 "NUMACKAGES" ) AS SELECT

 T1."DocNum" as DocNum,

 T0."PackageTyp",

 T0."Weight" AS Weight,

 T3."Length1" AS Length,

 T3."Width1" AS Width,

 T3."Height1" AS Height,

 T0."PackageNum",

 T2."NumPackages"

FROM "<SBODEMOUS>"."DLN7" T0

INNER JOIN "<SBODEMOUS>"."ODLN" T1 ON "T1"."DocEntry" = "T0"."DocEntry"

INNER JOIN "<SBODEMOUS>"."OPKG" T3 ON "T0"."PackageTyp" = "T3"."PkgType"

INNER JOIN (SELECT

 "T0"."DocEntry",

 MAX("T0"."PackageNum") "NumPackages"

FROM "<SBODEMOUS>"."DLN7" T0

GROUP BY "T0"."DocEntry") T2 ON "T2"."DocEntry" = "T1"."DocEntry"

WHERE "T1"."DocStatus" = 'O' WITH READ ONLY

--End Execute –

 

V33_VW_SHIP_PLD

--Execute in HANA Studio --

CREATE VIEW "<SBODEMOUS>"."V33_VW_SHIP_PLD" ( "CODE",

 "NAME",

 "U_DOCNUM",

 "U_PACKNUM",

 "U_WEIGHT",

 "U_COST",

 "U_ADDCHARGE",

 "U_TRACKNUM",

 "U_SHIPDATE",

 "U_CODCHARGE",

 "U_VOIDYN",

 "U_SHIPYN",

 "U_SHCHARGE",

 "U_SHIPPERCOST",

 "U_PKGNUMBER",

 "U_DISCOUNTRATE",

 "U_INSURECHARGE" ) AS select

 T0."Code" AS "CODE",

 T0."Name" AS "NAME",

 T0."U_DocNum" AS "U_DOCNUM",

 T0."U_PackNum" AS "U_PACKNUM",

 T0."U_Weight" AS "U_WEIGHT",

 T0."U_Cost" AS "U_COST",

 T0."U_AddCharge" AS "U_ADDCHARGE",

 T0."U_TrackNum" AS "U_TRACKNUM",

 T0."U_ShipDate" AS "U_SHIPDATE",

 T0."U_CODCharge" AS "U_CODCHARGE",

 T0."U_VoidYN" AS "U_VOIDYN",

 T0."U_ShipYN" AS "U_SHIPYN",

 T0."U_SHCharge" AS "U_SHCHARGE",

 T0."U_ShipperCost" AS "U_SHIPPERCOST",

 T0."U_PKGNumber" AS "U_PKGNUMBER",

 T0."U_DiscountRate" AS "U_DISCOUNTRATE",

 T0."U_InsureCharge" AS "U_INSURECHARGE"

from "<SBODEMOUS>"."@V33_SHIP_PLD" T0

--End Execute –

 

Grant Access to Required View(s) to V33SHIP HANA User

--After V33Ship workflow View creation

--Execute in HANA Studio --

GRANT SELECT ON "<SBODEMOUS>"."V33_VW_ORDERADDR" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT ON "<SBODEMOUS>"."V33_VW_DELIVERYPKGINFO" TO "V33SHIPDUS" WITH GRANT OPTION;

GRANT SELECT ON "<SBODEMOUS>"."V33_VW_SHIP_PLD" TO "V33SHIPDUS" WITH GRANT OPTION;

--End Execute –

 

 

Test HANA User and Granted Objects

In Chrome go to https://<hanaserver>:8000/sap/hana/ide/catalog

 

Login with V33Ship HANA User

 

Expand Schema objects and verify objects are listed and can be queried

 

 

Create ODBC Connection

Create ODBC connection to HANA (same as previous ODBC section above) from the workstation/server that hosts the carrier software.  Use the new V33SHIP user that was created to authenticate.

 

Import Mappings for UPS Worldship

The screenshot below is an example. Your system may need slightly different mappings.

 

Use the New V33SHIP HANA User (example: V33SHIPDUS) to configure mappings used during data import from SAP Business One, select “v33_vw_OrderAddr” on the ODBC Tables and the appropriate fields in UPS WorldShip. Once the two fields are selected, hit “Connect” and they will show at the bottom of the screen as “What You Have Mapped So Far”. 

 

A full list of mapped fields is provided below.

 

 

Map Name: SAPtoUPSImport

Map Information

Field	Details
Map Type	Shipment
Primary Table  SAP Table SQL view	v33_vw_OrderAddr
Primary Key	docnum
Prompt for table name	No

 

 

Field Mappings for UPS WorldShip (B1 to UPS)

Note: blank fields indicate that these do not require a mapping.

 

ODBC Data Source Field (Table::Field)	WorldShip Field (Container::Field)
V33_vw_OrderAddr::addr1	Ship To::Address 1
V33_vw_OrderAddr::addr2	Ship To::Address 2
V33_vw_OrderAddr::addr3	Ship To::Address 3
V33_vw_OrderAddr::CardName	Ship To::Company or Name
V33_vw_OrderAddr::city	Ship To::City or Town
V33_vw_OrderAddr::CODYN	Package::COD Option
V33_vw_OrderAddr::Contact	Ship To::Attention
V33_vw_OrderAddr::Country	Ship To::Country/Territory
V33_vw_OrderAddr::CustRefNum	Package::Reference 2
V33_vw_OrderAddr::DecInd	Package::Declared Value Option
V33_vw_OrderAddr::DecValue	Package::Declared Value Amount
V33_vw_OrderAddr::docnum	Shipment Information::Special Instructions for Shipment
V33_vw_OrderAddr::docnum	Package::Reference 1
V33_vw_OrderAddr::doctotal	Package::COD Amount
V33_vw_OrderAddr::E_Mail	Ship To::Email Address
V33_vw_OrderAddr::Phone	Ship To::Telephone
ODBC Data Source Field (Table::Field)	WorldShip Field (Container::Field)
V33_vw_OrderAddr::Residential	Ship To::Residential Indicator
V33_vw_OrderAddr::state	Ship To::State/Province/County
V33_vw_OrderAddr::TrnspName	Shipment Information::Service Type
V33_vw_OrderAddr::zip	Ship To::Postal Code

 

Choose the ODBC Data source fields and the relevant WorldShip fields and connect them. Once the connections are done as per the above table, select the docnum Column name and click the Define Primary Key for Import button.

 

 

 

Export Mappings for UPS WorldShip

The screenshot below is an example. Your system may need slightly different mappings.

 

To configure mappings used during data export back to SAP Business One, select “V33_VW_SHIP_PLD” on the ODBC Tables and the appropriate fields in UPS WorldShip. 

 

Once the two fields are selected, hit “Connect” and they will show at the bottom of the screen as “What You Have Mapped So Far”.

 

 

Map Name: UPStoSAPExport

 

 

Map Information

Field	Details
Map Type	Shipment
Primary Table  SAP Table to Map to	V33_VW_SHIP_PLD
Primary Key	(none)
Prompt for table name	No
Field Mappings for UPS WorldShip (UPS to B1)
WorldShip Field (Container::Field)		ODBC Data Source Field (Table::Field)
Shipment Information::Handling Charge Flat Rate		V33_VW_SHIP_PLD::U_AddCharge
Shipment Information::COD Amount		V33_VW_SHIP_PLD::U_CODCharge
Package::Package Published Charge		V33_VW_SHIP_PLD::U_Cost
Shipment Information::Special Instructions for Shipment		V33_VW_SHIP_PLD::U_DocNum
Shipment Information::Number of Packages		V33_VW_SHIP_PLD::U_PackNum
Shipment Information::Collection Date		V33_VW_SHIP_PLD::U_ShipDate
Package::Tracking Number		V33_VW_SHIP_PLD::U_TrackNum
Shipment Information::Void Indicator		V33_VW_SHIP_PLD::U_VoidYN
Shipment Information::Billable Weight		V33_VW_SHIP_PLD::U_Weight
Package:: Tracking Number		V33_VW_SHIP_PLD::Name
Package:: Tracking Number		V33_VW_SHIP_PLD::Code

 Configure the system to utilize discounted rates/list rates

 

 

To configure the system to utilize discounted rates (or) list rates, the following mappings should be used:

WorldShip Field (Container::Field)	ODBC Data Source Field (Table::Field)
Shipment Information::Handling Charge Flat Rate	V33_VW_SHIP_PLD::U_AddCharge
Shipment Information::COD Amount	V33_VW_SHIP_PLD::U_CODCharge
Package::Package Reference Charge	V33_VW_SHIP_PLD::U_Cost
Shipment Information::Special Instructions for Shipment	V33_VW_SHIP_PLD::U_DocNum
Shipment Information::Number of Packages	V33_VW_SHIP_PLD::U_PackNum
Shipment Information::Collection Date	V33_VW_SHIP_PLD::U_ShipDate
Package::Tracking Number	V33_VW_SHIP_PLD::U_TrackNum
Shipment Information::Void Indicator	V33_VW_SHIP_PLD::U_VoidYN
Shipment Information::Billable Weight	V33_VW_SHIP_PLD::U_Weight
Package:: Tracking Number	V33_VW_SHIP_PLD::Name
Package:: Tracking Number	V33_VW_SHIP_PLD::Code

 

 

Import Mappings for FedEx Shipping Manager

Open the FedEx Integration Assistant from the Integration menu on the menu bar. 

 

 

1. On the FedEx Integration Assistant, navigate to the Import tab
2. Navigate to the Information sub menu under Import menu.
3. The Recipient, Package and Special Services must be imported from SAP B1 into the FedEx integration Assistant.

 

Click on the Recipient, Package and Special services to bring up their respective windows. Check all the fields as shown in the figure and click OK to save changes.

 

 

 

 

 

Navigate to the Match sub-menu under the Import menu. The table must be selected from the data source prior to matching the FedEx Ship Manager fields. On the drop-down menu to the left, select V33_vw_OrderAddr. Drag the Fields to match as per the following figure:

 

 

 

Map Information

 

Field	Details
Map Type	Shipment
Primary Table  SAP Table SQL view	v33_vw_OrderAddr
Primary Key	docnum
Prompt for table name	No

 

Field Mappings for FedEx Ship Manager (B1 to FedEx)

ODBC Data Source Field (Table::Field)	FedEx Ship Manager Field (Container::Field)
V33_vw_OrderAddr::addr1	Recipient::Address 1
V33_vw_OrderAddr::city	Recipient::City
V33_vw_OrderAddr::CardName	Recipient::Company
V33_vw_OrderAddr::country	Recipient::Country
V33_vw_OrderAddr::zip	Recipient::Postal Code
V33_vw_OrderAddr::state	Recipient::State/Province
V33_vw_OrderAddr::docnum	Recipient::Customer Reference
V33_vw_OrderAddr::CustRefNum	Package::P.O. Number
V33_vw_OrderAddr::TrnspNam	Package::Service Type
V33_vw_OrderAddr::CODYN	Special Services::COD Flag

 

 

Export mappings for FedEx Ship Manager

1. On the FedEx Integration Assistant, Navigate to the Export tab.
2. Navigate to the Information sub menu under Import menu. 
3. The Tracking Numbers, Charges, Package and Special Services need to be exported from FedEx integration Assistant into the SAP B1.

 

 

Click on Tracking Numbers, Charges, Package and Special Services to open the respective window. Check the following fields and Click OK to save.

 

 

 

 

 

 

 

 

Navigate to the Match sub-menu under the Export menu. The table must be selected from Your Data Fields prior to matching the FedEx Ship Manager fields. On the drop-down under Your Data Fields, select V33_VW_SHIP_PLD. Drag the Fields to match as per the following table:

 

Field Mappings for FedEx Ship Manager (FedEx to B1)

 

Map Information

 

Field	Details
Map Type	Shipment
Primary Table  SAP Table to Map to	V33_VW_SHIP_PLD
Primary Key	(none)
Prompt for table name	No
Field Mappings for FedEx Ship Manager (B1 to FedEx)
FedEx Ship Manager Field (Container::Field)		ODBC Data Source Field (Table::Field)
Tracking Numbers::Track Num		V33_VW_SHIP_PLD::Tracking
Tracking Numbers::Track Num		V33_VW_SHIP_PLD::Code
Tracking Numbers::Track Num		V33_VW_SHIP_PLD::Name
Charges-Customer Rates::Total Customer Charge		V33_VW_SHIP_PLD::U_Cost
Package::Customer Reference		V33_VW_SHIP_PLD::DocNum
Package::Ship Date		V33_VW_SHIP_PLD::Ship Date
Package::Weight		V33_VW_SHIP_PLD::Weight
Package::Number of Packages		V33_VW_SHIP_PLD::Pack Num
Delete Indicator::Delete Indicator		V33_VW_SHIP_PLD::VoidYN

Configure the system to utilize discounted rates/list rates

 

To configure the system to utilize discounted rates (or) list rates, the following mappings should be used:

FedEx Ship Manager Field (Container::Field)	ODBC Data Source Field (Table::Field)
Tracking Numbers::Track Num	V33_VW_SHIP_PLD::Tracking
Tracking Numbers::Track Num	V33_VW_SHIP_PLD::Code
Tracking Numbers::Track Num	V33_VW_SHIP_PLD::Name
Charges-List Rates:: Total Customer Charge	V33_VW_SHIP_PLD:: U_Cost
Package::Customer Reference	V33_VW_SHIP_PLD::DocNum
Package::Ship Date	V33_VW_SHIP_PLD::Ship Date
Package::Weight	V33_VW_SHIP_PLD::Weight
Package::Number of Packages	V33_VW_SHIP_PLD::Pack Num
Delete Indicator::Delete Indicator	V33_VW_SHIP_PLD::VoidYN

 

 

Import mappings for USPS in Endicia Professional

To configure Data Import into Endicia, Open the Endicia application and navigate to Edit->Preferences.

 

This opens a preferences window, select the Data Sources and Post-Back tab and use the Configure button to open the Order Lookup mappings. Click on New in the Data Source field.

 

 

This will open a Create New Data Source window.

 

 

Choose ODBC Connection from the Shipping data connection method.

 

 

Select the ODBC Data Source and Enter the User name and Password credentials. Follow the Steps below:

 

 

Click on Next to bring up the Create a SELECT Statement, this will map the first field from the database to Endicia.

 

 

 

Click on next and choose DOCNUM for the Order Number Field.

 

 

 

A data source for Importing from SAP Business One is required. See screenshots and the mapping table below. Map the ODBC fields with the Endicia fields as shown.

 

Map Information

 

Field	Details
Map Type	Shipment
Primary Table  SAP Table  SQL view	v33_vw_OrderAddr
Primary Key	docnum
Prompt for table name	No

 

Field Mappings for USPS n Endicia (B1 to USPS)

 

ODBC Data Source Field (Table::Field)	Endicia Field (connected field tab::field)
V33_vw_OrderAddr::docnum	Package Details::Order Number
V33_vw_OrderAddr::CustRefNum	Package Details::Reference ID 2
V33_vw_OrderAddr::DecValue	Package Details::Value
V33_vw_OrderAddr::Contact	Recipient Address::Name
V33_vw_OrderAddr::CardName	Recipient Address::Company
V33_vw_OrderAddr::addr1	Recipient Address::Address 1
V33_vw_OrderAddr::addr2	Recipient Address::Address 2
ODBC Data Source Field (Table::Field)	Endicia Field (connected field tab::field)
V33_vw_OrderAddr::addr3	Recipient Address::Address 3
V33_vw_OrderAddr::city	Recipient Address::City
V33_vw_OrderAddr::state	Recipient Address::State
V33_vw_OrderAddr::zip	Recipient Address::Postal Code
V33_vw_OrderAddr::Country	Recipient Address::Country
V33_vw_OrderAddr::E_Mail	Recipient Address::Email
V33_vw_OrderAddr::Phone	Recipient Address::Phone

 

 

Click OK once the Order Lookup Data Map fields are connected. The Order Lookup Data Map should look like this:

 

 

 

Click OK to save the Data Map and connected fields. This should automatically Connect the Batch Print. If not connected, Configure the Batch Print from the Data Source and Post-Back from Preferences.

 

 

Export mappings for USPS in Endicia Professional  

To configure Data Export from Endicia, Open the Endicia application and navigate to Edit->Preferences. This opens the preferences window, select the Data Sources and Post-Back tab and use the Configure button to open the Post Back Data Map mappings. Click on to create a new data source for Post Back data. 

 

 

Select a data source

 

 

Click Ok to complete the connection.

 

 

 

 

Select the dbo.V33_VW_SHIP_PLD from the Table and map the following fields under Package Details.

 

Map Information

Field	Details
Map Type	Shipment
Primary Table		V33_VW_SHIP_PLD SAP Table to Map to
Primary Key		(none)
Prompt for table name		No

 

Field Mappings for USPS n Endicia (B1 to USPS)

 

Endicia Field (connected field tab::field)		ODBC Data Source Field (Table::Field)
Package details::Order Number		V33_VW_SHIP_PLD::U_Doc Num
Package details::Postage Amount		V33_VW_SHIP_PLD:: U_Cost
Package details::Tracking Number		V33_VW_SHIP_PLD:: U_TrackNum
Package details::Postmark Date		V33_VW_SHIP_PLD:: U_Ship Date
Package details::Actual Weight		V33_VW_SHIP_PLD:: U_Weight
Package details:: Tracking Number		V33_VW_SHIP_PLD:: Code
Package details:: Tracking Number		V33_VW_SHIP_PLD:: Name

 

 

Field Mappings for USPS n Endicia (B1 to USPS)

Endicia Field (connected field tab::field)	ODBC Data Source Field (Table::Field)
Package details::Order Number	V33_VW_SHIP_PLD::U_Doc Num
Package details::Postage Amount	V33_VW_SHIP_PLD:: U_Cost
Package details::Tracking Number	V33_VW_SHIP_PLD:: U_TrackNum
Package details::Postmark Date	V33_VW_SHIP_PLD:: U_Ship Date
Package details::Actual Weight	V33_VW_SHIP_PLD:: U_Weight
Package details:: Tracking Number	V33_VW_SHIP_PLD:: Code
Package details:: Tracking Number	V33_VW_SHIP_PLD:: Name

 

Click on Postmark Date button to bring up the date and time format. Enter the required Date and Time format as shown:

 

 

Previous

Next

---

  

Last modified: 04/01/2024/7:14 pm