| Status | |
| Owner | Soumen Laru |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach of G/L accounts from operational and local CoAs in S/4 HANA.
The document details out the field list, extraction criteria, scoping, mapping of CoA (Chart of Account Object)
Conversion Scope
G/L accounts which will be listed as part of scope list in a data collection template (DCT) with new numbering will be in scope of migration.
An additional mapping file will be prepared as part of GL account mapping from ECC to S4 accounts and that will be used for the subsequent objects.
Note: This object is collected in a DCT ( Data Collection Template ) and therefore, the information below does not have any relevance and it is just for information purpose only.
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | GL Accounts COA | ~2200 | S4HANA | ~700 |
| WP2 | GL Accounts COA | ~2200 | S4HANA | ~700 |
Additional Information
Multi-language Requirement
In the Syensqo Corporate Chart of Accounts, the following four language keys must be maintained:
- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)
Note: For certain countries it may be required to also maintain account descriptions for certain G/L accounts in local language as per regulatory requirement (e.g. Japenese) in the respective country. Such requests must be backed by supporting evidence of the underlying regulatory requirement.
Such data will be collected as part of DCT for the translation texts for GL Accounts.
In Country Chart of Accounts, only the language key of the official language for the country must be maintained. For example, In the country chart of accounts for Chile, the language key for Spanish (ES) must be maintained.
The translated G/L Short Description and Long Description must also be maintained in the corresponding fields.
Document Management
Legal Requirement
A list of countries will need local chart of accounts and here is the list
- France
- Luxembourg
- Peru
- Portugal
- Spain
- Belgium
- Morocco
- Turkey
Special Requirements
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length (Decimals) | Requirement | Syensqo Requirement R = Required : Mandatory field. |
| SKA1 | KTOPL | KTOPL | Chart of Accounts | CHAR | 4 | Key that uniquely identifies a chart of account. At Syensqo, the following naming convention applies: 1.) COCA for the operational corporate CoA 2.) LOXX for country CoAs where XX represents the country code of the country CoA. The global Syensqo operational Chart of Accounts will be assigned as operational Chart of Accounts to all Syensqo entities. A maximum of one local CoA per country is permitted. | R |
| SKA1 | SAKNR | SAKNR | G/L Account Number | CHAR | 10 | The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group. | R |
| SKA1 | GVTYP | GVTYP | P&L Statement Account Type | CHAR | 2 | With the P&L statement account type, you determine the retained earnings account for each P&L account. The retained earnings account is used during year-end closing to calculate the company's result. If you are creating a P&L account, you must make an entry here. | C |
| SKA1 | KTOKS | KTOKS | G/L Account Group | CHAR | 4 | The account group is a classifying feature within the G/L account master records. The account group determines the fields for the entry screens if you create or change a master record in the company code. The account group also determines in which number range the account number must be contained. | R |
| SKA1 | XLOEV | XLOEV | Indicator: Account Marked for Deletion? | CHAR | 1 | Indicator which specifies that master record data is to be deleted. The deletion must be carried out using the program for archiving G/L account master data. This program archives the master records that have been marked for deletion, providing there is no dependent data remaining in the system. | C |
| SKA1 | XSPEA | XSPEA | Indicator: Account Is Blocked for Creation ? | CHAR | 1 | An entry in this field causes the account to be blocked for creation in the specified company code. | C |
| SKA1 | XSPEB | XSPEB | Indicator: Is Account Blocked for Posting? | CHAR | 1 | An entry in this field means that the account is blocked for posting at Chart of Account level. | C |
| SKA1 | XSPEP | XSPEP | Indicator: Account Blocked for Planning ? | CHAR | 1 | An entry in this field causes the account to be blocked for planning. | C |
| SKA1 | FUNC_AREA | FUNC_AREA | Functional Area | CHAR | 16 | The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria: Manufacturing Administration Sales Research and development | C |
| SKA1 | GLACCOUNT_TYPE | GLACCOUNT_TYPE | Type of a General Ledger Account | CHAR | 1 | Specifies the general ledger account type that classifies the general ledger account. The following types are available (Financial Accounting modules where accounts are visible kept in brackets): X - Balance Sheet Account - Asset, liability, or equity B/S account. (FI only) C- Cash Account - Bank G/L Account (FI only) N - Non-operating Expense or Income - Below EBIT P&L Account (FI only) P - Primary Costs or Revenue - Above EBIT P&L Account (FI&CO) S - Secondary Costs - P&L Account (FI&CO) | R |
| SKA1 | GLACCOUNT_SUBTYPE | GLACCOUNT_SUBTYPE | Subtype of a G/L Account | CHAR | 1 | Indicates the usage of an account that has the Cash Account G/L account type. | C |
| SKA1 | MAIN_SAKNR | MAIN_SAKNR | Bank Reconciliation Account | This field indicates the relationship between bank subaccounts and the main reconciliation accounts the bank sub-accounts belong to. This field is only visible for accounts of G/L account subtype ''Bank Subaccount' and is a mandatory input field for those accounts so the system can establish a connection between the sub-accounts and the main bank reconciliation account in the bank ledger. | C | ||
| SKAT | SPRAS | SPRAS | Language Key | CHAR | 1 | Language Key to be picked up for the relevant Language specific description to be maintained E - English (EN) | R |
| SKAT | TXT20 | TXT20 | Short Text | CHAR | 20 | Short description of the G/L account. This should be used to provide a short text that will explain the use of the general ledger account. (Note: When used in reporting, if there is not enough space on the report, the short text can be displayed) | R |
| SKAT | TXT50 | TXT50 | Long Text | CHAR | 50 | Long description of the G/L account. This field should be used to provide a more detailed description of the G/L account that intuitively explains the purpose of the account. | R |
| SKB1 | BUKRS | BUKRS | Company Code | CHAR | 4 | The company code is an organisational unit used in financial accounting representing Syensqo's independent legal entity or other entity as described in the Enterprise Structure Position Paper. | R |
| SKB1 | SAKNR | SAKNR | G/L Account Number | CHAR | 10 | The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group. | R |
| SKB1 | FDGRV | FDGRV | Planning Group | CHAR | 10 | In cash management, G/L accounts as well as customer and vendor accounts are allocated to planning groups by means of an entry made in the master record. This is used for liquidity planning and reporting. | C |
| SKB1 | FDLEV | FDLEV | Planning Level | CHAR | 2 | The planning level is used to control displays in Cash Management. The freely defined field is used to identify specific account groups in cash management. | C |
| SKB1 | FSTAG | FSTAG | Field Status Group | CHAR | 4 | Field statuses are SAP's method to control which fields are required to have data in postings that are made to the general ledger account line items. It controls these fields by selecting them as suppressed, required or optional. Example of the fields are cost centre, text, material number, asset number, etc. - Suppressed: if this is selected, the field is not available for input. - Optional: if this is selected, the field is available for input but isn't mandatory. - Required: if this is selected, the field is mandatory for input. | R |
| SKB1 | MITKZ | MITKZ | Recon. Account for Acct Type | CHAR | 1 | An entry in this field characterises the G/L account as a reconciliation account. The reconciliation means that this G/L account represents a subledger account for Accounts Receivable, Accounts Payable, or Fixed Assets. Only these types of reconciliation accounts should be selected. | C |
| SKB1 | MWSKZ | MWSKZ | Tax Category | CHAR | 2 | Determines whether you want to use the account for tax-relevant postings and which types of taxes are allowed for that General Ledger account. | C |
| SKB1 | WAERS | WAERS | Account currency | CUKY | 5 | The account currency indicates the currency in which this account is held. If a currency other than the company code currency is specified, then you can only post items in that currency to this account e.g. foreign currency bank account or foreign currency loan. If the company code currency is specified, then you can post items in any currency to this account. | R |
| SKB1 | XGKON | XGKON | Relevant to Cash Flow | CHAR | 1 | Indicator that determines that the G/L account is a cash flow-relevant account. | C |
| SKB1 | XINTB | XINTB | Post Automatically Only | CHAR | 1 | This is selected for system accounts i.e. only where postings are made via account determination tables. This will ensure that there are only system postings and no manual adjustments to the account, eg GR/IR, inventory accounts, etc. | C |
| SKB1 | XSPEB | XSPEB | Indicator: Is Account Blocked for Posting? | CHAR | 1 | An entry in this field means that the account is blocked for zum posting. | C |
| SKB1 | XOPVW | XOPVW | Open Item Management | CHAR | 1 | Items posted to accounts managed on an open item basis are marked as open or cleared. The balance of these accounts is always equal to the balance of the open items. | C |
| SKB1 | ZUAWA | ZUAWA | Sort Key | CHAR | 3 | This field determines how the system will populate the default assignment field during document entry. This is then used for information to aid with clearing open items by the allocation field in the document line item. Each G/L account type may require a different key specified here to best facilitate sorting / clearing requirements line items posted to it. Note that the Sort Key only populates the assignment field with a default value, and the assignment field will be overwritten when a new value is entered. This applies to all postings whether manual or interfaced. | C |
| SKB1 | ALTKT | ALTKT | Alternative Account Number | CHAR | 10 | A freely definable field to be used to enter the account number from a country chart of accounts if a country chart of accounts is required for the company code. | C |
| SKB1 | XMWNO | XMWNO | Indicator: Tax code is not a required field | CHAR | 1 | Indicates that the account can still be posted to even if a tax code has not been entered. | C |
| SKB1 | XSALH | XSALH | Balances in Local Crcy Only | CHAR | 1 | Indicates that balances are updated only in local currency (LC) for all postings to the account. You set this indicator for accounts in which you do not want the system to update transaction figures separately by currency. Setting this indicator for accounts managed on an open item basis affects the clearing procedures. Clearing can only be done in local currency if the indicator is set. Setting this indicator for accounts which are line-item managed only affects the foreign currency revaluation. Accounts which only manage balances in local currency will not be taken into consideration in foreign currency revaluation runs towards local currency. | C |
| SKB1 | TOGRU | TOGRU | Tolerance group | CHAR | 4 | Tolerance groups define the limits within which differences are accepted when clearing open items. Where this is active, differences are automatically posted to predefined accounts. Syensqo will use the default tolerance group "Blank" which means no tolerance limits will be specified for clearing. For GR/IR clearing accounts a tolerance group shall be assigned with minimal value tolerances to allow for clearing of open items with minor rounding differences. | C |
| SKB1 | XLGCLR | XLGCLR | Open Item Management by Ledger Group | CHAR | 1 | Determines that journal entry line items are managed on an open item basis by ledger group for this G/L account. | C |
| SKB1 | XKRES | XKRES | Indicator: Can Line Items Be Displayed by Account? | CHAR | 1 | Indicator: Can Line Items Be Displayed by Account? | |
| CSKB | KATYP | KATYP | Cost Element Category | CHAR | 10 | The cost element category determines which cost elements can be used for which business transactions. Primary Cost Element Categories 01: Primary costs / cost-reducing revenues - This cost element category is used for all primary expense postings and requires at least one real cost object to be specified in the line item details. 11: Revenues - This cost element category is used for all revenue postings and requires a Margin Analysis characteristics or real billing elements to be specified as cost objects. 12: Sales Deductions - This cost element category is used for all revenue deduction postings and requires a profit center to be specified as a COPA characteristic.. e.g. Sales Rebates Secondary Cost Element Categories 21: Internal Settlement - This cost element category is used to settle project costs to objects in Controlling (CO), such as profitability segments, cost centers, and WBS elements. 22: External Settlement - This cost element category is used to settle project costs to objects outside of Controlling (CO), such as G/L accounts, Fixed Assets or Materials. 31: Order/Project Results Analysis - Enables order or project results analysis data to be saved to the relevant order or project. 41: Overhead - This cost element category is used to allocate overhead costs from cost centers to orders. 42: Assessments - This cost element category is used to allocate costs during assessment from a sender Cost Center to receivers (Cost Centers or WBS Elements). 43: Internal Activity Allocation - This cost element category is used to allocate costs during internal activity allocation and for allocating process costs via an activity type to a receiver object. Statistical Cost Element Category: 90: Statistical Cost Element for Balance Sheet Account - This cost element category is typically used for Fixed Asset Reconciliation Accounts or inventory accounts to update the Controlling module statistically with line items posted to those accounts for getting full visibility over directly capitalized expenditures in Controlling reports. | C |
| CSKB | MGEFL | MGEFL | Record Quantity | CHAR | 10 | Indicator defining whether the system issues a message if no quantity or quantity unit is specified for a postings. Note: Once you have specified this and a posting has occurred in the leading ledger fiscal year against the particular G/L account that has quantities recorded, although you can change the flag in the G/L account, the system will always use the original value set until the following leading ledger fiscal year. | C |
Data Cleansing
ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
N/A |
Conversion Process
When Data Source denotes DCT, no relevancy and extract rules to be applied in Syniti tool. DCT records will be collected by business Data Consultant.
Data Privacy and Sensitivity
Extraction
This data object does not exist (or cannot be converted from its current state). Therefore, this data is manually collected by the business directly in ADM/Syniti Data Construction page. This is to be conducted using DCT (Data Collection Template) in DSP Migrate.
Extraction Run Sheet
Req # | Requirement description | Team responsible |
1. | Ensure DCT is collected for the GL Accounts COAs based on the collection template and maintained in ADM Construction page | Data team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| N/A |
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for GL Accounts data with exception of some fields which require transformation as mentioned in the transformation rule.GL Account DCT Rules will be used by the data collectors for collecting data, nothing to be done in the Transformation in ADM.
Note: Constructed data will be imported into ADM Data Construction page(s).
There will be three pages -
1. Main page to contain the GL Account details with EN Language key Description
2. 2nd Page contains the Company Code Extension Data
3. Detailed Page will contain descriptions in various languages as they are collected.
DCT 1 ( General data for GL Accounts )
| Table Name | Field Name | Field description | Rule | ToolTip |
| SKA1 | KTOPL | Chart of Accounts | It is a Required Field, details given in the Target Design Segment. | Key that uniquely identifies a chart of account. At Syensqo, the following naming convention applies: 1.) COCA for the operational corporate CoA 2.) LOXX for country CoAs where XX represents the country code of the country CoA. The global Syensqo operational Chart of Accounts will be assigned as operational Chart of Accounts to all Syensqo entities. A maximum of one local CoA per country is permitted. |
| SKA1 | SAKNR | G/L Account Number | It is a Required Field, details given in the Target Design Segment. | The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group. |
| SKA1 | GVTYP | P&L Statement Account Type | It is a Conditional field, details given in the Target Design Segment. | With the P&L statement account type, you determine the retained earnings account for each P&L account. The retained earnings account is used during year-end closing to calculate the company's result. If you are creating a P&L account, you must make an entry here. |
| SKA1 | KTOKS | G/L Account Group | It is a Required Field, details given in the Target Design Segment. | The account group is a classifying feature within the G/L account master records. The account group determines the fields for the entry screens if you create or change a master record in the company code. The account group also determines in which number range the account number must be contained. |
| SKA1 | XLOEV | Indicator: Account Marked for Deletion? | It is a Conditional field, details given in the Target Design Segment. | Indicator which specifies that master record data is to be deleted. The deletion must be carried out using the program for archiving G/L account master data. This program archives the master records that have been marked for deletion, providing there is no dependent data remaining in the system. |
| SKA1 | XSPEA | Indicator: Account Is Blocked for Creation ? | It is a Conditional field, details given in the Target Design Segment. | An entry in this field causes the account to be blocked for creation in the specified company code. |
| SKA1 | XSPEB_SKA1 | Indicator: Is Account Blocked for Posting? | It is a Conditional field, details given in the Target Design Segment. | An entry in this field means that the account is blocked for posting at Chart of Account level. |
| SKA1 | XSPEP | Indicator: Account Blocked for Planning ? | It is a Conditional field, details given in the Target Design Segment. | An entry in this field causes the account to be blocked for planning. |
| SKA1 | FUNC_AREA | Functional Area | It is a Conditional field, details given in the Target Design Segment. | The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria: Manufacturing Administration Sales Research and development |
| SKA1 | GLACCOUNT_TYPE | Type of a General Ledger Account | It is a Required Field, details given in the Target Design Segment. | Specifies the general ledger account type that classifies the general ledger account. The following types are available (Financial Accounting modules where accounts are visible kept in brackets): X - Balance Sheet Account - Asset, liability, or equity B/S account. (FI only) C- Cash Account - Bank G/L Account (FI only) N - Non-operating Expense or Income - Below EBIT P&L Account (FI only) P - Primary Costs or Revenue - Above EBIT P&L Account (FI&CO) S - Secondary Costs - P&L Account (FI&CO) |
| SKA1 | GLACCOUNT_SUBTYPE | Subtype of a G/L Account | It is a Conditional field, details given in the Target Design Segment. | Indicates the usage of an account that has the Cash Account G/L account type. |
| SKA1 | MAIN_SAKNR | Bank Reconciliation Account | It is a Conditional field, details given in the Target Design Segment. | This field indicates the relationship between bank subaccounts and the main reconciliation accounts the bank sub-accounts belong to. This field is only visible for accounts of G/L account subtype ''Bank Subaccount' and is a mandatory input field for those accounts so the system can establish a connection between the sub-accounts and the main bank reconciliation account in the bank ledger. |
| SKAT | SPRAS | Language Key | It is a Required Field, details given in the Target Design Segment. | Language Key to be picked up for the relevant Language specific description to be maintained E - English (EN) |
| SKAT | TXT20 | Short Text | It is a Required Field, details given in the Target Design Segment. | Short description of the G/L account. This should be used to provide a short text that will explain the use of the general ledger account. (Note: When used in reporting, if there is not enough space on the report, the short text can be displayed) |
| SKAT | TXT50 | Long Text | It is a Required Field, details given in the Target Design Segment. | Long description of the G/L account. This field should be used to provide a more detailed description of the G/L account that intuitively explains the purpose of the account. |
DCT 2 ( Company Code Extension for GL Accounts )
| Table Name | Field Name | Field description | Rule | ToolTip |
| SKA1 | KTOPL | Chart of Accounts | It is a Required Field, details given in the Target Design Segment. | Key that uniquely identifies a chart of account. At Syensqo, the following naming convention applies: 1.) COCA for the operational corporate CoA 2.) LOXX for country CoAs where XX represents the country code of the country CoA. The global Syensqo operational Chart of Accounts will be assigned as operational Chart of Accounts to all Syensqo entities. A maximum of one local CoA per country is permitted. |
| SKB1 | BUKRS | Company Code | It is a Required Field, details given in the Target Design Segment. | The company code is an organisational unit used in financial accounting representing Syensqo's independent legal entity or other entity as described in the Enterprise Structure Position Paper. |
| SKB1 | SAKNR | G/L Account Number | It is a Required Field, details given in the Target Design Segment. | The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group. |
| SKB1 | FDGRV | Planning Group | It is a Conditional field, details given in the Target Design Segment | In cash management, G/L accounts as well as customer and vendor accounts are allocated to planning groups by means of an entry made in the master record. This is used for liquidity planning and reporting. |
| SKB1 | FDLEV | Planning Level | It is a Conditional field, details given in the Target Design Segment | The planning level is used to control displays in Cash Management. The freely defined field is used to identify specific account groups in cash management. |
| SKB1 | FSTAG | Field Status Group | It is a Required Field, details given in the Target Design Segment. | Field statuses are SAP's method to control which fields are required to have data in postings that are made to the general ledger account line items. It controls these fields by selecting them as suppressed, required or optional. Example of the fields are cost centre, text, material number, asset number, etc. - Suppressed: if this is selected, the field is not available for input. - Optional: if this is selected, the field is available for input but isn't mandatory. - Required: if this is selected, the field is mandatory for input. |
| SKB1 | MITKZ | Recon. Account for Acct Type | It is a Conditional field, details given in the Target Design Segment. | An entry in this field characterises the G/L account as a reconciliation account. The reconciliation means that this G/L account represents a subledger account for Accounts Receivable, Accounts Payable, or Fixed Assets. Only these types of reconciliation accounts should be selected. |
| SKB1 | MWSKZ | Tax Category | It is a Conditional field, details given in the Target Design Segment. | Determines whether you want to use the account for tax-relevant postings and which types of taxes are allowed for that General Ledger account. |
| SKB1 | WAERS | Account currency | It is a Required Field, details given in the Target Design Segment. | The account currency indicates the currency in which this account is held. If a currency other than the company code currency is specified, then you can only post items in that currency to this account e.g. foreign currency bank account or foreign currency loan. If the company code currency is specified, then you can post items in any currency to this account. |
| SKB1 | XGKON | Relevant to Cash Flow | It is a Conditional field, details given in the Target Design Segment. | Indicator that determines that the G/L account is a cash flow-relevant account. |
| SKB1 | XINTB | Post Automatically Only | It is a Conditional field, details given in the Target Design Segment. | This is selected for system accounts i.e. only where postings are made via account determination tables. This will ensure that there are only system postings and no manual adjustments to the account, eg GR/IR, inventory accounts, etc. |
| SKB1 | XKRES | Line Item Display | System Generated | An entry in this field means that the account is blocked for zum posting. |
| SKB1 | XSPEB_SKB1 | Indicator: Is Account Blocked for Posting? | It is a Conditional field, details given in the Target Design Segment. | Items posted to accounts managed on an open item basis are marked as open or cleared. The balance of these accounts is always equal to the balance of the open items. |
| SKB1 | XOPVW | Open Item Management | It is a Conditional field, details given in the Target Design Segment. | This field determines how the system will populate the default assignment field during document entry. This is then used for information to aid with clearing open items by the allocation field in the document line item. Each G/L account type may require a different key specified here to best facilitate sorting / clearing requirements line items posted to it. Note that the Sort Key only populates the assignment field with a default value, and the assignment field will be overwritten when a new value is entered. This applies to all postings whether manual or interfaced. |
| SKB1 | ZUAWA | Sort Key | It is a Conditional field, details given in the Target Design Segment. | A freely definable field to be used to enter the account number from a country chart of accounts if a country chart of accounts is required for the company code. |
| SKB1 | ALTKT | Alternative Account Number | It is a Conditional field, details given in the Target Design Segment. | Indicates that the account can still be posted to even if a tax code has not been entered. |
| SKB1 | XMWNO | Indicator: Tax code is not a required field | It is a Conditional field, details given in the Target Design Segment. | Indicates that balances are updated only in local currency (LC) for all postings to the account. You set this indicator for accounts in which you do not want the system to update transaction figures separately by currency. Setting this indicator for accounts managed on an open item basis affects the clearing procedures. Clearing can only be done in local currency if the indicator is set. Setting this indicator for accounts which are line-item managed only affects the foreign currency revaluation. Accounts which only manage balances in local currency will not be taken into consideration in foreign currency revaluation runs towards local currency. |
| SKB1 | XSALH | Balances in Local Crcy Only | It is a Conditional field, details given in the Target Design Segment. | Tolerance groups define the limits within which differences are accepted when clearing open items. Where this is active, differences are automatically posted to predefined accounts. Syensqo will use the default tolerance group "Blank" which means no tolerance limits will be specified for clearing. For GR/IR clearing accounts a tolerance group shall be assigned with minimal value tolerances to allow for clearing of open items with minor rounding differences. |
| SKB1 | TOGRU | Tolerance group | It is a Conditional field, details given in the Target Design Segment. | Determines that journal entry line items are managed on an open item basis by ledger group for this G/L account. |
| SKB1 | XLGCLR | Open Item Management by Ledger Group | It is a Conditional field, details given in the Target Design Segment. | Indicator: Can Line Items Be Displayed by Account? |
| CSKB | KATYP | Cost Element Category | It is a Conditional field, details given in the Target Design Segment. | The cost element category determines which cost elements can be used for which business transactions. Primary Cost Element Categories 01: Primary costs / cost-reducing revenues 11: Revenues 12: Sales Deductions Secondary Cost Element Categories 21: Internal Settlement 22: External Settlement 31: Order/Project Results Analysis 41: Overhead 42: Assessments 43: Internal Activity Allocation Statistical Cost Element Category: 90: Statistical Cost Element for Balance Sheet Account |
| CSKB | MGEFL | Record Quantity | It is a Conditional field, details given in the Target Design Segment. | Indicator defining whether the system issues a message if no quantity or quantity unit is specified for a postings. |
DCT 3 ( Language Specific Descriptions for GL Accounts )
GL Account Description in multiple Languages DCT Rules
| Table Name | Field Name | Field description | Rule | Tooltip |
| SKA1 | KTOPL | Chart of Accounts | It is a Required Field, details given in the Target Design Segment. | Key that uniquely identifies a chart of account. At Syensqo, the following naming convention applies: 1.) COCA for the operational corporate CoA 2.) LOXX for country CoAs where XX represents the country code of the country CoA. The global Syensqo operational Chart of Accounts will be assigned as operational Chart of Accounts to all Syensqo entities. A maximum of one local CoA per country is permitted. |
| SKA1 | SAKNR | G/L Account Number | It is a Required Field, details given in the Target Design Segment. | The G/L account number identifies the G/L account in a chart of accounts that must fall into the specified ranges as defined for the respective account group. |
| SKAT | SPRAS | Language Key | It is a Required Field, details given in the Target Design Segment. | Language Key to be picked up for the relevant Language specific description to be maintained E - English (EN) |
| SKAT | TXT20 | Short Text | It is a Required Field, details given in the Target Design Segment. | Short description of the G/L account. This should be used to provide a short text that will explain the use of the general ledger account. (Note: When used in reporting, if there is not enough space on the report, the short text can be displayed) |
| SKAT | TXT50 | Long Text | It is a Required Field, details given in the Target Design Segment. | Long description of the G/L account. This field should be used to provide a more detailed description of the G/L account that intuitively explains the purpose of the account. |
Note: Two construct pages are expected to be created in ADM to store GL Account list and texts in various languages to be stored in the sub-view.
Extraction Dependencies
As this object is fully collected into DCT, the section is not applicable.
Item # | Step description | Team responsible |
1. | N/A |
Transformation
The Target fields are mapped to the applicable DCT field that will be its source.
Note: as this object is DCT, the mapping rule for all the fields is 'Copy' as described in the transform rule section. However, some reports are to be created and executed to ensure integrity in the data collected in DCT as described in 'Pre-load Data Validation' section.
This step identifies the transformation activity required to allow to make the data Target ready:
- Prepare target-ready data in the target structure and format that is required for loading via prescribed Load Tool in the load section.
- Produce the preload reports as requested in the 'Preload Data Validation' section.
Transformation Run Sheet
Item # | Step description | Team responsible |
1. | Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into toolMigrate. | Data team |
2. | In tool, select the object GL_Account | Data team |
3. | Go to Process Area Launch and select the object GL_Account | Data team |
4. | Launch the Objects to execute transformation. | Data team |
5. | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Data team |
6. | Generate Pre-Load reports . | Data team |
7. | Generate data load count. | Data team |
8. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
9. | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
10. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
11. | Analyse and resolve any pre-load defects logged by business. | Data team |
12. | Repeat steps 6 to 11 if necessary | Data team |
13. | Proceed to pre-load validations | Data team |
Transformation Rules
The accounts will be given in a constructed dataset.
Note: Two separate load files to be produced - one for the Local Country Chart of Accounts ( KTOPL <> 'COCA' ) and the other for the Operational Chart of Accounts ( KTOPL = 'COCA' ) . An important point is to be noted here and that is Local/Country chart of account are not extended to company codes and therefore, there is no SKB1 ( company code specific information) for these accounts.
| Rule # | Source system | Source Table | Source Field | Source description | Target system | Target Table | Target Field | Target description | Transformation logic |
| 1 | ECC | SKA1 | KTOPL | Chart of Accounts | S4HANA | SKA1 | KTOPL | Chart of Accounts | Copy From the DCT File |
| 2 | ECC | SKA1 | SAKNR | G/L Account Number | S4HANA | SKA1 | SAKNR | G/L Account Number | Copy From the DCT file |
| 3 | ECC | SKA1 | GVTYP | P&L Statement Account Type | S4HANA | SKA1 | GVTYP | P&L Statement Account Type | Copy From the DCT file |
| 4 | ECC | SKA1 | KTOKS | G/L Account Group | S4HANA | SKA1 | KTOKS | G/L Account Group | Copy From the DCT file |
| 5 | ECC | SKA1 | XLOEV | Indicator: Account Marked for Deletion? | S4HANA | SKA1 | XLOEV | Indicator: Account Marked for Deletion? | Copy From the DCT file |
| 6 | ECC | SKA1 | XSPEA | Indicator: Account Is Blocked for Creation ? | S4HANA | SKA1 | XSPEA | Indicator: Account Is Blocked for Creation ? | Copy From the DCT file |
| 7 | ECC | SKA1 | XSPEB | Indicator: Is Account Blocked for Posting? | S4HANA | SKA1 | XSPEB | Indicator: Is Account Blocked for Posting? | Copy From the DCT file |
| 8 | ECC | SKA1 | XSPEP | Indicator: Account Blocked for Planning ? | S4HANA | SKA1 | XSPEP | Indicator: Account Blocked for Planning ? | Copy From the DCT file |
| 9 | ECC | SKA1 | FUNC_AREA | Functional Area | S4HANA | SKA1 | FUNC_AREA | Functional Area | Copy From the DCT file |
| 10 | ECC | SKA1 | GLACCOUNT_TYPE | Type of a General Ledger Account | S4HANA | SKA1 | GLACCOUNT_TYPE | Type of a General Ledger Account | Copy From the DCT file |
| 11 | ECC | SKA1 | GLACCOUNT_SUBTYPE | Subtype of a G/L Account | S4HANA | SKA1 | GLACCOUNT_SUBTYPE | Subtype of a G/L Account | Copy From the DCT file |
| 12 | ECC | SKA1 | MAIN_SAKNR | Bank Reconciliation Account | S4HANA | SKA1 | MAIN_SAKNR | Bank Reconciliation Account | Copy From the DCT file |
| 13 | ECC | SKAT | TXT20 | Short Text | S4HANA | SKAT | TXT20 | Short Text | Copy From the DCT file |
| 14 | ECC | SKAT | TXT50 | Long Text | S4HANA | SKAT | TXT50 | Long Text | Copy From the DCT file |
| 15 | ECC | SKB1 | BUKRS | Company Code | S4HANA | SKB1 | BUKRS | Company Code | Copy From the DCT file |
| 16 | ECC | SKB1 | SAKNR | G/L Account Number | S4HANA | SKB1 | SAKNR | G/L Account Number | Copy From the DCT file |
| 17 | ECC | SKB1 | FDGRV | Planning Group | S4HANA | SKB1 | FDGRV | Planning Group | Copy From the DCT file |
| 18 | ECC | SKB1 | FDLEV | Planning Level | S4HANA | SKB1 | FDLEV | Planning Level | Copy From the DCT file |
| 19 | ECC | SKB1 | FSTAG | Field Status Group | S4HANA | SKB1 | FSTAG | Field Status Group | Copy From the DCT file |
| 20 | ECC | SKB1 | MITKZ | Recon. Account for Acct Type | S4HANA | SKB1 | MITKZ | Recon. Account for Acct Type | Copy From the DCT file |
| 21 | ECC | SKB1 | MWSKZ | Tax Category | S4HANA | SKB1 | MWSKZ | Tax Category | Copy From the DCT file |
| 22 | ECC | SKB1 | WAERS | Account currency | S4HANA | SKB1 | WAERS | Account currency | Copy From the DCT file |
| 23 | ECC | SKB1 | XGKON | Relevant to Cash Flow | S4HANA | SKB1 | XGKON | Relevant to Cash Flow | Copy From the DCT file |
| 24 | ECC | SKB1 | XINTB | Post Automatically Only | S4HANA | SKB1 | XINTB | Post Automatically Only | Copy From the DCT file |
| 25 | ECC | SKB1 | XSPEB | Indicator: Is Account Blocked for Posting? | S4HANA | SKB1 | XSPEB | Indicator: Is Account Blocked for Posting? | Copy From the DCT file |
| 26 | ECC | SKB1 | XOPVW | Open Item Management | S4HANA | SKB1 | XOPVW | Open Item Management | Copy From the DCT file |
| 27 | ECC | SKB1 | ZUAWA | Sort Key | S4HANA | SKB1 | ZUAWA | Sort Key | Copy From the DCT file |
| 28 | ECC | SKB1 | ALTKT | Alternative Account Number | S4HANA | SKB1 | ALTKT | Alternative Account Number | Copy From the DCT file |
| 29 | ECC | SKB1 | XMWNO | Indicator: Tax code is not a required field | S4HANA | SKB1 | XMWNO | Indicator: Tax code is not a required field | Copy From the DCT file |
| 30 | ECC | SKB1 | XSALH | Balances in Local Crcy Only | S4HANA | SKB1 | XSALH | Balances in Local Crcy Only | Copy From the DCT file |
| 31 | ECC | SKB1 | TOGRU | Tolerance group | S4HANA | SKB1 | TOGRU | Tolerance group | Copy From the DCT file |
| 32 | ECC | SKB1 | XLGCLR | Open Item Management by Ledger Group | S4HANA | SKB1 | XLGCLR | Open Item Management by Ledger Group | Copy From the DCT file |
| 33 | ECC | CSKB | KATYP | Cost Element Category | S4HANA | CSKB | KATYP | Cost Element Category | Copy From the DCT file |
| 34 | ECC | CSKB | MGEFL | Record Quantity | S4HANA | CSKB | MGEFL | Record Quantity | Copy From the DCT file |
Transformation Mapping
As the data for this object is fully collected, there is no need of mapping for any field.Mapping Table Name | Mapping Table Description |
N/A |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
N/A |
Note: Generate Load file into the format of migration cockpit upload template as attached in the Load Segment.
Pre-Load Validation
Project Team
Completeness
Task | Action |
Generation of | Mandatory field check.
|
Record Count | Record Count Confirm the record counts in preload summary report
|
Accuracy
Task | Action |
Mandatory field mapping and transformation | Check all mandatory fields have values configured in the target. |
Business
Completeness
| Task | Action |
|---|---|
| Verify record count in Pre-load reports by region | Confirm the Preload File contains all the records in scope of migration ( Based on list of GL Accounts COAs mapped from old to new ). |
Accuracy
| Task | Action |
|---|---|
| Conversion accuracy | Manual Check to be done. |
Load
Loading will be done through migration cockpit and therefore, data from the transformation export view to be exported into the load file format.
4 export views to be prepared based on the field list from the load template ( Source data for FI - GL account (1).XML ) attached.
- Create export view for the general data of country Chart of Account ( Load Template tab name is 'General Data' ) and applicable for chart of account - KTOPL not equal to 'COCA'.
- Create export view for the general data of operational chart of account ( Load Template tab name is 'General Data' ) and applicable only for Chart of Account - KTOPL 'COCA'
- Create export view for the company code data of operational chart of account (Load Template Tab name is 'Company Code Data' ) - KTOPL not equal to 'COCA'.
- Create export view for the controlling area segment where cost element category is not null. Controlling area is defaulted to 'CO01'. ( Load Template tab name is 'Controlling Area Data') - KTOPL not equal to 'COCA'. Note: Get distinct records for combination Chart of account , GL Account and Controlling area when export view is generated.
- Create export view for the Texts of GL Accounts in various languages ( Load template tab name is 'Account Names' ) - Applicable for all Chart of accounts.
Note: 2nd template(Source data for FI - GL account - extend existing record by new org levels (1).XML ) is attached to just extend to a new company code. ( this is not to be used but can be used on exception basis in case there is a need to extend existing accounts to new company codes )
Source data for FI - GL account (1).xmlSource data for FI - GL account - extend existing record by new org levels (2).xml
The load process includes:
- Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of GL Accounts COA.
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_DCT, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)
Load Run Sheet
Item | Step description | Team responsible |
1 | Ensure the load tools are transported into the correct tool instance. | Data team |
2 | Ensure DCTs and all required mappings are submitted and complete | Data team |
3 | Ensure Pre-load sign-offs are obtained. | Data team |
4 | Execute upload of Local Country GL Accounts COA Object using Migration Cockpit Object for GL Accounts COA Upload | Data team |
5 | Execute upload of Operational GL Accounts COA Object using Migration Cockpit Object for GL Accounts COA Upload | Data team |
5 | Generate the post load reports in tool. | Data team |
6 | Log errors as defects, if any and address resolutions. Close defects. | Data team |
7 | Resolve defects by reupload and re-generate post load reports if necessary. | Data team |
8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
9 | Repeat steps 5 to 7 if necessary. | Data team |
Load Phase and Dependencies
Configuration
Item # | Configuration item |
1. | N/A |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| N/A |
Error Handling
Error type | Error description | Action taken |
N/A |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Reconciliation of Record Count | Record Count Confirm the record counts in Post-Load summary report
|
Accuracy
| Task | Action |
|---|---|
| Check values in key fields for accuracy | Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report. |
Business
Completeness
| Task | Action |
|---|---|
| Record Count Check | Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction code SE16N. |
Accuracy
| Task | Action |
|---|---|
| Spot check | Take a sample list of GL accounts and verify them on the SAP GUI tcode FS00 or using fiori app 'Manage G/L Account Master Data' |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||