cancel
Showing results for 
Search instead for 
Did you mean: 

Asset PO from PR - Cost Center getting cleared when Asset is entered in PO

amit_chavre
Explorer
0 Kudos

Hello Experts,

I'm having below issue. I have searched in the forum but could not find any solution.

Asset PR is created with cost center (same as linked in Asset >> time dependent) and G/L account.

When we try to create PO using PR, once asset number is entered, the cost center is getting cleared off/removed automatically.

My question is that is this a standard behavior of system or any correction required. Also can you please guide me where I can find the settings for above case.

Regards,

Amit

Accepted Solutions (1)

Accepted Solutions (1)

BijayKumarBarik
Active Contributor
0 Kudos

Hi,

You creating asset PR and PO where cost center disappearing.

Better use t.code OME9 , for account assignment A and allow setting for cost center as following

Now create a new PO and see how cost center appearing in PR and PO for acc. ass. cat. A

Regards,

Biju K

amit_chavre
Explorer
0 Kudos

Hello,

Even after making Cost Center field as display in AA cat. "A", while creating PO, Cost Center is getting deleted once asset number is entered. Please see below image:

Regards,

Amit

ajitkumar
Active Contributor
0 Kudos

In Assets ( AS03) time dependent tab you can see cost center. The asset is already assigned to a cost center.

Answers (1)

Answers (1)

former_member233510
Active Contributor
0 Kudos

When you create PR with account assignment category as 'A' then the system should ask you to input the asset number under the account assignment tab. When you convert PR to PO, the system adopts the asset details automatically from PR, no need to enter manually.

amit_chavre
Explorer
0 Kudos

Asset number is not available while creating PR, so PR is created without Asset and at the time of PO creation, asset number is mandatory & entered.

former_member233510
Active Contributor
0 Kudos

Call transaction OME9 and check the field status of Asset for the account assignment category 'A'. If it is marked mandatory then this applicable for both PR and PO. If the field status is already marked mandatory then the custom changes might be the reason for the system behaviour.