Default G/L Account assignment value in Shopping Cart

[Former Member]

Hello Experts,

Need your help but urgently.

There is a Requirement of creating new p.Category so inECC New material Grp is created and i repliczte the same in SRM system Development . Now i went to Default account assignment and assign my new P.Cateogry with default G/L account for Cost center.

It was working fine in Development but when i transport these settings to my SRM_quality system the source system for all the P.Categories Source system changes from QAS300SYCC to DEV300SYCC. i went to BDLS and run old and new logical system for table BBP_DET_ACCOUNT and source system gets changed but still when i create a Shppping cart default G/L account is not comming for all the P.Catoegories except the new one which i have created .

Smriti

[Former Member]

Hi there,

As per the standard design of GL account determination, the system will

first try to find the customing setting based on the category_guid,

category_id, acc_cat from the table bbp_det_account. If there is no

entry found, the system would then try to find the GL account based on

category_id and acc_cat alone and since in your case, there is the same

category id in different logical systems, the incorrect GL account is

fetched.

Setting up default G/L determination

See table V_BBP_DET_ACCT which can be accessed at

SPRO -> Supplier Relationship Management -> SRM Server ->

Cross-Application Basic Settings -> Account Assignment ->

Define G/L Account for Product Category and Account Assignment Category

This can be debugged in FM BBP_DETERMINE_ACCOUNT

Hope this helps,

Kind Regards,

Matthew

[Former Member]

Thanks mathew for your response,

I face problem when my P.categories and g/l got transported from DEV to QUA . now when i see tbale BBP_DET_ACCOUNT . i can see that all the GUID is changed. if i goto the view and delete the entry and maintain it again directlyin QA system then it works fine for me, Can you tell me do i need to maintain all the entries in the repsective system . Do they are not transportable but the transport request gets created.

Thanks!!

Smriti

[Former Member]

Hi Smriti,

Please see the answer from a development colleague :

- We cannot recommend to transport IMG table V_BBP_DET_ACCT entries

from DEV to PROD for the following reasons:

a) F4-help entries of field CATEGORY_ID contains category GUIDs

of LOGSYS DEV which may not exist in LOGSYS PROD.

b) If already entries in PROD exist in that IMG table it maybe

overwritten.

- Recommendation:

Please maintain IMG table entries with CATEGORY_ID reference

always manually using F4-help (dropdown). Sorry for the inconvenience,

but CATEGORY_ID /GUID triggers backend finding and is a substantial

and unique key field in every SRM system which cannot easily be

reused in other logical systems.

Also see note 872533 top 3.

Hope this helps,

Kind Regards,

Matthew

[Former Member]

Thanks ....

I maintain entries manually and then works fine...

Thanks to all the experts for the Guidance Provided

Smriti

[Former Member]

Mathew is very correct.

we do open a client and do the same for all new product category settings.

Muthu