Problem with post goods issue in SD std. delivery
hi
while doing post goods issue of a delivery in VL01n its showing run time error. the error message is gvn below.
Information on where terminated
Termination occurred in the ABAP program "SAPLMBWL" - in
"MB_POST_GOODS_MOVEMENT".
The main program was "SAPMV50A ".
In the source code you have the termination point in line 59
of the (Include) program "LMBWLU21".
Source Code Extract
Line SourceCde
29 * when a goods movement for an inbound or outbound delivery is posted
30 * directly from VL31N/ VL01N, XBLNR is not yet known when we call
31 * CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32 * BKPF as well. There is no other way to forward XBLNR to FI as not
33 * every document is posted by MB_CREATE -> a new function module in
34 * MBWL for transferring the information, called by FI, meant to load
35 * the complete function group for all MBxx postings when this isn't
36 * required (Performance). Would be the better way to transport the
37 * information after switching off MBxx in later release.
38 * corresponding IMPORT ... FROM MEMORY ... can be found in
39 * AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40 l_mem_id = 'MKPF-XBLNR'. " 641365
41 EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
42 ENDIF.
43 IF xmkpf-xabln IS INITIAL. "note 434093
44 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
45 ENDIF. "note 434093
46
47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50 CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51 EXCEPTIONS
52 error_message = 4.
53 * As soon as we have started to put things into UPDATE TASK, we must
54 * ensure that errors definitely terminate the transaction.
55 * MESSAGE A is not sufficient because it can be catched from
56 * external callers which COMMIT WORK afterwards, resulting in
57 * incomplete updates. Read note 385830 for the full story.
58 IF NOT sy-subrc IS INITIAL.
>>>>> MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
60 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61 * MESSAGE A263.
62 ENDIF.
if there is any configuration step for post goods issue in SD thn plz mention it.
Plz help..
Hi Lakshmipati,
I have maintained movement type 601 at OMJJ. I hav also added the filed cost center in that (before it was not available).
I checked GL acct at fs00, it is already contain field status group g004 and the check box "post automaticallyt" is also activated. The cost element has also assigned to cost center. After assigning the cost center to cost element, the error is changed to fld selection for mvmt type 601/ acct 300021 differs for cost center
But i noticed one thing: If i chage the field status group to g006, the error has not appeared and giving the other error:
valuation area xxx2 (plant) not yet ptoductive with material ledger this error has been already posted by me but not yet received correct answer.
Kindly provide the solution for this.
Regads
Sabera
Similar Messages
-
hi
I'm doing a delivery using vl01n bt at post goods issue its showing run time error.the error message details gvn below.
Information on where terminated
Termination occurred in the ABAP program "SAPLMBWL" - in
"MB_POST_GOODS_MOVEMENT".
The main program was "SAPMV50A ".
In the source code you have the termination point in line 59
of the (Include) program "LMBWLU21".
Source Code Extract
Line SourceCde
29 * when a goods movement for an inbound or outbound delivery is posted
30 * directly from VL31N/ VL01N, XBLNR is not yet known when we call
31 * CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32 * BKPF as well. There is no other way to forward XBLNR to FI as not
33 * every document is posted by MB_CREATE -> a new function module in
34 * MBWL for transferring the information, called by FI, meant to load
35 * the complete function group for all MBxx postings when this isn't
36 * required (Performance). Would be the better way to transport the
37 * information after switching off MBxx in later release.
38 * corresponding IMPORT ... FROM MEMORY ... can be found in
39 * AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40 l_mem_id = 'MKPF-XBLNR'. " 641365
41 EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
42 ENDIF.
43 IF xmkpf-xabln IS INITIAL. "note 434093
44 CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
45 ENDIF. "note 434093
46
47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50 CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51 EXCEPTIONS
52 error_message = 4.
53 * As soon as we have started to put things into UPDATE TASK, we must
54 * ensure that errors definitely terminate the transaction.
55 * MESSAGE A is not sufficient because it can be catched from
56 * external callers which COMMIT WORK afterwards, resulting in
57 * incomplete updates. Read note 385830 for the full story.
58 IF NOT sy-subrc IS INITIAL.
>>>>> MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
60 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61 * MESSAGE A263.
62 ENDIF.
plz tell me the configuration steps for post goods issue in SD if applicable.Hi Lakshmipati,
I have maintained movement type 601 at OMJJ. I hav also added the filed cost center in that (before it was not available).
I checked GL acct at fs00, it is already contain field status group g004 and the check box "post automaticallyt" is also activated. The cost element has also assigned to cost center. After assigning the cost center to cost element, the error is changed to fld selection for mvmt type 601/ acct 300021 differs for cost center
But i noticed one thing: If i chage the field status group to g006, the error has not appeared and giving the other error:
valuation area xxx2 (plant) not yet ptoductive with material ledger this error has been already posted by me but not yet received correct answer.
Kindly provide the solution for this.
Regads
Sabera -
Idoc to post goods issue against an outbound delivery
We happened to simulate both the idocs 'WPUWBW01' and 'MBGMCR02' for posting goods issue for an outbound delivery but failed.
Request you people to help us on this. Is there another idoc that we have to use to post GI... if so please let us know... and if we are using the right one, guess we are not executing it in the right way... in such a case please guide us with the steps...
Thanks
Arun
We got hold of the Idoc type 'DELVRY03 PGI SHPCON' we are able to post the Idoc but we are able to do the packing only or we are able to change the deliveries but the PGI is not happening..
please help us on this.. is there some condig that updates the delivery with the PGi or is there something else do be done in the Idoc....
will provide additional details if required.
ThanksHi Arun,
There are no configuration settings in this. It is development that your abaper need to carry out.
Explain to him that this is the func module. And intrun it has to either trigger a BDC or BAPI for creating packing and PGI.
He should then do the recording of that and will assign the program pertaining to BDC with in the function module.
One more suggestion is to put the same query in ABAP section too. U will definitely get a positive response.
Hope this helps.
Kind Regards
Chakradhar -
Automatic Billing with Post Goods Issue
I need Help on How to Make Automatic Billing while Posting Goods Issue, The Process Flow as Below:
VA01 Make Sales Order ( Normal Sales Order "OR" )
VL01N ( Picking and Post Goods Issue )
VF01 ( Make Billing )
My customer needs when he Posts Goods Issue in VL01N , automatically the Billing document to be Posted and The Invoice Printed, without Going to VF01 to make the Billing.
We are using SAP ECC 6.0
Please Note: i need it on how to do it in customization and with out using the Report (RV60SBT1) which makes collective billing in the background using a job
Thanks for Your HelpDear Omar,
One way is to use background jobs which will create billing documents in the background (VF06).
Another way is write a BDC program.
Refer to following links, in which the same has been discussed.
Automatic billing
Re: How to set up in SAP to have automatic billing after PGI
Hope, you may find this informaton useful.
Best Regards,
Amit -
Not able to post goods issue in case of delivery against a repair order
A faulty part was received from customer and repaired and further it has to be sent to customer. Then delivery has been created. Also handling unit has been assigned. Now at the time of post goods issue, following error is appeared.
"Deficit of sales order stock".
When I checked with transaction MMBE, I don't find any stock assigned to this order.Hi Atul
Please ensure that the settings is as per the followign link
http://help.sap.com/saphelp_47x200/helpdata/en/00/044f350bea3278e10000009b38f839/frameset.htm
Thanks
G. Lakshmipathi -
I can't post goods issue for the outbound delivery
I select the indicator of GI via delivery in transport block via TCODE OPKP and assign the production profile to the work schedule view of the material master.then I create a production order for the material and release it.I do the wm material staging for the producion order via TCODE LP10,An outbound delivery was created automatically and the movement type is 261.then I pick for the delivery and confirm the transfer order.When I do the post goods issue there is a error message .
E M7 226
Update control of movement type incorrect (entry 261 X X _ _ _ V )
then I see the onlinehelp,I find the configurations are ok.
the content is following in table t345.
werks supply area material staging indicaor
1000 PVB 1310WM 1 1 wmpp 10000Please kindly refer to the attached notes below :
523509 FAQ: Control tables (no Customizing)
161729 M7226 with KZVBR=V
Hope this helps. -
Problem with MIGO goods issue to a Service Order
Hello All
I have checked through out the forum as well as google and can not find the answer to my issue. Please read the below details and advise....
In MIGO; when trying to perform a goods issue to a service order (created in IW31) I get an error message the document does not contain any selectable items. I can not get passed this. When I use the transaction MB11, it works just fine. I went to the allowed transactions in OMJJ to ensure MIGO was listed as an allowed transaction... and MIGO is listed so I know that is not my issue. It is not related to the service order not being released as it is and plus if it was not released it would not work in MB11. I need this to work for the transaction MIGO....Please someone guide me in the proper direction of what is missing.Hi Kimberly,
When you post the goods issue as an unplanned goods movement against the order, the reservation is not even read, so it is never updated.
The data that you enter manually in this unplanned goods issue does not even need to match with the data in the reservation: the material, the plant... evrything can be different. The order is just a CO Account Assignment in this case and the reservation is not processed in any moment. This way, it is not possible to close the reservation when posting this kind of unplanned goods issue, as the reservation is not even considered (and, therefore, never updated).
It is only when you post the planned goods issue referencing the order directly when you really post your goods issue with reference to the reservation behind the order. Only in this case is when the data in the posting is checked against the reservation (the material, the plant, etc cannot be changed because they are taken directly from the reservation). Also, it is only in this case when the quantity in the posting is checked against the quantity in the reservation. If we issue the total reserved quantity, the reservation is closed automatically.
In the first case for the unplanned goods issue there is never an automatic update of the reservation because the posting does not even consider the reservation. It is only when you post the goods movement with reference to the order (in MB1A using "To Order..." and in MIGO "Goods Issue + Order") when the reservation is taken into account in the goods movement and, therefore, updated.
You can also refer to the SAP Library:
[http://help.sap.com/saphelp_erp2005/helpdata/en/a5/6337db43a211d189410000e829fbbd/frameset.htm]
It says:
"This withdrawal is unplanned because there is no reservation to be referenced."
An unplanned goods issue with the movement 261 and the order (working as CO account assignment object) is more or less the same as a 201 for a cost center. The cost center and the order are just CO Objects in this scenario.
I hope this helps you further!
Best regards,
Esther. -
Problem with posting goods receipt
Hi Gurus,
My PO is created for a material with quantity 45000 nos. Overdelivery tolerance is 20%. Already GR is posted for 48000 nos and MIRO is posted for the same.
Now, I want to post GR for the remianing qty ie. (45000*1.2) - 48000 = 6000 nos. When I try in MIGO, system says "No Selectable items for this PO".
What may be the possible reason? Please help me.
Regards,
Sastryyour PO has the delivery completed flag, as the first GR was already within the 20 % tolerance.
You can either remove the flag from the PO and then do MIGO.
Or you define your settings in MIGO and set a flag for propose all items.
Then you will even get closed items as proposal for a goods receipt. -
Special stock partner data problem in ERP system during "Post Goods issue"
Hi all,
I have a (probably) customizing issue in an ERP 6.0 EhP4 test system which not occurs in the ERP 6.0 test system. There is a difference but no one could tell me, what causes the problem in this scenario:
I have two customers, C1 and C2. C2 is the special stock partner (SB) of C1.
I've created a Consignment Fill-up order, then a delivery document based on the order and posted it with "Post Goods Issue". During the update process, a function module (SD_PARTNER_UPDATE) receives partner data in an internal table which contains the sold-to, ship-to and special partner data.
When we tried the same process in the ERP 6.0 EhP4 test system then special-partner data did not occur in the parameter table (I've used the same customers and materials). The special stock partner is probably not taken into consideration due to some customizing settings.
My question is what should I change in the customization to run the process the same way as in the ERP 6.0 system? As far as I know there are no new modifications which have effect on this area, and the used test customers and materials are almost the same - there are no noticable differences.
Thanks in advance.
AkosI tried setting that field in the sale order this morning. By defaulting it to "C"; I was able to get warning message for TAE line. I was able to post goods with TAE and TAQ, being different quantities. I need the check to determine if TAE and TAQ delivery quantity are different. Using this fields seems to be line specific. Thanks for the suggestion. I now know what that field does to the delivery.
I rewarded points.
Thanks,
Tony -
When I Press the Post Goods Issue Button for a delivery in SD the error dump appears.
Runtime Errors MESSAGE_TYPE_X
Date and Time 10/15/2008 06:38:52
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
No RFC destination is defined for SAP Global Trade Services
Long text of error message:
Technical information about the message:
Message class....... "/SAPSLL/PLUGINR3"
Number.............. 002
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMBWL" or "LMBWLU21"
"MB_POST_GOODS_MOVEMENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "biw7sap"
Network address...... "68.88.249.38"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "BIW7SAP"
Database type..... "ORACLE"
Database name..... "ECS"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 20 2007 00:45:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 102
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 26130600
Heap.... 0
Page.... 57344
MM Used. 19070624
MM Free. 785208
User and Transaction
Client.............. 800
User................ "CUSER14"
Language key........ "E"
Transaction......... "VL02N "
Program............. "SAPLMBWL"
Screen.............. "SAPMV50A 1000"
Screen line......... 39
Information on where terminated
Termination occurred in the ABAP program "SAPLMBWL" - in
"MB_POST_GOODS_MOVEMENT".
The main program was "SAPMV50A ".
In the source code you have the termination point in line 59
of the (Include) program "LMBWLU21".
Source Code Extract
Line
SourceCde
29
when a goods movement for an inbound or outbound delivery is posted
30
directly from VL31N/ VL01N, XBLNR is not yet known when we call
31
CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
32
BKPF as well. There is no other way to forward XBLNR to FI as not
33
every document is posted by MB_CREATE -> a new function module in
34
MBWL for transferring the information, called by FI, meant to load
35
the complete function group for all MBxx postings when this isn't
36
required (Performance). Would be the better way to transport the
37
information after switching off MBxx in later release.
38
corresponding IMPORT ... FROM MEMORY ... can be found in
39
AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40
l_mem_id = 'MKPF-XBLNR'. " 641365
41
EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365
42
ENDIF.
43
IF xmkpf-xabln IS INITIAL. "note 434093
44
CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093
45
ENDIF. "note 434093
46
47
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49
ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50
CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51
EXCEPTIONS
52
error_message = 4.
53
As soon as we have started to put things into UPDATE TASK, we must
54
ensure that errors definitely terminate the transaction.
55
MESSAGE A is not sufficient because it can be catched from
56
external callers which COMMIT WORK afterwards, resulting in
57
incomplete updates. Read note 385830 for the full story.
58
IF NOT sy-subrc IS INITIAL.
>>>>>
MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830
60
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61
MESSAGE A263.
62
ENDIF.
63
Optische Archivierung
64
Spaete Erfassung mit Barcode
65
Redesign of barcode handling -> note 780365
66
PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67
xmkpf-mjahr
68
barcode.
69
70
MOVE-CORRESPONDING xmkpf TO emkpf.
71
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72
EXCEPTIONS
73
error_message = 4.
74
MOVE-CORRESPONDING xmkpf TO emkpf.
75
CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76
EXCEPTIONS
77
error_message = 4.
78
IF NOT sy-subrc IS INITIAL.
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
6
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
W0
SY-UCOMM
WABU_T
SY-TITLE
Delivery 80015203 Change: Overview
SY-MSGTY
X
SY-MSGID
/SAPSLL/PLUGINR3
SY-MSGNO
002
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081015
SY-UZEIT
063852
SY-XPROG
SAPLBPFC
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
10 FUNCTION SAPLMBWL LMBWLU21 59
MB_POST_GOODS_MOVEMENT
9 FORM SAPMV50A FV50XF0B_BELEG_SICHERN 769
BELEG_SICHERN_POST
8 FORM SAPMV50A FV50XF0B_BELEG_SICHERN 86
BELEG_SICHERN_01
7 FORM SAPMV50A FV50XF0B_BELEG_SICHERN 16
BELEG_SICHERN
6 FORM SAPMV50A MV50AF0F_FCODE_SICH_OHNE_CHECK 10
FCODE_SICH_OHNE_CHECK
5 FORM SAPMV50A MV50AF0F_FCODE_WABU 11
FCODE_WABU
4 FORM SAPLV00F LV00FF0F 92
FCODE_BEARBEITEN
3 FUNCTION SAPLV00F LV00FU02 44
SCREEN_SEQUENCE_CONTROL
2 FORM SAPMV50A MV50AF0F_FCODE_BEARBEITEN 62
FCODE_BEARBEITEN
1 MODULE (PAI) SAPMV50A MV50AI0F 52
FCODE_BEARBEITEN
Chosen variables
Name
Val.
No. 10 Ty. FUNCTION
Name MB_POST_GOODS_MOVEMENT
XBLNR_SD
0080015203
3333333333
0080015203
0000000000
0000000000
EMKPF
000000000000000000 ##
2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
XMSSA[]
Table IT_589[0x196]
FUNCTION-POOL=MBWLDATA=XMSSA[]
Table reference: 307
TABH+ 0(20) = 00000000200D869300000000330100004D020000
TABH+ 20(20) = 00000000C4000000FFFFFFFF04090300E01B0000
TABH+ 40( 8) = 08000000C1108001
store = 0x00000000
ext1 = 0x200D8693
shmId = 0 (0x00000000)
id = 307 (0x33010000)
label = 589 (0x4D020000)
fill = 0 (0x00000000)
leng = 196 (0xC4000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000134
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xD80C8693
>>>>> 2nd level extension part <<<<<
tabhBack = 0x980C8693
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
RRESWK
22222222222
00000000000
00000000000
00000000000
%_SPACE
2
0
0
0
L_MEM_ID
MKPF-XBLNR
4454254445
DB06D82CE2
0000000000
0000000000
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
RNAME
R
52222
20000
00000
00000
SCREEN
BT_UALL
4555444222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
24F51CC000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_RSTRUCT
Table[initial]
XMKPF-XABLN
2222222222
0000000000
0000000000
0000000000
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
SAPLMBWL
5454445422222222222222222222222222222222
310CD27C00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ODM07M[]
Table[initial]
GT_GOCOMP
000000000000 #### 00000000000000
3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
4
0000
4000
L_ATPCB
22222
00000
00000
00000
XMKPF-MBLNR
4900035075
3333333333
4900035075
0000000000
0000000000
XMKPF-MJAHR
2008
3333
2008
0000
0000
BARCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T003
800WL49AMS XX XXXXXH
3335433445222222222222222222222222225522555554222222
8007C491D3000000000000000000000000008800888888000000
0000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000
KNVV
00000000 000
2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T064B
2222222222222222222222
0000000000000000000000
0000000000000000000000
0000000000000000000000
VGMSEG[]
Table[initial]
No. 9 Ty. FORM
Name BELEG_SICHERN_POST
MAT_AUF_HINWEIS_COPY
2
0
0
0
XLIKP[]
Table IT_392[1x2360]
PROGRAM=SAPMV50ADATA=XLIKP[]
Table reference: 197
TABH+ 0(20) = 082D1E94E0C8119300000000C500000088010000
TABH+ 20(20) = 01000000380900003000000004FC0100D0070000
TABH+ 40( 8) = 04000000C1108001
store = 0x082D1E94
ext1 = 0xE0C81193
shmId = 0 (0x00000000)
id = 197 (0xC5000000)
label = 392 (0x88010000)
fill = 1 (0x01000000)
leng = 2360 (0x38090000)
loop = 48 (0x30000000)
xtyp = TYPE#000027
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x18081E94
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 1541 (0x05060000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0xA87F1B94
collHook = 0x00000000
ext2 = 0x28940F93
>>>>> 2nd level extension part <<<<<
tabhBack = 0x70A22B93
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
XLIKP
8000080015203CUSER14 06580920081014 Z0011000LF X20081016200810152008101420081017200
3333333333333455453322222333333333333332222225333333344222533333333333333333333333333333333333
800008001520335352140000006580920081014000000A0011000C6000820081016200810152008101420081017200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<%_L195>
CVBAP
8000000012132000020T-AS301 T-AS301 0201 Su
3333333333333333333524533322222222222524533322222222222222222222222222222222222222233332222257
80000000121320000204D13301000000000004D1330100000000000000000000000000000000000000002010000035
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
MAT_AUF_HINWEIS_GEPRUEFT
2
0
0
0
<%_L195>-UPDKZ
UPDKZ_DELETE
D
4
4
0
0
IVBPA52_PAGIND
0.0.1.
000
00C
VBUK_KEIN_KREDITCHECK
2
0
0
0
XLIPS[]
Table IT_83[1x3552]
PROGRAM=SAPMV50ADATA=XLIPS[]
Table reference: 50
TABH+ 0(20) = E8F54D93F0282893000000003200000053000000
TABH+ 20(20) = 01000000E00D0000FFFFFFFF0400000080330000
TABH+ 40( 8) = 04000000C1108401
store = 0xE8F54D93
ext1 = 0xF0282893
shmId = 0 (0x00000000)
id = 50 (0x32000000)
label = 83 (0x53000000)
fill = 1 (0x01000000)
leng = 3552 (0xE00D0000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000260
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xD0896993
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 410 (0x9A010000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 4 (0x04000000)
lineAlloc = 4 (0x04000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0xC8402493
collHook = 0x00000000
ext2 = 0x50E41293
>>>>> 2nd level extension part <<<<<
tabhBack = 0xC8532493
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
VBUK_KREDIT_NEUAUFBAU
2
0
0
0
LT_INB_CIFEXT
Table IT_2692[1x476]
PROGRAM=SAPMV50AFORM=BELEG_SICHERN_POSTDATA=LT_INB_CIFEXT
Table reference: 1104
TABH+ 0(20) = C095F993B8301E940000000050040000840A0000
TABH+ 20(20) = 01000000DC010000FFFFFFFF0400000090AC0100
TABH+ 40( 8) = 10000000C1308401
store = 0xC095F993
ext1 = 0xB8301E94
shmId = 0 (0x00000000)
id = 1104 (0x50040000)
label = 2692 (0x840A0000)
fill = 1 (0x01000000)
leng = 476 (0xDC010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#002271
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xF077F993
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 1542 (0x06060000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x70E43294
>>>>> 2nd level extension part <<<<<
tabhBack = 0x70041E94
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
V50AGL-DISPLAY_FROM_ARCHIVE
2
0
0
0
XLIKP-VBELN
0080015203
3333333333
0080015203
0000000000
0000000000
EMKPF
4900035075200800000000000000 ##
3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
4900035075200800000000000000000000000010000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
VBMUE
2222222222222222222
0000000000000000000
0000000000000000000
0000000000000000000
VBSK
0000000000000000000000#### ####
2222222222222222222222222233333333333333333333330000222000022222222222222222222222222222222222
000000000000000000000000000000000000000000000000000C000000C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PACKDATEN_VERBUCHEN
2
0
0
0
No. 8 Ty. FORM
Name BELEG_SICHERN_01
IF_FINAL_CHECK
2
0
0
0
LF_ONLY_FINAL
2
0
0
0
LF_ONLY_PREPARE
2
0
0
0
LF_FLAG_DOCNUM_NEW
2
0
0
0
CF_SUBRC
0
0000
0000
T683V
22222222222222222222222222222222222
00000000000000000000000000000000000
00000000000000000000000000000000000
00000000000000000000000000000000000
SY-XPROG
SAPLBPFC
5454454422222222222222222222222222222222
310C206300000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
IF_RENUMBER
X
5
8
0
0
SPACE
2
0
0
0
XVBPA_FIRSTIND
0.0.1.
000
00C
SY-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
IF_POST
X
5
8
0
0
SYST-REPID
SAPMV50A
5454533422222222222222222222222222222222
310D650100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
XVBPA_AKTIND
0.0.1.
000
00C
No. 7 Ty. FORM
Name BELEG_SICHERN
%_DUMMY$$
2222
0000
0000
0000
IVBPA2KEY
000000
22333333
00000000
00000000
00000000
IV_FINAL_CHECK_DURCHFUEHREN
2
0
0
0
CHARX
X
5
8
0
0
LF_SUBRC
0
0000
0000
No. 6 Ty. FORM
Name FCODE_SICH_OHNE_CHECK
IVBPA1KEY
000000
33333322
00000000
00000000
00000000
T180-AKTYP
V
5
6
0
0
AKTYP-CREATE
H
4
8
0
0
CVBFA
000000 000000 #### #### 00000000000000 0
2222222222222333333222222222233333320000222000022222222333333333333332222222222222222222222223
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000C000000C00000000000000000000000000000000000000000000000
XSDCTRLFLAG
22
00
00
00
SYST
| ######################################T#######################################µ#########XP####
000000000000000000000000000000800000005000000000000000000000000000000000000010B0001000AF550000
0000100000000000000010601000104000000040006050407000000000000000000000000000C0500010300F800300
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000AF000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000BF00000C
GC_FCODE_PODCANC
ABBR
4445222222222222222222222222222222222222222222222222222222222222222222
1222000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
XSDCTRLFLAG-PROTSAVE
2
0
0
0
YES
X
5
8
0
0
GC_FCODE_PODQUIT
PODQ
5445222222222222222222222222222222222222222222222222222222222222222222
0F41000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
PROTOCOLCALLER-SDL
SDL
5442
34C0
0000
0000
GC_FCODE_PODSTOR
PODS
5445222222222222222222222222222222222222222222222222222222222222222222
0F43000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
LIKP-VBELN
0080015203
3333333333
0080015203
0000000000
0000000000
LIPS-POSNR
000010
333333
000010
000000
000000Hi
As soon as we have started to put things into UPDATE TASK, we must
54 ensure that errors definitely terminate the transaction.
55 MESSAGE A is not sufficient because it can be catched from
56 external callers which COMMIT WORK afterwards, resulting in
57 incomplete updates. Read note 385830 for the full story.
From the above message I think u need to read the not 385830 in tcode snote.
Thx. -
Error during Post Goods Issue of delivery
Hello SD experts,
I have an URGENT problem where users at a particular plant have problems in posting goods issue. I happened last Thursday and I desparately need solution before month end for closing activities.
System would send error msg " All HIM materials require quantity conversion. Maintain item 000010". Transaction code used are VL06O and VL02N. Msg no: 03 012.
Diagnosis
There is an item for the delivery that has not been fully processed. The
quantity conversion calculation has not been made. HIM (Hydrocarbon
Inventory Management) materials require that all quantities for all
units of measure defined in the unit of measure group are calculated by
the QCI (Quantity Conversion Interface).
The problem is, there's no problems in posting the particular material form the same plant before this. When I took a look at the Delivery document, I noticed the "Qty in alt UoM" tab in the Item Details screen is blank whereas there should have data in it. I believe these data is automatically derived from master data. Hence, I suspect the Goods issue problem is due to the missing data .
This problem only happens in one plant, for one material whereas this material is active in many other plants.
Anyone of you guys had the same problem and can share the solution with me?
HELP!!
SurianaPlease check Plant customer master reconsilation account properly maintained or not in XD03 transaction.
-
Posting goods issue using Message type SHPCON and idoc type DELVRY03
Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. The scenario should be posting goods issue based on the delivery order.
In some cases, quantity issued is less than the quantity in the DO. For this, I need to change the delv quantity in the DO via VL02N before I select Post goods issue button. This will change at the same time post the goods issue.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1EDTH13-QUALF = "006"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = updated quantity
But everytime I simulate using WE19, the entire quantity in the DO is not changed at all. The goods issue quantity posted is still the original DO quantity.
May I know how to do this? Thanks.Put value in E1EDL24-LGMNG for qty to pgi.
-
Post Goods issue using delivery
Hi,
Anyone know a function module or BAPI to post goods issue (mvt:601) for delivery. function module BAPI_GOODSMVT_CREATE does not support 601 or like. and if we use BDC, there are no return message because we use transaction VL02N and in this if any error, it will stop at error screen.
Pls let me know if you have any solution on this.
regards,
NileshHi,
I got solution with fm: WS_DELIVERY_UPDATE_2 which will update delivery, packing, picking.......
Still waiting for answer on: creating delivery realted billing document. Tried BAPI_BILLINGDOC_CREATEMULTIPLE which will create order related only. -
Post a good issue against an outbound delivery with movement type 601 K
Hello,
according to my business scenario I need to manage the stock of different vendors into the client's location (plant) at storage location level and I need to post the good issue against an outbound delivery to decrease the stock level.
Since the owner of the goods isn't my client the item is managed only at quantity level (not value) so I'm not interesed in the accounting document.
To do it I'm using the functionality related to the vendor consignment stock but I'm not able to post the good issue against an outbound delivery using the movemement type 601 and the special stock indicator equal to K.
In particular I've tried in two different ways:
- setup the consignment stock indicator (= K) into the sales item category, but when I post the goods issue the system is not able to find out the right vendor
- to create a stock determination rule instead of the setting previous described, but the system display an error message (Fld selectn for mvmt type 601 / acct L534200770 differs for Cost center (010) ) even if the accouting is not relevant in my scenario
Can you suggest me how the system has to be setup in order to cover my requirements?
Thanks in advance,
AlessandroHi,
Please clarrify which material type you are using in this scenario? I suggest you to use material type UNBW (no value updation will be there) and create a material master. Use special stock indicator K. Proceed with 601K to do GI. Hope it works. Thanking you. -
Post Goods Issue with BAPI with reference to BOM
Hi All,
I want to post Goods Issue with BAPI / FM with reference to BOM.
The requirement is like to replicate what we can do with MB1A with reference to BOM with BAPI / FM.
Please give ur suggestions.
Thanks in advance.
Chintan.https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_forums_rm&query=kanban&adv=false&sortby=cm_rnd_rankvalue&sortmode=true&searchmode=similar&similardocsuri=/forumsrm/1_category/42_category/50_forum/34196_thread/322837_message
Maybe you are looking for
-
Cleaning the guts of an HP B & W or Color LaserJet Printer
Hi: I currently have an HP4M LaserJet printer...it appears to have "died" after 20 years. I have had to do meticulous internal cleaning of it in the past, when I toner cartridge would go bad, dumping toner into the printer. With brushes, lint free c
-
SAP MM:Purchase info record
Hi experts, Can anyone tell me the complete process of purchase info record (ME11).Complete screen steps what are the tabs are there in ME11.I want screenshots of ME11 Hope for good answer from experts Regards sandhya
-
Reference with '*' in GL document
Hi. I know when I create a new GL document, and I write in Reference field an '*', when document is created, in field reference appears document number created. But now, I want to do the same for a preliminary document (type FW) and it isn't working.
-
Pages for iOS: possible to have multi-level numbering?
Hi all, I'm a new user to Pages for iPad (my iPad 3rd gen arrived last week w00t) and just imported a word document with fairly complex formatting. First thing i note is thst all my multi-level numbering is gone. Does the app not support this feature
-
HELP!! I'M SEEING DOUBLE
I just did some routine iLife upgrade, so maybe that's the problem. But now EVERY item in my calendar has doubled. The same item, same time listed twice. Anyone who knows how to correct this short of manually deleting 50% of what's in my database, lo