ALE -- E-Recruitment

We are implementing E-Rec on EhP4, WD4A. We are planning a 3 tier implementation. Are there documents about the ALE & IDOCS process for these two scenarios
-- Transfer employees as internal candidates (what is the triggering point, for example?)
-- Transfer new hires as employees (PA-48 action?)
You can also point me to links or resources that might be available.

Hello,
the decoupled infotype framework has a less close integration of infotype database and screen / ui representation. I know that it appears anywhere in the documents for the HR - E-rec integration but so far I have not seen any effects in standalone installations.
Perhaps the following link [SAP Help|http://help.sap.com/erp2005_ehp_04/helpdata/EN/43/a503b963161bbfe10000000a1553f7/frameset.htm] gives you more detailed information.
Kind Regrads
Roman

Similar Messages

ALE: e-recruiting organizational structure transfer

Hi friends,
I want to transfer the organization structure or the organization plan with O,S,C object types from one SAP system to another SAP system.
I have done the ALE configuration and using PAFL transaction to do the same.
I would like to know that model view i should use for the distribution also i would want to know the screen parameters in PAFL transaction.
I am doing the same for E-recruiting separate instance.
Regards,
Divya
Points would be given

Hello,
We are still having a problem with failing iDocs everytime we pass over IT0105 Sty 1 records from our SAP system to E-Recruiting.
Would anyone happen to know where I should start looking to troubleshoot this error message?
"Password is not long enough (minimum length: 6 characters)"
Currently both systems require that your password be at least 6 characters long, which makes this message even more perplexing.
Having a better understanding of how RBDAPP01 processes inbound IDOCS in status 64 would help. We are using message type HRMD_ABA. Our data filter looks like....
Infotype: 1000
Object Type: C, O, S
Infotype: 1001
Object Type: C, O, S
Subtypes: A002, A007, A008, A012, B002, B007, B008, B012
Infotype: 1001
Object Type: O, S
Subtypes: A003, B003
Infotypes: 0000, 0001, 0002
Object Type: P
Infotype: 0006
Object Type: P
Subtype: 1
Infotype: 0105
Object Type: P
Subtypes: 0001, 0010
So the question is how is IT0105 Sty 1 being processed when RBDAPP01 runs?
Thank you for your help!
Ryan
Edited by: Ryan Hubbell on Mar 31, 2009 7:00 PM
Edited by: Ryan Hubbell on Mar 31, 2009 7:47 PM

E-Recruiting Security Landscape (Different Clients)

Hi,
Our customer is discussing about E-Recruiting Security Landscape and now they are asking me if we can have the following landscape: One ERP having one client for HCM and another one for E-Recruiting.
They are asking me this because the application (we still don't know if will be the BSP or WDA)will be on the internet and they don't like the idea to have the ERP client (on the background) on the internet.
As far as I know we have just these scenarios to implement:
- E-Recruiting integrated with the ERP
- E-Recruiting and ERP with separated servers exchanging data trough ALE
- E-Recruiting integrated with the ERP but with the frontend for the External Candidate on a different server.
Here we are on ERP 6.0 and Enhancement Package 4.
I think that the customer scenario isnt't supported.
Also, has anyone used the scenario with the frontend for the External candidate(Constellation III with WDA) separated from the E-Recruiting system?
Thanks,
Daniel Kiel
HCM Consultant

Hello Daniel,
the two server scenario using a frontend server as a kind of additional proxy is a quite common, if you use web dynpro for candidates. Even for the standalone installations where e-recruiting is not on the hr server it is used very often due to security issues.
As said before I only know one e-recruiting 600 integrated installation which i rolled out on my own. The customer also uses the frontend server. I still would not recommend the integrated solution although it brings a lot of possibilities for contacs with the walldorf guys ;o).
For EhP4 it is a documented way to setup a sap e-recruiting standalone system on an ERP installation (erp installed but just e-recruiting run). This scenario is called I2B. It should be possible to implement it on a server which runs HR in another client but just as it might be possible it does not mean it is a good idea. I bet I could even run a standalone like e-recruiting setting within the HR server itself with EhP4 by using some kind of self ALE with broad renumbering of objects - my server admin just refuses to give me a server to prove it.
Even if you use another client the server is still open to the internet. Most security teams will not care that it is another client as it is the same server. Already the standalone installation is too open for some of my customers. As it uses some direct pull accesses to the hr server in standard. As this is a call from a less secure to a more secure network region this is a no go for some of them. One had all of these pull functions changed to a push system where HR server sends the information to e-recruiting otherwise security had not allowed the system. Bringing the HR server anywhere near Internet is completely out of imagination.
Best Regrads
Roman
Best regards
Roman

Issue in Data transfers using ALE for E-Recruiting standalone system

Dear Experts,
We have an issue in data transfers using ALE. We are having standalone system where E-Recruiting is maintaind seperately and the version is EHP5.
When we configured iDoc in Sandbox and its working fine. But when it comes to Dev and Quality servers this is not working fine.
we have created iDocs using the following filters.
For Object P: Infotypes 0000, 0001, 0002, 0003, 0006, 0024, 0105.
For Objects O,S: 1032, Subtype: 0010
For Object: 1001, Subtype: A003, A008, A012, B007
For Object O: 1001, Subtype: A002, B002, B003, B012, Tyoe of related object: O,S
For Objects: C, O, S, Subtype: 1000, 1002, 1028
For Object:C, Subtype: 1001, Subtype: A007
When we do the data transfers in Sandbox using PFAL it is transferring the data properly.
But when we do the same iin Dev and Quality servers we are not able to do it and gettign 52, 51 errors.
Here we are facing a strange issue. For some Users when we transfer data it is transferring data but with 52 error messgae.
For some users I am getting 51 error where i could not transfer any data.
For some users, when we tranfer O, S, and P related data is moving but getting mostly 52 error and all the relationships are not moving here for O,S and properly. But P related CP, BP and NA are getting created successfully.
It is happening only in Dev and Quality server and that too some users are able to get transferred but not all.
Where will be the issue? How can we resolve this?
Any help will be appreciable.
Thank you in advance.

Hi Sekhar,
Have a look over these threads.
Errors in ALE data transfer to E-Recruiting.
http://scn.sap.com/thread/1535402
BR,
RAM.

ALE data transfer in E-recruiting

hi All,
We are Implementing E-recruitment in HCM.
            I have following 2 requirements
Case 1). Distribute data of infotypes 0000,0001,0002,0006,0022,0023,,0024,1000 and 1001 into ER(E-recruiting) from my HCM (ECC) system. This i have achieved using message type HRMD_A and setting up ALE as per standard guidelines.
Case 2) i have to transfer Candidate data which gets created in E-recruitment server back into HCM(ECC) server(reverse of case 1) and stored them in infotypes 0000,0001,0002,0006,0022,0023 and 0024. How this can be achieved ??
is there any standard way i mean IMG configuration or ALE setup to transfer this data back into HCM (ESS) server?? or any BAdis or BAPIss??
    kindly suggest me some solution if anyone of you have encountered the same situation in past. The final solution i m thinking is of creating custom basic IDOC type, message type and custom programs for inbound and outbound processing but before doing this i just wan to have a confirmation that there is no standard way of doing this...
Thanks in advance..

Hi.
     There is a standard activity in e-Recruiting "Data Transfer for New Employee" which transfer the Candidate data from e-Recruiting to HCM system in temprary table T752F. when you hire this candidate from PA48 all transfer data will get stored in respective Infotype of SAP HCM system..
Thanks,
Madhu

How to - E-Recruiting ALE-integration step-by-step (EhP4)

Hi everyone,
Can anyone tell me the step-by-step guideline to perform the ALE initial run from SAP HCM to E-Recruiting using transaction PFAL (RHALEINI)??
We are implementing E-Recruiting stand-alone constellation: separate ECC instance integrated with E-Rec via ALE/RFC, enhancement package 4.
We've done some try-outs in the new version, but we lack the certainty that we've done things right.
Please do not refer to note 997181 since it does not explain the details on how to run the initial load. It explains adequately how to set-up the config and very basically how to run PFAL on page 2 (scen. I2-A) and page 4 (up to rel. 6.03)... But it's not sufficient in my opinion... We've done exactly the same...
So what I'm interested in is the right sequence of runs and the selection screen values.
We also have quite a few SLG1 errors which are unclear. Some suggest as if the processing occurs simultaneously (parallel) and blocks the asynchronous processes... Is there a certain number we should enter in the field "number of objects per process"? It's defaulted on 200...
Can anyone shed some light on the best-practice how to run this transaction?
Many thanks in advance!
Miroslav.

Hi Medic,
hope u r doing good.
Can u pls chk dese links by Roman,They speak alot on HR_ALE_ER issues.
Re: E-Recruitment Technical Structure ( Attn: Roman Weise)
Re: ALE data transfer from E-recruitment to HCM
Re: E-Recruiting- ALE is working for OM data, but not for internal employees
Re: ALE setting DEV / PROD
Re: ALE Linkage error in E Recruitment
Re: E Recruit 603 - ALE
Re: ALE from HR to E-Recruiting on EhP4
Regards
Rohit.S

E-Recruiting ep604 ALE ECC sync data

Hi all,
I already know that I have to synchronize the objects P, S, O and the standard ALE inbound processing for HR master data creates all other objects, such as BP, CP, and so on.
I read the SAP note 997181 and our escenario is I2-B, i also activated all the implementations listed on the document, but still have not been created the objects BP and CP.
Should I do other activities?
Thanks

Thanks Roman
I followed your suggestion, i run a hiring action directly on the e-recruiting server and the system created the CP object. Is the first time I synchronize data between ECC and e-recruiting.
These are the steps that I did:
1.- I use the t.code PFAL and distributed the object type O with the evaluation path O-O-S.
2.- Then i do the same with the object type P but without evaluation path.
The Message Type by default is HRMD_ABA as our distribution model use it with the following setting:
Filter group:
Infotype--> 0000,0001,0002,0003,0006,0105,1000,1001,1007,1008,1013,1025,1028 and 1033
Type of related object--> C, CP, O, Q, QK, S
Object Type--> C, O, P, S
In the e-recruiting system when distributed the object type P, the following warning message appears: "Relationship starting from 01P 10000039 impossible - 01CP50008123 does not exist/is not active". However in the ECC system the object P 10000039 is related with CP 50008123.
I would understand, how both system should be in the number range for personnel planning in the subgroup "01CP"
There are some basic configuration that I must do?
Thanks a lot for your help

Errors in ALE data transfer to E-Recruiting.

Hello,
I need help with my ALE for E-Recruiting.
We are on E-Rec 604 with seperated standlone e-rec system.
We have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with status 52.
Those are the messages:
Object 01 ,P ,01012021 does not exist: infotype 0105 cannot be created
Object 01 ,P ,01012021 does not exist: infotype 0009 cannot be created
Object 01 ,P ,01012021 does not exist: infotype 0006 cannot be created
Diagnosis:
You have tried to create infotype 0105 for plan version 01,object type P,object ID 01012021. However,the object does not exist.
PA objects exist if infotypes 0000, 0001, and 0003 have been created.
PB objects exist if infotypes 4000, 0001, and 0002 have been created.
PD objects exist if infotype 1000 has been created.
I followed the setting of "standalone" attachment to note 997181:
HRSYNC_P                                    CONV_HR_DATA_TO_EREC (active as of Release 604)
HRALE00INBOUND_IDOC             HRRCF00_INBD_NEWMOD (active as of Release 604)
HRALE00SPLIT_INBOUND            HR_INB_PROCESS_IDOC (inactive as of Release 604)
HRALE00INBOUND_IDOC             HRRCF00_DELETE_SPREL (inactive as of Release
604)
HRALE00SPLIT_INBOUND            HR_INB_PROCESS_IDOC (active up to Release 603)
HRALE00INBOUND_IDOC             HRRCF00_DELETE_SPREL (active up to Release 603)
So we have activated only the CONV_HR_DATA_TO_EREC and HRRCF00_INBD_NEWMOD because we are on 604.
We have distributed Infotypes 0000, 0001, 0002, 0105 (Subtypes 0001 and 0010), 0006, and 0009 and I have to distribute the P - CP relation with 1001 A209.
Somebody could help me please?.
Thanks,
Esther

Hi Esther,
Can you share you inputs how you have fixed the issue.
Currently we are following I2 A Scenario according to the link
http://help.sap.com/erp2005_ehp_05/helpdata/en/49/46037f06971ec6e10000000a42189b/frameset.htm
DO we need activate the swiches in HR System or Erec System.I believe it has to be in HR
HRALX HRAC - X
HRALX PBPHR ON
HRALX USRAC X
RECFA HRRFC
RECFA RECCE
RECFA DTCBA
BADI do i need to activate only below one's
HRSYNC_P
CONV_HR_DATA_TO_EREC (active as of Release 604)   HR system
HRALE00INBOUND_IDOC
HRRCF00_INBD_NEWMOD (active as of Release 604)   Erec System.
Correct me if im wrong.

Transfer IT0022 and IT0023 from HCM to E-recruiting via ALE

Hello,
In our HCM system we created a distribution model with HRMD_A type message and. Also we create several filter group with relevant data (infotype, object type...).
We need to transfer the IT0022 and IT0023 from HCM to e-recruiting, so we included these Infotypes into a filter group in the distribution model. We execute de t.code PFAL in the HCM system to distribute the data through ALE and the system include the data (IT0022, IT0023 and others) into the Idoc, but an error occur in the receptor system.
When we check the status message for the IDoc through t.code WE02 (in the receptor system), the status record is 51 - Infotype 0023 will be ignored (also Infotype 0022) and the Application document is not posted.
We need to transfer these two aditionals infotypes. Is there some missing configuration?
Thanks and kind regards

I assume, that you use e-recruiting as standalone system.
In e-erecruiting there are no PA infotypes. The inbound processing cannot work with those two infotypes. Therefore the inbound processing crashes.
Also there is no mapping possible with work experience and education of PA to e-recruiting in standard.
The only infotypes which are supported by standard are:
0001, 0002, 0006, 0105 + 1000 and 1001
If you want distribute further data, you will have to implement inbound processing and mapping yourself.
Also the target message type hrmd_aba05 in e-erecruiting the hrmd_a is mapped to does not contain those infotypes.
So you will need a specialist extending the idocs and extending the inbound processing BADI.
But before you do that, think if you can really map HR and e-recruiting infotypes, because fields and values do not match in generall. So this might be impossible!!!!
Regards
Sebastian
Edited by: Sebastian Menger on Apr 29, 2010 12:29 PM

ALE data transfer from E-recruitment to HCM

hi All,
We are Implementing E-recruitment in HCM.
            I have following 2 requirements
Case 1). Distribute data of infotypes 0000,0001,0002,0006,0022,0023,,0024,1000 and 1001 into ER(E-recruiting) from my HCM (ECC) system. This i have achieved using message type HRMD_A and setting up ALE as per standard guidelines.
Case 2) i have to transfer Candidate data which gets created in E-recruitment server back into HCM(ECC) server(reverse of case 1) and stored them in infotypes 0000,0001,0002,0006,0022,0023 and 0024. How this can be achieved ??
is there any standard way i mean IMG configuration or ALE setup to transfer this data back into HCM (ESS) server?? or any BAdis??
    kindly suggest me some solution if anyone of you have encountered the same situation in past. The final solution i m thinking is of creating custom basic IDOC type, message type and custom programs for inbound and outbound processing but before doing this i just wan to have a confirmation that there is no standard way of doing this...
Thanks in advance..

Hi Michell,
For this purpose, you will have to repair in three places.
1. One is the FM: HR_PREPARE_NEW_EE
Fro example you want to add something for infotype 008 you need to add this code ( level being the value you want to pass. ) :
PERFORM ppv USING email 'P0105-USRID' '03'.
Add the this in the import parameter as well.
2. You need to change include MP000040 under form: process_infogr. The internal table : proposed_values is carrying all the values.
You can insert your code right after this SAP's loop :
LOOP AT proposed_values WHERE infty EQ infogr-infty   "XDPK139847
                                AND seqnr IS INITIAL .      "XDPK139847
        IF proposed_values-fname EQ 'PSPAR-SUPDG'.          "QNUK74530
          pspar-supdg = proposed_values-fval.               "QNUK74530
        ELSE.                                               "QNUK74530
          MOVE proposed_values-fname                        "QNUK74530
            TO initial_values-field_name.                   "QNUK74530
          MOVE proposed_values-fval                         "QNUK74530
            TO initial_values-field_value.                  "QNUK74530
          APPEND initial_values.                            "QNUK74530
        ENDIF.                                              "QNUK74530
        DELETE proposed_values.                             "QNUK74530
      ENDLOOP.                                              "QNUK74530
For example for e mail it will be :
      if infogr-INFTY = '0105' and infogr-subty = 'U006'.
        infogr-subty = 'U009'.
        clear wa_infogr.
        loop at infogr into wa_infogr
          where INFTY = '0105' and subty = 'U006'.
                wa_infogr-subty = 'U009'.
        modify infogr from wa_infogr.
        endloop.
      if infogr-INFTY = '0105' and infogr-subty = 'U009'.
     LOOP AT proposed_values WHERE infty EQ infogr-infty   "XDPK139847
                                AND seqnr = '03' .         "XDPK139847
        IF proposed_values-fname EQ 'PSPAR-SUPDG'.          "QNUK74530
          pspar-supdg = proposed_values-fval.               "QNUK74530
        ELSE.                                               "QNUK74530
          MOVE proposed_values-fname                        "QNUK74530
            TO initial_values-field_name.                   "QNUK74530
          MOVE proposed_values-fval                         "QNUK74530
            TO initial_values-field_value.                  "QNUK74530
          APPEND initial_values.                            "QNUK74530
        ENDIF.                                              "QNUK74530
        DELETE proposed_values.                             "QNUK74530
      ENDLOOP.
      endif.
      endif.
3. You also need to change on the E -rec side in class:
CL_HRRCF_ACT_DATA_TRANS_RECORD
and method: TRANSFER_DATA.
Hope this is helpful.
Thanks
Amina

E-Recruitment - Loggin in Issues in E-Rec instance after ALE transfer

Hi,
We are running E-Rec in seperate instance and we have plans to implement the ALE Data transfer as a scheduled periodical Background job from HR system to E-Rec system.
We have also cutomized the ALE to set a default password when the data is transferred in to the E-Rec system.(We had done this to avoid the time & effort required from SAP Basis admin to reset the password of each E-Rec user whenever the ALE data transfer is performed)
After performing the ALE data transfer, when logging in the portal and accessing the E-Rec start page link the system prompts the user for a new password.
We are looking at an option where the ALE program can be modified to set a confirmed password instead of initial password.
Any suggestions on fixing this issue please. I request a solution for this on a high priority.
Thanks
G Raj

Sorry to be this direct,
but the first question which comes to my mind: Are you kidding?
You describe that you set the password of each user to the same default value just the bais admin is too lazy? And if this would not be enough you want that everyone can keep this password for eternity so everyone has always the possibility to log into every account including the recruiter / admin ones as they would be part of the ALE as all employees are part of the ALE and noone ever has to change the password (usually if you do not force someone to change his password he will never do)? Seems your security team died from an heart attac when u presented this idea so they do not have to be asked any longer.
Back to business:
The ALE creates a password on user creation. If the candidate is updated later the password won't be touched. Also if the user already exists when ALE is transfering an employee for the first time, the user will keep his password as before assigne authorization.
E-Recruiting has a standard function that the user can get a new password and unlock the user so no admin has to move a finger as long as the candidate has an email address where the system can send the new password.
If you do not want to bother the user with varius logins and passwords whild keeping a secure solution you shoul invest in a SSO solution.
Best Regards
Roman

E-Recruitment: Q-P not transferred as Q-CP in ALE

Hi
I am trying to transfer employee with Qualifications from HR system to E-Recruitment system (separate systems) via ALE. After executing PFAL, I noticed the Q-P relationships are not converted to Q-CP in the e-recruitment although the transfer was successful.
When i check the method HRRCF_CAND_FROM_EE_ALE, I realised it is reading the IDOC segment E1P1001 for conversion, rather than E1PAD31 which was storing the Q-P data. Can someone help? Thanks.
Regards
Stan

Hi Cheng,
The standard ALE method i.e. HRRCF_CAND_FROM_EE_ALE is only used to transfer org. assignment and basic personal data.
If you want to transfer Qualifications, you must use the BAdi in the class CL_HRRCF_CAND_FROM_EE_ALE . There is one implemenation , which u can code yourself.
Basically all these are used to create, transfer, create an E-recruiting user. so just try out this. May be it works for Qualifications.
Please get back to me with clarifications and try to assign suitable points.
Regards,
Bharat

SAP HR to E-Recruiting ALE for Qualifications - Dates Hard-Coded

The issue encountered occurs while using ALE to distribute Internal Candidate Qualifications from our SAP HR system to E-Recruiting (separate system/instance). The Qualifications which are stored in SAP HR (infotype HRP1001 or PA0024) looks nothing like what is being stored in E-Recruiting (infotype HRP5105) after distributation due to the fact that start and end dates are being hard-coded as 19000101 and 99991231. Given an internal candidate's proficiency in a qualification is changed, we don't know when it has changed. The time sequence is not being identified due to the fact that method CL_HRRCF_CANDIDATE_INFOTYPE_BL->MAINTAIN_CAND_QUALIFICATION is hard-coding 19000101 and 99991231 for the low and high dates. The standard class/method used for ALE inbound is
CL_HRRCF_EMPLOYEE_INBOUND->HRRCF_CAND_FROM_EE_ALE. As can be seen on line 558 we are always inserting qualications, no matter what time constraint the infotype is configured for. From our perspective this is unacceptable from a client perspective, since we cannot search for internal candidates effectively as a result since we do not know which proficiency they currently hold. We would like to generate interest in this since we need a "majority rule" to have SAP change the code.
Let me know if you need more detail to understand the issue.
Thanks in advance,
Matt

Thanks Roman
I followed your suggestion, i run a hiring action directly on the e-recruiting server and the system created the CP object. Is the first time I synchronize data between ECC and e-recruiting.
These are the steps that I did:
1.- I use the t.code PFAL and distributed the object type O with the evaluation path O-O-S.
2.- Then i do the same with the object type P but without evaluation path.
The Message Type by default is HRMD_ABA as our distribution model use it with the following setting:
Filter group:
Infotype--> 0000,0001,0002,0003,0006,0105,1000,1001,1007,1008,1013,1025,1028 and 1033
Type of related object--> C, CP, O, Q, QK, S
Object Type--> C, O, P, S
In the e-recruiting system when distributed the object type P, the following warning message appears: "Relationship starting from 01P 10000039 impossible - 01CP50008123 does not exist/is not active". However in the ECC system the object P 10000039 is related with CP 50008123.
I would understand, how both system should be in the number range for personnel planning in the subgroup "01CP"
There are some basic configuration that I must do?
Thanks a lot for your help

ALEs in E - Recruiting

Hi,
Can any body tell me what is the ALE that is triggered when Position is entered on the Organization data tab page of Requisition.The purpose of this ALE is to capture the Organization data from SAP R/3 to E recruiting
Thanks and best regards
Rajeev

Hello Rajeev,
there is no ALE triggered by entering the position in the Org tab.
The ALE is a requirement for having the possiblity to enter the position. The szenario is the following: when someone creates or changes a position in the hr core system a hr change pointer is written. Usually during the night a job is processing all the hr change pointers an creates Idocs according to your ALE configuration and sends them to the e-recruiting system. The e-recruiting system is processing the IDOCs (directly or by job depending on the configuration, while the processing via job is the recommended one). By processing the IDOC the position is created in the e-recruiting system. From that moment you are able to find it in the requisition maintanance org. tab..
Be aware that the vacncy flag has no effect in e-recruiting standalone systems.
Best Regards
Roman Weise

E-Recruiting: ALE Status 51 Posting Error - "Password is not long enough"

Hi experts!
We are having problems occationally posting idocs in our nightly ALE transfer from SAP to E-Recruiting. The error for the segment with a status 51 is "Password is not long enough (minimum length: 6 characters)". The system is trying to post IT0105 Sty 1.
This only seems to happen when either a new user is created in our SAP system. We are running SAP ECC 6.0 and E-Recruiting 6.0 sp10. In both systems you are required to have a password length of at least six characters.
Users in our SAP system are needed in E-Recruiting for the purpose of identifying internal candidates.
If both systems currently require that you have a password length of at least six characters, why would we recieve this error message when attempting to post idocs?
The concern here, obviously, is that if one segment fails to post in the idoc, the entire idoc fails to post.
Any help would be appreciated!
Thanks!
Ryan

Hello,
We are still having a problem with failing iDocs everytime we pass over IT0105 Sty 1 records from our SAP system to E-Recruiting.
Would anyone happen to know where I should start looking to troubleshoot this error message?
"Password is not long enough (minimum length: 6 characters)"
Currently both systems require that your password be at least 6 characters long, which makes this message even more perplexing.
Having a better understanding of how RBDAPP01 processes inbound IDOCS in status 64 would help. We are using message type HRMD_ABA. Our data filter looks like....
Infotype: 1000
Object Type: C, O, S
Infotype: 1001
Object Type: C, O, S
Subtypes: A002, A007, A008, A012, B002, B007, B008, B012
Infotype: 1001
Object Type: O, S
Subtypes: A003, B003
Infotypes: 0000, 0001, 0002
Object Type: P
Infotype: 0006
Object Type: P
Subtype: 1
Infotype: 0105
Object Type: P
Subtypes: 0001, 0010
So the question is how is IT0105 Sty 1 being processed when RBDAPP01 runs?
Thank you for your help!
Ryan
Edited by: Ryan Hubbell on Mar 31, 2009 7:00 PM
Edited by: Ryan Hubbell on Mar 31, 2009 7:47 PM

ALE -- E-Recruitment

Similar Messages

Maybe you are looking for