on 08-09-2010 10:24 AM
Dear Experts,
I hope somebody can help me:
I want to assign a network activity to a wbs element - but I don't want that the wbs-element is an account assignment indicator.
I first thought that I could control that by the paramter "Control key" in the networt activity - but I still get message/error above (CJ056).
In this case I want to use the network acitivty only for Scheduling not for any "Cost-Activities".
I hope somebody can help me.
kind regards
nexus
Hi,
even with Account Assignment Indicator in WBSE's you can prevent FI Postings through FI - Line Items Validations. Consult your FI CO Consultant for this. An exit should be written as a "Check" in the validation.You should have some fixed parameter in WBSE (For eg. Level of WBSE) against which the validation will check the prerequisites and throw Error.
Regards,
Arul.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
to assign a network activity to the WBS you need it to be account assigned
what is the issue if it is account assigned?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the problem is that users can assign cost's direct on the wbs element.
example:
....
Level 4 / wbs Element A
Level 5 / wbs Element B
Level 5 / wbs Element C
....
Now Every Element has a network activity assigned.
But only on the Elements B and C (Level 5 - at the lowest level in this group) should it be allowed to assigne costs (Account assignment element).
Edited by: nexus_123 on Aug 9, 2010 12:44 PM
thanks for your suggestions.
I know the possibility by using the user-status to avoid costs on the element already - but I can't define/set the user-status in a standard template.... and that makes it therefor not very usefull.
regarding the first input, I don't want to avoid costs on the wbs-elements at all - I just want to avoid them on the levels above (as I mentioned in my example).
Have you checked the flag Account assignment element (short acct) in the basic data for the WBS-elements? You probably cannot set or remove this flag if the status for the WBS-element in question does not allow it. Then you might have to go back to an earlier status, providing this is possible. If something has already been posted to this element it is not possible to go back.
I just created a new project to check if the status is the source of my problem.
But even with a new Project without any posted costs, it's not possible to remove the flag.
the error cj056 relats to the following check:
"The following assignments are checked:
network
network activity
Aufträge zum Projekt (Fertigungsauftrag, Innenauftrag, Instandhaltung)
Planauftrag"
Is it such a mandatory requirement that the flag is sent, when you assign a network acitivity to a wbs-element?
even when you use the network activity just for scheduling?
Edited by: nexus_123 on Aug 9, 2010 3:21 PM
I am just adding my option to what others have suggested it.
Since you dont want any cost posting at activity level, make the network as account assignment object not activity...and now create network and activities for Level 5 WBSE(with account assignment check box ticked)and now drag drop the respective activities to Level 4 WBSE(account assignment check box unticked)..now cost will be collected at network header..and this network header is assigned to level 5 WBSE..since level 4 WBSE is not account assignment object, user cannot post any cost to it.
thanks for your suggestions.
@virenda pal: how do you set the userstatus on only one element in a template?
In Transaction cj92 it's not possible to set the status on only one element and if I change the statusprofile for "wbs-sts." in the project definition, then all wbs-elements follow them (means, every wbs-element is blocked for costs). Or did I overlook something?
@Ahmed Rifaee: it's quite a good workaround - but I would prefer if I could manage it by using the user status.
You cannot set user status on one WBS element in CJ92
I would consider the following - what difference does it make if all the WBS have the same status - you do not want posting on WBS elements at all. For higher levels do not tick account assignment. For the level you need to connect NWA tick account assignment and let the user status do it job
Alternatively you can create a substitution exit to replace the status on the WBS where a NWA is linked or use BADI Workbreakdown_update.
User | Count |
---|---|
102 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.