Sales Order Extention
Hi,
I have a requirement like, i want extend Sales order in CRM. For this I choose EEWB. When i create them through EEW i have set the R/3 flag. Before that i have to maintain Logical system in EEWC t code. I did this also.
But now problem is, EEWB is asking for Package for R/3 logical system.
Where can i specify package name.
But it s true that we have to give package, because the extended fields would be created automatically in R/3. so we need package.
Please give me the solution. or any alternative solution.
Regards
Dinesh
Prasad,
If it is in Released To Warehouse status, you should see move_line_id against that delivery_detail_id in WDD table for that order line id. Can you check which organization that is created in and be in that organization to query up the screen. If it is autoallocate yes, you should also see records in the MMTP of that move order line. Can you check that table too?
Thanks
Nagamohan
Similar Messages
-
Sales Order Material and its MOQ mass change
*The issue is related to our Spare parts Ordering process in our company.*
We have a concept of having 65 days of back orders. Hence there will be
lot many open orders in the system.
The Material code will be changed from (for eg) M01 to M02. Hence forth the Material (M01) ordered will
automatically changed to M02 through Material determination logic. But
for the 65 days back orders, it is very difficult to change the
material one by one in sales order. There may be more than 100 orders
for a material. Even if the MASS change option in Transaction VA05
doesn't address because of the following reasons;
1. The changed new material (M02) may have new price with new validity
periods, whereas the back orders will have old pricing dates. Its
difficult to change individually in the open orders.
2. Some materials may have partially delivered.
Similar to ECM changes, there will be MOQ changes which also needs to
be changed individually the order quantity in the old Open orders.
For example,
Initially the MOQ for a material in 10. Order inflow has happened based
on this MOQ.
Now if the MOQ is changed to 20, future orders are addressed. But for
the 65 day back orders, we need to manually open the individual sales
order and change the order quantity.
Hence we require a mass change option for the open orders as below:
1. For Material Changes (M01 to M02), I will give the list of orders and
the line items and Qty for M01. The program should reject the existing
line item for M01. An additional line item should be created with M02.
Also the pricing date should be changed.
2. For MOQ changes, I will give the list of orders and the line items
and Qty. The program should reject the existing line item for those
materials. An additional line item should be created with new Qty.
If the material is partially delivered, the the existing qty should be
updated to the extent it is delivered and the remaining qty should be
updated with new material or New MOQ.You can use BAPI_SALESORDER_CHANGE.
1. Get the SO detail using BAPISDORDER_GETDETAILEDLIST.
2. MODIFY the ORDER_CFGS_* internal tables and update.
CALL FUNCTION 'BAPISDORDER_GETDETAILEDLIST'
TABLES
order_cfgs_value = gt_char
order_cfgs_ref = gt_char_ref
order_cfgs_inst = gt_char_ins.
MODIFY gt_cfgs_*.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
TABLES
order_cfgs_value = gt_char
order_cfgs_ref = gt_char_ref
order_cfgs_inst = gt_char_ins.
Refer SAP note 549563. -
Hi,
I was doing my config from quite a while and was able to save sales orders normally. All of a sudden, I am now unable to save any sales orders. It is throwing a dump while I am trying to save the sales order. The dump details are provided below. I tried debugging the code to an extent and realized that there is some error in acessing access sequences in output determination. Can someone guide me to fix this error please?
Please find the dump below:
Runtime Errors SAPSQL_INVALID_FIELDNAME
Exception CX_SY_DYNAMIC_OSQL_SEMANTICS
Occurred on 23.10.2008 at 09:09:10
One of the field names in the SELECT clause was not recognized.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLV61Z " had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
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.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYNAMIC_OSQL_SEMANTICS',
was neither
caught nor passed along using a RAISING clause, in the procedure "SEL_KONDTAB"
"(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The SELECT clause was specified in an internal table at runtime.
It contains the field name "DATBI", but this does not occur in any of
the database tables listed in the FROM clause.
How to correct the error
The exception must either be prevented, caught within the procedure
"SEL_KONDTAB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Check the field names in the SELECT clause.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_INVALID_FIELDNAME" CX_SY_DYNAMIC_OSQL_SEMANTICSC
"SAPLV61Z " or "LV61ZU01 "
"SEL_KONDTAB"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "sap_server"
Network address.......... "10.1.1.193"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "SAP_SERVER"
Database type............ "ORACLE"
Database name............ "NX1"
Database owner........... "SAPNX1"
Character set............ "English_United State"
SAP kernel............... "620"
Created on............... "Aug 5 2002 21:33:12"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "OCI_817_SHARE "
Patch level.............. "252"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.."
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 800
User................ "SAPUSER"
Language key........ "E"
Transaction......... "VA01 "
Program............. "SAPLV61Z "
Screen.............. "SAPMV45A 4001"
Screen line......... 61
Information on where termination occurred
The termination occurred in the ABAP program "SAPLV61Z " in "SEL_KONDTAB".
The main program was "SAPMV45A ".
The termination occurred in line 495 of the source code of the (Include)
program "LV61ZU01 "
of the source code of program "LV61ZU01 " (when calling the editor 4950).
Processing was terminated because the exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
occurred in the
procedure "SEL_KONDTAB" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "SAPLV61Z ". Its source code starts in line 225
of the (Include) program "LV61ZU01 ".
Source code extract
004650 IF SE_PRESTEP = YES OR
004660 SE_READ_ONLY_ONE_RECORD = YES.
004670 IF T681-KSDAT IS INITIAL.
004680 IF SE_READ_ALL_PRESTEP IS INITIAL.
004690 SELECT * FROM (T681-KOTAB) APPENDING TABLE KOND_TAB
004700 UP TO 1 ROWS
004710 WHERE KAPPL = SE_KAPPL
004720 AND KSCHL = SE_KSCHL
004730 AND (CODING_TAB).
004740 H_SUBRC = SY-SUBRC.
004750 ELSE.
004760 SELECT * FROM (T681-KOTAB) APPENDING TABLE KOND_TAB
004770 WHERE KAPPL = SE_KAPPL
004780 AND KSCHL = SE_KSCHL
004790 AND (CODING_TAB).
004800 ENDIF.
004810
004820 * it is enough to find one record in prestep
004830 * (care must be taken with pool tables - depending on database this
004840 * will cost performance instead of saving)
004850 IF SELECT_SPLIT NE 0 AND H_SUBRC NE 0.
004860 MODIFY CODING_TAB FROM CODING_ALTER INDEX SELECT_SPLIT.
004870 SELECT * FROM (T681-KOTAB) APPENDING TABLE KOND_TAB
004880 UP TO 1 ROWS
004890 WHERE KAPPL = SE_KAPPL
004900 AND KSCHL = SE_KSCHL
004910 AND (CODING_TAB).
004920 ENDIF.
004930 ELSE.
004940 IF SE_READ_ALL_PRESTEP IS INITIAL.
SELECT * FROM (T681-KOTAB) APPENDING TABLE KOND_TAB
004960 UP TO 1 ROWS
004970 WHERE KAPPL = SE_KAPPL
004980 AND KSCHL = SE_KSCHL
004990 AND DATBI >= SE_DATE
005000 AND DATAB <= SE_DATE
005010 AND (CODING_TAB).
005020 H_SUBRC = SY-SUBRC.
005030 ELSE.
005040 SELECT * FROM (T681-KOTAB) APPENDING TABLE KOND_TAB
005050 WHERE KAPPL = SE_KAPPL
005060 AND KSCHL = SE_KSCHL
005070 AND DATBI >= SE_DATE
005080 AND DATAB <= SE_DATE
005090 AND (CODING_TAB).
005100 ENDIF.
005110
005120 IF SELECT_SPLIT NE 0 AND H_SUBRC NE 0.
005130 MODIFY CODING_TAB FROM CODING_ALTER INDEX SELECT_SPLIT.
005140 SELECT * FROM (T681-KOTAB) APPENDING TABLE KOND_TAB
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 4 SY-INDEX 1
SY-TABIX 17 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 1 SY-LINNO 1
SY-COLNO 1 SY-PFKEY U
SY-UCOMM SICH SY-TITLE Create Sales Order: Overview
SY-MSGTY E SY-MSGID FI
SY-MSGNO 011 SY-MSGV1 AUD
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
1 FORM SEL_KONDTAB
SAPLV61Z
LV61ZU01 495
2 FUNCTION SD_COND_ACCESS
SAPLV61Z
LV61ZU01 196
3 FORM KOMT2_AUFBAUEN
SAPLV61B
LV61BF0K 78
4 FORM KONDITIONSVORSTEP
SAPLV61B
LV61BF0K 275
5 FORM COND_ACCESS_V1
SAPLV61B
LV61BMES 417
6 FUNCTION MESSAGING
SAPLV61B
LV61BU50 81
7 FORM NACHRICHTEN_POSITION
SAPMV45A
MV45AF0N_NACHRICHTEN_POSITION 81
8 FORM BELEG_BEARBEITEN_ENDE
SAPMV45A
MV45AF0B_BELEG_BEARBEITEN_ENDE 268
9 FORM BELEG_SICHERN
SAPMV45A
MV45AF0B_BELEG_SICHERN 270
10 FORM FCODE_SICH
SAPMV45A
MV45AF0F_FCODE_SICH 9
11 FORM FCODE_BEARBEITEN
SAPLV00F
LV00FF0F 90
12 FUNCTION SCREEN_SEQUENCE_CONTROL
SAPLV00F
LV00FU02 44
13 FORM FCODE_BEARBEITEN
SAPMV45A
MV45AF0F_FCODE_BEARBEITEN 90
14 MODULE (PAI) FCODE_BEARBEITEN
SAPMV45A
MV45AI0F_FCODE_BEARBEITEN 8
Chosen variables
1 FORM SEL_KONDTAB
SAPLV61Z
LV61ZU01 495
SE_KSCHL EXEM
4544
585D
CODING_TAB[] Table IT_44581x256
67050000E0006100000000000000FFFF0200C300
07320000F200A100100001000000FFFF47308600
... + 40
0000C020
A0001400
SY-REPID SAPLV61Z
5454533522222222222222222222222222222222
310C661A00000000000000000000000000000000
KOND_TAB[] Table IT_39140x480
3FC50000E00040000000E0000000FFFF02009000
03A100003100AF00000001000000FFFF47308A00
... + 40
0000C000
A0001E00
KOMGM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 00
233222222222222
000000000000000
SE_READ_ALL_PRESTEP
2
0
T681 B998V1B998
4333534333222222222222222222222222222222
2998612998000000000000000000000000000000
... + 40 X3 000
53233322222222222222222222
83000000000000000000000000
%_DUMMY$$
2222
0000
T681-KOTAB B998
433322222222222222222222222222
299800000000000000000000000000
CONDITION_IN_MEMORY_INTERNAL
2
0
KOMGR
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222222222222222222222
00000000000000000000000000000000000000
SE_KAPPL V1
53
61
*KOMGR
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222222222222222222222
00000000000000000000000000000000000000
KOMK 800 AUD 0000000001100
3332222222222222222222245423333333333333
8000000000000000000000015400000000001100
... + 40 0001MEL 21 AU VIC AUD A
3333444222332245254422222224542222222224
0001D5C000210015069300000001540000000001
... + 80 UD AUD #####0000000000000010050000
5422454222222000003333333333333333333333
54001540000000000C0000000000000010050000
... + 120 00100500000010050000001005
3333333333333333333333333322222222222222
0010050000001005000000100500000000000000
... + 160 000000000001###V SABI0120081023200
2222223333333333330005254443333333333333
00000000000000000100C6031290120081023200
... + 200 81023200810232008102320081023CIFdandenon
3333333333333333333333333333344466666666
8102320081023200810232008102339641E45EFE
... + 240 g
622222222222222
700000000000000
SE_DATE 20081023
33333333
20081023
KOMP 000010000000000000000857 MEL VI
3333333333333333333333332222222222444254
0000100000000000000008570000000000D5C069
... + 40 C
4222222222222222222222222222222222222222
3000000000000000000000000000000000000000
... + 80 04 MEL ##############
2332222444222222222220000000000000022222
0040000D5C00000000000000000C000000C00000
... + 120 015
2222222222222222222222222222333222222222
0000000000000000000000000000015000000000
... + 160 ###### 000010
2222222000000222222233333322222222222222
000000000000C000000000001000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
2 FUNCTION SD_COND_ACCESS
SAPLV61Z
LV61ZU01 196
APPLICATION V1
53
61
CALL_MODUS A
4
1
CONDITION_TYPE EXEM
4544
585D
DATE 20081023
33333333
20081023
HEADER_COMM_AREA AUD 0000MEL 00000110021
2222222222454233334442333333333332222222
000000000015400000D5C0000001100210000000
... + 40 0000001005000000100500000
2222222222222223333333333333333333333333
0000000000000000000001005000000100500000
... + 80 0100500000010050000000000CIF020001200810
3333333333333333333333333444333333333333
0100500000010050000000000396020001200810
... + 120 231######0#AUD YOR C CA
3330000003045422222222222222225452422244
2310000030C15400000000000000009F20300031
... + 160 CCCCCCCH 00000000
2222444444442222222333333332222222222222
0000333333380000000000000000000000000000
... + 200
222222222222222222222222
000000000000000000000000
KOPRT_I 00000003001 KRML00
3333333333322224544332222222222222222222
000000030010000B2DC000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222
0000000000000000000000000
NO_MEM_IMPORT
2
0
POSITION_COMM_AREA 0000100000000000000008570000000000000008
3333333333333333333333333333333333333333
0000100000000000000008570000000000000008
... + 40 57 015 T
3322222222222222222222222222223332222225
5700000000000000000000000000000150000004
... + 80 AN 100001100055555004##############K
4422222333333333333333333000000000000004
1E00000100001100055555004000000C000000CB
... + 120 AR #
4522222222222222222222222222222222222220
1200000000000000000000000000000000000000
... + 160 ### 000001######0#u0153 #################
0002223333330000003092200000000000000000
C0C0000000010000030CC000000010C0000010C0
... + 200 #######KAR######%#######u201EKG ########
0000000445000000200000008544200000000222
000010CB120000075C0000064CB700000000C000
... + 240 01MEL MEL1
334442222244432
01D5C00000D5C10
PRESTEP X
5
8
PROTOCOL_ACCESS X
5
8
PROTOCOL_DATE
2
0
READ_ALL_PRESTEP
2
0
READ_ONLY_ONE_RECORD X
5
8
SDPROTHEAD_I CONDB0000000000
2222222222222244444333333333322222222222
000000000000003FE42000000000000000000000
... + 40 00000000000000
222222233333333333333
000000000000000000000
T682I_I BV1EXEM03998## 000X
453454433333002233352
261585D039980C0000080
CONDITION_IS_IN_MEMORY #############
0000000000000
0000000000000
CONDITION_IS_PURELY_HEADER X
5
8
CONDITION_RECORDS[] Table IT_44400x119
3C15EA15E0005100000070000000FFFF0F004200
01C20DC2C2008100000070000000FFFF4C408500
... + 40
0000C020
10001400
POSITION_COMM_AREA_DYNAMIC
2222
0000
KOMPAZD
2222222222
0000000000
SYST ########################d###############
0000000010000000000000006000000000000000
1000100010001000000000004000000000000000
... + 40 ####################################|###
0000000000000000000000000000000000007000
100010001000000010000000000000000000C100
... + 80 ################S#######################
0000000000000000500000000000000000000000
0000000000004000310000000000000000000000
... + 120 ####################################¶###
000000000000000000000000000000001000B000
00000000000000000000000000000000D0006000
... + 160 ####ÿ####### u0152##XC############# E0 4
0000F0000000A800540000000000000222432223
0000F00000000C00830040000C0000C000500004
... + 200 001LIST N ####__S 800
3334455222420000555222222222222222223332
001C934000E01000FF3000000000000000008000
... + 240 00
222223322222222
000000000000000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
CONDITION_RECORDS 800V1VEN0
3335354432222222222222222222222222222222
8006165E00000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 0000002101
222222222222222222222222222223333333333
000000000000000000000000000000000002101
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
KOPF_POS_UNLOAD UNLOAD_COMMUNI_BV1
544444544445445453
5ECF14F3FDD5E9F261
3 FORM KOMT2_AUFBAUEN
SAPLV61B
LV61BF0K 78
SY-TABIX 17
1000
1000
*KOMKBNF
2222222222222222
0000000000000000
KOMKBWA
2222
0000
TYP_TNAPR 8
3
8
%_DUMMY$$
2222
0000
KOPRT 00000003001 KRML004502009
3333333333322224544333333333222222222222
000000030010000B2DC004502009000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222
0000000000000000000000000
C_EVENT 9
3
9
XSUBRC 0
0000
0000
KOMPBME ### 00000000
0002222222222222222222222222233333333222
00C0000000000000000000000000000000000000
... + 40 0000
2222222222222222222222233332222222222222
0000000000000000000000000000000000000000
... + 80
22222
00000
KOMKBME-UNAME
222222222222
000000000000
KOMT1-KAPPL V1
53
61
KOMT1-KSCHL EXEM
4544
585D
HEADER_COMM AUD 0000MEL 00000110021
2222222222454233334442333333333332222222
000000000015400000D5C0000001100210000000
... + 40 0000001005000000100500000
2222222222222223333333333333333333333333
0000000000000000000001005000000100500000
... + 80 0100500000010050000000000CIF020001200810
3333333333333333333333333444333333333333
0100500000010050000000000396020001200810
... + 120 231######0#AUD YOR C CA
3330000003045422222222222222225452422244
2310000030C15400000000000000009F20300031
... + 160 CCCCCCCH 00000000
2222444444442222222333333332222222222222
0000333333380000000000000000000000000000
... + 200
222222222222222222222222
000000000000000000000000
<%_TABLE_TNAD1> ???
ITEM_COMM 0000100000000000000008570000000000000008
3333333333333333333333333333333333333333
0000100000000000000008570000000000000008
... + 40 57 015 T
3322222222222222222222222222223332222225
5700000000000000000000000000000150000004
... + 80 AN 100001100055555004##############K
4422222333333333333333333000000000000004
1E00000100001100055555004000000C000000CB
... + 120 AR #
4522222222222222222222222222222222222220
1200000000000000000000000000000000000000
... + 160 ### 000001######0#u0153 #################
0002223333330000003092200000000000000000
C0C0000000010000030CC000000010C0000010C0
... + 200 #######KAR######%#######u201EKG ########
0000000445000000200000008544200000000222
000010CB120000075C0000064CB700000000C000
... + 240 01MEL MEL1
334442222244432
01D5C00000D5C10
KOMKBWR-ERNAM
222222222222
000000000000
KOMPBWR-ERNAM
222222222222
000000000000
*TNAD1-VKORG
2222
0000
G_SDPROTHEAD CONDB0000000000
2222222222222244444333333333322222222222
000000000000003FE42000000000000000000000
... + 40 00000000000000
222222233333333333333
000000000000000000000
T682I BV1EXEM03998## 000X
453454433333002233352
261585D039980C0000080
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
HEADKZ X
5
8
<%_TABLE_TNAD2> ???
KONDTAB[] Table IT_44400x119
3C15EA15E0005100000070000000FFFF0F004200
01C20DC2C2008100000070000000FFFF4C408500
... + 40
0000C020
10001400
*TNAD2-VKORG
2222
0000
*TNAD2-VTWEG
22
00
SY-REPID SAPLV61B
5454533422222222222222222222222222222222
310C661200000000000000000000000000000000
*TNAD2-SPART
22
00
SYST-REPID SAPLV61B
5454533422222222222222222222222222222222
310C661200000000000000000000000000000000
4 FORM KONDITIONSVORSTEP
SAPLV61B
LV61BF0K 275
%_SPACE
2
0
SY-SUBRC 4
0000
4000
SY ########################d###############
0000000010000000000000006000000000000000
1000100010001000000000004000000000000000
... + 40 ####################################|###
0000000000000000000000000000000000007000
100010001000000010000000000000000000C100
... + 80 ################S#######################
0000000000000000500000000000000000000000
0000000000004000310000000000000000000000
... + 120 ####################################¶###
000000000000000000000000000000001000B000
00000000000000000000000000000000D0006000
... + 160 ####ÿ####### u0152##XC############# E0 4
0000F0000000A800540000000000000222432223
0000F00000000C00830040000C0000C000500004
... + 200 001LIST N ####__S 800
3334455222420000555222222222222222223332
001C934000E01000FF3000000000000000008000
... + 240 00
222223322222222
000000000000000
INCL_ZUGRIFFSFOLGE X
5
8
NO
2
0
KOMT1-KOZGF EXEM
4544
585D
NACH-KSCHL
2222
0000
T683S-KAUTO
2
0
KOMKBMM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222
0000000000000
HEADER_COMM AUD 0000MEL 00000110021
2222222222454233334442333333333332222222
000000000015400000D5C0000001100210000000
... + 40 0000001005000000100500000
2222222222222223333333333333333333333333
0000000000000000000001005000000100500000
... + 80 0100500000010050000000000CIF020001200810
3333333333333333333333333444333333333333
0100500000010050000000000396020001200810
... + 120 231######0#AUD YOR C CA
3330000003045422222222222222225452422244
2310000030C15400000000000000009F20300031
... + 160 CCCCCCCH 00000000
2222444444442222222333333332222222222222
0000333333380000000000000000000000000000
... + 200
222222222222222222222222
000000000000000000000000
ITEM_COMM 0000100000000000000008570000000000000008
3333333333333333333333333333333333333333
0000100000000000000008570000000000000008
... + 40 57 015 T
3322222222222222222222222222223332222225
5700000000000000000000000000000150000004
... + 80 AN 100001100055555004##############K
4422222333333333333333333000000000000004
1E00000100001100055555004000000C000000CB
... + 120 AR #
4522222222222222222222222222222222222220
1200000000000000000000000000000000000000
... + 160 ### 000001######0#u0153 #################
0002223333330000003092200000000000000000
C0C0000000010000030CC000000010C0000010C0
... + 200 #######KAR######%#######u201EKG ########
0000000445000000200000008544200000000222
000010CB120000075C0000064CB700000000C000
... + 240 01MEL MEL1
334442222244432
01D5C00000D5C10
APPLIKATION V1
53
61
%_VIASELSCR #
0
4
SCREEN BT_PVMV
4555545222222222222222222222222222222222
24F06D6000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 BTA 00001#00000 ####
2222222222222224542222223333303333320000
0000000000000002410000000000100000000000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
5 FORM COND_ACCESS_V1
SAPLV61B
LV61BMES 417
KOMKBNF
2222222222222222
0000000000000000
KOMKBV1 AUD 0000MEL 00000110021
2222222222454233334442333333333332222222
000000000015400000D5C0000001100210000000
... + 40 0000001005000000100500000
2222222222222223333333333333333333333333
0000000000000000000001005000000100500000
... + 80 0100500000010050000000000CIF020001200810
3333333333333333333333333444333333333333
0100500000010050000000000396020001200810
... + 120 231######0#AUD YOR C CA
3330000003045422222222222222225452422244
2310000030C15400000000000000009F20300031
... + 160 CCCCCCCH 00000000
2222444444442222222333333332222222222222
0000333333380000000000000000000000000000
... + 200
222222222222222222222222
000000000000000000000000
KOMPBV1 0000100000000000000008570000000000000008
3333333333333333333333333333333333333333
0000100000000000000008570000000000000008
... + 40 57 015 T
3322222222222222222222222222223332222225
5700000000000000000000000000000150000004
... + 80 AN 100001100055555004##############K
4422222333333333333333333000000000000004
1E00000100001100055555004000000C000000CB
... + 120 AR #
4522222222222222222222222222222222222220
1200000000000000000000000000000000000000
... + 160 ### 000001######0#u0153 #################
0002223333330000003092200000000000000000
C0C0000000010000030CC000000010C0000010C0
... + 200 #######KAR######%#######u201EKG ########
0000000445000000200000008544200000000222
000010CB120000075C0000064CB700000000C000
... + 240 01MEL MEL1
334442222244432
01D5C00000D5C10
APPLIKATION V1
53
61
6 FUNCTION MESSAGING
SAPLV61B
LV61BU50 81
KOMKBWN
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22
00
APPLIKATION V1
53
61
SCHEMA V10000
533333
610000
PI_OBJTYPE VBAP
5445222222
6210000000
TYP_FRVOR C
4
3
G_OBJTYPE VBAP
5445222222
6210000000
G_ITEM X
5
8
PI_ITEM X
5
8
KOMK V10000##########
5333330000000000
6100000010007000
KOMK-KALSM V10000
533333
610000
L_CONDITION_FORM COND_ACCESS_V1
4444544445555322222222222222222222222222
3FE4F133533F6100000000000000000000000000
KOMKBMR
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222
0000000000000000000000
L_RC 0
0000
0000
KOMKBPA
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222
0000000000000000000000000
7 FORM NACHRICHTEN_POSITION
SAPMV45A
MV45AF0N_NACHRICHTEN_POSITION 81
VBMUEZ 0000
2222222222233332222222222222222222222222
0000000000000000000000000000000000000000
... + 40 ##
2222200
000000C
SY-SUBRC 4
0000
4000
SYST-REPID SAPMV45A
5454533422222222222222222222222222222222
310D645100000000000000000000000000000000
STEUERUNG BEDINGUNG_PRUEFEN_001
444444544555544445333
2549E75E7F025565EF001
VBUP 800 000010 CAA AA CCCC
3332222222222333333224442224422444422222
8000000000000000010003110001100333300000
... + 40
222222222222222
000000000000000
YVBUP 000000
2222222222222333333222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222
0000000000000000
IVBPA1_EINTRAG_AKTUELL 0
0000
0000
VBAP 800 000010000000000000000857000
3332222222222333333333333333333333333333
8000000000000000010000000000000000857000
... + 40 000000000000857
3333333333333332222222222222222222222222
0000000000008570000000000000000000000000
... + 80 015 Pattu Bombay Sandwitch Chutn
2223332222225677724666672566676766246776
0000150000000144502FD219031E47943803854E
... + 120 ey TAN A000000000000 1000011
6722222222225442224333333333333223333333
59000000000041E0001000000000000001000011
... + 160 00055555004##############KAR######KAR###
3333333333300000000000000445001001445000
00055555004000000C000000CB1200C00CB12000
... + 200 ###########00000000#######
0000000000033333333000000022222222222222
000C000000C00000000000000C00000000000000
... + 240
222222222222222
000000000000000
IVBEP 000000 00000000002008102310000000000####
3333332333333333333333333333333333330000
0000000000000000020081023100000000000000
... + 40 ########
2222222200000000
0000000000000000
VBKD 800 000000 21000001 CIFdanden
3332222222222333333223333333322444666666
800000000000000000000210000010039641E45E
... + 40 ong X #####0000000
6662222222222222222222522222000003333333
FE700000000000000000008000000000C0000000
... + 80 0000001 #####2008102320081023000000000
3333333222000003333333333333333333333333
00000010000100C2008102320081023000000000
... + 120 000000##### 000002
3333330000022222222222222222222223333332
0000000100C00000000000000000000000000020
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200 1000
2222222222222222223333222222222222222222
0000000000000000001000000000000000000000
... + 240 00
222222222222233
000000000000000
IVBEP_KEY 000010 00000000002008102710000000002
333333233333333333333333333333333333
000010000000000002008102710000000002
PART[] Table IT_44305x169
0F15EF15E00041000000A0000000FFFF0000A300
839282925200E100500090000000FFFF40000510
... + 40
1000C220
00001400
IVBEP_KEY1 000010 0000000000200810271000000
33333323333333333333333333333333
00001000000000000200810271000000
XVBPA[] Table IT_17425x542
A0E52CD58000C000000010000000FFFF00007D00
03810BD19000E6005000E2000000FFFF44008D00
... + 40
1000D200
00001480
SVBEP ####
0000
1000
TVAK-KAPPL V1
53
61
US_VBEPKOM 00000000000000 000000#######00000000 000
3333333333333323333330000000333333332333
000000000000000000000000000C000000000000
... + 40 000 0000 0000000000000000000000000000
3332223333223333333333333333333333333333
0000000000000000000000000000000000000000
... + 80 0000000000000000000000000000
3333333333333333333333333333222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 00
2222222222222222222222222222222222222233
0000000000000000000000000000000000000000
... + 200 000000000000
33333333333322
00000000000000
XOBJKY_POS 000010
222222222233333322222222222222
000000000000001000000000000000
CHARX X
5
8
IVBEP_TABIX_ZEILE_1 0
0000
0000
BUSINESSOBJEKT_POS VBAP
5445222222
6210000000
US_VBEPKOMX 0000000000
33333333332222222222222222222222
00000000000000000000000000000000
TVAP-KALSM V10000
533333
610000
IVBEP_TABIX_AKTUELL 1
0000
1000
%_SPACE
2
0
8 FORM BELEG_BEARBEITEN_ENDE
SAPMV45A
MV45AF0B_BELEG_BEARBEITEN_ENDE 268
WK_ABRUF_EXIST
2
0
SY-BINPT
2
0
BI_INFO-CTU_AMODUS
2
0
CATTAKTIV
2
0
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SY-REPID SAPMV45A
5454533422222222222222222222222222222222
310D645100000000000000000000000000000000
SY-MSGID FI
44222222222222222222
69000000000000000000
MAAPV ############## ##
2222222222222222222220000000000000022200
000000000000000000000000000C000000C00000
... + 40 ##### 00000000######
0000022222222222222222222233333333000000
0000C00000000000000000000000000000000000
... + 80 ######################
0000000000000000000000222222222222222222
C000000C000000C000000C000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
FCODE_SORT_AUFLOESEN AUFL
45442222222222222222
156C0000000000000000
XVCKEY[] Tableinitial
0000FFFD
0000FFFF
SPACE
2
0
SY-MSGNO 011
333
011
ORDTAB 000000 00
2222222222333333222222222222222222222233
0000000000000000000000000000000000000000
... + 40 000000##############
3333330000000000000022222
000000000000C000000C00000
SY-MSGV1 AUD
4542222222222222222222222222222222222222
1540000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
MODIFICATION_FLAG-NO_OUTPUT_CO
2
0
CVBFA 000000 000000 ####
2222222222222333333222222222233333320000
0000000000000000000000000000000000000000
... + 40 #### ######## 00000000000000
0000222000000002222222233333333333333222
000C0000000000C0000000000000000000000000
... + 80 00 00000000 #####
2222222222222222222223322233333333200000
0000000000000000000000000000000000000000
... + 120 ### ######## 000000#######
0002220000000022222222222223333330000000
00C0000000000C00000000000000000000000000
... + 160 ################ #############
0000000000000000222000000000000022222222
0000000000000000000000000000000000000000
... + 200 ####### ####
2222222222000000022222222222000022222222
0000000000000000C00000000000000000000000
... + 240 000000 ####
222333333220000
000000000000000
PARTAB1 000000000000000
2222222222222222222222222333333333333333
0000000000000000000000000000000000000000
... + 40 000
3332222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
XVBAK_UPDKZ I
4
9
UPDKZ_DELETE D
4
4
VVBRP[] Tableinitial
0000FFFD
0000FFFF
DPP_ACTIVE
2
0
XVBKD[] Table IT_37371x565
A2C554E560009000000030000000FFFF00009C00
82C100E1C1009E00100052000000FFFF44000200
... + 40
0000C020
50001E00
XVBKD 800 000000 21000001 CIFdanden
3332222222222333333223333333322444666666
800000000000000000000210000010039641E45E
... + 40 ong X #####0000000
6662222222222222222222522222000003333333
FE700000000000000000008000000000C0000000
... + 80 0000001 #####2008102320081023000000000
3333333222000003333333333333333333333333
00000010000100C2008102320081023000000000
... + 120 000000##### 000002
3333330000022222222222222222222223333332
0000000100C00000000000000000000000000020
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200 1000
2222222222222222223333222222222222222222
0000000000000000001000000000000000000000
... + 240 00
222222222222233
000000000000000
EFFECTIVITY_CHANGED
2
0
NA_VBKD 800 000000 21000001 CIFdanden
3332222222222333333223333333322444666666
800000000000000000000210000010039641E45E
... + 40 ong X #####0000000
6662222222222222222222522222000003333333
FE700000000000000000008000000000C0000000
... + 80 0000001 #####2008102320081023000000000
3333333222000003333333333333333333333333
00000010000100C2008102320081023000000000
... + 120 000000##### 000002
3333330000022222222222222222222223333332
0000000100C00000000000000000000000000020
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200 1000
2222222222222222223333222222222222222222
0000000000000000001000000000000000000000
... + 240 00
222222222222233
000000000000000
IVBEP1 000010 00000000002008102710000000002####
3333332333333333333333333333333333330000
0000100000000000020081027100000000022000
T180-TRTYP H
4
8
IVBEP[] Table IT_40082x56
500500000000A000000030000000FFFF0000BE00
8CB2000042008F00200080000000FFFF45000400
... + 40
0000C020
01001E00
VBAK 800 20081023090832SAPUSER 0
3332222222222333333333333335455545222223
8000000000000200810230908323105352000000
... + 40 00000000000000020081023C0YOR 00000000
3333333333333333333333343545222233333333
00000000000000020081023309F2000000000000
... + 80 ######0#AUD AUD 0000100ME
2222222222222200000030454224542333333344
000000000000000000030C1540015400000100D5
... + 120 L 0000000000000000 2008
4222222222333333333333333322222222223333
C000000000000000000000000000000000002008
... + 160 10231 SABI0102F2 100
3333322222222222544433334322333222222222
1023100000000000312901026200100000000000
... + 200 1000
2222222222222222222222222222222333322222
0000000000000000000000000000000100000000
... + 240
222222222222222
000000000000000
IVBEP1[] Table IT_38442x40
0205A5C590000000000020000000FFFF00003E00
84B28DB171004F00200080000000FFFF40008D00
... + 40
9000C020
60001400
VBUK 800 CAA AA CCCCCCCCA00000
3332222222222224442222442244444444433333
8000000000000003110000110033333333100000
... + 40 000 620
3332222222222222222222222222222222233322
0000000000000000000000000000000000062000
... + 80
22222222222222222
00000000000000000
9 FORM BELEG_SICHERN
SAPMV45A
MV45AF0B_BELEG_SICHERN 270
XFPLT[] Table IT_38480x696
0000E6C5A00000000000B0000000FFFF00003200
000002B171008F00000082000000FFFF40008C10
... + 40
0000C000
A0001E00
YVBAK 00000000000000 0
2222222222222333333333333332222222222223
0000000000000000000000000000000000000000
... + 40 00000000000000000000000 00000000
3333333333333333333333322222222233333333
0000000000000000000000000000000000000000
... + 80 ########
2222222222222200000000222222222222222222
000000000000000000000C000000000000000000
... + 120 0000000000000000 0000
2222222222333333333333333322222222223333
0000000000000000000000000000000000000000
... + 160 0000 000
3333222222222222222222222222333222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
YVBAPF[] Tableinitial
0000FFFD
0000FFFF
YVBAP[] Table IT_38540x1720
0000A6C5A00000000000B0000000FFFF0000B900
000006B1D100EF00000086000000FFFF40000E00
... + 40
0000C000
20001E00
XVBUV[] Table IT_17430x123
AE058CD58000C000000070000000FFFF00006F00
87A20AD18000F6000000B0000000FFFF44000800
... + 40
1000C020
00009400
YVBUV[] Tableinitial
0000FFFD
0000FFFF
%_DUMMY$$
2222
0000
DA_SUBRC 0
0000
0000
SYST ########################d###############
0000000010000000000000006000000000000000
1000100010001000000000004000000000000000
... + 40 ####################################|###
0000000000000000000000000000000000007000
100010001000000010000000000000000000C100
... + 80 ################S#######################
0000000000000000500000000000000000000000
0000000000004000310000000000000000000000
... + 120 ####################################¶###
000000000000000000000000000000001000B000
00000000000000000000000000000000D0006000
... + 160 ####ÿ####### u0152##XC############# E0 4
0000F0000000A800540000000000000222432223
0000F00000000C00830040000C0000C000500004
... + 200 001LIST N ####__S 800
3334455222420000555222222222222222223332
001C934000E01000FF3000000000000000008000
... + 240 00
222223322222222
000000000000000
FCODE SICH
54442222222222222222
39380000000000000000
FCODE_GLEICHE_SEITE ENT1
44532222222222222222
5E410000000000000000
XVBBE 0000000000
2222222222222333333333322222222222222222
0000000000000000000000000000000000000000
... + 40 00000000
2222222222222223333333322222222222222222
0000000000000000000000000000000000000000
... + 80 ################ 0000000000
2000000000000000022222222222223333333333
00000000C0000000C00000000000000000000000
... + 120 000
3332222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 ####################
2222222222222222222200000000000000000000
000000000000000000000000000000000000000C
... + 200 00000000 000000000000000000
2222222222233333333233333333333333333322
0000000000000000000000000000000000000000
... + 240 ###
222222222222000
000000000000000
CH_SUBRC 4
0000
4000
POSNR_NULL 000000
333333
000000
T178T
22222222222222222222222222
00000000000000000000000000
IVBPA2_PAGIND ###
000
00C
10 FORM FCODE_SICH
SAPMV45A
MV45AF0F_FCODE_SICH 9
TVAP-FPART
22
00
VTCOMWE-ALAND AU
452
150
IVBPA2_SELIND ###
000
00C
J_1BATL2T
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
SY-CALLD
2
0
CHARV V
5
6
TVAK-BEZOB
2
0
11 FORM FCODE_BEARBEITEN
SAPLV00F
LV00FF0F 90
SY-MSGV1 AUD
4542222222222222222222222222222222222222
1540000000000000000000000000000000000000
... + 40
2222222222
0000000000
FCODE SICH
54442222222222222222
39380000000000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
T185F-FCINT 0
3
0
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
AKTYP
2
0
SY-REPID SAPLV00F
5454533422222222222222222222222222222222
310C600600000000000000000000000000000000
T185-NMODUL FCODE_SICH
444445544422222222222222222222
63F45F393800000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
T185-NPROG SAPMV45A
5454533422222222222222222222222222222222
310D645100000000000000000000000000000000
%_SPACE
2
0
MODUL-POOL SAPMV45B
5454533422222222222222222222222222222222
310D645200000000000000000000000000000000
FLAG-ENDE
2
0
T185-CRMFUNC
222222222222222222222222222222
000000000000000000000000000000
SCREEN BT_PVMV
4555545222222222222222222222222222222222
24F06D6000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 BTA 00001#00000 ####
2222222222222224542222223333303333320000
0000000000000002410000000000100000000000
T185-FCODE SICH
54442222222222222222
39380000000000000000
12 FUNCTION SCREEN_SEQUENCE_CONTROL
SAPLV00F
LV00FU02 44
FUNKTION SICH
54442222222222222222
39380000000000000000
KOPFGRUPPE AU
4522
1500
POSITIONSGRUPPE N
4222
E000
PROGRAMM SAPMV45B
5454533422222222222222222222222222222222
310D645200000000000000000000000000000000
TYP
2
0
AKTYP
2
0
CUA_PARA1
2222222222222222
0000000000000000
CUA_PARA2
2222222222222222
000Hi Venkat,
Kindly share how this error is being fixed?
I hit the same error here...
CL_GM_ACTUAL_MGR -
Getting data in GATP Planning area on open Sales Orders yet to be PGI'ed
This is in context of allocation planning.
I understand there are two internal GATP relevant key figures AEMENGE (allocation) and KCQTY (incoming sales order quantity) which come over from R3. These two key figures are part of any allocation planning design to track consumption of allocation from sales orders.
We have a requirement to also get information on open sales orders not PGI'ed into GATP planning area. Is there a way to do this without configuring SNP and only core interface ? (Releasing data from SNP to GATP does not work since the levels are different)Hi
Just to correct you. The tcode is LBWQ and not LBQW.
Well as per your lines that it is not possible for 400 users to manually feed the data after changes .I totally agree.
To help get the same functionality we have v3 jobs or direct delta which serves the same job for you.
This is a job that runs at a regular interval as per you set it in the tcode LBWE.
If the Datasource is Delta Enabled then only these jobs would be available to run for those data sources and if incase the DS is Full then you dont need these jobs at all.
Thus once you set your DS as Delta. Go to LBWE select the DS you are working upon for delta
After finding the DS you see two options update mode and update.
Update mode -you can choose the type of update mode for example direct, queued and so on.. Generally we use Queued Detla
Update - you have to set here how do you want it to run and from wat date etc.clickin on job control gives you a window where in u can set all the fields as per ur requirement.
Once after these are done your job would automatically run and collect the changed records to the delta queue and from there you can pull the same using info pack.
Hope that clarifies your doubt to some extent.
Edited by: Puneet Chawla on Jan 29, 2010 8:52 AM -
Mapping between Sales Order-Schedule-Line and Delivery-item
Hi together,
I want to extend the Datasource 2LIS_12_VCITM (Delivery-number, -item, Order-number,-item is available) by Sales Order Schedule Line.
Could not find any ERP table (VBEP and LIPS allow a mapping only on item level) for the mapping between Sales Order Schedule Line and Delivery item yet. The use of the extractor 2LIS_12_VCSCL for the extention (e.g. infoset) afterwards is no option.
Thanks for your help in advance!!
Assign full points!!
SvenHi Reddy,
thanks for your answer.
I know that I have to add this field.. but the problem is, how to fill this field. I don't know how to map the delivery-item with the schedule line-item. -
Change in Item category in Sales order
Hi,
We have one requirement to change the quantity in the Billing document
our requirement goes like this,
Order was created with 10 Qty and PGI also done with 10qty, But physically customer receives 9 qty and Billing done with 10qty.
Now customers will not accept for the Billing and Business has to change the quantity in the Billing without reversig PGI
As per the legal regulations, we cannot reverse the PGI and change the quantity in Billing
But as per the standard, we cannot change the ITEM category in the sales order once the subsequent document is created.
can you please let me know is there any solution to change the Item category in the sales order using User exit of any other way
regards,
santoshSince I was handling similar scenarios quite frequently when I was in domain, from my experience, I can share the same.
It is known to customer also that billing cannot be changed once it is generated. Hence, the client can request the customer to either deduct the amount to that extent while releasing the payment against that billing document or the client can give one number extra or credit in the subsequent shipment. Any customer will accept for this.
Meanwhile, I also dont understand why you want to change the item category after billing and what you would like to achieve over this. If the above options is not acceptable to client, then the best approach would be generating a credit note straightaway against that billing document and set right the records.
thanks
G. Lakshmipathi -
Revenue Recognition - error while creating sales order
Hi,
one of my colleague is having a Problem. Its very urgent. could you guys help.
I have used Revenue recog as"b" and Accrual start period as "a".
We are getting the error while creating a sales order, G/L account no. not found.
We have checked all the account assignment config but couldn't find anything.Hi guys,
I have a question, we being SD consultants, do we deal with n e of the revenue issues, I am assuming we deal it to a really brief extent, but I am not familiar with the areas of doing it, so could someone please help me by letting me know the areas where we deal with those issues and how are they looked upon, any material would also be great.
Just in case, my email is : [email protected]
Look forward for a response
Thanks.. -
Hi,
We maintained all setting of Incompleteness log for Salesd order but still sales order is getting save without entering any material at item line.
WE maintained VBAP - MATNR
regards,
akshayChoose a relevant Incompletion Control: Status Group for your incompleteness procedure.
Status Groups - this is in IMG activity, you use status groups to define the status of incomplete sales and distribution documents. Then assign the "status" group to the fields in an incompleteness procedure.
In the status group, you define which functions may be carried out for an incomplete sales and distribution document, or for the items where a field entry is missing. You use this function to block a document for delivery, billing, or pricing. In addition, you can check at header level whether the general data is complete.
For instance, fields that are defined for deliveries do not also have to apply to the billing document. If you allocate the relevant status group to these fields in the incompleteness procedure, you can create a billing document for the incomplete sales order but not a delivery.
Activities
1. Check to what extent you can use the defaults for status groups that are defined in the standard system.
2. Change the existing status groups according to your requirements. Create new groups, if necessary.
3. Afterwards specify status groups for fields in the incompleteness procedures (see section Define Incompleteness Procedures)..
Thanks & Regards
JP -
Cost analysis through Purchase Order created from Sales Order
Hi Experts,
This is the scenario: There is an Item No. which is not stocked in warehouse and is purchased only when customers ask for it. The cost of the sales order line having this item is calculated by the Purchase Order line on which the item is there. (The PO have items for other Sales Orders as well. And, Sales Orders have multiple item types) The Sales Order have the PO no. against it and Purchase Order has SO no. against the line. This is all done using MS Access and Sage Accounts. Lots of free typing and manual cost analysis involved.
I have gathered from this forum that we can create Purchase Order from the Sales Order. The Document No. information can be pulled from one another using Formatted Search. Can we do the accounting and cost analysis as well?
Please let me know if I have not made myself clear.
Thank you in advance and kind regards.
IC
Edited by: iancameron03 on Sep 20, 2011 4:35 PMHi Ian,
I concur with Faraz, it is better if you use procurement document facility in doing back to back transaction from SO to PO.
However, in your case, I'm afraid you can't analyze the gross profit and recording the accounting related activity as your request using standard SAP B1 function.
As for gross profit case:
Since you're actually using workaround in order to evade all hassles in maintaining all item master data related to this case, you create just one item code called S1 right?
SO DocEntry - SO Line # - Item Code - Item Name - Quantity - Price
1001 - 0 - S1 - Table - 2 - 100
1001 - 1 - S1 - Chair - 8 - 25
1001 - 2 - S1 - Cloth - 3 - 10
PO # - PO Line # - PO BaseEntry (SO DocEntry) - PO BaseLine (SO Line #) - Item Code - Item Name - Quantity - Price
2001 - 0 - 1001 - 0 - S1 - 2 - 100
2001 - 1 - 1001 - 1 - S1 - 8 - 25
2001 - 2 - 1001 - 2 - S1 - 3 - 10
Note that standard B1 gross profit calculation is that system will compare selling price for each item with item cost / certain price list of each respective item. However, in your case, you put all item as a single item master. Thus, system couldn't compare Table to Table, Chair to Chair, Cloth to Cloth since the item cost for these 3 items will be the same, the price list for these 3 items will also be the same since it is actually only one master data. Of course you could update the gross profit calculation manually for each SO, but to be honest it seems rather weird to do this manually.
So, in order to simulate the gross profit calculation, you need to create a custom query and comparing PO line no with SO line no.
As far as accounting related recording concern, I'm afraid you can't do it
1. SO 1 : Item Table - Selling price 130 ; Item Chair - Selling price 30
2. PO 1 (linked to SO 1) : Item Table - Purchase price 100 ; Item Chair - Purchase price 25
3. SO 2 : Item Table - Selling price 150 ; Item Chair - Selling price 40
4. PO 2 (linked to SO 2) : Item Table - Purchase price 110 ; Item Chair - Purchase price 30
Correct me if I'm wrong, you want to record accounting wise that CoGS of Delivery based on SO 1 is 100 for Table and 25 for Chair, isn't it? No matter what costing method you use, you can't achieve this.
If you use moving average, system will average both Table and Chair cost price, since it is actually one item master data. Even if you distinguish each item as a master data, system will average the cost price for Table and Cloth by the time GR for PO 1 and PO 2 occurred.
Example (order by sequence of event):
1. GR based on PO 1 - Table - Purchase price = 100, therefore Item cost = 100
2. GR based on PO 2 - Table - Purchase price = 110, therefore Item cost = 105 (considering quantity only one for both PO)
3. Delivery based on SO 1 - Table - CoGS incurred will be 105, not 100
To certain extent, same thing could be said with FIFO costing method
1. GR based on PO 1 - Table - Purchase price = 100 (qty 1)
2. GR based on PO 2 - Table - Purchase price = 110 (qty 1)
3. Delivery based on SO 1 - Table - CoGS incurred will be 100 (qty 1)
4. Delivery based on SO 2 - Table - CoGS incurred will be 110 (qty 1)
At first glance, it seems right since the CoGS for SO 1 is 100, tied up with purchase price for PO 1. And CoGS for SO 2 is 110, tied up with purchase price for PO 2. But we're using assumption here, we're assuming the sequence of Goods Receipt of PO and Delivery of SO occurred in the very same sequence as the issuance of SO and PO.
1. GR based on PO 1 - Table - Purchase price = 100 (qty 1)
2. GR based on PO 2 - Table - Purchase price = 110 (qty 1)
3. Delivery based on SO 2 - Table - CoGS incurred will be 100 (qty 1)
4. Delivery based on SO 1 - Table - CoGS incurred will be 110 (qty 1)
If above scenario / sequence that happened, you will get the wrong figure of gross profit since the Delivery of SO 2 will take the item cost based on GR of PO 1. Since we're actually talking about real life business process, who can guarantee that above scenario wouldn't happen? It is possible that you send goods to customer who ordered late in real life, too much possibility that it is better for you to mitigate such result.
My suggestion would be that you record the accounting transaction based on standard business process, no need to really capture the actual cost and actual gross profit for certain SO and PO. Too complicated, and the software itself doesn't cater this kind of requirement. Best thing you could do only create custom query for gross profit simulation calculation, but for very accurate accounting recording, IMO you should forget it. Hope this help.
Best Regards,
Hendry Wijaya -
Condition records in ERP sales order still there after deletion
Hello,
I have maintained all the settings needed for lean order (creating ERP sales order from crm opportunity in CRM webui).
Now when i create a ERP sales order in CRM using LORD, there are certain condition values determined correctly (note that they are variant based condition values).
However depending upon the sales scenario, certain conditions are to be deleted from pricing details at item level. So, far no issue.
After I save this ERP sales order, and go to see it in our ERP system, i find that those condition values are still there !
I am unable to understand why this is happening.
Please help me.
RegardsHi,
Thanks for your reply, for your question "One more point confirm with you, you create sale order in CRM as a CRM order ( type LORD), and the order will transfer to ERP by CRM middleware, right?" , the answer is no i dont create a CRM order, however i create an ERP order in crm webclient. This feature of CRM 7.0 is explained in following documentation:
http://help.sap.com/saphelp_crm70/helpdata/en/17/99fb62928c46c28c10f3ebc52fdfa8/frameset.htm (then navigate to Entry of ERP Sales Transactions in SAP CRM)
As you also asked me to change the settings of condition type as manual input, which cannot be done because this will affect our business process to large extent, and my users will not accept it, hope you understand my situation
Please let me know if you can help me in some other way, or you want me to check some more settings.
Regards
Edited by: ar_on_crm on Jan 6, 2011 11:03 AM -
Incompletion procedure -Sales order Item level.
Hi
I want to add the field "MATERIAL SALES TEXT" in Incompletion procedure -Sales order Item level.
The Table that i need to enter in procedure is VBAP.
But what should be the "Field Name" and Screen for creating missing data?
Plz Help....
Regards
SubhasishField ARKTX refers to 'Description' of material in sales order and not to 'material item text'.
'Material sales text' flows into sales order from the text you maintained in customer master record or Material master record.
Of course, you could also maintain sales text at sales order stage also.
Incompletion process inspects specific fields in order to see if data has been maintained in these fields. Should data not be maintained in these specified fields, the system is told how to respond, that is, whether or not to give a warning message and to what extent does it allow further processing of the document.
Material sales text is not a field.
So, you cannot add material sales text at incompletion procedure.
Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme. -
Payment methods in the sales order
Hi Gurus,
How can we indicate the payment methods in the sales order.
Thanks for your quick answer.Hi,
Payment method can be found in CMR>Company Code Data>Payment Transations tab: Here you can specify the payment method {incoming/outgoing}
> List of the Payment Methods to be Considered
List of payment methods which may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.
If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item which are not listed in the master record.
Hope this will help you in some extent.
Hrishi -
Dear experts,
In the sales order, I can view the availability when clicking availability check. There're two fields, like "delivery", "confirmed delivery". I create the delivery for the sales order. But those two fields does not get updated.
What does those fields mean by? What's the usage of them? Plz advise. Many thanks.Confirmed Quantity
When you create a sale order for a material and if stock is made available for that, this column will get filled to the extent of stock available. The control is in your schedule line category VOV6 where you can see a field "Availability". You have to tick this box.
Delivered quantity
This is based on your copy control VTLA where for your item category, you can see two fields, viz.Update document flow and Pos./neg.quantity. You have to tick the box for Update document flow and maintain plus sign to the next field.
thanks
G. Lakshmipathi -
Sales order - customer numbers
hi all,
in sales order creation, who is involved in certain calculations whether
sold-to or ship-to party if both are specified.
if atleast one is not specified who will be the other party whether implicitly
it will consider the same party(which ever is specified i.e either sold-to or ship-to)
if any one know abt credit check
whether the values in knkk table
should reflect either
ship-to party(as customer)credit control areacredit account number(KNKLI)
(or)sold-to party(as customer)credit control areacredit account number(KNKLI)
(or) simply credit account number is enough.hi
to the extent of my understanding sold to is more important and the one that would be considered for a sales order.
we can have multiple ship to parties for a given sold to. as in you may have the customer to whom you are selling the goods but he may have different shipping locations assigned. so its the sold to party that would be considered by default for any claculations that need to be done for rebates and any other of that sorts.
in some cases Ship to party is considered where taxing should be taken care (Beyond specifed boundaries)
All the above is to the extent of my understanding.. correct me if I am wrong..
Santosh -
Prerequisites for archiving the sales order
Hi ,
What are the prerequisites for archiving a sales order? What is the last business transaction from which the archiving process is triggered? Is it necessary to set status CLSD on the sales order for archiving ? what are the other system statuses that should be set for archiving a sales order?
Thanks & Regards
SanHi Santosh,
Sales Order is linked to other subsequent documents in the Order Processing cycle like Delivery, Invoice , Shipments, etc. So, we've to make sure that all the dependencies are removed before we can start to archive an SO.
You can see the dependencies in SARA Transaction (Goto->Network Graphic).
The SO archiving program checks if the status of the subsequent documents are Completed or not. (status in VBUK table is "C") .
There are other options like Residence Time, Existence of PO , Existing of Accouting Doc.
You can select the options, based on your company's decision regarding the extent of SO archiving they wanted to achieve.
The program will throw the messages appropriately, based on the checks it performed and appropriate actions can be taken from the document side .
This is a link , which explains the checks the program does before archiving.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/a9/55c7d490a111d1a5510000e82deaaa/content.htm
Regards,
Shail.
Maybe you are looking for
-
Oracle 8i Installation Problem on w2000
Hi, I am trying to install Oracle 8i(8.1.7) downloaded from the OTN on a w2000 Pro computer. When I click on the install/Desisntall button, nothing happens and the installation windows is closed. Could someone helps me to resolve it ? Thanks. Yota
-
I have followed Integration of a Tree Structure in a Web Dynpro Table from SDN, all cofigurations are done and it is retrieving values correctly. But, the subtree entries are not get added to the corresponding nodes. All sub values are added to the e
-
I have completed a software update as prompted. However, all "Pages" and "Numbers" files are completely blank. Please advise
-
Anyone managed to change SBS2011 RWW to allow UPN username?
Per the subject, in SBS2011 you can use a UPN logon for OWA but not for RWW. Was wondering if anyone had ever changed the logon page to allow this?
-
Design Studio logon screen missing
Installed Design studio 1.3 on Windows 7 machine. Launched the application. I see welcome screen. But i don't see logon screen. Any help?