EditFiscalDates

Edit Fiscal Dates

Minor Business Rule

Object Name: B0000011

Parent DLL: CALLBSFN

Location: Client/Server

Language: C

Functional Description

Purpose
The purpose of this business function is to provide for the various edits required when adding or
changing a Date Pattern record in the Fiscal Date Patterns application (P0008).

Setup Notes and Prerequisites

Special Logic
This business function is specific to the Fiscal Date Patterns application (P0008).

Technical Specification
• Period 1 End Date must be greater than Fiscal Begin Date, Period 2 End Date must be greater than
Period 1 End Date, and so on.
• Begin Fiscal Date must be greater than period 14 of previous year, if set up for this date pattern.
• Period 14 must be less than the next year Begin Fiscal Date, if set up for this date pattern.
• If period end dates are the same, then all subsequent dates must be the same.
• If any period end date is left blank, all subsequent dates will be filled in from previous period
end date.
• Period End Date 1 can not be left blank.
•
Return Fiscal Year and Century, derived from Period 1 End Date.

Data Structure

D0000009 - Get Next Journal Entry Line Number

^

Parameter Name Data Item Data Type Req/Opt I/O/Both

szDocumentType DCT char NONE NONE

A user defined code (00/DT) that identifies the origin and purpose of the transaction.  PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P Accounts payable
documents R Accounts receivable documents T Time and Pay documents I Inventory documents O Purchase order documents S Sales order
documents

mnDocumentNumber 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.

szCompanyKey KCO char NONE NONE

A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher,
or journal entry. If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the
document company to retrieve the correct next number for that company. If two or more original documents have the same document number and
document type, you can use the document company to locate the desired document.

jdTransactionDate DGJ JDEDATE NONE NONE

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.

mnJournalEntryLineNumber JELN MATH_NUMERIC NONE NONE

A number that designates a line within a journal entry. The system uses this field to sequence the journal entry lines for inquiry purposes.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szDocumentType	DCT	char	NONE	NONE
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P Accounts payable documents R Accounts receivable documents T Time and Pay documents I Inventory documents O Purchase order documents S Sales order documents
mnDocumentNumber	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.
szCompanyKey	KCO	char	NONE	NONE
A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher, or journal entry. If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the document company to retrieve the correct next number for that company. If two or more original documents have the same document number and document type, you can use the document company to locate the desired document.
jdTransactionDate	DGJ	JDEDATE	NONE	NONE
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.
mnJournalEntryLineNumber	JELN	MATH_NUMERIC	NONE	NONE
A number that designates a line within a journal entry. The system uses this field to sequence the journal entry lines for inquiry purposes.