You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

SLA Account rules with multiple account rules where mapping set has 1st priority is not working

edited Apr 3, 2025 3:07PM in Project Management

Summary:

Account rules with multiple account rules where mapping set has 1st priority is not working in Project Costing but the same rules work in Payables

Content (please ensure you mask any confidential information):

We have the below account rule for Organization

Priority Value Type Value

1 Mapping Set Project org to organization

2 Source Project organization cost center segment

The mapping set will have only limited values with effective date and if no mapping exists rule will derive the value from the above source. We don't have any default value defined in the mapping set for this reason.

This works in AP but doesn't work in Projects even though we created similar mapping set and rule in Projects. If the rule can't any mapping in mapping set, it fails and doesn't go to source to get the value. I am wondering if anyone seen this behavior.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!