Show TOC

Procedure documentationImporting and Exporting Data Having Multiple Key Figures Locate this document in the navigation structure

 

You can import and export transactional data that consists of more than one key figure for the same source into the same Planning and Consolidation application. Use the *MVAL keyword in the mapping section of the transformation file (see Data Transformation Maintenance).

Syntax:

Dimension =*MVAL(keyfiguretype1|dim_mem1||keyfiguretype2|dim_mem2||keyfiguretype3|dim_mem3)

Prerequisites

The dimension must exist in the application.

The passed dimension members in dim_mem must be the noncalculated (CALC = N) members of the dimension.

The keyfiguretype must be the field name of the source data.

Procedure

  1. Access the Launch Page and log on to to the ApShell application set.

  2. Choose   eData   New transformation file  .

  3. Map the multiple key figures to the single key figure using a keyword in the mapping section of the transformation file.

  4. Save the transformation file.

  5. Run the package and choose the transformation file.

Example

Example 1:

Source data:

Account, Entity, Data source, LC, GC, TC.

Cash, SalesItaly, Input, key1, key2, key3

Mapping command:

Account =*MVAL(LC|*STR(Cash_lc)||GC|*COL(1)+*STR(gc)||TC|*STR(Cash_tc))

Target data:

Account, Entity, Data source, keyfigure

Cash_lc, SalesItaly, Input, key1

Cash_gc, SalesItaly, Input, key2

Cash_tc, SalesItaly, Input, key3

Example 2:

Source data:

Account, Entity, Data source, LC, GC, TC.

Cash, SalesItaly, Input, key1, key2, key3

Mapping command:

Keyfiguretype =*MVAL(LC|*NEWCOL(LC)||GC|*STR(GC)||TC|*NEWCOL(TC))

Target data:

Account, Entity, Data source, Keyfiguretype, keyfigure

Cash, SalesItaly, Input, LC, key1

Cash, SalesItaly, Input, GC, key2

Cash, SalesItaly, Input, TC, key3

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or by its gross negligence.