Backdated Transactions
Locked
 
|
Hello Community,
I am trying to achieve the following in my OFBIZ - In a real world scenario, to buy a product, a Purchase Order is created and the products are received in a warehouse. Real World Business Case Following are the events happening in real world. 1. A Purchase Order is created - May 01, 2014 2. Product was received in the warehouse on May 10th (warehouse is a remote warehouse in another state. Following is the scenario if I enter the PO in the ERP system, on May 20th, 2016. 1. Create a PO on May 20, 2014 (I can't select the PO Date) 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt date myself) When I see transactions, they have a date of May 20th, 2014 (as against May 10th, which is required / desired). Is there a way to make all the transactions mentioned above have May 10th 2014 date? If we amend the transaction date, are we defeating the basic purpose of an ERP? Appreciate your response. Thanks in advance, Sarang Systematrix Solutions -- Regards, Sarang |
|
|
Hi Sarang,
You can use the "StoreOrder" service, You can also send orderDate as parameter, so whatever the date you want you can create order of that date. With regards, Pradeep Kumar With regards, S K Pradeep Kumar, 9035009495 On Wed, May 21, 2014 at 3:56 AM, Sarang Deshpande <[hidden email]>wrote: > Hello Community, > > I am trying to achieve the following in my OFBIZ - > > In a real world scenario, to buy a product, a Purchase Order is created and > the products are received in a warehouse. > > Real World Business Case > > Following are the events happening in real world. > > 1. A Purchase Order is created - May 01, 2014 > 2. Product was received in the warehouse on May 10th (warehouse is a remote > warehouse in another state. > > Following is the scenario if I enter the PO in the ERP system, on May 20th, > 2016. > > 1. Create a PO on May 20, 2014 (I can't select the PO Date) > 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt > date myself) > > When I see transactions, they have a date of May 20th, 2014 (as against May > 10th, which is required / desired). > > Is there a way to make all the transactions mentioned above have May 10th > 2014 date? > > If we amend the transaction date, are we defeating the basic purpose of an > ERP? > > Appreciate your response. > > Thanks in advance, > > Sarang > Systematrix Solutions > > -- > Regards, > > Sarang > |
Administrator
|
In reply to this post by sarangdj
Le 21/05/2014 00:26, Sarang Deshpande a écrit : > Hello Community, > > I am trying to achieve the following in my OFBIZ - > > In a real world scenario, to buy a product, a Purchase Order is created and > the products are received in a warehouse. > > Real World Business Case > > Following are the events happening in real world. > > 1. A Purchase Order is created - May 01, 2014 > 2. Product was received in the warehouse on May 10th (warehouse is a remote > warehouse in another state. > > Following is the scenario if I enter the PO in the ERP system, on May 20th, > 2016. > > 1. Create a PO on May 20, 2014 (I can't select the PO Date) > 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt > date myself) > > When I see transactions, they have a date of May 20th, 2014 (as against May > 10th, which is required / desired). > > Is there a way to make all the transactions mentioned above have May 10th > 2014 date? > > If we amend the transaction date, are we defeating the basic purpose of an > ERP? I'd not say so. An ERP should always reflect the reality. There are 2 options: * Change the dates after by yourself using Webtools/Entity maintenance (all related entities) * Open a Jira to ask/or-create-a-patch to allow anti-dated orders creation (don't expect help from others, better create your patch and contribute) Jacques > Appreciate your response. > > Thanks in advance, > > Sarang > Systematrix Solutions > -- |
|
Administrator
|
In reply to this post by S K Pradeep kumar
I personaly was more thinking about UI, and yes it would be the way to go from UI
Jacques Le 21/05/2014 09:10, S K Pradeep Kumar a écrit : > Hi Sarang, > > You can use the "StoreOrder" service, You can also send orderDate as > parameter, so whatever the date you want you can create order of that date. > > With regards, > Pradeep Kumar > > With regards, > S K Pradeep Kumar, > 9035009495 > > > On Wed, May 21, 2014 at 3:56 AM, Sarang Deshpande <[hidden email]>wrote: > >> Hello Community, >> >> I am trying to achieve the following in my OFBIZ - >> >> In a real world scenario, to buy a product, a Purchase Order is created and >> the products are received in a warehouse. >> >> Real World Business Case >> >> Following are the events happening in real world. >> >> 1. A Purchase Order is created - May 01, 2014 >> 2. Product was received in the warehouse on May 10th (warehouse is a remote >> warehouse in another state. >> >> Following is the scenario if I enter the PO in the ERP system, on May 20th, >> 2016. >> >> 1. Create a PO on May 20, 2014 (I can't select the PO Date) >> 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt >> date myself) >> >> When I see transactions, they have a date of May 20th, 2014 (as against May >> 10th, which is required / desired). >> >> Is there a way to make all the transactions mentioned above have May 10th >> 2014 date? >> >> If we amend the transaction date, are we defeating the basic purpose of an >> ERP? >> >> Appreciate your response. >> >> Thanks in advance, >> >> Sarang >> Systematrix Solutions >> >> -- >> Regards, >> >> Sarang >> -- |
|
|
In reply to this post by Jacques Le Roux
Hi Jacques,
Changing thru webtools can hardly be regarded as an option as that feature seat is commonly not available to the average end users. Regards, Pierre Verstuurd vanaf mijn iPad > Op 21 mei 2014 om 09:32 heeft Jacques Le Roux <[hidden email]> het volgende geschreven: > > > Le 21/05/2014 00:26, Sarang Deshpande a écrit : >> Hello Community, >> >> I am trying to achieve the following in my OFBIZ - >> >> In a real world scenario, to buy a product, a Purchase Order is created and >> the products are received in a warehouse. >> >> Real World Business Case >> >> Following are the events happening in real world. >> >> 1. A Purchase Order is created - May 01, 2014 >> 2. Product was received in the warehouse on May 10th (warehouse is a remote >> warehouse in another state. >> >> Following is the scenario if I enter the PO in the ERP system, on May 20th, >> 2016. >> >> 1. Create a PO on May 20, 2014 (I can't select the PO Date) >> 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt >> date myself) >> >> When I see transactions, they have a date of May 20th, 2014 (as against May >> 10th, which is required / desired). >> >> Is there a way to make all the transactions mentioned above have May 10th >> 2014 date? >> >> If we amend the transaction date, are we defeating the basic purpose of an >> ERP? > > I'd not say so. An ERP should always reflect the reality. There are 2 options: > * Change the dates after by yourself using Webtools/Entity maintenance (all related entities) > * Open a Jira to ask/or-create-a-patch to allow anti-dated orders creation (don't expect help from others, better create your patch and contribute) > > Jacques > >> Appreciate your response. >> >> Thanks in advance, >> >> Sarang >> Systematrix Solutions > > -- |
|
Administrator
|
Le 21/05/2014 11:48, Pierre Smits a écrit : > Hi Jacques, > > Changing thru webtools can hardly be regarded as an option as that feature seat is commonly not available to the average end users. Yes, can be used only occasionally indeed Passing a orderDate to storeOrder service as suggested Pradeep is a better way. Now no UI exists for that, we might want to add this as a parameter to ordermgr/control/initorderentry Jacques > > Regards, > > Pierre > > Verstuurd vanaf mijn iPad > >> Op 21 mei 2014 om 09:32 heeft Jacques Le Roux <[hidden email]> het volgende geschreven: >> >> >> Le 21/05/2014 00:26, Sarang Deshpande a écrit : >>> Hello Community, >>> >>> I am trying to achieve the following in my OFBIZ - >>> >>> In a real world scenario, to buy a product, a Purchase Order is created and >>> the products are received in a warehouse. >>> >>> Real World Business Case >>> >>> Following are the events happening in real world. >>> >>> 1. A Purchase Order is created - May 01, 2014 >>> 2. Product was received in the warehouse on May 10th (warehouse is a remote >>> warehouse in another state. >>> >>> Following is the scenario if I enter the PO in the ERP system, on May 20th, >>> 2016. >>> >>> 1. Create a PO on May 20, 2014 (I can't select the PO Date) >>> 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt >>> date myself) >>> >>> When I see transactions, they have a date of May 20th, 2014 (as against May >>> 10th, which is required / desired). >>> >>> Is there a way to make all the transactions mentioned above have May 10th >>> 2014 date? >>> >>> If we amend the transaction date, are we defeating the basic purpose of an >>> ERP? >> I'd not say so. An ERP should always reflect the reality. There are 2 options: >> * Change the dates after by yourself using Webtools/Entity maintenance (all related entities) >> * Open a Jira to ask/or-create-a-patch to allow anti-dated orders creation (don't expect help from others, better create your patch and contribute) >> >> Jacques >> >>> Appreciate your response. >>> >>> Thanks in advance, >>> >>> Sarang >>> Systematrix Solutions >> -- > -- |
|
|
In reply to this post by sarangdj
Hi Sarang,
Maybe you should rethink the business process. Registering POs in a system days later than the negotiations where concluded is a bad practice. So is acceptance of delivery before the confirmation of the PO. But yes, the scenario as you have described it do occur and thus it should be handled within the system. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Wed, May 21, 2014 at 12:26 AM, Sarang Deshpande <[hidden email]>wrote: > Hello Community, > > I am trying to achieve the following in my OFBIZ - > > In a real world scenario, to buy a product, a Purchase Order is created and > the products are received in a warehouse. > > Real World Business Case > > Following are the events happening in real world. > > 1. A Purchase Order is created - May 01, 2014 > 2. Product was received in the warehouse on May 10th (warehouse is a remote > warehouse in another state. > > Following is the scenario if I enter the PO in the ERP system, on May 20th, > 2016. > > 1. Create a PO on May 20, 2014 (I can't select the PO Date) > 2. Receive the PO in warehouse on May 20, 2014 (I can't specify the receipt > date myself) > > When I see transactions, they have a date of May 20th, 2014 (as against May > 10th, which is required / desired). > > Is there a way to make all the transactions mentioned above have May 10th > 2014 date? > > If we amend the transaction date, are we defeating the basic purpose of an > ERP? > > Appreciate your response. > > Thanks in advance, > > Sarang > Systematrix Solutions > > -- > Regards, > > Sarang > |
|
|
In reply to this post by Jacques Le Roux
Jacques,
Indeed, passing the orderDate should be common practice. In the Ui this should be populated by default with the nowDate. Same should apply to the date of inventory receipt. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com |
|
|
This post was updated on .
If you enable this, I would suggest only allowing the field to be editable only for users with an admin-level security clearance, so a lazy warehouse worker doesn’t put off receiving PO’s because he can backdate them. :-)
--Paul On May 21, 2014, at 6:51 AM, Pierre Smits <pierre.smits@gmail.com> wrote: > Jacques, > > Indeed, passing the orderDate should be common practice. > > In the Ui this should be populated by default with the nowDate. > > Same should apply to the date of inventory receipt. > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com |
|
|
Paul,
Are you sure you would add complexity to a system to provision for avoidance of laziness? Better is it to improve business processes and procedures to flesh such behaviour out of the organisation. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com |
|
|
This post was updated on .
Always a difficult question - where do you draw the line between systemic controls vs. training?
At the minimum if we don’t have a security provision, we should have proper auditing of when a PO receipt is backdated or postdated, so someone can figure out While I wasn’t around for the initial decisions to make the dates not editable, in a large organization this could potentially have drastic results for other users in the organization. The scenario I can imagine (and has happened in my org before) is a purchase order contract dispute. Since purchase orders are legal contracts (at least in the USA), there is a potential if a PO is received late, and there is not a proper record of when the PO was received by the company, that you run into a problem. My organization, for example, doesn’t use OFbiz’s inbound package tracking functionality (too complicated and slow). Yeah, better training and supervision would fix this problem, but the reality is that most organizations would overlook a little thing like this, especially if the default old behavior changes between upgrades. Having it available just at a supervisor level at least mitigates that problem. Or at least stubbing it so it’s easy to figure out where to add the security control would be a good start. --P On May 21, 2014, at 7:15 AM, Pierre Smits <pierre.smits@gmail.com> wrote: > Paul, > > Are you sure you would add complexity to a system to provision for > avoidance of laziness? Better is it to improve business processes and > procedures to flesh such behaviour out of the organisation. > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com |
|
|
Hello Everyone,
First of all, thanks so much for all the responses and an interesting discussion. Apologies for the late response because of the time difference. As I gather from all the posts, I can select / edit the order dates programmatically. Whether this should be done principally is the question. I am working with a food processing company having multiple warehouses spread across US which are rented for short/long duration. Many times, the order pickup information is conveyed late to the company (Offline process) which leads to such scenarios. If someone is late by couple of days doesn't make any difference from accounting point of view. But when it comes to a date such as December 30th, it creates a huge difference because of the Financial Year change (US new financial year starts Jan 1) and invites troubles of journal entries to effect the transaction in the past year. I am sure every organisation comes across such a scenario. It will be interesting to understand how this situation is tackled. My question is, if we change the Sales Order Date and Sales Order Packing Date, what date will be considered for the following Accounting Transactions? (I have not considered changing the Invoice date, and effective payment date which add more variables to the situation.) 1. Txn date for Accounts Receivable entry 2. Txn date for reducing the Assets Thanks once again. Sarang Systematrix Solutions On Wed, May 21, 2014 at 9:05 AM, Paul Mandeltort <[hidden email]> wrote: > Always a difficult question - where do you draw the line between systemic > controls vs. training? > > At the minimum if we don’t have a security provision, we should have > proper auditing of when a PO receipt is backdated or postdated, so someone > can figure out > > While I wasn’t around for the initial decisions to make the dates not > editable, in a large organization this could potentially have drastic > results for other users in the organization. > > The scenario I can imagine (and has happened in my org before) is a > purchase order contract dispute. Since purchase orders are legal contracts > (at least in the USA), there is a potential if a PO is received late, and > there is not a proper record of when the PO was received by the company, > that you run into a problem. > > My organization, for example, doesn’t use OFbiz’s inbound package tracking > functionality (too complicated and slow). > > Yeah, better training and supervision would fix this problem, but the > reality is that most organizations would overlook a little thing like this, > especially if the default old behavior changes between upgrades. > > Having it available just at a supervisor level at least mitigates that > problem. Or at least stubbing it so it’s easy to figure out where to add > the security control would be a good start. > > --Paul > ---------- > Paul Mandeltort | Marco Specialties Inc > +1-512-394-8119 | [hidden email] > > On May 21, 2014, at 7:15 AM, Pierre Smits <[hidden email]> wrote: > > > Paul, > > > > Are you sure you would add complexity to a system to provision for > > avoidance of laziness? Better is it to improve business processes and > > procedures to flesh such behaviour out of the organisation. > > > > Regards, > > > > Pierre Smits > > > > *ORRTIZ.COM <http://www.orrtiz.com>* > > Services & Solutions for Cloud- > > Based Manufacturing, Professional > > Services and Retail & Trade > > http://www.orrtiz.com > > -- Regards, Sarang |
|
Administrator
|
In reply to this post by marcopaul
If ever we create a Jira, it seems to me Paul's comments should be taken in account
Jacques Le 21/05/2014 16:05, Paul Mandeltort a écrit : > Always a difficult question - where do you draw the line between systemic controls vs. training? > > At the minimum if we don’t have a security provision, we should have proper auditing of when a PO receipt is backdated or postdated, so someone can figure out > > While I wasn’t around for the initial decisions to make the dates not editable, in a large organization this could potentially have drastic results for other users in the organization. > > The scenario I can imagine (and has happened in my org before) is a purchase order contract dispute. Since purchase orders are legal contracts (at least in the USA), there is a potential if a PO is received late, and there is not a proper record of when the PO was received by the company, that you run into a problem. > > My organization, for example, doesn’t use OFbiz’s inbound package tracking functionality (too complicated and slow). > > Yeah, better training and supervision would fix this problem, but the reality is that most organizations would overlook a little thing like this, especially if the default old behavior changes between upgrades. > > Having it available just at a supervisor level at least mitigates that problem. Or at least stubbing it so it’s easy to figure out where to add the security control would be a good start. > > --Paul > ---------- > Paul Mandeltort | Marco Specialties Inc > +1-512-394-8119 | [hidden email] > > On May 21, 2014, at 7:15 AM, Pierre Smits <[hidden email]> wrote: > >> Paul, >> >> Are you sure you would add complexity to a system to provision for >> avoidance of laziness? Better is it to improve business processes and >> procedures to flesh such behaviour out of the organisation. >> >> Regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com > > -- |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |