Hello everybody,
I have a third party (UD Connect) transactional datasource that is not delta enabled. I want to avoid loading the complete history every day over and over again. There is a filter for characteristics 0FISCPER in the datasource. I know from the external system that there can be changes in current year, previous year and followíing year (relative to system date) only. The older data are frozen.
In one our older process chain we have a similar case that works fine. It is based othe the 3.x process though. There are three infopackages "previous year", "current year" and "following year". The selection criteria are derived by short ABAP routine as system date year -1, system date year, and system date year +1 respectively. As there are no DTP in 3.x these three infopackages create three requests in the infocube. Later in the chain there is a process step "Delete overlapping requests in infocube" that prevents the data to be duplicated. If the chain is run today three requests for 2013, 2014 and 2015 are generated and then the requests from yesterday for the same years are deleted from the InfoCube. On 1.1.2015 three new requests for 2014, 2015 and 2016 will be genereated into the InfoCube. The requests for 2014 and 2015 from 31.12.2014 will be deleted. The request for 2013 will remain untouched since there is no newer request for 2013 from 1.1.2015. This is exactly what is needed.
I would like to achieve the same result but with a 7.x chain. I have created three infopackages same way as in the old chain and a DTP to load the data from PSA to the infocube. Running the process creates three packages in PSA but the DTP merges them into one request. The trick with the shifted year on 1.1. does not work any more since as far as I understand it is not possible to delete just a part (2014 +2015) of the request in the cube leaving the 2013 part untouched.
How this can be done in 7.x chain? Or shell I use some copletely different approach?
Regards
Jiri
