Settlement Problem of WBS

HI All !!
I need to create a project to cater the cost like travelling, general expenses, electricity charges etc and then settle the amount on monthly basis to cost center. (I need to create this to have better control on these costs)
I've created the wbs and done the budgeting. Now when i assign the settlement rule as cost center with 100% and FUL settlement it gives me an error "maintain the distribution rule for G/L account without validity limit". So, to remove this error I randomly selected a g/l account and set the percentage to 0% and FUL and in No column its 2 ... so the question, is this correct ? will all the cost be settled into cost center and no cost will be settled in GL account ? (I can't change the settlement profile)
thanks

Thanks for the replies Sreekanth & Nitin
But i want to know will this setting work?? i dont have a testing system in my company and also i cant change the profile .. my first analysis was also the same that GL account is set as mandatory.. but sadly i can't change it ryt now
so i need to know if this setting of 100% and 0% will work ?
can u tell me what is the meaning of the No column when i press f1 on it it says Distribution Rule Number .. does this define a hierarchy ?
if it is defining a hierarchy then it should consider cost center first and settle 100% in it .. ryt ?
Thanks
Rabiee

Similar Messages

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á

How to settle previous period WBS element which was closed.

Hi all,
Please let me know, how to settle previous period WBS element which was closed.
Thanks and kind regards,
Padmaja.

actually the wbs element was related to 2005 and it must be cleared in 2005 itself.but due to some problem it had been not cleared. we cant open the prior period and close the wbs element .if we reverse it shows as erroneous transactions .

Sales Order Settlement to Only WBS

Hi,
I have scenario like Sales Order Settlement to only WBS in make to order.
Again from WBS settlement to COPA.
So far I know WBS settlement to COPA and I am not sure in the 1 st scenario.
Can you any body tell me where I need to configure, is it only settlement profile or any other settings required?
Thanks & Regards,
KBR

Hi,
What is the business rational to have a 2 step settlement to COPA?
Thank you and Regards,
Varshal Kachole

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)

Settlement profile for WBS element

Hi All,
While providing the settlement profile and rule to a wbs element and saving i getting one error
Rule 3Z000001072 not found" and
indetail Diagnosis
A subrule has been specified which does not exist.
System Response
None
Procedure
Check the name of the subrule and create a new one if necessary. The subrule may belong to a different class.
Can any one tell what exactly this means and how do i rectify.
regards SAM

Hi
Check the rule
SPRO - PS- Costs -
Automatic and periodic allocations-settlement-Settlement rule for WBS
in that check the settings of the rule which you got error and check the network order settlement rule also.
Thanks
S.Murali

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

WBS Settlement Problem

we are settling the WBS to asset under construction.
while executing the transaction CJ88, system prompt the following error message.
================================================================
Field Cost Ctr is a required field for G/L account 1400 Z0110201
Message no. F5808
Diagnosis
The value for field "Cost Ctr" in the interface to Financial Accounting is an initial value but you are required to make an entry in the field selection for G/L account "Z0110201" in company code "1400" linked to the field selection for posting key "50".
System Response
Error
Procedure
It might be an error in the configuration of the G/L account field selection. The initial application, used to call up the interface must otherwise define a value for field "Cost Ctr". If this is the case, contact the consultant responsible for the application used to call up the interface or get in contact with SAP directly.
======================================================
we know the cost centre is required on our GL. we also passing the GL entry on that GL with Cost center & WBS Elemenet.
Thanks

Hi
Try with this go to posting key field status if cost center is mandatory make it optional. Before doing it analyze the business scenario why cost cetner is made mandatory for posting key 50. There should not be any problems further
Cheers
Muralidhar

Settlement rule in WBS element

Hi Team
we are assigning General ledger accounts for settlement WBS element cost. system gives the below warning message. but we have three company codes we fallow the same steps for all company codes. but we are facing in one company code only why it happen. warning message like below
Total = 200.00%, ( Set.Type FUL / Version / Actual settlement ), period 009/2009, source assignment COE
Message no. KD041

we are selecting settlement catogiry G/L
Settlement receiver G/L Number
% = 100
settlement is = Ful
no = 1 ....10
we are transfering the total amount to 10 g/l like above that time we are facing the problem.

Settlement of order -WBS Element

Dear Experts,
Can any one tell me what is meant by WBS element and in what scenario,PM orders settlement rule created with category as WBS.If possible tell me with any practical example.
regards
KRISHNAN

Dear,
Dear,
Budget: Amount of resources allocated under a particular head in a financial year.
Budget Control: Having/ creating a control on the resources allocated in a financial year.
Original Budget: The initial budget that you have allocated to a WBS element.
Supplement of Budget: One time/ discrete increment in the original budget.
Return of Budget: Taking out the unutilized portion of the budget.
Transfer of Budget: Transferring the budget among two or more expense heads.
Project Definition: A framework for a business undertaking with a fixed goal to achieve with given resources.
The project definition contains dates and organizational information that are binding for the entire project.
WBS Element: Individual structural element in a work breakdown structure (WBS) representing the hierarchical organization of an R/3 project. Describes either a concrete task or a partial one that can be further subdivided.
Proposed Business Process
Assume there are seven expense heads in maintenance department. There may be addition of expense head in near future.
Based on the maintenance heads, maintenance department will create a project in project system. This project will be used for statistical purpose only & will not have any financial implication.
Upon creation of a project, WBS elements will be created as per the expense heads. So for each expense head, there will be one top level WBS element. Again these WBS elements will be divided in twelve WBS elements. These twelve WBS elements represent twelve calendar months.
Budget will be allocated to each WBS element & the WBS element will be released from the project.
Maintenance department will create maintenance orders as per their work requirements. These orders will be settled to cost centre, which is maintained in the settlement rule. Also WBS element will have to be mentioned in each order so that the budget control can take place. So as to capture cost from each maintenance order, the WBS element field will be made mandatory field in maintenance order.
So when a maintenance order is released, system will do a budget check against the WBS element mentioned. If the budget check status is OK, order is released or else it will stopped from release. If the order is stopped from release, maintenance department will have to supplement the budget. Upon supplementing, the order is released again & the maintenance cost such as, labour, material costs can be booked on the order. Again the order cost is settled to cost centre & at the same time, budget is consumed from the respective WBS element.
Every year, maintenance department will copy the previous years project so as to save time & efforts to create project & WBS elements. And the maintenance department will assign the budget allocated to each WBS element in a financial year.
It is also possible to return the unutilised budget or, transfer of budget from one WBS element to another.
Create a project CJ20N
Create WBS element CJ20N
Assign Budget to WBS elementsKO22
Display assigned Budget KO23
Supplement Budget KO24
Display Supplement budget KO25
Return Budget KO26
Display Return budget KO27
Transfer of budget CJ34
Hope u wull get ur answer
Regards
Rakesh

Report on Settlement - Project wise/ WBS element wise

Hello Friends,
I am looking for a report on settlement which will include the senders - Projects or WBS elements and Settlement receivers and the amount settled in the any period for a particular fiscal year.
Your response will be rewarded.
Vishal.

Hi,
Pls refer CJIC and CJID.
Regards,
Amit

WBS element is updated while settling cost from WBS to AUC

Hi Experts
At the time of settlement , when we settling the cost from WBS to AUC , WBS element is updated in AUC line item of accounting document , but it should not be updated actually.
As result AUC cost is loaded on WBS and budget of WBS is get affected , furthermore system is not allowing for MIGO even budget is available but in CJ30 it is showing assigned value is more then original budget.
Please suggest.
Thanks & Regards
shailesh

Hi Saurabh ,
I totally agree with you , but in our case system is not allowing(Error Message: Budget Exceeded) MIGO against capex PO - > WBS.
Note : in our case , system is checking budget at the time of MIGO also.
in our case , report S_ALR_87013558 is showing wrong actual value and also in CJ30 , total assigned value is larger then total distributable budget , As result our available budget gets negative figure in report S_ALR_87013558 , even i have already run CJEN->CJBN 2 or 3 times.
Note: Our Commitment value is correct.
Actually , according to report S_ALR_87013542 , system is showing correct actual value , that means we have sufficient available budget for further MIGO's
Now may be , due to WBS element is updated in AUC line item of accouning document of settlement (WBS to AUC) , system loads AUC values to WBS unnecessarily , our available budget gets negative figure.
For your reference , i am attaching screen shot of accounting document which is generated at the time of settlement from WBS to AUC.

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 doc number & wbs element relationship table

Hello,
I am trying to find any tables which can help me get the settlement doc number and wbs element relationship. Presently I am using table AUAA and here is my select for that:
SELECT belnr aufnr pspnr anln1 coobjnr FROM auaa INTO TABLE tab_auaa
                    WHERE emtyp = 'PR'
                    AND bukrs IN p_bukrs
                    AND kokrs IN p_kokrs.
since I do not have "belnr"(the primary key) it is taking too long to get this info.....any one has any idea of any other tables to get this information or a bapi?
appreciate the help
AS

Hi all,
thanks for all the help and support on this...I found a way to get all the CO settlement doc numbers for a project and their relationship as sender and receiver.....
first i went to anla and anek to get the AUC and the wbs settling to this AUC relatiionship...once i got my main wbs element...i found all the wbses for this project.
I need to use the table AUAK, AUFK, and AUAA to get all that information. I got all my wbses for a project first....than I went to table AUAK with all these wbses...and found the belnr(settlement doc numbers)....this table does not give out complete settlement doc numbers for wbses....we need to go back to AUAK with the internal orders to get the belnrs for them as well....so to get all the internal orders for a project i went to AUFK....than i took these orders and went back AUAK with these orders and got my missing belnrs....
now I had all my belnrs for a project....so i went to table AUAA and did the select with these belnr...and since now i have the primary key the access is lighting fast....by doing that select i got all my relationship, i mean which settlement is goind where...
mind you that I used AUAS to get the sender/receiver relationship with the amount....this is as well a cluster table but we have the primary key belnr(co settlement doc. numbers)...so no worries to get the data here as well....
here are my selects for AUAK, AUFK and AUAA....
TYPES: BEGIN OF prps_ty,
        psphi TYPE prps-psphi,
        END OF prps_ty.
        DATA all_proj TYPE STANDARD TABLE OF prps_ty.
        DATA wa_all_proj TYPE prps_ty.
TYPES: BEGIN OF objnr_ty,
           objnr TYPE auak-objnr,
           END OF objnr_ty.
DATA lo_p_psp TYPE STANDARD TABLE OF objnr_ty.
IF all_proj IS NOT INITIAL.
          SELECT objnr FROM prps INTO TABLE lo_p_psp FOR ALL ENTRIES IN all_proj
          WHERE
          psphi = all_proj-psphi.
        ENDIF.
IF lo_p_psp IS NOT INITIAL.
          SELECT belnr objnr FROM auak INTO TABLE tab_auak FOR ALL ENTRIES IN lo_p_psp
          WHERE
          kokrs IN p_kokrs
          AND gjahr IN p_gjahr
          AND objnr = lo_p_psp-objnr
*        AND objnr LIKE 'PR%'.
        SORT tab_auak BY belnr.
        DELETE ADJACENT DUPLICATES FROM tab_auak COMPARING belnr.
SELECT aufnr objnr pspel FROM aufk INTO TABLE tab_aufk FOR ALL ENTRIES IN lo_p_psp
          WHERE
          bukrs IN p_bukrs
          AND kokrs IN p_kokrs
          AND pspel = lo_p_psp-objnr.
        ENDIF.
*get the belnrs for orders---this part is very important or we miss out all the belnrs for I/O...
        IF tab_aufk IS NOT INITIAL.
          SELECT belnr objnr FROM auak INTO TABLE tab_auak2
          FOR ALL ENTRIES IN tab_aufk
          WHERE
          kokrs IN p_kokrs
          AND gjahr IN p_gjahr
          AND objnr = tab_aufk-objnr.
        ENDIF.
*append these new belnrs to tab_auak
        LOOP AT tab_auak2 INTO wa_tab_auak2.
*              CONCATENATE 'PR' wa_tab_aufk-pspel INTO wa_tab_auak2-objnr.
          APPEND wa_tab_auak2 TO tab_auak.
        ENDLOOP.
        SORT tab_auak. "by belnr.
        DELETE ADJACENT DUPLICATES FROM tab_auak.
*now get all the belnrs for this project...complete list....
        IF tab_auak IS NOT INITIAL.
          SELECT belnr aufnr pspnr anln1 coobjnr FROM auaa INTO TABLE tab_auaa
                   FOR ALL ENTRIES IN tab_auak
*            WHERE pspnr = wa_wbs-posnr
                                 WHERE
                                 belnr = tab_auak-belnr
                                 AND emtyp = 'PR'
                                 AND bukrs IN p_bukrs
                                 AND kokrs IN p_kokrs.
        ENDIF.
        SORT tab_auaa BY pspnr belnr.
I used our own indexes for all the transparent table accesses.... to speed up the process...you might want to create your own indexes depending on the where clauses for transparent tables.....
well thanks again..and hope all this will help someone else too....
AS...
Edited by: J Are on Oct 31, 2009 1:19 PM

Settlement Problem of WBS

Similar Messages

Maybe you are looking for