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

Similar Messages

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

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

Raise purchase order in me21n for 100 goods

HI,
i have problem. i raise purchase order in me21n for 100 goods.for that purchase order in MIGO i received 75 goods.when the invoice verification i found only 50 goods.how to clear in gr/ir in the month end process. please someone help me.
regards
subbarao

Hi
Reverse the MIRO and MIGO documents , and Post the MIGO and MIRO with actual quantity received
Regards
Rams

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

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

How to block articlee for purchases

we are planning to block some of articles for purchases. However we want to allow for stock transfers using stock transfer requests( ME21N-UB doc type).
when i kept 01 Blocked for procment/whse in X-site status of baisc data tab system is not allowing for stock transfer order creation also.
plz suggest how to block articles for purchases without impacting for stock transfers.
what is the usage of follwing selections for blocking
01     Blocked for procment/whse
02     Blocked for task list/BOM
03     Blocked for Purchasing

Hello,
If you want to block articles from procuring into DCs and do not want to block DC to Store movements, you may block articles in site-specific Block status (MARC-MMSTA) in Article/DC view. So DC to Store STOs can be created.
You may see the definitions of various blocking statuses in transaction OMS4. For example, 01 Blocked for procment/whse means blocked from Purchasing,Forecasting and RP (No Message, Warning or Error Message).
Thanks,
Venu

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?

I found a exit CIFPUR02 for purchase order inbound process.is it suitable?
my idoc is PORDCR102 AND message type is PORDCR1. my requirement is this is EXIT should trigger before saving the data in me21n.
Edited by: rk.kolisetty on Jun 24, 2010 4:59 PM

Hi,
Following are the user exit relevant to T Code ME21n.
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
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
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 P
MM06E008 Monitoring of contr. target value in case of release or
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 proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Rgd,
Chetan

Table for purchase order status

Hello friends,
There's a tab STATUS in purchase order (tcoe ME21N).
I can't find a table which contains theses statuses.
Anybody knows what's the table for purchase orders status ??
Regards,
Bahia

Hi
PO status is stored in Structure not in the table.
Please use the List displays to get the information like ME2N,ME2L, ME2M, ME2K etc
You can also get the information from the table EKKO, EKPO, EKET,EKBE
Hope it helps
thanks/karthik

Use of SAVE_TEXT in customer exits / BADI for purchase order

Hi All,
I am trying to save some long text by using SAVE_TEXT function module in a badi implementation for purchase order header text. The same is working fine if i try to update the PO header text via a report. But if i try using badi (the code is written in a PAI event for the BADI), then though the text transfer and save is successful during the code excution, but for the first time when i add any text its not visible in ME22N tcode. Since its an online event. But when i double click on that editor and the sap script editor gets opened. then i press back button, the text is appearing on the same small screen edtor . after this any number of time i edit or delete text, the save_text function module works fine.
My issue is why for the first time always i have to double click on the editor to open the sap script editor. I have also included commit_text in this case after save_text FM.
the requirement here goes like this. in one tab for PO header the user will enter some number (This is a customizing screen implemented through badi.) and the corresponsing discription should appear when user clicks on text tab in po header screen (me21n / me22n).
Kindly help.
Thanks
Mamata

Hi mamata rath
I have solve the problem which similar to yours. the code which is as the following
DATA: textline TYPE tdline,
        name TYPE c LENGTH 70,
        glines TYPE TABLE OF tline,
        gline LIKE LINE OF glines,
        ls_header TYPE thead.
     CONCATENATE ch_eban-banfn ch_eban-bnfpo INTO name.
         ls_header-tdobject = 'EBAN'.
         ls_header-tdname = name.
         ls_header-tdid = 'B01'.
         ls_header-tdspras = sy-langu.
         CALL FUNCTION 'SAVE_TEXT'
           EXPORTING
*           CLIENT                = SY-MANDT
             header                = ls_header
*           INSERT                = ' '
*           SAVEMODE_DIRECT       = ' '
*           OWNER_SPECIFIED       = ' '
*           LOCAL_CAT             = ' '
*         IMPORTING
*           FUNCTION              =
*           NEWHEADER             =
           tables
             lines                 = glines
           EXCEPTIONS
             ID                    = 1
             LANGUAGE              = 2
             NAME                  = 3
             OBJECT                = 4
             OTHERS                = 5
          IF sy-subrc = 0.
              CALL FUNCTION 'COMMIT_TEXT'
                EXPORTING
                  OBJECT                = 'EBAN'
                  NAME                  = name
*                ID                    = '*'
*                LANGUAGE              = '*'
*                SAVEMODE_DIRECT       = ' '
*                KEEP                  = ' '
*                LOCAL_CAT             = ' '
*              IMPORTING
*                COMMIT_COUNT          =
*              TABLES
*                T_OBJECT              =
*                T_NAME                =
*                T_ID                  =
*                T_LANGUAGE            =
          ENDIF.

G/L Account Error While doing Purchase Order In ME21N

Hi,
While Doing Purchase Order in ME21N,i am getting the below error.Kindly help me.
G/L account 809001 cannot be used (please correct)
Message no. ME045
Diagnosis
Comparison of the field selection strings from the G/L account 809001 and the account assignment category F reveals that there is an incompatible combination of field selections for the field selection group 'Network'.
The G/L account field selection is stored in table T004F; that for the account assignment is stored in table T162K.
Procedure
Please enter a correct G/L account.
Thanks
Supriya

Hi Supriya,
U will have to check the field status of account assignment category F in tcode OME9 and compare it with the Field status group that is assigned to GL 809001.
Kindly note that the field status has a prority in the following order.
Supress
Display
Required
Optional
Thus if the network field is suppressed in GL field status and option in account assignment category F, then the below error would come.
Regards,
Kiran

Goods receipt for purchase order is not allowed

Hi,
When I am doing the PO receipt i am facing the error message "Goods receipt for purchase order is not allowed WBS element xxxxxx"
What could be the problem
Thanks
Lucky

Hi,
Please check the WBS element in CJ03, in Basic Data, System status,
Is the WBS is not released or blocked.
Hope it helps you.
Thanks

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

Update was terminated while creating purchase order from ME21N

Hi Experts,
We are getting this dump when try to create purchase order from ME21N;
Our system ECC 6.0 and IS-AFS (Apparel & Footwear Solution) V600 component has installed,
How can we prevent this error,
Regards
Here is the dump and sm21 log,
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Exception              CX_SY_PROGRAM_NOT_FOUND
Date and Time          10.10.2008 10:22:03
Short text
     Program "RMCMS431 " not found.
What happened?
     There are several possibilities:
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCS4" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     or
     Error in the SAP kernel.
     The current ABAP "SAPLMCS4" program had to be terminated because the
     ABAP processor detected an internal system error.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
     caught in
    procedure "TMC2F_FROUT_CALL" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    On account of a branch in the program
    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
    or a transaction call, another ABAP/4 program
    is to be loaded, namely "RMCMS431 ".
    However, program "RMCMS431 " does not exist in the library.
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
       SUBMIT or, when defining a new transaction, a new
       dialog module or a new function module.
    b) Transport error
How to correct the error
    Check the last transports to the R/3 System.
    Are changes currently being made to the program "SAPLMCS4"?
    Has the correct program been entered in table TSTC for Transaction "ME21N "?
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"
    "SAPLMCS4" or "LMCS4F10"
    "TMC2F_FROUT_CALL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "TMC2F_FROUT_CALL" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
sm21 log ;
Transaction Canceled 00 671 ( LOAD_PROGRAM_NOT_FOUND 20081010102203saptest_TET_00 EYUCE 100
Update terminated
> Update key: F39796DD5421F1509233001E0BD601E0
> Update module: MCE_STATISTICS_UPD_V2
Run-time error "LOAD_PROGRAM_NOT_FOUND" occurred

Please follow the oss note 800335
V2 Update terminations in Purchasing transactions after upgrading or installing AFS 5.0 release.
Other terms
AFS, LIS, MIGO, ME22N, OLI3, S433, S431
Reason and Prerequisites
AFS Purchasing infostructure S431 is no longer used. S433 is the valid infostructure for the release AFS 5.0.
Solution
Please do the following.
For customers upgrading to AFS 5.0 only:
> Rebuild Infostructure S433.
- Goto transaction: OLI3 (Statistical Set up of Infostructures)
- Info structure to be compile: S433
- Specify the 'Name of run'.
- Execute.
> Please also follow the instructions given below.
For both Upgrade and Non-upgrade Customers:
> Create the report 'ZDELS431'.
- Transaction: SE38
- Give Program name as ZDELS431.
- Create (F5).
- Title : 'Program to delete S431'.
- Type : 1 (Executable Program).
- Status: T (Test Program).
> Copy the program text from the note and paste in the program.
> Save and activate the program.
> Execute the report for all clients in Update mode.
(Two check-boxes will appear: P_ALL_CL, P_UPDATE.
   Please check both of them).
This report will delete all the references to infostructure S431.

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_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
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
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 P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

Block asset for purchase order (TS ME21N)

Similar Messages

Maybe you are looking for