Kontakt

Ansicht
Dokumentation

J_1UF_KNIGA_PRIDB_PROD - Purchase/sales ledger for the Ukraine

J_1UF_KNIGA_PRIDB_PROD - Purchase/sales ledger for the Ukraine

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Description

The program J_1UF_KNIGA_PRIDB_PROD generates a purchase/sales ledger for Ukraine as a list that contains all necessary information.

Company code parameters, document number, fiscal year, document type, posting date, tax group and VAT code are used for limiting the quantity of analyzed documents.

When the "Totals column adjustment" indicator is activated, performed adjustments are displayed not only in the adjustment column, but also inthe "Volume with VAT" column and other corresponding columns (in accordance with VAT classification).

The J_1UF_PUR_LEDGER structure is used for storing the purchase ledger data in the report. The J_1UF_SAL_LEDGER structure is used for storing the sales ledger data in the report.

The FILLHEADBOOK procedure of the ZJ1UFBOOK module is used for displaying a name of the department in the report. It returns two lines via parameters (up to 60 characters) displayed in the report header (when this report is displayed on the screen).

Example

An example of displaying the department name in the report is shown below
REPORT zj1ufbook.
FORM fillheadbook CHANGING p_headline1 p_headline2.
p_headline1 = 'Name of'.
p_headline2 = 'department'.
ENDFORM.

In this reports version the bills of exchange data are not display.

Prerequisites

  1. Posting tax notes as separately financial documents. To ensure continuous number assignment and fast data processing, it is recommended to enter documents using a specific document type.
  2. To generate tax data in a document (in the BSET table), use tax codescorresponding to Ukrainian standard tax codes used in tax delivery notes
  3. The tax delivery note's number is defined in the document header, "Reference" field (BKPF-XBLNR).
  4. A reference to the original document (invoice or advance payment in the system) is entered in the "DocHeadText" (BKPF-BKTXT) field, or in the "Assignment" field of the tax account item in the document (BSEG-ZUONR), depending on the way these fields are used for other purposes. The report uses the reference document number to define a vendor and defines the name of this vendor (LFA1-NAME1 field) and VAT registration number (LFA1-STCD1) from the vendor master record. A single vendor item is available in the invoice/advance payment document. Supporting vendors has been carried out - via one-time account.

It is possible to enter a document number with/without a fiscal year. Only particular formats of entering numbers and fiscal years for the reference financial document are supported:

  1. If a four-digit fiscal year is entered, it must be separated from the document number by any character (no digits, including space);
  2. If the document number is entered without specifying the fiscal year, searching for the reference document is carried out using the fiscal year specified in the tax note.
  • When ledgers are created, tax codes for posting a tax note are assigned to corresponding columns of the purchase/sales ledger (OBCH and OBCG transactions). To define a tax and a taxable base, the ledger column number is entered into corresponding tables. The report processes only those document items in which the VAT code is displayed in tables.

    • The following tax group versions are used:

    1. PUR, Purchase ledger
    2. SAL, Sales ledger
  • To receive payment data automatically, you must perform clearing of the invoice document with corresponding payment documents. To do this, activate the "Financial transaction" indicator (in accounts master record 50 and 51).

    • To distinguish between cash payment transactions and payments from the bank clearing account to cash accounts, a keyword CASH (Extras Ð Keywords) has to be defined. Several keywords for different purposes are available for processing a balance sheet account.

    1. It is necessary to maintain address data for a company code or a tax group (taxable entity).
    2. The "VAT" field (KNA1-STKZU) in the customer master record is used for defining tax-dodgers (Sales ledger).

    Output

    The report is prepared by means of ABAP LIST VIEWER. Use its standard functions to get various displays of received data including calculations of subtotals. Displayed report type can be changed. In case of any alteration of the report representation, it is recommended to save its settings as a report variant.

    Example

    An example of posting to the system and subsequent creation of entries in the purchase/sales ledger is given below

    • Invoice (is not displayed in purchase ledger and tax return)
      31 Vendor P2 120,00
      40 05000000 Material stock P2 100,00
      40 64401000 TaxCreditW/oNote P2 20,00
      50 R1801999 Gross expenses (clearing) P2 100,00-
      40 R1800000 Gross expenses P2 100,00
    • Tax note (a separate document type)
    • VAT amount > 0
      40 TAXBASE0 Tax return amount S1 120,00
      50 TAXBASE0 Tax return amount D1 120,00-
      40 64102010 Input VAT S1 20,00
      50 64401000 TaxCreditW/oNote D1 20,00-

    Document items 3 and 4 are automatically generated on the basis of tax codes. Tax base is entered in the tax data of the document. Posting from the 644* account credit is performed with a tax code different from P2 (D1). The reason for this is that in this case the input tax code P2 generates not only tax items but also postings to accounts for gross expenses (R18* account).

    • VAT amount = 0
      40 TAXBASE0 Tax return amount S2 120,00
      50 TAXBASE0 Tax return amount D0 120,00-

    Tax codes D0 and S2 have the same settings as tax codes D1 and S1. However, a tax rate 0% has been assigned to them. Thus, in the tax file (from which tax data is retrieved) tax amount will equal 0.

    The correspondence between tax codes and certain columns of the purchase/sales ledger is set in the following tables: T007K for tax bases (Customizing transaction OBCG) and T007L for tax amounts (Customizing transaction OBCH).






    BAL Application Log Documentation   General Data in Customer Master  
    This documentation is copyright by SAP AG.

    Length: 6803 Date: 20240531 Time: 173729     sap01-206 ( 116 ms )