You are on page 1of 24

Company Internal 1(24)

FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11
Prepared by Date
IBM/CGIGE DAMODARAN RAMACHANDRAN 2012-04-24
Contents responsible if other than preparer Remarks
This document is managed in metaDoc.This document is managed
Approved by in metaDoc.ReferenceThis document is managed in metaDoc.

DDS for 6426 Global Reorg 2015 - FI


Solution area: FI

Version: PA1

Revision History
Version Date Description Author
PA1 FS creation

Note: Any hard copy of this document is for reference only. Due to template and application dependencies the header and footer may fail to display correct
data. It is the responsibility of the user to ensure that they have a correct and valid version. Any outdated hard copy is invalid and must be removed from
possible use.
Company Internal 2(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Content

1 Purpose..............................................................................................
2 High-Level Scope...............................................................................
3 Assumptions.......................................................................................
4 Dependencies.....................................................................................
5 Solution Proposal...............................................................................
6 Realignment activity performed in ERP SDMM area........................
7 Realignment activity performed in ERP FI area.............................21
8 Realignment activity performed in CRM area...................................28
9 Realignment activity performed in SAP BW area..............................42
10 Realignment activity performed in SAP APO....................................45
10.1 Realignment in APO DP&WDSB...................................................45
10.2 CPFR................................................................................................56
10.3 KRH..................................................................................................56
10.4 Spare Parts Planning........................................................................57
10.5 Accessories DP Planning..................................................................57
10.6 Accessories SNP Planning...............................................................64
11 Realignment activity performed in JIBE............................................64
11.1 Master Data Alignment.....................................................................69
11.2 Transaction Data Alignment..............................................................70
12 Realignment activity performed in RDP............................................73
12.1 Change Customer names.................................................................73
12.2 Delete Country..................................................................................73
12.3 Change Country - Customer Unit Link.............................................73
12.4 Rename LC name and LC code.......................................................75
12.5 Rename Customer unit name and Customer unit code....................75
12.6 To Move the Customers, FO and FU from an CU to another CU......77
12.7 To move users of One LC to another LC...........................................77
12.8 To Delete LC.....................................................................................78
12.9 To Create new Customer unit...........................................................78
12.10 To Move an LC from one region to another Region..........................79
12.11 Delete Customer...............................................................................79
12.12 To mark an IC3 as In-active (Temporary removal of IC3)..................80
12.13 Sourcing...........................................................................................80
13 Realignment activity performed in .NET............................................81
13.1 Sales Deduction Tool........................................................................81
13.2 Dashboard........................................................................................83
13.3 Multi Chart........................................................................................83
Company Internal 3(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

13.4 Demand planning.............................................................................83


14 Realignment of PMM module............................................................84
14.1 PMM Manage Prices:.......................................................................84
14.2 PMM Analytics:.................................................................................84
14.3 PMM Deal Manager:.........................................................................84
14.4 The forthcoming changes for APAC Reorg:......................................84
15 Realignment activity performed in PORTAL......................................86
16 Realignment activity performed in HPDD..........................................86
17 Relevant Reference Documents.......................................................88
17.1 Test Scripts/Use Cases.....................................................................89
17.2 Impact Analysis.................................................................................89
17.3 Risks.................................................................................................89
17.4 Regression Test Approach................................................................89
17.5 Testing Requirements.......................................................................89
17.6 Implementation Effort........................................................................89
17.7 Out of Scope.....................................................................................90
18 Authorization / Security Requirements..............................................90
19 Organizational Impacts.....................................................................92
20 Documentation & Communication Updates......................................92
21 Performance Considerations............................................................92
22 Outstanding Issues...........................................................................92
23 Appendix..........................................................................................92
23.1 Resource Estimate...........................................................................92
23.2 Further Technical Information...........................................................92

1 Master Data

1.1 Customer Master Data

Responsible : ERP SDMM

The master data shall be based on the new Sales hierarchy.

The customer master data has to be provided by the SDMM team in


concurrence with SM.
Company Internal 4(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

1.2 Cost center master data

Responsible : ERP FI
New cost centers may be required both from sales and warranty cost
perspective. The cost center master data and Cost center groups data will
be maintained by IBM in D37 and Q37. FMDG team is responsible for
maintaining the same in P37. This information needs to be identified by the
business and communicated by SM.

1.3 Profit center master data

Responsible : ERP FI
The Profit center master data and Profit center groups data will be
maintained by IBM in D37 and Q37. FMDG team is responsible for
maintaining the same in P37. This information needs to be identified by the
business and communicated by SM.

1.4 Updation of OKB9 table

Responsible : ERP FI
This information needs to be identified by the business and communicated
by SM. If any changes, provided by the business at the time of Build,
updating in SAP is done by IBM

1.5 Updation of OBCC table

Responsible : ERP FI
This information needs to be identified by the business and communicated
by SM. If any changes, provided by the business at the time of Build,
updating in SAP is done by IBM.

2 Updation of Derivation Rules


Responsible : ERP FI

Transaction code: KEDR

Change the derivation rule in Step 30 :


Company Internal 5(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

The existing derivation rules are changed according to the new reorg.

The input file for both the existing and to be added/changed values for the
KEDR derivation rules for step 30.

The derivation rules are uploaded in the below link:

http://metadoc.sonyericsson.net/?DOCS=75/00651-LXE108238

3 Changes in CoPA

3.1 Align CoPA data

Not in scope of FI

3.2 Realignment of Profitability Analysis data

Responsible : ERP FI
Company Internal 6(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Set up realignment run in transaction code KEND using selection


characteristics such as Customer, Distribution Channel, Division, Planning
and Sales org. Derive characteristics such as Customer group, Sales
Group, Sales office and Sales district.

Run realignment in Profitability analysis to update historical sales and


margin data according to the new organization.

Simulation in S37:

3.2.1 Customer master data before Reorg

Customer Master Data 1343 in transaction XD03 with Sales district 000006,
Sales office 0006 and Customer group 06.

3.2.2 Check the table CE4BT01

In table CE4BT01, four entries are seen.


Company Internal 7(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

3.2.3 Customer master data after Reorg

Master Data is changed in the Sales area (fields Sales office with 0002,
Sales district 000002 and Customer group 02).

3.2.4 Perform Realignment Run

Realignment in KEND for the customer 1343 selecting the parameters Sales
district, Sales office and Customer group for both Actual and Plan values.
Company Internal 8(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

3.2.5 Check the Background Job in SM37

Background job is created in SM37

Check the spool to find the results. It shows the number of transactions
changed.
Company Internal 9(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

3.2.6 Check the status in KEND

In KEND the status is successful


Company Internal 10(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

3.2.7 Check the table CE4BT01

Check the entries in table CE4BT01. The Sales office, Sales district and
Customer group are updated. The number of entries should be the same as
it showed before the realignment in KEND.

3.3 Execute Summarization Job

Run the summarization job by copying job


ZO_GLOB_PA_REBUILD_SUM_LEVEL_NEW in transaction code SM37.

BW is responsible for reload data.

3.4 CoPA Reports

3.4.1 Activation of Regional CoPA Reports

Responsible: ABAP

Transaction Y_D37_83000800 should be assigned to report YP-WATER RC

Transaction Y_D37_83000808 should be assigned to report YP-PROADJ


RC

Transaction Y_D37_83000813 should be assigned to report YP-CMT RC.


Company Internal 11(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Note: But, going by the Transaction code, currently for the transaction
Y_D37_83000800 the report is YP-WATER RC1 (which is deviating from
above report YP-WATER RC). Same is applicable for transactions
Y_D37_83000808 which is assigned to report YP-PROADJ-RN,
Y_D37_83000813 which is assigned to report YP-CMT RC1 currently.

For Transaction Y_D37_803000800 the below report is seen currently which


is to be changed to YP-WATER RC

For Transaction Y_D37_803000808 the below report is seen currently which


is to be changed to YP-PROADJ RC
Company Internal 12(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

For Transaction Y_D37_803000813 the below report is seen currently which


is to be changed to YP-CMT RC
Company Internal 13(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

The above transactions need to be linked to the mentioned reports


respectively in the respective node mentioned below in Transaction
ZSEMC.
Company Internal 14(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Transaction Y_D37_83000800 should be placed above Transaction


Y_D37_83000801

Transaction Y_D37_83000808 should be placed above Transaction


Y_D37_83000809

Transaction Y_D37_83000813 should be placed above Transaction


Y_D37_83000814

3.4.2 Changes in the layout of Regional CoPA Reports

Responsible: SAP FI

The field Customer Group shall be newly inserted and the field company
code shall be removed from the selection screen. The characteristic
Customer Group should be added to the navigation list in the report.
Company Internal 15(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Report YP-WATER RC in Q37 (before Reorg)

The field Company code should be removed and the field Customer Group
should be inserted in the selection parameters as below (as simulated in
S37) so that the report is run at Customer group level.

Report YP-WATER RC in S37 (after Reorg)

The characteristic Customer group should be selected from characteristics


list and selected as variable.
Company Internal 16(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

The Customer group will now be seen in the Variables tab.

The characteristic Customer group should be made available in the report


output in the navigation list also, so it is made optional in the selection
parameters. Therefore the variable Customer group should be made
optional in KE3E.
Company Internal 17(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

The report should handle multiple Sales offices (feature already available).

Report YP-PROADJ RC

The field company code should be removed and Customer group be added
to the selection screen. The report should display Customer group in the
navigation list. The report should handle multiple Sales offices (feature
already available). Same changes are applicable as illustrated with report
YP-WATER RC.

Before Reorg:
Company Internal 18(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Report YP-CMT RC

The field company code is removed and Customer group is added to the
selection screen. The report should display Customer group in the
navigation list. The report should handle multiple Sales offices (feature
already available). Same changes are applicable as illustrated with report
YP-WATER RC

Before Reorg:

3.4.3 Changes in the layout of MU CoPA Reports

Responsible: SAP FI

The reports with transactions Y_D37_83000801 (report YP-WATER RC1),


Y_D37_83000809 (report YP-PROADJ-RN) and Y_D37_83000814 (YP-
CMT RC1) are Customer Unit reports.

Report YP-WATER RC1 (Y_D37_83000801) in Q37 before Reorg:


Company Internal 19(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

When executed, the characteristic Customer group is not available in the


navigation list.

Because, the characteristic Customer group was not selected in the report
from the characteristic list as below:

Report YP_WATER RC1 (Y_D37_83000801) after Reorg (simulated in


S37):
Company Internal 20(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

The name of the report should be changed from Customer unit control to
Market unit control.

The characteristic Customer group should be available in the navigation list


when the report is executed.

In the report, the characteristic Customer group is selected from the


characteristics list. The name of the report should be changed: Customer
unit control should be changed to Market unit control.

When the report is executed:


Company Internal 21(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

Report name is changed and the characteristic Customer group is seen in


the navigation list.

3.4.4 Changes in the Transaction names of CoPA Reports

Responsible: ABAP

The Transaction names for Y_D37_830000801, Y_D37_83000809 and


Y_D37_83000814 should be changed from Customer unit control to Market
unit control in ZSEMC transaction node.
Company Internal 22(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

4 Master Data Stock Protection & Recon Tool (ZSP and


ZSD00083)
Responsible: Security Team

4.1 Report ZSP

The ZSP report is handled by SDMM team. Not in FI scope.

4.2 Report ZSD00083

The security team to update the appropriate roles.


Company Internal 23(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

4.3 Changes in the field label in Report ZSD00083

Responsible: SAP ABAP

The field label CU is changed to MU.

The enhancement for this Z transaction has been done in the report
ZSDR0126R. The technical team is responsible for making changes in the
field label CU to MU in the selection screen.

5 ABS Restatement (Non IBM task)


ABS restatement is handled by CC&MR (SEMC business).

6 Pricing Condition Requirement


Responsible: SDMM

Kindly refer to the below link updated by SDMM

http://metadoc.sonyericsson.net/?DOCS=401/10262-LXE108238
Company Internal 24(24)
FUNCTIONAL SPEC.
Document number Revision
1/155 17-191/FCP 119 0007 Uen PB11

7 Check WCMS confirmation program

SM shall communicate to WCMS Team not to transmit any file to SAP during
the downtime for the Go live. In case if any transmission happens, then the
below job is to be executed manually.

If ERP P37 is locked during realignment batch program


ZD_FI_IC0176_WCMS_PAYMENT has to be run manually.

Instruction to manually run confirmation program:

Microsoft Office
Word 97 - 2003 Document