Best practice Qualifications in infotype 0024

Hi
Im looking for a smarter way for the enduser to copy or delimit qualifications in infotype 24.
Copy:
If a qualification gets a new proficiency from a certain date, you have to create and search for the relevant qualification.
Why not a Copy button?
Dellimit:
If a qualification needs to have an enddate, you have to create a new qualification with the same startdate, set the enddate, save it and then delete the old record.
Why not a Delimit button?
Hopefully it just me being blind .... or what?
Regards Claus

Hi,
Please check the following discussion:
Delimit qualification
Credits: Wilfred Krens and other SDN members
Hope this helps.
Donnie

Similar Messages

Qualifications and Infotype 0024

I would like to understand the relationship between Qualifications Profiles and Infotype 0024
When we create Qualifications Profiles on the PD side, on the Person Object, for example, does it automatically get transferred to IT0024 or do we have to run a Program or a Report to populate IT0024.
Similarly, if we create IT0024 with Qualification data, do we have to also maintain Profile on the PD side with similar data or does it trnasfer data automatically or do we have to run a Report or a Program.
Pl note that PA/PD/OM integration is all ACTIVE

Hi My Friend
Please refer to the SAP note 384001 - FAQ: Qualifications and Requirements
1. How do you activate integration between Personnel Administration and
 Personnel Planning for qualifications?
Customizing: table T77S0, parameter PLOGI QUALI
 Page 2
2. How does active integration affect infotype 0024 in a personnel
 action?
When integration is active, infotypes 0024 or 0025 must always come at
the end of a personnel action.
3. What impact does active integration have for the Ad Hoc Query?
When integration is active, the data is no longer physically stored in
infotype 0024 (table PA0024), but in infotype 1001 (table HRP1001
subtype A032).This explains too, why you can no longer directly access
the infotype fields of IT0024 in the query. Any attempt to access these
always fails.
4. Why is the qualifications catalog not alphabetically sorted in F4
 possible entries help?
Generally speaking, sorting in the qualifications catalog (transaction
OOQA or PPQD) is not the same as sorting in the possible entries feature
(F4 help). The reason for this is the different method used for the
sorting. While sorting in transactions OOQA and PPQD is done
alphabetically, the possible entries feature only sorts the first level
(qualification groups) alphabetically. All other levels are sorted by
object ID.
From release 4.6C you can sort qualifications manually in the
qualifications catalog (transaction OOQA).From a technical point of
view, this information is stored in the database field P1001-PRIOX.This
sorting also applies to the possible entries help.Thus, the
qualifications catalog has the same sorting throughout.
If you have a pre-4.6C release, you can only achieve the same sorting if
you adjust the field P1001-PRIOX accordingly using transaction PP01 or
PP02. Before you use transactions PP01 or PP02, you should check whether
maintenance is allowed in table T777I.
5. How are notes for qualifications stored in the qualifications
 profile?
The notes are stored period-independent with the key 'person has
qualification' (for example, P 0003212 A032 Q 50001231).The advantage of
this is that you only have one note attached to a qualification, whose
history you can monitor.
Example (Qualifications profile):
Qualification Proficiency Period Note
 English 1 01.01.1980 - 30.06.1998 X
 English 2 01.07.1998 - 31.12.9999 X
The same note is displayed regardless of whether you look at the note
for the first or second entry.
6. Can you create customer-specific Infosets (Ad Hoc Query) for the
 unrestricted search for persons and applicants?
Yes, you can create customer-specific InfoSets. These customer-specific
InfoSets must be defined in the 'global work area' in transaction SQ02.
Customer-specific InfoSets for Personnel Development must not be
defined in the standard work area, they must always be in the global
area.
7. How does the inheritance logic work for the specification
 descriptions for qualifications?
If you want to store standard values for the specification descriptions,
you can do this in the IMG (Personnel Development) under 'Edit scales'.
So that these standard values are inherited to the qualifications, in
the qualification catalog, the 'Default' flag must be set both in the
qualification group and in the qualification in the tab.
If the flag in the qualification group is not set, the stardard values
are not inherited t othe qualification below.
If the flag is not set in the individual qualification, the standard
values are only not inherited to this qualification. Then you can enter
a specification description for this qualification.
Hope it can give you answer
Regards,
Jun

Best Practice for Updating Infotype HRP1001 via Class / Methods

I want to update an existing (custom) relationship between two positions.
For example I want
Position 1 S = '50007200'
Position 2 S = '50007202'
Relationship = 'AZCR'
effective today through 99991231
Is there a best practice or generally accepted way for doing this using classes/methods rather than RH_INSERT_INFTY ?
If so, please supply an example.
Thanks...
....Mike

Hi Scott
You can use a BAPI to do that.
Check the following thread:
BAPI to update characteristics in Material master?
BR
Caetano

SAP Best Practice HR: DX Toolbox

Hi Suresh,Saquib
This post is in continuity to my previous post, can u provide some advantages/disadv's of using ZBPHR_ZDTT - SAP Best Practice HR: DX Toolbox tool to upload PA infotypes

Vijay,
I havent used it , but I just Heard that SAP give best practices of common infotype. Most of the time you wouldnt find the country specific infotype . I also came to knew in discussion that you can not upload the data from application server.
Hope thisll give you some clue.
Thanks
Saquib
Message was edited by: Saquib Khan

Copy Qualifications of HR personel (Infotype 0024)

Hi all,
How can i copy qualifications of HR personel(Infotype 0024) from one to another?
Best regards,
Munur

Hello,
Are you planning to do this as a batch (a lot of copies) or do you want a single one of them?
With Pa30 I am afraid it's not possible, only for the same pernr.
Regards,
Bentow.

[Qualif.] Difference between object type 'Q' and infotype 0024

Hi,
For the xRPM 4.0 solution, we need to maintain skills for resources. There is a HCM integration functionality to import skills from a HR system to Business Partners (which - basically - represent users that can be staffed on a project in the xRPM solution).
Today, there is no skill management in our HR system.
There are 2 notions that look very similar to me :
- Infotype 0024 [Transaction PA20/PA30] : contains Qualifications of a user in PA (Personal Adminsitration) with the standard table T574A holding the possible values
- Organizational Structure (HRP1000/HRP1001) [transaction BP / PP* ?]: with the objects Qualifications 'Q' and Qualifications Group 'QK'
It seems taht the integration operates on the Organizational Structure. But we would like to assess both solutions.
What is the difference (pros&cons) between the 2 of them ?
Thanks in advance.
Best regards,
Guillaume
Message was edited by:
Guillaume GARCIA

To be precise, the way Infotype 24 behaves depends on whether integration between PA and PD is active. This is controlled by setting PLOGI QUALI in table T77S0. There are also other settings in this table that affect how quals work in an integrated scenario, you will find these in the QUALI XXXX section.
If integration is active, the qualifications are maintained in a catalogue via transaction OOQA. What you see in IT0024 are the object Q <--> P relationships as mentioned above once a qualification object has been assigned to the employee. This option has the advantages of being able to use the integrated objects in othe modules e.g. as prerequisites or imparted quals in the training module, skills/requirements matchup etc. The down side is that being PD objects, these are more difficult to report with SAP Query or Adhoc Query tools, but there are ways of doing it.
If integration is not active, the data is simple stored in PA table PA0024 and the quals themselves are set up via the IMG. The data really can't be used in any other module, but the reporting aspects are much easier with the standard query tools.
Regards,
John

Data retrieval from infotype 0024(Qualification)

hi abapers,
could someone suggest me how to retrieve data from infotype 0024(Qualification)
I tried from pa0024,but no data is stored there.
yogesh

Hi Yogesh,
Make use of below FMs to fetch the data from IT0024 -
* Fill t_pernr_tmp with employees (PERNRs) as follows -
      t_pernr_tmp-plvar = '01'.
      t_pernr_tmp-otype = 'P'.
      t_pernr_tmp-sobid = '00000001'. "give employee number here
      append t_pernr_tmp.
*     READ QUALIFICATION
      CALL FUNCTION 'RHPP_Q_PROFILE_READ'
        EXPORTING
          begda            = w_low "provide date in sy-datum format
          endda            = w_high "provide date in sy-datum format
          with_stext       = c_x
          with_qk_info     = c_x
        TABLES
          OBJECTS    = t_pernr_tmp
          profile          = t_qual_data
        EXCEPTIONS
          no_authority     = 1
          wrong_otype      = 2
          object_not_found = 3
          undefined        = 4
          OTHERS           = 5.
* here t_qual_data will have qualification data.
*after that make use of FM 'RHPE_QCAT_BRANCH_READ_UP' and the *t_qual_data table to read the branches of qualification data.

Infotype header - best practice

Hi group
Today our ifnotype headers are created in a way that makes us have to break a lot of infotypes just to refresh the header.
There are 2 reasons in my opinion:
- We have chosen to read header on infotype begda
- We have eg. position information in the header
We want to change this so we don't have to break eg. address just to read correct data.
I don't feel reading header at sy-datum is a right choice. This can give an incorrect picture if you read an infotype and the header is inconsistent with the actual situation in the date-range for the infotype.
So I am leaning towards letting the header contain much less information.
Does anyone have some "best practice" thoughts?
Any documentation I can read up on regarding best practice on this matter?
Thanks in advance
Kirsten

Hi,
Headers, in general, are part of the whole philosophical debate. Iu2019ve seen both ways: current dated and infotype date driven. Iu2019m an advocate of them being infotype date driven for the very same reason that you mentioned: display what is on the record.
The other school of thought is to always display current information. It also gets some leverage depending on what is being displayed. If you have OM related data like position, job, org units etc, and clients may want to always display the current information. Maybe they are trained that way to only pay attention to headers to give them ad-hoc type information. They can get historical data through other reports.
I donu2019t think there is any u201Cbest practiceu201D with headers; itu2019s a purely philosophical choice.
Hope this helps.
Donnie

Best practice in HCM

Hi,
1) Can you please advise,what all processes comes under SAP Best Practices for HCM?
2) What all infotypes comes under Payroll implementations?
Thanks!
Manish

Hi,
You can read every thread in this forum.
1.Personnel Administration - it deals with the HR Master Data
2.Organization Management - It deals with the personnel planning all about Business Units,Cost centers etc this will give the picture how your organization look virtually.
Keep these modules as base must know modules
3 Time Management - This manages employee times ,leaves,quotas,shifts,working schedules etc working patterns etc
CATS ,Cross Application Time sheets
Shift Planning etc are part of Time Management but these are individually separate knowledge of these is not necessary when you start your career going forward it would be helpful to grow.
4.Payroll- This manages employee payment part and payment including the off cycle payments
These 4 can be considered to be the basic modules of HCM
5 Recruitment -Deals with process of recruitment from manpower planning to on-boarding
Apart from these we have
6.Benefits -which deals with the fringe benefits (applicable to USA ) and some other countries-I t deals with the insurance ,medical etc
7,ESS/MSS This is self service module employee self service and manager self service these are Portal based modules
We have new generation modules
Such(8) E- Recruitment this deals with the E Recruitment this is portal based modules
Learning Solution
Succession Planning
Personnel Development
Talent Visualization by Nakisa
Enterprise compensation Management (this is again a separate module)
These all part of Talent Management Suite and portal based modules knowing these would give you an edge.
This module is very upcoming and hot
To become an effective HCM consultant you need have good business process knowledge combined with the any of 4 to modules (indepth)
Outside HCM if you knowledge of HR ABAP and MS Excel and MS Word of great advantage.
To start your choose Personnel Management,Org Management combined with Time Management and Payroll
Or ESS/MSS with Talent Management
Search in transaction PA30- Hr Master data and press F4 , you will find entire details 0000 Actions 0001 Organizational Assignment 0002 Personal Data 0003 Payroll Status 0004 Challenge 0005 Leave Entitlement 0006 Addresses 0007 Planned Working Time 0008 Basic Pay 0009 Bank Details 0011 External Transfers 0014 Recurring Payments/Deductions 0015 Additional Payments 0016 Contract Elements 0017 Travel Privileges 0019 Monitoring of Tasks 0021 Family Member/Dependents 0022 Education 0023 Other/Previous Employers 0024 Qualifications 0025 Appraisals 0027 Cost Distribution 0028 Internal Medical Service 0030 Powers of Attorney 0031 Reference Personnel Numbers 0032 Internal Data 0033 Statistics 0034 Corporate Function 0035 Company Instructions 0037 Insurance 0040 Objects on Loan 0041 Date Specifications 0045 Loans 0048 Residence Status 0050 Time Recording Info 0054 Works Councils 0057 Membership Fees 0077 Additional Personal Data 0078 Loan Payments 0080 Maternity Protection/Parental Leave 0081 Military Service 0083 Leave Entitlement Compensation 0105 Communication 0121 RefPerNo Priority 0123 Germany only 0124 Disruptive Factor D 0128 Notifications 0130 Test Procedures 0139 EE's Applicant No. 0165 Deduction Limits 0167 Health Plans 0168 Insurance Plans 0169 Savings Plans 0171 General Benefits Information 0185 Personal IDs 0219 External Organizations 0236 Credit Plans 0262 Retroactive accounting 0267 Add. Off-Cycle Payments w/Acc.***. 0267 Additional Off-Cycle Payments 0283 Archived Objects 0290 Documents and Certificates (RU) 0292 Add. Social Insurance Data (RU) 0293 Other and Previous Employers (RU) 0294 Employment Book (RU) 0295 Garnishment Orders (RU) 0296 Garnishment Documents (RU) 0297 Working Conditions (RU) 0298 Personnel Orders (RU) 0299 Tax Privileges (RU) 0302 Additional Actions 0315 Time Sheet Defaults 0330 Non-Monetary Remuneration 0334 Suppl. it0016 (PT) 0376 Benefits Medical Information 0377 Miscellaneous Plans 0378 Adjustment Reasons 0379 Stock Purchase Plans 0380 Compensation Adjustment 0381 Compensation Eligibility 0382 Award 0383 Compensation Component 0384 Compensation Package 0395 External Organizational Assignment 0396 Expatriation 0402 Payroll Results 0403 Payroll Results 2 0415 Export Status 0416 Time Quota Compensation 0429 Position in PS 0439 Data Transfer Information 0458 Monthly Cumulations 0459 Quarterly Cumulations 0460 Annual Cumulations 0468 Travel Profile (not specified) 0469 Travel Profile (not specified) 0470 Travel Profile 0471 Flight Preference 0472 Hotel Preference 0473 Rental Car Preference 0474 Train Preference 0475 Customer Program 0476 Garnishments: Order 0477 Garnishments: Debt 0478 Garnishments: Adjustment 0483 CAAF data clearing (IT) 0484 Taxation (Enhancement) 0485 Stage 0491 Payroll Outsourcing 0503 Pensioner Definition 0504 Pension Advantage 0529 Additional Personal Data for (CN) 0552 Time Specification/Employ. Period 0553 Calculation of Service 0559 Commuting allowance Info JP 0560 Overseas pay JP 0565 Retirement Plan Valuation Results 0567 Data Container 0569 Additional Pension Payments 0573 Absence for Australia PS 0576 Seniority for Promotion 0579 External Wage Components 0580 Previous Employment Tax Details 0581 Housing(HRA / CLA / COA) 0582 Exemptions 0583 Car & Conveyance 0584 Income From Other Sources 0585 Section 80 Deductions 0586 Section 80 C Deductions 0587 Provident Fund Contribution 0588 Other Statutory Deductions 0589 Individual Reimbursements 0590 Long term reimbursements 0591 Nominations 0592 Public Sector - Foreign Service 0593 Rehabilitants 0597 Part Time Work During ParentalLeave 0601 Absence History 0602 Retirement Plan Cumulations 0611 Garnishments: Management Data 0612 Garnishments: Interest 0614 HESA Master Data 0615 HE Contract Data 0616 HESA Submitted Data 0617 Clinical Details 0618 Academic Qualification 0624 HE Professional Qualifications 0648 Bar Point Information 0650 BA Statements 0651 SI Carrier Certificates 0652 Certificates of Training 0653 Certificates to Local Authorities 0655 ESS Settings Remuneration Statement 0659 INAIL Management 0666 Planning of Pers. Costs 0671 COBRA Flexible Spending Accounts 0672 FMLA Event 0696 Absence Pools 0702 Documents 0703 Documents on Dependants 0704 Information on Dependants 0705 Information on Checklists 0706 Compensation Package Offer 0707 Activation Information 0708 Details on Global Commuting 0709 Person ID 0710 Details on Global Assignment 0712 Main Personnel Assignment 0713 Termination 0715 Status of Global Assignment 0722 Payroll for Global Employees 0723 Payroll for GE: Retro. Accounting 0724 Financing Status 0725 Taxes SA 0742 HDB Concession 0745 HDB Messages in Public Sector 0746 De Only 0747 DE Only 0748 Command and Delegation 0758 Compensation Program 0759 Compensation Process 0760 Compensation Eligibility Override 0761 LTI Granting 0762 LTI Exercising 0763 LTI Participant Data 0783 Job Index 0784 Inquiry Family Court 0785 Pension Equalization Payment 0787 Germany Only 0788 Germany Only 0789 Germany Only 0790 Germany Only 0792 Organizational Additional Data 0794 Pensioner Message A 0795 Certification and Licensing 0796 Duty Assignments 0800 Material Assignment 0802 Sanctions / Offense 0803 Seniority Ranked List 0804 Personal Features 0805 Honors 0806 Course Data 0813 Historical Additional Fees A 0815 Multiple Checks in One Cycle 0845 Work Relationships 0846 Reimbursements 0851 Shukko Cost Charging 0852 Shukko Cost Charging Adjustment 0853 Shukko External Org. Assignment 0860 Sanctions / Offense 0861 Award/Decorations 0863 Verdict 0865 Mobility 0873 Additional Amount - Garnishment FR 0875 Events - My Simplification 0881 Expense Information 0882 Insurability Basic Data 0883 Entitlement Periods 0884 Insurability Calculation 0887 Garnishments (ES) 0900 Sales Data 0901 Purchasing Data 0904 Override Garnishable Amount D 0908 Info. about Annual Income Check 0942 Capital Payment 0976 Municipal Tax per Person 0978 Pension Contribution A 0979 Pension A 2001 Absences 2002 Activity Allocation (Attendances) 2002 Attendances 2002 Cost Assignment (Attendances) 2002 External Services (Attendances) 2002 Order Confs.(Att) 2003 Substitutions 2003 Substitutions: Indiv. Working Times 2004 Availability 2005 Overtime 2006 Absence Quotas 2007 Attendance Quotas 2010 Cost Allocation (EE Rem. Info) 2010 Cost Assignment (EE Rem. Info) 2010 Employee Remuneration Info 2011 Completed Time Events 2011 Time Events 2011 Time Events (CO) 2011 Time Events (PM) 2011 Time Events (PP) 2012 Time Transfer Specifications 2013 Quota Corrections 2050 Annual Calendar 2051 Monthly Calendar 2052 Absence Recording 2052 List Entry for Attendances/Absences 2052 Weekly Calendar w/Cost Assignment 2052 Weekly Entry w/Activity Allocation 3003 Materials Management 3202 Addresses 3215 SWF Staff Details 3216 SWF Contract Details 3217 SWF Qualifications 3893 Time Account Status 3894 Factoring Information BPO
Thanks and Regards,
Revathi.

Infotype 0024 enhancement

u201CNew joiner u201Cis an action in our client system in which 8 infotypes are configured. When I execute this action in PA40 transaction, the 8th infotype that appears will be 0024.When this infotype screen appears as a part of u201DNew joiner u201Caction, the user should be presented with the defaulted qualification and proficiency based on nationality of the individual.
I decided to look for a user exit. The user exit PBAS0001 gets triggered for the PBO and PAI of every infotype in PA .But infotype 0024 u2013 (Qualifications) belongs to Personal Development (It belongs to package PPPE).There is no exit associated with this package. Also I searched for the string u201Ccustomer u201Cin the function group RHP6 (0024 infotype screen belongs to this function group) but couldnu2019t get any solution.
Also I did not get any result for searching u201CBADIu201D in the above function group. I am using ECC 5.0 system.
The user needs the values to be defaulted in the 0024 infotype screen .
Can you please suggest any other approach to achieve the above objective?

Hi Kiran,
First, you need to check whether you're using qualifications with PD integration or not.
Goto SM31 -> PLOGI ORGA value.
If it is 1 A032 Q, then there is the PD integration.
So you need to attach a qualification to an employee through PP01.
Thus, in order for automatic creation, you may write a user exit in PBAS0001 and try to create A032 relationship between P object (employee) and Q object (qualification).
Best Regards,
Dilek

SAP HCM Implementation: Best Practice for configuring

Hi,
This is my first independent project of HCM implementation. I have just started the system configuration. Done with setting up the PA, PSA, EG and ESG. Assigned to CC. At this stage, I have a very basic question which is, what is the best practice for the next steps of configuration. What do I go to next, step up the OM in the SAP EasyAccess Menu? How should I go from here?
Would really appreciate some explanatory assistance.
Thanks in advance.
Papri
Edited by: papri_rc on Jul 8, 2011 6:40 AM

Its all depends on business requirement
at starting as i advised you review your BBP , make sure you configure everything
for your reference iam giving the following data for OM and PA config..
as part of OM
1.     depict client org structure using simple maintenance , with this you can create large structures in less time(while doing org structure be careful and refer BBP)
2.     maintain integration switches
3.     maintain plan version
4.     maintain number ranges
Configuration for PA
HR Enterprise /PersonnelStructure
u2022     Personnel Areas
u2022     Personnel Sub Areas
u2022     Employee Group
u2022     Employee Sub Group
u2022     Assignment of Personnel Area to Company Code
u2022     Assignment of Employee Sub Group to Employee Group
Basic Settings
1.     Maintain Number Range Intervals for Personnel Numbers
2.     Determine defaults for number ranges
Personal Data
1.     Create Forms of Address
2.     Create Marital Status
Family
1.     Defined Possible Family Members
Addresses
1.     Create Address Type
Communication
1.     Create Communication Types
Contractual and Corporate Agreements
1.     Define Contract Types
2.     Determine periods of notice
Employee Qualifications
1.     Create education establishment types
2.     Define Education Training
3.     Create educational Certificates
4.     Create branches of study
5.     Determine permissible certificates for education type
Infotype Menus
1.     User Group Dependency on Menus and Info groups
2.     Infotype Menu
3.     Determine choice of Infotype menus
4.     Infotype Menus
Actions
1.     User Group Dependency on Menus and Infogroups
2.     Info Group
3.     Personnel Action Types
4.     Create reasons for personnel actions
5.     Change Action Menu
*Developments(ABAPconsultant will do)     *Field Enhancements     (any field enhancements in infotypes)
Customer Infotypes     -Develop any customer infotypes if required for the business from 9000 series
Edited by: Piscian . on Jul 8, 2011 9:08 AM

Uploading data in infotype 0024

Hi all,
I want to upload datain infotype 0024 - qualifications tab. Now the issue here is that this infotype contains a table control in which the data is not getting stored in infotype 0024 but some place else instead.
Please suggest how to tackel the situation using bdc.
Thanks
Ribhu

Ofcourse i need more information - please read this:
Well please go to pa30 and try to create a record in Infotype 0024.
There in the qualifications tab, you cant enter anything - u have to click on the create button below the table control to choose languages - various check boxes for languages.
Now when I do recording - this step of choosing the languages do not comes up . moreover the fields in the tabstrip for qualification - they are not in the pa0024 table and are stored somewhere else. So even if i use hr_infotype_operation, it do not shows up the fields for qualifiactions tab - like language, profecincey level and dates for various languages.
Please suggest if you know something.
Infotype no 0045 is also a similar infotype where the data gets stored at some other place ..... I mean by any chance if u know how to upload data in IT0045, it would be a great help.
thanks
Ribhu

HR ABAP -- infotype 0024 enhancement

u201CNew joiner u201Cis an action in our client system in which 8 infotypes are configured. When I execute this action in PA40 transaction, the 8th infotype that appears will be 0024.When this infotype screen appears as a part of u201DNew joiner u201Caction, the user should be presented with the defaulted qualification and proficiency based on nationality of the individual.
I decided to look for a user exit. The user exit PBAS0001 gets triggered for the PBO and PAI of every infotype in PA .But infotype 0024 u2013 (Qualifications) belongs to Personal Development (It belongs to package PPPE).There is no exit associated with this package. Also I searched for the string u201Ccustomer u201Cin the function group RHP6 (0024 infotype screen belongs to this function group) but couldnu2019t get any solution.
Also I did not get any result for searching u201CBADIu201D in the above function group. I am using ECC 5.0 system.
The user needs the values to be defaulted in the 0024 infotype screen .
Can you please suggest any other approach to achieve the above objective?

that is an Function group problem tell to your Functional people, they will resolve

Direct access to document image via webservice - best practice?

Howdy,
 Rookie "Post-er".... be gentle. I've searched and I've read... didn't find this. I've not taken training. I may be way off base.
We have multiple manufacturing sites around the world with local Operator Qualification appls that want to access the enterprise SAP DMS mfg document images (stop dual maint - enterprise & local).... without dependency on SAP ECC being up. If we can pass them DMS meta-data via near-realtime msgs (including the document image access "key" data); then we would assume they can direclty access KPRO for the document image as needed.
Would this be considered a "best practice"? Webservice controlled (access only from known source).
Is PHIO-ID the only dynamic variable needed (based on info below I found in WIKI)?
*Alternatively, the url as below can be used to retrieve the documents from the content server[*http://<Server_Name>:<Port_No>/archive.dll?get&pVersion=<Version_No>&contRep=<Content_Rep>&docId=<PHIO_ID|http://<Server_Name>:<Port_No>/archive.dll?get&pVersion=<Version_No>&contRep=<Content_Rep>&docId=<PHIO_ID|\||]>
 <Server_Name> = Content server (IP address or name of content server)
 <Port_No> = Port No. of the server
 <Version_No> = Version No of content server (Transaction OACT)
 <Content_Rep> = content category of the server (Transaction OAC0)
 <PHIO_ID> = PHIO Id derived for each upload method

Hello,
This reply posted to help others who may refer this in the future.
As Amit Maheshwari mentioned, it is possible to give access to a document stored in the Content Server even when the partner system(ECC) is down.
As per your requirement, you want to access documents when the ECC System is down, but the content server is up and running.
The following steps can be of help to you:
1 - Create a program, that will create URL for the documents stored in the content server and send the URL to the external system.(Refer: FM- SDOK_PHIO_GET_URL_FOR_GET)
The URL refers to the public IP of the Internet Server on which the content server is hosted on.
2 - With this URL and few configurations on the Content Server (to allow access from external systems) you can fetch the file from the content server to the external system. Access privileges may vary based on your security settings.
Note: Since the ECC system will be down, creating URL for all the documents can be a bottleneck.
Probable Solution: While adding a document to the ECC system, the respective URL can be created and transferred to the external system along with the master details and stored there.
This can be undertaken if it is really important for the business, as it will increase the load for the external system. The solution can be modified based on the business requirement.
Thank you,
Regards,
Tamilnesan G

Best Practice - Changing description for Org Unit/Position or creating new?

Hello Freinds,
I just want to know from your experience what's normally practiced in your implementations for OM :-
For scenarios where there is a need to change the description of a particular org unit or position, do u
1. just change the description effective a particular date (to maintain history) or
2. put an end date to those objects and create new ones ?
Solution 1 is quick and easy, but in IT0001 the description displayed is as on start date of that infotype which is normally a date prior to the change in desc of those objects. As a result this infotype keeps displaying old description.
Is there any way to change this display to show the current description instead of the description as on start date of this infotype ???
Solution 2 calls for a lot of related activities, say if i create a new org unit and delemit the old one - then i have to move all the sub org units and positions into this new one ... which is quite time consuming and doesn't really seem practical.
How do u manage such scenarios ?
Thanks
Allen

We use option #1, although I am not sure this is best practice. Using option 1 for positions makes it challenging when it comes to reporting on length of time in position. We frequently have the scenario where a person is reorged not because they applied for another position, but just because the big wigs want to move around the chess pieces. In these cases we simply modify the position attributes and then run a PA action. Then if you run a query and use the standard delivered Length of time in position field, it appears as if the person has been in the same position for years (which they have), but their position has been retitled, re-graded, and re-orged numerous times. This makes it very difficult to get to an employee's length of time in their role.
This is a great discussion question I hope more people respond with what they do and why.

Best practice Qualifications in infotype 0024

Similar Messages

Maybe you are looking for