Skip to Content

Predecessor reference inconsistent 4500051338 00010 00000 (PORD) Message No. FICUSTOM402

Hi,

I activated Funds Management and all settings are done. But during integration tests, we faced with the below-mentioned problem.PO was created with Account assignment category "U" Unknown. In Service entry sheet true account assignments entered and posted. When we want to post invoice receipt system gives error message "Predecessor reference inconsistent 4500051338 00010 00000 (PORD) Message No. FICUSTOM402". I think system wants to reduce the committed amount in PO. But POs with Account assignment category "U" Unknown don't create FM documents. In OFUP GR/IR update is MM invoice receipt. Please tell me how can I fix this problem. We can change customer's future working procedure with POs (Select true account assignment in PO's). But I need something to do with old POs.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Feb 21 at 01:48 PM

    Hello Elvin

    Do you use Chain CCF? If you don't use it, then apply Note 2550916 - Wrong validation of reference document when chain CCF is not active

    best regards

    Mar

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 04 at 10:47 AM

    Hi,

    You should use FMCN/FMCT to complete FM assignment in the documents created before FM was activated. Even if a document doesn't generate FM transaction by itself, this assignment serves the system to determine the posting address for following documents.

    Regards,

    Eli

    Add comment
    10|10000 characters needed characters exceeded

    • GR/IR inscriptions are not impacted by settings for online or manual payment transfer. Unless, of course, you changed something is SAP-provided update profiles. Only a payment of an invoice, i.e. value type transfer to '57' could be dependent on these settings. Providing FM assignment for old documents sometimes is not required; it all depends on the settings you made for account assignment adoption. The best way to check it is through testing, of course.

      I'd suggest that you close this particular thread, as I believe, we have clarified the original question. Should you have other issue, you can open a new thread.