Source for PC Reference Data (e.g. Data on NGL)

PC_READTABLE

* from Allevo version 2.7.3 (extended to 3.4.23)

If the new general ledger is already used for profit center accounting, summary records are no longer saved in the table GPLCT but in FAGFLEXT.

Entry FAGFLEXT in column Value from activates access to this SAP table.

Note:

Reading statistical key figures using the new general ledger is not yet possible (the reading function might possibly switch back to GLPCT).

Since, depending on the system implementation, the currency fields of FAGFLEXT are not always filled, the currency type in the Allevo column definition must always be entered correctly. The following rules apply:

· T = transaction currency reads from the TSL fields,

· O = object currency reads from the HSL fields (local currency, referred to as “company code currency” in GLPCT),

· In all other cases (especially also with C = controlling area currency) the KSL fields are read (group currency which is referred to as “Profit Center local currency” in GLPCT).

An entry in column Value to can activate further functions; depending on the table that data are read from. So far, the following is realized:

· Entry “B“ activates reading via a company code in the new general ledger, irrespective of the current profit center (as with balance report, for details see below).

· Optionally: name of a database field that shall be used upon selection via a business transaction (see details in the following note).

Note:

The constant may also be used to access other tables within profit center accounting (e.g. also to read data from a customized table). However, these tables must use the same field names as in GLPCT for the relevant data records (such as profit center, business year, record type, transaction, credit-/debit indicator, partner profit center, value fields etc.). Amounts, however, are not read then. When using the PC integration (row definition P), column Value to has a very specific meaning:   · If a table field name is entered here, Allevo will select data per transaction using this field instead of the original database field (instead of field ACTIV of GLPCT). The transaction entered in Allevo may in this case acquire a completely different meaning. Example: instead of a transaction, the ID of an order type is included via the Allevo column definition and selection is performed via the customized field ZZAUART. · If different row definitions are available (P1, P2…) with different IDs during transaction, a very specific display is possible in Excel (with one row per transaction ID).

* new from version 3.2

If posting to the new general ledger is activated via PC_NGLA_PLANNING, the constant does not necessarily need to be active here. Allevo will then by default use the table FAGLFLEXT for reading.

* new from version 3.4

If reading for the new general ledger is active (table FAGLEFLEXT), it is possible to read data for a balance report, i.e. output of values cumulated for the company code. A representative profit center or Allevo object assigned to the respective company code serves for starting.

Activate the balance report by entry B (= balance report) in Column Value to; at the same time, FAGLFLEXT must be entered for Value from. The constant PRE_SELECT considers both the table FAGLFLEXT as well as reading across the entire company code.

From Allevo 3.4.23, reading from table GLT0 for the classical ledger is supported as well: entry in column Value from is sufficient (constant PRE_SELECT should not be active in this case).