importing factory calenders in APO- error

[Former Member]

Hi,

I was trying to import the new factory calendars in R3 to APO (Calendar ID) to create a new set of time streams. I used the program RSIMPCUST - (checked rebuild tables) to transfer the calendars and could see a list (seems ok). but heres the issue.

- The calendars imported are not the ones maintained in plant calendar in spro>ent struc in R/3

- Manually maintaining the "desired" calendar and generaing the periods pops a message- date dd/mm/yyyy before the start of factory calendar. i,e the first date of the bucket is before the start of the calendar. (though saving the calendar is allowed without generating the periods)

could someone explain

- How to correct this.

-More generally how to ensure that factory calendar (and changes to factory calendar in R3) is in sync with APO and time streams are current from according calendar in R/3.

- What could go wrong downstream if i delete some periods and regenerate periods from the new calendar

Please correct me if i sound ignorant.. not very sure of R3 side.

Thanks.

Lok

[srinivas_krishnamoorthy]

If you are manually trying to maintain a calendar in APO, then you may want to use the update mode instead of rebuild mode.

When you define a new custom factory calendar, make sure you attach a holiday calendar as well.

When creating a Time Stream ID, make sure number of years in the past and future is less than equal to the factory calendar definition.

[Former Member]

Thanks for the prompt response srini,

with update mode i got this error message. Moreover the objective is not to maintain the calendars manually as there a large number of locations and calendars.

"Only reconstruction supported for factory calendar

Message no. RSAR889"

The factory calendar and holiday calendar are defined by R3 MDM team, so i have no clue.

Once the periods are already created basis an earlier calendar how do i know what to enter in years in past and years in future . (to exactly match the start date <= the factory calendar definition).

The end purpose is to

- Import the value of factory calender key (table V_T001W field FABKL) from R/3- plant definition to APO calendar ID (struc /SAPAPO/CALIO field CALENDARID) in mass.

- Generate and/or correct the period buckets of the existing time stream basis the newly imported calendar.

Functionally nothing is harmed even if i dont do all this, as all these calendar definitions in our set-up are more or less same but for configuration and differentiaiton purposes (or may be accomodate future changes), new locations, new calendars etc, the correct values need to be maintained. The APO time streams and calendars should be accordinly maintained prefarably in mass.

- Dont see any attributes in massd standard functions to maintain this calendar ID. (we do maintain time streams in mass)

- Dont know if the period calculation program accomodates the new calendar definition and deletes/generates periods accordingly.