Skip to Content
0
Feb 24, 2011 at 02:38 PM

Infotype header - best practice

34 Views

Hi group

Today our ifnotype headers are created in a way that makes us have to break a lot of infotypes just to refresh the header.

There are 2 reasons in my opinion:

- We have chosen to read header on infotype begda

- We have eg. position information in the header

We want to change this so we don't have to break eg. address just to read correct data.

I don't feel reading header at sy-datum is a right choice. This can give an incorrect picture if you read an infotype and the header is inconsistent with the actual situation in the date-range for the infotype.

So I am leaning towards letting the header contain much less information.

Does anyone have some "best practice" thoughts?

Any documentation I can read up on regarding best practice on this matter?

Thanks in advance

Kirsten