MM_EBAN Test Variant picking up Purch Reqs outside Residence Periods

[Former Member]

I have MM_EBAN Customization Purch Doc Types all set with Res 1 - 730 days and Res 2 - 30 days.

Test Variant is setup as 2 step with detail log. When running today (11/26/2009) for example, I am picking up PR's without a delete indicator set for any items and it has:

- Last change date 10/22/2009

- Created on 02/02/2009

- Delivery Date 02/ 02/2009

PR has 3 items each have the same Quantity#, as Quantity Ordered, with Open Quantity 0, Processing Status = Active and GR and IR = X. Sched Line, GR = Qty, Goods Issue and Delivery note = negative Qty #.

Item 10 - Planned Delivery 24, GR proc. time 1

Item 20 - Planned Delivery 11, GR proc. time 1

Item 30 - Planned Delivery 98, GR proc. time 1

MM_EBAN Test Variant Log shows this PR as Archived. (To be Archived)

What am I missing? It appears that this PR should not qualify to be archived because it has no Del Ind Set for any of the items. Nor does it qualify to have the Archive Program set the delete indicators because the last change date is not older than 730 days.

Thanks in advance for help.

[Former Member]

Those EBAN records that were had the manually set del indicators only check the Res 2 residence time, therefore if they were over 30 days from the run/key date, they will automatically get archived. So they don't follow the 2 yrs on-line method that we originally thought they would. I don't believe this is a problem right now, however we are moving to ECC6 which now has the separate preprocessing pgm - we will see how it goes and what the business wants.

Thanks - Colleen

[JL23]

what did you run? the preprocessing or the write program?

a residence time has to be set per document type and item category.

do you have a record with the residence time whose item category matches with the item category of your PR ?

What program do you actually use? you can see the program when you define the variant.

Unfortunatly SAP has at least 2 different sets of programs for archiving, so it is important to know which one you use.

[Former Member]

There is no separate preprocessing for EBAN for ECC 5 - that I am aware of. The write program does the preprocessing for the next write run. In the write log it will show those PRs with a Del Indicator set by this prgm as Deactivated.

All residence periods are setup the same for each Type/Cat. combination that exists in the current database. This PR falls under one of those combinations.

RM96BW30 is the write prgm being executed.

[Former Member]

I believe I found my 'user error' issue - I had a transposed PR # that I was looking at in the on-line DB. Wrong PR # used than what was in the EBAN Write Log.

I think I'm ok - all of the PR's I've checked that appear outside the Residence Period, have all Items Deleted in the on-line DB, therefore, as I understand the program code to work, they will automatically get archived regardless of either residence period 1 or 2. For example, changed on date is 10/21/2009 and key date is 10/21/2009 but items are all deleted. If this is not how the program should work, please let me know.

Thanks for the quick response Jurgen - appreciate it.

[JL23]

you probably meant RM06BW30.

if you run it 2step, then residence time 1 is relevant to set the deletion indicator.

Looking at your dates, it looks like it uses 30 days (which is the SAP delivered residence time) and not 730.

if you are sure you have everywhere the 730 days, then open an incidend at SAP.

[Former Member]

I have Residence 1 set at 730 days and Residence 2 set at 30 days. It appears to be working correctly.

There is nothing archiving outside of any Res Dates. I was thinking there was a header record del indicator in EBAN table that wasn't previously set, but that since all the line items were previously set, it was getting archived immediately regardless of either Res period. There is no such header record in EBAN with a del indicator - they are all line items and if they all have del indicators previously set, and it's been at least 30 days since change date (ie. Change Date equal to or greater than Key Date) then they would be archived correctly.

Thanks,

Colleen