About rfc structure defination

should i use table type in IMPORT tag or using a TABLES to transfer a parameter of table?
what difference between both?

click on Table tab(se37) and specify
ParameterName Type Specification Associated Type
example LIKE GivetableName
to know the difference refer Difference between Table and Table Type

Similar Messages

File to RFC Structure mapping

Hi All
This is the first time I am going to work on customized mapping for the following requirement, please give your inputs.
I am working on File to Proxy Scenario where I have created custom proxy using standard RFC Function Module.
I have created my source data type, message type and service interface. The target structure I got by importing corresponding RFC structure and created service interface and proxy for the same.
Now I am trying for graphical mapping here to map file structure to RFC structure. Can you please tell if I have to consider whether its header data or item data. I mean how can I mention that there will be multiple entries of item.
Please let me know if mentioning in data type i.e 1 to unbound is sufficient and no need to do anything specially while mapping them to targe RFC tables.
Also, please let me know if my approach is correct. Thanks for your inputs.
Regards
Amol

>
Amol wrote:
> Hi All
> This is the first time I am going to work on customized mapping for the following requirement, please give your inputs.
>
> I am working on File to Proxy Scenario where I have created custom proxy using standard RFC Function Module.
>
> I have created my source data type, message type and service interface. The target structure I got by importing corresponding RFC structure and created service interface and proxy for the same.
>
> Now I am trying for graphical mapping here to map file structure to RFC structure. Can you please tell if I have to consider whether its header data or item data. I mean how can I mention that there will be multiple entries of item.
>
> Please let me know if mentioning in data type i.e 1 to unbound is sufficient and no need to do anything specially while mapping them to targe RFC tables.
>
> Also, please let me know if my approach is correct. Thanks for your inputs.
>
>
> Regards
> Amol
if you are asking about how to actually map a file to a RFC/Proxy structure please note that such requirements are defined by the business. The logic is owned by the customer.
But in case you are trying a POC scenario then all you need to consider is to make sure the mandatory fields and segments are mapped in the RFC/Proxy structure

Re: Questions about Plan structure

Reply-To: "Duncan Kinnear" <[email protected]>
Q. if you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
A It is better to have them in the same plan.It depends on the design
you have
Q Why should the Managers be separated from their business classes?
A Managers are usually service objects which might require different
resources.
These managers when deployed might be required by several other
applications.
Seperating them as a different plan will help in just using one
installed partition to be
Used by different applications (refer about Reference Partition)
Q If you have the Database managers separate, what scope does each DB
manager cover?
A It is better to have the DB managers in user scope.
It depends on the numbers of users, u have for the system.
Since u are talking about 100 tables. It's a huge system.
It also depends on the user licenses u have for the backend.
Take care that u use proper load balancing of DB Managers for the
system.
Krishna CVSR
GoldStone Softech Inc
>
Hi there,
We are in the middle of designing the structure of a new system.
I have read/heard that it is best to break down the plans into the
following categories:
Business Classes
Managers/Services
Clients
I have a few questions about this structure:
Should related business classes be grouped together in Plans? E.g. if
you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
Why should the Managers be separated from their business classes?
E.g. if there is an EmployeeMgr service which deals with anything to do
with the Employee business class, why separate them in different
plans? If you need the manager to access the class, you will always
need both.
Some of the Forte documentation talks about "Policy" managers and
"Database" managers. How do the functions of these managers differ
for a simple CRUD (Create Read Update Delete) class?
If you have the Database managers separate, what scope does each
DB manager cover? I.e. do you have one for the entire database (over
100 tables in our case), or do you break it down by sub-system?
Thanks in advance for any answers.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email: [email protected]
PO Box 764, McLean Towers, Phone: +64 6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
Providing Integrated Software to the Meat Processing Industry for over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Reply-To: "Duncan Kinnear" <[email protected]>
Q. if you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
A It is better to have them in the same plan.It depends on the design
you have
Q Why should the Managers be separated from their business classes?
A Managers are usually service objects which might require different
resources.
These managers when deployed might be required by several other
applications.
Seperating them as a different plan will help in just using one
installed partition to be
Used by different applications (refer about Reference Partition)
Q If you have the Database managers separate, what scope does each DB
manager cover?
A It is better to have the DB managers in user scope.
It depends on the numbers of users, u have for the system.
Since u are talking about 100 tables. It's a huge system.
It also depends on the user licenses u have for the backend.
Take care that u use proper load balancing of DB Managers for the
system.
Krishna CVSR
GoldStone Softech Inc
>
Hi there,
We are in the middle of designing the structure of a new system.
I have read/heard that it is best to break down the plans into the
following categories:
Business Classes
Managers/Services
Clients
I have a few questions about this structure:
Should related business classes be grouped together in Plans? E.g. if
you have an Employee class with related EmployeeSubordinate and
EmployeeSalaryHistory classes, should these all be in the same plan?
Why should the Managers be separated from their business classes?
E.g. if there is an EmployeeMgr service which deals with anything to do
with the Employee business class, why separate them in different
plans? If you need the manager to access the class, you will always
need both.
Some of the Forte documentation talks about "Policy" managers and
"Database" managers. How do the functions of these managers differ
for a simple CRUD (Create Read Update Delete) class?
If you have the Database managers separate, what scope does each
DB manager cover? I.e. do you have one for the entire database (over
100 tables in our case), or do you break it down by sub-system?
Thanks in advance for any answers.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email: [email protected]
PO Box 764, McLean Towers, Phone: +64 6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
Providing Integrated Software to the Meat Processing Industry for over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

How to create dynamic context based on a structure defined in the program?

Hi Experts,
         I need to create a dynamic context based on a structure wa_struc which i have define programatically.
When I pass wa_struc to structure_name parameter of create_nodeinfo_from_struc, i get a runtime error:
"Parameter STRUCTURE_NAME contains an invalid value wa_struc."
How to create dynamic context based on a structure defined in the program?
I have written the code like this:
TYPES: BEGIN OF t_type,
            v_carrid TYPE sflight-carrid,
            v_connid TYPE sflight-connid,
         END OF t_type.
Data: i_struc type table of t_type,
         wa_struc type t_type.
data: dyn_node   type ref to if_wd_context_node.
data: rootnode_info   type ref to if_wd_context_node_info.
rootnode_info = wd_context->get_node_info( ).
clear i_struc. refresh i_struc.
select carrid connid into corresponding fields of table i_struc from sflight where carrid = 'AA'.
cl_wd_dynamic_tool=>create_nodeinfo_from_struct(
parent_info = rootnode_info
node_name = 'dynflight'
structure_name = 'wa_struc'
is_multiple = abap_true ).
dyn_node = wd_context->get_child_node( name = 'dynflight' ).
dyn_node->bind_table( i_struc ).
Thanks
Gopal
Message was edited by: gopalkrishna baliga

Hi Michelle,
          First of all Special thanks for your informative answers to my other forum questions. I really appreciate your help.
Coming back to this question I am still waiting for an answer. Please help. Note that my structure is not in a dictionary.
I am trying to create a new node. That is
CONTEXT
- DYNFLIGHT
CARRID
CONNID
As you see above I am trying to create 'DYNFLIGHT' along with the 2 attributes which are inside this node. The structure of the node that is, no.of attributes may vary based on some condition. Thats why I am trying to create a node dynamically.
Also I cannot define the structure in the ABAP dictionary because it changes based on condition
I have updated my code like the following and I am getting error:
TYPES: BEGIN OF t_type,
CARRID TYPE sflight-carrid,
CONNID TYPE sflight-connid,
END OF t_type.
Data: i_struc type table of t_type,
dyn_node type ref to if_wd_context_node,
rootnode_info type ref to if_wd_context_node_info,
i_node_att type wdr_context_attr_info_map,
wa_node_att type line of wdr_context_attr_info_map.
wa_node_att-name = 'CARRID'.
wa_node_att-TYPE_NAME = 'SFLIGHT-CARRID'.
insert wa_node_att into table i_node_att.
wa_node_att-name = 'CONNID'.
wa_node_att-TYPE_NAME = 'SFLIGHT-CONNID'.
insert wa_node_att into table i_node_att.
clear i_struc. refresh i_struc.
select carrid connid into corresponding fields of table i_struc from sflight where carrid = 'AA'.
rootnode_info = wd_context->get_node_info( ).
rootnode_info->add_new_child_node( name = 'DYNFLIGHT'
attributes = i_node_att
is_multiple = abap_true ).
dyn_node = wd_context->get_child_node( 'DYNFLIGHT' ).
dyn_node->bind_table( i_struc ).
l_ref_interfacecontroller->set_data( dyn_node ).
But now I am getting the following error :
The following error text was processed in the system PET : Line types of an internal table and a work area not compatible.
The error occurred on the application server FMSAP995_PET_02 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_WD_CONTEXT_NODE~GET_STATIC_ATTRIBUTES_TABLE of program CL_WDR_CONTEXT_NODE_VAL=======CP
Method: GET_REF_TO_TABLE of program CL_SALV_WD_DATA_TABLE=========CP
Method: EXECUTE of program CL_SALV_WD_SERVICE_MANAGER====CP
Method: APPLY_SERVICES of program CL_SALV_BS_RESULT_DATA_TABLE==CP
Method: REFRESH of program CL_SALV_BS_RESULT_DATA_TABLE==CP
Method: IF_SALV_WD_COMP_TABLE_DATA~MAP_FROM_SOURCE_DATA of program CL_SALV_WD_C_TABLE_V_TABLE====CP
Method: IF_SALV_WD_COMP_TABLE_DATA~MAP_FROM_SOURCE of program CL_SALV_WD_C_TABLE_V_TABLE====CP
Method: IF_SALV_WD_COMP_TABLE_DATA~UPDATE of program CL_SALV_WD_C_TABLE_V_TABLE====CP
Method: IF_SALV_WD_VIEW~MODIFY of program CL_SALV_WD_C_TABLE_V_TABLE====CP
Method: IF_SALV_WD_COMPONENT~VIEW_MODIFY of program CL_SALV_WD_A_COMPONENT========CP
-Gopal
Message was edited by: gopalkrishna baliga

Changes in RFC Structure.

Hi Experts,
My RFC structure is changed, can i do anything else than restarting the server.
Regards
Upendra.

Hi,
its must and should, otherwise changes will not effect.
Please tell me how i will know wether my RFC is Adaptive RFC or not.
That will depend when you access the rfc in webdynpro from R/3. in the second step you have to select the adaptive rfc while importing the rfc.
from r/3 side, your rfc will be remote enabled, thats all.
PradeeP
Edited by: pradeep bondla on Oct 16, 2008 12:16 PM

RFC Structure

Hi All,
Actually, I am working on FILE->XI->RFC scenerio.The custom Function module created is the merging of 3 BAPIS which is used at the receiving end.But ,the Custom Function Module is having the response structure also while I need to work on Asynchronous scenerio.
From my understanding if I need to use the Asynchronous Adapter such as File for synchronouse communication then I need to write the Adapter Module.So if I need to use File for Synchronous Communication shall I need to write the Adapter Module for that?
Also,from my understanding if the custom BAPIS(RFCS) are merged into the custom Function Module then it is obvious to have a response structure as RFCS are used for Synchronous communication.Is it?If so, then I can neglect the response structure of the Custom Function Module if I need to implement the Asynchronous File->XI->RFC scenerio.Is it?
Please help me.
Thanks in advance.

Hi Shweta,
>>Is the following document applicable for my scenerio? https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without%20BPM%29
Yes very much.. BTW where you want your response to be written?
>>No. of Data Types,Message Types
2 Data type (Data type for sender file say DT_A, Data type for getting response from RFC say DT_A_resp)
2 Message Type (corresponding Message type say MT_A and MT_A_resp)
1 RFC structure
>>No. of Message Mappings,Interface Mappings
2 Message mapping (from MT_A to RFC and from RFC_response to MT_A_resp)
1 interface mapping
>>No of Communication channels
3 one for sender file, one for RFC (receiver) and one as receiver file
>>No. of Sender Agreements,Receiver Agreements
1 with File sender
>>No. of Receiver Determinations,Interface Determinations.
1. Between file service and RFC service
>>Which RFC Structure(Request/Response) shall I mention in the Interface Determination?
Mention RFC (not the response one)
Regards
Suraj

Question about RFC adapter

Hi,
There is this little concept about RFC adapter
I would like a liitle clarifiaction about..
Here it goes..
Let's just say I have made an RFC in R/3.
The same I have imported In xi.
now when we say RFC ...By definition
it is a remote enabled function module.
We import the "interface" of the Same in Xi
So if I make changes in the BODY of the RFC in
R/3... do i need to reimport it in XI.
Besides when XI's reciver RFC adapter is using the
Rfc's interface to make changes in R/3
is it using a Copy of this RFC created in R/3
I would like to intercep at the point it's doing so...
tried putting a break point in the body of rfc.
Another question is regarding RFC sender adapter
Program ID..tcp Ip protocol.
Conceptually How does this connectivity takes place
I tried and it worked ...
I dunno How to explain this connectivity taking place
just on the basis of PROGRAM ID...
Kindly Help

Hi Deepak,
+
>>We import the "interface" of the Same in Xi.So if I make changes in the BODY of the RFC in R/3... do i need to reimport it in XI.+
Yes you have to.
>>Another question is regarding RFC sender adapter.Program ID..tcp Ip protocol.Conceptually How does this connectivity takes place I tried and it worked ...I dunno How to explain this connectivity taking place just on the basis of PROGRAM ID...
·An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system).
·If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the corresponding JCo server program.
http://help.sap.com/saphelp_nw04/helpdata/en/09/c88442a07b0e53e10000000a155106/content.htm
Hope this will clarify your doubts.
Regards
Suraj

No rfc destination defined for global trade services error while doing migo

Hi all,
Pls help me in fixing the following error..
"no rfc destination defined for global trade services" error while doing migo

i guess you will be getting dumps in the background in ST22. Can you please check this and post the details if there are any dumps?
Meanwhile, check this note:
Note 1098491 - MIGO:Termination MESSAGE_TYPE_X with IO 304 (subcontracting)
Cheers,
Jazz

JCO RFC Server - defining a repository

Hi,
We're creating an RFC listener through JCO, and I'm not entirely sure where definitions for the RFCs go. Originally, we had the RFC definitions defined as stubbed out shell Functions, and in the Java code as a JCO.MetaData repository definition as well. It seems like the stubs in SAP don't actually matter, and it only needs the JCO.MetaData functions, but I'm not sure.
While I'm at it, if it is possible to not actually define the parameters to an RFC in a java-side repository, that would be great. We're planning on supporting Unicode, and those MetaData definitions look scary.
Thanks,
Corey

I think I just answered my own question. Can someone verify?
You have to define the repository on the Java side, and there should be no matching remote enabled function on the SAP side if you want a static repository.
If you want a dynamic repository, then the remote enabled RFCs must exist on the SAP side, and a connection from Java to the SAP system must exist so that the repository may be dynamically retrieved.
Is this all correct?

Change in RFC structure

Hii experts,
I was doing rfc scenario.. so i am imported a rfc structure in IR.. i done mapping and all.. but now my rfc structure has been changed say like one extra field has been added in rfc structure.. so i reimported it and trying to do mapping.. but i cant find the new field so i cant map that particular field.. how can i resolve this??
Im using PI 7.0
Regards,
Balaji

Ask your ECC Team to do the following things.
1. Cancel the Release of RFC.
2. Add the additional Field to RFC and Activate it.
3. Release the RFC.
After doing above.
1. Re-Import the RFC.
2. Make the mapping.
3. do some dummy changes in Sender channel and activate it again.

About RFCs

Hi all,
        I want to know more about RFCs. What is the diff between transactional async and sync RFCs. Can u tell me vividly so that it can help me in real time.
        Also can u send me some good docs on RFCs in my mail id [email protected]
        Pls experts help me on RFCs and explain me vividly.
        I will reward points.
With regards,
    Abir.

Hai Abhir
Sending system side(SEND--800)
Create function module by using Tcode SE37 or SE80
goto attributes select remote function
activate
Receiving system side(RECE--000)
goto Tcode SM59
here select the R/3 Connections-->click on Create Button
give RFC Desstination : TESTRFC
     Connection Type : 3 for Connecting two systems
     Description      : Some meaningful Description
Press enter
give Target system Name : SEND
          Language      : EN
          Client        : 800
          user Name     : sapuser
          Password      : xxxxxx
save this connections & click on test connections(f8)
                      & Remote logon(f7)---> it will open a session
                        with client 800 that is your sending system
                        then only your RFC is correct
create a report in SE38 Tcode
data : c1 type i.
data : itab like mara occurs 0 with header line.
call function 'ZRFCFM' destination 'TESTRFC' --->Function Module 'ZRFCFM' your just create at Sending system
     exporting
     importing
     exceptions.
Here are the steps.
SM59 Transaction is used for Connection Establishment with Destination.
When you establish a connection to a client through a destination, the HTTP connection must first be entered in transaction SM59.
There are two types of HTTP connection in transaction SM59: Call transaction SM59 to display the different RFC destinations.
The HTTP connection to the external server (connection type G) and the HTTP connection to the R/3 system (connection type H) are different only in their logon procedures. Their technical settings are the same. To display the technical settings, double-click a connection.
You can choose from three tabs. Under Technical Settings, you can specify the following:
・ Target Host: The host to which you want to connect.
Note that if you are using HTTPS as a protocol, you have to specify the full host name (with domain).
・ Service No.: Here, you specify the port. The destination host must of course be configured in such a way that the specified port understands the corresponding protocol (HTTP or HTTPS). See Parameterizing the ICM and the ICM Server Cache.
・ Path Prefix: At the time when the connection to this destination is initiated, the system inserts this sub-path before ~request_uri.
・ HTTP Proxy Options: Here, you can configure a proxy for HTTP connections: You can determine the proxy host and service, as well as users and passwords for the HTTP connection.
The tab page Logon/Security will be different depending on whether you have selected a HTTP connection to an external server (connection type G) or a HTTP connection to an R/3 system (connection type H).
HTTP Connection to an External Server (Connection Type G)
Choose the connection you want to use. You can choose from the following logon procedures:
・ No Logon: The server program does not request a user or password.
・ Basic Authentication: The server program requests a user and password. Basic Authentication is a standard HTTP method for authenticating users. When a user logs on to the target system, he or she provides a user ID and password as authentication. This information is then sent in a header variable as a Base 64-encoded string to the server, through the HTTP connection.
・ SSL Client Certificate: If you use client certificates for authentication, the client authentication is performed through the Secure Sockets Layer (SSL) protocol. In this case, you must also select the SSL Client PSE of the SAP Web AS that contains the relevant certificate for the authentication. The target system must handle the issuer of the SAP Web AS client certificate as a trusted system.
Under Logon/Security, you can also activate SSL to ensure that HTTPS is the protocol used (if you select SSL, make sure that the correct port is entered under Technical Settings). In the security transaction STRUST you can determine which type of SSL client is used. (Getting Started with the Trust Manager, Trust Manager).
The field Authorization for Destination has been implemented as an additional level of protection. We recommend that you specify a user and password for the RFC destination.
HTTP Connection to an R/3 System (Connection Type H)
Here, you can specify more settings for authentication in the target system.
The settings under Technical Settings and Special Options are the same as for connection type G. Under Logon/Security, the connection type H has additional logon procedures. As with external servers, you can activate and deactivate SSL and specify an authorization.
Because the target system is an SAP system, you can set the client and language for the logon as well as the user name and password. If you check Current User, you have to specify the password.
The following authentication procedures are available: Basic Authentication, SAP Standard, and SAP Trusted System, and SSL Client Certificate.
・ HTTP Basic Authentication: Logon with user and password
・ SAP Standard: This procedure uses an RFC logon procedure. The RFC Single Sign-On (SSO) procedure is valid within the one system. The same SAP user (client, language, and user name) is used for logon.
・ SAP Trusted System: Trusted RFC logon to a different SAP system (see Trusted System: Maintaining Trust Relationships Between SAP Systems)).
・ SSL Client Certificate: The SSL protocol enables you to use client certificates for the logon.
Type G/H (SM59)
Timeout:
When sending a HTTP request, you can use this parameter to specify the maximum response time for the connection.
HTTP Setting:
You can use the HTTP version to specify the protocol version of the HTTP request (HTTP 1.0 or 1.1).
Compression:
You can use this option to activate the gzip compression for the request body. This can only be activated in HTTP Version 1.1.
Compressed Response:
In the standard setting, the SAP Web Application Server sends the Accept Encoding field as a header field with the value gzip, if the application server can handle this compression. This notifies the partner that the caller can handle gzip decompression, and that the partner can send compressed data. If you want to prevent a compressed response being sent, choose the option No.
HTTP Cookie:
You can use this option to control the way received cookies are handled.
You can specify the following for cookies:
・ Accept them automatically
・ Reject them automatically
・ Accept or reject them in a prompt
・ Use a handler for the event IF_HTTP_CLIENT~EVENTKIND_HANDLE_COOKIE to process the cookies in the program.
・ In the next section, you can read about the parallelization of requests.
Check this thread
Re: SM59
Thanks & regards
Sreenivasulu P

About RFC's

Hi Experts,
 I want to know more about RFC's .
 How to work on RFC's
 Examples on RFC's
 Doc's on RFC's
Please let me know all these
Regards
khanna

Hi ,
RFC:Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Synchronous RFC:
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
For more information on RFC, please go through the link.
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
Regards,
Bhanu

Advice about application structure before starting

Hi all,
I am so sorry for this longest post, but I have to explain all thing. Sorry again.
I have been studying with Labview for a year by myself without taking any professional support. When I get stuck in preparing my VIs, I always post here and you answered me with great patient. Thank you for all. Now, I am about to start a new VI and before starting it I thought it would be good to consult you on that.
The goal of this VI could be classified under 4 main topics: Acquisition, control, analysis, and recording the data. I am studying on a test system. There are two types of data to be acquired from the test system: pressure and temperature. For this purpose I have 1xNI 9203 (analog input-current) & 2xN9214(analog input-temperature). The test system is desired to be under control by use of a DC compressor with a frequency converter. To control that frequency converter I have to use NI 9263 (analog output- voltage). All hardware system is installed on NI 9188 cDAQ.
Before preparition of this system, I have coded a VI that acquire, analyse, and record the data-there is no use of NI 9263 (attached here). In this VI, I used a basic structure and it works fine. The only problem of this VI is delaying when the stop button is pressed. Anyway, now I want to prepare a new one. The difference of the new VI from the old one is that it controls the system while acquiring, analysing, and recording processes. And this control is supported by acquired pressure and temperature values. This will be my first big project and I need your suggesttions on structure of this VI. Do I start to build it with state machine architect or another ones? To prevent the data loss what kind of precautions could be taken?
Thank you all in advance.
Egemen
Attachments:
MAIN PROGRAM_v0.vi ‏147 KB

Egemen,
First, Great! It is very important to plan and design your program before starting to write it.
Next, you do not need to apologize for providing the information necessary for someone to respond to your request. We would very much prefer a post of several paragraphs which contains the relevant information to a brief post which only elicits questions for more details.
Now to your questions.
1. Look at the style guides. Your block diagram was several screens high and wide. It is recommended to keep the diagram to one screen. Paticularly in programs which will get large and copmlicated like yours, this readability constraint will be very worthwhile. Effective use of subVIs is one way to help minimize screen bloat.
2. Look at the style guides. The use of local variables to pass data from one loop to a parallel loop is not recommended. It can lead to race conditions, force execution of the loops in the UI thread, and is slower than wires.
3. Read the help on Event Structures. Only one event structure per VI is recommended. Although the way you have used them will probably work, it consumes hectares of block diagram space and may be vulnerable to problems when you or another developer decides to make a few changes.
4. Because there is no data dependency, it is possible (although not very likely) that the main loop could start running before the clear history property nodes execute.
5. How do your temperature charts know which waveform to display?
6. You stop on DAQ errors but do not check for file errors. You may want to consider more robust error handling.
Now, some general comments on program structure. You list 4 topics: Acquisition, control, analysis, and recording the data. This may also be a good way to think about program structure. The structure probably needs one more topic: User Interface. The program you posted essentially has 2 topics: User Inputs and everything else. Think about the timing requirements for each topic. User interface - needs to respond to user inputs in about 100 ms or the user begins to feel as though the program is not responding. Similarly, displays do not need to update more than a few times per second. Acquisition - Software timed. Default value = 1.67 Hz. Output not specified, but since you are talking pressure and temperature, it is probably slow also. Once you start doing closed loop control, it may become more important to keep the timing constant. Record data - same timing as acquisition. However, writing 8-64 channels of data two two files twice per second may not be optimum. And what happens when the OS finds that the files are fragmented and must allocate new sapce for the file and takes more than half a second to do so? Analysis - Your subVIs were not included so I have no idea what they do, how fast they may be and what effects they may have on the overall operation.
What I suggest is that you study the Producer/Consumer Design Patterns and State Machines. I think you may end up with 3 or 4 parallel loops. One will be the User Interface loop with the only event structure. Another will handle all the data acquisition (possibly including outputs when controlling your test system). This will be a state machine which initializes the DAQ, Reads and Writes, and shuts it down when finished. The File writes may be in a separate loop. If file I/O is put into a parallel loop, it should be a state machine which opens, writes, and closes the files and retains the file path or reference for repeated writes. The control and analysis (another state machine) may be in a separate loop or could run in the timeout case of the event structure in the UI loop. Which is best depends on details of your system.
With the amount of data you are moving around and the number of property nodes you need to use, learn to manipulate the front panel from a subVI. Search the Forum for posts on use of control references and on updating the main front panel from a subVI. There are some good methods posted.
Lynn

Fault Structure defined in my WSDL

Hi I have made a wsdl;
I have defined the request element structure , response element structure and the fault element structure.
I made a proxy service consuming that wsdl.
Now whenever an internal OSB error or provider side error is occuring , i m not getting the error details in the fault structure i had defied in the wsdl.
please help

Hi,
Whenever an internal error occurs, OSB will not populate it in fault structure defined in WSDL. It has to be handled in error handler and the error details should be mapped to the fault structure defined in the WSDL.
Regards,
Vish

Questions from a rookie about event structures

Hello,
I am currently scheduled for Labview classes next month,
so I want to apologize in advance for "dumb questions". I have created
a program that is starting
to be a CPU resource hog. The majority of my program is inside a while
loop so that the program will "react" to changes in controls, etc. I am
assuming that
if I incorporate "event structures" in my program that my program will
not be a resource hog. Is the use of event structures the correct
way to go? If using
event structures is the correct way to go, what is the best way to
learn how to incorporate "event structures"? I am assuming that
the examples in Labview will show me how. Are there any good reading
materials about event structures?
Regards,
Kaspar

To fix the CPU resource issue, you need to place a small wait statement in your loop. It will solve two problems:
Slow down the loop (you don't need to check for UI changes more that 10x/second)
It will allow other, parallel tasks a chance to run after each iteration. Without a wait, it will hog the CPU for 55ms before releasing control.
If your loop currently spins one million times a second and you would place a 1ms wait, the CPU would go from 100% to 0.1%!
The event structure is a fantastic tool to solve most UI issues and it makes the diagram automatically simpler, more self-documenting and easier to read. Have a look at some of the examples that ship with LabVIEW.
The event structure is easy to learn, so dive right in. Read the online help for some important considerations. As a rule of thumb you should stick to a single event structure per diagram.
LabVIEW Champion . Do more with less code and in less time .

About rfc structure defination

Similar Messages

Maybe you are looking for