Characteristic Derivation in Profitability Analysis
Dear Experts,
I am finding it bit difficult to understand the concept fully when it comes to the Characteristic Derivation in Profitability Analysis.
I had gone through the various SAP explanations of MOVE, LOOK UP, ENHANCEMENT, DERIVATION RULEu2026. And now I am having rough understanding of all of it. But I am finding it difficult to understand on how these various steps or rule impact the COPA output. In other words if someone can explain the usage of all the MOVE, LOOK UP, ENHANCEMENT, DERIVATION RULE steps with an example?
Thanks in advance
Paul
Hello Paul,
Its purely clients decision/requirements which determine whether derivation is required or not. But in all COPA implemenation you need at least couple of derivations.
I will explain a simple scenario for Table Look up. Suppose you are settling production orders linked to a sales order ( Make to order scenario).
When the production order settles variances to COPA, system will not transfer Customer ( sold to party) characteristics.
But you can tweak the system through a small derivation rule to bring the customer from sales order and pass it to COPA when production order is settled.
For table look up first you have to identify the table, here our reference is sales order (VBAP-VBELN) and the required field is sold to party (VBAP-KUNNR), both are in VBAK
In the source field for table look up
VBAP- VBELN = CO-PA- KAUFN ( means if sales order number from VBAP table is same as the COPA sales order number)
VBAK-KUNNR= CO-PA-KDNR ( then pull the customer number associated with that sales order and populate the COPA customer field)
Please carefully go through SAP help for derivation, it is clearly explained with simple examples
http://help.sap.com/saphelp_46c/helpdata/en/7a/4c37ef4a0111d1894c0000e829fbbd/frameset.htm
thanks
SAP FREAK
Similar Messages
-
Incorrect material group derivation for Profitability Analysis doucment
Hi Gurus,
I found out some of the Profitability Analysis doucment generated with wrong material group assigned. Material group was derived from Product number, in my case it is defined as "table lookup" step type as below.
Source fields for table lookup:
MARA-MATNR = COPA-ARTNR
Assignement of Table fields to target fields:
MARA-MATKL = COPA-MATKL
Any idea of why this could be happen? Will it be due to my program error?
Pls advise asap.
Thanks & regards,
LOIcheck KEQ3. maybe it is defined as "not used"
-
Error in characteristic derivation at the level of the invoice item when re
We are implementing the SAP project for just one small private medical Center which includes mainly outpatient cases in different medical Clinics (different departments in the same medical center) .For example: Radiology center/department, cardiology center Obstetrics center and so on.
We have defined each center/department as a different profit center.
Some of departments are subdivided to several medical organizational units; each unit represents a different cost center at the same profit center/department.
A case-based order (internal CO orders relating to a patientu2019s case) is created in the background when the patient is admitted
The same patient can get services from few organizational units (in ISH)/cost centers at the same visit/case and that's why it is important to collect revenue and costs at the same case based order. The revenue is posted to the case base order by using billing in the ISH module and the costs by internal activity allocation.
We have assigned IS-H services to activity types in Controlling; the services transfer to the case based order. CO-relevant services are posted from IS-H to cost centers in CO and within internal activity allocation, allocate them to the case-based order.
For example:
X ray service assigned to Technician minutes activity type.
Each X Ray service takes 20 minutes of Technician (Qty Cnv Facto=20 MIN)
The service transfer is preformed automatically at final billing.
We have implemented Case Costing Level 2 in order to analyze case costs in CO-PA.
We want to have the ability to derive the profitability analysis characteristics at the level of a line item in the case, for example: we want to define a service or the preformed organizational unit as a characteristic in PA.
We are not sure what the best feasible solution for this requirement is.
We investigated few alternatives:
1. We have defined the case based order as real order with a settlement rule to a profitability segment. Revenue and Costs are posted to the cased based order and then settled to the profitability analysis. We eliminated this alternative because we didn't find any way to distribute revenue and case costs to PA between the different "line item characteristics" (for example: different services in the case).
2. After eliminating the first alternative we tried to change the solution.
We have dealt with revenue and costs separately.
1. Revenue: In the "configure revenue accounting" We flagged the Post to Prof.Segment checkbox, the patient billing module attempts to determine a profitability segment in CO for each invoice item and to post the revenue to it. The system determines the profitability segment using the characteristics of the patient and case data we defined.
We are using ISH_CHARACTERISTIC_* functions for characteristic derivation but we couldn't derive user defined characteristics which are defined at the level of the invoice item. (For example: billable service in the case or preformed organizational unit for each service.).We didn't succeed to it by using the ISH_CHARACTERISTIC_* functions.
2. Costs:
We tried to posts case costs (internal activity allocation) directly to profitability analysis, this way we hope to have the ability to derive characteristic of the line item.
We know that when we use transaction: KB21N for internal activity allocation and we define two receivers, internal order and profitability segment- In case the order will be statistical the true posting will be to profitability analysis segment.
Therefore we have defined the case based order as statistical order.
We want to intervene in the automatic creation of account assignment lines by enhancement NHCO0001 IS-H: Create account asgmt. line during CO transfer.
The transfer program creates for CO-relevant services account assignment lines for Assignment rules.
But-We didn't find any way to do it, because the profitability segment object is missing in enhancement NHCO0001.
As an alternative we tried to use User-Exit in the profitability analysis valuation (transaction: ke4u) but also with no success. (Enhancement COPA0002).
Could you Please advice what to do,I didn't succeed in my ideas and investigations.
Thanks
Yael Jacobi
Controlling ConsultantHI Claudius
Thanks for your answer, I will try to discuss it again with my customer to understand weather he really needs/wants a profitability analysis on service level.
I processed also an inquiry within the Service Remote Consulting according , I will let you know their answer as well.
I have additional issue to discuss with you , please let me know wheatear you can help me.
There are internal service sales between different departments in the same medical center. For example: Radiology center/department sells X-rays services for the cardiology center. We need the ability to sell a service to a different department in a different price than to an external payer/customer/insurance provider.
Is it possible to implement profit center transfer prices along with the ISH_CO integration?,
How is it getting along with the posting of internal activity allocation when services transfer to Controlling?
At standard the costs are allocated (by means of internal activity allocation) between profit centers. The responsible cost center (assigned to the performing organization unit) is credited and the case based order (which is assigned to different profit center) is debited.
Is it possible to implement transfer prices in case the performing organizational units are connected to the same profit center? (because some of departments are subdivided to several medical organizational units; and each unit represents a different cost center at the same profit center/department).
Do you recommend defining a different profit center also for each sub-department?
Do you have any other proposed solution for this issue?.
Thanks,
Yael -
Characteristic and value field in profitability analysis document
hi,
1 in VF03, when i click the accounting button, i got the profitability analysis document.
when i click on it, it shows display line items with tabs like characteristic and value fields.
may i know where i can see the characteristic and value fields defined where each time when i click on profitability analysis document, i get the list of characteristic and value field.
2 also if open FB03, can see the profit segment. the characteristic and value defined in where?
any tcode or spro that can show how the characteristic and value defined in profit segment.
thanksHi
Pleaase go through the below mentioned links. It will give you a better insight on the topic you want information about.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c38334a0111d1894c0000e829fbbd/content.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c388e4a0111d1894c0000e829fbbd/content.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c389b4a0111d1894c0000e829fbbd/content.htm
Hope this helps. Let me know if you have any questions.
Karthik -
Customizing Monitor in Profitability Analysis
Hello SAP-team!
What functions are provided by the Customizing Monitor in Profitability Analysis?
ps: thanks to SAP-community!
EugeneHi,
Customizing monitor in Profitability analysis as follows..
General topics:
35288 Technical Documentation CO-PA
69384 Account-based Profitability Analysis
199467 New act assignment table as of Release 4.5
2. Master data:
a) Characteristics and value fields:
13377 Naming conflicts in characteristics and value fields
21207 Deleting a charctrstc/value field from an op.concern
40336 Maintaining foreign keys for characteristics
76493 Changing texts of characteristics or value fields
b) Characteristics derivation and submission of characteristics values
32719 Customer hierarchy in CO-PA
33968 SD/CO-PA: Characteristics from sales document tables
36557 SD/CO-PA: Transfer partner functions to CO-PA
62690 Product hierarchy in CO-PA
93652 Info: Variant configuration in CO-PA
134889 Info on derv. of char:Why not all flds avail.?
148609 Char.deriv.:deriv. rule vals miss.aft.upgrade&trnsp.
172740 Techn.docum.charct. derivtn as of Release 4.0
c) Valuation
40408 Valuation for record types 'B' and 'C'
62536 Valuation using conditions in Profitability Analysis
67240 Info: Valuation with material cost estimate
111232 INFO: Valuation for materials valuated separately
144337 INFO rounding differences: Valuation with costing
142628 Behaviour of user exit in periodic valuation
3. Actual data transfer:
20254 Values from SD are not transferred to CO-PA
37114 Incorrect setup/reversal of provisions
33178 +/- sign logic in CO-PA (SD/FI interface)
52849 Transfer of conditions with +/- signs
39635 Profitability segment by substitution exits
64768 FI/CO-PA: Problems with exchange rate differences
87704 Cost-of-goods-sold Reconciliation: FI to Co-PA
83702 Acct assignmt logic sales order proc. - REM
111309 Transfer of quantities into CO-PA
185826 Enhancement COPA0005
a) Correction of data inconsistencies
69370 Clearing data inconsistencies in CO-PA
70718 Correctn of data inconsistency for order recpt
140457 Correcting data inconsstncs in incoming orders
126937 Correction of billing data inconsistency
93051 Restructure of the segment level from line items
4. Planning:
67191 Useful tips on the CO Planning Processor
72110 KE11: Long runtimes/timeout
77476 Information: Top-down planning
124598 CO-PA Planning: FAQs
5. Information system:
21773 Performance in reporting (summarization data)
83204 Usage strategy for summarization levels
136216 Fast rollup for summ. levels for costing-based CO-PA
6. Tools:
134430 Euro conversion and CO-PA
19015 Termination during external data transfer
19410 Characteristic validation during external data transfer
44658 Error with batch input for KE21
40994 Transport Profitability Analysis (CO-PA) to 3.0
52636 CO-PA Customizing transport
128862 Transport Customizing CO-PA in 4.0A/B
131664 Transport of operating concern structures 4.0
144015 Client copy and CO-PA/EC-EIS
65999 Information: Supported ALE scenarios in CO-PA
94458 CO-PA Realignments: documentation
113050 Segment table repair after realignments
127334 Missing archiving of profitability segments
199959 Change assignmt for operating concern
67839 Generating parts of an operating concern environment
69829 Delete operating concern in Release 3.0
106314 Delete operating concern in Release 3.1
562043 - Transfer actual costs to Profitability Analysis
544241 - INFO:Customizing Monitor new fnc 'Report Overview'.
429517 - INFO: Currency translation Billing document -> CO-PA
428563 - Material cost estimate valuatn: Translaton for posting date
400237 - CO-PA INFORMATION: Line item in company code currency
199959 - Information: change assignmt for operating concern
199467 - Info: New act assignment table as of Release 4.5
185826 - Information: Enhancement COPA0005
172740 - Info.:Techn.docum.charct.derivtn as of Release 4.0
148609 - Char.deriv.:deriv.rule vals miss.aft.upgrade&trnsp.
144337 - INFO rounding differences: valuation with costing
144015 - CC-INFO: client copy and CO-PA/EC-EIS
142628 - Behaviour of user exit in periodic valuation
140457 - Info:Correcting data inconsstncs in incoming orders
136216 - Fast rollup for summ.levels for costing-based CO-PA
134889 - CO-PA Info on derv.of char:Why not all flds avail.?
134430 - Information: Euro conversion and CO-PA
131664 - INFO: Transport of operating concern structures 4.0
128862 - INFO: Transport Customizing CO-PA in 4.0A/B
127334 - Missing archiving of profitability segments
126937 - INFO: Correction of billing data inconsistency
124598 - Info: CO-PA planning: frequently asked questions
113050 - Segment table repair after realignments
111309 - INFO: Transfer of quantities into CO-PA
111232 - INFO: Valuation for materials valuated separately
106314 - Delete operating concern in Release 3.1
94458 - CO-PA Realignments: documentation
93652 - Info: Variant configuration in CO-PA
93051 - Restructuring the segment level from line items
83702 - INFO: Acct assignmt logic sales order proc. - REM
83204 - Usage strategy for summarization levels
77476 - Information: top-down planning
76493 - Changing texts of characteristics or value fields
75334 - INFO:Downloading CO-PA correctn package fm SAPSERV
72110 - KE11: Long processing times / timeout
70718 - INFO:Correctn of data inconsistency for order recpt
69829 - Delete operating concern in Release 3.0
69384 - Information: Account-based Profitability Analysis
69370 - INFO: Clearing data inconsistencies in CO-PA
67839 - Generating parts of an operating concern environment
67240 - Info: valuation with material cost estimate
67191 - Info: Useful tips on the CO Planning Processor
65999 - Information: Supported ALE scenarios in CO-PA
64768 - FI/CO-PA: Problems with exchange rate differences
62690 - Info: product hierarchy in CO-PA
62536 - Info: Conditions in Profitability Analysis
52849 - INFO: Transfer of conditions with +/- signs
52636 - INFO: CO-PA Customizing transport
44658 - Error with batch input for KE21
40994 - INFO:Transprt Profitability Analysis (CO-PA) to 3.0
40408 - Info: Valuation for record types "B" and "C"
40336 - Info: maintaining foreign keys for characteristics
39635 - Info: finding the profitability segment using a substitution
37114 - Incorrect setup/reversal of provisions
36557 - Info SD/CO-PA:transfer partner functions to CO-PA
35288 - Profitability Analysis: Technical Documentation
33968 - SD/CO-PA: Characteristics from sales doc tables
33178 - INFO: +/- sign logic in CO-PA (SD/FI interface)
32719 - INFO: Customer hierarchy in CO-PA
21773 - Performance in Reporting (Summarization data)
21207 - Deleting a charctrstc/value field from an op.concern
20254 - INFO: Values from SD not transferred to CO-PA
19410 - INFO: Char.validity check f.external data transfer
19015 - Termination during external data transfer
13377 - INFO: Naming conflicts in charactrst. & value flds.
Thanks
Prasada -
50 Fixed CO-PA Profitability Analysis Elements
We are in the blueprint stage of a new SAP implementation using the Life Sciences express solution. Our consultants advised us that there are 50 SAP fixed characteristics in CO-PA for Profitablity Analysis and we have the ability to add up to 50 non-fixed characteristics. The list of the 50 fixed characteristics that our consulting team provided to us appeared very strange. Many of them appear to related to the airline industry. For example:
KMATYP - Aircraft type
KMDEST - Desitnation
KMFLTN - Flight number
KMFLTY - Flight type
KMIATA - IATA season
KMOPDY - Day of operation
KMORIG - Departure location
KMLEGS - Route segment
After questioning the provided list, we have been assured that we have been provided is the correct list of 50 fixed characteristics for all SAP implementations. We are looking for validation that these value are indeed part of the correct list. If not, we would greatly appreciate receiving the correct full list.
Thank you,
CarrieHi Carrie,
I vaguely remember that CO-PA (Profitability Analysis) module was initially developed/used for Airline industry to analyze the contribution margins. I'm not 100% sure on this, think i read it somewhere. SAP has provided these characteristics and derivation rules (logic to derive the characteristic for a transaction) by default. In my experience, i have always seen clients using at least 10-20 custom fields in CO-PA, since these are client specific we need to create additional derivation rules (either table lookup/Move/Derivation rules/Enhancements). Fields from Material master and customer master tables are commonly used for analysis in CO-PA.
Best Regards,
Venkata Ganesh Perumalla -
Hi,
We have a scenario wherein we create shipment cost documents against delivery. As a result of shipments fully transferred, a PO for freight vendor is automatically created and a service entry sheet confirmation happens. As a result of service entry sheet confirmation, we have Financial accounting, Controlling and profitability analysis documents created. We have a requirement wherein we need to have the characteristic “sales order number (KAUFN)” populated in the profitability analysis document created as a result of service entry sheet confirmation.
Could someone please advice how could this be attained in COPA. Thanks for your help in advance.
Regards,
SandeepHi Ajay,
Thank you for the quick update.
The document is updated to COPA through OKB9 settings. The profitability segment is updated with fields like customer, product, company code, plant, sales area data, profit center, etc; however the sales order number is missing.
Could you please elaborate further how could FI substitution be implemented to call for the FM COPA_PROFITABILITY_SEGMENT through user exit? Are you recommending the substitution through GGB1? What could be the possible validation to call for the user exit to be implemented?
Regards,
Sandeep Kulkarni -
Error in Derivation and Profitability Segment
Hello Gurus,
I am two issues, which isnt allowing me to create a sales order in IDES.
I am referencing a quotation when i want to create the sales order. But i got a warning message 'error in derivation rule' and the log text has
Error occurred in derivation rule. See long text
Message no. K/ 111
CO-PA Characteristic Derivation
Diagnosis
Step 0006 Country Ship-to > Intern.Reg
No entry in a derivation rule was found for the specified source field
The derivation rule was set up so that an error message appears when
this happens.
The required derivation rule entry would need the following source
fields:
Country Ship-to
I proceeded and the sales order couldnt save. An incompletion log pointing towards the profitability segment was generated. I have put the profit center, yet i have this issue.
Kindly help resolve it.
ThanksHi Luqman,
This issue is realted to the COPA Issue.
Please Try by giving the Profit Center at sales order Header by giving the Derivation rule and most important thing here is we have to mention the country of ship to here.
Please Reward IF Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Field catalog in Profitability Analysis
Hi,
In profitability analysis, if we want to use a particular characteristic or value field, then they should be maintained in field catalog.
Could anyone please explain me where we will define this field catalog.
Thanks
ChandraYou need to create the Characteristics and/or Value Fields using transaciton KEA5 / KEA6
Once this is done, assign these to the Operating Concern using transaction KEA0
In this transaction, enter the Operating Concern you need to modify, and then enter the Data Structure in the Data Structure tab. Assign the Characteristics / VFs in this screen (click on the respective tab to access the assignment). Once done, remember to generate the Operating Concern.
If you exit the maintenance screen on saving, the system normally prompts you to Generate the Op Co. Once this is generated, you can use these in your config./ analysis.
Cheers. -
Profitability Analysis not generated in Contract billing Document
I have created the Billing document against the contract order but the Profitability Analysis is not getting generated. But any sale order related billing document is created; system automatically creates the Profitability Analysis.
Can you tell me where the problem is or have I missed any steps?
Regards,
Devendra1) For a service material (DIEN), We are creating an Sales Order (VA01) and doing a order based billing (VF01). In the Sales Order we are giving the plant (no shipping point and storage location as it is a DIEN material).
Once we do the billing we are able to see the Profitability Analysis document.
2) Now we are using the same material we are creating a Contract (VA41) for a period of one year and doing a monthly billing. In this case we are using VF04 for doing the bills that are due.
We are getting two results in this:
a) If we give a Plant in the contract, the Profitability Analysis document is not getting generated at the time of billing.
b) If we do not give any plant, the Profitability Analysis document is getting generated at the time of billing.
Please note that we are using the same material, same pricing procedure in both the above cases 1) and 2). Only difference is that the source documents are different i.e., one is Sales Order and the other one is Contract.
In our copa valuation we have assigned the conditions to value field, no derivation rule assigned.
Regards
Devendra
Edited by: Devendrap on Apr 14, 2009 10:38 AM -
Account Based Profitability Analysis
Hi,
I am mapping characteristic fields of account based profitability analysis. I have been given fields such as KMLAND to map into BI fields.My question is how do i map the key figures. What fields in account based profitability analysis are key figures, are they value fields? Do i need a list field names of value fields to map it into BI.Some one mentioned something about cost elements.
Thanks
TJHello Tee Jay,
Cost Element is a key field in ECC. That means its char. in BW. What are the infoobjects that you have in your DSO or cube n BI.
Do you have 0COSTELMNT or 0GL_ACCOUNT? If so, then you map Cost element field from SAP to one of the above char. in BW.
By Revenue, do you mean a value field in R/3? If so, it will have to be mapped to key figure in BI.
Hope that helps. -
Costs of the product calculation lack in the profitability analysis
Hello there,
A group of students and I are currently working on a SAP project which is about to implement a full cost accounting in the SAP system (ERP). At first we used a case study reading (Friedl,Hilz,Pedell), some important components for calculating the products like u201Ccosting sheetu201D, u201Ccost component structureu201D and u201Ccosting variantu201D do exist already.
For our project we had to insert an additional primary cost center. For that reason we also added new components (the above given ones). After that the costs for our products could be calculated in the right way. We also booked supplies and stated the quantity of sales. Our problem is that the Profitability Analysis (CO-PA) does not show any costs of our cost centers (material input, manufacturing costs, overhead costs) only the earnings. We did not add any u201Cattributesu201D, u201Cderivation rulesu201D or u201Cvalue fieldsu201D but fulfilled all requirements in the Customizing menu (u201CAssign costing key to productu201D, u201CAssign costing key to productu201D, u201CAssign value fields for cost component structureu201D).
The first time when we used the case study reading and therefore another company code everything worked fine. We think that the problem might be that the costing key is not attached to the products.
Thank you for any help and suggestions,
Kind regards!In the same area as where you assign the costing key to the product, there is also an entry where you need to define the costing key. You don'tr mention that you have done that.
In the user menu for Profitability Analysis, there are also a lot of tcodes that will help you investigate the flows of values and derivation of characteristics. They are very helpful in most cases. -
How to Calculate Profitability Analysis ?
Hi
kishore
This is basically a part of Sales and Distribution Module . can u just revert me back with the Answer .
Regards
kishoreDear kishore
Profitability Analysis (CO-PA) enables you to evaluate market segments, which can be classified according to products, customers, orders or any combination of these, or strategic business units, such as sales organizations or business areas, with respect to your company's profit or contribution margin.
The aim of the system is to provide your sales, marketing, product management and corporate planning departments with information to support internal accounting and decision-making.
Two forms of Profitability Analysis are supported: costing-based and account-based.
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting.
Thanks
G. Lakshmipathi -
Batch split posting to Profitability Analysis
Hi All,
I am doing a batch split and when i create the invoice, i am getting two line items (corresponding to two batches with appropriate values). But there is only a single profitability analysis document being created for this, with the total values from both the batches. Say, i have split into two batches 2000 and 1000, then when i check the profitability doc. the batch number is showing as 2000 with the total quantity in 2000 and 1000 batches. Is this the way the standard is or is there any customizing that needs to be done to rectify this and create two Profitability analysis docs. for each batch that was created?
Thanks in advance.Has the batch been created as a characteristic and included into your PSG characterisics (KEQ3)?
Cheers. -
Implemented CO-PA (Profitability Analysis)
I would like to know if anyone has implemented Controlling - Profitability Analysis for a IS-Uitilities customer? I have some specific questions on this topic and would appreciate if someone could answer them.
RajHi Ivor
Re: Implementation: ISU Biling COPA Integration
Excuse me Ivor Martin for jumping on the bandwagon, I am in the process of implementing ISU Biling COPA Integration. I do have the cookbook but it does not clarify certain things i would like you to help me with as follows:
1.Operating concern
I am busy widentifying characteristics to use from Billing document. My question is should I set up Opconcern as in pure COPA,i.e working from reporting structure & subsequent derivation of e.g profit center?
I would like to be certain about this. Please advice me also with any other information you dem relevant.
2.I would also like to know about the pros and cons of transferring updates if that is ok with you.
Thanks in advance.
Maybe you are looking for
-
I have an iMac OS 10.4. I downloaded Firefox a while ago and I had no real problems with it. Then I got this message that I should update Firefox to 3.6.16. So I hit the "Download" button and I get the "Software Update" which says "Downloading the up
-
DBMS_SQL.PARSE + CLOB
Hi, I am using: DBMS_SQL.PARSE ( c IN INTEGER, statement IN VARCHAR2, language_flag IN INTEGER); I have to parse very very big pl/sql blocks. So I have to put into statement, paremeter which has CLOB type. When my statement is not too big everything
-
Hello, I'am experiencing some problems with a Z-Class. I want to read data from HR-Infotypes. Normaly you can use log. database PNP, macro PROVIDE, GET PERNR and so on. This you can not use in a class (if there is a way, I would be happy to know how)
-
File content conversion on Sender Side
Hi, I am doing file content conversion on sender side.when i am executing the scenario,i am getting the following error in sxmb_moni: Invalid at the top level of the document. Error processing resource 'file:///D:/Documents and Settings/.............
-
Cost of LabVIEW Exam in India and course details.
Hi I am planning to take the LabVIEW exam, I want to know the cost of exam. is LabVIEW Basics I and II manual are sufficient for the preparation of the exam as we have have them in the LabVIEW Academy. What is difference between LabVIEW Core I , II