Sold-to Party (Document header)

Hi,
when i create a sales order by a certain type and if in sold-to-party field i write a certain customer, a popup dialog Sold-to Party (Document header) appears with some information fields: Postal code, Email, Fax, Street adress,PO Box addres,Communication,....
I want to modify the default value in Postal Code/City? How can i do that?

hello, friend.
are you referring to the cash sales type of order, and a customer that is of the one-time type (account group DEBI)? if so, the system behavior is correct. the customer is just a dummy and you enter the name and address of the actual sold-to.
if above is not the case, please post again.
regards.

Similar Messages

Sold to party in Order header screen

Hi,
Iam having a service contract and when I assign the service contract in service order header screen in SALES DOCUMENT field, I need to have the sold to party(assigned to Contract) field automatically populate in the sold to party field in the order header screen.
Presently its not happening and how to make this?
Is there is any relavent exit available for this?
regards
KRISHNAN

I can't remember exactly how we did it - only that we did manage it via a user-exit.
Unfortunately I don't have the documentation either...
You could do it at save (IWO10009) as follows:
data: t_ihpa like ihpavb occurs 10.
* get order parnter data
call function 'PM_PARTNER_GET_XIHPA'
    tables
      h_xihpa = t_ihpa.
* do your own processing here
* remembering to set the UPDKZ field (I=insert, U=update, etc)
* set order partner data
call function 'PM_PARTNER_PUT_XIHPA'
    tables
      h_xihpa = t_ihpa.
Not entirely orthodox, but it'll work...
PeteA
[www.pjas.com]

How to Create Sold-to-party i.e. default in sales documents ?

Hi Experts,
I have studied a lot of threds about default sold-to-party.
But still I have a query, suppose I create any customer and using enhancement I use that customer as default in sales document, but suppose I dont know about the sales area of my actual customer and if the sales area of my actual customer and default customer are different then how the sales document will allow us to enter the another customer whose sales area is different.
Now what I want to know:
1. How to create a customer so that I can use that as a default in sales document and that customer should be compatible with other sales area.
2. Is it possible to include a customer, whose sales view has not been created, in our sales document.
Thanks in advance.
Regards,
Vishal Singh

Hi,
To create a default customer which can be attached to any sales document can be done through common distribution channel and common division. A customer created in common DC and Division can be attached to sales document in any sales area.
If a customer is not extented to sales view, it cant be attached to any sales document.
Regards,
Deepak

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

Sold TO party in display mode

Hi All,
Its a fresh impleemntation and We have created new sales document type, maintained proper sales area no incompletion procedure is assgined
at VA01
we r giving order type
Sales area
ENTER
till this time its working fine
but Sold-to-party and ship-to-party is in display mode
can you please advice why it is in display mode

hi vishal,
goto SPRO - SD - set up partner determinatin procedure- set up PDP for sales document header & select your PARTNER DETERMINATION PROCEDURE & check partner determination procedure assignment - which determination procedure is assigned to it.
balajia
Edited by: balaji timmampalli achari on Dec 21, 2010 4:58 PM

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 showing editble mode in sales contract

Hi all,
I created a sales contract and followed by sales order, delivery billing the movement i am checking sales contract SOLD TO Party its showing editable mode in contract over view screen and i check in header partners it showing sold to party in gray mode , i maintain relevant configuration ( partner determination i mark as a SP not editable and mandatory function in sales document header and procedure KAB release order in that i assign SP sold to party with not editable and mandatory function
still its showing editable mode in sales contract
Same Config is working fine for Sales order, once subsequent document is created sold changing into gray mode
why same confg is not working for Sales contract
can any one guide me where i am wrong
Thanks
Rajesh

hi
goto
img>sales and distribution>basic function>partner deternination>Set Up Partner Determination for Sales Document Header-->
partner determination procedure
partner determination procedure assignment(assign sales document and partner determination)
partner functions
account group-function
regards
senya
Edited by: senya_1111 on Sep 7, 2009 4:00 PM

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 for Inqury

Hi,
I have just created a new Sales Order Type (Inquiry) in SPRO, but when I use the Transaction VA11 to create the new Inquiry Type, the Sold-To party and the Ship-To Party are disabled... (Blanked out to prevent from entering value). I have already created several Customer Master for the Sales Area. Can anyone please give some advice to solve this?
Thanks.

Hi,
As suggested by Ramanathan,
Follow following steps for sales document header partner determination.
SPRO -->SD --> BASIC Functions -->Partner Determination --> Set up partner determination --> Set up partner determination for sales document header:
1: Set up partner determination procedure for Ex -TA
2: Assign partner functions to your partner determination procedure - Here you can control what are the partner functions you want see on your sales document header.
3: Assingn partner determination procedure to your sales document type
Best Regards,
Amit

How to change sold to party description

Hi all,
I want to change sold to party description to customer in VA11/ VA21/VA01 (sold to party).
Is there any possibility to change it?
Please give me solution if it is possible............
Thanks in advance
Babu

Dear Babu,
There are two ways to change the description of Sold to party:
1. XD02 / VD02 - Change the Customer description, which would be Master Data change & would effect all Documents.
2. At time of Sales Order processing (which is what you want): VA01 / VA02 - Double click on Sold-to-party code & you will go to Header - Partner Data - Here once again click on Customer Code of required partner (Sold-to-Party in your case) & make the necessary changes.
There changes would be applicable only for the particular Sales Order & the Master Data would not be changed.
Hope this helps...
Thanks,
Jignesh Mehta

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
Somnath

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

Grayed sold-to party during creation of quotation

Hi,
I've created new document type (quotation) and it works fine, but during creation of a quotation Sold-to and ship-to are grayed, so I cannot change it. Even quotations replicated from CRM does not have solt-to and ship-to. What should be change in order to make ship-to and sold-to editable?
Marek

hello, friend.
was your quotation created with reference to other documents like, say, inquiry of CRM documents? if so, then the quotation copies the sold-to party from the previous document and restricts changes in the sold-to party.
if your quotation was not copied with reference, then do VOV8 and check your document type and see if there is an entry in General Control > Reference mandatory.
also, this may have been affected by copy controls in VTAA, header > DataT (value 001 partner header).
regards.
Edited by: jonathan yap on Mar 5, 2008 6:51 PM

Ship-to party is not assigned to a sold-to party

Dear Experts
I am creating Sales ORder VA01
my customer is 42
so i have enterd 42 in Ship to party and Sold to party
but getting error is
Ship-to party 42 is not assigned to a sold-to party
could u please guide me
Regards
Amol

Hi,
Goto the T.Code "XD03".
Enter the customer number as "42".
Maintain the company code and sales area.Enter.
Goto the sales area tab.Click on "Partner functions" tab.
Check whether the ship-to-party is 42 or not.I think it is not 42,so that only,you are getting this error message.
In sales order,enter the sold-to-party as "42".The ship-to-party will be auto determined from the customer master.After this you can change it to 42 if the following setting is maintained for your partner determination procedure.
Goto the path:
SPRO>Sales and Distribution>Basic Functions>Partner Determination>Set Up Partner Determination-->Set Up Partner Determination for Sales Document Header.
Click on "Partner Determination Procedure Assignment".Identify the procedure assigned to your document type.
Click on "Partner Determination Procedures".Select that procedure.
Double click on "Partner Functions in Procedure".
Ensure that for "SH" partner function,the field "Not modifiable" is not ticked.
Save.
Regards,
Krishna.

To make the Billing document header updated with the new VAT number.

Hi Experts
Due the business requirement we change the VAT number of customers for the European countries.
And now how can we ensure that the Billing document header gets updated with the new VAT Reg.Number for the existing Billing documents.
The intention is to ensure that when we Print an already existing invoice,the new changed VAT number should appear in the invoice output.
Please suggest.
Montee

Hi,
   Have these documents been released to accounting? If yes then you have top canecl all the documents to update the billing documents and repost them with the new vat number. I think you might know how VAT gets determined in SAP. If not please go to SPRO-IMG-SD-BF-TAXES-MAINTAIN SALES TAX IDENTIFICATION UMBER DETERMINATION.
1. If the payer has a VAT ID number and RG <> AG, then the tax number
      and tax classification are copied from the payer (in this case, the
      ship-to party is not relevant).
      The tax number is taken according to the 'tax country of
      destination'.
2. If 1. does not apply:
      If the ship-to party has a VAT registration number and the sold-to
      party does not, tax number and tax classification are copied from
      the ship-to party.
3. If 2. does not apply:
      Tax number and tax classification are copied from the sold-to party.
If you enter A, tax number and tax classification are generally copied
from the sold-to party.
The tax number is copied according to the 'country of destination
relevant for taxes'.
If you enter B, tax number and tax classification are generally copied
from the payer.
The tax number is copied according to the 'country of destination
relevant for taxes'.
Kindly please let me know If you need any more information on this.
Regards
Ram Pedarla

Sold-to Party (Document header)

Similar Messages

Maybe you are looking for