Skip to Content
Author's profile photo Raghunathan Balasubramanian

Fields in EDIDC table that can be used

When  generating IDocs using Business Object Data Services (BODS), the EDIDC control table data is passed. There is a need to identify the IDoc against the corresponding records that are used to generate the IDocs. One option that I have used is to store the legacy value in some of the fields in EDIDC table when generating the IDocs using BODS. I would like to know whether there are alternative options that are more structured to using EDIDC fields for storing this corelation between legacy data and IDocs generated.

Below is an example where EDIDC fields RCVLAD was used to store legacy reference for Busienss Partner when creating/updating business partners when generating IDocs using BODS.


The IDocs loaded using this method all have NEW_<GUID> in column RCVLAD. A sample is shown in Fig2 below.


The same approach can be applied on column “SNDSAD”.

What would be better to understand is whether there are any other standard solutions provided that we can utilise in order to facilitate the IDoc to legacy record reference.

All comments on this topic is welcome.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member


      We have used SNDSAD field for storing legacy values. But I'm not aware of another option to store legacy data. However one issue I face with EDIDC approach is that this table gets a large amount of data loaded very fast. So reconciling does become a bit of an issue with time.

      Author's profile photo Former Member
      Former Member

      Good approach to using EDIDC fields. But I feel there should be something more standardised.