AssetDisposalParameters::findPostingAccount Method
Finds the asset disposal parameters.
Syntax
server public static AssetDisposalParameters findPostingAccount(
AssetSoldScrap _soldScrap,
AssetPostingProfile _postingProfile,
AssetBookId _bookId,
AssetPostValue _postValue,
AssetId _assetId,
AssetGroupId _assetGroupId,
AssetPostType _postType)
Run On
Server
Parameters
- _soldScrap
Type: AssetSoldScrap Enumeration
The type of disposal to find disposal parameters.
- _postingProfile
Type: AssetPostingProfile Extended Data Type
The posting profile to find disposal parameter.
- _bookId
Type: AssetBookId Extended Data Type
The asset book ID to find disposal parameters.
- _postValue
Type: AssetPostValue Enumeration
The asset post value to find disposal parameters.
- _assetId
Type: AssetId Extended Data Type
The asset ID to find disposal parameters.
- _assetGroupId
Type: AssetGroupId Extended Data Type
The asset group ID to find disposal parameters.
- _postType
Type: AssetPostType Enumeration
The asset post type to find disposal parameters.
Return Value
Type: AssetDisposalParameters Table
The asset disposal parameters.
Exceptions
Exception | Condition |
---|---|
Error | The asset disposal parameters table does not contain an applicable record. |
Remarks
The disposal parameters that most specifically match the passed in parameters are returned. The order of precedence for matching disposal parameters is to first look at the relationship specified and then the Asset Post Type. For example, a record that specifies a relation to the fixed asset group instead of no relation would be chosen because it is more specific. If there is another record that has a relation to asset ID instead of the fixed asset group it would be returned because it is even more specific. Finally, if there are two records that both have the same level of relationship, whether it is all, group, or table, but one has a more specific asset post type specified (For example negative, instead of all) it would be returned since it is the more specific record.