11
Points
Questions
0
Answers
5
-
If you’re trying to automatically link an Intercompany Purchase Order to an Intercompany Sales Order, the key issue is that you should not try to set the
Paired Intercompany Transactionfield directly. NetSuite explicitly says that field is not intended for the PO → SO workflow.For intercompany PO/SO transactions, NetSuite’s supported process is to use Manage Intercompany Sales Orders → Generate Sales Order, which creates the SO and establishes the native PO/SO pairing and
Intercompany Status = Linked.So the likely fix: use NetSuite’s intercompany generation process/API/action rather than creating a standalone SO and attempting to populate the pairing field yourself. If you’re scripting it, share the code and exact error message—the missing field/record transformation can then be identified precisely.
- 2350 views
- 2 answers
- -1 votes
-
- 5234 views
- 1 answers
- 0 votes
-
- 4518 views
- 3 answers
- 0 votes
-
@ hbethel , The likely issue is not the feature setup. With SuitePromotions enabled, the promotion must be eligible for the specific customer + items + date/channel, and the Sales Order must have a customer and at least one item before the Promotion list populates.
Check these first:
- Promotion type: Make sure you created a SuitePromotion, not an older/standard promotion that isn’t compatible with SuitePromotions.
- Eligibility: Verify the promotion’s Customers/Audience, Items, Sales Channel, start/end dates, and usage limits. Any mismatch can make the list empty.
- Coupon code: For a coupon-based promotion, make sure the coupon code is active, valid, and associated with that promotion.
- Test order: Select the customer first and add at least one eligible item, then go to the Promotions subtab. NetSuite requires both before promotions can be applied.
- Don’t move the old fields back to Items. With SuitePromotions enabled, NetSuite’s intended UI is the Promotions subtab; the Promotion/Coupon fields normally move away from Items automatically.
Most likely culprit: your promotion’s eligibility criteria don’t match the test Sales Order. As a quick test, create one simple promotion with Available to All Customers, no restrictive item/customer criteria, valid dates, and a multi-use coupon, then test it against a normal customer + eligible item.
There is also a recent NetSuite Community thread describing essentially the same symptom—even with Promotion Codes, SuitePromotions, Auto-Apply, dates, items, coupons, and customer eligibility correctly configured—so if the basic test still produces an empty list, it may be an account/configuration issue rather
- 477 views
- 1 answers
- 2 votes
-
@
Yes. The best way is to use NetSuite System Notes as the audit trail.
- Open the Sales Order → System Information → System Notes. NetSuite records the field changed, old value, new value, timestamp, user, and change context.
- For Salesforce synchronization, create a System Notes saved search filtered by the Sales Order and the relevant fields. You can also filter by context to identify changes made through web services, SuiteScript, CSV, etc.
- If you need to automate the comparison, System Notes are searchable through SuiteScript, allowing you to retrieve the changed field and old/new values.
Recommended approach: Before syncing to Salesforce, query the Sales Order’s System Notes for changes since the last sync, identify the modified fields, and send only those fields to Salesforce. This gives you a reliable NetSuite → Salesforce change-tracking mechanism without having to compare the entire Sales Order each time.
- 899 views
- 3 answers
- 0 votes