Sold to Party Error in VL01n

Hi,
This is my first time here.
I have created my own sales area (1040/ZM/ZM), own cust (146), own material (4919) In IDES and am now trying to create a sales order after confirguring the system.It allows me to save a sales order(sales order no:1000200010 )but when i try doing a VL01n it gives an incompletion log saying sold to party..when i try to complete it nothing come up and i get a msg saying "Required function KAGU is not available here ".i am not able to understand where the problem as it just says sold to party incomplete.I did check and all assignments seem to be in place.
Could someone please tell why i get this error and how to go about resolving it.
Thanks,
Molly.
Edited by: Molly Mandal on May 15, 2008 12:09 AM

Hi Molly,
-->Check the partner determination procedure in the sales document item level also.
-->Check partner functions correct in the sales order header level and item level.
-->Check the incompletion procedure fields in the in icompletion procedure which was assigned to your document type at header level and at item level.
If you foun any unusefull field remove those fields from the Incompletion procedure.
I hope it will help you.
Regards,
Murali.

Similar Messages

URGENT:SC creation: "Enter exactly one partner of type Sold-to Party" ERROR

Hi all,
we have a very urgent problem.
We are migrating to Production environment and in contract and SC creation we get the error:
"Enter exactly one partner of type Sold-to Party".
In Test environment this error never appear.
We are trying to debug without success till now.
SAP SRM 5.0 with ECS.
Thanks
#Bill J.

Hi
We have faced a similar problem in our previous Implementation.
What I recommend you, in the BBP_DOC_CHANGE_BADI Implementation, go into BBP_SC_CHANGE & BBP_CT_CHANGE methods,
and write the following lines..
SORT et_partner by partner_id partner_fct.
DELETE ADJACENT DUPLICATES from et_partner COMPAIRING partner_id partner_fct.
Hope it will help.
Regards
- Atul

Sold-to party error in 'BAPI_SALESORDER_CREATEFROMDAT2'

Hi,
I am using 'BAPI_SALESORDER_CREATEFROMDAT2' and am getting error message 'Please enter sold-to party or ship-to party', Parameter Name - 'SALES_HEADER_IN'.
I am using ECC 6.0.
In the BAPI, import parameter ORDER_HEADER_IN does not have Sold to party.
How do I pass sold to party to the sales order header?
Thanks.

check the below code.
Check below code. I used BAPI_SALESORDER_CREATEFROMDAT2.
Dont forget to call BAPI_TRANSACTION_COMMIT.
          o
                + Order header
x_order_header_in-doc_type = it_file-auart.
x_order_header_in-sales_org = it_file-vkorg.
x_order_header_in-distr_chan = it_file-vtweg.
x_order_header_in-division = it_file-spart.
x_order_header_in-ord_reason = it_file-augru.
x_order_header_in-purch_no_c = it_file-pohead.
          o
                + Partners data
                + Sold to party
it_order_partners-partn_role = 'AG'.
it_order_partners-partn_numb = it_file-soldto.
append it_order_partners.
clear it_order_partners.
          o
                + Ship to party
it_order_partners-partn_role = 'WE'.
it_order_partners-partn_numb = it_file-shipto.
append it_order_partners.
clear it_order_partners.
          o
                + Item Details
it_orders_items_in-itm_number = g_itemno.
it_orders_items_in-material = it_file-matnr.
it_orders_items_in-target_qty = it_file-zmeng.
it_orders_items_in-target_qu = it_file-zieme.
it_orders_items_in-plant = it_file-werks.
append it_orders_items_in.
clear it_orders_items_in.
          o
                + Schedule Lines
it_order_schedules_in-itm_number = g_itemno.
it_order_schedules_in-sched_line = c_0001.
it_order_schedules_in-req_qty = it_file-zmeng.
append it_order_schedules_in.
clear it_order_schedules_in.
Thanks,
Rajesh.

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_POSNR

Hi 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

Error Message while ship to party is not assigned to sold to party in VA01

Hi All,
In VA01, i need to throw an error message while giving a ship to party, which is not assigned to sold to party.
I tried in EXIT_SAPLV09A_001
              EXIT_SAPLV09A_002
              EXIT_SAPLV09A_003
              EXIT_SAPLV09A_004
above user exits, but i couldnt find the solution.
if possible provide with the code.
i appericiate the early response.
Regards,
Kumar.

User exit MV45AFZB, form-routine USEREXIT_CHECK_VBAK.

CRM orders with error "Do not enter a business agreement for sold-to party"

Dear SDN'ler,
after creating orders in SAP CRM via ISA (CRM 4.0) and uploading them to R/3 all orders are created successfully in R/3 but an error message is sent back to SAP CRM in case of ALL orders.
Error message is the following:
"Do not enter a business agreement for sold-to party xyz"
Message no. CRM_BILLING011
Diagnosis
The field "FI-CA active" is not selected for the sold-to party 6000201 in the business master record. Since the business agreement is used in the component FI-CA, excluding the control of processes, it makes sense to enter a business agreement.
Procedure
Delete the entered business agreement.
==> Could someone please give me some more information about the mentioned "business agreement"? Where do I find field "FI-CA active" (in R/3 or CRM customer master data?)?
==> And how can I eliminate this error message for CRM orders in SAP CRM?
Thanks a lot.
Best Regards,
Rainer Gryschka

Please check the customising setting under following path:
SPRO --> Customer Relationship Management --> Master Data --> Business Partner -- > Business Agreement --> Define Basic Settings
Alternatively you may also check following customisation table using SM30 --> CRMC_BUAG_ACTV

Error while converting Ship-to-party to Sold-to-party

Hi,
I need to covert a Ship-to-party to Sold-to-party using transaction XD07. While converting the above i m getting the following error
The planned change is not allowed as the following field
groups would be masked by the new account group
Group                                  Modif group 1
V D315 Shipping                       017 Order combination
When i checked the difference between account groups Sold-to and Ship-to, it was the Order combination field in Shipping tab which was suppressed in Sold-to party and an optional entry in Ship-to-party. because of which i was getting the error while converting a ship-to party to sold to party.
Please help me in transforming the Ship-to-party to Sold-to-party without changing the account groups in OBD2.
Thank you,
Arun.S

Hi
I am not able to convert any partner functions. the system displays the below error for all combinations (SP --> SH, SP --> PY, SH --> SP etc). Below is the error message i got whe i tried to change SP to SH.
The planned change is not allowed as the following field
groups would be masked by the new account group
Group                                  Modif group 1
A D120 Control                        017 Vendor
                                       018 Corporate group
                                       023 Industry
                                       029 Authorization
                                       036 Trading partner
A D130 Payment transactions           030 Bank details
                                       032 Alternative payer account
F D215 Payment transactions           010 Payment methods
                                       011 Alternative payer account
Is there any way to avoid this error and go ahead with the conversion.
Thank you,
Arun.S

Sales Order Error No customer master record exists for sold-to party

Hi,
I am trying to create a sales order in IDES. Unfortunately it is showing me error: No Customer master exists for sold to party. Now I have already checked my assignments, combined sales area in vor1 and vor2. Checked PDP ( In PDP I have creates partner functions as z2, z5, z6, z7). I have also checked in XD02 and XD03 and in partner function tab it shows as maintained. Please help as I am still not able to create it.

Dear Phanikumar,
I am not sure whether we can create a customer for a future date or not.
I might sound absurd but suggested this solution because I had faced a similar issue while I was working on a remotly supported IDES server which I was using for practice purpose.
Now the case was that, I had created some customers few days back, lets say on 01.03.2014 and today the administrator of the server changed the date & time of the system from 11.03.2014 to 11.03.2013 bymistake.
Hence when i was trying to create orders for a customer created on 01.03.2014 i was not able to do so as the system was throwing an error customer does not exist.
I am sorry if I have suggested something awkward or wrong, intention was to provide a solution.
Please correct if I have suggested someting wrong.
Thanks,
Kishor

BDOC Error : Partner function Sold-To Party occurs more often than specified in Customizing

Hi,
I am new to middleware and would like to know how to solve the below error.
My scenario is I am trying to perform an initial download for equipment from ECC to CRM. Most of the blocks get successfully uploaded, but for a few cases I get this error.
CRM_EQ_DMBDOC: Partner function Sold-To Party occurs more often than specified in Customizing
As my block size is 50, I would like to know which entry has this error and how to fix it. Once I fix it do I reprocess the BDOC.
Please advice me how to go about this. Thank you for your time.
Regards,
Dhruv

Hi Willie,
Thanks for your reply.
I applied the Note 1762574 and tried reprocessing the BDOC but it does not get processed.
The other note 1414329 de-implements the change made by the first one, so I did not use it.
Do you have any other suggestion?
Regards,
Dhruv

BDOC Error: A number range is not assigned to account group Sold-to party

Hi Experts,
We have a stuck BDOC for a BP with "ZEmployee" (custom) role in CRM with error as "Fill in Required fields". We knew this is b'cos one of the mandatory field in not maintained in CRM. After maintaining the mandatory field in CRM; we are re-processing the stuck BDOC and again it is getting into the error message with error "A number range is not assigned to account group Sold-to party".
We have checked the number range and grouping configuration both in ECC and CRM. But still not able to identify the gaps. Is there a detailed step-by-step approach which can be taken up to resolve the issue.
Request you quick response.
Thanks,
Chaudh.

Hi Chaudh,
Please find the exact solution here.
http://wiki.sdn.sap.com/wiki/display/CRM/IssuesduringBusinessPartnerreplicationbetweenCRMandERP
Cheers,
Josh

SP ( Sold to Party )is not in table

Hi
This is Srikanth Can Some help me when i am creating a customer master with the account group 0001 after completing all the required fields when want to save the record i am getting an error as Sp Sold to party is not table XXXX like that only for all these SH,BP PY.

Hi,
In VBPA table you will get the PARTNER FUNCTIONS of the SALES DOCUMENT
Goto VBPA table with the VBELN number which is Sales document number , then check the PARVW field for the required Partner function
The Partner functions maintained in the CUSTOMER MASTER are available in KNVP table
There will be difference you can find between these two table if any thing added manually during processing of sales order.
Hope it is clear,
regards,
santosh

How to update Sold-To Party (In ORDER_SAVE BADI)

Hi,
I have a requirement as follows:
In for a Sales Order, In ORDER_SAVE BADI, I have to do validation for Sold-to Party. If validation fails, I need to display an error message and I need to clear the Sold-to Party field, hence user has to select another sold-to party.
Could you please let me know, how can I clear the sold-to party, in ORDER_SAVE BadI. Any FM's to do that?
Thanks,
Sandeep

Hello Sandeep,
why you want to delete the sold-to ? I think its just easier to give a error message in the log, so the users could enter a new sold-to. Within the badi order_save you can prvent saving with exception do_not_save - see note 1519171 for detailed information.
Best regards
Rene

Not able to change the value in 'sold to party' once disabled.

Hi,
I am validating the Business partner entered in the 'sold to party' field while creating a sales order in webclient UI.
The error message pop up as expected but the field becomes disabled. I tried changing the field to editable by setting rv_disabled = 'FALSE' in method GET_I_SOLDTO_NAME.
Now the field is editable but it does not take the new value which i enter. it takes the old value only.
How do i make the field to accept new values?
Thanks in advance.
Regards
Shanthi.

Hi Shanthi,
Just check small config in your Partner determination profile if it helps you:
Path: SPRO->CRM->Partner Processing->Define Partner Determination Procedure-
Open you Partner determination Profile and go in details Sold-to-party partner and Mark Check box Changable to allow to make changes in partner.
Regards,
Dipesh.

Enter a country for partner with type 'Sold-to Party'

Hi
when we try to send Delivery Scheduld to SUS from R/3 thro
Idoc "DELINS" we are getting the following error on the SRM side
An error occured within an XI interface: Exception
occurredE:BBP_PD:147 -Enter a country for partner with type 'Sold-to
Party' E:BBP_PD:428 -Enter exactly one partner of type Sold-to Party
I:R5:553 -'Different country' field contents deleted because identical
to 'Country' E:BS:002 -"Create" is not allowed (SUS Purchase Order
7500000062 ) Programm: CX_BBP_BD_ERROR===============CP; Include:
CX_BBP_BD_ERROR===============CM002; Line: 57
we also tried referring the note 987569, we are on SP as follows
SAP_BASIS SAPKB70010
SRM_PLUS 550 SAPKIBK007
SRM_SERVER 550 SAPKIBKT07
regards,
Anand

Hi
We have faced a similar problem in our previous Implementation.
This is happening in some cases, where the configuartion settingas are not correctly done.
After several tentatives, I managed to solve it activing on the Customizing for Multicompany in one client.
I have accessed to table BBPC_MARKETSET (Status of selection in a market set system) through SM30 and I have just removed the flag "Configure Market Set Procurement".
Also, another option,
check your Enhancements (customer specific) because this is a clear logical error.
The same partner function is added twice, hence it must be deleted programmatically in the enhancement logic.
FYI.. I usually encountered same type of issues in almost every implementation.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Enter Valid Ship-to-party/Sold-to-Party-

Using T.code:J1ILIC01(Deemed Export License), I entered data for Series Group,License Type,License Name,Creation Date,Expiry Date
and Pressed Enter.
I get the error'Enter Valid Ship-to-party/Sold-to-Party'.
I have entered a Valid Ship-to-party/Sold-to-Party and yet the error is present.
How to overcome the error?Please advise.
R.Rao

Pls check the sold to party or ship to party are extended to the concerned sales area for which you are triggering the transaction.
Reward point if it helps.

Sold to Party Error in VL01n

Similar Messages

Maybe you are looking for