Abiola Oyedola Support Engineer

Title: Issue with Purchase Order Linked to Project

Description

When a purchase order is created and linked to a project, please ensure the following steps are completed before proceeding:

1. Set up the "Create Item Requirement" option.
2. Create the TM project, which will be linked to the purchase order.

Once the purchase order is linked to the project and posted, navigate to the project page, and under the item requirement section, attempt to invoice the sales order (item requirement). However, the item does not get stamped, resulting in a "rejected" status and displaying the error message below.

Additionally, the XML generated does not include the fields "ClaveProdserv" and "ClaveUnidad," which are required.

Resultado Descripcion="El campo ClaveUnidad no contiene un valor del catálogo c_ClaveUnidad." IdRespuesta="CFDI40165" Detalle="CFDI40_0065_ValidaConcepto_ClaveUnidad" FullError="<Errores>  <Error>    <Codigo>CFDI40165</Codigo>    <Mensaje>El campo ClaveUnidad no contiene un valor del catálogo c_ClaveUnidad.</Mensaje>    <Detalle>CFDI40_0065_ValidaConcepto_ClaveUnidad</Detalle>    <MensajeParaCliente>El atributo 'ClaveUnidad' es requerido y no puede ser vacío o nulo, para el concepto con ClaveProdServ ''.</MensajeParaCliente>  </Error>  <Error>    <Codigo>CFDI40158</Codigo>    <Mensaje>La clave del campo RegimenFiscalR debe corresponder con el tipo de persona (física o moral).</Mensaje>    <Detalle>CFDI40_0058_ValidaReceptor_RegimenFiscalReceptor</Detalle>    <MensajeParaCliente>La clave del campo RegimenFiscalR debe corresponder con el tipo de persona (física o moral).</MensajeParaCliente>  </Error>  <Error>    <Codigo>CFDI40162</Codigo>    <Mensaje>El campo ClaveProdServ, no contiene un valor del catálogo c_ClaveProdServ.</Mensaje>    <Detalle>CFDI40_0062_ValidaConcepto_ClaveProdServ</Detalle>    <MensajeParaCliente>El campo ClaveProdServ, no contiene un valor del catálogo c_ClaveProdServ.</MensajeParaCliente>  </Error> </Errores>" />

Actual Outcome: The CFDI is not including the information in the "ClaveProdserv" and "ClaveUnidad" fields.

Expected Outcome: Since the "ClaveProdserv" and "ClaveUnidad" information is provided for the sales order (required items) in question, once posted on the project page, the CFDI should be approved instead of "rejected." Furthermore, the XML should include the information for the "ClaveProdserv" and "ClaveUnidad" fields as defined in the system.

Issue Description:

In the current system behavior, when a credit memo is applied to a vendor payment, the credit is correctly deducted from the total amount, and the resulting payment amount is accurate. However, the payment advice does not display a separate line or reference to the applied credit memo, which leads to confusion on the vendor's side.

Vendors often interpret the reduced payment amount as a short payment, since they have no visibility into the credit memo application. This has resulted in multiple inquiries and misunderstandings.

Business Impact:

The absence of credit memo visibility in the payment advice is causing unnecessary confusion and manual follow-up between customers and vendors, impacting operational efficiency.

Requested Action:

We kindly request that the system be enhanced to include credit memo details—such as the reference and amount—in the payment advice document. Ideally, this would appear as a distinct line item or explanatory note.

Please consider this improvement for inclusion in version 10.0.43 or in a future release.

Thank you for your attention to this request.

Summary:

The customer would like the alignment date to influence the start date of the billing schedule. This would ensure that recurring contract or subscription billings occur consistently on the same day each month. Furthermore, the system should intelligently adjust the start date when billing falls on the 29th, 30th, or 31st of a month to ensure only one invoice is billed and recognized per month.

Current Behavior:

The system calculates billing based on the specified start and end dates. When an alignment date is entered, it currently only affects the end date.

Expected Behavior:

An additional field or functionality should be available in the alignment date section that allows the start date to be adjusted or aligned automatically as well. This would allow for consistent billing intervals and prevent overlapping or duplicate billing within a single month.

Repro Steps / Navigation Path:

1. Go to: Subscription billing > Billing schedules > All billing schedules > New
2. Enter the following details:

• Customer name: [Enter Name]
• Billing start date: 3/31/2025
• Number of periods: 12

1. The Billing end date will be automatically calculated as 2/28/2026
2. Click OK
3. Create Billing Schedule Lines
4. In the Lines > General section, enter 4/29/2025 as the Alignment Date
5. In Billing Schedule line section, go to view billing detail

Observed Outcome:

The system updates only the end date based on the alignment date.

Expected Outcome:

The system should also align the start date, or there should be an option to enable start date alignment.

When disposing of Fixed Assets using the Disposal Scrap, the system generates a “Depreciation Adjustment” transaction that incorrectly reverses the entire accumulated depreciation.

The expected behavior is that it should only adjust the remaining (pending) depreciation or any excess amount that may have been recorded in error. Kindly consider implementing a solution for this version 10.0.43 or the nearest upcoming version.

The "Number of Days Rented" field is not visible in the mobile app, despite being correctly configured in Dynamics 365 (D365) as a Recommended field for the Car Rental expense category.

Steps Taken / Configuration Details:

• The field has been set as Recommended in the Expense Management configuration within D365.
• The issue appears to be isolated to this specific field.
• Other similarly configured fields, such as "Number of Nights" for the Hotel expense category, are displaying as expected in the mobile app.

Impact:

• Mobile users are unable to input the number of days rented for car rental expenses, potentially leading to incomplete or inaccurate expense reports.

Steps to Reproduce:

1. Navigate to:
2. Expense management > Setup > General > Expense fields visibility (Expense reports re-imagined)

⚠️ Ensure that the company you're configuring is the same company used to test in the mobile app.

1. Select Category:
2. On the left panel, choose Car rental category.
3. Field Configuration:

• Locate the field: "Number of days rented"
• Set the Visibility to "Recommended"
• We also tested with other values like "Required", but the issue persists.

1. Confirm Expense Category Type:
2. Navigate to:
3. Expense management > Setup > General > Expense categories

• Active category: Car Rental
• Inactive categories: 110-Sales-Car Rental, 210-Office-Car Rental
• For each, open the category and check the “Expense type” field.
• Value is set to “Car rental”

1. Mobile App Testing:

• Open the Expense Management mobile app
• Go to the Expenses tab
• Tap the "+" button to create a new expense
• Click Skip (no receipt needed)
• Select “Car rental” as the Expense category
• Enter a Transaction amount
• Leave or modify Currency, Transaction date, and Payment method
• Tap “Add more details”

1. Issue Observed:

• The field “Number of days rented” is not visible in the app
• That field appeared once exactly where I highlighted in yellow color

1. Validation:

• We confirmed the configuration is applied to the correct legal entity used in the app.

Additional Observation:

• This issue appears to be specific to the Car Rental category.
• For example, in the Hotel category, the field "Number of nights" is also set to "Recommended" and does appear in the mobile app as expected.
• Steps to confirm:
• Configure “Number of nights” for Hotel category in Expense fields visibility
• Create a Hotel expense in the mobile app
• Tap “Add more details”
• Field does appear correctly