LSMW for Assigning Characteristics Profile to Merchandise Categories

IS-Retail: LSMW for Assigning Characteristic Profile to Merchandise Category


2

TABLE OF CONTENTS

STEP1: INITIAL SCREEN ................................................................................................................................ 3

STEP 2: MAINTAIN OBJECT ATTRIBUTES ................................................................................................... 4

STEP 3: MAINTAIN SOURCE STRUCTURES ................................................................................................ 5

STEP 4: MAINTAIN SOURCE FIELDS ............................................................................................................ 6

STEP 5: MAINTAIN STRUCTURE RELATIONS ............................................................................................. 8

STEP 6: MAINTAIN FIELD MAPPINGS AND CONVERSION RULES ........................................................... 9

STEP 7: SPECIFY FILES ............................................................................................................................... 13

STEP 8: ASSIGN FILES ................................................................................................................................. 15

STEP 9: READ DATA ..................................................................................................................................... 16

STEP 10: DISPLAY READ DATA .................................................................................................................. 18

STEP 11: CONVERT DATA ........................................................................................................................... 19

STEP 12: DISPLAY CONVERTED DATA ...................................................................................................... 24

STEP 13: START IDOC GENERATION ......................................................................................................... 25

STEP 14: START IDOC PROCESSING ......................................................................................................... 26

STEP 15: CREATE IDOC OVERVIEW ........................................................................................................... 27


3

STEP1: INITIAL SCREEN

Project YG_LSMW Subproject SUBPRJ Object MERCH_PROFILE


4

STEP 2: MAINTAIN OBJECT ATTRIBUTES

IDoc (Intermediate Document) Message Type CLFMAS Basic Type CLFMAS02


5

STEP 3: MAINTAIN SOURCE STRUCTURES

There will be one header and one item source structure: MERCHCATSRCHDR Header ITEM Item


6

STEP 4: MAINTAIN SOURCE FIELDS


7

Header Structure

Field Name Type Length Description

RECORDNO C 4 Record Number

OBJEK C 50 OBJEK

MSGFN C 3 Function

OBTAB C 10 OBTAB

KLART C 3 KLART

MAFID C 1 Record type

OBJECT_TABLE C 30 OBJECT_TABLE

Item Structure

Field Name Type Length Description

RECORDNO C 4 Record Number

CLASS C 18 Class number

DATUV C 8 Character field, 8 characters long

STATU C 1 Classification status

KEY_DATE C 8 Key date


8

STEP 5: MAINTAIN STRUCTURE RELATIONS

SAP structures

Source structure

E1OCLFM MERCHCATSRCHDR

E1KSSKM MERCHCATSRCITEM

E1DATEM MERCHCATSRCHDR


9

STEP 6: MAINTAIN FIELD MAPPINGS AND CONVERSION RULES

Control record Information

In order to see complete details of below control record reated information , click on variant butoon and select all checkboxes :

EDI_DC40 - IDoc Control Record for Interface to External System

Fields Description ,Rule and Code

TABNAM Name of Table Structure

Rule : Default Settings

Code: EDI_DC40-TABNAM = 'EDI_DC40_U'.

MANDT Client


Code: EDI_DC40-MANDT = SY-MANDT.

DOCNUM IDoc number


Code: if p_trfcpt = yes or sy-saprl >= '46A'.

EDI_DC40-DOCNUM = g_cnt_transactions_transferred + 1.

endif.


10

DOCREL SAP Release for IDoc


Code: EDI_DC40-DOCREL = SY-SAPRL.

STATUS Status of IDoc

DIRECT Direction


Code: EDI_DC40-DIRECT = '2'.

OUTMOD Output mode

EXPRSS Overriding in inbound processing

TEST Test flag

IDOCTYP Name of basic type

Rule : Default Settings Modified

Code: EDI_DC40-IDOCTYP = g_idoctyp.

CIMTYP Extension (defined by customer)


Code: EDI_DC40-CIMTYP = g_cimtyp.

MESTYP Message type


Code: EDI_DC40-MESTYP = g_mestyp.

MESCOD Message code


Code: EDI_DC40-MESCOD = g_mescod

MESFCT Message Function


Code: EDI_DC40-MESFCT = g_mesfct.

STD EDI standard, flag

SNDPOR Sender port (SAP System, external subsystem)


Code: if p_filept = yes. EDI_DC40-SNDPOR = g_fileport. elseif p_trfcpt = yes. EDI_DC40-SNDPOR = g_trfcport. endif.

SNDPRT Partner type of sender


Code: EDI_DC40-SNDPRT = 'LS'.

SNDPFC Partner Function of Sender

SNDPRN Partner Number of Sender


Code: EDI_DC40-SNDPRN = g_partnernr.

SNDSAD Sender address (SADR)

SNDLAD Logical address of sender

RCVPOR Receiver port


Code: concatenate 'SAP' sy-sysid into EDI_DC40-RCVPOR.

RCVPRT Partner Type of Receiver


11


Code: EDI_DC40-RCVPRT = g_partnertype.

RCVPFC Partner function of recipient

RCVPRN Partner Number of Receiver


Code: EDI_DC40-RCVPRN = g_partnernr.

RCVSAD Recipient address (SADR)

RCVLAD Logical address of recipient

CREDAT Created on


Code: EDI_DC40-CREDAT = SY-DATUM.

CRETIM Created at


Code: EDI_DC40-CRETIM = SY-UZEIT.

REFINT Transmission file (EDI Interchange)

REFGRP Message group (EDI Message Group)

REFMES Message (EDI Message)

ARCKEY Key for external message archive

SERIAL Serialization

E1OCLFM Master Object Classification Lets consider MSGFN as constant 009 Original: First message for process

MSGFN Function

Source: MERCHCATSRC-MSGFN (Function)

Rule : Transfer (MOVE)

Code: E1OCLFM-MSGFN = 009

OBTAB Name of database table for object

Source: MERCHCATSRC-OBTAB ()


Code: E1OCLFM-OBTAB = MERCHCATSRC-OBTAB.

OBJEK Key of object to be classified

Source: MERCHCATSRC-OBJEK ()


Code: E1OCLFM-OBJEK = MERCHCATSRC-OBJEK.

KLART Class Type

Source: MERCHCATSRC-KLART ()


Code: E1OCLFM-KLART = MERCHCATSRC-KLART.

MAFID Indicator: Object/Class

Source: MERCHCATSRC-MAFID ()


Code: E1OCLFM-MAFID = MERCHCATSRC-MAFID.


12

E1KSSKM Distribution Classification: Object Class Assignment Lets consider MSGFN as constant 009 Original: First message for process

MSGFN Function



Code: E1KSSKM-MSGFN = 009

CLASS Class number

Source: MERCHCATSRC-CLASS (Class number)


Code: E1KSSKM-CLASS = MERCHCATSRC-CLASS.

AENNR Change Number

DATUV Valid-From Date

Source: MERCHCATSRC-DATUV (Character field, 8 characters long)


Code: E1KSSKM-DATUV = MERCHCATSRC-DATUV.

STATU Classification status

Source: MERCHCATSRC-STATU (Classification status)


Code: E1KSSKM-STATU = MERCHCATSRC-STATU

.

E1DATEM Master Key Date and Change Number

MSGFN Function



Code: E1DATEM-MSGFN = MERCHCATSRC-MSGFN.

KEY_DATE Current Date of Application Server

Source: MERCHCATSRC-KEY_DATE (Key date)


Code: E1DATEM-KEY_DATE = SY-DATUM


13

STEP 7: SPECIFY FILES

Local file path will be provided : Header C:\CharProfile_To_MerchCat_TestData_header.txt Item C:\ CharProfile_To_MerchCat_TestData_item.txt Imported Data File for Imported Data (Application Server) Imported Data YG_LSMW_SUBPRJ_MERCH_PRFTST.lsmw.read Converted Data File for Converted Data (Application Server) Converted Data YG_LSMW_SUBPRJ_MERCH_PRFTST.lsmw.conv


14

File Layout with sample test data Header: RECORDNO OBJEK MSGFN OBTAB KLART MAFID OBJECT_TABLE

1 ZM0003 9 MARA 026 K MARA

File Layout with sample test data Item: RECORDNO CLASS DATUV STATU

1 A32030102 1

1 A32010102 1

1 A32040102 1

Sample Tab delimited text file:

CharProfile_to_MerchCat_Header.txt

CharProfile_to_MerchCat_Item.txt

Local file path will be provided:

Header C:\CharProfile_To_MerchCat_TestData_header.txt Item C:\ CharProfile_To_MerchCat_TestData_item.txt Imported Data File for Imported Data (Application Server) Imported Data YG_LSMW_SUBPRJ_MERCHLOAD.lsmw.read Converted Data File for Converted Data (Application Server) Converted Data YG_LSMW_SUBPRJ_MERCHCHLOAD.lsmw.conv


15

STEP 8: ASSIGN FILES

Assign the respective files defined in Step 7 to the source structures


16

STEP 9: READ DATA

Read the data file uploaded on above step


17


18

STEP 10: DISPLAY READ DATA


19

STEP 11: CONVERT DATA

Before Processing step : “Convert data” , Pls make sure to maintain File Port and Partner Type and Partner No. Settings using Idoc Inbound Processing menu :


20

Maintain Ports:


21


22


23


24

STEP 12: DISPLAY CONVERTED DATA


25

STEP 13: START IDOC GENERATION


26

STEP 14: START IDOC PROCESSING


27

STEP 15: CREATE IDOC OVERVIEW

In order to verify if Characteristic Profile has been assigned to Merchandise Category, use transaction WG24 and enter merchandise category or follow below mentioned path in SAP Easy Access using tcode W10T:


28


29


30

© 2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP

products and services mentioned herein as well as their respective

logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if

any. Nothing herein should be construed as constituting an additional

warranty.

www.sap.com

LSMW for Assigning Characteristics Profile to Merchandise Categories

Documents

Transcript of LSMW for Assigning Characteristics Profile to Merchandise Categories