cancel
Showing results for 
Search instead for 
Did you mean: 

PS-SD Billing scenario

Former Member
0 Kudos

Hai,

I have a scenario in a construction Industry,Where for the construction of a commercial complex, a contract has been signed between the customer and the project management concern.In the contract the concern has defined a unit rate for every activity say ,there might be excavation, footing e.t.c and these are maintained as seperate line items in the contract.Suppose in the contract if i have defined a unit rate say 150 US dollars per cubic meter of excavation activity.And i have planned a total of 100 cubic meter excavation,at the end of first period i have completed only 60 cubic meter and i have to generate the Bill to customer for 60x150=9000usd.But for me in the project system i have defined a unit rate of 120 Us dollars for the same excavation activity so my actual costs in the project will only be60x120=7200usd.How to make this scenario work in he system.For your information i tried out this with DIP profile and DP90[RRB billing request] but in my request the cost is picked up from PS that is it generates the bill for 7200USD and not 9000USD as i have defined the source to be actual costs line items in the DIP profile.

Please help me in this regard...

thanks in advance.....

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ravi,

Try this method, in the pricing procedure define a new codition type and assign to the pricing procedure, but make sure that the condition type should set as only statistical and set the printing status as not printable for the customer. Take the help of the ABAP team to create a new requirment for the condition type where in it deducts the margin amount from the base price. I work for the cement company and we have used the same technique.

Reward point if the answer is helpufl.

thanks

regards

ravi

Answers (3)

Answers (3)

former_member227476
Active Contributor
0 Kudos

dear ravi

PS SD integration happens during Milestone billing...

Below is whole process-

Billing Plan for Milestone Billing

Milestone billing means distributing the total amount to be billed over multiple billing

dates in the billing plan.

As each milestone is successfully reached, the customer is billed either a percentage of

the entire project cost or simply a pre-defined amount.

During sales order processing, the system determines from the item category whether a

billing plan is required and, if so, which type of plan

The type of billing plan that is determined at this point is set up in Customizing and

cannot be changed in the sales document.

Billing plans for periodic billing and milestone billing plans for project-related milestone

billing have different overview screens so that you can enter data relevant to your

processing.

For example, for milestone billing, you must be able to enter data to identify the

individual milestones.

IMG configuration requires:-

1. Maintain billing plan types for milestone billing in OVBO.

2. Define date description in SM30 - V_TVTB.

3. Maintain Date Category for Billing Plan Type IN OVBJ.

4. Allocate date category in SM30 - V_TFPLA_TY.

5. Maintain date proposal for Billing Plan Type in OVBM.

6. Assign Billing Plan Type to Sales Documents Type in OVBP.

7. Assign Billing Plan Type to Item Categories in OVBR.

8. Define rules for determining the date in OVBS.

Milestone billing is typically used for billing projects, such as plant engineering and

construction projects. Such projects often include a series of milestones that mark the

completion of different stages of the work. In the SAP R/3 System, milestones are defined

in a network along with planned and actual dates for the completion of work. The milestones

are also assigned to the billing dates in the billing plan.

Each milestone-related billing date is blocked for processing until the Project System

confirms that the milestone is completed.

Delivery-relevant order items for which a milestone billing plan applies are billed on the

basis of the requested delivery quantity and not on the total of the confirmed quantities.

The connection between the project and the sales document item is made in the individual

schedule lines of the item. Each schedule item can be assigned to a network in a project.

To display the project-related data for a schedule line, proceed as follows:

In one of the overview screens of the sales document, select

1. Item -> Schedule lines.

2. Mark the schedule line and select Procurement details.

The following figure shows an example of milestone billing where only the Contract have

been billed :

Order Item Turbine 100,000

Billing Plan

Billing date Description % Value Billing Block Milestone Billing Status

01-10-94 Contract 10 10,000 - x x

01-03-95 Assembly 30 30,000 x x

01-04-95 Maintenance 30 30,000 x x

01-05-95 Acceptance 30 30,000 x x

01-06-95 Final invoice .. .. x

Network/Activities

Milestone Estimate Actual

Assembly 01-03-95

Maintenance 01-04-95

Acceptance 01-05-95

For each billing date in a milestone billing plan, you can specify whether the billing

date is:

1. fixed

2. Always updated with the actual date of the milestone

3. Updated with the actual date of the milestone, if the date is earlier than the

planned billing date for the date

rewards if it helps

siva

Former Member
0 Kudos

HI

our requirement is the price which is coming from DP91 in to debit memo request is same as amt. to be billed. i can add new condition type in pricing procedure and give some extra price like 20 or 30%. and bill it. but this extra price which is given in debit memo request should reflect it in DP91. bkoz we require it from PS point of view. in our project all the MIS are directly trigerred from PS.

My self Divyendra Purohit (SD Consultant) working with Ravi in this scenario.

Regards

Divyendra Purohit

Former Member
0 Kudos

Hi Ravi,

you can achieve the billing only through RRB.

You are correct that if you define source to be actual costs line items in the DIP profile your condition type will bring in the actual cost in the pricing procedure.

As you are getting the price through DIP so your DIP configuration is correct.

What you should do is keep this condition as statistical in your pricing procedure.

Now you go and define two different condition type and you assign them in your pricing procedure. The first condition type can reference your statistical cond type and you can keep the rate as 100% / 120% or 150% so it will give a higher price or the same price depending on what pricing condition record you maintain in VK11. (you can create VK11 records for material which should use this cond type). Normally, you may use this condition type for expense kind of materials like air ticket, hotel stay etc for which you can keep it as 100%. So it picks up 100% value from your statistical cond. type.

the second condition type can be called like Manual base price, in this case for all the materials which you use in DIP maintain a pricing condition record in VK11 as per your access sequence. Then this will pick price from condition record.

This will solve your purpose.

Thanks