Problem on account assignment

[#1]

Hello,

I'm customizing a new backend on our SRM.

For account assignment, if we change cost center for another one, I have a error which says " please enter a CC or an order".

Can somebody help me.

Thanks!

[yann_bouillut]

Hi,

You have a configuration issue.

Now let's start from the beginning )

Can you create a PO directly in your new R/3 backend with exactly the same data as with your SC ?

Do you have the same error message ?

Kind regards,

Yann

[Former Member]

No I can create a PO with the order in my backend.

[yann_bouillut]

Hi,

Ok then

Can you create a PO (without changing the cost center) in SRM ?

Kind regards,

Yann

[Former Member]

Yes I can, but if I'm changing the cost center too.

But I can create a PO even if i change my cost center.

I can't when I want to change my imputation type like to have for exemple en order instead of a cost center

[yann_bouillut]

Hi,

Thus your issue is linked to the account assignment change (from CC to OR or WBS...) ? Correct ?

If yes, can you confirm that your SRM configuration point " Define G/L Account for Product Category and Account Assignment Category" is correctly set-up ?

Path : SPRo-> SRM server-> Cross-Application Basic Settings->Account Assignment->...

You should have for your product category (or *) , the correct backend system + a correct G/L account related to the order.

Please confirm.

Kind regards,

Yann

[Former Member]

In fact we don't use this.

To find the G/L account, we have some code in BADI change.

Our system is already implemented in 2 backends and it works for them...

[yann_bouillut]

Hi,

Do you have any other SC badi implemented ?

I guess your issue comes from one of your BADI ...

Kind regards,

Yann

[Former Member]

Hi,

we have implemented BADI check and Change...but i'm not really good on ITS debugging.

But I check something, When I do a "normal" SC, I put on my material group and then my cost center is automacally filled, for my other backend, we have to fill it, I think it is a R/3 custo. At this time the field "Business Area" is empty and still empty.

But if I change my account assignment for "Order" there is data in the field "Business Area".

In my backend that are already work this field stays empty, I think the problem might come from this.

What do you think about it?

Thanks,

[Former Member]

Hi

<b>

Seems to be Configuration issue in SRM side.

For time being disbale all the custom BADI Implementations and see what the standard SRM functionality is doing, when you shop using ITS Web ?

Especially de-activate the BADI Impmnetations -

BBP_DOC_CHANGE_BADI

BBP_DETERMINE_ACCOUNT

using transaction SE19

Note down whether the Cost center agains gets filled or not in this case for the same material group (Same Item Category in Shopping cart), which you used earlier ?

Also, note when you change to A/c assignment category "Order" in the cost assignment tab, what hapens ?

As far as i remember, Business Area data is not maintained in SRM side, not it will remain empty .. anyways, note down, what happens in this case ?

I guess, either the code or the configuration settings are getting over-rideen by one another and this problem is happening

This depends on the SRM Scenario configuration settings as well.

Anyways, Please keep me posted about the findings.

</b>

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

Hi,

I have news.

I'm debugging my program. the error doesn't comes from the BADI but it seems to come from the program SAPLBBP_PD specially the form "procdoc_update"...but I don't know anymore for the moment

[Former Member]

Hi

Which program you are mentioning here ? What are the steps to re-generate this issue ?

Please elaboarate in details.

Hope this will help.

Please reward suitable points.

Regards

- Atul

[Former Member]

In fact I have some breakpoint in Include LBBP_PDF0J on SRM side.

At the end of the program the function "BBP_PD_LOG_GET_MESSAGES" is called and I have my message on it from message class BBP_PD n° 047.

[Former Member]

Now i found that the error comes from function "META_ACC_PURCHASE_REQUI_CHECK"