Account determiantion error while doing ml81n.(obyc)issue.
while doing service entry sheet i am getting an error that M8 147 Account determination for entry teca wrx not possible.
i had already assign my gr/ir clearing account against dat valuation class which i am using for my service related p.o.in my company code already valuation group code has assign to plant level.why i am getting this error.if i am keeping valuation class blank and assign g.l account system is taking dat gr/ir clearing account but is temoprary solution reply as soon as possible
Dear,
Usually for service PO there is no need Goods Receipt because service entry sheet is created. Deselect GR-Bsd IV in the purchase order under the invoice tab.
Regards,
Chintan Joshi.
Similar Messages
-
Account dertermination error while doing MIRO for third party PO
Hello,
This is regarding error message while doing MIRO (IR)
There is already a PO in the system with item category S ( Third Party ) &
Acc assignment object u2013 C (Sales order).
For this PO , I could find 10 invoices already posted in the system.
Between when these invoices were posted , there were some changes done to the PO.
But even after those changes , many invoices were posted in the system,
But now , when I try to post the invoice , I am getting the below error message.
the error message is ** Account determination for entry SKPL WRX 0002 _ 1020 not possible** while posting.
Message no. M8147
Diagnosis
The system did not find an account for this transaction. This means that the account determination for key SKPL WRX 0002 _ 1020 is not maintained in MM Customizing (Valuation). The key is made up of:
u2022 Chart of account
u2022 Transaction key (= Posting transaction)
u2022 Valuation grouping code
u2022 Account grouping code
u2022 Valuation class
System Response
The system cannot update a G/L account for this transaction. You cannot post the transaction.
Procedure
Contact your system administrator.
If you have the authorization, check the Account determination in Customizing for Valuation.
Proceed
Note
The relevant posting transaction can be found in Table T030A.
I have checked the entry in OMWD, where valuation grouping code is maintained against the valuation area & company code.
PLEASE SUGGEST ME SOME SOLUTION.
Thanks,
VinothHi Raman,
Yes, still i am getting error.
before when the invoice is posted , there is no error.
there are some 10 invoices posted already , but there are some changes done in the PO , after that they could post two invoices but for the third invoice , i am getting this error.
when the invoive is posted without error , these are the account movements that are hit
Here
441510 is a vendor account
61799410 is a WBS element G/L account
27411000 is a G/L for tax.
What could have pulled out this WRX error (Account determination for entry SKPL WRX 0002 _1020 not possible ) for me????
can u suggest me some solutions.
Thanks,
Vinoth -
HI,
I am facing a serious problem,
I have created a standard service catalog(SSC) and i am using it to do a service purchase order against Cost centre. I have entered all the service data and account assignment in PO level and saved it.
But while doing the service entry sheet and saving it after acceptance. It is shooting arror.
M8 147 :: account assignment RUPA WRX not possible.
can anyone help me out, how to do handle this.
RegardsHi,
the WRX transaction event key is the GR/IR clearing account.
Go to OBYC and double click on the WRX transaction event key, enter your chart of accounts and then make sure that the GL code has been specified for the correct GR/IR clearing account to use (if you have valuation classes switched on then you will need an entry for every valuation class you use, it looks like you have one called RUBA? make an entry for RUBA with the correct GL).
Steve B -
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_BEARBEITENDear 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 -
Error while doing settlement from WBS to P&L Account
Hello
I am trying to do a settlement from WBS to P&L Account(Expense account). In this case, "Dummy" Prof Ctr is getting derived from 0KE5 (we have maintained a dummy prof ctr). We have set the validations to disallow any postings/settlements to dummy prof ctr. Hence I am getting an error while doing settlement.
Now I am maintaning a Prof ctr in my WBS master data. I am unable to understand why system is deriving dummy prof ctr and not the one maintained on WBS master data. The settlements are working fine when I do them against Balance sheet accounts and proper prof ctr is getting derived, which is being maintained on WBS master data. I am getting trouble only while doing settlement to my P&lL i.e. expense accounts.
can anyone throw some light on this?
Thks
SarangDear Sarang,
You have maintained profit center in WBS master which is not updated at the time settlement to FI that what makes you worried. If you are making FI posting and give WBS as an additional account assignment then Profit center in WBS master will be updated. Here in settlement WBS is sender not the receiver so that profit center will not be updated. In settlement receiver (any) is debited and sender (WBS) is credited so this credit entry will be updated in profit center.
To your second query that when you carry out settlement to balance sheet account right profit center is updated then please make sure, that balance sheet account is maintained in 3KEH with profit center or OKB9.
Your P&L account (expense) receives dummy profit center because it is not able to find cost center which can fetch profit center from the master. So, if you can afford, maintain that cost elements (expense account) with profit center in OKB9.
might help you.......................................................... -
Hello Everybody,
I am trying to do MIRO for a Purchase Order.
But I see the following error while doing that -
"G/L account is not defined in chart of accounts 1000".
Can someone tell me whats going wrong and where do I have to check to set the following conditions right for a MIRO posting to be done?
Please help. All the help is appreciated.
Thanks,
Sneha.Hello Sneha singh
In addition to Mr.srinath's suggestions please check whether you have maintained Reconsallation account for your vendor in the Vendor masterdata in XK01 in the company code level
have you maintained properly the OBYC settings (take the help of your MM or FI consultant for this) and also check in OMWD whether the valuation grouping 0001 code is assigned to your plant
Mostly along with Mr.Srinath's suggestions Reconsallation account checkings in the Vendor masterdata in XK01 should solve your issue
Regards
Raja -
Error While doing ABT1N transaction
Hi,
I am facing the below error while doing ABT1N in Asset Accounting.Please help me in fixing this Issue.
Error Message -No depreciation area for receiving the revenue
Message no.AAPO149
Diagnosis
You tried to post a retirement on asset 1000 100007-0.You entered transaction type 300,in which the retirement with revenue indicator is not set
You tried to transfer asset 1000 100007-0.According to transfer variant 0001,none of the areas on the asset uses a transaction type for retirement with revenue
In both of these cases, you are not allowed to enter revenue or make specifications for the determination of revenue.
Proceedure
Check the transfer variant and check your entry
please do the needful
Thanks
SupriyaHello,
You will have a check box for the same.
Double click on transaction type, you will see the check box for revenue.
Otherwise, tomorrow I will get back to you once I am in front of the system.
Regards,
Ravi
Edited by: Ravi Sankar Venna on May 5, 2009 7:53 PM -
Error while doing outbound delivery against Purchase Order
hello
i m getting error while doing Outbound delivery for purchase order as follows
EKPO-SOBKZ=E; EKPO-UMSOK=_; EKPO-KZBWS<>_ EKPO-KZVBR<>E (Note 305582) not supported (check your entry)
Message no. M7146, i m not getting wht will be the reason,
Regards
NISHJPlease go through the note - 305582. It is clearly given the direction.
Symptom
You try to post a goods movement for a stock transport order from the unrestricted-use stock into the sales order stock or project stock.
During the goods issue, the system displays error message M7146 with a text along the lines of "EKPO-SOBKZ=E; EKPO-KZVBR<>E; ... not supported".
Cause and prerequisites
In the goods issue for the stock transport order, the system may have to create a stock in transit which is deconstructed during the goods receipt. If the withdrawal takes place from the special stock, it is clear which is the receiving stock.
However, if the withdrawal is carried out from the unrestricted-use stock ("Collective requirements", controlled by the dependent requirements indicator MARC-SBDKZ in the material master of the issuing plant), this results in the design problem that the control tables of the goods movement do not have any key field for the receiving stock. Therefore, the control for the receiving stock is controlled via the consumption indicator in the account assignment category of the purchase order. The consumption indicator therefore requires a specific default setting (you may have assumed you could change the design of these control tables, however this is not possible).
Using an inappropriate consumption indicator then causes for the goods issue an incorrect or no stock in transit to be created so that the goods receipt fails.
Solution
Implement the program change in accordance with the correction instructions.
Afterwards implement Note 413908 immediately if this is relevant for your release. -
Acccount determination error while doing SES
Hi,
I am getting a error while doing SES i.e.
147 Account determination for entry ICOA FR1 not possible.
Can anybody please guide me how to resolve this.
Thanks in advance.
Regards,
AshishHi,
Use t.code:OBYC, enter chaart of account
Click FR1
In next screen enter Val. Gro. Code, Acct Gro. Code, Valuation class and G/L accounts for Dr & Cr and save.
Note: before that u have save the Rules
How to save Ruls:
OBYC-> enter chart of account-> Click FR1->Click Rules
Select the check box of Debit/Credit in accounts , General modification, Valuation Modification, Valuation class Account are determine based on TAB and save.
Regards, -
Error while doing ABGL Asset Credit Memo
Hi Friends,
I am getting the below error while doing Asset Credit Memo in ABGL. Please help me in fix this issue.
Balance for transaction type group 10 negative for the area 01
Note:In Asset Explorer Fiscal year start Asset value is 98,425.45 and Change is 4768.19. So total Asset value as of now is 1,03,193.64.
Now we are trying to do ABGL with 12,790.23 value (Transaction type is 105). System is giving the above highlighted error.
If we give the amount 4768.19 in ABGL transaction, system is not giving any error. If we give more that that system is giving error.
Why system is giving error even the asset has balance of 1,03,193.64? Please help me on this..
Thanks
SunilHi,
If the asset has been capitalized during earlier years, use ABGF to post credit memo. ABGL is meant for assets capitalized during the year.
Best Regards,
Madhu -
Error while doing "Visulaize Plan"
Hi,
Before i did Visualize plan many times without any problem.Now I am getting error while doing so.
I was able to run "Explain Plan" successfully.
I am on HANA revision 60.
I saved above error log and the log information is given below:
I can identify invalid XML tag <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved> but how to fix this issue?
I gone through various blogs related to Visulaization Plan but not found related to this issue.
<Plan xmlns="http://www.sap.com/ndb/planviz" ID="ID_0" Type="Estimated">
<SQL><![CDATA[SELECT KOKRS, BELNR, PERIO, SUM(MEGBTR)
FROM "_SYS_BIC"."raj/AN_VIZ"
GROUP BY KOKRS, BELNR, PERIO]]></SQL>
<CompileTime>
<Start Unit="us">1401281467643661</Start>
<End Unit="us">1401281467658329</End>
</CompileTime>
<RootRelation ID="ID_0" TypeName="PROJECT" Status="Finished">
<Name>Project</Name>
<ExecutionType>Row Search</ExecutionType>
<Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)]]></Summary>
<Location>hanasp7:30003</Location>
<EstimatedCost>
<Exclusive Unit="us">2.12902e+06</Exclusive>
<Inclusive Unit="us">2.64021e+06</Inclusive>
</EstimatedCost>
<EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
<Details><![CDATA[{"Projected Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)","Project column0":"NString(4, 0) __trex_field_NVarchar3__() ....... [3]:040:<5/7 (16B)>:
/1/ void* \"__rids__\" ....... [0]:NOP:<0/1 (8B)>:
/2/ int32_t(10, 0) const := 0 ....... [1]:LOAD:<3/4 (4B)>:
/3/ int32_t(10, 0) const := 0 ....... [2]:LOAD:<4/5 (4B)>:","Project column1":"NString(10, 0) __trex_field_NVarchar3__() ....... [8]:040:<5/7 (16B)>:
/1/ void* \"__rids__\" ....... [5]:NOP:<0/1 (8B)>:
/2/ int32_t(10, 0) const := 0 ....... [6]:LOAD:<3/4 (4B)>:
/3/ int32_t(10, 0) const := 1 ....... [7]:LOAD:<4/5 (4B)>:","Project column2":"NString(3, 0) __trex_field_NVarchar3__() ....... [13]:040:<5/7 (16B)>:
/1/ void* \"__rids__\" ....... [10]:NOP:<0/1 (8B)>:
/2/ int32_t(10, 0) const := 0 ....... [11]:LOAD:<3/4 (4B)>:
/3/ int32_t(10, 0) const := 2 ....... [12]:LOAD:<4/5 (4B)>:","Project column3":"Decimal(18, 3) __typecast__() ....... [23]:076:<10/12 (16B)>:
/1/ Fixed16(18, 3) __trex_field_Fixed16__() ....... [19]:043:<6/8 (16B)>:
/1/ void* \"__rids__\" ....... [15]:NOP:<0/1 (8B)>:
/2/ int32_t(10, 0) const := 0 ....... [16]:LOAD:<3/4 (4B)>:
/3/ int32_t(10, 0) const := 3 ....... [17]:LOAD:<4/5 (4B)>:
/4/ int32_t(10, 0) const := 3 ....... [18]:LOAD:<5/6 (4B)>:
/2/ int32_t(10, 0) const := 18 ....... [21]:LOAD:<8/9 (4B)>:
/3/ int32_t(10, 0) const := 3 ....... [22]:LOAD:<9/10 (4B)>:"}]]></Details>
<Child ID="ID_8" >
</Child>
</RootRelation>
<Relation ID="ID_8" TypeName="TREX_SEARCH" Status="Finished">
<Name>Column Search</Name>
<ExecutionType>Column Search</ExecutionType>
<Summary><![CDATA[Aggregation on a single table]]></Summary>
<Location>hanasp7:30003</Location>
<EstimatedCost>
<Exclusive Unit="us">511194</Exclusive>
<Inclusive Unit="us">511194</Inclusive>
</EstimatedCost>
<EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
<TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved>
<LogicalPlan ID="ID_11" Type="Estimated">
<RootRelation ID="ID_11" TypeName="PROJECT" Status="Finished">
<Name>Project</Name>
<EstimatedCost>
<Exclusive Unit="us">0</Exclusive>
<Inclusive Unit="us">0</Inclusive>
</EstimatedCost>
<EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
<Child ID="ID_12" >
</Child>
</RootRelation>
<Relation ID="ID_12" TypeName="GROUP_BY" Status="Finished">
<Name>Aggregation</Name>
<Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO\nSUM(raj/AN_VIZ.MEGBTR)]]></Summary>
<EstimatedCost>
<Exclusive Unit="us">0</Exclusive>
<Inclusive Unit="us">0</Inclusive>
</EstimatedCost>
<EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
<Details><![CDATA[{"Grouping Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO","Aggregation Cols":"SUM(raj/AN_VIZ.MEGBTR)"}]]></Details>
<Child ID="ID_13" >
</Child>
</Relation>
<Relation ID="ID_13" TypeName="TABLE" Status="Finished">
<Name>Column View</Name>
<Schema><![CDATA[_SYS_BIC]]></Schema>
<ObjectName><![CDATA[raj/AN_VIZ]]></ObjectName>
<Location>hanasp7:30003</Location>
<EstimatedCost>
<Exclusive Unit="us">0</Exclusive>
<Inclusive Unit="us">0</Inclusive>
</EstimatedCost>
<EstimatedOutputCardinality>682404</EstimatedOutputCardinality>
</Relation>
</LogicalPlan>
</Relation>
</Plan>
Regards
RajHi,
To solve this you must update your studio. In lower studio versions (PlanViz) does not allow "unknown" XML tags sent by higher version servers. A fix for this issue was made so that PlanViz parser can simply skip unknown tags.
Please go to version 74, if possible.
Regards,
Michael -
Error while doing GR for scheduling aggrement
Dear Experts,
We are facing error while doing GR for scheduling aggrement.
we have done the following steps.
1) Scheduling aggreement in ME31L
2) Released in ME35L
3) Mainatined Sch.Agmt Schdule in ME38 for todays and date 200 qty and other line is 800 qty.
When we are trying to do GR in MIGO system is giving the following message.
Document 5500000152 does not contain any selectable items
can I know what I have missed in the above steps.
Please guide me to resolve this.
Regards,
PrasadHi,
Please check Please check if Gr is already done against this document. Also please check whether you have attached SA in the source list with line items.
T-code:ME01
Enter Mat.code & Plant.
In the next screen pl.do the following:
Valid from - commencement date of the SA
Valid to - End date of the SA
Vendor - Vendor on whom the SA is released
POrg - Your purchase organisation
PPL - Leave it blank(This is only for interplant)
OUn - Ordering unit
Agreement - SA number
Item - 1
I hope this will resolve your issue. Thanking you -
Error while doing F-90 Asset Acquisation
Hi,
I am getting the below error while doing F-90 Asset Acquisation scenario. Please help me to fix this issue.
Tax code V1 country IN does not exist in procedure TAXINN
Message no. FF713
Diagnosis
You entered a tax code which is not defined for the country of the company code to be posted to in the tax calculation procedure.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system settings.
To do this, choose Maintain entries (F5).
Check whether the company code is assigned to the correct country and whether the correct tax calculation procedure has been entered for the company code country.
Create a new tax code if necessary.
Caution:
Since it is possible that the tables in question are being updated at a different time on another computer, it can take a certain amount of time for the tax code to be on all local machines in client server architectures after saving the new code.
Thanks
KBHi,
you need to maintain Tax Code A0 & V0 in t.code OBCL t.code.
and also ensure to check whether you have created tax code V1 or not in FTXP t.code. If not, create V1 tax code and assign GL on that in the right Transaction event keys in OB40.
Try.... if not working let me know....
Regards,
MOhan. -
Error while doing File to File Scenario
All,
I am trying a simple file to file scenario - where xi picks up the file from a location and maps the message and dumps it in another location.
I am Getting the below error while doing the same .........
Time Stamp Status Description
2009-03-30 14:30:24 Success Channel Test_send_cc: Send binary file "d:\input\input.xml". Size 203 with QoS EO
2009-03-30 14:30:24 Success Application attempting to send an XI message asynchronously using connection AFW.
2009-03-30 14:30:24 Success Trying to put the message into the send queue.
2009-03-30 14:30:24 Success Message successfully put into the queue.
2009-03-30 14:30:24 Success The application sent the message asynchronously using connection AFW. Returning to application.
2009-03-30 14:30:24 Error Attempt to delete file "d:\input\input.xml" after processing failed. Retry
2009-03-30 14:30:24 Success The message was successfully retrieved from the send queue.
2009-03-30 14:30:24 Success The message status set to DLNG.
*+2009-03-30 14:30:24 Error Transmitting the message to endpoint http://filip:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.*
2009-03-30 14:30:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Mar 30 14:35:24 GMT+05:30 2009.
And i cant see the meesages using the SXMB_MONI trasaction
please help me resolve ths issue
Regards,
Mahesh.
Edited by: mahesh uma on May 3, 2008 2:12 PMHi Uma,
Go through this links::
Hope these links are useful to you..
Urgent: Message not transmitted from AFW to Integration server
Error with huge file
File to JDBC error
Thanks,
Satya Kumar.. -
Hi every one'
i got an error while doing billing
Error :sub transactions in schema Z step 0001 inconsistent,
this error is comming while using transaction eamabi,
the schema is worked properly since i updated a line item for additional TAX,
and we created new sub transactins for additional vat,AND for the sub transactions i have added a new GL account,
and i have added those Sub transactions in the respective field of the rate,
I have maintained properly all the fica setting for the sub trasactions...like ek01 and ek02 and table te305 & tfktvo as well. Dont understand where the setting have been missed..Please let me kow if you come acrosee this kind of situation.
later i have deleted all the line items in tha same schema,and i have given only quanti01 variant
and does not have any vat related line item maintained at schema even though the same error proposed.
regards
BekMsI think you need to ask FICA person to fix the subs, This is not billing or rate error. There must be some config missing in sub's and main. If you give another try with any other subs it should work. This will help you to double check too.
GG
Maybe you are looking for
-
When I try to use safari I get a message that states can not find server Xn--%20%20-1ia0eb092a
-
That's about it. Whenever I try to launch the beta version I get the won't run on this architecture message.
-
Service master and service description
Hi, *Why we are maintain service master ? Why only we don't maintain description in PO* Because account determination possible through material group valuation class. Why we maintain service master? *Regards* *Anil* Edited by: Anil Patil on Feb 9, 20
-
Thank you for considering my question. That is very generous. 8 is rejecting my key code. Support indicates it is a valid code and I need to re install. I did and it is still rejecting. What should I do next.
-
I cannot dial out when I am on E7 with headset - using keypad. Is this a known issue, what a useless piece of hardware if it is... S