Error in ME21N

Hello Everyone,
While Creating PO( i.e, ME21N) and enterying all the data in the required field, before posting, i am clicking on Check icon... I am getting following messages
1. Purchase order item 00010 still contains faulty account assignments
2.System error: field selection for G/L account 70070031 not set up
Pls do suggect
Regards
Deepaak M B

Hi,
If you are using account assignment category "K" in ME21N, then u need to setup the GL account assigned in the PO correctly. You can check in FS00 if all the necessary fields have been maintained for this GL account.
Hope this resolves your issue,
Reg,
SGP

Similar Messages

Express document update error in me21n

Hai
Iam working on 000 client, Iam not able to see my PO in the list.
The error is "document update terminated by the user"
In SM13 ,i have checked the error log and it is showing the cause as
Module name -
>me_create_document
Type----->V1
Status----->Error
Please help me in resolving this error.
Regards
Anu

Hi Anushka..
Did u find the solution for this error ?(Express document update error in me21n) .. while creating PO.
I am having the same issue now.. need ur support @ the earliest.
Thanks in advance.

Error in ME21n 'The date 1,245 is not convertible (pl correct).

While preparing a STO thru T.Code ME21N , system is giving an error 'The date 1,245 is not convertible (pl correct).
Can u pl help us in analysing why the error is coming.
Regards,
Paras

Hi
Enter the date format as per user prifile sysem config.
Check In SU3 T-code deafult tab-date format
Like example MMDDYYYY/DDMMYYYY/YYYYMMDD
Nagaraj K

Error in ME21N : Authorization Object does not match EFB PID

Hello All
In one of our client we are getting the error as "Authorization Object does not match EFB PID" while executing Tcode ME21N. I have checked in User parameters EFB is not maintained but i am not sure if this is the reason for this error. if this is the case then can somebody tell me what value should i enter against EFB in user parameter. i have tried entering X but in Vain.
Also would like to know where one can see EFB parameter value in SPRO.
It is urgent.
regards
Yogesh

Hello Yogesh,
Here is the path:
SPRO --> Material Management > Purchasing > Authorisation Management > Define function authorisations for buyers > function authorisations for buyers
Regards
Arif Mansuri

STO - ERROR IN ME21N - sadhu kishore , ayub .

HI ALL ,
WHILE trying to transfer stock between 2 plants in different copmany codes , in ME21N the system is unable to recognise the IMG config , thou all is fine .
can any one pl guide ?
pl do guide with reg to stock between 2 plants in different copmany codes .
well all is fine with stock transfer between 2 plants in one company code .
Thanks ,
jerry

In the ME21N create screen Click on ALT+F12 (Custom Local Layout) click on Option>Click on Expert in the Controls> flag the check box:
Show Keys in All Dropdown list
& Sort items by Key
Click apply and ok
regards
John

Display item level Error in ME21N

i want to display an Item level message in ME21N.
Currently the messages are been displayed but all the messages are displayed at the header level.
im using an exit for the custom validation which I am doing.
how can we indicate the message for each item at item level.
please help.

Use this badi.
ME_PROCESS_PO_CUST
method PROCESS_ITEM
      CHECK doctype NE 'UB'. "stock transport purchase order no restriction
      lt_accounts = im_item->get_accountings( ).
      LOOP AT lt_accounts INTO st_account.
        l_accounting = st_account-accounting.
        ls_mepoaccounting = l_accounting->get_data( ).
        CHECK ls_mepoaccounting-ps_psp_pnr NE space.
        SELECT SINGLE stufe FROM prps INTO v_stufe
        WHERE pspnr = ls_mepoaccounting-ps_psp_pnr.
        IF sy-subrc EQ 0.
          CHECK v_stufe LE 3.
          CONCATENATE 'WBS Element of Level greater than 3:'
          'IN Item:' ls_mepoaccounting-ebelp INTO l_text.
          mmpur_message_forced 'E' 'ME' '083' l_text ' ' ' ' ' '.
          CALL METHOD im_item->invalidate( ).
        ENDIF.
      ENDLOOP.

STO - ERROR IN ME21N

HI ALL ,
WHILE trying to transfer stock between 2 plants in different copmany codes , in ME21N the system is unable to recognise the IMG config , thou all is fine .
can any one pl guide ?
pl do guide with reg to stock TRANSFER between 2 plants in different copmany codes .
Thanks ,
JERRY

Stock transfer can happen only within same company code.
If the plants belong to different company codes, then you need to do intercompany sales.

PO create error u2018Number range ZB for object not definedu2019

Dear all
I have a error in ME21N to create PO,When I click save button,then occurs a error u2018Number range ZB for object not definedu2019.
I define a PO types:u2019Z506u2019 and assigned to the Number Range u20185Hu2019.The u20185Hu2019 is from 5070000001 to 5079999999 not ext.
The u2018ZBu2019 number range is defined PR,not PO.So I donu2019t know where does define wrong?
Please help me!
Thanks
Sun

Hi
Please check if you have Defined the Number ranges for Document type ZNB in
SPRO-> Materials Management-> Purchasing-> Purchase Requisition-> Define Number Ranges
The reason the error is Coming like that is, in the Customizing of PO Doucment types in
SPRO-> Materials Management-> Purchasing-> Purchase Order-> Define Document Types-> Link purchase requisition - document type
here you have maintained the Link for the PR & The PO.
Thanks & Regards
Kishore

Message No 06076 ordered in full

Hi,
I have defined error message for message no 06076 Materials of requisition & item & alr. ordered in full, But it is only giving error in ME21N and ME22N transaction. For end user enjoy transaction is not allowed.
How can i set error message for the same in ME21 and ME22.
Thanks in advance,

Dear Asish,
Please refer this Post you will get the Idea how this message works
ME21/ME22 - Are there any solution to make error when qty.PO > qty.PR
Edited by: redriver on Dec 12, 2011 8:31 AM

00 671: ABAP/4 processor: ROLLBACK_IN_POSTING

Hi All,
We are facing update termination error in ME21N T-Code.
Details are given below:
Function Module                       ME_CREATE_DOCUMENT
Status                                      Update was terminated
Report                                      LEINUU03
Row                                         33
Error details   Class:     00         Number:    671
00 671: ABAP/4 processor: ROLLBACK_IN_POSTING
Please help..!!!
Regards,
Nitin Sharma

Hi
Try it. Not sure it will help or not? Tcode OMCQ convert the message no 671 to warning and save.
Regards,
Raman

Error while saving a vairant in purchase order- ME21n

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

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

Error message in ME21n / me22n (on save)

Hi Gurus
           I need to raise a error message in ME21n for which I am using ZXM06U44 and EXIT_SAPMM06E_013
I followed this link to help me out... https://forums.sdn.sap.com/click.jspa?searchID=20007769&messageID=6723170
I am getting a information message even though I gave a message of type E. I tired two options:
1.
*    mmpur_message 'E' 'ZV' '013' lv_lifnr lv_bukrs text-t00 text-t01 .
2.
MESSAGE e013(zv).
none of these was able to give a error message..

Use BAdi:ME_PROCESS_PO_CUST
Method:PROCESS_ITEM/PROCESS_HEADER"As per your Requirement.
DATA : re_data TYPE mepoitem.
CALL METHOD im_item->get_data
    RECEIVING
      re_data = re_data.
"Check for account assignment cat only for "A" and "L".
IF re_data-knttp = 'L' OR re_data-knttp = 'A'.
    GET PARAMETER ID 'KNT' FIELD re_data-knttp.
    IF sy-subrc NE 0.
      MESSAGE 'You are not aurthorized to use Account Assignment Category (Logit)L!!' TYPE 'E'.
    ENDIF.
ENDIF.
I got Error Message in Incomplete log.

ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

Dear All Expert,
I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
Please find the below ABAP Runtime Error.
Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
Date and Time          10.02.2011 11:13:07
Short text
     Change of a Dictionary structure at runtime of a program.
What happened?
     Runtime error
     The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
      terminated because one
     of the statements could not be executed at runtime.
What can you do?
     Restart the program.
     If the error persists, contact your SAP administrator.
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
      changed
     during the flow of the transaction.
     As the type was already used in the old version
     and in the new type should be used in the same transaction in the new
      version, the transaction had to be cancelled to avoid inconsistencies.
How to correct the error
    Try to restart the program.
System environment
    SAP-Release 700
    Application server... "iqe"
    Network address...... "172.25.0.85"
    Operating system..... "Linux"
    Release.............. "2.6.9-55.ELsmp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "iqe"
    Database type..... "ORACLE"
    Database name..... "IQE"
    Database user ID.. "SAPSR3"
    Terminal................. "MUMJML5727"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 26 2010 20:17:07"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 285
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 16192
EM...... 25139088
Heap.... 0
Page.... 40960
MM Used. 8038136
MM Free. 4528408
User and Transaction
Client.............. 600
User................ "JKMM"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
Screen.............. " "
Screen line......... " "
Information on where terminated
    The termination occurred during generation of the ABAP/4 program
     "CL_IM_WRF_MM_PROC_PO==========CP".
    The termination occurred in line 213
    of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
     calling the editor 2130).
Source Code Extract
Line SourceCde
183   DATA: l_flag TYPE wrf_pbas_boolean.
184
185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
186     IMPORTING
187       e_preview_flag = l_flag.
188
189   IF NOT l_flag IS INITIAL.
190
191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
192
193     MOVE im_header ?TO l_header.
194
195     CALL METHOD l_header->if_output_mm~preview( ).
196
197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
198
199 ***$ Widening Cast for printing information.
200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
201 **      EXPORTING
202 **        im_header = l_header.
203
204 * Printing Preview
205 * IF NOT gv_preview IS INITIAL.
206 *    CALL METHOD l_header->if_output_mm~overview( ).
207 *    CALL METHOD l_header->if_output_mm~preview( ).
208 * clear gv_preview.
209   ENDIF.
210
211 * ENDIF.
212
>>>>> ENDMETHOD.
Internal notes
    The termination was triggered in function "ab_RxDdicStruShareFailed"
    of the SAP kernel, in line 2539 of the module
     "//bas/700_REL/src/krn/runt/abtypload.c#11".
    The internal operation just processed is " ".
    Internal mode was started at 20110210111306.
    Name of the changed type......: "WRF_POHF_KOMP_STY"
    New version of the type.......: 20070508193207
    Old version of the type.......: 20070508193207
    New user......................: "Type" "WRF_POHF_KOMP_STY"
    Version of the new user.......: 20070508193207
    Old user......................: "???" "???"
    Version of the old user.......: "???"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(CTrcStack2+0x78)[0x6cbb78]
(CTrcStack+0xb)[0x6cc17b]
(ab_rabax+0x3be5)[0xb8d985]
(_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
(_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
(_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
(_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
(ab_GetView+0xc1d)[0xb0ee1d]
(_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
(_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
(_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
(_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
(sc_blkle+0xdd)[0xec6e4d]
(rs_oper_abap1729+0x37)[0x10eb237]
(rs_expan_abap+0xa1996)[0xfd7a2a]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_inclu+0x5fa)[0xe0d50a]
(rs_oper_abap2160+0x3a)[0x1115d6a]
(rs_expan_abap+0xcd41d)[0x10034b1]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_checkStart+0x41)[0xe1ac51]
(cg_generate+0xb65)[0xe57755]
(ab_gabap+0x14a)[0xb01a5a]
(dy_gen_abap+0x63c)[0x74428c]
(ab_genprog+0x13d3)[0xb03d13]
(_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
(_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
(_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
(_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
(_Z11ab_FillCfixtj+0x65)[0x957ae5]
(_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
(_Z8ab_jaboov+0x623)[0x959793]
(_Z8ab_extriv+0x607)[0x8ba9c7]
(_Z9ab_xeventPKt+0x1c1)[0xa1c021]
(_Z8ab_triggv+0x9c)[0xa1c77c]
(ab_run+0x97)[0xbde5c7]
(N_ab_run+0x9)[0x736359]
(dynpmcal+0x669)[0x7333b9]
(dynppai0+0x8eb)[0x734d9b]
(dynprctl+0x3e9)[0x733db9]
(dynpen00+0x4a5)[0x726eb5]
(Thdynpen00+0x359)[0x541bd9]
(TskhLoop+0xc49)[0x54d999]
(ThStart+0x20f)[0x55b29f]
(DpMain+0x2da)[0x4bd49a]
(nlsui_main+0x9)[0x4910c9]
(main+0x33)[0x491103]
/lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
Please help me to resolve the issue.
Thanks & Regards
SKK

read this part again: The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
how often had you restarted ME21N before you posted this message?
In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

Error Calling Data Provider for Return PO in Me21N Message Number FES011

Hi Experts,
I am trying to create a Return PO using ME21N. Im giving all the parameters and values. But While saving its generating an Error.
it states "Error calling Data Provider".
Message No. FES011
What could be the possible error . Any clues?
Thanks and Regards,
Selvakumar. M

hi,
Check with the Basis consultant....actually Data provider deals with the database..Also sometimes when the data provider doesnot provides the data...the error doesn't reach....
Pls check with the BASIS consultant....the netweaver part could be checked by ABAP consultant...
Also check the links:
http://msdn.microsoft.com/en-us/library/bb508810(SQL.90).aspx
http://help.sap.com/saphelp_nwpi71/helpdata/en/11/e8179b247e4720882512a04041491d/frameset.htm
http://sapnetweavernotes.blogspot.com/2008/04/sap-earlywatch-alert.html
Hope it helps....
Regards
Priyanka.P

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

Error in ME21N

Similar Messages

Maybe you are looking for