1/5/2016 6:27:11 PM

Compatibility views BSID, BSAD, BSIK, BSAK, BSIS, and BSAS to determine FI line items. Finance, the partially redundant tables BSID, BSAD, BSIK, BSAK, BSIS, and BSAS were replaced with views of the same name. This ensures that all programs that execute read accesses on BSID, BSAD, BSIK, BSAK, BSIS, and BSAS continue to work without any loss of function.


In addition, the views contain a UNION ALL with the relevant BCK table (for example, BSAD_BCK) for reading partially archived documents. In the case of BSID and BSIK, the UNION ALL is required for technical reasons only (so that the views in the ABAP Dictionary obtain the correct data elements).


Tips for using the compatibility views

In most cases, read accesses from the compatibility views can remain unchanged. If, however, the performance of your programs is worse than it was before the upgrade, note the following:

You can rewrite the SELECTs directly on BSEG or BKPF/BSEG. This is useful in the following cases:

In SAP_FIN 720, the UNION ALL consumes additional runtime for the views BSID and BSIK. A direct SELECT on the join BSEG/BKPF is more efficient.

You do not use archiving. Then, the UNION ALL with the BCK table is useless and consumes only runtime.

You require data from the tables BSID and BSAD (or BSIK/BSAK).

Avoid a large number of small SELECTs. Preferably, all data should be read with a single access. To prevent a memory overflow in the case of large datasets, you can use the cursor technique (OPEN CURSOR ... FOR SELECT ...).

If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.


COMMENTS