SAP for Retail Discussions
Join conversations about personalization, omnichannel strategies, and operational excellence in retail using SAP for Retail software.
cancel
Showing results for 
Search instead for 
Did you mean: 

Store replenishment issue - WRP1 - records exceeds- Table_invalid_index

Former Member
0 Kudos

Hi All,

We have an error while running the replenishment program - ZWRP1 (copy of WRP1) table.

The error is Table_invalid_index. - ie. abap dump message.

ZWRP1 is a copy of wrp1 program.

If we analyse the dump in ST22 ; the error occured in the

standard SAP program;

The termination occurred in line 31

of the source code of program "LATP0F0R " (when calling the editor 310).The program "SAPLATP0 " was started as a background job.

The program SAPLATP0 is standards SAP which is being called in our Z

program.

Now the reason given by SAP support is that refers to 1243541 note;

-


The ATP-check is designed in a way that only a check for a maximum of

99,999 records is possible. In your case this number is exceeded, which

leads to the dump you encounter.

Reason for the dump is that field 'BDCNT' in MDVE has only 5 digits,

so when moving the counter for check 100000 to BDCNT the first digit is

cut -> BDCNT = '00000'.Later in RESULTS_STANDARDIZE the system can not find the corresponding

record in P_MDVEX so the system dumps.-----

The Input for MDVE comes from WRPT. WRPT gets updated as soon as an article is listed. Now this table exceeds 100,000 records per store - approx. about 109,000 records per store. We found out that about 32000 articles were wrongly listed to these stores.

Therefore we ran WSP3 to de List these articles from these stores.

However we find that wsp3 does not remove the data record from WRPT table.

Also want to know when an article is out of life - ie. no longer sold nor purchased, shoudnt there be a way to remove from such tables llike WRPT which are critical for operations such as replenishment.

Do we necessarily have to archive ?? isnt there any other way to "delist" plus remove from WRPT such that the replenishment program does not have to do availability check.

In the ZWRP1 (copy of WRP1)

We feed the following selection data;

1. Store

2. Articles Range

3. Net change planning Ticked.

4 Packet size (increased from 1000 default to 99999)

Kindly help.

3 REPLIES 3

Former Member
0 Kudos

As far as I know, WRPT is more linked to MARx tables than to WLKx tables -> delisting should not affect WRPT -> the only way out is archiving or partial archiving of the article, which is a best practice and not necessarly very heavy to do.

Regards

Eric

Former Member
0 Kudos

Hi

I'm not sure if this will help but you can look to clean up WRPT a bit. this is some information about it.

Program RWRPLCHK u2013 Consistency Check for Replenishment Data

This program is used to eliminate inconsistencies in the Replenishment tables WRPL, WRPT and WRPP. The program performs three functions:

u2022 Reconciliation

Tables MARC and WRPL contain redundant data that should always be identical. In certain circumstances, however, inconsistencies can occur. This report eliminates inconsistencies in table WRPL by overwriting table WRPL with the entries from table MARC.

u2022 Deletion of replenishment data

Previously, there was no option to delete replenishment master data and the accompanying movement data apart from by completely archiving a material. This report enables you to delete entries from tables WRPL and WRPT. Only entries that have an RP type that is not relevant for replenishment are deleted e.g. ND

u2022 Deletion of requirement groups

If the replenishment data is maintained using requirement groups, there is no option to delete the entries in table WRPP for all materials in a store. Set this indicator if there are entries in table WRPP for materials that no longer exist in table WRPL and which therefore need to be deleted.

This may help you clean up your entries in WRPT and help with your issue.

Regards

Lisa

colin_cheong
Contributor
0 Kudos

Hi,

Did you limit your run by individual store or even specific article range?

The WRP1 actually locks up all the data it could find. This will prevent someone from accidentally running the same selection.

In our environment, we even set it to run by vendor and subrange using ZWRP1

There was also locking issues but was eventually settled.