Transaction Types Supported By Custom GL Lines Plug-in
The following table lists the transactions supported by the Custom GL Lines Plug-in.
|
Transaction Name |
ID |
|---|---|
|
Assembly Build |
assemblybuild |
|
Assembly Unbuild |
assemblyunbuild |
|
Bill |
vendorbill |
|
Bill Credit |
vendorcredit |
|
Bill Payment |
vendorpayment |
|
Blanket Purchase Order |
blanketpurchaseorder |
|
Book-Specific Journal Entry** |
journalentry |
|
Cash Refund |
cashrefund |
|
Cash Sale |
cashsale |
|
Check |
check |
|
Credit Card Charge |
creditcardcharge |
|
Credit Card Refund |
creditcardrefund |
|
Credit Memo |
creditmemo |
|
Customer Deposit |
customerdeposit |
|
Customer Payment |
customerpayment |
|
Customer Refund |
customerrefund |
|
Deposit |
deposit |
|
Deposit Application |
depositapplication |
|
Expense Report |
expensereport |
|
Finance Charge * |
invoice |
|
Inventory Adjustment |
inventoryadjustment |
|
Inventory Cost Revaluation |
inventorycostrevaluation |
|
Inventory Transfer |
inventorytransfer |
|
Inventory Worksheet |
inventoryworksheet |
|
Invoice * |
invoice |
|
Item Fulfillment |
itemfulfillment |
|
Item Receipt |
itemreceipt |
|
Journal * |
journalentry |
|
Ownership Transfer |
ownershiptransfer |
|
Opportunity |
opportunity |
|
Paycheck Journal |
paycheckjournal |
|
Purchase Contract |
purchasecontract |
|
Purchase Order |
purchaseorder |
|
Return Authorization |
returnauthorization |
|
Revenue Commitment * |
revenuecommitment |
|
Revenue Commitment Reversal |
revenuecommitmentreversal |
|
Sales Order * |
salesorder |
|
Store Pickup Fulfillment |
storepickupfulfillment |
|
Vendor Prepayment |
vendorprepayment |
|
Vendor Return Authorization |
vendorreturnauthorization |
|
Work Order |
workorder |
|
Work Order Close |
workorderclose |
|
Work Order Completion |
workordercompletion |
|
Work Order Issue |
workorderissue |
|
* See Transaction Support Exceptions. ** Book-specific journal entries use the same transaction type ID as a standard journal entry. You can distinguish book-specific entries from standard ones by checking the accountingbook field on the TransactionRecord object (see Custom GL Lines Plug-In Interface Definition). Standard journal entries will have a null value in this field, while book-specific journal entries return the NetSuite internal ID of the accounting book. No matter how your accounting books are set up, the Custom GL Lines Plug-in runs only one time for the accounting book of the journal entry. If the plug-in is not configured for the accounting book containing the journal entry, it won't run at all. |
|
Transaction Support Exceptions
The following transactions are supported with restrictions:
-
Finance Charge. A special type of invoice, the plug-in supports this transaction type when created through an invoice form.
-
Journal. The plug-in supports Journals except in the following cases:
-
Voiding journal and reversing journal
These journals aren't supported because they cancel the original transaction and shouldn't create new GL impact
-
Open balance journal
-
Statistical journal
-
Intercompany journal
-
Intercompany elimination journal
-
Revaluation journals
-
Collect Tegata
-
Pay Tegata
-
Revenue reclassification
-
Revenue arrangements
-
Time posting to journal entry
-
Recognize gift certificate income
-
Allocate paycheck to jobs
-
Payroll: Create funding transaction
-
Payroll: YTD process
-
Payroll batch journal
-
Paycheck journal
-
-
Revenue Commitment. A plug-in implementation doesn't run on book-specific revenue commitments.
-
Sales Order. A plug-in implementation doesn't run on book-specific sales orders.
Transaction Processing
An implementation of the plug-in processes transactions by the following methods:
-
Voided transactions. Voided transactions with custom lines are handled the same as voided transaction with standard GL impact lines. See Voiding, Deleting, or Closing Transactions.
-
Memorized transactions. When you enter the transaction, the plug-in implementation creates custom lines. The transaction is also set to Posting or Non-Posting, matching the value for the standard lines.
-
Due date. Due date is set on custom lines when you save the transaction, and it matches the transaction date. This lets the custom line appear on aging reports.