SAP CPI DS/IBP - Post-Processing Rejection Code Name - "Period is not within defined range"

[former_member594071]

Hi Experts,

I am getting a post processing error " Period is not within defined range" while loading the exchange rate master data into the IBP. I have not mapped any date field into the target query nor I have used any date data type global variable except the $G_LOAD_DATE(sysutcdate()), however I'm still facing this issue.

REJECTION CODE - 114

REJECTION_CODE_NAME - Period is not within defined range

REJECTION_DESCRIPTION - Check that period is within the limits defined in the time profile.

Any suggestions would be highly appreciated.

Regards,

Shubham

[Irmi_Kuntze · Accepted solution]

Hi Shubham

The exchange rate is usually defined as a so-called Attribute as key figure (AAKF)

That means you usually load it as attribute value without any time dimension, and in the post processing of IBP the key figure AFTER loading as attribute is populated to the key figure value.

This has NOTHING to do with CPI-DS but is purely within IBP.

Now where is the time horizon coming from?

That you can see in the planning area configuration app, open your planning area and go to the tab of the AAKF. There are From / To periods defined. If they are empty, that means the system loads the values within the full horizon of the loaded time profile.

I would guess that in your case a From and To period is defined, but the periods for which the time profile was loaded is smaller then the FROM / To periods of the AAKF.

To check what was loaded, you open the app "Data Integration Jobs" and "Download Template" for your time profile WITH existing time periods. That you compare with the From / To periods. if for example your TO period is 2 years in the future, but you have loaded only until end of next year, you have to reload the time profile with more data (but especially in a productive system, you have to be very careful that you do not change any of the already loaded values and that all values are still consistent, so test in a development environment first).

One other root cause could be that in the time profile the overall range in the header called "Start date" and "End Date" has run out and is smaller then what is provided in the AAKF - From / To period. In that case just enhance the horizon of the time profile, it does not change any data itself and is risk free. I usually set this with an end date where I will already be retired ... However, if that is the case then the loaded time profile values have likely to be reloaded as well, as you can not load them longer than the overall range within the time profile header

Maybe there is a third option which I cannot see.

In any case check ALL your settings of the time profile and within the planning area that they all make sense

Yours
Irmi