We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Team,
In Subcontracting Receipt, item rate is showing wrong. It is not capturing Raw material rate + Subcontracting service cost.
This is observed where there are multiple subcontracting services.
You can create first subcontracting PO with RM rate Rs. 100 and service rate is 10/-
in Sucontracting PO rate it shows only Rs. 100 which should be Rs 110 for the incoming item. In stock entry, it is working correct.
This is misguiding for subcontracting valuation process.
manufacturing
Installed Apps ERPNext: v15.35.2 (version-15)
Frappe Framework: v15.40.6 (version-15)
India Compliance: v15.13.2 (version-15)
manual install
No response
The text was updated successfully, but these errors were encountered:
can you confirm that the valuation rate is different on the stock sheet?
Sorry, something went wrong.
No branches or pull requests
Information about bug
Hi Team,
In Subcontracting Receipt, item rate is showing wrong. It is not capturing Raw material rate + Subcontracting service cost.
This is observed where there are multiple subcontracting services.
You can create first subcontracting PO with RM rate Rs. 100 and service rate is 10/-
in Sucontracting PO rate it shows only Rs. 100
which should be Rs 110 for the incoming item. In stock entry, it is working correct.
This is misguiding for subcontracting valuation process.
Module
manufacturing
Version
Installed Apps
ERPNext: v15.35.2 (version-15)
Frappe Framework: v15.40.6 (version-15)
India Compliance: v15.13.2 (version-15)
Installation method
manual install
Relevant log output / Stack trace / Full Error Message.
No response
The text was updated successfully, but these errors were encountered: