Use

Some infotypes in your system may need to manipulate more data than the current record contains. Because the manner in which the system manipulates the buffer in this release differs from that of prior releases, we recommend that you take a moment to examine how infotype records are written. To this end, consider why your infotype needs to update other records. The goal of this analysis is to determine whether your infotype would truly require the corresponding updates to be hard-coded.

To obtain an understanding of how infotype records are written in the system, we recommend that you review the Personal Data infotype (0002) as an example.

Procedure

If sufficient conditions exist to restrict the updates of other records to dialog mode only, then you should by all means hard-code the corresponding updates – but not in the infotype business logic itself. For additional information, you may refer to the subsequent topics in this section, which are summarized below; each topic addresses an aspect of managing infotypes that modify other infotype records within the system.

Background Information

Using Containers to Write Data

Reading Before Writing

Creating New Containers Before Writing

Modifying Contents of Containers

Deleting Existing Records

Inserting New Records

Modifying Existing Records

Using Pushbuttons

Declaring the Operations

The information presented in each of the subsequent topics exceeds the general knowledge that is required to create (or migrate) infotypes in(to) this release. Individuals who have particular expertise in this subject matter or who desire deeper knowledge of this issue may nonetheless consult these topics for reference.