Price Break through the Pricing Agreement API.

Hi All,
I need to put Range price break on the pricing agreement conversion. I am using the OE_Pricing_Cont_PUB.Process_Agreement API to accomplish this, but couldn't find where and What do I need to put to take care of the Price Breaks.
All pointers are highly appreciated.
Thanks,
Rahul

Hi David,
Advanced Pricing comes with 6 x seeded pricing attributes for cross-order volume d-iscounts: Period 1/2/3 Item Qty and Period 1/2/3 Order Amount ... which relate to the tables I mentioned previously.
Those Periods 1, 2 and 3 are based on the values in the 3 profile options I mentioned. So if you have a quarterly volume d-iscount structure you might use 30, 60, 90 as the values (i.e. not 30, 30, 30) which would bucket 1-30, 31-60 and 61-90 and ignore orders older than 90 days.
The Cross Order Volume Load takes place only for booked sales orders containing items/customers which qualify for a modifier/price list using cross-order volume pricing attributes/qualifiers+. To that end, when you're testing this, remember to run QP: Maintains the denormalized data in QP Qualifiers after creating/assigning qualifiers and before running the Cross Order Volume Load.
It is also important to note that the order amounts which are accumulated are gross only – i.e. they are based on the unit list price not the unit sell price post d-iscounts etc. Also, the cross-order amount does not include the current order being priced since the expected process is that the Cross Order Volume Load will be scheduled to run periodically, probably at the end of the business day. (You may feel that these two riders reduce the value of this functionality - they do for me!)
Note that there is also a Cross Order Volume Report which will list the accumulated data from the Cross Order Volume Load for you.
Hope that helps...
Regards,
Jon

Similar Messages

I would like to call through the CIS UCPM API but following error occurred

I would like to call through the CIS UCPM API but following error occurred, I would like to to set Loacle Chinese, how can I do? Thank you
intradoc.common.ServiceException: !csUnableToRetrieveSearchResults!csLocaleNotFound,English-US
at intradoc.server.ServiceRequestImplementor.buildServiceException(ServiceRequestImplem
entor.java:2115)
at intradoc.server.Service.buildServiceException(Service.java:2326)
at intradoc.server.Service.createServiceExceptionEx(Service.java:2320)
at intradoc.server.Service.createServiceException(Service.java:2315)
at intradoc.server.ServiceHttpImplementor.determineParameterizedLocale(ServiceHttpImple
mentor.java:668)
at intradoc.server.ServiceHttpImplementor.initLocale(ServiceHttpImplementor.java:467)
at intradoc.server.Service.initLocale(Service.java:426)
at intradoc.server.Service.initDelegatedObjects(Service.java:295)
at intradoc.server.SearchService.initDelegatedObjects(SearchService.java:86)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:436)
at intradoc.server.IdcServerThread.processRequest(IdcServerThread.java:265)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:160)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImp
l.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

I managed to find a solution to my problem described above. I downloaded a demo copy of the shareware called R-Tools which I found on Tucows.com
The site described the software thus: "Take advantage of R-Studio's unique ability to recover files and disks on remote computers, even if their partition structures are damaged or deleted."
The demo software searched my ipod and found all my photos and showed them as thumbnails. Of course the demo software would not save the files unless I registered it which cost US$49.95. There are several different suites of applications from this publisher, I got the cheapest option which is called "R-Studio FAT".
I didn't mind paying this amount because the photos were very precious to me and by this point I had just about resigned myself to losing them all. I had previously contacted a professional data recovery service and they had quoted me "AUD$80 per hour and probably 1 to 2 hours work".
I've been too busy organising my newly recovered photos into galleries and editing them using photoshop to be bothered to try and fix my ipod which I doubt I will want to use again for photo storage.

Updating Price Breaks through API

Hi,
We have a requirement to update the existing price break information. We have found an API for inserting a new price break for a given price list. The API name is
QP_PRICE_LIST_PUB.Process_Price_List.
Can any one let us know is there a way to update existing pricebreak using a standard API and how.
Thanks & Regards,
Parvathi S

Check the product related documents. They will have a mention of all the public APIs if they exist.
--Shiv

Can we create PRICE BREAK using qp_price_list_pub.process_price_list API

I am able to create Price list headers, prrice list lines and pricing attributes using qp_price_list_pub.process_price_list. But i am unable to create price break using this API. Is it possible to create Price Break using this API.

1008612 wrote:
I am able to create Price list headers, prrice list lines and pricing attributes using qp_price_list_pub.process_price_list. But i am unable to create price break using this API. Is it possible to create Price Break using this API.please see this
How To Add Price Breaks To A Pricing Agreement ? [ID 1305360.1]
;) AppsMAsti :)
Sharing is Caring

ProcessOrder API not populating the Price from the pricing attribute setup.

Hi,
I am having a problem while adding a line on the existing order through the Oe_Order_pub.Process_order API. A line is added but the pricing is not fetched using the pricing attribute.
I have passed calculate_Price_flag=’Y’ but in vain. I am not passing price list id but instead want to use a pricing attribute that will fetch the price on the item automatically.
But, it is working when I am calling this procedure from TOAD but when it is called through the Workflow, a line is added but no price is fetched.
Could anyone help me out on this? Here’s the code:
p_api_version_number NUMBER := 1.0;
p_init_msg_list VARCHAR2 (1) := FND_API.G_TRUE;
p_return_values VARCHAR2 (1) := FND_API.G_TRUE;
p_action_commit VARCHAR2 (1) := FND_API.G_FALSE;
x_return_status VARCHAR2 (1);
x_msg_count NUMBER := 0;
x_msg_data VARCHAR2 (2000);
p_header_rec oe_order_pub.header_rec_type:= oe_order_pub.g_miss_header_rec;
p_old_header_rec oe_order_pub.header_rec_type:= oe_order_pub.g_miss_header_rec;
p_header_val_rec oe_order_pub.header_val_rec_type:= oe_order_pub.g_miss_header_val_rec;
p_old_header_val_rec oe_order_pub.header_val_rec_type:= oe_order_pub.g_miss_header_val_rec;
p_header_adj_tbl oe_order_pub.header_adj_tbl_type:= oe_order_pub.g_miss_header_adj_tbl;
p_old_header_adj_tbl oe_order_pub.header_adj_tbl_type:= oe_order_pub.g_miss_header_adj_tbl;
p_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type:= oe_order_pub.g_miss_header_adj_val_tbl;
p_old_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type:= oe_order_pub.g_miss_header_adj_val_tbl;
p_header_price_att_tbl oe_order_pub.header_price_att_tbl_type:= oe_order_pub.g_miss_header_price_att_tbl;
p_old_header_price_att_tbl oe_order_pub.header_price_att_tbl_type:= oe_order_pub.g_miss_header_price_att_tbl;
p_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type:= oe_order_pub.g_miss_header_adj_att_tbl;
p_old_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type:= oe_order_pub.g_miss_header_adj_att_tbl;
p_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type:= oe_order_pub.g_miss_header_adj_assoc_tbl;
p_old_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type:= oe_order_pub.g_miss_header_adj_assoc_tbl;
p_header_scredit_tbl oe_order_pub.header_scredit_tbl_type:= oe_order_pub.g_miss_header_scredit_tbl;
p_old_header_scredit_tbl oe_order_pub.header_scredit_tbl_type:= oe_order_pub.g_miss_header_scredit_tbl;
p_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type:= oe_order_pub.g_miss_header_scredit_val_tbl;
p_old_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type:= oe_order_pub.g_miss_header_scredit_val_tbl;
p_line_tbl oe_order_pub.line_tbl_type:= oe_order_pub.g_miss_line_tbl;
p_old_line_tbl oe_order_pub.line_tbl_type:= oe_order_pub.g_miss_line_tbl;
p_line_val_tbl oe_order_pub.line_val_tbl_type:= oe_order_pub.g_miss_line_val_tbl;
p_old_line_val_tbl oe_order_pub.line_val_tbl_type:= oe_order_pub.g_miss_line_val_tbl;
p_line_adj_tbl oe_order_pub.line_adj_tbl_type:= oe_order_pub.g_miss_line_adj_tbl;
p_old_line_adj_tbl oe_order_pub.line_adj_tbl_type:= oe_order_pub.g_miss_line_adj_tbl;
p_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type:= oe_order_pub.g_miss_line_adj_val_tbl;
p_old_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type:= oe_order_pub.g_miss_line_adj_val_tbl;
p_line_price_att_tbl oe_order_pub.line_price_att_tbl_type:= oe_order_pub.g_miss_line_price_att_tbl;
p_old_line_price_att_tbl oe_order_pub.line_price_att_tbl_type:= oe_order_pub.g_miss_line_price_att_tbl;
p_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type:= oe_order_pub.g_miss_line_adj_att_tbl;
p_old_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type:= oe_order_pub.g_miss_line_adj_att_tbl;
p_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type:= oe_order_pub.g_miss_line_adj_assoc_tbl;
p_old_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type:= oe_order_pub.g_miss_line_adj_assoc_tbl;
p_line_scredit_tbl oe_order_pub.line_scredit_tbl_type:= oe_order_pub.g_miss_line_scredit_tbl;
p_old_line_scredit_tbl oe_order_pub.line_scredit_tbl_type:= oe_order_pub.g_miss_line_scredit_tbl;
p_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type:= oe_order_pub.g_miss_line_scredit_val_tbl;
p_old_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type:= oe_order_pub.g_miss_line_scredit_val_tbl;
p_lot_serial_tbl oe_order_pub.lot_serial_tbl_type:= oe_order_pub.g_miss_lot_serial_tbl;
p_old_lot_serial_tbl oe_order_pub.lot_serial_tbl_type:= oe_order_pub.g_miss_lot_serial_tbl;
p_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type:= oe_order_pub.g_miss_lot_serial_val_tbl;
p_old_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type:= oe_order_pub.g_miss_lot_serial_val_tbl;
p_action_request_tbl oe_order_pub.request_tbl_type := oe_order_pub.g_miss_request_tbl;
x_header_rec oe_order_pub.header_rec_type;
x_header_val_rec oe_order_pub.header_val_rec_type;
x_header_adj_tbl oe_order_pub.header_adj_tbl_type;
x_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
x_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
x_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
x_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
x_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
x_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
x_line_tbl oe_order_pub.line_tbl_type;
x_line_val_tbl oe_order_pub.line_val_tbl_type;
x_line_adj_tbl oe_order_pub.line_adj_tbl_type;
x_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
x_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
x_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
x_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
x_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
x_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
x_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
x_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
x_action_request_tbl oe_order_pub.request_tbl_type;
i NUMBER := 1;
x_data VARCHAR2(2000);
x_index NUMBER;
x_err_msg VARCHAR2(4000);
x_user_id NUMBER;
x_appl_id NUMBER;
x_resp_id NUMBER;
X_DEBUG_FILE Varchar2(400);
BEGIN
oe_msg_pub.initialize();
oe_debug_pub.initialize;
X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
oe_debug_pub.SetDebugLevel(3);
-- INITIALIZATION REQUIRED FOR R12
MO_GLOBAL.INIT('ONT');
MO_GLOBAL.SET_ORG_CONTEXT(p_org_id,'','ONT');
p_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_action_request_tbl(i) := OE_ORDER_PUB.G_MISS_REQUEST_REC;
p_line_tbl.delete;
p_action_request_tbl.delete;
p_line_tbl (i) := OE_ORDER_PUB.G_MISS_LINE_REC;
p_line_tbl (i).operation := OE_GLOBALS.G_OPR_CREATE;
p_line_tbl (i).header_id := p_header_id;
p_line_tbl (i).ordered_quantity := p_qty;
p_line_tbl (i).line_number := p_line_number;
p_line_tbl (i).shipment_number := 1;
p_line_tbl (i).calculate_price_flag := 'Y';--p_calc_price_flag;
p_line_tbl (i).created_by := p_user_id ;
p_line_tbl (i).creation_date := SYSDATE ;
p_line_tbl (i).inventory_item_id := p_item_id;
p_line_tbl (i).last_update_date := SYSDATE;
--p_line_tbl (i).last_update_login        := -1;
p_line_tbl (i).last_updated_by := p_user_id ;
p_line_tbl (i).line_type_id := p_line_type_id;
p_line_tbl (i).order_quantity_uom := p_qty_uom;
p_line_tbl (i).org_id := p_org_id;
--p_line_tbl (i).price_list_id            := p_price_list_id;
p_line_tbl (i).ship_from_org_id := p_ship_from_org_id ;
p_line_tbl (i).ship_to_contact_id := p_ship_to_contact_id;
p_line_tbl (i).ship_to_org_id := p_ship_to_org_id;
p_line_tbl (i).sold_from_org_id := p_sold_from_org_id ;
p_line_tbl (i).sold_to_org_id := p_sold_to_org_id;
p_line_tbl (i).subinventory := p_subinventory ;
--p_line_tbl (i).unit_list_price          := p_price;
--p_line_tbl (i).unit_selling_price       := p_price;
p_line_tbl (i).booked_flag := 'Y';
p_line_tbl(i).flow_status_code := 'CLOSED';
--SAVEPOINT BEFORE_PROC_API;
OE_ORDER_PUB.PROCESS_ORDER (
p_api_version_number => p_api_version_number
,p_init_msg_list => p_init_msg_list
,p_return_values => p_return_values
,p_action_commit => p_action_commit
,p_header_rec => p_header_rec
,p_old_header_rec => p_old_header_rec
,p_header_val_rec => p_header_val_rec
,p_old_header_val_rec => p_old_header_val_rec
,p_header_adj_tbl => p_header_adj_tbl
,p_old_header_adj_tbl => p_old_header_adj_tbl
,p_header_adj_val_tbl => p_header_adj_val_tbl
,p_old_header_adj_val_tbl => p_old_header_adj_val_tbl
,p_header_price_att_tbl => p_header_price_att_tbl
,p_old_header_price_att_tbl => p_old_header_price_att_tbl
,p_header_adj_att_tbl => p_header_adj_att_tbl
,p_old_header_adj_att_tbl => p_old_header_adj_att_tbl
,p_header_adj_assoc_tbl => p_header_adj_assoc_tbl
,p_old_header_adj_assoc_tbl => p_old_header_adj_assoc_tbl
,p_header_scredit_tbl => p_header_scredit_tbl
,p_old_header_scredit_tbl => p_old_header_scredit_tbl
,p_header_scredit_val_tbl => p_header_scredit_val_tbl
,p_old_header_scredit_val_tbl => p_old_header_scredit_val_tbl
,p_line_tbl => p_line_tbl
,p_old_line_tbl => p_old_line_tbl
,p_line_val_tbl => p_line_val_tbl
,p_old_line_val_tbl => p_old_line_val_tbl
,p_line_adj_tbl => p_line_adj_tbl
,p_old_line_adj_tbl => p_old_line_adj_tbl
,p_line_adj_val_tbl => p_line_adj_val_tbl
,p_old_line_adj_val_tbl => p_old_line_adj_val_tbl
,p_line_price_att_tbl => p_line_price_att_tbl
,p_old_line_price_att_tbl => p_old_line_price_att_tbl
,p_line_adj_att_tbl => p_line_adj_att_tbl
,p_old_line_adj_att_tbl => p_old_line_adj_att_tbl
,p_line_adj_assoc_tbl => p_line_adj_assoc_tbl
,p_old_line_adj_assoc_tbl => p_old_line_adj_assoc_tbl
,p_line_scredit_tbl => p_line_scredit_tbl
,p_old_line_scredit_tbl => p_old_line_scredit_tbl
,p_line_scredit_val_tbl => p_line_scredit_val_tbl
,p_old_line_scredit_val_tbl => p_old_line_scredit_val_tbl
,p_lot_serial_tbl => p_lot_serial_tbl
,p_old_lot_serial_tbl => p_old_lot_serial_tbl
,p_lot_serial_val_tbl => p_lot_serial_val_tbl
,p_old_lot_serial_val_tbl => p_old_lot_serial_val_tbl
,p_action_request_tbl => p_action_request_tbl
,x_header_rec => x_header_rec
,x_header_val_rec => x_header_val_rec
,x_header_adj_tbl => x_header_adj_tbl
,x_header_adj_val_tbl => x_header_adj_val_tbl
,x_header_price_att_tbl => x_header_price_att_tbl
,x_header_adj_att_tbl => x_header_adj_att_tbl
,x_header_adj_assoc_tbl => x_header_adj_assoc_tbl
,x_header_scredit_tbl => x_header_scredit_tbl
,x_header_scredit_val_tbl => x_header_scredit_val_tbl
,x_line_tbl => x_line_tbl
,x_line_val_tbl => x_line_val_tbl
,x_line_adj_tbl => x_line_adj_tbl
,x_line_adj_val_tbl => x_line_adj_val_tbl
,x_line_price_att_tbl => x_line_price_att_tbl
,x_line_adj_att_tbl => x_line_adj_att_tbl
,x_line_adj_assoc_tbl => x_line_adj_assoc_tbl
,x_line_scredit_tbl => x_line_scredit_tbl
,x_line_scredit_val_tbl => x_line_scredit_val_tbl
,x_lot_serial_tbl => x_lot_serial_tbl
,x_lot_serial_val_tbl => x_lot_serial_val_tbl
,x_action_request_tbl => x_action_request_tbl
,x_return_status => x_return_status
,x_msg_count => x_msg_count
,x_msg_data => x_msg_data
p_status := x_return_status;
IF x_return_status != apps.fnd_api.g_ret_sts_success THEN
x_err_msg:= 'API Error Occured while creating Recycle Fees line ' ;
FOR i in 1..x_msg_count
LOOP
OE_MSG_PUB.GET(i,'F',x_data,x_index);
x_err_msg := x_err_msg || x_data ;
END LOOP;
p_error := x_err_msg;
insert into xx_test values('API ERR: '||SYSDATE|| p_error);
-- ROLLBACK TO SAVEPOINT BEFORE_PROC_API;
END IF;
EXCEPTION
WHEN OTHERS THEN
-- ROLLBACK TO SAVEPOINT BEFORE_PROC_API;
p_error := 'Error Occured in Order Line API: '||SYSDATE||substr(SQLERRM,1,250) ;
p_status := 'E';
END call_order_api;
Thanks,
Rahul

Another striking feature here is, the API works absolutely well for the Internal Orders (Book--> Release-->Ship) but price is not pulled for the External Drop Ship Orders.

Advanced Pricing:Fetching Price from Price Break List

Hi All,
We have a requirement where we have to fetch the price for Items from a Price Break list using Pricing Engine. For this we did following setup.
1) We created a Price List for list of Items and it price list is defined there
2) Then we created Price List (Customer Specific) and based on the quantity in our custom table for that customer and item we have to fetch the price from the Price Break List.
We are doing this by using a Sql statement but we want to implement it by using Pricing Engine. QP_PREQ_PUB.PRICE_REQUESt.
Kindly share code with me for this.
Guys Please help.
Thanks
Aryan

What version of EBS are you on? I know in 12.1.3, there was a price book feature that enabled you to output the pricing from a particular list/modifier. I didn't find it particularly helpful for what I was trying to do (i.e. show all the prices a customer could use), but what I deemed a deficiency may work to your advantage.

How do I access the remote(requesting) clients IP address through the Portal API?

How can I access the remote(requesting) clients IP address through the Portal API?
On our 4.5 - IIS system, we can acces it using the Request.ServerVariables("Remote_Addr") in the ASP pages.
We are deploying 5.0 on Java Portal and would like to be able to do this through the Portal's API so I can call it in one of our custom login Activity space or control etc.
I have looked documentation for the HTTPServletRequest object. It seems like we should be able to access it through one of the methods getRemoteAddr if we can get a handle to HTTPServletRequest object through the Plumtree's framework.
I think the XPRequest object encapsulates the HTTPServletRequest but I didn't see getRemoteAddr method listed in the Javadocs.
Is there a way to access the client's IP address through the Plumtree's framework?
I need to do this so we know the location of the user and in our business case we have fixed IP adresss which let us identify which location is user accessign the system from. We can't do this through preferences or profile because we have to use generic userid for the specifc group of users.
Any help on this would be appreciated.
Thanks.
Vanita

Hi, Vanita. For now, you can use
stringsClientIP = HttpContext.Current.Request.ServerVariables["REMOTE_ADDR"].ToString();
Hope that helps!
Sarah

Open Sourcing an iPhone Application acceptable under the License Agreement?

I've read through the licensing agreement, but I'm still not convinced either way. I want to make my iPhone application's source code available on the internet and set up a project page and SVN repository on a site such as Google Code. I wouldn't be distributing my signing keys and would be the single source for submitting the app to iTunes. Is this allowed under the License Agreement?

(Disclaimer: IANAL, I'm just a smart guy who's worked on GPL projects.)
That isn't the relevant part of the iPhone license agreement. The GPLv2 (which is probably the most important open source license for this question, as it's both very popular and has restrictions on mixing with proprietary code) does not encompass headers and libraries that are part of the operating system. That's how people can write open source Windows and Mac applications--believe me, Microsoft would not be pleased if someone contacted them and said that since Gaim was open source, they had to release the source code to the Win32 API. So the GPLv2 would not attempt to "annex" anything provided by Apple, and thus it wouldn't violate that section.
What may be relevant is the iPhone license section concerning confidentiality. If the class, method, function and constant names are considered "Apple Confidential Information", you would be in violation of the contract if you distributed code that revealed them. I rather suspect that nothing in the Foundation or Core Foundation frameworks could be considered confidential, as information about them is freely available to anyone who has the Mac OS X Core Library, which is distributed with every copy of Leopard. UIKit, Core Location, etc. are another story; I personally think that the fact that the APIs are included in the free SDK ought to preclude considering them confidential, but Apple might think differently.
In other words: you're definitely safe using LGPLv2 libraries. If the code would also compile with the Mac OS X SDK, you're almost certainly safe releasing it under the GPLv2*. If the code uses UIKit or other frameworks documented in the free SDK, you may be safe releasing it under the GPLv2. If you release any code that uses APIs that only licensed developers have access to under the GPLv2, you're probably totally screwed.
The GPLv3 is much stricter, and so the story there might be different; for example, I think it may have key-releasing requirements that would conflict with the contract. I don't really know much about it, though.
\* Remember, the original copyright holder can create alternate licensing arrangements for specific people. So he can say "anyone can use this code under the GPL, and as a special exception, it can be linked against FooCorp's non-GPL software". But to use anyone else's GPL code, you'd have to get all of the authors of that code to agree to the same exception. Alternately, you can just release your own code under the LGPL instead and then it's all good.
Message was edited by: Brent Royal-Gordon

Pricing Agreements vs Blanket Sales Agreements

What is the difference between Pricing Agreements and Blanket Sales Agreements? As far as I can see, they are basically the same, except you have more functionality with a Blanket Sales Agreement.

Hi,
The pricing agreement is an agreement with the customer where we can attach the Agreement price list and it will assign the agreement number as a qualifier to refer in the sale order.
Where as the blanket sale order agreement is like an standard agreement where you have to attach the standard price list and it won't assign any qualifier to refer in the sale order.
Regards,
Arumugam S.

Difference between Blanket sales agreement and pricing agreement

Hi guys
I wasted hours the other day trying to get a blanket sales agreement number in the 'agreement' field on order management. Just to learn that there's two types of agreements in OM and it seems like there's some sort of overlap.
Can someone please give me a few functional tips of key indicators of when to use which.
Similarities between Blanket & Pricing agreements:
- Both can fix payment terms
- Both can have new pricing implications (set a new price other than existing pricelists)
Differences between blanket & pricing agreements:
I tried to read the manual for OM and Pricing but the pricing agreement was a bit short of a nice introduction explaining what it was. I was hoping it would read something like this: You go to your customer, you agree the following and therefore you need a pricing agreement.
Thanks!

Ah,
It struck me that hte most obvious difference is that sales agreements track the amount/qty of releases against that agreement. So the whole release process is some functionality that sales agreements can do that price agreements can not do.
So I'm wondering what can you achieve with a pricing agreement that you cannot achieve with a sales agreement?

Price for calculating the Cost of freight

Hello experts, would like to help, to calculate the cost of shipping by VI01 the system chooses a particular table price registered in TK11 based on the date of creation of the transport document. Is it possible to get the date of organization of transport? You know where to configure this item?
Tks,
Tatiane

I don't think the creation date is used to determine the price condition record - the pricing date should be used for that purpose.
Other thing is that the pricing date may equal the creation date.
Please check the setting of your shipment cost document item category in:
SPRO > LE > Transportation > Shipment Cost > Shipment Cost Document > Shipment Cost Types and Item Categories
Here choose "Define Item Categories" and check field "Pricing Date" of suitable item category (V_TVFT-DATPR).
Regards,
Csaba
(you can give the pricing date manually on selection screen in VI01)
Edited by: Csaba Szommer on Mar 3, 2010 9:43 AM

Where in the icx tables are price break and price break quantities stored?

I am trying to build a query from the icx tables that will show me all the BPA line price breaks and quantities.
I cannot seem to find any documentation on what is specifically is extracted from the BPA lines when an internal catalog build is performed. I am able to validate that in iP, the price breaks are being taken into consideration when I create Requisitions with various quantities, but I do not know where iP is storing this information. Perhaps the data isn't stored and is taken from the core app po_line_locations_all table at the time the requisition is being created?
I have a BPA, line 27, that has multiple price break lines.
select rt_item_id, price_type, contract_num, contract_line_num, allow_price_override_flag, not_to_exceed_price, value_basis
from apps.icx_cat_item_prices
where contract_num = 'xxxxxx' and contract_line_num = '27'
and price_type = 'BLANKET';
All I could find when running this query was the price break information for the first price break line, none of the other price break lines.
If anybody knows where the documentation is that tells me exactly what is extracted from the core application BPA to the icx tables, I would be greatly appreciative. Even better, if someone already knows the answer to either 1) price break and quantity are not stored in icx tables or 2) they are stored and you have SQL that shows me how to find it, I would be so very appreciative to have this information.
Edited by: user6287397 on Jan 24, 2009 6:40 AM

I got the answer. :-)
Price breaks details are not stored in any icx tables. iP retrieves the information based on the need by date entered on the requisition.
Oracle support referred me to the Oracle® Purchasing Release 11i10 Open Interfaces and APIs.
The java code - SourceDocHelper.java - is responsible to get the price information by calling the procedure po_price_break_grp.get_price_break (POXPRBKB.pls DefaultPricing ) For a given a Source Document (Quotation/Catalog), Quantity and Unit of Measure, this procedure derives the best price for the calling routine.
The SQL used to get the price information that was sent to me is attached. Note that this SQL uses the need by date to get the right price in case of price break used at the distribution level.
SELECT poll.price_override
, round(poll.price_override * v_conversion_rate,
l_base_curr_ext_precision )
, poh.rate_date
, poh.rate
, poh.currency_code
, poh.rate_type
, poll.price_discount
, poll.price_override
, decode( poll.line_location_id,
null, pol.unit_meas_lookup_code,
poll.unit_meas_lookup_code)
, poll.line_location_id -- SERVICES FPJ
FROM po_headers_all poh -- FPI GA
, po_lines_all pol -- FPI GA
, po_line_locations_all poll -- FPI GA
WHERE poh.po_header_id = p_source_document_header_id
and poh.po_header_id = pol.po_header_id
and pol.line_num = p_source_document_line_num
and pol.po_line_id = poll.po_line_id
and ( p_required_currency is null
or poh.currency_code = p_required_currency )
and ( p_required_rate_type is null
or poh.rate_type = p_required_rate_type )
and nvl(poll.unit_meas_lookup_code, nvl(p_unit_of_measure,
pol.unit_meas_lookup_code))
= nvl(p_unit_of_measure, pol.unit_meas_lookup_code)
Change sysdate to l_pricing_date in order to use the Need By
Date
to determine the price.
and (trunc(nvl(l_pricing_date, trunc(sysdate))) >= trunc(poll.
start_date) -- FPJ Custom Price
OR
poll.start_date is null)
and (trunc(nvl(l_pricing_date, trunc(sysdate))) <= trunc(poll.
end_date) -- FPJ Custom Price
OR
poll.end_date is null)
--Bug #2693408: added nvl clause to quantity check
and nvl(poll.quantity, 0) <= nvl(p_in_quantity, 0)
Determining the price based on ship-to-location and
destination organization
and ((poll.ship_to_location_id = v_ship_to_location_id OR poll.
ship_to_location_id is null)
AND
(poll.ship_to_organization_id = p_destination_org_id OR poll.
ship_to_organization_id is null))
and poll.shipment_type in ('PRICE BREAK', 'QUOTATION')
-- <2721775 START>: Make sure Quotation Price Breaks are Approved.
AND ( -- ( poll.shipment_type IS NULL )
( poll.shipment_type = 'PRICE BREAK' )
OR ( ( poll.shipment_type = 'QUOTATION' )
AND ( ( poh.approval_required_flag <> 'Y' )
OR ( EXISTS ( SELECT ('Price Break is Approved')
FROM po_quotation_approvals pqa
WHERE pqa.line_location_id = poll.line_location_id
AND pqa.approval_type IN ('ALL
ORDERS', 'REQUISITIONS')
AND trunc(nvl(l_pricing_date,
sysdate)) -- FPJ Custom Price
BETWEEN
trunc(nvl(start_date_active, sysdate-1))
AND trunc(nvl(end_date
_active, sysdate+1)))))))
-- <2721775 END>
order by poll.ship_to_organization_id ASC, poll.ship_to_location_id ASC,
NVL(poll.quantity, 0) DESC,
trunc(poll.creation_date) DESC, poll.price_override ASC; /*
*/

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

Expiration date and Price break date in blanket purchase agreement

Hi,
In Blanket purchase agreement i see expiration date and in price break i see the from date and to date, can some one tell me the difference between these two dates?
Issue
1.when i try to put an end date(expiration date) to one of the line i get this error message or when i try to cancel the po line by giving some reason it throws the same error.
The error
"You cannot cancel or finally close this agreement line because there are open purchase order lines referencing this document."
Regards
Sudharshan

Hi Sudarshan,
Expiration date under BPA is used to prevent ordering of the item after the date appearing in this expiration field. It will stop you to create new releases incase you are trying to create one after the expiry date of the BPA.
In short, If the item on the agreement has expired but already exists on an open release, you can still use the release. However, the expired line item will not be used for sourcing, and any future releases you create will not allow using the expired item.
Under Price Break, Effective from and to date indicates the validaity of Price break rule for a particular duration. This is restricted to Price break rule only.
Hope this will help.
Regards,
S.P DASH

HT5622 Sorry but I can't order any tunes for my ipod nano because a new trems and agreement statement keeps coming up sooooo where is the agree or disagree ( to check ) located? Read through the info twice even though it is langthy . ????

Sorry I can't order any new itunes for my nano because a new terms and agreement comes up after I press buy . It asks to click on agree or disagree? What I would like to know is where are these 2 terms located. Read through this twice and couldn't find any place to answer this question. So can't order any more music!!!

Hey briannagrace96,
Welcome to Apple Support Communities! I'd check out the following article, it looks like it applies to your situation:
iPod: Appears in Windows but not in iTunes
http://support.apple.com/kb/ts1363
You'll want to go through the following troubleshooting steps, and for more detail on each step follow the link to the article above:
Try the iPod troubleshooting assistant:
If you have not already done so, try the steps in the iPod Troubleshooting Assistant (choose your iPod model from the list).
If the issue remains after following your iPod's troubleshooting assistant, follow the steps below to continue troubleshooting your issue.
Restart the iPod Service
Restart the Apple Mobile Device Service
Empty your Temp directory and restart
Verify that the Apple Mobile Device USB Driver is installed
Change your iPod's drive letter
Remove and reinstall iTunes
Disable conflicting System Services and Startup Items
Update, Reconfigure, Disable, or Remove Security Software
Deleting damaged or incorrect registry keys
Take care,
David

Price Break through the Pricing Agreement API.

Similar Messages

Maybe you are looking for