Xk01 manual sap r33/10/2024 There are 3 screens with tables on XK01 out of which we use only 2 tables – Bank details and Patner functions hence 2 of the Personas screens are based on the table screens.ġst Persona screen is based on the Address screen combining the control screen where we had the VAT reg.no as mandatory.So one may need to design the NEXT button on 1st screen such that the Mandatory fields on the Control screen are also filled in along on the Address screen of Personas custom fields. In our scenario we have reduced the screens by 3 times – 9 to 3 screens.įirstly eliminating the tables customization not becuase its not possible (Thanks to Steve Rumsby for his wonderful blogs on Personas working with Tables to make it possible)but because we might invest little more time and also may not promise all the table validations and F4 field help that the standard tables on Personas inherit. If we are able to carefully design the requirements it is pretty viable to reduce the screens. However the tricky part is the screen flow from one to another given that it is conditional because of the mandatory fields to fill in and further validations. to reduce the number of SAP GUI screens working with Vendor Master(XK01) transaction. So this is about a Personas requirement in our Org. Thanks to Steve Rumsby for recommending to blog post this □
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |