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.
I think Martin is right. If I add the field using append and create an index for that field, how will I have multiple values for the same?
E.g if I want to add year to MARA. I can append a structure with year but if I create a material valid for 2 separate years, how would year be a key field? How will this scenario work by an index?
Martins answer is correct. You can add additional fields to standard tables using APPEND structures but you can't make them as KEY fields to the same standard table.
Purpose of having APPEND structure is to add new fields, use as foreign keys, attach search helps, etc.
You can create an index using the APPEND fields but this will only be helpful(speed up) when reading data from that table.
So could you tell me why you want to make your append field to be a part of the key to the table?
Maybe you can consider using the year in the value range of your MARA table - off course this will not inflict your 'old' data. But if you archive it, then in the end you can have the year embedded in the number range.
The year is a part of our process and needs to be added as a key field for calculations of quantities. I know creating an Index would speed up the query part but that would not help in creating multiple entries of the same part in the table and the requirement is that.
Via transaction MMNR you can maintain the intervals. I suggest that when you change the interval each year to another 201300000000000001 201399999999999999 (this year into: 201400000000000001 201499999999999999). Then you don't need to have this additional year field.
Bluesky
