Error when MIGO: Commitment item XXXX//1009000000/ cannot be posted to

[Former Member]

Hi all,

Please help me.

When i post MIGO with movement type 101 to post inventory, system error with message: Commitment item PTMN//1009000000/ cannot be posted to.

Message no. F6203

wheter i assigned (on fmderiver) commitment item fin.transc/commt.cat 30/3 or 50/3 to gl account inventory, the error message appear the same.

I have two same hirarchy commitment item. Superior is 1009000000 (50/3) with lower commitem 1009001800, another superior commitment item 1009000001 (30/3) with lower commitmen item 1009001000 and 1009003000.

Both 1009003000 and 1009001800 error message always refer to XXXX//1009000000/, btw i used former budgeting.

System can post when migo process movement type 103 and result is good movement without accounting document. 101 and 105 can not because they trigger accounting document.

Any advise will be appreciate.

regards,

Dewi

[former_member184992]

Hi Dewi,

Please kindly check the possible solutions to your problem:

1) Do you have note 1149269 applied in your system? If not, kindly apply it in one test system and retest your issue. It can resolve it.

2) If you are using former budgeting, please kindly check in your budget structure (TC F9ML) if you have accounts assignments that are budgetable or postable. You must have.

If nothing helps, please kindly let me know if you have some configuration under the following menu:

SPRO -> PSM -> Funds Management Government -> Master Data -> Account

Assignment Elements -> Year-Dependent Master Data -> Display Activation

Status of Year-Dependent Master Data.

I hope it helps you

Kind Regards,

Vanessa Barth.

[Former Member]

Hi Vanessa,

Big appreciate for your attention,

1. Looks like we have not implemented this note 1149269 (SAP_APPL rel.600 package level 13). Wheter our component version is APPL rel.600 package level 12.

Even the subject of the note looks like not relevant with my error message, i propose to basis to implement this, beside we plan to use contract as commitment plan.

2. I've already create budget structure with budget structure template. With budget object and posting object. Successful tested until availability control with FI posting, PO, travel but not yet when integrate with GR (warehouse etc).

3. I work with independent-year master data. Once i create budget structure, it will apply forgood.

I will report the impact of implemented note. Any comment regarding this?

regards,

Dewi

[Former Member]

Hi vanessa,

I already implemented the notes. Unfortunately, it did not work.

The error happen for MIGO reference by purchase stock.

MIGO reference by PO with account assignment is ok (ie cost centre)

regards,

dewi

[CesarCarreno]

Dewi,

I´m not sure about your scenario, but if you have ERP500 check note Note 700485 - PSM: Convert customizing for warehouse funds ctr scenarios.

Also you can check notes

788835 - FM account assignment incorrectly changed during GR/IR

859580 - GR/IR FM account assignment not inherited from PO

923672 - FM account assignment not inherited from PO (note 859580)

Hope this helps you.

Cesar

[Former Member]

Hi,

Actually, when you do MIGO, the system bypasses FMDERIVE and inherits account assignment from PO. I believe, the commitment item in your PO is 1009000000. Please check whether this is true. Also check whether 1009000000 is a postable CI.

Regards,

Ming

[Former Member]

Hi all,

Thanks for your reference notes and discussion.

First, the commitment item used by PO is 1009003000, and when MIGO, commitment item derive from PO correctly. But system said on error which commitment item is 1009000000. Offcourse 1009000000 can not be post because it is not directly posted. 1009000000 is upperlevel of commitment item 1009001800.

How come system said 1009000000 (when try to post) which commitment item in MIGO already is 1009003000 ?

Second, through the testing i found the case happen on MIGO based on PO-stock with material price V (moving average price). I tested with material price S (standard), MIGO post successfully. Post with right funds centre, commitment item and post as Funds Mgt document.

I think this might a kind of bug ....

regards,

Dewi

[Former Member]

Hi all,

I've been created customer message to SAP, and the development create note 1312483 to resolve this error.

regards,

Dewi