on 11-09-2010 10:51 PM
Hi All ,
We are using a Planning area with a Fiscal year variant in the storage bucket profile for DP. We are trying to copy the data from BW to the planning area which also has the same Fiscal year variant. All the settings in SPRO and the T009 tables are setup correctly for this fiscal year variant, still while using the TSCUBE transaction to copy the data from the cube to the planning area we enconter the above mentioned error. While investigating further we found a table /sapapo/T445C2 which assigns the infocube to the technical periods and this table is empty as of now,( A similar table is used in ECC for flexible planning which assings this value there ) , But in BW side there is no such table. I am not sure if this is the reason for the error. Did anyone face a similar problem in the past . Kindly share your comments on the same.
Regards
Chirag
Hi Chriag,
If not already, please have a look at following OSS notes, if these have some relevance.
OSS note 1408753 ( /SAPAPO/TSCUBE WRONG ERROR MESSAGE /SAPAPO/TSM232)
OSS note 1491820 ( Periodicities of Infocube and planning area are incompatible)
Regards
Datta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kadam,
Thank you for the reply. We already did check the notes , but that is not of relevance in this case, since the error is happening not only in APO but also in BI. The BI team found that the fiscal year variant defined for the year was 100 periods which is not possible since in a year if we make weekly periods the periods cannot exceed more that 53 to 64 hence the system was not creating any SID's they are trying to correct the error.
Regards
Chirag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.