Blanket purchase oreder price display

Hi all,
I don' want price to be displayed in PO printout for document type FO(blanket purchase order).
I would to know the setting for the same.
Ashok

Hi
If your PO Print form is a custom developed then you can make the Changes in the form itself.
Please take the help of ABAPEr
The logic would be if the PO document type is FO Then you need not print Price details in the PO.
You can get the form details in the Customizing of the message type used for the Purchase order in
SPRO_> IMG-> MM-> Purcahsing > Messages> Output Control-> Message Types-> Define Message Types for Purchase Order->
Select the message type & click on processing routines, here you can see the Print program & the form attched for each medium of Output
Thanks & Regards
Kishore

Similar Messages

Can I modify the column "Net Price" of purchase order to display 3 decimals

Dear expert,
     Can I modify the column "Net Price" of purchase order to display 3 decimals?
     Looking forward to your reply.
     Many thanks.
Best Regards,
Merry

Hi,
You can easily change ur decimal place in OY04 by seeting number of decimal place to ur currency.
But be careful as it cause a huge effect to ur finance documents, read system message carefully before applying.
Regards
ManUfacTuReR

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

Purchase order price change report

Hello
How to retieve the purchase order price change report ? do we have any standard report for it or any table which gives these data?
kindl

HI
Have you activate version management at your end for PO,i think this will help you to track changes of PO for qty,price etc.
[http://wiki.sdn.sap.com/wiki/display/ERPLO/Version+Management]
Regards
Kailas Ugale

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

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

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

Last purchase order price

Hi All
On which table will I be able to find the last purchase order price for a material
Vishnu

Hello, Vishnu
Table name: EINE (Purchasing Info Record: Purchasing Organization Data)
in the above table you can find the last PO price for that material. And the Conditions (Item) values are stored in the table: KONP (table name for Conditions (Item).
Suggestion: The last PO document (i mean PO, which contains the price of the material in the PO line item) is updated in the Purchase Info record.(this you can see in the Info record display through t.code: ME13)
Reward, if it helps,
Regards,
Srin.K
Edited by: sapsrin on Feb 12, 2008 5:51 AM

Change Purchase Requisition Price after assigned to Quotation

Hello.
I created purchase requisition and assigned to Quotation.
It if possible change purchase requisition price when is already assigned to Quotation?
The item price is display and don't let me apply changes.
Regards,
Hector.

Hello.
I did not converted the Purchase Requsition in Purchase Order.
I just running a Test Script, and after assigned a Quotation, the vendor sent me some price changes.
When I call the requisition, the system don't let me change any price.
I believe there is a good reason for that, but I need to read it.
If anyone knows any documentation available, please let me know.

Update PO Header Description field for Blanket Purchase Agreement

Hi all,
I am trying to update description field for Blanket Purchase Agreement using Import price catalog.
Open interface runs successfully and not getting any errors but, the description field is not getting updated.
Is it possible to update BPA using Import Price Catlaog. If not is there any API for this?
Thank you,
Prashanth

If you are having trouble with API, you can update DFF directly. Typically, it is a little/no risk update.
Just make sure that the new DFF value satisfies the value set attached to the DFF / DFF context.
Sandeep Gandhi

Limit/Blanket Purchase Orders and CCM Catalogs

Hi,
Is it possible to put Limit/Blanket Purchase Order items into CCM Catalogs?
John

Hi
It is possible to put anything into a catalog - however that does not mean the catalog item will be interpreted or acceptable to the SRM_SERVER, when passing data from a catlaog, the provided information has to be sufficient to allow for successful creation of a procurement document (not a limit/blanket order), i.e. you need either Material Number or Description, based on which of these are passed you may also then require vendor/UOM/quantity, price etc, it is clearly defined in note [395312|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=395312].
Regards,
Jason

Blanket purchase Agrement

Dear Experts
I have Created Blanket purchase Agrement for a period of 1 year ... and i have one release with some quantity.... supplier has sended and now we need to put receipt...here suppose price of the item has decreased nearly 50% and now i need to change amount in agrement ...how i can do ?
if we change agrement it need re approval right ? if it is re approved now what will happened with the quantity which is waiting for receipt?
2)if suppose we received first release before changing the agrement...what will happens ( can we change price of the item before payment)?

1) There will be no impact on the quantity awaiting receipt. You can go ahead and receive it
2) Yes.
Hope this helps,
Sandeep Gandhi

I have a macbook 13"screen purchased in 2007; I want to hook it up to my HDTV; I purchased a mini display port to hdmi adaptor but it does not fit. what kind of adaptor will work for this model?

I have a Macbook, 13" screen, purchased in 2007. I want to hook it up to my HDTV; I purchased a mini display port to hdmi adapter but it does not fit. Any suggestions?

If you connect yourMacBook using a MiniDVI/HDMI adapter you will need to use external speakers for audio since the pre-2010 MacBooks will only send video through the MiniDVI or MiniDisplay Port . The MiniDVI/HDMI doesn't carry audio and there's no audio plugs on the TV to work with HDMI since it's expecting audio with the HDMI.
If your TV has a DVI input plug you can use a MiniDisplayPort/DVI adapter. Then a DVI cable to the DVI input plug on the TV. The TV will have RCA audio plugs for use with the DVI. Plus DVI gives a sharper image than HDMI.

I have a Samsung HD TV and I purchased a Mini Display port to HDMI Adapter today. For some strange reason I get no display on my HD tv. I even tried switching a few HDMI cables and nothing popped up. I made sure my computer was updated. Help pls

I have a Samsung HD TV and I purchased a Mini Display port to HDMI Adapter today. For some strange reason I get no display on my HD tv. I even tried switching a few HDMI cables and nothing popped up. I made sure my computer performed all software updates, and I even tried calling Apple Support. They just told me to keep trying different hdmi cables and see if anything pops up. Does anybody know what the problem is? My HDMI cable is from "rocketfish" also my display port is too.

You may have the screen refresh rate set higher than the TV is generally able to track reliably. It may be able to get there most times, but occasionally loses sync because it is out of its nominal range.
I suggest you sit down with the manual for the TV and find out what resolutions at what refresh rates it intends to support through VGA, and make sure your screen settings are near (or below) those limits.

Blanket purchase oreder price display

Similar Messages

Maybe you are looking for