Sei sulla pagina 1di 6

Ericsson Internal

SAP TECHNICAL SPECIFICATION 1 (6)


Prepared (also subject responsible if other) No.

Manohar Potnuru
Approved Checked Date Rev Reference

Venkat Chinnam 2020-09-20

TS - MDG - CUSTOMER MASTER DATA FIELDS &


MAINTENACE RULES

Contents

1 Solution Overview........................................................................................2
1.1 Basic information............................................................................................2
1.2 Purpose & description....................................................................................2
1.3 Contacts......................................................................................................... 3
1.4 Reference documents....................................................................................4
2 Document history.........................................................................................4
2.1 TS creation..................................................................................................... 4
2.2 TS modification..............................................................................................4
3 Detailed solution description......................................................................4
3.1 Transportable object list.................................................................................4
3.2 Solution description........................................................................................ 5
3.3 SAP Enhancement Implementations..............................................................5
3.4 Virtual Forge Code Quality check...................................................................5
4 Error processing.......................................................................................... 7
5 Implementation / cycle zero requirements.................................................7
5.1 <Cycle zero step 1>.......................................................................................7
6 Execution information.................................................................................7
7 Unit Test Plan............................................................................................... 7
8 APPENDIX..................................................................................................... 7
8.1 Appendix A..................................................................................................... 7

Instructions for use of this template: Replace blue text between chevrons (<,>) below. Do not
remove other blue text that is provided for guidance.
Ericsson Internal
SAP TECHNICAL SPECIFICATION 2 (6)
Prepared (also subject responsible if other) No.

Manohar Potnuru
Approved Checked Date Rev Reference

Venkat Chinnam 2020-09-20

1 Solution Overview
This section is mandatory for approval purposes. Try to fit sections 1.1 and 1.2 on one page.

This is to Create an IDOC Mapping from ONE system to MDG specifically for Data
Migration

1.1 Basic information

Demand number / ALM Original Request Id NA

Demand name/title 3PP NPP WORKFLOW PROCESS

Development type(s) Data Migration/IDOC Mapping

Organization(s) affected NA

System(s) / Solution(s) affected NA

Where prototyped? F07/400 , F08/400

Where developed? F07/400 , F08/400

Cycle zero No

Batch job created via program? No

Batch job setup/change required for any No


standard / custom program?

Index creation / modification required? No

1.2 Purpose & description

ZBTA material type materials needs to be migrated from ONE system to MDG system

1.2.1 Existing Solution

NA-Not Applicable

1.2.2 Issue in Existing Solution

NA-Not Applicable
Ericsson Internal
SAP TECHNICAL SPECIFICATION 3 (6)
Prepared (also subject responsible if other) No.

Manohar Potnuru
Approved Checked Date Rev Reference

Venkat Chinnam 2020-09-20

1.2.3 Proposed Solution

 Extend IDOC with custom segments at MARA Level and at MARC Level

Contacts
Enter at least IT Supplier Design lead, Technical and ITTE. Then provide EAI, legacy, 3rd party, etc
if appropriate.

Role Name Email Tel no


IT Technical Product
manager (TPM)
Approver
IT Technical Product
manager (TPM)
Demand Owner
Process Owner
IT Supplier – Design
lead
IT Supplier - Manohar Manohar.potnuru@tcs.com
Developer

Remark regarding Approval handling:

The TS should be sent to the Monthly Release team for review and approval (mrreview@in.ibm.com).

1.3 Reference documents


Enter at least reference to Consolidated Design Document for which this TS is written.

Document filename / Type (SOD, SDD, Comment (description, location, …)


Link from Eridoc Test scripts, etc.)
SOD SOD
SDD SDD

2 Document history
This section is mandatory for approval purposes.

2.1 TS creation

Created by Manohar Potnuru

Creation date 20 september 2020

2.2 TS modification

TS modified by Modified date Sections Description of change SAP tech


Ericsson Internal
SAP TECHNICAL SPECIFICATION 4 (6)
Prepared (also subject responsible if other) No.

Manohar Potnuru
Approved Checked Date Rev Reference

Venkat Chinnam 2020-09-20

(yyyy-mm-dd) updated approver

Manohar 20 sep 2020 Initial version


Potnuru

3 Detailed solution description


This section is mandatory for approval purposes. This is where the technical details of your solution should
be described. E.g. Design rational; Components that form the solution; Pseudo-code for program logic; Etc.

Custom Segments were created at MARA level and at MARC level.

MARA level: ZMDG_MARA_EXT

MARC Level: ZMDG_MARC_EXT

IDOC extension done for MATMAS05: ZMDG_MATMAS05_EXT.

The above extensions were used to migrate the materials from SAP ONE system to
MDG system specifically for Migration activity.

3.1 Transportable object list


To provide a quick overview for a developer, provide a list of transportable objects touched. Do not provide
detail description in this table, as that should be provided in section 3.2

Object name Object type Created / Short


amended comment if
appl.

ZMDG_MARC_EXT Customizing Created Segmnt


created in
both systems
ZMDG_MARA_EXT Customizing Created Segment
created in
both systems
ZMDG_MATMAS05_EXT Customizing Created Extension
created in
both systems
ZXSBDU01 Program Enhanced Under the exit
ALE00001,
created in
ONE system
for outbound
Purpose
ZXMGVU04 Program Enhanced Under the exit
MGV00001 in
MDG system
for Inbound
purpose
Ericsson Internal
SAP TECHNICAL SPECIFICATION 5 (6)
Prepared (also subject responsible if other) No.

Manohar Potnuru
Approved Checked Date Rev Reference

Venkat Chinnam 2020-09-20

3.2 Solution description

Main objective is to map the below mentioned field which needs to be


mapped.

MARA level mapping    


     
F07 F08  
ZZMTART ZTARMTART  
ZZP_CODE ZZMVGRL  
ZZTRAC_AB ZZSERNP based on field SERNP( Y for Z001, Y for Z002 )
ZZVERPR_DE MAKT-MAKTX based on the material description in english, deleting leading '/'
ZZVERPR_NO EINA-IDNLF  
     
MARC Level
Mapping    
     
ZMDM_STAWN-
ZZHSCODET STAWN based on region and material
ZZCONORG HERKL  
ZZTRACAB MARC-SERNP based on field SERNP( Y for Z001, Y for Z002 )

User exit: ALE00001 was used in order to map the above fields from ONE
system to the ZMDG_MARA_EXT and ZMDG_MARC_EXT.

Logic for field ZZVERPR_NO:

If the material numbers does not start with ‘INH801’, then pass material
number itself as the vendor product number.

Else.

Fetch IDNLF from EINA table and map it to vendor product number. Here we
need to eliminate the vendors which start with 1 series and also deleted
vendors. Also pick up the latest info record.

User exit: MGV00001 was used to map the fields to MARA, MARC fields
based on the extensions ZMDG_MARA_EXT and ZMDG_MARC_EXT.
Ericsson Internal
SAP TECHNICAL SPECIFICATION 6 (6)
Prepared (also subject responsible if other) No.

Manohar Potnuru
Approved Checked Date Rev Reference

Venkat Chinnam 2020-09-20

Class:Method used to MAP MARA fields :


zcl_mdg_mm_idoc_ext_util=>fill_inb_mara_ext_data

Class:Method used to MAP MARC fields :


zcl_mdg_mm_idoc_ext_util=>fill_inb_marc_ext_data

NA

4 Error processing

5 Implementation / cycle zero requirements


N/A

5.1 <Cycle zero step 1>

5.2 N/A

6 Execution information

7 Unit Test Plan

8 APPENDIX
N/A

8.1 Appendix A

N/A