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

Similar Messages

  • 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 "

  • 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

  • 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

  • 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.

  • 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

  • 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

  • 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

  • You have not maintained a rule for the fiscal year variant

    1) I have Fiscal Year Variant in the Cube ( it got added along with fiscal year ) but there is no Fiscal year variant in the datasource & when I dont map it Transformation activation prompts error " You have not maintained a rule for the fiscal year variant ".
    Can I just delete Fiscal year variant from the cube..does it matter?
    2) Fiscal year & Posting Period can be populated from Fiscal Period, is the vice versa possible..? Does the sytem will take care of the conversion..?

    1. no, you should not delete and you cannot delete fiscal year variant from cube, it's required by fiscal year/ period (compound infoobject), you should add it in your datasource, or you can map with a constant value e.g K4
    2. yes, fiscal period can be populated by posting period
    some info on time characteristic relationtionship
    http://help.sap.com/saphelp_nw70/helpdata/en/44/be8b631c743959e10000000a1553f6/frameset.htm
    hope this helps.

  • 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

  • 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

  • Doubt about the settlement rule of the Production ORder

    The only default distribution rule allowed for a PP order is PP1 or PP2.  We would need to change that to allow settlement to multiple receivers as a default. If that is the case, we may want to look into a user exit to update the settlement rule during production order creation instead so that the G/L account is correct from the beginning.
    Currently when we create the production order, the settlement rule will default the below, I am not sure if a user exit is able to maintain the Source as 200 (Materials)?
    If yes, we can then add the second rule for Source 100 (Labor and Mfg) via the user exit as well.
    In this case, SAP will not prompt us error of settlement with 200%, as they are from difference Sources.
    now anybody can explain me about the User EXit we have to correct this

    any help on this.. please its very urgent
    thanks in advance

  • Maintain settlement rules for order category 30(Maintenance order).

    Hi Gurus,
    Can we maintain two settlement rules for an order without distribution rule?
    Eample:-  In an order there are three  different costs i.e. material cost,external labour cost and internal labour cost.We want to settle the material cost and external labour cost to Profitability segment and the internal cost to a particular GL account directly.
    Note: No distribution rule is required,because all the cost should settle directly to correspoanding heads i.e. PSG or GL.We don't want to assign  the GL# again and again for different orders in the corresponding order's  settlement rule.
    Require your valuable inputs to proceed.
    Best Regards,
    Ramakanta

    Hi Govardhan,
    If you are working in ECS, the Shopping cart will not create any follow on document in backend R/3.
    I think your Product category is 30, thats why the error says Manual reservation for order category 30 is not allowed.
    Where did you get the maintenance order? Generally maintenance order is created in the backend R/3 (Plant Maintenance) and a P.R will get generated against that order.
    Using PDP (Plan driven procurement) you can transfer that P.R to SRM and can carry out sourcing and can complete the procurement cycle.
    Can you please tell me what is your exact business requirement?
    Hope this will make you more clear.
    Clarifications are welcome.
    Award points for helpful answers.
    Rgds,
    Teja

  • Maintain settlement rules in a PM order

    Hi!
    I would like to find an easy way to automatically fill the settlement rule in an existing PM order. If it is possible I would like NOT to use BDC (Batch input). A function element or maybe a BAPI would be the best solution.
    If anyone knows a way to it, please share it with me..
    Thank you
    Tamá

    Answered...

Maybe you are looking for