Blank account assignment in plan-driven scenario

[Former Member]

Hi experts,

I'm currently in a project that R/3 purchase requisitions need to be transfered to SRM for sourcing processing - plan-driven scenario. The problem is that materials subjected to inventory management are associated to purchase requisitions (originated from MRP run) with blank accounting assignment category as their destiny is stock and not final consumption.

As SAP note 505030, external requirements with an unknow account assignment category are not supported in SRM. Does anyone have never had this problem or have an idea of how to solve it?

Best regards,

Cristiano Soares

[Former Member]

HI Pritesh,

I've done a formal consulting with SAP and they've answered that blank account assignment transfering is only available for the extended classic scenario because that's the only SRM scenario that supports direct material purchasing.

Have you activated the extended classic scenario in your SRM implementation?

Regards,

Cristiano Soares

[Former Member]

Hi,

Yes we have activated the Ext Classic scenario.

Regards

Pritesh

[Former Member]

Hi all,

First, sorry for the late response!

Yann, I've applied the note 930893 and it haven't solved my issue.

Dean, me actual problem is sending the purchase requisition without accouting data to SRM, but I'll test direct procurement also.

Cristophe, my SRM version is 5.0. I think that blank account assignment is standard in SRM. I'll create an OSS note to SAP.

Best regards,

Cristiano Soares

[Former Member]

Hi,

We too using SRM 5.0 and R/3 4.7.Could you tell how the issue was finally resolved.Hi,

Observed that when we create Requistion in R/3 using ME51N with account assighnment the Purchase Requistion gets transfered to SRM 5.0.But if i try to create Purchase Requisition without account assighnment it gives the error ANORETRY.

What could be the reason?

[Former Member]

Hi Cristiano,

Pls be sure you have "active" direct material procurement scenario, if you went to create PO which need to left account assignment as "blank".

Because if you set item as "Order as Direct Material" (this button only availablein in PO or S.C. item detail or you used the BAdI "BBP_DP_PROD_CHK_BADI"), the filed of account assignment will be "disable", then PO can sent to backend system and doesn't need account assignment.

best regards,

Dean

[Former Member]

Hi Cristiano, Hi Dean,

you don't have to play with "Order as direct material" or linked BADI in SRM.

In fact you can not even play with it, because PR are creating SC in the background with an RFC user, and you are not supposed to change them.

Direct procurement is directly enable by R/3 when sending the PR to SRM, if the item has a blank account assignment (EBAN-KNTTP) and an material number. (also possible for special stock scenario with EBAN-SOBKZ = E (orders on hand) or Q (Project stock).

This can be overwritten by R/3 BADI BBP_BADI_EXTREQ_OUT.

Cristiano, the main issue for you remains the account assignment category mapping in SRM.

Rgds

Christophe

PS: please reward points for helpfull answers

[Former Member]

Christophe,

If I let it blank (withou any value) in R/3, the following error occurs in SRM: Account assignment category could not be determined - Inform system admin

I've set the organization to the account assignment type STR - Generic Account Assignment, but the error continues as well.

Regards,

Cristiano Soares

[yann_bouillut]

Hi Cristiano,

I don't know if this note is relevant for you but

OSS note 930893 may resolve your issue.

Kind regards,

Yann

[Former Member]

Hi Cristiano,

Yann's note 930893 is valid for Government procurement.

Are you using it ?

What is your SRM release, because SRM external requirement processing has changed (use of new BBP_RFC_EXTREQU_UPDATE_IN instead of BBP_EXTREQ_INBOUND).

This make me remember this specific problem of account assignment category in External Requirement Scenario...

In standard, ECC is sending the accounting data but not the account assignement category (even if field ACC_CAT is available).

The category is determined by SRM (in function BBP_ACCCAT_MAP_IMP), by analyzing the accounting data.

You can use the SRM BADI BBP_ACCCAT_MAP_IMP to change this mapping/determination.

I never understood why we don't simply send the R/3 acc assignt category and map it to SRM category based on the mapping table (function BBP_ACCCAT_MAP_IMP has got the import parameter I_R3_ACC_CAT, but it is not passed !!).

Instead of this, a "fuzzy" logic is used: SRM scans all defined accounting categories with their main accounting field, and check if it is populated in R/3 accounting data !!! It's a kind of lotery...

So to have something correct, you must code the SRM BADI !!!

You could try to use the R/3 BADI to pass the backend accounting category, but in that case it will be kept as is in SRM, without mapping to internal SRM accounting category !!!

So, you have 2 solutions:

- use R/3 BADI to send acc category and change SRM ABAP code to take & map correctly this value

- use R/3 BADI to send acc category and SRM BADI BBP_DOC_CHANGE_BADI to change the SC data (it is called just before the creation) to convert the incoming ACC_CAT to real SRM ACC_CAT, using the std mapping table. In this BADI you will have to detect that you are in creation mode of an external requirement: you have the R/3 PR ID in item data.

Rgds

Christophe

PS: please reward points for helpfull answers

[Former Member]

In addition:

I remember the response from the support: this is designed like this because SRM is multi backend, and each backend and customer has its own categories, so we can not use the backend category directly.

If you are in a mono backend scenario, there is also another simple solution: delete all standard accounting categories in SRM, and re-create them with the same category ID as in R/3.

So in R/3 BADI, complete the accounting data with the category, and it will be ok in SRM, without doing anything.

Pros: simple and less code

Cons: use some 'K' category instead of 'CC' with is more <i>german</i>...

Rgds

Christophe

[Former Member]

Hi Cristiano,

This scenario is standard and should work.

In fact PR for stock items have a blank account assignment category, and this will activate the Direct Procurement scenario in SRM.

This is Ok.

But here, you are making a mistake when reading this note 505030: <b>unknow account assignment category</b> means 'X' category, and not blank category...

So there is no problem... ))

Rgds

Christophe

PS: please reward points for helpfull answers