Best Of

Glad to hear that, @User_ZA0IY! I'll have it documented here in the NetSuite Support Community.

Hi @Elizabeth Vance

In NSAW, the field NKEY is a surrogate key generated within the warehouse. It does not directly correspond to the Source Record ID from NetSuite, which is why joining on Source Record ID would not return matching results.

For tables like DW_NS_TRANSACTIONSHIPPINGADDRESS, the NKEY is intended for internal joins within NSAW, typically linking to related fact or dimension tables using warehouse-generated keys rather than source system IDs.

To properly connect shipping address data to transactions, you would usually:

• Identify the corresponding foreign key in the transaction fact table (e.g., shipping address key)
• Join using the NSAW surrogate keys (NKEY or related keys) instead of Source Record ID

For more details on NSAW data modeling and structure, you may refer to:

• Oracle Documentation (NSAW Overview & Admin Guide): https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawa/
• Oracle Analytics / Data Modeling Concepts (surrogate keys & warehouse modeling): https://docs.oracle.com/en/cloud/paas/analytics-cloud/

Regards

@Bry Cabria-Oracle

Thank you for suggestions, I will review the articles

Appreciate sharing the links!

Hi, @Bry Cabria-Oracle, Yes, I was using a custom role. The issue was resolved after adjusting the permissions.

Thank you for your help!

The NetSuite documentation on ACH doesn't clearly mention the requirement for Automated Clearing House permissions, which can be confusing.

Hi Vicki Bollinger

Customer Mapping Rules are created when you manually select a customer for a bank line, and NetSuite stores the association based on the Payor and Memo values from that line. Best practice is to create rules only when those values are consistent and uniquely identify a customer. If the same Payor or Memo text is used by multiple customers, it’s best not to create a mapping rule, as NetSuite does a direct comparison and may resolve the bank line to the wrong customer on future imports.

Hope this helps

HI @Judith Culanding-Oracle Thanks for your reply to confirm there is no localisation pack for OCR number based ACA. I will wait to see if there any other responses for an alternative solution for this requirement.

If you are receiving the 400 - Bad Request (request header or cookie too large) when attempting to log in via Chrome, try another browser.

Just received the same error when I tried to login to CertView using Chrome:

Good news is that I was able to login using Firefox. 😊

Hi @Dext3r!

Good day!

Can you try the steps below?

1. Login as an administrator.
2. Navigate to Setup > Users/Roles > Manage Roles > Select Role
3. Select Edit.
4. Add the following permissions:
   - Permissions > Lists > Custom Record Entries : Full
   - Permissions > Custom Record > WMS Item Alias : Full

Let us know if this would work, thank you!