Skip to Content

HR Interface Toolbox – PU12



I tried to Google on PU12 issues and could not find any good help over the internet or even SDN. I see many people posting questions but not many giving answers to them. After I found mane answers to my problems I thought of posting a blog of my work on SDN so that people in future get a good starting point.


This tutorial is for beginners in PU12 who have never used the tool; it is equally beneficial for Functional as well as Technical persons. This is my first blog on SDN and it might lack few technical points, few explanations might not be best, please feel free to post questions and I will try my best to answer those questions.


HR Interface Toolbox (a.k.a. PU12) is used for transferring HR Masterdata and Payroll data. It is a very robust tool and helps cut a lot of coding and testing costs. Even then, it is not widely used in the world the reason is not its limitations, but the learning curve that is involved. Many people do not have expert level skills in HR Interface Toolbox and try to avoid it, but they get involved in a lot of custom coding, bugs, testing and maintaining costs.


There are a lot of customizations and technical details in PU12 that can be found in this 184 pages document from sap. I will try to cut the blog to minimal simplicity. I will just go through the payroll data transfer process, and will discuss the Masterdata transfer process in a little detail.


First, PU12 by default transfers the data in plain text files, but it can be tweaked a little bit to send data through IDOCs. See the ADP interface provided by SAP, which sends data through IDOCs. Also, it does not give any configuration level control to send (pipe or comma) delimited files.


Let’s kick-off. I will strongly suggest going through the document provided by SAP at this link. This will be bible for us, and all answers can be found over there.


Let’s start with transaction code PU12. You will see following screen:


Export tab will be used to execute the interface and read the results.


Export History tab is used to see the log, and the results of previously executed runs.


Configuration tab will contain all of our development; this is where we are going to spend more than 95% of our development/configurations time.



Interface Format: This is the place where we specify the input layout of our interface, what data will be required by interface, we will specify the tables, infotypes and fields, plus we will do the conversions, restrictions, change validations and other configurations to pick the right data for our interface.


File Layout: In File Layout we will specify the output of the interface, we will specify which fields will be on the output, their widths, their order, and their frequency (e.g. for each employee).


Ideally, we need to generate the Interface Format and File Layout every time we do a change in any of them, so that it generates fresh ABAP code for the configuration and we do not get any error.


Let’s start with an interface name ZRAO and hit ‘create’


You will be asked the country grouping, one important thing; one PU12 interface format is only for one country, if you are dealing with many countries, then you will need to create as many interface formats. And, another important thing … this step cannot be undone or changed later on, if you chose a wrong country then you will have to delete the interface and create it again from scratch. File format can be reused for other countries as it does not require country grouping.



Continue, and you will be asked what data you want to include in the export:


In next step include the infotypes that will be required by the interface:



Then it will ask to give names to the programs that it will generate for the interface format, I will suggest to click on suggest values button, or you can chose a name according to your organization’s standards for the main program and then click on suggest values:

Here is how the interface format should look like now:


Choose the fields that will be required by the interface and remove all unwanted fields, this will be useful in the overall runtime of the interface and also reducing the fields will be good in troubleshooting and debugging, as the code generated will fetch data for all the fields that are included here and if you are debugging through the code then anticipate thousands of lines that you will need to run through …


Select the fields by double clicking and click the delete button to remove them:



I have limited the fields to following:


Configurations in Interface Format:


Table Entries: Here we specify which entries to pick, all of them are self explanatory, and we will chose 2nd option for both infotypes.


Conversions: These are on field level click on the field and then click on the conversions icon, there are three kinds of conversions that we can do.

Constant conversion will give us a way to convert the values in the infotypes to constant values that we will provide in a table format, lets do a constant conversion on FAMST field of infotype 0002.


Table value conversion looks into a database table for and matches values of infotype field mimicking a SELECT statement’s where clause and picks up the corresponding values. Let’s try it on country field of the infotype 0006.



Through above conversion we will pick up the description of the country from table T005U. Very handy.


User Exit conversion This is where a developer will be involved and code the custom logic, if above two methods cannot give the required conversion. We will need to create a Z program with a subroutine in it, it is important to specify the type of the program as ‘subroutine pool’.


Looks like a funny example, but just for the sake of learning ….




Here is the code inside that user exit:





  IF P0006-ORT01 = ‘My City’.

    RESULT = ‘Detroit’.


    RESULT = P0006-ORT01.



ENDFORM.                    “CHANGE_CITY

Restrictions : Here we restrict the records that out interface will fetch from infotypes, it is like a where clause of select statement and only constant restrictions are allowed, we can specify only values here, lets do a restriction on infotype 0006 to get the specific subtype ‘1’. Here is how we do it:


Attributes: A very important place where we specify the general behaviors of the interface:


Few important things to note are … we should select the Interface without payroll if we intend to not include the payroll data in the interface. And … we can change the report category that will be displayed when we run our interface. For details of each option please refer to the SAP documentation.


Change Validation: This is where we will specify the change validations, Interface Toolbox will look for the changes only on the fields specified here and will only export the whole record.


Single Field Validation: This option can be applied at infotype or table level and it verifies that only the changed items are exported instead of whole record. The changed data that is unchanged is replaced with ‘#’ signs and the changed data is replaced with new values.


Delimited: This option will allow specifying if the data is still valid for the current period or not. Interface toolbox will put ‘<” sign for the invalid data for current period.


Key fields: Here we can define a composite key by selecting multiple or single fields of infotypes, which will make it a key and the key fields will be only exported once. This will help us in case we want to export the data for some specific key values just once.


Relationships : If we want to export some fields depending on if we are exporting some other fields then we define relationships, for example click on NACHN and then click on  then select VORNA, and do same for VORNA then click  and select NACHN. This will ensure that whenever NACHN is exported then VORNA will be forcefully exported and when VORNA is exported then NACHN will be forcefully exported.


User Defined Change Validation: Here we can put a user exit and do some logic before we approve the change validation, this subroutine will contain only one parameter which will be used by Interface Toolbox to determine if change validation should be enabled or disabled. A return value of ‘1’ will make it active and ‘0’ will make is disabled and no change validation will be carried out.


Here old data for an infotype is available in OLD_xxxx table and new changed data will be available in NEW_xxxx table and we can put a custom logic to decide on change validation.



This is how our change validation will look after above exercise:


Let’s call it enough configurations on Interface format and let’s go to File Format.


Before that, remember to save the changes in change validations and go to the initial screen of PU12 without saving the changes in Interface Format, sometimes if you save twice, once change validation and then interface format then it will erase the changes in change validation, so I would recommend to save changes only for change validation and then without saving the changes in interface format, generate the Interface Format.


File Layout:

The default output for PU12 is text files and we will need to define a file layout of our exported data.


Give a custom name for the file layout, as a standard I will use the Interface format name and _OUT for file layout name. Hit Create.



Save it, and generate the programs same as we did in Interface Format by clicking the  icon and then suggest values, and then save and generate the file layout.


In file layout we need to understand a following hierarchy:


Blocks are at the top level of the hierarchy and they do not contain any data by them selves, they contain further structures which also do not contain any data, each structure can contain fields which actually contain data in them. It is important to use these as per our logic for the requirement.


First create a Block by hitting  icon.

Give it a name; this block will be processed after processing of employee data. This is another important step to consider, if we go with default value i.e. ‘During processing of employee data’ then multiple lines will be output for each employee. If you want to give the file a header line then select the option that says “begin of file”. It will be repeated once, and the output will be exported into the main export file, we can choose additional 4 files to send the output in, but we will limit our exercise to the most common scenarios i.e. one export file.


Next create a structure:


And then a field lets say EMP_NUMBER

Length of a referenced field will ask in later step a field name to limit the output length to that referenced field. Because of Dynamic value we will chose a field that will populate the data in this field.

In above screenshot you can see I have chosen the field P0002-PERNR so the field width will be picked same as field width or P0002-PERNR field.

In above screenshot I have chosen the global variable &VAR_PERNR which will contain the pernr value of the currently processed PERNR. Current entry makes sure that the record is active.


Field contents can be set using following methods:


A constant value, as it says will replace the contents with a constant value, irrespective of the contents of the infotype.

Dynamic value will get the data from the infotype or the global variables, there are many global variables available, that are available by hitting F4).

A user exit will execute a custom routine and the returned value will be placed in the contents.


Scroll up and this is how it should look like right now:


You can notice that there are a number of places where we can place our custom logic to be processed before and after some steps. Here is a list of their rank for each block.


  1. User Exit before (Block)
  2. User Exit before (Structure)
  3. User Exit (field 1)
  4. User Exit (field 2)
  5. User Exit (field n)
  6. User Exit after (Structure)
  7. User Exit after (Block)


All these user exits have common layout and parameters; they can all be programmed in same program file.


Here is an example user exit called from the field level. I have created a field that will contain the weekday of P0002-BEGDA and it will be placed in the field.


I have also shown how to pass an infotype field in user exit. Also another thing to note is that the subroutine has to have 16 parameters, out of which first 15 are input parameters to the form and the 16th is the return parameter which will replace the contents of the field in file layout.


The first, last and current value columns specify which record of the infotype to pick to pass value for P0002-BEGDA, the first, last or current active record.


Here is the code snippet in the subroutine:


FORM GET_DAY USING P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11

                                              P12 P13 P14 P15 P16.






      DATE    = P01




  P16 = L_WEEKDAY.


ENDFORM.                    “GET_DAY


Create few more fields as displayed in the screenshot below:


Save the File Layout, go back and generate again. It might ask to give program names if you have not done so, click  and click on suggest values.


Now our File Layout configurations are complete, but a real time business requirement might be far complex and involve multiple user exits and configurations. It is time to see the output!


Export Tab


Go to export tab, select first option and provide the interface format name ZRAO in our case, and execute. Give the payroll area and File Layout that should be run right after the Interface format gathers data, in our case ZRAO_OUT.


Export Options:


Very important to consider!


Only Original Periods: This option will suppress the retroactive accounting and the results will be only from original payroll period. If you want to take care of retro changes then un-check this checkbox.


Repeat: If you want to repeat the result of the previous run of interface format then select this option.


Update: This option will update the change log and create the text file on server, if you un-check this option then nothing will change and no file will be generated, useful before doing actual runs.


Display Log: If you want to see the log of the changes done/or to be done then check this option.


Results Analysis:


In first run, notice following, one page down:


See everything coming through, now run the interface again with same parameters



See first name and last name are all hashes, that’s because we have them in change validation and they were not changed since last run and they are replaced with ‘#’. This is change validation in life.


There are many other results that will be self explanatory in the log.


At the bottom of the log there will be statistics:


One pernr was locked so that is not included in the output.


Now go back to initial screen on PU12, select the last option:


Download from TemSe, i.e. Temporary Sequential File:


In TemSe Object, hit F4 and if asked select this option:


Select the latest TemSe file


Give a path to save the file on your system, like c:\Results.txt


And execute it …


This will create a text file on your system, which will contain all the results. This is what can be exported to any third party later on through FTP, email or what ever your company wants.


Export History Tab

This is where you can see what was exported in past for any interface format or pernr, this is also a good place to start over … By deleting all results of an interface format you can run the baseline again as if it never happened.

You must be Logged on to comment or reply to a post.
  • Hi,

    I really appreciate your blog and your efforts to put everything at one place.

    I have had a similar requirement couple of days back and I have used PFAL transaction, and had activated change pointers for the message type HRMD_ABA. These jobs were automated and all the filtering activities were carried out through BD79 and distribution model filters.

    So just wanted to check if there are any additional advantages or additional functionalities which PU12 can give me so that I can use it in my later requirements.

    Once again, nice effort by you. I appreciate that.


    • Thanks for taking time to read my blog,

      I am familiar with transaction PFAL, I have not played a lot with it so cannot give you a comparison of PFAL and PU12.

      But, as you have enough experience in PFAL I can point out a few key features that might make them different.

      – I guess PFAL always sends data through IDOCS, on the other hand PU12 by using default settings makes text file of the exported data.

      – PU12 has change pointers at a little more detailed level, we can apply change validation at field level instead of infotype level, and we can apply rules and put custom code for that change validation to trigger or not to trigger. Additionally, we can change the data before and after change validation if there is such requirement.

      – PU12 has about 15 different hooks to put your ABAP code (in form of user exits), that might not be the case with PFAL.

      – PU12 is all configurations and anything can be achieved by putting ABAP inside user exits.

      And above all, PU12 can be used for payroll transactional data too (other than just HR Master Data), I guess that PFAL does not have that functionality.

      BUT, there is a big learning curve to master all aspects of PU12. which one should be for a successful requirement implementation.

      Any further question, feel free to buz!


      • Hi,Thanks for the excellent document provided by you.I have a query regarding PU12. I have configured PU12 for transferring  master data only. But my output when I download on local PC always comes in one line for one pernr even though i pass structures in different blocks. I want many lines for single pernr in the file output.Could you please let me know where I am going wrong.
        Also could you please let me know whats the use of Conversion with file layout radiobutton? I did  not understand Input/Output Export files on selection screen when I execute ‘Converison with file layout’. No documentation details it. Thanks in advance.


  • Hi Shafiq Rehman,

    First of all thank you for your really helpful tool to configurate PU12. I followed all your steps and a real export program exist now.

    But there is just one thing that is not working and that is to update the export program.

    When I am doing an update without filling the name for the file layout I have the following error:
    “An error occurred when opening the “export file”

    When I am filling the file layout  I have the following error:
    “An error occurred when writing to an export file” (Error Number E107).

    “File processing: end of file”.

    Do you know what I am doing wrong?
    Thanks in advance!

    Kind regards,

    • “When I am doing an update without filling the name for the file layout” I did not understand what you are trying to do, can you please share screen shots of the process?

      What update you are doing? Is it on the main screen?

    • Thats very possible, you will need to copy the Interface Format and File Layout OTMU. These are for USA.

      Inside that copy, go to file layout (say ZOMTU) and go to first block, i.e. IDOC_CONTROL_HEADER, go inside user exits and you will see how to change partner profile etc and see other user exits in other blocks to see how to populate the idocs. If you know ABAP it will make much sense to you, otherwise have your ABAPer look into it as how to change the code.

      Hope it helps.

      • Hi,
        Great post,
        My requirement is i need to use idoc HROT_XXM and convert the data into XML file to be placed on the application server(Same client),being new to IDOC & ALE can you please guide me what all steps are needed from configuration side in terms of IDOC and ALE like (partner profile,ports,etc).
  • Hi Shafiq,
    Its a good knowledge sharing that you have done through this blog.I have a couple of queries regarding PU12.

    1) Can you please elaborate a scenario where in we can use delimit & key fields options in change validation?

    2) Is it mandatory that we need to include all fields, that we have created in interface format (for fetching required field values), in file layout ?   We were having issues regarding the extra fields in the interface over-writing(in the sequence in which it has been declared in the interface format) the existing values in file layout

    Thanks and Regards,

    • Hi Kiran,

      For the first part of your question, the answer will be pretty long. It is answered in the SAP’s document on PU12. You will need to digg it a little.

      For second part, you cannot find in SAP Document:- No, It is not mendatory. You can include whole infotypes in your interface format and yet include none of its fields (or just one). The Interface Format fields will be available during execution and they will hold data, it is not mendatory to export that data in File Layout.


  • Hi Shafiq! This is an excellent document that I have seen thus far on using PU12 interface toolbox. At my client’s place, gross payroll is planned to be run in SAP and net calculations in ADP. The format of output file asked for by ADP is .csv file, while the default of PU12 output is a text file. What is to be done to get the output in CSV format?
    • Thanks for appreciation Bob,

      Unfortunately there is no standard way to get the output in a delimited file format, PU12 will only give you text file output.

      That was the bad part, good part is that you can still do it. You have to create fields in the File Layout that will hold the delimitation character (for example pipe, comma etc.) You cannot have Tab as delimitation character.

      To do it, simple create a field of 1 constant character after each field and assign it comma as constant data. Such that you have output in folloing format:

      10000078,John Smith, USA, 05212008,

      It is a very simple way, but if I have succesfully made it difficult to understand then please feel free to follow-up with questions.

      And, when you are downloading the file from TemSe, simple give it an extension of .csv and you are good to go.


  • Hi Shafiq,

    After running the export, I see in the export statistics that number of personnel numbers selected  is zero for a given payroll area. I checked and found the following to be okay;
    1) employees or pernr’s do exist in that payroll area with all of the required master data
    2) control record exists and is valid for that payroll area.
    3) I generated the interface format and the file layout programs.

    Any idea why no personnel no’s are being selected by the interface?

  • Dear Shafique,
    Thanks for a great blog.

    I want to know, is there any known issue if we build big interfaces through PU12 ? I mean maintanence or something else ? Any idea ?

    • Only issue is learning curve and expert resources. I believe PU12 can handle almost all cases for payroll data export, you will definately need a goof functional HR person and a good technical HR person, to carry out the PU12 implementation. Both of them should have good knowledge of PU12, otherwise chances are that you will crash into many issues that require expertise.
  • We are using standard Master Data Export for us (PC00_M10_OTEM).  The Interface Layout and File layout are both OTMU.  This places the output into an IDOC, basic type of HROT_USM.  My problem is I want to add the supervisor area (PA0001-MSTBR) to the Interface and output.  I added MSTBR to P0001 in the Interface Layout for OTMU but am unclear how to get it in the output idoc of basic type HROT_USM.  The data does get placed in the E1HR_OR segment but not in a field.  It gets appened to the field after the MSTBR field in the Interface Layout. 

    How do I go about getting the MSTRB field into the E1HR_OR segment as a field?

    • I guess you will need to enhance the IDoc and segment type E1HR_OR, add the new field in the segment. You can ask an ABAPer to help you out in doing this.
  • Hi Shafiq it is great you have posted such a useful tool in abap hr. I appreciate your contribution. I am engaged with a serious problem in PU12.
    In the export tab in the Interface format when I execute it is showing me some termination after entering the payroll area D2. For your reference I am enclosing the screen shot below

    When I execute I am getting a termination message as given below

    Can you please guide me that where I got wrong and for your reference also I am enclosing the screen shots of Configuration

    Change validation screen

    File Layout screen

    Scroll down of the above screen

    • Hi Shafiq it is great you have posted such a useful tool in abap hr. I appreciate your contribution. I am engaged with a serious problem in PU12.
      In the export tab in the Interface format when I execute it is showing me some termination after entering the payroll area D2.
      When I execute I am getting a termination message as given below

      as PArea ignored because not realeased: D2
         Program Terminated.
      It is also saying tat payroll area not selected for export instead i have selected payroll area: D2

      • You should check if the payroll area is released or not in transaction PA03. Check with your HR Functional resource if you need more help on that.
  • Hi. This is a nice doc. on PU12. I was struggling to find a document to understand Interfaces in a better way. I do not know how can I give points to you on SDN. But you definitely deserve gratitude from my side. Thanks again
  • Excellent blog!

    Issue : When we are exporting file out of SAP (PU12) for ADP in (no log display mode) as CSV,
    the export file contains # within it’s fields.

    A ray of light on this issue shall be really helpful.

    Best regards,
    Manish K

  • Shafiq,

    This is an excellent document! It was very helpful in creating my interface and file formats. I had some questions regarding the output file.

    1) Is there a way to flag an entire record when one of its fields is changed (i.e. if a field is deleted, updated, or inserted)?

    2) I’ve set up a batch job in SM36 to generate the report automatically. Is there a way to automatically download the text file from TemSe?

  • Hi Shafiq, Thanks for this excellent blog. It was very helpful. It works fine for HR interface. Our requirement is to fetch time data for employees, who do not have payroll data in the system. When we try to run the export program for those people, who do not have any payroll record, it doesnot seem to fetch them. In debugging, we found that it goes and looks for cluster directory entry for those people in the selected period and if not found it rejects them.
    We have selected the check box for option “Interface without payroll” in attributes. But still it is not fetching and looks for rgdir.
    Any help in this issue would be much appreciated.
    D. Balajee
  • Hi Shafiq.
    I really would like to thank you for this excellent presentation on how to setup PU12.
    But, there is always a but. 🙂
    When I get to Export tab and fill in the payroll area and so on, as you explain, and run the report, I get this error message below.
    Hope you can help me with this.
    Best regards  //  Peter B

    An exception occurred that is explained in detail below.
    The exception, which is assigned to class ‘CX_SY_DYN_CALL_ILLEGAL_TYPE’, was
    not caught in
    procedure “GET_DAY” “(FORM)”, nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The call to the function module “DATE_TO_DAY” is incorrect:

    The function module interface allows you to specify only
    fields of a particular type under “DATE”.
    The field “P01” specified here is a different
    field type

  • Hey shafiq,
    I could reach to this blog throgh an answer on SDN forums by you.
    Please let me know in case you / anyone interested, can provide some inputs on below requirement:

    1.I have to transport time data (from CATSDB) to a third party systems.Can this be done? Is this better than development of a new custom program?
    2. Does PU12 store the last run date of interface?
    3. With PU12 can we also trasfer data in custom (Z) tables?


    Kumud Singh

    • 1. I think it only works on infotypes, you can do this on IT 2001/2002 etc, but I will not advise it. It’s better to create a custome program, there will be a lot of logic if you want to retrieve data from CATSDB. The learning curve for PU12 is not worth Time Export ptogram.

      2. PU12 does not store it I guess.

      3. No Z tables support in PU12, but you can always write code in user exits to do anything.

  • Hello Rehman,

    Thank you for contributing about PU12 configuration.
    I have question relating to the IDOCs,below i will explain process we use and list my issues and questions:

    We do our payroll thru ADP. We interface with ADP/ADP connect thru Master data export IDOC(PC00_M10_OTEM) and Time wage type Export IDOC(HR_PC00_OTTM).

    In the Master data export – When we make a change in position to an employee record via PA40 action ,we change the infotype Org assignment (0001) ,but when we run the Master data export -it picks up all the infotype key segments like Banking,address,personal data,benefits,tax information,where we didn’t make any changes.

    1. Why does it pick all the other infotypes where changes are not made?
    2. Is it picking because in PA40 action we have other infogroups ( note here: we skip all the other infotypes during performing this action and make change only in 0001 infotype and  save it?)
    3.In the attributes configuration of the export interface format – New change validation is un checked -Is this causing the problem of picking up all the infotypes?

    Hoping to get an earlier reply.

  • Sir! I have the same sentiments as everyone above, this is a fantastic information! I only have one question and that is what determines the data that goes in the idoc? I have results in the PU12 (two records for infotype 0014, two different wage types), where one is end dated and the end date falls in the pay period we are running so it was exported but is not flowing into the idoc (transaction WE05). Any ideas?

    Thanks in advance, as it looks like a lot of people have questions for you.

    Best regards, Heather

    • Hi Heather,

      It’s been a few years since I last worked on PU12, nevertheless, I’ll try to answer your question. There is an option where you can control which records go out in the interface. Please refer in my blog to section “Configurations in Interface Format:” Which option you have selected here for infotype 14? Can you attach/email screenshot of where you see the results in PU12 for two records of infotype 14 ?



  • Hi,

    The document is really help full for learners.

    I have the requirement on exporting only master data. i.e. from IT 0000,0001,00002 and 0006 .

    The Interface will check if any of the above mentioned Infotypes has changed on the current date. If yes, then these changes will be included in the interface.

    1) I do not have any report category on selection screen? Only thing I need to get the data from mentioned info types if any of the fields (selected Fields) changed comparing system date?  Can i run the interface without giving payroll area?

    2) Can u plz suggest me the approach for writing the code? Where do i need to write the code or configuration?

    3) Process for downloading the pipe delimited .txt file?

    Regards, Harika

    • 1. Yes, you can run it without payroll area, explore the option of Report Category on attributes window.

      2. You do not need to write any code if it’s straight forward pull from tables. If there is any logic involved then refer to the user exits, that’s where you write all your code.

      3. There is no straightforward way to download the file in pipe delimited format, but you can achieve this by adding a one character field which will contain the pipe symbol after every data field in your file layout.

  • Hi Shafiq

    Nice Document.

    Although I needed a help in PU12 interface.

    We are having a strang situation here.

    When we execute the interface if Display Log check box is unchecked, no files are downloading. If we execute with Display log check box then we are getting a Short dump with message

    “No more storage space available for extending an internal table.” .

    Please help

    • You should select “Update” option if you want the file written, and if there are memory issues then try to unselect the “Display Log” option. If you still get error then someone from BASIS team in your company might be able to help.

      • Hi The problem we are facing is when we uncheck Display Log check box, files are not exported to file path. This Display Log check box is the one in bottom. And when this check box is checked only then files are downloading.

    • Hi

      If file is already written also you will get this kind of message . I guess , you have change validation activated on you file layout .

      So Update check box must be selected when you are looking same data to be downloaded again at the same time check the ‘change validation’ in configuration button .