DraftChangeDeleteVoidNSF

Draft Change Delete Void NSF

Major Business Rule

Object Name: B03B0154

Parent DLL: CFIN

Location: Client/Server

Language: C

Functional Description

Purpose

This function does the void delete processing for drafts.

Setup Notes and Prerequisites

It is called by the B03B0019 Void NSF Receipt Function

Special Logic

Technical Specification






Parameters:


Data Item Data Structure DescriptionI/OReqNotes


PYIDmnPaymentIDIYPayment Id


DDSTcDraftStatusIYDraft Status


ICUmnBatchNumberIYBatch Number


ICUTszBatchTypeIYBatch Type


DICJjdDateBatchJulianIYBatch Date


COszCompanyIYCompany


DOCmnDraftNumberIYDraft Number


VREszVoidReasonCodeIYVoid Reason Code


VDGJszVoidDateForGLJulianIYVoid Date


EV01cVoid_NSF_V_NIYVoid Flag


BSTAcCurrentBatchStatusIYBatch Status


EV01cActionCodeIYAction Code C,D,N,V





Related Tables 





F03B11Customer Ledger File


F03B14A/R Check Detail File





Related Business Functions


 


B03B0146F03B14  Create F03B14 GL Entry


B03B0019Void/NSF Receipt





Processing 


 


Open Table F03B14


Select records for the payment id.


If action code passed in is C and draft status is 4 and the record is posted


 Create a reversing record


If action code passed in is C and the draft status is 4 and it is unposted


 Delete the draft record in the F03B14 file


 Delete the draft record in the F03B11 file


 


If action code passed in is D and draft status is 4 and the record is posted


 Create a reversing record


If action code passed in is D and the draft status is 4 and it is unposted


 Delete the draft record in the F03B14 file


 Delete the draft record in the F03B11 file











Close table F03B14

Data Structure

D03B0154 - Draft ChangeDeleteVoidNSF

Data Item Data Structure DescriptionI/OReqNotes
PYIDmnPaymentIDIYPayment Id
DDSTcDraftStatusIYDraft Status
ICUmnBatchNumberIYBatch Number
ICUTszBatchTypeIYBatch Type
DICJjdDateBatchJulianIYBatch Date
COszCompanyIYCompany
DOCmnDraftNumberIYDraft Number
VREszVoidReasonCodeIYVoid Reason Code
VDGJszVoidDateForGLJulianIYVoid Date
EV01cVoid_NSF_V_NIYVoid Flag
BSTAcCurrentBatchStatusIYBatch Status
EV01cActionCodeIYAction Code C,D,N,V

^

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnPaymentID	PYID	MATH_NUMERIC	NONE	NONE
A number that the system assigns from Next Numbers to identify and track payment records.
cDraftStatus	DDST	char	NONE	NONE
A code that the system assigns to draft records (F03B13 and F03B14) to indicate their progress during the collection process. Valid values are: 4 Accepted 3 Remitted - Cash or Discount 2 Remitted - Contingent 0 Collected
mnBatchNumber	ICU	MATH_NUMERIC	NONE	NONE
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.
szBatchType	ICUT	char	NONE	NONE
A code that specifies the system and type of transactions entered in a batch. The system assigns the value when you enter a transaction. Valid values are set up in user defined code table 98/IT. You cannot assign new values. All batch types are hard coded.
jdDateBatchJulian	DICJ	JDEDATE	NONE	NONE
The date of the batch. If you leave this field blank, the system date is used.
szCompany	CO	char	NONE	NONE
A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany transactions. Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000 for transaction entries.
mnDraftNumber	DOC	MATH_NUMERIC	NONE	NONE
A number that identifies the original document, such as a voucher, invoice, or journal entry. On entry forms, you can assign the document number or let the system assign it using the Next Numbers program (P0002). Matching document numbers (DOCM) identify related documents in the Accounts Receivable and Accounts Payable systems. Examples of original and matching documents are: Accounts Payable o Original document - voucher o Matching document - payment Accounts Receivable o Original document - invoice o Matching document - receipt Note: In the Accounts Receivable system, the following transactions simultaneously generate original and matching documents: deductions, unapplied receipts, chargebacks, and drafts.
szVoidReasonCode	VRE	char	NONE	NONE
A code that explains why a receipt was voided.
jdVoidDateForGLJulian	VDGJ	JDEDATE	NONE	NONE
The date that specifies the financial period to which the voided transaction is to be posted. Financial periods are set up in the Company Constants table (F0010).
cVoid_NSF_V_N	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cCurrentBatchStatus	BSTA	char	NONE	NONE
This field serves as a control mechanism within the Utility CIS Billing modules. The following values are verified prior to executing various jobs to ensure the functions are being performed in a proper sequence. The valid values are: blank Nothing has been performed. 0 Billing detail has been processed. 1 Bills have been printed. 2 A/R and G/L entries have been created. 3 A/R and G/L entries have been posted. 4 Billing detail has been posted to history. NOTE: Status codes are defined in User Defined Codes (System 19, Code BS).
cActionCode	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.

Related Functions

None

Related Tables

None