GL Impact and Hidden Custom Segment Fields
This topic describes GL impact and hidden custom segment fields. For overview information about configuring GL impact for a custom segment, see Configuring GL Impact for a Custom Segment Overview.
If a custom segment with GL impact is set for both the transaction body and transaction line fields, NetSuite automatically uses the body value for the line when the line field is hidden (by clearing the Show option in the Sublist Fields subtab of the form). This keeps financial reporting accurate, even if you can't set or see the segment at the line level.
However, when the line field is visible, NetSuite doesn't automatically copy the body value to the line. In this case, you must enter a value in the line field if you want it to be different from, or the same as, the body value-there's no default carry-over.
This default behavior changes only if a customization, like a Custom GL Lines plug-in or script, overrides it. If the line field is visible, you can enter a different value. This applies only to custom segments with GL impact enabled, ensuring correct reporting on all affected transactions.
Example Scenario
Suppose you have enabled GL impact for a custom segment and use it on Transfer Orders and Item Receipts. When an Item Receipt is created from a Transfer Order, you expect the custom segment value set on the Transfer Order to carry over automatically. If the custom segment's line field on the Item Receipt form is hidden, NetSuite automatically copies the body value, and the correct segment value will appear. However, if the line field is visible on the form, NetSuite will not auto-populate the value from the body, which may result in the segment value being blank on the Item Receipt lines. In such cases, you must manually enter the value, or edit and save the record to populate it. Consider hiding the line field or using a customization if you want the value to always carry over automatically during record transformations
For details about supported transformations that should be automatically populated, see Supported Transformation Types.