Generated DataSource for Special Ledger 

Technical name:      3FI_SL_XX_TT (Totals Table)

3FI_SL_XX_SI    (Single Item)

The technical name corresponds to the naming convention shown above, with XX replaced by the name of the ledger.

Use

The DataSource delivers transaction data from a customer-defined FI-SL ledger on a totals record or line item level. The DataSource can provide actual and plan data at totals record level and actual data at line item level.

Prerequisite

In your source system, you have assigned the DataSource to the totals records or line items of a ledger.

You carry out this assignment in Business Information Warehouse Customizing (SIBW).

Activities

To access Business Information Warehouse Customizing, call up the BW Administrator Workbench and choose: Modeling ® Source System Tree. Select the source system and choose Customizing for R/3 Extractors by carrying out a right mouse-click.

Choose Business Information Warehouse ®  Settings for Application-Specific DataSources ® Financials – Special Purpose Ledgers.

When you call up the transaction for extract structure or DataSource maintenance for the first time, a dialog box appears in which you are advised to directly convert all existing table entries.

Confirm the process with Yes and proceed as follows:

Generate Extract Structure for FI-SL Tables (Transaction BW01)

       1.      Use F4 help to choose the required totals table.

       2.      Flag whether you want extract structures to be generated for totals records and/or line items.

       3.      Choose Execute.

       4.      Result: You have generated the extract structure(s).

The extract structures contain the name of the totals table:

¡        Totals record extract structure: T in the totals table is replaced by B

¡        Line item extract structure: T in the totals table is replaced by W

Table group GLFUNC:

§         Totals table: GLFUNCT

§         Totals table extract structure; GLFUNCB

§         Line item extract structure: GLFUNCW

Assign DataSource to a Ledger (Transaction BW03)

...

       1.      After starting the transaction, you see a list of all selectable ledgers for which you can generate or maintain DataSources for totals records and/or line items.

If a required ledger does not appear, you might not have generated an extract structure for the corresponding table. In this case, execute transaction BW01.

The list contains the following information (columns from left to right)

·         Ledger

·         Description of the ledger

·         Table (totals table corresponding to the ledger)

·         Totals record DataSource

·         Delta-compatibility of the totals record DataSource (from Release 4.70)

·         Status of the totals record DataSource

·         Line item DataSource

·         Status of the line item DataSource

The status display in the column to the right of the field shows the current status of each DataSource.

       2.      Choose a DataSource by placing the cursor in the corresponding row for the ledger and column for the totals records or line items and carrying out a double-click.

Depending on your choice, the system now displays either the Totals record DataSource or Assign Line Item DataSource dialog box.

       3.      Enter the corresponding data.
When you create a new DataSource, the system proposes a name according to the following naming convention:

¡        Total record DataSources: 3FI_SL_xx_TT

¡        Line item DataSources: 3FI_SL_xx_SI (“xx“ stands for the ledger in question)

You can change the proposed name (though the 3 at the beginning cannot be changed). However, you are strongly advised to retain the naming convention from the proposal.

For the totals record DataSource, the option Activate Delta Updating is only displayed from Release SAP R/3 470. Delta updating is mandatory for line item DataSources. To display these, the flag Activate Delta Updating has to be activated in the dialog box.

       4.      Choose Continue.
The DataSource: Edit Customer Version screen appears. Here, you can exclude individual fields in the ledger from selection or transfer to the BW.

       5.      Configure the DataSource and save your settings.

       6.      Result: You have generated and can now use a DataSource for data extraction for your FI-SL ledger.

 

Characteristics

In this overview, only those characteristics that are always part of the DataSource are listed. Depending on the definition of the FI-SL tables, further characteristics can be added. As a rule, appropriate InfoObjects are proposed when defining the DataSource for the assignment of these characteristics. Under certain circumstances, however, new InfoObjects must be created for certain fields of the totals or line item table, particularly where customer-defined fields (beginning with ZZ...) are concerned.

InfoObject	Description	Data Element	Extrakt structure	Source
0COMPANY Only for global ledgers	Company	RCOMP Data element RCOMP_D from Release 4.0A	RCOMP	<Table>.RCOMP <Table> gives the FI-SL totals table, e.g. GLFUNCT
0COMP_CODE Optional for global ledgers	Company Code	BUKRS or OBUKR	BUKRS, OBUKR, ROBUKRS or RBUKRS	<Table>.BUKRS, <Table>.OBUKR, <Table>.ROBUKRS or <Table>.RBUKRS
0CHRT_ACC Chart of accounts and fiscal year variants cannot be used as selection criteria for data packages	Chart of Accounts	KTOPL	CHARTACCT	Master data of the ledger and organizational unit
0CURTYPE	Currency Type	RSCURTYPE	CURTYPE	Ledger master data
0VALUATION	Valuation View	VALUTYP	VALUTYP	Ledger master data
0VERSION This is the version managed in FI-SL. There is no transformation of the version in the extractor	Version	COVERSION	RVERS	<Table>.RVERS
0VTYPE The characteristic record type managed in FI-SL is built onto the InfoObject value type. The record types 0 and 2 are converted to value type 10, Record type 0 = Actual Record type 2 = Actual assessment Record types 1 and 3 are converted to value type 20, Record type 1 = Plan Record type 3 = Plan assessment	Reporting value type	RSVTYPE	VALUETYPE	<Table>.RRCTY

Time Characteristics

InfoObject	Description	Data Element	Extrakt structure	Source
0FISCPER	Fiscal year/period	RSFISCPER	FISCPER	<Table>.RYEAR and <Table>.RPMAX
0FISCVARNT	Fiscal year variant	RSFISCVAR	FISCVAR	Master data of the ledger and organizational unit
	Time stamp		TIMESTAMP	<Table>.CPUDT and <Table>.CPUTM

Units

InfoObject	Description	Data Element	Extrakt structure	Source
0CURRENCY	Currency unit	RSCURRENCY	CURRUNIT	<Table>.RTCUR or master data of the ledger and organizational unit
0UNIT	Unit of measure	ROUNIT	QUANUNIT	<Table>.RUNIT
0DOC_CURR	Document currency (Always corresponds to the transaction currency unit)	WAERK	RTCUR	<Table>.RTCUR

Key Figures

InfoObject	Description	Data Element	Extrakt structure	Source
0BALANCE	Accumulated balance	RR_KUMSL	BALANCE (this field is only available to the totals record extractor). If BALANCE is part of a transfer structure, the source fields are read through and the cumulative balance is calculated in the extractor during full upload. This generally means that considerably more records and read and transferred than would be the case without BALANCE. With BALANCE, periods without data transfers are also transferred.	<Table>.xSLnn and <Table>.xSLVT The source field from which the data is taken depends on the ledger master data, the characteristics of the InfoObject OCURTYPE and the posting period. Here, x stands for T, H, K or, from Release 4.5A in the flexible general ledger, also for O. The suffix nn portrays a two-digit offset, which, together with the key field <Table>.RPMAX, describes the posting period. (Generally, the posting period = RPMAX + nn-16). The source field <Table>.xSLVT contains the balance carried forward.
0CREDIT	Total credit postings for the posting period	RR_UMHAB	CREDIT	<Table>.xSLnn
0DEBIT	Total debit postings for the posting period	RR_UMSOLL	DEBIT	<Table>.xSLnn
0QUANTITY	Quantity	SMEGR	QUANTITY	<Table>.MSLnn
0SALES	Sales for the posting period (debit and credit)	RR_SALES	TURNOVER	<Table>.xSLnn

 

Result

FI-SL totals record DataSources (naming convention: 3FI_SL_xx_TT)

If the transfer structure in the OLAP system does not use a key field from the extract structure, the DataSource supplies the corresponding aggregated datasets:

The FI-SL totals record DataSoucr wotks in full upload mode and – from R/3 4.70 – also in delta mode.

Delta Compatibility

The generated DataSource 3FI_SL_xx_TT supports the full upload mode and – with the following restrictions – delta uploads.

·        The R/3 release must be 4.7 or higher. For R/3 releases from 4.0B to 4.6C, note 328197 must be installed.

·        The delta method can only be used for actual data. In an InfoPackage with Delta upload, enter the selection for actual data (0VTYPE = 010). Plan data can be transferred using a different InfoPackage in full upload.

·        The BALANCE field in the transfer structure is not supplied with data during Delta upload. To get the inventory for balance sheet account, 0BALANCE can be filled in BW in den updating rules.

·        During currency translations in FI, line item updating must be active.

·        Deletion transactions are not connected to the Delta method.

                            a.      Rollup

                            b.      Delete transaction data (TA GCDE)                                      

This means:                                                         

These transactions cannot be used if a delta method is initialized for the same selections, as the deletion is not passed on for the BW.                        

If you absolutely must use one of the transactions or do so accidentally, the initial and delta requests in the BW are deleted from the InfoCubes, and the Delta method is restarted with an initial upload.

The Delta method is based on Delta queue technology. If a Delta method has been initialized, during updating, the relevant data is posted to a separate table, the Delta queue.
You can see the content of the Delta queue by choosing transaction RSA7 in the source system.                                 

While the initial upload is running, you cannot post data. You have to ensure this yourself – the system does not carry out checks.                                                               

If the Delta method has been initialized for a source system, a Delta upload must be scheduled regularly so that the Deltaqueue will not overflow. If you want to stop the Delta method, you should also delete initialization.

FI-SL line item DataSources (naming convention: 3FI_SL_xx_SI)

If the transfer structure in the OLAP system does not use the following key fields, the DataSource supplies the corresponding aggregated datasets:

• DOCNR
• REFDOCNR
• CPUTM
• TIMESTAMP

The FI-SL line item DataSource works in full and Delta upload mode. For delta mode, the timestamp procedure is used. The TIMSTAMP field is used for this. The delta upload works with a security interval on an hour basis, meaning that posted line items can be loaded into the BW after one hour.

To optimize performance of data procurement when accessing the line item DataSource in the OLTP, you should create an extra secondary index for each line item table that you want to access. This should contain the following fields:

·         RCLNT

·         RLDNR

·         CPUDT

·         CPUTM

For R/3 releases 4.0B and 4.5B, install note 580273.

Constraints

·        The extract structure does not contain the BALANCE field. To get the inventory for balance sheet account, 0BALANCE can be filled in BW in den updating rules. For further information, see note 577644.

·        For the balance carryforward, no line items are posted. For this reason, DataSource 3FI_SL_xx_SI does not provide values for the balance carryforward.

Using a further InfoPackage for InfoSource 3FI_SL_xx_TT, carry over the exact balance carryforward from the totals table. (Restrict the period to = 0)