Skip to content

[IMP] inventory: security lead times fix #12929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 18.0
Choose a base branch
from

Conversation

Felicious
Copy link
Contributor

@Felicious Felicious commented Apr 17, 2025

Fixes the purchase security lead time error flagged by Jeso

Summary of changes

  • Rewrote the Purchase lead times section: now shows which lead time shifts the PO deadline and which only widens the JIT forecast window
  • Replace outdated text and images.
  • Added a worked example that ties vendor lead time, days‑to‑purchase, and purchase security lead time together.
  • Clarifying push vs. pull rule behavior and how it affects the lead times in 18.0

Received help from Jrma & Shke 😊

@robodoo
Copy link
Collaborator

robodoo commented Apr 17, 2025

Pull request status dashboard

@Felicious Felicious changed the title [IMP] purchase: security lead times fix [IMP] inventory: security lead times fix Apr 17, 2025
@C3POdoo C3POdoo requested a review from a team April 17, 2025 15:26
@Felicious Felicious added the 1 label Apr 19, 2025
@Felicious Felicious force-pushed the 18.0-inventory-purchase-security-feku branch from 483b539 to 10b27b4 Compare April 22, 2025 15:29
@Felicious Felicious removed the 1 label Apr 22, 2025
@Felicious Felicious self-assigned this Apr 22, 2025
@Felicious
Copy link
Contributor Author

Hi @justinmallette ! This PR is ready for peer review (:

@Felicious Felicious force-pushed the 18.0-inventory-purchase-security-feku branch from 10b27b4 to 564e99c Compare April 22, 2025 15:46
@Felicious
Copy link
Contributor Author

Oops i found some errors and pushed up another commit 😅 @justinmallette

Copy link
Contributor

@justinmallette justinmallette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments! I also saw that some of the images in this doc still have the outdated styling (the red boxes), but since they weren't included in your original PR, consider them a nitpick!

- Last calendar day to confirm the |RFQ| and convert it to a |PO|
* - Expected Arrival
- Arrival date of the products. Calculated by :math:`\text{Order Deadline} + \text{Vendor Lead
Time}`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Time}`
Time}`

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The render is removing the space between Lead and Time
Screenshot 2025-04-22 at 11 01 30 AM

.. example::
To tie all the purchase lead times together, consider this:

- Today: April 21
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Today: April 21
- **Order Placed**: April 21

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know the terminology like you do, so replace this if it isn't correct. My concern is that seeing "today" in an example won't make sense since it's relative (even if you're defining it here). Would something like Sales Order Confirmed or something like that work?


Example of the :abbr:`JIT (just-in-time)` forecast window, which is April 21-28.

When creating an RFQ today:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When creating an RFQ today:
When creating an RFQ on the day the order was placed/the sales order was confirmed:


When creating an RFQ today:

- :guilabel:`Order Deadline`: April 23 (:math:`\text{Today} + 2`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- :guilabel:`Order Deadline`: April 23 (:math:`\text{Today} + 2`)
- :guilabel:`Order Deadline`: April 23 (:math:`\text{Order Confirmation Date} + 2`)

time selected is the entry at the top of the list.

.. tip::
A PO is marked late if the *Expected Arrival* date has passed, and appears in the *Late* box on
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A PO is marked late if the *Expected Arrival* date has passed, and appears in the *Late* box on
A |PO| is marked late if the *Expected Arrival* date has passed, and appears in the *Late* box on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants