A) Below list of Updates done directly on WBP (open mandant)

all updates should be reproduced on WBD after the freeze + DQ1 also to remove on production and align all BW environnements.

1) Date 15.02.2019 : RFC 7000042973 / Admin Change

Update transformation :  0D38WB3HATF5Q5RHA3ELBINH0K773W1P  (TRSF : C_WBS_EL2 -> C_WBS_EL2)

Action : delete end routine because each reload of C_WBS_EL2 to C_WBS_EL2 is deleting all attributs except the attributs manages inside the transformation)

Linked with Freshdesk ticket 2430

2) Date 21.02.2019 : RFC 7000043200 / Admin Change : 5000006469

Update 2 queries :

BW_QRY_MVFIWC03_0002 + BW_QRY_MVFIWC03_0003

Action : change the formula to not take into account the % method in the calcul

Linked with IFSR16 project

Update of MPR_FC003

Action : add CRCOPA29  (PAX: Profitability Analysis: COPA - IECRA Determination WP1) in the multiprovider MPR_FC003

The infocube CRCOPA29 was created in January to follow the PAX split project and all PM, PV, PX and PY codes reloated to PAX project are not integrate in the existing infocube COPA dataflow but in the new one and this new is not well integrated in the Fixed costs solution and only COPA BW solution.

3) Date 21.02.2019 : update BW_QRY_MPR_IC001_0062_NA

Add new variable authorization :  on C_MATPLNT__CPFCTR1_2 + on 0COMP_CODE__C_AUTHMA + 0COMP_CODE 

B) Process to be apply during the freeze 

DQ1 -> WBP  (4 Mar 2019 -  10 May 2019)  - For emergency transport only

ฺB.1) BW developer asks approval from reporting coordinators, corresponding SL BW responsible and BI manager by email and detail of the change + reason why it is emergency.

B.2) In ChaRm, create RFC (Project = ZGEN) + General Change  by change manager --> update transport control file (on tab Duplication WBD at column G to J)
        Column G = RFC and GC number + Topic of the change
        Column H to J = Approve or Reject  (Change manager can update the file instead of RC and SL manager according to email from developer)
B.3) On DQ1, create TR and release task and Put in the description of TR, the GC# by developer
B.4) In ChaRm, put in the Text log of GC, the TR# and change the status to "Authorized for PRD" by change manager and inform BI team regarding to service line (Anon-I&P, Guillaume-RtR, Marco-PtP, or Craig-OtC) by forward email that already have approval from RC,SL and BI manager once development is done.  
***Please note that we don't have simulation to test. It will go directly to WBP. ***
B.5) Check conflict and send a mail to IS-QPsupport@solvay.com to ask them to release TR on DQ1 and import it on WBP by BI team (Anon, Guillaume, Marco, Craig or Francesco) ONLY

B.6) CHARM Support Team release and import TR on WBP, update the Text log, close the GC and update the file of manual duplication (tab : Duplication WBD) :

To identify emergency, 3 approvals from reporting coordinators, corresponding service line manager and BI team are required.
For example, I&P change request, we need approval from 

1. Reporting Coordinators (RC) = Meire Santos
2. Service line BW responsible (SL) = Michel Adant 
3. BI manger (BI) =  Francesco (back up Guillaume or Anon)
All 3 managers consider as emergency and approve for the change, then we will allow transport. 

C) Process to be apply after the freeze

WBD -> WBQ  -> WBP (Normal process after migration complete)

For each created TR from DQ1 and imported on WBP, you have to redo on WBD manually by the developer NOT BI team in TR and import it on WBQ and WBP to avoid inconsistencies between servers. 
 C.1) In ChaRm, create RFC + Urgent Change or Standard Change + TR on WBD

This step is possible from April, 11th

C.2 ) On WBD, release TR via ChaRM
This step is possible from April, 29th (Import on WBQ is active)

C.3) Transport to WBP via Charm
Import on WBP active from May, 20th after the migration  

C.4) In ChaRm, change the status of UC until the closure