Regarding Purchase order message Type

Hi
I am maintain purchase order type through MN04.
Now i want to message type with all condition which is maintained through MN04.
Is there these entries are stored in any tables?
If yes can any one provide me table name.
Thanks
DD

Hi,
Please check with acess sequence assigned to the output type, if the combination Purch. Organization and Vendor click F1 and find the table each access sequence assigned to the output type will define a new table
For example:
table -B025-Purchasing Output Determination: Doc.Type/Purch.Org/Vendor
          B026-Purchasing Output Determination: Document Type
          B987-Output Determination Training: EKO
           B027- Purchasing Output Determination: Purch. Org./Vendor for EDI
You can use like this
Regards,
Pramod

Similar Messages

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

I need output type NEU automaticaly for create purchase order document type

Dear Experts,
I need output type NEU automaticaly for create purchase order document type NB
when transaction code MN04, I am doing the following:
(1) I selected the third option Purchasing Output determination: Document type
(2) I selected the output type NEU.
(3) In condition records in document type , i have chosen NB.
(4) In name its automatically coming as Purchase requisition
Please suggest how Purchase Order NB will come

Hi,
Check & press F4, NB Purchase Order (for catagory F) will be there after entering PO output type NEU & then maintaion the condition record in MN04.
Output type NEU automaticaly defaulted during purchase order creation with document type ,then just fine tune the output (message) type in following path:
SPRO--->MM->Purchasing>Message>Output control->Message types> Define message type for Purchase Order----->Fine-Tuned Control: Purchase Order
Now here select the check box corresponding to your output(message) type NEU to have print output automatically displayed & save.
Now try to creating Purchase Order & you will have default message type NEU.
Regards,
Biju K

Material Statuses based on the Purchase order Document type

Hi Experts,
We need to maintain the Plant material status based on the purchase order document type.
Example - If I am using NB for normal purchase orders and ZB for STO procurement then, there should be a material status which should give warning message - 'do not use ' for ZB STO purchase orders and it should allow to create NB purchase orders for that same materials.
Please advise what are the possibilities?
Thanks
Regards
MM

Hi Gurus,
Thank you for your reply, Please find my replies below
@@ - Mallinath - We need this restrictions for some type of materials ( with specific Material types) which should not be procured through inter company STO process, buying plant should use the normal purchase. for other Material types they should be able to use the inter company STO process.
@@ DEV - We are already using the Spl. Procurement keys for inter company STO process.
Example - Material type ZXYX should not use the inter company STO process, but it should be allowed all other processes.
Please advise how we can control this process?
Thanks
Regards
Raja

Event : changing purchase order's type in transaction ME21N

Hi all,
I am looking for a user exit or an enhencement to set some abap code when a purchase order's type is changed by the user in transaction ME21N.
Thanks.
Regards,

Hi,
Please find the user exit list below for ME21N. You can try out.
USER EXIT
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
M06B0003 Number range and document number
M06B0002 Changes to comm. structure for purchase requisition release
Thanks,
Raj

Purchase Order Document Type and Account Assignment

Hi ,
We have a requirement to control Account Assignment in Purchase Order Item line based on the Document type selected on the Purchase Order header.
Like if user selects Purchase Order document type "ZNB" (Customized created) , then he will only able to select "K" or Blank or "P" as account assignment and similary we want to limit other Account assignments based on the Purchase Document type.
How can we make this Control settings?
Regards
Shrey

Hi,
You can't really limit the account assignment categories per document type, at least not directly.
You can limit the item categories that can be used for a document type via configuration:
Materials Management > Purchasing > Purchase Order > Define Document Types
Within this transaction you can define which item categories are valid for a specific document type.
You can then define which account assignment categories are valid for each item category
Materials Management > Purchasing > Account Assignment > Define Combination of Item Categories/Account Assignment Categories
BUT
limiting the account assignment categories that are valid for an item category will affect ALL purchase order document types that this item category is valid for. And you can't create your own item categories as this is a SAP standard table that can NOT be altered.
Regards,
Monika

Purchase Order Service Type

Hello All,
My client wants the gross price to be calculated based on the quantity on purchase order (service Type).
Can anyone help on this please.
Cheers

Hi Satish....
You can see the Gross Price Calculations on Right Click Gross Profit Option for Service Type.....
Please check it on Sales Window....
Regards,
Rahul

Purchase order service type through code

Hi Experts,
Can we create a purchase order of type service through code ?
Please give me some sample codes
Thanks in advance
Regards
Arun

Hello,
I think this is an userfield? Or a field that i don't know?
purchaseOrder.Lines.LocationCode = 2
For testing you must keep your code simple, first only fill the mandatory fields:
And catch you errormessage as well.
Dim purchaseOrder As SAPbobsCOM.Documents = B1Connections.diCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoices)
            'Set values to the fields
            purchaseOrder.DocObjectCode = BoObjectTypes.oPurchaseOrders
            purchaseOrder.CardCode = "V0001"
            purchaseOrder.DocType = BoDocumentTypes.dDocument_Service
            purchaseOrder.DocDate = Today
             purchaseOrder.DocDueDate = Today
            purchaseOrder.TaxDate = Today
            purchaseOrder.Lines.ItemDescription = "TESTPO"
            purchaseOrder.Lines.AccountCode = "500201"
            Dim lRetCode As Integer
            lRetCode = purchaseOrder.Add
            If lRetCode != 0 Then
                B1Connections.theAppl.SetStatusBarMessage("Error occured.", SAPbouiCOM.BoMessageTime.bmt_Short, True)
            Else
                B1Connections.theAppl.SetStatusBarMessage("Purchase order created.", SAPbouiCOM.BoMessageTime.bmt_Short, True)
            End If
HTH Regards Teun
Edited by: Teun Aben on Oct 22, 2010 3:54 PM

Purchase Order Document type FO?

Hi,
Why we need to use in Purchase Order Document type FO?
With Document type NB also we can make Services ,Right?
Thanks

Hi
FO - Frame work order Document type is a standard document type , which is used for Blanket Purchases, Purchase of services.
The FO document type has a Validity Start & End date feature whcih is not in the NB document type(You can get the same in NB also after cusotmization)
Services & limits are also presnet. The FO document type is limited to usage for Iterm categories
     Standard
B     Limit
D     Service
All these can be made for NB also, but only after customizing.
Thanks & Regards
Kishore

Purchase Order Document Type Defaulting in ME58 while converitn PR to PO

Dear All
While converting Purcahse Requesition to Purchase Order in ME58, System defaults one Purchase order document type . Ofcourse we can overwrite that
But would like to know how this defaulting can be controlled in SAP
Regards
Shyam

Hi,
If you have maintained an "Order Type" in table T160 (customizing
transaction OMH5) for the entry "ME21", then this value will be
defaulted in the pop-up in transaction ME58. Otherwise, the "Order Type"
of the Requisition will be defaulted.
The following code block of program (Note 125969) is for your reference:
SELECT SINGLE * FROM T160 WHERE TCODE EQ SY-TCODE.
IF SY-SUBRC EQ 0 AND NOT T160-BSART IS INITIAL.
   RM06E-BSART = T160-BSART.
ELSE.
   SELECT SINGLE * FROM T160 WHERE TCODE EQ 'ME21'.
   IF SY-SUBRC EQ 0 AND NOT T160-BSART IS INITIAL.
     RM06E-BSART = T160-BSART.
   ELSE.
     RM06E-BSART = BAT-BSART.
   ENDIF.
ENDIF
According to the code above, the system first checks the table T160 for
ME58, if there is no data then for ME21, if there is no data, then it
defaults from PREQ.This is the same as described in the note 114213.
BR
Nadia Orlandi

Restrict purchase order document type at plant level

Dear,
I would like to restrict the purchase order document type at plant level,
Plz help me.

Hi Dear,
             at the Plant level you have to use the below given Authorization Objects for the Users in different Plant
M_BEST_BSA     Document Type in Purchase Order
M_BEST_WRK     Plant in Purchase Order
Give the values of the respective Plant and Order Type for the Respective Users.
For more help you can contact your Security Team.
but before that please check out in the T-Code SU24, if both the Objects are active, if not then ask the ABAP person to activate them.
Hope it helps you.
regards,
yawar Khan

Specific process code for Production order message type LOIPRO

Hello,
Is there any specific process code for Production order message type LOIPRO.
Request you to reply.
Thanks
Prashanth

Hi Prashanth,
sorry for last thread ... that not contain full information ...
For message type LOIPRO you can use process code APLI.
In IDOC PARTNER definition, the partner is linked with an IDOC TYPE and PROCESS CODE for inbound processing. This process code is in turn linked with a FUNCTION MODULE to process the IDoc such as IDOC_INPUT_INVOIC_MRM (Reff.. http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_cid519558,00.html)
Regards,
Amit

Authorization based on plant and Purchase order document type

Hi
My client has a requirement wherein a user will have authorization for transactions only in his plant. But only for Purchase order document type UB (Stock Transport Order) the user should be allowed to create for all plants.
In short, if Purchase order document type is UB, should be allowed for all plants
if Purchase order document type is NB, should be allowed to only one particular plant.
My Basis person says that such a restriction is not possible.
Kindly suggest me on how to provide a solution to this.
Thank U.

Hi,
This is possible.In this case you need to create two seperate roles.
1)Create purchase order for all plants (This can be used in long text)
2)Create purchase order for <plant no> plants.
For case 1:--
i)Populate field BSART of M_BEST_BSA with UB.
ii)Populate field WERKS of M_BEST_WRK with '*'. SAP reccomends to fill up organizational data through organizational level tab only.So while doing this step you need to put * from organizational level tab only.
For case 2:--
i)Populate field BSART of M_BEST_BSA with NB.
ii)Populate field WERKS of M_BEST_WRK with 'plant no'.
Dont worry about the objects i mentioned those are maintained through SU24 and will be automatically pulled once you insert ME21 transaction code.
Let me know if it helps.
Thanks,
Aveek

Remove Planned Purchase Order from Type field on Purchase Order form.

Have requirement to remove Planned Purchase Order from LOV on purchase order form in 11.5.10.2. Tried to disable the Planned Purchase Order document type but Disable field isn't updatable. How can I remove Planned Purchase Order from LOV?

You can modify list of values in a form with CUSTOM.pll.

Authorization Object for Purchase order Message control

Hi ,
Is there any stadard authoriztion object to control the print and print preview options for Message control .
I am requied to control the print and print preview options for purchase order messages for certain users depeding on there authorizaion.
Thanks in advane.

Hi,
When you click on the 'print preview' button on ME22N/ME23N the system
makes an authority check on transaction ME9F activity 04. The current
logic forces the print preview functionality to be accessed ONLY by the
users who print. Therefore, only users that have authorization to use
ME9F are authorized to use the Print Preview button in ME22N/ME23N.
Kindly try the authorization objects M_BEST_EKG, M_BEST_BSA and
M_BEST_EKO = 04.
You can
also have a look the user exit
EXIT_SAPLMEDRUCK_001 in enhancement LMEDR001 for print program
SAPLMEDRUCK.
INCLUDE ZXM01U04
you can create own coding for all possible AUTHORITY-CHECK.
BR
Nadia Orlandi

Regarding Purchase order message Type

Similar Messages

Maybe you are looking for