When a company that operates in one of Syensqo main SAP ERP systems is sold or liquidated, Finance team updates specific tables linked to the Company Code maintenance in SAP PRS system PF2_050, with information acting the Company exit.
Refer to this procedure for more information : ZZF_T001_MGT_V - Company codes table maintenance
One of these tables is the ZZF_T001_MGT which is used as a source to BW, to update the authorization scope accordingly into the PRS Company Code master data C_COMPPRS, and other dependent master data.
Refer to BW - Authorization scope management
In certain M&A projects, where it has been agreed with buyers that Syensqo will provide a Transitional Service Agreement (TSA) for some reporting tools, it is necessary to keep in BW an authorization scope and consolidation method allowing this Company to be displayed properly in reporting.
Therefore, the information from table ZZF_T001_MGT must not be used in BW to set the Company as sold, preventing any display in reporting.
A new table ZZF_BW_TSA is maintained by Finance in SAP PRS system PF2_050, with the Company information to use to overwrite authorization scope and consolidation method in BW, as long as the Company data must be displayed in reporting.
Once the TSA period is over, the Company information is deleted from table ZZF_BW_TSA, and the Company exit information is taken again from table ZZF_T001_MGT.
Refer to this procedure for more information :
This page is explaining how this table is used in the BW data flow, and what is the procedure to follow for any new carve-out.
The BW model is enhanced as below to consider the information coming from table ZZF_BW_TSA in SAP PRS system PF2_050.
There are several steps to process to update the relevant Master Data used to set authorization scope and consolidation method in BW.
Check in SAP PRS system PF2_050 that table ZZF_BW_TSA is properly populated with the Company information to push in BW.
This information will overwrite the data coming from table ZZF_T001_MGT.
| Client | SAP system on which the company is running | Scope Code | Company Code | Consolidation method | Consolidation % | BFC Conso | Credit control area |
| MANDT | SNDPRN | SCOPE | BUKRS | METHOD | CONTROL | CONSO | KKBER |
| 050 | WP2_400 | 21 | 6402 | 10 | 100 | X | 0143 |
| 050 | WP2_400 | 21 | 6403 | 10 | 100 | X | 0143 |
| 050 | WP2_400 | 21 | 6416 | 10 | 100 | X | 0143 |
| 050 | WP2_400 | 21 | 7810 | 10 | 100 | X | 0143 |
The content of table ZZF_BW_TSA must be populated into the Master Data C_T001MGT (Sold Company setting) in BW.
This master data C_T001MGT is not used in any transactional structure in BW, which means that the content can be fully replaced without impact.
Now the sequence of reloading below can be processed to take the master data C_T001MGT information into account.
Main SCO Authorization analysis ZP2SCOP00
Main SCO Role ZP2_SCO_P00