Entries
Use this function to inquire the details of entry lines matching the entered criteria and to access accounting entries.
You can also jump to this function from the various balance inquiry screens.
Prerequisites
Refer to documentation Implementation
Screen management
Header
The inquiry is performed on a screen. Enter in the header:
- the company and site concerned,
- the ledger type,
- the date range for the inquiry.
Once the criteria are entered, click Search to launch the inquiry. Click Next and Return to browse through the data pages.
Using the Actions icon available on lines, you are provided direct access to:
- the accounting entry (for all entry types); access to this function is granted in view but also creation and modification modes,
- the invoice (for the Invoice and Credit memo entry types),
- the open items (for the Invoice and Credit memo entry types).
Selection
Company (field CPY) |
This field is used to specify the code for a company, group of companies or group of sites. |
Site (field FCY) |
The site code to be entered in this field is optional if a company code or a group code has already been selected. |
Ledger type (field LEDTYP) |
This field is used to specify the postings linked to the chosen ledger. |
Ledger currency (field CURLED) |
The specified ledger currency depends on the type of ledger selected. |
Display
Chart of accounts (field COA) |
This field reminds the chart of accounts linked to the company (or to the group of companies or the group of sites) and to the selected ledger type. |
Start date (field DATDEB) |
This field is used to enter a start date relating to the posting inquiry. |
End date (field DATFIN) |
This field is used to enter an end date relating to the posting inquiry. |
Tab Document
The listed fields are displayed only for inquiry.
Grid Details
Date (field ACCDAT) |
This date represents the accounting date of the original transaction. |
Type (field TYP) |
This field specifies the document type used to enter a journal. |
Document no. (field NUM) |
This field indicates the journal number. |
Debit (field DEBIT) |
This field reminds the amount in transaction currency. |
Ledger debit (field DEBLED) |
This field specifies the amount in ledger keeping currency. |
Credit (field CREDIT) |
Ledger credit (field CDTLED) |
Line description (field DES) |
Account (field ACC) |
BP (field BPR) |
Due date (field DUDDAT) |
Open item payment due date. If the MAXPD - Maximum period (companies) activity code is activated, a blocking message is displayed if the last due date is greater than the period specified, depending on the case, at the level of the following parameters or of the Contractual period possibly specified at the BP level.
|
Value (field VALDAT) |
Co. (field CPY) |
Site (field FCYLIN) |
Ctrl. (field SAC) |
Match letter (field MTC) |
Matching date (field MTCDAT) |
Maximum date (field MTCDATMAX) |
Status (field STA) |
Journal (field JOU) |
Reference (field REF) |
Curr. (field CUR) |
Offset (field OFFACC) |
Partner (field CSLCOD) |
This field is available depending on the inquiry screen setup selected in the Inquiry screens function GESGTC. This field is only available if the CSL - Consolidation activity code is active at the folder level. This is a display-only field that is populated according to the following: The value can default from the setup of the corresponding Journal entry transaction (GESGDE). There is no default value for this field when a journal entry is created from an automatic journal entry or manually. However, you can define a default value for this field when you create an automatic journal entry using the Automatic journal variables function (GESGVG). For example, on a sales invoice, to create a default value for the partner field on duty free and VAT lines, use the syntax [ F: SIH ] BPR. The automatic journal field is then populated with the partner code charged on TTC line of the sales invoice. The field can also default to the partner for the Extraction for Consolidation (BALCONSO) if the option Free criteria is selected. |
Flow (field CSLFLO) |
Flow code coming from the account if the flow code management has been chosen for the account. Flow initialization: The initialization rule only applies to accounts with Optional or Mandatory flow management selected and only for the first ledger defined in the journal entry transaction whose consolidation management is selected. When creating or posting a journal entry, the journal entry line flow code defaults as follows: If a flow code is parameterized on the journal, it defaults to that value. If there is no flow code on the journal, the flow code defaults to the value defined on the account. The flow depends of the direction on the journal entry line.
Note: When the journal entry transaction has several ledgers with consolidation management selected, the flow initialized on the first ledger is propagated to the other consolidated ledgers. If for any reason no flow has been initialized on the first ledger but is mandatory on another ledger, you receive a blocking error message that flow management is mandatory for the current account. |
Partner (field CSLBPR) |
You can only enter a Business partner with one of the following characteristics: Customer, Supplier, or Miscellaneous BP. The Partner is the partner of original record if an account class is set to Yes, and it is empty if the account class is set to No. For a profit and loss account (set up in the chart of accounts line 11), there is no partner regardless of the Partner management setup.
Partner initialization: The initialization rule only applies to accounts with Optional or Mandatory Partner management selected and only for the first ledger defined in the journal entry transaction with consolidation management selected. For control accounts
If no Business Partner is defined at the journal entry line level setup, the partner defaults to the CSLBPRDEF – Default partner (CPT chapter, CSL group) parameter value. If this parameter is defined, there is no default partner value. For General accounts
If the Entry partner check box is not selected for the general account defined at the journal entry line level setup, the partner defaults to the CSLBPRDEF – Default partner parameter value. If this parameter is not defined, there is no default partner value. If no control account line has been found, the partner defaults to the CSLBPRDEF – Default partner parameter value. If this parameter is not defined, there is no default partner value. Limit: If the journal entry is posted with several control account lines, the partner defaults from the first control account line. The partner is the same for all the general account lines where the Entry partner check box is selected. Note: When the journal entry transaction has several ledgers with consolidation management, the partner initialized on the first ledger is propagated to the other consolidated ledgers. If for any reason no partner can been initialized on the first ledger but is mandatory on another ledger, a blocking message appears notifying you that partner management is mandatory. |
Distribution (field DSP) |
field CCE1 |
Amount in currency (field AMTCUR) |
Amount expressed in the selected transaction currency. |
Ledger amount (field AMTLED) |
This field indicates the amount in ledger currency. |
Declared tax (field AMTVAT) |
Quantity (field QTY) |
It is the allocated quantity expressed in UOM unit. |
Mark (field CHK) |
Statistic 1 (field STT1) |
Tax (field TAX) |
Unit (field UOM) |
Entry date (field ENTDAT) |
Module (field ORIMOD) |
Source (field ORIGIN) |
Source transaction (field ORICOD) |
Source document (field BPRVCR) |
Document date (field BPRDATVCR) |
Transaction (field DACDIA) |
Multiplying rate (field MLTRAT) |
Dividing rate (field DIVRAT) |
Reminder (field FLGFUP) |
Pay approval (field FLGPAZ) |
Created (field CREDAT) |
Creation author (field CREUSR) |
Change date (field UPDDAT) |
Change author (field UPDUSR) |
Reconciliation date (field CHKDAT) |
Journal site (field FCY) |
Category (field CAT) |
Header description (field DESVCR) |
Interbank code (field BANCIB) |
Chronological number (field CHRNUM) |
Final number (field FNLPSTNUMW) |
Final date (field FNLPSTDAT) |
Project (field PJTLIN) |
Cost type (field PCCCOD) |
Basic Product Management |
The following actions can be available depending on the context. They are used to directly access the base object:
|
Open Items |
Depending on the context, this function is used to jump to the basic object:
|
Analytical allocation |
Use this action to go to the analytical distribution details, if the line is distributed analytically. |
Transactions by Date |
Use this action, available for entries from the stocks management module, to get an upstream access to the inquiry of stock movements. |
WIP Cost Inquiry |
Use this action, available for entries from the Manufacturing module, to get an upstream access to the WIP cost inquiry. |
Specific Buttons
Criteria
Click Criteria to refine the inquiry parameters. Selection
Display
|