Account assignment category not considered when populating OKB9 values

[Former Member]

Hi all,

We're on SRM Server 550, SP12. Read on if you have patience

An SRM Shopping Cart (SC) is created. Upon adding an item to the SC, the default account assignment category (e.g. OR - Order) is populated in the item from the user's org structure attritutes (PPOSA_BBP). At the same time, the system reads and populates default account assignment values (e.g. order number, cost center number) from the R/3 backend transaction OKB9. We've discovered that the default account assignment category is not taken into consideration during the transfer of values from OKB9.

This may lead to situations when the account assignment category does not correspond to the cost object number. For example, the default category OR (Order) is populated in the Shopping Cart from the user attributes, and at the same time the Cost Center number is populated from OKB9! This results in various problems, including corrupt Shopping Carts.

This behaviour occurs in standard SRM, with all BAdIs turned off.

Some processing scenarios where this problem may occur are described below.

Pre-requisites:

- OKB9 defaults are populated in R/3 for the G/L account (e.g. 516070) and plant (e.g. 5005) combination: e.g. cost center number is 11753, order number is blank.

- User attributes are maintained in SRM: the default plant 5005 (WRK), the default account assignment category e.g. OR (KNT)

Scenario A:

1. In SRM Web UI, create a Shopping Cart and add an item (e.g. from catalog).

2. On the Cost Assignment tab, note that the account assignment category is Order (from user attributes), and the number field is blank.

3. Check the SC. You would expect the message KI 235 "Account & requires an assignment to a CO object" per Note 815849, but this message does NOT appear. This is the first indication that something is wrong.

4. Hold the SC.

5. In transaction BBP_PD, ACC_CAT is "OR", ORDER_NO is blank, COST_CTR is "11753".

The Cost Center number got populated without end user's knowledge behind the scenes from OKB9, irrespective of the fact that the ACC_CAT is Order!

Scenario B:

1. In SRM Web UI, create a Shopping Cart and add an item (e.g. from catalog).

2. On the Cost Assignment tab, note that the account assignment category is Order (from user attributes), and the number field is blank.

3. Enter an Order number, e.g. 322123.

4. Check the SC. The following system messages are issued:

You cannot post to more than one real cost object

CO account assignments have different profit centers

Error in account assignment for item 1

5. Hold the SC.

6. In transaction BBP_PD, ACC_CAT is "OR", ORDER_NO is "322123", COST_CTR is "11753".

The Cost Center number got populated without end user's knowledge behind the scenes from OKB9, irrespective of the fact that the ACC_CAT is Order!

Scenario C:

1. In SRM Web UI, create a Shopping Cart and add an item (e.g. from catalog).

2. On the Cost Assignment tab, note that the account assignment category is Order (from user attributes), and the number field is blank.

3. Select Cost Center from the Account Assignment Category drop-down.

Note that the system now shows the cost center number in the number field - 11753.

4. Switch back to Order in the Account Assignment Category drop-down.

Note that the number field is blank again.

5. Enter an Order number, e.g. 322123.

6. Check the SC. The following system messages are issued:

You cannot post to more than one real cost object

CO account assignments have different profit centers

Error in account assignment for item 1

7. Hold the SC.

8. In transaction BBP_PD, ACC_CAT is "OR", ORDER_NO is "322123", COST_CTR is "11753".

The Cost Center number populated from OKB9 persists in the SC even after manually switching between account assignment categories!

Has anyone encountered the described issue, and if yes what was the solution (e.g. Customizing, SAP Note)?

Cheers,

Serguei

[Former Member · Accepted solution]

Hi. Have you asked SAP about this via a customer message?

If they tell you that it is standard behaviour, you can use the BBP_DOC_CHANGE_BADI to correct the data.

First select in the fields for your current account assignment category from BBP_C_ACCF where the account assignment = the one from the shopping cart item.

Then loop through IT_ACCOUNT and make sure the fields that are populated are specified in your account assignment.

If they are not then delete the entry and when you are finished pass it all to ET_ACCOUNT.

Regards,

Dave.

[former_member544585 · Accepted solution]

Thank you for replying, David.

Yes, I've created an OSS message, waiting for reply. I will have a hard time accepting that it's a standard behaviour. For example, with this behaviour, in the situation when both cost center and order are maintained in OKB9, they are both passed on to the SC, and "stick" there - one displayed to the user on Web UI, the other in the background. Switching between Order and Cost Center categories only changes the display of one or the other, but does not clear the non-displayed value. So, the SC under this scenario is always corrupt!

Cheers,

Serguei