on 2007 Aug 14 11:14 PM
Hi,
We are tiring to use RRB application in following scenario; I would appreciate if some one could let me know what would be the best way to configure so I will get expected result.
1) Create a sales order
a) Sales order is configured for manual pricing condition, so I can update manual pricing; along with price I have configured EK01 Condition type to capture cost.
2) I would like to book certain travel expenses in travel management and would like to capture that cost in sales orders EK01 condition type.
3) Steps performed to create this travel management document is as follows
a) Open Travel expense manager (TC : PR05) create new document
b) Update dates ( From date and to date)
c) Update Alternative cost assignment for entire trip as Sales order number, and line item number 10
d) Consider Exp Key, post certain cost and save the trip.
e) Please approve new trip number, settle that and go to transaction PRRW for posting.
f) Create new posting run, update required information and save it.
g) Once posting run got created then post this to financial document.
Now, my requirement is that whatever cost I have posted, I would like to capture this cost in EK01, and I would like to run RRB for this particular sales document.
I do anticipate, while executing DP90 or DP91 it should capture this cost and create a billing request. But in this scenario when I am executing same it is popping up error message that no Expenditure is available for this line item.
Iy any one need configuration document please let me know I will send.
I am not sure where we are going wrong, apart from this is we are missing something then your advice would be very appreciable.
Request clarification before answering.
Hi Mahaveer
Pl. follow the following steps and try.
This note contains the Customizing settings for the resource-related down payment processing.
Section I shows the required settings within the R/3 area Project System (PS).
Section II shows the settings for the R/3 area Sales and Distribution (SD).
The specifications do not refer to the credit memo process, that is, if instead of a debit memo request a credit memo request is to be created, since there are negative costs.
For Customizing of the credit memo process, consider
Note 983961.
Other terms
Integration of billing plan and resource-related billing document, DP90, DP91
Reason and Prerequisites
The functions/processes/restrictions of the resource-related down payment processing are given in Note 858702.
Note 213526 provides detailed information about the down payment processing without resource relation.
An actual account assignment object must be determined for the sales order item. On this cost object, the costs are collected and then posted as resource.
Consulting is necessary for the required Customizing in the R/3 standard system for the resource-related down payment processing.
Solution
Generally, the functions
Resource-related down payment processing
Down payment processing without expense reference
Resource-related billing without down payments
can only be used by means of the function of the billing plan (milestone billing).
Most of the following data is maintained in the standard Customizing and can be used as a copy template.
I. Customizing in PS (Project System)
Project System/Revenues and Earnings/Integration with SD documents/Creating Quotations and Project Billing
o Maintain Profiles for Quotation and Billing
- Transaction: ODP1
Assign sales document type L2 to the DIP profile BILLPLAN.
o Configure Integration of Billing Plan and Resource-Related Billing Doc.
- Transaction: ODP11
Assign sales document type for down payment request (Sales) L2DP and
sales document type for billing request L2DM
to DIP profile BILLPLAN and select indicator
'Billing Plan Active'.
o Maintain cost condition for the sales document type
- Transaction: ODP4
Assign condition type EK01 to the sales document types L2DP and L2DM.
o Define Condition Type for Fixed Price in Billing Plan
- Transaction: ODP14
Assign condition type AZFP to the sales document types L2DP and L2DM.
With these Customizing settings, the DIP profile is extended and the resource-related down payment processing function is activated.
II. Customizing in SD
1. Sales and Distribution / Sales / Sales Documents / Sales Document Header
o Define Sales Document Types
- Transaction: VOV8
Create sales document type TAF, L2DM and L2DP.
2. Sales and Distribution / Sales / Sales Documents / Sales Document Item
o Define Item categories
- Transaction: VOV7
Create item category TAF and L2W.
For item category TAF, define billing relevancy I
and DIP profile BILLPLAN.
For item category L2W, define billing-relevancy C
and DIP profile BILLPLAN.
o Assign Item Categories
- Transaction: VOV4
Assign sales document type TAF to item category TAF.
Assign sales document type L2DM and L2DP to item category L2W.
3. Sales and Distribution / Basic Functions / Pricing / Pricing Control
o Define Condition Types
- Transaction: V/06
Create condition type AZFP.
For this condition type, define the condition class PRICES, the calculation type FIXED AMOUNT and for manual entry C (the manual entry has priority). Do not define an access sequence. However, set the condition as GROUP CONDITION.
With these settings, the value for the item is not copied from its billing plan, but rather the value is distributed in percent according to the costs.
o Define and Assign Pricing Procedures
- Transaction: V/08
Maintain pricing procedure RVAA03.
The condition type EK01 and AZFP is contained in this pricing procedure.
Define document pricing procedure F and assign to sales document types TAF, L2DP and L2DM, as well as to the billing type FADP.
Define pricing procedure determination.
Assign pricing procedure RVAA03 to the document type F.
4. Sales/Billing/Billing Documents
o Define Billing Types
- Transaction: VOFA
Create billing type FADP.
Copy the billing type FAZ with billing category P.
o Maintain Copying Control for Billing Documents
- Transaction: VTFA
Copying requirement between sales order TAF and down payment request FADP
Fixed down payments: 20
Copying requirement between sales order TAF and (partial/final) invoice L2
Fixed invoice: 23
Copying requirement between down payment request (sales) L2DP and down payment request FADP
Resource-related down payments: 37
Copying requirement between billing request L2DM and
(partial/final) invoice L2,
if no down payment clearing is to occur
Resource-related invoice: 38
if a down payment clearing is to occur
Resource-related invoice: 37
5. Sales/Billing/Billing documents/Billing Plan
o Define Billing Plan Types
- Transaction: OVBO
Maintain billing plan types for milestone billing
Use billing plan type 04.
Copy the billing plan type 01 for milestone billing.
An own date category is not necessary - date category is 01.
o Maintain Date Proposals for Billing Plan Types
- Transaction: OVBM
Create planned reference using the 'Maintain dates' button with down payment date: Billing rule 5 and billing type FADP
(The use of billing rule 4 is not possible.)
o Assign Billing Plan Types to Item Categories
- Transaction: OVBR
Assigning billing-relevance I and billing plan type 04 to item category TAF.
reward points if u satisfied.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi mahavir,
I hope you have completed the following before running DP90
1. Configured DIP profile in ODP1
2. Configured your item category and attached the DIP profile to your item category.
If so, then if you need to ensure that you have the pricing condition EK01 in your pricing procedure.
Once this is configured, you can run DP90 and it will create the debit memo request for the cost incurred.
Please let me know if you need any more clarifications.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
39 | |
8 | |
5 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.