プロフィール
Review our AI Community Guidelines before posting AI-generated or AI-assisted content. Verify accuracy and include the appropriate AI disclaimer.
Action Required: Review and submit pending reconciliation matches before the NetSuite upgrade to avoid rework. After 26.2, unsubmitted matches will be unmatched. For more details, see SuiteAnswers 1047397
コメント
-
Hi @Tapendra Singh Thanks for the detailed response. There was no GL impact for the item fulfilment. The fulfilment was done before the item receipt. The vendor bill had no GL impact for the item's COGs line The GL impact is: Item Fulfilment (14/11/2024): No impact 2. Customer Invoice (14/11/2024) Dr Accounts Receivable Cr…
-
The defect has a priority of 2 which is pretty high. It was resolved for us within the same day as logging it. Try logging a support ticket and see if it can be added to the existing defect. If not, get a new support case number then escalate that via your NetSuite account manager
-
It is a defect that has to be solved by NetSuite The defect number is in my post linked above it was supposedly fixed though if you are still getting the issue, you will need to log a support ticket.I would suggest quoting the defect number to cut through having to explain the issue to support
-
@David B Aus I believe it is a global defect and not just tied to a specific account. I am not sure about the 429 part. The defect id is #909682 . I would suggest logging a ticket and quoting that if the issue still isn't resolved.
-
We logged a ticket and this was NetSuite's response: A fix for U2 Issue #909682: Login > 429 Too Many Requests was released earlier today. Our engineers recommend the following steps to ensure the fix takes full effect: 1. Close all open Oracle NetSuite tabs in your browser. 2. Log in to Oracle NetSuite again.
-
I have found a way to prevent the credit memo from returning stock Set the Quantity to 0 and only set an amount that means the GL impact does not hit COGS or Inventory
-
False
-
Also, the credit memo adjusted the inventory stock on hand
-
Hi Thanks for the suggestions. I didnt think it's possible to void an invoice once it has been credited?
-
Hi @Ayitah Tallada-Oracle It is 2026.2 I have found a workaround to having to delete the bank statement reconciliations: On the bank account page (chart of accounts), untick the 'Match bank data' checkbox. Then use the legacy bank reconciliation page to match the transactions for the date being reconciled
-
I realise the issue: I missed the special order item field That explains why the PO was auto generated
-
False
-
false
-
Thanks @Jervin Nicholas Teopengco-Oracle Does that mean we can start using 2.1 scripts for plugins now? and they will work
-
Hi @Jervin Nicholas Teopengco-Oracle No the plugins are not part of a bundle. the Suiteanswer doesn't mention anything about plugins now being compatible with 2.1 thanks
-
Hi @Cherry Eunice B Licyayo-Oracle Thanks for this. The issue isn't that the balance sheet numbers are incorrect or that CTA is used instead of dedicated equity account for FCTR. It is that the intercompany clearing account continues to increase in value month on month, when there are no underlying transactions which are…
-
Hi @Cherry Eunice B Licyayo-Oracle Thanks for the detailed response. I had a look at the cumulative translation adjustment report and can see the contribution from the intercompany clearing account transactions. One thing I wanted to confirm: Shouldn't the exchange difference be coded to 'Foreign Currrency Translation…
-
The other related question I have: Why is there only a Cumulative Translation Adjustment account and not a CTA-E account generated? These are the features enabled:
-
HI @Cherry Eunice B Licyayo-Oracle the intercompany clearing account, a system generated account, is not eligible for elimination. Since the underlying transaction is an inventory transfer and not a monetary transaction (eg.. a payables or receivable transaction), would the CTA-E account be affected? I would think it would…
-
I think I found it entity field (label: Name) when mainline=False and 'Billable'field