Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 13 22:53
    yamelsenih commented #3490
  • Jun 13 22:50
    EdwinBetanc0urt commented #3490
  • Jun 13 22:31
    EdwinBetanc0urt commented #3490
  • Jun 13 22:19
    yamelsenih commented #3490
  • Jun 13 22:19
    yamelsenih labeled #3490
  • Jun 13 22:19
    yamelsenih assigned #3490
  • Jun 13 22:18
    yamelsenih commented #3490
  • Jun 12 16:41
    marcalwestf labeled #3470
  • Jun 12 16:41
    marcalwestf unlabeled #3470
  • Jun 12 16:41
    marcalwestf labeled #3470
  • Jun 12 16:40
    marcalwestf labeled #3464
  • Jun 12 12:54
  • Jun 10 16:18
    yamelsenih review_requested #3491
  • Jun 10 16:18
    yamelsenih labeled #3491
  • Jun 10 16:18
    yamelsenih review_requested #3491
  • Jun 10 16:18
    yamelsenih opened #3491
  • Jun 10 16:18
    yamelsenih labeled #3491
  • Jun 10 16:18
    yamelsenih assigned #3491
  • Jun 10 16:18
    yamelsenih milestoned #3491
  • Jun 09 18:38
    e-Evolution commented #3408
Yamel Senih
@yamelsenih
Hi @/all here a change for ADempiere-Vue documentation:
Yamel Senih
@yamelsenih

rt-3.9

Hi erveryone, here a new release rt-3.9 with many changes. We are happy of share it with all:

Related Commits

Docs news

Components

Official Documentation

Available Docker Images:

  • ADempiere gRPC
    docker run -d \
      -it \
      --name adempiere-grpc-all-in-one \
      -p 50059:50059 \
      -e SERVER_PORT=50059 \
      -e SERVICES_ENABLED="access; business; core; dashboarding; dictionary; enrollment; log; ui; workflow; store; pos; updater;" \
      -e SERVER_LOG_LEVEL="WARNING" \
      -e DB_HOST="localhost" \
      -e DB_PORT="5432" \
      -e DB_NAME=\"adempiere\" \
      -e DB_USER="adempiere" \
      -e DB_PASSWORD="adempiere" \
      -e DB_TYPE="PostgreSQL" \
      erpya/adempiere-grpc-all-in-one
  • Proxy ADempiere API
    docker run -it -d \
      --name proxy-adempiere-api \
      -p 8085:8085 \
      -e AD_DEFAULT_HOST="Your_gRPC_Server_IP" \
      -e AD_DEFAULT_PORT="50059" \
      -e AD_TOKEN="Your_ADempiere_Generated_Token" \
      -e VS_ENV="dev" \
      -e RESTORE_DB="N" \
      erpya/proxy-adempiere-api
  • ADempiere Vue
    docker run -it \
      --name adempiere-vue \
      -p 80:80 \
      -e API_URL="http://localhost:8085" \
      erpya/adempiere-vue
  • ADempiere
    docker pull erpya/adempiere-base
    docker run -p 8888:8888 erpya/adempiere-base

Available Previews

amirsaifi
@amirsaifi
We are facing some issue in Generate Cost Transaction process. May be we are using it in a wrong way. Let me explain my issue first. As a practice we are running Generate Cost Transaction on Monthly Basis for the period, means for one month. It is observed that costing process do nothing for product which has no transaction in previous month ( for example if we are running Generate Cost for the Month of March and there is a product 'A' which has transactions in March but not in Feb then no impact of Costing Process on Product 'A'.) It requires to run costing from Feb on Product 'A' to get the correct impact for March. There are few products which are categorized as slow moving items and having no transaction since last two years or more. In that case opening all the periods and running Generate Cost from the last transaction month to get the impact in current month is laborious and risk too to open all Financial periods which are close. Is there any mistake in our way of doing this or configuration. Please guide and suggest.
Running Generate Cost on all products and then Client Accounting process also take hours to complete.
amirsaifi
@amirsaifi
Is it normal?
e-Evolution
@e-Evolution
Hi @amirsaifi

The generation of costs is done only when you are implementing, that is, once the system is generated it will work creating transactions based on the cost history.

When the process of generating costs is executed, it only impacts the movements of the open periods, the reason is that only the cost layers should be regenerated due to errors or documents entered at the wrong time, causing the average to be incorrect.

When the process of generating costs is executed, the averaging layers will regenerate correctly, but the process only does it for open periods to avoid the risk of modifying the results of an already closed period.

amirsaifi
@amirsaifi
Hi @e-Evolution
amirsaifi
@amirsaifi
Thanks for your response. Let me add a few more aspects like we are using Average Invoice Costing Method and in using Adempiere in process manufacturing industry. In Manufacturing industries, cost adjustments at month end is a routine like invoices are received at month end and the purchased material is used in manufacturing prior to receiving all costs/expenses. Landed Costs are loaded at month end and Generate cost is required to calculate new average price of raw material and other products. Further, its not easy to track which items needs regeneration of cost so we run costing on all products at month end. For products which are used/issued/purchased after a gap of few months, Cost generation is required to run from the last transaction months after opening all previous month till that month of transaction, to get the correct average price. Seems like Average Invoice Costing Method is not feasible for this situation.
Yamel Senih
@yamelsenih

rt-4.2

Hi erveryone, here a new release rt-4.2 with many changes. We are happy of share it with all:

Related Commits

Docs news

Components

Official Documentation

Available Docker Images:

  • ADempiere gRPC
    docker run -d \
      -it \
      --name adempiere-grpc-all-in-one \
      -p 50059:50059 \
      -e SERVER_PORT=50059 \
      -e SERVICES_ENABLED="access; business; core; dashboarding; dictionary; enrollment; log; ui; workflow; store; pos; updater;" \
      -e SERVER_LOG_LEVEL="WARNING" \
      -e DB_HOST="localhost" \
      -e DB_PORT="5432" \
      -e DB_NAME=\"adempiere\" \
      -e DB_USER="adempiere" \
      -e DB_PASSWORD="adempiere" \
      -e DB_TYPE="PostgreSQL" \
      erpya/adempiere-grpc-all-in-one
  • Proxy ADempiere API
    docker run -it -d \
      --name proxy-adempiere-api \
      -p 8085:8085 \
      -e AD_DEFAULT_HOST="Your_gRPC_Server_IP" \
      -e AD_DEFAULT_PORT="50059" \
      -e AD_TOKEN="Your_ADempiere_Generated_Token" \
      -e VS_ENV="dev" \
      -e RESTORE_DB="N" \
      erpya/proxy-adempiere-api
  • ADempiere Vue
    docker run -it \
      --name adempiere-vue \
      -p 80:80 \
      -e API_URL="http://localhost:8085" \
      erpya/adempiere-vue
  • ADempiere
    docker pull erpya/adempiere-base
    docker run -p 8888:8888 erpya/adempiere-base

Available Previews

Authentication values:

A Demo

User: demo
Password: demo

Garden World

User: GardenAdmin
Password: GardenAdmin
Prapon Aon
@vdevsoft
Has anyone ever used an ADempiere with a service business, such as a clinic or a small hospital?
How should I determine the service process?
In addition, there are cases where customers complain. link to external documents, image before and after service.
Yamel Senih
@yamelsenih
Hi @vdevsoft I not have experience with clinical but have some use cases with services and third party access
Prapon Aon
@vdevsoft
the main point is the service that includes the cost/wages of the employees at each step.
Do you have any advice?
Yamel Senih
@yamelsenih
Basically each employee have a.
A cost for consultant and it is charged to patient, I don't know if also you manage assurance
Michael McKay
@mckayERP

@vdevsoft Hi Prapon, Service processes can be similar to manufacturing processes where a series of services are performed in-house or by outside vendors. The product produced by the "manufacturing process" could be something non-traditional - such as patient records, test results or other documents. Along the way, the manufacturing process collects the costs of each step for material, resources, labor etc...

Complaints with documents etc could be considered quality control processes that have lessons learned and corrective actions associated with them.

So, with come creativity, you may be able to adapt the manufacturing workflows to your needs.

Prapon Aon
@vdevsoft
yes, that's right.
But how to make the process continue?
since the customer walks in to open a sales order to the manufacturing process
Prapon Aon
@vdevsoft
I'm writing a process diagram. I will seek advice from you. @mckayERP @yamelsenih
Prapon Aon
@vdevsoft
more question,
If I have to store a lot of image files.
What methods should be used to reduce the load on database?
Eric Leduc
@eelti
@vdevsoft a idea is create a table use for the files store in the dB and create it in a separate table space and put that table space on is own partion/ drive so the load on the dB is reduce, that will help you with the dB back if you manage that part maybe differently. That is just a idea.
Prapon Aon
@vdevsoft
It's an interesting idea, isn't it the AD_Image table? @eelti
Eric Leduc
@eelti
@vdevsoft you can move any table in a different table space and not you partion your table when to make sure don’t came to big
e-Evolution
@e-Evolution

Hi Prapon Aon @vdevsoft currently you can manage a hospital service as a resource, in fact Adempiere has the functionality to sell and allocate resources, you can make an example with Mary Consultant in GardenWorld.

From the images currently from version 3.9.3 it is possible to connect any solution that supports WebDav and deposit here the images or binary files that you require, generally this is done in document management software such as Alfresco or, Nuexo or NextCloud

@yamelsenih Yamel developed one of the services to connect to NextCloud adempiere/adempiere#2619
e-Evolution
@e-Evolution
Alfresco and Noxeo are Enterprise Content Management System, which would be the most appropriate for your business case, since they are designed to store a large amount of digital content, in addition to being able to classify them using tags and index them, this type of solution also has a BPM integration such as Alfresco that allows you to manage document approval flows.
The case of NextCloud is more designed for document collaboration, it would not prevent you from opening a directory as a patient file and saving all your digital information here, perhaps you would have to review the issue of ethical security since I suppose that protecting personal information from patients must have some kind of protocol to comply with.
e-Evolution
@e-Evolution
here the example to service based on resources
image.png
image.png
image.png
here you can check the Schedule Info the assigment the resource blue color
image.png
and the sales order :
image.png
Prapon Aon
@vdevsoft
thank you, I love ADempiere team so much.
Yamel Senih
@yamelsenih
Hi @eelti @vdevsoft complement the @e-Evolution comments, also is integrated with S3 protocol here: adempiere/adempiere#3135
Eric Leduc
@eelti

Hi all, We use jasper report like standard print out for many document. We do that to have uniformity in all the apps we have, so ex: one format for all the sales orders print out.

  • I want to know if some one find a way migrate the attachment of the jasper report?
  • I have try log migration script that one works well but the binary is not copy correctly...
  • I try the function packin but I don't find any way to pack-in the attachment of the jasper report and is logo.

Thanks

Yamel Senih
@yamelsenih
Hi @eelti how are you?
a way is macking a setup for NextCloud or S3 and it is saved on nextcloud instead database
is more clear
Eric Leduc
@eelti
@yamelsenih I'm gooing well thank to ask. And how are you? That is for standard print out in adempiere and other local tool I'm thinking more a local approach not one required a external access
I Have a local Jasper server maybe I can interface adempiere with that at place but I'm scare that will just slowdown the thing
Yamel Senih
@yamelsenih
fine thanks, I have all implementation with ADempiere + PostgreSQL + nextcloud or S3 service all can be installed local, is better when the big files are saved oter database
A option is get all attachment fromdb and save it in a repository but is very manually

rt-4.3

Hi erveryone, here a new release rt-4.3 with many changes. We are happy of share it with all:

Related Commits

Docs news

Components

Official Documentation

Available Docker Images:

  • ADempiere gRPC
    docker run -d \
      -it \
      --name adempiere-grpc-all-in-one \
      -p 50059:50059 \
      -e SERVER_PORT=50059 \
      -e SERVICES_ENABLED="access; business; core; dashboarding; dictionary; enrollment; log; ui; workflow; store; pos; updater;" \
      -e SERVER_LOG_LEVEL="WARNING" \
      -e DB_HOST="localhost" \
      -e DB_PORT="5432" \
      -e DB_NAME=\"adempiere\" \
      -e DB_USER="adempiere" \
      -e DB_PASSWORD="adempiere" \
      -e DB_TYPE="PostgreSQL" \
      erpya/adempiere-grpc-all-in-one
  • Proxy ADempiere API
    docker run -it -d \
      --name proxy-adempiere-api \
      -p 8085:8085 \
      -e AD_DEFAULT_HOST="Your_gRPC_Server_IP" \
      -e AD_DEFAULT_PORT="50059" \
      -e AD_TOKEN="Your_ADempiere_Generated_Token" \
      -e VS_ENV="dev" \
      -e RESTORE_DB="N" \
      erpya/proxy-adempiere-api
  • ADempiere Vue
    docker run -it \
      --name adempiere-vue \
      -p 80:80 \
      -e API_URL="http://localhost:8085" \
      erpya/adempiere-vue
  • ADempiere
    docker pull erpya/adempiere-base
    docker run -p 8888:8888 erpya/adempiere-base

Available Previews

Eric Leduc
@eelti
@yamelsenih thanks for the infos