Allow to create a purchase order with purchase requisiton item deleted

Dear all,
I have a question about creation purchase order process.
Firstly, I have a purchase requisition with 2 items, first of them is deleted.
If I try to create a purchase order thru transaction ME57N with the previous purchase requisition, I can only create it with one item (the one wich is not deleted)
However, if I try to create the purchase order thru transaction ME21N, with purchase requisition as reference, I can create the PO with item that was deleted in PR.
I don't understand why system allows to create a purchase order with an item that previously was deleted in PR.
Does anyone have a explanation about this issue?
Many thanks in advance
Best Regards.

Hi,
In the document overview of ME21N you get all the items of the purchase
requisitions, no matter if they are deleted or not.
When you convert the deleted item into a Purchase Order you get message
06 050 stating that this item is deleted in the purchase requisition.
This message can be defined as an error message in the customizing
transaction OME0. This way, it will not be possible to order an item
which is deleted in the referenced purchase requisition.
BR
Nadia Orlandi

Similar Messages

  • Purchase order with purchase requisition reference

    Hi All,
    I want to make config in system such that it should not allow me to create purchase order without purchase requisition.
    Can anyone guide me to resolve this issue.
    Which config i should do for this?
    Regards,
    Deepak.

    Hi,
    please consider that the system is not coded to have the PR field MEPO1211-BANFN to be set to required.
    The field BANFN cannot be made a required entry in ME21N. However you can use "Function Authorizations" (OMET) to restrict the user to only order with reference to a purchase requisition.
    As both the agreement field and purchase requisition fields are reference fields they are populated when created in reference and thus the system would not accept attempting to make them a mandatory field.
    Please use the OMET transaction and the PID EFB to accomplish your desired functionality.
    And also check the below link:
    PO with ref to PR

  • Purchase Order With Different Warehouse Items

    I have problem in creating the purchase order for the items belonging to 2 different warehouses.
    When I create the Purchase order it shows the error as
    “Cannot retrieve tax information message [80508-2]”

    Hello,
    No, I am referring to warehouse setup --> general tab.
    Are you creating one item that will be received by 2 warehouses or more items and more warehouses ?
    actually the error can be caused by tax group setup in item master data and business partner. Check also field tax information in  the module admin --> system initialisation --> accounting tab. maybe you forget to define the tax info there.
    Rgds,
    JM
    http://groups.yahoo.com/group/SBO_Knowledge_Village
    [email protected]

  • Unable to book orders created by Sales Order with ATO Model Items

    I am trying to create Orders for Ato Model Items with Option classes and Option using process_order API. The Issue we are facing is when we start booking the order. Although we are passing all the otions that are required for the Model, it says the configuration is incomlete when we try to book it.
    DECLARE
    v_line_id oe_order_lines_all.line_id%TYPE;
    v_api_version_number NUMBER := 1;
    l_return_status VARCHAR2(2000) := FND_API.G_FALSE;
    l_line_tbl oe_order_pub.line_tbl_type;
    l_msg_data VARCHAR2(300);
    l_msg_count NUMBER;
    l_header_rec oe_order_pub.header_rec_type;
    l_new_header_rec oe_order_pub.header_rec_type;
    t_header_val_rec oe_order_pub.header_val_rec_type;
    t_header_adj_tbl oe_order_pub.header_adj_tbl_type;
    t_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
    t_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
    t_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
    t_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
    t_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
    t_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
    t_out_line_tbl oe_order_pub.line_tbl_type;
    t_line_val_tbl oe_order_pub.line_val_tbl_type;
    t_line_adj_tbl oe_order_pub.line_adj_tbl_type;
    t_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
    t_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
    t_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
    t_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
    t_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
    t_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
    t_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
    t_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
    t_action_request_tbl oe_order_pub.request_tbl_type;
    v_message_index NUMBER;
    v_api_message VARCHAR2(300);
    v_count NUMBER := 1;
    BEGIN
    oe_msg_pub.initialize;
    fnd_global.apps_initialize(1459,21623,660,NULL);
    commit;
    mo_global.init('S',82);
    --header records
    l_header_rec := oe_order_pub.g_miss_header_rec;
    -- l_header_rec.shipping_instructions := p_special_instructions;
    l_header_rec.ship_to_org_id := 1067;
    l_header_rec.cust_po_number     :='9090909090';
    l_header_rec.operation := oe_globals.g_opr_create;
    l_header_rec.transactional_curr_code := 'USD';
    --l_header_rec.org_id := 82;
    --l_header_rec.context :=82 ;
    --l_header_rec.header_id         := null;
    --l_header_rec.order_number      := 100;
    -- l_header_rec.version_number := 1;
    l_header_rec.open_flag := 'Y';
    l_header_rec.booked_flag := 'N';
    l_header_rec.order_category_code := 'ORDER';
    l_hus,
    x_msg_data => l_msg_data,
    x_msg_count => l_msg_count,
    x_header_rec => l_new_header_rec,
    x_header_val_rec => t_header_val_rec,
    x_header_adj_tbl => t_header_adj_tbl,
    x_header_adj_val_tbl => t_header_adj_val_tbl,
    x_header_price_att_tbl => t_header_price_att_tbl,
    x_header_adj_att_tbl => t_header_adj_att_tbl,
    x_header_adj_assoc_tbl => t_header_adj_assoc_tbl,
    x_header_scredit_tbl => t_header_scredit_tbl,
    x_header_scredit_val_tbl => t_header_scredit_val_tbl,
    x_line_tbl => t_out_line_tbl,
    x_line_val_tbl => t_line_val_tbl,
    x_line_adj_tbl => t_line_adj_tbl,
    x_line_adj_val_tbl => t_line_adj_val_tbl,
    x_line_price_att_tbl => t_line_price_att_tbl,
    x_line_adj_att_tbl => t_line_adj_att_tbl,
    x_line_adj_assoc_tbl => t_line_adj_assoc_tbl,
    x_line_scredit_tbl => t_line_scredit_tbl,
    x_line_scredit_val_tbl => t_line_scredit_val_tbl,
    x_lot_serial_tbl => t_lot_serial_tbl,
    x_lot_serial_val_tbl => t_lot_serial_val_tbl,
    x_action_request_tbl => t_action_request_tbl
    IF l_return_status = FND_API.G_RET_STS_UNEXP_ERROR THEN
    RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
    ELSIF l_return_status = FND_API.G_RET_STS_ERROR THEN
    RAISE FND_API.G_EXC_ERROR;
    ELSE
    dbms_output.put_line('Order Created'||l_header_rec.order_number||l_return_status );
    END IF;
    EXCEPTION
    WHEN FND_API.G_EXC_ERROR THEN
    FOR x_index IN 1..l_msg_count
    LOOP
    OE_MSG_PUB.GET(p_msg_index => x_index,
    p_encoded => FND_API.G_FALSE ,
    p_data => v_api_message ,
    p_msg_index_out => v_message_index
    dbms_output.put_line('Execution'||v_api_message);
    l_return_status := FND_API.G_RET_STS_ERROR;
    END LOOP;
    WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
    -- To see the errors
    FOR x_index in 1..l_msg_count
    LOOP
    OE_MSG_PUB.GET(p_msg_index => x_index ,
    p_encoded => FND_API.G_FALSE,
    p_data => v_api_message ,
    p_msg_index_out => v_message_index
    dbms_output.put_line('Unexpected'||v_api_message);
    l_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
    END LOOP;
    WHEN OTHERS THEN
    dbms_output.put_line('In Others'||SQLERRM);
    END;
    COMMIT;
    END; -- get_process_order
    assing all the otions that are required for the Model, it says the configuration is incomlete when we try to book it.
    DECLARE
    v_line_id oe_order_lines_all.line_id%TYPE;
    v_api_version_number NUMBER := 1;
    l_return_status VARCHAR2(2000) := FND_API.G_FALSE;
    l_line_tbl oe_order_pub.line_tbl_type;
    l_msg_data VARCHAR2(300);
    l_msg_count NUMBER;
    l_header_rec oe_order_pub.header_rec_type;
    l_new_header_rec oe_order_pub.header_rec_type;
    t_header_val_rec oe_order_pub.header_val_rec_type;
    t_header_adj_tbl oe_order_pub.header_adj_tbl_type;
    t_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
    t_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
    t_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
    t_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
    t_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
    t_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
    t_out_line_tbl oe_order_pub.line_tbl_type;
    t_line_val_tbl oe_order_pub.line_val_tbl_type;
    t_line_adj_tbl oe_order_pub.line_adj_tbl_type;
    t_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
    t_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
    t_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
    t_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
    t_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
    t_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
    t_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
    t_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
    t_action_request_tbl oe_order_pub.request_tbl_type;
    v_message_index NUMBER;
    v_api_message VARCHAR2(300);
    v_count NUMBER := 1;
    BEGIN
    oe_msg_pub.initialize;
    fnd_global.apps_initialize(1459,21623,660,NULL);
    commit;
    mo_global.init('S',82);
    --header records
    l_header_rec := oe_order_pub.g_miss_header_rec;
    -- l_header_rec.shipping_instructions := p_special_instructions;
    l_header_rec.ship_to_org_id := 1067;
    l_header_rec.cust_po_number     :='9090909090';
    l_header_rec.operation := oe_globals.g_opr_create;
    l_header_rec.transactional_curr_code := 'USD';
    --l_header_rec.org_id := 82;
    --l_header_rec.context :=82 ;
    --l_header_rec.header_id         := null;
    --l_header_rec.order_number      := 100;
    -- l_header_rec.version_number := 1;
    l_header_rec.open_flag := 'Y';
    l_header_rec.booked_flag := 'N';
    l_header_rec.order_category_code := 'ORDER';
    l_hus,
    x_msg_data => l_msg_data,
    x_msg_count => l_msg_count,
    x_header_rec => l_new_header_rec,
    x_header_val_rec => t_header_val_rec,
    x_header_adj_tbl => t_header_adj_tbl,
    x_header_adj_val_tbl => t_header_adj_val_tbl,
    x_header_price_att_tbl => t_header_price_att_tbl,
    x_header_adj_att_tbl => t_header_adj_att_tbl,
    x_header_adj_assoc_tbl => t_header_adj_assoc_tbl,
    x_he
    Message was edited by:
    user604069

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

  • Creating an SRM Purchase Order with a Return Line

    Is it possible within standard SRM to create a purchase order with a 'Returns Item' line?
    I know it's possible in R/3 but really need to create it via SRM.
    Regards
    Keith

    Ganesh
    We are using the Extended Classic Scenario of SRM (and the Sourcing Cockpit) which therefore means that we won't be creating requisitions within R/3.
    In the R/3 PO you can create a line item as a 'Returns Line' (MEPO1211-RETPO)
    The standard help text is as follows:
    Logistics - General (LO)
    The returned goods from a customer to an internal or external vendor.
    Returns can be divided into the following types, according to vendor and recipient:
    Customer returns
    Returns to vendor
    Returns for stock transfers
    I know we can use a BADI to mark this flag in R/3 but for completeness really want to show this as a returns line in SRM too.
    Keith

  • Validity start & end, in Purchase Order with limit

    Hi All,
    We are using  a model of SAP with one type of Purchase Order: we have created a new type of purchase order (ZFOA), that we use for all purchase orders.
    Now we want to use ZFOA also for Blanket Purchase Order, instead of the standard type proposed for this scope by SAP (FO).
    We have inserted Validity Start & Validiti End  as Optional Entry in Customizing.
    ( IMG - MM - Purchasing - Purchase Ordrer - Define Screen Layout at Document Level).
    We have inserted them as Optional Entries, and not as Required Entries, because they are Required only for Blanket Purchase Order. (and we use ZFOA for all ours types of Purchase Order)
    So i want to know if it's possible to connect the obligatory requirement of these two entries to:
    - ZFOA (type of Purchase Order)
    - B (Item category in Purchase Order)
    In this way:
    1) when i create a PO (ZFOA) without item category B --> Validity date & Validity End are not obligatory fields
    2) when i create a PO (ZFOA) with item category B ---> Validity date & Validity End are  obligatory !!
    Have you got any Solutions??
    Best regards
    Alba

    Thanks very much!
    Now i found in MM SAP Manual (SCM 520, Purchasing) a similar example, and it could seem possible:
    When creating a standard purchase order with the standard item category, the following field selection key is determined for the Material group field:
    • Field selection key ME21N (Create/Change Purchase Order transaction):
    The Material Group field is an optional field.
    • Field selection key AKTH(Create activity category):
    The Material Group field is an optional field.
    • Field selection key NBF (purchasing document type NB):
    The Material Group field is an optional field.
    • Field selection key PT0F (item category Standard):
    The Material Group field is a mandatory (required-entry) field.
    The combination of field selection keys ME21N, AKTH and NBF means that the field is an optional field. Because the Material Group field is defined as a mandatory field in the field selection key PT0F however, this means that the field requires an entry when a purchase order is being created.
    I have the same problem for Validity start field, but why if i do all of this things, the field remain not mandatory?
    Thanks in advance
    Best regards
    ALba
    Edited by: Alba Battolini on Apr 22, 2009 9:21 AM

  • Purchase Order History not appearing for Purchase Order with service items

    A purchase order with a service item has been created.  A SES has been created and Miro transactions as well. When tcode ME2L is executed, the Purchase Order History field is blank. Any configuration missing or is there an applicable OSS note to fix  this?

    Hi,
    It is a coding error.
    Could you please check if you have applied the note 1049031 with the latest version 13?
    Regards,
    Edit

  • Creating a sales order with reference/BAPI_SALESDOCUMENT_COPY

    Hi,
    I have to create a sales order with a reference to another order and have to change some fields in the new document.
    According to SAP note 370988 the function BAPI_SALESDOCUMENT_COPY should allow to create a sales order with reference to another order.
    Unfortunately it doesn't work for me.
    The BAPI doesn't return an error and creates a new order but that one is incomplete.
    The reason seems to be that VKORG, VTWEG and SPART aren't provided and because of that the new order can't be created completely.
    I can find no way to provide these fields to the BAPI.
    Has anyone used the BAPI successfully or has found another way to achieve the desired result?
    I already checked
    batch input: problematic because I have to change partners which are displayed in an table control which can't be controlled reliably from batch input
    the second way described in the SAP note: high effort and high risk, as each data field has to be copied explicitly from one represantation to another.
    Any help is appreciated.
    Kai

    That approach would effectively duplicate the implementation of BAPI_SALESDOCUMENT_COPY, wouldn't it?
    As there is a lot more data involved than just VBAK/VBAP (e.g texts, partners, conditions, schedules) this is not only a lot more effort it's also harder to get it right, especially since there might also be copy control customization which has to be take into account.
    Nevertheless I tried it and it isn't working in my case.
    I' have to create a debit memo request (BUS2096) out of a sales order (BUS2032), and BAPIs SALES_ORDER_CREATE* only handle BUS2032.

  • Error while creating purchase order with account assignment category "A"

    Dear All,
                      At the time of creating purchase order with account assignment category A - Asset its throwing error as " GL Account 123400 can not be used"
    how to resolve this  issue"
    Edited by: Matt on Sep 16, 2010 10:09 AM - removed bold tags

    HI,
    Assign all assets GL to Asset Class
    spro --> financial accounting new -->assets accounting --> assets accounting (lean Implementation) --> organization structures --> Assign GL
    Hope Help U !
    Regards,
    Pardeep Malik

  • Create blocked purchase order with BAPI_PO_CREATE1

    Hi,
    I´m creating stock transport orders with BAPI_PO_CREATE1. At first, I need to
    set them to the release status 'S' for blocked. After some checks, I want be able
    to relase it and create the delivery.
    I have found some fields like rel_status inside of the header structure of
    BAPI_PO_CREATE1. But when I set this to 'S', the purchase order is created
    with status 'released'.
    How can I create a purchase order with BAPI_PO_CREATE1 and set it to 'blocked'
    first?
    Thanks, Arne

    No ideas about that?

  • Create service purchase order with negative value

    Hello,
    we created a service purchase order using the specific item category (value D) and with the service number details. We posted the entry service sheet with the transatcion code ML81N and we did the invoice verification.
    Now we need to reverse this document flow: in particular our requirement is to create a new purchase order (like a return order for goods) and then to post an entry service sheet with the opposite sign (both cost center and G/L account).
    Do you know whick document type I can use or how i can meet this requirement? Please consider that I cannot reverse the original document but I need to create new ones.
    Thanks in advance,
    Alessandro

    check below thread;
    service order
    yogesh

  • Program for Creating Purchase Order with reference to purchase requisition

    Hi ,
    I need to Create purchase Order with reference to  Purchase requisition,
    in my case i need to automize the Process which is happening in MD04,
    Can you please suggest me ?
    Thanks ,
    Murali

    Hi,
    Plz check this link. It will be helpful to you.
    Purchase order creation with reference to PR
    We can also create the PO Using the BAPI_PO_CREATE1 function module.
    In this function module fill up the all necessary Details.
    With details in Item Table we haveto give the Fields PREQ_NO and PREQ_ITEM for each item .
    then it will creates the PO with PREQ.
    Thanks & Regards,
    Sarita Singh Rathour
    Edited by: Sarita Rathour on Aug 3, 2009 7:01 AM

  • Create purchase order with reference to Sales order Line item

    Hi All,
    i had a requirement that i need to create the Purchase order with reference to sales order line item...
    In T.code me27 client requied a input field for sales order no and with that order reference he want the data of line item to PO creation line item screen.....
    please sujjust......how to proceed......
    regards,
    Ravi Nemani

    Hi
    Go to SPRO->Logistic general->Tax on goods movement->India->Movement types.
    Here you will find the group of movement types check which movement types is mantained for the out side movement groups or inward movement.
    also check the Material Master in MRP view if the collective requirements (02) is mantained.
    Regards
    Sri

  • Create Purchase Order with reference to Purchase Requisition using BAPI's

    Hello Experts,
    I need to create a Purchase order with reference to a Purchase Requisition.
    All the above has to be done by using BAPI's.
    For creating PR, I am using BAPI_REQUISITION_CREATE.
    and for PO, I am using BAPI_PO_CREATE.
    I am not able to use the requistion number in the PO. BAPI throws the following exception
    "Requisition 1014396 00010 not selectable"
    "Document contains no items"
    Query's:
    1. Do I need to release the PR for using it in PO?
    2. If so how can I work with the "BAPI_REQUISITION_RELEASE_GEN" to release PR?
    I have tried using the BAPI getting the following error "Release outside filed of responsibility".
    Please help I am in critical Postion...
    Thanks,
    Suma

    Hi Meenakshi,
    When, I try to release error I am getting the following the error " Purchase Requisition can not be released".
    Is this problem because of authorization or data issue?
    Thanks
    Suma

  • PURCHASE ORDER WITH OUT BAPI_PO_CREATE CAN WE CREATE?

    PURCHASE ORDER WITH OUT calling BAPI_PO_CREATE CAN WE CREATE?
    Don't Post your question with all Caps. Follow the Rules of Engagement
    Edited by: Vijay Babu Dudla on Apr 23, 2009 1:46 AM

    [Create Purchase order with program|can we create purchase order through report programming?]
    Plz be clear about your requirement instead of posting questions like these.
    Don't violate forum rules with Duplicate posts

Maybe you are looking for