on 06-12-2014 7:10 AM
Hello
We have a requirement to lock certain conditions in a contract for posting.
The workaround is to take note of such conditions in a contract and exclude the same while running the RERAPP but this is not feasible in our current scenario as billing team is different from accounting team.
Number of contracts are also huge (about 40000+). Billing team liaise with tenant and if there are any issues, would like to block the condition for posting. Accounting team will run RERAPP without this knowledge and if the lock option is activated, then this condition will not get posted.
Similarly we have an additional requirement that retroactive adjustments (follow on cash flow) should be posted separately in RERAPP. Now in this case, flow type is the only differentiating factor because due date of retro adjustment may be same as of regular cash flow item.
Please advise
Rakesh
Hi Rakesh,
The best way to restrict the posting of a condition by other team is with the authorization. Hence create different authorization roles for each condition posting.
Retro cash flow items generally will come in the follow on months with earlier month due date.
For example in May -2014 retro cash flow items will be created for Apr-14 or Mar-14 with a due date of 01.04.2014 or 01.03.2014( This can be done in Conditions and flows -> due date correction rule).
Hence users can manage postings with respect to cash flow due date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Sharma
Please refer to my last reply for another case as below link ;
http://scn.sap.com/thread/3554879
1. Configure following 'Business Transaction Control' on the 'User Status'.
(Go to RECACUST > General Settings for Master Data and Contract > User Status and Activity Control)
Business Transaction Allowed Warning Forbid No Action
RE: Execute periodic postings O
RE: Cancel periodic postings O
FI: Postings O
Thank you.
Regards,
Jeong, yeong-chul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Rakesh Sharma.
If you just only want to prevent/restrict certain conditions of contract posting activity
(RERAPP),you simply consider about this method as below ;
1) You can define the RE Authorization Object for the restrict activity of certain
condition in the Accounting team role.
- Authorization Object : F_RECD_CN
- Activity : 02 (Change)
- Condition Type : Except for the certain conditions.
but this method can not be suitable, when account team try to run RERAPP
with check the "Do Not Update Conditions" option.
So, you can consider the easiest way by applying the "Enhancements"
2) Apply the Enhancements for Periodic Posting.
- Enhancement Spot : BADI_RE_RA_CA
- BADI : BADI_RERA_POSTING_PARAM
(Periodic Posting: Restrict Selection of Cash Flow Records)
- Method : SUPPRESS_CF_ITEM
- Example : you can defined your own customer-specific parameters such as
"Check the Certain Condition & User role/department for suppressing"
but how about this..,when you design the lease account management process,
it seem better to rebuild the contract creation and contract posting process bwtween
contract management team and account team ahead of the technical processing.
Regards,
Jeong, Yeong-Chul
Well, I would like to reiterate my issue as your solution seems like more inclined towards the assumption that a user should not be able to post say x condition.
My business case is that say at times, 10 customers have disputed maintenance condition. I should hv d option in contract to block these conditions for posting. Once the dispute is over, I should be able to unblock and post it in next or ad-hoc run.
Now the issue is that person blocking and running RERAPP are two different. Had it been a single person, he could have easily excluded the condition from RERAPP run for these contracts.
Why do you make it so complicated with block and unblock? When the condition in date X should not be posted so why is it inserted then? I mean, at date Y the billing team had to go to the contract again in both cases.
When you want to see the condition value for informational reasons already at date X, then I would insert the condition as statistical condition. So you can be for sure that it will not be posted. Of course you canot see any cashflow in the contract then, but in REISCDCF or in some custom programs you can 😉
Regards
Michael
Hello
Where is complication. It is business requirement as simple. Take following case:
Maintenance condition added in contract with valid from date as 01.01.2014 and end date 31.12.2017 and frequency monthly posting.
Say customer x, y, z reported that maintenance is no up to the mark. Do not bill unless you resolve the issues. Maintenance deptt would like to block these conditions (cash flows) from getting posting in next posting run.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.