Blocking material for Purchase order only

hi all,
i have a material and i want to block it for purchase order only bcos we dont want to allow to purchase it but it can perform all other operations. can anyone please help me?
regards saurabh.

Dear,
Go to MM02, in Basic1 tab
X-plant material status - 01 Blocked for procment/whse
but it is relevant not only for that plant but also for client level becoz while go to MM02, please not select any plant and go to Basic Data 1 tab.
this may help u
Reagrds,
pardeep Malik
Edited by: Pardeep Malik on Mar 14, 2009 5:59 AM
Edited by: Pardeep Malik on Mar 14, 2009 6:06 AM

Similar Messages

Block material for sales order

Dear All,
there is any transaction code to release the block material(for sales order) with refernce to specific plant.
i can do in CO06 but we can delete one by one.
but i want to delete all blocked material form 2008 to till date.
Regards
ajit

Actually i have created a numbers of order since 2006 to till date but delivery is still pending.
because of this material is blocked for specific order and i can not create order for particular material because its block,
i have around 100 orders.
i know that we can do through CO06.but i don't want to do one by one.
Regards
ajit

Block material for purchasing standard p.o

Does anyone know how can i block purchase orders only for NB (standard po) type.
When i go to MM02 and change the X-plant matl status to 03, all purchase orders can't be made to this material.
I want to block only the NB purchase order.
Thank you,
in advance
Lilah.

In case you are lokking for funtion that standard materials like Raw materials and packing materials should not be ordered via document type NB, then control it via the ITem category reference in customizing.
SPRO > MM > Purchasing > Puchase Order > Define Document Types
here remove item category |Blank| which means Standard Item category is not allowed for this document type and no user can use document type NB for ordering materials.

Block material for sales order entry in specific plants

Hi Experts,
I wanted to know if there is a simple way to block material from being ordered in a specific plant other than maintaining exclusions. My situation is one sales org, two plants (A & B). Order entry should be blocked at plant A and not B.
I tried using the material Cross-distribution-chain material status on Sales org 1, but this blocks across all plants.
I also tried Plant-Specific Material Status on purchasing view, this blocks the material only if it is being procured (non stock). This does not work for materials that does not require procurement. Setting the material to deletion status in MM06 at the plant level will only give a warning.
Any ideas or suggestions on how to handle this?
Thanks,
Nanda

Lakshmipathi,
Thank you. But I don't want to entirely cut off the plant from the sales org. I just don't want to be able to create sales order for a few materials in a specific plant. Ex. Material A should not be allowed on sales orders in plant X but should be allowed in plant Y, both are assigned to the same sales org 1000.
I did some research and found there is no standard way to handle this in SAP, so I decided to go with a user exit MV45AFZZ. By checking against plant specific status (MARC-MMSTA) and if the value is 'XX' then issue an error message.
Thanks,
Nanda

Block asset for purchase order (TS ME21N)

Hi,
The company where I work need that if an asset is capitalized it will not be able to receive new assigment from the purchase order (by TS ME21N); but this is only for some users, so some specifics users can post a purchase order with an asset which has already values and other users not.
Any idea if it is posible to make something?
thanks
cecilia

Hi,
For this you need to go for user exit in purchase order.
Condition will be like:
IF EKKO-ERNAM = A, THEN SYSTEM SHOULD PASS EKKN-BUKRS, EKKN-ANLN1, AND EKKN-ANLN2 TO TABLE ANLA TO CHECK ANLA-AKTIV = BLANK, IF IT IS NOT BLANK ASSIGN AN ERROR MEESSAGE THERE TO STOP THE USER
A = your preferred user, who is not supposed to create the PO for an asset, which is already capitalised.
Please co ordinate with your ABAP resource for this development.
Hope this might help you
Thanks,
Srinu

Blocking material for sales order

hi all,
I have blocked a material from basic data 1 view of X-plant material status and Cost estimate 1 view of Plant Specific Material by changing them to 02. but for this material i can still create sales orders or quotations in that case i want system to give an error message. how can i resolve this problem.
best regards

Hi,
Use the material exclusion function:
FUNCTIONALITY:
SD> Master data > Products > Listing/Exclusion> Create
( Tcodes VBO1, VB02, VB03)
Enter the list/exclusion type B001: For the required
customer:
Enter Maintain materials > Save > Exit
Create the order and enter material excluded to test exclusion.
CONFIGURATION: IMG SETTINGS
For IMG settings; Go to IMG > SD > Basic Functions>Listing/Exclusion
Ensure that the listing/exclusion procedure is activated for your order type. You can also create your own condition types access sequences and procedures or use the SAP provided ones.
Reward points
Regards
Govind.

Goods-Receipt Block for Purchase Order depending on Goods-Receipt Date

Hi,
I want to set up the system so it can block the Goods-Receipt for Purchase Order respectively Scheduling Agreement if the Goods Receipt is about to take place 30 days or more before the Desired Delivery Date.
For Example: If I have a Purchase Order with the desired delivery date 30.09.2008. I want to set up the system so, that it bans (forbids) the Goods Receipt before the 01.09.2008.
If possible I would want to do that without additional programming. Is it possible to set up the system using only customising settings?
Thanks for your help
Bogdan

Hello Marius-Bodgan,
as this question is marked answered I assume you have received an solution for your requirement. Could you please share the solution with me by posting it here? I have the same requirement and did not find any possibility to do this in customizing.
Thanks in advance,
Emanuel
Found the solution in thread Re: Goods Receipt
Edited by: Emanuel Penalver on Jul 15, 2008 11:48 AM

Restrict print out of Purchase order only for Production system

Hi,
I want to restrict print out of Purchase order only for Production system, don't want to take it in devep or quality.
is there any identifier to find the system is production or development.
can anyone tell me how to restrict it,
is there any function module, not based on client system.
Thanx in advance
Kesav

Hi Kesavarathinam Vaidyalingam ,
yes, I also use thomas' suggestion using
t000-cccategory = 'P'.
to determine productive client.
Just one small hint: I found this condition as true in a test system: The admin had done a system copy to create a fresh test client - but forgot (or did not see a good reason) to change t000-cccategory = 'P. to t000-cccategory = 'T'.
Regards,
Clemens

User Exits for Purchase order & requistion to control Material description

Dear Experts,
I am creating a Purchasing requisition & Purchase order for certain Material Type. Currently user can change material description at item level without anu check. Now I have different material type like PACKING(ZPAC), Raw material(ZROH) Etc.
My requirement is like such that i want to allow change of material description of packing material(ZPAC) but system should not allow for Raw material type(ZROH). so from where i can control this?
Can any one give me EXIT name or enhancement point for Purchase order & requisition.
Thanks in advance.
Regards,
Piyush

Dear,
You can achieve this by Field selection in SPRO > MM > Purchasing > Purchase Requisition > Define Document Types > Here get the Field Selection Key for PR Doc Type
SPRO > MM > Purchasing > Purchase Requisition > Define Screen Layout at Document Level > Here for that Field Selection Key, for Selection group "Basic data, item", make field "Short text" as display.
Similarly do for PO also SPRO > MM > Purchasing > Purchase Order > Define Document Types > Here get the Field Selection Key for PO Doc Type
SPRO > MM > Purchasing > Purchase Order > Define Screen Layout at Document Level > Here for that Field Selection Key, for Selection group "Basic data, item", make field "Short text" as display.
Note: - But in case of text Purchases, you need to create a new PR and PO Document Type. So that this config. will not have any impact on Text Purchases.
Regards,
R.Brahmankar

PS - Set Commitment only for Purchase order

Hi experts,
I would like to know if its possible set in the Customizing, the Commitment just for Purchase Order.
Because, currently we have fixed Purchase Requisition and Purchase Order.
Thanks in advance.
Nacho

Hi,
SAP Note:955107 addresses this problem. You may refer the note, but for easy reference, relevant portios of the note are quoted below:
Quote begins:
Symptom
The purchase requisition commitment should not be taken into account in the availability control.
How can this be achieved?
Reason and Prerequisites
This is a customer request.
It should be possible to enter purchase requisitions with any amount and only the resulting purchase orders should be checked by an availability control.
Solution
For Releases 4.6C, 4.70, 5.00 and 6.00 first implement the corrections from Note 955106 if you have not already done this.
Afterwards proceed as follows.
1. Create a utility program ZBPFCI21 of the 'Subroutine Pool' type. For the source code of the program refer to the attached correction instruction 488705.
              Caution: Do not use a different name than ZBPFCI21.
2. Adjust the source code within the utility program ZBPFCI21 as follows:
              When the residual order plan should not be included in the assigned value of the availability control, activate the line
                       CLEAR cd_flag_pr_commitment_avac.
              (That is, delete the sign '*' in front of the line.)
3. Save and activate the ZBPFCI21 utility program.
4. Reconstruct the assigned values of the availability control (Transactions KO31 for orders or CJBN for projects).
Quote ends.
Kindly acknowledge, if it meets your requirement.
Muraleedharan.R

Getting errors when iam using BAPI_PO_CREATE1 for Purchase Order creation

Hi sap Gurus,
I am getting Errors when iam using BAPI_PO_CREATE1 for Purchase Order creation that Material (144) does not exist but it is alreardy maintained in MM01.
I dont get how it is coming.and what are the mandatory fields in bapi BAPI_PO_CREATE1 in item level .that is too material only.
pls let me know .
thanks in advance.

Hi,
Check the sample code..
report zpo_test             .
*DATA DECLARATION
constants : c_x value 'X'.
*Structures to hold PO header data
data : header like bapimepoheader ,
headerx like bapimepoheaderx .
*Structures to hold PO account data
data : account like bapimepoaccount occurs 0 with header line ,
accountx like bapimepoaccountx occurs 0 with header line .
*Internal Tables to hold PO ITEM DATA
data : item like bapimepoitem occurs 0 with header line,
itemx like bapimepoitemx occurs 0 with header line,
*Internal table to hold messages from BAPI call
return like bapiret2 occurs 0 with header line,
*Internal table to hold messages from BAPI call
pocontractlimits like bapiesucc occurs 0 with header line.
data : w_header(40) value 'PO Header',
purchaseorder like bapimepoheader-po_number,
delivery_date like bapimeposchedule-delivery_date.
data : ws_langu like sy-langu.
*text-001 = 'PO Header' - define as text element
selection-screen begin of block b1 with frame title text-001.
parameters : company like header-comp_code default '122' ,
doctyp like header-doc_type default 'NB' ,
cdate like header-creat_date default sy-datum ,
vendor like header-vendor default '2000000012' ,
pur_org like header-purch_org default 'PU01' ,
pur_grp like header-pur_group default '005' .
*sociedad like HEADER-COMP_CODE default '122' ,
*vendedor like HEADER-SALES_PERS default 'sale person'.
selection-screen end of block b1.
selection-screen begin of block b2 with frame title text-002.
parameters : item_num like item-po_item default '00010',
material like item-material default '12000000' ,
tipo_imp like item-acctasscat default 'K' ,
*pos_doc like ITEM-ITEM_CAT default 'F' ,
shorttxt like item-short_text default 'PRUEBA BAPI' ,
grup_art like item-matl_group default '817230000' ,
plant like item-plant default '3001' ,
mpe like item-trackingno default '9999' ,
*contrato like ITEM-AGREEMENT default '4904000003' ,
*quantity like ITEM-QUANTITY default 1 .
po_unit like item-po_unit default 'EA'.
selection-screen end of block b2.
Par?mnetros de imputaci?n
selection-screen begin of block b3 with frame title text-004.
parameters : centro like account-costcenter default '1220813150',
cuenta like account-gl_account default '6631400' ,
num_pos like account-po_item default '10' ,
serial like account-serial_no default '01' ,
ind_imp like account-tax_code default 'I2' .
selection-screen end of block b3.
start-of-selection.
*DATA POPULATION
ws_langu = sy-langu. "Language variable
*POPULATE HEADER DATA FOR PO
*HEADER-COMP_CODE = sociedad .
header-doc_type = doctyp .
header-vendor = vendor .
header-creat_date = cdate .
header-created_by = 'TD17191' .
header-purch_org = pur_org .
header-pur_group = pur_grp .
header-comp_code = company .
header-langu = ws_langu .
*HEADER-SALES_PERS = vendedor .
*HEADER-CURRENCY = 'DOP' .
*HEADER-ITEM_INTVL = 10 .
*HEADER-PMNTTRMS = 'N30' .
*HEADER-EXCH_RATE = 1 .
*POPULATE HEADER FLAG.
headerx-comp_code = c_x.
headerx-doc_type = c_x.
headerx-vendor = c_x.
headerx-creat_date = c_x.
headerx-created_by = c_x.
headerx-purch_org = c_x.
headerx-pur_group = c_x.
headerx-langu = c_x.
*HEADERX-sales_pers = c_x.
*HEADERX-CURRENCY = c_x.
*HEADER-ITEM_INTVL = c_x.
*HEADER-PMNTTRMS = c_x.
*HEADER-EXCH_RATE = c_x.
*HEADER-EXCH_RATE = c_x.
*POPULATE ITEM DATA.
item-po_item = item_num.
item-quantity = '1'.
*ITEM-MATERIAL = material .
item-short_text = 'prueba bapi_po_create1'.
*ITEM-TAX_CODE = ''.
item-acctasscat = 'K' .
*ITEM-ITEM_CAT = 'D' .
item-matl_group = '817230000' .
item-plant = '3001' .
item-trackingno = '99999'.
item-preq_name = 'test'.
*ITEM-AGREEMENT = '' .
*ITEM-AGMT_ITEM = ''.
item-quantity = '1' .
item-po_unit = 'EA'.
*ITEM-ORDERPR_UN = 'EA'.
item-conv_num1 = '1'.
item-conv_den1 = '1'.
item-net_price = '1000000' .
item-price_unit = '1'.
item-gr_pr_time = '0'.
item-prnt_price = 'X'.
item-unlimited_dlv = 'X'.
item-gr_ind = 'X' .
item-ir_ind = 'X' .
item-gr_basediv = 'X'.
*ITEM-PCKG_NO = '' .
append item. clear item.
*POPULATE ITEM FLAG TABLE
itemx-po_item = item_num.
itemx-po_itemx = c_x.
*ITEMX-MATERIAL = C_X.
itemx-short_text = c_x.
itemx-quantity = c_x.
*ITEMX-TAX_CODE = C_X.
itemx-acctasscat = c_x.
*ITEMX-ITEM_CAT = c_x.
itemx-matl_group = c_x.
itemx-plant = c_x.
itemx-trackingno = c_x.
itemx-preq_name = c_x.
*ITEMX-AGREEMENT = C_X.
*ITEMX-AGMT_ITEM = c_x.
itemx-stge_loc = c_x.
itemx-quantity = c_x.
itemx-po_unit = c_x.
*ITEMX-ORDERPR_UN = C_X.
itemx-conv_num1 = c_x.
itemx-conv_den1 = c_x.
itemx-net_price = c_x.
itemx-price_unit = c_x.
itemx-gr_pr_time = c_x.
itemx-prnt_price = c_x.
itemx-unlimited_dlv = c_x.
itemx-gr_ind = c_x .
itemx-ir_ind = c_x .
itemx-gr_basediv = c_x .
append itemx. clear itemx.
*POPULATE ACCOUNT DATA.
account-po_item = item_num.
account-serial_no = serial .
account-creat_date = sy-datum .
account-costcenter = centro .
account-gl_account = cuenta .
account-gr_rcpt = 'tester'.
append account. clear account.
*POPULATE ACCOUNT FLAG TABLE.
accountx-po_item = item_num .
accountx-po_itemx = c_x .
accountx-serial_no = serial .
accountx-serial_nox = c_x .
accountx-creat_date = c_x .
accountx-costcenter = c_x .
accountx-gl_account = c_x .
account-gr_rcpt = c_x.
append accountx. clear accountx.
*BAPI CALL
call function 'DIALOG_SET_NO_DIALOG'.
call function 'BAPI_PO_CREATE1'
    exporting
      poheader         = header
      poheaderx        = headerx
    importing
      exppurchaseorder = purchaseorder
    tables
      return           = return
      poitem           = item
      poitemx          = itemx
      poaccount        = account
      poaccountx       = accountx.
*Confirm the document creation by calling database COMMIT
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'
IMPORTING
RETURN =
end-of-selection.
*Output the messages returned from BAPI call
loop at return.
    write / return-message.
endloop.
Regards
Sudheer

Open items for purchase order its very urgent

hi
my requirement is to write extract program for purchase order(me21) to extract only open items.
please provide sample code its very urgent.
thanks in advance.
points will be rewarded.
thanks
hari prasad reddy

check the below report :
REPORT ZMM_OPEN_PO_REPORT no standard page heading
                          line-size 255
                          message-id zwave.
======================================================================
Program Name : ZMM_OPEN_PO_REPORT                                    *
Description : This report displays all Open PO Items and output     *
               would be PO Number,Material number and so on          *
Author       : Seshu                                                 *
Date         : 01/24/2007                                            *
MODIFICATION HISTORY                                                 *
DATE    | AUTHOR   | CHANGE #   | DESCRIPTION OF MODIFICATION        *
--|||--
01/24/07| Seshu    | DEVK921979 | Initial                            *
D A T A D E C L A R A T I O N   P A R T                         ***
type-pools
type-pools : slis.
Tables
tables : ekko, " Purchase order Header
         ekpo, " Purchase order Item
         marc. " Material with Plant data
Internal table for output.
data : begin of i_output occurs 0,
       ebeln like ekko-ebeln,
       matnr like ekpo-matnr,
       end of i_output.
ALV Data declaration.
data : v_repid like sy-repid.
ALV Function Module Variables
DATA: gs_layout type slis_layout_alv,
      g_exit_caused_by_caller,
      gs_exit_caused_by_user type slis_exit_by_user.
DATA: gt_fieldcat    type slis_t_fieldcat_alv,
      gs_print       type slis_print_alv,
      gt_events      type slis_t_event,
      gt_list_top_of_page type slis_t_listheader,
      g_status_set   type slis_formname value 'PF_STATUS_SET',
      g_user_command type slis_formname value 'USER_COMMAND',
      g_top_of_page type slis_formname value 'TOP_OF_PAGE',
      g_top_of_list type slis_formname value 'TOP_OF_LIST',
      g_end_of_list type slis_formname value 'END_OF_LIST',
      g_variant LIKE disvariant,
      g_save(1) TYPE c,
      g_tabname_header TYPE slis_tabname,
      g_tabname_item   TYPE slis_tabname,
      g_exit(1) TYPE c,
      gx_variant LIKE disvariant.
data : gr_layout_bck type slis_layout_alv.
Ranges
ranges r_eindt for eket-eindt.
initialization.
v_repid = sy-repid.
start-of-selection.
Get the data from EKKO ,EKPO and MARC Table
perform get_data_tables.
end-of-selection.
display the data in the form of ALV
perform display_data.
*&      Form get_data_tables
      Get the data from EKKO,EKPO and MARC Table
FORM get_data_tables.
clear : i_output.
refresh : i_output.
fill the dates in ranges
r_eindt-low = sy-datum - 7.
r_eindt-high = sy-datum + 14.
r_eindt-option = 'BT'.
r_eindt-sign = 'I'.
append r_eindt.
Get the data from EKKO,EKPO and EKET Tables
select aebeln bmatnr into table i_output
                       from ekko as a inner join
                            ekpo as b on aebeln = bebeln
                            inner join marc as c on cmatnr = bmatnr
                            inner join mara as d on dmatnr = bmatnr
                            inner join eket as e on eebeln = aebeln
                                           and   eebelp = bebelp
                            where c~beskz = 'E'
                            and   c~werks = '1000'
                            and   d~mtart = 'FERT'
                            and   b~loekz = space
                            and   b~elikz = space
                            and   e~eindt in r_eindt.
if sy-subrc ne 0.
message e000(zwave) with 'No open purchase order found'.
endif.
ENDFORM.                    " get_data_tables
*&      Form display_data
      text
FORM display_data.
Fill the Fiedlcat
PERFORM fieldcat_init using gt_fieldcat[].
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
   I_INTERFACE_CHECK                 = ' '
   I_BYPASSING_BUFFER                =
   I_BUFFER_ACTIVE                   = ' '
     I_CALLBACK_PROGRAM                = v_repid
   I_CALLBACK_PF_STATUS_SET          = ' '
    I_CALLBACK_USER_COMMAND           = g_user_command
   I_CALLBACK_TOP_OF_PAGE            = ' '
   I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
   I_CALLBACK_HTML_END_OF_LIST       = ' '
   I_STRUCTURE_NAME                  =
   I_BACKGROUND_ID                   = ' '
   I_GRID_TITLE                      =
   I_GRID_SETTINGS                   =
   IS_LAYOUT                         = gr_layout_bck
      IT_FIELDCAT                       = gt_fieldcat[]
   IT_EXCLUDING                      =
   IT_SPECIAL_GROUPS                 =
   IT_SORT                           =
   IT_FILTER                         =
   IS_SEL_HIDE                       =
   I_DEFAULT                         = 'X'
    I_SAVE                            = g_save
    IS_VARIANT                        =
   IT_EVENTS                         =
   IT_EVENT_EXIT                     =
   IS_PRINT                          =
   IS_REPREP_ID                      =
   I_SCREEN_START_COLUMN             = 0
   I_SCREEN_START_LINE               = 0
   I_SCREEN_END_COLUMN               = 0
   I_SCREEN_END_LINE                 = 0
   IT_ALV_GRAPHICS                   =
   IT_ADD_FIELDCAT                   =
   IT_HYPERLINK                      =
   I_HTML_HEIGHT_TOP                 =
   I_HTML_HEIGHT_END                 =
   IT_EXCEPT_QINFO                   =
IMPORTING
   E_EXIT_CAUSED_BY_CALLER           =
   ES_EXIT_CAUSED_BY_USER            =
    TABLES
      T_OUTTAB                          = i_output
   EXCEPTIONS
     PROGRAM_ERROR                     = 1
     OTHERS                            = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " display_data
*&      Form fieldcat_init
      text
     -->P_GT_FIELDCAT[] text
FORM fieldcat_init USING e01_lt_fieldcat type slis_t_fieldcat_alv.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
Purchase order number
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'EBELN'.
LS_FIELDCAT-ref_fieldname = 'EBELN'.
LS_FIELDCAT-ref_tabname = 'EKKO'.
LS_FIELDCAT-TABNAME    = 'I_OUTPUT'.
ls_fieldcat-seltext_L = 'Purchase Order'.
ls_fieldcat-seltext_M = 'Purchase Order'.
ls_fieldcat-seltext_S = 'Purchase Order'.
APPEND LS_FIELDCAT TO E01_LT_FIELDCAT.
Material #
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME    = 'MATNR'.
LS_FIELDCAT-ref_fieldname = 'MATNR'.
LS_FIELDCAT-ref_tabname = 'EKPO'.
LS_FIELDCAT-TABNAME    = 'I_OUTPUT'.
ls_fieldcat-seltext_L = 'Material'.
ls_fieldcat-seltext_M = 'Material'.
ls_fieldcat-seltext_S = 'Material'.
APPEND LS_FIELDCAT TO E01_LT_FIELDCAT.
ENDFORM.                    " fieldcat_init

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
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
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
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
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
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

Version management for Purchase order

Dear Friends,
I am implimenting version management for Purchase orders.
Under version management(IMG) ,set up change dispalys node--
following fields are available.
Ex:
Doc type-- ZCO,NB
For item view fields:
Field nameEMATN(material),TableMEPO1211--material field in Item over view
Field nameMENGE(Quantity),TableMEPO1211
For Header level fields:
Field nameZTERM(payment terms field),,TableMEPO1226
Category--A or B for selection of change documents
No out put--if i tick it concern field will not included in change doc
Version--what is the purpose
Please suggest me
1) we need enter the all the field names in the item over view and item details and Header level fields as given above ,is it correct.
2) And with regard to Table, do i enter for Header level fields-EKKO or MEPO1226 which is available in F1 under techinical information,
for item level fields,shall i enter table name-EKPO or MEPO1211as dispalyed in the F1 under techinical information.
3) I need to enter all the fields existing in the purchase order
4) All these fields and data is to be entered for every document type NB and ZCO.
5) After changes are made in Purchase order,first time on saving the PO,version is creating automatically,
second time,if we do changes, version is not creating on saving the purchase order,what configuration needs to be done.
Please suggest.
Regards,
Magana

Also tell me the use of *Display of change documents in PO*.
It will display changes made both in item & header.It will help you to audit all changes made in p.o after it is raised.
In version management not all changes can be ameneded as seperate versions
only critical changes like price revision,quantity revision.

SMART FORM FOR PURCHASE ORDER

Hii Experts,
I am developing a smart form for purchase order. I am customizing the existing PO smart form according to the clients requirements. The customer needs fields Discount percentage, Excise duty and VAT/CST%... all these fields when i explored in transaction me23n come from a structure so the values come only at run time.. can anyone tell me the exact table and fields from where these comes so that i can retrieve it from there and display it in my smart form. The fields i need are discount percentage, excise duty and VAT/CST%. its urgent.

REPORT ZMR_PURCHASE_ORDER.
types: BEGIN OF ty_lfa1,
          LIFNR TYPE lfa1-LIFNR,
          MCOD1 TYPE lfa1-MCOD1,
          STRAS TYPE lfa1-STRAS,
          MCOD3 TYPE lfa1-mcod3,
      END OF ty_lfa1.
TYPES: BEGIN OF ty_ekpo,
          ebeln TYPE ekpo-ebeln,
          ebelp TYPE ekpo-ebelp,
          txz01 TYPE ekpo-txz01,
          menge TYPE ekpo-menge,
          peinh TYPE ekpo-peinh,
          brtwr TYPE ekpo-brtwr,
      END OF ty_ekpo.
TYPES: BEGIN OF ty_ekko,
        ebeln TYPE ekko-ebeln, "purchase doc
        LIFNR TYPE ekko-LIFNR, "vendor
        MCOD1 TYPE lfa1-MCOD1, "vendor name
        STRAS TYPE lfa1-STRAS, "vendor add
        MCOD3 TYPE lfa1-MCOD3, "vendor city
        bedat TYPE ekko-bedat, "doc date
        unsez TYPE ekko-unsez, "contact person
        verkf TYPE ekko-verkf, "attn
        telf1 TYPE ekko-telf1, "tele
        ihrez TYPE ekko-ihrez, "ref
        KNUMV TYPE ekko-KNUMV, "doc condition
       ebelp TYPE ekpo-ebelp, "item
       txz01 TYPE ekpo-txz01, "message desc
       menge TYPE ekpo-menge, "qty
       peinh TYPE ekpo-peinh, "rate
       brtwr TYPE ekpo-brtwr, "gross
    END OF ty_ekko.
TYPES: BEGIN OF ty_t685t,
        kschl TYPE t685t-KSCHL,
        vtext TYPE t685t-vtext,
      END OF ty_t685t.
TYPES: BEGIN OF ty_line_item,
        KNUMV TYPE konv-KNUMV, "condition number
        STUNR TYPE konv-STUNR, "step
        kposn TYPE konv-kposn, "item
        KSCHL TYPE konv-KSCHL, "condition type
        vtext TYPE t685t-vtext, "condition name
        KAWRT TYPE konv-KAWRT, "base amt
        KRECH TYPE konv-KSCHL, "calculation type
        qty(13) TYPE n,         "qty
        kbetr TYPE konv-kbetr, "condition rate
        kwert TYPE konv-kwert, "condition value
    END OF ty_line_item.
data: wa_ekko TYPE zms_ekko,
      wa_item TYPE zms_konv,
      wa_lfa1 TYPE ty_lfa1,
      wa_t685t TYPE ty_t685t,
      wa_ekpo TYPE ty_ekpo.
data: it_ekko TYPE TABLE OF zms_ekko,
      it_item TYPE TABLE OF zms_konv,
      it_lfa1 type TABLE OF ty_lfa1,
      it_t685t TYPE TABLE OF ty_t685t,
      it_ekpo TYPE TABLE OF ty_ekpo.
SELECTION-SCREEN : BEGIN OF BLOCK ss_block WITH FRAME TITLE text-001.
   PARAMETERS: pa_ver(2) TYPE c DEFAULT '0'.
    SELECT-OPTIONS: pa_pord FOR wa_ekko-ebeln,
                    pa_date for wa_ekko-bedat.
SELECTION-SCREEN : END OF BLOCK ss_block.
SELECT EBELN LIFNR bedat unsez verkf telf1 ihrez knumv from ekko
    into CORRESPONDING FIELDS OF TABLE it_ekko.
if pa_pord is not INITIAL.
    DELETE it_ekko WHERE ebeln not in pa_pord.
endif.
if pa_date is not INITIAL.
    DELETE it_ekko WHERE bedat not IN pa_date.
endif.
if it_ekko is not INITIAL.
SELECT lifnr MCOD1 STRAS MCOD3 from lfa1
    INTO CORRESPONDING FIELDS OF TABLE it_lfa1
    FOR ALL ENTRIES IN it_ekko
    WHERE LIFNR = it_ekko-LIFNR.
SELECT ebeln ebelp txz01 menge peinh brtwr from ekpo
    INTO CORRESPONDING FIELDS OF TABLE it_ekpo
    FOR ALL ENTRIES IN it_ekko
    WHERE EBELN = it_ekko-ebeln.
loop at it_ekko into wa_ekko.
    READ TABLE it_lfa1 into wa_lfa1 WITH KEY lifnr = wa_ekko-LIFNR.
    wa_ekko-MCOD1 = wa_lfa1-MCOD1.
    wa_ekko-stras = wa_lfa1-stras.
    wa_ekko-MCOD3 = wa_lfa1-MCOD3.
    MODIFY it_ekko FROM wa_ekko TRANSPORTING MCOD1 STRAS MCOD3 WHERE ebeln = wa_ekko-ebeln.
ENDLOOP.
SELECT KNUMV STUNR KPOSN KSCHL KRECH kbetr kwert KAWRT from konv
    into CORRESPONDING FIELDS OF TABLE it_item
    FOR ALL ENTRIES IN it_ekko
    WHERE KNUMV = it_ekko-KNUMV.
SELECT kschl vtext from t685t
    INTO CORRESPONDING FIELDS OF TABLE it_t685t
    FOR ALL ENTRIES IN it_item
    WHERE spras = 'EN' and KSCHL = it_item-KSCHL.
LOOP AT it_item into wa_item.
    READ TABLE it_t685t into wa_t685t with key KSCHL = wa_item-KSCHL.
    wa_item-vtext = wa_t685t-vtext.
    if wa_item-kschl = 'ZBP1'.
      wa_item-qty = wa_item-KAWRT / wa_item-kbetr.
    endif.
    if wa_item-KRECH = 'A'.
     wa_item-kbetr = wa_item-kbetr / 10.
    endif.
    if wa_item-kschl = 'NAVS'.
      wa_item-vtext = 'Sales Tax'.
    endif.
    MODIFY it_item from wa_item TRANSPORTING vtext kbetr kschl qty
      WHERE stunr = wa_item-STUNR and
            kposn = wa_item-kposn.
ENDLOOP.
DELETE it_item WHERE kposn = '000000'.
DELETE it_item WHERE kschl <> 'ZBP1' and kschl <> 'ZD01' and kschl <> 'ZE01'
      and kschl <> 'NAVS' and kschl <> 'ZSRV'.
sort it_item by kposn STUNR.
CALL FUNCTION '/1BCDWB/SF00000025'
EXPORTING
    ARCHIVE_INDEX              =
    ARCHIVE_INDEX_TAB          =
    ARCHIVE_PARAMETERS         =
    CONTROL_PARAMETERS         =
    MAIL_APPL_OBJ              =
    MAIL_RECIPIENT             =
    MAIL_SENDER                =
    OUTPUT_OPTIONS             =
    USER_SETTINGS              = 'X'
IMPORTING
    DOCUMENT_OUTPUT_INFO       =
    JOB_OUTPUT_INFO            =
    JOB_OUTPUT_OPTIONS         =
    TABLES
      it_ekko                    = it_ekko
      it_item                    = it_item
EXCEPTIONS
    FORMATTING_ERROR           = 1
    INTERNAL_ERROR             = 2
    SEND_ERROR                 = 3
    USER_CANCELED              = 4
    OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.

Blocking material for Purchase order only

Similar Messages

Maybe you are looking for