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

Similar Messages

COPA document not generated when Post Goods Issue is reversed.

Hello Friends,
WE uses Stock Transport Order in two steps for transfering Stock from one plant to another. We have defined a Condition type FRB1 to capture the Freight cost involved in the stock transfer.
When the Post goods issue is done for the Stock Transport Order. following Accounting documents are generated.
Accounting
Profit Center
COPA
Spec. Purpose Ledger
Controlling Document
Material Ledger document.
But When the Post goods issue is reversed through transaction code VL09 all the above documents are generated except for COPA document. Though in controlling document it shows the object type hit is REO i.e profitability Analysis
For further information we have mapped cost element (600150) with Value field in PA transfer structure (Direct assignment from FI and MM. Movement type used for PGI are 641 & 642.
Thank you

Dear Colleagues
I thank all those who put in thier time and efforts for possible solution for my problem. But I could resolve this issue with help from SAP.
Basically in costing based COPA the system does not post the cost of goods sold to COPA during goods issue but it is done at the time of posting the invoice since the system wants to see the revenues and the COGS values together.
Since the system posts the COGS into COPA at the time of invoice posting, you will appreciate that if this is also done during goods
issue then you will have duplicate entries in your COPA (i.e. the COGS will be doubled).
If in transaction VL01N/VL02N a costing-based line item would be posted, the costs would be double in CO-PA (the billing and goods issue). For this reason, no costing based line items will be created in the standard R/3 system for transaction VL01N/VL02N.
If for some reason you still wish to post the COGS to COPA during goods issue you have to do the same thro a modification of the system.In your case you have applied note 214381 for the same. Please note here that movement type '641' is used as an example. For other movement types you will need to code accordingly.
as per note 337488 point 2. the changes of note 214381 were not required in our case. Therefore we reverted these changes in LKEIIF01 and added the relevant coding for movement type 642 in function COPA_DOCUMENT_CHECK as per note 337488 point 2.
Looking forward for your continued support
Regards
Umesh Gothankar

Accounting Document not generated after Post goods issue in delivery order.

Dear Experts
Greeting of the daays,
Need your help on below issue.
After making the post goods issue ,the system is not making the accounting document.
The error given by the system is as follows:
Material document 12365 does not include an accounting document
Diagnosis
The system cannot find an accounting document for the material document 12365.
Possible reasons for this are:
The goods movement has no relevance to accounting. Therefore, the system did not generate an accounting document for the material document.
The material document is a document that was posted before Release 2.1. Such documents must be converted so that the system can find the relevant accounting document.
The procedure for the subsequent calculation of value is not active in your system. For further information, refer to the documentation on the program for valuating goods movements: RM07MWBU.
__Solution what I tried to solve this issue ,but not successful.__
__Solution 1- maintain OMS2__
__Solution 2 - maintain OMJJ- movement type 601 - PRCTR is required entry.__
__Solution 3 - price maintain is material master.__
__Solution 4 - OBYC - BSX - 7920 - GLA/c and GBB- VAX and VAY - 7920 GLA/c.__
__Pls let me know if there is any confirgation is missing.__

Hi
Do this checks:
In tcode OBYC check if you have the proper entries.
Go to tcode OKB9 and do the settings for the G/L acc. that you have in OBYC.
To populate PRCTR you can use OKB9 and you can check if you have values in MARC-PRCTR.
I hope this helps you
Regards
Eduardo

Not able to post vendor payment in case of Cash discount received

Hello
We are on SAP ECC 6.0
I'm not able to post an outgoing payment through F-53 T code when cash discount is received from vendor due to early payment before due date.
I get the following error message -
Tax code V0 for country IN has been deleted or incorrectly changed
Message no. FS201
Our tax calculation procedure is TAXINN and we are an indian company in India.
GL account for cash discount received is already defined in OBXU t code for SKE transaction key tax code wise.
V0 tax code is defined through FTXP.
I'm able to display correct cash discount amount and cash discount % when i click on select process open item in F-53 after entering document date; posting date; company code; currency; Bank GL A/c; Amount (Net of discount); value date and Vendor Account.
What am i missing? Why am i not able to post vendor outgoing payment?
Is it possible to post cash discount received to the credit of Stock / Inventory Account as quantity received is not consumed or quantity is lying in inventory?
Thanks.
Vimal

Hello Chintan
I have assigned GL A/c in OBXU t code with and without reference to tax code.
Still, i am not able to post outgoing payment when cash discount is received as i am paying it before due date.
Cannot i take credit of cash discount received to Inventory / Stock Account?
Is cash discount received always posted to non-Inventory / non-stock GL Account?
Thanks.
VS

Error during Post Goods Issue of Material in VL02N for STO Purchase Order

I am getting one error message during Post goods issue of Material for STO Purchase order.
I am doing the Post goods issue in T code VL02N
Error is " Account type D is not defined for Document type WL"
What is the settings required to be done.
Thanks,
Shailendra

Please check Plant customer master reconsilation account properly maintained or not in XD03 transaction.

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

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   10000

Please kindly refer to the attached notes below :
523509     FAQ: Control tables (no Customizing)
161729     M7226 with KZVBR=V
Hope this helps.

Not able to post goods receipt trcode MB1c

hi problem in posting the gr (mb1c)
when i am trying to post goods receipt i am getting the message
ctr1000/testcc is not assigned to a business area.
but when i am trying to assign a business area to cost centre testcc
it is giving the message that transaction data already exists.
please note 1000 is my co code
1000 is my controlling area
test cc is my cost centre.

Hi,
Good afternoon and greetings,
I presume there should be a transaction already existing for that particular cost centre and that is the reason it is not allowing you to do the change...go to the cost centre reporting and reverse the old transaction and then make the changes and post the new transaction using MB1C.
Please reward points if found useful.
Thanking you,
With kindest regards
Ramesh Padmanabhan

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

Hi 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

Post Good Issue Error

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
000000

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

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.

Goods picking and Post goods issue in VL02N

Dear All,
Am hving problem in Picking goods and Post goods issue.
This is for the Stock Transport Order with Delivery via Shipping
Supplying plant is 1000(SAP std,sloc 0001) and Receiving plant 1100(sloc 0001).
Sales org:1000
Distrbn Chnnl:10
Division:00
1.maintained matrial for both the plants.
2.Creted STO by using DOC type as "UB" and item cat "U".
3.And getting the Shipping data for the material in the STO.as shipping point is 1000.
saved the Po.
4.After that i done the GR w/o PO for the material using Mvt type 501.
5.Then,VL10B creating Delivery doc.n this is also created.
6.but when i do the picking and PGI in VL02N there picking field is greyed out bt i have tried to mangae that when i give the picking Qty in the picking qty field system is throwing the following error.
<b>Item to be picked by WM (picking quantity cannot be entered)
Message no. VL118
Diagnosis
For this item, picking is carried out using warehouse management transfer orders since the material is stored in a warehouse with random storage.
System Response
The system does not allow you to enter a picking quantity manually. The picking quantity is copied automatically into the delivery during the creation of the corresponding transfer order.</b>
is any data missed by me while doing this process?
pls let me know n help me in this regrds
Thank you all

Hi Vijay
By changing storage location you could do b'coz the new storage location is not maintained with warehouse, hence no need to perform warehouse transactions (TO creation and confirmation) before inventory mgmt transactions (PGI).
For trying pick up with WH, first u should have enough stocks in approppriate storage bins and u should perform pick up by creation of TO and confirmation.
warm regards
sairam akundi

User exit/routine for post goods issue

Dear all,
I want to stop printing of delivery chalan from a replinshment delivery before post goods issue /actual goods movement.Can anuone suggest me for some user exit or routine that stops printing of delivery chalan from a replinshment delivery(VL10B) untill the post goods issue takes place in stock transfer scenario?
Is there any possibility to put some routine in the output of delivery chalan which displays a message that printing of delivery chalan is not possible since post goods issue has not taken place & system do not allow the printing from replinshment delivery unless PGI tales place in stock transfer scenario.
I will be highly greatful to you.
regards
vikas chhabra
[email protected]
[email protected]

Dear all,
I want to stop printing of delivery chalan from a replinshment delivery before post goods issue /actual goods movement.Can anuone suggest me for some user exit or routine that stops printing of delivery chalan from a replinshment delivery(VL10B) untill the post goods issue takes place in stock transfer scenario?
Is there any possibility to put some routine in the output of delivery chalan which displays a message that printing of delivery chalan is not possible since post goods issue has not taken place & system do not allow the printing from replinshment delivery unless PGI tales place in stock transfer scenario.
I will be highly greatful to you.
regards
vikas chhabra
[email protected]
[email protected]

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

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

How to post good receipt for an inbound delivery with HU in the stock?

Hello,
We have an inbound delivery of a purchase order with 10 Handling Units inside on.
The HU's has been put in a storage bin (by transport order + confirmation) before a good receipt has been posted for the whole delivery.
Due to this it's not possible to post good receipt for the inbound delivery, and the available stock quantity is in minus on zone: '902-GR Area External Rcpts' since the handling units are already in a storage bin.
Can anyone help me on this matter?
Thanks

Hi,
my situation is:
- a WM managed warehouse, society A;
- a HU managed warehouse (without WM), society B;
- a purchasing process of HU from society A towards society B.
Society B have a scheduling agreement; when a delivery schedule appears, in society A born a sales order and a delivery. After the registration of the delivery good issue, an idoc transfer information for inbound delivery creation.
This process is ok without WM, but with a WM managed warehouse the idoc has the following problem:
"V51VP - item was not found - process cancelled".
Can you help me to transfer these HU?

Not able to post goods issue in case of delivery against a repair order

Similar Messages

Maybe you are looking for