Best Of

Hi @User_NQL2C

Ramu is correct. The main reason why you cannot apply a Credit Memo to a Purchase Order is because PO is a non-posting transaction.

Please let us know if you have clarification. Thanks

We would greatly appreciate if you can click "Yes" on “Did this answer the question?” below the comment/s that helped in your concern. Doing so will help other community members who might have the same concern find the answer easier and you will also get closer to earning your next Answer Accepter badge. Thanks! 

Hello @Jet Zhang

Good day to you.

But you can try canceling a workflow instance from a single record.

When you cancel a workflow instance for a single record, NetSuite reloads the record. Therefore, when a workflow is set to initiate On Update and uses the All or Before Record Load server triggers, the workflow instance re-initiates when you cancel it.

1. Edit or view the record on which the workflow instance runs.
2. Click the Workflow subtab. The Active Workflows subtab appears by default.
   1. Note : Any other workflow instances still run; you must cancel each one individually.
   
3. Click Yes in the popup.
4. Optionally, click the Workflow History subtab to see the canceled instance. The Notes column displays the name of the user who canceled the instance.

Or as @Ramu Komireddy_9891, you can try doing it manually.

Let me know what ever works for you.

Hi Everyone
Thanks for the suggestion. The problem was resolved successfully. I tried temporarily unchecking this configuration.

Regards

Didik Rohadi

Thank you @Ramu Komireddy_9891 for sharing your insights on this!

Hi @Didik_Rohadi

Thank you for posting here in the NetSuite Support Community!

Hello everyone! One of our fellow members could use a hand. Please feel free to join this thread and share your knowledge, ideas, or tips. Your contributions are always valued and truly appreciated!

Thank you @Todd N Niedringhaus and @Michelle Jabanes-Oracle for your responses. This gives me confidence the upgrade will occur at the time we requested. Appreciate your insights!!

Vicki

Hi @User_HM9P7 Per checking, it is still possible that this is a NetSuite defect related to the 2026.1 upgrade. Issues like this don’t always appear immediately after an upgrade. Sometimes they surface later due to background patches, changes in system behavior, or specific transaction scenarios.

Since both issues started after the upgrade and are affecting standard functionality (saving Vendor Bills and subsidiary selection), this increases the likelihood that it could be a product defect rather than a configuration issue.

We recommend continuing to create ticket/follow up with NetSuite Support and asking them to check for any known defects or regressions related to 2026.1, and to treat both issues as potentially related.

Thanks for the tip @Ramu Komireddy_9891 !