Projects/Integration Yasmeera Webstore

Functional Specifications

Overview

Purpose

Integrasi ini bertujuan untuk se-efektif mungkin menjadikan ERP sebagai central repository, menjadi pusat data dan back office.
Yasmeera Webstore menjadi aplikasi front end yang berhubungan langsung dengan Customer/Pelanggan/Pembeli. Oleh karena itu semua master data akan didefinisikan dan dibuat di ERP. Akan terjadi sinkronisasi data utama dari ERP ke Webstore.
Webstore secara aktif melakukan sinkronisasi terhadap master data dan transaksi bisnis yang terjadi di webstore. Dengan demikian User Pengguna akan lebih banyak bekerja pada aplikasi ERP.

References

None.

Design Considerations

Proyek ini didesain tetap mempertimbangkan mengurangi waktu dan biaya implementasi adopsi InfiniteERP.
InfiniteERP tetap menjadi central repository untuk master data tidak terbatas pada produk dan business partner.

Assumptions

1. 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.

Functional Requirements

An Example

The Scenario

• Master Data
  • 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 ERP akan disepakati kemudian sesuai bisnis proses.

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 two remittance types
  • Mail deposit
  • Branch deposit

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

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

User Interface Mockups

TBD

Non-Functional Requirements

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?