BUT000 table not being updated with Business Partner

[mike_mccrary]

Hello Experts,

Can someone tell me how the BUT000 table gets updated with the BP number through a Hire process in PA40? Also, can someone tell me what tables need to be updated for Workforce Management (WFM)?

ECC 6.0

Portal 7.0

Thanks,

Mike

[Former Member]

Hi Mike:

I must confess, I'm not going to be very helpful for WFM, but I think I can help for the Business Partner piece.

Once everything is configured correctly, right about the time you hit the save button on infotype 0 for pa40, a few things will happen....

The Pernr will be generated. Then a Central Person will be generated and linked to the Pernr via the 209 relationship. Finally a Business Partner will be generated and linked to the central Person via the 207 relationship. It's at that moment you should see an entry in BUT000.

Are you seeing an issue with a BP not getting created at time of hire? If that's true, you could take a look at a couple things:

1) Is the BP number range and grouping configured?

2) Does the user you're doing the hire action with have proper authorizations for infotype 1001 and for obect CP/BP?

If you want to try explicitly creating the BP for a P or CP, you can always go to program HR_SYNC_PERSON and give it a try. If the BP is instantly created, you should know your issue is more about the access of the user doing the hire action. If it's not, you should get some guidance from the error message displayed.

Good luck.

Thanks,

Chris

[mike_mccrary]

Hello Chris,

We were able to resolve our issue by adding a function module called "WFA_BP_CREATE_MANUALLY" in our application. It is now updating the BUT000 table along with some of the other WFM tables such as WFM_AGENT and WFM_AGT_ORG.

I really appreciate your help and direction on this.

Thanks,

Mike

P.S. The P->CP->BP gets updated in the HRP tables by our application; It is coded to add those relationships. Which worked correctly for the past couple of years.

[mike_mccrary]

Good Morning Chris,

You are correct about the HRP tables getting loaded, but somewhere it is not writing to the BP tables anymore? I have checked the BP transaction and it is not showing the new hire (receive message BP does not exist). Also, I ran the repair, in the HR_SYNC_PERSON report and it gives me 2 warning messages on why it did not work.

1) Business Partner not created.

2) No unique jurisdiction code cannot be determined.

Any ideas on how I can get those BP tables loaded again?

Thanks,

Mike

[Former Member]

Hi Mike:

I know those warning messages well. They were the bane of my existence for quite some time. Ok, so I'm guessing your system has Vertex in use on the Finance side. They care about different kinds of Business Partners, but the BP object all the same. So when it goes to try to generate a BP, SAP goes and cross references the cost center that the person is tied to. Then it looks at the cost center's address and then cross references that with Vertex to choose a tax jurisdition. Who thought you'd be looking at tax jurisdictions, right!? When SAP finds more than one tax jurisdiction available, it will bring a popup to choose one. HR_SYNC_PERSON can't handle processing that popup, so it gives the message you got. To get around that I asked Finance to shut down Vertex for a short while (in non-production systems) and then in prod they had to configure that specific error message to only be a warning and not an error message.

However, I'm a little confused how you get the HRP1001 entry from a CP to a BP but still don't have a BP created. the SOBID in that HRP1001 record should be the true BP OBJID that you can take into transaction BP and find the info you're looking for. You're 100% sure the HRP1001 records say P 123 is tied to CP 456 and then CP 456 is tied to BP 789?

[mike_mccrary]

Chris,

Thank you for your reponse on this. I just want to give you a little details of why I asked this question. Currently, we are using MSS PCRs for Hiring our Employees. This application is customized and has been working for the last couple of years. Some reason, in the past month, we started getting this "error creating the WFA agent" when we hire people. We have supplied support packs in one landscape of our systems, but not in the other and they are both doing the same thing. My guess is someone on the WFM team has made a change somewhere and not realizing the impact. But, they are not sure of any change they made that could affect this.

Through our debugging of this application, it appears that the BUT000 table is not being updated with the new hire. Which should pass their hire data to a WFM Function Module and in turn create a BP and Agent. With the information that you provided, we are creating the B207 Relationship. Also, I ran the report too and that returned an error under the column Basic Data.

With that said, if you have any more information on the BUT000, that you think would be helpful, please let me know.

Thanks again for your response,

Mike

[Former Member]

Hey Mike:

Thanks for the clarification. Good info.

Just to make sure I understand. Your current situation IS creating an HRP1001 record between the CP and a BP at time of hire.... however there is no entry in table BUT000. Is that correct? That would be a peculiar one because that would mean a BP object is getting created but not getting stored in basically the most basic BP table.

However, if what I'm saying is correct, are you able to find the person when going to transaction BP?

Thanks,

Chris

ps - for the program HR_SYNC_PERSON, once you get results up on the right side, you'll want to highlight one of those records, and click the button that looks like 2 boxes with 2 arrows pointing down. That's the 'repair' button. If you are creating a BP already, this may be irrelevant, but I just thought I'd toss it out there.