Benefit cost calculation by removing cutoff dates;

Our client has benefit cost calculations configuration based on cutoff dates:
1.     Employee Cost : Use Age of  1st January of the current year and Annual base pay of  01 October  of the previous year(if the previous record does not exist , consider the current record) in the calculation of employee cost(EECST)
2.     01 st October  of the previous year annual base salary for calculation of employer credit
Now client wants to remove the cutoff dates and wants cost to be reflected in the benefit info type with the change of age and salary;
Iu2019ve tested the system by removing the cutoff dates in the configuration and here is the scenario;
IT 0168 validity dates 01.01.2009- 31.12.9999
Salary increase in info type 0008 : 01.08.2009
As when salary increased in the  0008 from 01.08.2009, cost and coverage amounts in 0168 changed as per the new salary in the existing record of IT 0168 from  01.01.2009;
When I run simulation payroll with forced retro from 01.01.2009, the new benefit cost which are due to change in the salary are getting calculated from  01.01.2009 instead of 01.08.2009;
But we want the new cost should take effect only from 01.08.2009; probably split in the infotype 0168 with the date of salary change or age change may be solution?
I can create this split in 0168 with dynamic action for salary change but I canu2019t do this for age changes;
Kindly advise us the better solution for this?

I worked out the solution as follows:
1. For the employee insurance plans I assigned wage type BSAL as the calculation base in the Payroll > Payroll:USA > Benefits Integration > Enter wage types for plans config step.  This wage type accumulates the wage types used to determine the base salary used in benefit insurance coverage rules
2. Update the wage type characteristics for wage type BSAL, (Personnel Management > Personnel Administration > Payroll Data > Basic Pay > Define Annual Salary > Wage type characteristics) setting the indirect evaluation module to ANSAL. 
3.  The indiect evaluation module ANSAL is where you assign the wage types that make up the accumulation wage type BSAL.  Assign the wage types that make up the BSAL accumulation wage type in Personnel Management > Personnel Administration > Payroll Data > Basic Pay > Define Annual Salary > Relevant wage types for annual salary valuation. 
4. In my case the wage types assigned to BSAL are the basic pay salary wage type and an additional payments (IT0015) wage type.

Similar Messages

  • Benefit cost reporting in ad hoc query

    Is it possible to use ad hoc query to report on future dated benefit cost changes?  I have tried several different ways but have not been successful.
    I tried changing the date of the reporting period to match that of the effective date for the benefit cost change but the system still outputs the old costs.
    I also tried using the benefit cost calculation date as a selection field and then enter the effective date for benefit change but that did not work either.
    Does anyone have any insight?  Thanks in advance for your input!

    Did you ever find an answer to your question?  I am having the exact same issue.  Unless a new infotype is saved with the dates that coincide with the cost configuration change, I cannot report on the new cost via Ad hoc or SAP query.  The only thing that works is the standard health plan cost report but my users prefer to use query so they can get every field they need.

  • Is there any API to update cost cutoff date?

    Hi All,
    Is there any API to update cost cutoff date?

    Hi,
    As per Oracle we have below APIS for locator in WMS,
    - Create Locator API to create a new locator (CREATE_LOCATOR)
    - Update Locator API to update an existing locator (UPDATE_LOCATOR)
    - Locator Item Tie API to assign an item to a locator (CREATE_LOC_ITEM_TIE)
    - Delete Locator API to delete an existing locator (DELETE_LOCATOR)
    The APIs are part of PL/SQL package INV_LOC_WMS_PUB. This is defined in
    $INV_TOP/patch/115/sql/INVLOCPS.pls.
    You can search *"Locator Maintenance Application Program Interface"* in Metalink or MFGAPI for details.
    Hope it helps
    Kind Regards,
    S.P DASH

  • Benefit costs changes year after year impact

    Dear SAP gurus,
    I am involved in benefits implementation now and as part of the implementation, I have the following query and request your expert guidance to help me solve the issue.
    The benefit costs are changed year after year.  If an employee enrolls into a benefit during the previous year, the costs for that year are featuring in the BN infotype.  When the costs are changed for the subsequent year, the EE continues with the same benefit options hence there is no changes done to his benefit inofytpe.  The end date is end of period.
    Now for this current year, how will  the new costs be displayed in the infotype.   Is there any process that should be followed in these cases.
    Request your expert opinion on this.
    Thanks
    Lakshmi

    Benefit costs are dynamically calculated and not store in the infotype record. Please note for Pension plans in Ifotype 169 you must update the records if the percentage or the amount changes, as these are stored in the infotype record.
    You don't have to update the record in 167 and 168. However, there are some implications in payroll. Please check how these infotypes are processed in payroll if payroll is implemented as well. Consult with the payroll group with regards to how these premiums are to be reflected in payroll in the period where the premium chnage is effective. You will have the complete picture of what may be required to be done in benefits in terms of what the effective date of the configuration change will be and or if you may require to update the records in infotypes 167 or 168

  • SSAS Multidimensional Time Intelligence YTD calculation showing BLANK for Date level

    Hi there,
    I am working with SSAS Multidimensional Cube, basically I have defined a Time Intelligence calculations for just YTD in the Cube, the calculation was created in the Calculations tab of the cube as follows:
    /*Year to Date*/
        [Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Year to Date],
    [Dimension Dim Time].[Year].Members, 
        [Dimension Dim Time].[Date].Members   
      =
      Aggregate(
                 { [Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Current Dimension Dim Time] } 
                 PeriodsToDate(
                                [Dimension Dim Time].[Calendar].[Year],
                                [Dimension Dim Time].[Calendar].CurrentMember
    My Calendar hierarchy is as follows:
    Year -> Quarter -> Month -> Week -> Date
    The problem I have is that when I am at Date level I am not getting the cumulative YTD value, instead I am just getting blank cells:
    Could anyone help me defining a Time Intelligence YTD calculation that works for all levels including the Date (highlighted in yellow above)?
    Thanks and best regards,
    Joss

    The only strange thing is the MDX script, I would have used this one instead (sse below) - but if this is not the issue, I would suggest you to isolate the issue in a simpler MDX script removing any other calculation.
    Also take a look at the DateTool solution for these calculations - I really don't like the wizard provided by the development environment, it has other issues but not something that should affect your calculation:
    http://www.sqlbi.com/articles/datetool-dimension-an-alternative-time-intelligence-implementation
    /*Year to Date*/
        [Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Year to Date],
        [Dimension Dim Time].[Calendar].Members, 
        [Dimension Dim Time].[Date].Members   
      =
      Aggregate(
                 { [Dimension Dim Time].[Calendar Dimension Dim Time Calculations].[Current Dimension Dim Time] } 
                 PeriodsToDate(
                                [Dimension Dim Time].[Calendar].[Year],
                                [Dimension Dim Time].[Calendar].CurrentMember
    Marco Russo http://ssasworkshop.com http://www.sqlbi.com http://sqlblog.com/blogs/marco_russo

  • Shipment Cost Calculation

    Dear All,
    I know that tariffzone plays a role in determining the price for the freight/Service Agent condition in case of outbound shipment cost calculation
    I have the following query in Shipment Pricing.
    Can anyone please explain whats the role of the 2 postal code columns in the tariff zone assignment?
    Also how & where I have to maintain the data for determining the tariff zone which I have assigned to the above combination.
    Please help.
    Regards,

    HI Dave,
    Thanks for the response.
    Please note that I have maintained postal codes in my Shipping point also in my customer master.
    For the combination of TP Point, Service agent, Shipping type & Country I have made the following assignment.
    I have given my shipping point Postal code in both the Postal code columns of Tarff zone assignment (say Tariff) & my customer master Postal code in both the Postal code columns of Tariff zone assignment (say Tariff1).
    Now I have maintained the condition records in TK11 for the combination of Depart. Tariff zone/Destn.Tariff zone/Service Agent i.e. Tariff/Tariff1/Service Agent
    But my condition record value is not getting determined & when I simulate my shipment cost I am getting the following error message.
    Shipment costs not yet calculated
    Shipment costs item 000001 w/ ref. to doc. $0001 item 0001
       Message no. VY104
    Goods types directory could not be determined
        Message no. VW803
    Please help to reolve this issue.
    Regards,

  • Weighted avg Unit Cost calculation for COGS

    Hi friends,
    Has any body done weighted avg unit cost calculation for inventory valuation and COGS calculation. In a way we need to mirror ECC material ledger functionality based on the APO data in side the planning tool.
    Any ideas on the above!!!
    Kind Regards,
    Krish

    Hi Jerry,
    Thanks for the tip. I actually needed to clean the spreadsheet up and put bogus values in to comply with company policy. Anyhow, here is a sample of the spreadsheet
    http://dl.dropbox.com/u/7499586/junk.png
    Just imagine about 100 products and several hundred raw materials, a dozen types of labor and about 30 types of packaging. It's a monster spreadsheet.
    The "units" under each product is the number of units per batch. You can see each product has two columns. One where you put in how much of a raw material, package type, and labor type go into each batch, the next calculates the cost for each item. Then it gets summed at the top for the total unit cost for that product.
    Let me know if you have any other questions about it. Thanks so much for your help!

  • Benefit costs stored on IT0167

    When we enroll a biweekly person into their benefits using PA30 (as in an ecatt) it saves the benefit costs period as biweekly.  We need this to be monthly.  When we use benefit enrollment it saves correctly as Monthly.  We have been able to enroll using PA30 in the past and have it default correctly to monthly.  We have tried tofind how to change this default but have been unsuccessful to date.  Does anyone know how to make this field default to Monthly for all payroll areas even when using PA30 to enroll the person?  Thanks.

    All of the appropriate Benefits and Payroll pieces are configured.  What is different is that in the past, when using PA30 to enroll Biweekly employees the time period saved on IT167 for the costs indicated the Monthly amount.  Now it saves Biweekly.  But if we use the Benefit enrollment process (HRBEN0001) it saves a Monthly amount on that infotype which is how we want it to work when using PA30.
    We understand when viewing this infotype we can change it to Monthly and see the correct monthly cost.
    The problem is that when we use SQ01 to report out the cost for Biweekly employees, the cost is reflected in the Biweekly amount and not the Monthly amount.
    We cannot determine how to make the Biweekly cost reflected on IT167 indicate Monthly when the employee is enrolled into benefits using PA30.
    Thanks.

  • Standard Cost Estimation Functionality removal from S.O.

    Hi Friends,
    I would like to know, is in SAP system there is an option to remove funcionality of auto Stadard cost Estimation i.e. we don't like to make Standard cost Estimation at the time of Sales order creation.
    Can you Please tell me about this feature.
    Rgds, Krishan Raheja.

    Hi,
    I am talking about the Cost Estimation happens, as it shows the cost via menu path---> Extra --> Costing. Further, the system will make the accounting entries for consumptions/Receipt w.r.t. to cost calculated vai this estimation. VPRS condition is not having the same prices as calculated in Costing. Further, the stock will also remain with same prices as calculated in price.
    Can you please suggest, if there is any option, so that we can omit this costing calculation and system make consumption/receipt entries with the values in material master.
    Rgds / Krishan Raheja.

  • Delivery cost calculation solution in SRM 7

    Dear all,
    We have a requirement to capture delivery costs associated purchases made via SRM. We would like to know if itu2019s possible to achieve the two scenarios indicated below. And if so, where and how do we enable delivery cost calculation process for SRM generated POs?
    Here are the 2 scenarios/requirements:
    Scenario 1.
    Shipping costs pre negotiated before a shopping cart is raised. When the PO vendor sends an invoice, shipping costs appear on a separate. We need a functionality to automatically calculate and add/capture these delivery costs to the SRM based PO and have the ability to match/pay for this when the vendor invoices.
    Scenario 2.
    Delivery costs such as fright costs are not know at the point the SRM PO is created. The PO vendor invoices only for goods that he delivers. Freight costs/charges have to be paid to another vendor - e.g. DHL. We need a functionality to automatically add/capture these Freight costs to the SRM based PO and have the ability to match/pay both the PO and Freight Vendors when they submit their invoices.
    Thanks in advance.

    Dear Poster,
    As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
    Best Regards,
    SDN SRM Moderation Team

  • Shiment Cost Calculation Rules

    Hi Gurus
    Can you please provide me details of configuring Shipment Cost Calculation Rules?
    Thank You

    Hi Brajesh,
    Is the following rules you are expecting?
    Determining the Calculation Basis  
    Use
    The origin of the data upon which a condition type is based during shipment costing determines the calculation basis. During shipment costing, the system determines the shipment cost items from the different calculation bases for the condition types of a pricing procedure. Shipment costing itself is carried out for each sub-item.
    Prerequisites
    You must maintain a suitable calculation base in the definition for the condition type in Customizing.
    If you select handling units as the calculation basis, you must also specify the packaging material type so that only the relevant handling units are used for shipment cost calculation.
    Features
    The calculation bases are determined during shipment costing for a shipment cost item on the basis of the settings made in the condition type.
    During pricing, the calculation base influences
    The condition types to be considered for each sub-item
    The information available for determination of the conditions
    All condition bases contain information from the shipment header or shipment stage, as well as from the shipment cost item. This information includes service agents, geographical information (point of departure and destination) and shipping type, for example.
    How the scale base types (gross weight, net weight and volume) are calculated
    The following types of calculation bases are possible:
    Deliveries
    If condition types with this calculation base exist in the pricing procedure, then the system creates a shipment cost sub-item for every relevant delivery.
    No information from the delivery items (such as materials) or the handling units is available.
    The scale base types (gross weight, net weight, volume) refer to the corresponding information from the delivery headers.
    Delivery items
    If condition types with this calculation base exist in the pricing procedure, then the system creates shipment cost sub-items for every relevant delivery item.
    Information from the delivery header and the relevant delivery item is available. There is no information from the handling units, however.
    The scale base types (gross weight, net weight, volume) refer to the corresponding information from the delivery items.
    Group of Handling Units
    If condition types with this calculation base exist in the pricing procedure, then the system creates shipment cost sub-items for the sum of all identical handling units with the relevant packaging material type (also specified in the condition type).
    There is no information from the deliveries or the delivery items available.
    The scale base types (gross weight, net weight, volume) refer to the corresponding cumulated information from the relevant handling units.
    Shipment cost item
    If condition types with this calculation base exist in the pricing procedure, then the system creates exactly one shipment cost sub-item.
    There is no information from the deliveries, the delivery items or the handling units.
    The scale base types (gross weight, net weight, volume) refer to the corresponding information from the relevant delivery headers.
    Per handling unit
    This calculation basis corresponds to the calculation basis handling units, with the only difference that each handling unit is calculated individually. This calculation base is necessary for shipping packages, for example.
    Handling unit including delivery item
    If condition types with this calculation basis exist in the pricing procedure, then the system creates a shipment cost sub-item for every packaged delivery item and handling unit (per combination of delivery item and handling unit). Shipment costs are therefore calculated with content depending on the handling unit.
    All of the information from the handling units and delivery items is available.
    The scale basis types (gross weight, net weight, volume) refer to the gross weight of a handling unit per delivery item.
    All
    You can use this calculation base if, for example, you want to define a discount that applies to both delivery-related and handling unit-related shipment prices. A condition type with this calculation base can be used for every shipment cost sub-item.
    Several calculation bases may be used within a shipment cost item. In performing a shipment comparison, for example, the calculation could be performed using two calculation bases. You could then compare the results. See also Shipment Comparisons.
    For system load and clarity reasons, we recommend selecting a calculation base that is only as detailed as absolutely necessary. For example, if only the total weight and the transportation leg are relevant, the calculation base for shipment cost items is sufficient. However, you can still distribute the costs in greater detail. The cost distribution is independent of the calculation base. For example, you can calculate shipment costs using the calculation basis for shipment cost items and distribute the costs at delivery item level. The system weights the costs and distributes them accordingly.
    When defining the condition tables in Customizing (Logistics Execution ® Transportation ® Shipment Costs ® Pricing ® Pricing Control ® Define price dependencies (condition tables), you should make sure that information is not available for every field - depending upon calculation base. If, for example, you select the field Incoterms for a condition table when condition types with the calculation basis Handling units exist in the pricing procedure, there can be no information on Incoterms for the corresponding sub-item. This means that no condition records will be found for this key. For further information on the role of the condition table in pricing, see  Condition Tables.
    Please let me know your thoughts.
    Thanks nand Regards,
    Satheesh Durgi
    Edited by: Satheesh on Jan 25, 2011 1:01 PM

  • INVENTORY ORGANIZATION PARAMETER항목중 CUTOFF DATE의 기능

    제품 : MFG_CST
    작성날짜 : 2004-05-21
    INVENTORY ORGANIZATION PARAMETER항목중 CUTOFF DATE의 기능
    ===================================================
    PURPOSE
    Inventory Organization Parameter항목중 Cutoff Date의 기능에
    대해 기술하고자 한다.
    Explanation
    Cutoff date로 설정된 날짜 이전에 발생한 transaction에 대해서만 cost manager가 수행하면서 costed된다.
    만약, transaction date이 cutoff date보다 이후이면 cost manager가 수행되어도 uncosted된 상태로 남아있게 된다.
    적용방법>
    위의 이 기능을 Business적으로 적용하려면, Standard Cost를 사용하는 site에서 일정한 기간별로 Standard Cost Update를 수행하는 경우에 유용하다.
    즉, 일괄적으로 새로운 Standard Cost를 적용하고자 하는 future date를 입력해두면, 그 날짜 이후에 발생한 Transaction들에 대해서는 cost manager가 수행하지 않고 Pending된 상태로 있게 된다.
    다음 작업으로 standard cost를 변경하고, cutoff date를 new future date로 수정하면, Pending 상태에 있었던 transaction들이 cost manager에 의해 새로운 cost로 부과된다.
    Example
    Cutoff date : 2004-05-01
    Item : A , Unit cost : 100
    In MMT table,
    Item tranaction date quantity Unit cost
    A 2004-04-30 1 100 <== costed
    A 2004-05-01 1 NULL <== uncosted
    step 1) Unit cost was changed by standard cost update : 100 --> 200
    step 2) change Cutoff date to New future date : 2004-09-01
    step 3) run cost manager
    In MMT table
    Item tranaction date quantity Unit cost
    A 2004-04-30 1 100 <== costed
    A 2004-05-01 1 200 <== costed
    Reference Documents
    -------------------

  • Calculation of goods issue date in scheduling agreements with routes

    Hello together,
    i have a problem with the calculation of goods issue date in scheduling agreements when we use route, because the system ignore the days of transit.
    Example:
    We had customized the route 4711 with a transit time of 3 days. This route would be related to a scheduling agreement. But this setting has no influence to the calculation of the goods issue date for the schedules. The same happens with loading date and so on.
    Can anyone give me a tip, which setting is additional necessary?
    Regards
    Andreas Walter

    Hi,
    check the following settings
    1, Route determination Path : IMG>sales and distribution>Basic function>Routes>Route determination
    2, Activate the route Determination for your sales document type in following path :IMG>sales and distribution>Basic function>Routes>Route Schedule Determination-->Schedule with route schedule for sales document type
    3, Maintain Delivery scheduling and transportation scheduling in the following path:IMG>sales and distribution>Basic function>Delivery scheduling and transportation scheduling>Maintain Duration
    Regards
    Senya

  • Calculated Column with Null date end result needs to be text.

    Good Morning,
    I am using SharePoint 2010 and am trying to create a calculated column converting a date/time column to to show just a month and day.  Calculation is
    =TEXT([Anniversary],"m/d")
    This is to enable sorting on the month.  And this works fine except when there is no date entered in the "Anniversary" column.
    I have tried to modify the formula in this column to no avail.  http://social.technet.microsoft.com/Forums/sharepoint/en-US/0c9d5ae1-132a-4e02-8a91-c54708919d9a/show-calculated-date-column-as-null-when-there-is-no-date?forum=sharepointgenerallegacy
    I do not have access to modifying the code so have to work strictly OOB.  Any help would be greatly appreciated.

    I would think you could add an IF statement to verify if the text is null. So...
    =IF(ISNULL(TEXT(Anniversary, "m/d")), What we do when null, TEXT(Anniversary,"m/d"))
    Andy Wessendorf SharePoint Developer II | Rackspace [email protected]

  • Bom Component qty & WIP Quantity differ at Trget cost calculation

    Dear gurus,
    i am facing the problem with WIP at target cost calculation in REM.
    My issue is
    BOM Component qantity is 9.524 TO  and price is 2000 then total cost is  9.521*2000=19048.
    but in WIP Report kkas in WIP explation it takes input qty 9.52 T0 and price 2000 then total price is 19040.
    Difference is 19048 - 19040 =8
    and also when i am issuing actual qty i.e 9.524 in BOM then my price is 19048.00 ant at time of variance calculaton then quantaty variance as   9.52.0-9.524.0=-0.04  then 0.004*2000 =-8 
    Please suggest solution for this.
    Any OSSS NOTE Required
    any Quires please revert back
    REGARDS
    Avinash.pegarlawar

    Hi
    Rounding differences between target and actual values and quantities are not unlikely to occur and cannot always be avoided but can be minimized.
    Small prices and price unit of 1 are likely to cause more of these rounding differences..
    The actual credit is simply calculated as price * quantity. The target credit however is calculated during the variance calculation
    and based on the sum of all items in the itemization/cost components of the cost estimate and therefore more accurate.
    To avoid this I suggest to store the material price with a larger price unit, i.e. 1000
    Std cost release stores price upto 2 decimals and target cost calculation goes upto 3 decimals...
    Please check also the note 1265918 for more information to this topic.
    Regards
    Ajay M

Maybe you are looking for

  • Does Mixing 802.11n with .11g Devices Slow the Whole Network?

    Hi all, I'm considering buying the new Airport Extreme as I also have a new Macbook Pro that supports 802.11n. I also have a couple Airport Expresses on my network, and my question is this: Will the presence of the Airport Express units (which are 80

  • Droid Razr - too hot to touch

    Having several issues with my Droid RAZR, purchased in June 2012.  Current Android Version 4.1.2, Build Nbr 9.8.20-72.... Main issues are: Battery life - stays plugged in all day & takes about an hour to go from 100% battery to about 65% battery.  It

  • Strange error message that won't go away...

    ...and it also crashes Mail for me. The message goes something like this: *Some actions taken while the account "jim@{myemail}.com" was offline could not be completed online.* Mail has undone actions on some messages so that you can redo the actions

  • Confition type FRC1- how to get the change log,

    Hi, When  the condition type FRC1 automatically gets deleted (deletion flag),. and we are not able to see the change log for the same. how the Conditions are deleted. Or if at all any one has deleted, how to get the change log,

  • Background colour change for WebDynpro Application has to changed

    Hi All, One of my custom built web dynpro application background color has to be changed, is it possible to do that? Satish