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 ZFI_BW_TSA is maintained by Corporate team & Finance in SAP PRS system PF2_050 only if TSA is created between the external company and Syensqo else BW keep the existing data managed in ZZF_T001_MGT (% of integration =0). 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.
Transition Service Agreement (TSA) is an agreement between buyer and seller companies (or divested entities), in which one entity provides services and support (e.g., IT, finance, HR, real estate, payroll) to another after a divestiture to ensure business continuity.
Once the TSA period is over, the Company information is deleted from table ZFI_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 main contact for IT SOURCING & TSA is sylvie.kramdi@syensqo.com
The main contact for MAC Data & Reporting is raquel.espadinha@syensqo.com
The main contact for Intercompany & Consolidation is guillaume.thevenet@syensqo.com
The BW model is enhanced as below to consider the information coming from table ZFI_BW_TSA in SAP PRS system PF2_050.
BW updates are embedded in the Transfer Request OBDK900649 (4000000764: SNF Scope to display in BW queries).
Master Data C_T001MGT (Sold Company setting) is created to save the data from SAP table ZFI_BW_TSA in BW.
It is a Company Code type (CHAR 4), compounded with Source System (LOGSYS) and Company Scope (C_SCOPE).


Attributes are :
C_CSMETH Consolidation Method
K_INTRAT Company Integration Rate
C_FLGINT Intercompany Flag
0C_CTR_AREA Credit Control Area

Do not use this Master Data in another object (ADSO structure, MD attribute..), since its content is fully deleted and replaced from the SAP source table. |
Datasource DTS_ZFI_BW_TSA is created on SAP PRS system PF2_050 with table ZFI_BW_TSA as a structure.
The Datasource is replicated on BW, and used as the source to the Transformation into Master Data C_T001MGT.
Transformation TRSF: DTS_ZFI_BW_TSA -> C_T001MGT is created to load data from table ZFI_BW_TSA into Master Data C_T001MGT.
For Non ERP Company Code (Landscape NONERP), the LOGSYS field must be empty in target Master Data C_T001MGT.

Transformation TRSF: ZZR_0COMP_CODE_ATTR_PRS PRS -> C_COMPPRS is updated in the Start Routine, to use the values from Master Data C_T001MGT in replacement to the incoming values from SAP.
The Datasource ZZR_0COMP_CODE_ATTR is retrieving scope and consolidation information from table ZZF_T001_MGT, in a dedicated Exit in source system (Include ZXRSAU02_ZZR_0COMP_CODE_ATTR).

The Intercompany Flag and Integration Rate populated are C_FLGINT and K_INTRAT, which are used for consolidation view = 1 in queries.
The C_FLGIN02, C_FLGIN03 and K_INTRA02, K_INTRA03 are used for consolidation view = 2 and consolidation view = 3, and are not overwritten by this specific process.

*** Start Add NGC20260204 |
Addition of a dynamic selection on Credit Control Area (KKBER), populated with distinct C_CTR_AREA values from Master Data C_T001MGT.

*** Start Add NGC20260204 * Loading Distinct Credit Control Areas from C_T001MGT |
Update End Routine in Transformation to add an English description for each distinct Credit Control Area from Master Data C_T001MGT.

*** Start add NGC20260204 |
Addition of a dynamic selection on Credit Control Area (KKBER), populated with distinct C_CTR_AREA values from Master Data C_T001MGT.

Addition of a dynamic selection on Credit Control Area (KKBER), populated with distinct C_CTR_AREA values from Master Data C_T001MGT.

*** Start Add NGC20260204 * Loading Distinct Credit Control Areas from C_T001MGT |
Update End Routine and 0RATING routine in Transformation to derive Rating field from Credit Control Area from Master Data C_T001MGT.

Start Routine ** Start Add NGC20260204 0RATING Routine IF l_t_range[] IS INITIAL. "NGC20260204+ |
Addition in Start Routine of a dynamic selection on Credit Control Area C_CTR_AREA values from Master Data C_T001MGT.

** Start Add NGC20260204 |
There are several steps to process to consider the new records from table ZFI_BW_TSA in BW.
Check in SAP PRS system PF2_050 that table ZFI_BW_TSA is properly populated with the Company information to push in BW (exple below for SNF scope).
This information will overwrite the data coming from table ZZF_T001_MGT.
| Client | PRS Company Code | Scope Code | Consolidation method | Consolidation % | BFC Conso | Credit control area | Comment |
| MANDT | BUKRS | SCOPE | METHOD | CONTROL | CONSO | KKBER | ZCOMMENT |
| 050 | 6402 | 21 | 10 | 100 | X | 0143 | TSA until 12.2026 |
| 050 | 6403 | 21 | 10 | 100 | X | 0143 | TSA until 12.2026 |
| 050 | 6416 | 21 | 10 | 100 | X | 0143 | TSA until 12.2026 |
| 050 | 7810 | 21 | 10 | 100 | X | 0143 | TSA until 12.2026 |
The content of table ZFI_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.
As long as there is no new update in the table ZFI_BW_TSA, there is no need to update Master Data C_T001MGT again.
Now the sequence of reloading below can be processed to take the master data C_T001MGT information into account.
These loadings can be done with temporary IP+DTP filtered on relevant Company selection, or with daily IP+DTP used in Process Chains with Full/Delta selection.
According to the level of emergency, only the loading of C_COMPPRS (step 1) must be done manually, to confirm the proper scope and consolidation values, then all other loadings could be done automatically with the next daily night process.
Step 13, to load Master Data C_CREDEXP, is a weekly process scheduled every Sunday at 11 PM CET, but it is not a a requirement for any other loading.
In addition to the Master Data updates, the authorization to display the scope must be granted to users, through a dedicated authorization analysis and a dedicated role .
In case of emergency, the new authorization scope value (from C_AUTHMA) can be added to all dimensions of the main SCO Authorization analysis ZP2SCOP00.

Example here for SNF scope added to the SCO scope for dimension 0COMP_CODE__C_AUTHMA.

This way, the authorization to display the new scope is automatically granted to all users already assigned to the SCO role ZP2_SCO_P00.
In a sustainable and flexible solution, the new authorization scope value must be added to a new Authorization analysis ZP2xxxP00, in copy of ZP2SCOP00, to get all relevant dimensions.
Then this new Authorization analysis ZP2xxxP00, must be assigned to a new dedicated role ZP2_xxx_P00, in copy of the SCO role ZP2_SCO_P00.
And finally, this new role ZP2_xxx_P00 must be assigned to the relevant users in charge of the scope in BW.
This process can only be done by the Authorization team in charge, and must be requested through a SAP Privilege Management Request as below, for all platforms from Development to Production. |

Once the BW data reloading is done and the authorization enhancement assigned, BW queries are automatically taking the new scope into account.
The consolidation view to use is 1, when required in the prompt (even if not proposed in the field description).

The identified Finance queries are the following :
BW_QRY_MVWISE01_0011 BW - WISE - Collection Global Overview (Core Query)
BW_QRY_MVFIAR01_0006 Aged Balance (Core Query)
BW_QRY_MVFIAR01_0008 Credit Exposure (Core Query)
BW_QRY_MVFIAR02_0001 Detailed Open/Cleared Items (Core Query)
BW_QRY_MVFIAR01_0002 Overdues (Core Query)
BW_QRY_MVFIAR01_0009 Payment Perfm. (Core Query)
BW_QRY_MVFIAR01_7001 DSO in acct. view (Core Query)
BW_QRY_MVFIAR01_7002 Overdue in acct. view (Core Query)
When the Xtract tool is used to extract data from BW through queries, the filters below must be adapted to consider the new scope :
The impacted queries are the following :
QVSBS_BW_QRY_MVFIAR01_0006 BW - Credit Management Aged Balance (Core Query) - QV SBS KP
QVSBS_BW_QRY_MVFIAR01_0001 BW - Credit Mgt Outstanding/Not due for DSO (QV)
QVSBS_BW_QRY_MVFIAR01_0002 BW - Credit Mgt Turnover for DSO (QV)
QVSBS_BW_QRY_MVFIAR01_0010 BW - Payment Performance (QV SBS Query) QV SBS KPI
with Eric Fournel list