| Status |
| ||||||||
| Owner | Soumen Laru | ||||||||
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach of Cost Centre into S/4 HANA.
Conversion ScopeThe document details out the field list, extraction criteria, scoping, mapping of Cost Centre object.
Cost Centres listed for target design as mapping from source to target is the scope of cost centres for migration. All the additional fields are read from source ECC systems for subsequent transformation. will be constructed based on the target design and a DCT (Constructed data based on Data Collection Template) will be provided to Syniti for subsequent processing. Along with the DCT, a mapping file of legacy(ECC) to target(S4) will be provided for dependent master and transaction objects.
Conversion Scope
List of source systems and approximate number of
recordsrecords.
Note: All the cost centres to be migrated will be collected. Therefore, Cost Centres are not going to be extracted from source and details given below is given for information purpose only.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Cost Centre | 7~7,141 | S4HANA | TBD |
| WP2 | Cost Centre | 12~12,229 | S4HANA | TBD |
Additional Information
Multi-language Requirement
Document Management
Legal Requirement
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
Type: Text
Length: 80
Key uniquely identifying a cost center.
Type: Text
Length: 80
When you create an object, the beginning date to which object is valid is defined here.
Type: Date
When you create an object, you use the ending date to define as of when the object is valid.
Type: Date
Language in which cost center texts are saved. If the language is not filled, logon language is used as default to save the cost center text.
Type: Text
Length: 80
General description of the object. The cost center name is used for online displays and evaluations that do not have enough space for the cost center description.
Type: Text
Length: 20
The cost center description is used for online displays and evaluations that have sufficient space.
If the master record does not contain a cost center description, the cost center name is shown instead, where the field is to be displayed.
Type: Text
Length: 40
In this field, you can enter the user ID of the person responsible for the cost center. This user ID is stored in the SAP user master record.
Type: Text
Length: 80
Person responsible for the given cost center.
Type: Text
Length: 20
In this field, you can enter the name of the department to which the cost center belongs. It then can be used for evaluations.
Type: Text
Length: 12
Indicator used to define a cost center category.
The master data of an activity type includes one or more cost center categories. The activity type may be used only by cost centers of the appropriate categories.
You define categories in Customizing. For each category, you can define default values for the "Lock" and "Record quantity" indicators, for transfer to cost center master data.
Type: Text
Length: 80
To create cost centers, you require a structure in master data maintenance to which you can assign cost centers. You create this CO structure, the standard hierarchy, when you create a controlling area. If this hierarchy is not present during controlling area maintenance, the system automatically creates the highest node there.
Type: Text
Length: 80
Type: Text
Length: 80
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
Please note: If this field is not supplied, then the corresponding indicator field "... with fixed assignment" must be left initial.
Type: Text
Length: 16
Key identifying a business area.
A cost center requires a business area allocation in dependency of the company code it is allocated to. If a balance sheet or P&L is to be created for each business area for the company code used (see definition of the company code), you have to enter a business area.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 80
Consider When Calculating Dunning Balance.
Type: Text
Length: 80
Key which together with the controlling area uniquely identifies a profit center.
If profit center accounting is active, it is mandatory to specify profit center.
Type: Text
Length: 80
Indicator defining whether the system issues a message if no quantity or quantity unit is specified for commitment or actual postings.
• The indicator has no effect on planning and quantity updates or on the identification of quantities in reports.
• You must set the indicator if you want to cost using an overhead that is dependent on the unit of measure posted with this cost element.
Note: This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.
Type: Text
Length: 1
Indicator defining whether a cost center is locked for posting with direct costs.
If the indicator is active, no primary costs can be posted to the cost center. You may, however, still use the cost center for evaluations such as summarization, and so on.
Type: Text
Length: 1
Indicator defining whether a cost center is locked for planning with direct costs.
If the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1
In the Syensqo Cost Centres, 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 Cost Centres in local language as per regulatory requirement (e.g. Japanese) 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 Cost Centres.
Document Management
Legal Requirement
Special Requirements
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement | Syensqo Requirement R = Required : Mandatory field. |
| CSKS | KOKRS | KOKRS | Controlling Area | CHAR | 4 | Identifies a self-contained organizational structure for which costs can be managed. Only 1 controlling used for all legal entities. Same value across all systems (same in 3 boxes : Global instance + Composites + China). | R |
| CSKS | KOSTL | KOSTL | Cost Center | CHAR | 10 | Organizational unit in controlling used for internal reporting and responsibility accounting. The Cost center represents in syensqo context either a Plant or a GBS 'non Plant'. The Syensqo Cost Center codification must follow the naming convention. "1 + 4 + 3 + 2" See naming convention in the appendix. Or the first 5 digits represent the Profit center which makes easier the usage of Cost centers (link to the GBU) and the associated reporting (filters on dimensions cost centers / profit centers). Digit #1 = GBU Indicator S=SPEC. POLYMERS or C=COMPOSITE MATERIALS or N=NOVECARE or T=TECHNOLOGY SOLUTIONS or B=CBS... From digit 2 to 5 : 4 char. Company Code OR Plant Code. From difit 6 to 8 : 3 char Function Coding From digit 9 to 10 : 2 char Free to distinguish several cost centers to isolate costs. Illustration : S101016301 | R |
| CSKS | DATBI | DATBI | Valid To Date | DATS | 8 | Date until which the Cost center is valid. | R |
| CSKS | DATAB | DATAB | Valid-From Date | DATS | 8 | Date from which the Cost center is valid. | R |
| CSKS | BKZKP | BKZKP | Lock Indicator for Actual Primary Postings | CHAR | 1 | Activate if need to lock the cost center for actual primary postings (cost element category '01) | R |
| CSKS | PKZKP | PKZKP | Lock Indicator for Plan Primary Costs | CHAR | 1 | Activate if need to lock the cost center for actual primary planning (cost element category '01) | R |
| CSKS | BUKRS | BUKRS | Company Code | CHAR | 4 | Company code of the cost center | R |
| CSKS | KOSAR | KOSAR | Cost Center Category | CHAR | 1 | Classifies the cost center families: Production, overhead... | R |
| CSKS | VERAK | VERAK | Person Responsible | CHAR | 20 | Name or ID of the person responsible for managing the Cost center. | R |
| CSKS | VERAK_USER | VERAK_USER | User Responsible | CHAR | 12 | SAP user ID of the responsible person. | R |
| CSKS | WAERS | WAERS | Currency Key | CUKY | 5 | Currency used in the Cost center. Will follow the legal entity one. | R |
| CSKS | TXJCD | TXJCD | Tax Jurisdiction | CHAR | 15 | Tax Jurisdiction assigned to the cost center. May be used for Canada and US to be confirmed later | O |
| CSKS | PRCTR | PRCTR | Profit Center | CHAR | 10 | Profit center assigned to the cost center | R |
| CSKS | WERKS | WERKS | Plant | CHAR | 4 | Plant assigned to the cost center | O |
| CSKS | LOGSYSTEM | LOGSYSTEM | Logical System | CHAR | 10 | System ID where the record originates or is used. Used for data migration usually. But Cost centers will be uploaded in mass. Good to track the origin for Audit purpose | O |
| CSKS | BKZKS | BKZKS | Lock Indicator for Actual Secondary Costs | CHAR | 1 | Activate if need to lock actual secondary postings (allocation and activity type posting) | C |
| CSKS | BKZER | BKZER | Lock Indicator for Actual Revenue Postings | CHAR | 1 | Activate if a need to lock actual revenue postings on the cost centre (cost element category 11/12) | C |
| CSKS | BKZOB | BKZOB | Lock Indicator for Commitment Update | CHAR | 1 | Activate if a need to lock purchase requisition and purchase order creation on the cost center | C |
| CSKS | PKZKS | PKZKS | Lock Indicator for Plan Secondary Costs | CHAR | 1 | Activate if need to lock planning secondary postings (allocation and activity type posting) | C |
| CSKS | PKZER | PKZER | Lock Indicator for Planning Revenues | CHAR | 1 | Activate if a need to lock actual revenue postings on the cost centre (cost element category 11/12) | C |
| CSKS | MGEFL | MGEFL | Indicator for Recording Consumption Quantities | CHAR | 1 | If there is a need to record quantities for G/L accounts managed by quantity. A good practice if to activate this indicator for all cost centers to be able to track and get quantities | C |
| CSKS | ABTEI | ABTEI | Department | CHAR | 12 | Name or code of the department associated with the Cost center. It will depend on the list of Cost centers : Plants or GBS ones. | R |
| CSKS | NKOST | NKOST | Subsequent Cost Center | CHAR | 10 | Cost center that replaces the current one upon deactivation. Only if change of Cost center. It will not be used in go lives Group 1 or 2 but later on during the run if some PC changes happen. | O |
| CSKS | LAND1 | LAND1 | Country Key | CHAR | 3 | Country code related to the Cost center's location. | O |
| CSKS | ANRED | ANRED | Title | CHAR | 15 | Title (e.g., Mr., Ms.) associated with a contact. | O |
| CSKS | NAME1 | NAME1_GP | Name 1 | CHAR | 35 | First line of the name or company name of the Cost center. Description of the Cost center. | O |
| CSKS | NAME2 | NAME2_GP | Name 2 | CHAR | 35 | Second line of the name or company name. | O |
| CSKS | NAME3 | NAME3_GP | Name 3 | CHAR | 35 | Third line of the name or additional details. | O |
| CSKS | NAME4 | NAME4_GP | Name 4 | CHAR | 35 | Fourth line of the name or additional details. | O |
| CSKS | ORT01 | ORT01_GP | City | CHAR | 35 | City name in the Cost center address. | O |
| CSKS | ORT02 | ORT02_GP | District | CHAR | 35 | District or region in the address. | O |
| CSKS | STRAS | STRAS_GP | Street and House Number | CHAR | 35 | Street name and house number of the Cost center location. | O |
| CSKS | PFACH | PFACH | PO Box | CHAR | 10 | PO Box address. | O |
| CSKS | PSTLZ | PSTLZ | Postal Code | CHAR | 10 | Postal code for the street address. | O |
| CSKS | PSTL2 | PSTL2 | P.O. Box Postal Code | CHAR | 10 | Postal code associated with the PO Box. | O |
| CSKS | REGIO | REGIO | Region (State, Province, County) | CHAR | 3 | State or regional subdivision (used in address). | O |
| CSKS | SPRAS | SPRAS | Language Key | LANG | 1 | Language key used in texts and descriptions. | O |
| CSKS | TELBX | TELBX | Telebox number | CHAR | 15 | Telebox number (rarely used). | O |
| CSKS | TELF1 | TELF1 | First telephone number | CHAR | 16 | Primary contact phone number. | O |
| CSKS | TELF2 | TELF2 | Second telephone number | CHAR | 16 | Secondary contact phone number. | O |
| CSKS | TELFX | TELFX | Fax Number | CHAR | 31 | Fax number. | O |
| CSKS | KHINR | KHINR | Standard Hierarchy Area | CHAR | 12 | Node assignment from the standard hierarchy | R |
| CSKS | BUDGET_CARRYING_COST_CTR | FCO_BUDGET_CARRYING_COST_CTR | Budget-Carrying Cost Center | CHAR | 10 | Budget availability data - The budget owner cost center | O |
| CSKS | AVC_PROFILE | AVC_PROFILE | Budget Availability Control: Profile | CHAR | 6 | Budget availability data - The budget owner cost center | O |
| CSKS | AVC_ACTIVE | AVC_ACTIVE | Budget Availability Control for Cost Centers is Active | CHAR | 1 | Budget availability data - The budget owner cost center | O |
| CSKS | ZZ1_Sub_Function | ZZ1_Sub_Function | Extra custom field to store grouping on a level below the function on the cost center. This can differentiate per function, therefore this field is fee-text - for the controller to decide. | CHAR | 30 | Free text entry | R |
| CSKT | SPRAS | SPRAS | Language Key | CHAR | 1 | Language key used in texts and descriptions. | R |
| CSKT | KTEXT | KTEXT | General Name | CHAR | 20 | General Name in the specific language | R |
| CSKT | KLTXT | KLTXT | Description | CHAR | 40 | Description in the specific language | R |
Data Cleansing
Note: Cleansing is applicable only for business and as the data for this object is collected, cleansing is not relevant for data conversion. It just helps business to reduce the mapping requirements.
ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
N/A |
Conversion Process
The high-level process is represented by the diagram below:
Note: 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
Req # | Requirement description | Team responsible |
1. | Ensure DCT is collected 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 data with exception of some fields which require transformation as mentioned in the transformation rule.
DCT Rules and will be used by the data collectors.
| Table Name | Field Name | Field Description | Requirment |
| CSKS | KOKRS | Controlling Area | Identifies a self-contained organizational structure for which costs can be managed. Only 1 controlling used for all legal entities. Same value across all systems (same in 3 boxes : Global instance + Composites + China). |
| CSKS | KOSTL | Cost Center | Organizational unit in controlling used for internal reporting and responsibility accounting. The Cost center represents in syensqo context either a Plant or a GBS 'non Plant'. The Syensqo Cost Center codification must follow the naming convention. "1 + 4 + 3 + 2" See naming convention in the appendix. Or the first 5 digits represent the Profit center which makes easier the usage of Cost centers (link to the GBU) and the associated reporting (filters on dimensions cost centers / profit centers). Digit #1 = GBU Indicator S=SPEC. POLYMERS or C=COMPOSITE MATERIALS or N=NOVECARE or T=TECHNOLOGY SOLUTIONS or B=CBS... From digit 2 to 5 : 4 char. Company Code OR Plant Code. From difit 6 to 8 : 3 char Function Coding From digit 9 to 10 : 2 char Free to distinguish several cost centers to isolate costs. Illustration : S101016301 |
| CSKS | DATBI | Valid To Date | Date until which the Cost center is valid. |
| CSKS | DATAB | Valid-From Date | Date from which the Cost center is valid. |
| CSKS | BKZKP | Lock Indicator for Actual Primary Postings | Activate if need to lock the cost center for actual primary postings (cost element category '01) |
| CSKS | PKZKP | Lock Indicator for Plan Primary Costs | Activate if need to lock the cost center for actual primary planning (cost element category '01) |
| CSKS | BUKRS | Company Code | Company code of the cost center |
| CSKS | KOSAR | Cost Center Category | Classifies the cost center families: Production, overhead... |
| CSKS | VERAK | Person Responsible | Name or ID of the person responsible for managing the Cost center. |
| CSKS | VERAK_USER | User Responsible | SAP user ID of the responsible person. |
| CSKS | WAERS | Currency Key | Currency used in the Cost center. Will follow the legal entity one. |
| CSKS | TXJCD | Tax Jurisdiction | Tax Jurisdiction assigned to the cost center. May be used for Canada and US to be confirmed later |
| CSKS | PRCTR | Profit Center | Profit center assigned to the cost center |
| CSKS | WERKS | Plant | Plant assigned to the cost center |
| CSKS | LOGSYSTEM | Logical System | System ID where the record originates or is used. Used for data migration usually. But Cost centers will be uploaded in mass. Good to track the origin for Audit purpose |
| CSKS | BKZKS | Lock Indicator for Actual Secondary Costs | Activate if need to lock actual secondary postings (allocation and activity type posting) |
| CSKS | BKZER | Lock Indicator for Actual Revenue Postings | Activate if a need to lock actual revenue postings on the cost centre (cost element category 11/12) |
| CSKS | BKZOB | Lock Indicator for Commitment Update | Activate if a need to lock purchase requisition and purchase order creation on the cost center |
| CSKS | PKZKS | Lock Indicator for Plan Secondary Costs | Activate if need to lock planning secondary postings (allocation and activity type posting) |
| CSKS | PKZER | Lock Indicator for Planning Revenues | Activate if a need to lock actual revenue postings on the cost centre (cost element category 11/12) |
| CSKS | MGEFL | Indicator for Recording Consumption Quantities | If there is a need to record quantities for G/L accounts managed by quantity. A good practice if to activate this indicator for all cost centers to be able to track and get quantities |
| CSKS | ABTEI | Department | Name or code of the department associated with the Cost center. It will depend on the list of Cost centers : Plants or GBS ones. |
| CSKS | NKOST | Subsequent Cost Center | Cost center that replaces the current one upon deactivation. Only if change of Cost center. It will not be used in go lives Group 1 or 2 but later on during the run if some PC changes happen. |
| CSKS | LAND1 | Country Key | Country code related to the Cost center's location. |
| CSKS | ANRED | Title | Title (e.g., Mr., Ms.) associated with a contact. |
| CSKS | NAME1 | Name 1 | First line of the name or company name of the Cost center. Description of the Cost center. |
| CSKS | NAME2 | Name 2 | Second line of the name or company name. |
| CSKS | NAME3 | Name 3 | Third line of the name or additional details. |
| CSKS | NAME4 | Name 4 | Fourth line of the name or additional details. |
| CSKS | ORT01 | City | City name in the Cost center address. |
| CSKS | ORT02 | District | District or region in the address. |
| CSKS | STRAS | Street and House Number | Street name and house number of the Cost center location. |
| CSKS | PFACH | PO Box | PO Box address. |
| CSKS | PSTLZ | Postal Code | Postal code for the street address. |
| CSKS | PSTL2 | P.O. Box Postal Code | Postal code associated with the PO Box. |
| CSKS | REGIO | Region (State, Province, County) | State or regional subdivision (used in address). |
| CSKS | SPRAS | Language Key | Language key used in texts and descriptions. |
| CSKS | TELBX | Telebox number | Telebox number (rarely used). |
| CSKS | TELF1 | First telephone number | Primary contact phone number. |
| CSKS | TELF2 | Second telephone number | Secondary contact phone number. |
| CSKS | TELFX | Fax Number | Fax number. |
| CSKS | KHINR | Standard Hierarchy Area | Node assignment from the standard hierarchy |
| CSKS | BUDGET_CARRYING_COST_CTR | Budget-Carrying Cost Center | Budget availability data - The budget owner cost center |
| CSKS | AVC_PROFILE | Budget Availability Control: Profile | Budget availability data - The budget owner cost center |
| CSKS | AVC_ACTIVE | Budget Availability Control for Cost Centers is Active | Budget availability data - The budget owner cost center |
| CSKS | CSKS-ZZ1_Sub_Function | Subfunction | Extra custom field to store grouping on a level below the function on the cost center. This can differentiate per function, therefore this field is fee-text - for the controller to decide. |
| CSKT | SPRAS | Language Key | Language in Which Texts Are Saved "In the Syensqo Cost centers, the following four language keys must be maintained: Additionally, fill in the name and description for the language key based on following rules: |
| CSKT | KTEXT | General Name | General Name in the specific language |
| CSKT | KLTXT | Description | Description in the specific language |
Descriptions will be collected on multiple languages and therefore a detail page to created and linked to the main page
Table Name | Field Name | Field description | Rule |
| CSKS | KOKRS | Controlling Area | 1 unique value for all PC. |
| CSKS | KOSTL | Cost Center | |
| CSKT | DATBI | Valid To Date | |
| CSKT | SPRAS | Language Key | Language in Which Texts Are Saved "In the Syensqo Cost centers, the following four language keys must be maintained: Additionally, fill in the name and description for the language key based on following rules: |
| CSKT | KTEXT | KTEXT | General Name Max Length of the text allowed: 20 |
| CSKT | LTEXT | LTEXT | Description Max Length of the text allowed: 40 |
Extraction Dependencies
Item # | Step description | Team responsible |
1 | N/A |
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
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 Cost Centre | Data team |
3. | Go to Process Area Launch and Process the Object - Cost Centre - Cost Centre | 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
| Rule # | Source system | Source Table | Source Field | Source description | Target system | Target Table | Target Field | Target description | Transformation logic |
| 1 | ECC-DCT | CSKS | KOKRS | Controlling Area | S4HANA | CSKS | KOKRS | Controlling Area | Copy From DCT as is |
| 2 | ECC-DCT | CSKS | KOSTL | Cost Center | S4HANA | CSKS | KOSTL | Cost Center | Copy From DCT as is |
| 3 | ECC-DCT | CSKS | DATBI | Valid To Date | S4HANA | CSKS | DATBI | Valid To Date | Copy From DCT as is |
| 4 | ECC-DCT | CSKS | DATAB | Valid-From Date | S4HANA | CSKS | DATAB | Valid-From Date | Copy From DCT as is |
| 5 | ECC-DCT | CSKS | BKZKP | Lock Indicator for Actual Primary Postings | S4HANA | CSKS | BKZKP | Lock Indicator for Actual Primary Postings | Copy From DCT as is |
| 6 | ECC-DCT | CSKS | PKZKP | Lock Indicator for Plan Primary Costs | S4HANA | CSKS | PKZKP | Lock Indicator for Plan Primary Costs | Copy From DCT as is |
| 7 | ECC-DCT | CSKS | BUKRS | Company Code | S4HANA | CSKS | BUKRS | Company Code | Copy From DCT as is |
| 8 | ECC-DCT | CSKS | KOSAR | Cost Center Category | S4HANA | CSKS | KOSAR | Cost Center Category | Copy From DCT as is |
| 9 | ECC-DCT | CSKS | VERAK | Person Responsible | S4HANA | CSKS | VERAK | Person Responsible | Copy From DCT as is |
| 10 | ECC-DCT | CSKS | VERAK_USER | User Responsible | S4HANA | CSKS | VERAK_USER | User Responsible | Copy From DCT as is |
| 11 | ECC-DCT | CSKS | WAERS | Currency Key | S4HANA | CSKS | WAERS | Currency Key | Copy From DCT as is |
| 12 | ECC-DCT | CSKS | TXJCD | Tax Jurisdiction | S4HANA | CSKS | TXJCD | Tax Jurisdiction | Copy From DCT as is |
| 13 | ECC-DCT | CSKS | PRCTR | Profit Center | S4HANA | CSKS | PRCTR | Profit Center | Copy From DCT as is |
| 14 | ECC-DCT | CSKS | WERKS | Plant | S4HANA | CSKS | WERKS | Plant | Copy From DCT as is |
| 15 | ECC-DCT | CSKS | LOGSYSTEM | Logical System | S4HANA | CSKS | LOGSYSTEM | Logical System | Copy From DCT as is |
| 16 | ECC-DCT | CSKS | BKZKS | Lock Indicator for Actual Secondary Costs | S4HANA | CSKS | BKZKS | Lock Indicator for Actual Secondary Costs | Copy From DCT as is |
| 17 | ECC-DCT | CSKS | BKZER | Lock Indicator for Actual Revenue Postings | S4HANA | CSKS | BKZER | Lock Indicator for Actual Revenue Postings | Copy From DCT as is |
| 18 | ECC-DCT | CSKS | BKZOB | Lock Indicator for Commitment Update | S4HANA | CSKS | BKZOB | Lock Indicator for Commitment Update | Copy From DCT as is |
| 19 | ECC-DCT | CSKS | PKZKS | Lock Indicator for Plan Secondary Costs | S4HANA | CSKS | PKZKS | Lock Indicator for Plan Secondary Costs | Copy From DCT as is |
| 20 | ECC-DCT | CSKS | PKZER | Lock Indicator for Planning Revenues | S4HANA | CSKS | PKZER | Lock Indicator for Planning Revenues | Copy From DCT as is |
| 21 | ECC-DCT | CSKS | MGEFL | Indicator for Recording Consumption Quantities | S4HANA | CSKS | MGEFL | Indicator for Recording Consumption Quantities | Copy From DCT as is |
| 22 | ECC-DCT | CSKS | ABTEI | Department | S4HANA | CSKS | ABTEI | Department | Copy From DCT as is |
| 23 | ECC-DCT | CSKS | NKOST | Subsequent Cost Center | S4HANA | CSKS | NKOST | Subsequent Cost Center | Copy From DCT as is |
| 24 | ECC-DCT | CSKS | LAND1 | Country Key | S4HANA | CSKS | LAND1 | Country Key | Copy From DCT as is |
| 25 | ECC-DCT | CSKS | ANRED | Title | S4HANA | CSKS | ANRED | Title | Copy From DCT as is |
| 26 | ECC-DCT | CSKS | NAME1 | Name 1 | S4HANA | CSKS | NAME1 | Name 1 | Copy From DCT as is |
| 27 | ECC-DCT | CSKS | NAME2 | Name 2 | S4HANA | CSKS | NAME2 | Name 2 | Copy From DCT as is |
| 28 | ECC-DCT | CSKS | NAME3 | Name 3 | S4HANA | CSKS | NAME3 | Name 3 | Copy From DCT as is |
| 29 | ECC-DCT | CSKS | NAME4 | Name 4 | S4HANA | CSKS | NAME4 | Name 4 | Copy From DCT as is |
| 30 | ECC-DCT | CSKS | ORT01 | City | S4HANA | CSKS | ORT01 | City | Copy From DCT as is |
| 31 | ECC-DCT | CSKS | ORT02 | District | S4HANA | CSKS | ORT02 | District | Copy From DCT as is |
| 32 | ECC-DCT | CSKS | STRAS | Street and House Number | S4HANA | CSKS | STRAS | Street and House Number | Copy From DCT as is |
| 33 | ECC-DCT | CSKS | PFACH | PO Box | S4HANA | CSKS | PFACH | PO Box | Copy From DCT as is |
| 34 | ECC-DCT | CSKS | PSTLZ | Postal Code | S4HANA | CSKS | PSTLZ | Postal Code | Copy From DCT as is |
| 35 | ECC-DCT | CSKS | PSTL2 | P.O. Box Postal Code | S4HANA | CSKS | PSTL2 | P.O. Box Postal Code | Copy From DCT as is |
| 36 | ECC-DCT | CSKS | REGIO | Region (State, Province, County) | S4HANA | CSKS | REGIO | Region (State, Province, County) | Copy From DCT as is |
| 37 | ECC-DCT | CSKS | SPRAS | Language Key | S4HANA | CSKS | SPRAS | Language Key | Copy From DCT as is |
| 38 | ECC-DCT | CSKS | TELBX | Telebox number | S4HANA | CSKS | TELBX | Telebox number | Copy From DCT as is |
| 39 | ECC-DCT | CSKS | TELF1 | First telephone number | S4HANA | CSKS | TELF1 | First telephone number | Copy From DCT as is |
| 40 | ECC-DCT | CSKS | TELF2 | Second telephone number | S4HANA | CSKS | TELF2 | Second telephone number | Copy From DCT as is |
| 41 | ECC-DCT | CSKS | TELFX | Fax Number | S4HANA | CSKS | TELFX | Fax Number | Copy From DCT as is |
| 42 | ECC-DCT | CSKS | KHINR | Standard Hierarchy Area | S4HANA | CSKS | KHINR | Standard Hierarchy Area | Copy From DCT as is |
| 43 | ECC-DCT | CSKS | BUDGET_CARRYING_COST_CTR | Budget-Carrying Cost Center | S4HANA | CSKS | BUDGET_CARRYING_COST_CTR | Budget-Carrying Cost Center | Copy From DCT as is |
| 44 | ECC-DCT | CSKS | AVC_PROFILE | Budget Availability Control: Profile | S4HANA | CSKS | AVC_PROFILE | Budget Availability Control: Profile | Copy From DCT as is |
| 45 | ECC-DCT | CSKS | AVC_ACTIVE | Budget Availability Control for Cost Centers is Active | S4HANA | CSKS | AVC_ACTIVE | Budget Availability Control for Cost Centers is Active | Copy From DCT as is |
| 46 | ECC-DCT | CSKS | ZZ1_Sub_Function | Subfunction | S4HANA | CSKS | ZZ1_Sub_Function | Subfunction | Copy From DCT as is |
| 47 | ECC-DCT | CSKT | SPRAS | Language Key | S4HANA | CSKT | SPRAS | Language Key | Copy From DCT as is |
| 48 | ECC-DCT | CSKT | KTEXT | General Name | S4HANA | CSKT | KTEXT | General Name | Copy From DCT as is |
| 49 | ECC-DCT | CSKT | KLTXT | Description | S4HANA | CSKT | KLTXT | Description | Copy From DCT as is |
Transformation Mapping
Note: This object will include the preparation of a mapping table for old to new cost centers.
Mapping Table Name | Mapping Table Description |
Cost Centre | Old to New Cost Centre |
Indicator controlling whether the cost center is locked against postings of secondary costs.
Use
If the indicator is active, you cannot post secondary costs to the cost center from now on.
This indicatory normally locks the cost center only against actual debits of secondary costs. However, actual credits to the cost center are possible.
Type: Text
Length: 1
Defines whether a cost center is locked for planning with secondary costs.
Use
If you select this indicator, you cannot plan any secondary costs on the affected cost center from this time.
The indicator normally locks the cost center only against debits with secondary costs in the plan. However, you can still credit the cost center in the plan.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1
Indicator defining whether a cost center is locked for posting with revenues.
If the indicator is active, you cannot post revenues to the affected cost center.
If the indicator is inactive, the revenues are written to the cost center as statistics only.
Type: Text
Length: 1
Indicator controlling whether a cost center is locked for planning with revenues:
•Active No revenue planning on the affected cost center
•Inactive Revenues recorded on the cost centers as statistics
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1
Indicator defining whether a commitment is updated for the cost center.
If the indicator is active, no commitments can be updated to the affected cost center.
Type: Text
Length: 1
Template for activity-independent formula planning.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for activity-dependent formula planning.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for the activity independent activity allocation of cost centers.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for the activity dependent activity allocation for cost centers.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for Independent Actual Statistical Key figure.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for dependent Actual Statistical Key figure.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Controls the calculation of overhead.
Use
You must store one costing sheet for each object for which the R/3 System is to determine overhead costs.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 6
Cost center, which receives a budget and, which plans and tracks expenses for a set of cost centers.
The budget-carrying cost center can be either the cost center itself or another cost center with the same company code.
Example 1: Cost center A has a budget and is responsible for its budget and costs only.
Cost Center Budget-Carrying Cost Center Company Code
A A 1010
Example 2: Cost center B has a budget and cost centers B, C, and D consume this budget.
Cost Center Budget-Carrying Cost Center Company Code
B B 1020
C B 1020
D B 1020
The field is only relevant when Universal Parallel Accounting activation.
Type: Text
Length: 80
The budget availability control profile brings all parameters together, which are necessary for you to actively control your budget.
The field is only relevant in case of Universal Parallel Accounting activation.
Type: Text
Length: 80
When you select this option, costs incurred are compared with the available budget for the budget-carrying cost center. This comparison is based on the settings in the budget availability control profile.
Availability control can be activated only on the budget-carrying cost center.
If you don't activate the availability control, you can still use the cost center budget report to track the expenses.
To enable this reporting option, enter the budget-carrying cost center and the budget availability control profile for cost centers.
Before you can activate budget availability control for cost centers, you must maintain budget availability control profile for cost centers in the following Customizing activity:
Maintain Budget Availability Control Profile for Cost Centers
The field is only relevant in case of Universal Parallel Accounting activation.
Type: Text
Length: 1
Title for Address data.
Type: Text
Length: 15
Name 1 of the customer/supplier address.
Type: Text
Length: 35
Name 2 of the customer/supplier address.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 35
Name 3 of the customer/supplier address.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 35
Name 4 of the customer/supplier address.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 35
Street and house number as part of the address.
Type: Text
Length: 35
This field contains the postal (zip) code for the house address (street and city).
Type: Text
Length: 10
Postal code needed to allocate the P.O. Box.
Use
This field is used for a country/region where:
- the postal code (zip code) used to send letters to a customer's/vendor's P.O. Box is different to that used to send letters to a customer's/vendor's company address.
- large companies have their own postal code and no P.O. Box.
Type: Text
Length: 10
PO Box for address.
Type: Text
Length: 10
Name of the city as a part of the address.
Type: Text
Length: 35
Supplement to city name or district.
Use
The entry is appended to the city name with a hyphen by the automatic address formatting function.
(Exceptions: Germany, United Kingdom/Ireland and Japan)
Type: Text
Length: 35
The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number.
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.
Type: Text
Length: 80
In some countries/regions, the region forms part of the address. The meaning depends on the country/region.
Type: Text
Length: 80
Max. length of input must not exceed 15 digits.
The tax jurisdiction is used for determining the tax rate. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied.
If Vertex is activated (esp. on US installations) the tax jurisdiction code will be determined by the business object's address. If the given postal code/Zip code is not accurate as possible, Vertex will determine more than one tax jurisdiction code for one record, the migration of this record will fail. You will then get the error message "No unique jurisdiction code can be determined".
Type: Text
Length: 15
The language key indicates:
- the language in which texts are displayed,
- the language in which you enter texts,
- the language in which the system prints texts.
Type: Text
Length: 80
Number of telebox for electronic mail.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 15
First telephone number
Type: Text
Length: 16
Second telephone number for communication.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 16
Number under which a business partner's telefax machine can be reached.
Use
The number is used by the system if you send a message by telefax to your business partner from within an SAP transaction.
Type: Text
Length: 31
Number under which a business partner's teletex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
Use
The number is determined by the SAP system if you send a teletex message to your business partner from within an SAP transaction.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 30
Number under which the telex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 30
Data communication line no.
Line number (telephone line). Dialing this number enables you to establish a link with another computer at a different location.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 14
Name of the printer where the cost center report is to be printed.
When mass reports are created, each cost center and cost center area can receive the corresponding reports from the local printers.
Type: Text
Length: 4
A joint venture in the SAP System is a summarization of cost objects whose costs are split up among partners.
A joint venture is usually lead by an operating authority, who is responsible for the costs incurred. At the end of a period, all of the costs incurred are split up and allocated to the partners involved.
Joint ventures are created to keep costs as low as possible for the operating authority and the partners. This is achieved by distributing the costs incurred to the participants of the joint venture.
Type: Text
Length: 80
In global companies that belong to joint ventures, incurred costs are usually shared among different recovery indicators which can then be dealt with in different ways using the periodic settlement program. You can define recovery indicators at three different levels:
- Document type
- Cost element (primary and secondary)
- Cost object
When you make a posting in one of the feeder systems of the Joint Venture Accounting system, all three levels are evaluated in the sequence defined. The first recovery indicator found is transferred to the Joint Venture Accounting system.
Example:
- Costs that are 100 % allocable
- Costs borne 100 % by the operator
- Overheads applied by the operator
- Costs which exceed a contractually agreed price and cannot therefore be allocated
- Costs already allocated
Type: Text
Length: 80
Type: Text
Length: 80
Type: Text
Length: 80
Data Cleansing
ID
Criticality
Error Message/Report Description
Rule
Output
Source System
1.
Can load, but business process will fail
Open Item is overdue and aged
TBD
Report
PF2 / PI2 / WP2
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
Req #
Requirement description
Team responsible
1.
Ensure source tables BKPF, BSIS are extracted in tool according to the agreed cut-off date in the project plan
Data team
2.
Perform preliminary completeness check documented in section 5.2.8.1.1
Data team
3.
Raise issues as defects if Req # 1 to 2 are not met
Data team
4.
Repeat Req # 1 to 3 if required
Data team
5.
Report extraction result to person in charge of APOI conversion
Data team
Selection Screen
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
Field Name
Field description
Rule
Type: Text
Length: 80
Cost Center*
Key uniquely identifying a cost center.
Type: Text
Length: 80
When you create an object, the beginning date to which object is valid is defined here.
Type: Date
When you create an object, you use the ending date to define as of when the object is valid.
Type: Date
Language in which cost center texts are saved. If the language is not filled, logon language is used as default to save the cost center text.
Type: Text
Length: 80
General description of the object. The cost center name is used for online displays and evaluations that do not have enough space for the cost center description.
Type: Text
Length: 20
The cost center description is used for online displays and evaluations that have sufficient space.
If the master record does not contain a cost center description, the cost center name is shown instead, where the field is to be displayed.
Type: Text
Length: 40
In this field, you can enter the user ID of the person responsible for the cost center. This user ID is stored in the SAP user master record.
Type: Text
Length: 80
Person responsible for the given cost center.
Type: Text
Length: 20
In this field, you can enter the name of the department to which the cost center belongs. It then can be used for evaluations.
Type: Text
Length: 12
Indicator used to define a cost center category.
The master data of an activity type includes one or more cost center categories. The activity type may be used only by cost centers of the appropriate categories.
You define categories in Customizing. For each category, you can define default values for the "Lock" and "Record quantity" indicators, for transfer to cost center master data.
Type: Text
Length: 80
Hierarchy Area*
To create cost centers, you require a structure in master data maintenance to which you can assign cost centers. You create this CO structure, the standard hierarchy, when you create a controlling area. If this hierarchy is not present during controlling area maintenance, the system automatically creates the highest node there.
Type: Text
Length: 80
Company Code*
Type: Text
Length: 80
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
Please note: If this field is not supplied, then the corresponding indicator field "... with fixed assignment" must be left initial.
Type: Text
Length: 16
Key identifying a business area.
A cost center requires a business area allocation in dependency of the company code it is allocated to. If a balance sheet or P&L is to be created for each business area for the company code used (see definition of the company code), you have to enter a business area.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 80
Consider When Calculating Dunning Balance.
Type: Text
Length: 80
Key which together with the controlling area uniquely identifies a profit center.
If profit center accounting is active, it is mandatory to specify profit center.
Type: Text
Length: 80
Indicator defining whether the system issues a message if no quantity or quantity unit is specified for commitment or actual postings.
• The indicator has no effect on planning and quantity updates or on the identification of quantities in reports.
• You must set the indicator if you want to cost using an overhead that is dependent on the unit of measure posted with this cost element.
Note: This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.
Type: Text
Length: 1
Indicator defining whether a cost center is locked for posting with direct costs.
If the indicator is active, no primary costs can be posted to the cost center. You may, however, still use the cost center for evaluations such as summarization, and so on.
Type: Text
Length: 1
Indicator defining whether a cost center is locked for planning with direct costs.
If the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1
Indicator controlling whether the cost center is locked against postings of secondary costs.
Use
If the indicator is active, you cannot post secondary costs to the cost center from now on.
This indicatory normally locks the cost center only against actual debits of secondary costs. However, actual credits to the cost center are possible.
Type: Text
Length: 1
Defines whether a cost center is locked for planning with secondary costs.
Use
If you select this indicator, you cannot plan any secondary costs on the affected cost center from this time.
The indicator normally locks the cost center only against debits with secondary costs in the plan. However, you can still credit the cost center in the plan.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1
Indicator defining whether a cost center is locked for posting with revenues.
If the indicator is active, you cannot post revenues to the affected cost center.
If the indicator is inactive, the revenues are written to the cost center as statistics only.
Type: Text
Length: 1
Indicator controlling whether a cost center is locked for planning with revenues:
•Active No revenue planning on the affected cost center
•Inactive Revenues recorded on the cost centers as statistics
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 1
Indicator defining whether a commitment is updated for the cost center.
If the indicator is active, no commitments can be updated to the affected cost center.
Type: Text
Length: 1
Template for activity-independent formula planning.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for activity-dependent formula planning.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for the activity independent activity allocation of cost centers.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for the activity dependent activity allocation for cost centers.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for Independent Actual Statistical Key figure.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Template for dependent Actual Statistical Key figure.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 10
Controls the calculation of overhead.
Use
You must store one costing sheet for each object for which the R/3 System is to determine overhead costs.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 6
Cost center, which receives a budget and, which plans and tracks expenses for a set of cost centers.
The budget-carrying cost center can be either the cost center itself or another cost center with the same company code.
Example 1: Cost center A has a budget and is responsible for its budget and costs only.
Cost Center Budget-Carrying Cost Center Company Code
A A 1010
Example 2: Cost center B has a budget and cost centers B, C, and D consume this budget.
Cost Center Budget-Carrying Cost Center Company Code
B B 1020
C B 1020
D B 1020
The field is only relevant when Universal Parallel Accounting activation.
Type: Text
Length: 80
The budget availability control profile brings all parameters together, which are necessary for you to actively control your budget.
The field is only relevant in case of Universal Parallel Accounting activation.
Type: Text
Length: 80
When you select this option, costs incurred are compared with the available budget for the budget-carrying cost center. This comparison is based on the settings in the budget availability control profile.
Availability control can be activated only on the budget-carrying cost center.
If you don't activate the availability control, you can still use the cost center budget report to track the expenses.
To enable this reporting option, enter the budget-carrying cost center and the budget availability control profile for cost centers.
Before you can activate budget availability control for cost centers, you must maintain budget availability control profile for cost centers in the following Customizing activity:
Maintain Budget Availability Control Profile for Cost Centers
The field is only relevant in case of Universal Parallel Accounting activation.
Type: Text
Length: 1
Title for Address data.
Type: Text
Length: 15
Name 1 of the customer/supplier address.
Type: Text
Length: 35
Name 2 of the customer/supplier address.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 35
Name 3 of the customer/supplier address.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 35
Name 4 of the customer/supplier address.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 35
Street and house number as part of the address.
Type: Text
Length: 35
This field contains the postal (zip) code for the house address (street and city).
Type: Text
Length: 10
Postal code needed to allocate the P.O. Box.
Use
This field is used for a country/region where:
- the postal code (zip code) used to send letters to a customer's/vendor's P.O. Box is different to that used to send letters to a customer's/vendor's company address.
- large companies have their own postal code and no P.O. Box.
Type: Text
Length: 10
PO Box for address.
Type: Text
Length: 10
Name of the city as a part of the address.
Type: Text
Length: 35
Supplement to city name or district.
Use
The entry is appended to the city name with a hyphen by the automatic address formatting function.
(Exceptions: Germany, United Kingdom/Ireland and Japan)
Type: Text
Length: 35
The country/region key contains information which the system uses to check entries such as the length of the postal code or bank account number.
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.
Type: Text
Length: 80
In some countries/regions, the region forms part of the address. The meaning depends on the country/region.
Type: Text
Length: 80
Max. length of input must not exceed 15 digits.
The tax jurisdiction is used for determining the tax rate. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied.
If Vertex is activated (esp. on US installations) the tax jurisdiction code will be determined by the business object's address. If the given postal code/Zip code is not accurate as possible, Vertex will determine more than one tax jurisdiction code for one record, the migration of this record will fail. You will then get the error message "No unique jurisdiction code can be determined".
Type: Text
Length: 15
The language key indicates:
- the language in which texts are displayed,
- the language in which you enter texts,
- the language in which the system prints texts.
Type: Text
Length: 80
Number of telebox for electronic mail.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 15
First telephone number
Type: Text
Length: 16
Second telephone number for communication.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 16
Number under which a business partner's telefax machine can be reached.
Use
The number is used by the system if you send a message by telefax to your business partner from within an SAP transaction.
Type: Text
Length: 31
Number under which a business partner's teletex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
Use
The number is determined by the SAP system if you send a teletex message to your business partner from within an SAP transaction.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 30
Number under which the telex machine can be reached.
Teletex is a service for the transmission of text and data. In comparison with a telex, however, the transmission times of teletex messages are shorter and the range of characters available is greater.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 30
Data communication line no.
Line number (telephone line). Dialing this number enables you to establish a link with another computer at a different location.
The field cannot be used when Universal Parallel Accounting is activated.
Type: Text
Length: 14
Name of the printer where the cost center report is to be printed.
When mass reports are created, each cost center and cost center area can receive the corresponding reports from the local printers.
Type: Text
Length: 4
A joint venture in the SAP System is a summarization of cost objects whose costs are split up among partners.
A joint venture is usually lead by an operating authority, who is responsible for the costs incurred. At the end of a period, all of the costs incurred are split up and allocated to the partners involved.
Joint ventures are created to keep costs as low as possible for the operating authority and the partners. This is achieved by distributing the costs incurred to the participants of the joint venture.
Type: Text
Length: 80
In global companies that belong to joint ventures, incurred costs are usually shared among different recovery indicators which can then be dealt with in different ways using the periodic settlement program. You can define recovery indicators at three different levels:
- Document type
- Cost element (primary and secondary)
- Cost object
When you make a posting in one of the feeder systems of the Joint Venture Accounting system, all three levels are evaluated in the sequence defined. The first recovery indicator found is transferred to the Joint Venture Accounting system.
Example:
- Costs that are 100 % allocable
- Costs borne 100 % by the operator
- Overheads applied by the operator
- Costs which exceed a contractually agreed price and cannot therefore be allocated
- Costs already allocated
Type: Text
Length: 80
Type: Text
Length: 80
Type: Text
Length: 80
Extraction Dependencies
Item #
Step description
Team responsible
1
Cost Centre Mapping containing any enrichments like new cost centre hierarchy is given
Business and Data
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
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 Cost Centre | Data team |
3. | Go to Process Area Launch and Process the Object - Cost Centre - Cost Centre | 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
Rule #
Source system
Source Table
Source Field
Source description
Target system
Target Table
Target Field
Target description
Transformation logic
Transformation Mapping
Mapping Table Name
Mapping Table Description
Company Code
Mapping of legacy company codes to target system value
Cost Centre Hierarchy
Mapping of legacy Cost Centre Hierarchy
Profit Centre
Mapping of legacy Profit Center to target system value
Currency Key
Mapping of legacy currency keys to target system value
Cost Centre Category
Mapping of legacy Cost Centre Category to New Cost Centre Category
Person Responsible
Map of Legacy Person Responsible to new person Responsible or new position
User Responsible
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Constructed Data of Cost Centre is Received | Data Team |
| 2 | Profit Centre Loading is Carried out | Data Team |
| 3 | Value Mapping Files are received | Data Team and Business |
| Carried out | Data Team |
Pre-Load Validation
Project Team
Completeness
Task | Action |
Generation of | Mandatory field check. Cost Centre Hierarchy Mapped Person Responsible Mapped Cost Centre Category Mapped Cost Centre user Responsible Mapped |
Reconciliation of total | Record Count Summary of Record Counts from Constructed dataset, Valid and Invalid record set. |
Accuracy
Task | Action |
Mandatory field mapping and transformation | Review the data report to ensure mapping value is not missing in tool. |
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 the DCT (Data Construction Template) |
Pre-Load Validation
Project Team
Completeness
Task | Action |
Generation of | Mandatory field check. Cost Centre Hierarchy Mapped Person Responsible Mapped Cost Centre Category Mapped Cost Centre user Responsible Mapped |
Reconciliation of total | Record Count Summary of Record Counts from Constructed dataset, Valid and Invalid record set. |
Accuracy
Task
Action
Mandatory field mapping and transformation
Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.
Review the data report to ensure mapping value is not missing in tool.
Capture errors in the Data Error report.
Business
Completeness
In legacy system, execute report AP Line Item Display (t/code: FS10N ) with selection parameters stated in section 7.2.
Group the output of the report by Company Code, GL Account and Profit Centre using subtotal function and compare the count in this report against the TB Balance ( PY ) count in the pre-load file.
The record count for TB Balance ( PY ) may also be done on the more granular level. The recommended granular level or the subtotal fields can consist of: Company Code, Vendor, Profit Centre, Document Currency Key, Company ID for Trading Partner.
If any of the count is different, raise defect and flag the relevant record as error.Accuracy
| Task | Action |
|---|---|
| Conversion accuracy | Verify GL Open Lines Profit Centres are transformed accurately as per endorsed transformation/mapping rules. Review error reports in tool for any mismatch or missing transformed values. In legacy system, execute report FBL3N If any of the sum is different, raise defect and flag the relevant record as error. |
| Business partner balance on Company code and profit center level | Check the total open item amount on Business partner at Company Code and Profit center level, against the total in legacy by Document, Local and Group currency. Apply currency rules where applicable |
rules. Review error reports in tool for any mismatch or missing transformed values. |
Load
Loading will be done through migration cockpit and therefore, data from the transformation export view to be exported into the load file format.
export views to be prepared based on the field list from the load template attached.
Note: Load
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Additional export view for the descriptions in additional languages to be created as is from detail page DCT
Note: Description translation will be loaded using tcode SE63. LSMW will be created based on the tcode SE63 to enable mass upload of this data. However, further checks will be done to check if some Fiori App could be used for uploading.
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 tool Trial Balance 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. | Controlling area related configuration |
2. | Standard Hierarchy Maintained |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1073 | Profit centre |
Error Handling
Error type | Error description | Action taken |
Profit Centre does not exist | Profit centre does not exist in company code | Ensure the profit centre mapping is correct and or create the profit centre if it is valid |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Reconciliation of Record Count | Confirm all the Cost Centres listed in the Construction file (DCT ) are part of target load file. |
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. Any mismatch will be reported under the Post Load - Error report. Each Column will have Source field, target field and Matching Status. ( XXXX_ECCDCT, XXXX_S4HANA, XXXX_MATCH). A loading status field to show the record is loaded in S/4HANA. Also, a field to unmatched fields in the Post-Load file. |
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 will check list of Cost Centre by extracting data from CSKS table using tcode SE16N. |
Accuracy
| Task | Action |
|---|---|
| Complete Check | Post-Load File contains matching status of each field. |
| Spot check | Business should choose some business partners and perform comprehensive check of open items, payment terms etc Such partners should have huge number of open items or be critical for payment runs in S4 or have certain complexity in conversion. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|
