Application Development 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: 

APPEND STRUCTURE vs Custom Z-table

ChadRichardson
Participant
0 Kudos

Good afternoon, Experts

We are debating whether to add fields to standard SAP tables via the APPEND STRUCTURE method or create a companion custom Z-table. New fields would need to be easily displayed and modified. We understand the concepts between the functionality of both.

Which method do you use??? or use most often???

Has anybody had any bad experiences with extending standard SAP tables using these APPEND STRUCTURES???

When would you ever consider creating a companion custom Z-table instead of using the APPEND STRUCTURE mechanism???

Chad

1 ACCEPTED SOLUTION

naimesh_patel
Active Contributor
0 Kudos

You should use the "companion custom Z-table" when you want to have the data in the field for the Historic data.

E.g. You want to have the Sales Order Custom status for each sales order. You can put some derivation logic in the user exit to calculate the Custom Status. So, whenever user changes the order it would determine the status and save. Since this information is important we need to have status for all historic orders.

If you have append structure to VBAK to store this Status, than you need to change all the historic orders (using manual or BAPI) to update this status field. But, if you have the Z table, you can run some Z program to update that table easily.

Regards,

Naimesh Patel

6 REPLIES 6

Former Member
0 Kudos

Moved to correct forum.

Rob

naimesh_patel
Active Contributor
0 Kudos

You should use the "companion custom Z-table" when you want to have the data in the field for the Historic data.

E.g. You want to have the Sales Order Custom status for each sales order. You can put some derivation logic in the user exit to calculate the Custom Status. So, whenever user changes the order it would determine the status and save. Since this information is important we need to have status for all historic orders.

If you have append structure to VBAK to store this Status, than you need to change all the historic orders (using manual or BAPI) to update this status field. But, if you have the Z table, you can run some Z program to update that table easily.

Regards,

Naimesh Patel

0 Kudos

What if I really don't care about the old historical values??? I only want to populate this information from this point forward. Would that change your mind as to which method to choose???

0 Kudos

What if I really don't care about the old historical values??? I only want to populate this information from this point forward. Would that change your mind as to which method to choose???

In this case, you can use the Append Structure. There would be more advantages as you don't have to keep track of data consistency, Locking / Unlocking mechanism etc.

Please refer to the section [Further Remarks on Append Structure|http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb61446011d189700000e8322d00/frameset.htm]

Regards,

Naimesh Patel

Former Member
0 Kudos

This message was moderated.

umashankar_sahu
Active Participant
0 Kudos

If you are adding a Z/Y field or custom field in standard SAP table through append structure it will more advantageous for you. And During Upgrade in SPDD Phase all standard tables where customization done will come for adjusting the tables in a higher version. At that time also system proposes to carry the customized field in include structure or Append structure.