Program RHALEINI

Hi all, i'd like to share with somebody a doubt concerning the program RHALEINI (transaction PFAL); For my customer i've set the HRMD_A message type for the transfer of certain infotypes from our system to their; The transfer mode is the doubt: how can i tell the program only to send only changes on MD and not all MD? Is the radio button "changes" for this purpose? If yes i'm missing something, bacause each time that i generate an idoc is the full population and all infotypes.
Do i miss some customazing to check? Is the message type HRMD_ABA done in order to send only changes? Does anybody have any documentation or reference where i can have a look?
Thanks in advance
Paolo Dazio

Hi
Welcome to sdn.
Select the transfer mode as Update.
You need to use only HRMD_A.
Cheers,
Abdul Hakim
Mark all useful answers..

Similar Messages

ABAP program RHALEINI

Hi All,
    I want to execute the SAP standard program RHALEINI from my customised program using SUBMIT statement. I want to pass the values for Plan Version , Object Id and Object type from my customised program. If you have any clue to which variables I should pass the values plz post.
Thanks & Regards,
Rahul Rathi

Hi Rahul,
in transaction SE38 or SE80 you can use the button [PATTERN]. In the following Screen you mark radio button [Other Pattern] and select with F4. In the list you could change SUBMIT. Then continue. This will *** you for the report name. Then the coding is write into your program like :
SUBMIT rhaleini
        with infty ...
        with insert ...
        with mestyp ...
        with pchactiv ...
        with pchbegda ...
        with pchcuttr ...
        with pchdepth ...
        with pchdymod ...
        with pchendda ...
        with pchistat ...
        with pchobeg ...
        with pchobjid ...
        with pchoend ...
        with pchopera ...
        with pchostat ...
        with pchotype ...
        with pchplvar ...
        with pchseark ...
        with pchsetgd ...
        with pchsobid ...
        with pchsvect ...
        with pchtimed ...
        with pchwegid ...
        with pchztr_a ...
        with pchztr_d ...
        with pchztr_f ...
        with pchztr_m ...
        with pchztr_p ...
        with pchztr_y ...
        with pchztr_z ...
        with proof ...
        with psize ...
        with rcvprn ...
        with rfcgr ...
        with snd_orig ...
        with subty ...
        with update ...
Regards
Bernd

Problem with RHALEINI - SAP HR Distribution

Dear All;
we are using program RHALEINI to distribute the Employee data from HR System to our EBP System. Some times we have some employee missed out or approver data missing.
Any pointers to how and where the program picks up approver data and why some employees are being left out while distribution would be greatly appreciated.
Thanks,
Vathsan.

Hi Srivathsan,
One of the reasons for employee missing out might be that, those personnel number might be locked with some other user ids , even we were facing this problem .
Regards,
Santosh

RHALEINI (PFAL) logs

Hi,
Where can I find logs created by transaction PFAL (RHALEINI) - ALE Distribution of HR Masterdata
if I check on the codes there is an
object: HRALE
subobject: OBJECT
however, everytime i run it, the logs that are created on tcode SLG1 is only
object: HRALE
subobject: IDOC
Where might I see the logs created with subobject OBJECT? because the latter logs only shows "Some data was not distributed because of conversion errors" but i want to see the specifics which according to the code, it is on the subobject: OBJECT.

The issue is I have the program RHALEINI in a custom program. the application log is a result of this program. by running PFAL manually I was able to see the errors.

Populating the custom segments for the Basic type attached to HRMD_A (IDOC)

Hi,
I've enhanced a few infotypes and want the new fields to be available in an IDOC created through the program RHALEINI.
Here are the steps I followed.
Step 1 :(we31)
We created new segment Z1IT023 , containing all the fields from infotype 0023 along with the custom fields added.
Step 2 :(we30)
We created an extension of IDOC type HRMD_A07 by name HRMD_EX to include this segement.
Step 3 :
We added an entry in table EDIMSG against message type HRMD_A , with base type : HRMD_A07 , extension : HRMD_EX , version : 700
Step4 :(we20)
Now , we made changes to partner profile by adding entry for message type HRMD_A with base IDOC type as HRMD_A07 and extension as HRMD_EX
Step5:
We changed the entry in table T777D and specified the IDOC segment as Z1IT023.
Step6.
We then tried to execute the report RHALEINI to generate the IDOC. The IDOC got created, but it didn't have the data for the segment Z1IT023.
In fact, there is a different solution to this... by adding the custom segment(containing nly the new infotype fields) as a child of the original segment E1P0023 and then writting code in the user-exit to populate the segment, but our intension is to have a single segment with all the infotype 0023 data. Besides, I believe in HR, making an entry in T777D should free us from writing any code for populating the IDOC segments.
Can anybody please suggest me, where am I going wrong. How can the new segments be populated automatically.
Thanks in advance.
Sujit.
Responses will be suitably rewarded.

Hi,
Did u get any exit to populate the custom segment?
Thanks,
San

IDoc status 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

Reg idoc interface

hi all,
its regarding idoc interface,try to help me.
i have a programRHALEINI and defined in Work Item WA00012 - "IDOC Extract for HR Master Data"
This IDoc will be created in SAP but not delivered to any external system.
The interface created in this work item will then read these IDOCs and the required fields will be identified and reformatted so that it can be processed by the FMS system.
Program RHALEINI is executed to create the IDocs for all employees. Refer to Work Item WA00012 - "IDOC Extract for HR Master Data
WI WA00012 will also provide Function Module Z_TP_INI_IDOCS to pull all the IDOCs needed to extract all of the employee data (latest employee extract).
The purpose of this interface program is to read all IDOCs created by program in WA00012 and map the required data into a flat file structure.
here to map i have header trailor and body data how to do this.
provide me solution asap with an example
thanking u

Hi,
Once you get the idocs then you have to read the info from these idocs and then you have to populate it into your file.
It depends on the data format that they want to create it.
cretae a file of type l_v_filename TYPE draw-filep,
then start creating header structure item structure and footer structure.
keep passing data to these structures and transfer it to file
TRANSFER l_wa_header TO l_v_filename_temp
same thing you cna do for ur item data,
loop on this and pass line by line to the file.
same way populate the footer data also.
It entirely depends ont he way they want to populate in the final file.
Reward points if you find useful.
Regards,
Sasi

Current date - x in variant

Hi,
I want to use program RHALEINI (tcode PFAL) with a variant.
In the field "Data selection period from" I want to have a value like current date - x.
In the Variant Attributes I select "D" for Selection variable (Dynamic date calculation) and as Variable name I select Current date +/- 30.
Then I get the message "Lower limit of interval is greater than upper limit"
Could somebody help?
Thanks and regards
Patrick

Hi,
at the moment I have selected "Current date" for "Name of Variable" of the field "Data selection period from".
If I try to select for example "First day of previous month" nothing happens.
If I select "Current date - 30" I still have the same error message mentioned above "Lower limit of interval is greater than upper limit".
But the lower limit should be less than before.
I would be very thankful if someone could explain this behaviour.
It works in ERP 5.0 but it's not working in ECC 6.0.
Regards
Patrick
Edited by: Patrick Koehnen on Aug 28, 2008 3:28 PM

Organizational structure creation

[Organizational Structure creation using HRMD_ABA;
Appologies if you saw this message on Friday, because I did originally post it under the general area. I was hoping that if I re-posted it under this area I might get a few more responses. I have included the one response I got, plus my reponse, which does contain more detail about how I ran PFAL - program RHALEINI, and re poses the question about what needs to be created in SRM re an organisational structure, prior to doing an initial load using transaction PFAL.
Many Thanks
Claire
I am trying to set up the organizational structure in our SRM 7.0 system using our ECC 6 organizational structure. I have created all the required distribution models for SRM and ECC 6, and have set up the switch settings in SRM. The number range settings have been set to external.
As per OSS Note 36317, which concentrates on the initial distribution, and I am working through, I have run PFAL in ECC 6 only for object type O. The HRMD_ABA idocs have been successfully transferred to our SRM system, but all are at status 52.
The message for all the idoc segments is:
'You tried to create a relationship from object 01O 50000333 to object 01S 50000846. However, object 01S 50000846 does not exist or is not active in the period from 19000101 to 99991231'.
One thing I haven't done, which might be incorrect, is create an Organizational Plan in SRM. I specifically haven't done this because I am wanting to use external numbering, and therefore thought the organizational plan would get automatically created as part of the initial distribution.
Does any one have any idea how to resolve my problem?
Many Thanks
Claire
Re: Organizational Structure creation using HRMD_ABA
Posted: Aug 21, 2009 6:03 PM    in response to: Claire Crosby-C...           Reply
Hello Claire,
It looks like you are replicating "S". After the "O" replication you should run the "S".
Please refer to the OSS note 934372 u201CSRM/CRM: HR integration for business partner u2013 new featuresu201D & SAP Note # 550055 EBP/SRM: New integration for business partner as well.
Hope this is helpful.
Thanks
Ashutosh
Claire Crosby-C...
Posts: 45
Registered: 3/22/04
Forum Points: 0
   Re: Organizational Structure creation using HRMD_ABA
Posted: Aug 21, 2009 6:53 PM    in response to: ASHUTOSH TRIPATHI     Edit          Reply
Hi Ashutosh
I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
I have also read the other 2 notes you mention.
Note 363187 stated:
'Perform the following steps in the sequence given if the target system is a
mySAP.com system (SEM, CRM, BBP/EBP):
1. If you want to use the change pointers for later changes, activate
them at once. During initial transport, you should not maintain the
data in parallel in HR because the distribution takes the blocking
mechanism into account, which can cause an incomplete initial
transport.
2. All objects of object type O are distributed with program RHALEINI. As
a transfer mode, the update mode with infotype 1000 selection should
be used.
This way you make sure that all objects of object type O are created
in the target system for existence checks.
3. As previous step but for object type C.
4. As previous step but for object type S.
So far all I have tried to do is up to step 2.
When running RHALEINI I have entered the following:
Objects - Object Type = 'O'
Reporting Period - Today is selected
Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
Any thoughts would be really helpful.
Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
Thanks
Claire

Hi Ashutosh
I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
I have also read the other 2 notes you mention.
Note 363187 stated:
'Perform the following steps in the sequence given if the target system is a
mySAP.com system (SEM, CRM, BBP/EBP):
1. If you want to use the change pointers for later changes, activate
them at once. During initial transport, you should not maintain the
data in parallel in HR because the distribution takes the blocking
mechanism into account, which can cause an incomplete initial
transport.
2. All objects of object type O are distributed with program RHALEINI. As
a transfer mode, the update mode with infotype 1000 selection should
be used.
This way you make sure that all objects of object type O are created
in the target system for existence checks.
3. As previous step but for object type C.
4. As previous step but for object type S.
So far all I have tried to do is up to step 2.
When running RHALEINI I have entered the following:
Objects - Object Type = 'O'
Reporting Period - Today is selected
Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
Any thoughts would be really helpful.
Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
Thanks
Claire

HR_Master Data to SRM

Hello Gurus,
I have the HR-Master Data for User to be replicated by using PFAL in R/3 to SRM.
can any 1 assist in using this done.plz assist me.
its Urgent.
about the Plan Version,
Object type,Object ID,Search Term,
Object status.
Thanks
Arshad

Hi
Which R/3 and SRM version releases are you using ?
Here are required details ->
Plan Version -> 01 (for current version)
HR Object type -> 'US' ( for User ), 'O' ( for Organizational unit), 'CP' (for contact person)
Object ID -> Contains a unique eight-digit number that represents a specific object, such as an organizational unit, a qualification, a business event, and so on.
Search Term -> In this field you can enter a search term to search for objects which you want to work with (organizational units, qualifications, events etc)
Object Status -> Contains a one-digit code that represents a status. All objects have one of the following statuses: active, planned, submitted, approved, or rejected. E.g., 1 (for Active), 2 (for Planned), 3 (for Submitted), etc.
Also Please go through this details as well ->
HR: ALE Distribution of HR Master Data
Description.
Scenario 1: Distribution of HR Master Data from a Central Central HR System
Requirements
Data is maintained centrally in the integrated HR system. Distributed data must not be maintained in the target system; see SAP Note 119780.
Message Types
HRMD_A: Distribution from the HR system to other SAP systems
HRMD_ABA: Distribution from the HR system to systems that are based on an SAP application basis system, such as the mySAP.com components CRM, EBP, and so on. For details, see SAP Note 312090.
HRMD_B: Distribution from the HR system to an SAP basis system. This message type is not currently relevant, since this system type is not delivered as a stand-alone product.
Basis IDoc Types
See also table EDIMSG or transaction WE82.
For HRMD_A*, HRMD_ABA*, and HRMD_B*, transaction WE30 displays the current version in each case with the highest sequential number, for the SAP Release 4.70 HRMD_A06, HRMD_ABA04, HRMD_B04.
In normal circumstances, that is when the participating systems are not SAP basis systems, you must use message type HRMD_A or HRMD_ABA. The system suggests the most suitable one on the selection screen in the program RHALEINI (or in the transaction PFAL, which has the same function).
Output
In accordance with the model views in the distribution model, the selected data is transported to the target system.
Tips and Tricks
For questions and answers on setting up a distribution scenario for HR master data, see SAP Note 200066.
Supported HR Object Types
Personnel Administration object types: P Person, AP Applicant (only for message type HRMD_A)
Personnel Planning object types: all (non-external) object types except X*. For information on T*, W*, RY*, see below.
Supported HR Infotypes
Transaction WE30 enables you to display the infotypes currently supported by a message type. In this respect, E1Pnnnn means that infotype Pnnnn is distributed (assignment in table T777D), and E1PADnn means that additional data PADnn for infotype P1001 is distributed (assignment in table T77AD).
For performance reasons you should enter all required object types and infotypes/subtypes as filters in the distribution model.
Infotypes referring to data that cannot be distributed (such as cluster data) are not included in the standard system (see SAP Note 105148), or are distributed without the additional information (for example cluster data, texts) (see also SAP Note 310993).
Customer includes for the infotypes are not automatically taken into account during distribution. Function exits are provided for supporting customer includes.
Transfer Mode
The transfer mode determines how data on the objects (= plan version/object type/object ID) is imported into the target system:
Insert (Create) for Complete Transfer
Data records for all of the objects and infotypes from the distribution model are transferred in full to the target system. If an object to be transferred already exists in the target system, it is replaced in full, which means it is first deleted completely (all infotypes) and then created again using the distributed data records.
You can specify a reporting period (data selection period). The system distributes all of the data records that are valid for at least one day between the 'start date' and 'end date'.
For a complete data transfer you must use insert mode. For consistency reasons we recommend that you use the reporting period 'All'.
Update (Change) for Period
You can specify a reporting period (data selection period). The system distributes the data records of the infotype/subtype to be entered that are completely within this period. In the target system, data records of the entered infotype/subtype that are completely within this period are deleted (relationships are only deleted if they were created earlier by distribution, see below: local relationships). The distributed data records are then created. In particular, this logic ensures that deleted data records, too, are correctly processed.
In this mode, IDocs created by change pointer evaluation are dispatched.
Import Lock:
Using an entry in table T77TR in the target system, you can lock specific object types/infotypes/subtypes for import.
You completely lock object types for import by entering an existence infotype:
Lock object type P by entering infotype 0000, object type AP by entering infotype 4000, PD object types by entering infotype 1000.
Size of IDoc
Each IDoc transfers a maximum of 200 objects. You can reduce this number with an entry in table T77S0: ALE BSIZE.
Execute Function
Change Pointers
To distribute changes after a complete transport, you can use change pointers. Once they have been activated (in the IMG), change pointers can be dispatched periodically using report RBDMIDOC.
You can display change pointers
Execute Function
and process them again, if necessary.
Execute Function
Generic Data Filtering
As well as the standard filters, you can define and use generic filters. See the corresponding section in the IMG.
Filter 1 for Distribution of HR Master Data: Execute Function
Filter 2 for Distribution of HR Master Data: Execute Function
To determine the filter values for each HR master data record, you must implement a BAdI: Display Documentation
Serialization
For distribution, you can implement serialization. See also the relevant section in the IMG.
Activate Serialization in ALE Inbound Processing: Execute Function
Activate Serialization in ALE Outbound Processing: Execute Function
Auxiliary programs allow you to control the settings:
You can check the consistency of serialization settings: Execute Function
You can display the counter status of the registry in ALE inbound
processing: Execute Function
You can display the counter status of the registry in ALE outbound processing: Execute Function
SAP Enhancements as Function Exits
Under the SAP enhancement RHALE001 are function exits that you can use in ALE inbound and outbound processing.
SAP Enhancements as BAdIs
Business Add-Ins continue to be available in the HRALE00* namespace.
Error Handling
You can use the standard task HRMD_Error (TS 00408178) for error handling in ALE inbound processing.
Component for Notes and Error Messages
Notes for ALE distribution of HR master data are stored under the component BC-BMT-OM-ALE. You must also use this component when reporting error messages in this area.
Restrictions:
HR master data has just one central HR System in which all HR components are integrated. Distributed HR master data must not be changed in the receiving system. Profiles with read authorization only, for example, enable you to ensure that distributed HR master data is not changed in the receiving system. Alternatively, you can use the original system mechanism from scenarios 2 and 3.
Only the infotypes required for SAP standard scenarios are supported.
Data in the receiving system is created with the same plan version as in the sending system. If the active plan version is not selected in the sending system, the distribution program displays an error message.
Only the object type, infotype, subtype, or related object type can be used as a filter. This means that data cannot be filtered in accordance with any other fixed organizational criteria if there is more than one receiving system. However, you can define customer-specific filters. For more information, see the "Generic Data Filtering" section above.
If you want to create additional HR master data records directly in the receiving system (such as a work center in Logistics), you must ensure that the number range intervals are different from those in the sending system.
Tasks (object types T*, W*) and responsibilities (object type RY) are not distributed. The relationship (infotype 1001) for these object types can be distributed. This means, for example, that you cannot distribute a standard task, but that you can distribute a relationship for a standard task.
You can reduce the messages. You can also use rules to convert data, with the exception of using a conversion rule to fill fields with initial values.
If you want to create a relationship to an object in the target system, but the object does not exist (yet) in the target system, a note is included in the transport log. In this instance, the IDoc is assigned status 52 (posting of application document incomplete) so that incomplete transports are recognized. If the missing object is distributed to the target system at a later date, the relationship is created automatically in both directions, and is therefore complete. A relationship to external objects (such as cost centers) is distributed and created in the target system if the external object exists there. For more information on this topic, see SAP Note 443187.
In update mode, a local PD relationship in the target system is retained. This means that a relationship created locally (not by distribution) in the target system is not deleted in update mode. On the technical level, a distributed relationship can be recognized by the fact that the value AL is entered as an ALE marker in the P1001-REASN field.
PA data and PD data is saved (updated) in the target system without checks (unlike in dialog or batch input). In particular, this means that updated data is not validated (time constraint, time delimitation, allowed values). What is more, no change pointers are written, the transport connection and workflow connection are deactivated, dynamic actions are not performed. You must take this into account when transferring data from an interface to an external system. The external system itself must itself ensure consistency and the correct format. For more information, see SAP Note 134085.
If you want to use standard transactions in the target system to access HR data, Customizing in the target system must be identical to the Customizing in the sending system.
Lock in ALE outbound processing: in the sending system, a lock entry is created for each object when data is sent. If objects are already locked in the sending system (by a maintenance transaction, for example), they are not dispatched. This is documented in the program log. You must repeat the send procedure later.
Lock in ALE inbound processing: in the receiving system, a lock entry is created for each object when data is received. If objects are already locked in the receiving system, they are not updated. This is documented in the status of the posted IDoc. You must repeat the posting procedure later.
When PA infotypes are distributed, you must ensure that at least the existence infotypes 0000, 0001, 0002, and 0003 for persons, or 0001, 0002, and 4000 for applicants, are distributed. For the distribution of holder relationships (S-P), you must also distribute infotype 1001 for persons.
In the sending system, you must have authorization (PLOGI, P_ORIGIN, P_APPL, structural authorization for T77PR and T77UA) to display the infotypes. For holder relationships (S-P), you must have authorization to display person infotypes (P_ORIGIN) in the receiver system.
Infotype 0003 is only distributed by change pointers if it has been changed in combination with one of the other PA infotypes that is supported.
Example
Personnel number for existence check:
Object type: P, infotypes: 0000, 0001, 0002, 0003.
Personnel number for existence check with holder relationship:
Object type: P, infotypes: 0000, 0001, 0002, 0003, 1001.
Applicant number for existence check:
Object type: AP, infotypes: 0001, 0002, 4000.
Personnel number for generating vendor accounts in Accounting:
Object type: P, infotypes: 0000, 0001, 0002, 0003, 0006, 0009, 0017.
Personnel number for sales personnel (maintained in HR):
Object type: P, infotypes: 0000, 0001, 0002, 0003, 0006, 0105, 0900.
Organizational unit, job, position with relationships:
Object type: O, C, S, infotypes: 1000, 1001.
Description
Scenario 2: Distributed Organizational Management
If you require further information on the 'Distributed Organizational Management' scenario, access the SAP Library and choose Cross-Application Components -> Business Framework Architecture -> ALE Business Process Library -> Human Resources -> Master Data Distribution (Human Resources).
Requirements
Scenario 2 'Distributed Organizational Management' is based on Scenario 1 'Distribution of HR Planning Data and HR Master Data from a Central HR System'.
This scenario is activated in T77S0: ALE REPLI.
Execute Function
By determining an original system (in original system table HRMDORIGIN), one logical system is determined for each object in Personnel Planning. Business responsibility is defined in this logical system.
A distinction is made between two types of object, namely the original (which usually exists in the system in which the object was created) and the replication (which is created by distribution).
Initialization
To initialize the original system table, the following function must be executed:
Initialization of HRMDORIGIN
Execute Function
To maintain HRMDORIGIN in expert mode, the following function must be executed:
Execute Function
The original can be transferred to a different logical system.
Execute Function
Objects as Original or Replication
The main differences between the original and the replication lie in the creation of change pointers and in inbound processing for distribution.
If an object is created in a logical system, that system is regarded as the original system and the object is stored there as an original. If the object is distributed, it exists in the target system as a replication.
A relationship that is distributed is created in the target system with the ALE marker (value AL in the P1001-REASN field), which flags it as distributed.
An original can be maintained. A change pointer is written to distribute the change. In insert or update transfer mode, an original is selected and dispatched. It is then created in the target system as a replication. This original is not overwritten during inbound processing.
A replication can be maintained. A change pointer is not written to distribute the change because the change is local. In insert or update transfer mode, a replication is selected and dispatched if the 'Distribute originals only' parameter has not been selected. It is then created in the target system as a replication. This replication is overwritten during inbound processing.
Report RHALEORIGLIST (transaction RE_RHALEORIGLIST) generates a list of original systems for the selected objects.
Execute Function
Relationships Between Original and/or Replication
A relationship between two originals can be created and maintained. Change pointers are written for distribution. In insert or update transfer mode, the relationship is selected and distributed. It is then created in the target system as a relationship with ALE marker (see above). This relationship between originals is not overwritten during inbound processing.
A relationship between two replications can be created and maintained. Change pointers are not written for distribution. In insert or update transfer mode, the relationship is selected and distributed. It is then created in the target system as a relationship with ALE marker. This relationship between replications is not overwritten during inbound processing.
A relationship between an original and a replication can be created and maintained. Change pointers are written for distribution, but only for the original with a determinable relationship direction. This specifies just one system, which prevents data from being distributed from both systems in both directions.
The distributable relationship direction is defined in T77ALERELA.
Execute Function
The distributable relationship direction is assigned in T77ALECOMB to the object type combinations for original and replication.
Execute Function
In insert or update transfer mode, the relationship is selected and distributed. It is then created in the target system as a relationship with an ALE marker. This relationship between original and replication is not overwritten during inbound processing.
A distributed relationship (that is, a relationship with an ALE marker) can be maintained between an original and a replication or between two replications. Change pointers are not written for distribution. In insert or update transfer mode, the relationship is selected and distributed. It is then created in the target system as a relationship with an ALE marker. This distributed relationship is overwritten during inbound processing.
If a replication is processed, a dialog box containing the appropriate information can be displayed in dialog mode. This function is activated by an entry in table T77S0: ALE POPUP.
Execute Function
Example
There are two systems, A and B, each with activated change pointers and distribution to the other system using change pointers.
Objects O 4711 and O 4712 have been created in system A and distributed to system B using change pointers, or insert or update transfer mode.
Object O 4713 has been created in system B and distributed to system A using change pointers, or insert or update transfer mode.
System A: Object O 4711 exists as an original
System A: Object O 4712 exists as an original
System A: Object O 4713 exists as a replication
System B: Object O 4711 exists as a replication
System B: Object O 4712 exists as a replication
System B: Object O 4713 exists as an original
Processing in System A for Infotypes that are not Relationships
In system A, infotypes 1000, 1002, and so on can be maintained for object O 4711. The object is an original, so change pointers are written.
Distribution by change pointer distributes the changed data from O 4711 in system A to system B. System B contains object O 4711 as a replication, so distribution overwrites the data in object O 4711 in system B.
Processing in System B for Infotypes that are not Relationships
In system B, infotypes 1000, 1002, and so on can be maintained for object O 4711. The object is a replication, so change pointers are not written.
Therefore, distribution by change pointer does not distribute the changed data from O 4711 in system B to system A. The changes are local and are overwritten again when data from system A is reposted.
T77ALERELA contains the entry 002 A.
T77ALECOMB contains the entry 002 O O.
Therefore, relationship 002 is distributed by change pointers from object type O as the original to object type O as the replication with relationship direction A.
All other relationships between the original and replication, even B002, are not entered, which means they are not distributed by change pointers.
Processing in System A for Relationships
Every relationship between original O 4711 and original O 4712 can be maintained. Change pointers are written, and the relationship is distributed to system B.
Every relationship between original O 4711 and replication O 4713 can be maintained. For relationship 002, a change pointer is written for relationship direction A002 from original O 4711 to replication O 4713, and the relationship direction is distributed to system B. No change pointers are written for any other relationships. In particular, a change pointer is not written for relationship direction B002 from replication O 4713 to original O 4711.
Processing in System B for Relationships
Every relationship between replication O 4711 and replication O 4712 can be maintained. Change pointers are not written.
Every relationship between original O 4713 and replication O 4711 can be maintained. Change pointers are not written. In particular, a change pointer is not written for relationship 002 (see above) between original O 4713 and replication O 4711 because relationship direction B002 has not been entered as distributable by change pointer from original O 4713 to replication O 4711.
Description
Scenario 3: Distributed HR Master Data
If you require further information on the 'Distributed HR Master Data' scenario, access the SAP Library and choose Cross-Application Components -> Business Framework Architecture -> ALE Business Process Library -> Human Resources -> Master Data Distribution (Human Resources).
The original system mechanism is retrieved for persons and applicants in the same way as for scenario 2 'Distributed Organizational Management'.
Requirements
Scenario 3 'Distributed HR Master Data' is based on scenario 2 'Distributed Organizational Management' and scenario 1 'Distribution of HR Planning Data and HR Master Data From a Central HR System'.
This scenario is activated in T77S0: ALE REPPA
Execute Function
In ALE inbound processing, PD / PA integration is activated in T77S0: ALE INTE
Execute Function
If a replication of a person or applicant is processed, a dialog box containing the appropriate information can be displayed in dialog mode. This function is activated by an entry in table T77S0: ALE POPPA
Hope this will help.
P.S. Please go through the help given with the Transaction - PFAL in the SRM system as well.
Do let me know.
Regards
- Atul

Integrating Data From ECC to CRM

Hi Experts,
My requirement is, After Updating the Material master data in ECC , the same updated data is integrated with the corresponding data of the Product Master in CRM.
Problem: to map the data from ecc to CRM , I am supposed to call this RFC Fm ( existed in CRM side) from ECC using RFC Destination.
to map the data to this TABLE parameter , In ECC side I don't have similar strcture that was exist in the SRM side. so could any body help me how can i send the data from ecc to this fm existed in SRM.
Thanks & Regards.
Naga Priyanka. T
Edited by: Priyanka Tubati on Feb 2, 2010 10:35 AM
Edited by: Priyanka Tubati on Feb 2, 2010 10:38 AM

Hi Kumar,
Please select the following parameters when downloading the HR Org from CRM:
You can do this in the program RHALEINI (or in the transaction PFAL, which has the same function)
Tx: SM30--> This scenario is activated in T77S0: ALE REPLI
Objects:
1. Plan Version: 01
2. Object Type: *
3. Object Id: Copy the Object Ids which you want to transfer from HR System
4. Object Status: *
Reproting Period: All
Structure Parmaters: Blank
Transfer Mode:
Insert: Complete distribution, this will delete the exisiting and recreate it in Target System
Update: this will update the change records in CRM system
Message Types: HRMD_ABA
Also check SAP Note: 119780
Hope this helps.
Regards,
Madde

Organization data from ECC to CRM

Hi Experts,
We need to download organization data from ECC to CRM, and our requirement is to download two different kinds of org structures, sales org structure and HR org structure. Could you please advise whether this is possible in the system and also if it is possible please advise how to download this.
Currently we are using ALE to download employees into CRM and transporting org structure in CRM systems from golden client.
Thanks&Regards,
Kumar.

Hi Kumar,
Please select the following parameters when downloading the HR Org from CRM:
You can do this in the program RHALEINI (or in the transaction PFAL, which has the same function)
Tx: SM30--> This scenario is activated in T77S0: ALE REPLI
Objects:
1. Plan Version: 01
2. Object Type: *
3. Object Id: Copy the Object Ids which you want to transfer from HR System
4. Object Status: *
Reproting Period: All
Structure Parmaters: Blank
Transfer Mode:
Insert: Complete distribution, this will delete the exisiting and recreate it in Target System
Update: this will update the change records in CRM system
Message Types: HRMD_ABA
Also check SAP Note: 119780
Hope this helps.
Regards,
Madde

Organizational Structure creation using HRMD_ABA

I am trying to set up the organizational structure in our SRM 7.0 system using our ECC 6 organizational structure. I have created all the required distribution models for SRM and ECC 6, and have set up the switch settings in SRM. The number range settings have been set to external.
As per OSS Note 36317, which concentrates on the initial distribution, and I am working through, I have run PFAL in ECC 6 only for object type O. The HRMD_ABA idocs have been successfully transferred to our SRM system, but all are at status 52.
The message for all the idoc segments is:
'You tried to create a relationship from object 01O 50000333 to object 01S 50000846. However, object 01S 50000846 does not exist or is not active in the period from 19000101 to 99991231'.
One thing I haven't done, which might be incorrect, is create an Organizational Plan in SRM. I specifically haven't done this because I am wanting to use external numbering, and therefore thought the organizational plan would get automatically created as part of the initial distribution.
Does any one have any idea how to resolve my problem?
Many Thanks
Claire

Hi Ashutosh
I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
I have also read the other 2 notes you mention.
Note 363187 stated:
'Perform the following steps in the sequence given if the target system is a
mySAP.com system (SEM, CRM, BBP/EBP):
1. If you want to use the change pointers for later changes, activate
them at once. During initial transport, you should not maintain the
data in parallel in HR because the distribution takes the blocking
mechanism into account, which can cause an incomplete initial
transport.
2. All objects of object type O are distributed with program RHALEINI. As
a transfer mode, the update mode with infotype 1000 selection should
be used.
This way you make sure that all objects of object type O are created
in the target system for existence checks.
3. As previous step but for object type C.
4. As previous step but for object type S.
So far all I have tried to do is up to step 2.
When running RHALEINI I have entered the following:
Objects - Object Type = 'O'
Reporting Period - Today is selected
Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
Any thoughts would be really helpful.
Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
Thanks
Claire

Resend an outbound idoc

Hi experts,
Can you please let me know how to resend an outbound idoc. It is HR master data related outbound idoc. Some idocs have been sent previously from SAP to business connector to a third party application. But the idocs did not reach the application. Is it possible to resend the same idocs from SAP again.
Thanks in advance,

Hi,
For HR data, you can resend using program RHALEINI in the order of organizational objects O,S,P, C
Thanks
Krithika

Personnel data replication to seperate HR server

we have a central R/3 server and separate HR server.
i already replicated onjects, relation ships, employee groups and subgroups to HR server from R/3 using ALE.
Now i am trying to replicate personnel data.
I am not getting any errors in both inbound or outbound idoc.but i didnt see any data in HR infotype tables.
can any one please tell me what i am missing.
Ale configuration is perfectly correct as i already sent 1000.1001 infotypes.
when i debug we19 i didnt find any error.
any idea??
any suggestions plzzz

Hi,
As you are saying that you are planning to replciate the HR org. struture to ECC, ask your HR team to assign the CP to user in ECC and then run the PFAL(program RHALEINI) transaction to replciate the correction.
with regards
Manjunath

Program RHALEINI

Similar Messages

Maybe you are looking for