Employee termination in HR system deletes BP role-BUP003 in CRM.

Hi all,
HR system is integrated with CRM.
When Employee is terminated in HR system it deletes BP role-BUP003 in CRM.Is this a standard behaviour? Is ther anyway we can stop this?
Thanks
S

Hello,
the existing process of deleting the role BUP003 for inactive employees
is standard design and will not be changed. If the role will be kept
for a terminated employee contract this definitely is an inconsistency
between the HR data and the CRM data (business partner).
There is one exception: if you have activated the time-dependance of the role
the time-frame would be limited.
Regards, Gerhard

Similar Messages

Delete request / role in ERM GRC 5.3

Hi All
I have a Role in ERM that I need to delete. Buuut, Role deletion is not possible; it has sent for approval.
In CUP we have already deleted all request (following instructions by SAP note) and there is not any request in the system.
The problem is that I can't delete this role from ERM because has been sent for approval, but I cant find the request in CUP or ERM, what can I do? Please, help me !!
Thanks in Advance.
David. ..

Hi David,
I was the same problem when i wanted to create a new role.
Confirm in the Approval stage what user you assign as approver. The system doesn´t check if this user exists.
If this user doesn´t exists, the only possibility to delete the role is create a new UME user with this user, giving the necessary roles and log in to CUP to delete the role.
I hope this help you,
Sergio

How to delete a role from other role.....

Hi All,
I have a query like....
I have created one new role ATH:MDC:INV3 and added two existing roles to that new role on DEV system ie Added ATH:MDC:INV2 + ATH:PUR:PMG0
So,now i need to remove only one role ie ATH:PUR:PMG0 from ATH:MDC:INV3.
All the 3 roles are single roles.
Is there any way to remove/delete that role or do we need to do manually by deleting one by one authorisation,which is time taking process....
Please give me if there could be any better way to approach....
Thanks & Regards,
Swapna.D
Edited by: swapna devi on Feb 1, 2008 3:53 AM

Doug,
You gave me an idea. What if you create a new folder on the desktop. Select the roll above #20, which you said will also select #20, and move that roll to the desktop folder? Will roll #20 move with the one above it? If so, then you could go back to iPhoto, drag them both to the trash, delete trash (will it delete with the roll above it?), Import to Library the pictures where you put them on the desktop.
Caution, you would probably lose some of the info from the roll you delete and re-import, like their dates, etc. So I wonder... can you select, say, half the photos in that roll and Create New Roll? Will the remaining roll still be linked to #20? If so, can you do it again and again until the linked roll only contains 1 picture? Then move it to desktop, trash in iPhoto, and re-import?
What happens if you play with it like that?

How to add/delete single role to/from CUA

Hi All,
I want to add/delete single role from CUA system. I found one FM to change roles i.e BAPI_USER_LOCACTGROUPS_ASSIGN , In function module documentation said that it will overwrites all existing roles with the roles in the table parameter.I dont want to do that. I need a FM to add/delete role to CUA system. Please help me with your suggestions.
Thanks,
Suman

I am not aware of another BAPI based way to do it. You will need to get the details of the Roles AND manual profiles assigned, and then re-assign the new set in the call.
Cheers,
Julius

Mass deletion of roles from users

I want to delete all roles from locked users. Is there a specific transaction for this instead of SU10? In SU10 one has to enter the roles to remove.

We developed our own application which locks users after a while, then removes their role assignments after a while, and then lists roles which no longer have any assignments or no one is using anything which the role authorizes.
This way you can optimize / automate periodic controls.
There is no standard monitoring cockpit for this, but you can use declaritive system params to destroy password based authentication.
The real trick with periodic controls is to target the sample before you unassign and destroy roles, but the ability to do that depends on how you buikd the roles.
Disclaimer: If you use composite roles then you have no chance. You are doomed.. ;-)
Cheers,
Julius

How to delete a role?

I could not find the catalog which FCPX may keep the role.
And I also can not delete them within FCPX itself,so...what can I do?

from the help system:
Create custom roles and subroles
You can create custom roles and subroles in addition to the five default roles (Video, Titles, Dialogue, Music, and Effects).
Important: Create custom roles and subroles with care. Custom roles (and the names of custom roles) cannot be edited or removed from the roles list. However, you can change the role assignments of clips at any time.

Reg: job termination in source system

hi experts
can anyone tell me solution for this problem after loading infopackage, status of the infopackage is showing is like this "job termination in source system", but i checked with ss it showing job gets cancelled. but i am not assigned any to the data source, so how can eliminate this problem.
regards
harikrishna.N

HI
This can happen when request IDOC is sent source system, but the source system for some reason is not available.
Ensure that source system is available. Change technical status of request to red and delete request from datatarget. Trigger Infopackage again to get data from source system.
Cheers,
Raj

AC ERM : role creation and how to delete ungenerated roles

Hi,
When you work on a role from ERM, the role is created in the back end. It will be generated only at the generation phase. But what if finaly it is decided not to generate the role, is there a way to delete the role in the BE from ERM?
It seems the only way is to go in PFCG and delete the role manualy?
Regards

Hello Vincent,
There are different tables in which the roles for RE (in frontend RE, frontend tables) and where the roles in R/3 are stored. That is, it might be that even if you are generating all the roles from RE, at a particular time the list of roles in RE is greater than number of roles in R/3 Backend. This is because:
RE roles = Generated roles (which exist at backend as well)+Ungenerated roles (which are in RE only till that particular time).
Here ungenerated roles would mean the roles which you have not yet generated in RE.
Thus, __deleting roles from R/3 and RE are two separate things__.
1. To achieve the deletion the role from Backend (R/3) you should create a request in RE to remove this role from all the users currently attached to it as there is no way possible to delete the role from R/3 by creating a request from RE. Doing this would still have the role in R/3 but with no user assigned.
2. To delete the role from RE tables, so that you do not see it again, you can Search for the role, select it and then click on the "Delete" TAB. This will delete the role from the RE tables.
Now, for the clenliness of your R/3 system, in case you do not want to see these roles in R/3 too, you can schedule a BG job to delete this or do a mass delete of all these roles say every fortnight or at whatever frequency as desired by your management.
Regards,
Hersh.

OIM - EBS - Employee termination query

I have configured OIM (9101) with EBS HR (9043) with Weblogic 10.3.
I want to know how Employee termination works. Right now if I manually enable/disable any user, the Enable User and Disable User tasks are triggered and the user is enabled/diabled in the EBS system. But I am not able to understand the flow from HR system to OIM i.e. when a user is terminated in HR system ( I don't know how), will it trigger the disable user task in OIM.
Please put some light on this matter. Thanks !!!

I always found the trusted source status mapping not to work. I would suggest creating a UDF called EBS Status. Create an entity and process adapter that both do the following:
Check the status field. Then either use the enable api or the disable api. On the entity adapter though, you should only put it on post-insert and only check if you need to disable the user.
Create a user form trigger (explained many many times on this forum). Add the task to your Xellerate User profile. Then use the adapter you created as a process task adapter to enable or disable the oim user based on the new value.
-Kevin

Regarding Employee termination

Hi Friends,
I have a problem regarding employee terminations. Generally how willwe terminate employees? I terminated using actions infotype with the action Teminated.
It worked fine. But when I run payroll for him, it is calculating for the period of termianted month as well. For example I terminated an employee in the motnh of Jul on 15th. When I tried to run payroll, it is running for this period and if I want to run for the next month it is not at all taking that PERNR. So is this the way generally it works?
Would appreciate your help.
Thanks
KM

Dear Kiran,
I suppose this is very much the normal process.
BTW kindly have a look at some SAP provided documentation :-
Making Payments after Termination Use
You can pay your employees by a normal payroll run, by cheque or an off-cycle payroll run.
You can choose to make continuous or one-off payments to employees after they have been terminated, for example, work cover payments to employees permanently disabled due to an accident at work.
This procedure describes how you set up the SAP System to make continuous and one-off payments after termination.
Procedure
Making Continuous Payments after Termination
       1.      Activate and, if necessary, modify the Organizational Assignment (0001), Personal Data (0002), Planned Working Time (0007), Basic Pay (0008), Bank Details (0009) and the Tax Australia (0188) infotypes.
These infotypes are delimited during the termination process.
       2.      To ensure that the payroll driver includes the terminated employees in the payroll run, configure the terminated employees into a separate employee subgroup.
       3.      Enter the continuous payment in either the Recurring Payments/Deductions infotype (0014) or the Additional Payments infotype (0015).
Making One-Off Payments after Termination
       1.      Change either the Basic Pay infotype (0008) or the Additional Payments infotype (0015) to reflect the one-off payment you want to make.
       2.      Perform a retroactive payroll run for the employee.
Processing based on the Payment Method
·        Payment method, Normal
Run regular payroll for the termination period to payout the employee. For retro terminations, run the payroll for the next payroll period (period that occurs after the last payroll period read by the payroll driver) to payout the employee.
·        Payment method, by Cheque
Run regular payroll for the termination period. For retro termination, run payroll for the next payroll period(period after the last exited period). The negative net payment created through the Additional Payments infotype (0015) balances out the net pay generated, thus, generating a zeroing out the net pay. This is because the in payment method By Cheque, a cheque is issued to the employee with the net pay amount generated during the termination process. Therefore, a regular payroll run after termination must not payout the employee again.
·        Payment method, Off-cycle
Run off-cycle payroll as of the off-cycle pay run date and parameters chosen from the termination process. This will payout the net payment amount updated in the off-cycle payment info type. Similar to that of cheque payment, a negative net payment is created through the Additional Payments infotype (0015) so that any regular pay run does not payout the employee.
Hope this helps.
Kindly reward in case useful.
Regards & Thanks,
Darshan Mulmule

Query regarding transporting deletion of roles

Hi,
When I delete a role in dev, in order to make the deletion effective across the landscape I need to put it in a transport request.
If I don't do that, and instead create a new role in dev by the same name as the one that was deleted, and then I transport this new role, will the new role overwrite the old one in the quality and production systems?
Or am I first required to transport the deletion, and then transport the newly created role ( by the same name)?
Thank you.

hii
This is little critical and tricky but you know whenever u do any modifcation with the role like deleting a role or creating a role the best pratice is to put in the transport request so that this request can be transported throughout the landscape .........
As per u r question dear u have created role in the development that role is already their in prd system with profile attached to it if u delete in dev and try to create the role with same name in dev again that role might not be deleted till u transport the new role frm dev to prd but their might be inconsisentcy with the new role which u have created as their might be cofusion with the two profiles the new profile and the old profile in prd server if u send the delete transport request frm dev to prd for the role which was their in the prd server the old role and profile will be lost so when u create a new role and transport it frm dev to prd their might be no inconsistency between the old profile and new profile,,,,,,,,,,,,,
takecare

How To Delete The Role We No Longer Needed

Hi Experts,
We implemented the standard SAP application architecture: DEV,QAS,PRD.
Now my problem is: There are some roles we no longer needed in our PRD circumstances, I don't want to delete them directly in PRD. How to do it? Anyone knows?
Thanks in advance!
Jason

Hi Jason,
It is client copy by client export import method.
For client export in source system --> SCC8
For import in target system --> SCC7
But I think the way prescribed by Ruchit is a better way ... You can do it in following way
Steps :
1) In Dev box --> PFCG --> give the role you want to delete --> click the transport button --> create a transport request .
Remember the transport request number.( don't release the request )
2) Delete the role in Dev box in PFCG by clicking the delete button.
3) Now in SE09 in Dev box, release transport request created in step 1.
4) Import the released the request to your test and prod box.
Now you can find the the roles has been deleted.
Please check and confirm.
Hope this will help you.
Regards,
Partha

"Program terminated in remote system NONE: Logon failed" when adding a new table

Hello,
I set up a replication flow from a SAP ERP 6.0 EHP7 with SAP ASE 16.0 source to SAP HANA 1.0 rev 82 target
I am using a standalone SLT system NetWeaver 7.0 with DMIS 2011_1_731 (with SP 1 to 7).
I have 100 tables to replicate.
I succeeded to set up replication for 57 tables. These tables are replicating properly.
Whenever I try to add a new one (with LTRC transaction, Data Provisioning -> Start Replication), the new table is marked as 'Failed' after a little while.
When I press 'Show Error Log' button I got an obscure error message:
"Program terminated in remote system NONE: Logon failed "
I do not understand this message. I checked both on SAP ASE source and SAP HANA target. I am still able to connect against both source and target.
Can you please tell how to troubleshoot this error.
Thanks in advance,
Christian

First thank you for answering my questions. I really appreciate your answers.
I rechecked the documentation.
"Application Operations Guide SAP Landscape Transformation Replication Server Document Version: 2.3 – 2014-07-08"
Page 29 - 30
3.5.2.2 Data Transfer Jobs
This section explains the relationship between the number of data transfer jobs and the number of available background work process.
Data transfer and data transformation processing on SLT server system is accomplished by the background work processes of the underlying SAP NetWeaver ABAP application server. Each job occupies 1 background work process in the SAP LT Replication Server system. For each configuration, the parameter Data Transfer Jobs restricts the maximum number of data load job for each mass transfer ID (MT_ID). In total, a mass transfer ID (MT_ID) requires at least 4 background jobs to be available:
 One monitoring job (master job)
 One master controller job
 At least one data load job
 One additional job either for the migration objects definition, access plan calculation or to change configuration settings in the Configuration & Monitoring Dashboard
Example
If you set the parameter Data Transfer Jobs to 04 in a configuration “SCHEMA1”, a mass transfer ID 001 is assigned. As a result, the following jobs should be in the system:
1 Master controller job: /1LT/IUC_REP_CNTR_001
 At most 4 parallel jobs for MT_ID 001: /1LT/IUC_LOAD_MT_001_001/~002/~003/~004
When configuring your data load or replication scenario, consider the following:
 Do not define more data transfer jobs than the number of available application server background work processes. If all available background work processes are already occupied by jobs, any other job will have to wait until a free work process becomes available. This can lead to long wait times until a new activity (for example creating triggers) can start, and can also result in significantly increased latency times for data replication.
 The number of dialog work processes in the source system corresponds 1:1 with the number of data transfer jobs in the SAP LT Replication Server system.
 Besides the work processes allocated by the data transfer jobs you need to provide additional available work processes for controller and monitoring jobs, the migration objects definition, access plan calculation or to perform configuration changes, and so on.
Sizing for SAP LT Replication Server involves determining how many work processes are required to perform the initial load of data into the target system within an acceptable timeframe, and accomplish the change capturing and the transfer of data changes to the target system within expected latency times.
Ensure that you add enough additional work processes to allow other required SAP LT Replication Server jobs to run.
Finally, you map the number of required application server work processes to their system resource consumption (CPU, memory, disc space) using the formulas provided by the SLT Sizing Guide.
With the simple formula below, you can calculate the number of required application server work processes (WPs) on the SLT Server for each active SLT configuration.
The number of required work processes can be determined by adding
 The Number of required data transfer jobs ,
 plus one background work process for Central Master (Monitoring) Job (only one per system!),
 plus one background work process for Master Controller Job,
 plus 3-5 additional empty background work processes (recommended per configuration),
 plus approx. 3 dialog work processes (recommended for each configuration).
Note: A lack of available free application server work processes can negatively affect the data load or data replication processes.
To summarize everything, the number of 'Data Transfer Jobs' must be set depending of the number of source tables, it is not the actual number of tables.
Assume that for my 100 tables I use 10 'Data Transfer Jobs' :
- The number of work processes on the SLT server would be 20. I took the simple formula of the documentation:
10 data transfer jobs ,
+ 1 background work process for Central Master (Monitoring) Job (only one per system!),
+ 1 background work process for Master Controller Job,
+ 5 additional empty background work processes (recommended per configuration),
+ 3 dialog work processes (recommended for each configuration).
- The number of dialog processes on the source server would be 10 ( equal to the number of 'Data Transfer Jobs')
Am I correct ?
Regards,
Christian

Job terminated in source system -- Request set to red,SAPSQL_SQLS_INVALID_

Hi All,
can any one help on this issue.
I run the BI statistics in production and found out the error while triggering the delta's
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Error msg : Job terminated in source system --> Request set to red
Message no. RSM078
Job started
Step 001 started (program SBIE0001, variant &0000000000756, user ID
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0TCT_DSA1
RLOGSYS = BCLNT300
REQUNR = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
UPDMODE = D
LANGUAGES = *
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 0 *
abap/heap_area_total.......... 2147483648 *
abap/heaplimit................ 40894464 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 3000320 *
ztta/roll_extension........... 2000683008 *
ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
Job cancelled
But delta laoding for same is working in DEV...but not in prod...
Please suggest
Regards
Shweta

Swetha
finally found out the notes.
Please look into them and ask you basis to implemnt,
1161940
1106569
1145041
1146851
Please have a look and ask for implemtation in your system which are suitable for you
We also faced the same issue job termination in source system for BI Statistics
Regards#
Srini

Procedure for deleting a role which is already in Production

Hi,
can any one explain me the procedure for deleting a role which is already in production
i want to know procedure for deletion of
1.single role
2.composite role
3.derived role
4.parent role
thanks,
SSSS

Hi,
Role deletion must be done in development box and the deletion must be transported to quality and productuion
For single and derrived roles create the transport request and delete the role and transport the deletion.
For Deletion of parent role: you cannot delete the parent role unless all the derrived roles within it are deleted.
To avoid the transport of user assignment make sure PRGN_CUST is set to 'NO' value for the parameter USER_REL_IMPORT.
Rakesh

Employee termination in HR system deletes BP role-BUP003 in CRM.

Similar Messages

Maybe you are looking for