Is there any settings for NetSuite GL Impact Credit/Debit Amount sourced from another Column?
Or We can Update Journal Entry record GL Impact by deploy one SuiteGL-Plugin?
The question is a little general which means the answer will also be...
It sounds like a a GL Plug in is what you want. It runs every time a transaction is saved. It dose NOT give you the ability to change the original lines that are created. What it dose is give you the ability to create more lines to reallocate the money so you could debit the credited account and then credit a new account.
You will need to enable the plugin before using it.
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_3989534344.html
If you decide to go this route and have a more specific question please ask.
Related
I have an invoice with 500USD after that I have the journal entry with 500USD. While I'm doing payment I can add the amount to 800USD so on odoo it will give an option to keep open or Mark As fully paid. So I'm choosing the keep open option So as per this case odoo has to keep the invoice in an open state with 300USD remaining amount but why it should change the state to pay with the same invoice amount?
So anyone can suggest the functional thing with this case?
Yes you're right this is the default functionality of the Odoo and it is extremely cool thing in Odoo because Odoo is managing outstanding payments of our customer very effectively.
Important Point
If there is an invoice of 500USD and I registered 800USD yes it is
right thing to close the invoice 500USD because customer has paid it.
But what about the remaining 300USD. Odoo has cool feature to manage
outstanding payments. Here you can see in attached image.
I've an invoice of 125USD and I registered 200USD (200-125=65USD) then see how Odoo manage it for my important customer.
I'm creating a contract API solution to keep items in sync between multiple tenants. Is there any way to track the changes to InventoryCD? In this case one Franchiser would like to update items in their 6 franchisees. It's easy for me to find the records that changed, but harder to know when the CD has changed (importantly what it chagned FROM). Certainly I could write customization to do it, but I thought maybe Acumatica has some option inbuilt.
Ideally I'd like to have a log of the changes with old and new CD. It's hosted so I don't think I can make it happen with DB Triggers (which is how pre-Acumatica me would have handled id)
Thanks in advance.
It depends on the Acumatica version. But have you tried looking at Business Events? I believe there is the ability to access the old and previous values.
Also look at Acumatica's Audit history capabilities but be careful to only turn on the fields you need to track as the DB can grow very large if you turn on all fields on the Stock Item screen or for any screen.
Hey there I'm trying to draw state machine diagram for this scenario but It's missing lots of information. If someone here could help out with it.
The Scenario
Tourists will start the journey by selecting the trip using the
Automated Ticketing system (ATS).
The Automated Ticketing System (ATS) will display the trip details.
This Trip details will include the seat-number and destination.
Based on provided trip details, the ATS will compute payment.
The tourist has the option to pay the payment by cash or credit
card.
If the tourist will insert a wrong amount of cash, the ATS will
display "Insert More Cash" message on the screen until the correct
amount will be inserted.
If payment by card was selected by the tourist, the ATS will perform
two parallel tasks. It will validate the expiration date of the card
and check the credit balance. If card is accepted, the bank will
authorize the payment and will update the account of the tourist.
However, if card is not accepted or invalid, the ATS will again ask
for payment option (back to step 5) from the tourist.
After payment is complete, the ticket and receipt are printed by the
ATS.
Cash payment might result in some change, so the change is also
dispensed by the ATS. The tourist will then get the ticket and the
change.
ATS will display the message "Transaction Complete" at the end of
the transaction.
My Drawing:
Ok, so I try to give you some hints. A state machine is always created for a single class, not the overall system under consideration. So let's assume the ATS is a single class (in reality it will probably be more a component consisting of several classes). Now this ATS will in the beginning be idle. It is triggered somehow when a trip is selected. It then has to complete the journey details. It waits for payment and finally it will spit out a ticket. Now (basically!) the state machine looks like this:
This is a scaffold and it was done without reading the details above. Note that instead of the cancel transitions you could use a general exception from an interruptible region which eventually clears payments. In practice you would likely do that since a cancellation should (from a user perspective) be possible at any point. A time out of course would also be possible (what if already some cash had been paid?).
Also I did not include the do/entry/exit actions. For the cash this would be something like add new cash sum so we know when enough money has been paid.
I've hit a bit of a wall trying to figure out how to bulk remove old emails within Netsuite (ie. transactions emailed to clients, statements, etc...).
I have over 40,000 emails taking up way to much storage space within NS.
Can't seem to do it via Workflow or Mass Update etc...
Is there a simplistic method I'm missing? Or am I going to have to write some suitescript to do it.
Cheers
I've used a Mass Delete Script before which works great on other records. I haven't used it on messages, but I did confirm that you can deploy it on messages so it should be good. Steps to use it are:
Install bundle 18108.
Create script deployment for the record type you want to delete (Message in your case)
Go to Mass Updates and expand Custom Updates. You should see Mass_Delete_Script in there under Message.
Create mass update as you usually would - TAKING EXTRA CARE NOT TO CLICK "PERFORM UPDATE" UNLESS YOU'RE ABSOLUTELY SURE YOU'RE SEARCH IS CORRECT! Beware that you can of course cause a lot of grief very quickly with a tool like this. On the other hand you can save a lot of time too :)
I create a weekly report on sales opportunities and am being asked to report on changes (e.g. change in deal size, new deals, closed deals), specifically looking at the biggest changes.
Any tips on how to accomplish this?
Create a new SalesChangeHistory entity that gets populated whenever a Sales Opportunity changes via a plugin. It could include flags that specify if the change was a change in size, brand new, or closed.
If you didn't want to develop new entities and plugins you could turn on auditing and create an SSRS report against the audit data. The data isn't in the best format but it's achievable! (just!)
Having said this the "best" solution would be as Daryl has suggested.