Below some news about DS M project :
PLEASE READ IT very important about all development in progress or plan to be started in the coming weeks.
1) Reminder about context
: integration of new BW system WBV in the existing BW landscape
Today : WBD -> WBQ -> WBP and WB1 as sandbox
After September, 15th 2020 : WBD -> WBQ -> WBV -> WBP and WB1 as sandbox.
With DSM tools, the refresh should be easiest and allow to extract only some data following slicing solution.
DSM will be used to copy the data from one BW system to another BW system (mainly prod to pre-prod)
BW is a pilote and DSM could be used for ECC in the future.
2) Slice of the data and runs
Run 1 done : copy of WB1 -> WBV (slice of the data 2018 + 2019 + 2020, slice used only for run1 ) as WB1 is copy of WBP done on May 2019 + any news loads done after May 2019 for Solstice project for example.
Run 2 : scheduled July 15th -> July 17th with data 2019 + 2020 from WBP + exception list (Stocks application only are in the exception list)
Run 2bis : scheduled September 9th -> September 11th with data 2019 + 2020 from WBP + exception list (Stocks application only are in the exception list)
Run 2ter : scheduled September 24th -> October 7th with data 2019 + 2020 from WBP + exception list (Stocks application only are in the exception list)
Run 3 : scheduled November 11th -> November 25th with data 2019 + 2020 from WBP + exception list (Stocks application only are in the exception list)
3) Run 3 and Solman
Run 1 and Run 2 (Bis and Ter) are done without a test of integration with Solman only test of copy and usage of DSM + make a real runbook to achieve it but for the go live = run 3, a new project or Change Cycle / phase will be implemented in Solman to allow the release with a new BW environnement.
Project or Change Cycle / phase is linked to RFC and change document (UC = only urgent change for BW)
After the new integration, keep Urgent Change usage only because it is not possible to use Normal Change and transport of copy for BW.
To implement this new project change cycle / phase, it will not be done as the creation of a new one but an update of the existing one so all developments on BW will be impacted.
Frozen period to allow this change
From November 10th 2020-> November 25th 2020
During this period it is not possible to add new any RFC or UC linked to BW + not possible to add new Transport request and possible to update existing transport request created before the frozen period.
→ if issue on WBP → need to open the mandant and do the change on WBP (I hope it will be never happening)
Monday 9th October and Tuesday 10th October the 2 last days before the frozen period to move BW developments on WBP (daily job still scheduled these 2 days at 05:00am CET Time) + during the day as it was explained by Catherine by mail.
Below differents cases just before the freeze :
Case 1 : RFC created + all UC created wihtout transport request
During frozen period, Q&P team will update the status of the UC to closed + update the status of the RFC to closed
It could be done by change manager before the frozen to clean the not useful UC and RFC to faciliate the work of Q&P team.
Action to be done after November 25th
For project : All change manager have to create new RFC and new UC linked to the new change cycle / phase
For CGI : All CGI coordinators have to recreate from freshdesk a new RFC.
Case 2 : RFC implemented + all UC closed
To facilitate the work of Q&P team, the RFC could be updated to close (Status = Confirm change)
Case 3 : RFC created + UC with status > in test qas so all transport requests are released on WBQ.
During frozen period, Q&P team will update the status of the UC in withdrawn and it will be no more possible to release TR released on WBQ and never released on WBP (Transport request removed from WBP buffer) + RFC closed
it could be done by change manager before the frozen by the creation of new ticket to Q&P team before the frozen period if you are sure that the release of the UC will generated too many issues but keep in mind that all objects updated and in this state could be updated in the future and could generated the issue on production after, so better to make a real rework, rollback on the existing objects to let clean the situaiton on WBD, WBQ and WBP all systems will be aligned.
Action to be done after November 25th
For project : All change managers have to create a new RFC and new UC linked to the new change cycle / phase + need for the developer to reassign the objects impacted in new transport request.and release again on WBQ.
For CGI : All CGI coordinators have to recreate from freshdesk a new RFC+ UC + same action of the project, reassign objects impacted on new transport requests.
Case 4 : RFC created + UC created and status "in development" and transport request created and filled (= BW objects assigned to the TR created)
During frozen period, Q&P team will update the status of the UC in withdrawn + update the status of the RFC to closed
Action to be done after November 25th
For project : All change managers have to create a new RFC and new UC linked to the new change cycle / phase + need for the developer to reassign the existing transport (done in the previous UC) to the new UC and nothing about new development will be lost .
For CGI : All CGI coordinators have to recreate from freshdesk a new RFC + new UC + same action of the project, reassign transport requests done in previous UC on the new one.
In any case don't change the description to keep a trace of the first UC linked to the TR.
Case 5 : RFC created + UC created status "in development" but with some transport requests released before. (rework for maintenance for example)
During frozen period, Q&P team will update the status of the UC in withdrawn and it will be no more possible to release TR released on WBQ and never released on WBP (Transport request removed from WBP buffer)+ RFC closed.
Action to be done after November 25th
For project : All change managers have to create a new RFC and new UC linked to the new change cycle / phase + need for the developer to reassign the existing transport (done in the previous UC and only TR in dev and never released) to the new UC and nothing about new development will be lost BUT need need to reassign to new TR all developments released on WBQ and not move on WBP if not = regression and issue during the release on WBP.
For CGI : All CGI coordinators have to recreate from freshdesk a new RFC + new UC + same action of the project, reassign transport requests (only TR not released) done in previous UC on the new one + new TR with same objects released in the previous one to have a complete UC if not = regression and issue during the transport on WBP
Conclusion :
The release of maximum of UC have to be done before the frozen if the tests are really done and sure that no regression could be generated after.
As it was communicate about the closing planning
The next real period to release will be December 7th.
3) After the November 25th 2020
All RFC and all UC have to be recreated + Transport Request in development will be reassigned on each UC (by yourself)
4) Stats of RFC today for WBP
Extraction done 07.07.2020 : 125 RFC opened and linked ot WBP system. (309 UC and more than 303 TR)
Extraction done 29.10.2020 : 103 RFC and 146 UC.
5) Impact on WBV about loads
Due very bad ABAP code on BW, some special rules will not working for example
source system in hard copy in the abap code
Transf: DPFIAR01 -> DBFIAR01
These kinds of codes are in Finance, QM, SD and master data application but as you can see even if on WBQ when in 2016, with new Solman the source system will be no more WV1 but WQ1 some rules are not done.
The program ZBW_ABAP_LOOKUP_FINDER can help to identify.
The correct way is to used global filter master data as below :
TRSF: DPDYN22 -> ABDPDY47
Or by using the function module Z_WBW_SOURCE_SYSTEM - Determine Source system of ERP FROM /bic/pc_glbfilt (Master data Global Filter)
Useful Codes (Transaction, tables, program, functions, tips or general doc...)
6) Issues after the last run 3 end of November 2020
Some DTP seems not working and generate a crash below the workaround to fix it (but need to ask by mail to Adagio team to open the mandant for 1 or 2 hours max)