POs with reference to a PRQ

Hi,
I want to customize the system so that if I create a PO with reference to a RFQ and I modify the quantity of the
PO (i.e. I set a quantity in PO that is > of the quantity in the RFQ) the system will create a message errore
Regards

Check
PO allows qty more than RFQ

Similar Messages

  • Default quantity = 2 pcs. in POs with reference to contract

    Hey gurus,
    we have a material "A". Its base unit of measure is (and has to be) piece. Now, we have a contract for this material.
    Normally we order this material in pairs (2 pieces) with reference to the contract, but sometimes only 1 piece has to be ordered.
    Now I would like the system to give me a default quantity of 2 pieces in the PO. But I also want to be able to manually change this to 1 piece.
    Is this possible?
    Thanks in advance
    Alicia

    enter a rounding rule in your material master  or info record, that always round to 2.
    SAP will then round the qantity to 2 when you create the PO, but if you overwrite again with 1, then SAP keeps this new quantity.

  • Create Return PO using ME21N with reference to Original Purchase Order

    Dear Experts,
    Does anyone knows how to create Return POs with reference to Original Purchase Order using ME21N.  The Purchasing Department will be initiating the Stock Return to Vendor so we don't want to use MB01, 161 Movement Type to create the return PO.  Can anyone help.
    Thanks.

    Hi,
    It is not possible to create a Return PO w.r.t. the original PO. Even if you will copy, it will just copy the details from PO but not store the reference of original PO in return PO.
    Better instead of creating a new return PO, add a separate line item in the orginal PO by marking it as "Return" and perform all the subsequent transactions. This will provide the better traking and reporting. But this may affect your release strategy (need to be tested).

  • PO with reference to invoice without GR (WRX)

    I would like to create POs with reference to an internal order and ONLY creating an invoice with reference to the invoice.
    I configured two-matching in SPRO, that is Maintain Account Assignment Category with only invoice receipt.
    I can create an invoice, it is not expected to create a MIGO, nevertheless when I want to post the invoice it is missing the GR/IR account determinarion (WRX).
    I must be missing something, however I do not want to post it to a GR/IR account as only invoices are expected to be posted against the PO.
    Please advice,
    Daan

    You need in Customizing the WRX settings because this WRX is not only
    for PO without GR flag but for the PO with GR flag too while
    the automatic posting
    In IMG it is impossible to control apart the settings of
    account determination for
    PO without GR flag OR
    PO with GR flag .
    Of course this could be an issue of FI and this relates to the chart
    of accounts too. You can find more information in IMG documentation
    of "automatic postic". Please see the note 301477 too.
    RESOLVED, even though all answers are useful the solution is within maintaining the WRX settings for this to happen.
    As of Release 4.0, you can enter a valuation class for the material group (Transaction OMQW). By means of this valuation class, the G/L account is determined in the purchase order which is relevant for transaction/event KBS provided that no material master record exists for the material ordered. The determination of the GR/IR clearing account is always carried out with an EMPT VALAUATION CLASS.

  • Create prq with reference

    Hi Gurus,
    Where in purchasing are customizing settings for PRQ creation with reference to another type of document.... contract.... PO order.... is this possible in MM? In sales this is easy and solved with copying control...
    Thanks + br
    Saso

    Hello Saso,
    A requisition cannot be created with reference to a contract. The reason is that PreReq is generally created when materials are in need  and it does not matter whether there is any concerning contract at the moment.
    The contract will come to consideration when the purchasing department makes a decision where to order the material from. Basing on that , you can only adopt other PreReqs in ME51N by "drag and drop" but no other documents like contracts, requests for quotations and so  fourth.                                                                               
    What can be done is to use the contract as a source of supply on PRe In t-code ME51N you inform the material, quantity, plant and PurOrg you will see tab "source of supply". here you need to click button "assign source of supply" and select the contract and clicking "assign source". The contract will be defaulted into the field 'agreement'.
    Regards,
    Mauro

  • ME2O with reference to POs.

    Hi,
    is true that using ME2O is not possible doing a 541 with reference to POs?
    The screen of ME2O trx allows only the selection of materials but not of the related POs.
    Best regards

    In general NO. As stated in the OSS note: it is designed this way.
    But if you arrange your process that you always have a kind of 1:1 relation ship.
    Eg. you create your PO, you deliver the exact amount on components for one PO at one time,
    if your subcontractor never has stock on his site for more than one order etc.
    then you can just assume that all stocks are for the one open PO, ............

  • POs created with reference to PRs

    Dear All
    I want PR item valuation price is to be copied in to the PO item as net price, when this PO item is being created with reference to a PR item.
    This is required for both materials PR items and Service PR items
    Presently for material PRs, system is coping the prices from material master, whereas for services no prices are copied as I am not following any service master.
    I want prices directly from PR item. Is this possible in SAP (ECC 6.0)?
    Thank you

    1. Go to SPRO > MM > Purchasing > Authorization Management > Define Function Authorizations for Buyers > Function Authorizations: Purchase Order > Here "New Entries" and define Function Authorization Key as "01" and give description.
    OR use T. Code - OMET
    Here under "General parameters" subscreen, cctivate "Adopt PO Price" indicator and select "Enter conditions"
    In "Possible ref. objects", select "W/o reference" otherwise reference documents (for e.g. PR, RFQ, etc...) for PO creation will become mandatory.
    2. Now go to SU01 > Enter User ID > Parameters Tab > Here for Parameter ID EFB i.e. Function Authorization: Purchase Order, maintain value "01" and check in PO, PR will become mandatory for that user.
    3. Now during creation of PR in ME51N, under "Valuation" Tab, you will get option for PO Price Adoption as Net or Gross. Select as per your requirement and it will copy Price to PO.

  • Create Credit memo with reference to billing in VF01

    Hi all:
    I want to create a credit memo with direct reference to the original billing. Thus the creation of CMR is not required. This is the new feature as of release 4.5a. In SAP system, I've done the configuration for copying control from billing document to billing document, source (F2) target (G2). Copying requirement 027. Pos/neg qty = + and Pricing type = D. I can create a credit memo with reference to a billing now. However, the system allow multiple credit memos. Duplicate credit memo are unwanted in the system.
    How to control the system to avoid duplicate credit memo?
    Thanks and regards,
    Sim

    Hi Mei,
       In t-code "VTFF" under your item category,the field VBRK/VBRP skuldn't be 001.
       Keep them as zero.
       Reward points if it helps.
    Regards
    Karan

  • Invoice Management Invoice with reference to a PO

    Hi,
    I´m working with Invoice Management. I know that an invoice could be procesed with reference to a PO, but is it possible to do so with reference to many PO documents??????? Is it possible refers that Invoice to many POs without take all the items in the POs???????
    And the last question, Is it possible to specify the a tax indicator per position??????
    Thanks

    > Can any one guide me how to create a PR with reference to a PO?
    PR Cannot be Created with Reference to PO. Further it can be Created referring PR.
    Copying Purchase Requisitions or Requisition Items
    When processing purchase requisitions, you can reduce your data entry effort by simply adopting or copying data from other requisitions.
    Features
    You can copy individual items or complete requisitions from the document overview into the requisition you are currently processing.
    Procedure
    To adopt items in a purchase requisition, you can either select the desired requisition in the document overview and adopt it in the current requisition in the right-hand part of the screen using the Adopt button, or you can drag it into the item overview using the left-hand mouse button.
    A prerequisite is that the relevant documents can be displayed in the document overview.
    How to set up the document overview display is described in How do You Create a Variant?
    Example
    Copying purchase requisitions
    Prerequisites
    To be able to copy complete requisitions, you must set up the document overview in such a way that the requisitions are initially sorted by number and the item data can be displayed below the document number.
    In this case, the document overview might have the following structure:
    Purchase requisition
    '->Item Material
    1000000012
    '-> 010 Screw 07
    1000000013
    '-> 010 Steel 09
    '-> 020 Zinc sheet 03
    Activities
    To insert the data in the current requisition, select the desired requisition in the document overview and click the Adopt symbol.
    Note
    If you know the requisition and the item, you can also enter them directly in the item overview (Reference requisition and Reference item fields).
    Use SDN Search

  • Goods Receipt using Inbound Delivery with reference to Outbound Delivery

    Here is our scenario that we need help finding a solution:
    1.  Multiple Intracompany POs created
    2.  On the confirmations tab of the POs, we have u201CInbound Deliveryu201D Selected because the items need to be received in with Handling Unit management.
    3.  We have the Order Combination box checked on the shipping tab to allow 1 delivery to be created for multiple purchase orders.
    4.  We create only 1 Outbound Delivery for only available items on various purchase orders.
    5.  Due to being handling unit managed, we need to receive the items using an inbound delivery.
    Problem:  We need to find a solution to easily enter an outbound delivery number which will allow us to receive only the parts that were shipped (issued), via the inbound delivery process. 
    If we remove the confirmation control key, we can complete a Goods Receipt for Outbound Delivery in MIGO u2013 but is there a way to complete a goods receipt using an inbound delivery with reference to an Outbound Delivery?
    Thank you for the help.

    Hi,
    You can work with Inbound delivery created via IDOC Triggered from Outbound Delivery, this will carry the HU Data as well. Please refer this wonderful note, which will explain you a lot of things,  Note 1119073 - FAQ: Automatic inbound delivery creation for stock transfers
    There are other notes also available for Inbound delivery creation with HU in STO, please browse the notes, if you find any difficulty.
    Regards
    Chandra Shekhar

  • BAPI: Create Sales order with reference to Quotation

    Hi ...
    I am using bapi BAPI_SALESOREDER_CREATEFROMDATA2  and
    i want to create sales order with reference Quotation... All quotation data like Materials prices and conditions must be copied from reference quotaion which is allready created .....
    ..Thanks..
    ..Ashish

    Hello,
    nice to see that this has already been solved.
    But it actually doesnt work in my scenario. Do you have an example coding which will explain your solution.
    Mine looks like this:
    * Update Flag
      ls_header_inx-updateflag = 'I'.
    * Angebotskopf einlesen
      SELECT SINGLE * FROM vbak INTO ls_vbak
        WHERE vbeln = iv_vbeln
          AND vbtyp = lc_vbtyp.
      IF sy-subrc <> 0.
        EXIT.
      ENDIF.
    * Auftragskopf setzen
      ls_header_in-doc_type      =  ls_vbak-auart.
      ls_header_in-sales_org     = ls_vbak-vkorg.
      ls_header_in-distr_chan    = ls_vbak-vtweg.
      ls_header_in-division         = ls_vbak-spart.
      ls_header_in-req_date_h   = ls_vbak-VDATU.
      ls_header_in-ref_doc        = ls_vbak-vbeln.
      ls_header_in-refdoc_cat   = 'B'.
    * Angebots-Partner einlesen (Nur AG und WE)
    * Auftrag anlegen
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
        EXPORTING
    *   SALESDOCUMENTIN               =
          order_header_in               =  ls_header_in
    *      order_header_inx              = ls_header_inx
    *   SENDER                        =
    *   BINARY_RELATIONSHIPTYPE       =
    *   INT_NUMBER_ASSIGNMENT         =
    *   BEHAVE_WHEN_ERROR             =
    *   LOGIC_SWITCH                  =
    *   testrun                       = 'X'
    *   CONVERT                       = ' '
       IMPORTING
          salesdocument                 = ev_vbeln
        TABLES
          return                        = et_return
    *      order_items_in                = lt_items_in
    *      order_items_inx               = lt_items_inx
          order_partners                = lt_partners
    *   ORDER_SCHEDULES_IN            =
    *   ORDER_SCHEDULES_INX           =
    *   ORDER_CONDITIONS_IN           =
    *   ORDER_CONDITIONS_INX          =
    *   ORDER_CFGS_REF                =
    *   ORDER_CFGS_INST               =
    *   ORDER_CFGS_PART_OF            =
    *   ORDER_CFGS_VALUE              =
    *   ORDER_CFGS_BLOB               =
    *   ORDER_CFGS_VK                 =
    *   ORDER_CFGS_REFINST            =
    *   ORDER_CCARD                   =
    *   ORDER_TEXT                    =
    *   ORDER_KEYS                    =
    *   EXTENSIONIN                   =
    *   PARTNERADDRESSES              =  .
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
    Unfortunatly this just makes the reference to the quotation but does not takeover ALL data from header and pos level.
    Thanks and regards
    Markus Armbruster

  • List of PO's created with reference to WBS element

    Dear Experts,
    I am looking for all the PO's that are created with reference to a WBS element, Can you please suggest a T-code?
    Thanks & Regards,
    Manish

    Answered in  this link List of POs for a WBS Element

  • Create order by VA01 with reference

    Hello Experts,
    we use different one-time-customers for our retail store. Now we want to create credits/returns with reference to these POS-invoices.
    The problem is that when you create "normal" orders there is a pop-up window to enter the adress data. But if you create those returns with the VA01 in reference to those POS-invoices there is a) no pop-up window and b) if you enter the adress data they were adopted to the master data and all following returns get the same adress....
    We installed different SAP-OSS-information yet to interupt b).
    I also achieved that a pop-up window occurs when the VA01 (with reference) is processed. But I am not sure if there are other problems. The tables and structures appear normal and the credits/returns don`t make any problems...
    Did anyone of you installed a similar exit program already???
    Thanks for your help!!!
    Alexander

    Dear VT,
    This you control through maintaining settings in the field Reference mandatory under General Control tab of the sales document type detail screen.But reference options are
    A -With reference to an inquiry
    B -With reference to a quotation
    C -With reference to a sales order
    E -Scheduling agreement reference
    G -With reference to a quantity contract
    M -With ref.to billing document
    Go to VOV8 transaction then select your document type go in to the details here you maintain one this option in the Reference mandatory field as per your requirement.
    I hope this will help you,
    Regards,
    Murali.
    Edited by: Murali Mohan.Tallapaneni on Dec 2, 2008 10:11 AM

  • Problem creating Service POs with BAPI_PO_CREATE1

    Hi.
    I'm trying to create service POs with data that i read from an excel file, to do this I'm using the bapi: <b>BAPI_PO_CREATE1</b> I'm passing the following parameters:
    IMPORT:
    - poheader
    - poheaderx
    TABLES:
    - return
    - poitem
    - poitemx
    - poaccount
    - poaccountx
    - poservices
    - posrvaccessvalues
    - poservices text
    - extensionin
    When I execute the bapi, I'm getting the following messages into table return:
    <i>W - Error transferring ExtensionIn data for enhancement CI_EKKODB
    E - No instance of object type PurchaseOrder has been created. External reference:
    E - PO header data still faulty
    E - Purchase order date is in the past
    I - Change WBS Element could not be effected
    E - You cannot maintain service specs. due to incomplete transfer structure</i>
    Can anybody, please say me what am i doing wrong? How this bapi works?
    Regards.
    Gregory.

    Hello My friend
    Check this code:
    Code listing for: LZMMIUP001F01
    Description: Include LZMMIUP001F01
    ***INCLUDE LZMMIUP001F01 .
    *&      Form  fill_item
          text
         -->P_WA  text
    FORM fill_item  TABLES:  poitem STRUCTURE bapimepoitem "Item Data
                             poitemx STRUCTURE bapimepoitemx "Item Data (Change Parameter
                    USING wa STRUCTURE zlo_mmcnv009
                          package.
    item number
      poitem-po_item = wa-itemnum.
      poitemx-po_itemx = 'X'.
      poitemx-po_item = wa-itemnum.
      IF package <> ''.
        poitem-pckg_no = package.
        poitemx-pckg_no = 'X'.
      ENDIF.
    *Account Assignment Category
      IF wa-category <> ''.
        poitem-acctasscat = wa-category.
        poitemx-acctasscat = 'X'.
      ENDIF.
    *Item Category in Purchasing Document
      IF wa-itemcat <> ''.
        poitem-item_cat = wa-itemcat.
        poitemx-item_cat = 'X'.
      ENDIF.
    *Short Text
      IF wa-sortxt <> ''.
        poitem-short_text = wa-sortxt.
        poitemx-short_text = 'X'.
      ENDIF.
    *Material Number
      IF wa-material <> ''.
        poitem-material = wa-material.
        poitemx-material = 'X'.
      ENDIF.
    Unit of Measure
      IF wa-undmesure <> ''.
        poitem-po_unit = wa-undmesure.
        poitemx-po_unit = 'X'.
      ENDIF.
    *Purchase Order Quantity
      IF wa-quantity <> ''.
        poitem-quantity = wa-quantity.
        poitemx-quantity = 'X'.
      ENDIF.
    *Net Price in Purchasing Document
      IF wa-netprice <> ''.
        poitem-net_price = wa-netprice.
        poitemx-net_price = 'X'.
      ENDIF.
    *Plant
      IF wa-plant <> ''.
        poitem-plant = wa-plant.
        poitemx-plant = 'X'.
      ENDIF.
    *Material Group
      IF wa-matgrp <> ''.
        poitem-matl_group = wa-matgrp.
        poitemx-matl_group = 'X'.
      ENDIF.
    *Free Item
      IF wa-free <> ''.
        poitem-free_item = wa-free.
        poitemx-free_item = 'X'.
      ENDIF.
      APPEND poitem.
      APPEND poitemx.
    ENDFORM.                    " fill_item
    *&      Form  fill_header
          text
         -->P_WA  text
    FORM fill_header  USING wa STRUCTURE zlo_mmcnv009
                        poheader STRUCTURE bapimepoheader "Header Data
                        poheaderx STRUCTURE bapimepoheaderx. "Header Data (Change Toolbar)
      DATA: dia(2), mes(2), ano(4),
            vendor(10) TYPE n.
      dia = wa-docdate(2).
      mes = wa-docdate+2(2).
      ano = wa-docdate+4(4).
      CONCATENATE ano mes dia INTO wa-docdate.
      dia = wa-datestart(2).
      mes = wa-datestart+2(2).
      ano = wa-datestart+4(4).
      CONCATENATE ano mes dia INTO wa-datestart.
      dia = wa-datend(2).
      mes = wa-datend+2(2).
      ano = wa-datend+4(4).
      CONCATENATE ano mes dia INTO wa-datend.
    Document Type
      IF wa-doctyp <> ''.
        poheader-doc_type = wa-doctyp.
        poheaderx-doc_type = 'X'.
      ENDIF.
    vendor number
      IF  wa-vendor <>  ''.
        IF NOT ( wa-vendor CA sy-abcde ).
          vendor = wa-vendor.
          poheader-vendor = vendor.
          poheaderx-vendor = 'X'.
        ELSE.
          poheader-vendor = wa-vendor.
          poheaderx-vendor = 'X'.
        ENDIF.
      ENDIF.
    Document Date
      IF wa-docdate <> ''.
        poheader-doc_date = wa-docdate.
        poheaderx-doc_date = 'X'.
      ENDIF.
    purchasing organization
      IF wa-organiz <> ''.
        poheader-purch_org = wa-organiz.
        poheaderx-purch_org = 'X'.
      ENDIF.
    Purchasing Group
      IF wa-purgroup <> ''.
        poheader-pur_group = wa-purgroup.
        poheaderx-pur_group = 'X'.
      ENDIF.
    Start of Validity Period
      IF wa-datestart <> ''.
        poheader-vper_start = wa-datestart.
        poheaderx-vper_start = 'X'.
      ENDIF.
    End of Validity Period
      IF wa-datend <> ''.
        poheader-vper_end = wa-datend.
        poheaderx-vper_end = 'X'.
      ENDIF.
    Company Code
      IF wa-compcode <> ''.
        poheader-comp_code = wa-compcode.
        poheaderx-comp_code = 'X'.
      ENDIF.
      Status of Purchasing Document
      IF wa-status <> ''.
        poheader-status = wa-status.
        poheaderx-status =  'X'.
      ENDIF.
    ENDFORM.                    " fill_header
    *&      Form  fill_account
          text
         -->P_WA  text
    FORM fill_account  TABLES  poaccount STRUCTURE bapimepoaccount
                               poaccountx STRUCTURE bapimepoaccountx
                       USING wa STRUCTURE zlo_mmcnv009.
      DATA: account(10) TYPE n.
      poaccount-po_item = wa-itemnum.
      poaccountx-po_item = wa-itemnum.
    *Cost Centre
      poaccount-costcenter = wa-coscenter.
      poaccountx-costcenter = 'X'.
    *Order Number
      poaccount-orderid = wa-ordernumb.
      poaccountx-orderid = 'X'.
    *"G/L Account Number
      IF wa-accnumb <> ''.
        account = wa-accnumb.
        poaccount-gl_account = account."wa-accnumb.
        poaccountx-gl_account = 'X'.
      ENDIF.
      IF NOT ( wa-coscenter = '' AND
         wa-ordernumb = '' AND
         wa-accnumb = '' ).
        APPEND poaccount.
        APPEND poaccountx.
      ENDIF.
    ENDFORM.                    " fill_account
    *&      Form  fill_schedule
          text
         -->P_WA  text
    FORM fill_schedule  TABLES  poschedule STRUCTURE bapimeposchedule
                                poschedulex STRUCTURE bapimeposchedulx
                        USING wa STRUCTURE zlo_mmcnv009.
      DATA: dia(2), mes(2), ano(4).
      dia = wa-delivdate(2).
      mes = wa-delivdate+2(2).
      ano = wa-delivdate+4(4).
      CONCATENATE ano mes dia INTO wa-delivdate.
    *Delivery Date
      poschedule-po_item = wa-itemnum.
      poschedulex-po_item = wa-itemnum.
      poschedule-delivery_date = wa-delivdate.
      poschedulex-delivery_date = 'X'.
      IF NOT wa-delivdate = ''.
        APPEND poschedule.
        APPEND poschedulex.
      ENDIF.
    ENDFORM.                    " fill_schedule
    *&      Form  fill_header_contract
          text
         -->P_WA  text
         -->P_HEADER  text
         -->P_HEADERX  text
    FORM fill_header_contract  USING wa STRUCTURE zlo_mmcnv009
                                 coheader STRUCTURE bapimeoutheader
                                 coheaderx STRUCTURE bapimeoutheaderx.
      DATA: dia(2), mes(2), ano(4).
      dia = wa-datestart(2).
      mes = wa-datestart+2(2).
      ano = wa-datestart+4(4).
      CONCATENATE ano mes dia INTO wa-datestart.
      dia = wa-datend(2).
      mes = wa-datend+2(2).
      ano = wa-datend+4(4).
      CONCATENATE ano mes dia INTO wa-datend.
    Purchasing Document Date
      coheader-doc_date = sy-datum.
      coheaderx-doc_date = 'X'.
    *Item Number Interval
      coheader-item_intvl = '10'.
      coheaderx-item_intvl = 'X'.
    Currency Key
      coheader-currency = 'BHD'.
      coheaderx-currency =  'X'.
    languaje
      coheader-langu = 'EN'.
      coheaderx-langu = 'X'.
    Document Type
      IF wa-doctyp <> ''.
        coheader-doc_type = wa-doctyp.
        coheaderx-doc_type = 'X'.
      ENDIF.
    vendor number
      IF  wa-vendor <>  ''.
        coheader-vendor = wa-vendor.
        coheaderx-vendor = 'X'.
      ENDIF.
    purchasing organization
      IF wa-organiz <> ''.
        coheader-purch_org = wa-organiz.
        coheaderx-purch_org = 'X'.
      ENDIF.
    Purchasing Group
      IF wa-purgroup <> ''.
        coheader-pur_group = wa-purgroup.
        coheaderx-pur_group = 'X'.
      ENDIF.
    Start of Validity Period
      IF wa-datestart <> ''.
        coheader-vper_start = wa-datestart.
        coheaderx-vper_start = 'X'.
      ENDIF.
    End of Validity Period
      IF wa-datend <> ''.
        coheader-vper_end = wa-datend.
        coheaderx-vper_end = 'X'.
      ENDIF.
    ENDFORM.                    " fill_header_contract
    *&      Form  fill_item_contract
          text
         -->P_WA  text
         -->P_COITEM  text
         -->P_COITEMX  text
    FORM fill_item_contract  TABLES: coitem STRUCTURE bapimeoutitem
                                     coitemx STRUCTURE bapimeoutitemx
                             USING  wa STRUCTURE zlo_mmcnv009.
    item number
      coitem-item_no = wa-itemnum.
      coitemx-item_no = wa-itemnum.
      coitemx-item_nox = 'X'.
    *Material Number
      IF wa-material <> ''.
        coitem-material = wa-material.
        coitemx-material = 'X'.
      ENDIF.
    *Target Quantity
      IF wa-quantity <> ''.
        coitem-target_qty = wa-quantity.
        coitemx-target_qty = 'X'.
      ENDIF.
    *Net Price in Purchasing Document
      IF wa-netprice <> ''.
        coitem-net_price = wa-netprice.
        coitemx-net_price = 'X'.
      ENDIF.
      APPEND coitem.
      APPEND coitemx.
    ENDFORM.                    " fill_item_contract
    *&      Form  fill_service
          text
         -->P_POSERVICES  text
         -->P_T_ITEM  text
         -->P_ITEMNUM  text
    FORM fill_service  TABLES   poservices STRUCTURE bapiesllc
                                t_item STRUCTURE zlo_mmcnv009
                                poservices_2  STRUCTURE  bapiesklc
                       USING    itemnum packno.
      DATA: line(10) TYPE n,
            service(18) TYPE n,
            packno2(10) TYPE n.
      poservices-pckg_no = packno.
      packno2 = packno.
      packno = packno + 1.
      poservices-line_no = '0000000001'.
      poservices-outl_ind = 'X'.
      poservices-subpckg_no = packno.
      APPEND poservices.
      line = '0000000002'.
      LOOP AT t_item WHERE itemnum = itemnum.
        IF t_item-activity <> ''.
          IF NOT ( t_item-activity CA sy-abcde ).
            service = t_item-activity.
            poservices-service = service.
          ELSE.
            poservices-service = t_item-activity.
          ENDIF.
        ELSE.
          poservices-service = t_item-activity.
        ENDIF.
        poservices-pckg_no = packno.
        poservices-line_no = line. "itemnum.
        poservices-ext_line = t_item-line.
        poservices-quantity = t_item-quantity1.
        poservices-base_uom = t_item-undmed.
        poservices-gr_price = t_item-price.
        poservices-short_text = t_item-shortxt.
        poservices-subpckg_no = '0000000000'.
        poservices-outl_ind = ''.
        APPEND poservices.
        poservices_2-pckg_no = packno.
        poservices_2-line_no = line.
      poservices_2-SERNO_LINE =
      poservices_2-SERIAL_NO =
        poservices_2-quantity = t_item-quantity1.
        poservices_2-net_value = t_item-price.
        APPEND poservices_2.
        line = line + 1.
      ENDLOOP.
    ENDFORM.                    " fill_service
    *&      Form  fill_pocond
          text
         -->P_POCOND  text
         -->P_POCONDX  text
         -->P_WA  text
    FORM fill_pocond TABLES  pocond      STRUCTURE bapimepocond
                             pocondx STRUCTURE bapimepocondx
                       USING wa STRUCTURE zlo_mmcnv009.
    *Net Price in Purchasing Document
      IF wa-netprice <> ''.
        pocond-itm_number = wa-itemnum.
        pocondx-itm_number = wa-itemnum.
        pocond-cond_value = wa-netprice.
        pocondx-cond_value = 'X'.
        pocond-currency = 'BHD'.
        pocondx-currency = 'X'.
        pocond-cond_type = 'PBXX'.
        pocondx-cond_type = 'X'.
    *COND_TYPE
        APPEND pocond.
        APPEND pocondx.
      ENDIF.
    ENDFORM.                    " fill_pocond

  • Depot  Excise Invoice with reference to Delivery from project

    please understood my requirement
    Normal Depo Sales is like VA01-VL01N-J1IJ----VF01 here whatever excise values captured in J1IJ those values come to the commercial Invoice.
    As per My requirement we are creating Project and while creating sales order we have to assign WBS element.
    now Project -Delivery--Excise Invoice J1IJ
    Sales order -
    Inovice VFO1
    my question is how excise and commercial Invoice values come together.
    regards
    etr

    Hello Amol,
    you can create with reference of the deliveyr document. in J1iin trnsaction you have the option in the header tabs of create from delivery
    enter the delivery and create the excise invocie
    Hope this helps
    Thanks
    akasha

Maybe you are looking for