HR Implementation in XI landscape

Hi Experts,
My client is looking to implement HR module.
What are the special scenarios when HR is being implemented and XI is the integration tool.
What will be the client looking at? Say in the interview point of view....
Are there any special IDocs, User Exits and things like that...with HR module.

Hi Naveen,
Please take a look at these...
http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d52a44575e11d189270000e8322f96/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/73/d3503885c3bd03e10000009b38f8cf/frameset.htm
HR - XI integration
cheers
Prashanth

Similar Messages

Rename 600+ users in CUA implemented 3 system landscape

Hello All,
Task ahead :
Rename around 600+ users in my Production system which is my CUA central system as well. I am having a simple 3 system landscape.
Advice on :
What can be the pitfalls for this activity ?
Since CUA is ON, there would not be a Rename Option available any more...so How to proceed with this activity ?
Is there any negative impact for such renaming actions in the system.
Any inputs would be rewarded handsomely...
Thanks for your time.
Br,
Sri

Hi Happyman,
How do i perfrom the Rename in my central system ? Its OK, i can delete child systems from the centrral CUA and perfrom a rename and then re add it back to CUA...bt my query is how to tackle this issue in central PRD system.
does that means i need to delete the existing CUA altogether and recreate it again after utilising the rename option ?>
Thx for the inputs...
Br,
Sri

Managing N+1 Landscape for Upgrade Project

Hello - I'm currently involved in a project that is rolling out a n+1 landscape. The landscape will look like this:
MNT (maintenance): DEV --> QAS --> PRD
PRJ (project): DEV --> QAS
The project landscape is going to be upgraded to newer enhancement packs and Netweaver versions. As an example, the maintenance landscape might be on Netweaver 7.30 and the project landscape on 7.40 (not real, just an example). In a situation like this, how are ABAP code and config changes managed or retrofitted across the two landscapes?
I've been investigating Solution Manager Retrofit as a possible tool to help, but I don't think it will work in this scenario. Can anyone help provide some high level guidance?

Hi Ethan,
I've been investigating Solution Manager Retrofit as a possible tool to help, but I don't think it will work in this scenario. Can anyone help provide some high level guidance?
You can manually track the changes which are being imported into Production system of Maintenance Landscape. Perform manual imports into Project landscape development system.
Perform upgrade impact analysis + unit testing on Development system of Project Landscape.
Perform SIT on QAS system of Project landscape
Alternate solution.
If you have CHARM implemented into your landscape , you can use critical object identification using solman. This will automatically highlight which objects needs attention.
Refer blogs http://scn.sap.com/people/dolores.correa/blog/2009/08/27/change-request-management-scenario-retrofit-functionality
Hope this helps.
Regards,
Deepak Kori

BW Implementation Approach

Hi Guys,
I am looking for the ASAP Paper on BW Implementation Approach. Which details at length how do we go about implementating it. With R/3 implementation together or after R/3. Cant find it on Sapnet though.
Can anyone help me with the link please ?
Cheers
Kirk

Hi Kirk,
As for the timing, BW in itself can function without a SAP environment all together as it could be implemented into any Landscape. With or After R3? Well with is always a better approach seeing that MasterData issues could be resolved at an early stage. Another reason is for modeling purposes. There are so many variables to consider that depending on the landscape and the future development and modules that you will be implementing it could go any route.
Personal suggestion based on experience is to do it with the R3 implementation, but in rythm with the implementation. Keep in mind that the whole architechture of BW Modelling needs to adapt to all the different source systems - you probably know this - and that this could really influence the decission on when what will be done.
If you do find that ASAP papare you are looking for, plz drop me a msg...
Regards,
Caz

BI dual landscape for upgrades

We recently built a dual / parallel landscape for our BI system to support a support stack upgrade.   I've used the dual landscape concept for many years when doing ERP upgrades, and it has worked very well.   We thought a dual landscape for BI would work also.   However, we did not consider the automatically generated objects in BI.
What we found is that with 2 development systems, even though BI objects are created with the same logical name, the technical (generated) name will be different between the 2 systems.
Has anyone successfully implemented a dual-landscape for BI?   If so, how did you syncronize the technical names of objects between development systems without transporting the objects from one development system to the other?   Note: I'm of the opinion that you need to be extremely careful transporting objects between systems with different release/support pack levels and therefore avoid it at all costs . . . Note 1090842 + several bad experiences.   Therefore, I am very unlikely to consider transporting the objects created in PSD to RLD as a valid solution.
The following is just an attempt to better describe the issue:
Production support landscape looks like this:
PSD -> BWP   (these systems have lower release/SP levels than the systems in the release landscape)
Release landscape looks like this:
RLD -> RLQ    -
> Changes will eventually go to BWP after release/SP upgrade in BWP
Lets say queryA must be developed and transported to BWP prior to the release/SP upgrade in BWP.
In PSD queryA is created and gets assigned technical name 123456 and is transported to BWP.
In RLD queryA also gets created, but gets assigned technical name ABCDEF.
Sometime after the release/SP upgrade, when you are back to a single landscape (RLD -> RLQ -> BWP), a change needs to be made to queryA.   When you transport queryA to BWP, you end up with 2 queryA's, one with technical name 123456 and one with technical name ABCDEF.

Hey. I worked for years in a dual landscape environment and at one point, some folks were actually looking at three paths all pointing to production. The three path idea got squashed fairly quickly, but we had two landscapes for as long as I can remember. So we essentially had:
PAD --> PAQ --> Prod
PBD --> PBQ --> Prod
This was very helpful to be able to work on major releases and upgrades while still allowing weekly maintenance releases. I never looked for a document that deeply discussed the concept and pitfalls to watch out for.
I will say the system synch-up could often become quite a pain. This may sound a little crazy but we would transport from landscape A to landscape B but dual code from B to A. This was because A was for the triannual major releases and upgrades and B was maintenance work. There were times when we would transport both ways, but we tried to stay away from that (except for queries).
The idea was that anything that went to prod as maintnenance, out of B, should be dual coded in parellel in A. Then once a tri-annual type release went from A, all those new transports and dual coding would be moved to B. This is how we kept everything in synhc and it worked rather well. You always had to be careful around the time of the tri-annual go live, but that's to be expected.
The only objects we had constant problems with werre queries. I don't know of anything you can do about that. We eventually decided to always transport queries between the two landscapes. We would never manually dual code a query. We would eventually get the duplicate query issue in production. The pitfall here is if the same query is getting touched for maintenance and a major release... that was just something we had to workaround. But we never had any major problems with transporting between the two landscapes. The times it became a huge headache is when people would forget to dual code, or just plain to a bunch of prototyping in one of these environments when they should have been using a sandbox.
Not sure if I have answered your question, but hope this helps in some way. At least you know plenty of us feel your pain!

Need help on implementing functionalities of solution manager

Hi solution manager gurus, i have to propose a method to implement SOLMAN functionality
Landscape consists of around 15 servers
SAP users 800
typical 3 system DEV-CONS-PRD landscape on all instances
Till now only Upgrade service functionality has been used in SOLMAN, they would like to implement the services below
   1. Engagement and Service Delivery u2013 service delivery and issue management
   2. System Administrations (Solution Monitoring, Root Cause Analysis, System Diagnostic, including non-SAP IT environments)
   3. Implementation/Upgrading SAP Solutions (Scenario Management)
   4. Business Process operations (Incident Management, System Landscape (cross IT landscape)
   5. Change management (for functional enhancements and updates)
   6. Test Management
Can anyone suggest the right approach in implementing those services
also can anyone suggest a rough possible time line in implementing this with rough FTE?

Hi,
my suggestion is to check the standard documentation of the interface IF_EX_ME_GUI_PO_CUST.
After that you can check the method IF_EX_ME_GUI_PO_CUST~TRANSPORT_TO_DYNP in the example implementation class CL_EXM_IM_ME_GUI_PO_CUST.
Usefull links:
[Re: Implementing badi ME_GUI_PO_CUST;
[Re: ME21N - PO Enhancement using BADI;
Kind Regards.
Andrea

SLD Landscape Question

Hi
We are about to implement the SLD landscape for our PI systems.
From the documentation (SDN and HELP.SAP.COM), it is recommended to have all SLD Data Suppliers send to the PI Production SLD Bridge. The SLD data is then automatically forwarded to the DEV/QA SLD Bridge (Design Time SLD).
This is straight forward and I can see how to get the ABAP stack to look at the correct SLD Server.
However, when it comes to the JAVA stack, I can't see how to configure the SLD CLIENT of an instance in the design-time landscape to use the design-time SLD Server.
Version of Netweaver in 7.0.
Thanks
Doug

SAP Web AS (Java) 6.30/6.40 Start-up: JProbe's Direct Support
This feature is available starting with JProbe 5.2.2. For details of application server integration, refer to the JProbe documentation. Here, the single steps for the SAP application server are briefly described.
Step 1: Create an Integration for the instance to be profiled.
 Click Tools -> Application Server Integration.
 Choose SAP Application Server 6.30.
 Click Create.
 To fill out the columns, follow the help you get via tooltip.
 Specify whether server or dispatcher should be profiled.
Step 2: Create a Configuration.
 Click Tools -> Manage J2EE Configurations.
 Click Add.
 Fill in Configuration Name and Integration.
 Optionally, you could specify an application to be profiled; this is just used to help to set the correct filters for profiling. If you know which packages or classes should be profiled, you can leave these fields empty; otherwise, specify the directory where the application is deployed and the .ear or .war file in this directory.
Step 3: Create the J2EE Settings.
 Click Session -> New J2EE Settings.
 Specify the configuration.
 Specify the other options, especially set filters (optionally, you could use the application specified in the configuration for filtering).
Step 4: Use the Connection Manager.
 Different to "startup via jlaunch" below the Connection Manager has to be used.
 Click Tools -> Options -> Advanced Session; mark "Use Connection Manager."
Step 5: Check the property 'IDxxxxxx.JavaPath' in instance.properties in the directory /usr/sap/<SID>/JCxx/j2ee/cluster
 JProbe relies on the property to find Java home, but there are Web AS 6.30/6.40 SPs that do not have this property.
 If it is not included, add it for dispatcher or server (dependent on which one should be profiled)
 For example, add "ID8156650.JavaPath=C:/java/jdk1.4.2_06."
 Be aware that using the standard startup procedure instance.properties is overwritten, so you might repeat this step.
Step 6: Start the J2EE Engine with JProbe
 Start the database and the central instance (enqueue and message server).
 In JProbe click "Run" for the J2EE settings defined before.
 Dispatcher and server of the J2EE Engine will be started; the one specified in the Integration will be profiled.
SAP Web AS (Java) 6.30/6.40 Start-up: Using JProbe 5.2.x via JLaunch
Starting the Server via JLaunch
Detailed instructions how to start JLaunch can be found in the documentation of SAP Web AS (Java). Here we give only the minimal list of steps:
 1.
 Include the location of JLaunch in the PATH
 2.
 Go to base directory of dispatcher or server (depending on which one you want to start).
 jlaunch pf=c:\usr\sap\<SID>\SYS\profile\<SID>_JCxx_<Host>
 -nodename=IDxxxxxxx
 where "IDxxxxxxx" can be figured out from the "instance.properties" in directory "cluster."
Creating a JProbe Startup File
In order to start up JProbe via JLaunch, you need to create a start-up file (.jpl) with the JProbe launchpad as follows:
 1.
 Click Session -> New J2SE Settings
 2.
 Enter filters, triggers, ...
 3.
 In the Configuration main class and the classpath fields are mandatory; a dummy entry for main class is sufficient, for classpath you could use %CLASSPATH%
 4.
 Save the .jpl file
 5.
 Switch off the Connection Manager; in JProbe 5.2.x a Connection Manager is introduced, which does not work if a Java application is started from a C-framework; therefore use Tools -> Options -> Session -> Advanced to switch off the Connection Manager
 6.
 Change the .jpl file with a text editor
 Comment out the line starting with -jp_java
 Add the connection information and the snapshot directory information; related to the introduction of the Connection Manager this is not written when the .jpl file is saved in the launchpad
 o
 -jp_socket=<host for analysis>:<port> (e.g. localhost:4444)
 o
 -jp_snapshot_dir=<snapshot directory> (e.g. c:
Jprobe
snapshots)
Starting JProbe with the Server
Start JLaunch as above, but attach the following parameters to the JLaunch command line:
jlaunch pf=... -nodename=... -Xbootclasspath/a:JProbe-Base-Dir\lib\jpagent.jar
 -Xrunjprobeagent:-jp_input=.jpl-file
For the .jpl-file please, specify the complete path. If there are blanks in the file or directory names, use double quotes or the DOS notation (e.g. PROGRA~1). After starting JLaunch you can now attach the viewer to it (JProbe -> Program -> Attach to Remote/Running Session).
regards
chandra

Role of a Security Consultant in an SAP implementation Project

Hi All,
What is the role of a Security Consultant in an SAP implementation Project and the stages in which he is involved?

Hello Mohammed,
The role of a Security consultant in any SAP product implementation (not just GRC) is wide enough and it's hard for anyone to sum up on a single forum post. Still I can give you some pointers.
Security consultants come from different backgrounds, some from networking, database administration, infrastructure and even development like me. They contribute enormously to any product implementation from scratch (landscape design) to go-live (and continuous maintenance) so they are active on every phase of the implementation.
Following are some of the activities they may perform (or participate)
-System Landscape Design (work closely with BASIS and DBAs)
-Check Infrastructure feasibility from security perspective (For Portals exposed to internet or extranet work closely with network providers for firewall security, VPS etc.)
-Propose security guidelines, access policies, disaster recovery plan, business continuity roadmap (work closely with information security consultants and internal auditors or risk management teams)
- Implement SAP solution specific Security measures (involves almost every SAP solution) for example: SAP R/3 security, GRC, BW/BI, HR, FI, Portal security etc.
- participate in application integration for example: LDAP, IDM, SAP UME, shared directories etc (User master records security is on high priority).
- Check for any possible backdoor access vulnerabilities (ex: open RFCs, function modules like ping_rfc), and it involves almost all SAP solutions and there are special procedures to analyze such vulnerabilities.
there are many such activities that a security consultant perform on day to day basis. Please do not interprete the above mentioned activities (entirely) as a criteria for any security consultant profile. There are many many possibilities for a security consultants to work from pen testing to SoD violation remediation. That's why I said it's not easy to sum up security.
Always remember, Security and GRC are two sides of a coin they work together. however GRC is more of a combination of policy, regulation, events and involves management participation whereas security is a purely technical practice.
You may also be interested to know what it takes to become a forensic security specialist. Take a quick look at [http://amudee.com/?p=378|http://amudee.com/?p=378]
Best Regards,
Amol Bharti

SLD Landscape Best Practice recomendation

I am seeking advise on setting up SLD in my ever growing landscape.
I currently have a Master SLD on the same system as my NWDI system and a local SLD on my Solution manager 7.0 system that is updated from the master.
The Master SLD is shared by our ECC6 Duel Stack landscape and my BI 70 Duel stack portal landscape.
I have upcoming projects of implementing a PI 7.1 landscape, implementing CTS+ and a Solution Manager Enterprise upgrade all of which will be heavily dependent on SLD.
I have seen documentation that PI would like it's own local SLD.
My question is what would be the prefered SLD landscape and how to I get there. Any recomendations or best practices would be most appreciated.
Bill Stouffer
Basis Administrator.

Hi,
SLD that we have implemented in our landscape is like bleow:
1) All PI and Portal system has local SLD.
2) For all non- production system, we have one SLD and production system we have seperate SLD.
3) It means we are following 3 tier SLD landscape as resommended by SAP.
4) Main SLd lies on solman, for production we have seperate and non-production we have seperate. non production and production sld sent data to main sld that is on solman.
4) All systems except PI and portal send data to production and non-production sld. PI and portal systems first send data to local which in turns send to production and non-production sld.
5) So by this way you whole environment is secure as production sld is different.
So, i will recommend to have 3 tier SLD approach. One of the important thing is don't use cenrtal user to send data across SLD as one user lock will in turns be the fallback of whole environment. So, always make each system specific user for data transfer so that user lock of one system will not impact other.
If you need any other information please let me know.
Thanks
Sunny

Transports on system landscape with no test environment

Hi,
Please share your experience about transporting from BWD to BWP. I have normally worked with BWD, BWQ, BWP, where we have the chance to test our transports on BWQ before moving the perfect changes to BWP. What precautions should I take when working and dealing with the landscape with no test instance?
Thanks
"Public opinion is a weak tyrant compared with our own private opinion. What a man thinks of himself, that is which determines, or rather indicates, his fate." ~ Henry David Thoreau, US Transcendentalist author (1817 - 1862)

Hi all,
Certainly I see and hear that smaller companies don't have enough funds to implement 3- system landscape, but I don't see why they would want to do that - better save money then and just do ABAP R3 reporting if all you will have is just implementing one module. Aren't you suppose to have sufficient funds in order to maintain and have SAP R3 and BW running? When they start wanting to implement more modules, then it will get clumsy and unstructured. They would have to spend more effort in doing the workaround and dealing with an unruly environment.
Thanks
"When the character of a man is not clear to you, look at his friends." ~ Japanese Proverb
"Nothing is easier than to denounce the evildoer; nothing is more difficult than to understand him." ~ Fyodor Dostoevsky, Russion Literaturer (1821 - 1881)
"Be smart and know who you're dealing with...But again who wants to" ~ Anonymous

More Easy Points...Portal Implementations

Hi all,
   I'm looking for information about portal implementations - project plans, staffing for the implementation, lessons learned, etc.
   I will happily award points for the right information.
   Thanks.
Dave

Hi,
You can deploy the portal in stages, for each of which you will need an implementation plan
that is distinct to the landscape.
The following are the key stages in which you plan and implement the portal landscape:
1. Development
The development stage consists of installation of the Portal Platform for content
development.
2. Integration and Testing
Integration and testing stage involves fine-tuning and troubleshooting issues, such as,
validating installations and testing the content developed during the development
stage.
3. Production
In the production phase, you scale the portal and implement high availability solutions.
Since you must deploy the portal in stages, any change implemented after completing the
production stage, such as, applying upgrades, support packages, patches, and other
applications changes the environment.
Regards,
Ameya

Unable to release the change request from se01

HI All,
Recently i had applied Rsecnotes as per sap recommendation in EWA Report and I implemented successfully in DEV System. But, When i try to release the change requests from SE01 in (DEV System)
it is giving the error message "Object Func<objectname> is inactive". I have unlocked all the request and checked but still problem exsist.
Please help me to release the request and implement in the landscape.
Thanks,
Rajesh N

Hi,
Activate the object using se03 and then relaese the request
thanks

Error while source system creation/Source system transport

Hi,
     In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
     Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
     I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
     Message no. RSAR502
Diagnosis
     With Remote Function Call to system GWPCLNT900 error connection closed
     (no data) ccurred.
Procedure
     Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
Krishna

Hi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier

Production Support for Multiple BI roll-outs

Hello BI Experts,
This might be more of an administrative question, but I will need inputs from Developer's perspective.
We are having 2 implemenation projects going on at the moment. They are sharing same ECC 6.0 & BI 7.0 landscape.
But as the 2 projects "Go-live" timings do not match, we will be having separate "Production Support" landscape for ECC containing separate DEV & QA system which will be used for Post Go-live production fixes.
So there will be 2 DEVs & 2 QAs for ECC & One Production system. At a time, only one QA will be connected to Prodution.
Do we need similar landscape for BI 7.0 or same DEV BI 7.0 can talk with 2 DEVs ECC 6.0 and same QA BI 7.0 can talk with 2 QA ECC 6.0 ?
What are the complexities of one QA BI talking with 2 QA R/3 source systems ??
Thanks,
Bhushan
P.S. We have SAP MDM 5.5 implemented in our landscape which manages master data.

Thanks Ramesh for the reply.
I agree with you it is not complicated from Basis perspective to create RFCs & source system connections.
I would like to know how complicated it would be for BI Developers to manage data coming from 2 very similar ECC6.0 systems and move it across to Production without trouble.
How will they distinguish which objects are of Production support & which objects belong to current development project ?
How we can guarantee that none of the "non-production object"(which is meant for development or prototype) moves to production via some "production-fix" transport ?
Thanks,
Bhushan

RFID DOC and Links.

Hi Everyone,
I wanna learn RFID, `m very new to this topic(technology) , can any one suggest me some links and doc related to RFID and how to implement in sap with examples?
Thanks & Regards,
Anil

Hello Anil,
Go through the following websites:
http://www.rfidjournal.com/
http://help.sap.com --> SAP Business Suite --> SAP Auto ID Infrastructure.
http://www.discoverrfid.org/
All the websites of the following groups will be very useful.
EPCGlobal
Auto ID Labs - http://www.autoidlabs.org/single-view/dir/article/1/296/page.html
GS1
Plus, very important: There is a project called BRIDGE undertaken by European Union. Here you will find a host of documents
http://www.bridge-project.eu/index.php/mainpage/en/
There is one free software download also which will help you understand implmentation of RFID in supply chain, thereby boasting your prepartion for understanding of SAP Auto ID Infrastructure.
In SAP, RFID is implemented with different landscapes. Most common landscape is:
SAP AII on Netweaver integrated with SAP EM. Please let me know if you require more info on this
Regards,
Yogesh Bhatia.

HR Implementation in XI landscape

Similar Messages

Maybe you are looking for