Simple Brompton hack

Inspired by a post on Facebook group "Brompton Hacks" I decided to do the same, this is a short note about what I did, actually changing your rear wheels to something useful both when pulling the bike and when letting the bike stand folded.

I can't understand how and why Brompton doesn't provide something like this as a default, so here it is, a simple upgrade/hack that should be standard equipment on every Brompton bike.

First step:
Procure material, visit a local Decathlon shop / hardware store / whatever and come back home with:

• Inline skate wheels 63mm 82A (sold as spare parts in package of 4) 
• Allen key set (you'll need size 4 and size 5)
• M6 x 35mm screws (I went for titanium with Allen head, could also have chosen taper cone head or maybe flanged button head that are more similar to standard Brompton ones)
• Some thread locker like Park Tool TL1 or Loctite 242

Second step:

• Allen key size 4 remove Brompton wheels, keep washers to be reused

Third step:

• Apply thread locker and with Allen key size 5 install Decathlon wheels reusing original washers

Fourth step:

ENJOY

Store away the Brompton wheels remains (blue stain is original thread locker)

One of the most useful SAP Notes for BW

Great note for those tuning BW parameters

912367 - Composite Note: RSADMIN Parameter

Two very important SAP Notes for BW Authorizations

These two notes can solve a lot of problems, or at least give a good start ...

150315 - BW-Authorizations for Remote-User in BW and OLTP

161292 - Authorization templates for user roles and tasks 

BPC filter 0CALMONTH in data package

A picture is worth a thousand words ...

so that's the correct format for 0calmonth.

BPC Member formula ... devil is in the details

I've found a "non working" item in BPC ... it's member formula was something like

IIF([HDCNT]=0,0,[TOT_COST]/[HDCNT])

very nice and workend fine, but ... while cost is currency converted headcount is not ... so it was "not working" ... 

A little revision, rewriting it in order to take into account dimensions brought the desired result

IIF(([HRCOST].[HDCNT],[RPTCURRENCY].[LC])=0,0,([HRCOST].[TOT_COST])/([HRCOST].[HDCNT],[RPTCURRENCY].[LC]))

 

Not that difficult, but I see that BPC people generally don't like to fully qualify things :(

After a while I had to change it again ... adding another bit of MDX to the game, IsLeaf and CurrentMember

IIF(
IsLeaf([TIME].CURRENTMEMBER)
,
IIF(([HRCOST].[FTE],[RPTCURRENCY].[LC])=0,0,([HRCOST].[TOT_COST])/([HRCOST].[FTE],[RPTCURRENCY].[LC]))
,
IIF(([HRCOST].[HEADCNT],[RPTCURRENCY].[LC])=0,0,([HRCOST].[TOT_COST])/([HRCOST].[HEADCNT],[RPTCURRENCY].[LC]))
)

BPC work status setup ... APPROVALORG, a little parameter often overlooked

When setting up workstatus in BPC there is a little web parameter to setup, APPROVALORG, it's often overlooked because generally one doesn't manage more than one hierarchy for an entity ... in our case we have 3 hierarchies and hierarchy number 3 (H3) is the one used to manage read/write permissions and thus the natural candidate for controlling workstatus.
So the web parameter APPROVALORG should not be H1 in this case, or you'll get some "strange" errors, but H3, and of course H3 will also have the owner property correctly filled.

An example:

Some useful tutorials can be found on SDN.