Best Of

Hello @TEN

Will you please click on 'Related Records' and edit the payment for this transaction? (It shows as paid)

Edit the payment and then 'unapply' the payment for this invoice. The Invoice will now be Open.

Now Add your Withholding taxes. Save the record.

Once you have saved it with the taxes and items, you can apply your payment to the invoice again.

I hope this helps!

Hi @Karen See 

Since you are referring to this search, the values generated are captured on the Asset Record. However, we confirmed that these values cannot currently be updated through the UI. After further testing and investigation, I confirmed that this is a current system limitation covered under Enhancement 237902: “Fixed Assets > Asset Sale/Disposal tab > Ability to edit the fields on this tab.

As a workaround:

User has to "undo" the Disposal of the Asset and Dispose it again with the correct date.

1. Edit the Asset Record by changing the following fields:
   1. Asset Status - set it from Disposed to Depreciating.
   2. Current Net Book Value – from 0.00 to its actual amount prior to disposal.
   3. Cumulative Depreciation – actual amount prior to disposal
   4. Quantity – from zero to its actual quantity prior to disposal.
2. Delete the Posting Transaction created by the Disposal i.e., the Journal Entry (User can check this in the Asset Record > Depreciation History Tab).
3. Delete the Depreciation History Record (User can check this in the Asset Record > Depreciation History Tab).
4. Dispose the Asset under Fixed Assets > Transactions > Asset Disposal, this time with the correct Disposal Date.

You may disregard the workaround if this does not work for you. You can go to SuiteIdeas page to vote for the enhancement.

Apologies for the inconvenience this limitation may be causing you but I hope this helps clarify your concern.

Thanks and regards,
Ayie

Solved! There is an undocumented option you can use for submitFields() called disableTriggers

record.submitFields({

type: so.type,

id: so.id,

values,

options: { enableSourcing: false, ignoreMandatoryFields: true, disableTriggers: true }

});

Hey @User_K51C7,

Until now, we were able to modify the SCM Mobile processing only via script. I can't recall seeing any modification options via Workflow per the official SCM Mobile customization guide.

Hello @User_A5D7F,

If the context is about SAML configuration, then no, SuiteProjects Pro SAML SSO is not strictly “UPN only.”

What it actually requires is a unique user identifier mapped in the SAML assertion, and that is typically the SuiteProjects Pro User ID (Employee ID), not necessarily Azure AD UPN.

The required identifier is: NameID or user_nickname in which these will map to the SuiteProjects Pro User ID.

Note: If your IdP (like Entra ID/Azure AD) uses NameID internally as a transient/session identifier, Oracle recommends sending the actual SuiteProjects Pro user identifier through user_nickname.

Additionally, in practice:

For Microsoft Entra ID specifically, Oracle’s example setup explicitly instructs admins to create a custom claim called user_nickname that contains the SuiteProjects Pro User ID.

You can find more information about this via SAML Assertion Attributes, Configuring Microsoft Entra ID for the SAML Integration or SuiteAnswers ID: 96764 Configuring Microsoft Entra ID for the SAML Integration.

Hi @faisalabdulmoid_39498!

Good day!

Apologies for the late response.

Upon further checking, there is currently no official documentation confirming whether a Custom Record Description field from an SDF SuiteApp deployed on a trailing account will automatically convert into the AI Description field when deployed to an account with NetSuiteNext enabled.

At this time, the AI Description field is primarily utilized by NetSuite AI-related features and services, such as the NetSuite AI Connector Service. This service leverages the Model Context Protocol (MCP) to connect external AI platforms (for example, ChatGPT or Claude) with NetSuite data to support AI-driven responses and integrations.

Additionally, there is no available documentation outlining how AI-mandated features can be embedded into an SDF SuiteApp developed on a trailing account that does not have the NetSuiteNext feature enabled.

For further clarification, it would be best to coordinate directly with your Account Manager, as they may have more information regarding upcoming changes or recommended approaches. We also recommend monitoring future NetSuite release notes and official documentation for updates related to NetSuiteNext and AI-related SuiteApp behavior.

Hi @User_OFTMK try to use below formula,

CASE
WHEN NVL({appliedtotransaction.fxamount}, 0) != 0
THEN {appliedtotransaction.amount} / {appliedtotransaction.fxamount}
WHEN NVL({debitfxamount}, 0) != 0
THEN {debitamount} / {debitfxamount}
ELSE 0
END

1. Criteria: Type is Item Fulfillment.
2. Criteria: Main Line is False (to see item/GL detail).
3. Criteria: Tax Line is False.
4. Criteria: COGS Line is True (This is a hidden gem filter that often fixes IF reporting).
5. Results: Use the CASE WHEN formula above with a Summary Type of Maximum.

By filtering specifically for the COGS Line, you isolate the GL impact you want (the debit) while still being able to see the "Created From" (Sales Order) information.