T.code CK55 Node is missing in std SAP tree

Hi,
T.code CK55 used for multiple sales order costing, it is available in sap command filed but it is missing in sap standard Tree node
could u help us.
some of components we are not activated how to find such component
Regards
Vinu

SAP Easy access
SAP menu
Logistics
Materials Management
Foreign Trade/Customs
General Foreign Trade Processing
Environment
Sales - Export
Sales
Product Cost by Sales Order
Cost Estimate
CK55 - Mass Costing - Sales Documents
Usually you can find and transaction code/text by Find Icon (Ctrl+F)
Srinivas
Edited by: Srinivasa Maruvada on Nov 24, 2011 11:29 AM

Similar Messages

URGENT:LWF Node is missing: Function INUCD adition to INN1?

Dear Experts,
We have applied Support packages : BASIS - SAPKB62062 and
SAPKB62063
ABAP - SAPKA62062 and SAPKA62063
HR - SAPKE47045 to SAPKE47074
Now in spro LWF node is missing and system is showing an run time error.
I have gone through the SAP note 973398 and done the initial IMG
changes as per note but i couldn't able to do changes in Schema INN1 .
as per note it says:
"Schema changes:
In the standard payroll schema, the payroll
function INLWF is no longer used at sub schema INN1 to compute the LWF
contribution. Instead now payroll function INUCD is called with
appropriate parameters. The schema in all the clients should be
adjusted accordingly."
I tried to change existing INLWF with INUCD but system is asking for
parameter is required, can any one tell me how i can maintain the
parameter.
Thanks and Regards,
R.B.Paramshetty __.____._

Hi,
First find out the relevant Function Module from WE57 tcode.
After getting the FM , u see the sorce code mentionjed in the FM which will fill the relevant Segmnets.
Also check the code whtehr it fill the mandatory segment YMMSMBEW.
Mostly this logic is missing in that FM.
Rvert back if any issues,
Regards,
Naveen

Code interface node - .lsb generated but does not load

Howdy,
i am using labview 6.1 and VC++/visual studio .NET 2003.
i tried creating a simple code interface node to add two numbers. i followed the steps given in the "Using External Code in Labview" Manual. I made only one change, which is switching out "$(WkspDir)\$(OutDir)" (under custom build) with "$(ProjectDir)$(OutDir)" as the $(WkspDir) macro is missing from VC++.
The build occurs successfully and i get a .lsb file. But when i ask the code interface node to load it up, it doesn't. The error description is, "Code Interface Node: object code not loaded."
any suggestions? thanks in advance.

Hi,
This KB describes what may be the issue. I hope this is helpful.
Regards,
Ankita

Obligatory node 'E1OILKV' missing, Not getting'12'Status fromR/3 to XI Port

Hi,
I am sending the Customer Master Data from R/3 to XI. I enhanced the Idoctype OILDEB06 to ZOILDEB06. I am getting the message code status as 03. "Data sent to the Port". But if i execute the the Report RBDMOIND. It is not moving to status 12. "Despatch Ok".
I Got the error message in the tRFC as "Obligatory node 'E1OILKV' missing in the structure".
I am able to see the structure E1OILKV in the IDoc with data. But why this error is coming.
Could any one can help on this Issue.
Thanks and Regards,
Venkat.

The Idoc is going to the Recieving End only till the General View and Company Code view. E1OILKV Segment comes under the Sales View. Since Sales view is not changed it is not capturing the Change Pointers. If Sales view is avilable in the Idoc it is not going to the XI Port. tRFC gives the error.
We checked for other Idocs Which were enhanced. Those other IDocs{example Cost center,Vendor Idocs} are going.
I tried to send the Standard Idoc OILDEB without the Enhancements. It is going to the XI Port. Once i Send the OILDEB06 With Enhancements. It gives that error.Obligatory node 'E1OILKV' missing in the structure. As i already said, I am able to see Data in this segment using the Idoc editor. But not fully moved to the Configured XI Port.
Thanks,
Venkat.

T code for Material,plant, stock and price data in std sap

Dear All,
In Std SAP is der any t-code to get Material,plant, stock and price data in 1 go..
waiting for ur early reply
Regards
Nainesh

Hi,
Try T.Code: MC.9 and MC.5 etc. These reports will give you total value of the stock but not unit price.
If you are looking at unit price please write a small query using SQVI or append the relevant info structure.
Regards
Srinivas.P

Do we have std SAP Reports for? 1. 4/5 Challan 2. PO & Tax Code?

Hi Friends,
Do we have std SAP Reports for.... if y what are tcodes?
1.Report for Rule 4(5) a transactions - Tracking of challans issued and closure within stipulated period
2. Report for Purchase orders raised with the tax code assignment for checking whether proper tax codes is selected.
Thanks and Rgds,
Navin

Hi,
1.Report for Rule 4(5) a transactions - Tracking of challans issued and closure within stipulated period
Ans: - J1IFR
2. Report for Purchase orders raised with the tax code assignment for checking whether proper tax codes is selected.
Ans: - J1I2

Error: Obligatory node 'E1MAKTM' missing in the structure

Hello All
   I extended material master IDOC.
After extending, the segments look like this:
ZMATMAS05
     - E1MARAM
            - ZEXTENDED_SEGMENT
            - E1MARA1
            - E1MAKTM
            - E1MARCM
so on and so forth.
When I create idocs, I get a message saying that the message is successfully sent. When I see in SM58, I see the message "Obligatory node 'E1MAKTM' missing in the structure".
The idoc which is created has E1MAKTM segment, but it is still giving the error.   Am I extending at the wrong position?
Thanks
Naga

looking at this
ZMATMAS05
- E1MARAM
- ZEXTENDED_SEGMENT
- E1MARA1
- E1MAKTM
- E1MARCM
makes me just feel that all your segments are at the same level.
but usually the E1MAKTM is a sublevel to E1MARAM
so it should look like this:
ZMATMAS05
- E1MARAM
- -ZEXTENDED_SEGMENT
- -E1MARA1
- -E1MAKTM
- -E1MARCM
- - -E1MARDM

Win32 API calling by Code Interface Node

Hi all,
I wish to call a Win32 API function by using the code interface node.
However, I don't know the data types in LabVIEW corresponding to the "HANDLE
*" in Visual C++.
Here's the function I wish to call:
BOOL bOpenDriver (HANDLE * phDeviceHandle, PCHAR devname) {
*phDeviceHandle = CreateFile(devname,
GENERIC_WRITE,
FILE_SHARE_WRITE,
NULL,
OPEN_EXISTING,
0,
NULL);
if (*phDeviceHandle == INVALID_HANDLE_VALUE) {
return (FALSE);
} else {
return (TRUE);
Thank you in advance.
JJ

If this is really a Windows API function, then the handle can most likely be treated as an I32.
Note that you can't actually do anything with the handle other than passing it to other functions.
If you search this site for "LabVIEW" and "DLL" you should find some resources about working with DLLs and Win32 API DLLs.
Try to take over the world!

Code Interface Nodes and multithreading (openMP)

Hi,
We are experiencing a rather strange problem with the use of Code Interface Nodes (CIN) in LabView. The CINs are built with the Intel Compiler in the Visual Studio .NET 2003 IDE and use the openMP directives to easily implement multithreading. This does not seem to give any problems, as long as we do not declare our code threadsafe. If the code is declared threadsafe, everything runs smoothly but LabView crashes when the VI where the CIN is located is closed. If we do not declare the code threadsafe, there is no problem but our user interface is blocked during execution of the CIN. Since we are building an application for other users this is not acceptable.
It clearly has to do with the multithreading, because forcing the compiler to create sequential code solves the problem. But off course we don't want to implement multithreading to disable it afterwards.
We could switch to DLLs, but we are building an exe version which is under full development and can be updated by our users through the internet. Since CINs are part of the exe file itself and DLLs are not, we would like to keep it this way.
We know this is a very specific problem, but we do not know if the problem is related to the multithreading in general or to the use of openMP in particular. Has anyone else tried multithreaded CINs and experienced any problems ? We basically just want to be able to stop the CIN from using our user interface, since we know everything is threadsafe.Message Edited by Raistlin on 05-07-2005 07:34 AM

I have tried putting the vi in another execution system (standerd,other 1,other 2, ...) and the problem persists. I now built a DLL and have the same problem : marking it as reentrant makes the vi crash at closure, marking it as running in the UI does not give a problem. I now sent some code to Intel to check the thread safety, but I am quite certain there is no problem there.
I found another thread where the problem was mentioned but also without an answer that could get me any further :
http://forums.ni.com/ni/board/message?board.id=170&message.id=47264&requireLogin=FalseMessage Edited by Raistlin on 05-10-2005 02:04 AM

Using code interface node with dll crashes LV 2011 but not LV 8.6... using max error handling does nothing

Hi all,
I'm having a peculiar problem.
I inherited a project saved in LabVIEW 8.6. The project must use of particular dll that was built a few years ago. The original developer and source code for this .dll are long gone. The very core logic exists, in the form of embedded C code, and that's it. The .dll is called through a Code Interface Node in LV 8.6 and this setup manages to "work". Howver, running the VI that calls this .dll in LV 2011 causes an "insta crash", as in, no "program has stopped responding". Error message pops up, then all LV windows close.
It's very similar to that described in here:
http://digital.ni.com/public.nsf/allkb/D84C9775ABD921CF8625772A005CA50C
but this KB says to try putting the amount of error handling to maximum. I tried that, but it didn't help.
Using the "Debug" option allows me to run the just-in-time debugger with CVI 2010, which then proceeds to say this:
Finally, I manage to get this out of it:
FATAL RUN-TIME ERROR: Unknown source position, thread id 0x000012D4: A non-debuggable thread caused a 'General Protection' fault at address 0x00000000.
I don't think that really helps at all, but it's there.
Here is the function prototype of the .dll:
void _inputPM@224(uint8_t arg1, uint16_t arg2, uint8_t arg3, float arg4, float arg5, float arg6, float arg7, float arg8, float arg9, float arg10, float arg11, float arg12, float arg13, float arg14, float arg15, float arg16, float arg17, uint16_t arg18, uint16_t arg19, uint16_t arg20, uint16_t arg21, uint16_t arg22, uint16_t arg23, uint16_t arg24, uint16_t arg25, uint16_t arg26, float arg27, float arg28, float arg29, float arg30, float arg31, float arg32, float arg33, float arg34, float arg35, float arg36, float arg37, float arg38, float arg39, float arg40, float arg41, float arg42, float arg43, float arg44, float arg45, float arg46, float arg47, uint16_t arg48, uint16_t arg49, uint16_t arg50, uint16_t arg51, uint16_t arg52, float arg53, float arg54, float arg55, float arg56);
(never seen a function take 50 input params like that (wouldn't you use a struct? array? something? But I digress, and I don't know anything about .dlls...))
I do have a ".lib" and a ".cdb" file with the same name as the .dll, but those also looks like some kind of compiled file.
I'm sure the answer I'm going to get is that there is no way of telling what's really going on without .dll source code. I'm hoping against hope that there may be another way or hack.
Any ideas? Thank you for you help.
Regards,
Mark G
Solved!
Go to Solution.

MarkCG wrote:
Changing the call library node to stdcall (WINAPI) did the trick! No more crash. Thank you very much!
I haven't run LV2011 on windows XP, only on windows 7, so I don't know if that makes a dfference. But The call type makes no difference when using LV 8.6 on the same machine, however.
Now I've got to make the .DLL run corretly on a compact fieldpoint.... and avoid crashing IT.
Thank you for the help all!
Well, the DLL did work fine in LabVIEW 8.6 because earlier versions of LabVIEW automatically proceeded to change the calling convention to stdcall, if they noticed a function name decoration of @# (# = number of bytes passed on the stack) appended to the name. This is the default naming decoration for stdcall functions used by VisualC. However this decoration can be overwritten with linker switches, other compilers don't use them always in the same way, and most likely there are in the mean time compilers out there that can produce such decorations also for non stdcall calling convention. So this automagic trickery was removed from newer LabVIEW versions.
I do think it could be considered a bug in the code that upgrades LabVIEW VIs, that it uses the calling convention that is configuerd in the dialog, instead of the calling convention earlier LabVIEW versions used automagically, but it is an esoteric corner case.
What Compact Fieldpoint controller do you have? If it's anything newer than 20xx or 21xx forget it. The 22xx controllers use a PPC CPU and VxWorks operating system and can never get a Windows DLL to operate properly. If it is a 20xx controller it's still highly likely that DLL can not even get loaded into LabVIEW as it likely relies on other runtime libraries and possibly Win32 APIs not present in the Pharlap ETS runtime kernel used on those controllers.
There is a tool to check a DLL for incompatible imports that are not present on specific ETS RT systems. And this list summarizes the RT system used on the various NI controllers.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Please teach me how to make the arrangement using Code Interface Node.

How is what is necessary just to make arrangement (for example, Sine?Wave)
using Code Interface Node? Please teach me a way.

Try to get hold of the 'Advanced Analyis' library for labview. It contains VIs for doing FFT! No need to reinvent the wheel.
If you can't get it and want to take the hard way, try to learn CIN programming by
- reading the manual (no joke or cynism intended)
- look for advice in NI's developer zone (www.ni.com/devzone) by using the search phrase 'CIN tutorial': you'll get several links which should be helpful in your case.
- better than a CIN: try to use the DLL calling mechanisms and compile your C code into a dll. In order to learn dll intewrfacing for LabVIEW, follow the route explained under point 1 and 2 above...
Good luck,
Franz

Obligatory node 'E1KONP' missing in the structure

Hi Experts,
I am extending cond_a04 idoc. am adding the custom segment as the child segment of E1KONH. Am populating the custom fields of this segment in an enhancement in LVKOEF01. This segment is populating and the idoc is successful but its not reaching PI side. In SM58 it shows status text as "Obligatory node 'E1KONP' missing in the structure" and the function module it shows in SM58 is "IDOC_INBOUND_ASYNCHRONOUS". Am confused. When sent without this extended segment its reaching PI side. What might be the problem??

hi
they have imported and updated the idoc definition.
Problem solved.
Need to check the structure in IDX. structure in IDX was wrong. when changed this it is reaching PI.Thanks.
Regards
Sridevi S
Edited by: Sridevi Sivanandam on Aug 5, 2010 2:59 PM

Obligatory node 'ZMAT_SPO' missing in the structure IDOC

Hello,
Scenario is : File - IDOC
I am trying to post the contents of the file into Matmas
The file gets picked and shows up a red color flag with the error : :Obligatory node 'ZMAT_SPO' missing in the structure Matmas04 Matmas04 "
I tried by disabling segment ZMAT_SPO, tried mapping to a constant.
nothing worked
When I copy the payload from moni, and do test in MM, its successful
What could be the problem?
thanks
nikhil.
Edited by: nikhil a on Jan 21, 2008 9:52 AM

Here is the error message:

<Trace level="1" type="T">Message-GUID = 8F7E3AA0C7FD11DC9E5600132165C741</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0000</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
I disabled that field in the course of MM in IR
do I need to reimport when i do this? i dont think so .....
nikhil

Please guide me:LWF NODE IS MISSING

Dear Experts,
We have applied new Support packages : BASIS - SAPKB62062 and
SAPKB62063 ABAP - SAPKA62062 and SAPKA62063
HR - SAPKE47045 to SAPKE47074
But in spro LWF (Labour Welfare Fund ) node was missing and system was
showing an run time error.
I have gone through the SAP note 973398 and done IMG changes in Tables
: V_7In0p_all, V_t7INU1, V_T7INU3 and (V_T7INU5)
BASE WAGE TYPE:Created base wage type by copying /140
SM30:
table V_512W_D maintained the processing class 20 with specification
3 for wage type basis and checked the cumulation class 40.
PE51:
I have edited the HR form and transferred the wage type
Schema Changes:
I have made changes to Schema IN00> INN1 we have delimited the old
LWF funaction INLWF and incerted new function as per sap note as
INUCD -
here i have maintained the parameter LWF, basis wagetype , -- and
01 (Universal grouping).
PCR Change : Sytem was throughing an error saying that "STOP: No rule
in key INCS******".
I have copied INCS and created ZNCS incerted basis wagetype init.
now while running payroll error is not there,
but wage type is not appearing either in RT table or in payslip,
has any one come across LWF missing , what are the steps you have followed.
I am missing something.
Please guide me.
Thanks in advance
Paramshetty.

hiii,
Please find the screeshot.Differeniace is coming in the tax on totl income as after calculaton it should be arnd 19k,Please help.
I hope screenshots are clear to you.
Thanks

CIN (Code interface node) LabVIEW runtime engine dependency

Hello:
Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
However if I create a dll from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
Thank You!

GE Osmonics wrote:
Hello:
What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded).
What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll to effectively do what the old CIN accomplished
provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
Thanks for the input
If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

T.code CK55 Node is missing in std SAP tree

Similar Messages

Maybe you are looking for