ATO Model - Selling Price

Question on Calculating the Price of an ATO model - When we configure an ATO model, the * item so created will have a zero price for the Top model, the client’s requirement is to price the Top model by rolling up the price of each component of the BOM. Do you know how to roll-up the selling price for the top model on a Sales order line. They are on 11.5.10.
Appreciate any pointers, or ideas to achieve the same.
Thanks in advance.

Hi
Model item plus all optional items roll up for the Pricing. When you invoice, however the configured item will have Zero Price. You need to define the Price list with the below setup
Product Context: Item
• Product Attribute: ALL_ITEMS
• Product Value: ALL
• UOM: whatever
• Application Method: Unit Price
• Value: (or whatever default price you want to set)
In case you are happy with the answer please mark as Helpful or Correct Answer

Similar Messages

ATP FUNCTIONALITY NOT WORKING CORRECTLY FOR ATO Model

Guru's,
Currently I am facing issue in ATP Inquiry to arrive at schedule ship date, we have set up an ATO Model and its low-level parts for multi level ATP, including ATP rules, item attributes, bom attributes, and lead times and ATP check is based on planned output and enabled 24X7 plan.
When try to perform ATP inquiry either from ASCP/OM responsibility, Instead of showing complete drill down of material constraint at the part level, it "stops" at the model level and shows no availability until the inifinte supply timefence, then unlimited availability after that.
I was earlier able to view the complete ATP pegging details with ATP dates well within ITF, but however when we re run the plan to include additional SO the above behavior is observed.
Can some one help me to reslove the issue, as I am not sure what exactly which is triggering this behavior.
Thanks,

Thanks for the reply, but this note was not addressing the above stated issue. In this note for matched configuration, they are not able to view pegging else they are able to perform multilevel atp check.
Can anyone help me to reslove this issue.
Thanks
Edited by: user604737 on Jun 18, 2011 4:48 AM
Edited by: user604737 on Jun 19, 2011 11:50 PM

Closing stock with selling price

Dear Experts
I am using the below query to get the instock with value but its not giving option of datewise report.Can anybody modify my query so i can get Instock and value by datewise report.So any point i can see what was the instock and its total value.
SELECT T0.[ItemCode], T1.[ItemName], T0.[OnHand] as 'In Stock (TINS)',T1.[InvntryUom] as 'Pak Size', (T0.OnHand /T1.InvntryUom ) as 'In Stock (Carton or Pail)' ,T1.[CodeBars] AS 'Min Inventory', T2.[Price] as 'Selling Price', (T0.OnHand *T2.Price ) as 'Total',T3.[ListName] FROM OITW T0 INNER JOIN OITM T1 ON T0.ItemCode = T1.ItemCode INNER JOIN ITM1 T2 ON T1.ItemCode = T2.ItemCode INNER JOIN OPLN T3 ON T2.PriceList = T3.ListNum WHERE T0.[WhsCode] =[%0] AND T1.[SuppCatNum] =[%1] AND T3.ListNum =1
Thanks in advance
Looking for your support
Parikshit

Dear Gordon
Thanks for your advice.But can you able to add selling price in below query which you have advice me. even i want zero item in query.
Declare @FromDate Datetime
Declare @ToDate Datetime
Declare @Group nvarchar(10)
Set @FromDate = (Select min(S0.Docdate) from dbo.OINM S0 where S0.Docdate >='[%0]')
Set @ToDate = (Select max(S1.Docdate) from dbo.OINM s1 where S1.Docdate <='[%1]')
Set @Group = (Select Max(s2.ItmsGrpCod) from dbo.OITB S2 Where S2.ItmsGrpNam = '[%2]')
Select
a.Itemcode,
max(a.Dscription),
sum(a.[Opening Balance]) as [Opening Balance],
sum(a.[IN]) as [IN],
sum(a.OUT) as OUT,
((sum(a.[Opening Balance]) + sum(a.[IN])) - Sum(a.OUT)) as Closing
from(
Select
N1.Itemcode,
N1.Dscription,
(sum(N1.inqty)-sum(n1.outqty)) as [Opening Balance],
0 as [IN],
0 as OUT
From dbo.OINM N1
Where
N1.DocDate < @FromDate
Group By
N1.ItemCode,N1.Dscription
Union All
select
N1.Itemcode,
N1.Dscription,
0 as [Opening Balance],
sum(N1.inqty) as [IN],
0 as OUT
From dbo.OINM N1
Where
N1.DocDate >= @FromDate and N1.DocDate <= @ToDate and
N1.Inqty >0
Group By
N1.ItemCode,N1.Dscription
Union All
select
N1.Itemcode,
N1.Dscription,
0 as [Opening Balance],
0 as [IN],
sum(N1.outqty) as OUT
From dbo.OINM N1
Where
N1.DocDate >= @FromDate and N1.DocDate <=@ToDate and
N1.OutQty > 0
Group By
N1.ItemCode,N1.Dscription) a, dbo.OITM I1
where
a.ItemCode=I1.ItemCode and
I1.ItmsGrpCod = @Group
Group By
a.Itemcode
Having sum(a.[Opening Balance]) + sum(a.[IN]) + sum(a.OUT) > 0
Order By a.Itemcode
thanks
parikshit

Selling price in the Pricing procedure

In my implementation the company is arriving at the selling price like this:-
Basic GLP Price     100
Freight & Insurance @5%      5.00
Sub Total      105.00
Exchange to INR @ 1Euro=Rs.1.00(For ex.) 105.00
Loading 1%      1.05
***. Value      106.05
Basic Customs Duty at 15 %      15.91
Sub Total      121.96
CVD 16%      19.51
Cess on CVD 2 %      0.39
Sub Total      141.86
Total Duty      35.81
Cess on Total Duty 2%      0.72
Clearing Charges 1%      1.42
TOTAL COST ( CIF + C DUTY+ CVD+ CESS +CL CHRG)      142.95
Sub Total cost without CVD      <b><u>123.04(Selling price)</u></b>
I want this selling price to be picked up once I punch in the material part no. in my sales order. Can I get this selling price directly without using the pricing procedure? Can I hardcode the selling price or can i use some selling price simulation? Since the data to arrive at the selling price is dynamic is it advisable to hardcode the SP or to use different condition types to arrive at this selling price?

Hi Arindam,
It is advisable to create a new condition type so that in future it will be useful for the reporting purposes related to sales order documents.
Othewise you can write a exit ( Requirement/ Formula etc ), and do the calculation part for the selling price what you have mentioned in any of the mandatory condition type which you are using in sales orders, so that selling price value will always get populated.
Thanks
Lakshman

Collected ATO Model & items with sales orders and forcast not in ASCP plan

PTO/ATO/ATP challenged - need some help understanding this and how it should work or if it can work.
On 11.5.10.2, a customer wants to see the ATO model and options in the ASCP plan
when the ATO configuration item is not created in the Sales Order.
Using the BOMN example below level 2 - ATO item and level 4 - Marketing Code (Forecast at this level)
ALTIX-4700-PTO-Z level 1 PTO Model
ALTIX-4700-ATO-Z level 2 ATO model
--ALTIX4700-SYS-Z level 3
LST-IRU-Z level 4 Ordered item
LST-4700-WC-Z level 4 Ordered item
LST-IRU-WC-SRACK-Z level 4 Ordered item
They are not seeing level 4 items in the plan even though they have Sales Order Demand and forecast at this level.
They see the items in the collection workbench, but they are missing in the ASCP plan.
Any ideas will be appreciated.
Thanks.
Edited by: Bob Marchant on Oct 16, 2008 12:02 PM

Are you able to book an order on sales order work bench with same configuartion?

Manual override option for Unit selling price in Order line level.

In OM R-12
Our client wants manual override option for Unit selling price in Order line level.
But there is no solution available to fulfill this requirment. To be able to manually override the price on a Sales Order line you
must have defined a manual modifier that qualifies for the Sales Order line in question. Without a suitable manual modifier the price cannot be changed.
This is current standard functionality.
Anybody can give some suggestion/workaround to override selling price in Order header level without using the modifiers.
regards,

Hi Kashif,
I'm finding it little difficult to buy Oracle Support's feedback with regards to R12 functionality for direct List Price update without using any modifier (manual or whatever). After all it is Oracle's product and they should know better. But test results in Solution Beacon's Vision 12.0.6 instance (http://www.solutionbeacon.com/tools_r12vision.htm) and documentation updates in R12 (R12.0.4) OM user guide & implementation manuals potray a different picture.
After your last post, I did a test in Solution Beacon's Vision 12.0.6 instance with following details:
OM: List Price Override Privilege = "Unlimited Access" at user level
OM: Discounting Privileges = "None" at user level
No manual modifiers defined and Order status = "Entered"
I could display the "List Price" field from folder under Line Items >> Main tab, override the list price to a new value and save. The unit selling price showed the new value based on updated List Price as soon as I tabbed out of the list price field after overriding. After saving it showed the new selling price. _Please note that under Line Items >> Pricing tab there is another "List Price" field and that is not editable_. For such overrides "View Adjustments" (from Line >> Actions) will not show any adjustment details as it is a direct update of list price.
Also please note that, if "Enforce List Price" checkbox is selected for the order type, the list price cannot be overridden even if the profile option is set to "Unlimited Access".
Document References:
Oracle® Order Management User's Guide
Release 12, Part No. B28099-03, September 2007 >> R12.0.4
Page No. 10-74
+Note: Note: If any order line for an order has the Calculate Price Flag value equal to Partial Price or Freeze Price new order level adjustments will not be applied or allowed to be overridden. _The profile option OM: List Price Override Privilege controls your ability to override the unit list price. If you have this profile set to Unlimited, you may modify the unit list price by editing the current value displayed_. The original list price is saved in a hidden folder field, so you can display it if necessary+.
Page No. 10-94
User Procedures
_A new profile option, OM: List Price Override Privilege controls whether or not you can update the List Price_. It is enabled and updated at the application, responsibility and user level. It is not user visible and updatable. The values include+:
- View Only: This is the default value. If set to this value, the current behavior is retained, which means unit list price field is protected.
- Unlimited Privilege: If set to this value, you can override the unit list price field from the main tab and immediately see selling price adjusted accordingly.
To use Override List Price:
+1. Navigate to the Sales Orders/Quick Sales Orders window.+
+2. Enter the header and line information, including the ordered item and quantity, then tab to the next field. The Selling Price and List Price display+.
+3. If the profile is set to Unlimited Privilege, you can enter a new list price in the List Price field. You can either proceed to the next line or save your work+.
+4. You can see the new, entered list price, and if there are automatic discounts applied, they will be based on the new list price+.
+5. If the folder has been modified to show the Original List Price, the original list price displays+.
+6. To change the List Price again, go to the list price field and enter a new value, replacing a previously entered value. If Audit Trail is enabled for List Price and a reason is required, a window appears to enter a reason and optional comments+.
Note: Subsequent overrides of the List Price, after the order line is saved, can be captured by Audit Trail, depending on the setup of Audit Trail (entered or booked state) and any processing constraints that have been set up.
In the OM Implementation Manual also there are notes related to this.
OM Implementation Manual
Release 12, Part No. B25975-03, September 2007 >> R12.0.4
You can refer to page no. 2-59, C-4 etc.
Thanks
Supro

ESYU: Order Import를 통해 간단한 ATO Model을 위한 Order를 생성하는 방법

Purpose
Oracle Order Management - Version: 11.5.9 to 12.0.5
Information in this document applies to any platform.
아래와 같은 구조를 갖는 간단한 ATO model을 위한 order를 order import를 통해 생성하는 방법에 대해 알아본다.
ATO Model (542851)
|- ATO Option Class (542852)
|--Option Item (152840)
Solution
Order Import interface table에 header와 lines을 입력하는 아래 script를 이용한다.
Interface tables에 data insert 후 Order Import concurrent program을 실행한다.
INSERT INTO OE_HEADERS_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,creation_date
,created_by
,last_update_date
,last_updated_by
,operation_code
,sold_to_org_id
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,sysdate --creation_date
,-1 --created_by
,sysdate --last_update_date
,-1 --last_updated_by
,'INSERT' --operation_code
,1005 --sold_to_org_id
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,top_model_line_ref
,item_type_code
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,'1' --orig_sys_line_ref
,542851 --inventory_item
,1 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'1' --top_model_line_ref
,'MODEL' --item_type_code
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,top_model_line_ref
,link_to_line_ref
,item_type_code
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,'2' --orig_sys_line_ref
,542852 --inventory_item_id
,1 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'1' --top_model_line_ref
,'1' --link_to_line_ref
,'CLASS' --item_type_code
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,top_model_line_ref
,link_to_line_ref
,item_type_code
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,'3' --orig_sys_line_ref
,152840 --inventory_item_id
,1 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'1' --top_model_line_ref
,'2' --link_to_line_ref
,'OPTION' --item_type_code
); commit;
- Orders, Returns -> Import Orders -> Order Import Request
- Parameter form의 Order Source LOV에서 Order Source를 선택
- Submit the concurrent request.
Reference
Note 746677.1

Daily sales report with last selling price

Dear All,
how to query daily sales record with last selling price as following:
cust. code , item , unit price, last selling price to this cust. within 3 month , highest selling price of this item with 3months
I'm new to both SAP and SQL, Please help! Many Thanks!!
Wing

Hi,
Try this........
SELECT P.CardCode,P.CardName,P.ItemCode,
[1] as [Jan],
[2] as [Feb],
[3] as [Mar],
[4] as [Apr],
[5] as [May],
[6] as [Jun],
[7] as [Jul],
[8] as [Aug],
[9] as [Sep],
[10] as [Oct],
[11] as [Nov],
[12] as [Dec]
FROM (SELECT (T0.CardCode),T0.CardName,t1.ItemCode,T1.price,MONTH(T1.Docdate)as month
FROM dbo.OINV T0
inner join INV1 T1 ON T0.DocEntry=T1.DocEntry
inner join OITM t2 on T1.ItemCode=t2.ItemCode
WHERE T1.DocDate>='[%0]' and T1.DocDate<='[%1]' and T1.ITEMCODE='[%2]'
and T0.CardCode='[%3]'
) S
PIVOT (max(price) FOR [month] IN
([4],[5],[6],[7],[8],[9],[10],[11],[12],[1],[2],[3])) P
ORDER BY P.[CardCode]
Check this link for SQL tutorials.........
http://beginner-sql-tutorial.com/sql-subquery.htm
http://w3schools.com/sql/default.asp

Unit Selling Price Override through PROCESS_ORDER API

Hi All,
I have this below requirement to be achieved through process_order API.
1. In the Order Oganizer UI, I open the Order Entry form.
2. Open the Lines tab
3. For the Unit Selling Price, I change the price manually and tab out.
4. Its gives me a LOV to select a Surcharge modifier.
5. I select one of the surcharge and click save.
6. The price is overridden and a manual price adjustment is created for the above selected surcharge.
This functionality I want to acieve through the PROCESS_ORDER API. Basically, I want to override the unit selling price and apply a surchage modifier. This should change the selling price and create a adjustement record for the above line.
Please let me know if anyone knows about this. That would help me.
Thanks,
Anand

Anand
I tested this in 12.0.4 vision and works. Also if you need to use update option if you are applying the same modifier more than once(not create), just like the way screen changes behave.
DECLARE
l_return_status VARCHAR2 (30);
x_msg_data VARCHAR2 (2000);
x_msg_count NUMBER;
l_adj_rec oe_order_pub.line_adj_rec_type;
l_adj_tbl oe_order_pub.line_adj_tbl_type;
l_x_header_rec oe_order_pub.header_rec_type;
l_x_header_adj_tbl oe_order_pub.header_adj_tbl_type;
l_x_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
l_x_line_tbl oe_order_pub.line_tbl_type;
l_x_line_adj_tbl oe_order_pub.line_adj_tbl_type;
l_x_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
l_x_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
l_x_action_request_tbl oe_order_pub.request_tbl_type;
l_x_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
l_x_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
l_x_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
l_x_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
l_x_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
l_x_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
l_list_line_type_code VARCHAR2 (30) := NULL;
l_list_line_id NUMBER;
l_x_header_payment_tbl oe_order_pub.header_payment_tbl_type;
l_x_line_payment_tbl oe_order_pub.line_payment_tbl_type;
l_prc_adj_request oe_order_pub.request_tbl_type;
l_prc_adj_index NUMBER := 1;
l_price_adj_id NUMBER;
v_msg_index_out NUMBER;
x_header_rec_type oe_order_pub.header_rec_type;
x_header_val_rec_type oe_order_pub.header_val_rec_type;
x_header_adj_tbl_type oe_order_pub.header_adj_tbl_type;
x_header_adj_val_tbl_type oe_order_pub.header_adj_val_tbl_type;
x_header_price_att_tbl_type oe_order_pub.header_price_att_tbl_type;
x_header_adj_att_tbl_type oe_order_pub.header_adj_att_tbl_type;
x_header_adj_assoc_tbl_type oe_order_pub.header_adj_assoc_tbl_type;
x_header_scredit_tbl_type oe_order_pub.header_scredit_tbl_type;
x_header_scredit_val_tbl_type oe_order_pub.header_scredit_val_tbl_type;
x_line_tbl_type oe_order_pub.line_tbl_type;
x_line_val_tbl_type oe_order_pub.line_val_tbl_type;
x_line_adj_tbl_type oe_order_pub.line_adj_tbl_type;
x_line_adj_val_tbl_type oe_order_pub.line_adj_val_tbl_type;
x_line_price_att_tbl_type oe_order_pub.line_price_att_tbl_type;
x_line_adj_att_tbl_type oe_order_pub.line_adj_att_tbl_type;
x_line_adj_assoc_tbl_type oe_order_pub.line_adj_assoc_tbl_type;
x_line_scredit_tbl_type oe_order_pub.line_scredit_tbl_type;
x_line_scredit_val_tbl_type oe_order_pub.line_scredit_val_tbl_type;
x_lot_serial_tbl_type oe_order_pub.lot_serial_tbl_type;
x_lot_serial_val_tbl_type oe_order_pub.lot_serial_val_tbl_type;
x_request_tbl_type oe_order_pub.request_tbl_type;
x_header_payment_tbl_type oe_order_pub.header_payment_tbl_type;
x_header_payment_val_tbl_type oe_order_pub.header_payment_val_tbl_type;
x_line_payment_tbl_type oe_order_pub.line_payment_tbl_type;
x_line_payment_val_tbl_type oe_order_pub.line_payment_val_tbl_type;
l_control_rec oe_globals.control_rec_type;
BEGIN
fnd_global.apps_initialize (1005902, 21623, 660);
mo_global.set_policy_context ('S', 204);
l_x_line_tbl (1).line_id := 319799;
l_x_line_tbl (1).header_id := 155008;
l_adj_rec := oe_order_pub.g_miss_line_adj_rec;
l_adj_rec.price_adjustment_id := fnd_api.g_miss_num;
l_adj_rec.list_header_id := 8988; --Modifier id
l_adj_rec.list_line_id := 16596; --Modifier line id
l_adj_rec.automatic_flag := 'N';
l_adj_rec.list_line_type_code := 'DIS'; --Change this is it is surcharge
l_adj_rec.arithmetic_operator := 'AMT'; --Percentage or amount
l_adj_rec.operand := 10; --How much?
l_adj_rec.operation := oe_globals.g_opr_create;
l_adj_rec.line_index := 1;
l_adj_rec.update_allowed := 'Y';
l_adj_rec.applied_flag := 'Y'; --this is required to change the price of the line
l_adj_rec.change_reason_code := 'MANUAL';
l_adj_rec.change_reason_text := 'Manually applied adjustments';
l_adj_tbl (1) := l_adj_rec;
l_control_rec.process_entity := oe_globals.g_entity_line_adj;
l_control_rec.process := TRUE;
oe_order_pub.process_order (p_api_version_number => 1.0
, x_return_status => l_return_status
, x_msg_count => x_msg_count
, x_msg_data => x_msg_data
, p_header_rec => l_x_header_rec
, p_header_adj_tbl => l_x_header_adj_tbl
, p_header_scredit_tbl => l_x_header_scredit_tbl
, p_header_payment_tbl => l_x_header_payment_tbl
, p_line_tbl => l_x_line_tbl
, p_line_adj_tbl => l_adj_tbl
, p_line_scredit_tbl => l_x_line_scredit_tbl
, p_line_payment_tbl => l_x_line_payment_tbl
, p_lot_serial_tbl => l_x_lot_serial_tbl
, p_action_request_tbl => l_prc_adj_request
, p_header_price_att_tbl => l_x_header_price_att_tbl
, p_header_adj_att_tbl => l_x_header_adj_att_tbl
, p_header_adj_assoc_tbl => l_x_header_adj_assoc_tbl
, p_line_price_att_tbl => l_x_line_price_att_tbl
, p_line_adj_att_tbl => l_x_line_adj_att_tbl
, p_line_adj_assoc_tbl => l_x_line_adj_assoc_tbl
, x_header_rec => x_header_rec_type
, x_header_val_rec => x_header_val_rec_type
, x_header_adj_tbl => x_header_adj_tbl_type
, x_header_adj_val_tbl => x_header_adj_val_tbl_type
, x_header_price_att_tbl => x_header_price_att_tbl_type
, x_header_adj_att_tbl => x_header_adj_att_tbl_type
, x_header_adj_assoc_tbl => x_header_adj_assoc_tbl_type
, x_header_scredit_tbl => x_header_scredit_tbl_type
, x_header_scredit_val_tbl => x_header_scredit_val_tbl_type
, x_header_payment_tbl => x_header_payment_tbl_type
, x_header_payment_val_tbl => x_header_payment_val_tbl_type
, x_line_tbl => x_line_tbl_type
, x_line_val_tbl => x_line_val_tbl_type
, x_line_adj_tbl => x_line_adj_tbl_type
, x_line_adj_val_tbl => x_line_adj_val_tbl_type
, x_line_price_att_tbl => x_line_price_att_tbl_type
, x_line_adj_att_tbl => x_line_adj_att_tbl_type
, x_line_adj_assoc_tbl => x_line_adj_assoc_tbl_type
, x_line_scredit_tbl => x_line_scredit_tbl_type
, x_line_scredit_val_tbl => x_line_scredit_val_tbl_type
, x_line_payment_tbl => x_line_payment_tbl_type
, x_line_payment_val_tbl => x_line_payment_val_tbl_type
, x_lot_serial_tbl => x_lot_serial_tbl_type
, x_lot_serial_val_tbl => x_lot_serial_val_tbl_type
, x_action_request_tbl => x_request_tbl_type
DBMS_OUTPUT.put_line (l_return_status);
IF x_msg_count > 0
THEN
FOR v_index IN 1 .. x_msg_count
LOOP
oe_msg_pub.get (p_msg_index => v_index, p_encoded => 'F', p_data => x_msg_data, p_msg_index_out => v_msg_index_out);
x_msg_data := SUBSTR (x_msg_data, 1, 200);
DBMS_OUTPUT.put_line (x_msg_data);
DBMS_OUTPUT.put_line ('============================================================');
END LOOP;
END IF;
END;
Thanks
Nagamohan

FICO - Add selling price in S_ALR_87099931

Hi! I'm a beginner of the ABAP. I would like to add the selling price in the report S_ALR_87099931.
This selling price shld auto capture from the Sales module.
Is there anyone can give me a guidelines?

copy RKKBCAL2 into ZRKKBCAL2 from se80 than do required changes.and give new t-code to this report.

IV01 : Selling price to customer And PR00 Selling price to customer

Dear SD Experts ..
I know inter company Process But i have small doubt please clear me
IV01 : Selling price to customer
PI01: Pricing between Supplying company to selling company ( Internal Purpose only )
ICAA01( Pricing procedure)
By using this we can bill the customer But PR00 Also Selling price to customer ( RVA001)
Please tell me i know all setting but logically i want to know why we have to maintain 2 Pricing procedures because By using inter company pricing procedure we can Bill the customer as per IV01 Right
i have this doubt ?

Hi Amit,
IV01 : Selling price to customer
your interpretation for IV01 as selling Price to customer is wrong.
IV01 is intercompany pricing which will be seen in pricing procedure ICAA01 . This condition get the value populated from PI01 which is your intercompany pricing Condition type from RVAA01
as your know IV is the billing document type which is used for intercompany Billing process and IV01 value gets populated from your F2 billing type
PI01 is used as reference condition type for IV01
for example you have created intercompany scenario in which your F2 contains
customer price is PR00 = 1000
Intercompany Price is PI01 = 900
now when ever you creates IV the condition type IV01 get 900 from PI01
hope it is clear
revert if you need any further help

DP91-Debit memo request -selling price

Dear Friends,
the client requirement is to bill the his customer based on the equipment and manpower utilized
Now i have created a contract - has assigned the DIP profile in item category and the WBS element is attached in contract item level
based on the utilization/confirmation the DMR is created in DP91, there it is fetching only the cost which was maintained in KP26 and it is capturing thorough EK01 condition type. this subsequently copying to billing
I need to bill the customer with selling price, not the cost
in pricing procedure

Thanks for your explanation santhosh
In normal sales VPRS is the cost price of matrial
Here RRB EK01 is the cost of the activity/service , am i right santhosh?
one more thing, for working hours of manpower, in condition record per hour rate is maintained,
can i push only the quantity/working hours from Project systems?
example:
per hour rate is 15 USD in VK11 maintained
From WBS 10 hours is coming to DMR, so system will calculate automatically 150 USD in DMR
is it possible ? If yes , where is the configuration?
please help me to solve my issue
Regards,
pratheep

Unit Selling Price in OM

Hi All,
I am new in OM. i just want to know when my user enter and modified unit selling price the message shows no list of values contain no entries, please advice how can i add its list or how can i use range of list against list.
Thanks

Dear All,
Please advice above issue
thanks

Same Batch Material to be sold at different selling prices

Hello,
I have a customer requirement where a material at depot belonging to the same batch should be sold at different sales price.
Eg: on 1st of May, Material XYZ belonging to batch AB052011 of 100 qts was GR into the Depot at Rs 100 / qty. A selling Price PR00 will be maintained at Rs 100 / qty. On 5th of May, sales happen for 50 qts, hence PR00 condition of Rs 100 /Qty will be picked accordingly. Till this point everything is fine.
Price change happens for the material at the plant.
Again on 15th of May another GR for XYZ material of Batch AB052011 of 200 qts was GR'ed into the Depot at Rs 150 / qty now. Accordingly PR00 price was changed to Rs 150 /qty.
On 20th of May the total stock of Material XYZ belonging to Batch AB052011 is 250 qts. On 20th if sale happens for 250 qts, Customer requirement is pick a PR00 of Rs 100 for the 50 qts and PR00 of Rs 150 for the remaining qty.
We dont want to allow price to be changed manually, this should only happen through condition records. Is there any way by which I can create a condition table which allows me to maintain two different prices for the same batch at a given point of time.
Regards
Raj

Hi Rajendra,
Option1:
Assuming that you are only talking about Batch Number based price (and not Batch characteristics based price) you can maintain price condition record based on Batch where Batch number will be one of the key criteria in your Access Sequence. So you many need to create a new Condition table with Material/Batch Number and insert it into your Pricing condition Access Sequence.
Since you will not know what batch you deliver till the goods been issued, you may need to redetermine the Pricing procedure during the Billing. Based on the batch that is delivered system will redetermine the Price from Condition record maintained on Batch basis.
Option2:
If you are talking about Batch Characteristics based Price, you have more to do.
Please check these forums links which might help you and also look at the OSS Note: 675409
http://www.sapfans.com/forums/viewtopic.php?f=5&t=285438
http://www.sapfans.com/forums/viewtopic.php?f=5&t=222440
Good Luck

Can we copy the already created Configuration Item in ATO Model

Hi all,
We have the requirement for copy the Existing configurator ATO items into new model. i.e. Customer will congifured the model in istore process flow to create a sale order. After that for second sales order customer don't want to make same configuration so added interface for copying the existing configuration. In this process we are facing following issue.
Steps we are followed for copying the existing ATO models:
=>First we find the existing configuration's for already created ato model.
=>Then we copied the existing model configuration into new configuration using cz_cfg_api.copy_configuration API.
=>After that we are passing new configuration detail, model line details and sub item detail into ASO_QUOTE_LINES_PVT.Insert_Quote_Line_Rows API.
=>This API's will made the appropriate entry in 'ASO_QUOTE_LINES_ALL' and 'ASO_QUOTE_LINE_DETAILS', line_relation tables.
After the all process when we looking into the cart page the model and model sub-items are created as separate lines.
It was not converted as ATO model.
Please help.

Hi,
We solved this issue by using custom API process, also we used ASO oracle packages.
Thanks,
LSP

ATO Model - Selling Price

Similar Messages

Maybe you are looking for