Skip to content
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

feat: toggle updation of billed amount in previous purchase docs #40102

Merged

Conversation

GursheenK
Copy link
Member

@GursheenK GursheenK commented Feb 25, 2024

Introduce the check to choose if the billed amount should be updated in the Purchase Order and Purchase Receipt when a Debit Note is created against the Purchase Invoice.

Case

  • User creates a Purchase Receipt for an item with a Qty 10.
  • User creates a Purchase Invoice against the PR with Qty 10. This leads to the billed amount in the PR to be 100%
  • Now, suppose the user creates a Debit Note against the invoice with Qty -5, the status of the PR changes to partly billed and the billed amount becomes 50%.
  • Then, the user creates a Purchase Return against the PR with Qty -5. In this case, the qty captured in the PR is 5 and the qty billed is also 5. But, the billed amount remains as 50% leaving the PR in Partly Billed status.

Since there is no specific order enforced for creation of Purchase Return before the Debit Note, the check can be used to handle cases when the billed amount should be / should not be changed in the previous doc.

no-docs

@nabinhait nabinhait merged commit 0c52eb9 into frappe:develop Feb 27, 2024
17 of 18 checks passed
GursheenK added a commit that referenced this pull request Feb 27, 2024
…-40102

feat: toggle updation of billed amount in previous purchase docs (backport #40102)
GursheenK added a commit that referenced this pull request Feb 27, 2024
…-40102

feat: toggle updation of billed amount in previous purchase docs (backport #40102)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants