Proposal for a Generic Batch Document Process in iDempiere

[Md Rifatul Islam]

Dear Community,

At the iDempiere 2026 Conference, we discussed the possibility of having a common batch process for different document types.

We reviewed the standard Order Batch Process, but as far as we understand, it works only with C_Order, mainly for Sales Orders and Purchase Orders.

The related workshop discussion is available here: https://wiki.idempiere.org/en/IDempiere_workshop_2026#closing_orders_in_batch

At Sysnova, we are considering developing a generic Info Window / Batch Document Process where users can select documents from different transaction types, such as Purchase Order, Material Receipt, AP Invoice, Production, Inventory Movement/Adjustment, Sales Order, Shipment, AR Invoice, Fixed Asset documents, etc., and execute valid Document Actions in bulk.

For example: Prepare, Complete, Close, Void, or Reactivate, depending on the current document status and the actions supported by that document.

The intention is not to update DocStatus directly. We want to use the normal iDempiere Document Action / Document Engine logic for each selected document.

Before we start developing this, we would like to know if there is already any generic standard approach, reusable component or community solution available for this purpose.

We would really appreciate suggestions and feedback from the iDempiere community.

[Carlos Antonio Ruiz Gomez]

Hi Rifatul,

Idea sounds good, I have not seen something similar.

We have the windows "Unposted Documents" based on the view RV_UnPosted, and "Unprocessed Documents" based on the view RV_Unprocessed

Those views are a collection of UNION getting the information for many different documents, so maybe it can help you as a guide as I think you would need a similar view for your info window.

Regards,

Carlos Ruiz

[Jesús Castillo]

I really like the idea. In my own developments, I have two similar processes: one that allows repost records and another that allows modifying column values or processing records. It is very useful during implementations because it avoids a lot of manual work. I also think the idea of putting it in an info window is much better.

As a limitation, these processes take the table and a SQL WHERE clause as input parameters.

Still, I can offer it as an example of what is being proposed.

 

Atte: Jesus Castillo.

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/idempiere/061784c2-c8a8-4303-b7e3-ed408cb0b5ed%40gmail.com.

[Md Rifatul Islam]

Yes, Carlos, I am checking both views. They will help us. Thank you for the suggestion

[Md Rifatul Islam]

Hi Jesus,

Thank you for your feedback and for offering to share your work. Your processes sound useful and could help us develop this idea. Please share your example so we can review how it works and use it as a reference for the Info Window.

[Jesús Castillo]

Hi, 

Both processes, UpdateTableProcess allows changing column values, or processing records.

 

Atte: Jesus Castillo.

To view this discussion visit https://groups.google.com/d/msgid/idempiere/afa77b8d-81f4-47cf-b896-4b0d4b31b57dn%40googlegroups.com.