Post Goods issue after clicking on Load Starting push button

Hi All,
Post goods issue for deliveries, suppose if the shipment document is created for XXXX country do the post goods issue after clicking the push button loading start on. and if the shipment is created other than the XXXX Country do the post goods issue after clicking the shipment start button(Done by Standard SAP).
There will be validation table in background to identify which shipping point to allow Post Goods Issue before shipment completion. This will require enhancement of Delivery User Exit to incorporate above check based on below mentioned Z Table.
Z-Table
- Shipping Point.
- Delivery Type
Any body please suggest the user exit or any function module and how to start code for this particular requirement.
Thanks & Regards,
Narasimha

Hi,
You can write your own vaalidation on click of loading start button.
Go to include MV56AI_IS_ENHANCEMENT of program SAPMV56A.
Click on the circular button(Enhance).
Then Edit --> Enhancement Operation --> Create.
Create your enhancement giving it a Z name.
Then in this enhancement you can write your code.
For loading start you can write your code in the following fashion.
IF fcode = 'MM_ST03'.
business logic.....
ENDIF.
Regards,
Firoz.

Similar Messages

Exception in CRM system after creating post goods issue in ECC

Hi Folks,
We are facing an issue in CRM system. I will tell the scenario in details so that it would be helpful to understand,
We are creating sales order in CRM system and it got replicated to ECC correctly. We have maintained action definition to trigger email to the customer.
Then we will be creating delivery and then post goods issue(PGI) for items replicated to ECC systems. After PGI system will update the status in CRM sales order and here configured an action definition to trigger an email to customer.
We have created custom badi implementations for action definition execute badi to send email. Emails are triggering correctly but after PGI creation while replicating the changes from ECC to CRM we are getting an exception in standard code because PPFTTRIGG table does not have entry. We have failed entry in CRM inbound queue and then did some debug and come to know the place of issue. Help me out with some inputs here.
Best Regards,
Dharmakasi.

Hi,
I have identified one thing here, if the action definition does not have start condition system is not updating that entry in PPFTTRIGG table. Here i got 2 questions my mind
1. Why system is not updating the table with all the action definitions available in action profile
2. Why system is looking for the entry which was not updated in PPFTTRIGG table?
I do not understand problem with updating table or with action profile itself. Please give some input here. If we deactivate all the definitions which does not have start condition then there is no error.
Best Regards,
Dharmakasi.

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

No Acc. Doc generated after Post Good Issue - please help!

Hi All,
I have problem when I try to post good issue, the accounting doc doesn't generated.
I have created SO, (Order type - OR, item category - TAB, Schedule Line cat - CB), created PO after the purchase requisition was generated in the SO. processed good receipt and created outbound delivery, everything is fine until post good issue, there is no Acc. Doc created automatically after PGI.
I have check the following setting
material type attribute setting - ok (standard price control, val.update, qty update)
valuation level - ok (valuation area is plant)
valuation grouping code - ok (activated)
valuation areas assigned to the valuation grouping code - ok
valuation class(s) is linked to material type(s) vis acc. cat. ref. - ok
accout grouping for movement type - ok (leave it as default)
configure auto posting - ok (I have run the simulation test, and created the missing G/L acc in the company code which under testing)
The WL Acc Doc type is defined and assigned with number range.
material and accounting period are open
In Purchase order, the purchase item assigned with Acc Assignment Category E, Special Stock is E, Consumption Posting set in Acc Assignment Category is E, Acc Modification is VAY, GR non-valuated and GR non-val. binding checkboxes are deselected.
I know the Acc Assignment Cate will affect the auto acc posting in GR, but I am not sure it will affect PGI in the same way.
Could anyone tell me which value string will be using for this auto acc posting for PGI? My best guess is
MvT S val. update, qty update Mvt Cns
601 E YES YES L ?
Could anyone tell me what cause the Acc Doc not be generated after PGI?
Thanks for your time
Alvin

thanks for reply.
Regard to the point 2 suggested by Cathy, the account determination for billing is set, the accouting doc is created after billing.
my problem is no acc. doc generated after PGI.
meanwhile I have searched a similar problem in other forums, I found some similar reply as Prasanth did, so I think I may try to run VA88 to see the result.
Prasanth, could you please explain the pinciple behind of why this happen if what you say is correct.
Thanks for your time!!!
Alvin

Accepted change after post goods issue

when i made delivery and post goods issue in sap then if any body change the quantity of order in va02 the system accept ?
how can i change this

Hi,
yes..it will accept...but it will show a warning message as per standard.
Example: " Delivery of 1 EA has already been made for item 10" message no V4096
if you want to show as an error message try to change the category " W" to "E" in OVAH
so that it will not allow you to change the order quantity.
Note: Order quantity will be grayed out after creation of Billing only.
Hope it helps.
Thanks,
Krishna.

User exit to triger after PGI (Post Goods Issue)..

Hi,
Can any one help me on this........... Plz .. Urjent...
I want to make some operation after PGI and I want to find out the user exit to triger after PGI... I dont know How to find out that exact .. Can any one help me on this ...
I want the User exit that triger after PGI...
Regards,
Raghunath.S

Hello Sudha,
Once the PGI ( Post Goods Issues ) over then I want to do some operation .. for that I want to find out the user exit where I can write some logic and process after the PGI...
Can you help me on this Plzzzzzzzzzzzzz....

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.

Problem with post goods issue

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

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

VL02N:Post Goods Issue Error: PXA_NO_FREE_SPACE

Hi gurus,
i am testing post goods issue under vl02n after posting&delivering a sales order with type OR. the ' PXA_NO_FREE_SPACE' error occured after my clicking post good issue.
PFB the error log, can anyone help to solve it out. TIA.
    No PXA storage space available at the moment.
What happened?
    The current ABAP/4 program had to be terminated because there
    was no space available to load it.
    Each ABAP/4 program to be executed is stored in a central
    storage area that is divided between all users.
    This area was too small to hold all currently active programs for all
    users.
    Resource bottleneck
    The current program "SAPMV50A" had to be terminated because
    a capacity limit has been reached.
What can you do?
    Since this could have resulted in a temporary bottleneck, you should
    try to restart the program.
    Ask your system administrator to increase the size of the area (PXA)
    used to store the ABAP/4 programs.
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    Unable to load a program of 1048576 bytes.
    The PXA ('program execution area') was too small to hold all
    currently active programs for all users.
    At present, the size of the PXA is set at 144868 Kbytes.
    The largest contiguous and unlocked memory chunk has 1014784 bytes.
How to correct the error
    The current size of the PXA was set at 144868 kilobytes.
    You can increase or decrease the PXA in the SAP profile. When
    doing this, please refer to the relevent instructions in the
    installation manual.
    You can use the utility program 'ipclimits' to display the
    available system resources.
    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:
    "PXA_NO_FREE_SPACE" " "
    "SAPMV50A" or "FV50XF0B_BELEG_SICHERN"
    "BELEG_SICHERN_POST"
    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.
any reponses will be awarded,
regards,
samson

Check these links where the same issue was discussed
[PXA_NO_FREE_SPACE|http://www.sapfans.com/forums/viewtopic.php?f=12&t=304020&p=917783]
[PXA_NO_FREE_SPACE Error|http://sap.ittoolbox.com/groups/technical-functional/sap-basis/pxa_no_free_space-error-858115]
thanks
G. Lakshmipathi

Automatic Goods Issue after Outbound delivery and shipment.

Hi,
I am working on LES part.
Could you please explain me how to do Automatic post goods issue for shipments.
(in our scenario where after outbound delivery, picking, packing shipment takes place.)
Can we use VL23 for automatic goods issue for shipments? (or igoods issue is only for outbound deliveries?)
If so what is the selection criteria for background scheduling-Variants?
Please explain me in detail
Thanks a lot.

Anil,
Not sure if I understand your question, Goods Issue is posted for the delivery and not the shipment. In a shipment you can update the actual values for Planned, Check-In, Load Start, Load End etc values. A shipment can have single/multiple deliveries, you can use VL23 for scheduling a background job to do the PGI automatically, use either the standard variants or define your own variant and use that variant to schedule the job.
hith
Sunil Achyut

Error message while posting goods issue.

Hi,
Please help me with the following problem..
I have created Sales Order, Delivery & also created the Transfer Order number. After creating Transfer ordering, while submitting post goods issue, when I click on PGI, I get
"Posting only available for period 2002/10 to 2002/11"...
As a resulf of the above, I am not able to complete Billing for all the sales orders I have created.
Can somebody please help me with above?
Regards
Nadeem

Use the MMPV transaction to check your current period. Since you have transactions already done you need to do closing for every month.
If you are on an IDES system for training purposes you can do a fast transaction by removing the plant assignment from the company code. The use the MMPI transaction to set your current period. Remmber April is period 1 if you are are using the indian financial year and fiscal year variant k4.
Then reassign the plant and now try posting It will allow you. But a word of caution. Never attempt to remove the plant asignment in the development system. It might cause errors. for that there is a separate note.
regards
Jude

POST GOODS ISSUE in Delivery Order

Dear Friends:
After going to Delivery Order,Vl02n, I clicked on Post Goods Issue and I am getting this error.
Delivery has not yet been completely processed by WM.
Delivery has not yet been put away / picked (completely)
How to Overcome this problem?
All the help will be greatly apprecaited.
Thanks

Hi,
What it is telling you is:
Delivery Note first need to be picked. If the storage location used in DN# is of WM managed, (you may verify this in the picking tab of the delivery itself.)....It would show WM relevant and not yet picked as statuses in this tab.
You need to create Transfer Order (TO) pick list for this delivery.
Do it from LT03.
Enter the warehouse number that you would see for this delivery in its picking details in the item.
Enter delivery note.
Hit enter and if everything works fine for you and if you are familiar with WM TO creation, you will be able to create TO and if not setup for auto confirmation, you can do it from LT12.
Once you do these steps, you can do the PGI.
Regards

Post goods Issue ,in VL02n

Hi friends ,
I am trying to post Goods issue from delivery order,through VL02n .I tried using BAPI_GOODSMVT_CREATE but it returns the message 'Goods Movement not possible with mvmt type 645'.
I saw in some of the threads about this BAPI ,BAPI_OUTB_DELIVERY_CONFIRM_DEC .Can i achive the same functionality .Please suggest me which parameters should be passed into the BAPI.
The BAPI should return me the material document number generated from VL02n ,i mean after posting the goods issue .
Regards ,
Hemanth Nugur .

Hi
"I am trying to post Goods issue from delivery order,through VL02n"
If you want to do it inside VL02N transaction, you already a PGI button, just click on that, PGI will be done
Regards
MD

Cancel post goods issue..............

How do I cancel post goods issue?Process of how it happens?pls tell me.

by useing the tcode VL09
You caGoods issue reversal means that you cancel the goods issue posting for a delivery. This function enables you to remove the posting without having to create a returns delivery and then having to post a goods receipt for it (see also Processing Returns After Goods Issue Posting). This function can be especially useful if you have accidentally posted goods issue, for example, and you would like to reverse it. Goods issue reversal usually occurs shortly after goods issue posting.
Integration
The cancellation document is integrated in the document flow of the delivery.
Prerequisites
Goods issue reversal is only possible for movement types for which a reversal movement type is defined in Customizing. Therefore, if you have defined your own movement types for goods issue, you must also define the respective reversal movement types and assign them to the movement types for goods issue.
Range of Functions
When you reverse goods issue for a delivery, the system creates a cancellation document that adopts the quantities and the valuation from the original goods issue document, and also executes the respective value and quantity posting to stock.Procedure
From shipping, choose Post Goods Issue ® Cancellation/reversal.
The Reverse goods movement screen appears.
Enter your selection criteria, for example, route, goods issue date, shipping point, and so on, and choose Execute.
A list of all deliveries that correspond to your selection criteria appears.
From the list of deliveries to be reversed, you can branch directly to a list entry in the delivery by double clicking on the entry.
Select the deliveries for which you wish to reverse goods issue and choose Cancel/reverse.
A dialog box appears.
In the dialog box, confirm that you want to reverse goods issue.
Result
The system reverses goods issue for all selected deliveries. It also generates a log of all the reversals executed and any errors that may have occurred.

Post Goods issue after clicking on Load Starting push button

Similar Messages

Maybe you are looking for