mirror of
https://github.com/erpnext/foundation.git
synced 2026-10-17 02:10:45 +02:00
[Docs] Updated Documentations
This commit is contained in:
frappe-pr-bot
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,16 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Krankenversicherung
|
||||
|
||||
Krankenversicherung ist eine wichtige Information, die dem Arbeitnehmer beigefügt ist.
|
||||
|
||||
Um Krankenversicherungssätze anzulegen:
|
||||
|
||||
> Personalwesen > Krankenversicherung > Neu
|
||||
|
||||
<img class="screenshot" alt="Employee" src="{{docs_base_url}}/assets/img/human-resources/health-insurance.png">
|
||||
|
||||
Im Datensatz Mitarbeiter können Sie den Leistungserbringer anhängen und die Krankenkassennummer eingeben.
|
||||
|
||||
<img class="screenshot" alt="Employee" src="{{docs_base_url}}/assets/img/human-resources/insurance-no.gif">
|
||||
|
||||
{next}
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,6 +1,6 @@
|
||||
introduction
|
||||
bill-of-materials
|
||||
production-order
|
||||
work-order
|
||||
workstation
|
||||
operation
|
||||
subcontracting
|
||||
|
||||
@@ -1,100 +0,0 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Fertigungsauftrag
|
||||
<span class="text-muted contributed-by">Beigetragen von CWT Connector & Wire Technology GmbH</span>
|
||||
|
||||
Der Fertigungsauftrag (auch als Arbeitsauftrag bezeichnet) ist ein Dokument welches vom Produktionsplaner als Startsignal in die Fertigung gegeben wird, um eine bestimmte Anzahl eines bestimmten Artikels zu produzieren. Der Fertigungsauftrag unterstützt Sie auch dabei den Materialbedarf (Lagerbuchung) für diesen Artikel aus der **Stückliste** zu generieren.
|
||||
|
||||
Der **Fertigungsauftrag** wird aus dem **Werkzeug zur Fertigungsplanung** generiert, basierend auf den Kundenaufträgen. Sie können weiterhin direkt einen Fertigungsauftrag erstellen über:
|
||||
|
||||
> Fertigung > Dokumente > Fertigungsauftrag > Neu
|
||||
|
||||
<img class="screenshot" alt="Fertigungsauftrag" src="{{docs_base_url}}/assets/img/manufacturing/production-order.png">
|
||||
|
||||
### Einen Fertigungsauftrag erstellen
|
||||
|
||||
* Wählen Sie den Artikel aus, der gefertigt werden soll.
|
||||
* Die Standard-Stückliste für diesen Artikel wird aus dem System gezogen. Sie können die Stückliste auch ändern.
|
||||
* Wenn die ausgewählte Stückliste auch Arbeitsgänge mit berücksichtigt, sollte das System alle Arbeitsgänge aus der Stückliste übernehmen.
|
||||
* Geben Sie das geplante Startdatum an (ein geschätztes Datum zu dem die Produktion beginnen soll).
|
||||
* Wählen Sie das Lager aus. Das Fertigungslager ist der Ort zu dem die Artikel gelangen, wenn Sie mit der Herstellung beginnen, und das Eingangslager ist der Ort, wo fertige Erzeugnisse lagern, bevor sie versandt werden.
|
||||
|
||||
> Anmerkung: Sie können einen Fertigungsauftrag abspeichern ohne ein Lager auszuwählen. Lager sind jedoch zwingend erforderlich um einen Fertigungsauftrag zu übertragen.
|
||||
|
||||
### Arbeitsplätze neu zuordnen/Dauer von Arbeitsgängen
|
||||
|
||||
* Als Voreinstellung zieht das System Arbeitsplätze und die Dauer von Arbeitsgängen aus der gewählten Stückliste.
|
||||
|
||||
<img class="screenshot" alt="Fertigungsauftrag - Arbeitsgänge" src="{{docs_base_url}}/assets/img/manufacturing/PO-operations.png">
|
||||
|
||||
* Wenn Sie den Arbeitsplatz für einen bestimmten Arbeitsgang im Fertigungsauftrag neu zuordnen möchten, können Sie das tun, bevor Sie den Fertigungsauftrag übertragen.
|
||||
|
||||
<img class="screenshot" alt="Fertigungsauftrag - Arbeitsgänge neu zuordnen" src="{{docs_base_url}}/assets/img/manufacturing/PO-reassigning-operations.png">
|
||||
|
||||
* Wählen Sie den betreffenden Arbeitsgang aus und ändern Sie seinen Arbeitsplatz.
|
||||
* Sie können auch die Dauer des Arbeitsgangs ändern.
|
||||
|
||||
### Kapazitätsplanung im Fertigungsauftrag
|
||||
|
||||
* Wenn ein Fertigungsauftrag basierend auf dem geplanten Startdatum und der Verfügbarkeit des Arbeitsplatzes übertragen wird, plant das System alle Arbeitsgänge für den Fertigungsauftrag ein (wenn der Fertigungsauftrag selbst Arbeitsgänge enthält).
|
||||
|
||||
### Material der Fertigung übergeben
|
||||
|
||||
* Wenn Sie Ihren Fertigungsauftrags übertragen haben, müssen Sie das Rohmaterial übertragen um den Fertigungsprozess zu starten.
|
||||
* Das erstellt eine Lagerbuchung mit allen Artikeln, die benötigt werden, um diesen Fertigungsauftrag abzuschliessen. Die Artikel werden an das Fertigungslager übertragen (dieser Prozess fügt basierend auf Ihren Einstellungen Unterbaugruppen mit Stückliste als EINEN Artikel hinzu oder löst die Unterpunkte auf).
|
||||
* Klicken Sie auf "Material der Fertigung übergeben".
|
||||
|
||||
<img class="screenshot" alt="Materialübertrag" src="{{docs_base_url}}/assets/img/manufacturing/PO-material-transfer.png">
|
||||
|
||||
* Geben Sie die Menge des Materials an, das übertragen werden soll.
|
||||
|
||||
<img class="screenshot" alt="Materialübertrag - Menge" src="{{docs_base_url}}/assets/img/manufacturing/PO-material-transfer-qty.png">
|
||||
|
||||
* Übertragen Sie die Lagerbuchung.
|
||||
|
||||
<img class="screenshot" alt="Lagerbuchung zum Kundenauftrag" src="{{docs_base_url}}/assets/img/manufacturing/PO-SE-for-material-transfer.png">
|
||||
|
||||
* Das an die Fertigung übertragene Material wird basierend auf der Lagerbuchung im Fertigungsauftrag aktualisiert.
|
||||
|
||||
<img class="screenshot" alt="Lagerbuchung zum Fertigungsauftrag" src="{{docs_base_url}}/assets/img/manufacturing/PO-material-transfer-updated.png">
|
||||
|
||||
### Zeitprotokoll erstellen
|
||||
|
||||
* Der Fortschritt des Fertigungsauftrages kann über ein [Zeitprotokoll]<img class="screenshot" alt="Make TL against PO" src="{{docs_base_url}}/assets/img/manufacturing/PO-operations-make-tl.png"> mitprotokolliert werden.
|
||||
* Zeitprotokolle werden zu den Arbeitsgängen des Fertigungsauftrages erstellt.
|
||||
* Vorlagen für Zeitprotokolle werden für die eingeplanten Arbeitsgänge zum Zeitpunkt des Übertragens des Fertigungsauftrages erstellt.
|
||||
* Um weitere Zeitprotokolle zu einem Arbeitsgang zu erstellen, wählen Sie "Zeitprotokoll erstellen" im betreffenden Arbeitsgang aus.
|
||||
|
||||
<img class="screenshot" alt="Zeitprotokoll zum Fertigungsauftrag erstellen" src="{{docs_base_url}}/assets/img/manufacturing/PO-operations-make-tl.png">
|
||||
|
||||
### Fertige Erzeugnisse aktualisieren
|
||||
|
||||
* Wenn Sie den Fertigungsauftrag fertiggestellt haben, müssen Sie die Fertigen Erzeugnisse aktualisieren.
|
||||
* Das erstellt eine Lagerbuchung, welche alle Unterartikel vom Fertigungslager abzieht und dem Lager "Fertige Erzeugnisse" gutschreibt.
|
||||
* Klicken Sie auf "Fertige Erzeugnisse aktualisieren".
|
||||
|
||||
<img class="screenshot" alt="Fertigerzeugnisse aktualiseren" src="{{docs_base_url}}/assets/img/manufacturing/PO-FG-update.png">
|
||||
|
||||
* Geben Sie die Menge des übertragenen Materials an.
|
||||
|
||||
<img class="screenshot" alt="Menge der Fertigerzeugnisse aktualisieren" src="{{docs_base_url}}/assets/img/manufacturing/PO-FG-update-qty.png">
|
||||
|
||||
>Tipp: Sie können einen Fertigungsauftrag auch teilweise fertig stellen, indem Sie über eine Lagerbuchung das Lager Fertige Erzeugnisse aktualisieren.
|
||||
|
||||
### Einen Fertigungsauftrag anhalten
|
||||
|
||||
* Wenn Sie einen Fertigungsauftrag anhalten, wird sein Status auf "Angehalten" gesetzt, mit der Folge, dass alle Herstellungsprozesse für diesen Fertigungsauftrag eingestellt werden.
|
||||
* Um den Fertigungsauftrag anzuhalten klicken Sie auf die Schaltfläche "Anhalten".
|
||||
|
||||
1. Wenn Sie den Fertigungsauftrag übertragen, reserviert das System für jeden Arbeitsgang des Fertigungsauftrags in Serie gemäß dem geplanten Startdatum basierend auf der Verfügbarkeit des Arbeitsplatzes ein Zeitfenster. Die Verfügbarkeit des Arbeitsplatzes hängt von den Arbeitszeiten des Arbeitsplatzes und der Urlaubsliste ab und davon, ob ein anderer Arbeitsgang des Fertigungsauftrages in diesem Zeitfenster eingeplant wurde. Sie können in den Fertigungseinstellungen die Anzahl der Tage angeben, in denen das System versucht den Arbeitsgang einzuplanen. Standardmäßig ist dieser Wert auf 30 Tage eingestellt. Wenn der Arbeitsgang über das verfügbare Zeitfenster hinaus Zeit benötigt, fragt Sie das System, ob der Arbeitsgang pausieren soll. Wenn das System die Terminplanung erstellen konnte, legt es Zeitprotokolle an und speichert sie. Sie können diese verändern und später übertragen.
|
||||
2. Sie können außerdem zusätzliche Zeitprotokolle für einen Arbeitsgang erstellen. Hierzu wählen Sie den betreffenden Arbeitsgang aus und klicken Sie auf "Zeitprotokoll erstellen".
|
||||
3. Rohmaterial übertragen: Dieser Schritt erstellt eine Lagerbuchung mit allen Artikeln, die benötigt werden, um dem Fertigungsauftrag abzuschliessen, und dem Fertigungslager hinzugefügt werden müssen (Unterartikel werden entweder als EIN Artikel mit Stücklister ODER in aufgelöster Form gemäß Ihren Einstellungen hinzugefügt).
|
||||
4. Fertigerzeugnisse aktualisieren: Dieser Schritt erstellt eine Lagerbuchung, welche alle Unterartikel vom Fertigungslager abzieht und dem Lager Fertige Erzeugnisse hinzufügt.
|
||||
5. Um die zum Fertigungsauftrag erstellten Zeitprotokolle anzusehen, klicken Sie auf "Zeitprotokolle anzeigen".
|
||||
|
||||
<img class="screenshot" alt="Fertigungsauftrag anhalten" src="{{docs_base_url}}/assets/img/manufacturing/PO-stop.png">
|
||||
|
||||
* Sie können auch einen angehaltenen Fertigungsauftrag wieder weiter laufen lassen.
|
||||
|
||||
> Anmerkung: Um einen Fertigungsauftrag zu einem Artikel zu erstellen müssen Sie auf dem Artikelformular das Feld "Fertigungsauftrag zulassen" ankreuzen.
|
||||
|
||||
{next}
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,2 +1 @@
|
||||
production-planning-tool
|
||||
bom-replace-tool
|
||||
bom-update-tool
|
||||
@@ -1,52 +0,0 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Werkzeug zur Fertigungsplanung
|
||||
<span class="text-muted contributed-by">Beigetragen von CWT Connector & Wire Technology GmbH</span>
|
||||
|
||||
Das Werkzeug zur Fertigungsplanung unterstützt Sie dabei die Fertigung zu planen und Artikel für eine Periode einzukaufen (normalerweise eine Woche oder ein Monat).
|
||||
|
||||
Die Liste der Artikel kann über die offenen Kundenaufträge im System erstellt werden. Folgendes wird angelegt:
|
||||
|
||||
* Fertigungsaufträge für jeden Artikel.
|
||||
* Materialanforderung für Artikel deren vorhergesagte Menge wahrscheinlich unter 0 fällt.
|
||||
|
||||
Um das Werkzeug zur Fertigungsplanung zu nutzen, gehen Sie zu:
|
||||
|
||||
> Fertigung > Werkzeuge > Werkzeug zur Fertigungsplanung
|
||||
|
||||
<img class="screenshot" alt="Werkzeug zur Fertigungsplanung" src="{{docs_base_url}}/assets/img/manufacturing/ppt.png">
|
||||
|
||||
### Schritt 1: Auswahl und Kundenauftrag
|
||||
|
||||
* Wählen Sie einen Kundenauftrag für die Materialanforderung über die Filterfunktion (Zeit, Artikel und Kunde) aus.
|
||||
* Klicken Sie auf "Kundenaufträge aufrufen" um eine Übersicht zu erhalten.
|
||||
|
||||
<img class="screenshot" alt="Werkzeug zur Fertigungsplanung" src="{{docs_base_url}}/assets/img/manufacturing/ppt-get-sales-orders.png">
|
||||
|
||||
### Schritt 2: Artikel aus Kundenaufträgen abrufen
|
||||
|
||||
Sie können Artikel hinzufügen, entfernen oder die Menge dieser Artikel verändern.
|
||||
|
||||
<img class="screenshot" alt="Werkzeug zur Fertigungsplanung" src="{{docs_base_url}}/assets/img/manufacturing/ppt-get-item.png">
|
||||
|
||||
### Schritt 3: Fertigungsaufträge erstellen
|
||||
|
||||
<img class="screenshot" alt="Werkzeug zur Fertigungsplanung" src="{{docs_base_url}}/assets/img/manufacturing/ppt-create-production-order.png">
|
||||
|
||||
### Schritt 4: Materialanfragen erstellen
|
||||
|
||||
Erstellen Sie für Artikel mit prognostiziertem Engpass Materialanfragen.
|
||||
|
||||
<img class="screenshot" alt="Werkzeug zur Fertigungsplanung" src="{{docs_base_url}}/assets/img/manufacturing/ppt-create-material-request.png">
|
||||
|
||||
Das Werkzeug zur Fertigungsplanung wird auf zwei Ebenend verwendet:
|
||||
|
||||
* Auswahl von offenen Kundenaufträge einer Periode auf Basis des erwarteten Lieferdatums.
|
||||
* Auswahl von Artikeln aus diesen Kundenaufträgen.
|
||||
|
||||
Das Werkzeug erstellt eine Aktualisierung, wenn Sie bereits einen Kundenauftrag für einen bestimmten Artikel zu einem Kundenauftrag erstellt haben ("geplante Menge").
|
||||
|
||||
Sie könnenjederzeit die Artikelliste bearbeiten und die zur Fertigung geplante Menge erhöhen bzw. vermindern.
|
||||
|
||||
> Anmerkung: Wie ändern Sie einen Fertigungsplan? Des Ergebnis des Werkzeuges zur Produktionsplanung ist der Fertigungsauftrag. Sobald Ihre Aufträge erstellt wurden, können Sie sie ändern, indem Sie die Fertigungsaufträge ändern.
|
||||
|
||||
{next}
|
||||
100
foundation/www/docs/user/manual/de/manufacturing/work-order.md
Normal file
100
foundation/www/docs/user/manual/de/manufacturing/work-order.md
Normal file
@@ -0,0 +1,100 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Arbeitsauftrag
|
||||
<span class="text-muted contributed-by">Beigetragen von CWT Connector & Wire Technology GmbH</span>
|
||||
|
||||
Der Arbeitsauftrag (auch als Arbeitsauftrag bezeichnet) ist ein Dokument welches vom Produktionsplaner als Startsignal in die Fertigung gegeben wird, um eine bestimmte Anzahl eines bestimmten Artikels zu produzieren. Der Arbeitsauftrag unterstützt Sie auch dabei den Materialbedarf (Lagerbuchung) für diesen Artikel aus der **Stückliste** zu generieren.
|
||||
|
||||
Der **Arbeitsauftrag** wird aus dem **Werkzeug zur Fertigungsplanung** generiert, basierend auf den Kundenaufträgen. Sie können weiterhin direkt einen Arbeitsauftrag erstellen über:
|
||||
|
||||
> Fertigung > Dokumente > Arbeitsauftrag > Neu
|
||||
|
||||
<img class="screenshot" alt="Arbeitsauftrag" src="{{docs_base_url}}/assets/img/manufacturing/work-order.png">
|
||||
|
||||
### Einen Arbeitsauftrag erstellen
|
||||
|
||||
* Wählen Sie den Artikel aus, der gefertigt werden soll.
|
||||
* Die Standard-Stückliste für diesen Artikel wird aus dem System gezogen. Sie können die Stückliste auch ändern.
|
||||
* Wenn die ausgewählte Stückliste auch Arbeitsgänge mit berücksichtigt, sollte das System alle Arbeitsgänge aus der Stückliste übernehmen.
|
||||
* Geben Sie das geplante Startdatum an (ein geschätztes Datum zu dem die Produktion beginnen soll).
|
||||
* Wählen Sie das Lager aus. Das Fertigungslager ist der Ort zu dem die Artikel gelangen, wenn Sie mit der Herstellung beginnen, und das Eingangslager ist der Ort, wo fertige Erzeugnisse lagern, bevor sie versandt werden.
|
||||
|
||||
> Anmerkung: Sie können einen Arbeitsauftrag abspeichern ohne ein Lager auszuwählen. Lager sind jedoch zwingend erforderlich um einen Arbeitsauftrag zu übertragen.
|
||||
|
||||
### Arbeitsplätze neu zuordnen/Dauer von Arbeitsgängen
|
||||
|
||||
* Als Voreinstellung zieht das System Arbeitsplätze und die Dauer von Arbeitsgängen aus der gewählten Stückliste.
|
||||
|
||||
<img class="screenshot" alt="Arbeitsauftrag - Arbeitsgänge" src="{{docs_base_url}}/assets/img/manufacturing/PO-operations.png">
|
||||
|
||||
* Wenn Sie den Arbeitsplatz für einen bestimmten Arbeitsgang im Arbeitsauftrag neu zuordnen möchten, können Sie das tun, bevor Sie den Arbeitsauftrag übertragen.
|
||||
|
||||
<img class="screenshot" alt="Arbeitsauftrag - Arbeitsgänge neu zuordnen" src="{{docs_base_url}}/assets/img/manufacturing/PO-reassigning-operations.png">
|
||||
|
||||
* Wählen Sie den betreffenden Arbeitsgang aus und ändern Sie seinen Arbeitsplatz.
|
||||
* Sie können auch die Dauer des Arbeitsgangs ändern.
|
||||
|
||||
### Kapazitätsplanung im Arbeitsauftrag
|
||||
|
||||
* Wenn ein Arbeitsauftrag basierend auf dem geplanten Startdatum und der Verfügbarkeit des Arbeitsplatzes übertragen wird, plant das System alle Arbeitsgänge für den Arbeitsauftrag ein (wenn der Arbeitsauftrag selbst Arbeitsgänge enthält).
|
||||
|
||||
### Material der Fertigung übergeben
|
||||
|
||||
* Wenn Sie Ihren Arbeitsauftrags übertragen haben, müssen Sie das Rohmaterial übertragen um den Fertigungsprozess zu starten.
|
||||
* Das erstellt eine Lagerbuchung mit allen Artikeln, die benötigt werden, um diesen Arbeitsauftrag abzuschliessen. Die Artikel werden an das Fertigungslager übertragen (dieser Prozess fügt basierend auf Ihren Einstellungen Unterbaugruppen mit Stückliste als EINEN Artikel hinzu oder löst die Unterpunkte auf).
|
||||
* Klicken Sie auf "Material der Fertigung übergeben".
|
||||
|
||||
<img class="screenshot" alt="Materialübertrag" src="{{docs_base_url}}/assets/img/manufacturing/PO-material-transfer.png">
|
||||
|
||||
* Geben Sie die Menge des Materials an, das übertragen werden soll.
|
||||
|
||||
<img class="screenshot" alt="Materialübertrag - Menge" src="{{docs_base_url}}/assets/img/manufacturing/PO-material-transfer-qty.png">
|
||||
|
||||
* Übertragen Sie die Lagerbuchung.
|
||||
|
||||
<img class="screenshot" alt="Lagerbuchung zum Kundenauftrag" src="{{docs_base_url}}/assets/img/manufacturing/PO-SE-for-material-transfer.png">
|
||||
|
||||
* Das an die Fertigung übertragene Material wird basierend auf der Lagerbuchung im Arbeitsauftrag aktualisiert.
|
||||
|
||||
<img class="screenshot" alt="Lagerbuchung zum Arbeitsauftrag" src="{{docs_base_url}}/assets/img/manufacturing/PO-material-transfer-updated.png">
|
||||
|
||||
### Zeitprotokoll erstellen
|
||||
|
||||
* Der Fortschritt des Arbeitsauftrages kann über ein [Zeitprotokoll]<img class="screenshot" alt="Make TL against PO" src="{{docs_base_url}}/assets/img/manufacturing/PO-operations-make-tl.png"> mitprotokolliert werden.
|
||||
* Zeitprotokolle werden zu den Arbeitsgängen des Arbeitsauftrages erstellt.
|
||||
* Vorlagen für Zeitprotokolle werden für die eingeplanten Arbeitsgänge zum Zeitpunkt des Übertragens des Arbeitsauftrages erstellt.
|
||||
* Um weitere Zeitprotokolle zu einem Arbeitsgang zu erstellen, wählen Sie "Zeitprotokoll erstellen" im betreffenden Arbeitsgang aus.
|
||||
|
||||
<img class="screenshot" alt="Zeitprotokoll zum Arbeitsauftrag erstellen" src="{{docs_base_url}}/assets/img/manufacturing/PO-operations-make-tl.png">
|
||||
|
||||
### Fertige Erzeugnisse aktualisieren
|
||||
|
||||
* Wenn Sie den Arbeitsauftrag fertiggestellt haben, müssen Sie die Fertigen Erzeugnisse aktualisieren.
|
||||
* Das erstellt eine Lagerbuchung, welche alle Unterartikel vom Fertigungslager abzieht und dem Lager "Fertige Erzeugnisse" gutschreibt.
|
||||
* Klicken Sie auf "Fertige Erzeugnisse aktualisieren".
|
||||
|
||||
<img class="screenshot" alt="Fertigerzeugnisse aktualiseren" src="{{docs_base_url}}/assets/img/manufacturing/PO-FG-update.png">
|
||||
|
||||
* Geben Sie die Menge des übertragenen Materials an.
|
||||
|
||||
<img class="screenshot" alt="Menge der Fertigerzeugnisse aktualisieren" src="{{docs_base_url}}/assets/img/manufacturing/PO-FG-update-qty.png">
|
||||
|
||||
>Tipp: Sie können einen Arbeitsauftrag auch teilweise fertig stellen, indem Sie über eine Lagerbuchung das Lager Fertige Erzeugnisse aktualisieren.
|
||||
|
||||
### Einen Arbeitsauftrag anhalten
|
||||
|
||||
* Wenn Sie einen Arbeitsauftrag anhalten, wird sein Status auf "Angehalten" gesetzt, mit der Folge, dass alle Herstellungsprozesse für diesen Arbeitsauftrag eingestellt werden.
|
||||
* Um den Arbeitsauftrag anzuhalten klicken Sie auf die Schaltfläche "Anhalten".
|
||||
|
||||
1. Wenn Sie den Arbeitsauftrag übertragen, reserviert das System für jeden Arbeitsgang des Arbeitsauftrags in Serie gemäß dem geplanten Startdatum basierend auf der Verfügbarkeit des Arbeitsplatzes ein Zeitfenster. Die Verfügbarkeit des Arbeitsplatzes hängt von den Arbeitszeiten des Arbeitsplatzes und der Urlaubsliste ab und davon, ob ein anderer Arbeitsgang des Arbeitsauftrages in diesem Zeitfenster eingeplant wurde. Sie können in den Fertigungseinstellungen die Anzahl der Tage angeben, in denen das System versucht den Arbeitsgang einzuplanen. Standardmäßig ist dieser Wert auf 30 Tage eingestellt. Wenn der Arbeitsgang über das verfügbare Zeitfenster hinaus Zeit benötigt, fragt Sie das System, ob der Arbeitsgang pausieren soll. Wenn das System die Terminplanung erstellen konnte, legt es Zeitprotokolle an und speichert sie. Sie können diese verändern und später übertragen.
|
||||
2. Sie können außerdem zusätzliche Zeitprotokolle für einen Arbeitsgang erstellen. Hierzu wählen Sie den betreffenden Arbeitsgang aus und klicken Sie auf "Zeitprotokoll erstellen".
|
||||
3. Rohmaterial übertragen: Dieser Schritt erstellt eine Lagerbuchung mit allen Artikeln, die benötigt werden, um dem Arbeitsauftrag abzuschliessen, und dem Fertigungslager hinzugefügt werden müssen (Unterartikel werden entweder als EIN Artikel mit Stücklister ODER in aufgelöster Form gemäß Ihren Einstellungen hinzugefügt).
|
||||
4. Fertigerzeugnisse aktualisieren: Dieser Schritt erstellt eine Lagerbuchung, welche alle Unterartikel vom Fertigungslager abzieht und dem Lager Fertige Erzeugnisse hinzufügt.
|
||||
5. Um die zum Arbeitsauftrag erstellten Zeitprotokolle anzusehen, klicken Sie auf "Zeitprotokolle anzeigen".
|
||||
|
||||
<img class="screenshot" alt="Arbeitsauftrag anhalten" src="{{docs_base_url}}/assets/img/manufacturing/PO-stop.png">
|
||||
|
||||
* Sie können auch einen angehaltenen Arbeitsauftrag wieder weiter laufen lassen.
|
||||
|
||||
> Anmerkung: Um einen Arbeitsauftrag zu einem Artikel zu erstellen müssen Sie auf dem Artikelformular das Feld "Arbeitsauftrag zulassen" ankreuzen.
|
||||
|
||||
{next}
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -70,6 +70,16 @@ identify which Customers are profitable and which are not. Territories will
|
||||
help you set sales targets for the respective territories.
|
||||
You can also mention [Sales Person](/docs/user/manual/en/CRM/setup/sales-person.html) against a customer.
|
||||
|
||||
|
||||
<div>
|
||||
<style>.embed-container { position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; max-width: 100%; } .embed-container iframe, .embed-container object, .embed-container embed { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }
|
||||
</style>
|
||||
<div class='embed-container'>
|
||||
<iframe src='https://www.youtube.com/embed//zsrrVDk6VBs?end=212' frameborder='0' allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
### Sales Partner
|
||||
|
||||
A Sales Partner is a third party distributor / dealer / commission agent /
|
||||
|
||||
@@ -6,4 +6,12 @@ ERPNext helps you track business **Opportunities** from **Leads** and
|
||||
|
||||
The CRM Module helps maintain Leads, Oppurtunities and Customers.
|
||||
|
||||
<div>
|
||||
<div class='embed-container'>
|
||||
<iframe src='https://www.youtube.com/embed//o9XCSZHJfpA' frameborder='0' allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
{index}
|
||||
@@ -19,4 +19,9 @@ send the email to all the intended receipients by clicking on the send button.
|
||||
|
||||
<img class="screenshot" alt="Newsletter - Test" src="{{docs_base_url}}/assets/img/crm/newsletter-test.png">
|
||||
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/muLKsCrrDRo?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
{next}
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -60,4 +60,10 @@ advance in the advances table. The accounting will be adjusted accordingly.
|
||||
|
||||
Save and submit the Sales Invoice.
|
||||
|
||||
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/J46-6qtyZ9U?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
{next}
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,14 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Bulk Payment Entry
|
||||
|
||||
If you want to create a single payment entry adjusting against multiple invoices, follow the steps given below.
|
||||
|
||||
* Make a "New Payment Entry".
|
||||
* Select a Party Type and Party. On selection of a Party, all the outstanding invoices will be fetched for that Customer/Supplier.
|
||||
* Enter the Payment Amount.
|
||||
* Allocate the amount against invoices/orders as needed.
|
||||
* Save and Submit Payment Entry.
|
||||
|
||||
### Demo of Bulk Payment Entry
|
||||
|
||||
<img class="screenshot" alt="Bulk Payment" src="{{docs_base_url}}/assets/img/accounts/bulk-payment.gif">
|
||||
@@ -0,0 +1,15 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Exchange Rate Field Frozen
|
||||
|
||||
In ERPNext, you can fetch Exchange Rates between currencies in real-time, or save specific exchange rates as well. In ERPNext, saved exchange rates are also referred as Stale Exchange Rate.
|
||||
|
||||
In your sales and purchase transactions, if the field of Currency Exchange Rate is frozen, that is because the feature of allowing stale exchange rates in transactions is enabled. To you wish to make Currency Exchange Rate field editable again, then disable the feature of Stale Exchange Rate from:
|
||||
|
||||
* Accounts > Setup > Accounts Settings
|
||||
* Uncheck field "Allow Stale Exchange Rates".
|
||||
<img class="screenshot" alt="Exchange Rate Frozen" src="{{docs_base_url}}/assets/img/accounts/exchange-rate-frozen.png">
|
||||
* Save Account Settings
|
||||
* Refresh your ERPNext account
|
||||
* Check Sales / Purchase transaction once again
|
||||
|
||||
After this setting, the Exchange Rate field in the transactions should become editable once again.
|
||||
@@ -0,0 +1,105 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# How To Manage Subscriptions With ERPNext
|
||||
|
||||
ERPNext now allows you to manage your subscriptions easily. A single subscription can contain multiple plans. At
|
||||
the same time, A single subscriber can also have multiple subscriptions. ERPNext also automatically manages your
|
||||
subscriptions for you by generating new invoices when due and changing the subscription status for you.
|
||||
|
||||
## Related Doctypes
|
||||
### Subscriber
|
||||
Like its name suggests, the Subscriber Doctype represents your subscribers and each record is linked to a single
|
||||
Customer.
|
||||
|
||||
<img alt="Subscriber form" class="screenshot" src="{{docs_base_url}}/assets/img/articles/subscriber.png">
|
||||
|
||||
### Subscription Plan
|
||||
Each Subscription Plan is linked to a single Item and contains billing and pricing information on the Item. You can have
|
||||
multiple Subscription Plans for a single Item. An example of a situation where you would want this is where you have
|
||||
different prices for the same Item like when you have a basic option and premium option for a service.
|
||||
|
||||
<img alt="Subscription Plan Form" class="screenshot" src="{{docs_base_url}}/assets/img/articles/subscription-plan.png">
|
||||
|
||||
### Subscription Settings
|
||||
Subscription Settings is where you tweak the behaviour of the Subscription Doctype. For example, you can set a grace
|
||||
period for overdue invoices from it. You can also elect to have a subscription cancelled if an overdue invoice is not
|
||||
paid after the grace period.
|
||||
|
||||
<img alt="Subscription Settings Form" class="screenshot" src="{{docs_base_url}}/assets/img/articles/subscription-settings.png">
|
||||
|
||||
## Creating A Subscription
|
||||
To create a Subscription, go to the Subscription creation form
|
||||
`Explore > Accounts > Subscriptions`
|
||||
|
||||
<img alt="Subscription form" class="screenshot" src="{{docs_base_url}}/assets/img/articles/subscription-1.png">
|
||||
|
||||
Select a Subscriber.
|
||||
|
||||
If you want to cancel a subscription at the end of the present billing cycle, check the 'Cancel At End Of Period'
|
||||
check box.
|
||||
|
||||
Select the start date for the subscription. By default, the start date is today's date. (Optional).
|
||||
|
||||
If you are giving the subscriber a trial, enter the Trial Period Start Date and Trial Period End Date.
|
||||
|
||||
If your invoice is not payable immediately, you can set the number of days before the invoice will be due in the
|
||||
'Days Until Due' field.
|
||||
|
||||
If you require more than one unit of a plan, set it in the 'Quantity' field. For instance, a web developer is subscribed
|
||||
to your web hosting service. The developer buys a plan for each customer. Instead of having multiple subscriptions for
|
||||
the same plan, you can simply increase the quantity as needed.
|
||||
|
||||
In the 'Plan' table, add Subscription Plans as required. You may have multiple Subscription Plans in a single
|
||||
Subscription as long as they all have the same billing period cycle. If the same Subscriber needs to subscribe to
|
||||
plans with different billing cycles, you will have to use a separate subscription.
|
||||
|
||||
Select a Sales Taxes and Charges Template if you need to charge tax in your invoices.
|
||||
|
||||
Fill the relevant fields in the 'Discounts' section if you need to add discounts to your invoices.
|
||||
|
||||
Click Save.
|
||||
|
||||
### Subscription Status
|
||||
ERPNext Subscription has five status values:
|
||||
- **Trialling** - A subscription that is in trial period
|
||||
- **Active** - A subscription that does not have any unpaid invoice
|
||||
- **Past Due** - A subscription whose most recent invoice is unpaid but is still within the grace period
|
||||
- **Unpaid** - A subscription whose most recent invoice is unpaid and past the grace period
|
||||
- **Canceled** - A subscription whose most recent invoice is unpaid and past the grace period. In this state, ERPNext no longer monitors the subscription.
|
||||
|
||||
### Subscription Processing In The Background
|
||||
Every one hour interval, ERPNext processes all Subscriptions and updates each for any change in status. It will
|
||||
create new invoices if need be. When an outstanding invoice is paid, ERPNext updates the subscription accordingly.
|
||||
|
||||
### Manually Updating Subscriptions
|
||||
Once you have saved a subscription, you can change the 'Days Until Due', 'Quantity', 'Plans', 'Sales Taxes and Charges
|
||||
Template', 'Apply Additional Discount On', 'Additional Discount Percentage' and 'Additional Discount Amount' fields.
|
||||
|
||||
Note that changing any of the values will reflect in newly generated invoices only. Previously generated invoices will
|
||||
not be changed.
|
||||
|
||||
### Cancelling Subscriptions
|
||||
To cancel a Subscription, simply click the 'Cancel Subscription' button. The subscription will update its 'Cancellation
|
||||
Date' field and the subscription will no longer be monitored.
|
||||
|
||||
If you are cancelling an active subscription, an invoice will immediately be generated. The generated invoice will be on
|
||||
pro-rata basis by default. If you want ERPNext always create an invoice for the full amount, uncheck the 'Prorate' field
|
||||
in Subsciption Settings.
|
||||
|
||||
### Restarting Subscriptions
|
||||
To restart a canceled subscription, simply click the 'Restart Subscription' button. Note the Subscription will empty
|
||||
its invoices table. Note that the invoices will still exist but the Subscription will no longer track them. The start
|
||||
date of the subscription will also be changed to the date the Subscription is restarted. The start of the billing
|
||||
cycle will also be set to the date the Subscription is restarted.
|
||||
|
||||
### Recalculating Subscriptions
|
||||
Some times, a Subscription's status might have changed but might not yet be reflected in the Subscription. You can force
|
||||
ERPNext to update the subscription by clicking 'Fetch Subscription Updates'.
|
||||
|
||||
### Subscription Settings
|
||||
**Grace Period** represents the number of days after a subscriber's invoice becomes overdue that ERPNext should delay
|
||||
before changing the Subscription status to 'Canceled' or 'Unpaid'.
|
||||
|
||||
**Cancel Invoice After Grace Period** would cause ERPNext to automatically cancel a subscription if it is not paid before the grace period elapses. This setting is off by default.
|
||||
|
||||
**Prorate** would cause ERPNext to generate a prorated invoice when an active subscription is canceled by default.
|
||||
If you would prefer a full invoice, uncheck the setting.
|
||||
@@ -14,4 +14,7 @@ withdrawing-salary-from-owners-equity-account
|
||||
adjust-withhold-amount-payment-entry
|
||||
common-receivable-account.md
|
||||
types-in-tax-template
|
||||
freeze-account
|
||||
freeze-account
|
||||
round-off-account-validation
|
||||
exchange-rate-field-frozen
|
||||
bulk-payment-entry
|
||||
@@ -0,0 +1,31 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Round of Account Validation Message
|
||||
|
||||
**Question**
|
||||
|
||||
When submitting an invoice, why does it ask for a Round Off Account? How to update it?
|
||||
|
||||
<img class="screenshot" alt="Fees Section" src="{{docs_base_url}}/assets/img/accounts/round-off-account.png">
|
||||
|
||||
**Answer**
|
||||
|
||||
In the Purchase Invoice, Grand Total is calculated based on various calculations like:
|
||||
|
||||
- Qty * Rate = Amount
|
||||
- Tax and other charges applied to each item
|
||||
- Discount applied to some or all the items
|
||||
- Multiplication with exchange rate, in case of multiple currencies
|
||||
|
||||
As a result of multiple calculations, there could be some rounding loss in the final amount. This rounding loss is generally very marginal like 0.034. But for the accounting accuracy, has to be posted in the accounts. Hence, you need to define a default Round-Off account in the Company master in which such amount availed as a result of rounding loss can be booked.
|
||||
|
||||
You need to create Round-off Account in the Chart of Accounts and update in the Company master. Steps here.
|
||||
|
||||
* Accounts > Chart of Accounts
|
||||
* In the Chart of Account, check or create new Account under Expense > Direct Expense. Ignore if account for this purpose already existing
|
||||
* Come to Company master
|
||||
Account > Company
|
||||
* Open Company in which Round-Off account has to be updated.
|
||||
* In the Company master, scroll to Accounts Settings and select Round-Off account and Cost Center.
|
||||
<img class="screenshot" alt="Fees Section" src="{{docs_base_url}}/assets/img/accounts/company-round-off-account.png">
|
||||
|
||||
Once Round-Off account this updated in the Company master, then try to submit Purchase Invoice once again.
|
||||
@@ -1,5 +1,5 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
#Tracking Project Profibitability using Cost Center
|
||||
#Tracking Project Profitability using Cost Center
|
||||
|
||||
To track expenses and profibility for a project, you can use Cost Centers. You should create separate Cost Center for each Project. This will allow you to.
|
||||
|
||||
@@ -78,4 +78,4 @@ To check Budget Variance report, go to:
|
||||
|
||||
[Click here to learn how to do budgeting from Cost Center](/docs/user/manual/en/accounts/budgeting.html).
|
||||
|
||||
<!-- markdown -->
|
||||
<!-- markdown -->
|
||||
|
||||
@@ -56,4 +56,9 @@ Accounts > Budget and Cost Center > Budget Variance Report
|
||||
|
||||
<img class="screenshot" alt="Budget Variance Report" src="{{docs_base_url}}/assets/img/accounts/budget-variance-report.png">
|
||||
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/wWHkB0jlXNk?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
{next}
|
||||
|
||||
@@ -156,4 +156,14 @@ Typically, you might want to create Accounts for
|
||||
* Types of Sales (for example, Product Sales, Service Sales etc.) under Income.
|
||||
* Types of Assets (building, machinery, furniture etc.) under Fixed Assets.
|
||||
|
||||
|
||||
<div>
|
||||
<div class="embed-container">
|
||||
<iframe src='https://www.youtube.com/embed//AcfMCT7wLLo' frameborder='0' allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
{next}
|
||||
|
||||
@@ -11,6 +11,11 @@ In ERPNext, your accounting operations consists of 3 main transactions:
|
||||
* Purchase Invoice: Bills that your Suppliers give you for their products or services.
|
||||
* Journal Entries: For accounting entries, like payments, credit and other types.
|
||||
|
||||
<div class="embed-containers">
|
||||
<iframe src="https://www.youtube.com/embed/5wjollWN0OA?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
### Topics
|
||||
|
||||
{index}
|
||||
|
||||
@@ -2,6 +2,7 @@ chart-of-accounts
|
||||
opening-accounts
|
||||
sales-invoice
|
||||
point-of-sale-pos-invoice
|
||||
point-of-sales
|
||||
purchase-invoice
|
||||
payments
|
||||
journal-entry
|
||||
|
||||
@@ -105,4 +105,12 @@ Here, select the company and type of invoice (sales or purchase) and add a line
|
||||
|
||||
<img class="screenshot" alt="Opening Invoice Creation Tool" src="{{docs_base_url}}/assets/img/accounts/opening-invoice-creation-tool.png">
|
||||
|
||||
|
||||
<div>
|
||||
<div class='embed-container'>
|
||||
<iframe src='https://www.youtube.com/embed//U5wPIvEn-0c' frameborder='0' allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
{next}
|
||||
|
||||
@@ -11,6 +11,10 @@ The documents you can attach Payment Terms to are:
|
||||
|
||||
Note that the introduction of Payment Terms removes "Credit Days" and "Credit Days Based On" fields in Customer/Supplier master. Payment Term contains the same information and makes it more flexible to use.
|
||||
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/Z91oWYJx6yA?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
## Payment Terms
|
||||
Navigate to the Payment Term list page and click "New".
|
||||
> Accounts > Payment Term > New Payment Term
|
||||
|
||||
@@ -1,119 +1,23 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Point of Sale Invoice
|
||||
|
||||
For retail operations, the delivery of goods, accrual of sale and payment all happens in one event, that is usually called the “Point of Sale” (POS).
|
||||
The one-screen point-of-sale software, for the one-stop-shop retail business. It does everything your store needs, right from POS billing,
|
||||
to purchasing, to customer relationship management.
|
||||
|
||||
<iframe width="660" height="371" src="https://www.youtube.com/embed/4WkelWkbP_c" frameborder="0" allowfullscreen></iframe>
|
||||
<img class="screenshot" alt="POS Invoice" src="{{docs_base_url}}/assets/img/accounts/retail-hero.jpg">
|
||||
|
||||
###Offline POS
|
||||
### Offline POS
|
||||
|
||||
In the retails business, invoicing needs to done very quickly, hence should less dependency. In the ERPNext, you can create POS Invoices, even when not connected to the internet.
|
||||
|
||||
POS Invoices created in the offline mode will be saved locally in the browser. If internet connection is lost which creating POS Invoice, you will still be able can proceed forward. Once internet connection is available again, offline invoices will be synced, and pushed onto your ERPNext account. To learn more on how POS Invoices can be created when offline, [check here.](https://frappe.io/blog/blog/erpnext-features/offline-pos-in-erpnext-7)
|
||||
<img class="screenshot" alt="POS Invoice" src="{{docs_base_url}}/assets/img/accounts/invoice.jpg">
|
||||
|
||||
#### POS Profile
|
||||
### POS Demo
|
||||
|
||||
In ERPNext all Sales and Purchase transactions, like Sales Invoice, Quotation, Sales Order, Purchase Order etc. can be edited via the POS. There two steps to Setup POS:
|
||||
Here is the quick demonstration on the Point of Sale feature of ERPNext.
|
||||
|
||||
1. Enable POS View via (Setup > Customize > Feature Setup)
|
||||
2. Create a [POS Profile](/docs/user/manual/en/setting-up/pos-setting.html) record
|
||||
|
||||
#### Different sections of the POS
|
||||
|
||||
* Update Stock: If this is checked, Stock Ledger Entries will be made when you “Submit” this Sales Invoice thereby eliminating the need for a separate Delivery Note.
|
||||
* In your Items table, update inventory information like Warehouse (saved as default), Serial Number, or Batch Number if applicable.
|
||||
* Update Payment Details like your Bank / Cash Account, Paid amount etc.
|
||||
* If you are writing off certain amount. For example when you receive extra cash as a result of not having exact denomination of change, check on ‘Write off Outstanding Amount’ and set the Account.
|
||||
|
||||
|
||||
### Customer
|
||||
|
||||
In POS, user can select the existing customer during making an order or create the new customer. This features works in the offline mode also. User can also add the customer details like contact number, address details etc on the form. The customer which has been created from the POS will be synced when the internet connection is active.
|
||||
|
||||
<img class="screenshot" alt="POS Customer" src="{{docs_base_url}}/assets/img/accounts/pos-customer.png">
|
||||
|
||||
### Adding an Item
|
||||
|
||||
At the billing counter, the retailer needs to select Items which the consumer buys. In the POS interface you can select an Item by two methods. One, is by clicking on the Item image and the other, is through the Barcode / Serial No.
|
||||
|
||||
**Select Item** \- To select a product click on the Item image and add it into the cart. A cart is an area that prepares a customer for checkout by allowing to edit product information, adjust taxes and add discounts.
|
||||
|
||||
**Barcode / Serial No** \- A Barcode / Serial No is an optical machine-readable representation of data relating to the object to which it is attached. Enter Barcode / Serial No in the box as shown in the image below and pause for a second, the item will be automatically added to the cart.
|
||||
|
||||
<img class="screenshot" alt="POS Item" src="{{docs_base_url}}/assets/img/accounts/pos-item.png">
|
||||
|
||||
> Tip: To change the quantity of an Item, enter your desired quantity in the
|
||||
quantity box. These are mostly used if the same Item is purchased in bulk.
|
||||
|
||||
If your product list is very long use the Search field, type the product name
|
||||
in Search box.
|
||||
|
||||
### Removing an Item from the Cart
|
||||
|
||||
1. Select row in the cart and clik on delete button in the numeric keypad
|
||||
|
||||
<img class="screenshot" alt="POS Item" src="{{docs_base_url}}/assets/img/accounts/pos_deleted_item.gif">
|
||||
|
||||
|
||||
2. Set Qty as zero to remove Item from the POS invoice. There are two ways to remove an Item.
|
||||
|
||||
* If Item's Qty is 1, click on a minus sign to make it zero.
|
||||
|
||||
* Manually enter 0(zero) quantity.
|
||||
|
||||
### Make Payment
|
||||
|
||||
After all the Items and their quantities are added into the cart, you are
|
||||
ready to make the Payment. Payment process is divided into 3 steps -
|
||||
|
||||
1. Click on “Make Payment” to get the Payment window.
|
||||
2. Select your “Mode of Payment”.
|
||||
3. Click on “Pay” button to Save the document.
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/pos-payment.png">
|
||||
|
||||
Submit the document to finalise the record. After the document is submitted,
|
||||
you can either print or email it directly to the customer.
|
||||
|
||||
### Write off Amount
|
||||
|
||||
Outstanding amount can be write off from the POS, user has to enter the amount under write off field on the payment screen.
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/write-off.png">
|
||||
|
||||
System books the write off amount into the ledger which has selected on the POS Profile.
|
||||
|
||||
### Change Amount
|
||||
|
||||
POS calculate the extra amount paid by the customer, which user can return from the cash account. User has to set the account for the change amount on the POS profile.
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/change-amount.png">
|
||||
|
||||
### Offline Records
|
||||
All the records from the POS stores into the browser's local storegae and sync submitted records after every minute of the interval if system is connected to internet. User can view the offline records by clicking on Menu > View Offline Records
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/offline-records.png">
|
||||
|
||||
#### Accounting entries (GL Entry) for a Point of Sale:
|
||||
|
||||
Debits:
|
||||
|
||||
* Customer (grand total)
|
||||
* Bank / Cash (payment)
|
||||
|
||||
Credits:
|
||||
|
||||
* Income (net total, minus taxes for each Item)
|
||||
* Taxes (liabilities to be paid to the government)
|
||||
* Customer (payment)
|
||||
* Write Off (optional)
|
||||
* Account for Change Amount (optional)
|
||||
|
||||
To see entries after “Submit”, click on “View Ledger”.
|
||||
|
||||
### Email
|
||||
User can send email from the POS, after submission of an order, user has to click on menu > email
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/pos-email.png">
|
||||
After sync of an order, email sent to the customer with the print of the bill in the attachment
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/4WkelWkbP_c" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
{next}
|
||||
|
||||
118
foundation/www/docs/user/manual/en/accounts/point-of-sales.md
Normal file
118
foundation/www/docs/user/manual/en/accounts/point-of-sales.md
Normal file
@@ -0,0 +1,118 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Point of Sale Invoice
|
||||
|
||||
For retail operations, the delivery of goods, accrual of sale and payment all happens in one event, that is usually called the “Point of Sale” (POS).
|
||||
|
||||
<iframe width="660" height="371" src="https://www.youtube.com/embed/4WkelWkbP_c" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
###Offline POS
|
||||
|
||||
In the retails business, invoicing needs to done very quickly, hence should less dependency. In the ERPNext, you can create POS Invoices, even when not connected to the internet.
|
||||
|
||||
POS Invoices created in the offline mode will be saved locally in the browser. If internet connection is lost which creating POS Invoice, you will still be able can proceed forward. Once internet connection is available again, offline invoices will be synced, and pushed onto your ERPNext account. To learn more on how POS Invoices can be created when offline, [check here.](https://frappe.io/blog/blog/erpnext-features/offline-pos-in-erpnext-7)
|
||||
|
||||
#### POS Profile
|
||||
|
||||
In ERPNext all Sales and Purchase transactions, like Sales Invoice, Quotation, Sales Order, Purchase Order etc. can be edited via the POS. There two steps to Setup POS:
|
||||
|
||||
1. Enable POS View via (Setup > Customize > Feature Setup)
|
||||
2. Create a [POS Profile](/docs/user/manual/en/setting-up/pos-setting.html) record
|
||||
|
||||
#### Different sections of the POS
|
||||
|
||||
* Update Stock: If this is checked, Stock Ledger Entries will be made when you “Submit” this Sales Invoice thereby eliminating the need for a separate Delivery Note.
|
||||
* In your Items table, update inventory information like Warehouse (saved as default), Serial Number, or Batch Number if applicable.
|
||||
* Update Payment Details like your Bank / Cash Account, Paid amount etc.
|
||||
* If you are writing off certain amount. For example when you receive extra cash as a result of not having exact denomination of change, check on ‘Write off Outstanding Amount’ and set the Account.
|
||||
|
||||
### Customer
|
||||
|
||||
In POS, user can select the existing customer during making an order or create the new customer. This features works in the offline mode also. User can also add the customer details like contact number, address details etc on the form. The customer which has been created from the POS will be synced when the internet connection is active.
|
||||
|
||||
<img class="screenshot" alt="POS Customer" src="{{docs_base_url}}/assets/img/accounts/pos-customer.png">
|
||||
|
||||
### Adding an Item
|
||||
|
||||
At the billing counter, the retailer needs to select Items which the consumer buys. In the POS interface you can select an Item by two methods. One, is by clicking on the Item image and the other, is through the Barcode / Serial No.
|
||||
|
||||
**Select Item** \- To select a product click on the Item image and add it into the cart. A cart is an area that prepares a customer for checkout by allowing to edit product information, adjust taxes and add discounts.
|
||||
|
||||
**Barcode / Serial No** \- A Barcode / Serial No is an optical machine-readable representation of data relating to the object to which it is attached. Enter Barcode / Serial No in the box as shown in the image below and pause for a second, the item will be automatically added to the cart.
|
||||
|
||||
<img class="screenshot" alt="POS Item" src="{{docs_base_url}}/assets/img/accounts/pos-item.png">
|
||||
|
||||
> Tip: To change the quantity of an Item, enter your desired quantity in the
|
||||
quantity box. These are mostly used if the same Item is purchased in bulk.
|
||||
|
||||
If your product list is very long use the Search field, type the product name
|
||||
in Search box.
|
||||
|
||||
### Removing an Item from the Cart
|
||||
|
||||
1. Select row in the cart and clik on delete button in the numeric keypad
|
||||
|
||||
<img class="screenshot" alt="POS Item" src="{{docs_base_url}}/assets/img/accounts/pos_deleted_item.gif">
|
||||
|
||||
|
||||
2. Set Qty as zero to remove Item from the POS invoice. There are two ways to remove an Item.
|
||||
|
||||
* If Item's Qty is 1, click on a minus sign to make it zero.
|
||||
|
||||
* Manually enter 0(zero) quantity.
|
||||
|
||||
### Make Payment
|
||||
|
||||
After all the Items and their quantities are added into the cart, you are
|
||||
ready to make the Payment. Payment process is divided into 3 steps -
|
||||
|
||||
1. Click on “Make Payment” to get the Payment window.
|
||||
2. Select your “Mode of Payment”.
|
||||
3. Click on “Pay” button to Save the document.
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/pos-payment.png">
|
||||
|
||||
Submit the document to finalise the record. After the document is submitted,
|
||||
you can either print or email it directly to the customer.
|
||||
|
||||
### Write off Amount
|
||||
|
||||
Outstanding amount can be write off from the POS, user has to enter the amount under write off field on the payment screen.
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/write-off.png">
|
||||
|
||||
System books the write off amount into the ledger which has selected on the POS Profile.
|
||||
|
||||
### Change Amount
|
||||
|
||||
POS calculate the extra amount paid by the customer, which user can return from the cash account. User has to set the account for the change amount on the POS profile.
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/change-amount.png">
|
||||
|
||||
### Offline Records
|
||||
All the records from the POS stores into the browser's local storegae and sync submitted records after every minute of the interval if system is connected to internet. User can view the offline records by clicking on Menu > View Offline Records
|
||||
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/offline-records.png">
|
||||
|
||||
#### Accounting entries (GL Entry) for a Point of Sale:
|
||||
|
||||
Debits:
|
||||
|
||||
* Customer (grand total)
|
||||
* Bank / Cash (payment)
|
||||
|
||||
Credits:
|
||||
|
||||
* Income (net total, minus taxes for each Item)
|
||||
* Taxes (liabilities to be paid to the government)
|
||||
* Customer (payment)
|
||||
* Write Off (optional)
|
||||
* Account for Change Amount (optional)
|
||||
|
||||
To see entries after “Submit”, click on “View Ledger”.
|
||||
|
||||
### Email
|
||||
User can send email from the POS, after submission of an order, user has to click on menu > email
|
||||
<img class="screenshot" alt="POS Payment" src="{{docs_base_url}}/assets/img/accounts/pos-email.png">
|
||||
After sync of an order, email sent to the customer with the print of the bill in the attachment
|
||||
|
||||
{next}
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -35,6 +35,6 @@ To setup your Chart of Cost Centers go to:
|
||||
|
||||
> Accounts > Setup > Chart of Cost Centers
|
||||
|
||||
<img class="screenshot" alt="Cost Center" src="{{docs_base_url}}/assets/img/chart-of-cost-center.png">
|
||||
<img class="screenshot" alt="Cost Center" src="{{docs_base_url}}/assets/img/accounts/chart-of-cost-center.png">
|
||||
|
||||
{next}
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
If you are receiving payments or making payments via cheques, the bank statements will not accurately match the dates of your entry, this is because the bank usually takes time to “clear” these payments. Also you may have mailed a cheque to your Supplier and it may be a few days before it is received and deposited by the Supplier. In ERPNext you can synchronise your bank statements and your Journal Entries using the “Bank Reconciliation” tool.
|
||||
|
||||
The Bank Reconciliation Report provide the difference between the bank balance shown in an organisation's bank statement, as provided by the ban against amount shown in the companies Chart of Accounts.
|
||||
The Bank Reconciliation Report provide the difference between the bank balance shown in an organisation's bank statement, as provided by the bank against amount shown in the companies Chart of Accounts.
|
||||
|
||||
####Bank Reconciliation Statement
|
||||
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,11 +1,17 @@
|
||||
<!-- add-breadcrumbs -->
|
||||
# Agriculture
|
||||
# ERPNext for Agriculture
|
||||
|
||||
Farmers know that even a small operation requires intensive recordkeeping. A well-run farm requires proper management of accounting, payroll, suppliers, customers and logistics to name a few areas. ERPNext already helps organize these activities.
|
||||
|
||||
<img class="screenshot" alt="Land Unit" src="{{docs_base_url}}/assets/img/agriculture/land-unit.png">
|
||||
|
||||
### Capture Land Units and Manage Crops
|
||||
|
||||
A farm requires additional attention to manage its productive units (plots of land), time sensitive crop activities (such as planting, irrigating, fertilizing, etc.), recording environmental and crop data for analysis, and reports to help make effective decisions.
|
||||
|
||||
<img class="screenshot" alt="Task" src="{{docs_base_url}}/assets/img/agriculture/agri_desk.png">
|
||||
<img class="screenshot" alt="Soil Texture" src="{{docs_base_url}}/assets/img/agriculture/soil-texture.png">
|
||||
|
||||
### ERPNext Agriculture Demo
|
||||
|
||||
The Agriculture module in ERPNext helps you keep track of your farming operations. It allows you keep records for each field where you farm, such as geospatial and soil texture characteristics. It allows you to:
|
||||
|
||||
@@ -16,8 +22,12 @@ The Agriculture module in ERPNext helps you keep track of your farming operation
|
||||
* Record sale of the harvest or transfer to warehouse for further processing
|
||||
* View reports
|
||||
|
||||
<img class="screenshot" alt="Task" src="{{docs_base_url}}/assets/img/agriculture/agri_doctypes.png">
|
||||
To see feature of ERPNext Agriculture in action, check the following demo video.
|
||||
|
||||
### Topics
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/A14cnWwE0vQ?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
### Agriculture User Manual
|
||||
|
||||
{index}
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -53,6 +53,8 @@ In the depreciation entry, the "Accumulated Depreciation Account" is credited an
|
||||
|
||||
If you are required to calculate the depreciation based on your Fiscal Year and prorated by the number of days left, select the corresponding option in "Account Settings".
|
||||
|
||||
<img class="screenshot" alt="Asset" src="{{docs_base_url}}/assets/img/asset/book-asset-depreciation-accounting-automatically.png">
|
||||
|
||||
The system will automatically set the fiscal year end date as the next depreciation date and calculate the depreciation amount prorata temporis based on the Available-for-use Date (IFRS16)
|
||||
|
||||
<img class="screenshot" alt="Asset" src="/docs/assets/img/asset/asset-prorated-depreciation.png">
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -11,6 +11,11 @@ profitability.
|
||||
ERPNext contains a set of transactions that will make your buying process as
|
||||
efficient and seamless as possible.
|
||||
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/efFajTTQBa8?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
### Topics
|
||||
|
||||
{index}
|
||||
|
||||
@@ -9,6 +9,11 @@ In ERPNext, You can create Request for Quotation directly by going to:
|
||||
|
||||
After creation of Request for Quotation, there are two ways to generate Supplier Quotation from Request for Quotation.
|
||||
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/embed/q85GFvWfZGI?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
|
||||
#### For User
|
||||
|
||||
@@ -53,3 +58,5 @@ __Step 4:__ On submission, system will create Supplier Quotation (draft mode) ag
|
||||
If a supplier indicates that they will not provide a quotation for the item, this can be indicated in the RFQ document by checking the 'No Quote' box after the Request for Quotation has been submitted.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -9,6 +9,13 @@ You can create a new Supplier from:
|
||||
|
||||
<img class="screenshot" alt="Supplier Master" src="{{docs_base_url}}/assets/img/buying/supplier-master.png">
|
||||
|
||||
<div>
|
||||
<div class='embed-container'>
|
||||
<iframe src='https://www.youtube.com/embed//zsrrVDk6VBs?start=213' frameborder='0' allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
### Contacts and Addresses
|
||||
|
||||
Contacts and Addresses in ERPNext are stored separately so that you can create multiple Contacts and Addresses for a Suppliers. Once Supplier is saved, you will find option to create Contact and Address for that Supplier.
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -1,22 +1,22 @@
|
||||
[
|
||||
{
|
||||
"route": "/docs",
|
||||
"route": "/docs",
|
||||
"title": "Docs Home"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/user",
|
||||
"route": "/docs/user",
|
||||
"title": "User Guide"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/api",
|
||||
"route": "/docs/current/api",
|
||||
"title": "Server API"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "/docs/current/models",
|
||||
"route": "/docs/current/models",
|
||||
"title": "Models (Reference)"
|
||||
},
|
||||
},
|
||||
{
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"route": "https://github.com/frappe/erpnext/tree/develop/erpnext/docs",
|
||||
"title": "Improve Docs"
|
||||
}
|
||||
]
|
||||
@@ -7,7 +7,10 @@ There are three kind of reports in ERPNext.
|
||||
|
||||
Report Builder is an in-built report customization tool in ERPNext. This allows you to define specific fields of the form which shall be added in the report. Also you can set required filters, sorting and give preferred name to report.
|
||||
|
||||
<iframe width="660" height="371" src="https://www.youtube.com/watch?v=TxJGUNarcQs" frameborder="0" allowfullscreen></iframe>
|
||||
<div class="embed-container">
|
||||
<iframe src="https://www.youtube.com/watch?v=TxJGUNarcQs?rel=0" frameborder="0" allowfullscreen>
|
||||
</iframe>
|
||||
</div>
|
||||
|
||||
### 2. Query Report
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ By **Doctype** mentioned in the Option field, we mean parent Doctype. So, just l
|
||||
---- Quotation<br>
|
||||
---- Sales Invoice<br>
|
||||
---- Employee<br>
|
||||
---- Production Order<br>
|
||||
---- Work Order<br>
|
||||
.. and so on.
|
||||
|
||||
So linking this field with parent Doctype will list all the Doctype records.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user