HR number ranges best practice

What would be the best practice for the global organization in terms of HR records number ranges?
1. Having country specific ranges and Central person functionality to group several records when people are moved between countries
2. Having one common number range and mix up all countries in there? There would be no need to leave and re-hire if moved between countries?
Thank you for sharing your experience!

Hi,
Our NUMKR Feature looks at country, but only splits out employees from Contractors/Consultants assigning one number range for all employees and one for all contractors.
Pros are you could identify the country of the employee by looking at the personnel number without having to know the Personnel Area or other information.
Con - You would have to look at other indicators such as Company Code or Personnel Area to determine the country of assignment. You would have to change the personnel number - terminate in old country and hire in new country each time there was a change of country.
Paul

Similar Messages

Number Ranges - Best Practise

Can anyone advise what's the best approach if a particular number range is being used up for a sales order type? Do we assign another number range? What if we really run of number ranges, is there anyway to reuse the number range by archiving documents out?
Thanks
Peter

There are many ways by which you can acheive your desired result.
You can have number range based on Fiscal year. eg. in 2008 for Sales doc you are using no range 10, 1000000000 - 199999999 and say you exhaust that. this u can treat in two ways:
either Reassign new number range to the sales doc say 49, 2000000000 - 2999999999.
or reset the counter for the number range 10 to 0 (Zero) and use it. There will be no conflict in numder series use in the same fiscal year. As doc number does not total depend on number range only, it also take date into consideration.
Hope it clears you query. If not kindly revert or esle reward.
Take care. JP

New whitepaper: Oracle9iAS Best Practices

Check out the newly published whitepaper on Oracle9iAS Release 2 best practices:
http://otn.oracle.com/products/ias/ohs/collateral/r2/bp-core-v2.PDF
Ashesh Parekh
Oracle9iAS Product Management

Carl,
There is really no set number or best practice for the number of segments. It is driven by the needs of your organization based upon reporting requirement, collective bargaining agreements, the degree of organizational change occurring within the enterprise, etc. I do believe that "less" segments usually makes more sense from a maintenance and ease of use perspective. Jobs are available across the Business Group, unlike positions, which are subordinate and specific to jobs and organizations...so you'll be maintaining less of them (hopefully).
Regards,
Greg

Number ranges - Import of Legacy Data - best practice

Hi,
we are planning to move legacy data objects to our SAP CRM.
These Objects have an external key (Numeric, 6 digit) in a number range that is relatively full and highly fragmented.
Is there a best practice how to implement internal number assignment for this kind of pre filled number range?
The internal key in SAP would be different and under our control, the external key is the interesting one.
Cheers,
Andreas

Hi Luís,
The scenario is in the context of insurance business.
The setup: SAP CRM as central Business Partner system. And in the CRM we keep the policy numbers of the surrounding (non SAP) policy systems as references (I'm talking about insurance policies...).
For each policy we create a one order object, containing, among others, LOB, policy type and the policy number.
These policy number ranges are to be maintained in the central CRM system in the future.
And in one of these Systems they have the situation described above:
6 digit key in a number range that is relatively full and highly fragmented. They are managing their numbers in an xls right now, but we would also have them migrated into our system.
And after the migration we would be responisble to find a unused number, whenever a new policy is to be created.
Cheers,
Andreas

Best Practice for Change Maintenance Order Number Range

Hello
We have decided that our Maintenance Orders will always start with the year of the open date. Example 201112345155
Every year we will need to change the number ranges
What is the best practice to change the order number range? What is the best approach here?
I have also another question. Why the "Current Number" is not incremental?
Thanks for the help

Hi,
The current number can be explained by use of buffering of the numbers. Buffering is defined via transaction SNRO, the AUFTRAG object is relevant for orders. When buffering is active, a set of unused numbers are assigned to each application server.
In your example - The fiirst 20 numbers were taken from the available number range and assigned to the buffer (possible 10 numbers to each of two servers). As orders are created a number is assigned from the buffer. Once the buffer values are used a further set of numbers are taken from the number range and the current number is increased (by buffer value).
-Paul

Best practice for Number range buffering in SAP BI for FI Cubes

Hello Experts,
I have a question regarding Number range buffering. What i have observed is if we use more number of background processes while loading data, it for sure creaets locks with NRIV table bcoz of more calls for bufffered numbers with multiple processes.
But there is a clause in SNRO while we buffer 'Main Memory' that it should not be used for Financial documents. I understand that this is for serial assignment of numbers for Documents and acoounts on the backend ECC, but does this even stand true for DIM ID's which we are buffering while loading data into a FI Cube?
I have looked up a SAP note 1398444, which talks about NRIVSHADOW and parallel buffering and different use case scenarios.
Which one of those should be used if I need to buffer my Dimension while loading a FI Cube in BI with maximun background processes?
Please help me understand the difference?

hi,
well the message is just like a warning to signify that incase you load more number of new records then your existing limit of buffer then you will have to increase accordingly if no then you can ignore
if you want to understand the reason it like this....
if there is not sufficent buffers space available and then process would be rollback and the existing numbers will get lost resulting gaps between the document numbers and for applications like finance this is not desirable .
see doc more details
http://help.sap.com/saphelp_nw04/helpdata/en/95/3d5540b8cdcd01e10000000a155106/frameset.htm
Also if you are not sure you ask your basis team for Early watch alert report in their you can easily see whether number range buffering is really required or not, if yes then for which object/dimensions
Also check below SAP Note:449030 and 62077
hope it helps
regards
laksh

Best practices on number of pipelines in a single project/app to do forging

Hi experts,
I need couple of clarification from you regarding endeca guided search for enterprise application.
1)Say for example,I have a web application iEndecaApp which is created by imitating the jsp reference application. All the necessary presentation api's are present in WEB-INF/lib folder.
1.a) Do I need to configure anything else to run the application?
1.b) I have created the web-app in eclipse . Will I be able to run it from the any thirdparty tomcat server ? If not then where I have to put the war file to successfully run the application?
2)For the above web-app "iEndecaApp" I have created an application named as "MyEndecaApp" using deploymenttemplate. So one generic pipeline is created. I need to integrate 5 different source of data . To be precise
i)CAS data
ii)Database table data
iii)Txt file data
iv)Excel file data
v)XML data.
2.a)So what is the best practice to integrate all the data. Do I need to create 5 different pipeline (each for each data) or I have to integrate all the 5 data's in a single pipeline ?
2.b)If I create 5 different pipeline then all should reside in a single application "MyEndecaApp" or I need to create 5 difference application using deployment template ?
Hope you guys will reply it back soon..... Waiting for your valuable response ..
Regards,
Hoque

Point number 1 is very much possible ie running the jsp ref application from a server of your choice.I havent tried that ever but will draw some light on it once I try.
Point number 2 - You must create 5 record adapters in the same pipeline diagram and then join them with the help of joiner components. The resultant must be fed to the property mapper.
So 1 application, 1 pipeline and all 5 data sources within one application is what should be the ideal case.
And logically also since they all are related data, so must be having some joining conditions and you cant ask 5 different mdex engines to serve you a combined result.
Hope this helps you.
<PS: This is to the best of my knowledge>
Thanks,
Mohit Makhija

Best practice for phone number column data type

Hi,
I hope I have posted this in the right forum, if not just notify me and i will remove it to the correct area.
What would be considered best practice for storing a phone number.
Number of Varchar2.
Ben

Well I was thinking that Number would have the following disadvantages,
1. Users entering phone numbers into a form may be tempted to pre format with spaces, thereby throwing up an error.
2. Mobile phone numbers may have leading zeros
3. Calculations are not carried out on phone numbers.
I was leaning towards a varchar2 type.
Ben

Best practice for number of result objects in webi

Hello all,
I am just wondering if SAP has any recommendation or best practice document regarding number of fields in Result Objects area for webi. We are currently running on XI 3.1 SP3...one of the end user is running a webi with close to 20 objects/dimensions and 2 measure in result objects. The report is running for 45-60 mins and sometimes timing out. The cube which stores data has around 250K records and the report would return pretty much all the records from the cube.
Any recommendations/ best practices?
On similar issue - our production system is around 250GB what would be the memory on your server typically...currently we have 8GB memory on the sap instance server.
Thanks in advance.

Hi,
You mention Cubes so i suspect BW or MS AS . Yes, OLAP data access (ODA) to OLAP DataSets is a struggle for WebIntelligence which is best at consuming Relational RowSets.
Inefficient MDX queries can easily be generated by the webi tool, primeraly due to substandard (or excessive) query and document design. Mandatory filters and focused navigation (i.e. targetted BI questions) are the best for success.
Here's an intersting article about "when is a webi doc too big" https://weblogs.sdn.sap.com/pub/wlg/18706
Here's a best practice doc about webi report design and tuning ontop of BW MDX : https://service.sap.com/~sapidb/011000358700000750762010E
Optimization of the cube itself, including aggregates and cache warming is important. But especially use of Suppress Unassigned nodes in the BW hierarchy, and "query stripping" in the webi document.
finally, patch level of the BW (BW-BEX-OT-MDX) component is critical. i.e. anything lower than 7.01 SP09 is trouble. (memory management, mdx optimization, functional correctness)
Regards,
H

What is the best practice with Keychain re: number of keychains?

I'm not clear on what is the best way for using keychains. I have two that appear to overlap with similar entries (e.g., passwords for various websites and applications). One of the keychains is named login and other is named with my full name (first name and surname). There are two keychains that have blank boxes in front of them as opposed to the lock icon. One of those has the same name as my account name and the other is named X509Certificates.
Is there a best practice that recommends either consolidating keychains or, if multiple keychains are better, than what type of information should be kept in what keychain? I find that I have to enter passwords for a number of apps when I boot up instead of the passwords being automatically retrieved. I would hope that setting up the keychains correctly will address this problem.

You don't need to worry about setting it up properly, OSX will do this for you. The only reason I ever use Keychain Access is if I forget a password or want to delete one. Moving files around in keychain access could lead you to some serious problems. If I was you I would just leave the files be and OSX take care of the rest.

Best practice when upstream does not provide version number

I'm currently preparing a package for the game Dreamfall Chapters, unfortunately the Developer does not (yet) provide a Version number.
What is the best practice for this? Just count the releases and set epoch when they finally provide one themselves?
thanks in advance!

If you are missing a version number, you could use the date. Prefix it with "r" in case you want to avoid epoch when upstream decides to start versioning.
pkgver=r20140122
If you have another release on the same day, increment another subversion
pkgver=r20140122.1
Counting the releases by hand is poor practice (you could miss one). Do it only if upstream provides the count.
Edit: To tie the version stronger to the release, you can also add a part of the archive hash, e.g. +m###### with the first 6 characters of the md5sum.
pkgver=r20140122+m23df1e
Edit: r as prefix is better, thanks rumpelsepp.
Last edited by progandy (2014-10-22 09:32:56)

What's the 'best practice' way to get email and fax number from vendor?

Hello *,
could anybody let me know what the 'best-practice' is to get the fax number and smtp address from the vendor master? Is there a preferred function module I should use?
Thanks a lot,
Torsten

Hi ,
try that:
TYPE-POOLS: szadr.
DATA adr_kompl TYPE szadr_addr1_complete.
DATA adr1 TYPE szadr_addr1_line.
DATA adtel TYPE szadr_adtel_line.
DATA admail TYPE szadr_adsmtp_line.
DATA adfax TYPE szadr_adfax_line.
CALL FUNCTION 'ADDR_GET_COMPLETE'
       EXPORTING
            addrnumber              = lfa1-adrnr
       IMPORTING
            addr1_complete          = adr_kompl
       EXCEPTIONS
            parameter_error         = 1
            address_not_exist       = 2
            internal_error          = 3
            wrong_access_to_archive = 4
            OTHERS                  = 5.
* Mail
LOOP AT adr_kompl-adsmtp_tab INTO admail.
    MOVE admail-adsmtp-smtp_addr TO atab-mail.
ENDLOOP.
* fax
LOOP AT adr_kompl-adfax_tab INTO adfax.
    MOVE adfax-adfax-fax_number TO atab-fax_number.
ENDLOOP.
regards Andreas

Best Practices- Number of users in Contract Manager

What is the best practices for the number of users operating in Primavera Contract Manager? We currently have v13.0.3.0

There are no real limits to the number of users working in PCM, but your server(s) must be sized correctly to work effectively. I've seen PCM instances with hundreds of users. Sizing requirements is typically included with your installation materials; otherwise you may want to look at the knowledgebase for this document.

Range Extender best practices

Does anyone have any advice or resources on best practices when using a range extender?
I have a **bleep** client who has a large house. their e4200 router is one side of the house while their updstairs bedrooms are on the other side and they complain about horrible coverage.
We've tried the PLW400 and they didn't like having 2 SSIDs. So now we're trying the RE2000 and they are not thrilled about that either. I have yet to get specifics. Maybe it's too far away from the router, I dunno...
I should probably move the e4200 to a more central location in the house but there is no ethernet jacks their to connect to the modem.
So does any one else have any thoughts?

Did you check the thread on your last post (RE: e4200 and PLEK400...how to use the same SSID???)? I had made my insights on your previous post regarding the PLW400 SSID concern/problem.
Please try to check this link on how to maximizing the use of Linksys Wireless-N Range Extenders.
I would also suggest that you try to get the EA6500 or other EA series of routers. to have a more wireless range and speed, it might be an E4200 issue as well.

Database best practice: max number of columns

I have two questions that I would appreciate comments on...
We have a table titled TRANSACTION with 160 columns and a view titled TRANSACTIONS_VIEW with 233 columns in it. This was designed by someone a while ago. I am wondering if it is against best practice to have this many columns in a table? I have never before seen a table with this many columns in it and feel that there must be a way to split the data into multiple tables to make it more manageable.
My second question is on partitions, the above table TRANSACTION is partitioned by manually specifying partitions with max values on the transaction date starting august 2008 through january 2010 at 1 month increments. Isn't it much better to specify automatic partitioning using the interval clause?

kev374 wrote:
thanks for the response, yes there are many columns that violate 3NF and that is why the column count is so high.
Regarding the partition question, by better I meant by using "interval" the partitions could be created automatically at the specified interval instead of having to create them manually.The key is to understand the logic behind these tables and columns. Why it was designed like this, if it's business requirement then 200 some columns are not bad, if it's design flaw 20 columns could be too much. It's not necessarily always good to have strict 3NF design, sometime for various reason you can denormalize the tables to get better performance.
As to partitioning Q, you have to do the rolling window (drop/add partition as time goes by) type of partitioning scheme manually so far.

HR number ranges best practice

Similar Messages

Maybe you are looking for