Settlemnent rule for Non-Billable WBS at Level 2 .

Hi Folks,
We have the Finance related WBS at Level 2 one is billable & other is non billable WBS . As per the recommendation of SAP , we are generating the automatic settlement rule for Billable WBS at level 2 & all the below WBS ( which are non-billable ) & account assigned as Do not settle. ( settlemnet rule 90) .
This issue is creating a issue to the non billable WBS at level 2 created wherein we are not able to settlement due to the strategy followed as Do not settle ( Rule 90 ) for the Account assigned WBS element.
Is there any way we can settle the costs posted to the non-billable level 2 WBS to the reciever ?
Your advice to this issue will be helpful.
Thanks in advance.
Ramu

You can settle the cost of Non-billable WBSE to billable WBSE. and then from billable WBSE settle the cost to other reciever. for this to happen, you have to delete the settlement rule "do not settle" in non-billabe WBSE and write a settlement rule which settles to billable WBSE.

Similar Messages

Garnishment - Special Rule for Non-Exempt Amount

There is calculation scheme for each special rule for non-exempt amount. For example federal rule for support is 04. The calculation scheme for this rule has 2 lines with operation multiplication and subtraction; and operand F1 and DN. Can someone explain to me what each line means and the cumulative effect of both the lines?
Thanks for your help!!
BBC

Hi,
Line 1 = F1 * DN i.e. Field 1 from infotype (IT0195 field 1 for fed exempt as per table T5UGA config) is multiplied by Disposable Net (wage type /G00) and stores result in R1 (intermediate result field)
Line 2 = DN - R1 i.e. subtract intermediate result stored from line 1 in R1 field from Disposable Net (/G00 wage type) to output result as minimum limit defined for nonexempt amount.
You can verify same in UGARN CALC (Garnishment Calculations section) in schema.
Thanks,
Ameet

Ship to address required for non-billable items?

Hi
We are using order management but all our items are non-billable items. Orders are for Adverts in Magazines/Newspapers therefore not tangible items.
Is it mandatory to assign Ship-to address to all our customers? We are not doing any shipping. How is it possible to create customers only with Bill to Addresses?
Thanks

Hello,
I think it is no problem, just create customer like you want in test instance and test it or delete Ship-to address on sales order and book.
Remember that you have to add correct workflow to sales order type(without shipping)
Regards,
Luko

Capital Project Settlement Rule for lower WBS

Hello,
At my present client, for Investment projects the client want to settle top level WBS to AUC and capitalise it. So ideally the cost from lower level WBS should flow to top WBS. I am using substitution to remove investment profile from lower WBS.My concern is how do I auto populate the settlement rule for lower WBS to top WBS. I am aware about settlement strategy and OSS note 211324 (however dont want to implement this note)
The appraoch I am looking for is using "WBS_SETTLEMENT_RULE' BAdI . However this BADI calls for strategy and I could not maintain the required strategy (settlement to top WBS). Is there some BADI/Function module available which can be called for updating the settlement rules on lower WBS while saving or Release ? Can I make use of exits in Substitution?
Please let me know your opinions.
Thanks
Sarang

Thanks Virendra. I agrree the only approach is development. But I need to give inputs to my developer.
We tried with BADI "WBS_SETTLEMENT_RULE" but it didnt work as it calls strategy in configuration.
So I am checking for some other options for e.g "WORKBREAKDOWN_UPDATE" which is called during save or Fn modules K_SETTLEMENT_RULE_FILL or K_SETTLEMENT_RULE_SAVE which I can use. This is a client requirement to create AUC only at top level n all cost to be rolled up to superior WBS n then settle to AUC.
The other option I was thinking is of using exits thru substitution.
What will be the best approach?
Thanks
Sarang

Storage option for Non leaf level dimension members: Store vs Dynamic calc

Hi All,
What is the general rule regarding the storage options for non leaf level members? My understanding is that it should be Dynamic Calc under normal circumstances and have it as store if we are going to load data at non leaf level. Is this correct? Are there any other considerations while defining the members?
Thanks and Regards,
Amol

Don't forget to consider whether the dimension is sparse or dense. Upper level dynamic calcs generally work well on dense dimensions as long as you aren't entering data into upper level members. Upper level dynamic calcs in a sparse dimension CAN work well, but usually only on smaller dimensions. This really depends on what else you have going on in your cube. On large sparse dimensions, upper levels are almost always stored, but this is one of those areas where you can sometimes bend the rules.
Also, don't forget to consider the calc order implications of making something stored or dynamic.
- Jake

Config for Cost & budgeting at activity level and WBS element level in PS

Dear GURU's,
please suggest me how to do the spro configuration for budgeting and costing, here my requirement is I need to do cost planning and budgeting at WBS element level and Activity level. We two deferent types of projects.
Regards,
Bha

Hi Bhanu,
Cost planning in projects can be done through two techinques:
I. Manual cost planning (at WBS level)
1. Overall planning (Struture-oreiented planning)
2. Detailed planning (Cost element planning)
3. Unit costing
4. Easy cost planning form
II. Automatic cost planning using networks and assigned orders
For customizing: Use transaction OPUV and enter the required entries for cost planning.
Budget can do only at WBS level. For configuration do the following steps:
1. Create Budget profile - OPS9
2. Assign Budget profile in Project profile - OPSA
3. Then allot budget to your project - CJ30
hope it will be very clear. Appreciate with point if it useful.
Thanks and Regards
vetrivelan

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á

Auto Run Program not updating Settlement Rules for few WBS elements

Hi,
Addition of settlement rules for OPEX WBS.
In producion system, two jobs are running daily for generating settlement rules of WBS elements but, all WBS elements are not updating with Settlement rules.
It is becoming a problem in the Period end while doing the settlement. Currently we are updating the settlement rule manually.
We have investigated and found the following WBS element with Profile name are not updating Settlement rule.
H-U0DU0204DE-EX-J0 - HHDC01
H-N0U00ULD01-P1-D1-W2 - 000090
H-U0DU0204DE-EX-U0-T1-OB - HHDC01
H-U0DU0204DE-EX-U1-W1-ON - HHDC01
H-U0DU0204DE-EX-U2-W1-ON - HHDC01
H-U0DU0204DE-EX-I0-E1 - HHDC01
H-U0DU0204DE-EX-I0-B1 -HHDC01
H-U1DU0204DE-EX-U0-W1-ON - HHDC01
Job Names :
ZFPD_UK_SETTLEMENT_RULE_GEN
ZFPD_NO_SETTLEMENT_RULE_GEN
Please suggest on this issue
Regards

Hi,
I suppose these are background jobs. Usually there is an issue with background jobs that are run for a custom developed program. Not sure why that happens. Even i faced this issue with a couple of jobs in my system. I have still not found out the reason as to why this happens. There might be a possibility that these projects were being processed in the foreground by some user and hence they were omitted from the run.
I would suggest you to consult your technical guys on this.
Regards,
Gokul

10:1 rule for skip - level aggregation

Hy.
I'm new in OLAP. I'm using AWM on 10gR2 and could somebody explain to me what does mean 10:1 rule. I know that is ratio of children to parent level which is 10:1, but example that i study doesn't show me that.
Example:
(from Oracle 10g documentation, data warehousing, OLAP Application Developer's Guide, part 7 Aggregating Data, Case Study: Aggregating a Moderately Sparse or Dense Cube)
SELECT COUNT(DISTINCT ship_to_id), COUNT(DISTINCT warehouse_id),
COUNT(DISTINCT region_id),COUNT(DISTINCT total_customer_id),
COUNT(DISTINCT account_id), COUNT(DISTINCT market_segment_id),
COUNT(DISTINCT total_market_id), FROM global.customer_dim;
Global is a very small data set, so few adjacent levels have the desired 10:1 ratio of children-to-parent dimension members. Table 7-4 and Table 7-5 identify the appropriate levels to be calculated and stored for the two hierarchies. Only eight members are stored out of a total of 45 aggregate members.
On the Summarize To page for the Units Cube, select the precalculated levels for Customer, and select all levels for Time, Product, and Channel.
Table 7-4 Precalculated Levels in the Customer Shipments Hierarchy
Level Members Precalculate?
Total_Customer 1 No
Regio 3 Yes
Warehouse 11 No
Ship_To 61 Yes
Level Members Precalculate?
Total_Market 1 No
Market_Segment 5 Yes
Account 24 No
Ship_To 61 Yes
If I use rule 10:1 child to parent member why Warehouse and Account doesn't have precalculate set to Yes If they have 10 or more child values below.
Please help!!!!

It is a long time since I used the global schema and at the moment I am using the BI common schema so I am trying to quote from memory here regarding the data. The figures you have outlined below are number of members at each level, a better calculation would be the average number of children that would be returned when drilling from one level to the next. In this case there are 3 regions and 11 warehouses, so drilling from region to warehouse is likely to return at most 4 warehouses on average.
To quote from the OLAP documentation:
This 10:1 rule is best applied with some judgment. You might want to permit a higher
ratio for levels that you know are seldom accessed. Or you might want to store levels
at a lower ratio if you know they have heavy use.
The key for pre-aggregation is understanding expected usage patterns of your users. In this case for the global schema I expect it is optimised for demo purposes and the levels that are precomputed are those most likely to be used in a demo.
In your case you need to understand where your users will most likely start there analysis and make sure that combination of levels is precomputed to ensure fast response times for the first query and then monitor usage patterns and get feedback from users over time.
If you are using Discoverer OLAP Plus client you could export the Discoverer catalog and analyse the XML for each report to determine which values are being created. I don't think there is an easy way to monitor OLAP queries at the moment (I could be wrong but I have not seen anything in Enterprise Manager that would help in this area). You could quickly create a program in PL/SQL or OLAP DML that would help analyse the XML for Disco reports. If you are using BI Beans you can scan the XML from the BI Beans catalog for each report.
For the OLAP Spreadsheet Addin it might be necessary to create a program to scan the $V_SQL/V$SESSION tables to work out which data points are being requested by users.
Of course you could just try pre-computing every other level which I think was/is the default aggregation plan generated by OWB and AWM.
Hope this helps
Keith

Typing rules for assigning non-wildcards to wildcards

Hi all,
I have the following code:
public class A<T extends Number> {
     T t;
     public void foo() {
          Number number = null;
          Integer integer = null;
          A<? extends Integer> a1 = null;
          A<? super Integer> a2 = null;
          a1.t = null; // OK
          a1.t = integer; // Error
          a2.t = number; // Error
          a2.t = integer; // OK
}The code contains four assignments of a non-wildcard type to a wildcard type. Two of them are correct, two are wrong. Now, intuitively, the following rules seem to hold for such assignments to upper/lower bounded wildcards:
- Only the null-type can be assigned to an upper bounded (or unbounded) wildcard.
- A non-wildcard type can be assigned to a lower bounded wildcard iff it can be assigned to the wildcard's lower bound.
I think that the rules are quite intuitive but I would be interested in finding the formal typing rules for such assignments in the JLS. Can anyone provide a reference into the
JLS which which cover the semantics of the above assignments?
Any help would be really appreciated. Thanks a lot in advance!

kablair & dannyyates,
first of all, thanks a lot for taking you the time to explain the things to me that clearly! Sorry also for the somewhat confusing example by having chosen the final class Integer which is some kind of a special and limiting case.
In any case, I have gone through the JLS yesterday as I was particularly interested in the role of capture conversion to formally explain the correctness of the above code and here are my conclusions I want to share with you: Actually, there seem to be no subtyping rules for wildcards because you always apply capture conversion (JLS3 5.1.10) to wildcards before looking for their subtype relationship to other types. Capture conversion converts each wildcard to a new fresh synthetic type variable which has appropriate upper bounds and also a lower bound. Now, in the very last sentence of section 4.10.2 of the JLS3, it is stated that a type variable is a direct supertype of its lower bound which I think is the key point. This means that you can assign something to a type variable iff you can assign it to its lower bound.
Now, capture conversion converts every unbounded or lower bounded wildcard into a type variable which has the null type as its lower bound. This formally shows that you can really just assign null to them as in the code above. Contrary, every lower bounded wildcard is capture converted to a type variable whose lower bound is the lower bound of the wildcard. So, again, you can assign it every type you can assign to that lower bound. This is also reflected in the above code.
So, that's maybe the formal explanation for something which is intuitively clear anyway...

Mass deletion of settlement rules for few WBS- Codes

HI All,
I just want to know that is there any possible way to delete settlement rule in mass.
We use to upload the settlement rule data through LSMW program for all the project codes.By mistake the user has excuted twicw the LSMW program and now instead od having one settlement rule now they have two settlement rule assigned to the project code. thats is the second rule is duplicated.
now the user wnats to delete those second settlement rule which got duplicated for all the WBS codes. nearly there will be 6000 records are there which got affected by this.
No entries has been posted to those WBS codes till now.
Kindly any one suugest me how to proceed further to resolve this issue.
Regards,
Joby

Hi,
In customization, use the strategy with "No Receiver" and then use transaction CJB1/ CJB2 to automatically generate the revise settlement rules without receiver.
Regards,
Gaurav

Project Status Report using CATSPS. Billable/Non-billable Hours?

I am working on a Project Status Report and am using CATSPS table instead of CATSDB table since thatu2019s the cross-application table for PS module. But I am facing a small problem in using CATSPS table. There is no field in CATSPS table that tells me if the hours are billable or non-billable. Table CATSDB had a field u201CBill Typeu201D (Billable/Non-Billable) but I donu2019t see anything like that in CATSPS. If I use CATSDB table and filter out status "30" for only approved hours, I am getting duplicate entries for actual hours in Crystal Report 2008. What is the correct table to be used in this case and also what is the mapping field(s).
Also, looking to display the billing type for the document in VBRP table. I am able to display the document type code but not the description itself. Which table will have this mapping?
Also, in Crystal I have the total Purchased hours at the 3rd level WBS but the total actual hours are coming from the 4th level WBS (Activity level). Each 3rd level WBS can have multiple 4th level WBS (difference networks). How do I know (logic) which 4th level WBS total to pick up and add to which 3rd level WBS total? Also, how do I display the total actual work hours form the 4th level WBS to display at the 3rd level?
Here is an example:
WBS , Level , SKU# , Network# , Activity# ,   Purch. Hours , Act. Bill. Hours , Remaining Hours
EP-2927-AMB-0001 , 3 , 600-310-100000 , N/A , N/A , 100.00 , N/A , 55.00 (=100.00 - (30.00+15.00))
(Purchase Hours from this line) - Total Act. Bill. Hours from level(s) 4 below: A+B)
EP-2927-AMB-00011 , 4 , N/A , 000004008303 , 10 , N/A , 5.00 , N/A
EP-2927-AMB-00011 , 4 , N/A , 000004008303 , 20 , N/A , 6.00 , N/A
EP-2927-AMB-00011 , 4 , N/A , 000004008303 , 30 , N/A , 15.00 , N/A
EP-2927-AMB-00011 , 4 , N/A , 000004008303 , 40 , N/A , 4.00 , N/A
(A)    Total Billable Hours = 30.00 (5.006.0015.00+4.00)
EP-2927-AMB-00012 , 4 , N/A , 000004008304 , 10 , N/A , 6.00 , N/A
EP-2927-AMB-00012 , 4 , N/A , 000004008304 , 20 , N/A , 4.00 , N/A
EP-2927-AMB-00012 , 4 , N/A , 000004008304 , 30 , N/A , 5.00 , N/A
(B)    Total Billable Hours = 15.00 (6.004.005.00)
If you notice there are two level 4 WBS (EP-2927-AMB-00011 & EP-2927-AMB-00012) in this example that are under level 3 WBS (EP-2927-AMB-0001). The Purchased Hours are coming from level 3 which means the hours are assigned per project at the WBS 3 level. Within each project there are different activity levels where actual hours worked by each employee are coming from. I need to sum the actual hours from all the available level 4 WBS and bring them over to the corresponding level 3 WBS in order to calculate the remaining hours. My challenge is how do I know which level 4 WBS belong to which level 3 WBS since there are more than one level 3 WBS in a Project and each level 3 WBS can have multiple level 4 WBS?
Please advise.
Regards.
-Rohit
Edited by: RohitBora on Feb 27, 2012 8:40 AM
Edited by: RohitBora on Feb 27, 2012 7:27 PM

Hi,
My personal suggestion to you is try to describe problem very crisp and easy to understand so that you will get quick responses. Its very difficult to read and pin point what you are aksing and finally you will miss readers attentions.
As standard practice, hours planned at indiviudal activity level and actual costs posted on each indiviudal activity will roll up and display the aggregate values at corresponding higher WBS element level. At the same time system will let you know reamining hours at indiviudal level and not higher level as rolled up.
Your WBS structuure is bit confusing me, in what way you are encoutring problem in identitying level 3 and level 4 WBS elements. Key will clearly denotes which is level 3 and level 4. As cited by you, EP-2927-AMB-0001 this should be level 3 and EP-2927-AMB-00011 is level 4. I am sorry to say that structure key was not maintained proper way and bit confusing.
Regards,
PSR
Edited by: PSR on Feb 27, 2012 11:05 PM

Default Settlement Rule for Project Definition

Hi Viewers,
I am having the requirement that, when i create the project, automatically system should create the AUC asset in the project level.
I tried and I am able to make at WBS element level. I need at Project level.
I need help on this...
Regards,
Aswin

Hello,
In Customizing for the order type it is set that orders should be settled periodically (default rule PP2). However, this is not supported for subordinate orders in the collective order.
For this collective order, the system sets the default rule to PP1 regardless of the settings predefined in the order type. Then the collective order is subject to full settlement.
200060 - Periodic settlement in the collective order
Please check if you have any custom development for settlement.
If not then raise this to OSS.
Best Regards,
R.Brahmankar

Settlement rule for Asset Under Construction not automatically generated.

Hi Experts,
I am working on a capital project scenario where in i configured the SAP IM and SAP PS module. i am able to create AUC at the WBS level on project release,but i am not able to generate the settlement rule for AUC automatically.
Please suggest as to what i am missing to generate settlement rule for AUC automatically.
Thanks,
shiv

i think for automatically AUC to be generated, u need to create investment profile in OITA in that u have to tick mange AUC in investment measure. & select settlement for summary settlement.
This investment profile u need to specify in Project Profile OPSA.
do this setting & let me know whts happen?
ok best of luck.
Regards,
ANSAR

ECS: New Pricing condition for purchase order on item level

Hello Experts,
we use SRM 5.0 with the extend classic scenario.
We customized a new pricing condition (absolute discount), which we want to use in a purchase order and added it to the calculation schema.
condition type:
Application     BBP
Source system LOCAL
Usage           PR
Condition Type ZRBT
Access Seq.     01CT
Condition class       discount
Calculat. Type    fixed amount
Condit.category
Rounding rule commercial
manual has priority
item level
delete
amount/percent
UoM
Scale Base Type   quantity
Check stat             none
Max. No. Dimens    no scales
We see the condition type and can choose it in the transaction which is used to create a po.
But when we choose it from the drop-down box it isn't added to the calculation.
Regards,
Sven

Hello Sven,
Thank you very much for posting the OSS note solution for your issue.
I had similar issue and finally was able to resolve it after reading your post.
regards
Vinod

Settlemnent rule for Non-Billable WBS at Level 2 .

Similar Messages

Maybe you are looking for