Hi,
Code part demands simply designates requirements for a successful code string. As you can see, the code part demands for an account can designate that a code part is blocked, can or mandatory. That’s all it does.
Then other rules, such as posting control are used to provide values for a given code part.
In your example your account XYZ requires the interco code part to have a value. You need to investigate what posting type is not set up correctly such that the interco can fill.
Several ways exist to do the investigation. You can look at the posting control report, search to find the posting types that use the account and compare this to the transaction being performed that caused the error.
If you're in TEST type environment, IMO the easiest way to investigate is - temporarily set the code part demands to can and allow the transaction. Then review the results and see the posting type that was used. Fix the set up for that posting type, and then after GL update, set the code part demands back to mandatory, and test again.
Best regards,
Thomas
Hi Thomas,
Thank you for your reply.
When i checked the Posting Control for GCP% Posting Types, GCP postings have been defined from GCP1 to GCP15 Except GCP 9 & GCP 10.
Also identified that the GL Account in issue has been used in the Intercompany Elimination Rules for Matching Accounts from/To.
Do you think it could be due to not defining the Posting Types GCP 9 & GCP 10?
Best Regards
Razan Ramzy