Export Transaction Data to a File Stored in File Service

You can define a Data Manager package to export transaction data from an application into a file stored on the File Service using the /CPMB/EXPORT_TD_TO_FILE process chain.

Activities

Create a Data Manager package by using the corresponding process chains (see Package Usage).
Run the Data Manager package as follows:
1. Log onto the Planning and Consolidation Office module.
2. On the action pane, choose Manage data Run a package .
3. Choose the package created in step 1 and choose Run.
4. Select the measures.
5. Choose the transformation file.
6. Choose the destination file.
7. Choose Yes if other application data will be added, then choose Next.
  
  Note
  Other application information includes application set, application, user name, and time stamp.
  
  End of the note.
8. Select the dimension values.
9. Choose one of the following options:
  - Run now
  - Schedule
  - Run now & schedule
10. Choose Finish.

You can change the default package instructions (see Modifying the Dynamic Script of a Package).

Dynamic script task parameters

Task	Parameter	Default Value	Description
/CPMB/APPL_TD_SOURCE	DIMENSIONVALUE		Dimension values
/CPMB/APPL_TD_SOURCE	MEASURES		Measures types
/CPMB/APPL_TD_SOURCE	SELECTION		Scope/Range
/CPMB/APPL_TD_SOURCE	SPACKAGE_SIZE	40.000	Package size
/CPMB/EXPORT_TD_CONVERT	SPACKAGE_SIZE	40.000	Package size
/CPMB/EXPORT_TD_CONVERT	TRANSFORMATIONFILEPATH		Transformation file
/CPMB/TD_FILE_TARGET	ADDITIONALINFO		Additional information that is passed to the export file: 1 = YES 0 = NO
/CPMB/TD_FILE_TARGET	FULLFILENAME		File name and path
/CPMB/TD_FILE_TARGET	SPACKAGE_SIZE	40.000	Package size

Example Example

Instructions to pass the parameters as constants: In this example, you would like to hardcode the parameters for the end user to export the data of the Planning application into the file MyExampleExportFile.csv. It should include the YTD and Periodic measures for the entity dimension value A1000 only. The additional information shall be exported as well.

The example instructions might look like this:

INFO(%DIMVALUE%,E=24)

INFO(%TEMPNO1%,%INCREASENO%)

INFO(%TEMPNO2%,%INCREASENO%)

INFO(%ADDITIONINFO%,1)

INFO(%FILE%,\ROOT\WEBFOLDERS\APSHELL_HOERISCHM\PLANNING\DATAMANAGER\DATAFILES\MyExampleExportFile.csv)

INFO(%TRANSFORMATION%,\ROOT\WEBFOLDERS\APSHELL_HOERISCHM\PLANNING\DATAMANAGER\TRANSFORMATIONFILES\EXAMPLES\TRANSFORMATIONFILE.XLS)

INFO(%MEASURES%,YTD,PERIODIC)

INFO(%SELECTION%,\ROOT\APSHELL_HOERISCHM\PLANNING\PrivatePublications\I810742\TempFiles\FROM.TMP@@@SAVE@@@@@@EXPAND@@@|DIMENSION:ENTITY|A1000|DIMENSION:CATEGORY||DIMENSION:TIME||)

TASK(/CPMB/APPL_TD_SOURCE,SELECTION,%SELECTION%)

TASK(/CPMB/APPL_TD_SOURCE,DIMENSIONVALUE,%DIMVALUE%)

TASK(/CPMB/APPL_TD_SOURCE,MEASURES,%MEASURES%)

TASK(/CPMB/APPL_TD_SOURCE,OUTPUTNO,%TEMPNO1%)

TASK(/CPMB/ EXPORT_TD_CONVERT,SPACKAE_SIZE,25000

TASK(/CPMB/EXPORT_TD_CONVERT,INPUTNO,%TEMPNO1%)

TASK(/CPMB/EXPORT_TD_CONVERT,TRANSFORMATIONFILEPATH,%TRANSFORMATION%)

TASK(/CPMB/EXPORT_TD_CONVERT,SUSER,%USER%)

TASK(/CPMB/EXPORT_TD_CONVERT,SAPPSET,%APPSET%)

TASK(/CPMB/EXPORT_TD_CONVERT,SAPP,%APP%)

TASK(/CPMB/EXPORT_TD_CONVERT,OUTPUTNO,%TEMPNO2%)

TASK(/CPMB/TD_FILE_TARGET,INPUTNO,%TEMPNO2%)

TASK(/CPMB/TD_FILE_TARGET,FULLFILENAME,%FILE%)

TASK(/CPMB/TD_FILE_TARGET,ADDITIONALINFO,%ADDITIONINFO%)

TASK(/CPMB/TD_FILE_TARGET,SPACKAGE_SIZE,25000)

A selection including filters can be set using the following:

INFO(%SELECTION%, //APSHELL_DAVY75_MIT/PLANNING/PrivatePublications/I045795/TempFiles/FROM.TMP@@@SAVE@@@@@@EXPAND@@@|DIMENSION:CATEGORY|[FILTER: FILTER_NAME]|DIMENSION:ENTITY||DIMENSION:P_ACCT||DIMENSION:P_ACTIVITY||DIMENSION:P_DATASRC||DIMENSION:RPTCURRENCY||DIMENSION:TIME||]

End of the example.

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.