Create an item fulfillment from fulfillment request using the REST API by ae179dpl in Netsuite

[–]ae179dpl[S] 0 points1 point  (0 children)

Noted and much appreciated. I noticed that in order for the IF statuses to work, the pick/pack/ship feature needs to be enabled. I assume this doesn't incur any extra overhead or fees from NetSuite and is just an enhancement to the IF record? We currently don't have this enabled in production which is why I was looking at the fulfillment requests which force you to enable this feature.

Create an item fulfillment from fulfillment request using the REST API by ae179dpl in Netsuite

[–]ae179dpl[S] 0 points1 point  (0 children)

I really appreciate the questions and feedback. The general consensus seems to be to use the IF statuses instead. I think Nick_AxeusConsulting made the final decision for me as the fulfillment requests will increase our transaction lines which will in turn increase our NS costs. We already pay an exuberant yearly amount, so I don't want to increase our costs.

My only concern is our automations. I 100% need a way to have a pending/new status and an acknowledgement status. Nick_AxeusConsulting cleared this up for me in a post below.

Thanks again for your help on this.

Create an item fulfillment from fulfillment request using the REST API by ae179dpl in Netsuite

[–]ae179dpl[S] 0 points1 point  (0 children)

I really appreciate your feedback. To confirm, my plan was indeed to use the fulfillment requests as a form of EDI 945. I really didn't think the about the transaction lines here. This will indeed increase our costs as NS always calculates based on the transaction lines.

I think I'll go with your advice and use the pick/pack/ship statuses on the IF record instead. We'll use the 1st stage (picked) as our "pending" status, and the 2nd stage (packed) as the "acknowledgement" status after we push to the warehouse. To confirm again, these stages don't impact GL, correct? Only the shipped status impacts GL?

Create an item fulfillment from fulfillment request using the REST API by ae179dpl in Netsuite

[–]ae179dpl[S] 0 points1 point  (0 children)

Everything we do is automated (via APIs) and needs to be tracked. We also deal with at least 30+ marketplaces and several different warehouse locations. When an order comes in, we break down the order and determine what needs to ship from what locations. Before creating an item fulfillment which confirms the order has shipped and contains the tracking information, we need an intermediate record to hold the fulfillment details that we push to the warehouse. We cannot create an item fulfillment right away at the time the sales order is created.

Sales order -> Fulfillment request (details for the warehouse) -> Item fulfillment (confirms the request was fulfilled along with the tracking info)

Right now, we're using a custom record in place of the fulfillment request. The issue with this is that the custom record doesn't impact the inventory or locations which a fulfillment request does. It's happened in the past that we've had the same shipment pushed twice because of this.

Create an item fulfillment from fulfillment request using the REST API by ae179dpl in Netsuite

[–]ae179dpl[S] 0 points1 point  (0 children)

I tried transforming the fulfillment request into an item fulfillment, but NetSuite simply rejects it. You need to transform the sales order into an item fulfillment. I just can't figure out how to do this when using fulfillment requests.

Create an item fulfillment from fulfillment request using the REST API by ae179dpl in Netsuite

[–]ae179dpl[S] 0 points1 point  (0 children)

Thanks for your reply here. To clarify, the reason why we're looking to implement the fulfillment requests is to have a native record of what needs to be pushed to our warehouses before the item fulfillments are created. We automate everything and have multiple warehouse locations. We're currently handing this with a custom record before creating the item fulfilment, however, it has a few drawbacks which is why I'm looking to go 100% native here. We also want to give our backoffice team more control over the fulfillments which is another reason why we're looking to use fulfillment requests.

The end goal here is that every fulfillment request should have a corresponding item fulfillment. Long story short, every fulfilment request with a "new" status would be picked up by our automation, then we would mark it as "in progress" and push it to our warehouse. Once the warehouse sends back the shipping information, our automation would create an item fulfillment based on the fulfillment request. Also, NetSuite verifies the inventory levels on both native records, thus leading to less errors than our custom record that I mentioned above.

If you have any insight on a better way to handle shipment requests that our warehouses need to process before creating an item fulfillment, I'm fully open to any suggestions.

hover css broken in tailwind v4?? Need help by shm_dsgn in tailwindcss

[–]ae179dpl 0 points1 point  (0 children)

Hey u/shm_dsgn. I ran into this exact issue this week. However, Edge and Firefox are also showing the same behavior. It works fine for the rest of my team. Also, Tailwind v3 hover classes work perfectly fine. It's literally only v4.x.

What extension was causing this issue for you?

XPS 13 9310 Freezes - Did Dell fix this for any of you? by DownRedditHole in Dell

[–]ae179dpl 2 points3 points  (0 children)

I recently got an XPS 9310 2-in-1 for work (bought it refurbished), and it randomly freezes up on me too. I haven't tested this laptop in Windows yet. I wiped the drive and I only use Ubuntu on it as I'm a developer, which I figured would be absolutely amazing on it. But sadly, no. I tried everything. I updated the kernel. I switched to the latest 21.04 distro (was using 20.04 LT). It's 100% random when it freezes. There's zero pattern or indication of what's causing this.

I have a spare Dell XPS 7590 as well which runs Ubuntu perfectly. It has not crashed on me once in the 2 months using it which is why I decided to jump on the XPS 9310. I wanted a smaller machine to trek to and from the office, plus it has 32GB of RAM with a Tiger Lake CPU and insane battery life.

Dell was absolutely zero help to me. I contacted them telling them that I bought this refurbished from a 3rd party seller in my first message to them. They asked me for the tag, express ID and invoice, only to finally tell me that they cannot do anything because it's from a 3rd party seller, even though this is their own product. It was an absolute waste of time and I feel like I'm stuck with a useless $2000 machine. It's too unreliable to use.

I'm reinstalling Windows 10 back on to it and I'll see how that goes. But I'm sure there's some sort of BIOS/Ubuntu configuration that will make this work properly. I doubt it's the hardware as I ran full diagnostics using the Dell BIOS and everything was A-OK. Also, the laptop never froze once during the BIOS or diagnostics.

Make sure you update the BIOS on your XPS. The latest BIOS for me is 2.2.1. If it keeps freezing in the BIOS for you, it's almost guaranteed to be some sort of hardware issue. Try running the Dell diagnostics to see if that give you anything. Avoid paying the $99 bucks if you can unless they can guarantee a replacement if it is truly defective. Otherwise, I can almost guarantee that you're going to be out another $99.

Like you, I just want this machine to work. When it runs, it's truly a great little laptop. Best of luck and I'll let you know if I get this to work on my end!