Skip to Content
avatar image
Former Member

Auto Factory calendar update in APO using RSIMPCUST

Hi all,

While setting up automatic factory calendar update job in APO, I have following queries:

1) In Standard SAP program RSIMPCUST, there are options of “rebuild tables” or “update tables”. So far I have known that for Factory Calendars, “Rebuild” is the only option and it does not allow “update” as standard behavior. Please confirm. Also is “update” table option achieved through any modification in the code of program copy of RSIMPCUST?

2) If we select the “Rebuild tables” option, are there any risks?

3) Are there any risks of transaction data inconsistency due to this automatic calendar update program?

4) Timestreams are generated immediately after calendar updates. There is a standard SAP program /SAPAPO/TIMESTREAM_UPDATE for that. Are you using this same program or are there any important modifications done? Or if there is any other option for the same?

5) Are there any SAP Notes which need to be applied necessarily if we are using the program RSIMPCUST in APO as a batch job?

6) In case of weekly run of this program are there any risks of transaction data inconsistency?

7) In BW system, do we need to run a similar automatic calendar update program to ensure that calendars are in sync in BW system? Do we need to recalculate timestreams in BW also?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 26, 2014 at 03:32 PM

    Rahul,

    So far I have known that for Factory Calendars, “Rebuild” is the only option and it does not allow “update” as standard behavior. Please confirm.

    Confirmed.

    Also is “update” table option achieved through any modification in the code of program copy of RSIMPCUST?

    I have no experience in this area, so I will give you my standard answer.  Anything is possible if you have enough time and money and resources.  You can modify any SAP program to do anything, although best practices is to avoid modifying anything in the SAP namespace.  Usually better to clone a SAP program and then modify your clone.

    I personally would not attempt such a modification unless there were a compelling business requirement that could not be solved in any other way.

    If we select the “Rebuild tables” option, are there any risks?

    Of course there are risks.  There would also be risks if 'update' were possible as well.  Calendars are the foundation of all planning; any changes to any calendar in any system must have a mitigation plan. For instance, if yesterday January 1 2015 was NOT a holiday, and today January 1 2015 IS a holiday, then you have to ensure that all existing transactional data is managed in such a way so as to accommodate this new holiday.

    Realistically, as long as all of the master data objects that are dependent on Calendars are updated right after the FCs are overwritten, there is typically very little adverse impact on transactional data.  In real life, much transactional data undergoes some changes during its lifetime, and many of these changes trigger re-scheduling.  Re-scheduled transactional objects will reflect the latest info contained in the master data time-based structures.  Many companies just ignore any transactional inconsistencies, if they are minor and short-lived.

    ...program /SAPAPO/TIMESTREAM_UPDATE for that. Are you using this same program...

    Yes

    ....or are there any important modifications done?...

    You seem to be very enthusiastic towards performing modifications.  These are the absolute last resort, to be used only when an KNOWN business requirement cannot be met in any other way.  I would suggest that you run the program "as-is" and then determine if running this program generates problems thereby.  Once you know you actually DO have a problem, the first thing you consider is an enhancement of some sort, rather than a modification.

    In all implementations I have seen, this program is successfully run on a periodic basis, without any enhancements or modifications.

    Bear in mind that this program only updates timestreams.  There are other Factory calendar dependent objects in SCM besides timestreams; it depends upon the solutions you have implemented in SCM.

    Are there any SAP Notes which need to be applied necessarily if we are using the program RSIMPCUST in APO as a batch job?

    I have never had to implement any SAP notes to run this program.  Obviously, SAP discovers new bugs all the time, and new notes are sometimes created to repair old programs.  RSIMPCUST has been around for a long long time, though, and it is pretty stable now.

    In BW system, do we need to run a similar automatic calendar update program to ensure that calendars are in sync in BW system? Do we need to recalculate timestreams in BW also?

    Depends on your BW design.  In general, a common practice is to designate one system to be the 'Master' of all factory calendars.  From this system, the 'satellite' systems (such as SCM, and BW, and others) will then run RSIMPCUST periodically to keep all the Factory calendars in synch.

    I am not aware of Timestreams' existence in BW.  Depending upon the design of the BW solution, you may have to update certain objects there as well, that may have a dimension that is affected by FC changes.  It is possible to design a BW solution such that changes in Factory calendars require no additional effort. Speak to your BW expert to discover the vulnerabilities in your BW system.

    Best Regards,

    DB49

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 25, 2014 at 05:17 PM

    Hello Rahul,

    We have recently an issue where user would like to avoid RLT maintenance and perform correct ATP(ECC), we started maintaining the factory calender in ECC updating working/nonworking days.

    After changing the work days in factory calendar I am running RSIMPCUST with rebuild option( because I guess it is work bench request ECC, rebuild is better option to update tables) after that, I found the capacity profile is getting updated but not the resource capacity on the planning board. To resolve that I am running program /SAPAPO/CRES_CREATE_LC_RES so that the changes get update in LC.

    Hope this info will help you,

    Thanks,

    Rajiv

    Add comment
    10|10000 characters needed characters exceeded