1

(23 replies, posted in FA Modifications)

So 2 of our clients use SAP. Ideally according to their process:

1) there should be a proforma invoice from our side (in FA) indicating approximate price
2) We supply a commodity which has variable quantity and variable rates on a daily basis (agri commodities)
3) Based on the delivery, our clients generate a GRN and then a backdated PO in their SAP. The GRN carries the invoice number which ideally should have been shipped along with the material (agri commodity)

Now because of the stupid implementation of the SAP system...
4) Based on proforma invoice, using Proforma Invoice number they generate the GRN
5) Our final invoice should then carry the final amount, final quantity, final rates, the invoice number as depicted in proforma invoice  , etc.

Due to the low margin nature of the business, we can not afford to hire too many people to handle the process heavy nature. And, we supply from many locations.

What we do:
So we end up giving series of invoice numbers to these 2 clients i.e. <ourName>/17-18/Client1/Location1/<Invoice Series> and <ourName>/17-18/Client1/Location2/<Invoice Series>. The client accounts team knows which number is going to come next. So they generate GRNs against invoice numbers (invoices which we make later). All we need to do is make invoices. Process is simple.

We have still not evaluated FA completely yet. However, if we can not define series client wise and location wise in invoice numbers... then "Invoice Editable" sounds like a good idea.

Hello,

mySQL/ mariaDB is a deal-breaker for us (source: prior horror scenarios). We do not mind paying for building in support for postgres.

However, the primary concern is that any updates, future versions of FA system may not support postgres after we have one running. If we have any interest in moving in this direction, we wouldn't mind spending a bit of money to seed this.

Your thoughts, hate-mail, criticisms welcome.

/MTM

PS: I really do not wish to get into mySQL vs postgres debate