Dynamic Scheduling Best Practice -- IS-U-BF-PS E1DY E2DY

[daniel_mccollum]

I have been tasked with resolving several long standing issues with My Companies Meter Reading Schedules. My question originates out of the desire to implement the eventual corrections I make as close to a best practice standard as possible.

Near the end of 2009 I extended the Dynamic Schedule Records out to the end of 2010 with transaction E1DY

At the beginning of 2010 I reported a program error which resulted in [Note 1411873|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001411873&nlang=E&smpsrv=https%3a%2f%2fwebsmp103%2esap-ag%2ede&hashkey=9D07D6F4306CBF2AF0B69DEE0022142E| Schedule record: Previous period end in dynamic scheduling]

I requested clarification of the comment:

 "In certain operational scenarios that are not explicitly forbidden (but which are strongly advised against), the end of the previous period of the first schedule record of a series of a year may not be calculated correctly in the dynamic scheduling"

& was advised:

it means such cases where you don't have a full sequence of MRU.
The standard process of dynamic scheduling is designed that you have for every day several readings (consilidated in meter reading units/ MRU).

There was no further clarification other than the confirmation that the configuration existing in our system did not match this ideal condition.

The Current Design of Dynamic schedules is as follows:

1. No Budget Billing implemented at all. All Portions defined with a parameter record Without Budget Billing configured

2. Several Groups of Monthly Portions allocated to Calendar Z3

2a.     21 Monthly Portions 
2b.     21 Monthly Portions
2c.     21 Monthly Portions
2d.     21 Monthly Portions
2e.     21 Monthly Portions
2f.     20 Monthly Portions
2g.     1 Monthly Portion
2h.     1 Monthly Portion

-Please note, that this results in day 21 of 2a-2e not including day 1 of the 2f Monthly Portions as is intended. this results in manual movement of the 20 Monthly portions in transaction E2DY one by one.

-Please note, for portions in group 2d, & 2e there is a "gap" in the config where the factory Calendar is not Assigned for day 12 & 13 in the series. resulting in a gap in the schedule record creation.

3. Many Meter Reading Units are configured for each portion.

My intended changes to the configuration are as follows:

4. No change to Budget Billing

5. All Groups of 21 Monthly Portions (2a - 2e) share the same configuration, so change all Meter reading units for (2a - 2e) to 2b (least change)

6. 2g is configured the same as day 14 of groups 2a - 2e, move to 2b equivalent

7. 2h is configured the same as day 15 of groups 2a - 2e, move to 2b equivalent

8. 2f is configured on Calendar Z3, so update configuration to Calendar ZL

9. Generate schedule records for Calendars Z3 & ZL

Having read all the above, can anyone expert in the design & implementation of Dynamic scheduling think of any issues which may arise from updating the configuration as described.

If anything is unclear or stupid let me know, I'm definitely interested in feedback to help ensure the corrections are made smoothly, & to clarify what was the "operational scenarios that are not explicitly forbidden (but which are strongly advised against)" as mentioned in the SAP Note.

Also as a final question, how feasible would it be to delete the unused portions after these changes are migrated?

regards

Daniel

Edited by: Daniel McCollum on Sep 9, 2010 7:12 AM

[daniel_mccollum · Accepted solution]

I have started on point 8 first:

after moving all 2f portions to calendar ZL & reentering the Meter Reading Units to resync the calenadar configuration, I used E3DY to delete schedules on calendar ZL from a future date.

This has eliminated the offending schedules on these portions from the Z3 Calendar.

Point 9:

using E1DY to generate the schedules & E2DY to "merge" them with the end of the older schedules still on Calendar Z3 has resulted in the expected 20 day cycle.

I am now dealing with the portions still on the Z3 calendar by regenerating them via E1DY & moving to the correct dates via E2DY to verify the schedules.