Newsletter            Wir rufen zurück            Impressum

Issues when Delimiting entries in custom tables

2 Responses
  1. Narender Singh

    Thank you for this post.

    I have created a maintenance program for maintaining a custom table. I want to embed the delimit logic in my program, as i have both start date and end date as keys.
    could you please help?

    1. Sven Ringling

      Hi Narender,

      No change in logic, whether it’s a custom table or not. In an ABAP to manipulate the data, you can never just change a key field, so if both dates are keys you copy the old entry to you new target key and delete the old one.

      However: it’s not really „delimiting“, because that doesn’t really say anything, if both dates are keys. Because that means your data model says yo can have entries with otherwise same keys and overlapping time periods.
      Are you SURE, this is the case. In most cases I see custom tables with start data as well as end date being key fields, this is actually not properly implemented. If you actually need entries to be in a sequence (when the word „delimit“ makes sense) only the end date is a key field.
      If you check most standard tables with time ranges, you’ll se that this is the case for them as well.
      Got nothing to do with custom tables or ABAP. Just basic data modelling principles, which apply here as well.

      hope that helps.

      best wishes

Antwort schreiben