Settlement rule (Transport)
Hello All,
Can you please let me know, if there is a way to Transport Settlement rules linked to Internal order?
This is urgent. Points would be rewarded.Thanks
Regards.
Hello rajeshwari,
After you have created a settlement rule, actual costs have been incurred on the sender object, and all the settlement prerequisites for that sender have been met, you can settle the costs incurred.
You can use individual or collective processing.
Procedure: Choose Settlement from the menu of the object you want to settle.
Make the relevant entries
For the order when you are in individual processing.
For the selection variant when you are in collective processing.
In contrast to assessment, you cannot perform settlement across fiscal year boundaries.
The system automatically determines the posting date from the posting period and the fiscal year. The posting date is the last day of the posting period. There is no input field for this, but the date does appear, for example, in settlement documents.
Asset value date
This is the date for valuation in Asset Management. You can enter the date in the initial screen in the settlement or derive it from the settlement rule for the sending or receiving asset. This field does not appear, for example, during settlement of production orders.
Processing type
There are 3 processing types defined for settlement:
Automatic
The system selects all the distribution rules for a sender. Note the following special features:
If a sender only has distribution rules with settlement type PER, the system only selects and settles the costs of the settlement period.
If a sender has distribution rules with settlement type PER (PER rules) as well as distribution rules with settlement type FUL (FUL rules), the PER rules are applied first to the costs for the settlement period. If any costs are left after that, the FUL rules are applied.
A production order with the FUL settlement rule to materials is not settled until the final delivery is received. However, if any work in process is calculated for the order (order accrual), the related values can be transferred to Financial Accounting.
For investment measures, FUL rules are not applied until the measure is technically closed (compare "partial capitalization"). Assets under construction (AUC) are always settled, regardless of status.
Periodic
All distribution rules with settlement types PER and AUC are selected. PER rules are applied first. In investment measures, this is followed by settlement to assets under construction.
Partial capitalization
Use this processing type if you want to partially capitalize an investment measure which is not yet complete, that is, if you want to settle part of the overall cost to finished assets.
Hope thisn helps. please assign points.
Rgds
Manish
Similar Messages
-
How can I make settlement rule mandatory in create work order (IW31)
How can I make settlement rule mandatory in create workorder and saving without release.
I kanow we can make settlement rule mandatory upon Release order but here requirement is
Create work order (IW21) save without releasing that time settlement rule should default.Hi,
1.If you want the settlement rule default then maintain account assignment data in technical object and when MO is created on that it would be copied into the settlement rule...
2. If you want to make those fields mandatory .... plz check up field selections in config , if you cannot find those then use SHD0 Transaction variant to make those fields mandatory.
3. Enter SHD0 , Enter IW31 in transaction and ZIW31 for transaction variant ..click create option and this takes you to IW31 initial screen , here enter required values of technical object etc and press enter and this gives you IW31 Initial scree screen variant , click continue and this takes you to inside screen and here enter required field values and on pressing enter gives you screen variant .. so you need to enter field values and check the flow of screen variants and on getting settlement rule screen variant select required option for the fields you need.
4. Finally you can save that in package created in SE80 for transporting to other client .., you can activate the variant in SHD0 -->Standard variants -->you can find activate option ..
regrds
pushpa -
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.
Lalynhi
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^ -
Hello Experts,
I need to create settlement rule for work order.
Got one FM K_ORDER_SRULE_ADD but don't know how to use it.
Is this FM correct one to create settlement rule?
Can anyone please send sample code for FM?
Thanks in Advance,
Ripal.Hi everybody,
I found in a Rusian foruma way to create a settlement rule using the functions of the FM KOBS. I changed a bit the code because my requirement was just to update the field URZUO of the settlement rule. The original post (in Russian) can be found here.
My implementation is more simple because the requirement was different:
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
Hope it helps,
Jaime -
Network activity - settlement rule change FM or BAPI
I wonder if there is any FM or BAPI to change settlement rule for network activity?
Hi everybody,
I found in a Rusian foruma way to create a settlement rule using the functions of the FM KOBS. I changed a bit the code because my requirement was just to update the field URZUO of the settlement rule. The original post (in Russian) can be found here.
My implementation is more simple because the requirement was different:
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
Hope it helps,
Jaime -
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. -
GR/IR expenses not affected with the settlement rule run process in the GL
<i><b>Please neglect by previous post with the same title</b></i>
There is a problem I face while running the settlement rule process related to internal orders on the GR/IR expenses.
According to the internal order settlement rule every expense associated to an Internal order no. whether its an account payable or manual journal accounts it should be settled (distributed) on the cost centers specified in each internal order after the monthly settlement run process is done through T.Code "KO8G", and this actually happens on the entries that are booked manually through T.Code "FB50", but the GR/IR entries is the biggest problem, it didn't reflect the settlement rule distributions in the GL it just gives me the original transaction once its was automatically created through T.Code "MIGO" they are only allocated to a one profit center with no cost center and without being distributed to a multiple cost centers according to the distribution strategy.
After a long search I found that the cost center distribution occurred only on a secondary none GL account named A&P Settlement (720010), all GR/IR expenses was settled correctly only on this account not through the ordinary GL accounts (e.g. Gifts, printed materials) and of course the correct distribution didn't appear in the GL,
So is there a transaction or any way to allocate the GR/IR expenses to there correct cost centers with the correct cost element in the GL?
Is there anything to do with the GR/IR calculation that depends on quantity base not value base?
<i><b>The Process as follows:</b></i>
(<b>1) Creating Internal order with a settlement rule (E.g. Cost center 1 (50%) Cost center 2 (50%)</b>
<b>2) Creating a purchase order associated to an internal order</b>
<b>3) The Goods received and creating the GR transaction T.Code "MIGO"</b>
Acc/DR Expenses accounts
Acc/CR GI/IR Account 400301
Profit enter ###### (eg. 111177)
Cost Center <blank>
Internal order no. ####### (e.g. 9810512)
<b>
4) Closing the GR/IR accounts when receiving the invoice T.Code "MIRO"</b>
<b>When we receive vendor invoice:</b>
Acc/Dr GI/IR Account 400301
Acc/Cr Vendor Account
Profit enter ###### (eg. 111177)
Cost Center <blank>
Internal order no. ####### (e.g. 9810512)
<b>5) Performing the Internal order settlement rule run process</b>
<b>(N.B.</b> By entering the report of the cost center (Actual/Plan/ Variance) T.Code S_ALR_87013611
I found that GR/IR expenses was not charged on the concerned cost centers as shown in the GL <b>)</b>
<b>Your Reply is highly appreciated</b>Thanks for your kind reply,
But is there a way solve this problem?
And what is the use of leaving a field in the account assignment tab for an internal order while creating a PO and it will not take advantage of the settlement rule????????
And as you know the internal order settlement is a way to create a multiple account assignment
Can we solve the problem by making an automatic fake transaction that reverse the value of the GR/IR and creating another transaction can apply on it the settlement rule??
You know that settlement rule process is one of the best features in the SAP system it save time and effort to make distributions manually -
CO Order settlement rule to be changed on monthly basis.
Hello,
We have a scenario where in CO orders (i.e. orders created in KKF1) which is being used for goods issue (MT 261). Settlement rule is defined in the order and the receiver is CO-PA.
Now the requirement is, values lying in each order needs to be distributed to say 3 profit center on every month. This distribution rule is subject to change on a monthly basis. I know we can give the percentage say 50% to PC 1, 20% to PC 2 and 30% to PC 3.
But this rule is subject to change every month. How can the user give the Settlement rule manually every time which is very time consuming. Even if we gives it cannot exceed 999 line items.User wants to use the Same co order.
Regards
KarthikHi ajay,
Thanks for the reply. I am also planning to do the same... but is there any other way for this...
Even While trying to settle to Cost centre, system is not allowing to settle to cost centre for apr 2014. I have already remove the 100% indicator in settlement profile. -
Can anyone please advise on the following.
We have a project (WBS) created that has a settlement rule just for AUC in 07/08, was settled in both 07/08 and 08/09 with automatic settlement. We know want to add a rule for full settlement to transfer it to a GL. We are receiveing an error message to say system does not support this for previous years postings???Hi Jamie,
Please, check this node:
Re: First settle items from the previous year in the previous year
There must be also an OSS note mentioned in the same thread.
BR
Paulo -
Hi all.
I am using line item settlement. using investment projects.
Unable to generate the settelemnt rule for the lower level WBS elements. while settling from WBS to AUC
1. Created project (throught AR) with one one level WBS element (top level), planned cost, released budget, posted actual. now while doing settlemnt, i am able to generate settlemnt rule for top level WBS element automatically and settlemnt is done.
2. Created project (throught AR) with TWO level WBS elements (top level and 2nd level), planned cost, released budget, posted actual and while doing settlemnt, i am unable to settle, as system is asking me to maintain settlemnt rule for the 2nd level.
is there a way to generate settlemenmt rule for 2nd level automatically, as i have mainitained settelemnt strategy 40, to take the settlement rule from superior WBS.
i have checked it with CJB2 also, and it giving an error ORB501.
regards
Edited by: Surya Pampana on Oct 12, 2010 12:25 PMThanks for all the inputs.
Ahmed, i have implement the note 211323 and its relevent notes, still not working.
Ok, if i have to maintain settelemnt rules manully, how to maintain at level 2.
FYI: both level 1 and level 2 are account assigned
Now i have to maintain the settelment rule for 2nd level as : from level 2 to level 1?
pls suggest
Regards
Surya -
Settlement rule does not exists in order number.
Hi All,
I have been recieving a error while trying to save the Production order. The error reads as "Settlement rule does not exixts in order". But fact is that order has settlement rule. Also there is a default setting done in order type settlement profile because of which settlement rule is created automatically.
Now there is a way around. We calculate cost manually and then we go to settlement rule and check for error. Once we do so the order is good to save.
But we are not able to save it automaticaaly after release. This issue occurs when we try to release the order and then after releasing the order we try to save it.
Please help us on this issue.Hi Prabhakar,
Thanks for your input. But the said setting was already done while implementation. All the material except this material has the issue. We are able to realease the order properly for the material except this one. And since go live we are using this material for first time.
We did a work around. We copied this material and recreated a new material with reviced part number. That one is working fine in lower client. We have now no idea how could one material all the same data like material master and routing and BOM and work centers can work properly whicle failing for other.
We are trying to debug this will let you all know if we find the solution. Till then if you all have any idea any prior experience, please let me know. -
For internal order settlement rule amount column is requied instead %
Hi Gurus,
For internal order settlement rule percentage is there but business wants to settle from AUC to final asset by amount wise how can we do this.
I tried to change the investment profile but it is coming amount field while saving it is not displaying.
Please help in this regard
Thank you.
RanganadhHi
Check the path
IMG>Controlling>Internal Orders>Actual Posting>Settlement>Maintain Settlement Profile>Maintain Settlement Profile.
Here there is a tick for amount settlement under Indicators. You need to maintain this check box for your requirements.
Regards
Sanil Bhandari -
AUC and settlement rule mismatch.
Hi,
We have created many AUCs while uploading initial data at the time of go-live by posting JVs on WBSE and then performing the settlement. Now due to some currency issues we have reversed all settlements, and then Asset accounting person has resetted the asset register.
now when I am trying to create AUC from CJ20N, system creates AUC and provides the number. but this newly generated AUC number is not matching with the AUC in settlement rule. I can't delete the old settlement rule as the settlement performed on that. as well as I am not able to add new AUC in settlement rule.
Please let me know if there is any program / tcode which can remove this inconsistency. or is there any other procedure to make it streamline.
Please help.
Regards,
Nilesh.Hi,
There is no error message in this case.
The scenario is like:
I have one WBSE and AUC is created for this WBS. for example AUC number is 1. the WBSE is released and some cost has incurred on it. during periodic settlement the cost is settled on the AUC.
Now the Client FICO team observed that the asset accounting is wrong due to currency conversion problem, so FICO team decided to reset the asset register and upload the entire master with new corrections. this will reset the AUCs as well.
so i reversed the settlement done on AUC and got the cost back on WBSE.
FICO team has resetted the asset register and all AUCs got deleted.
Now the issue is: WBSE is having AUC #1 in settlement rule which can not be deleted as settlement is carried out on this rule.
But when I create new AUC for WBS it is being created as some different number, (lets say #7) so even if now I run settlement the settlement will be done on AUC #1 insted of #7 even though #1 belongs to some other WBSE now in new scenario.
I hope I have clearly mentioned the issue.
Regards,
Nilesh -
Error: Maintain settlement rule of the sender for a higher level WBS
Hi,
I dont want to maintain the settlement rule for a higher level WBS. How can i configure this in such a way that i dont get the following error:" Maintain settlement rule of the sender" while doing CJ88. Maintaing a separate Settlement profile for a higher level WBS is an option but we are looking if something else could be done The problem is that there are no actuals booked against, say, level 2 WBS but when i execute CJ88, i get the aforesaid error. How can i ensure that only the lowest level WBS ask for the settlement rule and not the levels above it. I have already removed the Investment profile from the higher level WBS but still getting the same error.
Regards,
DPilHi,
It is a type Capex WBS and Biling element is not checked. In fact i get a warning while doing the settlement: WBS is neither a billing element nor an account assignment element.
Diagnosis
WBS element is not indicated as either an account assignment element or as a billing element in the master record.
System Response
The WBS element cannot be assigned to an account.
Procedure
Correct your entries or add the missing indicator to the master record for the WBS element.
But this is just a warning. On pressing enter i get the error :Maintain settlement rule of the sender " -
Hi,
I am facing as issue while settling costs to internal order. The system is giving warning message "Enter a percentage, equivalence number, or amount"
Diagnosis
You have entered at least one distribution rule which contains neither a percentage nor an equivalence number nor an amount.
Procedure
For each distribution rule, you must enter either a percentage, an equivalence number or an amount.
Alternatively, and depending on the situation and how you want the system to behave, one of the following is possible or required:
You want to enter the percentage, equivalence number or amount later.
You can ignore this warning. However, you should check that the appropriate values are entered before settlement.
You want to enter a percentage, an equivalence number, or an amount. However, the relevant field will not accept input, or is not displayed.
Go to the settlement profile you are using and check that one of "Percentage settlement", "Equivalence numbers", or "Amount settlement" has been switched on. You can find out which settlement profile you are using from the "Parameters" section of the screen in settlement rule maintenance.
(Press F5 to proceed to customizing.)
You receive this message other than in settlement rule maintenance - for example, when saving an order or a WBS element.
Go to settlement rule maintenance and check the individual distribution rules.
This error is coming only from past one week. Any pointers towards the resolution/ or the reasons for the error will be highly appreciated.
Regards,
S.SumanaHi,
On further analysis, we found that there was a settlement (in KO03) that took place without specifying percentage or equivalence amount. Is there anything that can be done like reverting the settlement so that this message doesnot appear.
Regards,
S.Sumana
Maybe you are looking for
-
Problem with wwsbr_api.modify_item and Text 8191 characters
Hi all. I have a PL/SQL portlet used to insert/update content in Oracle Portal. I noticed that if I try to insert or update a text item with data longer than 8191 characters it gives the following error: ORA-06502: PL/SQL: numeric or value error. Als
-
All Pages Docs scrambled after 10.6 Update
That means: formattings were changed, font spacing too tight or too wide etc., really ugly! Just as a test I opened a few old AppleWorks Docs (in AW, of course) ant they are fine. Luckily I could go back to 10.5.8 with TimeMachine for now - but I'd r
-
Command line exp status return
Hello I'm using a batch file with an export to backup my DB but I would like to receive an email if something go wrong, maybe even with the log file. How can I check if the exp fails? Thanks Ownr
-
Synchronous Messages persistence in XI
hi Can someone guide me through the steps require for monitoring Synchronous Messages persistence in XI? I believe we need to swtche on logging in XI.
-
Log dopo il riavvio: Incident Identifier: 0C578488-F96C-459E-B787-B5AFE7008316 CrashReporter Key: c61856f29e97da35d62d6affec18a94747794dbe Hardware Model: iPhone2,1 Date/Time: 2012-05-08 19:22:48.562 +0200 OS Version: iPhone OS 5.1.