Script Logic Posts to Non-existent Member

[Former Member]

Hi,

We have an issue with a piece of script logic which seems to post to a member which doesn't actually exist.

This is the code which posts the data:

//Copies KG_FACTOR for WIP from the Product dimension to the WIP dimension

*XDIM_MEMBERSET ACCLABOUR = KG_FACTOR

*WHEN PRODUCT.PROD_TYPE

*IS "WIP"

*REC(FACTOR=1, WIP=PRODUCT.SPS_SORTKEY, PRODUCT="NOPRODUCT")

*ENDWHEN

*COMMIT

The property SPS_SORTKEY sometimes contains a member which does not exist in the WIP dimension but the datamanager package doesn't seem to check this.

We are currently on BPC v.7 but shortly upgrading to 7.5. Is this something which would be resolved in 7.5 or do we need to make a chage to this script logic to prevent this from happening?

Thanks,

Jamie

[Former Member · Accepted solution]

Hi Jamie,

There is no issue with version. I guess it is more with the logic and property maintenance, your code should take care of making sure that only valid PRODUCT.SPS_SORTKEY are picked which represent valid WIP IDs.

Regards,

Kalyan.

[Former Member · Accepted solution]

Hi Kaylan,

What logic would check if the SPS_SORTKEY was a valid member of our WIP dimension?

Thanks,

Jamie

[jrg_finster3 · Accepted solution]

Hi Jamie,

unfortunatly Script Logic never checks if you use a valid WIP ID.

This will not change with MS 7.5.

So you or the one who is responisble for the dimension has to ensure that the properties are filled with valid ID's.

The only way to ensure that you use valid ID's would be to do this calculation step via SQL-Server (Stored procedure) and implement a check there.

But in our case, the dimension admin has to check the properties.

Regards

Jörg

[Former Member]

Thanks for your replies! I'll make sure our users check this when they set up a new member in the product dimension.

[Former Member]

Hello Jamie,

I totally agree with Jörg, there's no way to implement such a check in the script logic, independent, which BPC version use use. Even in BPC 10, there no possibility.

Try to create a simple SSIS package to do your calculation and implement a check in there.

Best Regard,

Karsten