SAP for Public Sector Discussions
Foster conversations about citizen engagement, resource optimization, and service delivery improvements in the public sector using SAP.
cancel
Showing results for 
Search instead for 
Did you mean: 

Reassignment not inherited in PO

atif_farooq
Active Contributor
0 Kudos

Hi:

We have fixed wrong commitment items hit at PR usinging FMCB and FMCT. Now i am facing a issue. A PR whose commitment item was A and we changed it B vis reassignment. When we create PO with reference to Reassigned PR, system not inheriting PR commitment item, instead it is calling from FMDERIVE.. Is there a way to aboid it , fixing derivation rules is last option ..

Regards

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Atif,

I just tested FMCT for a PR with account assignment category K without any chained documents. Yes, FMIOI was updated with the new commitment item. When I went ahead to create a PO with reference to this PR, yes, system was still deriving the CI based on the FMDERIVE. Only after I switched off the 'overwrite with new value' indicator in FMDERIVE, system was using the CI from the PR.

However, I also found this has nothing to do with PR changes. Even with a brand new PR, the system behaves the same way as above described. The FM account assignment inheritance starts only from GR onwards.

Regards,

Ming

View solution in original post

6 REPLIES 6

Former Member
0 Kudos

Atif,

Try to reconstruct PR's with transaction FMN3N. I think FMCT does not update all the tables.

Regards,

Ming

0 Kudos

Hi Ming:

Issue is not in PR. We have tested PR reassignment for all material related PRs, its working fine. However PRs with account assignment category K are not showing up error although i change commitment item target field with "overwrite with new values" . System is issuing error message

Reassignment of account assignment element Commitment Item not possible

Message no. FMCF108

It says to make reassignment derivation strategy (i have defined none for it) and account assignment derivation strategy compatible.

For PO related issue my point is why is system not inheriting reassigned PR FM Account assignment when creating PO with reference to it. At PO it is taking value from FMDERIVE.

Regards

0 Kudos

Hi,

1. wrong commitment item hit in PR:- how?  system fetch account assignment as per the derivation rule you defined. If you change it manually then it wont reflect same on PO because system access derivation  again  during PO creation as in your case CC and FC relation. So make the derivation rule consistent .

Regards

Rabin

0 Kudos

Atif,

It appears that the PO is retaining the value that is derived and the new value in the PR is not being copied into the PO. Once the PO line item is created with reference to a requisition, the copy function is no longer invoked. So changes to the requisition will not flow into the PO. You can create a reassignment rule for the PO to correct the PO using FMCT. Alternatively you have to delete the PO line item and recreate it with reference to the requisition line item.

Thanks

Shyam

0 Kudos

Hi Atif,

Do your material PR's create entries in table FMIOI? If they do, please read the documentation of FMCT. The listed tables that the program updates do not include FMIOI. That is why I think you need to run FMN3N to update FMIOI after the FMCT run. Also I believe PO not inherit PR's fm account assignment may have something to do with entries in table FMIOI.

Regards,

Ming

Former Member
0 Kudos

Hi Atif,

I just tested FMCT for a PR with account assignment category K without any chained documents. Yes, FMIOI was updated with the new commitment item. When I went ahead to create a PO with reference to this PR, yes, system was still deriving the CI based on the FMDERIVE. Only after I switched off the 'overwrite with new value' indicator in FMDERIVE, system was using the CI from the PR.

However, I also found this has nothing to do with PR changes. Even with a brand new PR, the system behaves the same way as above described. The FM account assignment inheritance starts only from GR onwards.

Regards,

Ming