Posting Goods Error
Hi Experts,
While posting goods in Tcode MB1C I am getting error "Maintain Fiscal Year Variant For Company Code XXXX" and as a result of which unable to post good.
But I have assigned Company code to Fiscal Year Under Financial Accounting in spro.
Plz Help
Hi,
This error occurs as you haven't maintained the "Fiscal year Variant" for company code in question.
You can do this following IMG path: OB29. If you have NewGL active:
Financial Accounting(New)
-> Financial Accounting Global Settings(New)
-> Ledgers
-> Ficial Year and Posting Periods
-> Maintain Fiscal Year Variant (Maintain Shortened Fiscal Year)
You could access SAP library for ERP via:
http://help.sap.com/saphelp_erp2005/helpdata/en/
e1/8e51341a06084de10000009b38f83b/frameset.htm
Hope the above information could help you.
Oscar Diaz
Similar Messages
-
When I Press the Post Goods Issue Button for a delivery in SD the error dump appears.
Runtime Errors MESSAGE_TYPE_X
Date and Time 10/15/2008 06:38:52
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
No RFC destination is defined for SAP Global Trade Services
Long text of error message:
Technical information about the message:
Message class....... "/SAPSLL/PLUGINR3"
Number.............. 002
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMBWL" or "LMBWLU21"
"MB_POST_GOODS_MOVEMENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "biw7sap"
Network address...... "68.88.249.38"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "BIW7SAP"
Database type..... "ORACLE"
Database name..... "ECS"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 20 2007 00:45:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 102
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 26130600
Heap.... 0
Page.... 57344
MM Used. 19070624
MM Free. 785208
User and Transaction
Client.............. 800
User................ "CUSER14"
Language key........ "E"
Transaction......... "VL02N "
Program............. "SAPLMBWL"
Screen.............. "SAPMV50A 1000"
Screen line......... 39
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.
63
Optische Archivierung
64
Spaete Erfassung mit Barcode
65
Redesign of barcode handling -> note 780365
66
PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67
xmkpf-mjahr
68
barcode.
69
70
MOVE-CORRESPONDING xmkpf TO emkpf.
71
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72
EXCEPTIONS
73
error_message = 4.
74
MOVE-CORRESPONDING xmkpf TO emkpf.
75
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76
EXCEPTIONS
77
error_message = 4.
78
IF NOT sy-subrc IS INITIAL.
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
6
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
W0
SY-UCOMM
WABU_T
SY-TITLE
Delivery 80015203 Change: Overview
SY-MSGTY
X
SY-MSGID
/SAPSLL/PLUGINR3
SY-MSGNO
002
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081015
SY-UZEIT
063852
SY-XPROG
SAPLBPFC
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
10 FUNCTION SAPLMBWL LMBWLU21 59
MB_POST_GOODS_MOVEMENT
9 FORM SAPMV50A FV50XF0B_BELEG_SICHERN 769
BELEG_SICHERN_POST
8 FORM SAPMV50A FV50XF0B_BELEG_SICHERN 86
BELEG_SICHERN_01
7 FORM SAPMV50A FV50XF0B_BELEG_SICHERN 16
BELEG_SICHERN
6 FORM SAPMV50A MV50AF0F_FCODE_SICH_OHNE_CHECK 10
FCODE_SICH_OHNE_CHECK
5 FORM SAPMV50A MV50AF0F_FCODE_WABU 11
FCODE_WABU
4 FORM SAPLV00F LV00FF0F 92
FCODE_BEARBEITEN
3 FUNCTION SAPLV00F LV00FU02 44
SCREEN_SEQUENCE_CONTROL
2 FORM SAPMV50A MV50AF0F_FCODE_BEARBEITEN 62
FCODE_BEARBEITEN
1 MODULE (PAI) SAPMV50A MV50AI0F 52
FCODE_BEARBEITEN
Chosen variables
Name
Val.
No. 10 Ty. FUNCTION
Name MB_POST_GOODS_MOVEMENT
XBLNR_SD
0080015203
3333333333
0080015203
0000000000
0000000000
EMKPF
000000000000000000 ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSSA[]
Table IT_589[0x196]
FUNCTION-POOL=MBWLDATA=XMSSA[]
Table reference: 307
TABH+ 0(20) = 00000000200D869300000000330100004D020000
TABH+ 20(20) = 00000000C4000000FFFFFFFF04090300E01B0000
TABH+ 40( 8) = 08000000C1108001
store = 0x00000000
ext1 = 0x200D8693
shmId = 0 (0x00000000)
id = 307 (0x33010000)
label = 589 (0x4D020000)
fill = 0 (0x00000000)
leng = 196 (0xC4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000134
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xD80C8693
>>>>> 2nd level extension part <<<<<
tabhBack = 0x980C8693
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
RRESWK
22222222222
00000000000
00000000000
00000000000
%_SPACE
2
0
0
0
L_MEM_ID
MKPF-XBLNR
4454254445
DB06D82CE2
0000000000
0000000000
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
RNAME
R
52222
20000
00000
00000
SCREEN
BT_UALL
4555444222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
24F51CC000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_RSTRUCT
Table[initial]
XMKPF-XABLN
2222222222
0000000000
0000000000
0000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ODM07M[]
Table[initial]
GT_GOCOMP
000000000000 #### 00000000000000
3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
4
0000
4000
L_ATPCB
22222
00000
00000
00000
XMKPF-MBLNR
4900035075
3333333333
4900035075
0000000000
0000000000
XMKPF-MJAHR
2008
3333
2008
0000
0000
BARCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T003
800WL49AMS XX XXXXXH
3335433445222222222222222222222222225522555554222222
8007C491D3000000000000000000000000008800888888000000
0000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000
KNVV
00000000 000
2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T064B
2222222222222222222222
0000000000000000000000
0000000000000000000000
0000000000000000000000
VGMSEG[]
Table[initial]
No. 9 Ty. FORM
Name BELEG_SICHERN_POST
MAT_AUF_HINWEIS_COPY
2
0
0
0
XLIKP[]
Table IT_392[1x2360]
PROGRAM=SAPMV50ADATA=XLIKP[]
Table reference: 197
TABH+ 0(20) = 082D1E94E0C8119300000000C500000088010000
TABH+ 20(20) = 01000000380900003000000004FC0100D0070000
TABH+ 40( 8) = 04000000C1108001
store = 0x082D1E94
ext1 = 0xE0C81193
shmId = 0 (0x00000000)
id = 197 (0xC5000000)
label = 392 (0x88010000)
fill = 1 (0x01000000)
leng = 2360 (0x38090000)
loop = 48 (0x30000000)
xtyp = TYPE#000027
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x18081E94
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 1541 (0x05060000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0xA87F1B94
collHook = 0x00000000
ext2 = 0x28940F93
>>>>> 2nd level extension part <<<<<
tabhBack = 0x70A22B93
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
XLIKP
8000080015203CUSER14 06580920081014 Z0011000LF X20081016200810152008101420081017200
3333333333333455453322222333333333333332222225333333344222533333333333333333333333333333333333
800008001520335352140000006580920081014000000A0011000C6000820081016200810152008101420081017200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<%_L195>
CVBAP
8000000012132000020T-AS301 T-AS301 0201 Su
3333333333333333333524533322222222222524533322222222222222222222222222222222222222233332222257
80000000121320000204D13301000000000004D1330100000000000000000000000000000000000000002010000035
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
MAT_AUF_HINWEIS_GEPRUEFT
2
0
0
0
<%_L195>-UPDKZ
UPDKZ_DELETE
D
4
4
0
0
IVBPA52_PAGIND
0.0.1.
000
00C
VBUK_KEIN_KREDITCHECK
2
0
0
0
XLIPS[]
Table IT_83[1x3552]
PROGRAM=SAPMV50ADATA=XLIPS[]
Table reference: 50
TABH+ 0(20) = E8F54D93F0282893000000003200000053000000
TABH+ 20(20) = 01000000E00D0000FFFFFFFF0400000080330000
TABH+ 40( 8) = 04000000C1108401
store = 0xE8F54D93
ext1 = 0xF0282893
shmId = 0 (0x00000000)
id = 50 (0x32000000)
label = 83 (0x53000000)
fill = 1 (0x01000000)
leng = 3552 (0xE00D0000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000260
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xD0896993
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 410 (0x9A010000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0xC8402493
collHook = 0x00000000
ext2 = 0x50E41293
>>>>> 2nd level extension part <<<<<
tabhBack = 0xC8532493
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
VBUK_KREDIT_NEUAUFBAU
2
0
0
0
LT_INB_CIFEXT
Table IT_2692[1x476]
PROGRAM=SAPMV50AFORM=BELEG_SICHERN_POSTDATA=LT_INB_CIFEXT
Table reference: 1104
TABH+ 0(20) = C095F993B8301E940000000050040000840A0000
TABH+ 20(20) = 01000000DC010000FFFFFFFF0400000090AC0100
TABH+ 40( 8) = 10000000C1308401
store = 0xC095F993
ext1 = 0xB8301E94
shmId = 0 (0x00000000)
id = 1104 (0x50040000)
label = 2692 (0x840A0000)
fill = 1 (0x01000000)
leng = 476 (0xDC010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#002271
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xF077F993
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 1542 (0x06060000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x70E43294
>>>>> 2nd level extension part <<<<<
tabhBack = 0x70041E94
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
V50AGL-DISPLAY_FROM_ARCHIVE
2
0
0
0
XLIKP-VBELN
0080015203
3333333333
0080015203
0000000000
0000000000
EMKPF
4900035075200800000000000000 ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
4900035075200800000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
VBMUE
2222222222222222222
0000000000000000000
0000000000000000000
0000000000000000000
VBSK
0000000000000000000000#### ####
2222222222222222222222222233333333333333333333330000222000022222222222222222222222222222222222
000000000000000000000000000000000000000000000000000C000000C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PACKDATEN_VERBUCHEN
2
0
0
0
No. 8 Ty. FORM
Name BELEG_SICHERN_01
IF_FINAL_CHECK
2
0
0
0
LF_ONLY_FINAL
2
0
0
0
LF_ONLY_PREPARE
2
0
0
0
LF_FLAG_DOCNUM_NEW
2
0
0
0
CF_SUBRC
0
0000
0000
T683V
22222222222222222222222222222222222
00000000000000000000000000000000000
00000000000000000000000000000000000
00000000000000000000000000000000000
SY-XPROG
SAPLBPFC
5454454422222222222222222222222222222222
310C206300000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
IF_RENUMBER
X
5
8
0
0
SPACE
2
0
0
0
XVBPA_FIRSTIND
0.0.1.
000
00C
SY-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
IF_POST
X
5
8
0
0
SYST-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
XVBPA_AKTIND
0.0.1.
000
00C
No. 7 Ty. FORM
Name BELEG_SICHERN
%_DUMMY$$
2222
0000
0000
0000
IVBPA2KEY
000000
22333333
00000000
00000000
00000000
IV_FINAL_CHECK_DURCHFUEHREN
2
0
0
0
CHARX
X
5
8
0
0
LF_SUBRC
0
0000
0000
No. 6 Ty. FORM
Name FCODE_SICH_OHNE_CHECK
IVBPA1KEY
000000
33333322
00000000
00000000
00000000
T180-AKTYP
V
5
6
0
0
AKTYP-CREATE
H
4
8
0
0
CVBFA
000000 000000 #### #### 00000000000000 0
2222222222222333333222222222233333320000222000022222222333333333333332222222222222222222222223
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000C000000C00000000000000000000000000000000000000000000000
XSDCTRLFLAG
22
00
00
00
SYST
| ######################################T#######################################µ#########XP####
000000000000000000000000000000800000005000000000000000000000000000000000000010B0001000AF550000
0000100000000000000010601000104000000040006050407000000000000000000000000000C0500010300F800300
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000AF000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000BF00000C
GC_FCODE_PODCANC
ABBR
4445222222222222222222222222222222222222222222222222222222222222222222
1222000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
XSDCTRLFLAG-PROTSAVE
2
0
0
0
YES
X
5
8
0
0
GC_FCODE_PODQUIT
PODQ
5445222222222222222222222222222222222222222222222222222222222222222222
0F41000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
PROTOCOLCALLER-SDL
SDL
5442
34C0
0000
0000
GC_FCODE_PODSTOR
PODS
5445222222222222222222222222222222222222222222222222222222222222222222
0F43000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
LIKP-VBELN
0080015203
3333333333
0080015203
0000000000
0000000000
LIPS-POSNR
000010
333333
000010
000000
000000Hi
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.
From the above message I think u need to read the not 385830 in tcode snote.
Thx. -
Error while posting goods receipt
Hi All,
I am getting error message while posting goods receipt.
The error says posting only possible 2007/06.....
Thanks in advance
kumarGo to MMPV give your company code and the period and the fiscal year and execute.
Regards'
Navin -
Error while posting goods in MB1C
Hi All
I am trying post goods mvt type 561 in t-code 'mb1c' . I am geting an error message saying:<b>Field selection for movement type 561 / acct 799999 differs for Vendor goods
movement (014) Message no. M7093. </b> I am sure that there is some FI configuration
is missing. Please guide to setup FI side configuration for this issue.
Thanks
Prasead Khi prasad,
try TCODE:OMWB
and give material number to which u want post goods
in movement type field give 561 and enter
then select account assignments button
next screen select screen layout button
here u can find the difference field selection for the gl acc and mv type so correct them.
definitley this will solve ur problem
thanq
sandhya.
Message was edited by:
sandhya reddy -
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
NadeemUse 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 in post goods receipt of delivery for a cross company return STO
Hi
I created a cross company return STO in ME21N (with returnd indicator). Vendor V001 (DC) and Site F001.
I created a delivery in VL10B. Delivery Type NCR.
I did a Goods Receipt for STO. Movement Type 161. Internally stock in issued from site F001.
I am trying to do a Post Goods Receipt of the Delivery in VL02N and I am getting this error.
Delivery quantity is greater than supplying site stock quantity
Message no. VL900
Supplying site is F001 which has enough stock.
DC has no stock and I amtrying to return stock to DC from store.
How to eradicate this issue?
Thanks and RegardsHi
http://wiki.sdn.sap.com/wiki/display/B1/SAPBusinessOne...ToGo-3.TheBasicsofFinancial+Accounting
http://help.sap.com/saphelp_sbo88/helpdata/en/45/06b9997d720487e10000000a155369/content.htm
kiran -
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
RakeshHi 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 -
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 & RegardsDear 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 -
Hitting error when post goods receipt in MIGO
Dear SAP Gurus and Expert
Kindly advice what config or setting need to be done when the post good receipt in MIGO hit the error of "Acct. 81110140 for trans. /ev. key ANL, is not a control account".
Thank you
Regards
Leonard TanHi
http://wiki.sdn.sap.com/wiki/display/B1/SAPBusinessOne...ToGo-3.TheBasicsofFinancial+Accounting
http://help.sap.com/saphelp_sbo88/helpdata/en/45/06b9997d720487e10000000a155369/content.htm
kiran -
Posting goods receipt in migo getting the error
hi
when posting goods receipt in tc migo getting the error ' check table 169p: entry "cocode" does not exist". What does it mean? what is th e solution for this?Hi,
Use Se12-Enter table name T169Pdisplay---select utilities from menu bar--table entries-create entries--enter your company code and save.
try the entry again.
Regards
Aravind
Assign points if useful -
Cannot post Goods receipt in MIGO Error message"Field Business Area requird
Hai
I am posting Goods Receipt ( MIGO) with Reference to Purchase Order its having 47 Line item material. When i will doing Goods Receipt with rreference to po number its triggered error message in :Message No F5808 Field business Area is a Required field for G/L account 1180 300000 . for only particular line item 47 material shown error..
i checked all the settings in MM Automatic determination And G/L element, field variants, posting keys.. but everything configured profer settings..why particulat materail it shown error? how to resolve this error?Hi Thiru,
A somewhat late aswer, but it might be helpfull for other users with the same problem. You can solve this problem by assigning the division/valuation area to the business area. Follow the path below to execute this:
SPRO - enterprise controlling - Consolidation - Integration: preparation for consolidation - Preparation in the sender system - Further settings for Business Area Consolidation - Materials Management - Assign Division/Valuation Area to Business area.
Under Enterprise structure - Assignment - Logistics General, you will find a similar function. First execute option 1 or 2 here and then execute option 3. This makes it work as well, exept that it will not be recorded in a proper transport. The first option I gave for assigning is properly transportable.
Greetings,
Sjaak van den Berg
Magnus Technology Consultants
Edited by: S. van den Berg on Aug 14, 2009 1:09 PM
Edited by: S. van den Berg on Aug 14, 2009 1:10 PM -
Hi......
There is an error " Update Control of Movement Type is Incorrect (entry 161XX_L_V) when i create Post Goods Receipt.
Need help
ThanksTry maintaining spcial indicators E or Q. It might help.
Regards,
Rohit -
Error during Post Goods Issue of delivery
Hello SD experts,
I have an URGENT problem where users at a particular plant have problems in posting goods issue. I happened last Thursday and I desparately need solution before month end for closing activities.
System would send error msg " All HIM materials require quantity conversion. Maintain item 000010". Transaction code used are VL06O and VL02N. Msg no: 03 012.
Diagnosis
There is an item for the delivery that has not been fully processed. The
quantity conversion calculation has not been made. HIM (Hydrocarbon
Inventory Management) materials require that all quantities for all
units of measure defined in the unit of measure group are calculated by
the QCI (Quantity Conversion Interface).
The problem is, there's no problems in posting the particular material form the same plant before this. When I took a look at the Delivery document, I noticed the "Qty in alt UoM" tab in the Item Details screen is blank whereas there should have data in it. I believe these data is automatically derived from master data. Hence, I suspect the Goods issue problem is due to the missing data .
This problem only happens in one plant, for one material whereas this material is active in many other plants.
Anyone of you guys had the same problem and can share the solution with me?
HELP!!
SurianaPlease check Plant customer master reconsilation account properly maintained or not in XD03 transaction.
-
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,
ShailendraPlease check Plant customer master reconsilation account properly maintained or not in XD03 transaction.
-
Error at the time of Post Goods Issue
Dear All,
I am getting an error when I am doing the post goods issue the error says that Field Selection Movement Type 601 Differs for Business Area.Though we went to the respective table RM07CUFA and rectified the same what could be the cause of this error and why does this happen.
Best Regards
Atul KeshavHi,
The reason for this error is because of field group in movement type and accounts might be differ.
You can check the same as below :
Go to transaction OMWB ---> click on simulation ---> mention plant and material and movement type
and click on account assignments
Now click on check screen layout
Now check for Business area in additional account assignment whether entry is required in movement type and supress in GL accounts.
Changes the fields status then.
This will solve the issue
Maybe you are looking for
-
Hello!! Although I am NOT new to Mac, I have NEVER attempted to edit an SWF file and I'm seeking an EASY way to do so. I think I might be CLOSE but I'm wasting time trying to figure it out so I'm posting here for some help...hopefully!! :-)) I also a
-
Mapping keyboard and mouse keys onto my gamepad
I'm using arch linux x86_64 and I want to map some keyboard and mouse keys onto my gamepad to play games which don't support the gamepad directly. How can I do this?
-
Does anyone know how to recover deleted mailboxes in Mail? An hour ago, I installed the new software from Earthlink and told it to sync with Apple Mail. I ended up with two accounts in Mail, one with my address (the existing one) and another with my
-
Continued Drop-outs--time for re-install?
I previously posted about a problem with drop-outs while running 10 or so tracks of EXS24 instruments (it's a dual-core intel machine, 2 gigs ram running snow leopard)...I was advised to check out several links to articles on the apple website & the
-
I have the iPhone 3GS with fully updated software and iPhoto '09. What i want is to be able to automatically import photos from my iphone to iphoto, organize them into events and delete them from my iphone when they sync, all automatically. Can this