Blanket Sales Agreements

Can Blanket sales agreements be captured as demand in ASCP?

Blanket Sales agreements are intentionally not collected by ASCP. ASCP will pick up the specific sales order releases only.
What is your intent?
Regards,
Kevin
PS. I'd like if you would add your first name to your profile or your posts.

Similar Messages

Item/lot Reservation against blanket sales agreement

Hi all.
my client has a requirement (in warehousing environment 11.5.10 CU2) to reserve the entire lot for a customer (preferably against a blanket sales agreement) and release the BSA in small quantities over a period of time. The lot is has to be reserved for a specific customer, may stay in warehouse for 1 or 2 years sometime, but, client agreed to received in small quatities.
Currently we are creating a dummy sales order line to reserve for that customer and manually decreasing the total reserved quantity everytime, we ship a small quatity to customer. Thinking of creating as BSA and release the shipment as and when needed, instead of standard sales order, but, no way to hold reservation at BSA level.
Any options to reserver at BSA level or any better way to hold the item in stock for a customer over multiple SO or releases over 1 or 2 year period. A particular lot is reserved for a customer, until the whole quantity of the lot is exhausted.
thanks.
Ganesan.

If you have a small number of customers, can you create a subinventory for each customer?
When you receive the material for a customer, move it to the appropriate subinventory.
And in your defaulting rules, you can default a given subinventory for a given customer.
This way, whenever you get a "Real" order for a customer, the onhand in appropriate subinventory will get reserved to that customer. This way, you don't have to create dummy orders, dummy reservations and then delete the dummy ones later to create real ones.
Just a thought,
Sandeep Gandhi

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.

Processing Constraints and Blanket Sales Agreement

Hi all,
We are using Blanket Sales Agreement, and we have defined a processing constraint to make Payment Term a required field.
If user adds a blanket and informs payment term before saving, everything goes fine. However, if user tries to save before informing payment term, the error message from processing constraint is presented, until now everything working as planned.
After that, user informs payment term and tries to save it again. In this case, OM does not generate blanket number and does not allow saving the blanket agreement. In order to be able to add the blanket, user must delete the current agreement, and add a new one, this time informing the required field. Is this supposed to work like that or is there additional setup to use processing constraints with blanket sales agreement?
Thanks for your help,
Ketter Ohnes

Hi Ketter,
to me this sounds like a BUG. I can not imagine that this is the intended behaviour. Sounds like the blanket number gets generated only once, when the form opens.
I would recommend to open a Service Request (SR) on Metalink for that issue and ask Oracle Support for help on that.
best regards,
David.

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?

Sales Agreement workflow errored on 3205: is not a valid role or user name.

Hi experts,
We're currently on EBS R12.1.2 We're running into an issue that seems like a very general issue that other businesses would have encountered before. We have a business user who creates most of sales agreements. When this business user left the company, we set active end date on the particular userid. Now, when we go into these sales agreements originally created by this particular userid, and put in the expiration date to expire these sales agreement. We're seeing the sales agreement workflow erroring out in the pre-notification workflow email with error 3205: is not a valid role or user name.
It seems to be this is a very typical business scenario. If you have encountered this problem, please share how you resolved this issue within your oracle apps environment.
Thank you in advance for your help,
Jennifer

Hello,
We have the same problem in 11.5.10.2. If we want use this blanket sales agreement I have to skipped this notification by sysadmin and after this I can extend end date and another user can use this BSA.
Look at Extend The Expiration Date For Closed Non-Active Expired BSA Blanket Sales Agreement [ID 1394888.1]
Regards,
Luko

Query on Blanket Purchase Agreement-- Lines Agreement

Hi friends,
I have a query on Blanket purchase agreement.When a minimum release amount is provided in the Terms >Agreement controls it is holding fine and taking that value perfectly for each release.
But when in the PO Lines,under the Agreement when i specify a Minimum relase,Quantity agreed and Amount agreed for a line,the system is not picking up the values mentioned here when i create a release.
Eg. Created a Blanket PO with a line.
For the line under the Agreement tab, specified the following values.
Minimum release : 100.00
Quantity agreed : 100
Amount agreed : 10,000.00
1.When i created a release,it allowed me to create with the release amount of 20.00
2. When i created one more release for a quantity of 500,it allowed me to go ahead.System didn't stop me or throw me any message like you are crossing the qty agreed.
How come these two cases 1 and 2 happen.
This is contradicting the agreement controls for the blanket PO line.
FYI: At the header level ,the minimum release amount are holding good and working fine.
Only at the PO Line ,the system is not taking the agreement values.
Any pointers in this regard would be great help.
Regards,
Bala.

Hi All,
I have issue with Blanket Sales Agreement(BSA) in PDF format for approval.
NOTE: To Preview and Print from the Blanket Sales Agreement header, you can use the Action, Preview and Print or right mouse click to access Preview and Print, to Preview and Print from the Blanket Sales Agreement header. When a specific blanket is open, you can initiate preview of the formatted contract document. The document always displays in PDF format when previewed from the blanket sales agreement; you will not be required to choose a file output format.
In our test instance,
I am not able Preview Blanket Sales Agreement and send it for approval through the Workflow Notification.
Requirement is customer should view the document.
Please, let me know the reason for not able to Preview the BSA.
Many thanks.
Regards
Dass
Edited by: user10255615 on Nov 2, 2008 10:38 PM

BLANKET SALES ORDER의 DATA가 ORDER의 DEFAULT 값으로 되지 않는 이유?

제품 : MFG_OM
작성날짜 : 2004-10-12
BLANKET SALES ORDER의 DATA가 ORDER의 DEFAULT 값으로 되지 않는 이유?
===================================================================
PURPOSE
Blanket Sales Agreement form에서 Create Release button을 선택하면
Blanket Sales Agreement의 정보들이 Sales Order form의 default 값으로
입력되어 보여야 하나 현재는 Sales Order form은 open 되지만 header나
line에 blanket의 data가 populated 되지 않는다.
이 note에서는 그 원인과 해결책을 알아본다.
Explanation
Change(s)
=========
Blanket Sales Agreement는 정의 되어 있고, Customer 정보는 Header에 입력
되어 있다. 또한 Line item은 특정 products을 위해 정의되어 있다.
Blanket agreement는 blanket order type과 연관되어 있다.
원인
====
보통 Agreements에 대한 Orders/Releases를 신청하는 Customers는 먼저
folder를 만들어야만 한다. 이 folder는 order header에 blanket number
field는 가지며 default folder로 저장되야 한다.
Blanket Sales Agreement form에서 Create Release button을 click 하면
Sales Order form이 열리고 cursor는 blanket agreement field로 이동할
것이다.
User가 다른 field로 tab을 하면 customer data는 blanket에서 release
order로 default 조회된다.
만약 Customer data가 아닌 다른 data를 blanket agreement에서 release
order로 default 하길 원한다면, 먼저 그 영향을 주는 defaulting rule을
생성해야 한다.
Fix
=====
Blanket으로부터 data를 default로 받길 원하면 Sales order header와
line에 있는 모든 field에 대한 defaulting rules은 정의되어져 있어야 한다.
Defaulting rule에서 defaulting source로 'Blanket'을 이용하여 가능하다.
Example
Price List는 blanket agreement의 값을 default로 해야 하는 business rule
이 있다면, Price List의 defaulting rules을 아래와 같이 변경한다.
Price List First Default
=========================
Source Type : Related Record
Default Source : Blanket Agreement
위와 같은 rules은 blanket header를 sales order header default로 하거나
blanket line을 sales order line의 default로 하려면 먼저 생성되어져야
한다.
Reference Documents
Note 253150.1

Sales Agreement query - multiple agreements

I'm wondering if there are any queries or reports out there that will show multiple sales agreements, the customers sales amounts and their accrual amounts related to COOP and Volume Rebates? Typically you need to run VB01,02 or 03 but this only produces the data for one agreement at a time. Running VB(8 will return multiple agreement but provides no financial data.
Our IT department claims this would be a major project which means it is stuck on the backburner. I feel like this should be a very basic and commonly requested report. Does anyone have any suggestions?

Hello,
We have the same problem in 11.5.10.2. If we want use this blanket sales agreement I have to skipped this notification by sysadmin and after this I can extend end date and another user can use this BSA.
Look at Extend The Expiration Date For Closed Non-Active Expired BSA Blanket Sales Agreement [ID 1394888.1]
Regards,
Luko

Updating unit_price in PO_LINES for a Blanket Purchase Agreement

Hello,
In R11i, 'PO_CHANGE_API1_S.update_po' was the API we call to achieve the price update of blanket PO.
This api in turn calls 'PO_DOCUMENT_UPDATE_GRP'.
The api 'PO_DOCUMENT_UPDATE_GRP' has two overloaded procedures 'update_document'.
a. 'update_document' with 18 parameters is not suited for R12 as per oracle api documentation.
b. Thus, we have to call 'update_document' with 12 parameters for achieving the objective.
Thus, I tried to update price using the following sample code attached. But am hitting on few issues,
a. If I do not pass 'release' or 'shipments' or 'distributions' information as part of this api call, the api fails at the validation indicating 'Invalid Doc Id'.
b. If I do pass 'release' or 'shipments' or 'distributions' information, inside the api for 'some' reason, they reassign the po_header_id as 'NULL' and cause of that in another validation block inside the same API it throws an error indicating 'Releases have no lines'.
I have to admit my search in metalink/other forums has not really helped me to find out how to 'update a blanket purchase agreement'.
Please advise.
Thanks,
Santhosh
sample code (without shipment/releases/distributions):
DECLARE
lv_var            VARCHAR2(2000) := NULL;
lr_changes        PO_CHANGES_REC_TYPE;
x_api_error       PO_API_ERRORS_REC_TYPE;
x_return_status   VARCHAR2(4000);
dummy             NUMBER;
BEGIN
lr_changes := PO_CHANGES_REC_TYPE(21696 -- header id
+,NULL -- release id+
+,PO_LINES_REC_TYPE(po_tbl_number(54121) -- line id+
+,po_tbl_number(100) -- price+
+,po_tbl_varchar30(NULL) -- vendor product num+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_date(NULL) -- start date+
+,po_tbl_date(NULL) -- expiration date+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_varchar30(NULL) -- request uom+
+,po_tbl_number(NULL) -- secondary_quantity+
+,po_tbl_varchar30(NULL) -- request sec uom+
+,po_tbl_varchar1(NULL) -- delete record+
+,po_tbl_varchar240(NULL) -- preferred_grade+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_varchar30(NULL) -- unit meas lookup code+
+,po_tbl_number(NULL) -- item id+
+,po_tbl_number(NULL) -- from header id+
+,po_tbl_number(NULL) -- from line id+
+,po_tbl_varchar1(NULL) -- has ga reference+
+,po_tbl_varchar1(NULL) -- cancel flag+
+,po_tbl_varchar30(NULL) -- closed code+
+,po_tbl_varchar30(NULL) -- value basis+
+,po_tbl_varchar30(NULL) -- purchase basis+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_date(NULL) -- start date+
+,po_tbl_date(NULL) -- expiration date+
+,po_tbl_number(NULL) -- unit price+
+,po_tbl_number(NULL) -- from line location id+
+,po_tbl_number(NULL) -- secondary quantity+
+,po_tbl_varchar30(NULL) -- secondary uom+
+,po_tbl_varchar40(NULL) -- item number+
+,po_tbl_varchar240(NULL) -- preferred grade+
+,po_tbl_varchar1(NULL) -- from price break+
+,po_tbl_number(NULL) -- from line location id+
+,po_tbl_number(NULL) -- base unit price+
+,po_tbl_varchar1(NULL) -- manual price change flag+
+,po_tbl_varchar30(NULL) -- new secondary uom+
+)+
+,PO_SHIPMENTS_REC_TYPE(po_tbl_number(NULL) -- line location id+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_date(NULL) -- promised date+
+,po_tbl_number(NULL) -- price override+
+,po_tbl_number(NULL) -- parent line location id+
+,po_tbl_number(NULL) -- split shipment num+
+,po_tbl_date(NULL) -- need by date+
+,po_tbl_number(NULL) -- ship to location id+
+,po_tbl_date(NULL) -- sales order update date+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_varchar30(NULL) -- request uom+
+,po_tbl_number(NULL) -- secondary quantity+
+,po_tbl_varchar30(NULL) -- request secondary_uom+
+,po_tbl_varchar1(NULL) -- delete record+
+,po_tbl_varchar240(NULL) -- preferred grade+
+,po_tbl_varchar30(NULL) -- payment type+
+,po_tbl_varchar240(NULL) -- description+
+,po_tbl_varchar25(NULL) -- new supplier order num+
+,po_tbl_number(NULL) -- po line id+
+,po_tbl_number(NULL) -- quantity+
+,po_tbl_varchar30(NULL) -- unit meas lookup code+
+,po_tbl_varchar1(NULL) -- cancel flag+
+,po_tbl_varchar30(NULL) -- closed code+
+,po_tbl_number(NULL) -- item id+
+,po_tbl_number(NULL) -- ship to organization id+
+,po_tbl_varchar1(NULL) -- drop ship flag+
+,po_tbl_number(NULL) -- quantity received+
+,po_tbl_number(NULL) -- quantity billed+
+,po_tbl_number(NULL) -- amount received+
+,po_tbl_number(NULL) -- amount billed+
+,po_tbl_varchar1(NULL) -- accrue on receipt flag+
+,po_tbl_varchar30(NULL) -- value basis+
+,po_tbl_varchar30(NULL) -- purchase basis+
+,po_tbl_number(NULL) -- amount+
+,po_tbl_number(NULL) -- price override+
+,po_tbl_number(NULL) -- parent quantity+
+,po_tbl_number(NULL) -- parent amount+
+,po_tbl_number(NULL) -- secondary quantity+
+,po_tbl_varchar30(NULL) -- secondary uom+
+,po_tbl_varchar40(NULL) -- item number+
+,po_tbl_date(NULL) -- approved date+
+,po_tbl_varchar1(NULL) -- encumbered flag+
+,po_tbl_varchar30(NULL) -- shipment type+
+,po_tbl_number(NULL) -- quantity shipped+
+,po_tbl_varchar240(NULL) -- preferred grade+
+,po_tbl_varchar30(NULL) -- payment type+
+,po_tbl_varchar1(NULL) -- from price break+
+,po_tbl_varchar1(NULL) -- manual price change flag+
+,po_tbl_varchar1(NULL) -- sec qty grade change only+
+)+
+,PO_DISTRIBUTIONS_REC_TYPE(po_tbl_number(NULL) -- po distribution id+
+,po_tbl_number(NULL) -- quantity ordered+
+,po_tbl_number(NULL) -- parent distribution id+
+,po_tbl_number(NULL) -- split shipment num+
+,po_tbl_number(NULL) -- amount ordered+
+,po_tbl_varchar30(NULL) -- request uom+
+,po_tbl_varchar1(NULL) -- delete record+
+,po_tbl_number(NULL) -- po line id+
+,po_tbl_number(NULL) -- line location id+
+,po_tbl_number(NULL) -- quantity ordered+
+,po_tbl_varchar30(NULL) -- unit meas lookup code+
+,po_tbl_number(NULL) -- item id+
+,po_tbl_number(NULL) -- quantity delivered+
+,po_tbl_number(NULL) -- quantity billed+
+,po_tbl_number(NULL) -- amount delivered+
+,po_tbl_number(NULL) -- amount billed+
+,po_tbl_varchar30(NULL) -- value basis+
+,po_tbl_varchar30(NULL) -- purchase basis+
+,po_tbl_number(NULL) -- amount ordered+
+,po_tbl_number(NULL) -- parent line location id+
+,po_tbl_number(NULL) -- award id+
+,po_tbl_number(NULL) -- project id+
+,po_tbl_number(NULL) -- task id+
+,po_tbl_number(NULL) -- distribution num+
+,po_tbl_varchar1(NULL) -- encumbered flag+
+,po_tbl_number(NULL) -- req distribution id+
+,po_tbl_date(NULL) -- creation date+
+)+
+);+
dbms_output.put_line('BEFORE API');
fnd_global.apps_initialize
+(user_id => 8171+
+,resp_id =>20707+
+,resp_appl_id => 201+
+);+
dbms_application_info.set_client_info(201);
mo_global.init('PO');
FOR i IN 1..2
LOOP
BEGIN
PO_DOCUMENT_UPDATE_GRP.update_document
+(p_api_version => '1.0'+
+,p_init_msg_list => NULL+
+,x_return_status => x_return_status+
+,p_changes => lr_changes+
+,p_run_submission_checks => NULL+
+,p_launch_approvals_flag => NULL+
+,p_buyer_id => NULL+
+,p_update_source => NULL+
+,p_override_date => NULL+
+,x_api_errors => x_api_error+
+,p_approval_background_flag => NULL+
+,p_mass_update_releases => NULL+
+);+
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line ('SQLERRM <'||SQLERRM||'>');
END;
dbms_output.put_line('value of x_return_status<'||x_return_status||'>');
dbms_output.put_line ('SQLERRM <'||SQLERRM||'>');
dbms_output.put_line ('get msg <'||fnd_message.get||'>');
dbms_output.put_line('value of message_name <'||x_api_error.message_name(1)||'>');
dbms_output.put_line('value of message_name <'||x_api_error.message_text(1)||'>');
END LOOP;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line ('SQLERRM <'||SQLERRM||'>');
dbms_output.put_line('value of x_return_status<'||x_return_status||'>');
END;
+/+

Hi Alister,
You can't create a release of a BPA through API, there is no such APIs provided by oracle.
Where as you can create a BPA by using API. You need to dump/poplulate data in PO_headers_interface & PO_Lines_intreface table.. Then use Purchasing Documents Open Interface API to create a BPA.
Regards,
S.P DASH

API or interface table to create releases for a blanket purchase agreement

Hi
I need to know if Oracle provides a standard API or interface table to create releases for a blanket purchase agreement.
I tried using the release_num field in PO_HEADERS_INTERFACE, PO_LINES_INTERFACE. But this is not working.
I'm able to create the blanket purchase agreement using the open interfaces, but not the releases.
Regards,
Alister

Hi Alister,
You can't create a release of a BPA through API, there is no such APIs provided by oracle.
Where as you can create a BPA by using API. You need to dump/poplulate data in PO_headers_interface & PO_Lines_intreface table.. Then use Purchasing Documents Open Interface API to create a BPA.
Regards,
S.P DASH

Purchasing Document Open Interface Error - Blanket Purchase Agreement

Hi all.
I have a problem creating a blanket purchase agreement through the interface. What i did was this:
INSERT INTO po_headers_interface (interface_transaction_id,
batch_id,
interface_source_code,
process_code,
action,
group_code,
org_id,
document_type_code,
document_num,
currency_code,
agent_id,
vendor_id,
vendor_site_id,
ship_to_location_id,
bill_to_location_id,
approval_status,
amount_agreed,
effective_date,
expiration_date)
VALUES
INSERT INTO po_lines_interface (interface_line_id,
interface_header_id,
action,
line_num,
line_type,
line_type_id,
item_id,
category_id,
quantity,
unit_price,
taxable_flag,
tax_code)
VALUES
Then i run from the application "Import Price Catalogs" to import the BPA.
I get this error in po_interface_errors: "No corresponding Blanket Agreement line available for this Price Break record. (COLUMN_NAME=SHIPMENT_NUM)"
I mention I don't want to create a price break for the BPA i just want to create the line for the BPA. Anyone knows what I am doing wrong????
I also got other errors b4 but I could resolve them.
Thanks for any help on this.
Edited by: user9525262 on Feb 14, 2012 12:08 AM

Guys I found It out!!!!!! YEEEEEEEEE!
It was because the quantity values. The lines on BPA doesn't accept any quantity on it.
I write this because I searched the internet alot and the forums about this problem who also others had and now they can see where in fact the problem lies.
Have all a nice day.
Edited by: user9525262 on Feb 14, 2012 12:35 AM

ESYU: PDOI를 이용하여 생성되지 않은 Blanket Purchase Agreements를 PDOI를 이용하여 update 할 수

Symptoms
Oracle Purchasing - Version: 11.5.10.2
Information in this document applies to any platform.
PDOI에 의해 생성되지 않은 'Blanket Purchase Agreements'를 PDOI를 이용하여 update 할 수 있는 방법을 알아본다.
Solution
이것은 Procurement family pack H나 그 이상의 version에서는 가능하다.
Procurement family pack H(11.5.8 포함) 이전 version에서는 PDOI를 이용해 생성되지 않은 Blanket Purchse Agreements를 PDOI나
'Import Price Catalogs' concurrent program을 이용하여 update 하는 것은 불가능하였다.
11.5.8과 이 이상의 version에서 비공개 Enhancement 2128450가 이행되었고, 이 ER은 interface loading시
PO_HEADERS_INTERFACE에 VENDOR_DOC_NUM가 지정되지 않더라도 Blanket Purchase Agreements를 update 가능하게
만들었다.
Oracle Manufacturing APIs 와 Open Interfaces Manual, Release 11i, Part No. A95955-03, September 2004 documentation은
update가 되었고, 다음은 10-39 page에 update 된 내역이다.
The Purchasing Documents Open Interface updates blanket purchase agreements and catalog quotations
by doing the following:
First, it identifies the catalog quotation or blanket purchase agreement that needs to be updated by
comparing the supplier document number (VENDOR_DOC_NUM in the PO_HEADERS_INTERFACE table)
or document number (DOCUMENT_NUM in PO_HEADERS_INTERFACE and SEGMENT1 in PO_HEADERS_ALL)
with the existing supplier document number (VENDOR_ORDER_NUM for a blanket agreement,
or QUOTE_VENDOR_QUOTE_NUMBER for a catalog quotation in the PO_HEADERS table).
The supplier (VENDOR_ID or VENDOR_NAME) and document type (DOCUMENT_TYPE_CODE) must also match.
The Purchasing Documents Open Interface matches only to currently or future-effective documents that are
not canceled or finally closed.
Its important to note that it is necessary to supply DOCUMENT_NUM in the PO_HEADERS_INTERFACE when trying to
update blanket purchase agreements which has not been created through the PDOI.
For documents created through PDOI, VENDOR_DOC_NUM can be specified in the PO_HEADERS_INTERFACE.
Following is a sample script that has been used to load the PO_HEADERS_INTERFACE and PO_LINES_INTERFACE
to update the price of a blanket agreement.
예제 script: PO_HEADERS_INTERFACE and PO_LINES_INTERFACE를 이용해 blanket agreement의 price를 update
INSERT
INTO po_headers_interface
(interface_header_id,
batch_id,
action,
org_id,
document_type_code,
document_num,
vendor_id,
vendor_site_code,
vendor_site_id,
reference_num)
values
(po_headers_interface_s.nextval,
'8484844',
'UPDATE',
204,
'BLANKET',
'5360',
2925,
'USA',
4622,
'TEST_VEND_DOC02');
insert into PO_LINES_INTERFACE
INTERFACE_HEADER_ID
,INTERFACE_LINE_ID
,ACTION
,LINE_NUM
,DOCUMENT_NUM
,LINE_TYPE_ID
,ITEM
,ITEM_DESCRIPTION
,UNIT_OF_MEASURE
,UNIT_PRICE
values(
PO_HEADERS_INTERFACE_S.CURRVAL
,PO_LINES_INTERFACE_S.NEXTVAL
,'UPDATE'
,'1'
,'5360'
,'1'
,'AS54888'
,'Sentinel Standard Desktop'
,'Each'
,1204.24
Note 746040.1

Unable to finally close blanket purchase agreement

Hello,
I am unable to final close the blanket agreement due to error: "Open releases exist against the purchase document." I checked and all the releases status are closed, the amount billed matched amount received. Does anyone know how to fix this? I researched on METALINK and it doesn't help much.
Thanks.

Hi,
I understand, the current system functionality does not support the feature that you are looking for:
The following ER's have been filed for this issue:
Bug 5065862: PDOI DOES NOT UPDATE PRICE BREAKS ON BLANKET WITH EFFECTIVE DATES
Bug 5246003: ALLOW PDOI TO UPDATE PRICE BREAKS ON BLANKET PURHCASE AGREEMENT
Bug 7285119: UPDATING BPA THROUGH PDOI, NEED TO BE ABLE TO UPDATE PRICE BREAK INFO
Bug 7219129: DATAFIX:UPDATING BPA THROUGH PDOI, NEED TO BE ABLE TO UPDATE PRICE BREAK INFO
Regards,
Paarthy

Link India Localization with Blanket Purchase Agreements and Releases

Could anyone highlight on how India Localization Taxes be linked with Blanket Purchase Agreements and Blanket Releases?
Any additional Setups required?
Shubhendu Chakraborty
Kolkata.INDIA.

Only Amount Agreed field on header level can control the checks on the blanket purchase order.

Blanket Sales Agreements

Similar Messages

Maybe you are looking for