cancel
Showing results for 
Search instead for 
Did you mean: 

Idocs not created in the sender system

Former Member
0 Kudos

Hi experts,

I've configured the HR-CRM integration (OM+PA). Now I'm proceeding with the download of the employees from the transaction PFAL, but for some of them the relative Idoc has not been created neither in the sender system HR. I don't understand the reason why the idocs are not created.

In particular, we I launch the background job no errors are displayed.

Could you please indicate me which are the checks to perform in order to inderstand the reason of this behaviour?

Thanka lot.

Best regards,

Stefano

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

I'm already using the SAP_ALL authorization profile: I think it can cover any authorization issue.

But the problem still persists.

Do you have any other suggestions?

Thanks a lot for the support.

Best regards,

Stefano

Edith-Cuellar
Explorer
0 Kudos

I know maybe is too late, but I answer because it could be useful for others. I pretty sure that the reason because some of your employees are not replicated via PFAL, is because they do not compliant with the following sentence:

u201CWhen PA infotypes are distributed, you must ensure that at least the existence infotypes 0000, 0001, 0002, and 0003 for personsu201D

You can find this requirements in PFAL Application help

As you said you are only replicating the Infotypes that CRM needs, but the ERP where your HR system is, it requires that Infotypes 0000, 0001, 0002, and 0003 exist, just to be sent.

If the problem were authorization you could see it in job log.

Regards,

Edith Cuellar

Edited by: Edith Cuellar Vazquez on Oct 19, 2009 9:15 PM

Former Member
0 Kudos

Hello

I've the same problem I think. The problem is, when I create a new PersNo PA40 the hiring start date is in the future, for example 01.04.2011, the dataset is listed in the table BDCPV. After I run BD21 or Pfal with this new PersNo, no Idocs generated. The message "NO data distributed". And in the table BDCPV is the field "process" = X.

So I just have this problem, if the Persno hiring in the future. When I change an exist employee or create a new employee the hiring start date in the present, than everthing is working.

Hope somebody can help me

Former Member
0 Kudos

Hi Ozlem,

I am facing same issue now. I don't see any idocs for pernr with a hire date in future. Have you found any solution for this issue. could you please share?

Thanks in advance.

Former Member
0 Kudos

How can I perform that check? Where can I see if the user used to run the background

has the correct authorizations to process also the employees affected by this issue?

Thanks a lot.

Best regards,

Stefano

0 Kudos

Mainly, you would need to check the user-id's profile, look for 'P_ORGIN' object to see if it's limitted by personnel area, employee group/subgroup, org key. Also, if structural authorisation is turned on, you also need to see if the user is assigned to an authorization profile.

Rgds.

Former Member
0 Kudos

Exactly! I've already checked also the distribution model and it seems ok: there aren't filters concerning the company code or the personnel area.

In fact some of the employees correctly downloaded belong to the same company code and have the same personnel area.

Other checks?

Thanks a lot.

Best regards,

Stefano

0 Kudos

When HR master data change are done to the ee that "do not work", did you check if change pointers were created for these changes ? Also, check the user-id used to run the background job to process change pointers to see if the id has correct authorization to view these ee that you have issue with.

Former Member
0 Kudos

Sorry, but it doesn't work. I tried but nothing.

I don't understand the reason why the same procedure doesn't work for all the employees, but only for some of them.

I've already checked the infotypes which are mandatory for the replication into CRM and they are ok: infotypes 0000, 0001, 0002 and 0006 have been properly maintained in HR.

Could you please give me other indications?

Thanks a lot.

Best regards,

Stefano

0 Kudos

Did you mean it generates idocs for some ee sucessfully, but not others? If this is the case, check your distribution model to see if it has filtering on company code or personnel area .

Rgds.

Former Member
0 Kudos

Hi Ted,

this is exactly what I've just tried to do but the idoc has not been created in HR.

Do you have any other suggestions?

Thanks a lot.

Best regards,

Stefano

0 Kudos

Try one more thing. Make some change to an HR master data record. Then run 'BD21' tcode with message type = 'HRMD_A' (or your custom message type) to see if an outbound idoc is created. If not, check if change pointer is created for HR data that you just change in sending system (I think RHALECPS program). If no change pointer created, check if for some reason either central change pointer or change pointer specifically for HRMD_A message type is turned off.

Rgds.

Former Member
0 Kudos

Hi Ted,

thanks a lot for your answer: I've always used the "Update" transfer mode for Data Migration, also for the Initial Download.

Doing so I've already transferred thousands of employees and this is the first time I face this kind of issue.

Anyway, I tried to do as suggested by you but anything changed. The background job launched from PFAL runs in zero seconds without creating any idocs in HR.

Do you have any suggestions?

THanks a lot.

Best regards,

Stefano

0 Kudos

Stefano :

Could you manually try to do PFAL for 1 employee with objtect type = 'P', object id = employee number in 'Insert mode' to see if an outbound idoc is created ?

Rgds.

0 Kudos

Check the background job to run 'PFAL' and see if 'Tranfer mode' radio button is 'Insert' or 'Update'. If you want to push data to receiver system the first time, you may want to use 'Insert' with object type/ object id parameters filled . After that, switch this transfer mode to 'Update' (process from change pointer).

Rgds.