Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

append to standard table

Former Member
0 Likes
484

Hello,

I would like to maintain BW related classification in R3 standard table. For example , I would like to add couple of columns to material type table (T134) and populate it with values.

I would like to ask you the following questions :

Do you think its a right approach?

What is the down side of this approach?

How to populate these values as table looks not open for modify

Thanks

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
434

Hello,

I see no problem with your approach only pay attention with the following :

1/

Make sure you use unique field names.

Example start all your field names with ZZ and make sure you don't use SAP fieldnames.

This is important to avoid duplicate field names in future SAP releases for the table where you would like to add fields.

Duplicate field names will result in problems during patching of the system and can cause eventual data loss when handled incorrectly.

2/

Pay attention when future support packs, upgrades, enhancement packages, ... are installed in your system that there is a change that the table you are going to append will appear in the SPDD list because SAP provides a new version of the table.

It is then up to the basis team to handle this SPDD correctly and re-implement the append structure to prevent data loss.

This is the only side effect that I see.

Wim Van den Wyngaert

Hello,

I would like to maintain BW related classification in R3 standard table. For example , I would like to add couple of columns to material type table (T134) and populate it with values.

I would like to ask you the following questions :

Do you think its a right approach?

What is the down side of this approach?

How to populate these values as table looks not open for modify

Thanks

1 REPLY 1
Read only

Former Member
0 Likes
435

Hello,

I see no problem with your approach only pay attention with the following :

1/

Make sure you use unique field names.

Example start all your field names with ZZ and make sure you don't use SAP fieldnames.

This is important to avoid duplicate field names in future SAP releases for the table where you would like to add fields.

Duplicate field names will result in problems during patching of the system and can cause eventual data loss when handled incorrectly.

2/

Pay attention when future support packs, upgrades, enhancement packages, ... are installed in your system that there is a change that the table you are going to append will appear in the SPDD list because SAP provides a new version of the table.

It is then up to the basis team to handle this SPDD correctly and re-implement the append structure to prevent data loss.

This is the only side effect that I see.

Wim Van den Wyngaert