Creating custom SAP PA infotypes HR Kennis. Hi,Often, a customer requests to save data in SAP HCM which is not present in a SAP standard infotype. For this reason, SAP made it very easy to create your own infotype, using transaction PM0. Steps needed to create the infotype Create if needed custom check tables. Create a custom PS structure. SAP ABAP Quick Guide Learn SAP ABAP in simple and easy steps starting from Overview, Environment, Screen Navigation, Basic Syntax, Data Types, Variables, Constants. Hi Meher I see your point. Userexit EXITSAPMF02D001 is for customer master data and since customer hierarchy is not a customer master attribute, it will not be. A technical writing and personal blog by Alessandro Banzer. Check out everything regarding SAP GRC and other IT relevant topics. Check whether the tcodes are displayed in the SAP menu. Tcodes are not displayed in this case. So how to display the tcodes along with description in SAP menu SAP Fiori Quick Guide Learn SAP Fiori starting from Introduction, Architecture, NetWeaver Gateway, Installation, Launchpad, OData Services, Transactional Apps, Fact. SUSE Linux Enterprise Server for SAP Applications is the reference platform for the software development of SAP. It is optimized in various ways for SAP applications. SAP Support Services Overview of services which are available as a component part of a Premium Engagement. This area provides descriptions of the Services which are. The PAI event of a subscreen is processed when the calling screen calls the subscreen during its PAI event using the statement CALL CUSTOMERSUBSCREEN ltarea. Home SAP Authorizations SAP CRM Authorizations Process flow of the Authorization Check in Business Transactions. SAP CRM Authorizations Process flow of the. Recurring Documents in SAP For Recurring document template we can use the following T. CodesFBD1 Creation of recurring documentFBD2 Change recurring document This. Generate your infotype in transaction PM0. Maintain the technical settings for your infotype can be done in PM0. Define infotype settings in T5. A can be done in PM0. Sometimes at this point, you need to re generate in PM0. Changing the screen in SE8. Creating check tables. First of all, the required subtype table is T5. A You do not have to have a separate check table for infotype subtypes. For other check tables not being the subtype table, first create a customizing table using transaction SE1. C customizing. Fill the fields for the table, always containing the client mandt. Fill the technical properties. Next, create a maintenance view. Go to the table maintenance generator, fill in the details like authorization group and the needed function group create one in SE8. NEW. Now, hit the link next tot the overview screen and hit LAYOUT. Change your maintenance screen in the screen painter and save and activate the screen. Create a custom PS structure. You can create the custom PS structure by defining a structure in transaction SE1. It has to be named PS9nnn, whee 9nnn is your custom infotype number. Only the normale fields need to be included, not the infotype key fields like begda, endda, infotype number, et cetera. You can check PS0. In the third tab, you can link your check table to key fields by using the KEY symbol button. Generate your infotype in transaction PM0. Now your structure is defined and activated, generate your new infotype in transaction PM0. GENERATE. Maintain the technical settings for your infotype. The technical settings of the infotype can be maintained in transaction PM0. Be sure to maintain the fieldname containing the subtype if applicable of the infotype and the check table for the subtypes. Define infotype characteristics in T5. AIn the generation of the infotype was successfull, you are now able to define the infotype characteristics in T5. A. Most of the fields can be taken over from other infotypes, but keep the following in mind The subtype table must always be T5. AThe single screen has to be filled with 2. The list screen field has to be filled with 3. The time constraint is very important, it defines how timeframes must be uniquenot unique and may overlap or not overlap 1 Timeframe of infotype must exist and may not overlap. Timeframe of infotype does not have to exist, but may not overlap. Timeframe does not have to exist and may overlap woth other records of this infotype. Sometimes at this point, you need to re generate in PM0. Check at this point if the infotype can be used in transaction PA3. The clue is, dat everytime you re generate the screen in PM0. So you really want your screen to work perfectly before going into the last step modifying the default screen using the screen painter. If your infotype does not yet work perfectly, re generate it in PM0. Changing the screen. Now the infotype has been created, you can modify the ugly screen, which was default created, making it more pretty with the screen painter. Go into your screen in se. MP9. 00. 10. 0 for infotype 9. Be aware that if you change or replace a screen element in the screen painter and re link in to structure P9. lt fieldname SAP offers this option automatically if you name the field P9nnn again, you have to manually assign screen groups to these modified fields. If you do not do this, your field will be read onyl in PA3. These screen groups are located in the properties of the creen element, check the next screenprint. Some words of advice. If you get the message infotype not supported, try re generating the infotype and make sure the subtype table is T5. A. If the check tables do not have any description when you hit F4, use a search help, an elementary search help can be defined in SE1.