hospi

2023-12 updates

hn_sale module

Edit sequences:

1. CO Sale Sequence, rename to OEM Sale Sequence, change padding to 4, change prefix to OEM
2. Sale Order Sequence, rename to Reguler Sale Sequence, change padding to 4

Need to update old records to this specification:

1. those with co_sale TRUE should have oem as their order type.
2. those with co_sale FALSE should have reguler as their order type. It's recommended to use mass export+import to perform this update.

purchase_request module

Approver is now Approver 1 and Approver 2. Both are users assigned to Purchase Request Approver group. We assume that approvers are just that: approvers; they do not create RFQ or "done" a request, etc., also cannot access other modules/features. They can still reject a purchase request though.

We also introduce ACC 1 state in addition to (and "before" in sequence to) Approved. Requests that have no Approver 2 will go straight to Approved from To Approve state. Clicking Done while on ACC 1 will result in error if Approver 2 was filled in. In other words, ACC 1 is an intermediary state reached only if the request has two approvers.

We keep Purchase Request Manager group as is, including implied from Purchase Request User. We add a new group, Purchase Request Approver. Please note that this group does not imply Purchase Request User, since it is assumed the user can be from another division, director, or even owner. Set a user to both Purchase Request Manager and Purchase Request Approver if you'd like them to act as purchase request manager too.

Action Items

Need to add users to Purchase Request Approver group.

The purchase request module's creators calls for empty record rule so admins can adjust them according to needs. We just follow this convention when adding new ones, but here's what I did regarding rule on staging:

• Purchase Request Line Approver: Rule Definition is [('assigned_to2','=',user.id)]
• Purchase Request Approver: Rule Definition is the same This means that approvers can only see his/her assigned requests. After approving a request it is automatically gone from the user's list. Feel free to set these on live.

Document Number

We now have Document Number field under every report on Settings | Technical | Reporting | Reports. First of all fill the field in for the appropriate reports, preferably those which are printed as form (like invoice, purchase request, etc). This field is then available in all report xml as document_no variable.

As an example, let's edit report's footer and print document_no if one exists for the form:

    <div t-attf-class="footer o_clean_footer o_company_#{company.id}_layout">
      ...
      <span t-if="document_no">Form No: <t t-esc="document_no" /></span>
    </div>

(the code above can be edited in via Settings | General Settings | (Business Documents section) | Edit Layout button)

Special note: as per late December 2023, purchase requests need below action to be able to be printed:

Go to Settings | Technical | Reports | (click Purchase Request)

Then click "Add in the 'Print' menu" button. Please be aware that this will show the print button for all users.