Import Master Data from an SAP BW InfoObject

You can define a Data Manager package to import master data (dimension members) from an SAP NetWeaver BW InfoObject for use in Planning and Consolidation using the process chain /CPMB/IMPORT_IOBJ_MASTER. This supports the loading of descriptions as well.

Note Note

Delta upload and packaging are not supported.

End of the note.

Activities

Create a Data Manager package using the /CPMB/IMPORT_IOBJ_MASTER process chains (see Package Usage).
Run the Data Manager package as follows:
1. Log on to 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. Enter the technical name of the SAP NetWeaver InfoObject.
  
  Note
  Expect a long runtime when choosing the Select Button for the first time.
  
  End of the note.
5. Set the selection to filter to filter the master data to be uploaded.
6. Set the write mode.
  use Overwrite mode for replacing the exiting master data with the new master data Update mode or Update mode for adding or changing the existing master data (see Write Mode Example).
7. Choose the format.
  The External Format calls the Output conversion routine of the infoobject. The Internal Format does not call the output conversion routine.
8. Choose Next.
9. If necessary, select a transformation file.
10. Choose the destination dimension.
11. Choose one of the following options:
  - Run now
  - Schedule
  - Run now & schedule
12. Choose Finish.

Note Note

When setting the selection, the default values are the following:

For the Attributes tab, the default value is all.
For the Hierarchy tab, the default is no selection for loading masterdata from hierarchy.
For text, the first language is checked by default.
For selecting attribute fields, all fields are checked by default.

The process chain /CPMB/IMPORT_IOBJ_HIER can be used to load master data hierarchies from an SAP NetWeaver BW InfoObject (see Import Hierarchies from an SAP BW InfoObject).

End of the note.

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/SPLIT_IOBJ_MD_TXT_DATA	SPACKAGE_SIZE	40.000	Package size
/CPMB/MERGE_IOBJ_MD_DATA	MASTERDATA-SELECTION		InfoObject values
/CPMB/MERGE_IOBJ_MD_DATA	SPACKAGE_SIZE	40.000	Package size
/CPMB/BPC_TXT_DATA_TARGET	DIMNAME		Dimension
/CPMB/BPC_TXT_DATA_TARGET	SPACKAGE_SIZE	40.000	Package size
/CPMB/BPC_MASTER_DATA_TARGET	DIMNAME		Dimension
/CPMB/BPC_MASTER_DATA_TARGET	SPACKAGE_SIZE	40.000	Package size
/CPMB/BPC_MASTER_DATA_TARGET	WRITEMODE	2	Write mode: 1 = Overwrite 0 = Update
/CPMB/BW_IOBJ_TEXT_SOURCE	INFOOBJECT		InfoObject
/CPMB/BW_IOBJ_TEXT_SOURCE	MASTERDATA_FORMAT		Conversion exit: 1 = No conversion 0 = Conversion executed
/CPMB/BW_IOBJ_TEXT_SOURCE	MASTERDATA_SELECTION		InfoObject values
/CPMB/BW_IOBJ_TEXT_SOURCE	SPACKAGE_SIZE	40.000	Package size
/CPMB/BW_IOBJ_MASTER_SOURCE	MASTERDATA_FORMAT		Conversion exit: 1 = No conversion 0 = Conversion executed
/CPMB/BW_IOBJ_MASTER_SOURCE	MASTERDATA_SELECTION		InfoObject values
/CPMB/BW_IOBJ_MASTER_SOURCE	SPACKAGE_SIZE	40.000	Package size
/CPMB/IOBJ_SOURCE_MD_CONVERT	CLEARDATA	0	Delete data before writing: 0 = NO 1= YES
/CPMB/IOBJ_SOURCE_MD_CONVERT	DIMNAME		Dimension name
/CPMB/IOBJ_SOURCE_MD_CONVERT	SPACKAGE_SIZE	40.000	Package size
/CPMB/IOBJ_SOURCE_MD_CONVERT	TRANSFORMATIONFILEPATH		Transformation file

The package size parameter can be set for all different tasks separately.

Example Example

PROMPT(MASTERSELECTION,%INFOOBJECT%,"%SELECTION%",Please select the infoobject and the selection,,)

PROMPT(RADIOBUTTON,%WRITEMODE%,"Write Mode",2,{"Overwrite","Update"},{"1","2"})

PROMPT(RADIOBUTTON,%FORMAT%,"Choose format.",1,{"Internal Format","External Format"},{"1","0"})

PROMPT(TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls) PROMPT(DIMENSIONNAME,%DIMNAME%,"Dimension name:",,,%DIMS%)

INFO(%TEMPNO1%,%INCREASENO%)

INFO(%TEMPNO2%,%INCREASENO%)

INFO(%TEMPNO3%,%INCREASENO%)

INFO(%TEMPNO4%,%INCREASENO%)

INFO(%TEMPNO5%,%INCREASENO%)

INFO(%TEMPNO6%,%INCREASENO%)

INFO(%TEMPNO7%,%INCREASENO%)

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

TASK(/CPMB/BW_IOBJ_MASTER_SOURCE,MASTERDATA_SELECTION,%SELECTION%)

TASK(/CPMB/BW_IOBJ_MASTER_SOURCE,INFOOBJECT,%INFOOBJECT%)

TASK(/CPMB/BW_IOBJ_MASTER_SOURCE,MASTERDATA_FORMAT,%FORMAT%)

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

TASK(/CPMB/BW_IOBJ_TEXT_SOURCE,MASTERDATA_SELECTION,%SELECTION%)

TASK(/CPMB/BW_IOBJ_TEXT_SOURCE,INFOOBJECT,%INFOOBJECT%)

TASK(/CPMB/BW_IOBJ_TEXT_SOURCE,MASTERDATA_FORMAT,%FORMAT%)

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

TASK(/CPMB/MERGE_IOBJ_MD_DATA,INPUTNO2,%TEMPNO2%)

TASK(/CPMB/MERGE_IOBJ_MD_DATA,MASTERDATA_SELECTION,%SELECTION%)

TASK(/CPMB/MERGE_IOBJ_MD_DATA,OUTPUTNO,%TEMPNO3%)

TASK(/CPMB/IOBJ_SOURCE_MD_CONVERT,FORMULA_FILE_NO,%TEMPNO7%)

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

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

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

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

TASK(/CPMB/IOBJ_SOURCE_MD_CONVERT,DIMNAME,%DIMNAME%)

TASK(/CPMB/IOBJ_SOURCE_MD_CONVERT,OUTPUTNO,%TEMPNO4%)

TASK(/CPMB/SPLIT_IOBJ_MD_TXT_DATA,INPUTNO,%TEMPNO4%)

TASK(/CPMB/SPLIT_IOBJ_MD_TXT_DATA,OUTPUTNO,%TEMPNO5%)

TASK(/CPMB/SPLIT_IOBJ_MD_TXT_DATA,OUTPUTNO2,%TEMPNO6%)

TASK(/CPMB/IOBJ_SOURCE_MD_CONVERT,INPUTNO,%TEMPNO3%)

TASK(/CPMB/BPC_MASTER_DATA_TARGET,INPUTNO,%TEMPNO5%)

TASK(/CPMB/BPC_MASTER_DATA_TARGET,DIMNAME,%DIMNAME%)

TASK(/CPMB/BPC_MASTER_DATA_TARGET,WRITEMODE,%WRITEMODE%)

TASK(/CPMB/BPC_MASTER_DATA_TARGET,FORMULA_FILE_NO,%TEMPNO7%)

TASK(/CPMB/BPC_TXT_DATA_TARGET,INPUTNO,%TEMPNO6%)

TASK(/CPMB/BPC_TXT_DATA_TARGET,DIMNAME,%DIMNAME%)

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.