Sreedhar Burgula

Business Scenario Company is having a fixed price project signed with one customer with below criteria - Milestone are o First Milestone - 100,000 $ o Second Milestone 200,000 $ o Last Milestone 300,000 $ - Retention term 10% to be deducted from each milestone till the work is completed 100% - Its mentioned in the contract if the company will not complete the milestone in the scheduled date, 1% from milestone value will be deducted from total invoice amount First milestone: After completing first milestone in the agreed date, invoice for the 100,000$ is issued to customer, the invoice should contain the below details Work Done 100,000 Retention 10,000 Invoice Amount (90,000) So the voucher should be as below Dr. Customer 90,000 $ Dr. Retention 10,000 $ Cr. Unearned Revenue 100,000 $ In this entry, system is 100% fit the business need Second Milestone When having a delay in delivery for the second milestone, deduction should be added to invoice amount, so invoice will contain the below details Work done 200,000 Retention 20,000 Penalty Deduction 2,000 Invoice Amount 178,000 So the voucher Generated from system should be Dr. Customer 178,000 Dr. Retention 20,000 Dr. Delay Penalty(expanse account) 2,0000  This entry is missing in D365 FO Cr. Unearned Revenue 100,000 This is for Fixed Price project. This Request is logged on behalf of the partner Mohammed Rasheed (SR 119030519729898)

Using 'create project invoice proposals' menu item under Project management and accounting > Periodic > Project invoices. When running this in batch the batchhistory table is growing to fast. This is caused by the parameters field on the batch and batchhistory table. The tasks for the class 'ProjInvoiceProposalCreateLinesTask' is adding a record in the batch table with a huge parameters field. These parameters cannot be viewed in the user interface. Cleaning this parameters field for these specific tasks clean up the tables. This parameter field should cleared after running the task.

We create a New Subscription Fee with "Regular "and we cancel it with the new Subscription Fee with the Subscription type “Reduction days".

When we try to Invoice this from the project, on the Invoice proposal summary, we see both the transactions with negative and positive values with the Billable line property.

If we print the Invoice proposal summary form the report shows both the amounts, which is confusing.

The Expectation here is to show only the balanced transaction amounts instead of both the transactions lines the Invoice proposal summary form

For our client timesheets come in to D365 in an approved status (bypassing the workflow). However, some timesheets are appearing in 'Reset unposted timesheets to draft' which is causing confusion.   

Each table has a RecId that is unique on its own table, meaning that no 2 records on the same table have the same RecId however, this RecId isn’t necessarily unique on 2 different tables. 

Also, the workflow tracking status table has a link to this RecId and the TableId.

So basically, what is happening here is that there are 2 tables with the same RecId (which again, no problem with this) and the query used only links on the RecId (doesn’t care about the TableId to link to the timesheet table)

Example: Timesheet has the RecId of 5637380088, but there is another record on IQ01 on the table (LedgerJournalTable) mentioned on the TableId that has a workflow associated with it.

 Basically, the query on this form is taking the RecId from the TSTimesheetTable and linking with the WorkflowTrackingStatusTable (It does other links and verifications to make sure if they should appear on the form, but they are irrelevant for this issue).

             The problem here is that, with only this RecId link, there is no way to verify if the WorkflowTrackingStatusTable record is supposed to be for Timesheets or for any other table. For Example:

• We have 2 tables with the same RecId. TSTimesheetTable and LedgerJournalTable with RecId 5637380088 (This can happen, this is normal, no issues here).
• The TSTimesheetTable doesn’t have a workflow associated, but the LedgerJournalTable does have one:
• So, when the query is trying to link the TSTimesheetTable with the WorkflowTrackingStatusTable using only the RecId, it finds the workflow for the LedgerJournalTable. Which is completely wrong.

To fix this issue I suggest confirming if the workflow is from a timesheet using the ContextTableId available on the WorkflowTrackingStatusTable, or, using the Document field to check for Timesheets only.

If item requirement PMA parameter is enabled à system is not checking budget check results.

We have the business scenario where the project purchase order should have the budget check performed while the item requirement is created.

When you create a beginning balance journal from: Project management and accounting -> Journals-> Beginning balance then create a transaction for a specific project. Then go check on beginning balance for that project, the created project is not retrieved:

Project management and accounting->Projects->All Projects the journal doesn't' appear.

If you do the same test with fee, hour our expense journal the journal is also shown on the specific project.

• What is the business impact to the customer?

The analysis of the project can be mistaken as we do not find a beginning balancing journal created on the project

The manager on charge of the project will not have access to the migration journal with all the projects inside

• How does the problem impact their business? Financials

It concerns 80% of the business – Fixed price

Upon theses analysis, we decide if the project is profitable or not and change the pricing

• How frequently does this issue occur? -

Once for migration.

 but impact for all time for the history of the project

• Is there a workaround? –

No, checking by each journal is not allowed to the manager and they have to find the right journal

Just for one company, we had 10 journals with 1500 lines

• How many users are affected by this issue? – 

2000

When the user posts a project invoice (in charts of accounts on revenue account activate dimension project) in a currency which is not company currency on date 1.1.2023 with exchange rate X

When run under AR the periodic process for revaluation (Accounts receivable foreign currency revaluation) at 31/1 (put an exchange rate Y on 31/1)

The system will create a transaction within the revenue account 0 in invoice currency and XXX in company currency with dimensions project.

We would like to have this transaction also on the project (so to see it under manage/posted transaction in project)

We have attached a document on the Hour journal and posted it. When verified the project posted transactions this attachment is not visible in the action pane at the paper clip symbol .

When we add the attachment on the posted transactions and we try to adjust the transaction. This attachment is not visible in the at the paper clip symbol .

Period type is Week with auto-split in case of month end. Week starts on Monday. 

Missing timesheet notification should be sent on weekly basis but also needs to cater for month-end. 

Since timesheets need to be submitted on weekly basis, the missing timesheet email batch is scheduled to run in recurrence that includes each Monday. 

However, since month-end can be in the middle of the week, missing timesheet notifications need to be scheduled to run also on the first day after the month-end. 

Example: Jan 31, 2023, is Wednesday. There will be two timesheet periods: for week 5: Jan 30 - Jan 31, 2023, and Feb 1 - Feb 5, 2023.

Missing timesheet mail notification should be received on Thursday (Feb 1, 2023). The batch job cannot be set with recurrence per weekday, since month-end will be in different weekdays. The option "repeat a specific weekday" by a fixed interval cannot be used, since it also requires a weekday to be chosen. 

Period type is Week with auto-split in case of month end. Week starts on Monday. Saturday and Sunday are not working days as per the calendar attached to the project resources. 

Missing timesheet notification should not be sent if the period includes non-working days. 

Example: There are cases, in which a period contains non-working days only. example: Saturday-Sunday, e.g. April 1- April 2, 2023. 

Since these are non-working days, the users should not receive a missing timesheet email. Currently, it seems that this cannot be avoided.