Sold-to party 1000003 and sales area PECC/10/02 (for ZWEB) are incompatible
Hello,
We're configuring SAP CRM 7.0 ISA with ERP Sales Order.
After login into ERP webshop, the system shows the error:
"Sold-to party 1000003 and sales area PECC/10/02 (for ZWEB) are incompatible"
I've already checked the following:
1) In Shopadmin: Combination of sales Area and Doc type in Webshop- IT's OK;
2) In CRM System: Catalog used has the right sales area combination- IT's OK;
3) In ECC System: If that document (ZWEB) is alowed to that sales area- IT's OK;
Does anyone can help with that??
Thanks & Regards,
Paulo Pela
Hello Developer,
Yes, I've checked the combinations of webshop(In Shopadmin) and Product Catalog.(Sales Area)
All of them are compatible.
Hey DJ,
When you say: u201Cthe first entry maintained in the USAPPLREF tableu201Du2026.in our case, there are 2 entries for my user (PPELA3). The first one is for object type BUS1006001 and object key nr° 23263-my contact person, linked to sold-to nr° 1000003), which is the employee that I 've created in the ISAUSERADMIN.
The second entry is with object type KNA1 with object key nr° 1000003 (which is the sold-to).
Those are the only entries for my user in this table.
Does this sequence have the influence described by you? Is that what you want to say?
Other point: Does the REFERENCE CUSTOMER is important for the B2B scenario? (Our case) Since I thought it was important just for B2C scenarios, It was the same number in SHOPADMIN Webshop creation.
In the meantime, I will create a new reference customer and change the webshop parameters.
Thanks for your inputs.
Regards,
Paulo Pela
Similar Messages
-
Program terminated error after entering sold to party no. in sales order
hello friends,
can any help me, i was doing the topic of user exit for pre-defined sold to party using v45a0002 in cmod and i wrote a program for include 'if sy-uname= 'sapuser'.
message e000(0) with ' you are not authorised to create so'
endif
while activating i got error msg 'The last statement is not complete (period missing)." & i have saved inspite error
after i tried create a order
program terminated error after entering sold to party no. in sales order
so i have deactivated the project created in cmod & deleted the project inspite i am getting the program terminated error
i am sending total error plz reply quickly urgent friends
Runtime Errors SYNTAX_ERROR
Date and Time 19.04.2008 17:51:58
ShrtText
Syntax error in program "SAPLXVVA ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLVKMP" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLXVVA ", the following syntax error occurred
in the Include "ZXVVAU04 " in line 5:
"The last statement is not complete (period missing)."
Author and last person to change the Include are:
Author "SAPUSER "
Last changed by "SAPUSER "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLXVVA ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
In program "SAPLXVVA ", the following syntax error occurred:
"The last statement is not complete (period missing)."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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....... "mtpl7"
Network address.......... "192.100.10.1"
Operating system......... "Windows NT"
Release.................. "5.1"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "MTPL7"
Database type............ "ORACLE"
Database name............ "ERP"
Database owner........... "SAPERP"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Nov 4 2004 23:26:03"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "43"
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....................... 8362368
Heap..................... 0
Page..................... 122880
MM Used.................. 4229224
MM Free.................. 995472
SAP Release.............. "640"
User and Transaction
Client.............. 800
User................ "SAPUSER"
Language key........ "E"
Transaction......... "VA01 "
Program............. "SAPLVKMP"
Screen.............. "SAPMV45A 4701"
Screen line......... 16
Information on where terminated
The termination occurred in the ABAP program "SAPLVKMP" in
"SD_DETERMINE_KKBER".
The main program was "SAPMV45A ".
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
4
SY-LSIND
0
SY-PAGNO
1
SY-LINNO
8
SY-COLNO
1
SY-PFKEY
U
SY-UCOMM
SY-TITLE
Create Standard Order kb: Overview
SY-MSGTY
E
SY-MSGID
VP
SY-MSGNO
106
SY-MSGV1
BUS2032
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
13 FUNCTION SAPLVKMP LVKMPU41 91
SD_DETERMINE_KKBER
12 FUNCTION SAPLVKMP LVKMPU41 91
SD_DETERMINE_KKBER
11 FUNCTION SAPLV09B LV09BU30 148
SD_PCHECK_PAYER_IN_CREDITAREA
10 FUNCTION SAPLV09B LV09BU26 296
SD_PARTNER_EXECUTE_CHECKS
9 FUNCTION SAPLV09B LV09BU25 57
SD_PARTNER_CHECK_BEFORE
8 FUNCTION SAPLV09A LV09AU26 342
SD_PARTNER_SINGLE_MODIFY
7 FORM SAPLV09A LV09AF39 176
PARTNER_SELECTION
6 FUNCTION SAPLV09A LV09AU29 820
SD_PARTNER_DETERMINATION
5 FUNCTION SAPLV05E LV05EU01 654
VIEW_KUAGV
4 FORM SAPMV45A MV45AF0K_KUAGV_SELECT 40
KUAGV_SELECT
3 FORM SAPMV45A MV45AF0A_AUFTRAGGEBER_PRUEFEN 46
AUFTRAGGEBER_PRUEFEN
2 FORM SAPMV45A MV45AF0K_KUNDEN_PRUEFEN 454
KUNDEN_PRUEFEN
1 MODULE (PAI) SAPMV45A MV45AI0K_KUNDEN_PRUEFEN 15
KUNDEN_PRUEFEN
Chosen variables
Name
Val.
No. 13 Ty. FUNCTION
Name SD_DETERMINE_KKBER
I_KKBER_KNVV
2222
0000
I_KKBER_T001
8888
3333
8888
I_KKBER_TVTA
2222
0000
I_KUNNR
7000000000
3333333333
7000000000
I_SPART
SM
54
3D
I_VKORG
T000
5333
4000
I_VTWEG
S4
53
34
XVBAK
00000000000000 000000000000000000000000 00000000
2222222222222333333333333332222222222223333333333333333333333332222222223333333322222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
E_KNVV_FLG
2
0
RC
0
0000
0000
XVBKD[]
Table[initial]
XVBPA[]
Table IT_1743[2x542]
FUNCTION=SD_PCHECK_PAYER_IN_CREDITAREADATA=LVT_CREDIT_XVBPA
Table reference: 275
TABH+ 0(20) = 70A2883B388BC43B0000000013010000CF060000
TABH+ 20(20) = 020000001E020000FFFFFFFF04910100D82F0000
TABH+ 40( 8) = 02000000C1248400
store = 0x70A2883B
ext1 = 0x388BC43B
shmId = 0 (0x00000000)
id = 275 (0x13010000)
label = 1743 (0xCF060000)
fill = 2 (0x02000000)
leng = 542 (0x1E020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000209
occu = 2 (0x02000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x28C1883B
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2 (0x02000000)
lineAlloc = 2 (0x02000000)
store_id = 690 (0xB2020000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
hsdir = 0x00000000
ext2 = 0x28A4883B
>>>>> 2nd level extension part <<<<<
tabhBack = 0x109C883B
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
I_KKBER
2222
0000
FCODE_KOMM_LIEF_MENGE_SICH
MOD2
44432222222222222222
DF420000000000000000
SYST-REPID
SAPLVKMP
5454544522222222222222222222222222222222
310C6BD000000000000000000000000000000000
%_SPACE
2
0
FCODE_KONFIGURATION1
POKO
54442222222222222222
0FBF0000000000000000
CREDIT_CHECK
2222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000
SY-REPID
SAPLVKMP
5454544522222222222222222222222222222222
310C6BD000000000000000000000000000000000
SAV_BUKRS
SS00
5533
3300
CHAR_
2
0
%_DUMMY$$
2222
0000
AUTOMO_VOLVO
08
33
08
SPACE
2
0
FCODE_ABRUF_GENERIEREN
PABG
54442222222222222222
01270000000000000000
XVBRK
00000000 0000000
2222222222222222222222222222222222222222222222223333333322222222223333333222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
KOPGR_LIEFERPLAN
LL
4422
CC00
FCODE_ZUSAETZE_FAB
PFZU
54552222222222222222
06A50000000000000000
FCODE_REPARATUR
PREP
55452222222222222222
02500000000000000000
XVBKD
000000 #####0000000000 ####
2222222222222333333222222222222222222222222222222222222222222222222200000333333333322222220000
000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000
FCODE_GEFAHRGUT
KGGP
44452222222222222222
B7700000000000000000
I_KKBER_HELP
2222
0000
T001
800SS00SRIYA TEXTILES HYDERABAD IN INR EINT 10K41 0000050495DE1
3335533554542545544452222222222245445444422222222222222224424452244452334332222223333333333443
800330032991045849C530000000000089452121400000000000000009E09E20059E4010B410000000000050495451
FCODE_STOFFBERICHTE
IEHS
44452222222222222222
95830000000000000000
T001-BUKRS
SS00
5533
3300
No. 12 Ty. FUNCTION
Name SD_DETERMINE_KKBER
I_KKBER_KNVV
2222
0000
I_KKBER_T001
8888
3333
8888
I_KKBER_TVTA
2222
0000
I_KUNNR
7000000000
3333333333
7000000000
I_SPART
SM
54
3D
I_VKORG
T000
5333
4000
I_VTWEG
S4
53
34
XVBAK
00000000000000 000000000000000000000000 00000000
2222222222222333333333333332222222222223333333333333333333333332222222223333333322222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
E_KNVV_FLG
2
0
RC
0
0000
0000
XVBKD[]
Table[initial]
XVBPA[]
Table IT_1743[2x542]
I_KKBER
2222
0000
XVBKD
000000 #####0000000000 ####
2222222222222333333222222222222222222222222222222222222222222222222200000333333333322222220000
000000000000000000000000000000000000000000000000000000000000000000000000C000000000000000000000
I_KKBER_HELP
2222
0000
No. 11 Ty. FUNCTION
Name SD_PCHECK_PAYER_IN_CREDITAREA
FIC_OBJECTKEY
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
FIC_OBJECTTYPE
BUS2032
4553333222
2532032000
FIF_CHECKTYPE
I
4
9
FIF_MSGTYPE
E
4
5
FIF_NRART
KU
45
B5
FIF_PARGR
TA
5422
4100
FIF_PARNR
7000000000
3333333333
7000000000
FIF_PARVW
RG
5422
2700
FIF_POSNR
000000
333333
000000
FIF_RTYPE
0003
3333
0003
FIS_SDORGDATA
T000S4SMZSOR
533353545545222222
4000343DA3F2000000
FRF_MESSAGES
0
0000
0000
FRF_MESSAGE_COUNT
0
0000
0000
LVF_KKBER2
2222
0000
LVF_KUNNR
7000000000
3333333333
7000000000
SYST-REPID
SAPLV09B
5454533422222222222222222222222222222222
310C609200000000000000000000000000000000
LVF_KURGV2
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
FIS_SDORGDATA-SPART
SM
54
3D
FIS_SDORGDATA-VKORG
T000
5333
4000
FIS_SDORGDATA-VTWEG
S4
53
34
%_O_SD_PARTNER_CONTEXT-HEX_0004
1
0
LVT_CREDIT_XVBPA
Table IT_1743[2x542]
LVF_KKBER1
2222
0000
GCS_HERTAB
ABCDEFG
24444444
01234567
%_DUMMY$$
2222
0000
SY-SUBRC
0
0000
0000
LVF_BEFORE_PARVW
2222
0000
No. 10 Ty. FUNCTION
Name SD_PARTNER_EXECUTE_CHECKS
FIC_OBJECTKEY
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
FIC_OBJECTTYPE
BUS2032
4553333222
2532032000
FIF_BEFORE
2
0
FIF_CHECKTYPE
I
4
9
FIF_DIALOG
2
0
FIF_MSGTYPE_TO_EXEC
E
4222
5000
FIF_NRART
KU
45
B5
FIF_PARGR
TA
5422
4100
FIF_PARNR
7000000000
3333333333
7000000000
FIF_PARVW
RG
5422
2700
FIF_POSNR
000000
333333
000000
FIF_RTYPE
0003
3333
0003
FIS_SDORGDATA
T000S4SMZSOR
533353545545222222
4000343DA3F2000000
FRF_MESSAGES
0
0000
0000
FRF_MESSAGE_COUNT
0
0000
0000
LVF_ALL_PREDECESSORS_SUCCEEDED
X
5
8
FALSE
2
0
GS_MARKED_PARTNERS
222222222222
000000000000
LVT_CHECKCALLSTACK
Table IT_1515[21x52]
FUNCTION=SD_PARTNER_EXECUTE_CHECKSDATA=LVT_CHECKCALLSTACK
Table reference: 219
TABH+ 0(20) = E8C3863B0000000000000000DB000000EB050000
TABH+ 20(20) = 1500000034000000F00000000491010058090000
TABH+ 40( 8) = 15000000C1248000
store = 0xE8C3863B
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 219 (0xDB000000)
label = 1515 (0xEB050000)
fill = 21 (0x15000000)
leng = 52 (0x34000000)
loop = 240 (0xF0000000)
xtyp = TYPE#000033
occu = 21 (0x15000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x90BF863B
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 21 (0x15000000)
lineAlloc = 21 (0x15000000)
store_id = 595 (0x53020000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LVS_CHECKCALLSTACK_WA
80000018BUS2030 SD_PCHECK_PAYER_IN_CREDITAREA XX
3333333345533332225455444445545455445454445454422255
80000018253203000034F03853BF01952F9EF325494125100088
GT_MARKED_FOR_DEL_PARTNERS
Table[initial]
LVS_CHECKCALLSTACK_WA-FUNCNAME
SD_PCHECK_PAYER_IN_CREDITAREA
545544444554545544545444545442
34F03853BF01952F9EF32549412510
GC_NO_ACTION
2
0
GC_NEW_PARTNER
I
4
9
GVC_PARTNER_CONTEXT
CONTEXT_X_SD_PARTNER_CONTEXT fò####################################################
44454555555455455445544454552222222222226F0000000000000000000000000000000000000000000000000000
3FE4584F8F34F0124E52F3FE4584000000000000620000000000000000000000000000000000000000000000000000
GC_ERROR
E
4
5
GC_PROCESSMODE_DIALOG
D
4
4
LVF_MSGTYP
E
4
5
BUFFER_FULL_FILLED
F
4
6
POS_NUL
000000
333333
000000
BUFFER_PARTITIAL_FILLED
P
5
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GCS_PARTNER_ROLETYPES
0001000200030004000500060007000800090010001100120013NONE
33333333333333333333333333333333333333333333333333334444
0001000200030004000500060007000800090010001100120013EFE5
GCS_PARTNER_TYPE
KUAPLIPE
45454454
B510C905
LVF_RTYPE
0003
3333
0003
GCS_PARTNER_CALL_BACK_EVENTS
CHANGE DELETE NEW
444444222244445422224452222222
381E75000045C5450000E570000000
%_PRINT
000 0 ##
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GCF_INITIAL_PARTNER
0
32
00
GCF_CALLER_TRANSPORT
T
5
4
TPACHECKRELATION
0000000000
2223333333333
0000000000000
GC_APPL_LOG
SDBFPD
54445422222222222222
34260400000000000000
SY-REPID
SAPLV09B
5454533422222222222222222222222222222222
310C609200000000000000000000000000000000
GVC_PARTNER_CONTEXT-B0007-PARVW
RG
54
27
No. 9 Ty. FUNCTION
Name SD_PARTNER_CHECK_BEFORE
FIC_OBJECTKEY
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
FIC_OBJECTTYPE
BUS2032
4553333222
2532032000
FIF_BEFORE
2
0
FIF_CHECKTYPE
I
4
9
FIF_DIALOG
2
0
FIF_NRART
KU
45
B5
FIF_PARGR
TA
5422
4100
FIF_PARNR
7000000000
3333333333
7000000000
FIF_PARVW
RG
5422
2700
FIF_POSNR
000000
333333
000000
FIF_RTYPE
0003
3333
0003
FIS_SDORGDATA
T000S4SMZSOR
533353545545222222
4000343DA3F2000000
FRF_MESSAGES
0
0000
0000
FRF_MESSAGE_COUNT
0
0000
0000
LS_STATISTICS
########################4 ################
00000000000000000000000032220000000000000000
00000000000000000000000040000000000000000000
No. 8 Ty. FUNCTION
Name SD_PARTNER_SINGLE_MODIFY
FIC_OBJECTKEY
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
FIC_OBJECTTYPE
BUS2032
4553333222
2532032000
FIF_BOKRE
2
0
FIF_CLEAR_APPL_LOG
X
5
8
FIF_DIALOG
2
0
FIF_HARD_DELETION
2
0
FIF_HISTUNR
00
33
00
FIF_HZUOR
00
33
00
FIF_INITIAL_VALUE
X
5
8
FIF_KNREF_PARNR
2222222222
0000000000
FIF_KUNNR_NEW
7000000000
3333333333
7000000000
FIF_KUNNR_OLD
2222222222
0000000000
FIF_LISTPROCESSING
2
0
FIF_MANUAL_ADDRESS
2222222222
0000000000
FIF_MANUAL_ADDRESS_ORIGIN
2
0
FIF_NO_CPD_DIALOG
2
0
FIF_NO_DIALOG
2
0
FIF_NO_MESSAGES
2
0
FIF_PARGR
TA
5422
4100
FIF_PARTIAL_NEW_DETERMINATION
2
0
FIF_PARVW
RG
5422
2700
FIF_POSNR
000000
333333
000000
FIF_PRFRE
2
0
FIF_VKORG
2222
0000
FIS_SDORGDATA
T000S4SMZSOR
533353545545222222
4000343DA3F2000000
FEV_ACTION_DONE
I
4
9
FRF_LOG_COUNT
0
0000
0000
SYST-REPID
SAPLV09A
5454533422222222222222222222222222222222
310C609100000000000000000000000000000000
GVT_LOCAL_CALL_BACK_MEMORY[]
Table[initial]
%_SPACE
2
0
SY-REPID
SAPLV09A
5454533422222222222222222222222222222222
310C609100000000000000000000000000000000
LVF_ACTION_TODO
I
4
9
GC_UPD_PARTNER
U
5
5
%_VIASELSCR
0
4
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GCS_PARTNER_ROLETYPES-SHIP_TO
0002
3333
0002
LVF_NRART
KU
45
B5
LVF_KUNNR_NEW
7000000000
3333333333
7000000000
GCS_ADDRESS_GROUP
SD01CA01
54334433
34013101
GCF_APPL_TABLE_SD
VBUK
5454222222
625B000000
LVF_ROLETYPE
0003
3333
0003
RSJOBINFO
00000000000000 ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LVF_MESSAGE_COUNT
0
0000
0000
%_DUMMY$$
2222
0000
GCF_ADDRESS_TYPE_CONT_PERSON
3
3
3
No. 7 Ty. FORM
Name PARTNER_SELECTION
TVTA
000
222222222222222222222222222222222333222222222222222
000000000000000000000000000000000000000000000000000
TPAER
00
22222222222222332222
00000000000000000000
LVS_XVBPA
000000RG7000000000 0000000000000000000000050510
2222222222222333333543333333333222222222233333333333333333333333333332222222222222222222222222
0000000000000000000277000000000000000000000000000000000000000000505100000000000000000000000000
LVF_PARNR
7000000000
3333333333
7000000000
PIC_OBJECTKEY
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
PIC_OBJECTTYPE
BUS2032
4553333222
2532032000
PIF_NO_DIALOG
2
0
PIF_PARGR
TA
5422
4100
LVF_PARVW
RG
5422
2700
PIF_POSNRHi Kartik,
Could you please be more clearer as to how do you want me to proceed so that this syntax error stops bothering me while creating a standard order thru TCode VA01.Also what do you mean by "well comment the code in the include and activate the include"
I created a projet in CMOD and than added the enhancement V45A0002.The components shown as EXIT_SAPMV45A_002(Predefined sold to party when making the standard order),i double click on the exit and entered into the function module.After that i double clicked on the include ZXVVZU04 and entered in and wrote E_KUNNR=100171
While activating i got error msg 'The last statement is not complete (period missing)." & i have saved inspite the error .After that i tried to create a order and program terminated error came after entering sold to party no. in sales order
so now i have deactivated the project which i created in CMOD & deleted the project also inspite of this i am getting the program terminated error while making the order
I would be great ful if somebody helps me *** out of this syntax error.
Thanks
Rishi -
Change the Sold to Party(SP) in sales order in change mode
Hi,
Is it possible to change the Sold to Party(SP) in sales order in change mode?
If yes then How??
Regards
SomnathHi somnath,
It is very much possible to change the sold-to-party in the change mode of Sales order(VA02).
Goto VA02-->enter the sale order number.
Press enter.
In the overview screen if you change the sold-to-party then every thing will be redetermined(Taxes and pricing procedure etc...).These will be determined from CMr etc.
You cannot change the sold-to-party at the partners tab that is present in the Header details.
It will be greyed out.
If you change the sold-to-party at the overview screen as suggested earlier it will not apply to the item.
You are also going to see this message while changing.
And finally save the document.
Regards,
Krishna. -
Default sold to party coming in Sales order
Hi,
Whenever i am trying to create sales order the system automatically purpose a default number in the sold to party field.And there is no such customer master record maintained for this number.After deleting this number then i can able to create sales order.
How to resolve it??
Regards
JyotiHi
i think there is a user exit so that u r getting default sold to party
It seems user exit V45A0002 is applied
Go to transaction CMOD
Create a project called ZVA01
Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document.
Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed
Press Save Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = ''.
If there is any value After E_KUNNR remove it
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder.
OR ELSE YOU CAN DEACTIVATE THE USER EXIT
regards -
Report for Sold to Party code against Sales order number
Hi,
Is there any standard report to take out the Sold to Party code against Sales order number as i have the sales order number.
I don't want to use Tables ,so pls tell standard report if any.Dear Monty garg.
You can use u201CVA05Nu201D to find the sales orders which have been created against for the particular customer/sold to party.
Please let me know if any further clarifications pertinent to this.
Thanks&Regards
Raghu.k -
Mutiple sold to party in one sales order???
Hi,
Is it possible for one sales order have mutiple sold-to party???
If yes, how to do the split when in billing process for those mutiple sold-to parties?
Thank you.Hoo laa,
Do the following
In Customizing for Sales and Distribution, choose Sales > Sales Documents > Scheduling Agreements with Delivery Schedules > Maintain planning delivery sched. instruct./splitting rules > Maintain Delivery Schedule Splitting Rules.
Enter a name for your splitting rule.
Enter a split share in the weekdays that you require for the forecast delivery schedule split.
Define how the system reacts when schedule lines falls on a holiday.
Specify how the system rounds schedule line quantities when generating a planning delivery schedule.
Assign splitting rule ranges to an instruction.
Choose Sales > Sales Documents >Scheduling Agreements with Delivery Schedules > Maintain planning delivery sched. instruct./splitting rules > Assign Delivery Schedule Splitting Rules.
In the dialog box, specify for which instruction you are entering a splitting rule. Then enter a splitting rule and specify its ranges in weeks or months. -
How to validate Sold to party while creating sales order
Hi All,
I need to validate the sold to party which is entered when a order is created.
I able to read the Partner no using the FM u2018CRM_ORDER_READ_OWu2019, but how can I check if this partner number has u2018sold to partyu2019 function assigned.
Thanks & Regards
ShanthiHi Shanti,
There is a little twist in the validation that you intend to do to meet your business requirement. I will provide you with the Sap help link also. Have a look at this and you will understand the same.
[Partner Function|http://help.sap.com/saphelp_sm40/helpdata/EN/3c/92eceb484a11d5980800a0c9306667/content.htm] - Come to very end. Here there is a pictorial representation of how you can map a Partner function with the Business Partner Master Data. The system also maps in the similar way.
The Database tables which might be of help to you are BUT050 - Business Partner Relationship Category, CRMC_PARTNER_PFT - Definition of Partner Function Types. The rest you need to follow your own logic. I guess this will be enough to help you to get started. Let me know if you need any more inputs.
Hope this helps.
Thanks,
Samantak. -
"sold-to party" role "sales area"
Hi,
I'm working at VAR Solution Manager 7.0 SP17.
When I create a support message from satelllite system or workcenter this support message is created successfully but when I open it at crm_dno_monitor I get two errors:
Pricing data for partner 323 could not be read.
Enter a Currency
About detail error:
Diagnosis
The attempt to read the pricing data for the current, valid business partner from the customer master was unsuccessful.
The access was carried out with sales organization 'O 50000721', distribution channel '' and division ''
If you have maintained a sales area conversion in R/3 that must be loaded per download into the CRM System (tables SMOTVTA and SMOTVKOS), this sales area is converted before the actual access.
System Response
The document is incorrect until the pricing data can be determined.
Procedure
The pricing view is probably missing for your business partner in the customer master. Maintain this data. To do this, you can call up transaction BP for maintaining the business partner. In the locator select your business partner and load it by double-clicking. Choose the "sold-to party" role. Press the "sales area" button and choose the sales area given above. Maintain the incorrect data in the billing data screen.
I know the error reason but I don't know how to solve it. About errors:
BP 323 is the sold-to party so if I go to TA bp->323->sold-to party role->button "sales area data" -> Sales area->Sales Organization any value appears. The same to Distribution Channel field
I know that this error is generated by ppoma_crm configuration so at this TA my conf is:
GRUPOTEC(organizational unit)
tab function->checkbox sales->checked Sales Organization
tab function->checkbox service->checked Service Organization
tab attributes->checked Obj. Permitted in Determination
tab attributes->country->ES
Check consistency->green
GENERAL(organizational unit)
tab function->service->local->checked service team
tab attributes-> sales -> NO checked Obj. Permitted in Determination
tab attributes-> service -> checked Obj. Permitted in Determination
Check consistency->green
GENERAL(manager)
tab attributes-> service -> checked Obj. Permitted in Determination
Check consistency->green
Please could you help me?
Thanks and Regards.
RaulHi Prakhar,
I've checked this parameters and it contains values
spro->CRM->master data->org management->Division Settings->Define Divisions:
Division Description
00 Product Division 00
01 Product Division 01
10 Product Division 10
20 Product Division 20
spro->CRM->master data->org management->Organizational Data for Sales Scenario->Define Distribution Channels
Dist. Chan. Description
01 Distribution channel 01
spro->CRM->master data->org management->Organizational Data for Sales Scenario->Define Combination of Distribution Channel and Division
01 Distribution channel 01 01 Product Division 01
Regards
Raul -
Failing to determine sales area in sales order for many BP's(Sold-To Party)
Hi Experts
In SAP CRM version 4.0, when I enter the Sold-to party (BP) in the sales order transaction, for some it determines the sale area automatically and for most of the BP's it is not determining.
The Determination rule is organizational Model.
The determination rule used is 91000141 (ZORGMAN_RA = Organization based on BP and trans.)
Under Container tab in this determination rule, using simulate Rule resolution button, for some BP, it find the agent with green light when I place a BP in the Container element value field but for many BP's, it shows as No agent found.
Org. data profile used is ZORGPROF_RA (Mandatory are sales Org, Dist. Ch, Sales Off.) and has set the above determination rule.
In the Organizational model, the General attributes are country, currency, dist. Ch & division.
So, Why Org determination is working for some BP and not for all.. I've checked each field in BP transaction comparing those BP where the org detrmination is automatic with those where it is not determining...but not able to find a clue also to trace it.
we are introducting a sales order block in BP (under sales tab) for some specific Sold-To party and in webshop when these Sold-to party are tried to place an order then an error message will show that this "Sold-To party has a sales area block".
To achieve this, first the org determination should work automatically for all BP's otherwise for those BP which cannot detrmine the sales area in the sales order transaction will allow to place order (which should not be in our case)
Can any one throw some light in this case..please do ask if you need more clarification in my question.
Thank & Regards
Pravin BabuHello Maggie
Thanks for your reply.
I found the cause of the failure, in not determining the sales area automatically in sales transaction for some BP's.
It is due to the BP settings, under sales area view, under organization tab, by pressing 'Choose sale area" button, I can see the sales Organization has uncheck for 'sales' but it is check for all others - shipping, billing, partner, status, Organization.
It is due to -> no data mainatined for the BP under Sales tab, after mainatianing it, I can see the check by pressing the 'choose sale area under organization tab.
Now, in Order transaction, the sale area is determined automatically when I enter the BP.
So this was the reason that some BP's was able to determine the sales area automatically but not for others in the sales transaction.
Regards
Pravin
Edited by: Pravin Babu on Jul 14, 2010 3:49 PM -
Sold to party and Ship to party are the same but has different address
Hi,
I have problem here wherein Sales order has the same sold to party and ship to party but they have different address. When the customer master data is changed the sold to party in the sales order is also updated but the ship to party is not updated.
I've checked the table VBPA and I noticed that the value of ship to party VBPA-ADRDA is 'E' (manually enetered).
Is this the reason why the address of ship to party in sales order is not updated whenever the customer master is change?
Another question, how does ship to party entered in sales order manually?
Thanks in advance.Hi,
Please correct me if I have understood the scenario incorrectly which I try to explain below:
Sales order is created where SP and SH both have same address initially and while creating the SO, address of the SH was changed manually by Header>partners>SH
Now master data for that customer is changed for address. As per the standard functionality of SAP, all sales order created for that customer will have new address for SP only.
If address of SH needs to be changed in SO, it has to be done manually by the same way as explained in the above mails.
As far as manually entering the SH in SO is concerned, system will automatcally selects the SH if only one record is available for SH. If you have specified more than one SH, system will give you an option to select one by displaying a pop up.
Please let me know if you find this explanation suitable.
Ravi -
Sold to party field should be editable and non-Editable for diff sales org
Hi,
in creation of SO,i want SP field should be editable for Domestic sales org and Non Editable for Export sales org.
please help on this.Dear Mohanty,
In sales order, for domestic sles SP is editable - It is Normal process.
Non Editable for Export sales org.
In this how user will enter the sold to party while creating sales order.
And did you create export customer classification in Sales org rather Distribution channel.
Regards,
Mani -
How to ATP check when sold to party in sales order is changed?..
Dear SD Gurus,
I have one issue with ATP check in my current project where I need to change the the Sold to party of the sales order for a valid business case. We are using production allocation method for ATP check which reduces the Open PA qty once the sales order is saved.
In the above scenario, once the Sold to party in sales order is changed, it redetermines everything and also goes through a ATP check which is cusing as an issue as it would again reduce the open PA qty for the same items in sales order for which are already taken into account. It would either reduce the open qty or propose the next date if it is no more available on that day.
This is a big issue for us. Also it deleted the texts that are maintained.
Does anyone know how to stop the ATP check in this (main issue) and also if possilble stop the deleteion of texts?
Thank you very much for your help in advance..
BR/
AshutoshHello SAJU,
The ATP check is done automatically when sold to party is changed..the issue is how to stop it? beacause of production allocation , it would be incorrect to reduce the open PA qty once more for the sales order when sold to party is changed. So I would like to stop it. Is there any exit or paramater by which we can stop ATP check?
Thanks for your reply..
BR/
Ashutosh -
In sales order sold to party is non editable mode
Dear Experts ,
I am facing one issue regarding customer code in sales order,my issue is
As we are creating sales order with reference to service order ,when it comes to sales order the sold to party is in non editable field,as we want to give the option for the user to change the sold to party address and save the document,is there any standard process to change the sold to party at sales order level,how to do that,and what will be the effect If i change the sold to party address,soon reply will be more helpful and thankfull.
I have check all the related questions but I cant find related answer for this.Hello,
Sold to Part is non modifiable in SAP Standard.
For changing Customer address you need to change the Sold to Party code in Sales Order.
Just go to partners Tab & double click on Customer Code of required partner & system will open Customer Address in new screen. You can change the address here.
This change will be applicable only to particular Transaction & Customer Master address will not be changed.
Hope this helps,
Thanks,
Jignesh Mehta -
Sold to party and ship to address is different
Dear Experts,
Sold to party and ship to party is different address but when invoice is happened sold toparty adrees displayed in ship to party
how i can make the changes for ship to party kindly help me in this regards
Thanks a
BasavarajHi,
This is what you needs to do.
Create your Sold to Party "A" using the Account Group "Sold to Party" from Tx: XD01
Then Create your Ship to Party "B" using the Account Group "Ship to Party" from Tx: XD01
Then go to you Sold to Party using Tx: XD02
Go to Sales area data / Partner tab
Add your Ship to Party "B" there with Partner Function "Ship to Party"
Save
Now create a sales order from Sold to Party "A"
Enter Sold to Party "A" and press enter
You will get a pop up to select relevant Ship to Party for the Sales Order Header level with "A" or "B"
Select relevant one at there.
If you select "B" at the header, same will get copied to all line items later. Else you can select "A" and then change only the relevant line item partner to Ship to "B" at Item level as well.
When you create delivery, relevant Ship to will be picked form the line item level.
You can do same for Bill to Party and Payer as well.
Best regards,
Anupa -
Language issue for sold to party in sales order
Hi,
we have a sold to party A which is in china. the address for the same is maintained in local version and inetrnational version while creating customer master for A.
we aslo have a sold to party B, which is in Greece. the address for the same is maintained in local version and inetrnational version while creating customer master for B.
now we logon to sap and the language we select is Italian. we then go to t code Va01, then the first screen shows everything in Italian which is ok. we then enter order type and sales area. we then go to next screen and enter the sold to party A and we press enter. now the issue is the address against A is shown in chinese characters and not Latin ......... why so ??? we need the characters to be shown in latin and not chinese ?
if we make a sales order for sold to party B ( logged into sap in Italian language), then the address appears in Latin and not greece ..so this is ok !
but my question is why this is not happening for sold to party A ??? what settings i need to check in customer master and other settings. In fact how the language management works ??? and how we maintain the local and international version ? . can someone explain by taking my above example and also give possible solution to my question above for sold to party A
regdsHi,
A cutomer displaying address in chinesse, even if you loging through Italian language,
I think reseon for this is you had created customer master in chinesse language,
Kapil
Maybe you are looking for
-
I want to switch my SSD to another MacBook Pro
Hi, I just received a Refurb i7 quad core UMBP. I currently am using a 2009 UMBP with a SSD (yes, it's a non-apple SSD - but I use an app to turn on TRIM). a) So, since all my apps and files are on this SSD already, I want to simply remove it from
-
Contribute error message when trying to embed PDF's
I am trying to insert an embedded PDF as a new webpage on my website. I can get it to work fine and embed the PDF, but then I try to resize the PDF so that when I open the webpage the PDF takes up the whole page and not just a small corner. Any tho
-
OIM Post process event handler when a role is assigned or reovked to User
Hi All, I have written a custom postprocess eventhandler which populates the list of roles assigned to the user in OIM in a Custom UDF. The code is working fine if I have it triggered on any User Profile Modification. See below: +<?xml version='1.0'
-
Problem with internet connect?
Hi, I have installed a Netgear wireless router, which is connected to my eMac by an ethernet cable. I can access the internet through Firefox without a problem, but when I try to check software update or get to the itunes store it says it cannot conn
-
Driver Software not working on windows 8.1
Hi, I have truble with driver software for win 8.1 x86 and x64 on several laptop-models. Right now Im working on a 8570p and 9470m. 9470m: HP Connection Manager (ver. 4.3.8.1) - installs but doesn't work and somtime generates error massages all ower