Statistical Journal Entry Body and Sublist Fields

When you create a statistical journal entry, you must define certain body fields, and you must create at least one sublist line.

The required body fields are described in the following table.

Field	Description
unitsType	This field must reference an existing field listed at Lists > Accounting > Units of Measure. Later, when you populate the sublist, the account associated with each line must be of this unit type. This field cannot be updated after the statistical journal entry record has been created.
subsidiary (OneWorld only)	This field must reference an existing subsidiary listed at Company > Setup > Subsidiaries. Later, when you populate the sublist, each account you choose must be a valid account for this subsidiary. This field cannot be updated through SOAP web services after the statistical journal entry record has been created. You can update this field through the user interface. To do this, delete the lines from the sublist, select a new subsidiary, add new lines, and then save the modified record.

Field

Description

unitsType

This field must reference an existing field listed at Lists > Accounting > Units of Measure. Later, when you populate the sublist, the account associated with each line must be of this unit type.

This field cannot be updated after the statistical journal entry record has been created.

subsidiary (OneWorld only)

This field must reference an existing subsidiary listed at Company > Setup > Subsidiaries. Later, when you populate the sublist, each account you choose must be a valid account for this subsidiary.

This field cannot be updated through SOAP web services after the statistical journal entry record has been created. You can update this field through the user interface. To do this, delete the lines from the sublist, select a new subsidiary, add new lines, and then save the modified record.

Note:

With the 2015.2 and later WSDLs, you can also interact with the Memo body field. By contrast, the Memo field from the Lines sublist is available in all supported WSDLs.

Each sublist line must include values for the fields described in the following table.

Field	Description
account	This field must reference an existing statistical account listed at Lists > Accounting > Accounts. The account you choose must be valid for the subsidiary body field value, and it must use the same unit of measure specified in the unitsType body field.
debit	This field takes a double value that represents the adjustment you want to make to the account. Though the field is called debit, entering a positive amount increases the value of the account. Entering a negative amount decreases the value. This field is labeled “Amount” in the user interface.

Field

Description

account

This field must reference an existing statistical account listed at Lists > Accounting > Accounts. The account you choose must be valid for the subsidiary body field value, and it must use the same unit of measure specified in the unitsType body field.

debit

This field takes a double value that represents the adjustment you want to make to the account. Though the field is called debit, entering a positive amount increases the value of the account. Entering a negative amount decreases the value.

This field is labeled “Amount” in the user interface.

Note:

The unitLabel field is read-only. It is populated automatically when you set the unitsType field. (The unitlabel value is the unitstype’s base unit value. This value is defined in the corresponding unit of measure record.)

Field Definitions

For more details on body and sublist fields, see the SOAP Schema Browser’s statistical journal entry reference page. The SOAP Schema Browser includes definitions for all body fields, sublist fields, search filters, and search joins available to this record.

Note:

For information on using the SOAP Schema Browser, see SOAP Schema Browser.

Usage Notes

The maximum number of lines per statistical journal entry is 1000 when using synchronous SOAP web services processing. With asynchronous SOAP web services processing, the limit is 10,000 lines. If your import includes transactions with more than 1,000 lines, CSV import can also serve as an alternative. For transactions submitted through CSV import, the limit is 10,000 lines per transaction.

Field Definitions

Usage Notes

Related Topics