Kontakt

Ansicht
Dokumentation

J_1GCL000 - Customer Ledger

J_1GCL000 - Customer Ledger

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Description

Customer Ledger report, shows customers movements according to reconciliation accounts.

Selection

The following selections can be used (those w/ obvious meaning are not listed):

  • Posting dates range:
    For this range the movements will be shown analytically. The dates before this range and within the same fiscal year are considered previous dates.
  • Show previous year balance:
    Show balance carry forward from previous year.
  • Show previous dates balance:
    Show balance from previous dates.
  • Print not moved accounts:
    Print customers without movements.
  • Customers not moved:
    The customers to be shown even without movements. Must be a subset of customers selected.
  • Print one time customer name:
    Print names of one time account customers.
  • Show transaction currency:
    Display information also on transaction currency.
  • Sums on reference documents:
    Show sums for documents within the same posting date, posting key, reference doc.
  • Show only sums on refer. doc.:
    Display only the sums and not analytically ( makes sense if 'Sums on reference documents' has been selected).
  • Print user selections:
    Prints them on the last page.

Output

Apart from the movements, an error log is printed in case of errors encountered.

Requirements

Note: The program (when previous date sections are used), determines the GL account based on customer's master data and not on transactions, except an SPL is used. Alternative accounts are also found based on master and not transaction data.

Performance issues
For best performance create a non-unique index on tables BSID and BSAD, for fields: MANDT - BUKRS - KUNNR - BUDAT.

Standard Ledger & Extended Ledger (SPL)
The program reads from table KNC1 ( Standard Ledger ) for "normal" transcation period sums. If there is a need to read period sums for special GL transactions, these must be read from a suitable extended ledger (or special purpose ledger - SPL).

  • A suitable SPL must have a "key" (object table) comprising at least the following fields: Company code (RBUKRS) - GL Account (RACCT) - Account type (RZZKOART) - Vendor number (RZZLIFNR) - Customer number (RZZKUNNR) - Special GL Indicator (RZZUMSKZ).
  • There is no need for the SPL to store line items.
  • The SPL can also use another Fisal Year Variant, only if it coincides chronologically with the Company's FYV.
  • The SPL's summary table, must have at least all the fields of program's internal data type SPL_TYPE (see include J_1GSPLEDGER).
    If 2nd currency is used, the program assumes that it is stored in SPL's KSL field group.
    If such a ledger exists, it is also advisable to use it everytime, The reason being that when reading from KNC1 we determine the reconciliation account for the customer based on its master file, which can lead to errors if a customer has changed reconciliation account in the interim ( not advisable to do such anyways , but... ).





BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3576 Date: 20240531 Time: 233517     sap01-206 ( 50 ms )