Skip to main content
Question

MPL VOUCHER CAN'T BE APPROVED


Forum|alt.badge.img+3

Hello, 

I have 3 MPL vouchers which can’t be approved because the CODE J posting rules are missing on M49 and M184. Is anybody know how i can fix the issue?

 

4 replies

cperdue
Hero (Partner)
Forum|alt.badge.img+14
  • Hero (Partner)
  • 439 replies
  • May 5, 2023

Start with the accounts involved.   Are the accounts actually intended to be cost/revenue elements?  If they should be CRE’s, should the code part ‘J’/Projects be ‘mandatory’?  If the Project code should be mandatory, verify the correct mapping is listed in the M49 & M184 posting controls/details.

 

 

 


Forum|alt.badge.img+6
  • Hero (Partner)
  • 40 replies
  • May 6, 2023

Hello,
MPL is a voucher transferring transactions from inventory. If it was created successfully, it means hat posting issue has not been identified at that time - usually all posting errors are identified before voucher is created. Was it recent setup change? 
Anyway, you cannot mofify MPL voucher postings - they are created automatically. All you can do is to try change account settings:

  • if project id is present in posting line together with activity sequence, you are blocked and need to call support for back-end data repair
  • If project id is present, but activity sequence is not, perhaps setting account as excluded from project follow-up will be an option (I suspect code part J containing project cost element is already set to optional or even blocked for this account).

Yathartha Karunananda
Sidekick (Employee)
Forum|alt.badge.img+6

Hi,

The reason for this error is basic data set up in posting control is missing. You have to have postings set up for M49 and M184, code part name J(which is the project cost revenue element). But after the MPL voucher is created you cannot edit it.

There are couple of workarounds to overcome the situation:
1) temporarily change the restrictions on code part demands and handle it using a manual correction voucher
2) Data Repair (Since this is in cloud environment and R&D has classified this as a user error, you have to create a ticket for consulting organization to get this resolved)

 


Yathartha Karunananda
Sidekick (Employee)
Forum|alt.badge.img+6

Hi ​@FABPO ,

The reason for this behavior is setting up a revenue type account for the account code part and not defining the posting control for Project cost/revenue element code part. Ideally, before transferring the transaction to the MPL, there should be a warning.
This has now been fixed in 23.1.23 - 23R1 SU23, 23.2.16 - 23R2 SU16, 24.1.10 - 24R1 SU10, 24.2.4 - 24R2 SU4, 25.1E.0 - 25R1 EA


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings