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.

Similar Messages

User Exit to change the Ship-to party address at Sales Order headder level

Hi,
I have requirement like this......
I need to change the ship-to party address at Sales Order headder level. for that which user exit i need to use and which structure i need to use to update the transaction.
I used : userexit_save_document_prepare, in that i passed data to 'xvbpa' and 'xvbadr' structures. even though it is not update the transaction.
Please let me know the answer.
Thanks,
Satish.

Hi Satish,
Step1. Create new Data Copy Routine using Tcode VOFM.
Step2. *-----------------------------------Ship to Party from contract
   IF CVBPA-PARVW = 'WE' OR
      CVBPA-PARVW = 'SH'.
    REFRESH IT_STP.
    SELECT KTOKD
           A~KUNNR
           NAME1
           NAME2
           A~ADRNR
           FROM VBPA AS A INNER JOIN KNA1 AS B ON A~KUNNR = B~KUNNR
           INTO CORRESPONDING FIELDS OF TABLE IT_STP
           WHERE VBELN = CVBPA-VBELN .
Step3.
   CALL FUNCTION 'POPUP_WITH_TABLE_DISPLAY'
        EXPORTING
          ENDPOS_COL   = 80
          ENDPOS_ROW   = 10
          STARTPOS_COL = 10
          STARTPOS_ROW = 5
          TITLETEXT    = 'Your Title'
        IMPORTING
          CHOISE       = T_SELIDX<=====Index No of selection
        TABLES
          VALUETAB     = IT_STP
        EXCEPTIONS
          BREAK_OFF    = 1
          OTHERS       = 2.
Step4.
       READ TABLE IT_STP INTO WA_STP INDEX T_SELIDX.
        IF SY-SUBRC = 0.
          CLEAR:CVBPA-KUNNR, CVBPA-ADRNR.
          MOVE WA_STP-KUNNR TO CVBPA-KUNNR.
          MOVE WA_STP-ADRNR TO CVBPA-ADRNR. <========Address ID (Change Here).
       ENDIF.
Regards,
Amrendra
Moderator Message - Please do not reply to old, dormant threads.
Message was edited by: Suhas Saha

Report for Sold to Party code against Sales order number

Hi,
Is there any standard report to take out the Sold to Party code against Sales order number as i have the sales order number.
I don't want to use Tables ,so pls tell standard report if any.

Dear Monty garg.
You can use u201CVA05Nu201D to find the sales orders which have been created against for the particular customer/sold to party.
Please let me know if any further clarifications pertinent to this.
Thanks&Regards
Raghu.k

Sales order: price condition not working when i change the sold to party

Hi guys,
I've a strange problem by making the following steps:
1. Create a sales order:
By VA01 i create an order by filling the SOLD TO and one material - all OK. The price is calculated correctly.
2. Change SOLD TO:
I change the sold to by filling another payer that has a different price list (PLTYP) - the price is not re-calculated
If i change with another payer with the same price list everything is ok.
Can you tell me what could be the problem?
Many thanks

Did you actually change the sold-to party though or just the payer? The sold-to party's price list type controls the price list type value copied into the order header. Even if the payer has a different value, it's not copied to the order header. You can see this behavior in FV45KFKD_VBKD_FUELLEN. If you switch sold-to's then you should get a pop-up that new pricing was carried out; you should also see your new price list type value in the order header and you can use the 'analysis' function at the item level to verify that the correct price was used.

Reversing the billing an change the sold to party...

Hello Experts...
We have a complete Sales Order submitted which has a mile stone based billing. The sold to party (A) has paid 4 installments out of 10 installments. He now wants to take back his 4 payments and change the Sold to Party to B. The new Sold to party (B) will pay the 4 installments and continue with the payment of balance installements. There is no change in the materials sold and pricing. The customer does not want to cancel the sales order and create a new sales order.
This is a high priority issue. Kindly advice asap.
Thanks and Regards

Dear Patnaik,
I think you can do like this, try with this......
You do the reverse or cacel for the 4 instalments which sold to party A has paid.
You need to reverse or cancel the all susequent documents of the sales order
Make sales order status as open
Now you can change sold to party to B in the sales order in VA02 transaction
I hope it will help you
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on May 16, 2008 2:43 PM

Change the sold to party

Hi expert,
Can i change " Sold to party code" after the creation of the sales order.
Regard
Shashi

Hi
After the sales order say order no 10000 saved for sold to party as X you cannot change the sold to party in VA02 transaction as Y for order no 10000
That means if the order is created and saved then you cannot change the Sold to party for that order
But while processing it self before saving in VA01 transaction itself it is possible to change the SP
after the creation of the sales order.
Not possible
You cannot touch SP in VA02 transaction irrespective of subsequent document is there or not and the
img settings said under partner determination for sales document types say TA for standard order there also i dont think you can change the standard settings as the SP is mandatory and not modifiable
You cannot remove the tick in non modifiable for SP for TA the standard sales doc type partner determination and make it
modifiable
Regards
Raja
Edited by: ramanathan raja on Nov 1, 2009 12:33 PM

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

User Exit/Badi to change the billing plan date when create sale order

Experts,
Please advise which user exit/badi can be used to change the billing plan date wen create sale order.
My requriement is based on some rules to dynamically change the line item billing plan start date and end date when create sales order.
I tried some user eixt in MV45AFZZ, but the date got revert to the orginal date from billing plan.

Hi,
check the include MV45AFZB.
Thanks & Regards,
Sateesh.

Changing the receiving partner in idoc (Outbound SALES ORDER)

Hi All,
In my scenario Sales order (ORDERS) outbound is created and it should send to Delivering plant not to the Sold-to party. how to do this in partner profile? Is there is any coding should be written?
Thank you in advance,
Adithan S.

Hi,
Aveek is right, you only option is to use partner type 'LS'. So you need to create logical systems for these delivering plants, but since setting up 'LS' as the partner function for all the customers requires lots of illogical customizing changes and master data changes, I suggest that you use 'ALE' medium instead of 'EDI'. So that all you need to do is maintain distribution module for any one of these logical system so that output type processing can take place. Later you can use exit 'EXIT_SAPLVEDC_001' to change control record (change recipient to delivery plant).
Cheers,
Sanjeev

Default sold to party coming in Sales order

Hi,
Whenever i am trying to create sales order the system automatically purpose a default number in the sold to party field.And there is no such customer master record maintained for this number.After deleting this number then i can able to create sales order.
How to resolve it??
Regards
Jyoti

Hi
i think there is a user exit so that u r getting default sold to party
It seems user exit V45A0002 is applied
Go to transaction CMOD
Create a project called ZVA01
Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document.
Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed
Press Save Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = ''.
If there is any value After E_KUNNR remove it
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder.
OR ELSE YOU CAN DEACTIVATE THE USER EXIT
regards

How to validate Sold to party while creating sales order

Hi All,
I need to validate the sold to party which is entered when a order is created.
I able to read the Partner no using the FM u2018CRM_ORDER_READ_OWu2019, but how can I check if this partner number has u2018sold to partyu2019 function assigned.
Thanks & Regards
Shanthi

Hi Shanti,
There is a little twist in the validation that you intend to do to meet your business requirement. I will provide you with the Sap help link also. Have a look at this and you will understand the same.
[Partner Function|http://help.sap.com/saphelp_sm40/helpdata/EN/3c/92eceb484a11d5980800a0c9306667/content.htm] - Come to very end. Here there is a pictorial representation of how you can map a Partner function with the Business Partner Master Data. The system also maps in the similar way.
The Database tables which might be of help to you are BUT050 - Business Partner Relationship Category, CRMC_PARTNER_PFT - Definition of Partner Function Types. The rest you need to follow your own logic. I guess this will be enough to help you to get started. Let me know if you need any more inputs.
Hope this helps.
Thanks,
Samantak.

Mutiple sold to party in one sales order???

Hi,
Is it possible for one sales order have mutiple sold-to party???
If yes, how to do the split when in billing process for those mutiple sold-to parties?
Thank you.

Hoo laa,
Do the following
In Customizing for Sales and Distribution, choose Sales > Sales Documents > Scheduling Agreements with Delivery Schedules > Maintain planning delivery sched. instruct./splitting rules > Maintain Delivery Schedule Splitting Rules.
Enter a name for your splitting rule.
Enter a split share in the weekdays that you require for the forecast delivery schedule split.
Define how the system reacts when schedule lines falls on a holiday.
Specify how the system rounds schedule line quantities when generating a planning delivery schedule.
Assign splitting rule ranges to an instruction.
Choose Sales > Sales Documents >Scheduling Agreements with Delivery Schedules > Maintain planning delivery sched. instruct./splitting rules > Assign Delivery Schedule Splitting Rules.
In the dialog box, specify for which instruction you are entering a splitting rule. Then enter a splitting rule and specify its ranges in weeks or months.

How to change the sequence that VL10 use for sales order during DN creation

We are using VL10 for DN creation , VL10 is executed in background as a batch job ..... we have created a variant and have given range of shipping points for which we want to create the Deliveries.
What we want to understand is that how SAP standard code for VL10, sorts the sales orders for which the delivery are to be created using VL10?
we would like VL10 to process the sales order which belong to same shipping point in some order....so that delivery needs to be created for the first sales order rather than last sales order for a given shipping point....
Is there any sort order that SAP follows to pick which order it will consider for delivery creation ....first over the other sales order where the shipping happens to be same ? if yes then is there any way we can change it ?
Any guidance is appreciated
Thanks
Rajey

We are facing the same problem and are running at 4.7.
There are orders with the same goods issue date and if so, it should be sorted by order no.
Nevertheless, it does not sort it by order no but we could not find yet what the sort criteria is if it runs in the background and how to change these rules.

How to change the status of material while creating sales order via BDC

Hai.
In BDC while creating sales order( va01 posting ) it is stucking up in middle saying material is new. I.e Sales order (va01) is not getting created because of material status is new . I want to create sales order (va01) even material status is new.
pls give me out the solution. Points will be rewarded.
thanks & regards,
sami.

Hi,
If you drag the line item a little towards the right side, you will find a filed material entered. The one you see in the material filed on sales order over view screen is the one determined. You can as well double click and see the fields material entered and material determined.
Is there anything else you are expecting to see as part of analysis ?
Regards
Sadhu Kishore

Changing the Ship-to partner details in Sales order header through exit

Hi all,
I have a requirement where in during the process of the sales order creation, based on certain
criteria, the details in the ship-to partner would have to be modified.
These details like the Name, Street, etc would be maintained in a local table and based on the criteria,
the appropriate record from this table would be fetched and updated to the ship-to partner.
I was trying to implement this in the MV45AFZZ user exit. However, I was not able to update this through the exit.
Would I have to somehow update the ADRC table directly through this exit or is there any better method.
Please suggest.
Regards,
Sudeep

Hi,
If you could not find Street in this Routine call the BAPI BAPI_BUPA_ADDRESS_CHANGE to update Street and required details ..
Thanks and regards,
Sree.

Change the Sold to Party(SP) in sales order in change mode

Similar Messages

Maybe you are looking for