nkuebelbeck
VIP Member
There is a new business requirement to save some additional information about the F3211 into the F4211. Specifically when someone has a Y/N in a certain segment, they want that information at a glance and be QBE searchable, and not in a report or looking into the configurator.
I know how to query F3211 and determine what I need. I'm looking for suggestions/best practices in this situation.
As I see it I have 2 options
1) store the information in the F4211 user defined fields, modify V4211A to include those fields, and add those field to the P4210 form (probably P42101 too)
2) store the information in a new table (I believe, commonly refereed to as a tag file), create a new bsvw/form for inquiry.
My worry about number 1 is
1.a) what else will be affected by modifying the bsvw
1.b) what else are they gonna want added to it and i'm going to run out of user defined fields
My worry about number 2 is
2.a)Data available form new form that NOT available from P4210/P42101
2.b)What type of P4210 functionality am I going to duplicate (i'm thinking row/form exits)
please weigh in professionals
I know how to query F3211 and determine what I need. I'm looking for suggestions/best practices in this situation.
As I see it I have 2 options
1) store the information in the F4211 user defined fields, modify V4211A to include those fields, and add those field to the P4210 form (probably P42101 too)
2) store the information in a new table (I believe, commonly refereed to as a tag file), create a new bsvw/form for inquiry.
My worry about number 1 is
1.a) what else will be affected by modifying the bsvw
1.b) what else are they gonna want added to it and i'm going to run out of user defined fields
My worry about number 2 is
2.a)Data available form new form that NOT available from P4210/P42101
2.b)What type of P4210 functionality am I going to duplicate (i'm thinking row/form exits)
please weigh in professionals