Tax value not linked to HANA Optimized Business Content ADSO for Billing /IMO/D_SD31

[Former Member]

There is no Tax Information available for HANA Optimized Business Content ADSO for Billing /IMO/D_SD31. In Old Standard Infocube 0RT_C01 there was seperate Keyfigure for Sales with tax and without tax. But in the transformation for new ADSO

TRCS /IMO/SD_IS31 -> ADSO /IMO/D_SD31, the TAX field is not mapped.

[Vince_Lu]

Hello Reshoi,

you're right, 0TAX_AMOUNT in TRCS /IMO/SD_IS31 is not mapped to any fields in ADSO /IMO/D_SD31.

Seems to me there's no such field in /IMO/D_SD31 is with tax. You could of course change the /IMO/D_SD31 by adding fields.

I will also get to the development owner of this ADSO to inquiry for details.

Best regards,

Vince

[Former Member]

Thank You Vince Lu. Appreciate your Prompt response.

We are already reporting from Infocubes which were copied from traditional standard Infocube for Billing 0RT_C01. We would like to move all our reporting to the new Hana Optimized ADSO as part of LSA++. There is another point that the data in old Infocube 0RT_C01 was linked to the date field from Source 'FKDAT' which was linked to 0BILL_DATE in infosource and then 0CALDAY in infocube. But in the new ADSO the date mapping is : VDATU --> 0ST_UP_DTE --> 0CALDAY. Similarly there are lot of difference in /IMO/BCT delivered Contents for SD, SCM, FMCO etc.

Regards

Reshoi R

[Vince_Lu]

Hi Reshoi,

Thanks a lot for the feedback. I'm getting in touch with the owner of these HANA optimized content.

We will get back to you soon.

Best regards,

Vince

[Vince_Lu]

Hi Reshoi,

We double checked on that.

0RT_C01 seems to be a demo cube.

Mapping for the date etc. is actually based on the famous Sales cube: 0SD_C03.

Mapping date fields to 0CALDAY (SAP Netweaver BW) is also quite customer specific, depends on which date you want to report on.

In BW/4HANA (not sure if it's the case for you), this is different due to the navigational attributes of date fields, which make analysis quite easy on different date fields.

Best regards,

Vince

[Former Member]

Thanks Vince Lu for your Comment but this doesnt answer the question why the Tax field was not mapped. We actually follow a procedure to copy the standard business content objects and make the necessary changes based on our needs. The reason is because the standard content will have all the routines and formulas and we need to apply only a minor change on top of that to make it custom. Kindly let us know if there will be an updation of the standard content with all the field mapping with routines and formulas required for the retail Industry

Regards

Reshoi R