Real Time Consolidation:System doesnot pick records from ACDOCA table during Currency Translation

[former_member540457]

Hi Team,

We are implementing Real Time Consolidation where currency Translation is done inside RTC using the transaction code RTCCT. Below is the issue:

For Model XCON, there is no record in ACDOCC table. In ACDOCA table, we have records against entity 1234 for period 201707. We ran Currency Translation using the RTCCT but system did not pick records from ACDOCA table. Also while Data Submit request using RTCDSRB, no records were fetched. Our concern is that records from ACDOCA table should have been fetched. Note that, when records are present in ACDOCC table, the Currency Conversion via RTCCT picks records only from ACDOCC.

Can it be related to SAP note 2490401 which talks of leading 0s in case of entity?

What are we missing here.

Regards,
SHUBHAM

[former_member612856]

Hi Lucus,

I am using Company code as base for Entity using RTCCMD transaction code.

Any idea as to why the data from ACDOCA isn't read into UNION view which is called into Virtual provider and composite provider? While we can post and read records from ACDOCC but not able to read records from ACDOCA. We have tested the foundation view for Actual. In there, we can read the actual data from ACDOCA but not further upwards.

Thanks,

Manish

[lucas_costa3]

This note 2490401 is about the leading zeros in the presentation layer. If you have saved the mapping correctly it will work fine. e.g.: ENTITY = 1001 and RCOMP = 001001..

I had a problem in the past where I uploaded the mapping from a flat file, and S/4 characteristic - RCOMP - was missing the leading zeros, and no data was being selected because internally there is a join using the this field.

[damovand]

Hello,

Is the note relevant for your version? If yes, then I would say implementing it can only be beneficial. However, if you are looking for more validation if leading zeros are causing the problem then you may see some clues in BPC web client. I worked on an issue with BPC journal entry, through BPC web client, when some dimension members appeared in member selection lists without leading zeros but in other places they could be seen with leading zeros and the data was not being posted. Applying the recommendations and making sure the ALPHA routine was enabled fixed the problem.

Best Regards,

Leila Lappin

[former_member540457]

Hi Leila,

Yes the note did work. Only precaution is that while maintaining the entities in transaction code RTCENT, entities have to be saved with leading 00 post applying the note.

Regards,
SHUBHAM

[damovand]

Hello,

Are you saying that you want leading zeros in some areas of the application but not in BPC? I am not sure how that can work since BPC consumes the same data then it has to be the same format.

Regards,

Leila

[lucas_costa3]

Hi Leila, actually most customers I know are removing the leading zeros from the entity mapping. Especially for Company (2 leading zeros) and Profit Centre (4 leading zeros). This leading zeros, if not removed, are displayed in BPC and reports, which is really usable..

There is a note for this:

2490401 - Customized entity InfoObjects to replace /ERP/ECOMP & /ERP/ICOMP to solve leading-zero problem in entity mapping

However, If for some reason the ABAP value (fields RCOMP, PRCTR etc) is missing the zeros in table RTC_ENTITY_M, the HANA views won't work - and I telling you this from my own experience.

[damovand]

Hello Lucas,

I agree with you about the leading zeros should be removed at least as far as BPC is concerned. However, I read that ALPHA conversion routine is supposed to take care of any mismatched format, especially regarding the leading zeros. I assume this will apply to all values persisted at the data base level.

Regards,

Leila