DEVELOPMENT SPECIFICATION
MARKDOWN INDICATOR IN WP_PLU IDOC
PROJECT IDENTIFICATION
Project Name
Customer Name
Maison Implementation
Maison Joint Stock Company
Abeo-Electra Project Manager
Customer Project Manager
Lam Quoc Dat
Triet Tran
DOCUMENT IDENTIFICATION

Version and Status:
o 0.0 Working
o 1.0 Review
o 2.0 Released
o 3.0 Final
o 4.0 Technical Specification
Author
Filename
Amit Tunara
Maison_E007_Markdown_Indicator_in_WP_PLU_IDoc_v1.0
Version
Status
Date (YYYY-MM-DD)
Document Classification
1.0
Release for
Development
17.11.2015
Confidential
REVISION HISTORY
Version
Date
Description
1.0
17.11.2015
Released for Development
REVIEW AND APPROVAL
Name
Документ1
Role
Signature
Date
Page 1 of 10
TABLE OF CONTENT
1.
NOTATION ................................................................................................................... 3
2.
PROCESS REQUIREMENTS * .................................................................................... 4
2.1
Functional Design .................................................................................................. 4
2.2
Test Scenario ........................................................................................................ 5
Документ1
Page 2 of 10
1. Notation




* indicates mandatory sections to be filled by the functional owner
* indicates optional sections to be filled by the functional owner
** indicates mandatory sections to be filled by the development team
** indicates optional sections to be filled by the development team
Документ1
Page 3 of 10
2. Process Requirements *
2.1 Functional Design
2.1.1 Functional Area
*
POS Integration
2.1.2 Short Description
For Maison, it has been decided to use WP_PLU IDoc for downloading the article prices. In SAP when the
markdown plan is activated, it also creates VKP0 pricing condition record for a sales price during markdown
period. ETP needs an indicator in standard IDoc for VKP0 condition record. Since this indicator is not in
standard SAP IDoc, an enchantment is required for the same.
2.1.3 Detail Requirements
When the article sales price is downloaded to POS, it is downloaded by a standard IDoc WP_PLU. For
Maison POS integration, we need to populate an indicator for VKP0 pricing condition as a markdown price.
Following are the steps which are to be implemented to achieve the above mentioned information populated
in standard SAP IDoc:





Add a custom segment in WP_PLU IDoc. Create a child segment ZCUSTFLDS under a standard
parent segment E1WPA04.
In custom segment ZCUSTFLDS, add a custom field ZMRKDWN with checkbox data type (Char of
length 1).
An additional custom field ZMRKPER (Markdown %) is to be added to the custom segment
ZCUSTFLDS. The data type for this field is same as WMFU-MDPRZ.
Use standard SAP user-exit EXIT_SAPLWPDA_002 and include ZXWPDU02 to pupulate this
field.
Populate this field using the below logic to be implemented in given user-exit:
o Take article from main header segment (E1WPA01-ARTIKELNR). Pass this article
number to Markdown item table WMFP and field WMFP-ARTNR. Take all the unique
markdown plan numbers (WMFP-MFCNR) and the Item number (WMFP-POSNR) for the
IDoc article from this table.
o In order to check the validiy of the markdown, we need to pass the combination of
markdown number and item numbers to WMFU table. When we go to WMFU table, we can
find a price phases for each markdown plan and item number combination. Each price
phase has sub item number (WMFU-UPOSN). First check the number of price phase. The
markdown plan valididty start date is the valid from ( WMFU-DATAB) date for first phase.
o To determine the end date for markdown plan, take the valid from date for the last price
phase (last sub item number). Add the number of caladner ( WMFU-MDPER) to calculate
validity end date.
o Once we have valid from and valid to date from above logic, we can check the current date
of WP_PLU IDoc falls under which markdown plan. Consider only the valid markdown plan
for further analysis.
o The markdown plan should be relevant for the store in IDoc ( E1WPA01-FILIALE). For
this pass the store number in markdown header table WMFH. If the markdown plan we
filtered above is created for a specific store, the WMFH table will have the store code in
WMFH-SPKNR. If this exists and the store code is same, the markdown plan is relevant for
the store. If the WMFH-SPKNR field is blank, check the distribution chain of IDoc store with
Документ1
Page 4 of 10
WMFH- SPVKO and WMFH-SPVTW fields. If they are same, then the markdown plan is

relevant for IDoc store.
If the valid markdown plan is determined, please check the field ZMRKDWN as 'X‘. Take the
relevant price phase from WMFU table and put the markdown percentage (WMFU-MDPRZ) in
custom field ZMRKPER.
2.1.4 Assumptions and Limitation
*

NA
2.1.5 Output / Result Layout
*

NA
2.1.6 Requirement Flow

NA
2.1.7 Exception Logic

NA
2.2 Test Scenario
*
Ver.
1.0
Test
#
1.
1.0
2
1.0
1.0
3
4
Test scenario and test data
Expected results
Download an article price without
markdown price.
Download an article price which is
part of markdown plan.
The markdown indicator should be populated
as BLANK.
The markdown indicator should be populated
as ‘X’.
2.3 Technical
STT
1
Object name
ZCUSTFLDSZMRKPER
Object type
Segment type
Description
Add new field ZMRKPER to Structure ZCUSTFLDS
2
EXIT_SAPLWPD
A_002
Function module
Create Include ZXWPDU02 and add code
Документ1
Page 5 of 10
2.4 Config Technical for IDOC
2.4.1 WE31 create segment ZCUSTFLDS
Документ1
Page 6 of 10
2.4.2 WE30 ZWP_PLU03
2.4.3 WE82 assign to IDOC types
Документ1
Page 7 of 10
2.4.4 WE81 ZWP_PLU
2.4.5 WE20
Документ1
Page 8 of 10
2.4.6 EXIT_SAPLWPDA_002 ZXWPDU02 Enhancement
System
Project Name
Enhancement
Function Name
Include
Remark
ECC
ZPOS_OUT
WPDA0001
EXIT_SAPLWPDA_002
ZXWPDU02
Add custom fields for WP_PLU extensions =>
markdown download article
2.4.7 T-code Markdown WMF1 WMF2 WMF3
Документ1
Page 9 of 10
Kiểm tra dòng markdown dựa vào giá trị nhỏ hơn 100 WMFUD-W_MDPRZ
Документ1
Page 10 of 10