Blanket PR Creation

Hi Experts,
I am using BAPI_REQUISITION_CREATE to create blanket requisition. Blanket requisition is successfully created but the 'LIMITS' data are not stored into the particular Blanket PR.
Below is my coding, any mandatory fields or indicators I left during Blanket PR creation?
*===Item===
    PR_ITEM-PREQ_ITEM = '1'.    "<--Item Number>
    PR_ITEM-PUR_GROUP = 'C02'.    "<--Purchasing Group (Department)
    PR_ITEM-SHORT_TEXT = 'BLANKET'.    "<--Short Text
*    PR_ITEM-FIXED_VEND = GT_DATA-FLIEF.    "<--Fixed Vendor
    PR_ITEM-DES_VENDOR = '001CDO0001'.    "<--Desired Vendor
    PR_ITEM-DELIV_DATE = '20090129'.    "<--Delivery Date
    PR_ITEM-DOC_TYPE   = 'ZPR4'.    "<--Document Type
    PR_ITEM-ACCTASSCAT = 'K'.    "<--Account Assignment Category
*    PR_ITEM-QUANTITY   = '1'.    "<--Quantity
*    PR_ITEM-UNIT       = 'AU'.    "<--UoM
    PR_ITEM-MAT_GRP    = '100'.    "<--Material Group
    PR_ITEM-PLANT      = '1101'.    "<--Plant
*    PR_ITEM-C_AMT_BAPI = '1000'.    "<--Valuation Price
*    PR_ITEM-CURRENCY   = 'MOP'.    "<--Currency
    PR_ITEM-ITEM_CAT   = '1'.    "<--Item Category
    APPEND PR_ITEM.
    CLEAR PR_ITEM.
*===Account Assignment===
    PR_ACCOUNT-COST_CTR = '0001430101'. "<--Cost Center
    PR_ACCOUNT-G_L_ACCT = '0008510002'.
    APPEND PR_ACCOUNT.
    CLEAR PR_ACCOUNT.
*===Limits===
    PR_LIMIT-EXP_VALUE = '1000.0'.
    PR_LIMIT-LIMIT      = '1000.0'.
    APPEND PR_LIMIT.
    CLEAR PR_LIMIT.
CALL FUNCTION 'BAPI_REQUISITION_CREATE'
    IMPORTING
      NUMBER                         = PR_NO
    TABLES
      REQUISITION_ITEMS              = PR_ITEM
      REQUISITION_ACCOUNT_ASSIGNMENT = PR_ACCOUNT
      REQUISITION_LIMITS             = PR_LIMIT
*      REQUISITION_SERVICES           = PR_SERVICE
*      REQUISITION_SRV_ACCASS_VALUES = PR_SRV_ACCASS_VAL
      RETURN                         = PR_RETURN.
thank you.
Best Regards,
Weng

hi
try calling BAPI_TRANSACTION_COMMIT after you have used BAPI_REQUISITION_CREATE
hope this helps
regards
Aakash Banga

Similar Messages

Creation of Blanket PO having Multiple Line items using Bapi_po_create1

Hi
How to create a Blanket Purchase ordetrs using Bapi BAPI_PO_CREATE1. The PO has multiple line items.
Regards
Lakshman

Maybe this will help:
[blanket purchase order (MM)|http://help.sap.com/saphelp_srm30/helpdata/en/35/26c019afab52b9e10000009b38f974/content.htm]
Rob

Reg. creation of Blanket Order through BAPI_PO_CREATE1

Hi All,
I have a requirement of creating framework order of document type FO. When I fill bapi interface correctly, I am getting an error message as either error SE-518 u201CNo account assignment exists for service lineu201D or error 06 436-In case of account assignment, please enter acc. assignment data for item". I even tried in reverse way of filling bapi interface of po create1 by seeing from BAPI_PO_GETDETAIL1 of already created PO.but still I face same error. I filled up POLIMTS,with dummy package value in POSERVICES,POITEM,POITEMX, and account assignment details in POACCOUNT,POACCOUNTX tables of BAPI_PO_CREATE1 inetrface.
If any one of you has worked on this before, i request you to send the code or any suggestion on how to proceed.
Srikanth.

i have the same problem. Can you suggest me your solution.
Thank in advance.

Questions about PO creation / update / cancel interfaces

Hi there,
An E-Business Suite 11.5.10.2 customer wants to use the 11i PO creation / update / cancel interfaces in order to manage Purchase Orders created from a 3rd party system.
I've been through the 'Oracle Purchasing Open Interfaces' guide (115mfgapi.pdf), but it's still unclear to me whether:
1/ It is possible or not to add a new PO line to an existing PO through the interfaces ? If yes, how do one do that: what interface ? sample code ?
2/ It is possible or not to change the distribution (= accounting information) of an existing PO line ? If yes, ...
3/ It is possible or not to reject the full PO document if a single line fails during the PO creation ? Same for a batch of POs: reject the full batch if a single PO fails ?
4/ Is it possible or not to cancel a PO line even if the shipment already occured ? And even if the payment already occured ? Are there some controls here ?
Thanks for your help,
Kind regards - Hugues

1. Answer is YES. You can add a line to an existing standard purchase order by choosing the UPDATE. This can be done through Purchase Documents Open Interface.
I can not give an example. It's quite long to write it. But You should use Open interface user guide to find nessesary columns. Just insert new row with status UPDATE and try to import
2. Think You can NOT.
3. Answer is YES. You can do it. Use "Cancel PO API". Function name is PO_Document_Control_PUB.control_document ().
For technical details read Open interface UG.
You must create exception to be avoid problems if some lines can not be canceled.
4. Answer is YES. You can do it if there's still expected quantity to recive.
boldJust from UG:*bold* :)
bold1. Purchase Order Change APIs. bold
boldThe APIs enable you to do the following*bold*:
- Record Acceptance/Rejection in Oracle Purchasing
- Update quantity, price, and promise date on standard purchase orders or releases in Oracle Purchasing
boldSo only qty, promissed date, price*bold*
boldRead next*bold*:
Line Level Validation and Update: This logic occurs when LINE_NUM is not null
and SHIPMENT_NUM is null.
1. No update occurs if the line status is FINALLY CLOSED or CANCELLED.
2. The new quantity or price value must be positive.
3. If updating quantity, the new quantity must be greater than or equal to the
greater of total quantity_received of all shipments and total quantity_billed
of all shipments for this line. After the update takes place, the new quantity
will be prorated at the shipment level and for each shipment the quantity is
prorated at the distribution level if applicable.
4. If updating price, no update occurs if a receipt has been created against one
of the line’s shipments and it's been accrued upon receipt. No update
occurs if an invoice has been created against one of the line’s shipments.
After a price update takes place, price changes are rolled down to the
shipment level for standard POs. No price update occurs for a release if the
Price Override flag on the blanket purchase agreement Line is No.
boldSummary:*bold*
boldYou can update qty if still there's a qty to receive (Expected) and if PO still is not canceled*bold*
boldEXAMPLE:*bold*
Usage Example
set serveroutput on;
-- After the API completes, do not forget to commit if the result is 1
-- and rollback if the result is 0.
DECLARE
l_result NUMBER;
l_api_errors PO_API_ERRORS_REC_TYPE;
BEGIN
-- This needs to be changed according to your environment setup.
FND_GLOBAL.apps_initialize ( user_id => 1318, resp_id => 50578, resp_appl_id => 201 );
-- Record an acceptance of Y for PO 1261.
l_result := PO_CHANGE_API1_S.record_acceptance(
x_po_number => 1261,
x_release_number => null,
x_revision_number => 0,
x_action => 'NEW',
x_action_date => null,
x_employee_id => 588,
x_accepted_flag => 'Y',
x_acceptance_lookup_code => 'On Schedule',
x_note => 'All valid',
x_interface_type => 'APITEST',
x_transaction_id => null,
version => '1.0');
IF (l_result <> 1) THEN
-- Handle the errors in the PO_INTERFACE_ERRORS table.
END IF;
-- Change the quantity to 5 on line 1, shipment 1 of PO 1263.
l_result := PO_CHANGE_API1_S.update_po (
x_po_number => 1263,
x_release_number => 1,
x_revision_number => 1,
x_line_number => 1,
x_shipment_number => 1,
new_quantity => 5,
new_price => NULL,
new_promised_date => NULL,
launch_approvals_flag =>'Y',
update_source => NULL,
version => '1.0',
x_override_date => NULL,
x_api_errors => l_api_errors,
p_buyer_name => null
IF (l_result <> 1) THEN
-- Display the errors
FOR i IN 1..l_api_errors.message_text.COUNT LOOP
dbms_output.put_line ( l_api_errors.message_text(i) );
END LOOP;
END IF;

Blanket PO functionality in MM

Hi All:
I am a FICO guy and need some assistance in understanding Blanket PO Functionality in SAP.
This is what I have understood so far:
? Use FO document type in ME21
? Use "B" in item category
? Provide a maximum limit for Blanket PO (BPO)
? Provide validity for BPO
? We create a blank PO with unspecified materials, quantity
and delivery dates
This is what I would like to know:
? Lets say the BPO was created on Jan 1, and the requirement for procurement arises in March, June, October and December. In this case do we have to create a new PO with reference to BPO for each of these months?
? If not, do we have to modify the BPO that was originally created?
? How does vendor receive our requirement for materials?
? Can we use ERS in this case for automatically generating invoices?
Edited by: Vj on Dec 17, 2007 12:12 PM

hi,
This is what I would like to know:
1. Lets say the BPO was created on Jan 1, and the requirement for procurement arises in March, June, October and December. In this case do we have to create a new PO with reference to BPO for each of these months?
Answer: there is no need to create the separate PO for each month. the use of framework order and item category B open the value limits and validity period. give the validity period as per your requirement and the value.
thru BPO you instruct the vendor before hand in this particular period you are going to buy these specific material of total amount assigned. you can call him and inform that you require that material, it is helpful in those cases.
2. If not, do we have to modify the BPO that was originally created?
Answer: if the material are not covered what you have agreed with him may be yes.
3.How does vendor receive our requirement for materials?
Answer: you can make a call or send a intimation about this.
4.Can we use ERS in this case for automatically generating invoices
Answer : yes you can.
I am writing below the complete process of BPO, this will clear your doubts.
The use of blanket purchase orders enables you to simplify the procurement process for low-value consumables and thus reduce costs.
**Business Example
For some of the office supplies needed by your firm, you can simply phone your vendor to give notification of your requirements. The goods are then delivered directly to the individual offices, so that a confirmed
goods receipt does not have to be recorded in the system. To cover such transactions, you have created a blanket purchase order in the system.
You check each invoice you receive from the vendor against the limit and validity period of the blanket PO.
Advantages of Blanket POs
With certain procurement transactions, the costs of procurement are disproportionately high in relation to the value of the material or service involved. This is frequently the casewith office supplies (such as pencils
and notepads) and services of relatively minor importance (such as small repairs, cleaning work, and courier services), for example.
Procurement costs - which in the case of standard procurement processes can be quite high - are significantly reduced if a so-called blanket purchase order is created instead of a standard PO. Such a single long-term purchase order can be used to procure a variety of materials or services whose
modest value does not justify the high processing cost of issuing a series of individual POs.
The main advantage of using blanket POs is thus the associated reduction in order processing costs. Transaction costs are lower with blanket POs because:
 The blanket PO is valid for a longer period.
 There is no goods receipt or service entry.
 It is not necessary to create PO items for individual procurement transaction
When creating a blanket PO, you should use document type FO because this document type causes the header fields Validity Start and Validity End to become mandatory entry fields. You must enter the item category B in the PO item overview. The entry of this item category causes the Limits tab page to appear on the item detail screen. There, you enter an overall limit and an expected value. The overall limit represents the maximum value for which invoices referencing the PO item can be posted without the system issuing messages. If the overall limit is exceeded when an invoice is posted, the system issues a warning or error message, depending on the settings in Customizing.
The expected value is the anticipated end value of the order placed with the vendor. If you work with the release procedure for purchasing documents, this value can serve as the basis for assigning this blanket PO to a release strategy. Controlling establishes the PO commitment from this value. The system does not check whether the expected value is exceeded when an invoice is posted with reference to a blanket order.
In the standard system, the account assignment category U (unknown) is allowed for POitems of item category B. You need not specify the account assignment until the time of invoice entry.
When creating a blanket purchase order, you need enter neither an order quantity nor a net price. As soon as the expected value is specified during the creation of the blanket PO, it is automatically adopted as the net price.
Regards
Rajesh

Auto Creation of PO from SO

Hi
We are working on 11.5.10.2 and our requirement is
1.     User is entering multiple lines (say 20 lines) on Sales Order.
2.     Upon progressing the line, Purchase Order has to be created for these 20 Lines.
3.     Is there any way by which the User can create Purchase Order for the items entered on Sales Order without much User Intervention. The user does not want to go through the process of selecting lines from Purchase Requisition and create Purchase Order through the AUTO Create Document functionality in Oracle. OR can be PO creation From PR be automated without having to manually run the AutoCreate Document request .
We are not using BPA ; is there any solution involving ASL and/or Sourcing Rule which can be used to meet the User requirement.
Thanks

We are not using BPA ; is there any solution involving ASL and/or Sourcing Rule which can be used to meet the User requirement.There certainly is. It involves using either Blanket Purchase Aggreement (which you don't have) or using Quotes.
Once you have created either of those, simply create an ASL entry for the item(s), attach the Quote or BPA to the ASL entry; create a sourcing rule.
Once these setups are done, when a requisition is created and approved, it will get converted into a PO automatically.
And depending upon the value you enter in the "Release method" field on the ASL screen (and your PO workflow attributes), the PO will be created in incomplete status or it can be automatically submitted for approval.
Hope this answers your question,
Sandeep Gandhi
Independent Techno-functional consultant

Automatic creation of PO's from Requisitions

Hi
I'm trying to get a grasp of what's needed to automatically create approved PO's upon approval of a requisition.
There seems to be two ways to do it, a release program under a Contract Agreement, or using workflow with a Global BPA.
Under either method, would you need to create a Contract Agreement or Global BPA for each and every supplier? Is there any easier way to achieve this?
Thanks

To automatically created Approved PO's you will need the following
1. To create Standard PO's a Requisition will have to use a Quotation. This quotation can be attached to an ASL to default while creating a req
The Workflow "PO Create Documents" should have automatic creation allowed set to yes
2. To create Releases a Blanket PO must be attached to an ASL . The Workflow "PO Create Documents" should have automatic creation allowed set to yes
Please let me know if you have any questions
Thanks
Navin

Change Purchase Order type ,price before auto creation of PO through MIGO?

Hi ,
I have reuirement infront of me.
We are creating return Purchase order through MIGO for Non-ordered items.
Purchase Order is created automatically by SAP.
I need to change its Purchase Order type , Net Price , Order Price Unit .
Is it possible to modify the content before the creation of this PO.
Please help me .
Regards,
Amit

We are not using BPA ; is there any solution involving ASL and/or Sourcing Rule which can be used to meet the User requirement.There certainly is. It involves using either Blanket Purchase Aggreement (which you don't have) or using Quotes.
Once you have created either of those, simply create an ASL entry for the item(s), attach the Quote or BPA to the ASL entry; create a sourcing rule.
Once these setups are done, when a requisition is created and approved, it will get converted into a PO automatically.
And depending upon the value you enter in the "Release method" field on the ASL screen (and your PO workflow attributes), the PO will be created in incomplete status or it can be automatically submitted for approval.
Hope this answers your question,
Sandeep Gandhi
Independent Techno-functional consultant

Field Status in Blanket PO

Hi,
I am creating a blanket PO from copying another Blanket PO. But the fields vendor, plant, net price,PO quantity,item category,account assignment category are in display mode. But same is possible in standard PO. I want to create a Blanket PO refferring another one by changing vendor ,net price etc. How can I make those fields in change mode while copying one?There is no problem in creation of Blanket PO.
regards
Ashok

If you use the adopt function, it should be able to copy all the information from an existing PO and in change mode status.
To copy the PO, click "Document Overview On" button, and click the first little button "Selection Variant" to select the old PO, after the PO number display in the space below, HIGHLIGHT the PO (remember not double clicks, if double clicks meaning display), and then click "Adopt" button.
Hope this help you.

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

Problem in blanket po

When I am creating a blanket PO I am facing a error as:-
Indicator for invoice receipt used not allowed at the time PO creation item level.
why this error is come,bcoz IV should be created for the same.
I have one more doubt,
Is there any difference in Framework order or Blanket Purchase Order.
or both are same thing.

Hi There
I am using this every day..
1. Document Type- FO, vendor, P Group , Valildity start and End
2. Enter the short text (Since the material can not be procured using Item Category B), Acc *** cat- U and Item Cat- B
3. Enter the Material Group/Plant
4. You will get the Limits Tab enter the Overall limit and Expected limit
5. And Save it,,
This is are all the steps to create the Blanket PO, Have you entered all these fields,,
Please check and let us know the details
Thanks
Senthil

Query of blanket purchase order

Hi experts
can anyone explain how to do invoice verification for blanket po?
thanks in advance!

Hi Mark,
In SAP, Blanket Purchase Orders refer to the business process where you have a Purchase Order with a validity period (start / end date) and a limit on the item. No Goods Receipt takes place. Payment is triggered by Invoice.
Multiple invoices can be processed. Main point is that invoices must be processed within the validity period spesified in PO. The total value of invoices must also not exceed the limit spesified in PO item. The validity period is spesified on PO Header Level, while the Limit is on Item level. The creation of Purchase requisition is Optional.
Purchase Requisitions doesn't have validity period fields, although the limit can be spesified on item level. So if users create PR's then they could type the validity period simply as text in one of the long text fields.
During invoicing, if the date is outside validity period or the amount is bigger, either a Warning or Error will occur. This setting is done in customising.
Examples on where this business process can be used include: Services: example buying flowers, travel. Perticular if the receipt process is not very formalised. It is also sometimes used for utilities (water, electricity...).
Look at processes where Financial invoices (no PO) are used. To improve control, a lot of vendor invoices could be moved to Blanket Order process.
Lets look at key fields in the Purchase Order
The Overall Limit is the value that will be used to in the check during invoicing. If Commitment is switched on in Costing, the Expected value is the value of the commitment against in this case the Cost Centre. The actual will be posted during invoicing.
Account assignment is mandatory, so this process is non stock purposes only. Stock can not be procured using this method (For stock a GR is required).
Because no Goods Receipt (GR) will take place, the GR indicator is switched off when the item category is selected.
Regards,
Ashok

Blanket PO - Actual Value Calculation

Hi All,
Can anybody tell me how the actual value is calculated for each line item in Blanket PO.(In Limit tab you can able to find Overall Limit, Expected Value and Actual Value.)
Thanks and regards,
Senthil.B

Hi Friends,
I am comparing 4.7 and ECC 6.0 EHP 4 functionalities in MM.
I found some change has been made to Purchase requisition to save as template.
Here is the detail in ERP browser.
"Creation of purchase requisitions for materials.
- Purchase requisitions can be saved as templates and templates can be used for faster creation of extensive purchase requisitions without the need of manual data entry.
- Fast maintenance of account assignment with template functionality.
- Personalization of user interface based on Web Dynpro"
I could not find the option to save Purchase requisition as template in ECC 6.0.
Kindly let me know how to activate this menu option or functionality.
BR,
SB.

Blanket PO process - cant do MIGO

Hello,
I am trying to use the standard blanket PO process (FO doc type, with B item category)... However, when i go to the MIRO and pull in PO, the amount is automatically populating as ZERO, therefore i can not post invoice. The validate dates are correct, and the amount is not exceeding the overall limit set on the PO...
Any suggestions?
Thanks

The doc type is 'FO' (Framework Order). The GR or Service Entry for the PO are not necessary in case of Blanket POs as well as one need not to mention the account assignment category during creation of PO it can be 'U'-unknown & can be changed at the time of IR.
Order type FO (framework order)
1. Validity period in header of purchase order (field selection)
2. Item category B (limit)
A.. Limit in the item
B. No material number
C. Account assignment category U (unknown) is allowed
D. No goods receipt or service entry
3. Accounting data for the item suggested in invoices
4. Additional or multiple account assignment possible in invoice verification
5. Check of validity period and limit in invoice verification
To be able to work with validity periods and limits in a purchase order, you must
use document type FO (framework order) and item category B (limit). In the
standard system, document type FO enables you to specify the validity period at
PO header data level and use the item category B for limit items. (Limit items are
sometimes referred to as blanket items.)
cross verify all the parameters mentioned above , you will get the solution.

Blanket Purchase Order - process

Hi,
Can anyone provide me, the complete procss abt Blanket purchase order i.e the complete cycle.
as well, let us know, in whihc case , they will use this blankent orders.
thanks in advance.

In SAP, Blanket Purchase Orders refer to the business process where you have a Purchase Order with a validity period (start / end date) and a limit on the item. No Goods Receipt takes place. Payment is triggered by Invoice.
Multiple invoices can be processed. Main point is that invoices must be processed within the validity period spesified in PO. The total value of invoices must also not exceed the limit spesified in PO item. The validity period is spesified on PO Header Level, while the Limit is on Item level. The creation of Purchase requisition is Optional.
Purchase Requisitions doesn't have validity period fields, although the limit can be spesified on item level. So if users create PR's then they could type the validity period simply as text in one of the long text fields.
During invoicing, if the date is outside validity period or the amount is bigger, either a Warning or Error will occur. This setting is done in customising.
Examples on where this business process can be used include: Services: example buying flowers, travel. Perticular if the receipt process is not very formalised. It is also sometimes used for utilities (water, electricity...).
Look at processes where Financial invoices (no PO) are used. To improve control, a lot of vendor invoices could be moved to Blanket Order process.
Lets look at key fields in the Purchase Order
The Overall Limit is the value that will be used to in the check during invoicing. If Commitment is switched on in Costing, the Expected value is the value of the commitment against in this case the Cost Centre. The actual will be posted during invoicing.
Account assignment is mandatory, so this process is non stock purposes only. Stock can not be procured using this method (For stock a GR is required).
Because no Goods Receipt (GR) will take place, the GR indicator is switched off when the item category is selected
Read the Rules Use the Search...........

Blanket PR Creation

Similar Messages

Maybe you are looking for