Regarding Purchase order ME21N

Hi gurus,
My requirement is i need to place the time field in ME21N transaction.When ever i created purchase order on that time the time is recorded and it stored in database.Please can any one help me out this.
Thanks in Advance.
Regards
Srihari.

Hi,
Use the enhancement 'MM06E005'.
First Create one project in CMOD then assign this enhancement and activate it.
Then add a new field in the custom include(CI_EKKODB) of
EKKO table.then in 'EXIT_SAPMM06E_018' pass the system time to ur new field,system will automatically update database(table).
rewards points if helpful.
Regards,
Srinivas Ch

Similar Messages

INFO UPDATE in the purchase order ( ME21N)

Why the field INFO UPDATE in the purchase order ( ME21N) is not flaged when I create a purchase order?
I create a PO, and I flag it in ME21N, but it cancel it? WHY
I have already tried it in spro Default values for purchasing, and all seem good!!
Anybody could tell how can I tick this field?
Thanks a lot
Kari

Hi
Info update indictor can be set by defualt if you maintain the same in the Purchase inforecord,
If no inforecord exists then this would not be flagged and if you flag it then the Purchase inforecord gets created with the update of with or wothout plant based on the default value assigned to the buyers.
Thanks & Regards
Kishore

BADI / User exit for Purchase order(ME21N) after saving the document

Hi expert,
I need the BADI / User exit for Purchase order(ME21N) after saving the document
This is for email sending after create the purchase order so PO document number will be the import parameter
pls help me
point will be reward
Regards,
Ganesh

Hi Ganesh,
Could you please share your solution?
Thanks.
Hoops
Edited by: Hoops on Jun 13, 2011 10:51 PM

Error while saving a vairant in purchase order- ME21n

Hai friends,
While creating/saving a variant in create purchase order transaction(me21n) it is showing the error as " Not all radio buttons from radio button group FUNC were hidden". Can any one help me to fix this problem.
Thanks
Hari

Hi,
Could you please implement the following sap-notes and restest
this issue.
923131 If you start a report w/ variant, radio buttons not hidden
962712    DB291 for saving a variant: Radio button group func
994798   Error DB 291 when saving variants
Thanks
Best regards
Erika

Smartform in Purchase Order ME21N

Hi guys.
I'm working in SAP 6.0 ECC. I am developing a sapscript for purchase order and it is working well, but i wanna do the same in smartform, i checked on the web that sap 6.0 ecc has some standard smartform for Purchase Order, but mine doesnt have it. In addition, i tried to convert my sapscript to smartform, but the only thing that converts are the windows, no tables or variables, so it doesnt work.
how can i do it? somebody did a smartform for ME21N??? what are the parameters that i need to use? the idea is that this smartform will be trigged at the moment of release the purchase order throught ME29N.
Regards
it will be super usefull that somebody could send me a smartform

Sending attachments by mail is not really compliant with forum rules (because other people won't get the information).
The good answer would have been to look at SDN "smart forms" home page, then look at section "preconfigured smart forms".
It says that it must be downloaded from SWDC (SAP software download center), choose Installations and Upgrades -> ...Entry by Application Group -> SAP Best Practices -> SAP BP BASELINE PACKAGE ...

Regarding Purchase Order Error:

Hai Gurus,
I have created a standard purchase order using ME21N transaction code, while saving the system is throwing an error message which reads Error in net price calculation, item 000001 (Please correct).
When I changed the payment terms for the same vendor there is no error. Please help me out how to correct the error message with out changing the payment terms in the vendor master.
Thanks in advance.
Shankar G.

Dear,
Then Why isn't Showing Any Error after Changing the Payment Terms???
Can u send me the Screen Shot of both the Payment Terms & item Condtion Pricing in this mail id [email protected]
Regards
Biswajit

Fetching fields from Purchase Order - ME21N

Hi,
I need to fetch the 'Delivery Date', 'Scheduled Qty', 'Committed Date', 'Committed Quantity', 'Material Availability Date' ' Goods issue Date' for a Purchase order.
The tcode is ME21N.
From which table can i get these fields, as F1 help on these fields shows a structure.
Is there any Function Module or BAPI which i can use.
Regards.

>
Akshay Raj wrote:
> Hi,
>
> I need to fetch the 'Delivery Date', 'Scheduled Qty', 'Committed Date', 'Committed Quantity', 'Material Availability Date' ' Goods issue Date' for a Purchase order.
>
> The tcode is ME21N.
>
> From which table can i get these fields, as F1 help on these fields shows a structure.
>
> Is there any Function Module or BAPI which i can use.
>
> Regards.
se84-> abap dictionary-> fields-> table fields -> short description-> execute

Problem regarding Purchase Order with Free of Cost Material

Dear Xperts,
I am facing problems while doing Goods Receipt of a Purchase Order having all the materials we are going to receive Free of Cost from the Vendor.
This case is happening with Doemstic and as well as Importer Vendors also.
Problems to be solved:
1. If we are using Tax Code(with excise conditions) ,excise duty calculation does not take pace automatically at Goods Receipt as the Material Value is Zero on which the duties will be calculated for a Manufactuing Plant.
2. This case seems very problammatic if that Purchase Order is having almost thousand line items.The user has to enter all the Excise duties manually for each & every line item during Goods receipt in a manufacturing Plant.
3. In case of Importer Purchase Order also, the CVD portion & CESS on CVD portion user has to enter manually.
4. To solve this problem we are not using Free Goods Indicator in PO, we are entering 0.01 paisa , but during the MIRO of Planned Delivery Costs , the system is not showing or providing POP-ups of those relevant condition types to the user to enter the actual amount.
Please advice, how can we proceed in this case.
Regards,
Soumick

First you are putting 0.01 value . So the planned delivery cost is not showing coz if say tax is 8% then 0.01 x 0.08 will be 0.0008. It will take first two digit after decimal and hence its 0.00 and hence plannded delivery cost is not showing.
If you put 0.5 you will be able to put planned delivery cost in MIRO
Now regarding value is zero and how will the import duty be calculated. May be make a pricing routine where in the custom duty is not calculated on this base price 0.5 or 0.01 but on the actual value if it was not free of cost and that value you can maintain through MEK1 transaction code.
And while posting MIRO or MIGO you need to identify that these are free of cost material and use BADI fi_ac_document
and may be replace the actual GL with some other GL so that 0.5 or 0.01 does not add to your inventory cost and you could knock off later.
Regards
Sangeeta
Edited by: Sangeeta Khurana on Feb 6, 2012 1:37 PM

Regarding Purchase order upload

Dear All,
I have to upload the Purchase orders in to the SAP using DTW.i have fillled the follwing fields in to the opor and POR1 template but it is showing application error.
OPOR
Record Key
Docentry
address
cardcode
docduedate
docdate
doctotal
POr1
Recordkey
linenum
accountcode
itemcode
price
quantity..........
I think am missing a manadatory field.......Pls give me a solution to this...............Also tell me what are the mandatory fields that has to be filled for uploading.Actually the datas are large so i cannot ask the client to type all of them......Uploading is the only way..........So pls help me out.
Regards,
Shyam

Hello ,
You dont need to fill thise field in OPOR
Record Key
address
doctotal
because these all field all system generated
Then try again upload it.
Thanks
Manvendra Singh Niranjan

Regarding purchase order report in bw

Hi guys,
I have a requirement for report in bw. I am getting data form datasources from po header and item level. In the report i have to show Purchase order quantity,
Goods recived quantity, MRP and goods reciept value. Can u tell me what all the infoobjects i have to take for these fields in BW. Its urgent. I will definitley award points.Also tell me the fields from R/3 and from which tables they are coming from.
Regards,
Niranjan
[email protected]

Hi Niranjan,
check this link u will know all fields in bw and r/3..if u have any concerns get back to me.
http://help.sap.com/saphelp_nw2004s/helpdata/en/ed/62073c44564d59e10000000a114084/frameset.htm(header level)
http://help.sap.com/saphelp_nw2004s/helpdata/en/ed/62073c44564d59e10000000a114084/frameset.htm ( Item level)
Regards anil.

Regarding purchase order

hi,
is there any standard report for open purchase order ?
what are the tables and field used for open purchase order report.
thank u
ravi

Hi,
There is no Std report for this;
See the report for Open PO's
*& Report ZMM_PO_REPORT
REPORT ZMM_PO_REPORT message-Id yb
       NO STANDARD PAGE HEADING
       LINE-COUNT 60(1)
       LINE-SIZE 230.
       D A T A B A S E T A B L E S   D E C L A R A T I O N
TABLES: lfa1,           " Vendor Master
        t161,           " PO Doc Types
        t024,           " Purchase Groups
        ekko.           " PO Header
               T Y P E S D E C L A R A T I O N S
Purchase Orders Main Structure
TYPES: BEGIN OF s_po,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        bstyp TYPE bstyp,           " PO Category
        bukrs TYPE bukrs,           " Company Code
        bsart TYPE bbsrt,           " PO Type
        lifnr TYPE lifnr,           " Vendor No
        ekgrp TYPE bkgrp,           " Purchase Group
        waers TYPE waers,           " Currency
        bedat TYPE etbdt,           " PO Date
        txz01 TYPE txz01,           " Material Text
        werks TYPE ewerk,           " Plant
        lgort TYPE lgort_d,         " Storage Location
        matkl TYPE matkl,           " Material Group
        menge TYPE bamng,           " PR Quantity
        meins TYPE bamei,           " UOM
        bprme TYPE bbprm,           " Price Unit
        netpr TYPE netpr,           " Net price
        peinh TYPE peinh,           " Price Unit UOM
        pstyp TYPE pstyp,           " Item Category
        knttp TYPE knttp,           " Account Assignment Category
       END OF s_po.
Purchase Orders History Structure
TYPES: BEGIN OF s_account,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        gjahr TYPE mjahr,           " Fiscal Year
        belnr TYPE mblnr,           " PO Invoice No
        menge TYPE menge_d,         " PR Quantity
        wrbtr TYPE wrbtr,           " Price in Local Currency
        dmbtr TYPE dmbtr,           " Price in Foreign Currency
        waers TYPE waers,           " Currency
        shkzg TYPE shkzg,           " Dr/Cr Indicator
       END OF s_account.
Purchase Orders History Structure(Item Sum)
TYPES: BEGIN OF s_inv_sum,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        menge TYPE menge_d,         " PR Quantity
        wrbtr TYPE wrbtr,           " Price in Foreign Currency
        waers TYPE waers,           " Currency
       END OF s_inv_sum.
Purchase Orders Main Structure
TYPES: BEGIN OF s_rep,
        lifnr TYPE lifnr,           " Vendor No
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        bstyp TYPE bstyp,           " PO Category
        bsart TYPE bbsrt,           " PO Type
        ekgrp TYPE bkgrp,           " Purchase Group
        waers TYPE waers,           " Currency
        bedat TYPE etbdt,           " PO Date
        txz01 TYPE txz01,           " Material Text
        werks TYPE ewerk,           " Plant
        lgort TYPE lgort_d,         " Storage Location
        matkl TYPE matkl,           " Material Group
        menge TYPE bamng,           " PR Quantity
        meins TYPE bamei,           " UOM
        bprme TYPE bbprm,           " Price Unit
        netpr TYPE netpr,           " Net price
        peinh TYPE peinh,           " Price Unit UOM
        pstyp TYPE pstyp,           " Item Category
        knttp TYPE knttp,           " Account Assignment Category
        name1 TYPE name1,           " Plant
        orewr TYPE netpr,           " To be Invoiced Price
        curr TYPE waers,           " Inv Doc Currency
       END OF s_rep.
           D A T A D E C L A R A T I O N S
DATA: gv_title1 TYPE sylisel,            " Report title
      gv_dial.                           " Color flag
            C O N S T A N T S D E C L A R A T I O N S
CONSTANTS: c_x                VALUE 'X',   " Flag X
           c_h                VALUE 'H',   " Debit
           c_vgabe TYPE vgabe VALUE '2'.   " Transaction Type
     I N T E R N A L T A B L E S D E C L A R A T I O N S
DATA: i_po    TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
                             " Purchase Order
      i_inv   TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
                                     " PO Invoice Values
      i_rep   TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
                                 " PO Invoice Values
      i_ekbe TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
                           " PO Invoice Values
                 S E L E C T I O N S C R E E N                      *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
                s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
                s_bsart FOR t161-bsart,
                s_ekgrp FOR t024-ekgrp,
                s_bedat FOR ekko-bedat.
SELECTION-SCREEN END OF BLOCK b1.
                  I N I T I A L I Z A T I O N                        *
INITIALIZATION.
              A T S E L E C T I O N - S C R E E N                   *
AT SELECTION-SCREEN.
Validate the screen fields
PERFORM validate_screen.
               S T A R T - O F - S E L E C T I O N                   *
START-OF-SELECTION.
Fetch main data
PERFORM fetch_data.
               T O P - O F - P A G E                                 *
TOP-OF-PAGE.
Header of the List
PERFORM header.
               E N D - O F - P A G E                                 *
Footer
END-OF-PAGE.
ULINE.
               E N D - O F - S E L E C T I O N                       *
END-OF-SELECTION.
Display the Report Output data
PERFORM display_data.
At Line-Selection
AT LINE-SELECTION.
When double clicked on EBELN display the details of Purchase Doc
PERFORM line_sel.
*&      Form validate_screen
Validation of Selection Screen fields
FORM validate_screen .
Validation of Vendor Number
CLEAR lfa1-lifnr.
IF NOT s_lifnr[] IS INITIAL.
    SELECT lifnr UP TO 1 ROWS
        INTO lfa1-lifnr
        FROM lfa1
        WHERE lifnr IN s_lifnr.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Vendor'(002).
    ENDIF.
ENDIF.
Validation of PO Number
CLEAR ekko-ebeln.
IF NOT s_ebeln[] IS INITIAL.
    SELECT ebeln UP TO 1 ROWS
        INTO ekko-ebeln
        FROM ekko
        WHERE ebeln IN s_ebeln.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Document Number'(003).
    ENDIF.
ENDIF.
Validation of PO Document Type
CLEAR t161-bsart.
IF NOT s_bsart[] IS INITIAL.
    SELECT bsart UP TO 1 ROWS
        INTO t161-bsart
        FROM t161
        WHERE bsart IN s_bsart.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
    ENDIF.
ENDIF.
Validation of Purchasing Group
CLEAR t024-ekgrp.
IF NOT s_ekgrp[] IS INITIAL.
    SELECT ekgrp UP TO 1 ROWS
        INTO t024-ekgrp
        FROM t024
        WHERE ekgrp IN s_ekgrp.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
    ENDIF.
ENDIF.
ENDFORM.                    " validate_screen
*&      Form fetch_data
Fetching the PO related data from Database Tables
FORM fetch_data .
CLEAR i_po.
REFRESH i_po.
SELECT a~ebeln            " PO No.
         b~ebelp            " PO Item
         a~bstyp            " PO Category
         a~bukrs            " Company Code
         a~bsart            " PO Type
         a~lifnr            " Vendor No
         a~ekgrp            " Purchase Group
         a~waers            " Currency
         a~bedat            " PO Date
         b~txz01            " Material Text
         b~werks            " Plant
         b~lgort            " Storage Location
         b~matkl            " Material Group
         b~menge            " PR Quantity
         b~meins            " UOM
         b~bprme            " Price Unit
         b~netpr            " Net price
         b~peinh            " Price Unit UOM
         b~pstyp            " Item Category
         b~knttp            " Account Assignment Category
    INTO TABLE i_po
    FROM ekko AS a JOIN ekpo AS b
    ON a~ebeln = b~ebeln
    WHERE a~ebeln IN s_ebeln AND
          a~lifnr IN s_lifnr AND
          a~ekgrp IN s_ekgrp AND
          a~bsart IN s_bsart AND
          a~bedat IN s_bedat.
SORT i_po BY ebeln ebelp.
break-point.
IF NOT i_po[] IS INITIAL.
Fetch the PO History/Invoice Details from EKBE Table
    CLEAR i_ekbe.
    REFRESH i_ekbe.
    SELECT ebeln           " PO No.
           ebelp           " PO Item
           gjahr           " Fiscal Year
           belnr           " PO Invoice No
           menge           " PR Quantity
           wrbtr           " Price in Local Currency
           dmbtr           " Price in Foreign Currency
           waers           " Currency
           shkzg           " Dr/Cr Indicator
     INTO TABLE i_ekbe
     FROM ekbe
     FOR ALL ENTRIES IN i_po
     WHERE ebeln = i_po-ebeln AND
           ebelp = i_po-ebelp AND
           vgabe = c_vgabe.
break-point.
    IF sy-subrc = 0.
      SORT i_ekbe BY ebeln ebelp.
      LOOP AT i_ekbe.
        IF i_ekbe-shkzg = c_h.
          i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
        ENDIF.
        MODIFY i_ekbe.
      ENDLOOP.
break-point.
Sum up the Item wise Invoice totals
      LOOP AT i_ekbe.
        AT END OF ebelp.
          READ TABLE i_ekbe INDEX sy-tabix.
          SUM.
          MOVE-CORRESPONDING i_ekbe TO i_inv.
          APPEND i_inv.
        ENDAT.
        CLEAR i_inv.
      ENDLOOP.
      SORT i_inv BY ebeln ebelp.
        break-point.
    ENDIF.
ENDIF.
Move the Vendor Name and Invoice Values to I_rep Internal Table
LOOP AT i_po.
    MOVE-CORRESPONDING i_po TO i_rep.
    CLEAR i_inv.
    READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
                              ebelp = i_po-ebelp.
    IF sy-subrc = 0.
      i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
      i_rep-curr = i_inv-waers.
    ELSE.
      i_rep-orewr = i_po-menge * i_po-netpr.
      i_rep-curr = i_po-waers.
    ENDIF.
break-point.
Get the Vendor Name
    CLEAR lfa1-name1.
    SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
      WHERE lifnr = i_po-lifnr.
    IF sy-subrc = 0.
      i_rep-name1 = lfa1-name1.
    ENDIF.
    APPEND i_rep.
    CLEAR i_rep.
      break-point.
ENDLOOP.
SORT i_rep BY lifnr ebeln ebelp.
DELETE i_rep WHERE orewr LE 0.
break-point.
ENDFORM.                    " fetch_data
*&      Form display_data
Display the Report Output data
FORM display_data .
DATA: lv_flag,               " New Flag
        lv_rec TYPE i.         " No of Records
CLEAR lv_rec.
IF i_rep[] IS INITIAL.
    MESSAGE e000 WITH 'No Data found'(022).
ELSE.
    LOOP AT i_rep.
Toggle Color
      PERFORM toggle_color.
      IF lv_flag <> space.
        NEW-LINE.
      ENDIF.
At New Purchase Document
      AT NEW ebeln.
        WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
        lv_flag = c_x.
        lv_rec = lv_rec + 1.
      ENDAT.
      WRITE: 1 sy-vline,
            12 sy-vline,13(4)   i_rep-bsart,
            17 sy-vline,18(10) i_rep-lifnr,
            28 sy-vline,29(35) i_rep-name1,
            64 sy-vline,65(4)   i_rep-ekgrp,
            69 sy-vline,70(10) i_rep-bedat,
            80 sy-vline,81(5)   i_rep-ebelp,
            86 sy-vline,87(40) i_rep-txz01,
           127 sy-vline,128(9) i_rep-matkl,
           137 sy-vline,138(1) i_rep-pstyp,
           139 sy-vline,140(1) i_rep-knttp,
           141 sy-vline,142(4) i_rep-werks,
           146 sy-vline,147(4) i_rep-lgort,
           151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
           165 sy-vline,166(3) i_rep-meins,
           169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
           185 sy-vline,186(4) i_rep-waers,
           190 sy-vline,191(5) i_rep-peinh,
           196 sy-vline,197(4) i_rep-bprme,
           201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
           217 sy-vline,218(4) i_rep-curr,
           222 sy-vline,223(7) i_rep-bstyp centered,
           230 sy-vline.
      NEW-LINE.
      hide: i_rep-ebeln.
    ENDLOOP.
    ULINE.
    FORMAT COLOR OFF.
    WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
                lv_rec COLOR 3.
ENDIF.
ENDFORM.                    " display_data
*&      Form header
Write the Report Header
FORM header .
FORMAT RESET.
header
WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
SKIP.
FORMAT COLOR COL_HEADING.
ULINE.
WRITE:/1 sy-vline,2(10)   'Pur.Doc.No'(006) CENTERED,
        12 sy-vline,13(4)   'Type'(007),
        17 sy-vline,18(10) 'Vendor'(008) CENTERED,
        28 sy-vline,29(35) 'Name'(009) CENTERED,
        64 sy-vline,65(4)   'PGrp'(010) CENTERED,
        69 sy-vline,70(10) 'Doc.Date'(012) CENTERED,
        80 sy-vline,81(5)   'Item'(011),
        86 sy-vline,87(40) 'Material Short Text'(024) CENTERED,
       127 sy-vline,128(9) 'Mat.Group'(013),
       137 sy-vline,138(1) 'I',
       139 sy-vline,140(1) 'A',
       141 sy-vline,142(4) 'Plnt'(014),
       146 sy-vline,147(4) 'SLoc'(015),
       151 sy-vline,152(13) 'Quantity'(016) CENTERED,
       165 sy-vline,166(3) 'UoM'(017),
       169 sy-vline,170(15) 'Net Value'(018) CENTERED,
       185 sy-vline,186(4) 'Curr'(019),
       190 sy-vline,191(5) 'Per'(020),
       196 sy-vline,197(4) 'Unit'(021),
       201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
       217 sy-vline,218(4) 'Curr'(019),
       222 sy-vline,223(7) 'Doc.Cat'(026),
       230 sy-vline.
ULINE.
ENDFORM.                    " header
*&      Form toggle_color
This routine alters the color of the records in the list
FORM toggle_color.
IF gv_dial = space.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    gv_dial = c_x.
ELSE.
    FORMAT COLOR 1 INTENSIFIED OFF.
    CLEAR gv_dial.
ENDIF.
ENDFORM.                    " toggle_color
*&      Form LINE_SEL
*When double clicked on EBELN field display the details of Purchase Doc
FORM line_sel.
CASE sy-lsind.
    WHEN '1'.
      DATA: lv_field(20),
            lv_value(10),
            lv_bstyp like i_rep-bstyp.
      clear: lv_bstyp,lv_value, lv_field.
      GET CURSOR FIELD lv_field VALUE lv_value.
      IF lv_field = 'I_REP-EBELN'.
        IF NOT lv_value IS INITIAL.
          READ LINE sy-index FIELD VALUE i_rep-bstyp
                                   INTO lv_bstyp.
         READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
          if lv_bstyp = 'F'.
            SET PARAMETER ID 'BES' FIELD lv_value.
            CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
          elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
            SET PARAMETER ID 'VRT' FIELD lv_value.
            CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
          elseif lv_bstyp = 'A'.
            SET PARAMETER ID 'ANF' FIELD lv_value.
            CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
          endif.
        ENDIF.
      ENDIF.
ENDCASE.
ENDFORM.                    " line_sel
<b>reward points if useful</b>
regards,
Anji
Message was edited by:
        Anji Reddy Vangala

Authorization in purchase order(ME21N) and inbound delivery(VL31N)i

I have the following scenario and requirement:
there is a customer adopt concentrated procurement. the headquarter create purchase order and the branches create the inbound delivery. all the data including company code, purchase organization, purchase group and the plant are same except the information of goods receipt person we put in header text field.
now i want to control the authorization in VL31N depend on the goods receipt person or something related, how can do this? please kindly let me know?

Hi,
You can use the storage location or shipping point as authorization control, these two should be different for different locations.
Regards,
Ramakrishna

DBIF_RSQL_INVALID_RSQL when creating a Purchase Order (ME21N)

Hi,
The system is generating a short dump DBIF_RSQL_INVALID_RSQL when a user tries to create a purchase order.
what could be the cause of this? i have analysed the short dump in st22 and looked at sm21 and st11 and they are giving very little detaill.
                                                                                Error in the module RSQL accessing the database interface.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLZMM_GET_ACT" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"ZMM_GET_ACT_PLN" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL Statement violates a
restriction imposed by the database system used in R/3.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
o The statement contains too many input variables.
o The space needed for the input data exceeds the available memory.
o ...
You can usually find details in the system log (SM21) and in the
developer trace of the work process (ST11).
If an error occurs the developer trace often informs you about the
current restrictions.
How to correct the error
The exception must either be prevented, caught within the procedure
"ZMM_GET_ACT_PLN"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
The SAP Open SQL statement must be divided into several smaller units.
If the problem occurred due to the use of an excessively large table
in an IN itab construct, you can use the addition FOR ALL ENTRIES
instead.
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
"SAPLZMM_GET_ACT" or "LZMM_GET_ACTU01"
"ZMM_GET_ACT_PLN"

Hi,
Wherever you have used SQL statement please do check all the fields here as some of the fields are not in correct order as they are required per the actual table in dictonary, to just verify that you can use addition of "INTO CORRESPONDING FIELDS OF INTERNALTABLE" in your SQL statement as this will not require the fields to be in order but this may cause performance issue.
Thanks and Regards
Sudharshan

Regarding Purchase order MEDRUCK

Hi gurus,
What actual my doubt is when i saved purchase order that time i need to fetch . For example on 10/01/2008 at 1.00 pm they created purchase order.may be tomorrow they will send that purchase order to vendor.so if they take print out on tomorrow, it needs to show todays ate time.But by default in satndard purcahes order MEDRUCK the date will be displayed,So the total problem with the time field only.When i consult my functional people they told there is no time field in tables so you have to fetch that on . Please guide for this query.
Thanks in advance.
Regards
Srihari.

Hi,
You cannot enable the Copy From button on the purchase order window. This is because there is no originating document for a purchase order (which is the first document in the chain on the purchasing side).
Perhaps if you explain your reasons for needing this functionality someone can come up with a suitable workaround.
Kind Regards,
Owen

Down payment Request from purchase order (me21n)

We need Down payment Request automatically created as per payment terms from purchase order screen.(ME21N)

no answer

Regarding Purchase order ME21N

Similar Messages

Maybe you are looking for