Error: Maintain settlement rule of the sender for a higher level WBS

Hi,
I dont want to maintain the settlement rule for a higher level WBS. How can i configure this in such a way that i dont get the following error:" Maintain settlement rule of the sender" while doing CJ88. Maintaing a separate Settlement profile for a higher level WBS is an option but we are looking if something else could be done The problem is that there are no actuals booked against, say, level 2 WBS but when i execute CJ88, i get the aforesaid error. How can i ensure that only the lowest level WBS ask for the settlement rule and not the levels above it. I have already removed the Investment profile from the higher level WBS but still getting the same error.
Regards,
DPil

Hi,
It is a type Capex WBS and Biling element is not checked. In fact i get a warning while doing the settlement: WBS is neither a billing element nor an account assignment element.
Diagnosis
WBS element is not indicated as either an account assignment element or as a billing element in the master record.
System Response
The WBS element cannot be assigned to an account.
Procedure
Correct your entries or add the missing indicator to the master record for the WBS element.
But this is just a warning. On pressing enter i get the error :Maintain settlement rule of the sender "

Similar Messages

Maintain settlement rule of the sender

Dear All,
Hi, I am Settling the all orders in co88 t.code, i run test run mode for all orders.At the time of running i am getting the below error:
Maintain the settlement rule of the sender
Message no. KD205
Diagnosis
Either the settlement rule for the sender does not exist, or it is incomplete.
The settlement rule must contain settlement parameters and at least one valid distribution rule. A distribution rule is valid for a settlement run if
The settlement period is in the validity interval for the rule, and - if a settlement type was specified during settlement -
The settlement type corresponds to the rule for the specified settlement type.
Settlement type FUL -> The system selects all rules with the FUL and PER settlement types.
Settlement type PER -> The system selects all rules with the PER settlement type.
The settlement share is set for the rule (percentage, equivalence number).
Procedure
The settlement rule belongs to the sender master data, where you can maintain it.
Internal order
Proceed
CO Production order
Proceed
Project
Proceed
Cost object
Proceed
Network
Proceed
QM Order
Proceed
PM Order
Proceed
Production order
Proceed
Process order
Proceed
Sales order
Any body please help, where i can check the settings, I checked my settlement profile and allocation structure also.it's working properly, but i am getting the error at the time of order settlement in co88.
Thanks & Regards
Reddy

Hi
Each Order Type is assigned to the Settlement profile and in settlement profile the Settlemet receiver is maintained.
Genereal Critaria
Sales Order Settled               to Production order.
Production Order Settled       to Material
Internal order settled              to Cost center or GL
Please refer following T code.
OKO7     Creat settlement profile
Check for Periof End Activity in Costing.
Product Cost by Sales Order
Product Cost by Order
Internal Orders
Period-End Closing > Settlement > Create Settlement Profile

Maintain the settlement rule of the sender error

Dear Friends,
Using T.code Ko88, The following data has been entered.
Order :100010R.
Settlement period - 11
processing type - automatic
Selected the Test run.
When executed, the following error is displayed " Maintain the settlement rule of the sender" Message No: Message no. KD205
Settlement rule was selected and the settlement rule was displayed.
In the distribution rules, in the category FXA and GL are defined and in Settlement, it is Full and from and to date is 10,2010.
Please suggest how to solve the error?
Regards
Sridhar

Hi
Maintain only the FROM DATE... Remove the TO DATE as 10.2010 (Extend the TO DATE)
OR
Create a new settlement rule which is valid in the Period of Execution of settlement
Br, Ajay M

How to restrict from creating the Network for 1st & 2nd level WBS

Hi All,
In our project structure we have up to 5 levels of WBS, In some cases we have creates 3 level also . Now we want to restrict creates Network for first two level WBS , actually we want to restrict user to Create PR for those WBS so if we restrict them from creation of Network for 1st & 2nd level then they not able to create PR for same .
Thanks,
Virendra

Hi Virendra,
I can suggest you other way round solution.
If you are sure that those two WBS will not take any actual or commitment cost, then its better to NOT to mark those WBS elements as Account Assignment Element. I mean, if you do not set the indicator of Acct. Assignment Element (Untick Acct Assignment Element) on those WBS, then user will not be able to create Networks on those WBS Elements. Try this on your development or quality client and let me know if it works.
If it works, then you just need to disabled the Acct. Assignment Element indicator for those two WBS element and you can achieve that through substitution and field selection of WBS as well.
OR
Just look at OPSG settings at tab component. Just look if that can solve your purpose because your requirement is to stop PR from those WBS element. (I am just wondering if you can stop user from creating/change material components from those WBS-Networks)
OR
Go for User Status and set it to on those WBS Elements. Object Types will be Networks and Network Header.
OR
Try to achieve a validation or substitution where in you can mark Res./Pur. Req as 1 (Never) only for those two WBS elements. In this way user cannot create PR on those two WBS elements.
Regards,
Amit

KO8G-sudden surge of error mess(Maintain the settlement rule of the sender)

hi!
we encountered a lot of error message(Maintain the settlement rule), more than 4k, after we run KO8G, this is the first time happened to us. when we checked the PM orders from the error message, most of it came from previous periods even previous years, which are already closed. we can understand if there are posting for the said order for the period, but there is none. why those closed orders with no postings, still read by the settlement? were having a diffuclty of checking it one by one, we only expect less than 100. we hope you can help us.
thanks in advance
vince

Dear,
As found...
Maintain only the FROM DATE... Remove the TO DATE as 10.2010 (Extend the TO DATE)
OR
Create a new settlement rule which is valid in the Period of Execution of settlement
Regards,
Syed Hussain.

Returning the macbook for a higher level macbook?!?!??!

Hi all,
I just got my macbook 13 aluminum (2.0 GHz) on 14th April 2009 which was supposed to be delivered to me on 7th April, but because my office was closed so I got my macbook on 14th Arpil 2009. I would like to ask if I can return the current one and get a higher level one which is macbook 13 aluminum (2.4 GHz), as I found that the backlight keyboard is great and I want my macbook with faster performance. In fact, I returned my macbook to Apple before because there was a scratch on the keyboard, and Apple gave me a new macbook 13 aluminum which I am currently using now. So because I got my macbook on 14th instead of 7th because of the delivery problem, base on the 15 days policy, should the date starts on 7th or 14th? And am I suppose to return it and get a higher level one, i am willing to pay more for that.
Thanks!

You'll need to contact Apple on that. There are a few ways they can handle it. First of all, they usually consider your original purchase date for returns. If you have had yours replaced, the replacement date is not usually considered the original purchase date... so you're likely past your 14 day return period. If they make an exception, as you know, you typically have 14 days to make a return... that return period should commence on the date you accept delivery of the product. Provided you have documentation to show when the product was delivered, they may commence the 14 day period from that time. There is also generally a 10% restocking fee for returned products. The only way to know for sure is to contact Apple. This is just a user-to-user forum and Apple will not respond directly to comments posted here.

Maintain settlement rule - parameter

Dear all ,
I Create new maintenance order type in system and creat a manual order through iw31 . but when we want realease the order system open one window name ''Maintain settlement rule - parameter''and asking for settelement profile.
please help me where i can maintain settlement rule in SPRO for system autometic settlement at the time of realease.
Raghav

Hi RS,
Go to -" spro>>>>>PM & CS>>>>>>>>Maintenance and service processing>>>>>>>Maintenance and service orders>>>>>Functions and settings for order types>>>>>>Settlement rule: Define time and creation of distribution rule
Execute
then
put "mandatory for release" and main order will be a settlement receiver" in settlement rule time and Distribution rule sub order field with corresponding to your order type.
After completing this configuration your settlement rule will automatically create for order
Thanks & Regards,
Rahul Pawar

Cannot Maintain settlement rule for the activity

Dear All,
I tried to maintain settlement rule in activity under WBS. But it shows message :
You cannot maintain the settlement rule for the activity
Message no. CN006
Diagnosis
The network has header account assignment. You can only maintain settlement rules for the network header.
System Response
Processing stopped.
Procedure
Maintain the settlement rule for the network header.
Please help.
Cheers,
Nies

Hi,
I already tried the config OPUV (network type Parameters) but it shows the activity account assignment already ticket.
If i go to network header and go to settlement rule the warning message shows :
Network has activity account assignment
Message no. CN057
Diagnosis
Costs can only be written to activities for the network whose key you have entered.
System Response
Processing stopped.
Procedure
1. Check whether you have entered the correct key for the network. Change it if necessary.
2. Maintain the key for the network to which you want the costs to be written.
In addition, if i tick the activity under the network header : it shows
You cannot maintain the settlement rule for the activity
Message no. CN006
Diagnosis
The network has header account assignment. You can only maintain settlement rules for the network header.
System Response
Processing stopped.
Procedure
Maintain the settlement rule for the network header.
Cheers,
Nies
Edited by: Nies on Nov 6, 2009 3:26 AM

Problem in maintaining the settlement rule in the maintenance order

Dear Friends,
I have a problem ,When I am trying to maintain the settlement rule in the maintenance order ,I am getting information like below
Decentralized system -> note settlement rule is not distributed
Message no. /ISDFPS/PM124
Diagnosis
You navigated to the settlement rule.
System Response
The system informs you that a settlement rule can be created but that it will not be distributed to the target system. Settlement is carried out in the target system, where the order is usually settled to the WBS element of the operation.
Can anyone throw some light on how this is happeing and remedy?
Appreciating your early response

Hello
Please check
TC --> KSR2_ORC
Please maintain the Strategy Sequences for Automatic Generation of Settlement Rule.
You define a strategy sequence for automatic generation of settlement rules for internal orders.
Regards,
Rakesh
Edited by: RAKESH ASHOK MANE on Sep 3, 2010 12:37 PM

Getting 'Maintain Settlement Rule' Error while GI

Hello Friends,
While posting GI through MB31, I am getting an error of settlement rule, I was wondering what the error of kind and how to resolve it.... what are the entries need to make ?
Regards,
Rahul

Hi,
Actually you are doing GR through MB31, go to order change CO02 and in the menu to to Header tab and click Settlement rule from the menu. In that screen whether settlement rule is assigned or not, if it not assigned assign a receiver (category) and percentage and save.
(In this situation, you can choose catrgory CTR and give any cost center number in the order.)
(For information, this settlement is defaulted from OKO7 transaction code, check with your CO consultant about the entries
then try to do the MB31.
Thanks,
JK

Maintain settlement Rule for CJ20N

Hi Experts,
How can i maintain settlement rule for sales order and item in cj20n. Is there any t.code or BAPI available..?, Please help me.
Thanks.

Hi ,
u can use these FMs K_SETTLEMENT_RULES_UPDATE, if u want to know what to pass , put a break point in this FM ,and try to create a settlement rule ? then u will come to know .
K_SETTLEMENT_RULE_GET
K_SETTLEMENT_RULE_REFRESH
K_SETTLEMENT_RULE_SAVE
K_SRULE_CREATE
K_SRULE_CREATE_WITH_SL
K_SRULE_GET_SLIST
Regards
Prabhu

VA02 - maintain settlement rules

Hi folks,
I am trying to maintain a settlement rule within the Sales Order without the user going to the Item Level.
I want to inherit the WBS element from the Header VBAK and on the save of the document automatically create the settlement rule.
I have tried K_SETTLEMENT_RULES* functions and cant seem to get them to work.
Anyone got any ideas or any advice on this ?
Regards
Gary

I managed to work this one out myself, but just in case someone else has to do it. here is how I acheived it.
Firstly set up all fields on COBRA and COBRB, then call FM
             CALL FUNCTION 'K_SETTLEMENT_RULE_FILL'
               TABLES
                 I_COBRA       = lt_cobra
                 I_COBRB       = lt_cobrb.
Next
           For some reason the internal system ALWAYS sets the table
           up as the update status, this causes problems on creation,
           so we have to change to Insert status.
             Assign (c_GT_cobrb) to <fs_cobrb>.
             if <fs_cobrb> is assigned.
               LT_COBRB_BT[] = <fs_cobrb>.
               loop at lt_cobrb_bt.
             Somehow the previous records are being kept in so have to
             delete them or else prog falls over.
               if lt_cobrb_bt-objnr <> lv_objnr.
                 delete lt_cobrb_bt.
               endif.
               check to see if record exists.
                 select count(*)
                 from cobrb
                 where objnr = lt_cobrb_bt-objnr
                 and   bureg = lt_cobrb_bt-bureg
                 and   lfdnr = lt_cobrb_bt-lfdnr.
                 if sy-subrc <> 0.
                 Set the flag to be insert instead of U
                   lt_cobrb_bt-uflag = 'I'.
                   modify lt_cobrb_bt.
                 else.
                 If settlement exists then exit.
                   lv_settl_exist = 1.
                   exit.
                 endif.
               endloop.
              If settlement exists then exit.
                if lv_settl_exist = 1.
                  exit.
                endif.
                <fs_cobrb> = LT_COBRB_BT[] .
             endif.
           For some rreason the internal system ALWAYS sets the table
           up as the update status, this causes problems on creation,
           so we have to change to Insert status.
             Assign (c_GT_cobra) to <fs_cobra>.
             if <fs_cobra> is assigned.
               LT_COBRa_BT[] = <fs_cobra>.
               loop at lt_cobra_bt.
             Somehow the previous records are being kept in so have to
             delete them or else prog falls over.
               if lt_cobra_bt-objnr <> lv_objnr.
                 delete lt_cobra_bt.
               endif.
               check to see if record exists.
                 select count(*)
                 from cobra
                 where objnr = lt_cobra_bt-objnr.
                 if sy-subrc <> 0.
                 Set the flag to be insert instead of U
                   lt_cobra_bt-uflag = 'I'.
                   modify lt_cobra_bt.
                 else.
                 If settlement exists then exit.
                   lv_settl_exist = 1.
                   exit.
                 endif.
               If settlement exists then exit.
                 if lv_settl_exist = 1.
                   exit.
                 endif.
               endloop.
                <fs_cobra> = LT_COBRa_BT[] .
             endif.
Then when the tables have had their update status amended then call FM
             CALL FUNCTION 'K_SETTLEMENT_RULE_SAVE'
               EXPORTING
               DIALOG                  = ' '
                 OBJNR                   = lv_objnr
                I_STATUS_UPDATE         = ' '
              EXCEPTIONS
                NO_RULE_FOR_OBJNR       = 1
                OTHERS                  = 2.

Maintain Settlement Rule

Hi All
I would like to maintain more than ten line items in maintain settlement rule screen for distribution. Currently system allows me to enter only ten distribution line items. Pleease let know to increase the way. Thanks in advance.

hi
in OKO7 for your settlement profile make the entries in the Max.no of dis rls and check
regards
thyagarajan

My inbox used to show the sender for each message and now it does not...how do I get it back to where it was?

My inbox used to show the sender for each message and now it does not...how do I get it back to where it was?

Right click the heading at the top of the message list and select From from the list of options.

Warning: The sender for the SL-3100 Wireless Headphones is highly susceptible to static shock

I have a jacket that is bad for static, and one day I was wearing it while using my SL-3100 headphones, and the jacket shocked my mp3 player. The mp3 player was ok, but the sender for the headphones won't even turn on anymore.
Message Edited by DuctTapeNinja on 01-23-200807:15 AM

I have a jacket that is bad for static, and one day I was wearing it while using my SL-3100 headphones, and the jacket shocked my mp3 player. The mp3 player was ok, but the sender for the headphones won't even turn on anymore.
Message Edited by DuctTapeNinja on 01-23-200807:15 AM

Error: Maintain settlement rule of the sender for a higher level WBS

Similar Messages

Maybe you are looking for