InfiniteERP Wiki - User contributions [en]

Attendance Machine Configuration

2022-06-10T03:08:09Z

Asp-rahmadi: /* Introduction */

= Introduction =

this Attendance Machine Configuration is created to make :
- it easy to setup machine on it own table without using preference like last time.
- Third-party app can now get last data in from attendance machine, to use as filter, so that old data will not get processed too.
- the data that will get from the API is the newest data, it will make the process fast because there is no duplicate data get inserted too.

= How to setup =

[[File:Attendance Machine Config.png|thumb]]

Open Attendance Machine Config Menu
Create Record Per API of the Machine
Example like on the picture above
Check the is Check in if the API of the Machine is to insert Check in
Check the is Check out if the API of the Machine is to insert Check out

note : for now this program is not implement check in and check out in the same API yet

Attendance Machine Configuration

2022-06-10T03:05:03Z

Asp-rahmadi: /* How to setup */

= Introduction =

= How to setup =

[[File:Attendance Machine Config.png|thumb]]

Open Attendance Machine Config Menu
Create Record Per API of the Machine
Example like on the picture above
Check the is Check in if the API of the Machine is to insert Check in
Check the is Check out if the API of the Machine is to insert Check out

note : for now this program is not implement check in and check out in the same API yet

File:Attendance Machine Config.png

2022-06-10T02:59:34Z

Asp-rahmadi:

Attendance Machine Config

Projects/WEBSTORE Sales Order DocumentType

2022-02-22T00:48:40Z

Asp-rahmadi: /* InfiniteERP Implementation */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

and the process have customize document status on Goods Shipment and Sales Invoice that being generated, the document status is configurated based on Sales Order document type. using Approval Configuration Tab on Document Type Menu.

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)
* Define Document Routing Configuration of Sales Order when complete the document status using '''org.infinite.documentrouting.porting.CustomOrderActionHandler''', if you want to change how Goods Shipment and Sales Invoice document status generated, if not you can use the default one ('''org.wirabumi.gen.oez.porting.OrderActionHandler''').
* Define generated document status of Goods Shipment and Sales Invoice on Approval Configuration Tab on Document Type Menu (if not being define the Goods Shipment and Sales Invoice document status will be generated using default process).

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===

to make the process for each document type dynamic, there is need a table that will be put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.
* and etc, it can be add depends on what client requirement is.

====Process====

the process will be put on document routing, this will make sure other client will not get impact when the implementation used on other client, from now the new document routing will be using new module org.infinite.documentrouting.
the process will be use the new table as configuration to process(approval) data, the end result is depends on configuration that used on the new document type configuration table.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-02-22T00:46:59Z

Asp-rahmadi: /* InfiniteERP Implementation */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

and the process have customize document status on Goods Shipment and Sales Invoice that being generated, the document status is configurated based on Sales Order document type. using Approval Configuration Tab on Document Type Menu.

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)
* Define Document Routing Configuration of Sales Order when complete the document status using org.infinite.documentrouting.porting.CustomOrderActionHandler, if you want to change how Goods Shipment and Sales Invoice document status generated, if not you can use the default one (org.wirabumi.gen.oez.porting.OrderActionHandler).
* Define generated document status of Goods Shipment and Sales Invoice on Approval Configuration Tab on Document Type Menu (if not being define the Goods Shipment and Sales Invoice document status will be generated using default process).

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===

to make the process for each document type dynamic, there is need a table that will be put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.
* and etc, it can be add depends on what client requirement is.

====Process====

the process will be put on document routing, this will make sure other client will not get impact when the implementation used on other client, from now the new document routing will be using new module org.infinite.documentrouting.
the process will be use the new table as configuration to process(approval) data, the end result is depends on configuration that used on the new document type configuration table.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-02-22T00:41:18Z

Asp-rahmadi: /* InfiniteERP Implementation */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

and the process have customize document status on Goods Shipment and Sales Invoice that being generated, the document status is configurated based on Sales Order document type. using Approval Configuration Tab on Document Type Menu.

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)
* Define generated document status of Goods Shipment and Sales Invoice on Approval Configuration Tab on Document Type Menu (if not being define the Goods Shipment and Sales Invoice document status will be generated using default process)

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===

to make the process for each document type dynamic, there is need a table that will be put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.
* and etc, it can be add depends on what client requirement is.

====Process====

the process will be put on document routing, this will make sure other client will not get impact when the implementation used on other client, from now the new document routing will be using new module org.infinite.documentrouting.
the process will be use the new table as configuration to process(approval) data, the end result is depends on configuration that used on the new document type configuration table.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-02-22T00:37:40Z

Asp-rahmadi: /* Overview */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

and the process have customize document status on Goods Shipment and Sales Invoice that being generated, the document status is configurated based on Sales Order document type. using Approval Configuration Tab on Document Type Menu.

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===

to make the process for each document type dynamic, there is need a table that will be put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.
* and etc, it can be add depends on what client requirement is.

====Process====

the process will be put on document routing, this will make sure other client will not get impact when the implementation used on other client, from now the new document routing will be using new module org.infinite.documentrouting.
the process will be use the new table as configuration to process(approval) data, the end result is depends on configuration that used on the new document type configuration table.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-01-05T02:56:31Z

Asp-rahmadi: /* Technical Requirements */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====
* Master Data
** Produk baru akan dibuat dan didefinisikan di InfiniteERP oleh pengguna tim Yasmeera
** Webstore secara rutin akan sinkronisasi produk baru yang ada di ERP.
** Tim Admin Webstore akan menambahkan gambar-gambar produk yang akan ditampilkan dan dilihat oleh customer.

* Transaksi Penjualan/Sales Order
** Setiap terjadi transaksi penjualan, Webstore akan melakukan update/insert data penjualan tersebut ke ERP dalam bentuk transaksi Sales Order
*** Criteria Status transaksi yang akan dikirim ke InfiniteERP akan disepakati kemudian sesuai bisnis proses.
* Proses Penjualan/Sales Order di InfiniteERP
** Setelah ERP menerima data transaksi penjualan, Tim Admin CS akan melakukan monitoring melalui window Outstanding Sales Order.
** Tim CS akan membuat prioritas dan memilih Sales Order mana yang akan diproses dan merubah Document Status pada Sales Order menjadi COMPLETED.
** Jika diperlukan, bisa dicetak dokumen PICKING LIST yang akan digunakan oleh Tim Picking di gudang untuk mengambil stock produk yang akan dikirim.
*** Picking List ini menjadi acuan transaksi untuk mengambil sejumlah produk baik Quantity maupun Lokasi Rak (storage bin). Dengan demikian stok produk disetiap rak di gudang benar-benar tepat dan akurat.

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===

to make the process for each document type dynamic, there is need a table that will be put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.
* and etc, it can be add depends on what client requirement is.

====Process====

the process will be put on document routing, this will make sure other client will not get impact when the implementation used on other client, from now the new document routing will be using new module org.infinite.documentrouting.
the process will be use the new table as configuration to process(approval) data, the end result is depends on configuration that used on the new document type configuration table.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-01-05T02:48:16Z

Asp-rahmadi: /* Technical Requirements */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====
* Master Data
** Produk baru akan dibuat dan didefinisikan di InfiniteERP oleh pengguna tim Yasmeera
** Webstore secara rutin akan sinkronisasi produk baru yang ada di ERP.
** Tim Admin Webstore akan menambahkan gambar-gambar produk yang akan ditampilkan dan dilihat oleh customer.

* Transaksi Penjualan/Sales Order
** Setiap terjadi transaksi penjualan, Webstore akan melakukan update/insert data penjualan tersebut ke ERP dalam bentuk transaksi Sales Order
*** Criteria Status transaksi yang akan dikirim ke InfiniteERP akan disepakati kemudian sesuai bisnis proses.
* Proses Penjualan/Sales Order di InfiniteERP
** Setelah ERP menerima data transaksi penjualan, Tim Admin CS akan melakukan monitoring melalui window Outstanding Sales Order.
** Tim CS akan membuat prioritas dan memilih Sales Order mana yang akan diproses dan merubah Document Status pada Sales Order menjadi COMPLETED.
** Jika diperlukan, bisa dicetak dokumen PICKING LIST yang akan digunakan oleh Tim Picking di gudang untuk mengambil stock produk yang akan dikirim.
*** Picking List ini menjadi acuan transaksi untuk mengambil sejumlah produk baik Quantity maupun Lokasi Rak (storage bin). Dengan demikian stok produk disetiap rak di gudang benar-benar tepat dan akurat.

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===

to make the process for each document type dynamic, there is need a table that put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-01-05T02:47:13Z

Asp-rahmadi: /* Technical Requirements */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====
* Master Data
** Produk baru akan dibuat dan didefinisikan di InfiniteERP oleh pengguna tim Yasmeera
** Webstore secara rutin akan sinkronisasi produk baru yang ada di ERP.
** Tim Admin Webstore akan menambahkan gambar-gambar produk yang akan ditampilkan dan dilihat oleh customer.

* Transaksi Penjualan/Sales Order
** Setiap terjadi transaksi penjualan, Webstore akan melakukan update/insert data penjualan tersebut ke ERP dalam bentuk transaksi Sales Order
*** Criteria Status transaksi yang akan dikirim ke InfiniteERP akan disepakati kemudian sesuai bisnis proses.
* Proses Penjualan/Sales Order di InfiniteERP
** Setelah ERP menerima data transaksi penjualan, Tim Admin CS akan melakukan monitoring melalui window Outstanding Sales Order.
** Tim CS akan membuat prioritas dan memilih Sales Order mana yang akan diproses dan merubah Document Status pada Sales Order menjadi COMPLETED.
** Jika diperlukan, bisa dicetak dokumen PICKING LIST yang akan digunakan oleh Tim Picking di gudang untuk mengambil stock produk yang akan dikirim.
*** Picking List ini menjadi acuan transaksi untuk mengambil sejumlah produk baik Quantity maupun Lokasi Rak (storage bin). Dengan demikian stok produk disetiap rak di gudang benar-benar tepat dan akurat.

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===
====Setup====
to make process for each document type dynamic, there is need a table that put on Menu Document Type as sub Tab, that we can use as configuration of document type, such as :
* configuration for document status of Sales Invoice that generated.
* configuration for document status of Goods Shipment that generated.
* configuration for is auto generate Payment In.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Projects/WEBSTORE Sales Order DocumentType

2022-01-05T02:41:14Z

Asp-rahmadi: /* Non-Functional Requirements */

{{WorkInProgress}}

== Functional Specifications ==
TBD

=== Overview ===
Fitur ini bertujuan untuk mempersingkat proses transaksi penjualan hingga pengiriman yang harus melalui beberapa tahap utama yaitu Sales Order > Goods Shipment > Sales Invoice > Payment In

====Purpose====
Beberapa klien apparel manufakturing memiliki online store atau market place yang digunakan untuk transaksi penjualan dengan pelanggan. Proses di ERP diharapkan semakin dipersingkat sebagai bentuk otomasi.

====References====
;POS Order - Document Type: Saat ini ERP sudah memiliki Document Type - POS Order dimana setiap transaksi Sales Order yang menjadi COMPLETED secara otomatis membentuk transaksi Goods Shipment dan Sales Invoice.

===Design Considerations===

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.

====Assumptions====
# It should be possible to operate this functionality in a pure multi-tenant implementation. In particular, this means that it should be possible for a user to initiate the creation of a new client applying an industry template in a self-service manner without having any prior access to the system and without being a system administrator.

====Dependencies====
None.

====Constraints====

===Glossary===

===Functional Requirements===

====An Example====
=====The Scenario=====
* Master Data
** Produk baru akan dibuat dan didefinisikan di InfiniteERP oleh pengguna tim Yasmeera
** Webstore secara rutin akan sinkronisasi produk baru yang ada di ERP.
** Tim Admin Webstore akan menambahkan gambar-gambar produk yang akan ditampilkan dan dilihat oleh customer.

* Transaksi Penjualan/Sales Order
** Setiap terjadi transaksi penjualan, Webstore akan melakukan update/insert data penjualan tersebut ke ERP dalam bentuk transaksi Sales Order
*** Criteria Status transaksi yang akan dikirim ke InfiniteERP akan disepakati kemudian sesuai bisnis proses.
* Proses Penjualan/Sales Order di InfiniteERP
** Setelah ERP menerima data transaksi penjualan, Tim Admin CS akan melakukan monitoring melalui window Outstanding Sales Order.
** Tim CS akan membuat prioritas dan memilih Sales Order mana yang akan diproses dan merubah Document Status pada Sales Order menjadi COMPLETED.
** Jika diperlukan, bisa dicetak dokumen PICKING LIST yang akan digunakan oleh Tim Picking di gudang untuk mengambil stock produk yang akan dikirim.
*** Picking List ini menjadi acuan transaksi untuk mengambil sejumlah produk baik Quantity maupun Lokasi Rak (storage bin). Dengan demikian stok produk disetiap rak di gudang benar-benar tepat dan akurat.

=====InfiniteERP Implementation=====
Untuk menerapkan integrasi ini dibutuhkan beberapa setup yang harus dilakukan terlebih dahulu:

''Setup Data''
* A client that represents the organization itself.
* Membuat sebuah user account yang akan digunakan Webstore untuk mengakses API
* Organization
** Define new Organization for Online WebStore called "ONLINE_STORE"
* Master Data Management
** Business Partner
** Product
*** Setiap product yang akan dijual online harus memiliki record di sub tab Product Organization
** Price List - Selling Price
** Import Business Partners
* Sales Management
** Sales Order
** Create Invoices from Orders
** Generate Invoices
** Print Invoices
* Financial Management
** Define a GL calendar with quarterly periods
** Define Financial Account / a bank account
** Define a cashbook for petty cash transactions
* Define the business partner categories:
** Distributor
** Agen
** Reseller
** Suppliers
* Define the product categories
** Ads
** Services
** Other
* Define Payment Method
* A price list adjustment to represent the discount on advertisements for business members (*)

=====The Industry Template=====

====User roles & profiles====

The user roles affected by this functionality are:
;Non-professional Functional Administrator: Typically a small business owner or trusted employee at a small business that is tasked with configuring the system to meet the requirements of the business. These users are typically computer-literate and very familiar with desktop applications and consumer web sites but does not have a formal education in computer science; they are therefore expecting a user experience comparable to the one of a consumer-grade application. They are very knowledgeable about the way their business work but are not familiar with ERPs and have never participated in a complex IT or formal business process re-engineering project.

====Business process definition====
# Users connect to an InfiniteERP instance with a ''guest user'' which has access to a role that only allows to initiate an initial client setup with industry template action.
# Users can choose to either browse a catalog of industry templates or to instantiate a client from a template they previously downloaded
# Users can initiate the client creation process using the selected industry template and specifying the organization specific data
# Optionally, an instance administrator approves the client creation (this task might include payment verification)
# The system instantiates the client, applies the template
# Users receive a notification with the login instructions

====User stories====

====Functional requirements based on business processes====

====User Interface Mockups====
TBD

===Technical Requirements===
====Setup====
;Performance: The initial client setup with the application of an industry template should complete within 30 minutes.

===Open Discussion Items===
; ''Self-service model'': In a pure self-service model - required for a full support of a pure multi-tenant system - the user should be able to initiate the creation of a new client using a template without having any previous access to the system. This action would then be considered as a request and it would need to go through a workflow which includes various steps (example: payment collection, approval, provisioning, etc.). This presupposes the existence of a workflow engine, which is not available in Openbravo. Instead, we assume that the user can connect with a guest user and initiate the action. Is this acceptable?

; ''Industry templates by organization'': Larger enterprises can have multiple organizations each implementing different lines of businesses or operations in different countries. It is therefore conceivable that a larger organization might want to implement different industry templates within a single client. The current proposal is to have a template per client. Is that acceptable? This feature targets smaller enterprises that typically have only one organization; is that areasonable simplification assumption?''

===Closed Discussion Items===

[[Category:Projects_ERP]]

Payroll Configuration

2021-12-31T03:12:12Z

Asp-rahmadi: /* Payroll Configuration */

== Payroll Configuration ==

[[image:preference_ot_minimum_overtime.png|800px]]

====Configuration====

====Execution====

Payroll Configuration

2021-12-31T03:11:58Z

Asp-rahmadi: /* Payroll Configuration */

== Payroll Configuration ==

[[image:preference_ot_minimum_overtime.png|600px]]

====Configuration====

====Execution====

File:Preference ot minimum overtime.png

2021-12-31T03:10:51Z

Asp-rahmadi:

Payroll Configuration

2021-12-31T03:10:39Z

Asp-rahmadi: Created page with "== Payroll Configuration == image:preference_ot_minimum_overtime.png ====Configuration==== ====Execution===="

== Payroll Configuration ==

[[image:preference_ot_minimum_overtime.png]]

====Configuration====

====Execution====

Human Resource Management

2021-12-31T03:07:16Z

Asp-rahmadi: /* Payroll */

{{BackTo|User Guide}}

== Introduction ==
ToDo.

This application area of Openbravo covers Requisition to Receipt and Invoicing parts of the Procure To Pay business flow and Supplier Returns business process.
For Payments Management of Procure To Pay see Financial Management // Receivables & Payables application area.

== HR Business Flow ==
Due to its complexity and different roles involved it is convenient to split Procure to Pay down into two main sub-processes:

[[image:HumanResourceBusinessFlow.png]]

====Configuration====
The following setup needs to be done before performing the process:
* Employee
* Overtime Rules
* Business Partners (Vendors & Suppliers).
* Tac Rate

'''Products''' need to be configured prior any purchase requisition is issued.
Each product that is being purchased needs to have a price in the purchase price list in order to be selectable in any transactional document like a purchase order or a purchase invoice.

'''Business Partners''' need to be configured prior any purchase requisition can automatically turns into a purchase order.
Please refer to Business Partner Setup and Business Partner for more information.

====Execution====
In Procurement Management the Procure to Pay business process is executed as follows:

Any member of the organization allowed to do so can directly issue a Requisition as a result of an organization or business unit need.

== '''Relationship with other application areas''' ==

Human Resource Management has a relationship with other application areas:
* [[Master Data Management]] as Employee Information can be maintained as Business Partner.
* [[Financial Management]] in terms of managing account payable payments.

== '''Application Menu''' ==
Please find below detailed description of all windows and reports of the Procurement Management application area.

*[[Employee Information| Employee Information]]
*[[Daily Job Activity | Daily Job Activity]]

==== '''Payroll''' ====
Payroll module provides a flexible and automated payroll workflow.
Starting from here you will learn how to operate payroll processes.

*[[Incidental Earning | Incidental Earning ]]
*[[Incidental Deduction | Incidental Deduction]]
*[[Import Incidental Earning | Import Incidental Earning]]
*[[Import Incidental Deduction | Import Incidental Deduction]]
*[[Pay Slip Individual | Pay Slip Individual]]
*[[Reimbursement | Reimbursement ]]
*[[Salary Back Payment | Salary Back Payment]]
*[[Salary Payment| Salary Payment]]

:'''Analysis Tools'''
*[[Generate Pay Slip| Generate Pay Slip]]

:'''Setup'''
*[[Salary Formula Library | Salary Formula Library ]]
*[[Payroll Configuration | Payroll Configuration ]]

==== '''Loan''' ====
*[[Installment | Installment]]
*[[Incidental Loan | Incidental Loan]]

:'''Analysis Tools'''
*[[Employee Loan Report | Employee Loan Report]]

==== '''Jamsostek''' ====
*[[Jamsostek Pension Funds Report | Jamsostek Pension Funds Report]]
*[[Jamsostek Payment Report|Jamsostek Payment Report]]

==== '''Insurance''' ====
*[[Insurance Membership | Insurance Membership]]
*[[Benefit Claim | Benefit Claim]]
:'''Setup'''
*[[Insurance Provider|Insurance Provider]]
*[[Insurance Payee|Insurance Payee]]

==== '''Overtime and Emergency Call''' ====
*[[Overtime Request|Overtime Request]]
*[[Emergency Call Request|Emergency Call Request]]
*[[Calculate Overtime Amount|Calculate Overtime Amount]]
:'''Analysis Tools'''
*[[Overtime Report|Overtime Report]]
*[[Overtime By Employee|Overtime By Employee]]
:'''Setup'''
*[[Overtime Rule|Overtime Rule]]

==== '''Business Trip''' ====
*[[Business Trip Request | Business Trip Request]]

==== '''Income Tax''' ====
*[[Employee A1 1721 | Employee A1 1721]]
*[[Import Employee Income tax|Import Employee Income tax]]
*[[Employee Income Tax|Employee Income Tax]]

:'''Analysis Tools'''
*[[Laporan PPH 21 Bulanan per Orang|Laporan PPH 21 Bulanan per Orang]]
*[[Laporan PPH 21 Bulanan per Site|Laporan PPH 21 Bulanan per Site]]

:'''Setup'''
*[[Rate of Indonesian Non Taxable Income|Rate of Indonesian Non Taxable Income]]
*[[Indonesian Position Cost Rate|Indonesian Position Cost Rate]]
*[[Progressive Income Tax Rate|Progressive Income Tax Rate]]

==== '''Leave''' ====
*[[Leave Category| Leave Category]]
*[[Leave Permission|Leave Permission]]
*[[Manage Employee Leave|Manage Employee Leave]]
*[[Manage Leave Request|Manage Leave Request]]
*[[Leave Permit|Leave Permit]]
*[[Mass Leave|Mass Leave]]
*[[Leave Request|Leave Request]]
*[[Employee Leave|Employee Leave]]

:'''Analysis Tools'''
*[[Leave Request Report|Leave Request Report]]
*[[Leave Balance Report|Leave Balance Report]]

:'''Setup'''
*[[Leave Rule|Leave Rule]]

==== '''Time and Attendance''' ====
*[[Attendance Entry | Attendance Entry]]
*[[Attendance Leave Deduction|Attendance Leave Deduction]]
*[[Attendance Earning Deduction|Attendance Earning Deduction]]
*[[Employee Manual Schedule | Employee Manual Schedule]]
*[[Employee Shift | Employee Shift]]
*[[Import Attendance | Import Attendance]]
*[[Import Employee Manual Schedule | Import Employee Manual Schedule]]
*[[Shift Exchange Request | Shift Exchange Request]]

:'''Analysis Tools'''
*[[Attendance Report | Attendance Report]]
*[[Attendance Summary Report| Attendance Summary Report]]
*[[Attendance Performance Report| Attendance Performance Report]]
*[[Individual Attendance Performance Report| Individual Attendance Performance Report]]
*[[Shift Report| Shift Report]]

:'''Setup'''
*[[Shift Rule| Shift Rule]]
*[[Manual Schedule Group| Manual Schedule Group]]
*[[Attendance Machine Configuration| Attendance Machine Configuration]]

==== '''Performance Management''' ====
*[[KPI Measurement|KPI Measurement]]
*[[KPI Job Title|KPI Job Title]]
*[[KPI|KPI]]
*[[KPI Category|KPI Category]]

==== '''Employee Administration''' ====
*[[Employee Transfer | Employee Transfer]]
*[[Employee Job Experience | Employee Job Experience]]
*[[Employee Education | Employee Education]]
*[[Employee Training | Employee Training]]
*[[Employee Competency | Employee Competency]]
*[[Employee Certificate/License | Employee Certificate/License]]
*[[Employee Achievement | Employee Achievement]]
*[[Family Information Change Request | Family Information Change Request]]
*[[Generate Employee Closure | Generate Employee Closure]]
*[[Print Death Certificate | Print Death Certificate]]

:'''Analysis Tools'''
*[[Print ARCI Matrix | Print ARCI Matrix]]

:'''Setup'''
*[[Achievement Catalogue | Achievement Catalogue]]
*[[ARCI Matrix | ARCI Matrix]]
*[[Certificate/License Catalogue | Certificate/License Catalogue]]
*[[Department | Department]]
*[[Employee Position | Employee Position]]
*[[Employee Grade | Employee Grade]]
*[[Employee Grade Rule | Employee Grade Rule]]
*[[Employee Supervisor Management | Employee Supervisor Management]]
*[[Education Dicipline | Education Dicipline]]
*[[Import Mapping Definition | Import Mapping Definition]]
*[[Job Competency Catalogue | Job Competency Catalogue]]
*[[Job Title | Job Title]]
*[[Manufacturing Cost Center | Manufacturing Cost Center]]
*[[Position Rule | Position Rule]]
*[[Set Applicable Contract | Set Applicable Contract]]
*[[Site | Site]]

==== '''People Development''' ====
*[[Education Exam| Education Exam]]
*[[Education Permit | Education Permit]]
*[[Education Admission | Education Admission]]
*[[General Exam | General Exam]]
*[[Training Calendar | Training Calendar]]
*[[Training Plan | Training Plan]]

:'''Analysis Tools'''
*[[Required Competency Report by Job Title by Personel | Required Competency Report by Job Title by Personel]]
*[[Required Training Report by Job Title by Personel | Required Training Report by Job Title by Personel]]
*[[Competency By Employee | Competency By Employee]]

:'''Setup'''
*[[Training Catalogue | Training Catalogue]]

==== '''Termination and Retirement''' ====
*[[Employee Termination| Employee Termination]]
*[[Retirement | Retirement]]
*[[Severance Payment | Severance Payment]]

:'''Setup'''
*[[Severance Rule (Termination) | Severance Rule (Termination)]]
*[[Severance Rule (Pension) | Severance Rule (Pension)]]
*[[Severance Rule (Pension) | Severance Rule (Pension)]]

==== '''Recruiment''' ====
*[[Import Employee Candidate| Import Employee Candidate]]
*[[Employee Candidate | Employee Candidate]]

==== '''Case Management''' ====
*[[Employee Case| Employee Case]]

:'''Setup'''
*[[Punishment Classification | Punishment Classification]]
*[[Violation Catalogue | Violation Catalogue]]

== Advanced ==
=== Related Desktop Application===
*[[Attendance Machine Importer| Attendance Machine Importer]]
=== Background Processes ===
*[[Background Processes Setup | Background Processes Setup]]

{{BackTo|User Guide}}

[[Category:User_Guide]]

Human Resource Management

2021-12-31T03:05:54Z

Asp-rahmadi: /* Payroll */

{{BackTo|User Guide}}

== Introduction ==
ToDo.

This application area of Openbravo covers Requisition to Receipt and Invoicing parts of the Procure To Pay business flow and Supplier Returns business process.
For Payments Management of Procure To Pay see Financial Management // Receivables & Payables application area.

== HR Business Flow ==
Due to its complexity and different roles involved it is convenient to split Procure to Pay down into two main sub-processes:

[[image:HumanResourceBusinessFlow.png]]

====Configuration====
The following setup needs to be done before performing the process:
* Employee
* Overtime Rules
* Business Partners (Vendors & Suppliers).
* Tac Rate

'''Products''' need to be configured prior any purchase requisition is issued.
Each product that is being purchased needs to have a price in the purchase price list in order to be selectable in any transactional document like a purchase order or a purchase invoice.

'''Business Partners''' need to be configured prior any purchase requisition can automatically turns into a purchase order.
Please refer to Business Partner Setup and Business Partner for more information.

====Execution====
In Procurement Management the Procure to Pay business process is executed as follows:

Any member of the organization allowed to do so can directly issue a Requisition as a result of an organization or business unit need.

== '''Relationship with other application areas''' ==

Human Resource Management has a relationship with other application areas:
* [[Master Data Management]] as Employee Information can be maintained as Business Partner.
* [[Financial Management]] in terms of managing account payable payments.

== '''Application Menu''' ==
Please find below detailed description of all windows and reports of the Procurement Management application area.

*[[Employee Information| Employee Information]]
*[[Daily Job Activity | Daily Job Activity]]

==== '''Payroll''' ====
Payroll module provides a flexible and automated payroll workflow.
Starting from here you will learn how to operate payroll processes.

*[[Incidental Earning | Incidental Earning ]]
*[[Incidental Deduction | Incidental Deduction]]
*[[Import Incidental Earning | Import Incidental Earning]]
*[[Import Incidental Deduction | Import Incidental Deduction]]
*[[Pay Slip Individual | Pay Slip Individual]]
*[[Reimbursement | Reimbursement ]]
*[[Salary Back Payment | Salary Back Payment]]
*[[Salary Payment| Salary Payment]]
*[[Overtime| Overtime]]

:'''Analysis Tools'''
*[[Generate Pay Slip| Generate Pay Slip]]

:'''Setup'''
*[[Salary Formula Library | Salary Formula Library ]]

==== '''Loan''' ====
*[[Installment | Installment]]
*[[Incidental Loan | Incidental Loan]]

:'''Analysis Tools'''
*[[Employee Loan Report | Employee Loan Report]]

==== '''Jamsostek''' ====
*[[Jamsostek Pension Funds Report | Jamsostek Pension Funds Report]]
*[[Jamsostek Payment Report|Jamsostek Payment Report]]

==== '''Insurance''' ====
*[[Insurance Membership | Insurance Membership]]
*[[Benefit Claim | Benefit Claim]]
:'''Setup'''
*[[Insurance Provider|Insurance Provider]]
*[[Insurance Payee|Insurance Payee]]

==== '''Overtime and Emergency Call''' ====
*[[Overtime Request|Overtime Request]]
*[[Emergency Call Request|Emergency Call Request]]
*[[Calculate Overtime Amount|Calculate Overtime Amount]]
:'''Analysis Tools'''
*[[Overtime Report|Overtime Report]]
*[[Overtime By Employee|Overtime By Employee]]
:'''Setup'''
*[[Overtime Rule|Overtime Rule]]

==== '''Business Trip''' ====
*[[Business Trip Request | Business Trip Request]]

==== '''Income Tax''' ====
*[[Employee A1 1721 | Employee A1 1721]]
*[[Import Employee Income tax|Import Employee Income tax]]
*[[Employee Income Tax|Employee Income Tax]]

:'''Analysis Tools'''
*[[Laporan PPH 21 Bulanan per Orang|Laporan PPH 21 Bulanan per Orang]]
*[[Laporan PPH 21 Bulanan per Site|Laporan PPH 21 Bulanan per Site]]

:'''Setup'''
*[[Rate of Indonesian Non Taxable Income|Rate of Indonesian Non Taxable Income]]
*[[Indonesian Position Cost Rate|Indonesian Position Cost Rate]]
*[[Progressive Income Tax Rate|Progressive Income Tax Rate]]

==== '''Leave''' ====
*[[Leave Category| Leave Category]]
*[[Leave Permission|Leave Permission]]
*[[Manage Employee Leave|Manage Employee Leave]]
*[[Manage Leave Request|Manage Leave Request]]
*[[Leave Permit|Leave Permit]]
*[[Mass Leave|Mass Leave]]
*[[Leave Request|Leave Request]]
*[[Employee Leave|Employee Leave]]

:'''Analysis Tools'''
*[[Leave Request Report|Leave Request Report]]
*[[Leave Balance Report|Leave Balance Report]]

:'''Setup'''
*[[Leave Rule|Leave Rule]]

==== '''Time and Attendance''' ====
*[[Attendance Entry | Attendance Entry]]
*[[Attendance Leave Deduction|Attendance Leave Deduction]]
*[[Attendance Earning Deduction|Attendance Earning Deduction]]
*[[Employee Manual Schedule | Employee Manual Schedule]]
*[[Employee Shift | Employee Shift]]
*[[Import Attendance | Import Attendance]]
*[[Import Employee Manual Schedule | Import Employee Manual Schedule]]
*[[Shift Exchange Request | Shift Exchange Request]]

:'''Analysis Tools'''
*[[Attendance Report | Attendance Report]]
*[[Attendance Summary Report| Attendance Summary Report]]
*[[Attendance Performance Report| Attendance Performance Report]]
*[[Individual Attendance Performance Report| Individual Attendance Performance Report]]
*[[Shift Report| Shift Report]]

:'''Setup'''
*[[Shift Rule| Shift Rule]]
*[[Manual Schedule Group| Manual Schedule Group]]
*[[Attendance Machine Configuration| Attendance Machine Configuration]]

==== '''Performance Management''' ====
*[[KPI Measurement|KPI Measurement]]
*[[KPI Job Title|KPI Job Title]]
*[[KPI|KPI]]
*[[KPI Category|KPI Category]]

==== '''Employee Administration''' ====
*[[Employee Transfer | Employee Transfer]]
*[[Employee Job Experience | Employee Job Experience]]
*[[Employee Education | Employee Education]]
*[[Employee Training | Employee Training]]
*[[Employee Competency | Employee Competency]]
*[[Employee Certificate/License | Employee Certificate/License]]
*[[Employee Achievement | Employee Achievement]]
*[[Family Information Change Request | Family Information Change Request]]
*[[Generate Employee Closure | Generate Employee Closure]]
*[[Print Death Certificate | Print Death Certificate]]

:'''Analysis Tools'''
*[[Print ARCI Matrix | Print ARCI Matrix]]

:'''Setup'''
*[[Achievement Catalogue | Achievement Catalogue]]
*[[ARCI Matrix | ARCI Matrix]]
*[[Certificate/License Catalogue | Certificate/License Catalogue]]
*[[Department | Department]]
*[[Employee Position | Employee Position]]
*[[Employee Grade | Employee Grade]]
*[[Employee Grade Rule | Employee Grade Rule]]
*[[Employee Supervisor Management | Employee Supervisor Management]]
*[[Education Dicipline | Education Dicipline]]
*[[Import Mapping Definition | Import Mapping Definition]]
*[[Job Competency Catalogue | Job Competency Catalogue]]
*[[Job Title | Job Title]]
*[[Manufacturing Cost Center | Manufacturing Cost Center]]
*[[Position Rule | Position Rule]]
*[[Set Applicable Contract | Set Applicable Contract]]
*[[Site | Site]]

==== '''People Development''' ====
*[[Education Exam| Education Exam]]
*[[Education Permit | Education Permit]]
*[[Education Admission | Education Admission]]
*[[General Exam | General Exam]]
*[[Training Calendar | Training Calendar]]
*[[Training Plan | Training Plan]]

:'''Analysis Tools'''
*[[Required Competency Report by Job Title by Personel | Required Competency Report by Job Title by Personel]]
*[[Required Training Report by Job Title by Personel | Required Training Report by Job Title by Personel]]
*[[Competency By Employee | Competency By Employee]]

:'''Setup'''
*[[Training Catalogue | Training Catalogue]]

==== '''Termination and Retirement''' ====
*[[Employee Termination| Employee Termination]]
*[[Retirement | Retirement]]
*[[Severance Payment | Severance Payment]]

:'''Setup'''
*[[Severance Rule (Termination) | Severance Rule (Termination)]]
*[[Severance Rule (Pension) | Severance Rule (Pension)]]
*[[Severance Rule (Pension) | Severance Rule (Pension)]]

==== '''Recruiment''' ====
*[[Import Employee Candidate| Import Employee Candidate]]
*[[Employee Candidate | Employee Candidate]]

==== '''Case Management''' ====
*[[Employee Case| Employee Case]]

:'''Setup'''
*[[Punishment Classification | Punishment Classification]]
*[[Violation Catalogue | Violation Catalogue]]

== Advanced ==
=== Related Desktop Application===
*[[Attendance Machine Importer| Attendance Machine Importer]]
=== Background Processes ===
*[[Background Processes Setup | Background Processes Setup]]

{{BackTo|User Guide}}

[[Category:User_Guide]]