on ‎2015 Jun 17 8:18 AM
Hello Team,
Its one of the requirement is that " If my assets are not matching with Liabilities the user can not submit the data:" If he try to submit the wrong data,
can we restrict at work status level Submission restriction?
Please advise me.
Regards,
Madhu
Request clarification before answering.
Hi Madhu,
Your requirements are not related to work status. Please read about controls.
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vadim,
Thanks for your quick suggestion on this.
Yes, I suggested the same to customer. They are raising a question on, If user send any data should system accept? we need to check point..
One of the entities use will submit the data, while submitting some users will input wrong data. In that point of time they need rejection at work status level.
I suggest controls, how ever before submitting the data user has to verify or run the control, once its fine he can submit the data for approval.
Regards,
Madhu
"One of the entities use will submit the data, while submitting some users will input wrong data. In that point of time they need rejection at work status level." - once again, work status has no relation to data validation!
And in general BPC is not a transactional system with balance control... You can use journal data entry but it's not very convenient...
Vadim
Hi Madhu,
If you check data as it is entered and reject data that is not complete/correct at that point you will cause problems for the users entering the data. Imagine you enter data for an entity and want to take a quick brake from doing so to get a drink. The sensible thing is to save the data before you leave. If saving would not be allowed unless the data is correct, the user could not save at this point. Restricting the ability to save at this point is not practical.
In BPC users are allowed to save incomplete or incorrect data but need to run the controls before they can change the work status to submitted. This way, they can save as and when required but are forced to check the data (run the controls) before changing the work status.
BR,
Arnold
If the user is sending 2 values that has to be checked for balance - then UJ_VALIDATION will be triggered for each value individually - with unbalanced result!
With write back - the badi will be triggered only once for the whole scope - for 2 values in this case. And it will be possible to check balance for the whole send data scope.
Hope it's clear.
Vadim
| User | Count |
|---|---|
| 15 | |
| 11 | |
| 10 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 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.