WBSE Strategy creation for settlement rules

For Automatcally creation of settlement rules:    I created the strategy for WBSE settlement rules at IMG but idid not find option of superior WBSE in account assignment category field at setting folder.
can any one tell me why it did not not appear,

this functionlaity is not standard
apply note OSS 211324

Similar Messages

  • 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

  • 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

  • Mass maintenance for Settlement rule

    Hi,
    I want to maintain settlement rule of Network (cn22) and Internal order (Ko02). How can I carry out mass maintenence for these business process?
    PLease mention steps or any transaction.
    Thanks
    SIM

    HI,
    I don't know a standard transaction for settlement rules mass maintenance but you can use LSMW based on a batch-input recording  for the changes you want to make.
    Best regards, Christian

  • Business object for Settlement Rules

    Hi Experts,
    Is there any Business Object available in SAP for Settlement Rules ?
    I've identified Change Document Object RKABRV for Settlement Rules but I need respective BO to do the mapping in tcode SWEC.
    Please share.
    Thanks,
    Anirban.

    Hi Naval,
    To find out a BTE for a given tcode you can try this. In a session open SE37 tcode and open the function module BF_FUNCTIONS_FIND. Set a break point at CALL FUNCTION. Then in another session open FB08 tcode. Try creating a entry and save. When you press it will call this function module. Now check for the values in the container I_EVENT. It contains the BTE that can be used for the given tcode.
    Regards,
    Raj

  • Can User Exit works for Settlement Rule in Maintenance Order creation?

    Dear Experts,
    I have this situation where I tried to create an Internal Maintenance Order via IW31 for multiple equipments from different functional location (different cost centers) using the Object List.  However, the settlement rule has a problem to pull out as there's no Equipment in the reference object. That's the reason, I'm looking at the User Exit which I understand the IWO10027, can do the work.  Since I'm new to User Exit, can I enhance the settlement rule by the following condition.
    The costs spent on each equipment will be used as a basis of calculating the weightage (via equivalence no) for the settlement rule.
    Can it be done that way?
    regards,
    Abraham

    Sanjay,
    This data can be checked in the following user-exits:
    COZF0001: Change purchase req. for externally processed operation
    COZF0002: Change purchase req. for externally procured component
    PeteA

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

  • Bapi for settlement rule in IW32

    I want a bapi which will create settlement rule for IW32 ?It should be able to update Valid From And Valied to fields in IW32.
    I have checked BAPI_ALM_ORDER_MAINTAIN it does not have Valid from and Valid to fields in structure BAPI_ALM_ORDER_SRULE.I need a bapi which can be used to update those fields.

    HI
    Check This Link
    Re: Create/change settlement rule for inv.order - BAPI, funct.module???

  • Table for Settlement rule in production orders

    Hi All,
    Is there any table by which I can get list of production order numbers & the details of the settlement rule maintained in that order.?
    Regards,
    MHP

    There will be object number (OBJNR)  against each production order number which you can obtain from table AUFK.
    Later pass this object number to function module K_SETTLEMENT_RULE_GET to get the settlement rules.
    Also try function module K_SRULE_PRE_READ for reading the settlement rules. Here pass the object numbers to the tables parameters

  • 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

  • PM:Action log for Settlement rule

    Dear all,
    May i know are there any way that i can see the changes that being done at screen maintain settlement rule. For example if I change the settlement type, system will keep the change/action log for that changes.
    One more question, what the different between settlement type 'FUL' and 'PER' (impact to the settlement)
    thank you so much,
    Siti Norbaida

    Hi,
          I Hope this Documentation will help you ........
    Settlement type
    Depending on the processing type, the settlement type determines which settlement rule is used in a particular type of settlement processing.
    The SAP system supports four settlement types. The AUC and PRE settlement types are used for settlement of capital investment measures. You can only use the PER settlement type for planned settlement.
    PER (periodic settlement):
    Settlement with this settlement type covers only the costs for the relevant settlement period.
    The following data from internal cost allocations:
    Sender cost center/activity type sent
    Business process
    Quantities
    is allocated further to the following receivers:
    Cost center
    Internal order
    Sales order
    WBS element
    Cost object
    Business process
    Actual activity prices, elimination of internal business volume and variances can then be calculated correctly in Cost Center Accounting and Activity-Based Accounting;
    FUL (full settlement):
    You can use this settlement type in automatic settlements.
    The difference to periodic settlement is that in full settlement you settle each time all the costs that have occurred for a sender object for all the periods prior to the settlement (and are not yet settled). If PER rules exist, they take precedence over the FUL rule.
    Quantities from internal activity allocations are not sent to the receiver. This means that there is no guarantee that actual activity prices, elimination of internal business volume, and variance calculation will take place correctly. For this reason, we do not recommend that you use FUL for cost centers or business processes.
    AuC (Capitalization in asset under construction):
    This settlement is automatically generated if you enter a capital investment profile with an AuC as its capital investment measure in the order control data.
    Settlement is conducted periodically and in full to the AuC
    PRE (periodic preliminary settlement):
    You can enter PRE rules in the settlement rule for the order. They are used as part of settling capital investment measures.  Depending on the rules you entered, posted debits are settled to the CO receivers or to a G/L account before the periodic settlement.
    It is good idea to do this for particular line items if there are additional costs assigned to a capital investment measure that should not be capitalized. This may be necessary, should you wish to monitor the total costs of the measure in controlling.
    Use
    Note that settlement type FUL permits quantity settlement for primary cost elements only.  You cannot settle quantities to assets.
    Note that you cannot manually create or change a distribution rule with settlement type AUC.  This has the following effect on settlement rule maintenance:
    The required rule is generated from the asset under construction, which is stored in the master data for a capital investment measure, ( order or WBS element)when you carry out settlement for the first time.
    Regards,
    Gangadhar

  • BAPI For settlement rule for IW33 transaction

    hi,
    good day guys
    Iam searching for BAPI for iw33 for settelment rule..but i couldnt get it..
    Settlement rule is nothing but Rule that determines which portions of a sender's costs are allocated to which receivers.
    If you go to iw33 t.code.. give the order numbe and then enter..
    Go to tab--->Settlement Rule..
    plz can anyone tell me which bapi is fit for it...
    Regarsd

    hi,
    try the following BAPI
    BAPI_ALM_ORDERSRULE_CREATE
    hope this helps
    Regards
    Ritesh

  • Infoobject for settlement rule

    hi,
    Can anyone tell me the infoobejct for the settlement rule on WBS element.
    I am able to find only settlement area in OCOOM_CO2.
    thanks
    venku

    HI
    Check This Link
    Re: Create/change settlement rule for inv.order - BAPI, funct.module???

Maybe you are looking for