cancel
Showing results for 
Search instead for 
Did you mean: 

CO Object Error while doing GR

Former Member
0 Kudos

Hello Team,

I am doing GR for purchase order which has source system as SRM. While doing GR I am getting below error message - Account 1104030130 requires an assignment to a CO object While I have checked PO I have given WBS in PO itself still why this error ? I tried to posting to GL account via FB60 as well still the same issue.

I don't want to use any other cost object other than WBS. I have checked WBS is not neither statistical nor billing element. As well Account Assignment Element is also checked.

I understand this is quite common error but this time I don't understand why it is NOT picking CO Object as WBS ?

Thers no substitution also defined for this. What other check points are ? Or what I am missing here please guide.

Experts guidance is much appreciable.

Regards,

Sharvari Joshi.

Accepted Solutions (0)

Answers (3)

Answers (3)

kamalkumar_biswas2
Active Contributor
0 Kudos

Hi

Can you check mov type 101 field status and GL a/c field tatus...it should match

Run prog RM07CUFA  and see

former_member198650
Active Contributor
0 Kudos

Hi Joshi,

Have you created the PO w/ref to account account assignment?

Regards,

Mukthar

Former Member
0 Kudos

Yes Mukthar with "P", that is why system is facilitating me to enter WBS . Please let me know if you have any other checkpoints ?

Regards,

Sharvari Joshi.

former_member198650
Active Contributor
0 Kudos

Hi Joshi,

Check the WBS element whether it has the status as release or not and also it should allow goods movement also.

Regards,

Mukthar

Former Member
0 Kudos

Hello Mukhtar,

It is already released. Anything else ?

Regards,

Shavrari Joshi.

Former Member
0 Kudos

Hi Sharvari,

The most likely reason is Field status group assigned in Account master data. Check the "Additional account assignments" for the account and see if WBS element is optional or not.

If it is suppressed then the you cannot use it with WBS element.

Regards,

Ritesh

kamalkumar_biswas2
Active Contributor
0 Kudos

Hi

I think this error may be from SRM-CO integration where you have maintained not WBS as CO object account assignment,

Pl check with your SRM consultant also to check SRM transaction.....link to ECC