Overview
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.
Contacts
BW data flow
The BW model is enhanced as below to consider the information coming from table ZZF_BW_TSA in SAP PRS system PF2_050.
Master Data C_T001MGT
Master Data C_T001MGT (Sold Company setting) is created to save the data from SAP table ZZF_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
Warning
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_ZZF_BW_TSA
Datasource DTS_ZZF_BW_TSA is created on SAP PRS system PF2_050 with table ZZF_BW_TSA as a strcuture.
The Datasource is replicated on BW, and used as the source to the Transformation into Master Data C_T001MGT.
TO COMPLETE
Transformation TRSF: DTS_ZZF_BW_TSA -> C_T001MGT
Transformation TRSF: DTS_ZZF_BW_TSA -> C_T001MGT is created to load data from table ZZF_BW_TSA into Master Data C_T001MGT.
TO COMPLETE
How to update the BW scope
There are several steps to process to update the relevant Master Data used to set authorization scope and consolidation method in BW.
1- Table ZZF_BW_TSA
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.
- MANDT Client
- SNDPRN Indicate the SAP system on which the company is running
- SCOPE Scope Code
- BUKRS Company Code
- METHOD Consolidation method
- CONTROL Consolidation %
- CONSO BFC Conso
- KKBER Credit Control Area
| 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 |
2- Update Master Data C_T001MGT
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.
- Delete the content of Master Data C_T001MGT
- Execute the Full DTP to extract data from Datasource DTS_ZZF_BW_TSA into master data C_T001MGT and activate it.
- Check master data C_T001MGT content.
3- Load relevant Master Data
Now the sequence of reloading below can be processed to take the master data C_T001MGT information into account.
According to the level of emergency, only the loading of C_COMPPRS (step 1) can be done manually, to confirm the proper scope and consolidation values, then all other loadings will be done automatically with the next daily night process.
Only the step 13, to load Master Data C_CREDEXP, is a weekly process scheduled every Sunday at 11 PM CET.
- Load Master Data C_COMPPRS from Datasource ZZR_0COMP_CODE_ATTR_PRS (IP + DTP) + Activate
- Load Master Data C_COMPCDE from Datasource ZZR_0COMP_CODE_ATTR (IP + DTP) + Activate
- Load Master Data C_COMPCDE from Datasource DTS_0COMP_CODE_ATTR (IP + DTP) + Activate
- Load Master Data C_COMPCDE from Datasource C_COMPCDE + Activate
- Load Master Data 0COMP_CODE from Datasource DTS_0COMP_CODE_ATTR + Activate
- Load Master Data 0COMP_CODE from Datasource 0COMP_CODE + Activate
- Load Master Data 0PLANT from Datasource 0PLANT + Activate
- Load Master Data C_PLANT from Datasource C_PLANT + Activate
- Load Master Data C_CST_CA2 from Datasource 0FI_AR_9 (IP with dynamic Credit Area + DTP) + Activate
- Load Master Data C_CST_CA2 from Datasource 0CUSTOMER_TEXT (IP + DTP)
- Load Master Data C_CUSTPRS from Datasource 0CUSTOMER_ATTR (IP + DTP) + Activate
- Load Master Data C_CUSTID from Datasource 0CUSTOMER_ATTR (IP + DTP) from both source systems + Activate
- Execute Process Chain PC_FIWC_04 to load DBFIAR07 and Master Data C_CREDEXP
- Load Master Data C_VENDPRS from Datasource 0VENDOR_ATTR (IP + DTP) + Activation
- Load Master Data C_AGRITM from Datasource C_AGRITM
- Load Master Data 0PROFIT_CTR from Datasource 0PROFIT_CTR
- Load Master Data C_WBS_ELE from Datasource C_WBS_ELE
- Load Master Data C_WBS_EL2 from Datasource C_WBS_EL2
- Load Master Data C_PMORDER from Datasource C_PMORDER
- Load Master Data C_PMORDR from Datasource C_PMORDR
- Load Master Data C_COSTCTR from Datasource C_COSTCTR
- Load Master Data C_PMORDER from Datasource C_PMORDER
Authorization Analysis & Role
In addition to the Master Data attributes update, 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.
