Error loading data from BW to BPC with standard package

[former_member205115]

Hi experts,

A big part of our solution is pulling actuals from BW into BPC.  To do so we use the standard SAP package "Load InfoProvider Selections" which calls the process chain /CPMB/LOAD_INFOPROV_UI.

We have migrated our environment to BPC 10 and tried to run this process and are now getting the following error:

“ Task name CONVERT:

No 1 Round:

An exception with the type CX_ST_MATCH_ELEMENT occurred, but
was neither handled locally, nor declared in a RAISING clause

System expected element 'Selections' ”

We have tested and this is happening with all data loading packages.  It appears as though it is expecting a "selection" parameter, but selections have definitely been made.  Has anyone encountered a similar issue or have any idea how to resolve it?

Best,

Chris

[former_member186338 · Accepted solution]

Hi Chris,

Can you provide the advanced DM script for the package?

B.R. Vadim

[former_member205115 · Accepted solution]

Hi Vadim,

Yep, my script is:

(INFOPROVIDERSELECTION,%InforProvide%,"%SELECTION%",Please input the infoprovider and set selection,,)

(TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls)

(RADIOBUTTON,%CLEARDATA%,"Select the method for importing the data from the source file to the destination database",0,{"Merge data values (Imports all records, leaving all remaining records in the destination intact)","Replace && clear datavalues (Clears the data values for any existing records that mirror each entity/category/time combination defined in the source, then imports the source records)"},{"0","1"})

(RADIOBUTTON,%RUNLOGIC%,"Select whether to run default logic for stored values after importing",1,{"Yes","No"},{"1","0"})

(RADIOBUTTON,%CHECKLCK%,"Select whether to check work status settings when importing data.",1,{"Yes, check for work status settings before importing","No, do not check work status settings"},{"1","0"})

(%TEMPNO1%,%INCREASENO%)

(%ACTNO%,%INCREASENO%)

(/CPMB/INFOPROVIDER_CONVERT,OUTPUTNO,%TEMPNO1%)

(/CPMB/INFOPROVIDER_CONVERT,ACT_FILE_NO,%ACTNO%)

(/CPMB/INFOPROVIDER_CONVERT,TRANSFORMATIONFILEPATH,%TRANSFORMATION%)

(/CPMB/INFOPROVIDER_CONVERT,SUSER,%USER%)

(/CPMB/INFOPROVIDER_CONVERT,SAPPSET,%APPSET%)

(/CPMB/INFOPROVIDER_CONVERT,SAPP,%APP%)

(/CPMB/INFOPROVIDER_CONVERT,FILE,%InforProvide%)

(/CPMB/INFOPROVIDER_CONVERT,CLEARDATA,%CLEARDATA%)

(/CPMB/INFOPROVIDER_CONVERT,INFOPROV_SELECTION,%SELECTION%)

(/CPMB/CLEAR_DATA,INPUTNO,%TEMPNO1%)

(/CPMB/CLEAR_DATA,CHECKLCK,%CHECKLCK%)

(/CPMB/APPEND_LOAD,INPUTNO,%TEMPNO1%)

(/CPMB/APPEND_LOAD,ACT_FILE_NO,%ACTNO%)

(/CPMB/APPEND_LOAD,RUNLOGIC,%RUNLOGIC%)

(/CPMB/APPEND_LOAD,CHECKLCK,%CHECKLCK%)

(/CPMB/APPEND_LOAD,CLEARDATA,%CLEARDATA%)

Thanks,

Chris

[former_member205115 · Accepted solution]

Also, we are on BW 7.4 in case that could matter.

[former_member186338 · Accepted solution]

If I look on the environment shell standard package "Load Transaction Data from BW InfoProvider UI" using chain /CPMB/LOAD_IFOPROV_UI I can see the following script (BPC 10 SP12):

PROMPT(INFOPROVIDERSELECTION,%InforProvide%,%SELECTION%,"Please select the InfoProvider and set selection (InfoProvider list is restricted by both BW and BPC authority)",,)

PROMPT(TRANSFORMATION,%TRANSFORMATION%,"Transformation file:",,,Import.xls)

PROMPT(RADIOBUTTON,%TARGETMODE%,"Handling of records in target",0,{"Append","Overwrite records with match key","Replace data in same data region of Entity, Category, Time and Audit ID"},{"0","1","2"})

PROMPT(RADIOBUTTON,%RUNLOGIC%,"Select whether to run default logic for stored values after importing",1,{"Yes","No"},{"1","0"})

PROMPT(RADIOBUTTON,%CHECKLCK%,"Select whether to check work status settings when importing data.",1,{"Yes, check for work status settings before importing","No, do not check work status settings"},{"1","0"})

PROMPT(KEYDATE,%KEYDATE%,"Key date",0)

INFO(%TEMPNO1%,%INCREASENO%)

INFO(%ACTNO%,%INCREASENO%)

INFO(%KEYDATE%,)

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

TASK(/CPMB/INFOPROVIDER_CONVERT,ACT_FILE_NO,%ACTNO%)

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

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

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

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

TASK(/CPMB/INFOPROVIDER_CONVERT,FILE,%InforProvide%)

TASK(/CPMB/INFOPROVIDER_CONVERT,INFOPROV_SELECTION,%SELECTION%)

TASK(/CPMB/INFOPROVIDER_CONVERT,KEYDATE,%KEYDATE%)

TASK(/CPMB/LOAD_IP,PREPROCESSMODE,0)

TASK(/CPMB/LOAD_IP,TARGETMODE,%TARGETMODE%)

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

TASK(/CPMB/LOAD_IP,ACT_FILE_NO,%ACTNO%)

TASK(/CPMB/LOAD_IP,RUNLOGIC,%RUNLOGIC%)

TASK(/CPMB/LOAD_IP,CHECKLCK,%CHECKLCK%)

TASK(/CPMB/LOAD_IP,KEYDATE,%KEYDATE%)

Vadim

[former_member186338 · Accepted solution]

And the chain is:

[former_member205115 · Accepted solution]

Vadim, that is absolutely fantastic.  I needed to adjust it slightly for our chain as it had a different variable and an additional step, but that was easy enough.  Thanks a lot.

[ravindra_tumuluri]

Can you try running the package again after activating the model ?

[former_member205115]

Hi Ravindra,

The package is already active, unless I misunderstand?

Best,

Chris