Could i use 'HR_MAINTAIN_MASTERDATA' to create new employee ?

Dears
it seems using PA40 to create new employee.
i just want to create simple person with infotype 0000, but when i using 'HR_MAINTAIN_MASTERDATA' it will automitically jump into new screen of new infotype such as 0001 without push saving button the same as i use PA40.
How could i control the screen sequence ?

Hi,
You cannot create Employees using this FM HR_MAINTAIN_MASTERDATA. This FM can be used to maintain infotypes AFTER an employee/applicant has been created in SAP(pa40).
i think there are no FMs to create Employees. There are FM's to create,update,delete,delimit etc other infotypes but IT0000(actions) Need to be performed either using PA40 or thru other mass data entry precedures like LSMW etc. where Recording of a transaction is performed.
and coming to the jumping of screens u mentioned, it is initiated by Infogroups, where the sequence of infotypes to be maintained while performing an action are defined.
you can remove the infotypes you dont want to maintain by identifying the infogroup and deleting it from there.
also for this FM 'HR_MAINTAIN_MASTERDATA' the important import parameter itself is PERNR? how are u using this FM to create an employee?
any special reason why u wanna use a Function module to create an employee?
Message was edited by:
Hruser

Similar Messages

HR_MAINTAIN_MASTERDATA create new employee with specific PERNR

I have a list of new employee to import into SAP in automation
And this employee have a I have a list of new employee to import into SAP in automation
And this employees have a their id
How can i create new employees into SAP with a their id ?
thanks

Is your system set up to assign a new employee number when the hire process is initiated? Why are you giving people an employee number before they are hired into the HR system?
If you use PA40 I think (not sure) you can assign an employee number on the screen.
SL

Creating new Employee in ECC

Hi,
i am new to SAP and new to this group also, Can any one help me how to create new employee(HR) in SAP using the BAPIs, after creation of employee how can i check the new employee details in SAP.Can one give me step by step approach to solve this problem.
Thanks in advance.
Thanks & Regards
sushma

Hi,
Welcome to SDN. Please post your question in the correct forum for better replies.
/community [original link is broken]
Regards,
Harini S

Creating New Employee Record

Hello Expert,
I am very new to SAP HR module. Is anybody knows hoe to create new employee record in SAP HR module?
Other than creation, My requirement also is to edit some data given pernr number using pa30 transaction.
Any help??
Thanks,
Prashant

Prashant,
To hire an employee, go to PA40.
Leave the personnel number field blank; as it is internally given by the system.
Give the date on which the employee is being hired.
Select 'Hiring' action from the list of actions.
Press F8(Execute).
This leads to different Infotype records, which need to be filled and saved accordingly.
~Kumar K

How to remove 'Create new employee' option for a scenario in org modelling?

Hi Luke,
We want to remove 'create new employee' option that appears under 'actions' in details panel for a position in scenario (for org chart).
I checked in linkconfiguration folder for position, but it doesn't show this option to be disabled. I also checked detailspresentationconfiguration folder but no luck. I am assuming, it must be pretty different to achieve this for a scenario object.
Please help!
Thanks,
Prashant

Hi Prashant,
I'm not entirely sure this can be changed. It doesn't appear to be controlled through configuration or XSL. My guess is it is hard-coded.
Sorry I can't be of more help.
Best regards,
Luke

Use LSMW to create new MMR.

Hi All,
When using LSMW to create new MMR, for example material 202851 was created. However, when using MM03 to display this material, it says"The material 202851 does not exist or is not activated"
What does this mean?
Thanks.
Jason

I am doing migration project for more than 11 years. I load all kind of material masters with its individual depth in one go.
But I usually use IDOC method instead of the batch input.
Because most of my projects are migration projects from SAP to SAP. But it works either way, anyway.
Please tell in detail where your problems are, You say you loaded it, but SAP says you did not. You have to trust SAP.
It does not find your data. It is just a program that tells you it does not find your values, so there are no emotions in the game.
In most cases the error is already in the source file.
But you have to know has well how the source file has to look to make your migration succesfull.
Search the forum, There have been many links to well documented LSMW documentation that show how the source file looks and what you need to do in batch input, to make it work.
By the way, SAP has issued a very good book on LSMW. Even it costs a lot bucks, it is worth. As well the SAP documentation at service.sap.com/lsmw is worth to be read.

Hr_maintain_masterdata to create new emp, error='Pers num not yet assigned'

Hi All,
I'm going to need to use the fm hr_maintain_masterdata to create a new employee. I've done up a test program just to get it working before i begin. When i run the code below i keep getting the error 'Personnel number has not yet been assigned'. Can anyone tell me what i'm doing wrong? Or can anyone tell me where i can find info on how to use this FM.
data: t_prop_vals type table of pprop,
        modified_keys type table of pskey,
        return type bapireturn,
        return1 type BAPIRET1.
data: wa_prop_vals type pprop.
        move '0000' to wa_prop_vals-infty.
        move 'massn' to wa_prop_vals-fname.
        move 'A1' to wa_prop_vals-fval.
        append wa_prop_vals to t_prop_vals.
        move '0000' to wa_prop_vals-infty.
        move 'massg' to wa_prop_vals-fname.
        move '01' to wa_prop_vals-fval.
        append wa_prop_vals to t_prop_vals.
        move '0001' to wa_prop_vals-infty.
        move 'werks' to wa_prop_vals-fname.
        move '1101' to wa_prop_vals-fval.
        append wa_prop_vals to t_prop_vals.
        move '0001' to wa_prop_vals-infty.
        move 'persg' to wa_prop_vals-fname.
        move 'F' to wa_prop_vals-fval.
        append wa_prop_vals to t_prop_vals.
        move '0001' to wa_prop_vals-infty.
        move 'persk' to wa_prop_vals-fname.
        move '01' to wa_prop_vals-fval.
        append wa_prop_vals to t_prop_vals.
        call function 'HR_MAINTAIN_MASTERDATA'
          exporting
            pernr                    = '02000511'
            MASSN                    = 'A1'
            actio                    = 'INS'
            tclas                    = 'A'
            begda                    = '20081204'
            endda                    = '99991231'
          importing
            return                   = return
            return1                  = return1
          tables
            proposed_values          = t_prop_vals
            modified_keys            = modified_keys
          exceptions
            others                   = 1.
if not return1 is initial.
write: return1-number.
write: return1-message.
else.
   message s054(hrwpc_pcr).
endif.
Many Thanks,
Liz.

Hey,
Thanks for the response to you too. Can you explain a little more what you mean by ' it is interfearing with number ranges'. I've checked the documentation on se37 and didn't find it much help to be honest.
Regards,
Liz.

BAPI for create new employee

Hi,
There is any BAPI for create a new employee (transaction pa40)?
Basically a bapi that create employee number and assign personnel area, EE group,...
I suppose that BAPI_PARTNEREMPLOYEE_CREATE is for external customer users... not the bapi that we are looking for...
Regards.Thanks.

Hi Garcia,
The FM calls the transaction PA30/PA20 based on your activity whether to create/display.
If you do not have the FM HR_MAINTAIN_MASTERDATA
You can use even BDC to create the employee data.
Fill all the required data for an employee and call the transaction PA30 for each infotype.
Also HR_INFOTYPE_OPERATION implicitely calls the HR_MAINTAIN_MASTERDATA .
search for the same ..and also look for the include LHRMMU03.
Check for Function group HRMM which has these FM's

How to use HR_MAINTAIN_MASTERDATA to terminate an employee

Greetings experts:
I'm working on an inbound interface that, among other things, can terminate an employee. I'm new to ABAP and so it was recommended to me early on to record PA40 for this action. That seemed to be working great until they added a new action and the index position recorded by SHDB no longer was accurate. I tried reproducing the list in PA40 using some queries but that didn't work either.
So now I've been asked to use HR_MAINTAIN_MASTERDATA. I understand the basics of how this FM works but I'm not sure how to relate what the recording was doing to this function module. The recording touched 3 infotypes: 0000, 0001 and 0378. Some of the fields were defaulted on the screen so I didn't need to provide them in the BDC code, i.e., "PSPAR-WERKS", etc. Now that I'm having to "manually" setup these infotypes I don't know what values I can omit and which absolutely must provide.
Can I use the code from the recording as a guide? In other words, if I didn't record a field because it was being defaulted will it also be defaulted if I use HR_MAINTAIN_MASTERDATA?
Many thanks and Merry Christmas to all.

Yes, Steve, HR_MAINTAIN_MASTERDATA is basically a FM that reproduces PA40. I use this FM for all the interfaces that require measures and besides some bug or two, the FM works perfectly, be it for the hiring or firing measures. Like PA40, when you fill the MASSN field, the FM will go through every infotype that is specified in that infogroup and will fill each infotype with the default values unless you pass them in the PROPOSED_VALUES table. For the values to pass, it's pretty simple as well, all you need is the name of the field (in the PA structure and not the screen name like in Batch Input) and the value you want to pass. Here is a sample code for you ...
Also, you can even use the parameter DIALOG_MODE to make the input visible so you can see if some strange error occurs, you can see exactly what it is, just use DIALOG_MODE = '2' for visible.
data: return type bapiret1.
data: w_pernr type p0001-pernr,
        w_pnalt type p0032-pnalt,
        w_begda type p0001-begda,
        w_massg type p0000-massg,
        w_retcode type sy-subrc,
        w_dial type c.
clear : w_massg.
w_massg = '01'.
if NOT P_MASSG IS INITIAL.
    w_massg = p_massg.
endif.
LOOP AT P_TAB.
    clear : wa_proposed_values, proposed_values, t_output.
    free proposed_values.
* Caso o motivo não venha do ecran de seleccao entao fica 01
* Preencher os dados para cada infotipo usando a tabela "proposed_values"
*** Dados Infotipo 0000
    wa_proposed_values-infty = '0000'.
    wa_proposed_values-fname = 'P0000-MASSG'.
    wa_proposed_values-fval = w_massg.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0000'.
    wa_proposed_values-fname = 'PSPAR-PERSG'.
    wa_proposed_values-fval = P_TAB-PERSG.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0000'.
    wa_proposed_values-fname = 'PSPAR-PERSK'.
    wa_proposed_values-fval = P_TAB-PERSK.
    append wa_proposed_values to proposed_values.
*** Dados Infotipo 0016
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-CTTYP'.
    wa_proposed_values-fval = P_TAB-CTTYP.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-CTBEG'.
    wa_proposed_values-fval = P_TAB-CTBEG.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-CTEDT'.
    wa_proposed_values-fval = P_TAB-CTEDT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-PRBZT'.
    wa_proposed_values-fval = P_TAB-PRBZT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-PRBEH'.
    wa_proposed_values-fval = P_TAB-PRBEH.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-EINDT'.
    wa_proposed_values-fval = P_TAB-EINDT.
    append wa_proposed_values to proposed_values.
*** Dados Infotipo 0001
    wa_proposed_values-infty = '0001'.
    wa_proposed_values-fname = 'P0001-BTRTL'.
    wa_proposed_values-fval = P_TAB-BTRTL.
    append wa_proposed_values to proposed_values.
*    wa_proposed_values-infty = '0001'.
*    wa_proposed_values-fname = 'P0001-PERSG'.
*    wa_proposed_values-fval = P_TAB-PERSG.
*    append wa_proposed_values to proposed_values.
*    wa_proposed_values-infty = '0001'.
*    wa_proposed_values-fname = 'P0001-PERSK'.
*    wa_proposed_values-fval = P_TAB-PERSK.
*    append wa_proposed_values to proposed_values.
*** Dados Infotipo 0002
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-ANRED'.
    wa_proposed_values-fval = P_TAB-ANRED.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-CNAME'.
    wa_proposed_values-fval = P_TAB-CNAME.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-VORNA'.
    wa_proposed_values-fval = P_TAB-VORNA.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-NACHN'.
    wa_proposed_values-fval = P_TAB-NACHN.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GBDAT'.
    wa_proposed_values-fval = P_TAB-GBDAT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GBLND'.
    wa_proposed_values-fval = P_TAB-GBLND.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GBORT'.
    wa_proposed_values-fval = P_TAB-GBORT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0336-COUBI'.
    wa_proposed_values-fval = P_TAB-COUBI.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0336-PARBI'.
    wa_proposed_values-fval = P_TAB-PARBI.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GESCH'.
    wa_proposed_values-fval = P_TAB-GESCH.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-NATIO'.
    wa_proposed_values-fval = P_TAB-NATIO.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-FAMST'.
    wa_proposed_values-fval = P_TAB-FAMST.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-ANZKD'.
    wa_proposed_values-fval = P_TAB-ANZKD.
    append wa_proposed_values to proposed_values.
*** Função HR_MAINTAIN_MASTERDATA
* Perform PA40 via Maintain_masterdata
    clear w_dial.
    if p_modo = 'X'.
      w_dial = '2'.
    endif.
    call function 'HR_MAINTAIN_MASTERDATA'
      EXPORTING
        massn           = 'CD'
*        massg           = w_massg
        actio           = 'INS'
        begda           = P_TAB-EINDA
        werks           = P_TAB-WERKS
        plans           = P_TAB-PLANS
        dialog_mode     = w_dial
      IMPORTING
        return1         = return
      TABLES
        proposed_values = proposed_values.
    if not return is initial.
      CONCATENATE return-message_v1 return-message_v2 into t_output-mensagem.
    else.
      t_output-mensagem = 'Medida E1 criada com sucesso'.
    endif.
ENDLOOP.
Edited by: Pedro Guarita on Dec 22, 2008 5:10 PM

Error while creating new employee in CAF Core application

Hi
I am novice to the CAF, this is my first CAF Core application which I have created and deployed in J2EE engine successfully. Its ready for Testing, here I am trying to create a new employee but while saving it, giving error like:-
ERROR. Exception thrown in method createEmployee. The transaction is marked for rollback.: Exception thrown in method create. The transaction is marked for rollback.: com/sap/caf/rt/exception/CAFIllegalAccessException
Anyone can help out me.
Regards
Srikanth

Hi Cindy Herrman,
FYI , that check box already unchecked, while setup the employee entity only that Permission check box unchecked, still I am getting same problem.
-Srikanth

How to Use iSetup to create new environment in copy of clean master.

Hi,
I want to use iSetup to create a complete new environment. No manual setup has been done yet in the copy of the master (no Business Group, No OU, no Chart of Acc: nothing). Source environment is being setup rightnow by functional consultants
Can one please provide me with a manual or guideline how to start this challenging job. Maybe a best practise can be used ?
In the end we want to setup an environment based on a clean master.
( practical data: eBS 12.1.2 on linux )
Thanks in advance
Guido

Hi Guido,
You can get in touch with [email protected] who is the product manager for iSetup. He would able to assist you to go forward in the right direction.

Use USERID from DB and increment it using position() to create new USERID's?

I'm trying to do the following in XSQL:
<?xml version="1.0"?>
<database connection="test" xmlns:xsql="urn:oracle-xsql">
<xsql:include-request-params/>
<xsql:query id-attribute="" tag-case="lower" rowset-element="maxuserid" row-element="idnum">
SELECT MAX(USER_ID) AS "USERID"
FROM LKUP_USER
</xsql:query>
<xsql:insert-request table="LKUP_USER" transform="/dvd/xsl/admin/createusertransform.xsl"/>
</database>and XSL:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="/">
<ROWSET>
<xsl:choose>
<xsl:when test="/request/parameters[not(row)]">
<xsl:for-each select="/request/parameters">
<xsl:call-template name="generate-rows"/>
</xsl:for-each>
</xsl:when>
<xsl:otherwise>
<xsl:for-each select="/request/parameters/row">
<xsl:call-template name="generate-rows"/>
</xsl:for-each>
</xsl:otherwise>
</xsl:choose>
</ROWSET>
</xsl:template>
<xsl:template name="generate-rows">
<ROW>
<FIRSTNAME><xsl:value-of select="firstname"/></FIRSTNAME>
<LASTNAME><xsl:value-of select="lastname"/></LASTNAME>
<PASSWORD><xsl:value-of select="password"/></PASSWORD>
<EMAIL><xsl:value-of select="user-email"/></EMAIL>
<ACCESSLEVEL><xsl:value-of select="accesslvl"/></ACCESSLEVEL>
<USER_ID><xsl:value-of select="/maxuserid/idnum/userid + position()"/></USER_ID>
</ROW>
</xsl:template>
</xsl:stylesheet>which returns the following:
<?xml version="1.0" ?>
- 
- <database>
- <request>
- <parameters>
<password>test</password>
<lastname>test</lastname>
<firstname>test</firstname>
<accesslvl>5</accesslvl>
<user-email>test</user-email>
</parameters>
- <session>
<access>1</access>
<emailparam>[email protected]</emailparam>
<adminfirstname>Malik</adminfirstname>
<adminlastname>Graves-Pryor</adminlastname>
</session>
- <cookies>
<JServSessionIdroot>57ta3u4mns</JServSessionIdroot>
</cookies>
</request>
- <maxuserid>
- <idnum>
<userid>17</userid>
</idnum>
</maxuserid>
- <xsql-error action="xsql:insert-request">
<message>'java.sql.SQLException: ORA-01722: invalid number ' encountered during processing ROW element 1. All prior XML row changes were rolled back. in the XML document.</message>
</xsql-error>
</database>You can see what I'm trying to do, but I can't figure out exactly how to implement it. I want to avoid the problem of conflicting USER_ID values in the Oracle DB, so I figured, pull out the max USER_ID before submission and use that when 'row-ifying' the data to create new USER_ID which are incremented based on the position() function.
Help? Is this even possible?
p.s.: I realize that I might not be able to do this because the query is not a "request". Is there another way of accomplishing this task?
p.p.s.: I don't have my XSLT book yet..
Malik Graves-Pryor

My book, Building Oracle XML Applications, has lots of XSLT material and examples :-)
You should use:
<xsql:set-stylesheet-param>
to accomplish this. Remember again that the XML that the <xsql:insert-request> sees is not the XML of your data page, but the POSTED XML. The posted XML document will not have the maxid value in it. So, instead just use a top-level stylesheet parameter in your stylesheet:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

<xsl:param name="maxid"/>
<xsl:template match="/">
Rest of template here.
Refer to value of maxid in any XPath expression
in the stylesheet with $maxid
</xsl:stylesheet>then in your XSQL page, you use <xsql:set-stylesheet-param> instead of <xsql:query> like this:
<xsql:set-stylesheet-param name="maxid">
select max(user_id) from lkup_user
</xsl:set-stylesheet-param>However -- and this is not an XSQL issue, but a general database thing -- you need to be careful about concurrency issues using the SELECT MAX() trick. If two requests come in simultaneously, they will both SELECT MAX() and get the same current maximum number, then both try to insert a new user. One will (presumably) violate your primary key constraint.
It's better to use database SEQUENCES instead, so the numbers are guaranteed to be unique. To use a sequence you would just change your SQL statement above to be:
SELECT yoursequencename.NEXTVAL FROM DUAL
instead of the SELECT MAX() query.

[SOLVED] Use clonezilla, or create new partitions then copy?

I'm migrating my Arch for the first time. What would you recommend for a complete newb in this area, cloning the disk with some tool like clonezilla, or creating partitions manually and copying everything over?
I saw a few threads on how to make partitions and copy stuff over, but they all leave me with uncertainties. Would cloning the hard drive be an easier option?
Last edited by trusktr (2012-04-01 21:50:09)

trusktr wrote:
Hey graysky thanks for the answer. Could you also provide some insight into why not using clonezilla?
For a someone doing this for the first time ever (like me), creating the new Linux partitions seems kind of tricky. The only time I've ever created partitions was from the Arch Install CD which made them automatically. I'd imagine that I would create each partition with the same size, except for the putting all the extra space of the new hard drive into the home partition.
Best for learning now. Making a partition is easy to do. Just be sure you carefully keep track of drive letters when doing it. Plus, the last time I looked, clonezilla wasn't updated for several years and didn't support ext4. This may have changed though.
Advice: draw out on paper your partition scheme, sort of like a map. ie
/ 15 GB /dev/sda1
/boot 200 MB /dev/sda2
/var 10 GB /dev/sda3
/home <<rest of drive>> /dev/sda4
Then use a util like fdisk or gptdisk to do the partitioning itself. If using GPT, make sure to have an empty 1 MB partition for the BIOS!
https://wiki.archlinux.org/index.php/GPT
Here is a nice walk through using GPT --> https://wiki.archlinux.org/index.php/SS … DED_METHOD

Using iSetup to create new operating within an existing application

Hi
We have a requirement to replicate multiple operating units and related config within Finance, Procurement, Inventory and EAMS ... so we have previously configured the operating units again in each new environment - crp, dev, sit, uat, prod -
There are multiple selection sets available which include operating unit setup (we are on 12.0.5) including Financials Operating Unit Level Setup, Financials Setup and Organisation structure.
There seems to be overlap the ... Which is the best to initially migrate the OU
Is there a document or metalink note which covers the dependency for various migration requirements?
In our case we are migrating within the Business group, legal entity and set of books so would expect we could load it via selection sets with little intervention.
thanks for your assistance, the forum is excellent.
Regards

This is Mugunthan, Development manager for iSetup.
Yes, you are right. Operating Unit is available in multiple selection sets. The idea is that it is grouped wherever it makes sense so that you need not switch over to other selection set to load the data.
For example, you cannot load most of the financial, hrms and manufacturing related data without loading operating unit. So, we have added the same API under multiple theme. But essentially it is the same API which is getting reused everywhere.
Coming to hierarchy document, it is available. You can send a mail to [email protected] I will send you the doc. I will publish it to metalink as well soon.

Use Automator to create new subfolders in a selected folder

This seems like it should be easy to accomplish, but I have had no luck.
I want to be able to select a folder, and then run an Automator Service to create a specific set of subfolders within the selected folder.
I am able to set up automator to create the subfolders, but it does so in the folder containing the selected folder.
Any suggestions on how to accomplish this simple task?

Which type of variable should I choose? I tried "text" but there's no way to set it to "input"? There are many Variables in the Library.
Here's how I have things set up now, I thought the "Service receives selected 'folders' in 'Finder'" (at the very top of the workflow area) would pull in the selected folder.
Thanks!

Could i use 'HR_MAINTAIN_MASTERDATA' to create new employee ?

Similar Messages

Maybe you are looking for