Mapping the Version and Transfer Price
Valuation
The values transferred to BW for the InfoObjects 0VERSION and 0VALUATION depend on the following parameters in R/3:
· Controlling area of the object (COSP-OBJNR, COSS-OBJNR)
· Version field of the records read (COSP-VERSN, COSS-VERSN)
· Settings for the transfer price valuations in R/3 Customizing
Extraction into BW is based on the delta version logic of R/3. That is, only records with complete amounts are transferred. For example, for a valuation that is updated in R/3 in a delta version, the amounts of the version belonging to the base valuation are added automatically.
Delta versions of activity-based costing are not supported.
Initializing the Extraction
ROMU_GET_VERSN_FOR_VALUATION or ROMU40_GET_VERSN_FOR_VALUATION:
If selection criteria were entered for 0VERSION and 0VALUATION (valuation), the extractor maps the version required for this valuation as well as the base version, and adds them to the selection criteria for 0VERSION.
(Module K_VERSN_VALUATION in ROMU_GET_VERSN_FOR_VALUATION or ROMU40_GET_VERSN_FOR_VALUATION).
If no selection criteria were entered for 0VERSION, all versions (and therefore all valuation versions) are always selected.
Processing of the Imported Totals Records/Line Items
ROMU_ENHANCE_VERSN_IN_DATA or ROMU40_ENHANCE_VERSN_IN_DATA:
The system determines whether the version of the imported record is an operational version or a delta version. If it is an operational version, the record is copied for all delta versions belonging to that operational version. The delta version is entered into the new, copied records. The new, copied records then run through the complete mapping logic of the extractor for all other fields as well.
ROMU_GET_VALUTYP_FROM_VERSN or ROMU40_GET_VALUTYP_FROM_VERSN:
For the version of the record read, the valuation in Customizing of the versions is determined and entered in 0VALUATION.
ROMU_RESET_CO_VERSN
or ROMU40_RESET_CO_VERSN:
For versions that do not belong to the basic valuation, the version is set to
000.