Updating Infotype 0001 (PA) as per OM structure
Dear Experts,
Can any one pls let me know how to update info type 0001 position and Org Unit from OM info type 1001 (Relation ship)
I have created relation ship between position and holder (A 008) in OM structure and want to get it reflected in PA info type 0001. Is there any standard program exists.
With regards,
Chandrasekhar.
Hi,
T-Code - SA38
try reports - RHINTE00 ,RHINTE10,RHINTE20 & RHINTE30
Regards,
Param
Similar Messages
-
Updating InfoType 0001 in ABAP
Our parent company is passing different begin and end dates from Infotype 0001 to our HR system. In our system an employee would have a start date of 3/1/2005 but our parent company has the same employee in there system as a start date of 1/1/2008. I was looking at using user exit EXIT_SAPLRHA0_003 to capture these and add the parent companies dates into our Infotype 0001 so that there feed doesnt overwrite our original dates. I have attempted to use HR_INFOTYPE_OPERATION with no luck. Any one have a possible way to update InfoType 0001 without using a BDC?
What exactly is the issue? In any case HR_INFOTYPE_OPERATION in turn calls HR_MAINTAIN_MASTERDATA so you might end up with the same issue with either function call.
~Suresh -
Using FM HR_INFOTYPE_OPERATION to update infotype 0001.
We're using FM HR_INFOTYPE_OPERATION to update the infotype 0001 (Organisation). We basically have the Cost center field grayed out on the entry screen so can not update it via BDC, which the cirrent method that we use to create new employees, based on data passed in from a third party system. When then attempt to update the employee record (using Copy) and the FM mentioned.
We first get the details of the infotype using FM HR_INFOTYPE_GETDETAIL, and this work perfectly, returning all the information required. We the update the structure returned by the RECORD parameter and then use the FM HR_INFOTYPE_OPERATION, like so:
call function 'HR_INFOTYPE_OPERATION'
exporting
infty = '0001'
number = gs_p0001-pernr
SUBTYPE =
OBJECTID =
lockindicator = 'X'
validityend = '99991231'
validitybegin = gs_p0001-einda
RECORDNUMBER = '001'
record = gs_p0001
operation = 'COP'
nocommit = 'X'
importing
return = gt_bapireturn1
key = gs_bapipakey
exceptions
others = 1.
However, we receiving an error in the gt_bapireturn1 itab basically giving the error PG 184. When I look up the error it basically says that to update this info type we need an exclusive lock, which I would have thought exists when using the LOCKINDICATOR parameter. The previous FM ( HR_INFOTYPE_GETDETAILS) returns blank against the SPRPS fileld (Lock indicator) when reading the infotype data, so it's not previously locked or anything.
We're using version 4.0b, which I know is pretty old, but surely this update should work.
Has anyone encountered this problem before, and, do you think I should be able to update this field even though it's grayed out on the screen ?.
Jason
Edited by: Jason Stratham on Mar 16, 2010 11:41 AMI read that I should be using the enqueue and dequeue FM's despite the LOCKINDICATOR parameter.
This I have now done, but am now receiving an error PG 428 'A complex application error has occurred', but I'm none the wiser in knowing why this error has occurred. Has anyone encountered this error before?.
I'm beginning to feel that despite being told that I can use the HT_INFOTYPE_OPERATION function module it may well purely imitate the front screen processing, which does not allow us to change the cost center value. Is there any way that this might be done. We're on version 4.0b, and I'm sure that in later version there might be a BAPI that almost directly updates it. I guess there's no such method for 4.0b?.
Jason
Edited by: Jason Stratham on Mar 16, 2010 12:06 PM -
When I change the position by PPOM / PPOME for single Person, is not updated infotype 0001, Organizational Assignment, I see it by PA20.
Although into the table T77S0 is set:
PLOGI ORGA X Integration Switch: Organizational Assignment
PLOGI PLOGI 02 Integration Plan Version / Active Plan Version
The version 02 is active.
What is missing ?
Any assistance would be greatly appreciated.
Thanks.
Best regards.
EricHi Eric,
>PPOME is Transaction code in OM to maintain structure and IT 0001 is a Infotype in Personnel Administration.
>There is no direct relationship but, when you maintain Position which is a integration point between OM & PA, it has a direct relationship to both the modules if the integration is active.
>This issue is because the change what you made in OM is not updated in PA, this is a common issue and as other members already suggested you need to check the integration switches and run reports (RHINTE00, RHINTE10, RHINTE20, RHINTE30) to update the database both in OM & PA.
Regards
Chandrashekar -
Not able to update organizations units in an infotype 0001
Iam unable to update organizational units, positions through lsmw in an infotype 0001 if i do manually it is updating in 1infotype.
Iam trying to run reports rhinteoo still not able to figure it out
experts share your experience on thisRan LSMW Record created successfully for position
If I see in organizational Assignment Infotype The record is not displaying
As per your email Iam trying reports to display organizational units for the positions
RHINTE10
Done Livrun
Next step RHINTE20
My position is not in the list that is 600450
Executed RHINTE30 I wonder how do we come to know personnel number when we are recording positions and organizational units. Still i checked personnel number in organizational assignment infotype and executed but it is displaying No batch input folder created . Yes we didnt create any batch input for personnel numbers we created batch input for positions and org units.
I believe we need to run first two records
After running above reports i checked in an organizational assignment Infotype . Still data is not updating what would be the cause please let me know -
Cost center (KOSTL) is not updating in HR master table for infotype 0001
Hi ABAP gurus,
We have one interface where we are posting the HR master data using the IDOC (IDOC_INPUT_HRMD) into SAP.
While updating cost center, We have one issue regarding infotype 0001.
It is working fine for all the fields except: KOSTL, ORGEH, STELL. Surprisingly the created IDOC contains the value in these fields but it is not getting updated in master table PA0001. I have tryied inserting the value manually and it is working fine and tried with BDC Programming and no issues. Only we have this issue while we want to use the IDOC. This is mandatory in our interface.
While debugging the IDOC function module I found that one condition is there for these three fields.
CHECK NOT inte IS INITIAL. where inte value is being fetched from table t77s0 based on
GRPID = PLOGI
SEMID = ORGA
In this condition I see no value for this combination and hence it is not getting further. I am not sure how this condition does exist for only these three fields and not for others.
Can any please provide the reasona and solution for this.
Appreciate the help in advance.
Thanks,
JitenderDear Mohan,
Try assigning your cost center to position it will default both your org unit and cost center.
Cheers! -
I HAVE ENHANCED INFOTYPE 0001. NOW I WANT TO UPDATE THOSE FIELDS. IS THERE ANY BAPI which will update the infotype 001.
please help me.Hi umesh,
1. There is on FM
HR_INFOTYPE_OPERATION
2. But its not RFC Enabled (as u want)
3. U can make another Z FM (RFC Enabled )
and use this FM inside it.
regards,
amit m. -
Standard programs to update infotypes
Please provide updates for this question:
What are the standard SAP programs to update infotypes ( Ex: 001 / 002 / 003 ) .
I will be uploading data from legacy system ( Excel / Text file ) and would like to use standard programs
before going ahead with BDC .
Thanks
RohanHi,
I checked out the program you stating.......
In that program itself if you check the documentation its given how to add in fields.......
You can use report RPUSTD00 to transfer master data from your old HR system.
The dataset to be transferred must be stored in a sequential file. The file is stored under the name specified in the "logical file name" field (for more information on logical file names, read the IMG section entitled Additional client-dependent file name maintenance).
The report reads this dataset and creates a batch input session for transaction PA30.
The data description of your old record is defined according to the structure HRDATASET. If this structure does not meet your requirements, create the structure CI_HRDATAS in the ABAP Dictionary. In this structure, you can store the infotype fields to which data should be transferred. Make the necessary changes in RPUSTD00.
Example
If the include CI_HRADATAS contains the field F1 which is to be assigned to the infotype nnnn, add the following ABAP statements to FORM Dnnnn:
CLEAR BDCDATA.
BDCDATA-FNAM = 'Pnnnn-F1'.
BDCDATA-FVAL = SATZ-F1.
APPEND BDCDATA.
If the FORM Dnnnn does not exist for your infotype nnnn, copy FORM D0008 to FORM Dnnnn. Replace the 0008 by your infotype number:
FORM Dnnnn.
CLEAR BDCDATA.
BDCDATA-PROGRAM = 'MPnnnn00'.
BDCDATA-DYNPRO = '2000'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'Pnnnn-F1'
BDCDATA-FVAL = SATZ-F1
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'BDC_OKCODE'.
BDCDATA-FVAL = '=UPD'.
APPEND BDCDATA.
ENDFORM.
The FORM Dnnnn is called directly after FORM D0008; see the ABAP statement indicated as "<------ INSERT in the following (starting at line 1730 in the standard system):
LOOP AT INFTAB.
CASE INFTAB.
Include all infotypes in your action *
WHEN '0002'. PERFORM D0002.
WHEN '0001'. PERFORM D0001.
WHEN '0006'. PERFORM D0006.
WHEN '0007'. PERFORM D0007.
WHEN '0008'. PERFORM D0008.
WHEN 'nnnn'. PERFORM Dnnnn. "<------ INSERT
WHEN OTHERS. WRITE: / 'Infotype not included:' (008), INFTAB.
STOP.
ENDCASE.
ENDLOOP.
Parameter DSLOGNAM
Logical file name
Parameter MAPNAME
Session name
Definition
Enter any name for the session to be created. -
Hi,
I have to update Infotype 1016 using the BAPI FM "BAPI_HRMASTER_SAVE_REPL_MULT".
Two tables need to get updated, HRP1016 & HRT1016.
The Data in the HRT 1016 is a Table Data for Record in HRP1016.
Say: Orgunit O 10000001 has two standrd Profiles..
IF I go to PP01 and create the two standard profiles,
I will have a single record in HRP1016 which has a TABNR field value generated.
Now for this TABNR, I have two record in HRT1016 each corresponding to one Profile.
I need to create these three ( 1 + 2 ) entries using the FM. The FM has Input structure BAPIHR1016 which allows only one profile per structure. Also it asks for the TABNR field, which I donot know until the actual creation.
If I send one profile & TAB_SEQNR as 00001, its working fine, generating a TABNR for me.
But when I send two records in the FM, one with TAB_SEQNR 00001 & other with TAB_SEQNR 00002, the second one is overwriting the first one, and I have only the second profile assigned.
Please help solve this issue.
Thanks in Advance.
Suryakiran D.For updating the IT 1011, we have 6 fields in the BAPI.
But when I go to PP01, i have only one field in input mode, rest all are disabled for input.
Even if I fill the values in all the fields, only one is considered for update, and rest all are recalculated using this.
Can someone please let me know how we can decide this.
Thanks,
Surya -
[MRS] Conflict in Infotype 0001 between A and S object type
Hi,
We use SAP MRS on top of our HR box. (sorry, I am not a SAP MRS expert so bear with me please....)
As we activated PA-PD integration, whenever a Work Center (otype A) is assigned to an employee (otype P), it updates the Infotype 0001 accordingly (PLANS and OTYPE field) while also inserting a new entry into T528B and T528T tables.
This is consistent with what the RHINTE30 program does (look at the $plste [S] and Work Center [A]):
But, the employee is also assigned to a position (otype S)! It makes much more sense to have Position filled in the Infotype 0001 rather than Work Center!!
Thus, our first approach would be to deactivate PA-PD integration for Work Center (otype A) and only leave it active for Position (otype S).
Thanks in advance for your help.
Best regards,
GuillaumeGuillaume,
Has your issue ever been solved?
Kind regards,
Lieselot -
BUS1065 - SAP HCM - Employee changes in infotype 0000 + infotype 0001
Dear all,
I have a problem with the customizing in order to recognize the changes in infotype 0000 + infotype 0001 for employees.
What do I want?
If there is a new hire, a rehire, a retire or a company-left action, I want to start ONE workflow in order to dispatch the employee data to several satellite systems considering the new validity dates.
What happens currently?
I maintain a rehire action through transaction PA40 and the system raises several events so that the workflow start multiply, meaning raises event hired, rehired, companyleft, ...
My customizing:
TCode: SWETYPV
BO BOR-Objekttyp BUS1065 COMPANYLEFT WS91000007 0
BO BOR-Objekttyp BUS1065 HIRED WS91000007 0
BO BOR-Objekttyp BUS1065 POSITIONCHANGED WS91000007 0
BO BOR-Objekttyp BUS1065 REHIRED WS91000007 0
BO BOR-Objekttyp BUS1065 RETIRED WS91000007 0
TCode: SWEHR1
P Person 0000 BUS1065
P Person 0001 BUS1065
TCode: SWEHR2
P Person 0000 Maßnahmen APP 100 BUS1065 CACS_LOG_HRINFTY
P Person 0000 Maßnahmen DEL 100 BUS1065 CACS_LOG_HRINFTY
P Person 0000 Maßnahmen INS 0 BUS1065 HR_EVENT_RULES_PA0000
P Person 0000 Maßnahmen INS 100 BUS1065 CACS_LOG_HRINFTY
P Person 0000 Maßnahmen UPD 0 BUS1065 HR_EVENT_RULES_PA0000
P Person 0000 Maßnahmen UPD 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun APP 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun DEL 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun INS 0 BUS1065 HR_EVENT_RULES_PA0001
P Person 0001 Organisatorische Zuordnun INS 100 BUS1065 CACS_LOG_HRINFTY
P Person 0001 Organisatorische Zuordnun UPD 0 BUS1065 HR_EVENT_RULES_PA0001
P Person 0001 Organisatorische Zuordnun UPD 100 BUS1065 CACS_LOG_HRINFTY
TCode: SWEHR3 (For testing purpose only one entry)
P Person 0000 INS 1 BUS1065 HIRED
Can anybody tell me how I can customize our system so that the system raises only event hired for a new employee hire and e.g. companyleft event for a termination action?
Thx you all in advance for your support!!!
In case you need more information, don't hesitate to contact me!
Kind regards,
AndréHi
TCode: SWETYPV
BO BOR-Objekttyp BUS1065 COMPANYLEFT WS91000007 0
BO BOR-Objekttyp BUS1065 HIRED WS91000007 0
BO BOR-Objekttyp BUS1065 POSITIONCHANGED WS91000007 0
BO BOR-Objekttyp BUS1065 REHIRED WS91000007 0
BO BOR-Objekttyp BUS1065 RETIRED WS91000007 0
Iam not sure about what you have done in the customizing but, the above settings represents that the same workflow is set as receiver for different events.
Now As per my understanding what ever you have posted, I feel like you want to restrict the workflow intiiation only for some of the events. and for the remaining events you do not want to start the workflow.
If this is the case then I would suggest that to over come any kind of issues, I suggest you take a copy of the workflow WS9100000070 and assign the new workflow template to each different event, in this way you can differentiate which workflow is acting as a receiver for the event.
and accordingly you activate the Event Linkages in SWE2 txn too.
Regards
Pavan -
ALE Message type HRMD_A Infotype 0001 is incorrect using PROOF flag = X
Hi
We have an issue using HRMD_A for Infotype 0001 with the PROOF flag swithed on. Using the PROOF flag triggers a call of HR_MAINTAIN_MASTERDATA instead of a direct write to db tables. However sometimes the update of Infotype 1 is incomplete and records are lost. The data goes through a transformation in the inbound BAdi, here I have checked the sequence is still correct. But when the data is written to Infotype 1 it seems to overwrite the last entries.
If anyone has any experience with this, I would be very interested for any input.
Thanks in advance
SonnyHi Sandip
Thx for your response. If I understand you correctly you suggest I use the HR_INFOTYPE_OPERATION. This could be an alternative, but I would prefer to understand the reason behind the error.
HR_INFOTYPE_OPERATION actually calls HR_MAINTAIN_MASTERDATA, so this FM might not solve the issue, but it does give the option for updating one record at a time.
Sonny -
Function to update Infotype 0003
Hi,
I want to update 'Run payroll up to' field of infotype 0003 based on some conditions .
Is there any function module to update Infotype 0003 fields ?
ThanksI have calle the FM with action 'EDQ' .
It did not uloack the pernr .
I am using this code :
SELECT SINGLE STAT2
INTO LV_STAT2
FROM PA0000
WHERE PERNR = INNNN-PERNR AND
ENDDA >= INNNN-BEGDA AND
BEGDA <= INNNN-ENDDA .
IF SY-SUBRC = 0 AND
LV_STAT2 <> '3' .
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
PERNR = INNNN-PERNR
INFTY = '0003'
IMPORTING
SUBRC = LV_SUBRC_1
TABLES
INFTY_TAB = IT_PA0003
EXCEPTIONS
INFTY_NOT_FOUND = 1
OTHERS = 2.
IF LV_SUBRC_1 = 0 .
READ TABLE IT_PA0003 INDEX 1 .
CHECK SY-SUBRC = 0 .
WA_PA0003 = IT_PA0003 .
IF INNNN-BEGDA > IT_PA0003-ABWD1 .
Reset the "Run payroll for pers.no. up to" date
WA_PA0003-ABWD1 = INNNN-BEGDA .
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '0003'
NUMBER = INNNN-PERNR
RECORD = WA_PA0003
OPERATION = 'EDQ'
IMPORTING
RETURN = LV_SUBRC_2 .
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '0003'
NUMBER = INNNN-PERNR
VALIDITYEND = WA_PA0003-ENDDA
VALIDITYBEGIN = WA_PA0003-BEGDA
RECORD = WA_PA0003
OPERATION = 'MOD'
NOCOMMIT = 'X'
IMPORTING
RETURN = LV_SUBRC_2 -
Hello experts,
I need to update the IT 1007 marking a position as Vacant.
Is this can be done using a Function Module? like the one that updates infotype in the PA30 (HR_INFOTYPE_OPERATION) ?
Thanks in advance for your help,
ArepaKingDear King,
Not much sure but kindly have a look at function module :-
RH_UPDATE_INFTY
Short Text
Change infotype records
Functionality
With this function module you can change multiple infotype records for OM objects from Personnel Planning database tables (HRPnnnn). The infotype tables of the table parameter INNNN must all have the structure Pnnnn (logical structure for the infotype nnnn). The records you want to change must exist in the Personnel Planning database tables. If not, this triggers the exception ERROR_DURING_UPDATE.
Might be other members can have some more better ideas as well.
Hope this helps.
Kindly reward in case useful.
Regards & Thanks,
Darshan Mulmule -
Supervisor name in infotype 0001
Hi Friends,
One of my new requirement is show the name supervisor beside supervisor field in Infotype 0001.This name is based on what ever the employee number is updated in supervisor field.So can any one update the possible to solve this requirement.
Thanks,
arjunHello Arjun,
To fulfill your requirement you need to modify the screen and add the field next to supervisor field.
Generally modifying SAP standard screens are not recommended. But still we can do that. You need to add a field next to the SUPERVISOR.
Regards,
Kiran I
Maybe you are looking for
-
Error in Database installation while installing CRM 4.0 on Linux
Hello, We are installing CRM 4.0 on LINUX platform, We have successfully installed the Central Instance, but while installing the database instance, when we start the OUI the installation starts and hangs at 0% <b>installing java runtime environment
-
Conversion in Seeburger BIC and XI
Hi, We receive e-mails with an EDIFACT messages (ORDERS or DELFOR) as an attachment. The e-mails are received in the same INBOX on an e-mail server. I configured a sender mail adapter in XI and added the PAYLOADSWAPBEAN to put the e-mail attachment i
-
I'm creating a connection pool for soademo and having issues setting the JDBC URL to access the database. This is what have:jdbc:oracle:thin:@mydb.com:1521:orcl and this is what I get when the URL is tested: Unable to establish connection. Error mess
-
Defining Multiple operations for async calls in OSB
Hi, I have three Asynchronous BPEL processes- BPELProcessA, BPELProcessB and BPELProcessC I am trying to invoke BPELProcessB and BPELProcessC from BPELProcessA through an OSB Proxy service. I want to use a single proxy service to make calls to BPELPr
-
Does data guard run in 11 g primary and 10g standby vice verca in any situation physical or logical. Is the any possibility.