[Axapta-Knowledge-Village] Journal print out does not have tax!!

Thu, 30 Jun 2005 19:50:23 -0700

Title: Message
I have just realised the general journal report does not have any info if there is tax for a transaction!!!
 
Can anyone suggest a report or modificaiton as my customer wants a journal printout to use for approving purposes and hence it should show the total affect of the journal lines that wil be posted.
 
Thanks
James
 
-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Harry (Harshawardhan Deshpande
Sent: 01 July 2005 09:02
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Sales Order - Question

hi
 
interesting ....
 
on the same lines...
 
once a sales order is created insert the sales id in a new table.
 
create a batch job that will check say after 10 mins if the sales order is still in the database, if yes then send it to the web-database.
 
Use opposite logic for deleted sales orders.
 
think through of a scenario where user created a sales order and immediately deletes it.
 
regards
 
harry
Jesper Kehlet <[EMAIL PROTECTED]> wrote:
What database is your web site based on?  A Microsoft SQL 2000 database?
 
Anyway, here is my 2 cents:  Modify Application.ttsNotifyCommit() to do the synchronization -- that way you can ensure that transactions have been committed before you synchronize.  Do it like this:
 
    1.  Create a method to do the actual synchronization somewhere, make it take a parameter equal to the SalesId.  Do it in class SalesTableType, which is an excellent place.
    2.  Create a new table e.g. SalesTableInsert with just the SalesId, or find another means for storage of inserted sales orders.
    3.  Create functionality in Application.ttsNotifyCommit() to test if xApplication.ttslevel() is 0, then read all records in this structure and call the replaction method defined in #1, one by one, and delete the records after each one have been successfully replicated.
    3.  On the SalesTableType.insert() method, test for xApplication.ttslevel() == 0 (right after salesTable.doInsert()):
        a.  If it is 0, call your new method with the SalesId.
        b.  If it is non-0, insert the SalesId into the table/structure defined above in 2, and wait for Application.ttsNotifyCommit() to grab it.  The inserts here will be in the same ttslevel, thus the Application.ttsNotifyCommit() will grab it when it gets committed.
 
One minor detail:  If this is a SQL based web database, I would seriously consider a trigger instead as it will be a lot faster and less taxing on the sales order creation functionality.

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Brandon George
Sent: Thursday, June 30, 2005 4:57 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Sales Order - Question

Well this is great conversation! Thanks for your input, and I believe that I found the Solution:
 
 Override the ValidateWrite and ValidateDelete methods. Adding code that would transfer the information from the SalesLine to our Web Database at this point seems to work every time.
 
@ harry:
    Did you consider ValidateWrite / ValidateDelete methods? After doing some research it seems that these methods are called every time no matter what, when it comes time to actually write a Line in ANY table for that matter.
 
-Brandon

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Harry (Harshawardhan Deshpande
Sent: Thursday, June 30, 2005 5:35 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Sales Order - Question

hi Brandon
 
this email is just for the sakes of complete discussion.
 
it is not necessary tha the update and insert methods on a table will be executed. The logic may go for doInsert and doUpdate. though I cant think of a scenario where doInsert/Update methods are called for sales table it may be worthwhile to check this out especially the modifications developed by your programmers (I have seen a lot of times that programmers will uncessarily call the doInsert/update methods).
Another problem that you are going to face is ttsabort. If a transaction is inserted into the database and later aborted then there is no easy way to get hold of this abort statement.  You can avoid this problem to a great extent by putting your code after the ttscommit statement (if any) in the insert/update method
 
I have not checked all the code but one place where you will be completely lost will be if a piece of code is creating a sales order and there is a tts loop at the higher level. For e.g. may be creation of inter-company orders etc. Or may be auto creation of sales lines.
 
I would give a serious thought to writing triggers in sql server.  I am aware that sql server is a black box for Axapta and believe me I personally hate doing such triggers but in your case it may be the correct way to go.
 
regards
 
harry
 
 
-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED]On Behalf Of Brandon George
Sent: Thursday, 30 June 2005 8:39 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Sales Order - Question

Hello all,
 
    Ok let me give you some information, that will hopefully help explain what I am trying to do. You see we have a Web Site and Database structure for that website in place. We are currently implementing Axapta, and in order not to change to much at once, we are wanting to replicate data from Axapta to our Web site database.
 
In order to do this, I am wanting to run a piece of code every time a Sales Order is created that would replicate that Sales Order to our web site database.
 
Does anyone have a clue as to the best way to do this? Is there a class that is always called when a new Sales Order is created? I figure SalesAutoCreate, but I am not so sure.
 
Anyway thanks in advance! And please let me know if you don't understand that question and I can give more details!
 
thanks,
Brandon


Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.

Discover Yahoo!
Find restaurants, movies, travel & more fun for the weekend. Check it out!

Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.


YAHOO! GROUPS LINKS



Reply via email to