How to resolve error “INVALID_FLD_VALUE The field custrecord_ste_backend_inv_error_details contained more than the maximum number ( 4000 ) of characters allowed.”

Scenario: An error keeps showing when we enter each detail in the Tax Registrations subtab of vendor, or customer records. The error-mentioned field is from the Suite Tax Engine bundle and is a locked one. We have recently migrated to SuiteTax and the new subsidiary implementation is ongoing. The error started after SuiteTax Migration. The… Continue reading How to resolve error “INVALID_FLD_VALUE The field custrecord_ste_backend_inv_error_details contained more than the maximum number ( 4000 ) of characters allowed.”

Post approval edits on Journal workflow

Scenario: The client wants the journal to go through approval routine, if the admin edits the journal after approval. i.e. Administrator edits trigger re-approval and JE is unposted until re-approved. The journal contains a review state. Reviewed journals will be submitted for approval by admin. If they are approved by admin it should go to… Continue reading Post approval edits on Journal workflow

Saved search not displayed in the custom field creation page

Scenario: While creating a custom field and trying to set the value of the field through search, the page is not displaying the created search. i.e. A saved earch has been created. But the search is not displaying in the custom field creation page. Solution: Confirm that the search fulfills the following: Apply a valid… Continue reading Saved search not displayed in the custom field creation page

BOM revision update through CSV import

Scenario: User wants to update the BOM revision by removing the existing Bom components and adding new components through csv import. Solution: For removing the existing components, select update and check the ‘override sub list’ checkbox in import options. But if you add all the components in the same file and set the file for… Continue reading BOM revision update through CSV import

Mapping HSN code of items in PO for overseas vendor

Scenario: During Purchase Order import, the vendor’s registration type is ‘overseas’ therefore GST is not applicable for the vendor. But the item has hsn code with GST rule applied which results in automatic tax calculation. Solution: Since GST tax calculation is not required for the vendor, map ‘Tax details override’ as ‘Yes’. Now, tax calculation… Continue reading Mapping HSN code of items in PO for overseas vendor

Updated auto-generated numbers manually but the new record created does not have the required document number

Manually updated the autogenerated numbers of journals using ‘ALLOW OVERRIDE’ option but the next document number generated automatically is not the required one task reference: Surin-762 This can be overcome by checking the ‘Update Initial Number’ field and entering the required value as initial number. Then new journal entries will possibly be created with the… Continue reading Updated auto-generated numbers manually but the new record created does not have the required document number

Auto-Generated Numbers updation

A user wants to update autogenerated numbers of Journal entry Recommendations or steps to manually adjust or reset the numbering. Enable the ‘Allow override’ option corresponding to journal, by navigating to Setup > Company > Auto-Generated Numbers > Document Numbers ALLOW OVERRIDE – when enabled, the auto-generated numbers assigned to numbered records cannot automatically be… Continue reading Auto-Generated Numbers updation

Create outsourcing charge item

Outsourced manufacturing items are the goods and services that have been produced in cooperation with your outsourcing vendor. You need to define the charge item used in the purchasing transaction. To create an outsourcing charge item: Go to Lists > Accounting > Items > New. On the New Item page, click Other Charge for Purchase or Service For Purchase.… Continue reading Create outsourcing charge item