1. What could be the reason for getting error message FCO_COPA006 after upgrading to SFIN?
In SAP Accounting, for using the new CO-PA features for SAP Business Suite powered by SAP HANA, it is a prerequisite to activate the account-based CO-PA in your operating concern. Costing-based CO-PA or both in parallel can be used further. Do not forget activating the account-based variant as otherwise an error message FCO_COPA 006 is received as a reminder. On tab "Data structures" flag "Account-based" should be set in the operating concern maintenance (transaction KEA0). The error message should not be there once this flag is set. If account-based CO-PA is not required to be used, and the costing-based variant on the other hand, this error message in customizing can be switched off as in the long text of message FCO_COPA 006, it has been described.
Report FCO_ADD_COPA_FIELD_TO_ACDOCA should run without problems after either of the two actions is performed. Generating the CO-PA characteristics of your operating concern into the new G/L line item table to activate account-based CO-PA is the purpose of this report.
2. How can Q1 changes be transported to production?
Maintain the entry for switching off error message in FCO_COPA 006 in Transaction OBA5. By using transaction KE3I it is transportable, as is the activation of the flag “Account-based”. The generation of the characteristics into table ACDOCA should work automatically as well if transaction KE3I is used furthermore to transport the data structures– this should work rather fast in NW 7.5* and 7.60, it should take few hours in NW 7.40 (to generate the client-independent environment via transaction KEA0 this report FCO_ADD_COPA_FIELD_TO_ACDOCA in NW 7.40 is taken otherwise would run into time-outs).
3. What is the purpose of using COPA tables in SFIN?
The line items are stored in ACDOCA in account based COPA. By a HANA compatibility view for reading, Table COEP is replaced and from table ACDOCA it is redirected to read data and to the COEP structure it is mapped.
The line items are stored in CE1XXXX (actual) and CE2XXXX (planning) in costing based COPA where the operating concern is denoted by 'XXXX'.
In CE4XXXX the PA segments are stored.
4. When trying to run realignment (KEND) in account based COPA why error message FCO_COPA058 are received?
For account based COPA in SFIN the realignment functionality is not supported currently. Realignment is possible if only costing based CO-PA is active.
5. Why PA segment on the sales order is received after upgrading to SFIN ? Why after upgrading to SFIN during settlement of production order, the variances get posted to a PA segment?
During upgrade to SFIN as mentioned earlier (Q1) account based CO-PA should be activated. A PA segment gets created on the sales order automatically when account based CO-PA is active. For the settlement of the production order variances a PA segment gets created automatically if in order for CO-PA to be reconciled with FI, the account based CO-PA is active. Due to PA segment account assignment if additionally the costing based CO-PA is active then to costing-based COPA the record type B gets posted during settlement in addition to the record type C.
6. Unable to generate the operating concern, after upgrading to SFIN 2.0. Why error message KE606 / FCO_COPA014 are received?
In database table ACDOCA (Universal Journal Entry Line Items) at least one new unknown characteristic was added to operating concern XXXX. To activate the database table the runtime needs to be performed in the background as the runtime is very long. With transaction KEA0, the client-independent environment cannot be executed for this reason in the foreground. The step for adding new CO-PA characteristics is transferred to program FCO_ADD_COPA_FIELD_TO_ACDOCA for the database table ACDOCA. After the characteristics are added to database table ACDOCA the client-independent environment can only be fully activated without errors and without errors the database table is activated.
Program FCO_ADD_COPA_FIELD_TO_ACDOCA is executed in the background for operating concern XXXX. The client-independent environment for operating concern XXXX should be generated again when the program has been executed without errors. The availability of the operating concern XXXX can be seen again.
7. Why in SFIN KEQ3 is not available?
In SFIN there is no concept of segment level and non-segment level characteristics, thus, KEQ3 is no longer used. Segment level characteristics are the only characteristics. A new summarization concept comprising ACDOCA and profitability segment summarization is created with sFIN 1503 SPS 1511 and S/4 HANA 1511 OP Edition – in the IMG refer SAP 2179270 and the referenced documentation. For high volume customers like big retailers who need to handle huge data volumes, this was mainly developed. Most customers have no need for summarizing data and the default still is and shall remain.
8. Why in case of postings involving a PA segment CO document is created in SFIN? What purpose does the use of this document serve? Can the creation of CO document be deactivated?
During upgrade to SFIN (refer Q1), account based CO-PA would have been activated. A CO document with account assignment to PSG will be created automatically in the releases prior to SFIN once account based COPA is active and there is posting to a PA segment. In table COEP with the document number, no entry is made in case of SFIN if there is no physical CO document. However we display the CO document as HANA compatibility view as we want to keep the compatibility with the previous releases and hence to read data it is redirected from table ACDOCA and map it to the COEP structure. Since no CO document is really created as in the past the creation of the CO document cannot be deactivated i.e. in COEP table no physical entry. In this case users get the same look and feel that they are used to in previous releases as it’s just a view from table ACDOCA.
9. When trying to change or delete operating concern SFIN Why errors are received?
In S/4 Hana Financials, SAP provided SFIN operating concern as template operating concern. With sFIN 1.0 Operating concern SFIN was shipped and the structure is unchanged, as with the field catalog of this operating concern, the structure of table CE4SFIN needs to coincide. Problems may occur due to changes. In S/4 HANA Finance 1503 Operating concern SFIN furthermore shall not be used at all, as in 2042464 it has been mentioned. Therefore its data structures can only be activated from support package SPS 1508 but in transaction KEA0 it is not adapted any more. In a support package before 1508 changes unfortunately are still possible. However changes should not be made. Do not delete or change it as it is a template operating concern.
10. Some field length's in SAP S/4HANA have been increased to 40 characters. Why in CO-PA the characteristic length has not been increased?
The maximum field length of the material number (MARA-MATNR) has been extended to 40 from 18 characters in SAP S/4HANA, on-premise edition 1511. The material number (ARTNR) in CO-PA is an exception as it is a fixed characteristic and with a length of 40 from S/4HANA it is the only characteristic in CO-PA, on-premise edition 1511. The maximum logical limit on length of CO-PA characteristic is 18 characters. Due to limitation of length of database table, the limit is set. On maximum number of characteristics and value fields this has dependency that can be defined in an operating concern. Therefore due to technical constraints an extension of this length for other characteristics is impossible.
11. Why on the PA segment screen the characteristic 'SEGMENT' is grayed out?
To be able to report on it in SFIN characteristic to the operating concern SEGMENT was added as fixed characteristic. Directly from the profit center SEGMENT characteristic is derived and hence on the PA segment screen it cannot be changeable manually. Furthermore in the profitability segment a manual entry would only be visible but from the CO-PA account assignment screen it would not be returned to the document item to be posted (on the CO-PA account assignment screen the only fields you can enter which are transferred back are the PRCTR, FKBER and for one special case GSBER). Between FI and COPA this would result in inconsistency for an important characteristic like SEGMENT and hence for manual entry it is not open.