Title: Message

Have checked the hotfixes and there is only one relating too Q orders and it does not fix the costing issues.

 

 

But thanks anyway

 

 


From: Axapta-Knowledge-Village@yahoogroups.com [mailto:Axapta-Knowledge-Village@yahoogroups.com] On Behalf Of James Flavell
Sent: 18 July 2005 04:06 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Quarantine

 

I think MBS have stated use of Q orders can cause problems in costing....check out their 'costing' package release which is backwards compatible to SP2 and SP3...I cannot recall whether this solves the Q orders problem or whether MBS know its a problem but do not have a answer to it....

 

SOrry not have the info at my finger tips right now...

James

 

-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:Axapta-Knowledge-Village@yahoogroups.com] On Behalf Of Craig Fidler
Sent: 18 July 2005 23:30
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Quarantine

Hi,

 

I am using Axapta 3 service pack three.

 

Using weighted average as a costing method, agianst the stock model group

 

When using the quarantine functionality for purchase orders the following situation arises.

 

Quaratine Warehouse

 

 

 

Transaction Warehouse

 

 

 

 

 

 

 

 

 

 

 

units

Cost

Extended

 Avg

units

Cost

Extended

 Avg

4

100

400

 100.00

4

100

400

    100.00

4

10

40

   55.00

4

10

40

     55.00

4

50

200

   53.33

4

50

200

     53.33

12

 

640

   53.33

12

 

640

     53.33

 

 

Standard Axapta takes the value of the inventsum and not of the purchase line.

 

 

 

Has anyone come across a problem like this before??

 

 

Regards

 

 

Craig

 



Sharing the knowledge on Axapta.



YAHOO! GROUPS LINKS




Reply via email to