_O6NAQ's Profile
Rookie
11
Points

Questions
0

Answers
5

  • Rookie Asked on August 19, 2026 in SuiteTalk.

    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 Transaction field 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
  • This error usually means your script is trying to create Inventory Detail on a line that doesn’t support it or is missing the required bin/lot/serial information.

    For an Item Fulfillment, check:

    1. Item type — confirm the item requires inventory detail (bin-managed, lot-numbered, or serialized).
    2. Location — make sure the fulfillment location matches the item’s inventory/location setup.
    3. Bin/Lot/Serial — if required, populate the inventorydetail subrecord with the correct bin, lot, or serial number and quantity. NetSuite requires serial/lot details when fulfilling those items.
    4. Don’t create inventorydetail for ordinary items — NetSuite will throw this exact error if the line doesn’t support an inventory-detail subrecord.
    5. For bins, verify the bin actually has sufficient available quantity at the fulfillment location.

    If you’re using SuiteScript/SuiteTalk, the key is to only access/create the Inventory Detail subrecord when the item requires it, then populate the appropriate binNumber, issueInventoryNumber/lot or serial number, and quantity. The Inventory Detail record is a subrecord of the parent transaction.

    In short: Don’t blindly create Inventory Detail on every fulfillment line. First determine whether that item/location requires bin, lot, or serial tracking; then supply the correct inventory assignment.

    • 5234 views
    • 1 answers
    • 0 votes
  • Yes. NetSuite can generate an Intercompany Sales Order from an Intercompany Purchase Order, and the transactions are automatically paired with Intercompany Status = Linked.

    However, for standard intercompany inventory transactions, Oracle documents the supported process as Manage Intercompany Sales Orders → Generate Sales Order; simply creating an SO via SuiteScript and setting the paired-transaction field is not the supported pairing mechanism.

    Bottom line: SuiteScript can automate the surrounding process, but if you need NetSuite’s native intercompany pairing, the transaction should go through NetSuite’s intercompany-generation process rather than manually setting the pairing field.

    • 4518 views
    • 3 answers
    • 0 votes
  • Rookie Asked on August 19, 2026 in Marketing.

      @ 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:

    1. Promotion type: Make sure you created a SuitePromotion, not an older/standard promotion that isn’t compatible with SuitePromotions.
    2. Eligibility: Verify the promotion’s Customers/Audience, Items, Sales Channel, start/end dates, and usage limits. Any mismatch can make the list empty.
    3. Coupon code: For a coupon-based promotion, make sure the coupon code is active, valid, and associated with that promotion.
    4. 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.
    5. 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