help on manufacturing module
This commit is contained in:
Umair Sayyed
parent
dc83bb8d18
commit
fc8d0f6ac7
Binary file not shown.
|
Before Width: | Height: | Size: 50 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 68 KiB |
BIN
erpnext/docs/assets/img/articles/delete-transactions.gif
Normal file
BIN
erpnext/docs/assets/img/articles/delete-transactions.gif
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 603 KiB |
BIN
erpnext/docs/assets/img/articles/manufacturing-settings-2.png
Normal file
BIN
erpnext/docs/assets/img/articles/manufacturing-settings-2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
BIN
erpnext/docs/assets/img/articles/manufacturing-settings-3.png
Normal file
BIN
erpnext/docs/assets/img/articles/manufacturing-settings-3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 58 KiB |
BIN
erpnext/docs/assets/img/articles/manufacturing-settings-4.png
Normal file
BIN
erpnext/docs/assets/img/articles/manufacturing-settings-4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
BIN
erpnext/docs/assets/img/articles/nested-bom-1.png
Normal file
BIN
erpnext/docs/assets/img/articles/nested-bom-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 107 KiB |
BIN
erpnext/docs/assets/img/articles/use-multi-level-bom.png
Normal file
BIN
erpnext/docs/assets/img/articles/use-multi-level-bom.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 93 KiB |
BIN
erpnext/docs/assets/img/articles/valuation-based-on-1.png
Normal file
BIN
erpnext/docs/assets/img/articles/valuation-based-on-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 116 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 117 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 77 KiB |
55
erpnext/docs/current/index.html
Normal file
55
erpnext/docs/current/index.html
Normal file
@ -0,0 +1,55 @@
|
||||
<!-- title: ERPNext: Developer Docs -->
|
||||
<!-- no-breadcrumbs -->
|
||||
|
||||
|
||||
<div class="dev-header">
|
||||
|
||||
<a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
|
||||
Version 6.x.x</a>
|
||||
|
||||
|
||||
<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext"
|
||||
target="_blank" style="margin-left: 10px; margin-bottom: 10px;"><i class="octicon octicon-mark-github"></i> Source</a>
|
||||
|
||||
</div>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<tr>
|
||||
<td style="width: 20%">
|
||||
App Name
|
||||
</td>
|
||||
<td>
|
||||
<code>erpnext</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
Publisher
|
||||
</td>
|
||||
<td>
|
||||
<code>Frappe Technologies Pvt. Ltd.</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
Version
|
||||
</td>
|
||||
<td>
|
||||
<code>6.19.0</code>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>Contents</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="models">Models (DocTypes)</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="api">Server-side API</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<!-- autodoc -->
|
||||
<!-- jinja -->
|
||||
<!-- static -->
|
||||
1971
erpnext/docs/current/models/buying/purchase_order.html
Normal file
1971
erpnext/docs/current/models/buying/purchase_order.html
Normal file
File diff suppressed because it is too large
Load Diff
164
erpnext/docs/current/models/hr/branch.html
Normal file
164
erpnext/docs/current/models/hr/branch.html
Normal file
@ -0,0 +1,164 @@
|
||||
<!-- title: Branch -->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="dev-header">
|
||||
|
||||
<a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
|
||||
Version 6.x.x</a>
|
||||
|
||||
|
||||
<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/branch"
|
||||
target="_blank" style="margin-left: 10px; margin-bottom: 10px;"><i class="octicon octicon-mark-github"></i> Source</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<p><b>Table Name:</b> <code>tabBranch</code></p>
|
||||
|
||||
|
||||
|
||||
|
||||
<h3>Fields</h3>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width: 5%">Sr</th>
|
||||
<th style="width: 25%">Fieldname</th>
|
||||
<th style="width: 20%">Type</th>
|
||||
<th style="width: 25%">Label</th>
|
||||
<th style="width: 25%">Options</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
<tr >
|
||||
<td>1</td>
|
||||
<td class="danger" title="Mandatory"><code>branch</code></td>
|
||||
<td >
|
||||
Data</td>
|
||||
<td >
|
||||
Branch
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
<hr>
|
||||
<h3>Controller</h3>
|
||||
<h4>erpnext.hr.doctype.branch.branch</h4>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<h3 style="font-weight: normal;">Class <b>Branch</b></h3>
|
||||
|
||||
<p style="padding-left: 30px;"><i>Inherits from frappe.model.document.Document</i></h4>
|
||||
|
||||
<div class="docs-attr-desc"><p></p>
|
||||
</div>
|
||||
<div style="padding-left: 30px;">
|
||||
|
||||
</div>
|
||||
<hr>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<h4>Linked In:</h4>
|
||||
<ul>
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/employee">Employee</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/employee_attendance_tool">Employee Attendance Tool</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/employee_internal_work_history">Employee Internal Work History</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/leave_control_panel">Leave Control Panel</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/process_payroll">Process Payroll</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/salary_slip">Salary Slip</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/salary_structure">Salary Structure</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/selling/sms_center">SMS Center</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
<!-- autodoc -->
|
||||
<!-- jinja -->
|
||||
<!-- static -->
|
||||
186
erpnext/docs/current/models/hr/department.html
Normal file
186
erpnext/docs/current/models/hr/department.html
Normal file
@ -0,0 +1,186 @@
|
||||
<!-- title: Department -->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="dev-header">
|
||||
|
||||
<a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
|
||||
Version 6.x.x</a>
|
||||
|
||||
|
||||
<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/department"
|
||||
target="_blank" style="margin-left: 10px; margin-bottom: 10px;"><i class="octicon octicon-mark-github"></i> Source</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<p><b>Table Name:</b> <code>tabDepartment</code></p>
|
||||
|
||||
|
||||
|
||||
|
||||
<h3>Fields</h3>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width: 5%">Sr</th>
|
||||
<th style="width: 25%">Fieldname</th>
|
||||
<th style="width: 20%">Type</th>
|
||||
<th style="width: 25%">Label</th>
|
||||
<th style="width: 25%">Options</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
<tr >
|
||||
<td>1</td>
|
||||
<td class="danger" title="Mandatory"><code>department_name</code></td>
|
||||
<td >
|
||||
Data</td>
|
||||
<td >
|
||||
Department
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>2</td>
|
||||
<td ><code>leave_block_list</code></td>
|
||||
<td >
|
||||
Link</td>
|
||||
<td >
|
||||
Leave Block List
|
||||
<p class="text-muted small">
|
||||
Days for which Holidays are blocked for this department.</p>
|
||||
</td>
|
||||
<td>
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/leave_block_list">Leave Block List</a>
|
||||
|
||||
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
<hr>
|
||||
<h3>Controller</h3>
|
||||
<h4>erpnext.hr.doctype.department.department</h4>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<h3 style="font-weight: normal;">Class <b>Department</b></h3>
|
||||
|
||||
<p style="padding-left: 30px;"><i>Inherits from frappe.model.document.Document</i></h4>
|
||||
|
||||
<div class="docs-attr-desc"><p></p>
|
||||
</div>
|
||||
<div style="padding-left: 30px;">
|
||||
|
||||
</div>
|
||||
<hr>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<h4>Linked In:</h4>
|
||||
<ul>
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/employee">Employee</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/employee_attendance_tool">Employee Attendance Tool</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/employee_internal_work_history">Employee Internal Work History</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/leave_control_panel">Leave Control Panel</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/process_payroll">Process Payroll</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/salary_slip">Salary Slip</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/salary_structure">Salary Structure</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/selling/sms_center">SMS Center</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
<!-- autodoc -->
|
||||
<!-- jinja -->
|
||||
<!-- static -->
|
||||
244
erpnext/docs/current/models/hr/employee_attendance_tool.html
Normal file
244
erpnext/docs/current/models/hr/employee_attendance_tool.html
Normal file
@ -0,0 +1,244 @@
|
||||
<!-- title: Employee Attendance Tool -->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="dev-header">
|
||||
|
||||
<a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
|
||||
Version 6.x.x</a>
|
||||
|
||||
|
||||
<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employee_attendance_tool"
|
||||
target="_blank" style="margin-left: 10px; margin-bottom: 10px;"><i class="octicon octicon-mark-github"></i> Source</a>
|
||||
|
||||
</div>
|
||||
|
||||
<span class="label label-info">Single</span>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<h3>Fields</h3>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width: 5%">Sr</th>
|
||||
<th style="width: 25%">Fieldname</th>
|
||||
<th style="width: 20%">Type</th>
|
||||
<th style="width: 25%">Label</th>
|
||||
<th style="width: 25%">Options</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
<tr >
|
||||
<td>1</td>
|
||||
<td ><code>date</code></td>
|
||||
<td >
|
||||
Date</td>
|
||||
<td >
|
||||
Date
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>2</td>
|
||||
<td ><code>department</code></td>
|
||||
<td >
|
||||
Link</td>
|
||||
<td >
|
||||
Department
|
||||
|
||||
</td>
|
||||
<td>
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/department">Department</a>
|
||||
|
||||
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>3</td>
|
||||
<td ><code>column_break_3</code></td>
|
||||
<td class="info">
|
||||
Column Break</td>
|
||||
<td >
|
||||
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>4</td>
|
||||
<td ><code>branch</code></td>
|
||||
<td >
|
||||
Link</td>
|
||||
<td >
|
||||
Branch
|
||||
|
||||
</td>
|
||||
<td>
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/branch">Branch</a>
|
||||
|
||||
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>5</td>
|
||||
<td ><code>company</code></td>
|
||||
<td >
|
||||
Link</td>
|
||||
<td >
|
||||
Company
|
||||
|
||||
</td>
|
||||
<td>
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/setup/company">Company</a>
|
||||
|
||||
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr class="info">
|
||||
<td>6</td>
|
||||
<td ><code>unmarked_attendance_section</code></td>
|
||||
<td >
|
||||
Section Break</td>
|
||||
<td >
|
||||
Unmarked Attendance
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>7</td>
|
||||
<td ><code>employees_html</code></td>
|
||||
<td >
|
||||
HTML</td>
|
||||
<td >
|
||||
Employees HTML
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr class="info">
|
||||
<td>8</td>
|
||||
<td ><code>marked_attendance_section</code></td>
|
||||
<td >
|
||||
Section Break</td>
|
||||
<td >
|
||||
Marked Attendance
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>9</td>
|
||||
<td ><code>marked_attendance_html</code></td>
|
||||
<td >
|
||||
HTML</td>
|
||||
<td >
|
||||
Marked Attendance HTML
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
<hr>
|
||||
<h3>Controller</h3>
|
||||
<h4>erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool</h4>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<h3 style="font-weight: normal;">Class <b>EmployeeAttendanceTool</b></h3>
|
||||
|
||||
<p style="padding-left: 30px;"><i>Inherits from frappe.model.document.Document</i></h4>
|
||||
|
||||
<div class="docs-attr-desc"><p></p>
|
||||
</div>
|
||||
<div style="padding-left: 30px;">
|
||||
|
||||
</div>
|
||||
<hr>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<p><span class="label label-info">Public API</span>
|
||||
<br><code>/api/method/erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.get_employees</code>
|
||||
</p>
|
||||
<p class="docs-attr-name">
|
||||
<a name="erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.get_employees" href="#erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.get_employees" class="text-muted small">
|
||||
<i class="icon-link small" style="color: #ccc;"></i></a>
|
||||
erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.<b>get_employees</b>
|
||||
<i class="text-muted">(date, department=None, branch=None, company=None)</i>
|
||||
</p>
|
||||
<div class="docs-attr-desc"><p><span class="text-muted">No docs</span></p>
|
||||
</div>
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<p><span class="label label-info">Public API</span>
|
||||
<br><code>/api/method/erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.mark_employee_attendance</code>
|
||||
</p>
|
||||
<p class="docs-attr-name">
|
||||
<a name="erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.mark_employee_attendance" href="#erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.mark_employee_attendance" class="text-muted small">
|
||||
<i class="icon-link small" style="color: #ccc;"></i></a>
|
||||
erpnext.hr.doctype.employee_attendance_tool.employee_attendance_tool.<b>mark_employee_attendance</b>
|
||||
<i class="text-muted">(employee_list, status, date, company=None)</i>
|
||||
</p>
|
||||
<div class="docs-attr-desc"><p><span class="text-muted">No docs</span></p>
|
||||
</div>
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- autodoc -->
|
||||
<!-- jinja -->
|
||||
<!-- static -->
|
||||
87
erpnext/docs/current/models/hr/holiday.html
Normal file
87
erpnext/docs/current/models/hr/holiday.html
Normal file
@ -0,0 +1,87 @@
|
||||
<!-- title: Holiday -->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="dev-header">
|
||||
|
||||
<a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
|
||||
Version 6.x.x</a>
|
||||
|
||||
|
||||
<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/holiday"
|
||||
target="_blank" style="margin-left: 10px; margin-bottom: 10px;"><i class="octicon octicon-mark-github"></i> Source</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="label label-info">Child Table</span>
|
||||
|
||||
|
||||
<p><b>Table Name:</b> <code>tabHoliday</code></p>
|
||||
|
||||
|
||||
|
||||
|
||||
<h3>Fields</h3>
|
||||
|
||||
<table class="table table-bordered">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width: 5%">Sr</th>
|
||||
<th style="width: 25%">Fieldname</th>
|
||||
<th style="width: 20%">Type</th>
|
||||
<th style="width: 25%">Label</th>
|
||||
<th style="width: 25%">Options</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
<tr >
|
||||
<td>1</td>
|
||||
<td class="danger" title="Mandatory"><code>description</code></td>
|
||||
<td >
|
||||
Text Editor</td>
|
||||
<td >
|
||||
Description
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr >
|
||||
<td>2</td>
|
||||
<td class="danger" title="Mandatory"><code>holiday_date</code></td>
|
||||
<td >
|
||||
Date</td>
|
||||
<td >
|
||||
Date
|
||||
|
||||
</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
<h4>Child Table Of</h4>
|
||||
<ul>
|
||||
|
||||
<li>
|
||||
|
||||
|
||||
<a href="https://frappe.github.io/erpnext/current/models/hr/holiday_list">Holiday List</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
<!-- autodoc -->
|
||||
<!-- jinja -->
|
||||
<!-- static -->
|
||||
2440
erpnext/docs/current/models/selling/sales_order.html
Normal file
2440
erpnext/docs/current/models/selling/sales_order.html
Normal file
File diff suppressed because it is too large
Load Diff
1632
erpnext/docs/current/models/setup/company.html
Normal file
1632
erpnext/docs/current/models/setup/company.html
Normal file
File diff suppressed because it is too large
Load Diff
2408
erpnext/docs/current/models/stock/item.html
Normal file
2408
erpnext/docs/current/models/stock/item.html
Normal file
File diff suppressed because it is too large
Load Diff
@ -1,6 +1,4 @@
|
||||
Expense Claim is made when Employee’s make expenses out of their pocket on
|
||||
behalf of the company. For example, if they take a customer out for lunch,
|
||||
they can make a request for reimbursement via the Expense Claim form.
|
||||
Expense Claim is made when Employee’s make expenses out of their pocket on behalf of the company. For example, if they take a customer out for lunch, they can make a request for reimbursement via the Expense Claim form.
|
||||
|
||||
To make a new Expense Claim, go to:
|
||||
|
||||
@ -13,16 +11,12 @@ Set the Employee ID, date and the list of expenses that are to be claimed and
|
||||
|
||||
### Approving Expenses
|
||||
|
||||
The person making the claim must also set the id of the user who will
|
||||
“Approve” these expenses and set the “Assign To” to notify the user of the
|
||||
request Approve.
|
||||
Approver for the Expense Claim is selected by an Employee himself. Users to whom `Expense Approver` role is assigned will shown in the Expense Claim Approver field.
|
||||
|
||||
If the Approver sees the “form”, she or he can update the “Approved Amounts”
|
||||
and click on “Approve”. To cancel the claim, they can click on the “Reject”
|
||||
button.
|
||||
After saving Expense Claim, Employee should [Assign document to Approver]({{docs_base_url}}/user/manual/en/using-eprnext/assignment.html). On assignment, approving user will also receive email notification. To automate email notification, you can also setup [Email Alert]({{docs_base_url}}/user/manual/en/setting-up/email/email-alerts.html).
|
||||
|
||||
Comments can be added in the Comments section explaining why the claim was
|
||||
approved or rejected.
|
||||
Expense Claim Approver can update the “Sanctioned Amounts” against Claimed Amount of an Employee. If submitting, Approval Status should be submitted to Approved or Rejected. If Approved, then Expense Claim gets submitted. If rejected, then Expen
|
||||
Comments can be added in the Comments section explaining why the claim was approved or rejected.
|
||||
|
||||
### Booking the Expense and Reimbursement
|
||||
|
||||
|
||||
@ -1,4 +1,3 @@
|
||||
nested-bom-structure
|
||||
partial-production-entry
|
||||
production-planning-subassembly
|
||||
valuation-based-on-field-in-bom
|
||||
@ -1,30 +1,34 @@
|
||||
<h1>Nested BOM Structure</h1>
|
||||
#Nested BOM Structure
|
||||
|
||||
**Question:** Our manufacturing process involves producing sub-assembly items before final product. How should we manage BOM master in this scenario?
|
||||
|
||||
**Answer:** You should create BOM for item in the order of their production. Let's consider an example to understand this better.
|
||||
**Answer:** You should create BOM for item in the order of their production. BOM for the sub-assembly item should be created first. BOM for the Product Order item should be created last. Let's consider an example to understand this better.
|
||||
|
||||
If Computer manufacturer assembles Hard Disk and DVD Drive (sub-assemblies) themselves, they should first create BOM for Hard Disk and DVD Drive. After that BOM for Computer will be created, which is finished and saleable item. BOM of computer will have
|
||||
Hard Disk and DVD Drive (sub-assemblies) will be selected as raw-material items in it. BOM ID will be fetched for the respective sub-assembly item.
|
||||
A computer assembler is creating a BOM for PC. They also manufacture Hard Disk and DVD Drive themselve. They should first create BOM for Hard Disk and DVD Drive. After that BOM for the PC should be created.
|
||||
|
||||
BOM of PC will have all the raw-material items selected in it. Hard Disk and DVD Drive (sub-assemblies) will also be selected as raw-material items. For the sib-assembly items, respective BOM no. will be fetched as well.
|
||||
|
||||
<img src="{{docs_base_url}}/assets/img/articles/Screen Shot 2015-04-02 at 3.58.19 pm.png">
|
||||
<img alt="Nested BOM" class="screenshot" src="{{docs_base_url}}/assets/img/articles/nested-bom-1.png">
|
||||
|
||||
Following is how the structure of nested BOM will look:
|
||||
|
||||
<div class="well">
|
||||
|
||||
<b>-Personal Computer (FG Item)</b><br>
|
||||
<b>---- Mother Board</b><br>
|
||||
<b>---- SMTP</b><br>
|
||||
<b>---- Accessories and wires</b><br>
|
||||
<b>----<i>Hard Disk (sub-assembly)</i></b><br>
|
||||
------- Item A<br>
|
||||
------- Item B<br>
|
||||
------- Item C<br>
|
||||
<b>----<i>DVD Drive (sub-assembly)</i></b><br>
|
||||
------- Item X<br>
|
||||
------- Item Y<br>
|
||||
------- Item Z
|
||||
|
||||
</div>
|
||||
|
||||
<br>Following is how the structure of nested BOM will look:
|
||||
<br>
|
||||
<br><b>Computer (FG Item)</b>
|
||||
<br><b>---</b> Mother Board
|
||||
<br><b>---</b> SMTP
|
||||
<br><b>---</b> Accessories and wires
|
||||
<br><b>---</b> <i>Hard Disk (sub-assembly)</i>
|
||||
<br> ------ Item A
|
||||
<br> ------ Item B
|
||||
<br> ------ Item C
|
||||
<br><b>---</b> <i>DVD Drive (sub-assembly)</i>
|
||||
<br> ------ Item X
|
||||
<br> ------ Item Y
|
||||
<br> ------ Item Z
|
||||
<br>
|
||||
|
||||
|
||||
<!-- markdown -->
|
||||
@ -1,25 +0,0 @@
|
||||
<h1>Partial Production Entry</h1>
|
||||
|
||||
If you completed production for few items, then you can make Partial Production Entry for that items in system. For example, your production order is for 15 quantity and you completed production for 10 quantity only. Then you can make production entry for 5 quantity. Following are step to make Partial Production Entry
|
||||
|
||||
#### 1. Stock Entry
|
||||
|
||||
Click on Update Finish Goods button from submitted Product Order, You will land on new Stock entry form.
|
||||
|
||||
#### 2. Edit Manufacturing Quantity
|
||||
|
||||
In the Update Finished Goods entry, check "From Bill of Material section", and edit Manufacturing Quantity to actual quantity produced. Production Order quantity will be fetched as Manufacturing Quantity by default.
|
||||
|
||||
#### 3. Update Qty of Items
|
||||
|
||||
Click on **Get Items**. With this, quantity will be updated for both raw-material as well as finish good item.
|
||||
|
||||
|
||||
|
||||
#### 4. Save and Submit
|
||||
|
||||
After updating quantity in stock entry form, save and submit the stock entry. On submit stock will update for quantity entered in this stock entry.
|
||||
|
||||
When will you create another finish goods entry against this Production Order, system will only fetch pending quantity to be produced.
|
||||
|
||||
<!-- markdown -->
|
||||
@ -1,8 +0,0 @@
|
||||
<h1>Production Planning & Subassembly</h1>
|
||||
|
||||
if you need Production Planning Tool to consider raw-materials required for the manufacturing of sub-assembly items selected in the BOM, please check following instructions to achieve the same.<br><br>Production Planning Tool has field called "Use Multi-Level BOM", checking which will consider raw-material of sub-assemblies as well in the material planning. If this field is not checked, then it will consider sub-assembly as an item, and won't consider raw-material required for the manufacturing of that sub-assembly.<br><br><img src="{{docs_base_path}}/assets/img/articles/$SGrab_203.png"><br><br>You will find same field in the Production Order and Stock Entry as well.<br><br>This feature is very useful for the companies who create BOM for the
|
||||
sub-assemblies, but Production Order is created only for the finished
|
||||
item. They do not create separate Production Order for the
|
||||
sub-assemblies, but raw-materials as listed in the BOM of sub-assembly
|
||||
items are consumed in the production process, and not sub-assembly item
|
||||
directly.<br>
|
||||
@ -6,4 +6,4 @@ Production Planning Tool has field called "Use Multi-Level BOM", checking which
|
||||
|
||||
<img src="{{docs_base_path}}/assets/img/articles/$SGrab_203.png">
|
||||
|
||||
You will find same field in the Production Order and Stock Entry as well.This feature is very useful for the companies who create BOM for the sub-assemblies, but Production Order is created only for the finished item. They do not create separate Production Order for the sub-assemblies, but raw-materials as listed in the BOM of sub-assembly items are consumed in the production process, and not sub-assembly item directly.
|
||||
`Use Multi-Level BOM` field is also there in the Production Order and Stock Entry. If checked, raw-materials of sub-assembly item will be consumed in the manufacturing process, and not the sub-assembly item itself.
|
||||
|
||||
@ -1,10 +0,0 @@
|
||||
<h1>'Valuation Based On' Field in BOM</h1>
|
||||
|
||||
<div><b>Question:</b> What do the various options in <i>Valuation Based On </i>Field in Bill Of Materials (BOM) Form mean? <br><br><b>Answer:</b> There are 3 available options in the <i>Valuation Based On</i> field;<br><br><img src="{{docs_base_path}}/assets/img/articles/kb_bom_field.png"><br><br><ul><li><b><i>Valuation Rate:</i></b> <br></li><ul><li>Item valuation rate is
|
||||
defined based on it's purchase/manufacture value + other charges. <br></li><li>For
|
||||
Purchase Item, it is defined based on charges entered in the Purchase
|
||||
Receipt. If you don't have any Purchase Receipt
|
||||
made for an item or a Stock Reconciliation, then you won't have
|
||||
Valuation Rate for that item.</li></ul></ul><ul><li><b><i>Price List Rate:</i></b> <br></li><ul><li>Just like you pull item prices in sales and purchase transaction, it can be pulled in BOM via Price List Rate.</li></ul></ul></div><div><ul><li><i><b>Last Purchase Rate</b>:</i> <br></li><ul><li>It will be the last Purchase Rate value of an item. This
|
||||
value is updated in the item master as well, based on rate in the
|
||||
Purchase Order for this item.</li></ul></ul><p><br></p></div>
|
||||
@ -1,17 +1,16 @@
|
||||
#Valuation Based On' Field in BOM
|
||||
#Valuation Based On in BOM
|
||||
|
||||
**Question:** What do the various options in <i>Valuation Based On </i>Field in Bill Of Materials (BOM) Form mean?
|
||||
**Question:** What are for various options in `Valuation Based On` in the Bill Of Materials (BOM)?
|
||||
|
||||
**Answer:** There are 3 available options in the <i>Valuation Based On</i> field;
|
||||
**Answer:** There are 3 available options in the <i>Valuation Based On</i> field:
|
||||
|
||||
<img src="{{docs_base_path}}/assets/img/articles/kb_bom_field.png">
|
||||
<img alt="Nested BOM" class="screenshot" src="{{docs_base_url}}/assets/img/articles/valuation-based-on-1.png">
|
||||
|
||||
Valuation Rate: Item valuation rate is defined based on it's purchase/manufacture value + other charges.
|
||||
**Valuation Rate:** Item valuation rate is defined based on it's purchase or manufacture value.
|
||||
|
||||
For Purchase Item, it is defined based on charges entered in the Purchase Receipt. If you don't have any Purchase Receipt
|
||||
made for an item or a Stock Reconciliation, then you won't have
|
||||
Valuation Rate for that item.
|
||||
made for an item or a Stock Reconciliation, then there won't be any Valuation Rate for that item.
|
||||
|
||||
Price List Rate: Just like you pull item prices in sales and purchase transaction, it can be pulled in BOM via Price List Rate.
|
||||
**Price List Rate:** This option allows to pull item rates from [Price List.]({{docs_base_url}}/user/manual/en/stock/item/item-price.html)
|
||||
|
||||
Last Purchase Rate: It will be the last Purchase Rate value of an item. This value is updated in the item master as well, based on rate in the Purchase Order for this item.
|
||||
**Last Purchase Rate:** It will be the last Purchase (Order) Rate of an item.
|
||||
@ -1,15 +1,53 @@
|
||||
* Manufacturing Settings can be found at
|
||||
#Manufacturing Settings
|
||||
|
||||
> Manufacturing > Production Order > Setup > Manufacturing Settings
|
||||
Manufacturing Settings can be found at:
|
||||
|
||||
<img class="screenshot" alt="Manufacturing Settings" src="{{docs_base_url}}/assets/img/manufacturing/manufacturing-settings.png">
|
||||
`Manufacturing > Setup > Manufacturing Settings`
|
||||
|
||||
* Allow Overtime - Specify if workstations are to allow overtime.(schedule operations outside working hours)
|
||||
<img class="screenshot" alt="Manufacturing Settings" src="{{docs_base_url}}/assets/img/manufacturing/manufacturing-settings-1.png">
|
||||
|
||||
* Allow Production on Holidays - Specify if system is to allow scheduling of operations on Holidays.
|
||||
####Disable Capacity Planning and Time Tracking
|
||||
|
||||
* Capacity Planning for (Days) - Specify no. of Days for Capacity Planning.
|
||||
As per Capacity Planning feature, when Production Order is created for an item, for each Operation, Time Log is created. Based on actual Operation Time, Time Logs is updated. This also provides total Operations Cost against Production Order.
|
||||
|
||||
* Time Between Operations (in mins) - Specify the gap between two Production Operations.
|
||||
If you don't track actual operations time, and want to disable creation of Time Log based on Operations, you should check "Disable Capacity Planning and Time Tracking" in the Manufacturing Settings.
|
||||
|
||||
{next}
|
||||
####Allow Overtime
|
||||
|
||||
In the Workstation master, actual working hours are defined (say 101m to 6pm). As per the Capacity Planning, Time Logs are created against Workstation, for tracking actual operations hour. It also considers working hours of a Workstation when scheduling job (via Time Log).
|
||||
|
||||
<img class="screenshot" alt="Manufacturing Settings" src="{{docs_base_url}}/assets/img/articles/manufacturing-settings-2.png">
|
||||
|
||||
As per the standard validation, if Operation cannot be completed within working hours of Workstation, then user is asked to divide an Operation into multiple and smaller Operations. However, if `Allow Overtime` field is checked, while creating Time Logs for Operation, working hours of Workstation will not be validated. In this case, Time Logs for Operation will be created beyond working hours of Workstation as well.
|
||||
|
||||
####Allow Production on Holidays
|
||||
|
||||
Holiday of a company can be recorded in the [Holiday List]({{docs_base_url}}/user/manual/en/human-resources/) master. While scheduling production job on workstation, system doesn't consider a day listed in the Holiday list. If you want production job to be scheduled on holidays as well, `Allow Production on Holidays` field should be checked.
|
||||
|
||||
<img class="screenshot" alt="Manufacturing Settings" src="{{docs_base_url}}/assets/img/articles/manufacturing-settings-3.png">
|
||||
|
||||
####Over Production Allowance Percentage
|
||||
|
||||
In Production Order, `Qty to Manufacture` is set. When creating Manufacture entry against Production Order, it validates `Qty to Manufature` entered in production order, and doesn't allow creating Manufacture Entry for more qty and Production Order qty. If you want to create Manufacture Qty than Production Order qty, mention Over Production Allowance Qty in the Manufacturing Settings. Based on Allowance Percentage mentioned, you will be able to create Manufacture Entry for more Qty than in Production Order.
|
||||
|
||||
####Back-flush Raw Materials Based On
|
||||
|
||||
When creating Manufacture Entry, raw-material items are back-flush based on BOM of production item. If you want raw-material items to be back-flushed based on Material Transfer entry made against that Production Order instead, then you should set Back-flush Raw Materials Based On "Material Transferred for Manufacture".
|
||||
|
||||
<img class="screenshot" alt="Manufacturing Settings" src="{{docs_base_url}}/assets/img/articles/manufacturing-settings-4.png">
|
||||
|
||||
####Capacity Planning For (Days)
|
||||
|
||||
Define no. of days for which system will do production job allocation in advance.
|
||||
|
||||
####Time Between Operations (in mins)
|
||||
|
||||
Time gap between two production operations.
|
||||
|
||||
####Default Work In Progress Warehouse
|
||||
|
||||
This Warehouse will be auto-updated in the Work In Progress Warehouse field of Production Order.
|
||||
|
||||
####Default Finished Goods Warehouse
|
||||
|
||||
This Warehouse will be auto-updated in the Work In Progress Warehouse field of Production Order.
|
||||
@ -12,7 +12,7 @@ In Company master, click on the **Delete Company Transactions** button right at
|
||||
|
||||
This action will wipe out all the data related to that company like Quotation, Invoices, Purchase Orders etc. So be careful
|
||||
|
||||
<img alt="Delete Transactions" class="screenshot" src="{{docs_base_url}}/assets/img/articles/delete-company.png">
|
||||
<img alt="Delete Transactions" class="screenshot" src="{{docs_base_url}}/assets/img/articles/delete-transactions.gif">
|
||||
|
||||
**Note:** If you want to delete the company record itself, use the normal "Delete" button from Menu options. It will also delete Chart of Accounts, Chart of Cost Centers and Warehouse records for that company.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Adding Attachments to Outgoing Messages</h1>
|
||||
#Adding Attachments to Outgoing Messages
|
||||
|
||||
ERPNext has in-built file manage system. Click [here](https://erpnext.com/kb/tools/managing-attachments) to learn more on how attachments are managed in ERPNext.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Checking Link Between Documents</h1>
|
||||
#Checking Link Between Documents
|
||||
|
||||
Linked With function in ERPNext allows you checking a document is linked with which other documents. You will find Linked With function in the every document.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Delete Submitted Document</h1>
|
||||
#Delete Submitted Document
|
||||
|
||||
ERPNext allows you to assign deletion permission exclusively to User. Only those users will be able to delete records. Click [here](/user-guide/setting-up/permissions/role-based-permissions) to learn more about permissions.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Duplicate a Record</h1>
|
||||
#Duplicate a Record
|
||||
|
||||
ERPNext allows you to duplicate existing record. With this, you get values of existing record into new form, and create entries faster.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Adding Attachments in a Documents</h1>
|
||||
#Adding Attachments in a Documents
|
||||
|
||||
ERPNext allows to attach files with documents like Order, Invoices, Items etc. User with a read permission on particular document will also be able to access files attached with it. For example, Sales Order can have text file attached detailing item description and specification as decided with customers. Also it can be image file of drawing as per which product is to be manufactured.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Merging Documents </h1>
|
||||
#Merging Documents
|
||||
|
||||
Document merging feature is available in ERPNext. You can done this via 'Rename' feature in ERPNext.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Rename Tool</h1>
|
||||
#Rename Tool
|
||||
|
||||
ERPNext has Renaming Tool which allows you to rectify/change record id for existing records. This facility can be only performed by User with System Manager's role.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Renaming Documents</h1>
|
||||
#Renaming Documents
|
||||
|
||||
ERPNext has Renaming feature which allows you to correct primary id of a record.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Search Filters</h1>
|
||||
#Search Filters
|
||||
|
||||
Search Filter option allows user to filter records based on value in the specific fields of that form.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<h1>Tree Master Renaming</h1>
|
||||
#Tree Master Renaming
|
||||
|
||||
There are various master which are maintained in tree structure. Click [here](https://erpnext.com/kb/setup/managing-tree-structure-masters) to learn more about tree structured masters in ERPNext.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user