NettingEntryForAR

Netting Entry for Accounts Receivable

Minor Business Rule

Object Name: B03B0240

Parent DLL: CFIN

Location: Client/Server

Language: C

Data Structure

D03B0240 - Netting Entry for Accounts Receivable

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szNetEntryCacheName	CANAME	char	REQ	INPUT
A name that uniquely identifies a cache.
mnResultBatchNumber	ICU	MATH_NUMERIC	REQ	INPUT
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either assign a batch number or let the system assign it using the Next Numbers program.
mnTransferBatchNumber	ICU	MATH_NUMERIC	REQ	INPUT
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either assign a batch number or let the system assign it using the Next Numbers program.
jdNetBatchDate	DICJ	JDEDATE	REQ	INPUT
The date of the batch. If you leave this field blank, the system date is used.
jdResultDocDueDate	DDNJ	JDEDATE	OPT	INPUT
In the Accounts Receivable system, the date that the invoice must be paid to receive the discount. The system calculates the discount due date based on the payment term. If the payment term does not specify a discount, the system completes this field with the net due date. In the Accounts Payable system, the date that the voucher is due.
jdNetGLDate	DGJ	JDEDATE	REQ	INPUT
A date that identifies the financial period to which the transaction will be posted. You define financial periods for a date pattern code that you assign to the company record. The system compares the date that you enter on the transaction to the fiscal date pattern assigned to the company to retrieve the appropriate fiscal period number, as well as to perform date validations.
mnNetTransactionID	NETTCID	MATH_NUMERIC	REQ	INPUT
A number that identifies a netting transaction. The system assigns it using the Next Numbers program (P0002). A netting transaction could contain one or more netting documents.
mnCacheRecordCount	MATH06	MATH_NUMERIC	REQ	INPUT
Event point for Math Numeric.
cPayInstrumentProcessFlag	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.
cResultDocPayInstrument	PYIN	char	OPT	INPUT
A user defined code (00/PY) that determines the means by which a payment is issued to a supplier or received from the customer. Examples of payment instruments include check, electronic funds transfer, lockbox, and EDI.
szResultDocRemark	RMK	char	OPT	INPUT
A generic field that you use for a remark, description, name, or address.
cValidResultDocPayStatus	PST	char	REQ	INPUT
A user defined code (00/PS) that indicates the current payment status for a voucher or an invoice. Examples of codes include: A Approved for payment but not yet paid H Held pending approval P Paid Note: Some of the payment status codes are hard coded; the system assigns the code.
szResultDocTradeAcctGLOffset	APC	char	OPT	INPUT
A code that determines the liability account in Accounts Payable that will be the offset when you post vouchers. This code might be alphanumeric, or it might match the object account of the account number in the general ledger. Use offset codes such as TRAD or OTHR as the exception to the trade account. If you leave this field blank during voucher entry, the system uses the default value from the supplier master record. Examples include: Blank Trade Accounts Payable TRAD or 4110 Trade Accounts Payable OTHR or 4120 Other Accounts Payable
szClearAcctGLOffset	GLC	char	OPT	INPUT
A code that determines the trade account that the system uses as the offset when you post invoices or vouchers. The system concatenates the value that you enter to the AAI item RC (for Accounts Receivable) or PC (for Accounts Payable) to locate the trade account. For example, if you enter TRAD, the system searches for the AAI item RCTRAD (for receivables) or PCTRAD (for payables). You can assign up to four alphanumeric characters to represent the G/L offset or you can assign the three-character currency code (if you enter transactions in a multicurrency environment). You must, however, set up the corresponding AAI item for the system to use; otherwise, the system ignores the G/L offset and uses the account that is set up for PC or RC for the company specified. If you set up a default value in the G/L Offset field of the customer or supplier record, the system uses the value during transaction entry unless you override it. Note: Do not use code 9999. It is reserved for the post program and indicates that offsets should not be created.
cResultDocPayeeNoFlag	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.
szReceiptEntryVersion	VERS	char	REQ	INPUT
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.
szVoucherEntryMBFVersion	VERS	char	OPT	INPUT
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.
szJournalEntryMBFVersion	VERS	char	OPT	INPUT
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.

Related Functions

None

Related Tables

None