JRev
Active Member
All,
Just wanted to get everyone's opinion on something. I was wondering if it's pretty common to change P4210 to exclude unused fields and form/row exits. We have actually done some extensive modifications to P4210 business functions etc which links with a custom module, but for some reason never considered the most basic aesthetic changes.
There are a lot of fields visible in P4210 that we don't use like Salesperson 1, Salesperson 2 etc. My question is, if we were to hide them from the grid, would they still be included in all queries? Or would we need to create an identical business view and also delete those unnceccesary fields from the view?
Also, I would like to remove the unneeded exits and reorganize them. Have a lot of companies used this approach or just left P4210 alone?
I would think a few simple changes would save a lot of time and unnecessary table fetches.
Any comments?
Justin
Justin Revoredo
Amersham Pharmacia Biotech
Piscataway, NJ
OW B7332 Coexistence SP11.1
AS/400 Oracle
Citrix/Fat
Just wanted to get everyone's opinion on something. I was wondering if it's pretty common to change P4210 to exclude unused fields and form/row exits. We have actually done some extensive modifications to P4210 business functions etc which links with a custom module, but for some reason never considered the most basic aesthetic changes.
There are a lot of fields visible in P4210 that we don't use like Salesperson 1, Salesperson 2 etc. My question is, if we were to hide them from the grid, would they still be included in all queries? Or would we need to create an identical business view and also delete those unnceccesary fields from the view?
Also, I would like to remove the unneeded exits and reorganize them. Have a lot of companies used this approach or just left P4210 alone?
I would think a few simple changes would save a lot of time and unnecessary table fetches.
Any comments?
Justin
Justin Revoredo
Amersham Pharmacia Biotech
Piscataway, NJ
OW B7332 Coexistence SP11.1
AS/400 Oracle
Citrix/Fat