Where to enter sold to party in BAPI_SALESORDER_CREATEFROMDAT2

Hi all,
I have a doubt relating to BAPI_SALESORDER_CREATEFROMDAT2 for sales order creation.When am executing this bapi it gives me error to enter the ship to party and sold to party field.I am not getting where to enter the sold to party & ship to party fields.Kindly help.
Thanks
Siji

Hi,
You need to enter in ORDER_PARTNERS (partner data) In that table.
This table parameter is used to enter partners such as sold-to party, or
ship-to party, both at header and item level.
PARTN_ROLE (sold-to party) if sold-to party means 'SP' and Ship-to Party means 'SH'
PARTN_NUMB (Customer number)
Regards,
Dhina..

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_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

Please enter sold-to party or ship-to party USING BAPI_SALESORDER_CREATEFRO

Hello Guys,
Im having a hard time in inserting the data using BAPI_SALESORDER_CREATEFROMDAT2.
The return error is Please enter sold-to party or ship-to party how can i solve this?whats the reason behind this?
The return error are :
 |V4 |219 |Sales document was not changed
 |VP |112 |Please enter sold-to party or ship-to pa
 |V4 |219 |Sales document was not changed
Please help. Will reward points to those helpful one.
Thanks in advance.
aVaDuDz
This is my sample code.
*& Report Z_ORDER_CREATE_SPA_HBR
REPORT z_order_create_spa_hbr.
Parameters
PARAMETERS: p_order LIKE vbak-vbeln.
We need to create a new order number P_New from an existing order
*P_order
linked to an existing quotation P_quote
Tables
TABLES: vbak,
 vbap,
 vbkd. "Sales Document: Business Data
Data and internal table
DATA: order_header_in1 LIKE bapisdhd1.
DATA: order_header_intx LIKE bapisdhd1x.
DATA : salesdocument1 TYPE bapivbeln-vbeln.
DATA : return2 TYPE bapiret2.
DATA: order_partners1 TYPE bapiparnr OCCURS 0 WITH HEADER LINE.
DATA: order_items_in1 TYPE bapisditm OCCURS 0 WITH HEADER LINE.
DATA: order_items_in1x TYPE bapisditmx OCCURS 0 WITH HEADER LINE.
DATA: order_schedules_in1 TYPE bapischdl OCCURS 0 WITH HEADER LINE.
DATA: order_schedules_in1x TYPE bapischdlx OCCURS 0 WITH HEADER LINE.
DATA : return1 TYPE bapiret2 OCCURS 0 WITH HEADER LINE.
START-OF-SELECTION.
PERFORM order_header_in.
PERFORM ORDER_PARTNERS.
PERFORM order_schedules_in.
PERFORM ORDER_ITEMS_IN.
PERFORM call_function.
*& Form call_function
text
--> p1 text
<-- p2 text
FORM call_function .
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 SALESDOCUMENTIN = P_new
 order_header_in = order_header_in1
ORDER_HEADER_INX = order_header_intX
SENDER =
BINARY_RELATIONSHIPTYPE =
INT_NUMBER_ASSIGNMENT =
BEHAVE_WHEN_ERROR =
LOGIC_SWITCH =
TESTRUN =
CONVERT = ' '
IMPORTING
 salesdocument = salesdocument1
TABLES
 return = return1
 order_items_in = order_items_in1
ORDER_ITEMS_INX = ORDER_ITEMS_IN1X
 order_partners = order_partners1
 order_schedules_in = order_schedules_in1
ORDER_SCHEDULES_INX = ORDER_SCHEDULES_IN1X
ORDER_CONDITIONS_IN =
ORDER_CONDITIONS_INX =
ORDER_CFGS_REF =
ORDER_CFGS_INST =
ORDER_CFGS_PART_OF =
ORDER_CFGS_VALUE =
ORDER_CFGS_BLOB =
ORDER_CFGS_VK =
ORDER_CFGS_REFINST =
ORDER_CCARD =
ORDER_TEXT =
ORDER_KEYS =
EXTENSIONIN =
PARTNERADDRESSES =
IF NOT salesdocument1 IS INITIAL.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'
 IMPORTING
 return = return2.
ELSE.
 CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
ENDIF.
ENDFORM. "call_function
*& Form ORDER_HEADER_IN
 text
--> p1 text
<-- p2 text
FORM order_header_in .
order_header_in1-doc_type = 'ZMCH'.
order_header_in1-sales_org = '2000'.
order_header_in1-distr_chan = '20'.
order_header_in1-division = '30'.
order_header_in1-incoterms1 = 'FH'.
order_header_in1-sales_off = '3102'.
order_header_in1-sales_grp = '301'.
order_header_in1-ORD_REASON = 'Cost Center RelevanT'.
order_header_in1-SALES_DIST = '230144'.
order_header_in1-PURCH_DATE = '07/31/2008'.
order_header_in1-PURCH_NO_C = 'UPLOAD2-TEST'.
APPEND order_items_in1.
ENDFORM. " ORDER_HEADER_IN
*& Form order_schedules_in
 text
--> p1 text
<-- p2 text
form order_schedules_in .
order_schedules_in1-req_date = sy-datum + 20.
order_schedules_in1-req_qty = vbap-kwmeng.
APPEND order_schedules_in1.
endform. " order_schedules_in
*& Form ORDER_PARTNERS
 text
--> p1 text
<-- p2 text
form ORDER_PARTNERS .
order_partners1-partn_role = 'PH'.
order_partners1-partn_numb = '1200038'.
 APPEND order_partners1.
endform. " ORDER_PARTNERS
*& Form ORDER_ITEMS_IN
 text
--> p1 text
<-- p2 text
form ORDER_ITEMS_IN .
order_items_in1-ITM_NUMBER = 1.
order_items_in1-MATERIAL ='300040'.
order_items_in1-TARGET_QTY = 1.
order_items_in1-SALES_UNIT = 'MON'.
APPEND order_items_in1.
endform. " ORDER_ITEMS_IN

Hi AVA MARIE TRINIDAD.
Pass QUOTATION_PARTNERS-ITM_NUMBER = '0000000'.
And pass customers like this.
QUOTATION_PARTNERS-PARTN_NUMB = '1000000'.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = QUOTATION_PARTNERS-PARTN_NUMB
IMPORTING
 OUTPUT = QUOTATION_PARTNERS-PARTN_NUMB

Enter sold-to party debit memo request - credit memo request

Hi Gurus,
I have a scenario here while creating a Debit memo request.
1. I create a Debit memo request with sold-to party 1000
2. I create a Credit memo request with the same sold-to party 1000.
That will be saved,
but when you enter VA02 or VA03 for CMR, a message displays "Enter a Sold-to Party".
So in VA02, I will refill it with Sold-to party 1000, then I can save it. But when I view it again, I will encounter the same message again.
However, if I use a different sold-to party 2000, the CMR will be saved normally, and if you view it via VA02, you will see it is correct (you can see sold-to party 2000).
Why? Cant I use the same sold-to party for DMR to CMR?
Please help....
Ram

Check whether the partner functions are mantained properly for customer 1000. Go to VD01 and maintain.
Regards,
GSL.

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.

Change sold-to party VA02 - XD02 supply company code

Hello everyone
I am in the editing or creation mode of an order (VA01/VA02) and want to change the data of the sold-to party. Therefor i use the 'Display sold-to party'-Icon in the order (F6) to jump to the customer change dialog (XD02).
I get the message "Customer XXXXXXXX has not been created for company code XXXX" and the message is correct, cause in the XD02 dialog the company-code field is initialized with the wrong company code.
For example:
The order is created for sales organization 0300 and company code 0300 and the sold-to party is also created for these. But if i jump to the 'customer change'-Transaction useing the button in the oder (F6) the sales-organization-inputfield is initialized with 0300 and and the 'company code'-field is initialized with 0100.
While debugging i saw that the called transaction XD02 determines the company code useing GET PARAMETER ID 'BUK' FIELD rf02d-bukrs, but the parameter was never set by VA02/VA01.
How can i teach the VA01/VA02 to supply the company code to the called transaction (XD02)?
Kind regards
Markus

Hi,
Pl clarify on the following points:-
1> When you click F6 in sales order after entering sold to party, it will not take you to XD03 screen rather it should be VD03. So how did you get the extension error message?
2> Have you provided any sales org in the initial screen where we usually give order type and sales area? From there sales org would've come in order header. Based on the mapping of sales org to company code in SPRO, company code would ve been determined. (Hope you have one to one mapping)
3> If you have not provided any sales area in the initial screen, it would've prompted you to select the sales area from the available list of sales areas.
Since you are not entering into the company code view of customer from sales order, it is not necessary to supply company code from order to XD02.
Regards,
P Gomatheeswaran

Sold-to Party in SD_SALESDOCUMENT_CREATE

Hi expert,
I got problem during creation Credit note / Debit note (tCode VA01) using Function module SD_SALESDOCUMENT_CREATE. the FM always retunr error message "Please enter sold-to party or ship-to party".
Could you tell me where can I insert value of customer to parameter of this function module ?
Thanks in Advance.

hi
You may be missing ACCOUNT GROUP Parameter . so kindly check for it.
regards
anand kumar

Sold to Party and Ship to party field are in grey out mode in VA01.

Hi Friends,
I am facing a very critical situation, Please help me on this.
While creating the sales order by VA01, the Sold to Party and Ship to Party field are in grey out, so we cannot enter sold to party and ship to party. This is happening for all Order types.
And while checking the existing sales order by VA02, so I found that at Header level and Item level the Partner tab are disable
( mena partner tab are in grey mode,).
But when we click on sold to party field in VA02 it directly moves to partner but all Partner shown in Sales tab.
I have check all the partner function and partner determination configuration.
So can any one help me out in this, how in VA01 sold to party and ship to party field are in grey out mode.
How in VA02 the partner tab are disable.?
Thanks
Irfan Ullah
09370236510

Hai Irfan Ullah,
In Sales - customer
1. Partners are listed (SP,BP,PY, SH)for account group and Partner Determination procedure(TA) is assigned to it
Now for sales order type you need to assign the partner determination process
SPRO
Sales and Distribution
Basic Functions
Partner Determination
Set Up Partner Determination
Execute
Set Up Partner Determination for Sales Document Header
Select TA - standard order from the right side list
and select Partner Determination Procedure Assignment (from left)
Now assign your sales type to Partner determination TA.
Create a SALES order you can find the sold to and ship to are editable.
Regards,
Mani

Sold to Party and Ship to party are in grey out mode in VA01.

Hi Friends,
I am facing a very critical situation, Please help me on this.
While creating the sales order by VA01, the Sold to Party and Ship to Party field are in grey out, so we cannot enter sold to party and ship to party. This is happening for all Order types.
And while checking the existing sales order by VA02, so I found that at Header level and Item level the Partner tab are disable
( mena partner tab are in grey mode,).
But when we click on sold to party field in VA02 it directly moves to partner but all Partner shown in Sales tab.
I have check all the partner function and partner determination configuration.
So can any one help me out in this, how in VA01 sold to party and ship to party field are in grey out mode.
How in VA02 the partner tab are disable.?
Thanks
Irfan Ullah
09370236510
Edited by: Lakshmipathi on Aug 4, 2011 4:30 PM
Thread Locked - Reason Cross Posted

Hai Irfan Ullah,
In Sales - customer
1. Partners are listed (SP,BP,PY, SH)for account group and Partner Determination procedure(TA) is assigned to it
Now for sales order type you need to assign the partner determination process
SPRO
Sales and Distribution
Basic Functions
Partner Determination
Set Up Partner Determination
Execute
Set Up Partner Determination for Sales Document Header
Select TA - standard order from the right side list
and select Partner Determination Procedure Assignment (from left)
Now assign your sales type to Partner determination TA.
Create a SALES order you can find the sold to and ship to are editable.
Regards,
Mani

Sold-to-party not getting updated

Hi
we are trnasferring outboud deliveries from system A to system B. in system a the delivery is with reference to order and when it comes to B we have custom delivery type which without order reference. we are using BAPI_OUTB_DELIVERY_CREATENOREF to transfer the delivery. all the data is updated correctly but the sold-to-party is not updated. In fact in the FM there is not import parameter for entering sold-to-party.
In system B we tried to create a delivery without order reference using the same ship to party , in this case the sold-to-party is picked up by the system automatically. So when only replicating with the BAPI the sold-to-party is not picked up automatically. How do i update the sold-to-party. is there any FM to do this??
thanks
sankar

Take a look at the OSS note 1069352 - it won't solve the issue but might explain something.
Try using EXTENSION_OUT / EXTENSION_IN to add sold-to. Otherwise you might have to use something different. E.g. FM BAPI_DELIVERYPROCESSING_EXEC technically allows creating the deliveries in a scenario that you're describing:
The preceding document can be in another system. To ensure that the entire requested quantity is generated in the delivering system and the corresponding requirements are planned in the planning system, for example, for cross-system deliveries SAP recommends creating unchecked deliveries (techn_control-check_mode = 'A').
There are also IDocs for deliveries. Hope this helps...

Sold-to-Party info

Hi!
I've configured the Solution Manager for the VAR scenario following the config document.
I can create messages in this SM but when I create a message I don't have Sold-to-Party info in Header Data (I have only Reported By info)
See the log:
Enter   Sold-To Party
Technical Data
Message type__________     E (Error)
Message class_________     COM_PARTNER (Partner Processing Messages)
Message number________     119
Message variable 1____
Message variable 2____
Message variable 3____     Sold-To Party
Message variable 4____
Has anyone encountered this problem?
Thanks,

Hi.
The Sold-To Party is iBase dependent in the VAR scenario. Did you enter an iBase component?
If you have set the SMSY_SETUP parameters correctly report AI_SC_REFRESH_READ_ONLY_DATA will read the customer numbers from Service Marketplace and generate business partners of type organisation and role sold-to party.
iBase components may be generated from smsy (if you set IB_GEN parameter in DNO_CUST04 accordingly).
Report AI_SC_REFRESH_READ_ONLY_DATA can generate SMSY components if set in view V_AISAPCUSTNOS / V_AIINSNRS and after SMSY_SETUP is maintained.
For each customer number in IB52/IB53 the sold-to party will be added to the component automatically
(can be done manually via tx: IB52 -> installation 1 -> GoTo -> Partner).
Regards

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
Basavaraj

Hi,
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

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

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

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

Where to enter sold to party in BAPI_SALESORDER_CREATEFROMDAT2

Similar Messages

Maybe you are looking for