Function documentationImport Data from a BW InfoProvider Locate this document in the navigation structure

 

You can define a package to upload transactional data from an InfoProvider defined in the underlying SAP NetWeaver system using the process chain /CPMB/LOAD_INFOPROVIDER.

Activities

  1. Create a Data Manager package by using the corresponding process chains (see Package Usage).

  2. 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. Choose the source InfoProvider.

    5. Choose a transformation file.

    6. Select the method to copy the data:

      • Merge — Joins the data values

      • Replace — Clears existing data values and replaces them

    7. To run the default logic after import, choose Yes, then choose Next.

    8. To check the work status when importing the data, choose Yes.

    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/INFOPROVIDER_CONVERT

CLEARDATA

0

Delete data before writing:

0 = NO

1= YES

/CPMB/INFOPROVIDER_CONVERT

FILE

InfoProvider name

/CPMB/INFOPROVIDER_CONVERT

SPACKAGE_SIZE

10000

Package size

/CPMB/INFOPROVIDER_CONVERT

TRANSFORMATIONFILEPATH

Transformation file

/CPMB/APPEND_LOAD

CHCKLCK

0

Check work status:

1 = YES

0 = NO

/CPMB/APPEND_LOAD

CLEARDATA

0

Delete data before writing:

0 = NO

1= YES

/CPMB/APPEND_LOAD

RUNLOGIC

0

Run logic after process:

0 = NO

1 = YES

/CPMB/CLEAR_DATA

CHCKLCK

0

Check work status:

1 = YES

0 = NO

/CPMB/CLEAR_DATA

RUNLOGIC

1

Run logic after process:

0 = NO

1 = YES

Example Example

The data imported from the BW InfoProvider overwrites the records in the application that have matching keys. The records in the post-import application are affected, but the data from the BW InfoProvider is not affected. If there are duplicate records in the data they are aggregated using the dimensions as the key.

Post-Mapping InfoProvider Data

ACTUAL,CASH,2006.JAN,500

ACTUAL,CASH,2006.JAN,200

ACTUAL,CASH,2006.FEB,200

Pre-Import Application Data

ACTUAL,CASH,2006.FEB,100

ACTUAL,CASH,2006.JAN,200

ACTUAL,CASH,2006.APR,900

Result

ACTUAL,CASH,2006.FEB,200

ACTUAL,CASH,2006.JAN,700

ACTUAL,CASH,2006.APR,900

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.