Error "EXPORT_INCONSISTENT_STRUCTURE" IN PR (ME52N)

Hello Friends,
I am getting runtime error EXPORT_INCONSISTENT_STRUCTURE while saving Purchase requisition(PR). Below is the details displayed in runtime time error description.
short text:
INTERNAL ERROR:INVALID STRUCTURE DESCRIPTION
ERROR ANALYSIS:
when exporting the error description, the structure components overlapped. the error occured in description of object 'XEBKN'.
USER AND TRANSACTION:
TRANSACTION: ME52n
program: "saplmereq"
screen: "saplmegui 0014"
What should I do correct this error.
Please help.

Hello,
the reason why this inconsistency happens should be that some change were made to the dictionary object by means of transport request or support package application or manual correction and there were error during the activation. So a program tries to reference this inconsistent objects, hence the dump.
in your description i see that there is an invalid structure description for XEBKN used.
Please check this object in transaction SE11 and also runtime and database object for this and try to activating this.
Regards,
Mauro

Similar Messages

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.

ME52n - Error Message - Company was not supplied in function module.

Hello,
It is giving error Message - "Company was not supplied in function module" in the initial screen of ME52n and ME53n.
Please help.
Thanks,
Piyush

Hi Vadi,
when ever you open me52n or me53n ..system by default opnes/shows your last created/ opned PR.
so if that last created / changed PR is having wrong/faulty data (missing assignment/ plat stolocation deleted etc) ..system will not be able to fetch respective data....thats why you will get above eror message...
Solution : Create any smaple PR in ME51n/ or try to chnage any existing PR.. and then save it.
try this 1 or 2 times.
Hope so this will help.
Regards,
Nilesh

Error while creating a Purchase Requisition T Code ME52N

Dear Freinds,
The users are trying to create the Purchase Requisition, however the system gives the error message that the GL Account xxxxxx cannot be used, as the comparison of the field selection strings are not comparable with the Account Assignment Category E. Message no. is ME045. How could we resolve this?
Thanks for the help.
Regards

Dear,
check the FSG for the GL Account 200010 and go to TCcode OBC4 and check the status of field 'Asset number / subnumber' and then go to TCode OME9 and select A and check the field status for field 'Asset number / subnumber'. Status at both areas are different hence system is not accpting. Make status identical.
Regards,
Sandip

Modify Standard Error in ME51N / ME52N

Dear All Gurus,
This is my reuirement. In ME51n when user selects RV Document (Outline Agreement Requisiton - EBAN-BSART = 'RV') .
In SAP metrial number is compulsory.
I need to change this option as non - compulsory filed (avoid error message) .
How do I do this ?
Thank you in advance

Dear Vishnu Tallapra...
Thank you for the reply....
Can you explain more about this confiduration. Great Help..
Is there any other way to resolve this ?
Thanks

Third party process - error

Dear all,
In the third party process, have we to create outbound delivery?
I have created PO from PR of a third party sales order. And now, i don't understand to delivery to customer.
Pls tell me solution.
If we have to create outbound delivery from that sales order, i get errors:
Item category TAS is not defined and Item category TAS is not defined, so item 000010 will be disregarded. I also checked in VOV4, VOV6, VOV7.
Thank you,

Hi
In third party scenario the material is delivered to your customer thro out side vendor
You are billing your customer
Vendor is billing you for the material he has delivered to your customer
Here we dont make any delivery
Process Flow for 3rd Party Sales
Customize the third party sales in summary:
1. Create Vendor XK01
2. Create Material u2013 Material Type as "Trading Goods". Item category group as "BANS".
3. Assign Item Category TAS to Order type that you are going to use.
4. A sale order is created and when saved a PR is generated at the background
5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
7. Goods receipt MIGO
8. Goods issue
9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the configuration and,   therefore, there is no delivery process attached in the whole process of Third party sales.
10. Billing
SD - 3rd party sales order Create Sales Order
VA01
      Order Type
      Sales org, distribution channel, div
      Enter
      Sold to
      PO #
      Material
      Quantity
      Enter
      Save
SD - 3rd party sales order View the PR that is created with a third party sales order
VA01
      Order Number
      Go to Item Overview
      Item ->Schedule Item
SD - 3rd party sales order View the PR that is created
ME52N
      Key in the PR number
      Save
SD - 3rd party sales order Assign the PR to the vendor and create PO
ME57
      Key in the PR number
      Toggle the "Assigned Purchase Requisition"
      Execute
      Check the box next to the material
      Assign Automatically button
      Click on "Assignments" button
      Click on "Process assignment"
      The "Process Assignment Create PO" box , enter
      Drag the PR and drop in the shopping basket
      Save
SD - 3rd party sales order Receive Goods
MIGO_GR
      PO Number
      DN Number
      Batch tab , click on classification
      Serial Numbers tab
      Date of Production
      Flag Item OK
      Check, just in case
      Post
      Save
SD - 3rd party sales order Create Invoice
MIRO
      Invoice Date
      Look for the PO , state the vendor and the Material
      Check the box
      Click on "Copy"
      Purchase Order Number (bottom half of the screen)
      Amount
      State the baseline date
      Simulate & Post
      Invoice Number
      *Invoice blocked due to date variance
SD - 3rd party sales order Create a delivery order
VL01N
      In the order screen , go to the menu Sales Document , select "Deliver"
      Go to "picking" tab
      State the qty and save
SD - 3rd party sales order Create a billing document
VF01
      Ensure that the delivery document is correct in the
      Enter
      Go to edit -> Log
      Save
Hope the process is very clear to you now
Regards
Raja
Edited by: ramanathan raja on Sep 18, 2008 3:06 PM

Runtime error CONNE_IMPORT_CONVERSION_ERROR in MM module

Hi all,
When we call the selection variants in the document overview in
Transactions ME21N, ME22N, ME33N, ME51N, ME52N, ME53N, ME54N, the
CONNE_IMPORT_CONVERSION_ERROR runtime error occurs.
Runtime Errors         CONNE_IMPORT_CONVERSION_ERROR
Date and Time          28.05.2007 12:38:35
ShrtText
Error in IMPORT statement: Change of length on conversion.
What happened?
Error in ABAP application program.
The current ABAP program "AQZZ/SAPQUERY/MEMEPO==========" had to be terminated
because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
When importing an object, it became apparent that one or more characters
would not be converted, or that conversion would result in a length
change. If you add the IGNORING CONVERSION ERRORS addition, the program
will not terminate, even though the object contains characters that
cannot be converted.
How to correct the error
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONNE_IMPORT_CONVERSION_ERROR" C
"AQZZ/SAPQUERY/MEMEPO==========" or " "
"%_IMPORT_VARI_CLNT"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "saptharishi"
Network address.......... "192.168.7.5"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "SAPTHARISHI"
Database type............ "MSSQL"
Database name............ "SPS"
Database owner........... "sps"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Jul 4 2005 23:49:14"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "80"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 15678480
Heap..................... 0
Page..................... 32768
MM Used.................. 12392440
MM Free.................. 1192832
SAP Release.............. "640"
User and Transaction
Client.............. 100
User................ "BASIS"
Language key........ "E"
Transaction......... "ME21N "
Program............. "AQZZ/SAPQUERY/MEMEPO=========="
Screen.............. "SAPLMEGUI 0014"
Screen line......... 22
Information on where terminated
The termination occurred in the ABAP program "AQZZ/SAPQUERY/MEMEPO=========="
in "%_IMPORT_VARI_CLNT".
The main program was "RM_MEPO_GUI ".
The termination occurred in line 0 of the source code of the (Include)
program " "
of the source code of program " " (when calling the editor 00).
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
NORMAL
SY-UCOMM
SY-TITLE
Create Purchase Order
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
22 FORM         AQZZ/SAPQUERY/MEMEPO==========      ???                                     0
%_IMPORT_VARI_CLNT
21 FORM         RSDBSPVA                            RSDBSPVA                              497
CHECKVARI
20 FORM         RSDBSPVD                            RSDBSPVD                              196
IMPORT_VARIANT_STATIC
19 FORM         SAPLALDB                            LALDBFXX                               57
CHECK_VARIANT_UP_TO_DATE
18 FUNCTION     SAPLALDB                            LALDBU03                              119
SUBMIT_REPORT
17 FORM         SAPLAQRC                            LAQRCF01                              253
QUERY_CALL
16 FUNCTION     SAPLAQRC                            LAQRCU10                               69
RSAQ_QUERY_CALL
15 METHOD       CL_ABAP_QUERY_MM==============CP    CL_ABAP_QUERY_MM==============CM00A    61
CL_ABAP_QUERY_MM=>IF_READER_MM~READ_TABLE
14 METHOD       SAPLMEQUERY                         LMEQUERYCI1                           431
LCL_SAP_SQL_SEL=>IF_READER_MM~READ_TABLE
13 METHOD       CL_TABLE_MODEL_MM=============CP    CL_TABLE_MODEL_MM=============CM00A    13
CL_TABLE_MODEL_MM=>READ
12 METHOD       CL_QUERY_CONTROLLER_MM========CP    CL_QUERY_CONTROLLER_MM========CM002    18
CL_QUERY_CONTROLLER_MM=>NEW
11 METHOD       CL_QUERY_CONTROLLER_MM========CP    CL_QUERY_CONTROLLER_MM========CM008    23
CL_QUERY_CONTROLLER_MM=>EXECUTE
10 METHOD       CL_SCREEN_VIEW_MM=============CP    CL_SCREEN_VIEW_MM=============CM003     9
CL_SCREEN_VIEW_MM=>EXECUTE
9 METHOD       CL_MODEL_VIEW_MM==============CP    CL_MODEL_VIEW_MM==============CM00O     3
CL_MODEL_VIEW_MM=>EXECUTE
8 METHOD       CL_TABLE_MODEL_TREE_VIEW_MM===CP    CL_TABLE_MODEL_TREE_VIEW_MM===CM00I     3
CL_TABLE_MODEL_TREE_VIEW_MM=>EXECUTE
7 METHOD       CL_COMPOSITE_SCREEN_VIEW_MM===CP    CL_COMPOSITE_SCREEN_VIEW_MM===CM008    10
CL_COMPOSITE_SCREEN_VIEW_MM=>EXECUTE
6 METHOD       CL_WINDOW_MM==================CP    CL_WINDOW_MM==================CM005    21
CL_WINDOW_MM=>HANDLE_EVENT
5 MODULE (PAI) SAPLMEGUI                           LMEVIEWSF01                           286
FCODE_EXIT
4 FORM         SAPLMEGUI                           LMEVIEWSF01                            21
CALL_SCREEN
3 METHOD       CL_WINDOW_MM==================CP    CL_WINDOW_MM==================CM004    17
CL_WINDOW_MM=>SEND
2 FUNCTION     SAPLMEGUI                           LMEGUIU04                             270
MEGUI_MAINTAIN
1 EVENT        RM_MEPO_GUI                         RM_MEPO_GUI                            24
START-OF-SELECTION
Chosen variables
Name
Val.
No.      22 Ty.          FORM
Name %_IMPORT_VARI_CLNT
SP$00016[]
Table[initial]
SP$00019[]
Table[initial]
SP$00018[]
Table[initial]
SP$00024[]
Table[initial]
SP$00027[]
Table[initial]
SP$00021[]
Table[initial]
SP$00022[]
Table[initial]
SP$00023[]
Table[initial]
S_MATNR[]
Table[initial]
S_WAERS
22222
00000
00000
00000
SO_VDAT1[]
Table[initial]
SO_VDAT2[]
Table[initial]
SO_LIFNR[]
Table[initial]
%G00-EKKO-FRGZU
22222222
00000000
00000000
00000000
P_QCOUNT
000000
333333
000000
000000
000000
S_NETTO1
0.0.0.0.0.0.1.
0000000
000000C
S_NETTO2
0.0.0.0.0.0.1.
0000000
000000C
S_NETTO3
0.0.0.0.0.0.1.
0000000
000000C
S_NETTO4
0.0.0.0.0.0.1.
0000000
000000C
PA_RWEIT
00000000
33333333
00000000
00000000
00000000
PA_GULDT
00000000
33333333
00000000
00000000
00000000
%_P_CLNT
000
333
000
000
000
%CALLED_BY_WWW
2
0
0
0
%_DUMMY$$
2222
0000
0000
0000
%_P_RKEY
AQZZ/SAPQUERY/MEMEPO==========          SAP&MEPOBEST
455525455545524444543333333333222222222254524454445522
11AAF31015529FD5D50FDDDDDDDDDD00000000003106D50F253400
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
No.      21 Ty.          FORM
Name CHECKVARI
BIT_SSCR_F2_HRHI
4
0000
4000
P_RKEY-VARIANT+0(8)
SAP&
5452
3106
0000
0000
SYST-REPID
RSDBSPVA
5544555422222222222222222222222222222222
2342306100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
VARISCREENS[]
Table[initial]
SPACE
2
0
0
0
VSCR_T
Table[initial]
P_RKEY-REPORT
AQZZ/SAPQUERY/MEMEPO==========
4555254555455244445433333333332222222222
11AAF31015529FD5D50FDDDDDDDDDD0000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
P_RKEY
AQZZ/SAPQUERY/MEMEPO==========          SAP&MEPOBEST
455525455545524444543333333333222222222254524454445522
11AAF31015529FD5D50FDDDDDDDDDD00000000003106D50F253400
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
SY
######X###############################Ǭ#########(#################################(###䵘# C####
00000050000010000000000000000000000000E0000000002000000000000000000000000000109000200050240000
000010800000E0000000100010001000000000C0000000008000000000000000000000000000B00000800080030100
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000
00000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000000C
L_SUBRC
0
0000
0000
L_MANDT
000
333
000
000
000
SY-REPID
RSDBSPVA
5544555422222222222222222222222222222222
2342306100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No.      20 Ty.          FORM
Name IMPORT_VARIANT_STATIC
SCREEN
MEPO1211-RESLO
4454333325454422222222222222222222222222222222222222222222222222222222222222222222222222222222
D50F1211D253CF00000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-TFILL
88
5000
8000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_PRINT
000                                                                                0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
P_VARIDYN
Table[initial]
SYST-REPID
RSDBSPVD
5544555422222222222222222222222222222222
2342306400000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
P_VARI
Table IT_1795[42x372]
FUNCTION-POOL=ALDBFORM=CHECK_VARIANT_UP_TO_DATEDATA=L_VARI
Table reference: 603
TABH+ 0(20) = F05A553D00000000000000005B02000003070000
TABH+ 20(20) = 2A00000074010000FFFFFFFF0494020080120000
TABH+ 40( 8) = 14000000C9108000
store        = 0xF05A553D
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 603   (0x5B020000)
label        = 1795 (0x03070000)
fill         = 42    (0x2A000000)
leng         = 372   (0x74010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000085
occu         = 20    (0x14000000)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xB09B7F3D
pghook       = 0xE022E13C
idxPtr       = 0x18BD353D
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 52    (0x34000000)
lineAlloc    = 52    (0x34000000)
store_id     = 1192 (0xA8040000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
P_SSCR
Table IT_1793[88x492]
FUNCTION-POOL=ALDBFORM=CHECK_VARIANT_UP_TO_DATEDATA=L_SSCR
Table reference: 600
TABH+ 0(20) = 5023E13C00000000000000005802000001070000
TABH+ 20(20) = 58000000EC010000FFFFFFFF04930200E04B0000
TABH+ 40( 8) = 20000000C9108000
store        = 0x5023E13C
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 600   (0x58020000)
label        = 1793 (0x01070000)
fill         = 88    (0x58000000)
leng         = 492   (0xEC010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000391
occu         = 32    (0x20000000)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xF0D5543D
pghook       = 0xB022E13C
idxPtr       = 0x487A813D
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 128   (0x80000000)
lineAlloc    = 96    (0x60000000)
store_id     = 1190 (0xA6040000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
P_RKEY
AQZZ/SAPQUERY/MEMEPO==========          SAP&MEPOBEST
455525455545524444543333333333222222222254524454445522
11AAF31015529FD5D50FDDDDDDDDDD00000000003106D50F253400
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
P_SUBRC
4
0000
4000
%_SPACE
2
0
0
0
SY-REPID
RSDBSPVD
5544555422222222222222222222222222222222
2342306400000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No.      19 Ty.          FORM
Name CHECK_VARIANT_UP_TO_DATE
%_SPACE
2
0
0
0
L_SSCR
Table IT_1793[88x492]
P_REPORT
AQZZ/SAPQUERY/MEMEPO==========
4555254555455244445433333333332222222222
11AAF31015529FD5D50FDDDDDDDDDD0000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
P_SUBRC
4
0000
4000
VUV_INFO
222222222222222222222
000000000000000000000
000000000000000000000
000000000000000000000
OPTION_NE_NUM
9
0000
9000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
L_VARI
Table IT_1795[42x372]
L_VARIVDAT
Table[initial]
L_VARIDYN
Table[initial]
L_VDATDYN
Table[initial]
L_RKEY
AQZZ/SAPQUERY/MEMEPO==========          SAP&MEPOBEST
455525455545524444543333333333222222222254524454445522
11AAF31015529FD5D50FDDDDDDDDDD00000000003106D50F253400
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLALDB
5454444422222222222222222222222222222222
310C1C4200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No.      18 Ty.          FUNCTION
Name SUBMIT_REPORT
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
SY-REPID
SAPLALDB
5454444422222222222222222222222222222222
310C1C4200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-MSGID
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
OPTION_GT_NUM
5
0000
5000
SSCR_F2_SIGN
0
1
SPACE
2
0
0
0
SY-MSGNO
000
333
000
000
000
LIST_INFO
0.0.0.0.0.0.1. ######
2222222222222222222220000000220000FF2222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000FF0000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000FF0000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000FF0000000000000000000000000000000000000000000000000000000000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
RALDB-VARIANT
SAP&MEPOBEST
54524454445522
3106D50F253400
00000000000000
00000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
GL_OPTI
0.0.0.0.1.
2000002222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RALDB-REPORT
AQZZ/SAPQUERY/MEMEPO==========
4555254555455244445433333333332222222222
11AAF31015529FD5D50FDDDDDDDDDD0000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
L_VARIPROG
AQZZ/SAPQUERY/MEMEPO==========
4555254555455244445433333333332222222222
11AAF31015529FD5D50FDDDDDDDDDD0000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SUBRC
4
0000
4000
LIST_FIELDS[]
Table[initial]
No.      17 Ty.          FORM
Name QUERY_CALL
GENERATED
G
4
7
0
0
<%_TABLE_TRDIR>
SYST-REPID
SAPLAQRC
5454455422222222222222222222222222222222
310C112300000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-REPID
SAPLAQRC
5454455422222222222222222222222222222222
310C112300000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CO_ACT_DOCUMENTATION
DOCUMENTATION
444544454544422222222222222222
4F35D5E4149FE00000000000000000
000000000000000000000000000000
000000000000000000000000000000
CO_GENERATED
G
4
7
0
0
L_REPORT
AQZZ/SAPQUERY/MEMEPO==========
4555254555455244445433333333332222222222
11AAF31015529FD5D50FDDDDDDDDDD0000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CO_ACT_INFOSET_GENERATOR
INFOSET_GENERATOR
444454554444545452222222222222
9E6F354F75E5214F20000000000000
000000000000000000000000000000
000000000000000000000000000000
TRDIR
AQZZ/SAPQUERY/MEMEPO==========                    ST1 1S        BASIS       20070528BASIS
4555254555455244445433333333332222222222222222222255323522222222445452222222333333334454522222
11AAF31015529FD5D50FDDDDDDDDDD0000000000000000000034101300000000213930000000200705282139300000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
HEADQU_TEXT3
222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000
P_FREE_SEL
Table[initial]
C_WARNUNG
3
3
3
0
0
HEADQU_TEXT2
222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000
P_SKIP
X
5
8
0
0
L_VARIANT
SAP&MEPOBEST
54524454445522
3106D50F253400
00000000000000
00000000000000
VARIT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
P_SELECTIONS[]
Table IT_1787[2x204]
DATA=GT_SELECTION_TABLE |
| Table reference: 594 |
| TABH+ 0(20) = 50F1823DC061E13C0000000052020000FB060000 |
| TABH+ 20(20) = 02000000CC000000FFFFFFFF04E50100B0030000 |
| TABH+ 40( 8) = 10000000C1248000 |
| store        = 0x50F1823D |
| ext1         = 0xC061E13C |
| shmId        = 0     (0x00000000) |
| id           = 594   (0x52020000) |
| label        = 1787 (0xFB060000) |
| fill         = 2     (0x02000000) |
| leng         = 204   (0xCC000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000006 |
| occu         = 16    (0x10000000) |
| access       = 1     (ItAccessStandard) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 2     (ItUniqueNon) |
| keyKind      = 1     (default) |
| cmpMode      = 2     (cmpSingleMcmpR) |
| occu0        = 1 |
| collHash     = 0 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0x686C813D |
| pghook       = 0x00000000 |
| idxPtr       = 0x00000000 |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 16    (0x10000000) |
| lineAlloc    = 16    (0x10000000) |
| store_id     = 1186 (0xA2040000) |
| shmIsReadOnly = 0     (0x00000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = 0x00000000 |
| hsdir        = 0x00000000 |
| ext2         = 0x68D77D3D |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = 0xB8B1E13C |
| delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000 |
| pb_func      = 0x00000000 |
| pb_handle    = 0x00000000 |
| CLOGQU[] |
| Table IT_1434[10x40] |
| FUNCTION-POOL=AQRCDATA=CLOGQU[] |
| Table reference: 315 |
| TABH+ 0(20) = F8E7013DD892F13C000000003B0100009A050000 |
| TABH+ 20(20) = 0A00000028000000FFFFFFFF04E9010090230000 |
| TABH+ 40( 8) = 0A000000C1048400 |
| store        = 0xF8E7013D |
| ext1         = 0xD892F13C |
| shmId        = 0     (0x00000000) |
| id           = 315   (0x3B010000) |
| label        = 1434 (0x9A050000) |
| fill         = 10    (0x0A000000) |
| leng         = 40    (0x28000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000176 |
| occu         = 10    (0x0A000000) |
| access       = 1     (ItAccessStandard) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 2     (ItUniqueNon) |
| keyKind      = 1     (default) |
| cmpMode      = 2     (cmpSingleMcmpR) |
| occu0        = 0 |
| collHash     = 0 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0x58E6013D |
| pghook       = 0x00000000 |
| idxPtr       = 0x00000000 |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 10    (0x0A000000) |
| lineAlloc    = 10    (0x0A000000) |
| store_id     = 1023 (0xFF030000) |
| shmIsReadOnly = 0     (0x00000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = 0x00000000 |
| hsdir        = 0x00000000 |
| ext2         = 0xE0E93E3D |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = 0xA0E93E3D |
| delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000 |
| pb_func      = 0x00000000 |
| pb_handle    = 0x00000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| CLOGQU |
| 00000000 |
| 33333333222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| SUCAT[] |
| Table[initial] |
| HEADBG |
| F |
| 4 |
| 6 |
| 0 |
| 0 |
| %_PRINT |
| 000                                                                                0### |
| 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No.      16 Ty.          FUNCTION |
| Name RSAQ_QUERY_CALL |
| DATA_TO_MEMORY |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| DBACC |
| 0 |
| 0000 |
| 0000 |
| FREE_SELECTIONS |
| Table[initial] |
| QUERY |
| MEPO |
| 44542222222222 |
| D50F0000000000 |
| 00000000000000 |
| 00000000000000 |
| SKIP_SELSCREEN |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| USERGROUP |
| /SAPQUERY/ME |
| 254555455244 |
| F31015529FD5 |
| 000000000000 |
| 000000000000 |
| VARIANT |
| SAP&MEPOBEST |
| 54524454445522 |
| 3106D50F253400 |
| 00000000000000 |
| 00000000000000 |
| WORKSPACE |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| LISTTEXT |
| |
| 222222222222222222222222222222222222222222222222222222222222 |
| 000000000000000000000000000000000000000000000000000000000000 |
| 000000000000000000000000000000000000000000000000000000000000 |
| 000000000000000000000000000000000000000000000000000000000000 |
| LIST_ID |
| |
| 222 |
| 000 |
| 000 |
| 000 |
| PROGRAM |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| REF_TO_LDATA |
| 0.0.0.0.0.0.0.1. |
| C0000000 |
| F0000000 |
| USED_VARIANT |
| |
| 22222222222222 |
| 00000000000000 |
| 00000000000000 |
| 00000000000000 |
| FPAIRS[] |
| Table IT_1788[0x18] |
| CLASS=CL_ABAP_QUERY_MMMETHOD=IF_READER_MM~READ_TABLEDATA=LT_FPAIRS |
| Table reference: 598 |
| TABH+ 0(20) = 0000000038F36E3D0000000056020000FC060000 |
| TABH+ 20(20) = 0000000012000000FFFFFFFF04E50100300B0000 |
| TABH+ 40( 8) = 10000000C1248000 |
| store        = 0x00000000 |
| ext1         = 0x38F36E3D |
| shmId        = 0     (0x00000000) |
| id           = 598   (0x56020000) |
| label        = 1788 (0xFC060000) |
| fill         = 0     (0x00000000) |
| leng         = 18    (0x12000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000046 |
| occu         = 16    (0x10000000) |
| access       = 1     (ItAccessStandard) |
| idxKind      = 0     (ItIndexNone) |
| uniKind      = 2     (ItUniqueNon) |
| keyKind      = 1     (default) |
| cmpMode      = 2     (cmpSingleMcmpR) |
| occu0        = 1 |
| collHash     = 0 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = Not allocated |
| pghook       = Not allocated |
| idxPtr       = Not allocated |
| refCount     = Not allocated |
| tstRefCount = Not allocated |
| lineAdmin    = Not allocated |
| lineAlloc    = Not allocated |
| store_id     = Not allocated |
| shmIsReadOnly = Not allocated |
| >>>>> 1st level extension part <<<<< |
| regHook      = 0x00000000 |
| hsdir        = 0x00000000 |
| ext2         = 0x90F3283D

correct the length in the program, by supplying same type as appears in database table.

Error message does not lead to the custom tab me51n

Hi Experts,
When I try to to create a PR in me51n and check, a popup with error messges appear when we pick one of the entry and select edit button that leads to the field of that concerned tab.I have a custom tab and cutom field the issue is error message is displayed to fill the custom field but when I check mark that error and select edit that does not take me to the custom tab where custom field exists please suggest I have tried lot of user exits but no use.
appreciate your help......

We added some error message checking using Function exit EXIT_SAPLMEREQ_005. How we can bring the screen to Customer Data Tab when there are any errors under the tab. And as long as the error is not fixed, the screen will stay on the tab?
To eloborate my question - in ME51n/Me52n, the system gives a messages window/subscreen with errors or warnings upon clicking the check button or upon save. On the messages window/subscreen, we can select a particular message and edit will take action to the corresponding tab with the cursor on the field with the issue. I understand this is standard functionality.
However I'm looking for a way to make this work for a mandatory field on the customer data tab i.e., when I select the error message pertaining to this mandatory field and choose edit, control should jump to the customer data tab with the cursor on the mandatory field.

Screen enhancement in ME51N/ME52n/ME53N

Hi All,
I want to display 2 additional tabs in the line item of ME52N tcode. There is already an enhancement MEREQ001 created in a project named MEREQ001. I tried to do the changes in the existing screen after deactivating the project, But after creating the tabs in the screen & when i try to save it I am getting an information message "Object can only be created in SAP package" , and after clicking continue i get the error "SAP object FUGR XM02 cannot be assigned to package ZMM". But even if I try to save it in any other namespace I am getting the error "Object belongs to function group with customer exit", and it will come out of the screen layout deleting the changes made the screen layout.
My requirement is to display 2 tabs in the Tcode Me52n, and the user must be able to fill data in these tabs & the data should be saved in the database on clicking save.
Is it possible to use Badi "ME_PROCESS_REQ_CUST" ?, if yes then please advice how.
Thanks in advance.

Hi,
You can't use the BADI " ME_PROCESS_REQ_CUST.
The main purpose of this badi is use to validate the PR at different levels. If you see the methods of that BADI for eg :
1. Process_header : This for validating the header part.
2. Process_item : This for validating the line item details.
Like that there are so many methods are there inside this BADI.
You mentioned that you deactivated the Existing Project of PR and i want to know in which package you have mentioned.
If that existing project is not needed you can delete the old one and incoporate the new logic and the old logic in the new project.
Hope you got some idea now.
With Regards,
Sumodh.P

PR release procedure no longer working-error MEPO 822

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
Situation :
One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
NB = NOT subject to release
RNB = SUBJECT to release.
So when they :
create a PR with document type RNB - it will goes for approval.
create a PR with document type NB - it will not go to approval.
It was working fine until after they created a new document type which copied from NB, called ZTP.
ZTP = NOT subject to release.
They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
Findings:
I've created a PR, and go to ME45N to release it but system prompt me an error message
"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.
So i check in OSS and found a note which is similar to this case.
Note 939371 - Overall release PR using ME54N gives error MEPO 822
Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
But my question is,is it also applied to ME51N and without external application as per my client's case?
Please anyone help.
Thanks.

Hi guys!
Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
Here's the reply from SAP :
Purchase requisition 10000066 cannot be released
Message no. MEPO822
Now click the other requisition button and let say
choose Purchase requisition 10000068,
Execute ME54N again:
Purchase requisition 10000068 cannot be released
Message no. MEPO822
Comment/explanation:
The log incidence seems not having problem with release
strategy as it was ok but it was the last PR was called
everytime ME54N was called. This same as it works in enjoy
transaction ME21N/ME22N or ME51N/ME52N.
For example, When using ME21n or ME22n to create or change PO,
after saving the PO. There are 2 ways to exit the transaction,
1, enter another T-code or use /n to exit directly.
2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
Then you can access ME23n to see the difference.
For the 1st way, ME23n won't display the last PO created in ME21n
For the 2nd way, ME23n will display the last PO just created!!!
Please see attached consulting note 595627 that explains a new
functionality as of release 470:
Due to performance problem, a decision had to be taken about the way to
use transactions. If you leave transaction ME21N/ME22N via the
exit button (F3), the expected PO will be displayed next time you use
these transactions. But if you quit abruptly (/nXXX) the PO number
won't be saved for the next transaction ME2?N.
As SAP note is the official document to explain system behavior,
this document is provided by SAP developement to explain this system
behavior to customers.
In your case, you had used ME54N and this was same as you use ME53N.
The last PO always display. You may try to view Purchase requisition
with release strategy, for example Release group R1, Rel. strategy
R1, then after this execute transaction ME54N again, the message
MEPO822 will not be there anymore.
Hope this will help you guys if you're having the same problem in future.
Thanks,
Crystal.

EXPORT_INCONSISTENT_STRUCTURE

Hi,
I am facing a problem while creating the purchase condition (Tcode-MEK2). I get an exception EXPORT_INCONSISTENT_STRUCTURE and the error analysis of the problem displays the following: ( This Program dynamic generated by SAP with one Function Module while creating the condition table )
Error analysis
When exporting the structure description, the structure
components overlapped. The error occured in the
description of the object "KOMG".
IN START-OF-SELECTION
START-OF-SELECTION.
Füllen der Überagbe-Parameter                                        *
Material                                                             *
MOVE F001 TO KOMG-MATNR.
VAKE-DATAB = SEL_DATE.
Selektionsparameter im Memory sichern                                *
EXPORT
   F001
   F002
   F003
   SEL_DATE
TO MEMORY ID 'RV_COND_MEMORY_01'.
Steuerungsdaten im Memory sichern                                    *
EXPORT
   T185F
   VAKE-DATAB
   KOMG
   UNCHGDBI FROM DATE_AS
   TO MEMORY ID 'RV_COND_MEMORY_02'.
LEAVE.
Thanks
Muthu

Muthu,
Pls Check the Table status. Some tables are in the Partially active Mode Because If a changed object is activated, all the objects depending on this object must be adjusted to the change. The active versions of the dependent objects are activated again. If errors occur when adjusting a dependent object, it is marked as partially active (since the object is no longer correct). The activated object itself is also marked as partially active (since the dependent object could not be fully adjusted to the change).
Pls Let me know the status.
Kanagaraja L

User exit or badi for me52n transaction.

Hi all,
i have a requirement to write a user exit or badi for me52n transaction. the requirement is in header section, only one plant should be accepted. that is in the first row one plant will be inserted. in the second row if we are inserting another plant other the first row plant, it should not accept it and it should raise an error.
that is from the second row onwards, every plant should match with the first row plant.
if any part of this issue is unclear, plz let me know so that i can explain it clearly
this is urgent requirement.
please let me know the solution as soon as possible.
points will be awarded.
thanking u in advance.
A.srinivas.

In this version exit EXIT_SAPLMEREQ_005 should exists (look at OSS <a href="https://service.sap.com/sap/support/notes/843446">Note 843446 - MEREQ001: Cannot call up external service data in user exit</a> this note refers to the exit and is applicable in 4.70. Look also at OSS <a href="https://service.sap.com/sap/support/notes/310154">Note 310154 - ME21N/ME51N: Customer-specific check, generating error log</a>
Regards

PR creation for 'F" in ME51N, ME52n, the cost center field exit getactivate

Dear Gurus,
We have a Cost center Field exit activation, meaning when a PR is generated, the system will validate only for his department cost center. Its working fine
The issue, when we create PR through ME51n or me52n for Acct Assign "F" here we are going to enter only Work order number and GL number, not cost center. Still this field exit has activation, here the same error message popup, which suppose not to be.
So in MM configuration, i have disabled Cost center field for acct assignment "F".
Now when i create a PR for F, for single account assignment, the system will alllow, but if i want to distribute the qty to different work order, the system goes for validation for cost center field exit.
How to resolve for multiple assignment, how to deactivate the Cost center field exit for this case, its woking fine of Single account assignment (after disable the cost center field for Account Assignment "F")
Please help me out or any way to do this?
Regards
RS
Edited by: RS on Sep 14, 2009 7:40 AM

Hi,
Cross check you have Cost Center field is Hidden for Account Assignment Category A (Asset) in t.code:OME9. Now change Cost Center field as Display for Account Assignment Category A and save.
Now create a new PO with Account Assignment Category A and find the difference how Cost Center appearing in your PO in “Account Assignment” TAB.
Regards,
Biju K

Error miro posting in third party sales order

error in miro posting in third party sales order occured i.e, level F1 belongs to cash position(source symbol BNK)....
pls solve the problem it is very urgent...

Hi,
Process
VA01 - Create sales order (Schedule line CS and item category TAS) >> ME52N - PR is generated after save of sales order >> ME21N - Convert PR in to P.O >> Then vendor will send goods to customer and will send invoice to our company >> MIRO - Invoice receipt from vendor >> VF01 - Final invoice to customer
When you enter vendor invoice then you come to know that vendor sent qty. same will be billed to customer(Billing relevance in item category should be F)
Kapil

BADI - ME_PROCESS_REQ_CUST- G/L Accounts Error Message

Hi guys,
I have a problem regarding autodeterminating G/L Accounts.
I used BADI ME_PROCESS_REQ_CUST with Method: PROCESS_ACCOUNT.
For setting the G/L Account I used:
            ls_accounting-sakto = ls_ctrlacc_b-sakto.
            ls_accountingx-sakto = 'X'.
            CALL METHOD im_account->set_exkn
              EXPORTING
                im_exkn = ls_accounting.
            CALL METHOD im_account->set_exknx
              EXPORTING
                im_exknx = ls_accountingx.
The problem is in ME52N (changing mode) when i change the G/L Account and after the BADI Logic, a still receive the transaction error "Enter a G/L Account" which will disappear if i press enter again.
So ...i need in my BADI Logic , at one point (G/L Account is not initial) to erase from the Message Stack that error.
How do I do that using data and methods from this BADI method: PROCESS_ACCOUNT?
Thanks a lot.

I solve this problem by doing :
CALL METHOD cl_message_handler_mm=>get_handler
        IMPORTING
          ex_handler = lref_msg.
CALL METHOD lref_msg->remove_all.
mmpur_message_force 'E' 'ME' '083' text-003 '' '' ''.
Now, I don't know how to set cursor on matkl field
Any opinions?

Error "EXPORT_INCONSISTENT_STRUCTURE" IN PR (ME52N)

Similar Messages

Maybe you are looking for