Goods Issue in CO27

HI
      I have given to a client CO27 - as they wanted goods issue for multiple production orders.
       I have a problem in posting period.For 2 days some entries are pending in December month.Due to this we didnt open the period for january.Iam trying to isue for december month with CO27 screen but iam getting a posting period error.
      Client is not interested to use MIGO / MB1A they are very specific on Co27 and in CO27 there is no option to change Posting date / document date so system takes current date and throws error.
     Kindly give me suggestion how to reslove this error.
Regards
Jayshankar.A

Dear Brahmankar
I have tried with MB26 it works fine but it takes the reserved components for the production order.
They have some unplanned goods issues.
In MB26 we dont have the option to add Components actually consumed.
Thanx for your reply i was able to fetch it to COGI screen was able to clear the error. But i found this yesterday through SDN. i have this problem of unplanned goods issues.
In Cogi when we click on we get all options in the goods movement screen.Can we get that screem anywhere are can we get that screen through USER exit so that this issue can be permanently resolved.
Regards
Jayshankar.A

Similar Messages

MB26 ,CO27 - goods issue components with serial number?

Hi ,everyone!
I know CO27 and MB26 can do goods issue to production order very easily and quickly!
But It seems CO27 and MB26 can not work well with the component with serial number.
I aslo know MB1A and MB1B can post goods issue for component with serial number.But in MB1A and MB11 , it is very difficult to can material by material number quickly while doing more then 100 components issue to one production order.
And for authorization purpose we restrict MIGO not to use goods issue for production order.
So I want to ask how CO27 and MB26 do goods issue for the component with serial number?
Or there is another ways to goods issue component with serial number to production order easily,exclude MB1A,MB11 and MIGO?
Thanks for any reply!

Hi Vivek
We use CO27 for goods issue to production order ,just like MB1A goods issue to production order.
But in the BOM components of the production orders ,some semi finished products are with with serial numbers ,so we can not use CO27 or MB26 to issue these components with serial numbers to production orders!

MM: Material Goods Issue to Procudtion order CO27

Hi anybody,
When I Material goods issue to Production order using co27. I give the Material number, qty, Storage location and batch number. But I got the error Pick List Wrong Componenets. What is the error?.
anybody please tell me about this error?.
Why this error coming? how to solve this error?.
Tks
S.Muthu.

Hi,
Check the BOM of the material which you are entering in the production order.
Check which is the input material for the final produced material. send the input material.
Or
You can go to CO11N / CO11 and while confirming the production order you can directly click on goods movement and do a GI with 261 Mvt type.
Thanks & regards,
Kiran

Issue while posting using goods issue for delivery type NL

Hello Experts,
I have created an outbound delivery for an intra-company transfer (within same company code) between two plants. The delivery type in NL (replinishment delivery)
When i am trying to post the goods issue from supplying plant, I am getting following error
"Account type K is not defined for document type WL".
Delivery type NL should not be used to issue stock to vendor but I am not issuing it to any external vendor , issuing the stokc only to a receiving plant.
Please help to understand why i am getting this error.
Regards,
Nish.

Hi,
If you are doing an STO Scenario, Check whether you have created the supplying plant as a vendor.
The Vendor Account group should be plants.
Also check whether you have given the plant in the vendor master Purchasing Data - Extras tab in the menu click on add purchasing data & check.
If you haven't assigned this, do the same & create a fresh STO & check.
Hope it will work.
Thanks & Regards,

Changing the field content of 'wrbtr' in accounting document during Post Goods Issue in VL02N

Hi Experts,
     I have requirement ,where I need to change the 'amount in document currency value (wrbtr)' in line item of a accounting document, which is created as part Post Goods issue through VL02N.
          I have already check BADI's below as follows:-.
1) LE_SHP_GOODSMOVEMENT- No accounting document information flows in this BADI.
2) AC_DOCUMENT - Field 'WRBTR' is not available in substitutable fields list.
3) BTE-1050 - This BTE is not getting triggered while doing PGI.
        Please suggest any other possibilities to make the change.
Thanks & Regards,
Suganth.

Hi Kartik,
            I have checked the enhancement you specified, but it didn't trigger during PGI. Can u please let me know is there any other possibilities to make the change.
Thanks
Suganth.

Goods Receipt / Goods Issue / Transfer Posting

Hi
Scenario:
A pack contains 6 materials of same type but of 3 different colors viz Red:2; Yellow:2; White:2.
I purchase this pack and sell the same pack.
If sales of this pack is not not much, then i do a Goods Issue to a Cost Center. And then i want to do a Goods Receipt into my Inventory as individual items of 6.....2 nos. each of Red, Yellow and White.
How to do GR in to my inventory all the four materials viz:
1. Pack (of 6 material)......ofcourse i am able to do w.r.t PO.
2. Individual entry of all 3 types Red,yellow,white
kindly answer me ASAP
cheers
MaruthiRam

As per your 1st post, it seems that there would be a material code for Pack and 3 material masters for Red, White and Yellow materials (If not then create)
And when you are selling to customer, you are selling the pack not individual material and when you are issuing against cost center, issuing the pack only.
So
GI of Pack; MIGO - Goods Issue > Others (Movement Type 201)
And GR of Red, White and Yellow materials; MIGO - Goods Receipt > Others (Movement Type 202) from Same Cost Center as in GI. Enter Red, White and Yellow materials, plant, storage location, quantity, etc... manually.
The above 2 transactions to be done separately 1st GI and the again go to MIGO and do GR.

Calculation of goods issue date in scheduling agreements with routes

Hello together,
i have a problem with the calculation of goods issue date in scheduling agreements when we use route, because the system ignore the days of transit.
Example:
We had customized the route 4711 with a transit time of 3 days. This route would be related to a scheduling agreement. But this setting has no influence to the calculation of the goods issue date for the schedules. The same happens with loading date and so on.
Can anyone give me a tip, which setting is additional necessary?
Regards
Andreas Walter

Hi,
check the following settings
1, Route determination Path : IMG>sales and distribution>Basic function>Routes>Route determination
2, Activate the route Determination for your sales document type in following path :IMG>sales and distribution>Basic function>Routes>Route Schedule Determination-->Schedule with route schedule for sales document type
3, Maintain Delivery scheduling and transportation scheduling in the following path:IMG>sales and distribution>Basic function>Delivery scheduling and transportation scheduling>Maintain Duration
Regards
Senya

Profit Centre Document issue at the time of Post Goods Issue on SD.

Dear Experts,
While SD person is posting Post Goods Issue, System is generating Profit Centre Document along with other documents. We are facing an issue with Profit Centre document here and the issue is:
Some Profit Centre Documents are populating Delivery Order Number on respective field while some are not. Ideally all profit centre line items should show Delivery Order Numbers.
Please guide any solution to resolve this issue, its urgent.
Thanks in Advance.
Regards,
Zain Bashir

Hi Zain
This is a tricky issue
Are you saying that the PCA document has the Delivery Number (VL01N) updated in some cases and not updated in some cases?
The Delivery Number is updated in PCA document when you create Delivery from VL01N and do PGI from VL02N
But, if you do PGI from VL01N itself, then the delivery number is not updated in the PCA document
SAP recommends to post PGI from VL02N
Br. Ajay M

How to change movement type of Delivery goods issue?

Hi all!
I need to change the movement type used by posting Goods Issue in an outbound delivery (tcode VL02N).
Please provide some instructions or cookbooks on how to do the configuration..
Thanks a lot!

Hi,
Get the Schedule Line Category used in Sales order. Go to VA03, here double click on the sales order line item and go to "Schedule Lines" tab, here get the Schedule Line category.
And then go to VOV6 and double click the Schedule Line category and in detailed screen, change the movement type.
Then try for Delivery and PGI.

Different GOGS GL account for goods issue

Hello SAP export,
The F&A department requests to generate different COGS GL account based on Customer Account Assignment Group when goods issue (or billing). Customer Account Assignment Group field name is KNVV-KTGRD. The solution is NOT possible at T-CODE OBYC (with GBB transaction (MM FI configuration for goods issue) because we are using the same materials. (All materials are with same valuation class in MATERIAL master).
I had posted this question in SD forums but the export suggests me to post in FI forum.
If you know any workable solution, please help.
Great thanks in the advance!

Hi,
Check the link for how to have default a G/L account on a Purchase Order account assignment for an inventory item & how to post to a separate G/L account for inventory item by having GR posting
http://www.bluemarlinsys.com/ns/0603-03.asp
OR
you can have a thought of having different valuation grouping codes where you can have different G/L posting with respect to plant for same materiel
valuation grouping code........valuation area
0001......................................P001(plant-1)
0002----
P002(plant-2)
Regards,
Biju K

COST GL account when goods issue - enhancement or user exist

Hello SAP exports,
There is a requirement from F&A department for different COGS GL account based on Customer Account Assignment Group value when goods issues (GI) (goods movement). Customer Account Assignment Group field name is KNVV-KTGRD.   The solution is NOT possible for standard SAP SD (pricing procedure) / MM (T-Code:OBYC with GBB).    Therefore, I am searching solution for enhancement.
the requirement is like following:
KNVV-KTGRD                                   COGS GL account at goods issue
01                    Domestic                   818100
02                    Export                       818200
03                    Testing - sample         818300
04                    Testing - VOM            818400
05                    Franchise                   818500
Can you please let me know what and how this can be resolve by enhancement or user exist?
Thank you.
Kind Regards,
Sylvia Chen

Hello,
The requirement is to provide different COGS GL account based on the Customer Account Assignment Group value(KNVV-KTGRD) when SAP performs goods issue. for example, movement type 601,
This means, when company ships goods to differnt customers, then SAP should generate different COGS GL account.
for example, when company ships goods to customer account assignment group '01' (Domestic customers), then SAP should generate COGS GL account 818100.
when company ships goods to customer account assignment group '02' (export customes), then SAP should generate COGS GL account 818200.
when company ships goods to customer account assignment group '03' (Testing - sample customers), then SAP should generate COGS GL account 818300.
the logic is following:
KNVV-KTGRD              COGS GL account at goods issue
01 Domestic                 818100
02 Export                     818200
03 Testing - sample      818300
04 Testing - VOM         818400
05 Franchise                818500
I am not good at user exist.
Can you please provide solution with step-by-step guide?
Thank you.
Regards,
Sylvia Chen

Goods issue in third party process

Hi All,
I have done third party process. But I am not clear for goods issue to the customer.
We will place goods at customer premises at the time of goods receipt with purchase order reference. In this flow will place goods to customer place directly. Why should I go once again goods issue to customer and which document reference can I do.
Thanks
Nagi

Hi
In Third party scinerio their is no need to issue stock to customer or vendor,
In system when we do GR stock is consumed that momvent, after GR quantity is not update.
Regards
Chandrajit Patil

Regarding Goods Reversal and Goods Issue process for Production orders

Hi,
I have a issue regarding Goods Reversal and Goods Issue process for Production orders.
Actually I am having a Z - Function Module in that i am passing production order number other details to
make the Goods Reversal happen.
The code for the above is as below:
 i_mvtit-material = wa_mdfa-matnr.
 i_mvtit-plant = i_resb-werks.
 i_mvtit-spec_stock = 'Q'. "New
 i_mvtit-stge_loc = 'ZWIP'.
 i_mvtit-stge_type = i_resb-lgtyp. "New
 i_mvtit-batch = i_resb-charg. "New
 i_mvtit-orderid = i_resb-aufnr.
 i_mvtit-spec_stock = i_resb-sobkz.
 i_mvtit-entry_qnt = i_resb-enmng.
 i_mvtit-entry_uom = i_resb-erfme.
 i_mvtit-entry_uom_iso = i_resb-meins. "New
 i_mvtit-wbs_elem = v_frwbs.
 i_mvtit-move_type = '262'.
 i_mvtit-xstob = 'X'.
 i_mvtit-gr_rcpt = i_resb-aufnr. "New
 i_mvtit-reserv_no = i_resb-rsnum.
 i_mvtit-res_item = i_resb-rspos.
 APPEND i_mvtit.
* HEADER ELEMENTS
 k_gmvt_code-gm_code = '03'.
 k_gmvt_head-pstng_date = sy-datum.
 k_gmvt_head-doc_date = sy-datum.
* CREATE GOODS MOVEMENTS
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = k_gmvt_head
 goodsmvt_code = k_gmvt_code
 TABLES
 goodsmvt_item = i_mvtit
 return = i_return.
The Above code does the Goods Reversal but then i will update one Z Table with fields like
Production Order Number[AUFNR], Number of Reservation[RSNUM], Item Number of Reservation [RSPOS], Material Number [MATNR], Requirement Quantity [BDMNG], WBS element[PSPNR] etc. If Above BAPI runs sucessfully.
That is happening correctly.
But Then actual issue is i have do Goods Issue for those Z-Table records.
There i will give Production order Number's & Storage Location in Selection-Criteria.
Then i need to do Goods Issue for that order.
The code i had written as follows.
* POPULATE VALUES FOR BAPI CALL
 i_mvtit-material = i_zpsi7603_01-matnr.
 i_mvtit-plant = i_resb-werks.
 i_mvtit-spec_stock = 'Q'. "New
 i_mvtit-stge_loc = p_sloc.
 i_mvtit-stge_type = i_resb-lgtyp. "New
 i_mvtit-batch = i_resb-charg.
 i_mvtit-orderid = i_resb-aufnr.
 i_mvtit-spec_stock = i_resb-sobkz.
 i_mvtit-entry_qnt = i_resb-enmng.
 i_mvtit-entry_uom = i_resb-erfme.
 i_mvtit-entry_uom_iso = i_resb-meins. "New
 i_mvtit-wbs_elem = v_frwbs.
 i_mvtit-move_type = c_261.
 i_mvtit-mvt_ind = 'F'. "New
 i_mvtit-xstob = c_x.
 i_mvtit-gr_rcpt = i_resb-aufnr. "New
 i_mvtit-reserv_no = i_resb-rsnum.
 i_mvtit-res_item = i_resb-rspos.
 APPEND i_mvtit.
* HEADER ELEMENTS
 k_gmvt_code-gm_code = c_03.
 k_gmvt_head-pstng_date = sy-datum.
 k_gmvt_head-doc_date = sy-datum.
* CREATE GOODS MOVEMENTS
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = k_gmvt_head
 goodsmvt_code = k_gmvt_code
 TABLES
 goodsmvt_item = i_mvtit
 return = i_return.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_x.
 READ TABLE i_return INDEX 1.
 IF i_return-type EQ c_s.
 DELETE FROM zpsi7603_01 WHERE aufnr = i_resb-aufnr AND
 rsnum = i_resb-rsnum AND
 rspos = i_resb-rspos.
 ENDIF.
If i run above code for Goods Issue it is giving error can anybody tell me what changes i need to do to make it work.
The Error Message i am getting is as below:
Qty and / or "delivery completed" ind. or final issue ind. are missing
Error Number for the above is : 264.
Can anybody solve my issue.
Any help will be appreciated.
Thanks in advance.
Thanks & Regards,
Rayeez.

Hi,
Thanks boss.
It is working now correctly.
The issue is the i_mvtit-XSTOB should be equal space in case of Goods issue while incase of Reversal it should be equal to X.
Thanks for ur efforts.
I had awarded you points.
Thanks a lot.
Thanks & Regards,
Rayeez.

Return under Warranty (Tracking Line only) Should we use MIGO - Goods Issue

Return under Warranty (Tracking Line only) Should we use MIGO - Goods Issue when sending out Materials for repair or exchange under Warranty (Free)?

Please post it in SD/MM forum.

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.

Goods Issue in CO27

Similar Messages

Maybe you are looking for