The only difference is that the segment number for ACDOCA-PAOBJNR and ACDOCA-OBJNR doesn't come from CE4XXXX but from CE4XXXX_ACCT. It's therefore one of the billing segment numbers 100, 101 or 102 that is reused as ACDOCA-PAOBJNR and ACDOCA-OBJNR segment number in this case. In other words: while the ACDOCA item has been created as summarized It will bring consolidated Actual data coming from ACDOCA and Plan data from ACDOCP together in one table (‘one version of the truth’). This means that all data within a consolidated report originated from SAP S/4HANA Group Reporting are based on the table ACDOCU.Within SAP S/4HANA actual data (e.g. balances for SAP S/4HANA companies) is define view Y_ACDOCA as select from acdoca { key acdoca.rldnr, //Ledger in General Ledger Accounting key acdoca.rbukrs, //Company Code key acdoca.periv, //Fiscal Year Variant key acdoca.gjahr, //Fiscal Year key acdoca.poper, //Posting period key acdoca.ktopl, //Chart of Accounts key acdoca.racct, //Account Number key acdoca.rcntr, //Cost Center ACDOCA table has been introduced in S/4Hana which have all the fields which were in separate tables before. BSIS, BSAS, BSID, BSAD, BSIK, BSAK, BSIM table and many more are now obsolete. They are available in system but will not be used further. Even FAGLFLEXA is obsolete now. Below is the screen for ACDOCA table A: Combined Profitability Analysis is a really interesting feature. It’s been around even before S/4 HANA. And the general advice on that feature is it was created by the support people at SAP not by the developers. It was a way for people to have account based and cost based data in one table for reporting. Combined COPA will not be in After an upgrade is performed and Account-based COPA is activated, you notice in table GLPCA that Origin Type = 10 'Profitability Segment in Account-Based CO-PA', but you are expecting Origin Type = 34 'Profitability Segment in Costing-Based CO-PA' as it was before the upgrade because costing-based COPA was only activated. Note that while table BSEG uses both the old IMKEY field and the new INTRENO field, COEP, FAGLFLEXA and ACDOCA use the OBJKEY field. For cost collectors, this means that we have to look in VISCCC to find the right INTRENO, which we can use in VICAINTRENO to get the rest of the data. Discount is not considered at all. Step 1. Create a BAdI Implementation for Flow Builder Plus. Flow Builder Plus used the central BAdI of One Exposure to adjust the final flow: BADI_FQM_FLOW_ADJUST_CORE. The BAdI filter ORIGIN_APPLICATION shall be set to ‘ BSEGV ’. Step 2. BAdI Implementation Logic. Vay Tiền Trả Góp Theo Tháng Chỉ Cần Cmnd.

difference between bseg and acdoca