Consumption not updated - MVER not update
Hi experts,
Here's my case :
- inital stock has been uploaded via mvt 561
- a consumption mvt (201) has been done
- a month later another consumption mvt (201) has been done
The thing is the first consumption has not been updated in MVER table whereas the second one was.
I already checked OSS note 804011, but can't find an explanation . Does someone have an idea?
Thanks in advance
P.
I dont think so.
Is this consumption made from the same stock type like unrestricted use stock, or is one made from unrestricted use stock and the other one from special stock like sales order stock?
I suggest you open a message at SAP to get the report ZMVERBRP from OSS note 791728.
This report should rebuilt the consupmtion for your first goods issue if the posting string situation is okay now.
Similar Messages
-
High power consumption after update
I recently updated all my packages (it had been a few weeks since I had done this last) and I've noticed my power consumption has jumped dramatically. Before I would average around 13.0W and now the baseline seems to be about 18.5W. I use laptop-mode-tools.
I'm happy to post the output of any command but didn't want to spam as I'm not sure what would be valuable.
I have looked at powertop, but without being able to compare to the past I'm not sure how to diagnose this. Any suggestions or pointers would be greatly appreciated.
I have a Thinkpad T410: Linux alpha 3.11.2-1-ARCH #1 SMP PREEMPT Fri Sep 27 07:35:36 CEST 2013 x86_64 GNU/LinuxIt's possible I suppose that it is related to audio codec power management. After I upgraded I had to add myself to the audio group to get sound working again. I also noticed snd_hda_intel is always pretty high up in powertop.
Finally, I use laptop-mode-tools, and it appears audio codec power mgmt isn't working by default. I can manually select it to turn it on. I also saw this output in journalctl:
Sep 29 11:57:17 alpha slim[1048]: [001:307] F->C: ["getdevicestate","15","0",["__default_device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Front speakers","HDA Intel MID, CX20585 Analog - 4.0 Surround output to Front and Rear speakers","HDA Intel MID, CX20585 Analog - 4.1 Surround output to Front, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 5.0 Surround output to Front, Center and Rear speakers","HDA Intel MID, CX20585 Analog - 5.1 Surround output to Front, Center, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers"],"0",["__default_device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Front speakers","HDA Intel MID, CX20585 Analog - 4.0 Surround output to Front and Rear speakers","HDA Intel MID, CX20585 Analog - 4.1 Surround output to Front, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 5.0 Surround output to Front, Center and Rear speakers","HDA Intel MID, CX20585 Analog - 5.1 Surround output to Front, Center, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers","HDA Intel MID, HDMI 0 - HDMI Audio Output","HDA Intel MID, HDMI 1 - HDMI Audio Output","HDA Intel MID, HDMI 2 - HDMI Audio Output"],"-1",[]]
Sep 29 11:57:17 alpha slim[1048]: [001:307] F->C: ["getdevicestate","15","0",["__default_device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Front speakers","HDA Intel MID, CX20585 Analog - 4.0 Surround output to Front and Rear speakers","HDA Intel MID, CX20585 Analog - 4.1 Surround output to Front, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 5.0 Surround output to Front, Center and Rear speakers","HDA Intel MID, CX20585 Analog - 5.1 Surround output to Front, Center, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers"],"0",["__default_device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Default Audio Device","HDA Intel MID, CX20585 Analog - Front speakers","HDA Intel MID, CX20585 Analog - 4.0 Surround output to Front and Rear speakers","HDA Intel MID, CX20585 Analog - 4.1 Surround output to Front, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 5.0 Surround output to Front, Center and Rear speakers","HDA Intel MID, CX20585 Analog - 5.1 Surround output to Front, Center, Rear and Subwoofer speakers","HDA Intel MID, CX20585 Analog - 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers","HDA Intel MID, HDMI 0 - HDMI Audio Output","HDA Intel MID, HDMI 1 - HDMI Audio Output","HDA Intel MID, HDMI 2 - HDMI Audio Output"],"-1",[]]
Sep 29 11:57:17 alpha slim[1048]: [001:248] F->C: ["mf","mf4.6","4.6.3.0",2,{"audioCodecs":[[103,"ISAC",1,0,16000],[104,"ISAC",1,0,32000],[9,"G722",1,64000,16000],[102,"ILBC",1,13300,8000],[0,"PCMU",1,64000,8000],[8,"PCMA",1,64000,8000],[107,"CN",1,0,48000],[106,"CN",1,0,32000],[105,"CN",1,0,16000],[13,"CN",1,0,8000],[127,"red",1,0,8000],[126,"telephone-event",1,0,8000]],"audioRtpHdrExts":[{"id":1,"uri":"urn:ietf:params:rtp-hdrext:ssrc-audio-level"}],"camDeviceName":"Unknown Camera","caps":7,"cpuAdaptVersion":1,"cpuArchitecture":1,"cpuCacheSize":3145728,"cpuFamily":6,"cpuFlags":["sse2","ssse3","sse4_1","sse4_2"],"cpuHasSSE2":true,"cpuModel":37,"cpuSpeed":2667,"cpuStepping":5,"cpuVendor":"GenuineIntel","cpus":4,"cpusPhysical":2,"cryptoRandom":"Wh5rpjH5WwxrggyWxtWgghIM","cryptoSuites":["AES_CM_128_HMAC_SHA1_80","AES_CM_128_HMAC_SHA1_32"],"dataChannelVersion":1,"effectsVersion":10,"gpuDescription":"","gpuDeviceId":0,"gpuDeviceName":"","gpuDriver":"","gpuDriverVersion":"","gpuVendorId":0,"machineModel":"Not available","remotingAssistanceAllowed":0,"remotingVersion":1,"renderer":2,"rtcpMux":true,"screencast":2,"screencastLocalPreview":1,"supportsConcurrentSessions":true,"transports":["i","gice"],"videoCodecs":[[99,"H264-SVC",640,360,30],[97,"H264",640,360,30],[98,"H263",640,360,30]],"videoRtpHdrExts":[{"id":2,"uri":"urn:ietf:params:rtp-hdrext:toffset"},{"id":3,"uri":"http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time"}]}]
Sep 29 11:57:17 alpha slim[1048]: [001:206] F->C: ["mf","mf4.6","4.6.3.0",2,{"audioCodecs":[[103,"ISAC",1,0,16000],[104,"ISAC",1,0,32000],[9,"G722",1,64000,16000],[102,"ILBC",1,13300,8000],[0,"PCMU",1,64000,8000],[8,"PCMA",1,64000,8000],[107,"CN",1,0,48000],[106,"CN",1,0,32000],[105,"CN",1,0,16000],[13,"CN",1,0,8000],[127,"red",1,0,8000],[126,"telephone-event",1,0,8000]],"audioRtpHdrExts":[{"id":1,"uri":"urn:ietf:params:rtp-hdrext:ssrc-audio-level"}],"camDeviceName":"Unknown Camera","caps":7,"cpuAdaptVersion":1,"cpuArchitecture":1,"cpuCacheSize":3145728,"cpuFamily":6,"cpuFlags":["sse2","ssse3","sse4_1","sse4_2"],"cpuHasSSE2":true,"cpuModel":37,"cpuSpeed":2667,"cpuStepping":5,"cpuVendor":"GenuineIntel","cpus":4,"cpusPhysical":2,"cryptoRandom":"E8HMoakvNyHpWl2HL5jLZBgC","cryptoSuites":["AES_CM_128_HMAC_SHA1_80","AES_CM_128_HMAC_SHA1_32"],"dataChannelVersion":1,"effectsVersion":10,"gpuDescription":"","gpuDeviceId":0,"gpuDeviceName":"","gpuDriver":"","gpuDriverVersion":"","gpuVendorId":0,"machineModel":"Not available","remotingAssistanceAllowed":0,"remotingVersion":1,"renderer":2,"rtcpMux":true,"screencast":2,"screencastLocalPreview":1,"supportsConcurrentSessions":true,"transports":["i","gice"],"videoCodecs":[[99,"H264-SVC",640,360,30],[97,"H264",640,360,30],[98,"H263",640,360,30]],"videoRtpHdrExts":[{"id":2,"uri":"urn:ietf:params:rtp-hdrext:toffset"},{"id":3,"uri":"http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time"}]}]
Sep 29 11:57:17 alpha slim[1048]: [2571:2594:0929/115717:ERROR:audio_manager_base.cc(422)] Not implemented reached in virtual std::string media::AudioManagerBase::GetDefaultOutputDeviceID() -
Podcasts 2.1.1: Huge data cellular data consumption since update
Hi,
Since updating iOS Podcasts app to 2.1(.1), I have noticed huge cellular data consumption... Despite having disabled cell data for iOS Podcasts, the new iOS podcasts seem to be downloading again podcasts episodes that have already been downloaded and are shown as is in the app... I have lost over 1GB out of 3GB for a month among the past few days, which is pretty unusual... Seems like I am not the only one: https://twitter.com/mattdenholmross/status/469131198162558976https://twitter.com/mattdenholmross/status/469131198162558976https://twitter.com/mattdenholmross/status/469131198162558976
iOS Podcasts now often asks for using temporarily the cellular data even for podcasts episodes that are shown as downloaded.
Have you noticed the same?
Best,It is because v2.1.1 does not delete played podcasts for a 24hr period. That holds storage that prevents you from storing new podcasts or other files.
Discussed at:
https://discussions.apple.com/message/25828362 -
Material Document for Scrap consumption not Found
Dear Friends
During order confirmation, molten material / raw material is consumed by 261 MT and dross SH100002 is generated by MT 531 along with the finished product with MT 102. I reversed finished product through 102 MT and Raw material through MT 262. Thus do I need to reverse dross through MT 532, against order?
When I went to MB51, I found the material document for finished Material production with MT 101 and raw material consumption with MT 261. But in MB51when I tried to find out dross generation with MT 531, I did not get any material document for that particular order no.
In the production order though total quantity: 88000 and delivered quantity is only 26000. When user is trying to confirm the production order only for 200 units, system is giving the following error message:
Overdelivery is not permitted (Check entry)
Message no. RU139
Diagnosis
The total yield and scrap confirmed exceeds the overdelivery tolerance defined in the order header.
Procedure
You can either
u2022 reduce the confirmed quantity
u2022 deactivate the tolerance check during confirmations (customizing),
u2022 increase the overdelivery tolerance in the order header and then enter the confirmation again
Please tell me why Material movement of dross/ scrap is not visible and why production order is not getting confirmed
Thanks
ChandraChandra,
When you say te movement is with order confirmation then I assume that it is backflush of the components & byroduct.
If you do not find the material document in MB51 then it is not posted yet.
In that case excute T code COGI & process the same.
Regarding the order confirmation error, kindly check the 'Goods receipt' tab page in the order header.
The delivery completed indicator must be marked. Unmark the same & save.
Now try to process the confirmation.
Anyhthing else please let me know.
Hope this helps you.
SmanS -
Forecast consumption not working when using BAPI_SLSRVAPS_SAVEMULTI2
HI SAP APO experts,
I have a problem. We are sourcing our transactional data from non-SAP system so we had to develop an interface that will post transactional data to APO. We developed a program that will post data from flat file to APO LC. We used BAPI_SLSRVAPS_SAVEMULTI2 in posting sales order but my problem is that its not consuming my forecast. I am using strategy 20 and backward consumption of 28 days in my product master.
Using CIF, forecast consumption is working but not for our abap. Hope you can help me. Thanks.
MyleneHi Sarvesh,
No, I was not able to find what is that internal request type 52. But I did some more research and you need to have check mode populated in your BAPI. In our case, we can not hard code check mode in the BAPI since we are using more than one check mode. My abaper just parsed then change the program that it will parse check mode from material master to the BAPI. Now, forecast consumption is alreayd working. But I am still facing 2 issues:
1. After this change in the code, our program is now running longer than usual. This used to run only for 20 minuutes but now its running for more than 3 hours.
2. For materials using demand strategy 20, sales order is consuming forecast which is correct. But when I delete this sales order, forecast quantity does not go back to original quantity in the planning book.
Mylene -
Hello friends,
In a manufacturing company there are departments like lathe, milling. They use common material in the BOM's. The problem is consumption ( backflush ) is happening for the BOM components for Lathe department and not happening for Milling department.
This is not happening specifically from Jan1'08 ( Start of financial year ). The consumption was happening earlier. What can be the possible reasons?
Please guide???
Regards,
Narendra BoraHello friends,
The problem is still unresolved. Let me summarize once again.
1. There are two mfg dept. The BOM has some common components. The problem is the consumption ( auto backflush ) is happening in one dept and not happening in another dept.
2. This problem is happening from Jan 1st. Earlier to that the consumption was happening.
3. The reservation is getting created for the orders.
4. The goods movement for the finished goods is happening where as the same for consumption is not happening.
5. The error of goods movement not happening is also not going in COGI.
Please some one guide me what can be the posssible reasons.
Regards,
Narendra Bora -
Consumption value updated for zero value materials
Hi Masters
I have maintained value of a material in material master as zero.Although it is maintained zero, When the material is issued using 261 accounting document got generated and showin the following entries
Inventory a/c
Consumption a/c(+)
How it is happening?
Regards
Mohanhi,
Check your price control it would be MAP...
REASON :
Suppose you post the GR at price of 100/pc...where as in MMR the price is ZERO...
Now when you post the GR at 100/pc...the MAP changes in the MMR automatically...ie. via total value / total stock...so the MAP doesn't remain ZERO now...
So, now when you post the GI, the current MAP is taken from MMR ie. Non-ZERO value and so system post the accounting document while GI...
I hope the matter is clear now..
Regards
Priyanka.P -
Updation of Consumption values in material master
Dear Experts,
For a FERT ,
When I use strategy 40 , Consumption values ( PGI - Deliveries )are getting updated in MM02 in Forecast view.
whereas,
When I use strategy 50 , Consumption values are not getting updated in MM02 in Forecast view.
Is there any setting to control this updation of Consumption values in Material Master ?
Regards,
SheikHi,
Update of consumption is based on movement type, and you can decide which movement types should have or have not consumption updating.
Check in transaction OMJJ if the movement types in question have indicator "Consumption posting" (field V_156_VC-KZVBU) as marked.
If it is the case, consumption is updated, opposite for un-ticked.
Hope that helps.
Thanks. -
Prepare has not been completed succesfully
Hi Experts,
I started an upgrade release 4.6C to ECC 6.0 on windows 2003 db version is SQL Server 2005,
I am getting an error message at the begining of prepare phase,
I've also updated sapup.exe version and source system kernel to 2364,
how can i prevent this error,
ERROR: PREPARE has not been completed successfully.
Correct the problems reported by PREPARE otherwise
you cannot start the upgrade.
here is UpgDialog.log
Target SAP system is AHQ
Enter the SAP instance number [00]:
? INSTANCE NUMBER =
Waiting for input since 30.Eki.2008 10:31:46
> INSTANCE NUMBER = 00
Type of database system is mss
>>>>>>>>>> Input Wizard <<<<<<<<<<
Please enter up to 24 mount points for CDs.
Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
? MOUNT POINT 01 = E:\upgdvds\upgmaster_51033520\UMN_WINDOWS_I386
Reading data from "Upgrade Master CD/DVD"...
SAP UPGRADE CONTROL PROGRAM
================================
This is SAPup version 7.00/3 upgrade to release
600 of EA-APPL
600 of EA-DFPS
600 of EA-FINSERV
600 of EA-GLTRADE
600 of EA-HR
400 of EA-IPPE
600 of EA-PS
600 of EA-RETAIL
600 of ECC-DIMP
600 of ERECRUIT
600 of FI-CA
600 of FI-CAX
600 of FINBASIS
600 of INSURANCE
600 of IS-CWM
600 of IS-H
600 of IS-M
600 of IS-OIL
600 of IS-PS-CA
600 of IS-UT
600 of LSOFE
2005_1_700 of PI_BASIS
700 of SAP_ABA
700 of SAP_AP
600 of SAP_APPL
700 of SAP_BASIS
700 of SAP_BW
600 of SAP_HR
600 of SEM-BW
2005_1_700 of ST-PI
Target SAP system is AHQ, MSSQL database
? continue
? cancel
Waiting for input since 30.Eki.2008 10:34:32
> continue
ERROR: PREPARE has not been completed successfully.
Correct the problems reported by PREPARE otherwise
you cannot start the upgrade.
? continue
? cancel
And also in /usr/sap/put/log directoy these logs existent;
SAPup.log;
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
SEVERE ERROR: problems with SERVER mode - abort
...CANCELED at 20081030104921.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
...begin dialogue at 20081030105012
...end dialogue at 20081030105013
...begin dialogue at 20081030105013
...end dialogue at 20081030105015
...begin dialogue at 20081030105034
...end dialogue at 20081030105039
Reading Parameter File "C:\usr\sap\put\bin\DBSYNC.PAR" at 20081030105039
Condition level 1, total => FALSE '#if ( "MSS" == "ORA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "OPS" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "ADA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "INF" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "DB6" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "D4A" )' => FALSE
Condition level 1, total => TRUE '#elseif ( "MSS" == "MSS" )' => TRUE
...begin dialogue at 20081030105039
...end dialogue at 20081030105041
...STARTED at 20081030105041.
Reading Parameter File "C:\usr\sap\put\bin\TRATTR.LST" at 20081030105041
Reading Parameter File "C:\usr\sap\put\bin\TRGROUP.LST" at 20081030105041
...begin dialogue at 20081030105041
...end dialogue at 20081030105104
...CANCELED at 20081030105104.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.011.
...begin dialogue at 20081030105626
...end dialogue at 20081030105627
...begin dialogue at 20081030105627
...end dialogue at 20081030105630
...begin dialogue at 20081030105711
...end dialogue at 20081030105715
Reading Parameter File "C:\usr\sap\put\bin\DBSYNC.PAR" at 20081030105715
Condition level 1, total => FALSE '#if ( "MSS" == "ORA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "OPS" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "ADA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "INF" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "DB6" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "D4A" )' => FALSE
Condition level 1, total => TRUE '#elseif ( "MSS" == "MSS" )' => TRUE
...begin dialogue at 20081030105715
...end dialogue at 20081030105719
...CANCELED at 20081030105719.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
...begin dialogue at 20081030105752
...end dialogue at 20081030105753
...begin dialogue at 20081030105753
...end dialogue at 20081030105756
...begin dialogue at 20081030105814
...end dialogue at 20081030105818
Reading Parameter File "C:\usr\sap\put\bin\DBSYNC.PAR" at 20081030105818
Condition level 1, total => FALSE '#if ( "MSS" == "ORA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "OPS" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "ADA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "INF" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "DB6" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "D4A" )' => FALSE
Condition level 1, total => TRUE '#elseif ( "MSS" == "MSS" )' => TRUE
...begin dialogue at 20081030105818
...end dialogue at 20081030105824
...STARTED at 20081030105824.
Reading Parameter File "C:\usr\sap\put\bin\TRATTR.LST" at 20081030105824
Reading Parameter File "C:\usr\sap\put\bin\TRGROUP.LST" at 20081030105824
...begin dialogue at 20081030105824
...end dialogue at 20081030110026
...CANCELED at 20081030110026.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
...begin dialogue at 20081030110034
...end dialogue at 20081030110035
...begin dialogue at 20081030110035
...end dialogue at 20081030110038
...begin dialogue at 20081030110054
...end dialogue at 20081030110104
Reading Parameter File "C:\usr\sap\put\bin\DBSYNC.PAR" at 20081030110104
Condition level 1, total => FALSE '#if ( "MSS" == "ORA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "OPS" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "ADA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "INF" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "DB6" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "D4A" )' => FALSE
Condition level 1, total => TRUE '#elseif ( "MSS" == "MSS" )' => TRUE
...begin dialogue at 20081030110104
...end dialogue at 20081030110123
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
...begin dialogue at 20081030110134
...end dialogue at 20081030110140
...begin dialogue at 20081030110140
...end dialogue at 20081030110143
...begin dialogue at 20081030110149
...end dialogue at 20081030110154
Reading Parameter File "C:\usr\sap\put\bin\DBSYNC.PAR" at 20081030110154
Condition level 1, total => FALSE '#if ( "MSS" == "ORA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "OPS" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "ADA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "INF" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "DB6" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "D4A" )' => FALSE
Condition level 1, total => TRUE '#elseif ( "MSS" == "MSS" )' => TRUE
...begin dialogue at 20081030110154
...end dialogue at 20081030110155
...STARTED at 20081030110155.
Reading Parameter File "C:\usr\sap\put\bin\TRATTR.LST" at 20081030110155
Reading Parameter File "C:\usr\sap\put\bin\TRGROUP.LST" at 20081030110155
...begin dialogue at 20081030110155
...end dialogue at 20081030110328
...CANCELED at 20081030110328.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
...begin dialogue at 20081030110335
...end dialogue at 20081030110335
...begin dialogue at 20081030110335
...end dialogue at 20081030110337
...begin dialogue at 20081030110342
SEVERE ERROR: problems with SERVER mode - abort
...CANCELED at 20081030110342.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/3 patch level 25.013.
...begin dialogue at 20081030110858
...end dialogue at 20081030110859
...begin dialogue at 20081030110859
...end dialogue at 20081030110901
...begin dialogue at 20081030110937
...end dialogue at 20081030110940
Reading Parameter File "C:\usr\sap\put\bin\DBSYNC.PAR" at 20081030110940
Condition level 1, total => FALSE '#if ( "MSS" == "ORA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "OPS" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "ADA" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "INF" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "DB6" )' => FALSE
Condition level 1, total => FALSE '#elseif ( "MSS" == "D4A" )' => FALSE
Condition level 1, total => TRUE '#elseif ( "MSS" == "MSS" )' => TRUE
...begin dialogue at 20081030110940
...end dialogue at 20081030110941
...STARTED at 20081030110941.
Reading Parameter File "C:\usr\sap\put\bin\TRATTR.LST" at 20081030110941
Reading Parameter File "C:\usr\sap\put\bin\TRGROUP.LST" at 20081030110941
...begin dialogue at 20081030110941
...end dialogue at 20081030110945
...CANCELED at 20081030110945.
CHANGES.LOG
MILESTONE
"BEG_IR"
"STO_IR"
"20081030104921"
"20081030104921"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105012"
"20081030105012"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105013"
"20081030105013"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105013"
"20081030105013"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105015"
"20081030105015"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105034"
"20081030105034"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105039"
"20081030105039"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105039"
"20081030105039"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105041"
"20081030105041"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"STO_IR"
"20081030105041"
"20081030105041"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105041"
"20081030105041"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105104"
"20081030105104"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"STO_IR"
"20081030105104"
"20081030105104"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105626"
"20081030105626"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105627"
"20081030105627"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105627"
"20081030105627"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105630"
"20081030105630"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105711"
"20081030105711"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105715"
"20081030105715"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105715"
"20081030105715"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105719"
"20081030105719"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"STO_IR"
"20081030105719"
"20081030105719"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105752"
"20081030105752"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105753"
"20081030105753"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105753"
"20081030105753"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105756"
"20081030105756"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105814"
"20081030105814"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105818"
"20081030105818"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105818"
"20081030105818"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030105824"
"20081030105824"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"STO_IR"
"20081030105824"
"20081030105824"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030105824"
"20081030105824"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110026"
"20081030110026"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"STO_IR"
"20081030110026"
"20081030110026"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110034"
"20081030110034"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110035"
"20081030110035"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110035"
"20081030110035"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110038"
"20081030110038"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110054"
"20081030110054"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110104"
"20081030110104"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110104"
"20081030110104"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110123"
"20081030110123"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110134"
"20081030110134"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110140"
"20081030110140"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110140"
"20081030110140"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110143"
"20081030110143"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110149"
"20081030110149"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110154"
"20081030110154"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110154"
"20081030110154"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110155"
"20081030110155"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"STO_IR"
"20081030110155"
"20081030110155"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110155"
"20081030110155"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110328"
"20081030110328"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"STO_IR"
"20081030110328"
"20081030110328"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110335"
"20081030110335"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110335"
"20081030110335"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110335"
"20081030110335"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110337"
"20081030110337"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110342"
"20081030110342"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"STO_IR"
"20081030110342"
"20081030110342"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110858"
"20081030110858"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110859"
"20081030110859"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110859"
"20081030110859"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110901"
"20081030110901"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110937"
"20081030110937"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110940"
"20081030110940"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110940"
"20081030110940"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110941"
"20081030110941"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"STO_IR"
"20081030110941"
"20081030110941"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"DIA_IR"
"20081030110941"
"20081030110941"
"0"
"0"
"0"
"0"
MILESTONE
"END_IR"
"DIA_IR"
"20081030110945"
"20081030110945"
"0"
"0"
"0"
"0"
MILESTONE
"BEG_IR"
"STO_IR"
"20081030110945"
"20081030110945"
"0"
"0"
"0"
"0"
TOOLOUT.LOG
SAPup> Starting subprocess disp+work.exe with id 732 at 20081030103432
EXECUTING C:\usr\sap\AHQ\SYS\exe\run\disp+work.exe -V
disp+work information
kernel release 46D
kernel make variant 46D
DBMS client library SQL_Server_7.00
DBSL shared library version 46D.00
compiled on NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00
compile time Jan 14 2008 08:47:41
update level 0
patch number 2364
source id 0.2364
supported environment
database (SAP, table SVERS) 46A
46B
46C
46D
DBMS server MSSQL 6.5.213 or higher
MSSQL 7.0.1 or higher
operating system Windows NT 4.0
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
System build information:
LCHN : 955407
disp+work patch information
( 0.001) Correct cursor preservation (I) (note 307486)
( 0.002) SU53 reports always 'Check on S_TCODE SU53' (note 310513)
( 0.003) PXA: Emergency mode (note 307976)
( 0.004) Correct shortcut handling under EASY ACCESS (note 309791)
( 0.005) POST driver: no set locale (note 310076)
( 0.006) ASSIGN attr+off(len) TO <fs> (note 302214)
( 0.007) Contextmenu for tableview cells (note 309755)
( 0.008) Rfc and full screen (note 308383)
( 0.009) Dropdown listbox performance (note 307795)
( 0.010) Correct cursor preservation (II) (note 307486)
( 0.011) Spool-Patch-Collection 26 (note 92482)
( 0.012) Correct cursor preservation (III) (note 307486)
( 0.013) Correct cursor preservation (IV) (note 307486)
( 0.014) Core in dyCheckRadioGroups() (note 308958)
( 0.019) STAT: DB Resonse Time for SQL Server (note 310288)
( 0.021) Rfc authority problem (note 93254)
( 0.024) RFC extended trace information (note 311386)
( 0.027) CALL SCREEN: error 'MISMATCH DYNPRO NAME / CONTENT' (note 310186)
( 0.028) ABAP: OO-Transactions and event LOAD-OF-PROGRAM (note 312244)
( 0.029) Profile 'abap/oo_warn' suppress OO-context errors (note 182767)
( 0.031) Occasional core when reading statistics file (note 313669)
( 0.032) ABAP: unnecessary class-constructor calls (2) (note 213622)
( 0.035) Corrections in errormessage handling (sapdext) (note 312252)
( 0.040) TSTC: transaction is not an oo-transaction (note 315037)
( 0.044) F4 on checkbuttons (note 312258)
( 0.045) Core in moveleft() (note 312418)
( 0.046) Error trace: invalid dynpro dynpabsv.c 3490 (note 314373)
( 0.047) Error trace: memory conflict diagscrol.c (note 313967)
( 0.048) Iterator problem with iXML collections fixed (note 315119)
( 0.050) Invocation of not-implemented methods (note 314064)
( 0.051) Core at dynamic invoke with interface reference (note 314487)
( 0.052) GW: Avoid multiple send (note 314495)
( 0.053) Spool-Patch-Collection 27 (note 92482)
( 0.054) Printing via e-mail (note 311037)
( 0.055) User default time zone from TTZCU-TZONEDEF (note 314300)
( 0.056) Bad batch job statistic (note 315147)
( 0.057) LOOP AT SCREEN: counter field increased (note 314516)
( 0.058) Missing init. in temse (note 314094)
( 0.065) GW: shared block leak with multiple reg programs (note 309969)
( 0.067) RFC: load balancing over SAPRouter (note 316221)
( 0.068) No debugging until login while remote debugging (note 316456)
( 0.069) Open SQL: INTO CORRESPONDING with JOINs (note 315747)
( 0.071) Support 'Windows NT 5.1' (note 316188)
( 0.072) Destroyed dynpro load (note 207817)
( 0.073) Error in spool entry queue (note 316148)
( 0.074) mySAP.com workplace single signon enabling (note 177895)
( 0.075) Sap statistic destroys eye catcher (note 317178)
( 0.076) Syslog messages while printing (note 316630)
( 0.077) Performance optimization for list boxes (note 214806)
( 0.078) Loop in batch input (note 316686)
( 0.080) Loop in batch input 2 (note 316686)
( 0.081) Don't block s-messages in local update processing (note 312252)
( 0.084) Correct error message in conversion exit 'ALPHA' (note 318027)
( 0.085) Destroyed dynpro load (note 207817)
( 0.086) Print from rfc server (note 318692)
( 0.087) Unknown syntax errors after changing the kernel (note 142888)
( 0.088) RFC: error discarding unneeded tables (note 319634)
( 0.089) Sapstartsrv handle service stop and shutdown correctly (note 142100)
( 0.091) GW: Nonblocking connect problems (note 319675)
( 0.092) Tstc: transaction is not an oo-transaction (note 315037)
( 0.093) Coredump with 'INSERT LINES OF ...' (note 142100)
( 0.094) Corrupted cluster item displayed (note 318904)
( 0.096) BDC: Enable input in list screens (note 212569)
( 0.099) Hanging apps after writing core (note 320168)
( 0.102) Syntax warning for literals crossing line boundaries (note 319328)
( 0.103) Generation error at statement 'IF itab IS SUPPLIED' (note 321069)
( 0.105) Spool-Patch-Collection 28 (note 92482)
( 0.109) Several errors within footline (note 312848)
( 0.111) Check dynpro processor state (note 301406)
( 0.112) Memory usage roll area 0+1 (note 322070)
( 0.113) Sapstartsrv: GetProcessList exception, librfc32 delayload (note 142100)
( 0.114) Rfc call and default fontsize data (note 323342)
( 0.115) OBJECTS_NOT_COMPATIBLE with READ TABLE (note 323039)
( 0.116) Random syntax errors (MOVE-CORRESPONDING) (note 207149)
( 0.117) SKIP 1ST SCREEN: ignore GRAPH dynpros (note 317917)
( 0.118) Japanese IXML, table TCP0F (note 301406)
( 0.119) SE30 errors (note 170470)
( 0.121) Correct call of POV modules for comboboxes (note 323141)
( 0.122) Exception in NiExit (note 319675)
( 0.123) GW: No restart during db reconnect (note 321863)
( 0.125) TX variants: correct reset field input (note 325275)
( 0.126) ITS_LOGIN_CHECK_RFC rejected as XXPASS caller (note 324758)
( 0.129) Error message: correct cursor setting (note 318292)
( 0.130) Check dynpro processor state (II) (note 301406)
( 0.131) Correct SET FOCUS CONTROL for NO-PAI (note 322455)
( 0.132) Init tcview components (note 323686)
( 0.133) BDC: No loosing track of data during F4-Help (note 323061)
( 0.136) BDC: Avoid duplicate messages in log (note 324490)
( 0.138) Resize: docking control - dynpro (note 323974)
( 0.139) GW: Secinfo for start of external programs (note 323925)
( 0.140) False error texts for workplace ticket logon (note 325222)
( 0.141) "user locked" for logon attempt at CUA master system (note 325213)
( 0.143) HPL2 driver: unreadable text for green/red (note 323460)
( 0.146) Loop of dispatcher (note 325559)
( 0.148) Spool-Patch-Collection 29 (note 92482)
( 0.149) Control Framework global flush mode (note 316243)
( 0.150) TX variants: correct reset field input (II) (note 325275)
( 0.152) Em detach before process restart (note 326876)
( 0.153) Workplace: multiple logon popup for wingui sessions (note 326604)
( 0.154) ABAP Debugger: Rollback before restart (note 325903)
( 0.156) Conversion X to STRING (note 327086)
( 0.158) Bugfix new-page print on + message (note 107321)
( 0.159) IXML: coredump when parsing empty XML document (note 326888)
( 0.160) Resume in current screen after returning from exit module (note 327803)
( 0.161) SORT: close extract file, if runtime error occurs (note 328691)
( 0.162) Adapt ABAP runtime to new signal handling (note 329091)
( 0.163) BDC: corresponding screen to bsdup-entry in dybimsgi (note 330071)
( 0.164) Stat-file is not deleted in old 4.6 releases (note 329603)
( 0.169) Do not change loopheader during help processing (note 330761)
( 0.171) Disabling GUI in aRFC when called from tRFC (note 329811)
( 0.174) Test dynpro: do not call POV modules (note 332538)
( 0.175) No commit during wait in update task (note 332077)
( 0.176) Printing frames in text mode (note 320792)
( 0.177) Spool-Patch-Collection 30 (note 92482)
( 0.178) TSTC transaction is not an oo-transaction (note 315037)
( 0.179) RFC-Import of deep structures failed (note 333694)
( 0.180) STRING_BAD_REF in control break processing (note 332663)
( 0.181) Increase structure stack (note 332500)
( 0.184) PXA: initialization (note 160875)
( 0.185) PXA_NO_FREE_SPACE (note 147568)
( 0.186) Update task: increase vb2Cnt for update type 5 (note 333878)
( 0.187) Correct handling of empty loop lines (note 334886)
( 0.188) TX variants: correct reset field input (III) (note 325275)
( 0.189) EmHyperContextCreate() => alreday exists (note 334389)
( 0.192) Default cursor: reset cursor offset (note 334951)
( 0.194) Invalid client index of sap gateway (note 333949)
( 0.195) RFC authority check failed (note 93254)
( 0.196) BDC: No loosing track of data after F4-Help (note 323061)
( 0.197) ABAP: optimized dynamic SELECT clauses (note 324772)
( 0.198) Bugfix new-page print on + message (note 107321)
( 0.199) Bugfix displaying printer name after print (note 107321)
( 0.201) Error recovery (in ni datagram) after workprocess-restart (note 335967)
( 0.207) Diag: correct list size (note 337298)
( 0.209) GW: memory block freed twice (note 337957)
( 0.210) Incorrect logon ticket expiration calculation (note 337794)
( 0.218) Errortrace: invalid offset (dybasfield.c 95) (note 337820)
( 0.219) Deactivate LIST TO MEMORY on selection screen (note 313558)
( 0.220) Dbbmng0.c: generic invalidation of shared buffer objects (note 338451)
( 0.221) Itab operations on tableview-controls (note 339270)
( 0.222) GW: RFC attached gui (note 337425)
( 0.223) ASSIGN: set output length accurately (note 338925)
( 0.224) Tabstrip pages and wrong scroll offset (note 339469)
( 0.225) Set pf-status excluding and rollout (note 338954)
( 0.226) Auth problems with 20 characters transactions (note 339913)
( 0.227) Batch input: new algorithm for QID-generation (note 338246)
( 0.229) Inappropriate short dump ZDATE_ILLEGAL_LOCTIME (note 323954)
( 0.230) Print of a list dumps (note 338994)
( 0.231) Archive device (note 339659)
( 0.232) S-messages in CTU-log (note 339302)
( 0.238) Correct trace SET PARAMETER (note 340096)
( 0.240) Print of a list dumps (II) (note 338994)
( 0.242) Start Row Start Column for Dynproresizing (note 351685)
( 0.243) GW: Bad em context handling (note 351526)
( 0.244) SORT AS TEXT: length too short (note 350526)
( 0.245) Get cursor information on pushbutton (note 351890)
( 0.247) ABAP: Slin default check; type I vs. type P (note 351976)
( 0.248) GW: CCMS Monitoring Patch-Collection 1 (note 202591)
( 0.249) Short dump CALL_TRANSACTION_LOCKED (note 350360)
( 0.250) Controls and list processing (note 352065)
( 0.251) Blanks in authorization values (note 207196)
( 0.252) Tableview line/column selection (note 350363)
( 0.253) Spool-Patch-Collection 31 (note 352269)
( 0.254) Decrease and increase for dynpro and window (note 352542)
( 0.255) ABAP Debugger: Avoid DEBUGGER_ILLEGAL_VALUE in RFC-Debug. (note 182989)
( 0.256) Incomplete DATA in D010INC and D010TAB (note 352480)
( 0.257) Diag: warning and resize (note 212524)
( 0.258) Workplace: provide logon ticket for X.509 logon (note 350776)
( 0.260) StartRow StartColumn for Dynproresizing (note 351685)
( 0.261) EmHyperContexts: reduce memory consumption (note 353103)
( 0.262) Invalid focus memory (note 353496)
( 0.263) EmHyperContexts: reduce memory consumption (II) (note 353103)
( 0.266) Slow SetQoS due to unnecessary DNS query (note 180940)
( 0.268) ABAP-Exception-Handling: Internal State-Stack (note 350146)
( 0.269) BDC: no user command allowed on SAPMSYST 0040 (note 163639)
( 0.270) Wrong portability warnings from extended syntax check (note 353681)
( 0.271) Passing EXP-IMP parameters in RFC calls (note 352629)
( 0.272) Spool-Patch-Collection 31a (note 352269)
( 0.273) Modal level and suppress dialog (note 355616)
( 0.274) DBIF_RSQL_INVALID_REQUEST with very old cluster records (note 353651)
( 0.275) Horizontal radiobutton groups (note 355260)
( 0.276) Proportional cut for variable Dynpro-objects (note 351685)
( 0.277) Hostname resolution blocks processes (note 356788)
( 0.278) Tabstrip pages and wrong scroll offset (note 339469)
( 0.280) Core in DiagiTableHeader (note 159421)
( 0.281) GW: Bad statistic after summer time switch (note 353893)
( 0.283) CPIC-Timeout for frontend printing (note 352269)
( 0.284) List scrollbar and docking control (note 357241)
( 0.285) Sy-SubRc 8 with SELECT SINGLE on logic cluster table (note 355714)
( 0.287) Missing entry in table FIDO (note 357019)
( 0.290) BDC: conversion of old batch-input logfiles (note 356758)
( 0.293) Invalid sapgui data (note 358681)
( 0.294) Reading of ASTAT records fails in 4.6D (note 358532)
( 0.295) ABAP: Loop in function LookForFref (note 357698)
( 0.297) Muliconnect error reporting (note 358171)
( 0.298) RFC: data dependent read error (note 358557)
( 0.300) Protect against 'error in datastream' (note 359511)
( 0.301) Treatment of looplines by loc. horiz. resize (note 212861)
( 0.302) Initial values with DynpValuesUpdate (note 359873)
( 0.303) ABAP: warning for duplicate keys removed (note 359114)
( 0.304) Core dump when calling RfcClose (note 359865)
( 0.306) Suppression of unnecessary syslog messages (note 359523)
( 0.308) System Core Dump with F4-Button in R/3-Dialog(modal) setting (note 212861)
( 0.309) Core dump in RFC engine (note 353136)
( 0.311) Start EASY-ACCESS only for dialog sessions (note 360980)
( 0.314) Check if dynpro exists before access it (note 361120)
( 0.315) Optimize concatenate for STRING (note 327185)
( 0.317) New RFC logon method 'external identification' (note 358469)
( 0.319) List scrolling: last line missing (note 362181)
( 0.320) GW: Set locale in update task (note 360971)
( 0.321) SORT: avoid EXSORT_TOO_MANY_PARALLEL_SORTS (note 361532)
( 0.322) Extended syntax check with BETWEEN ... AND (note 361470)
( 0.323) ICMAN fails to open event flags for HTTP connections (note 360696)
( 0.326) Open SQL: improved statement generation for UPTO (note 361392)
( 0.327) Check (ABAP_ASSERT) in ASSIGN to avoid core (note 363059)
( 0.329) Bad NOWP request (note 365156)
( 0.330) ABAP; SCAN STRUCTURE: error in SELECT-ENDSELECT logic (note 363992)
( 0.331) Native SQL: return code for EXECUTE PROCEDURE (note 364707)
( 0.332) Semaphore error in ASTAT (note 363499)
( 0.333) Printing with format LETTER (note 363624)
( 0.334) Problems with missing or short quickinfo (note 363394)
( 0.335) Parameters in macro _splitpathU swapped (note 365337)
( 0.339) Modified length mismatch (note 207817)
( 0.340) Problems with missing or short quickinfo (2) (note 363394)
( 0.341) Errortrace invalid value dybas.c 0179 (note 337820)
( 0.342) Errortrace invalid parameter dynpdiag 1131 (note 337820)
( 0.343) Errortrace dytracefocus invalid container (note 353496)
( 0.346) Spool-Patch-Collection 32 (note 352269)
( 0.347) Invalid focus memory 2 (note 353496)
( 0.348) Prevent duplicate RFC struct parameter transmission (note 365916)
( 0.351) Native SQL: memory leak for stored procedures (note 367509)
( 0.352) Resizing side to side and one below other Dynpro-Objects (note 367811)
( 0.353) Check ztta/dynpro_area (note 167229)
( 0.354) Problems with missing or short quickinfo (3) (note 363394)
( 0.355) GW: Bad NOWP request II (note 365156)
( 0.358) Breakpoint in ABAP Debugger at CONTINUE (note 368433)
( 0.359) Errortrace: should not happen (dycuahlp 1661) (note 369415)
( 0.360) Reactivate suspended clients (note 367384)
( 0.361) Disable persistent trace for RFC-Library (note 364034)
( 0.365) Large file support (note 330992)
( 0.366) IMPORT: avoid IMPORT_INIT_DECOMPRESS_FAILES (note 370053)
( 0.367) BAPI_USER_CHANGE returns wrong/blank error message (note 369761)
( 0.368) ABAP debugger: field display and global TABLES-parameters (note 370103)
( 0.369) ABAP debugger: empty source display (note 370717)
( 0.370) Saplicense: license buffer not initialized (note 371301)
( 0.371) List token in SELECT (note 370587)
( 0.373) GW: Duplicate conversation ids in gateway work processes (note 371481)
( 0.375) Dynamic Type at CREATE DATA (note 371607)
( 0.376) Printing selection page & long transaction (note 370661)
( 0.377) Library iXML: correction of CDATA size problem (note 371846)
( 0.378) DEC field input for none DDIC fields (note 373047)
( 0.379) Spool-Patch-Collection 33 (note 352269)
( 0.380) C-Call ABAP_CALLSTACK (note 371779)
( 0.381) Loop during decompression of corrupted Sources/Loads (note 374200)
( 0.382) Extended table compression for certain RFC connections (note 373452)
( 0.383) SORT: avoid EXSORT_TOO_MANY_PARALLEL_SORTS and recursion (note 361532)
( 0.384) PostScript error with TrueType fonts (note 373604)
( 0.385) XML-Import failed after empty structure tags (note 374447)
( 0.386) Disable QoS support by default (note 180940)
( 0.387) Message display type (note 368333)
( 0.389) DEC field input for none DDIC fields II (note 373047)
( 0.390) Long running report (note 373343)
( 0.391) Illegal request looping in dispatcher (note 373345)
( 0.394) Fix printing selection page & long transaction (note 370661)
( 0.397) Reserve address space for Extended Memory (note 373326)
( 0.399) VALUE /namespace/const (note 371720)
( 0.402) DYNG: get translated buttontexts from D021T (note 363394)
( 0.403) Correct returncode for SET_DYNP_FIELD_VALUE (note 374941)
( 0.404) Refresh control from screen (note 375251)
( 0.406) Receive result of aRFC (note 375356)
( 0.410) Disp+Work doesn't start up (note 376242)
( 0.414) DEC field input for none DDIC fields (note 373047)
( 0.415) Core dump in GenViewGetPbagRudi (note 375055)
( 0.416) DBIF_REPO_PART_NOT_FOUND during Garbage-Collection (note 374884)
( 0.417) Control focus correction (note 374510)
( 0.418) Title problems (note 374560)
( 0.419) Window width > 255 cause list problems (note 375856)
( 0.420) IS REQUESTED/SUPPLIED and RETURNING parameter (note 375329)
( 0.423) DEC field input for none DDIC fields (note 373047)
( 0.424) Core in appl info (note 376906)
( 0.425) Core in DiagIConvert, if trace level 3 (note 377184)
( 0.426) Correction for Spool-Patch-Collection 33 (note 352269)
( 0.429) Change default for cursor preservation (note 378706)
( 0.430) Error trace from dyariftb() (note 378093)
( 0.431) Enqueue table overflow, syslog message corrected (note 378682)
( 0.433) DEC field input for none DDIC fields (note 373047)
( 0.434) Illegal chars set spooljob to error (note 379119)
( 0.435) Debugger: data references and tables of type I (note 378838)
( 0.436) Set DISPLAY AGAIN in TH (note 380164)
( 0.437) Prepare: several mySAP.com components in one DB (note 379572)
( 0.439) Workplace: disable password logon (note 379081)
( 0.445) DiagSetCodepage() failed (note 382240)
( 0.446) Sapstartsrv update available.log on Start/Stop (note 142100)
( 0.447) Ldapreg: ITS LDAP registration (note 379691)
( 0.448) GW: Wp stuck in PRIV mode (note 381870)
( 0.449) Too many invalidations on USRBF2 (note 319727)
( 0.450) Correct static focus on subscreens (note 380809)
( 0.451) Correct HOLD DATA message (note 381528)
( 0.452) Trace DYNP_SET/GET_STATUS (note 381694)
( 0.453) Init screen buffer parameters (note 382032)
( 0.454) No core in dypov_treatDpovtabRow (note 381221)
( 0.455) Server shutdown after bind error (note 382440)
( 0.457) Handling of fatally corrupted cluster records (note 381968)
( 0.466) EXPORT: dynamic export of strings (note 384694)
( 0.467) Message in help: no core dump (note 384639)
( 0.468) Pull up other objects down of table after TABLE_PBO_DONE (note 383033)
( 0.469) Tablecontrol init and context (note 373977)
( 0.470) Correction of the nls locale check tool (note 40815)
( 0.471) GW: Missing aRFC response (note 384015)
( 0.472) GW: Core during write of statistic (note 384433)
( 0.473) Wp stuck in PRIV mode (II) (note 381870)
( 0.474) Shared Pool disturbed corrected (note 384810)
( 0.477) SORT/EXTRACT: large file support (note 384257)
( 0.478) Codepage problem: sap8000 (shift_jis) (note 384947)
( 0.479) Active/Inactive-Handling (note 385628)
( 0.480) Sporadic logon failures in batch processing (note 385894)
( 0.483) GW: Free unallocated memory (note 387747)
( 0.484) SORT/EXTRACT: large file support (II) (note 384257)
( 0.487) Open SQL: several minor errors (note 386783)
( 0.489) RABAX no dbrollback and dbcommit at core (note 386268)
( 0.490) C-call DY_GET_S_MESSAGE available (note 383089)
( 0.491) Correct I message for batch input (note 386661)
( 0.492) Do not skip message popup (note 385147)
( 0.493) Async RFC: set size of full screen (note 385132)
( 0.494) Correct error messages for CALL SUBSCREEN (note 386674)
( 0.495) Logon tickets slightly too long valid (note 387595)
( 0.496) Format error during output of empty strings (note 385796)
( 0.497) RFC: patch collection (46D) (note 387366)
( 0.498) Method calls in arithmetics (note 387066)
( 0.499) Reallocate the number of boxes for resizing (note 388988)
( 0.500) Generate correct forkey selects in dynpro (note 388699)
( 0.501) Destroyed dynpro load (note 207817)
( 0.502) Open a new audit file next day after maxsize event (note 321148)
( 0.503) Delete audit files with extended filenames (SM18) (note 370829)
( 0.504) DiagSetCodepage() failed (note 382240)
( 0.507) Missing arfc response (II) (note 384015)
( 0.508) Generation of very long sources: repeating END_INBUF (note 389041)
( 0.509) Correct hold control framework focus (note 389364)
( 0.510) BDC: F1 or F4-request in bdcdata (note 323061)
( 0.511) Overflow of memory (note 370661)
( 0.512) PARAMETERS referencing a named DDIC include (note 389940)
( 0.515) DB2/390: default dbs/db2/use_hints=abap->1 (note 162034)
( 0.516) Recovery from NI-error after WP-restart (note 335967)
( 0.517) Avoid RFC server timeout (note 390219)
( 0.522) Avoid core in ABAP debugger by bad string references (note 391169)
( 0.523) Keep scrollposition (note 391871)
( 0.524) ABAP debugger: Display header for bad object reference (note 391187)
( 0.530) Enqueue traces during transaction reset (note 392873)
( 0.531) Garbage-Collection beyond 600MB (note 393378)
( 0.534) Enqueue traces during transaction reset (II) (note 392873)
( 0.535) CPICFAIL in smq1 after kernel upgrade (note 394549)
( 0.536) APO: correct internal table processing in COM routines (note 395695)
( 0.537) DYNPRO_FIELD_CONVERSION on Get Parameter (output) (note 395450)
( 0.538) Core in dyGetDataR() (note 395299)
( 0.540) Core in DpFreeResource after restart (note 394454)
( 0.542) Restore of sy.datar when popping screen (note 393511)
( 0.543) Open SQL: Memory leak when updating with %_HINTS (note 393897)
( 0.547) List scrolling: last line missing(2) (note 362181)
( 0.548) DiagSetCodepage() failed (note 382240)
( 0.549) Limit on number of sessions per logon (note 392369)
( 0.552) ABAP: error in string access with offset or length (note 396800)
( 0.553) Wrong portability warnings from SLIN (note 353681)
( 0.555) SY-VLINE in Thai on AS/400 (note 391627)
( 0.557) Unsuccessful READ on a SORTED TABLE (note 395205)
( 0.559) Sapstartsrv shutdown one process after the other (note 142100)
( 0.560) GW: COMPUTE_INT_TIMES_OVERFLOW in SAPLSALK (note 395671)
( 0.561) MS: improved trace features (note 396750)
( 0.562) ABAP: PERFORM .. CHANGING VALUE(<itab-line>-comp) (note 399078)
( 0.564) No hint generation in case of SELECT SINGLE (note 397170)
( 0.565) READ TABLE with attribute keys (note 399263)
( 0.566) Error in msg-server communication (note 398525)
( 0.568) Spool-Patch-Collection 34 (note 352269)
( 0.569) GW: Destroyed update start message (note 157840)
( 0.576) ABAP debugger: display active calls (note 399920)
( 0.577) ABAP debugger: display of interface aliases (note 399915)
( 0.578) ABAP: SET LOCALE and SUBMIT / CALL TRANSACTION (note 399918)
( 0.579) Enforce minimal patch level for database library (note 400216)
( 0.581) Ticket logon resets initial flag (password) (note 402076)
( 0.582) New translations cause locks on D020 (note 36795)
( 0.585) Catching of problems during string <-> char handling (note 402340)
( 0.586) GET LOCALE: language incorrect (note 402801)
( 0.587) Icons are not printed properly (note 402967)
( 0.588) Em context destroyed after exception (note 403562)
( 0.589) Dummy call: super constructor (note 401553)
( 0.590) Visibility of local types (note 401910)
( 0.591) Coredump with READ TABLE and float attributes (note 400516)
( 0.592) Offset/length specifiers in a table key definition (note 402255)
( 0.594) Resize: docking control - dynpro (note 323974)
( 0.598) Avoid inconsistent overall source time stamp (note 405821)
( 0.599) PXA: correct unfound object cache & statistic counters (note 406075)
( 0.600) SY-VLINE and JAVASCRIPT in Thai on AS/400 (note 391627)
( 0.601) Avoid inconsistent overall source time stamp (II) (note 405821)
( 0.605) RFC_DEBUGGING_NO_DIALOG_USER (note 407471)
( 0.606) Core in dyAbapGetContainerPosition (note 405930)
( 0.607) X.509 certificate logon: timezone not set (note 408601)
( 0.608) Unsuccessful READ on a SORTED TABLE (II) (note 409175)
( 0.609) IPC, max shm size detection accelerated (note 406738)
( 0.610) Graphical characters and page borders (note 406673)
( 0.611) SE30: close measurement on /n (note 381500)
( 0.612) Detail selection does not work correct (note 400090)
( 0.613) Negative value for hdcurrow is not permitted (note 352542)
( 0.624) Cutting terminal names (note 412628)
( 0.625) Update debugging (note 336925)
( 0.626) Control for Table-Control in Resizing is wrong (note 388988)
( 0.627) Correct treatment of field symbols (note 406306)
( 0.629) Init params of ab_ListGetFieldName (local field symbols) (note 413506)
( 0.630) Open SQL: more than 255 alias names in SELECT list (note 411136)
( 0.631) Open SQL: wrong SY-DBCNT for FETCH NEXT (note 412399)
( 0.632) Core in db_blob (note 412063)
( 0.633) Core in DiagGetWindowDimension (note 412168)
( 0.634) Core by 'Display current statement' in debugger (LREF) (note 411673)
( 0.636) Coredump in PfOpenScratchFile (note 414242)
( 0.637) VALUE class=>const (note 413384)
( 0.639) Hebrew Sapscript printing causes signal 11 (note 155261)
( 0.640) Workarea change in case of SELECT SINGLE with SY-SUBRC 4 (note 410175)
( 0.641) Function DB_DBSCHEMA returns correct result now (note 411971)
( 0.642) Wrong syntax error at literals in macros (note 411757)
( 0.643) Change of an interface (note 411769)
( 0.647) Dbbuf: restrict rtbb/buffer_length to 200000 [kB] (note 414220)
( 0.649) Inserted option WAN_CONN into RfcOpenEx (note 415169)
( 0.650) SU01: error texts for invalid passwords (note 369761)
( 0.651) CONVERT TIME STAMP... for 9999/31/12 23:59:59 (note 401610)
( 0.653) Text of check- and radiobuttons with icon (note 414703)
( 0.654) MESSAGE ... INTO no rabax at message x (note 408740)
( 0.655) New list line at program load (note 412142)
( 0.656) Displaying frames in lists (note 412787)
( 0.657) Selection page and empty report (note 370661)
( 0.658) VMIT (NT): higher precision (note 414135)
( 0.659) Runtime error DSTEP_WRONG_PROGRAM (note 416350)
( 0.660) Core in csulzh.c (note 413899)
( 0.661) Msg_server accept ad-msg opcode 60 AD_SELFIDENT (note 415447)
( 0.662) Highlighting in Hebrew list printing (note 353987)
( 0.663) Extended syntax check with BETWEEN ... AND (2) (note 361470)
( 0.664) Breakpoint at (RFC) function module (note 414952)
( 0.665) Don't break iXML because of missing character (note 410929)
( 0.667) WP opmode switch (note 415840)
( 0.674) Msg_server accept ad-msg opcode 60 AD_SELFIDENT (note 415447)
( 0.675) Duplicate key in VBMOD (note 416961)
( 0.676) Trace spa/gpa memory overflow (note 34533)
( 0.677) Dbbuf: check rtbb/buffer_length and rtbb/max_tables (note 414220)
( 0.678) Display '?' in DropdownListboxes (note 417405)
( 0.679) Correct call dialog for system messages (I) (note 416053)
( 0.680) Correct call dialog for system messages (II) (note 417096)
( 0.682) Memory leak in short storage (MEMSAV) (note 419819)
( 0.683) Spooler C-call info msg in trace (note 418740)
( 0.684) Dithering of color bitmaps (note 410727)
( 0.685) Standalone enqueue server prepared (note 419283)
( 0.686) Correction of the nls locale check tool (note 40815)
( 0.687) System Core Dump in C-Destructors of ABAP Objects (note 416163)
( 0.688) QHi Experts,
After i tried a few times, i can successfully start prepare with upgrade asistant monitor - Administrator >> Start Prepare,
Thanks -
Updation of ABC indicator in Material Master
Hi,
For ABC analysis, I carried out it according to T_code MC40(Usage value). I got the category of material. For eg "A".But how the ABC indicator updates in Material master.Because I couldnt get indicator in MRP1 view.
Whats the right way? Pls guide me.
Thanks,
Goraksh.Hi,
Update of consumption is based on movement type, and you can decide which movement types should have or have not consumption updating.
Check in transaction OMJJ if the movement types in question have indicator "Consumption posting" (field V_156_VC-KZVBU) as marked.
If it is the case, consumption is updated, opposite for un-ticked.
Hope that helps.
Thanks. -
Hello,
In my JWS app I save on the user system a db.sqlwrapper database, for the app consumption (not read-only). I now need to make a change to the schema, of the db.
Is it possible that users on their next update (launch of the app) they once only execute java code that would do the required (perhaps in some extra .jar) and then not again (since the change needs to be done only once)?Easiest way would be to provide a db upgrade mechanism. I'd suggest numbering your upgrades and creating a table where you store executed upgrades. On application startup (or db startup if they differ), you'll just need to check the presence of upgrades higher than the last executed one.
I've been doing this for a long while.
In my case it's even easier 'cause I've got both a read-only db and a user one.
I record upgrades by number and key (actually keys comma separated) in the read-only db (that gets updated through JWS), storing SQL instructions in a property file (I read using the key retrieved in the DB).
That's it: select max(required upgrade) as A from readOnly.UP, select max(executed update) as B from userDB.UP, if A>B for each key K in readOnly.UP where K>B, split K, for each part of K read property and add text as batch, once done cicling through K.parts execute batch and insert new line in userDB.UP.
One last thing: at the end of userDB creation you should insert a line in the userDB.UP to mark out your DB version.
This way you'd be able to upgrade your db schema (and data if needed) whenever you like.
Bye. -
Account Assignment - Qty and Value Update
Hi,
I need to have value and qty update for a a/c assignment po's.. ie in po i'm using a/c assignment as A, and in gr i need to have qty and value update . how to do?? is it possible? i knew that that a/c assingment won't generate qty update for a/c assignment catergores... is any way to create qty update for a/c assignmnt cateroires (K-cost center,A-Asset)Hi,
when you are creating a PO with account assignments menas , the costs of this product need to get posted to the account assignment , and the material is being procured for consumption ( not for stock) to this account assignment.
But however , qty and value updates depends upon the material type of the material.When you use a stocked material type material is used for the PO, change the account assignment definition as said in above posting.
Chek the material type of the material you used for the PO to your error message.
Regards, -
Can anyone tell me where to see OSS notes
Hi
Can anyone tell me where to see composite OSS note 586163 (any OSS notes). In which site and in which category i should search.www.service.sap.com
SAP Support Portal
Quick Lnks :
Search for OSS notes.
You need to have a login..its not free.
After login - Help & Support - Search for SAP notes
<b>
Anyws here is the note</b>
Summary
Symptom
You are transferring data from SAP R/3 Inventory Management to the BW system. You get unexpected data or data that differs from the data in the analyses in the R/3 system.
This note should help you to analyze this problem.
Other terms
2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 2LIS_03_S195,
2LIS_03_S196, 2LIS_03_S197, 2LIS_03_S198, 0IC_C01, 0IC_02, 0IC_C03,
0IC_MC01, 0IC_MC02, 0IC_MC03, stock analyses, inventory management,
Non-cumulative InfoCubes, stock key figures, stock, stocks,
RMCBINIT_BW, RMCBNERP, RMCBNEUA, consistency,
data consistency, healthcare, health service
Reason and Prerequisites
This note provides an overview of the release strategy, sources of information, tips and tricks, and known errors for this subject area.
Solution
Contents
1. Release strategy
a) General information
b) Recommended objects for BW Releases 3.0B, 3.1 Content and 3.2 Content
c) Recommended objects for BW Releases 2.0B and 2.1C
d) Obsolete objects
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
2. Sources of information
a) BW technology
SAP BW online documentation
"How to" documents
b) Business Content
Online documentation for BI Content
Extraction Documentation:
"How to" documents
Plug-In information
3. Extracting non-cumulative data from R/3
a) Explanations for the extraction
b) Known errors
Stocks (2LIS_40_S278/2LIS_03_BX)
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
Industry-specific notes
4. Technical information regarding non-cumulative info cubes in BW
a) Warehouse Management
b) Queries
c) Update rules
d) Known errors
5. Stock Analyses in BW
a) Explanations on data flow
b) Known errors
c) Tips and tricks
6. Performance
1. Release strategy
Use the following objects depending on your BW and R/3 or plug-in releases:
a) General information
The following basic principle applies: The 0IC_C03 InfoCube (material movements) replaces the 0IC_C01 (material movement plant) and 0IC_C02 (material movements storage location) InfoCubes. The 2LIS_03_BX (material stocks) InfoSource or DataSource replaces the 2LIS_40_S278 (transfer BW: stock) 2LIS_03_S197 (material stocks storage location) and 2LIS_03_S198 (material stocks plant) InfoSource or DataSource. The 2LIS_03_BF (material movements) InfoSource or DataSource replaces the 2LIS_03_S195 (material movements storage location) and 2LIS_03_S196 (material movements plant) InfoSource or DataSource.
We therefore STRONGLY recommend that you use the OIC_C03, 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM objects. We will continue to deliver and support any other objects mentioned in this note, but only for reasons of downward compatibility. These objects will not be enhanced because they are based on obsolete technology.
For information about the general support for DataSources based on information structures, see also Note 543002.
As of PI 2002.2, the 2LIS_03_BX DataSource is available for Release 4.0B and higher.
As of PI 2001.2, the 2LIS_03_BF and 2LIS_03_UM DataSources are available for Release 4.0B and higher.
The 0IC_C03 InfoCube is available as of Release 3.0B.
b) Recommended objects for BW Release 3.0B and higher
InfoCube: 0IC_C03 (Material movements)
InfoSources and update rules:
2LIS_03_BX (stocks) - available for Release 3.0B as of Support Package 10
2LIS_03_BF (movements)
2LIS_03_UM (revaluations)
If your Support Package version for Release 3.0B is Support Package 9 or lower, you have the alternative option of using the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons stated above, we recommend that you change to 2LIS_03_BX as of Support Package 10. For more information, see Note 588015.
c) Recommended objects for BW Releases 2.0B and 2.1C
InfoSources: 2LIS_03_BX (stocks) - available for Release 2.0B as of Support Package 30
- available for Release 2.1C as ofSupport Package 22
2LIS_03_BF (movements)
2LIS_03_UM (revaluations)
If you are using Release 2.0B Support Package 29 or lower or Release 2.1C Support Package 21 or lower, you can alternatively use the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons given above, we recommend that you change to 2LIS_03_BX as of Support Package 30/Support Package 22. For more information, see Note 588015. Unfortunately, we cannot provide the 0IC_C03 InfoCube and related update rules. If you need to use this InfoCube, we can provide a similar solution to the one provided for Releases 3.0B or higher as part of a consulting project. Note that Note 589024 does not apply in this case.
d) Obsolete objects
If you are using R/3 Release 3.1I and do not intend to upgrade to a higher release (regardless of the BW release) in the foreseeable future, use only the 0IC_C01 and 0IC_C02 InfoCubes and the related InfoSources or DataSources 2LIS_03_S195 - 2LIS_03_S198. If you are using the Healthcare industry solution and are interested in using the 0IC_C01_Q0020 and 0IC_C01_Q0021 queries, you can also use the 0IC_C01 InfoCube and related objects. Unfortunately, there is no automatic data migration for the transition from 0IC_C01/2 to 0IC_C03. See also Note 804781 for a complete overview of all key figures in 0IC_C03 that are also possible in 0IC_C01/2.
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
For more information, see Note 591063.
2. Sources of information
The main sources of information are located in the BW online documentation in the BW section of the SAP Service Marketplace and in the IMG documentation for the Plug-In. Other useful information is contained in various notes. These notes are listed under headings 3 - 6 below.
a) BW technology
This area contains documentation on the technical mapping of stock analyses in SAP BW.
Online documentation SAP BW (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration -> SAP BW
i Stocks
-> BI Platform -> OLAP
-> Performance Optimization -> Stocks
ii Validity Table
-> Data Warehousing
-> Administrator Workbench -> Modeling -> InfoCube
-> Additional functions for InfoCube maintenance
-> Stock Parameter Maintenance
iii Compression
-> Data Warehousing
-> Administrator Workbench -> Data Warehouse Management
-> Process Management
-> Managing Data Targets
-> Managing InfoCubes -> InfoCube Compression
iv Aggregation
-> Data Warehousing
-> Administrator Workbench -> Modeling
-> InfoObject -> Create InfoObject: Key Figure
-> Aggregation v Exception Aggregation
-> BI Platform -> OLAP
-> Special OLAP Functions and Services
-> Aggregation
-> Scenarios for the Use of an Exception Aggregation
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> In the information index: N ("Non-cumulatives") ->
"Non-Cumulative Values 3.x (ppt)"
b) Business Content
This area contains the business content representation of stock analyses in SAP BW, based on the SAP R/3 process and object model.
Online documentation for BI Content (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration: BI Content
-> BI Content -> Supply Chain Management
-> Supply Chain Performance Management -> Inventory Management
Documentation for extraction (OLTP system)
-> Transaction SBIW
-> Business Information Warehouse
-> Settings for application-specific DataSources
-> Logistics
Here you will find the relevant documentation for each of the relevant nodes.
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: N ("Non-cumulatives") ->
"How to... Handle inventory management scenarios in SAP BW 3.x" (pdf)
Plug-In information
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Extractors - Plug-in
3. Extracting non-cumulative data from R/3
This section explains the extraction process in the R/3 system and it gives an overview of known errors and their solutions.
a) Explanations for the extraction
Determining transaction keys
Note 492828
Determining the component
When stocks are initialized, the 'MM' core application is transferred, regardless of which component you specify in Customizing under 'Specify Industry' (TAC MCB_). You must implement Note 323018 for this purpose.
In most cases, the 'MM' Core application is also used when you initialize documents and for the delta load. However, 'IS-R' is transferred as the component if Retail is set as the component and you are working with stock transfers or movements for material group articles (MATNR <> MATBF).
To create the component, the BW enrichment is required during extraction. For more information, see Notes 315880 and 353042.
The "GETSYSDEF" report provides the system setting.
Creating non-cumulative relevance
In general, the non-cumulative relevance is set to '1', meaning 'relevant'. The exceptions are consumption postings (BSTTYP = V and BSTAUS = V) and postings for material group articles (MATNR <> MATBF). Value '2' is assigned in these cases.
Logistics data extraction: Customizing Cockpit (transaction LBWE)
You can configure the 2LIS_03_BF und 2LIS_03_UM DataSources in application 03. You cannot configure the 2LIS_03_BX DataSource in the Customizing Cockpit. To activate the 2LIS_03_BX DataSource, see Note 631345.
Generic extraction of stocks
This function is available as of PI 2003.1. For lower release levels, a consulting solution can be implemented on request (contact SAP in this case).
User exit (SAP enhancement RSAP0001)
Note 413807
Update methods/extract structures/XPRAs
i Update methods (V3 update, DeltaQueue, and so on).
Notes 380078, 396647, 486784 and 505700.
For information about the automatic conversion of update methods in the logistics extraction, refer to the release notes for plug-in 2003.1
DataSources for application 03 are delivered by default with the "Unserialized V3 Update" method.
A change to "Queued Delta" may occur.
For performance reasons, you should not select "Direct Delta".
ii Changes to extract structures/XPRAs
Notes 328181, 489259, 511657 and 566917.
If you try to add another field from the pool to the "2LIS_03_BF" DataSource , the system issues error message "D0 322".
Possible reason:
XPRA "RMCSBWXP_IM_01" did not run after you imported the plug-in. This XPRA is responsible for comparing customer fields in the extract structure (enhancement) with new default fields in the extract structure (SAP). This error message appears as a result.
b) Known errors
Stocks, movements and revaluations are transferred to BW using various extractors. All known errors and proposed solutions of these three extractors are listed below.
Stocks (2LIS_03_BX/2LIS_40_S278) -> see Note 691228.
i Rounding error/valuation at company code level
Notes 663681 and 762219
ii Project stocks
Note 535657
iii Valuated sales order stocks or project stocks
Notes 487043, 616119, 674351 and 756151
iv Vendor consignment stocks
Notes 585619 and 726485
v Special stocks for customers/vendors
Note 533682
vi Valuation class
Note 684789
vii Stock in transit
Notes 767786 and 898231
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
i Delta ability/procedure
Notes 385703 and 581778
ii Update methods (V3 update, delta queue, qRFC and so on)
Notes 339691, 444261, 498484 and 631562
iii Missing BW derivation (component,
transaction key, and so on)
Notes 315880 and 353042
Caution: You MUST read these notes
BEFORE you transfer data to the BW system.
iv Movements (2LIS_03_BF)
- Returnable packaging with customer
Notes 512597 and 530730
- Vendor consignment
Notes 585139 and 607710
- Project stocks
Note 522770
- Stock transfers
Notes 399929, 557378 and 628090 (stock in transit/
valuation type)
- Purchase orders with account assignment (consumptions)
Notes 587320 and 629726 (non-valuated materials,
see also Notes 752607 and 790506)
- Batches
Notes 445632 and 685450
- Incorrect stock type
Notes 438649 and 451355
- Customer consignment
Note 563342
- Incorrect / missing valuation class
Notes 735425, 747581 and 770858
- Returns (movement types 122/123)
Notes 741396 and 763424
- Profit center
Note 769660
- Subsequent adjustments
Note 822396
v Revaluations (2LIS_03_UM)
- Incorrect update because the
BSTAUS and BSTTYP fields are missing
Notes 494288 and 675610
- Missing BW derivation of characteristics with settlement ofrequests
Notes 523298 and 747361
- External display of the WBS element does not exist
Note 512611
- Incorrect transaction key during setup
Note 587241
- Incorrect sign
Note 587283
- Duplicate document for MR22
Note 587304
- Incorrect/missing document number
Notes 489290, 500825, 507958, 521046, 619482,
667534, 739050, 839711, 845307, 856669 and
864630
- The BUZEI field is not filled
Note 599731
- Currency field not filled
Note 612131
- Returns (movement types 122/123)
Note 715176
- Reconstruction report RMCBNERP
Note 735209
- Missing valuation class
Note 837052
vi Master data (0STOCKTYPE/0STOCKCAT)
Note 766954
- 0STOCKCAT_TEXT is not filled since the value 'U' has not been added to the BSTTYP domain.
Note 907195
Industry-specific notes
i IS Retail
- Revaluation at retail (2LIS_40_REVAL)
Notes 533577 and 600460
- Miscellaneous
Note 841878
ii IS Oil/IS Mine
- G/L quantity for two-step stock transfer procedure
Notes 608744, 608975 and 629320
4. Technical information regarding non-cumulative info cubes in BW
In addition to the relevant sections in the online documentation, there are a number of explanatory notes that will help you to analyze problems. Section 4 e) deals with known errors and proposed solutions.
a) Warehouse Management
Validity table: Notes 360249 and 534865
Selective deletion: Note 510680
Aggregates: Note 456359
ODS capability: Notes 322303, 323811, 385099, 417703, 581778,
747037, 752492/782314 and 773823
DataMart/Open Hub capability: Notes 375098, 566145 and 566762
Compression (updating the stock marker)
->>> ESSENTIAL INFORMATION <<<-
You can see in the log whether or not the stock marker was updated during the compression (as of 3.0B Support Package 13)
For example:
"START cond CUBE IC11 at 165446 on 20030514 maxreqid 23282 maxcnsid 0 refpoint update + null elim" ->
"refpoint update" or "no refpoint update" provides the relevant information.
See Notes 613701 and 639253 if you are using Oracle 9.
Also see Notes 643687 and 655798.
For a BW system with several application servers, see also Note 834829.
->>> ESSENTIAL INFORMATION <<<-
b) Queries
-> For information about the recommended procedure for analyzing query problems see the following note: Note 370004
Slow-moving item/slow seller reports: Note 541559
A How to document is also available:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: M ("MultiProviders") -> "MultiProviders (incl. Slow Moving Item Scenario) ..."
c) Update rules
The following special features are provided for updating in non-cumulative cubes:
The non-cumulative key figure has to be included with the relevant cumulative value(s) in the InfoCube definition.
Only receipt key figures are provided for updating from the InfoSource with the stocks.
The issue and receipt key figures are provided for updating from the InfoSource with movements.
Therefore, from a technical point of view, stocks are written to the receipt key figure. The process of differentiating between the stocks and the remaining receipts then takes place in the InfoCube using record type = 1 (InfoObject: 0RECORDTP) in the technical dimension table (this also sets up the connection to the validity table).
The OLAP processor dynamically calculates non-cumulative key figures in the query (taking into account the issues/receipts and the validity table).
d) Known errors
Warehouse Management
i Loading data
Notes 534865 and 529610
ii MultiCube/MultiProvider
Note 435227
iii Compression (updating the stock markers)
Notes 613064, 613701 and 615349
iv Updating
Note 574341
Queries
i Fiscal year variant characteristic (0FISCVARNT, 0FISCPER
and 0FISCYEAR)
Note 490067
ii Exception aggregations
Notes 145630 and 607608
iii No/multiple time restrictions
Note 388983
5. Stock Analyses in BW
This section explains the data flow in BW and provides an overview of known errors and their solutions. This section also explains certain limitations and workarounds for same.
a) Explanations on data flow
See the How to paper from Section 2 b)
"How to... Handle inventory management scenarios in SAP BW 3.x" (PDF).
Note that the 2LIS_03_UM can also be loaded before the 2LIS_03_BF.
You will find further information on the SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Business Content
-> SAP Supply Chain Management
-> Supply Chain Performance Management
-> In the navigation area on the left: Related Topics
-> Business Content
-> Inventory Management.
b) Known errors
0IC_C03
Notes 637927, 655798, 668085 and 710404
0IC_MC01
Note 664520
Queries
Notes 534429, 630034 and 676960
c) Tips and tricks
Analyses in BW with the storage location (0STOR_LOC) and stock characteristic (0STOCKTYPE) characteristics in the drilldown.
Solution: Note 589024 (see also Notes 201327, 322335, 456106, 506077 and 543188) and the How to document
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Realize summarized display of stock values on storage"
Stock transfers in the two-step stock transfer procedure/differences between analyses in BW and the R/3 transaction MB5B
If you notice different results for the issue and receipt quantities of the total stock during the analysis of stock transfers in the two-step procedure, for example, storage location to storage location within a plant (movement types 351 and 101), add the "0STOCKTYPE" characteristic to the drilldown. Where necessary, filter according to the values "A" (unrestricted) and "H" (transit). You will then find the same values under stock type "A" and in transaction MB5B (if you select the storage location stock or the valuated stock).
Individual analysis of revaluations
After stock is initialized using the 2LIS_03_BX InfoSource, load revaluations into the 0IC_C03 InfoCube with the 2LIS_03_UM InfoSource. By doing this, you avoid uploading movements with the 2LIS_03_BF InfoSource. If you do so, the non-cumulative values (quantities and values) can no longer be calculated. Reason: When you initialize stocks, DIM IDs are created for 0BASE_UOM and 0LOC_CURRCY. As a result, all stock markers for 0BASE_UOM have an entry other than ' '. With revaluations, only values are updated-all quantities and their units are updated with ' '. This means that you can no longer assign revaluations to the stock markers because the units of measure are inconsistent. Solution: Update the revaluations with quantities also, as you did for the values (the result for the quantities is always RESULT = 0).
Incorrect results if quantity key figures and value key figures are analyzed together.
For example, you only displayed quantity key figures in the current drilldown. If you now add value key figures, the quantity key figures are no longer calculated correctly (the reverse also applies). As in the case of individual analyses of revaluations, movements may not be assigned to the stock markers due to missing DIM IDs. As a result, stock cannot be recalculated correctly either. This should not usually occur when the 0IC_C03 InfoCube is filled with the 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM InfoSources (this is also the case with the other relevant Business Content InfoCubes, for example 0CP_IC_C1 or 0RT_C36/37). However, it may occur because of certain loading processes, for example. Solution: Update the quantities (or values) in the same way as the values (or quantities) (RESULT = 0 is always the result for the quantities or values). See Note 643291 for the 0CP_IC_C1 InfoCube.
Enhancing the 0IC_C03 InfoCube with additional characteristics
These additional characteristics must be updated from the 2LIS_03_BX InfoSource, as well as from the 2LIS_03_BF and 2LIS_03_UM InfoSources, only then can movements be assigned to stock markers (see the two preceding points).
The following enhancements are possible:
1. Valuation type (0VAL_TYPE)
Source field from 2LIS_03_BX/BF: BWTAR
2. Company code (0COMP_CODE)
Source field from 2LIS_03_BF/UM: BUKRS
3. Valuation area (0ID_VALAREA)
Source field from 2LIS_03_BX/BF/UM: BWKEY
4. Vendor (0VENDOR/0GN_VENDOR) - for vendor consignment stocks
Source field from 2LIS_03_BX/BF/UM: LIFNR
This is delivered with BI Content 3.3 Add-On (see SRM Business Content Online documentation).
5. Customer (0CUSTOMER) - for consignment stocks at customer
Source field from 2LIS_03_BX/BF/UM: KUNNR
6. Sales order (0DOC_NUMBER/0S_ORD_ITEM) - for sales order stocks
Source field from 2LIS_03_BX/BF: KDAUF/KDPOS
7. Project number (0WBS_ELEMT) - for project stocks
Source field from 2LIS_03_BX/BF: PS_PSP_PNR
8. Evaluation class (0VAL_CLASS)
Source field from 2LIS_03_BX/BF/UM: BKLAS (Note 684789)
Enhancement possibilities for 2LIS_03_BX:
Note that the 2LIS_03_BX DataSource cannot be extended in the same way as the 2LIS_03_BF DataSource, for example.
Only SAP can enhance this DataSource (Note 684789).
Other enhancements are no longer useful since fields, such as the movement type, G/L account or profit center do not in appear in the stock tables (for example, MARC and MARD) but only in the movement tables (for instance, MSEG).
Evaluation restrictions that occur as a result (similar to the two preceding points) can only be resolved by a data enhancement (for example, reading from a DataStore object with all material movements) subsequent to the extraction or by not using 2LIS_03_BX. In both cases, all material movements must exist in the source system. If this is not the case, you must read from the corresponding archive files for the extraction.
Changing the exception-aggregation of the stock key figures
There is a predefined exception aggregation for stock key figures (for example, "last value") in the key figure definition. If you want to override these in the query definition, proceed as follows:
-> Create a new calculated key figure.
-> Drag the relevant basic key figure to the formula area.
-> Choose "OK".
-> In the next window, choose "Extend >>".
-> Then, maintain the required exception aggregation and the reference characteristic.
Mapping FIFO logic
The data structures in the 0IC_C03 InfoCube allow FIFO logic to be mapped using the relevant query definitions. In this case, contact your SAP consultant.
Unexpected or negative stock values due to FI document summarization
If FI document summarization is activated for the MATNR field, revaluations (2LIS_03_UM) are transferred to BW without a material number. As a result, complete analyses are no longer possible at material number level. For more information, see Notes 36353 and 497992.
Options for the R/3 and BW data verification/consistency check
TAC MB5B <-> Queries 0IC_C03_Q???
(Stocks/movements R/3 <-> BW)
TACs MC.? <-> Queries 0IC_C03_Q???
(Inventory controlling LIS <-> BW)
Reports MBQUANT and RM07MMFI
(verification of the R/3 data)
Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
With Note 766622 you can also create a LOG file for the extraction.
Archiving
See the corresponding "How to" document about archiving that is available on SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: A ("Archiving")
MultiProvider and non-cumulative key figures
Note 690475
Displaying the contents of the InfoCube with TAC "LISTCUBE"
Note 629451
Snapshot scenario
The "How to" document mentioned in section 2 b) "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)" contains important information about the advantages and disadvantages of mapping stocks using a snapshot procedure.
Validity period of stocks
You can use transaction RSDV to determine the time period in which stocks can be calculated. This time period is determined automatically by the oldest and the most recent material movement. If you have a reporting requirement to display further stocks in the past, you can use the RSDG_CUBE_VALT_MODIFY report to manually change the time period.
Evaluations of cross-company code stock transfers.
Corresponding reports are currently not possible using the 2LIS_03_BX/BF/UM DataSources. For further information, see the following "How t"o document:
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Report on cross company stock in transit", which allows you to carry out evaluations in BW similar to the ones in R/3 transaction "MB5T".
0IC_C03 data modeling
Due to the different characteristic value calculation for stock quantities and values, a MultiCube scenario ("sparse tables") is useful in this case, one InfoCube for quantities and one for values.
You can then execute common stock quantities, values and evaluations using queries on a MultiCube.
The 0IC_C03 InfoCube currently uses a key figure model (various specific key figures, such as inspection stock, stock in transit and so on). In this case, an account model is suitable:
- Three key figures: Stock quantity, stock value and valuated stock quantity (including the movement key figures)
- Based on stock instance/type, you can then limit the query to the special stock
- Advantage: Uses less database space
- Disadvantage: The load for the OLAP processor is higher and there is more work during the query definition, the other approach may also be more transparent for the end user.
Inventory management and ODS
ODS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
In this connection, you should use the ODS technology only for:
- Document-related reporting or the Enterprise DataWarehouse layer based on the 2LIS_03_BX/BF/UM InfoSources (see Notes 581778 and 747037).
- The implementation of a snapshot scenario; see the How to document mentioned in section 2 b) for more information:
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Implement Note 773823 to be able to update the 2LIS_03_BX InfoSource to an ODS.
If you want to activate another ODS object for the 2LIS_03_BF and 2LIS_03_UM DataSources before the 0IC_C03 InfoCube, we recommend a parallel update.
However, if you want the InfoCube to be filled by a subsequent update from the ODS, take the following into account:
Documents that are entered after the stock initialization (CPUDT field > stock initialization key date) and are posted back to a period before the stock initialization (BUDAT field < stock initialization key date),
must be updated with a delta request in the InfoCube, because only these requests can be compressed with a stock marker update.
Therefore, mechanisms for which the movements are different before and after the stock initialization (as a result of restrictions on the posting date) are incorrect in this case. However, if you want to work with the requests in question, you must restrict the movements using the date of entry (CPUDT). Otherwise the stock evaluations will be incorrect due to the compression logic used.
The same problem occurs if documents are posted to the future (CPUDT field > stock initialization key date and BUDAT field > stock initialization key date).
Posting to a prior period and postings to the future
If you can post this type of material documents in the system, take note of the documents that caused the initialization run (transaction MCNB, or report RMCBINIT_BW)during the reconstruction in R/3 (transaction OLI1BW, or report RMCBNEUA):
1. BUDAT < stock initialization key date and CPUDT > stock initialization key date
You execute the report with a date restriction (for example, upper limit = key date of stock initialization) to avoid a posting block.
-> Postings to a prior period are selected by mistake.
-> Solution: You MUST set a posting lock (if this is not possible, it may help to select according to the document number).
2. BUDAT > stock initialization key date and CPUDT < stock initialization key date
Here the same applies as described under point 1, however, the documents are then missing in the setup table. You can still make restrictions according to the posting date but you must set a relatively high upper limit.
Consumption key figures in 0IC_C03 (the same as LIS reports)
See Note 804781.
Avoiding data inconsistencies, HASH solution.
See Note 838050 for more information.
Connection between transaction keys and reversals. See Note 352344 (and an example in Note 745788).
Suppressing the display of the previous period in the BEx Web Analyzer.
See Note 623944.
6. Performance
a) General BW/logistics extraction (TSV_TNEW_PAGE_ALLOC_FAILED/ SYSTEM_IMODE_TOO_LARGE)
Notes 409641, 417307, 419465, 548845 and 589997
b) Extraction 2LIS_03_BX
The recommended setting in the RMCBINIT_BW report for 'Number of data records per LUW' is 5000. Higher values may cause the following errors:
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
TSV_LIN_ALLOC_FAILED
You can reduce an extremely long runtime by setting up the stock individually for each plant. For more information, see Note 728360.
When you run the report, the "Transfer Zero Stocks" option must NOT be active, because this will significantly increase the runtime.
This is no longer required as of Note 823951 (for more information, see Note 655798).
c) Extraction 2LIS_03_UM
Notes 537235 and 585750
d) Extraction 2LIS_03_BF
Note 454267
e) Warehouse
Due to the stock marker generation technology, it is normal for the E table to be larger than the F table in the non-cumulative InfoCubes.
As a result of the different updating of stock quantities and values (see Note 589024) required by the R/3 data model, movement data usually generates two entries in the F table.
To reduce the data volume of the 0IC_C03 InfoCube, you can distribute quantity and value key figures to two InfoCubes. As a result, the key figures have the same characteristic value update again. You can then use MultiCubes to execute common evaluations of quantities and values.
f) Queries
Notes 419490 and 784682
Message was edited by:
Jr Roberto -
Negative postings to MVER table
Dear SAP guru's,
I am trying to simulatie the MVER table trough the MSEG material movements. I've accomplished 95% accuracy through the use of T156-KZVBU en MSEG-KZVBR fields. I'm still missing the posting of some material movement.
For example the following line:
MSEG-MENGE=500
MSEG-BWART=602
MSEG-SHKZG=S
MSEG-KZVBR=V
T156-SHKZG=S
T156-KZVBU=G
This has been posted as negative consumption (-500) in MVER. Although it is adding stock (S) this usually gets posted as positive consumption (like a 101 movement with KZVBR=V).
What am I missing? Which fields are used to further determine the consumption posting to MVER?
With kind regards,
Nanne SluisIf it helps somebody, I wrote a little tutorial, documenting my research (no guarantees on completeness; and feedback welcome):
How does MSEG-INSMK work, or better: How are the different stock types being updated in MARD/MARDH/MCHB/MCHBH/u2026
According to SAP note 368259, MSEG-INSMK cannot be used to determine which stock type fields in history tables are getting updated by the MSEG row. Hence, we investigated the approach on how stock type quantities are getting updated:
Required SAP tables:
- MSEG
- MKPF
- T156M
- T156F
Maybe required:
- T156SC
- T156SY
- T156W
- T156X
The following tables need to be considered and joined accordingly:
Example:
The following tables/fields need to be joined together to retrieve the information which history table fields of stock types are getting updated based on which material movement. Beware that multiple fields can get updated within one transaction; hence the joins can multiply rows. It makes sense to first create a table of T156M / T156F values and pivot it. Afterwards it can be used within the material movements flow:
1. Table MSEG (Document Segment: Material): Starting point
MSEG-BWART = 555 (GI scrapping blocked)
MSEG-SHKZG = H (Credit posting)
MSEG-SOBKZ = u2018u2019 (no special stock)
MSEG-BUSTM= u2019MS01u2019 (Posting string for quantities)
MSEG-ZUSTD_T156M= u2018u2019 (Stock Type Modification (Read from Table T156M))
2. Table T156M (Posting String: Quantity): Result after Join
T156M-BUSTM=u2019MS01u2019 (Posting string for quantities)
T156M-ZUSTD=u2019u2019 (Stock type modification)
T156M-CNT02=u201801u2018 (Consecutive counter in ATAB tables for inventory management)
T156M-SMARD=u2018LS1u2018 (Segment string) Updating table MARD
T156M-SMCHB=u2018CD1u2018 (Segment string) Updating table MCHB if batches are used
3. Table T156F (Fields in Quantity String): Result after Join
T156F-SEGST=u2018LS1u2018 (Segment string)
T156F-CNT02=u201801u2018 (Consecutive counter in ATAB tables for inventory management)
T156F-FELDV=u2019MARD-SPEMEu2018 shows the updated history table field
The following fields need to be joined, basically:
MSEG inner join T156M ON
MSEG.BUSTM=T156M.BUSTM
and MSEG.ZUSTD_T156M=T156M.ZUSTD
T156M inner join T156F ON
T156M.SMARD=T156F.SEGST
T156M.CNT02=T156F.CNT02
Additional Information:
MSEG-BUSTM (Posting string for quantities)
Key for the automatic determination of the stock fields that:
u2022 Have to be checked when a goods movement is entered (availability check)
u2022 Are updated following a goods movement.
T156M-ZUSTD (Stock type modification)
Serves to differentiate between quantity updates carried out for the various stock types. -
Where in the IMG or std system do you set the Period Indicator for the consumption posting table MVER?
Currently all movements are posting as Month. I need to change this to Period.I believe t-codes MM02 Forecasting and MM17 would be used to change the Forecasting period indicator in table MPOP, not the Consumption Usage period indicator in table MVER.
As soon as you perform a real time consumption movement such as peforming MB1A with movement type (GI Cost Center), the total and unplanned consumption are increamented by the transaction quantity immediately in table MVER. The results can be seen in the Material Master MM03 view (Additional Data/Consumption). When it updates the table is considers the period, which mine is currently M (Month). There should be some place I can change this to P (Period).
Thanks for your input
Maybe you are looking for
-
Invoices not showing up for clearing with F-32
Hi, For 2 customer accounts we have similar issues. Customer 1: FBL5N: 1 invoice and 1 payment received which perfectly match. F-32: only the payment is displayed, no trace of the invoice, unable to clear Customer 2: FBL5N: 4 invoices and 1 payment r
-
Why is music folder not recognized and what can I do to solve this problem?
I had to reformat my computers hard drive and re installed iTunes version 6. My songs were in iTunes 5 before the system crash and now that I have fully restored my computer, I cannot import my backup music folder into the iTunes library. I have over
-
Http server code 403 in SXMB_MONI
*Hello All,* *When I am posting an IDoc from R/3 to XI I get the following in SXMB_MONI in the Call Adapter.* <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> - <!-- Call Adapter --> - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/3
-
Hi Apologies for the first post as I had an itchy trigger finger ;-) The following link is broken which can be navigated to from the OTN Jdeveloper Online Demonstations page. In fact, all the links in the J2ME section do not work. Please can you fix
-
Workflow Cancellation Notifications - Prevent without changing global sett
I am wondering if anyone has been able to prevent cancellation notifications from being sent to users for a specific workflow. There is a global profile setting but I can't use that as other workflows require the cancellation notification. I was thin