+2We’re using Shipments in IFS to be able to consolidate lines from different customer orders that are shipping to the same customer location, that could all ship together to save our customers some freight costs. We’ve been trying to get IFS to send the customer order number, listed on the Shipment page on the Shipment Lines tab as “Source Ref 1” and to date, we have had no success.
Has anyone had any success with getting fields mapped from the Shipment page over into PaceJet?
If I recall correctly, natively the Source Ref 1 of the 1st customer order connected to the Shipment is sent to Pacejet.
Where are you expecting the individual Source Ref 1 values to be visible in Pacejet?
+2
If I recall correctly, natively the Source Ref 1 of the 1st customer order connected to the Shipment is sent to Pacejet.
Where are you expecting the individual Source Ref 1 values to be visible in Pacejet?
I’ve successfully mapped data from other pages as well, just can’t get that data to go from the Shipment. I thought it was supposed to, I’ve tried all kinds of mappings to try and get it to go, but nothing shows up in the API log.
We’re wanting Source Ref 1 of the 1st Customer Order connect to the Shipment to show up in the Order field under the Shipment header in PaceJet.
We’re also trying to get the PO to show up as well, but I think we’ll have to add a custom field to the Shipment page in IFS to be able to make that happen. I can’t find any logic that would know what PO number to grab from what customer order when using the shipments function like this.
Are you able to share some screenshots of the messsage mapping row in IFS and the destination in Pacejet?
As you may be aware, the data attribute will not show up in the API log if there isn’t a valid corresponding attribute on the Pacejet side. In the past I’ve encountered this issue a handful of times because the current API version that Pacejet is using is much newer than the API version that the Freight Integration was built on.
Unfortunately, I don’t currently have access to a reference environment that I can see the Freight Integration module in IFS as well as the a test Pacejet instance so this feedback in based on memory and my notes.
+2
Are you able to share some screenshots of the messsage mapping row in IFS and the destination in Pacejet?
As you may be aware, the data attribute will not show up in the API log if there isn’t a valid corresponding attribute on the Pacejet side. In the past I’ve encountered this issue a handful of times because the current API version that Pacejet is using is much newer than the API version that the Freight Integration was built on.
Unfortunately, I don’t currently have access to a reference environment that I can see the Freight Integration module in IFS as well as the a test Pacejet instance so this feedback in based on memory and my notes.
Screenshots are attached.
The highlighted fields are what we’re trying to get paired together.
Everything else in my message mapping works correctly. These lines were the defaults that were loaded with our initial integration of IFS before it was handed over to me to deal with. I’ve tried a variety of message mapping combinations, but it seems to me that my Message Level will have to be Shipment, and my Source Field Type needs to be either Order Value or Order Custom Field, based on the description of those field types.. “Field from the first/primary Customer Order on Shipment”
Currently, when I make my API call, in the attached API log is where I’d expect to see that data showing up, next to the other custom fields for the HsnSacCode and COO data points. But it’s not even displaying the Name of the field and a value of Null if it was sending the data and just not mapped to the correct field.
Thanks for the screenshots.
As you mentioned, those two highlighted rows are apart of the core integratation between IFS and PaceJet, they won’t be visibile in the Custom Fields section of the outgoing message.
Instead you should see them higher up in the API log towards the beginning of the outgoing message.
Are those empty or do you see a value?
+2Thanks for the screenshots.
As you mentioned, those two highlighted rows are apart of the core integratation between IFS and PaceJet, they won’t be visibile in the Custom Fields section of the outgoing message.
Instead you should see them higher up in the API log towards the beginning of the outgoing message.
Are those empty or do you see a value?
Those areas are all empty as well.
Basically, all the import APIs show the same thing after the Location, Destination, and Billing fields. They all show this:
"ShipmentDetail": {
"UserField8": "DEVDB",
"weightUOM": "LB",
"ShipmentOptions": {},
"LTLOptions": {}
},
"MessageList": [],
If you process a Shipment with only one Customer Order, is a value populated for Source Ref 1 and Customer PO Number in the file?
If the issue is isolated to multiple customer orders, I’d recommend reviewing the code within Developer Studio with your technical team or you can submit a support case to IFS. For the latter route, I’d recommend indicating this is the Freight Integration specifically for the North American market which will allow for better traction.
Alternatively, as you did with the custom fields, you could create new custom fields in IFS and Pacejet then use a copy field rule in Pacejet to copy the data to the Order and Purchase Order fields.
+2If you process a Shipment with only one Customer Order, is a value populated for Source Ref 1 and Customer PO Number in the file?
If the issue is isolated to multiple customer orders, I’d recommend reviewing the code within Developer Studio with your technical team or you can submit a support case to IFS. For the latter route, I’d recommend indicating this is the Freight Integration specifically for the North American market which will allow for better traction.
Alternatively, as you did with the custom fields, you could create new custom fields in IFS and Pacejet then use a copy field rule in Pacejet to copy the data to the Order and Purchase Order fields.
That was the hope, but nothing shows up in that case either.
I did open a case with IFS Support and was told that since we’re utilizing shipments, and not the standard integration to ship from the customer order screen, it would be a custom case to be handled by IFS Consultancy Services.
We are going to explore the path of creating new custom fields on the Shipment page that we can attempt to map successfully for resolution. PaceJet support told me to reach back out to them once I was able to get data to show up in the API log and they can assist in mapping it to the correct field on their side if necessary.
Thanks for your replies! Just wanted to be sure this was our route to go for now!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
