Automatic Allocation of Settlement Rule on WBS

Hello,
I am facing issues with automatic population of settlement rule in Expense Projects. I have a scenario where I need to settlement to Cost Centres,G/L etc. Now I have maintained a settlement strategy for WBS in configuration. However in that config the account assignment option is only for PSG, responsible CC and requesting CC.So I have left it blank and just assigned the settlement profile.
Is there any way to automatically fill the settlement rule. What will be the ideal way to deal with this situation? Manual or just maintain default receiver as responsible CC.
Please let me know if anybody has experience in above.
Thanks

You'll need to use Business addin for automatically generating settlement rules for expense projects with receiver as req cost center.
Check the documentation at:
SPRO=>PS=>Cost=>Automatic and Periodic Allocations=>Settlement=>Settlement Rule for Work Breakdown Structure Element=>Business Add-In: Generation of WBS Element Settlement Rule (CJB1/CJB2)

Similar Messages

  • Automatic creation of  settlement rule while creating sales order

    Hi Friends,
    Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
    thanks
    bobby

    Hi,
    Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
    and write the form routine in Program named 'ZRGGBS000'
    The code is below ,
    *&      Form  U902
       Automatic Generation of Settlement Rule For WBS and Company 4180
    FORM u902.
    Exit For Automatic Settlement Rule Creation for WBS Billing elements
      IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
        DATA   lv_proj TYPE ps_pspid.
        lv_proj = proj-pspid.
        EXPORT lv_proj TO MEMORY ID 'PSPID'.
    Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
        SUBMIT ygps_cjb1exec AND RETURN.
      ENDIF.
    ENDFORM.                                                    "u902
    *& Program  YGPS_CJB1EXEC
    PROGRAM  ygps_cjb1exec.
       Automatic Generation of Settlement Rule For WBS and Company 4180
    Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
    DATA: bdcdata_wa  TYPE bdcdata,
          bdcdata_tab TYPE TABLE OF bdcdata,
          itab TYPE TABLE OF bdcmsgcoll.
    DATA :lv_currm LIKE bkpf-monat,
          lv_curry LIKE bkpf-gjahr,
          lv_prevm LIKE bkpf-monat,
          lv_prevy LIKE bkpf-gjahr,
          lv_proj TYPE ps_pspid,
          lv_mode TYPE c,
          lv_time TYPE sy-uzeit.
    DATA :g_datfm            LIKE usr01-datfm,
          g_dd(2)            TYPE c,                         " Day
          g_mm(2)            TYPE c,                         " Month
          g_yyyy(4)          TYPE c,                         " Year
          g_sydatum(10)      TYPE c.
    IMPORT lv_proj FROM MEMORY ID 'PSPID'.
    lv_mode = 'N'.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLKAZB'.
    bdcdata_wa-dynpro   = '1000'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_CURSOR'.
    bdcdata_wa-fval = 'PRZB-VARIANT'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'PRZB-VARIANT'.
    bdcdata_wa-fval = 'ZGPS0001'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CALL FUNCTION 'GET_CURRENT_YEAR'
      EXPORTING
        bukrs = '4180'
      IMPORTING
        currm = lv_currm
        curry = lv_curry
        prevm = lv_prevm
        prevy = lv_prevy.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-FROM'.
    bdcdata_wa-fval = lv_currm.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-GJAHR'.
    bdcdata_wa-fval = lv_curry.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=VARC'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'RKPSEL00'.
    bdcdata_wa-dynpro   = '1000'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_CURSOR'.
    bdcdata_wa-fval = 'CN_PROJN-LOW'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_PROJN-LOW'.
    bdcdata_wa-fval = lv_proj.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_NETNR-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'CN_MATNR-LOW'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '/00'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=SAVE'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=VBAC'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLSPO1'.
    bdcdata_wa-dynpro   = '0100'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=YES'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLKAZB'.
    bdcdata_wa-dynpro   = '1000'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-BATCH'.
    bdcdata_wa-fval = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'RKAUF-TEST'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=RUN'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLKABA'.
    bdcdata_wa-dynpro   = '0210'.
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-JNAME'.
    bdcdata_wa-fval = 'CJB1_EXEC'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_SUBSCR'.
    bdcdata_wa-fval = 'SAPLKABA'.
    APPEND bdcdata_wa TO bdcdata_tab.
    Extract the date format from the user settings
    PERFORM f_get_dateformat CHANGING g_datfm.
    Changing the current date format to User Profile Date Settings
    PERFORM f_format_date USING   g_datfm
                                  sy-datum+4(2)
                                  sy-datum+6(2)
                                  sy-datum+0(4)
                         CHANGING g_sydatum.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-STDAY'.
    bdcdata_wa-fval = g_sydatum.
    APPEND bdcdata_wa TO bdcdata_tab.
    lv_time = sy-uzeit  + 30.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-STTME'.
    bdcdata_wa-fval = lv_time.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'KABA01-PRIKZ'.
    bdcdata_wa-fval = space.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.
    bdcdata_wa-fnam = 'BDC_OKCODE'.
    bdcdata_wa-fval = '=TAKE'.
    APPEND bdcdata_wa TO bdcdata_tab.
    Calling Transaction 'CJB1' for creating settlement rule
    CALL TRANSACTION 'CJB1'  USING bdcdata_tab MODE lv_mode .
    IF sy-subrc = 0.
    ENDIF.
    *&      Form  F_GET_DATEFORMAT
          This subroutine returns the date format in the user setttigs
         <--P_G_DATFM  Date Format
    FORM f_get_dateformat CHANGING p_g_datfm.                   "#EC *
      SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
      WHERE bname = sy-uname.
    ENDFORM.                    " F_GET_DATEFORMAT
    *&      Form  F_FORMAT_DATE
          This subroutine returns the date as per the user settings
         -->P_G_DATFM  Date Format
         -->P_G_MM  Month
         -->P_G_DD  Day
         -->P_G_YYYY  Year
         <--P_G_DATE  Date
    FORM f_format_date USING    p_g_datfm
                                p_g_mm
                                p_g_dd
                                p_g_yyyy
                       CHANGING p_g_date.                       "#EC *
      CONSTANTS: c_dot VALUE '.',
                 c_slash VALUE '/',
                 c_dash VALUE '-',
                 c_1 VALUE '1',
                 c_2 VALUE '2',
                 c_3 VALUE '3',
                 c_4 VALUE '4',
                 c_5 VALUE '5',
                 c_6 VALUE '6'.
      DATA: l_day(2),
            l_month(2).
      l_day = p_g_dd.
      l_month = p_g_mm.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          input  = l_month
        IMPORTING
          output = l_month.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          input  = l_day
        IMPORTING
          output = l_day.
      CASE p_g_datfm.
        WHEN c_1.
          CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
              SEPARATED BY c_dot.
        WHEN c_2.
          CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
           SEPARATED BY c_slash.
        WHEN c_3.
          CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
              SEPARATED BY c_dash.
        WHEN c_4.
          CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
              SEPARATED BY c_dot.
        WHEN c_5.
          CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
              SEPARATED BY c_slash.
        WHEN c_6.
          CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
              SEPARATED BY c_dash.
      ENDCASE.
    ENDFORM.                    " F_FORMAT_DATE
    thanks
    bobby

  • Automatic Creation of Settlement Rule for Maintenance Order

    Hi,
    While doing TECO for Maintenance Order, its asking for Settlement Rule. IF I click settlement rule, message is coming as Maintain Settlement Profile with options like With Default, Without Default & Cancel.
    I have maintained the Cost center in Equipment Master. Also I maintained Cost Center as Default Settlement receiver.
    Also I have gone through setting in Automatic Creation of Settlement Rule under Controlling Category.
    But I couldnt understand that. Can you please tell what are the steps to be done?
    Regards,
    Maheswaran.

    Hi,
    Please check the indicatorsin Actual cost/cost sales  and Valid recevivers in settlement profile.
    If for cost center : 1 settlement optional is maintained in valid recevivers and also for order
    and in actual cost/ cost sales: indicator to be settled in full is selected.
    Also check Allocation structure too if you have assigned the valid allocation structure.
    **check if you have assigned the valid settlement profile to order types.
    *****Most important after doing all these settings you need to create new order. for same order you will not get the automatic settlement rule
    Hope this helps.
    Regards,
    PMAddi

  • Creation of settlement rules for WBS element

    Hi,
    Iam having problem when creating the settlement rules for WBS elements. The business goes like this.
    We have XI interface which creates the Idocs and an inbound program(customized) to process the Idocs. When the Inbound program is run the WBS elements are created and settlement rules are created for the WBS elements. The inbound program is run automatically thru batch job.
    First time when the Idocs are processed about 95% of the WBS elements have settlement rules created and for other 5% settlement rules are not created. The Idoc is in status 64. I tried reprocessing the Idoc and then the settlement rules are getting created succussfully. The problem is Iam not able to find why the Inbound program is not processing succusfully when its run first time but works when reprocessed.
    I appreciate if anyone can send their views.
    Best Regards
    SK

    Hi!
    You might set the processing to check not only once the relevant IDocs, but more times...
    Check out these programs, and set them into a batch job periodically...
    RBDMANI2
    RBDAPP01
    Regards
    Tamá

  • Automatic generation of settlement rules

    Hi
    I want the system automatically create a settlement rule to to settle costs from Plant Maintenance orders directly to assets but when you look at the strategies available, there is nothing for Sender type ORC (Internal orders). Even under sender type ORI (maintenance orders), there is no option available. Does anyone know of a way I can accomplish this?
    Thanks

    Check the settlement profile/allocation structure that is assigned to your order type. You may want to explore creating a new profile and/or allocation structure that will allow settlement to fixed assets.
    SPRO->Plant Maintenance and Customer Service->Maintenance and Service Processing->Basic Settings->General Order Settlement
    From here, you can maintain settlement profiles and allocation structures. Depending on your situation, you may need to assign your specific order type to default to the new profile/structure.

  • CO: IO automatic Creation of settlement rule

    Hello everyone,
    We created a customer field in internal order (ZWBS field).
    Now, I customized all transactions:
    1. By T-code KSR4 I created Strategy 'C25'.
    2. I created Strategy Seq. called 'ZC25' by T-Code 'KSR2_ORC'.
    3. I' have Assigned the strategy Seq. to the order type by T-code 'KSR2_ORC'.
    When I create and internal order and go into Settlement rule I can see the two lines (FUL & PER) exactly like I've customized, but when I'm saving the order, the settlement rules are not save with the order.
    Is anyone met with a problem like that?
    I'll be gratefull for your help.
    Thanks,
    Lior

    Hi Lior,
    Is this the same with CO: Automatic creation of Settlement rule - settlement rule not saved?
    Best Regards,
    Owen

  • CO: Automatic creation of Settlement rule - settlement rule not saved

    Hello,
    First, We have a customer field in our internal order called 'ZWBS'.
    also, I have  customized automatic Creation of settlement rule for internal order by:
    1. T-code KSR4 - I have created Strategy called 'C25'.
    2. I created Strategy Sequences for Automatic Generation of Settlement Rule called 'ZC25'
    with T-code KSR2_ORC.
    3.I Assigned the Strategy Sequence To Order Type ZC25.
    4. I used User Exit COOM0003 in order to create Settlement rule from ZWBS field.
    In KO01, when i go into the settlement rule I can see the 2 lines that the user exit created.
    The problem is that when i'm saving the internal order the settlement rules are not saved.
    My questions are:
    1. Is anyone met this problem?
    2. is the user exit work on T-code KO02 also?
    thanks for your help.
    Best regards,
    Lior

    Hi Lior,
    Hope below information can give you some hints:
    See the detailed description of the error for example for order, in transaction KO02, click button 'Master data', click button 'Settlement Rule', populate column category with 'PSG' and press
    <enter>. On the 'Assignment to a Profitabilty Segment' screen press button 'Derivation' and see the long text of message K/111. In case the generation of settlement rules fails again later use these steps to find out why and check the derivation rule by means of transaction KECM.
    Best Regards,
    Owen

  • BAPI for settlement rules in WBS Elements

    Hi,
    Is there any standard bapi, method, or whatever... to create / modify settlement rules for WBS Elements?.
    Rgds,
    Jose

    Look at BAPI/FM of FG CJ2054
    BAPI_BUS2054_CHANGE_MULTI     Change WBS Elements by BAPI
    BAPI_BUS2054_CREATE_MULTI     Create WBS Elements by BAPI
    BAPI_BUS2054_DELETE_MULTI     Delete WBS Elements by BAPI
    BAPI_BUS2054_GET_GUID_FROM_KEY     Read the GUIDs Using the WBS Keys
    BAPI_BUS2054_GET_KEY_FROM_GUID     Read the WBS Keys Using the GUIDs
    CJ2054_CHANGE     
    CJ2054_CREATE     
    CJ2054_DELETE     
    CJ2054_WBSELEMENT_CHANGE_STRU     
    MAP2I_BAPI_BUS2054_CHG_TO_PRPS     
    MAP2I_BAPI_BUS2054_NEW_TO_PRPS     
    MAP2I_BAPI_BUS2054_UPD_TO_PRPS     
    Regards

  • Production order: Automatic Generation of settlement rule .......

    Hi Gurus,
    I am trying to settle a production order to a cost center. I have already define a settlement profile with Cost center as the default reciever and assigned it to the Order type but when I tried to settle it, I have to create a distirbution rule manually every time. Is this some thing to do with the strategy sequence? I have done a lot of research but the system doesnt give me any option for autmatically generating a settlement rule or assigning strategy sequence to order type for production order. I found some thing for Internal orders, but still i cant do it. Would any of you please help me. I would appreciate if you put the steps with the trxn codes.
    Thanks

    Dear.
    As I know, there're no way to generate settlement rule of production order automatically such as that of WBS(network).
    In settlement profile, If you want automatic fuction, you can only set PA segment as receiver addionally.
    What you want to do is the price difference(PRD-PRF) of production order be settled? then, why don't you make automatic account assignment(OKB9)?
    Generally, assumed using PA segment as receiver, we don't make price difference account as cost element, But, In your case, If you want to settle all amount of that to fixed cost center, specify that cost element to cost center by OKB9 instead of adding cost center in settleme rule.
    Regards.

  • Automatic Generation of Settlement Rules for PM order

    Hi All,
    I am doing a maintenance orders settlement and I have the fallowing issue:
    My client has 2 types of equipment, namely vehicles and industrial equipment. Both have particular rules.
    For vehicles, we need to control all cost by an internal order
    Industrial equipment costs will be control by cost center.
    So, cost center is maintained for industrial equipment, and Settlement Order for vehicle equipment.
    I have a unique order type for which in Settlement profile I have entered Order and Cost Center as 'Settlement Optional' and default object type as CTR.
    When I create a PM order for vehicle, system cannot generate automatically the settlement rule, because in order type I have entered default object type as CTR and in equipment I just have the Settlement Order.
    But if I create a PM order for industrial equipment system create automatically the settlement rule, because cost center is maintained for industrial equipment and order type has default object type as CTR.
    In the allocation structure I have a receiver category for CTR and ORD.
    So, Could you help me how to generate automatically settlement rule for both cases without 2 order types?
    Thanks & regards,
    Hélder Nunes

    hi
    i think it is not possible to generate settlement rule based on equipment ,if you have specified the default settlement category in IMG ,it will be generated .
    check with your technical team whether user exit IWO10027 can be mapped
    regards
    thyagarajan

  • Automatically GL account & settlement rule should appear in CO01 in creatio

    While Creating a Production Order in CO01 pl input the qty,finish date ,backward scheduling & release the order.
    This is REM ,choose prod version,click on Header---->Settlement rule
    Screen shoudl automatically show CAT---->GL ACCOUNT,Settlement Reciever say 59000000.
    But right now the values are inputed manually which meight result in errors & also wastage of time.
    What background settings need to be done (i think in OKO7) .Pl suggest.
    Thanking You
    Uday

    hi,
    Go to Settlement rule (CJ02),where enter the WBS .here go to Extra in the menu bar of that WBS ,under Asset under construction ckeck the box of Historiy....something like that .
    Regards
    Ricky

  • Automatic Creation of Settlement rule with the settlement type - AUC

    We have a situation where I have created an Internal order for AUC. But unable to create the setlement rule automatically with the settlement type -AUC. Please guide us.

    Hi,
    This is possible through investment management module.
    Define an investment profile using OITA and assign the asset class of AuC in investment profile. Assign investment profile to internal order master data.
    AuC will be created on settlement automatically on settlement of inernal order when processing option "Automatic" is selected in KO88.
    Regards
    Chetan.

  • Settlement Rules on WBS

    Is there any single screen wherein I can maintain the settlement rules for all the WBS elements under a project definition instead of selecting the WBS and then going through menu to maintain the rules?
    I know its possible to select settlement rule button by selecting all WBS and then maintain rules by clicking Next Entry.
    Expecting something similar to an overall screen available on WBS wherein we maintain the master data.
    Help me.
    Regards
    Sreenivas

    Hi Srinivas
    Its not possible as you are looking at Projet Defintion level.
    However, its possible to transfer settlement rule to all other WBS elements if similarities exists between them through T Code CJ02
    Regards
    Sudhakar
    Message was edited by:
            Sudhakar Pappu
    Message was edited by:
            Sudhakar Pappu

  • Settlement rules for WBS element

    Hi,
    I have a requirement to create WBS with settlement rules. Is there an FM or BAPI to call to create the settlement rule?
    Thanks.
    Lalyn

    hi
    good
    types: begin of ty_objnr,
      objnr    like prps-objnr,
    end of ty_objnr.
    *.COBRA-Buffer (see FM KOBS)
    types: begin of ty_cobra_buf.
            include structure cobra.
    types:   uflag like dkobr-upd_flag,
           end of ty_cobra_buf.
    types: ty_t_cobra_buf type ty_cobra_buf occurs 10.
    *.COBRB-Puffer mit Änderungsflag (see FM KOBS)
    types: begin of ty_cobrb_buf.
            include structure cobrb.
    types:   uflag like dkobr-upd_flag,
           end of ty_cobrb_buf.
    types: ty_t_cobrb_buf type ty_cobrb_buf occurs 10.
    Internal tables                                                    *
    data: it_abrechnug      type standard table of ty_abrechnung,
          it_objnr          type standard table of ty_objnr,
          it_cobra          like table of cobra with header line,
          it_cobrb          like table of cobrb with header line.
    Data                                                                *
    data: wa_cobra_buf      type ty_t_cobra_buf,
          wa_cobrb_buf        type ty_t_cobrb_buf,
          wa_objnr            like line of it_objnr,
          wa_urzuo            like cobrb-urzuo,
          l_mem_cobrb         like wa_cobrb_buf[],
          l_mem_cobra         like wa_cobra_buf[],
          l_mem_cobrb_zeile   like line of l_mem_cobrb,
          l_mem_cobra_zeile   like line of l_mem_cobra.
    form urzuo_aendern  using    p_objnr p_pspnr p_urzuo.
      data: c_objnr like prps-objnr,
            c_pspnr like prps-pspnr,
            c_urzuo like cobrb-urzuo.
      c_objnr = p_objnr.
      c_pspnr = p_pspnr.
      c_urzuo = p_urzuo.
      refresh: it_objnr,
               it_cobra,
               it_cobrb,
               l_mem_cobra,
               l_mem_cobrb.
      wa_objnr = c_objnr.
      append wa_objnr to it_objnr.
    Reas settlement rule from the DM
      call function 'K_SRULE_PRE_READ'
      exporting
        i_pflege               = ' '
      tables
        t_sender_objnr         = it_objnr
            T_COBRA                =
      exceptions
        wrong_parameters       = 1
        others                 = 2.
      if sy-subrc  0.
        perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        exit.
      endif.
    Fill internal buffer with settlement rules
      call function 'K_SETTLEMENT_RULE_GET'
        exporting
          objnr     = c_objnr
          x_all     = ' '
        tables
          e_cobra   = it_cobra
          e_cobrb   = it_cobrb
        exceptions
          not_found = 1
          others    = 2.
      if sy-subrc  0.
        perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        exit.
      endif.
    Save settlement rule in ABAP-Memory
      call function 'K_SRULE_EXPORT_IMPORT'
        exporting
          i_mode     = 'EX'
        exceptions
          wrong_mode = 1
          others     = 2.
      if sy-subrc  0.
        perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        exit.
      endif.
    Read ABAP-Memory
      import l_mem_cobra l_mem_cobrb from memory id 'K_SRULE'.
    Change field URZUO and set Update-Flag
      loop at l_mem_cobrb into l_mem_cobrb_zeile where urzuo is initial.
        l_mem_cobrb_zeile-urzuo = p_urzuo.
        l_mem_cobrb_zeile-uflag = 'U'. "Update Kennzeichen
        modify l_mem_cobrb from l_mem_cobrb_zeile transporting urzuo uflag.
      endloop.
    Clear internal buffer
      call function 'K_SETTLEMENT_RULE_REFRESH'
        exporting
          objnr = c_objnr.
    Fill ABAP-Memory with new rules
      export l_mem_cobra l_mem_cobrb to memory id 'K_SRULE'.
    Fill internal buffer with new rules
      call function 'K_SRULE_EXPORT_IMPORT'
        exporting
          i_mode     = 'IM'
        exceptions
          wrong_mode = 1
          others     = 2.
      if sy-subrc  0.
        perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        exit.
      endif.
    SAve new rules
      call function 'K_SETTLEMENT_RULE_SAVE'
        exporting
          dialog            = 'X'
          objnr             = c_objnr
          i_status_update   = ' '
        exceptions
          no_rule_for_objnr = 1
          others            = 2.
      if sy-subrc  0.
        perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        exit.
      endif.
      commit work.
      perform erfolg using c_pspnr.
    endform.                    " URZUO_AENDERN
    Thanks
    mrutyun^

  • Settlement Rules in WBS Hierarchy

    Hello,
    I have a scenario, where there is a WBS hierarchy. Now the situation is such that client wants each WBS to be settled to different Account assignment categories such as G/L, Cost Centre, PSG, and a combination of 3 (35%,35%,30%). In this case what will happen to the cost that is at top WBS/Project defn?
    Also can I have one settlement profile which will have all the above as valid receivers or do I need to have seperate settlement profiles?
    Secondly if I maintain a statistical account assignment ( for example a cost centre) in the detailed screen, with main receiver as G/L, will the statistical cost be seen against that CC?
    Thanks
    Shiv

    you usually post at the lower level WBS elements so do not worry about the highest level - even if you did make a posting the settlement would take care if it
    you can have one settlement profile with different receivers - just make sure that your settlement configuration is correct
    you will need to check this yourself - I think that applies to profit centre but not cost centre

Maybe you are looking for