on 11-11-2014 9:49 AM
Guys - a prompt response would be much appreciated.
These are the suggested entries for VA02...
From what I understand I am using:
4002: Sales Header Overview which I am boiling down to one simple screen using tab caching
4001: Sales Order Item Overview - again a simplified version of with tab caching
4003: Sales Order Item Detail with tab caching
BUT also for the possibility of third party requisition in some cases there is also a flavour of VA02 SAPLEBNE/0102 (called from the Schedule Line tab of 4003).
i) What I'm not clear about from the example table above is why the new screen number X00X contains (is linked to) the old screen numbers for one header screen (4002) & one Item screen (4001) YET screen 4003 (another line item screen) is linked to new screen ID Y00Y?
ii) The new screen numbers can be anything, e.g. ZZZZ, YYYY as long as they are unique .... is that correct?
iii) We have not written any new program code so I'm assuming I can leave that column blank?
iv) Would VA02 SAPLEBNE/0102 by linked to 4003 in this context?
Any help much appreciated.
Regards.
Patrick.
Hi Patrick,
Please refer to this post to udnerstand screen and control id overwrite entries
4001 (Payment cards tab - also note the program name is SAPLV60F here), 5002 (conditions tab) and 4002 (all other tabs) are part of Doc header details screen. Hence they are mapped to X00X.
5003 (conditions tab) and 4003 (all other tabs) are part of item data screen. Hence they are mapped tp Y00Y.
Yes, you can map to anything like XXXX, YYYY, ZZZZ.
New program name is required when your mapped entries differ in old program name. In this case 4001 has SAPLV60F whereas 5002 and 4002 has SAPMV45A. So it is mapped to SAPXXXXX.
Always note that Personas flavors are identified by combination of tcode+program name+screen number. So even if you have used same codes or program names in other transaction, they dont clash.
Hope that makes sense.
Thanks
Chinthan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Chinthan,
As described in my comment above, please note that I believe the following screen override entries need to be added to the OSS Note (and likewise for VA02 and VA03):
VA01 | SAPMV45A | 4001 | 9099 | SAPMV999 | Overview - All Tabs except Sales | |
VA01 | SAPMV45A | 4008 | 9099 | SAPMV999 | Overview - Sales Tab |
I had to add VA01 entries to combine screens 4001 and 4008 of program SAPMV45A. These are the Overview screens (not header or items).
Rob
Hi Rob,
For standard order even sales tab has 4001, so there is no overwrite required for overview screen. If you are using specific type of order then it is possible that the sales order tab uses different screen number (4008) in dynpro code and you need to have overwrite entries for overview screen as well. So based on the use case and order types, we may need more or sometimes less overwrite rules.
Thanks
Chinthan
Helpful as usual Chinthan - thanks.
Your blog is a little more user friendly than the OSS not but it basically reiterates the same content. Please don't take this the wrong way - I mean this as friendly constructive criticism only.
This is such an important concept in the Personas world and has far reaching consequences (I have had to re-do more than one flavour with issues emanating from this area) I think it should be flagged up in some way as a key concept and would benefit greatly from having a visual tutorial with a spoken commentary.
I know you guys are busy and there’s not always time for the nice to have stuff, but as I say … this seems to me to be an important one.
As an aside – it seems that you don’t always have to re-build flavours after making changes to the screen id control table as the OSS note suggests. Apparently if you map existing screens to one already existing ID, i.e. map 4001, 4002, & 5002 to 4001 rather than X00X (and associated programs) the flavour’s integrity is retained.
Once again - many thanks.
All the best.
Patrick.
Hi Patrick,
Appreciate your feedback. SCN post gives more flexibility to add screenshots etc but not all customers will see it. So we have the note which also includes the list of overwrite entries which can be used by customers.
We understand that recreation of flavors is annoying, hence we are working on it. So keep looking out for new features .
Regards
Chinthan
Although I am not an expert regarding screen overwrites, here is what I used for VAxx transactions:
Transaction Code | Program | Original Screen Number | New Screen Number | New Program | Screen Description | Screen Example given in OSS Note |
VA01 | SAPMV45A | 4001 | 9099 | SAPMV999 | Overview - All Tabs except Sales | Not in note |
VA01 | SAPMV45A | 4008 | 9099 | SAPMV999 | Overview - Sales Tab | Not in note |
VA01 | SAPMV45A | 4002 | 8099 | SAPMV888 | Header Data - All Tabs except Conditions and Billing Plan | X00X |
VA01 | SAPMV45A | 5002 | 8099 | SAPMV888 | Header Data - Conditions Tab | X00X |
VA01 | SAPLV60F | 4001 | 8099 | SAPMV888 | Header Data - Billing Plan Tab? | X00X |
VA01 | SAPMV45A | 4003 | 7099 | SAPMV777 | Item Data - All Tabs except Conditions | Y00Y |
VA01 | SAPMV45A | 5003 | 7099 | SAPMV777 | Item Data - Conditions Tab | Y00Y |
VA02 | SAPMV45A | 4001 | 9099 | SAPMV999 | Overview - All Tabs except Sales | Not in note |
VA02 | SAPMV45A | 4008 | 9099 | SAPMV999 | Overview - Sales Tab | Not in note |
VA02 | SAPMV45A | 4002 | 8099 | SAPMV888 | Header Data - All Tabs except Conditions and Billing Plan | X00X |
VA02 | SAPMV45A | 5002 | 8099 | SAPMV888 | Header Data - Conditions Tab | X00X |
VA02 | SAPLV60F | 4001 | 8099 | SAPMV888 | Header Data - Billing Plan Tab? | X00X |
VA02 | SAPMV45A | 4003 | 7099 | SAPMV777 | Item Data - All Tabs except Conditions | Y00Y |
VA02 | SAPMV45A | 5003 | 7099 | SAPMV777 | Item Data - Conditions Tab | Y00Y |
VA03 | SAPMV45A | 4001 | 9099 | SAPMV999 | Overview - All Tabs except Sales | Not in note |
VA03 | SAPMV45A | 4008 | 9099 | SAPMV999 | Overview - Sales Tab | Not in note |
VA03 | SAPMV45A | 4002 | 8099 | SAPMV888 | Header Data - All Tabs except Conditions and Billing Plan | X00X |
VA03 | SAPMV45A | 5002 | 8099 | SAPMV888 | Header Data - Conditions Tab | X00X |
VA03 | SAPLV60F | 4001 | 8099 | SAPMV888 | Header Data - Billing Plan Tab? | X00X |
VA03 | SAPMV45A | 4003 | 7099 | SAPMV777 | Item Data - All Tabs except Conditions | Y00Y |
VA03 | SAPMV45A | 5003 | 7099 | SAPMV777 | Item Data - Conditions Tab | Y00Y |
In my naming scheme:
9 = Overview
8 = Header Data
7 = Item Data
I may have over anlalyzed this and just used the names in the Note. But I believe you are correct, they can be anything as long as they are unique. Just be aware that once you create a flavor for VAxx, any changes to the overwrite names will "break" your flavor.
Important note: I had to add two rows to properly handle the Overview screen tabs that were not addressed in the OSS Note. See my note in column 6 of the table above. I commented on this in Chinthan's blog but still no response:
In the table above, the Screen Description column is my note on what tabs I believe the screens are associated with.
Regarding your question about program SAPLV60F, screen 4001 - I believe this is a screen from the header data, not the item data.
Rob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, the last two columns got cut off. Here they are again:
Screen Description | Screen Note Example |
Overview - All Tabs except Sales | Not in note |
Overview - Sales Tab | Not in note |
Header Data - All Tabs except Conditions and Billing Plan | X00X |
Header Data - Conditions Tab | X00X |
Header Data - Billing Plan Tab? | X00X |
Item Data - All Tabs except Conditions | Y00Y |
Item Data - Conditions Tab | Y00Y |
Overview - All Tabs except Sales | Not in note |
Overview - Sales Tab | Not in note |
Header Data - All Tabs except Conditions and Billing Plan | X00X |
Header Data - Conditions Tab | X00X |
Header Data - Billing Plan Tab? | X00X |
Item Data - All Tabs except Conditions | Y00Y |
Item Data - Conditions Tab | Y00Y |
Overview - All Tabs except Sales | Not in note |
Overview - Sales Tab | Not in note |
Header Data - All Tabs except Conditions and Billing Plan | X00X |
Header Data - Conditions Tab | X00X |
Header Data - Billing Plan Tab? | X00X |
Item Data - All Tabs except Conditions | Y00Y |
Item Data - Conditions Tab | Y00Y |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.