ALE FOR HRM - EREC SYSTEMS

Hi all..
We are trying to configure ALE between Ecc Hr and EREC systems.
what we did :
3 badi imlementations were activated in HRM and EREC systems.
1. created logical system and assigned cleint.
2. created RFC connection and determined RFC dewstinations.
3. created Model view , added HRMD_A message type and created filers.
4. Generated profiles and distributed models.
5. Using Tcode Pfal for message type HRMD_A, for a ORG unit , we had sent data and IDOC status shows green with message reciever available , no filters, no conversions.
Issue :
But this org unit is not sent to EREC.
Differences :
1. In EREC system : Model is available with message type HRMD_A , but filters are not availale which are active in HRM ecc system.
2. in EREC , PFAL transaction : message type HRMD_B is comming by default and is in disabled mode, so even cannot change the message type. Even found that in table HRMD_A ia not available.
Please let us know , wether we should create the filters manually in EREC system or should we create HRMD_A message type manulally.
Thanks in advance
Regards
Ravi

Application Link Enabling (ALE)
You distribute data using ALE if you want to communicate from one system to
one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
· ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.

Similar Messages

SAP Erec System Integration with Portal

We have installed a new erec system in Sap nw 7.02 abap system which has to be integrated with Existing portal system. There is another existing HR system(ecc6.0 ehp ) which is already connected to portal. What are the steps to be followed for Integrating Erec system with portal.
Thanks.

Dear Colleagues,
We have similar situation and this week we hopefully will approach to integrate ERECRUIT with SAP Portal. We have recommendations from consultants but since ERECRUIT implementation is still no commodity’s I’d like to confront this recommendations and share experiences. Please have a look on the the thread about it:
ERECRUIT 606 integration with SAP Portal 7.31 - what to take in mind?
Cheers
Waldek

How to remove the complete ALE configuration for a given system

Hello everybody,
Through ALE ,data is transferred between a number of SAP systems and the necessary ALE setups are in place.
Now,a particular SAP system,which used to be a receivor to the central SAP system,is to be retired.
Hence,the associated ALE set up is to be completely removed from the central SAP system.
Is the following sequence correct?If not and I have missed something,please enlighten me with the correct sequence.
1.Removal of the receivor logical system and its assignment to client ,through transaction SALE.
2.Removal of partner profile, through transaction WE20.
3.Removal of RFC destinations,through transaction SM59.
4.Removal of transactional ports for the logical system,through transaction code WE21.
5.Removal of Distribution model between the retiring system and the central SAP system.
(a)Regarding distribution model,I have a question-if the distribution model is maintained such that it contains the linking relationships between the central system and several receivor systems(in addition to the one I wish to remove),then is it possible to remove only the desired linkage and not touch the rest?
(b)Through BD64,I have tried but I am able to delete only the entire distribution model as a whole,while I would like to keep the distribution model and delete just one of the nodes,so as to cut the connection between only central system and the retiring system.
This is so because the other receivor systems are working fine,involving a lot of batchjobs and I am afraid that deleting the distribution model wholly will create unnecessary trouble.
Any help will be appreciated.Thanks
Papri

HI Nicolas,
I chatted with Rev-Trac support earlier today and here is what they have come back to me with.
Assuming the change in question was carried out in the development system. Changes to fields in tables should in most cases be captured in transports. Assuming it was a transportable change then go to the development system and execute transaction SE16 and query Rev-Trac table /RSC/T_MFM_4T filtering by TABLENAME.
On executing the query you should see a list of transports involved with changes to the transport. You can then check to see if there is a recent transport associated with the change - if so then you can find out who created the transport by using standard SAP functionality."
If you find this doesn't help, then please contact your Rev-Trac Administrator who can then log a support request on our support portal at www.xrsc.com
Hope this helps, Rick

Error in RBDMIDOC report run in E-REC, for data transfer from HR to EREC system

Hi,
We are on EHP5, EREC 605, SP0007. EREC is on a standalone, separate instance. HR in a separate instance.
We have created new org.units & positions, which we are trying to move from HR to EREC system for starting the EREC process.
In the report message type, gave input "HRMD_ABA", The output throws this error. (Screenshot attached)
Please provide your helps on the reasons for the error and corrective action to be taken.
Regards,
ER.

Thank Nicole for the reply.
Just extending my query,
I have created newly 2 org.units & 2 positions under the org.units in HR system.I
If i want to create a requisition as a recruiter from EREC portal, for that newly created vacant positions, what needs to be done?
How to move that new vacant org.unit with position to EREC system ?
Should I run the org.unit with positions using PFAL (Insert/update mode) or use RBDMIDOC method ?
Look for inputs.
Regards,
ER.

E-Recruiting : How to setup ALE for standalone setup

Dear experts,
We are implementing eRecruiting with the following setup:
ECC 603 on a separate server from eRecruiting 603.
I know that in such a scenario we have to transfer the data to & from ECC using ALE and IDOCs.
We have setup RFC connections between both the systems & defined the same in the table T77S0 (both ECC & eRec using HRRCF & DTCBA)
After this can anyone please specify what needs to be done?
I am looking for some kind of detailed information or a reference to any documentation will also do.What are the activities that BASIS needs to take care. Some of the things i am looking for answers are :
What are the BADIs that i need to activate both at ECC & eRec level?
How do i set up or build an ALE model?
How do i decide on the meesage type?
When should i use transactions PFAL & SALE & how do i use it?
How do i check that the data is transferred successfully?
Your inputs on these topics will be appreciated.
Thanks & Regards,
Sowmya

actiivate following badis and enhancespot implementations on e rec server
HRRCF00_SEARCH_RANKING
HRRCF00_DELETE_SPREL
HR_INB_PROCESS_IDOC
these are important for ALE point of view.
Steps for ALE
Go to the Sender HCM system Transaction SALE
Define logical system under basic settings
assign logical system to the client
Create an RFC connection to Erec server with the same name as the logical system name
add the user id and password (use system user with SAP_ALL)
Go to Communication under sale tcode
Determine RFC connection for method calls
Create Standard BAPI and DIALOG destination for the Logical destination
In SALE under modelling and implementing business processes
Maintain distribution models and views
Create Model View
Add a message type HRMD_A for the model view and add the sender and receiver system
Then go back to sale
and in partner profiles generate partner profiles put the model view sender system and user(system user)
go back to sale
goto Maintain distribution models and views
there select your modelview (just hightlight) go to edit->modelview->distribute
in your sender system in T77s0 table for RECFA DTCBA maintain the RFC name of the E-rec system.
Now login to Erec system
There maintain the RFC connection to E-rec system with system user
Goto T77s0 for RECFA HRRFC maintain the RFC name to HCM system.
Go to PFAL transaction in HCM sender system and for the model view/message type you have created send the data to e-rec
Regards,
Divya

ALE for message type BATMAS

Hello
I am trying to generate IDocs for a copy of the message type BATMAS and have added some custom fields to this new custom message type..
1. I have created BD52 entries for this new custom message . But starngely the IDoc created is for message type BATMAS instead of the new custom message type in WE02. I am executing BD21 for the new custom message type . I have checked BD64 and partner profile settings for the new custom msg type. I have activated change pointers for this new message type in BD50 and BD61.
2. I added a new field MCHA LVORM to the fields in BD52 . But the IDoc is not genearted whenever we change deletion indicator(IDoc).. Its creating the IDocs for changing all the other already existing fields.
I'd appreciate any suggestions/help.
Thanks
V

Hi Ravi;
Just so I understand you, an IDOC was successfully created in ECC and sent to an outbound system. Your outbound system, in this case is PI, which is acting as middleware for your ALE. Now you have an error in PI and you can't get it sent to EREC.
I know people don't like getting questions answered with other questions, but why are you using PI in this scenario? Every ALE scenario I've utilized uses HRMD_ABA directly from ECC to the target system (not with a middleware piece included). In WE20, what would be the harm in changing your receiver port to your actual EREC system? Do you have some kind of business logic being executed in PI converting IDOC field values?
If you think you must use PI, then in sxmb_moni, it would be interesting to know the error message for the IDOC there. However, I think it's entirely likely you don't need to use PI at all and could just use a direct RFC between ECC and EREC.
Good luck,
Chris

Passing Changed extended fields using ALE-IDOC to receiving system

Hi all,
Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
For ex. in matmas05 extended for classification and inspection view and then created using 'CREATION'
related bapi.Do i also need to incorporate the changes by change related bapi or ir can be handled by change pointer concept.
Thanks.

Hi Sanu
1) Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.
=> Looks like you have extended standard IDOC here. so you need to find User Exit or BADI for the Push program to populate the additional fields. Yes, it is possible thru change pointers as well.
1) Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
=> Yes, as suggested in 1 try finding User Exits/BADIs.
Regards
Shital

ALE settings in sapR3 system logical system

Hi People
IN IDoc to File scenario
How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that, we have to 1st create LS name (for R3 sys & PI sys), after that we have to assign that name's how to assign that, PLS can u provide me to with screen shots (if possible) r any links
Regards
shekar

Hi,
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

ERec - Data Transfer from eRec system to HCM System

Hello All,
Currently am able to do the data transfer from eRec system to HCM system but am finding some inconsistencies here.
In our scenario we are on ehp4 and no XI in place, We are doing via RFC only. Stanalone eRec system
So here are few queries and if someone can address these would be really great and appreciate the help
1) While i do the data transfer activity, when i select activity and don not give the Hiring Date in the Org Assignment Column it throws an error "When transferring data using XI, the hiring date must be specified". But am not using XI, then why should it give this error?
Also is it not possible that i do the data transfer without any hiring date?
Also there are two options Planned and Completed. When i do the data transfer i keep it in planned status and do it it automatically saying that Complete
Is this correct
2)Now when i do the data transfer it is getting appeared in HR system when i execute the PA48 tcode.
Here my queries are
a) Suppose i do a data transfer for a candidate Abc on 10.10.2010 and run the PA48 tcode it appears in the list as hire date 10.10.2010
Now as a recruiter am again doing the data transfer for the same candidate Abc for 11.10.2010 and againg when i see PA48 there is again another entry for the Abc candidate for hiring
Is this correct process. How should these duplicate entries to be avoided. Pls help me
3) Also i case if I want additions infotypes to be transferred in PA48 how should we go for this development
Pls help me in these queries

Hi ,
Check the following OSS notes.
1. 1006679
2. 997181 ( Read the attachment in the OSS note ) gives the detailed information regarding EREC and HR)
Let me know if you need more info.
Regards,
Ram

What could be the Approximate time for HRMS Implementation?

Dear Friends,
Any clue on What could be the Approximate time for HRMS Implementation?
Modules: Core HR, Payroll, SSHR & OLM
Bahrain Legislation
2 Functional
1 Technical Resource
Integration with Third Party system for Financials..
Anyy approximate time pls..
Guru

Hi Guru,
Difficult to estimate these as each legislation is different.
I also presume, Bahrain is not a seeded legislation.
So you will have to write all the tax rules and reports.
But, as the Tax/NI rules for GCC are fairly simple, should not be difficult.
Best way to go about it, is to do it in phases.
Core HR - BG configuration, Person migration, Absences etc.. and finally any reports for HR
Payroll - elements, balances, formulas and all the logic.. and then all the reports.
Once HR and payroll are done.. SSHR and OLM should take 1/3(or 1/2) of the time you spent on the HR/Payroll.
Cheers,
Vignesh

ALE for G/L and Cost Center Master Data

Dear Expert,
I am a fresher in ALE and want to distribute G/L and Cost Center Master Data from our production system to Development and Q/A system. Can you give some guidances? and how to configure ALE for this purpose?
Regards,
MAL

hi,
steps to configure ALE :
1.first u hav to create 2 logical systems for ur 2 clients in BD54.
2.then assign thm in SCC4 for both clients.
3.thn crete rfc destination in SM59.create in client from which u want to send only.
4.create port in WE21 for sender.
5.create partner profiles in We20 for both clients,outbound for sender and inbound for reciever.
6.now create distribution model in BD64.
generate partner profiles and distribute.
now ur ale configration to send data frm 1 clnt to other is ready.
u hav diff methods like master data,change pointers,idoc extensions,idoc reductions,...... to send data .
hope this helps.
reward points if helpful.

ATTN: SSHR Rollup 3 for HRMS FP.K Rup 5671710

The SSHR Rollup 3 for HRMS FP.K Rup patch 5671710 has just been released today.
This patch contains fixes for the following bugs:
Bug 5612687 : ORACLE.APPS.FND.FRAMEWORK.OAEXCEPTION: FOR CHANGE MANAGER PROCESS.
Bug 5590776 : POSITION DEFAULTING AND POSITION LOV NOT WORKING IN RFC NOTIFICATIONS
Bug 5587674 : ONDEMAND:OHS: SEARCH IN SELFSERVICE HAS DUPLICATE VALUES FOR ASG
Bug 5582127 : ESC:PROPOSED_SALARY_N CONTAINS 38 DIGITS AFTER DECIMAL FROM SSHR.
Bug 5572041 : THIS PERSON IS NOT ELIGIBLE FOR THE ELEMENT ASSOCIATED WITH THIS ABSENCE TYPE.
Bug 5522407 : EMPLOYEE'S RECORD OR ELIGIBILITY CHANGED ERROR WHEN ADDING EMERGENCY CONTACT.
Bug 5515312 : SSHR SALARY CHANGES AUTOMATICALLY WHEN USING BACK BUTTONS.
Bug 5501388 : ONDEMAND:CANNOT ENTER REQUIRED FIELDS FOR JAPAN HIRE PROCESS.
Bug 5468591 : VOL TERM OF A MGR RESULTS IN INVALID ERROR MESSG -DUE TO SUB-ORD FUTURE ASSG CHG.
Bug 5527923 : GENERIC ADDRESS STYLE IS BEING REPLACED IN SELF SERVICE CONTACTS FORM.
Bug 5515814 : ONDEMAND:IN SSHR WHEN TERMING AND REHIRING AN EMP THE PARTY ID # IS NOT THE SAME.
Bug 5508360 : CHANGE JOB FUNCTION POSITION QUERY RETURN ONLY 'ACTIVE' STATUS POSITIONS.
Bug 5507401 : MANAGER SSHR HIRE APPLICANT GIVES NUMERIC OR VALUE ERROR WHEN ADDING SUPERVISOR.
Bug 5328872 : WRONG EVENT PASSED TO FINALIZETRANSACTION CALLBACK FOR DELETE ACTION ON SFL.
Bug 5138131 : DEFAULT VALUES IN EXTRA INFORMATION DFF IN SELF SERVICE NOT DISPLAYED
Bug 5652542 : THE EMPLOYEE'S RECORD OR ELIGIBILITY STATUS HAS CHANGED ERROR.
This patch requires additional prerequisite patches to have been successfully applied to your system before it can be applied. These prerequisite patches, as at the time that this patch was built, are listed below. Please check Oracle Metalink to determine if any of these have been superseded.
11i.HR_PF.K.delta.1 - 11I.HR_PF.K RUP 1
Regards,
Greg

We need to know the new codes which will be added and which if any will be replaced. We know those identified on the US Gov site but can Oracle Dev. provide the specifics in advance so we can update our Employment Applications etc to match Oracle HR definitions?
Regards,
Ed

ALE - BDM5 - No Checkable Systems:

Hi,
I have done the ALE connection settings , but soomething seems tobe missing..
In ECC, when i run BDM5, it shows CRM system as checkabel system and is green.
When i run BDM5 in CRM, there are no Checkable systems visible.
Is there anything that i have missed,
Kindly help...
Full points for helpful answers
thanks

hi kalyan,
when u r assigning message type BD64, u have to give the message type as MATFET for the receiving system.
check this link, hope u can understand.
Re: ALE INBOUND STATUS 51
Regards...
Arun.
Reward points if useful.

Error "codepage could not be determined for the receiver-system"

Hi,
we use the idoc-adapter to send message from mySAP ERP to PI.
All worked fine.
So, this morning I have changed the datatype of the messageId from "char" to "int" in mySAP ERP in the customizing menue (install param). So, no message received in SAP PI.
When I start transction "we05" in mySAPERP" I get the following error:
"codepage could not be determined for the receiver-system" status 02.
I have changed the datatyp to "char" but the same probleme
Can anybody help me please?
Regards
Stefan

This error shouldn't occur unless there is some modification at the OS level codepages.
Please check the entried in the RFC destination for connecting to the XI system. Unicode settings.
Regards,
Prateek

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

ALE FOR HRM - EREC SYSTEMS

Similar Messages

Maybe you are looking for