Default Settlement Rule of PM Maintenance Order

Hi,
While creation of settlement rule on Maintenance Order, Option appears of default settlement rule. Whenever i select that option on Settlement Rule definition screen, two rows appears for the same Cost reciever automatically ( One for Full settlement and second for Periodical Settlement) But i only want Full settlement option to appear on screen in this scenario. Can anybody pin point the root cause and share the solution of it.

hi
while defining the settlement profile specify CTR as default settlement receiver and check ,and also make the settlement profile mandatory for order release,
regards
thyagarajan

Similar Messages

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

Default settlement rule with settlement type as FUL for service orders

Hi Folks,
Could you please advise me on the below issue?
Requirement: setting up of default settlement rule with default settlement receiver as u201CCOST CENTREu201D and settlement type as u201CFULu201D for the maintenance orders (Order category u2013 30).
I was trying to configure the same in transaction KSR3_ORI to assign the strategy to the service order type by clicking u201CNew Entriesu201D system not showing the drop list for the status column which is a mandatory field.
We have applied the below notes:
Note 313454 - Info: Default value for settlement type
Note 851975 - Settlement use automatic generation creates
Could you please guide us to get the default settlement rule for service orders along with settlement type as u201CFULu201D

I was also with this problem in 2013 january and only found some information about this, here.
Our solution was change the Maximum number of distribution rules in Maintain Settlement Profiles to 1, because we wanted the FUL rule and it is always in the first line.
Now, for curiosity, I was search for another solution and found the SAP note 2028108 that explain that is not possible to change the strategy for PM/CS orders.
This note was released at 09.06.2014

Settlement rule in rework process order

Hello
When creating a rework process order without material in CORO the system is asking automatically for the settlement rules. Here we can then maintain a cost center order order. This is very nice and perfectly fine to us.
When now creating in a different case a rework order with material in COR1 (because we plan a goods receipt) the system is automatically taking the material as default settlement rule without asking the user. Would anybody know a way how to customize the system to ask the user in any case for the settlement rules? So the user really has to make a choice and is not always forgetting to update the correct values which are not only the material. (kind of a training issue but maybe the system can do something about that..)
Thanks

Hi,
Please click this link
http://help.sap.com/saphelp_470/helpdata/en/38/0cf817ed9b11d29fa2080009b0db33/content.htm
Rework order
thanks
krishna

User Exit for the Settle rule of a Production Order

Hello all
i got a requirement to change the settlement rule of a production order to multiple receivers.
suppose i have the following rule
Categeory | Settlement Reciever | Receiver Short text |   %   | Settlement Type | No | Source Assignment
    MAT             ZMDT89                   ZMDT88              100        FUL                 1            left as blank
now my requirement is that i have to default the source assignment as 200 (Materials) so as to allow the other reciever entered with the same settlement type as FUL and also the No should be 2
i.e. my req is like this
Categeory | Settlement Reciever | Receiver Short text |   %   | Settlement Type | No | Source Assignment
    MAT             ZMDT89                   ZMDT88              100        FUL                 1            200
    G/L             G/L A/C no                G/L shor text       100        FUL                 2            100
the bold one is i have to ADD
the T-Code is CO02.
your help is highly appreciated...
thanks in advance

hi,
check these exits in co02.
Transaction Code - CO02                     Change Production Order
Enhancement/ Business Add-in            Description
Enhancement
PPCO0010                                Enhancement in make-to-order production - Unit of measure
PPCO0012                                Production Order: Display/Change Order Header Data
PPCO0013                                Change priorities of selection crit. for batch determination
PPCO0015                                Additional check for document links from BOMs
PPCO0016                                Additional check for document links from master data
PPCO0017                                Additional check for online processing of document links
PPCO0018                                Check for changes to production order header
PPCO0019                                Checks for changes to order operations
PPCO0021                                Release Control for Automatic Batch Determination
PPCO0022                                Determination of Production Memo
PPCO0023                                Checks Changes to Order Components
STATTEXT                                Modification exit for formatting status text lines
PPCO0009                                Enhancement in goods movements for prod. process order
CCOWB001                                Customer exit for modifying menu entries
COIB0001                                Customer Exit for As-Built Assignment Tool
COZF0001                                Change purchase req. for externally processed operation
COZF0002                                Change purchase req. for externally procured component
PPCO0001                                Application development: PP orders
PPCO0002                                Check exit for setting delete mark / deletion indicator
PPCO0003                                Check exit for order changes from sales order
PPCO0004                                Sort and processing exit: Mass processing orders
PPCO0005                                Storage location/backflushing when order is created
PPCO0006                                Enhancement to specify defaults for fields in order header
PPCO0007                                Exit when saving production order
PPCO0008                                Enhancement in the adding and changing of components
reward points if hlpful.

How to Make Settlement Rule Mandatory in Sales Order(In Acct Assigt Tab)

Hi Gurus,
I have a business requirement. For Free of charge 3rd party orders (yes they have FOC orders delivered by third party) the business wants to ensure that the Settlement rule should be mandatory. They enter cost center & receiver in the settlement rule.
i.e the order should not save till Settlement rule is maintained in the line item in the Acct Assignment tab.
Please let me know how this can be done.
1: Applied my brains on incompletion procedure but does not seems like it can be done there.
2: Is there something in CO where some setting can make it mandatory to enter settlement rule in Sales order?
3: I s there any other way in user-exits or ABAP?
4: Is there any setting in Item category(I could not locate any)?
5: Can this be done via Requirement class.
Please assist to resolve this one.

Dear,
It depends on settings in Requirement Class (OVZG) and Account Assignment Catg (AAC) in OME9
If your AAC is E in Req Class, then your sales order is a CO object.
Requirement Class in IMG can be checked - IMG > Controling > Prod Cost Planning > Cost Obj Controling > Prod Cost By Sales Order > Control of Requirement.
Or any filed any you can Make mandatory through Transaction variant SHD0.

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

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

Settlement rule SDI in prod order

Hi,
I used strategy make to order in my client, when i create prod order the settlement rule is always MAT and want the settlement rule to be SDI to my sales order.
What should i config to achieve this ? since i tried to change order type dependent parameter and it did not allow (only PP1 and PP2 allowed).
Please kindly help
Best regards,
Freddy Ha

Hi,
i tried to change the requirement class for makte to order so the setlement become SD1 in setting for requirement type KE. In the OPJH i still used PP01. and now it work thanx for all off your input.
Thankx once again.
Good day,
Freddy Ha

No access to settl rule when copying Sales order from Quotation

Hi all
Can you help me on my following issue :
I create quotation in which I refer to a settlement rule.
WHen creating a sales order in reference to my quotation, the settlement rule in the "item account assignment" tab is not reachable ...
This mean that all costs are posted on the quotation but not in the sales order.
But we would like to keep all costs on the sales order, as we do in all our process.
I've checked the copying rules but found nothing..
Any suggestions?
thanks in advance
martine

In the standard sales order screen (type OR for example) if you go to Go To Item Account Assignment you can press on the button"Settlement Rule "
But when copying Sales Information to Sales order with standard copying requirements, you can not presse on the button "settlement rule"
Furthermore, in this tab, a field called "PC DUMMY" is now appaered on the screen ...??!!!
Any idea of what to do ??
thanks !
martine

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

Settlement Rule mandatory in Process order

hai,
How can I make the Settlement Rule mandatory while releasing a Process Order?
Sonali

In OKO7, select process order and in details, make the option for "ORDER- settlement required"...
karthick

WBS Settlement rule control for service orders

Hello,
We have an requirement to implement validation point for service order settlement rule. Currently there is no validation check of settlment rule for service order. So that the settlement is happend to incorrect receivers in service orders.
For example :
Service order created for company code - 400 and the settlement rule receiver should be WBS which is belongs to same company code but some case , user are maintained wrong WBS in settlement rule which belongs to some other company code.
Can you please hlep us on this requirement and suggest any enhencement point avalible on the same.
Thanks
Risha

Hi,
Please go to okg2,
Calculate wip or result analysis
remove the tick for Order In Engineer to Order Production
Now run result analysis and check whether settlement will not happen for cross company code.
please check this and revert back.
Thanking you
Vengaiah Chowdary

Shortdump upon calculating settlement rule in co-product-orders w/rule PP6

Hello,
We use production orders with co-products. Production Order Type contains distribution rule PP6 (settlement of co-products by actual cuantities). We have installed the MILL-funcionality
If we create a production order for a small quantity, the system gives a shortdump upon calculating the distribution rules in the settlement rule in the order.
Key-words in shortdump:
COMPUTE_INT_TIMES_OVERFLOW
CX_SY_ARITHMETIC_OVERFLOW
in procedure "MILL_IT_CALCULATE_BASEQUANTITY" "(FUNCTION)"
If we create the order with a sufficient big quantity, information messages appear, telling that are rounding errors creating the settlement rule in the order. The order nevertheless is created correctly and no shortdump appears.
We already implemented notes 1349991 and 1524822 but they dont resolve this problem.
Any clues?
Thanks for any answer on this strange problem we face.
Aart

Thanks,
We aplied the notes you suggested but it didnt sove the problem.
Any sugestions?
Thanks.
Aart

Settlement rule while creating service order

Hi Gurus,
1. can someone help me in knowing what should be passed as receivers key while updating settlement rule if i am using Sales Order for settlement ; sales order, sales order item, object number of item or something else because i tried to pass all of these but not working.
2. I pass receiver category as SDI.
Kindly help asap.
Thanks,
Ritu

Hi Gurus,
1. can someone help me in knowing what should be passed as receivers key while updating settlement rule if i am using Sales Order for settlement ; sales order, sales order item, object number of item or something else because i tried to pass all of these but not working.
2. I pass receiver category as SDI.
Kindly help asap.
Thanks,
Ritu

Default Settlement Rule of PM Maintenance Order

Similar Messages

Maybe you are looking for