Error While Doing Post Goods Issue

Hi SD Gurus
While I am Doing PGI for Standard Order, I am Getting the following Error.
Version : 5.0
Clien: 800
Runtime Errors         PXA_NO_FREE_SPACE
Date and Time          24.01.2008 23:50:48
Short dump has not been completely stored (too big)
ShrtText
No PXA storage space available at the moment.
What happened?
The current ABAP/4 program had to be terminated because there
was no space available to load it.
Each ABAP/4 program to be executed is stored in a central
storage area that is divided between all users.
This area was too small to hold all currently active programs for all
users.
The current program, "SAPLMCB1", had to be terminated because a capacity limit
has been reached.
What can you do?
Since this could have resulted in a temporary bottleneck, you should
try to restart the program.
Ask your system administrator to increase the size of the area (PXA)
used to store the ABAP/4 programs.
Make a note of the actions and input which 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.
Error analysis
Unable to load a program of 1234944 bytes.
The PXA ('program execution area') was too small to hold all
currently active programs for all users.
At present, the size of the PXA is set at 145444 Kbytes.
How to correct the error
The current size of the PXA was set at 145444 kilobytes.
You can increase or decrease the PXA in the SAP profile. When
doing this, please refer to the relevent instructions in the
installation manual.
You can use the utility program 'ipclimits' to display the
available system resources.
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:
"PXA_NO_FREE_SPACE" C
"SAPLMCB1" or " "
"LIS_VERBUCHUNG"
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....... "super"
Network address.......... "192.168.0.10"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "Intel 801586 (M"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "SUPER"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPPRD"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Apr 18 2004 23:27:50"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "10"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8112
EM....................... 11498256
Heap..................... 0
Page..................... 65536
MM Used.................. 7861472
MM Free.................. 498776
SAP Release.............. "640"
User and Transaction
Client.............. 800
User................ "SAPUSER"
Language key........ "E"
Transaction......... "VL02N "
Program............. "SAPLMCB1"
Screen.............. "SAPMV50A 4004"
Screen line......... 26
Information on where terminated
The termination occurred in the ABAP program "SAPLMCB1" in "LIS_VERBUCHUNG".
The main program was "SAPMV50A ".
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
E0
SY-UCOMM
WABU_T
SY-TITLE
Change Outbound Delivery
SY-MSGTY
E
SY-MSGID
WMOD
SY-MSGNO
081
SY-MSGV1
M1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
15 FORM         SAPLMCB1                            LMCB1F20                              200
LIS_VERBUCHUNG
14 FORM         SAPLMCB1                            LMCB1F20                              198
LIS_VERBUCHUNG
13 FUNCTION     SAPLMCB1                            LMCB1U03                               57
MCB_STATISTICS_LIS
12 FORM         SAPMM07M                            MM07MFB9_BUCHEN_AUSFUEHREN            863
BUCHEN_AUSFUEHREN
11 FUNCTION     SAPLMBWL                            LMBWLU17                                6
MB_CREATE_MATERIAL_DOCUMENT_UT
10 FUNCTION     SAPLMBWL                            LMBWLU21                               45
MB_POST_GOODS_MOVEMENT
9 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                599
BELEG_SICHERN_POST
8 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                 64
BELEG_SICHERN_01
7 FORM         SAPMV50A                            FV50XF0B_BELEG_SICHERN                 14
BELEG_SICHERN
6 FORM         SAPMV50A                            MV50AF0F_FCODE_SICH_OHNE_CHECK         10
FCODE_SICH_OHNE_CHECK
5 FORM         SAPMV50A                            MV50AF0F_FCODE_WABU_VL02               10
FCODE_WABU_VL02
4 FORM         SAPLV00F                            LV00FF0F                               92
FCODE_BEARBEITEN
3 FUNCTION     SAPLV00F                            LV00FU03                               45
SCREEN_SEQUENCE_CONTROL_INIT
2 FORM         SAPMV50A                            MV50AF0F_FCODE_ANFORDERUNG             33
FCODE_ANFORDERUNG
1 MODULE (PAI) SAPMV50A                            MV50AI0F                               66
FCODE_ANFORDERUNG
Chosen variables
Name
Val.
No.      15 Ty.          FORM
Name  LIS_VERBUCHUNG
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
CON_ZEITP
BF
44
26
XMCMSEG[]
Table IT_895[1x2708]
4D947FA400005000700000009000FFFF0000A4000000C380
85F283F200001100F30010004A00FFFF4E20812040001000
XMCBEST[]
Table IT_894[2x1059]
13943FA400005000700000002000FFFF000094000000C380
8FD283F200000100E30020003400FFFF4E20852080009000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
%_VB_SWITCH_KEY
2222222222222222222222222222222222
0000000000000000000000000000000000
I_MSEG-BNBTR
0000000
000000C
FLG_BW
X
5
8
MSPR
00000000000000 #######################################
2222222222222222222222222222222222222222333333333333332000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000C000000C000000C000000C000000C0000
CON_MODUS_SIM_NEW
F
4
6
%_DUMMY$$
2222
0000
IF_RELEASE
1
0000
1000
H_E1CMCCO[]
Table[initial]
0000FFFF
0000FFFF
SY-REPID
SAPLMCB1
5454444322222222222222222222222222222222
310CD32100000000000000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
TMCW
00
222223322222222222222222222
000000000000000000000000000
HLP_CONTROL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
S035
0000000000        ########################
2222222222222222222222222222222222222222222222333333333322222222000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000C0000000C0000000C
No.      14 Ty.          FORM
Name  LIS_VERBUCHUNG
IF_RELEASE
1
0000
1000
No.      13 Ty.          FUNCTION
Name  MCB_STATISTICS_LIS
MSLB
000000 ############################
2222222222222222222222222222222222222222222222333333200000000000000000000000000002222222222222
00000000000000000000000000000000000000000000000000000000000C000000C000000C000000C0000000000000
I_MODUS
2
0
CON_MODUS_LOG
C
4
3
IDOC_SENDEN
2
0
TRUE
X
5
8
SYST-REPID
SAPLMCB1
5454444322222222222222222222222222222222
310CD32100000000000000000000000000000000
T001K
     0000
2222222222222222222222222222220002222223333
00000000000000000000000000000000C0000000000
LIS_UPD
X
5
8
EKPO
00000  00000000
2222222222222333332233333333222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_MSEG-PS_PSP_PNR
00000000
33333333
00000000
MKPF
0000      00000000000000000000000000000000000000
2222222222222333322222233333333333333333333333333333333333333222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
No.      12 Ty.          FORM
Name  BUCHEN_AUSFUEHREN
SY-REPID
SAPMM07M
5454433422222222222222222222222222222222
310DD07D00000000000000000000000000000000
%_VB_SWITCH_KEY
2222222222222222222222222222222222
0000000000000000000000000000000000
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
WS_MENG_WA
0000000222
000000C000
XMKPF[]
Table IT_532[1x205]
4A940D940000400010000000C000FFFF0000ED001000C380
83A281F20000610042001000D000FFFF4E20050000001000
KZDWS
1
3
1
XMSEG[]
Table IT_492[1x1241]
1B74598400002000E0000000D000FFFF00005D000000C380
0FA283C200000100C10010009400FFFF4E20060080001040
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
SYST
0000000000000000000000000000000000000000000000000000000000008000000000000000200000000000000000
0000000010000000000000000000000000000000100000001000000010004000000000000000A00000000000000000
T003M
800WL02
3335433
8007C02
XMCMSEG[]
Table IT_895[1x2708]
4D947FA400005000700000009000FFFF0000A4000000C380
85F283F200001100F30010004A00FFFF4E20812040001000
XMCMSEG
800M1                SCCLSCCL                    0000000111EA INR  -
3334322222222222222225444544422222222222222222222333333333344244522222222222222222222222222222
800D10000000000000000333C333C0000000000000000000000000001115109E200D00000000000000000000000000
XEKLB
00000000          000000000          0000                         ##############     0000#####
3333333322222222223333333332222222222333322222222222222222222222220000000000000022222333300000
000000000000000000000000000000000000000000000000000000000000000000000000C000000C00000000000000
T333T
000
22222223332222222222222222222222222
00000000000000000000000000000000000
ZMSEG-MAT_PSPNR
00000000
33333333
00000000
XPF02
2
0
XMCBEST[]
Table IT_894[2x1059]
13943FA400005000700000002000FFFF000094000000C380
8FD283F200000100E30020003400FFFF4E20852080009000
XPAUS
2
0
XMCMRES[]
Table IT_1030[0x129]
00005FA400000000000000008000FFFF000024001000C380
000083F20000D200640000001000FFFF4E20072000001000
XBCODE
2
0
KZDCH
1
3
1
T000
800IDES-ALE: Central FI SystFrankfurt - Deutschland  EUR            C1     X I802358     20041
3334445244432466776624425777476666777222467776666662245522222222222243222225243333332222233333
8009453D1C5A035E421C06903934621EB65240D04554338C1E40055200000000000031000008098023580000020041
No.      11 Ty.          FUNCTION
Name  MB_CREATE_MATERIAL_DOCUMENT_UT
RBDTER
0000000000000000
2223333333333333333
0000000000000000000
RIDNLF
2222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000
KZBWA
01020304050607B3SZK3
33333333333333435543
01020304050607233AB3
FUSS-UPVOR
2
0
UPTYP_LG
3
3
3
%_SPACE
2
0
MLGVM07I-DISPO
YTFMAT
222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
FUSS-UPTYP
2
0
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
MVM07I-LFGJA
FUSS[]
Table IT_377[0x4488]
000000000000D000700000008100FFFF00001E000000C380
0000000000005000910000008100FFFF40200D0020001000
ECODE
NP
45222222222222222222
E0000000000000000000
CCODE_NEXT
22222222222222222222
00000000000000000000
FCODE
NP
45222222222222222222
E0000000000000000000
FCODE_NEXT
NP
45222222222222222222
E0000000000000000000
PCODE
22222222222222222222
00000000000000000000
No.      10 Ty.          FUNCTION
Name  MB_POST_GOODS_MOVEMENT
XBLNR_SD
0080014044
3333333333
0080014044
EMKPF
000000000000000000          ######
2222222222333333333333333333222222222200000022222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
ATPDT
000000           0
2222222222333333222222222223
0000000000000000000000000000
PREFETCH34
00000000000000
22222222222222222222222222222222222222222222222222222222233333333333333222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
FCOD-ST
ST
55222222222222222222
34000000000000000000
%_VIASELSCR
0
4
XMKPF-XBLNR
0080014044
3333333333222222
0080014044000000
XMKPF[]
Table IT_532[1x205]
4A940D940000400010000000C000FFFF0000ED001000C380
83A281F20000610042001000D000FFFF4E20050000001000
XMKPF
80049000331532008WLWLPR20080125200801252008012423504100000000SAPUSER         0080014044
3333333333333333354545533333333333333333333333333333333333333545554522222222233333333332222222
800490003315320087C7C0220080125200801252008012423504100000000310535200000000000800140440000000
XMSSA
000000  000000###############################################
2222222222222222222222222222222223333332233333300000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000C000000C000000C000000C000000C000000C00000
MDVER[]
Table[initial]
0000FFFF
0000FFFF
L_MEM_ID
MKPF-XBLNR
4454254445
DB06D82CE2
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XEKPK_KEY
00000
222222222233333
000000000000000
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMKPF-XABLN
2222222222
0000000000
%_DUMMY$$
2222
0000
XDBEFU
00000 ##############                             #######       0000#############      ######
3333320000000000000022222222222222222222222222222000000022222223333000000000000022222200000022
000000000000C000000C00000000000000000000000000000000000C0000000000000C00C000000C00000000C00C00
GT_SUBCON_PARENT
Table[initial]
0000FFFF
0000FFFF
SY-SUBRC
0
0000
0000
TBSL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000EEDDDDDDDDDDDDEDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD0000DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
MDM07I-BTEXT
FUSS+4215(16)
0000010661000010
3333333333333333
0000010661000010
L_ATPCC
    ########00000000########00000000########00000000###############00000000########
0002222200000000333333330000000033333333000000003333333300000000000000033333333000000002
00C0000000000000000000000000000C000000000000000C00000000000000C0000000C000000000000000C0
FUSS-EXWRT
0000000
000000C
IMSEG-DMBTR
No.       9 Ty.          FORM
Name  BELEG_SICHERN_POST
BS_CHECKBOX
2
0000
2000
LIKP
8000080014044SAPUSER     23453420080124      SCCLENSULF   X20080129200801282008012820080129200
3333333333333545554522222333333333333332222225444445544222533333333333333333333333333333333333
800008001404431053520000023453420080124000000333C5E35C6000820080129200801282008012820080129200
BS_PUSHBUTTON
0
0000
0000
V50AGL
00X          B         X      ####                          Ol4kQoiVBas4}R6ApXF7YW
2222223352222222222422222222252222220000222222222222222222222222224636566546737534754355222222
000000008000000000020000000008000000000000000000000000000000000000FC4B1F962134D261086797000000
VBSK
0000000000000000000000#######   #######
2222222222222222222222222233333333333333333333330000000222000000022222222222222222222222222222
000000000000000000000000000000000000000000000000000000C000000000C00000000000000000000000000000
%_DUMMY$$
2222
0000
T683C
2222222222222222222222
0000000000000000000000
WA_ZAEHL
1
0000
1000
CHAR1
1
3
1
SYST-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
EMKPF-SUBRC
1
0000
1000
CVBEP[]
Table IT_165[0x472]
0000000000006000A0000000D000FFFF0000F0002000C180
0000000000003000500000008100FFFF4000060000001000
ABR_VOR_GABJA
0000
3333
0000
XLIKP[]
Table IT_253[1x1016]
5A74785400008000F0000000F00000000C00D0001000C180
02D280920000B000D0001000830000004910070000001000
XLIKP
8000080014044SAPUSER     23453420080124      SCCLENSULF   X20080129200801282008012820080129200
3333333333333545554522222333333333333332222225444445544222533333333333333333333333333333333333
800008001404431053520000023453420080124000000333C5E35C6000820080129200801282008012820080129200
<%_L170>
VBAP_GESAMTNETZTERMINIERUNG
2
0
<%_L170>-UPDKZ
UPDKZ_DELETE
D
4
4
XLIKP-VBELN
0080014044
3333333333
0080014044
EMKPF
4900033153200800000000000000            ####
3333333333333333333333333333222222222222000022222222222222222222222222222222222222222222222222
4900033153200800000000000000000000000000100000000000000000000000000000000000000000000000000000
DEFAULT_VKGRP
222
000
PACKDATEN_VERBUCHEN
2
0
No.       8 Ty.          FORM
Name  BELEG_SICHERN_01
SYST
0000000000000000000000000000000000000000000000000000000000008000000000000000200000000000000000
0000000010000000000000000000000000000000100000001000000010004000000000000000A00000000000000000
IVBPA1KEY
000000
33333322
00000000
IF_FINAL_CHECK
2
0
LF_FLAG_DOCNUM_NEW
2
0
CF_SUBRC
0
0000
0000
KNVP
000                    000000000000000000
2222222222222222222222233322222222222222222222333333333333333333222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
IF_RENUMBER
X
5
8
SPACE
2
0
IVBPA2KEY
000000
22333333
00000000
SY-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
IF_POST
X
5
8
IVBPA3KEY
000000
22333333
00000000
T180-AKTYP
V
5
6
AKTYP-CREATE
H
4
8
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XSDCTRLFLAG
22
00
No.       7 Ty.          FORM
Name  BELEG_SICHERN
IVBPA1_SELIND
000
00C
TVLK-KAPPL
V2
53
62
IVBPA1_LOOPIND1
005
01C
LIKP-WERKS
2222
0000
XVBPAKEY_FEHLER
000000
222222222222233333322
000000000000000000000
IV_FINAL_CHECK_DURCHFUEHREN
2
0
CHARX
X
5
8
LF_SUBRC
0
0000
0000
No.       6 Ty.          FORM
Name  FCODE_SICH_OHNE_CHECK
V4231_SHOWN
2
0
%_SPACE
2
0
FCODE
WABU_T
54455522222222222222
7125F400000000000000
FCODE_DEFAULT_UEBERSICHT_1
DEF1
44432222222222222222
45610000000000000000
KOMKD
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
E1EDL32_QUALI
001002
333333
001002
J_1AINFT21
222222222222222222222222222222222222222
000000000000000000000000000000000000000
CFG_SUBITM_DATA
000000
222222222222223333332222222222222222222222
000000000000000000000000000000000000000000
VBAP_ENDE_BEARBEITUNG
2
0
XVBPAKEY
000000
222222222222233333322
000000000000000000000
CVBFA
000000          000000 ########   ########        00000000000000
2222222222222333333222222222233333320000000022200000000222222223333333333333322222222222222222
0000000000000000000000000000000000000000000C0000000000C000000000000000000000000000000000000000
GC_CHK_DO_QUAN_NO_REQ
2
3
2
No.       5 Ty.          FORM
Name  FCODE_WABU_VL02
FCODE_ZURUECK1
BAC1
44432222222222222222
21310000000000000000
XVBPA[]
Table IT_31[2x542]
DD641A6400001000100000001000FFFF00002C001000C280
8C92033200002000F0002000E200FFFF40000D0000001400
FCODE_ZURUECK3
BAC3
44432222222222222222
21330000000000000000
XVBUV[]
Table IT_182[0x123]
0000867400006000B00000007000FFFF00009E000000C080
00008CC20000D00060000000B000FFFF4000870090001400
FCODE_ZUSAETZE_FAB
PFZU
54552222222222222222
06A50000000000000000
YVBADR[]
Table IT_32[0x609]
0000C95400001000200000006000FFFF0000DF000000C080
00008B5200003000000000001200FFFF40000C0010001400
FCODE_ZURUECK2
BAC2
44432222222222222222
21320000000000000000
YVBPA[]
Table IT_33[0x542]
0000E95400001000200000001000FFFF00009C001000C280
00008B520000400010000000E200FFFF40000D0000001400
FCODE_VORIGE_POSITION
POS-
54522222222222222222
0F3D0000000000000000
FCODE_REPARATUR
PREP
55452222222222222222
02500000000000000000
FCODE_GEFAHRGUT
KGGP
44452222222222222222
B7700000000000000000
OBJEKTART_IS
IS
45
93
FCODE_GLEICHE_SEITE
ENT1
44532222222222222222
5E410000000000000000
CVBAP
8000000010661000010M1                M1                                                     DI
3333333333333333333432222222222222222432222222222222222222222222222222222222222222222222222244
8000000010661000010D10000000000000000D10000000000000000000000000000000000000000000000000000049
LIPS-VGBEL
0000010661
3333333333
0000010661
No.       4 Ty.          FORM
Name  FCODE_BEARBEITEN

Dear Hari
If you have on your own solved the problem, please let me know how you have solved.  You have closed the thread without rewarding points to the contributors !!!!!.
Thanks
G. Lakshmipathi

Similar Messages

  • Error while doing post good receipt

    Hi Frnd,
       I am doing Returns delivery VL02n while doing Post goods receipt i am getting an error saying that
    *Document is incomplete: You cannot post goods movement*
    The batches are not defined for delivery item 900001
    What is this error ?
    Regards
    Rakesh

    Hi Rakesh,
    Go to IMG... logistic general ... batch management ...  batch determination and batch check ... batch search procedure and check the activationu2026 Activate Automatic Batch Determination in SD
    Activate Automatic Batch Determination for Delivery Item Categories
    I think you have not checked the Auto batch determination for your delivery item categories.
    Please check and then try.
    Hope it helps,
    Regards,
    MT

  • While doing the goods issue system is thruoghing an erro message no VL621

    hi ,
    actually while doing the goods issue we had put a validation if that filed(serial number) is not valid.like AVAILABLE then the system has through to an error message.but after that error message system is throughing an nother error.
    Risk of posting several mat.documents for one delivery->long text
        Message no. VL621
    Diagnosis
        Processing has been terminated because there is the risk that the system
        creates several material documents for this delivery.
    Procedure
        If this message occurs frequently, please note the exact situation and
        procedure as well as error messages and inform the system administrator.
    and we changed that error to warning also still we are getting that error message.
    how to stopthis error message.

    hi actually not for serial number check.
    there is a Z field in serial number master which is used for SIM number.
    that SIM number will be validated with available SIM number from another Z table.
    after this SIM error system is throughing this VL621 error after transaction terminated message.

  • Accounting document while doing Post Goods Receipt

    Hi,
    The scenario is like this.
    1.     Sales order1 is created.
    2.     Delivery document created; PGI (post goods issue) is done. Here the movement type is 601.
    I want to get back the material (equipment) for some reason; I want to check the material for its condition. If there is any damage, I have to charge the customer.  So, the material will be received to Return stock by return sales order with reference to the first sales order1 (Movement type 651); then will be sent to Quality (Movement type 457); if it is not damaged will be sent to unrestricted stock (Movement type 321) by transaction code MB1B.
    When I am doing the PGI, the accounting document is created; the Inventory account is credited and COGS (Cost of goods sold) is debited.
    When I am doing PGR (Post Goods Receipt), the accounting document is not created (Movement type 651).
    I have created a new u2018Schedule line categoryu2019 (YL) for the return process with the movement type 651.
    I want to get an accounting document while doing PGR. The inventory account is to be debited; the COGS is to be credited.
    Can I get the accounting document by changing the movement type in Schedule line category u2018YLu2019?
    Please guide me in this regard.
    Regards,     
    K Bharathi

    Hi
    Can I get the accounting document by changing the movement type in
    Schedule line category u2018YLu2019?
    Yes in your schedule line category if the movement type is not 651 then an accounting doc will be created
    For movement type 651 there wont be any accounting document
    In returns (651M.Type)  If a returns delivery exists, the return should be posted in the Sales (SD-SLS) component, not in the Inventory Management component.
    Depending on how Customizing for Sales is configured (the movement type is configured in the step Define Schedule Line Category), the delivery is posted to the following stock:
    - Blocked stock returns (non-valuated, not unrestricted-use) (movement type 651)
    - Unrestricted-use stock (movement type 653)
    - Quality inspection stock (movement type 655)
    - Blocked stock (movement type 657)
    If the given quantity is posted to blocked stock returns first, you can make a manual goods movement posting in the Inventory Management component to transfer the quantity to valuated stock.
    So, when the goods arrives in so called "Block stock returns" it is not your property, it belongs to the customer (the ownership has not changed) - it is not valuated. Whiles you post the goods to your own (plant) stock by 653/655/657 it becomes your property that's why it is valuated and material document will be created
    Regards
    Raja

  • Print Dialog-box Pop-Up while doing Post Good Receipt in VL32N

    I have created Inbound delivery for a Purchase Order. When i try to perform Post Good Receipt operation, the material is getting posted to the respective storage location, but the print dialog-box appears immediately. I faced this problem in only one plant.
    Output Conditions are maintained for the specific output type, in that medium is print output and time of output is Print with own application.
    Why the system is giving print dialog box when we perfrom Post Good receipt operation?
    How to avoid this print pop-up dialog box?
    Edited by: Paul Pandian on Mar 21, 2009 3:27 AM

    Hi Pawan,
    As sheer conincidence I should say, I just posted question on this topic just 1 hour back. And based on the comments in your question my problem is also solved. Thanks for that.
    BTW, I can confirm that the settings you have mentioned are correct. As I have tested it.
    Do you want to consider setting for auto GR?
    Logistics Execution -> Warehouse Management -> Interfaces -> Shipping -> Define Shipping Control -> Define Shipping Control at the Movement Type Level -> For movement type 101 we have put the Copy WM quantity as 'Copy WM quantity as delivery quantity and post GR/GI'.
    I hope this helps.
    Kind Regards,
    Prakash

  • I have a question about error messange in [Post Goods Issue] process.

    Dear all.
    I'm working a SD system operater in south Korea.
    I'm really sad for our recent defeat in worldcup gameTT.
    Anyway, I need your help.
    When I make outbound delivery document and post GI,
    I got a message like this :
    Fld selectn for mvmt type 601 / acct 43010101 differs for Customer goods movement (015)
    Message no. M7093
    I don't know to solve this problem.
    I Think this is a kind of LE module's error,
    But there are no LE professional in my company.
    So, I need your help.
    And also, I try to find this error using message class M7, no 093.
    I found the message in the class, but embarrassly, there is no result the maessage's where-used-list!.
    PLZ let me know the solution about this.
    Best Regards.
    Kwangkyun choi.
    Edited by: Kwang-Kyun Choi on Jun 21, 2010 3:16 AM
    Edited by: Kwang-Kyun Choi on Jun 21, 2010 3:22 AM

    Hi,
    If you read the long text of the error message, you can find out that the cause of the problem is due to the incompatible setting of fields selection between movement type and G/L account.
    SAP note 9281 will help you to solve this problem.
    The system is functioning as designed, a check is done on both tables T004F (FI) and T156B (MM).  These tables define what data is required, optional,etc... when processing the transaction. There are certain fields that are contained on both tables.
    For those fields that are redundant, the field selections must be the same.  Since the data is processed through a single dynpro,  the system must have only one instruction for a data field. This is why message M7 093 is being generated when optional is specified for MM and required is specified for the General Ledger.
    Please read SAP note 9281 and, according to it, execute the report RM07CUFA to compare the field selection definitions in MM
    and FI. Maintain the incorrect settings from the report (when a red line appears, it means that it is wrong so you have to review your customizing settings). The customizing transactions for setting the field status are:
    - OMBW -> field status group by movement type.
    - OBC4 -> field status group for finantial documents, defined in the G/L account master data.

  • Problem with post goods issue in SD std. delivery

    hi
    while doing post goods issue of a delivery in VL01n its showing run time error. the error message is gvn below.
    Information on where terminated
    Termination occurred in the ABAP program "SAPLMBWL" - in
    "MB_POST_GOODS_MOVEMENT".
    The main program was "SAPMV50A ".
    In the source code you have the termination point in line 59
    of the (Include) program "LMBWLU21".
    Source Code Extract
    Line SourceCde
    29 * when a goods movement for an inbound or outbound delivery is posted
    30 * directly from VL31N/ VL01N, XBLNR is not yet known when we call
    31 * CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
    32 * BKPF as well. There is no other way to forward XBLNR to FI as not
    33 * every document is posted by MB_CREATE -> a new function module in
    34 * MBWL for transferring the information, called by FI, meant to load
    35 * the complete function group for all MBxx postings when this isn't
    36 * required (Performance). Would be the better way to transport the
    37 * information after switching off MBxx in later release.
    38 * corresponding IMPORT ... FROM MEMORY ... can be found in
    39 * AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
    40 l_mem_id = 'MKPF-XBLNR'. " 641365
    41 EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
    42 ENDIF.
    43 IF xmkpf-xabln IS INITIAL. "note 434093
    44 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
    45 ENDIF. "note 434093
    46
    47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    48
    49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
    50 CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
    51 EXCEPTIONS
    52 error_message = 4.
    53 * As soon as we have started to put things into UPDATE TASK, we must
    54 * ensure that errors definitely terminate the transaction.
    55 * MESSAGE A is not sufficient because it can be catched from
    56 * external callers which COMMIT WORK afterwards, resulting in
    57 * incomplete updates. Read note 385830 for the full story.
    58 IF NOT sy-subrc IS INITIAL.
    >>>>> MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
    60 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    61 * MESSAGE A263.
    62 ENDIF.
    if there is any configuration step for post goods issue in SD thn plz mention it.
    Plz help..

    Hi Lakshmipati,
        I have maintained movement type 601 at OMJJ. I hav also added the filed cost center in that (before it was not available).
      I checked GL acct at fs00, it is already contain field status group g004 and the check box "post automaticallyt" is also activated. The cost element has also assigned to cost center. After assigning the cost center to cost element, the error is changed to fld selection for mvmt type 601/ acct 300021 differs for cost center
       But i noticed one thing: If i chage the field status group to g006, the error has not appeared and giving the other error:
    valuation area xxx2 (plant) not yet ptoductive with material ledger this error has been already posted by me but not yet received correct answer.
    Kindly provide the solution for this.
    Regads
    Sabera

  • Post Goods Issue (VL06O) - taking more time approximate 30 to 45 minutes

    Dear Sir,
    While doing post goods issue against delivery document system is taking lots of time, this issue is very very urgent can any one resolved or provide suitable solution for solving this issue.
    We creates every day approximate 160 sales order / delivery and goods issue against the same by using transaction code VL06O system is taking more time for PGI.
    Kindly provide suitable solution for the same.
    Regards,
    Vijay Sanguri

    Hi
    See Note 113048 - Collective note on delivery monitor and search notes related with performance.
    Do a trace with tcode ST05 (look for help from a basis consultant) and search the bottleneck. Search possible sources of performance problems in userexits, enhancements and so on.
    I hope this helps you
    Regards
    Eduardo

  • BADI or User Exit for Post Goods Issue Reverse (VL09)

    Hi,
    Could you please let me know any BADI/User Exit which will trigger while doing Post Goods Issue Reverse through VL09 transaction.
    Thanks,
    Sandeep

    Hello,
    If you can be specific about your requirement, then response can be better.
    Still, check with following Exit:
    - V50R0001  Collective processing for delivery creation
    - V50R0002  Collective processing for delivery creation
    - VMDE0003  Shipping Interface: Message SDPICK (Picking, Inbound)
    - VMDE0004  Shipping Interface: Message SDPACK (Packing, Inbound)
    - V50S0001  User Exits for Delivery Processing
    Thanks & Regards
    JP

  • Error message while posting goods issue.

    Hi,
    Please help me with the following problem..
    I have created Sales Order, Delivery & also created the Transfer Order number. After creating Transfer ordering, while submitting post goods issue, when I click on PGI, I get
    "Posting only available for period 2002/10 to 2002/11"...
    As a resulf of the above, I am not able to complete Billing for all the sales orders I have created.
    Can somebody please help me with above?
    Regards
    Nadeem

    Use the MMPV transaction to check your current period. Since you have transactions already done you need to do closing for every month.
    If you are on an IDES system for training purposes you can do a fast transaction by removing the plant assignment from the company code. The use the MMPI transaction to set your current period. Remmber April is period 1 if you are are using the indian financial year and fiscal year variant k4.
    Then reassign the plant and now try posting It will allow you. But a word of caution. Never attempt to remove the plant asignment in the development system. It might cause errors. for that there is a separate note.
    regards
    Jude

  • Error during Post Goods Issue of Material in VL02N for STO Purchase Order

    I am getting one error message during Post goods issue of Material for STO Purchase order.
    I am doing the Post goods issue in T code VL02N
    Error is " Account type D is not defined for Document type WL"
    What is the settings required to be done.
    Thanks,
    Shailendra

    Please check Plant customer master reconsilation account properly maintained or not in XD03 transaction.

  • Update termination error when posting goods issue

    Helllo
    I have a strange problem I can not figure out.  We have serial numbers like 12345/345.  When trying to post goods issue I get an update termination error  for invalid character. This only happens if the quantity is more than 1 each.  A quantity of 1 each works fine and receives no update termination when post goods issue...only recieve termination error if the post goods issue is for a qty of 2 each.
    I searched the SAP site found OSS note 40355...applied the note.  The note also mentions the chaging print paramters to include "/ _"  this is all done.
    I tried doing a ABAP Debug in SE38 (for the delivery note print program) and setting the breaking point, but when I go to run the transaction after the setting break point...when I hit post goods issue...SE38 does not return back to its screen.  So not sure if I am running the correct program there...or if this works for the update terminations?
    So strange I do not get this for a qty of one each only when it is greater than that.  I am stumped need help....
    Any advice wiould be GREATLY appreciated....

    Looks like there is an error in the delivery (or material movement ?) print program. Easiest would be to disable these outputs for test purposes. When no dump then the error is somewhere in the print program an could be analysed by triggering the print separately with ABAP RSNAST00.
    regards Jack

  • Post Goods Issue - error : Class type does not exist - Message no. VK662

    Hi,
    I am trying to do Post Goods Issue and getting this error: Class type does not exist
    When double click on the error, it shows it is a message no vk662.
    Any help to resolve it is appreciated. Thanks in advance.
    -Sri

    Sri
    There is a problem in batch determination.
    The batch you assigned to the material does not have a class or if it has a class, that class does not exist.
    Display the batch from the delivery item  using MSC3N and go into the Classification tab. You should have a class of class type 22.  See if that class exists in CL03 and its status in basic data tab. Work on these lines and revert.
    Hope this helps.

  • Error while doing Goods receipt for process order. Error code: "BS027"

    I am getting error while doing GR for a day whereas previous day(s) GR is already done and also 2 days post that day are also done successfully.
    Error :  ""Goods receipt for prodn. order" is not allowed (ORD XX-CEMTSAL) " (XX = First two characters of plant code)
    Error code: BS027.
    Thanks to all in advance.

    Hello,
    This issue would occur when you want to post a confirmation for a production order. The error message is generated if you wanted to post a backflush for a component and if this component was assigned to a sales order stock. The sales order itself was assigned to a work breakdown structure element which should be debited with the actual costs. However, the business transaction 'Confirm' is not permitted for a work breakdown structure.
    Please look into SAP Note 62367 and 64370
    Hope the information is helpful
    regards

  • Inter Company -Error in Post Goods Issue

    Dear Experts,
    I have developed new intercompany process between selling company & supplying company to customer. I have created sales order and delivery order. After delivery, am able to to PGI. If i check the Post goods issue document number accounting documents, supposed to take 0020 (selling company code) but its taking some different company conde. we never user that company code for intercompany scenarion. Vould you please tell me...why its taking different company code and how its taking wat we have to do. pls suggest me.  and let me know what are the steps involved during PGI (bcoz PGI accounting entries are automatic)
    Thanks & Regards

    Dear Murali,
    I have checked as per ur suggestions, every things is correct but why it is asking different company code. Actualy our intercompany process between 0010 to 0020. 0010 is the supplying company and 0020 is the selling company. i have assigned 0020 s.org to 0020....config side everything is ok ...i never maintain 0315...but when am doing PGI its getting error                                                                               
    No accts maintained for company code clearing between comp.cds 0010 and 0315.
    Menas here for  acoount clearing between 2 company codes its taking another company code istead of 0020. If its take 0020 i wont get help bcoz we maintained account clearing between 2 company codes.
    Please suggest me
    Thanks & regards
    VS

Maybe you are looking for