-
Discounts are considered in different way depending on the form where we post the transaction
Look at TFS 3838627
Discount works in different way in each scenario. this behavior should be consistent accross the system:
SCENARIO 1 PURCHASE ORDER WITH ITEM REQUIREMENT: Create item requirement: Yes; Item consumption: Yes> Create a project purchase order for our item. Sales price = 0
SCENARIO 2 PURCHASE ORDER WITHOUT ITEM REQUIREMENT: Create item requirement= No; Item consumption= No> Create a project purchase order for our item. Select sales price = 10000
SCENARIO 3 MANUAL ITEM REQUIREMENT: Create item requirement> post packing slip. Unit price and sales price = 100; Net amount= 100
SCENARIO 4 PROJECT ITEM JOURNAL: Same as scenario 2 and 3
SCENARIO 5 PURCHASE REQUISITION: In the purchase order created from the purchase requisition, the sales price does not consider the discount 100
SCENARIO 6 REQUEST FOR QUOTATION: In the purchase order created from the purchase requisition, the sales price does not consider the discount 100 >BUT the project transaction considers the discount= 80 and invoice proposal is also fine
SCENARIO 7 SALES ORDER: When selection the item setup with discount: AX defaults unit price as 100 and discount as 20 and net amount is 80
SCENARIO 8: SALES AGREEMENT. The sales agreement does not default the price and either the discount. It is 0
SCENARIO 9: PURCHASE AGREEMENT. Purchase order created from the agreement has sales price 100 and does not consider the discount and Invoice proposal is fine and considers the discount 80
SCENARIO 10 PROJECT ASJUSTMENT: When making adjustments if we keep the option: Select fields to default values from setup: Sales price= Yes. The price is adjusted to the sales price without considering the discount, it means, it would change the price from 80 to 100
Scenario 11: WBS in project. System defaults price without discount
Scenario 12: Item forecast. Item forecast created from WBS: Sales price 100 without discount
Scenario 13: Project Quotation:
- Manual line: sales price considers discount. Unit price= 100; net amount= 80
- Create quotation from WBS: Unit price= 100; net amount= 80
-
Check Sales Tax Group should also check when sales tax group, item sales tax group or both are blank
After several fixes in AX 2012 te design of this feature was decided to:
- Do not verify if both the sales tax group and item sales tax group are blank.
- Do not verify if either the sales tax group or item sales tax group is blank. This is to prevent verification warning/error for scenarios such as multi-line journals and payment journals.
But this is still highly required specially in some countries and the workaround does not fully cover the lack and it is complex to setup.
Please, consider to improve the design to include those scnearios without breaking any other scenario.
-
Check Sales Tax Group should also check when sales tax group, item sales tax group or both are blank
After several fixes in AX 2012 te design of this feature was decided to:
- Do not verify if both the sales tax group and item sales tax group are blank.
- Do not verify if either the sales tax group or item sales tax group is blank. This is to prevent verification warning/error for scenarios such as multi-line journals and payment journals.
But this is still highly required specially in some countries and the workaround does not fully cover the lack and it is complex to setup.
Please, consider to improve the design to include those scnearios without breaking any other scenario.
-
Resourcing week always starts from Sunday and we should be able to edit this
Going to Project management and accounting> Project resources > resource availability> Yes. You can see all weeks start on Sunday and end on Saturday and this cannot be edited. The start of the week value is currently being hard coded in AVWeekProcessor class and hard coded Sunday as the start date of the week. In order to address this issue, we should expose a parameter in ProjParameter to capture resource scheduling week start date and default it to Sunday. If user will change this date to some other date, it needs to pop up warning message that ResRollup will needs to be run to recalculate the denormalized ResRollup table.
-
Improvement in purchase prepayment funtionaity
Invoice prepayment functionality is very limited and does not cover the real needs of customers business. Some missing basic features covered by other ERPs as Oracle are: Scenario 1. We cannot create multiple prepayments for just one purchase order: 1.- Create a PO: Quantity= 20; price 100 2.- Create a prepayment of 100 3.- Invoice the prepayment 4.- Create a product receipt of quantity 10 5.- Invoice the product receipt and apply the prepayment 6.- If we need to create a new prepayment. We are unable to do it. How can we create another prepayment for the same purchase order? It is a very common process that one PO has several prepayments and no just one. Scenario 2. We cannot create a prepayment for several purchase orders 1.- Create several Purchase order 2.- Try to create a prepayment linked to different purchase orders. How can we do this? Note: Add another purchase order option in the pending invoice is disabled for prepayments
-
Employee dimensions should retrieve dimensions from the position
When we create an employee from a position, D365 does not default the position dimensions for the new employee created for that position -
Tax exempt number for delivery address should be considered in the right way in EU Sales list
Tax exempt number for delivery address should be considered in the right way in EU Sales list. When we have a triangular transaction: one european country send goods to another european company to the warehouse they have in other one: ACTUAL RESULT Country is ok delevery country tax exempt number: Customer tax exempt number This makes that the customer name is not found also at lease in the Spanish report EXPECTED RESULT Country is ok delevery country tax exempt number: delivery tax exempt number Customer name is updated
-
prepayments from POS
When we register a prepayment from the POS, it is automatically registered in the BackOffice a payment journal to the Customer with the amount of the prepayment decreasing the amount to be paid in the sales order. According to the laws of many european countries the VAT that corresponds to the payment has to be declared at the moment of the payment (in D365 we have prepayment invoices) to the authorities. Suggestion to manage this scenario: When we generate prepayment from the POS, D365FO should generate automatically a free text invoice to get the tax registered, settling the transaction with the payment done. When the reception is posted the free text invoice should be credited to avoid the duplication of the invoice. -
Order HFP/1314/2022 on non reusable plastic packaging tax reports for Spain
There is a new legal requirement: https://www.boe.es/boe/dias/2022/12/30/pdfs/BOE-A-2022-23749.pdf which is not covered by the standard and it is mandatory for Spain since January 1st and it will be also requested in other EU countries.
Approved forms
- 592 'Self-assessment of Excise duty on non-reusable plastic packaging' and
- A22 'Request return of Excise duty on packaging Non-reusable plastic',
You’re offline. This is a read only version of the page.
