Difference between model and metadata JCos

Hello,
What is the difference between modeldata and metadata JCos ?
Regards
Mrinalini

Hi Mrinalini,
The difference between the Model & Meta data is:
Model data is the data coming through the table (which means it describes the actual data present in the table).
Metadata is the structure of the table (which contains structure definitions, type definitions etc.)
Thus, model data destination will fetch actual data while metadata destination will contain descrition of the data.
Hope this helps you
Cheers!!!
Umang

Similar Messages

Model and Metadata JCo Destination Config in WD

Hi!
I just want to ask or verify if this is a correct JCo setup:
Logical System Name: WD_APT_MODELDATA_UIP_GDC
Model Instance Logical System Name: WD_APT_METADATA_GDC
Thanks!

Hi,
Thanks for that link. Yup, I think the project's JCO is interchanged somehow based on the link that you gave me. To give a background, this is just a transitioned project to me and the JCO was set up in that way...
I don't know why that was the case, but when I reversed the two JCO, it gave me an RFC authorization error. However, when I interchanged the MODEL and METADATA JCO, it worked fine again.
Would you know why this is the case? I just want to verify if it is alright to interchange JCOs and ensure that the conifgurations are correct.

Difference between Model and Open MBeans?

Hey all,
does somebody know what the difference is between an Open ManagedBean and an Model ManagedBean?
Thanks a lot!
theKeymaker

Hey,
I've already read the specification of JMX, so also
the chapter about Model and Open MBeans, but I don't
get the point when I'd have to use a Open and a Model
MBean.
What's the real difference between them?
Thanx!
Hi,
The "real" difference is that Open MBeans are restricted to using data types that are portable to any Java /JMX client. This allows management applications to immediately make use of MBeans without
recompilation, re-assembly, or dynamic linking.
hope this answers your question,
-Hans
Hans Hrasna - Sun Java Software

Model and Metadata in JCO creation

Hi all,
I am having dout regarding Modeldata and Metadata.For example i am having 2 function modules.Is it that the name given to the fields " Default logical name for model instances " and
"Default logical name for metadata instances " should be same for both the function modules as WD_BAPI_MODELDATA_DEST and WD_BAPI_RFC_MODELDATA_DEST so that JCO connection created for the above 2 names can be used for all the function modules
Regards
Padma N

Hi Chaitanya,
For example i want to work with 5 function modules in my application.So while creating model i used model data and metadata as
Modeldata Name : WD_BAPI_MODELDATA_DEST
MetaData : WD_BAPI_RFC_MODELDATA_DEST
and i selcted all the 5 function modules and i clicked finish.
If i delpoy the application now and tried to create JCO connection the above 2 names are visible with red button besides them.
If i create JCO connection for the above model and metaData instances will the 5 function modules will work fine or not
Regards
Padma N

Question about Jco conenctions/Logical name of the model and metadata

Is it common to use the same logical name of the model and metadata across different enviroments?
For example, MODEL_DATA_DEST, META_DATA_DEST is used for DEV, QAS and PRD? Because i seem to have some trouble using code built in DEV to another environment if the logical name of the model and metadata is different.
Thanks in advance

Hi,
No for every environment the logical name of the model and metadata are different...
for eg: some logical names,
WD_RFC_METADATA_DEST
WD_MODELDATA_DEST
USERINFO_WD_RFC_METADATA_DEST
USERINFO_WD_MODELDATA_DEST
About JCo Details,
SAP JCo Functions,Architecture,Applications,Installation,Client & Server Programming :
http://help.sap.com/saphelp_nw70/helpdata/en/6f/1bd5c6a85b11d6b28500508b5d5211/frameset.htm
Creating Jco destination:
http://help.sap.com/saphelp_nw70/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/frameset.htm
Maintaining Jco destination:
http://help.sap.com/saphelp_nw70/helpdata/en/94/3c1b40fcdd8f5ce10000000a155106/frameset.htm
The SAP JCo Repository :
http://help.sap.com/saphelp_nw70/helpdata/en/01/43e13d82fcfb34e10000000a114084/frameset.htm
Dynamic Jco creation Blogs:
/people/anilkumar.vippagunta2/blog/2007/02/06/dynamic-jco-creation
/people/gregor.wolf3/blog/2004/09/23/from-function-module-to-jco-application--part-1-of-3

Difference between models G20 and G25

Hi folks!
I've been seeking a laptop and I was amazed with Qosmio.
When I was going to order it, i noticed that there are lots of G20 models with different specifications. I also found G25 on internet searches and found no difference between G25 and G20 except that G25 TV receiver is NTSC and G20 was out on March and G25 was on June. They've the same specifications instead for the hard drive.
I live in Portugal and the only Qosmio model I can find here is G20-118. I was looking for the model that has 2x100Gb SATA HD but can't figured it out.
On internet researches i found Qosmio G20-111 that has 2x100Gb SATA HD but on the web page mentioned that it was a Pentium III processor (ridicule, isn't it?). I was looking for more reliable information.
Already searched toshiba pages and didn't find specifications for all models that i found on web searches such as G20-102, 105, 106, 108, 109, 111, 118, 123,490LS, ...
Can anyone help me with this? Is there any reliable web page where i can see the differences between models? is there any .pdf or anyone that can please give me some tips?
Money is no problem at this time to acquire the laptop, i am only looking for the higgest performance laptop!
Best Regards
Joo Pereira

Hi
Its very difficult to say which unit is the best, because there are many models with different parts.
Nevertheless I found page with G20 and G25 description.
Take a look at this link.
http://www.releasereview.com/Toshiba-Qosmio-G20-105-108-114.aspx?d=0101000580926052005
Bye

Difference between CAF and GP?

Dear All,
Can any one explain me what is the difference between CAF and GP? what is the difference between the CAF application and webdynpro application? In which senario we will go for CAF development and in which senarion we will go for GP application. Can we deploy the CAF/GP application in Enterprise Portal?
Thanks in advance
With Regards,
Balachander

Composite Application Framework consist of two parts
1. CAF Core
2. CAF GP (Guided Procedure).
CAF core is used to model the the services. Composite Application Framework (CAF Core) service-oriented architecture and the standardized object access allow for uniform treatment of business processes as servicesand business objects independent of the underlying system. CAF Core integrates the elements of all the SAP NetWeaver integration layers to facilitate the creation of new business solutions across people, information, processes and application object repositories. Composite Application Framework Core (CAF Core) is an environment for building andrunning packaged composite applications (PCAs) such as SAP Collaborative Cross Applications (xApps).CAF Core supports the development of new business solutions across people, information, and processes by unifying elements from all layers of the SAP NetWeaver technology platform.
CAF Core is a comprehensive environment, which includes programming abstractions, a
programming model, metadata, and tools to support the development and deployment of
composite applications based on Enterprise Services Architecture (ESA). This environment
allows developers to build applications, which leverage the whole SAP NetWeaver stack
without the need to feed low-level APIs. This way, they can focus on implementing the
business logic of a composite application. SAP CAF comes with predefined generic patterns
for reuse in different development projects.
CAF Core consists of the following main elements:
Composite Application Services perspective, which includes a tool for modeling entity,
application, and external services
Configurable user interface components
CAF Core administrative tool
CAF Core and SAP Business Information Warehouse (SAP BW) integration.
CAF GP (Guided Procedure) : CAF GP is used for process or orcastration. Anything you want to integrate with GP you will firat go through Callable Object. For Each Callable Object has one Action. So callable Object and Action are mapped with 1:1. On the top of Actions you need to create Block and on the top of Block you will Create Process.
Difference between the CAF application and webdynpro application: CAF application CAF Core) is used for modeling services. The services may be local in respect of CAF or remote (like RFC, BAPI, Web Service). But Web Dynpro application is used to develop the UI (User Interface). You can Line your CAF application with Web Dynpro Applicationa and ultimatelly you can expose the web dynpro application as a Callable Object which will be integrategrated with Guiged Procedure. Another ways for developing your UI using VC(Visual Composer), CAF UI Pattern.
If you need more details let me know.
Thanks and Regards
Chandan

What's the difference between thunderbolt and mini displayport?

I'm trying to connect my Macbook with a monitor and I'm thinking of what cable to get. I will have to connect using a (Thunderbolt to HDMI cable) or a (mini displayport to HDMI cable).
I was wondering what's the difference between Thunderbolt and mini displayport
Thanks

@bontistic: it is not true that only the Macbook Air supports Thunderbolt. All models(!) support thunderbolt: also the Macbook Pro's and Mini's. Eg.: http://www.apple.com/nl/macbookpro/features.html#thunderbolt
My Macbook Pro from 2011 already supported Thunderbolt...

Difference Between BAPI And RFC in ABAP

Hi,
i want to know difference between BAPI and RFC in SAP,
can we call SAP GUI screen from NON SAP System Using BAPI.
Reg,
Hariharan

Hi Ravishankar,
The difference is not importat while you understand the concept.
I think, RFC is the protocol for calling functions from external systems in R/3.
I understand like BAPI a series of complet functions that SAP offers you for use and model a business use.
But if I need program a function that can be called for external system i would call it RFC_NAME, because is a unique function that makes a single task.
In other words, the difference i think is about work idea more than another thing.
RFC
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
BAPI
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Check these Links out
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
Refer following SDN threads:
Diff. Between BAPI and RFC
Re: BAPI and RFC
Hope this resolves your query.
Reward all the helpful answers.
Regards

What is the difference between ERP2004 and SAP 47 Enterprise?

Currently we have SAP 47 Enterprise with WAS 6.2. I understand ERP2004 is NW and 6.4 sp9. Can any one please let me know the major difference between ERP2004 and SAP 4.7 Enterprise ( more from abap / workflow view)?
Thanks
Swamy

From Abap point of view some of the major add-on in erp2004,netwever :
1) Development of webdynpro studio for java development for portal and iviews.
2) Major abap development uses Abap object oriented methodology, rathet hten old conventional Abap,i.e MVC model (Model,View,Controller) where in it uses concept of classes,interfaces,etc.
3) Advanced BSP tech using MVC model to develop web based modules
4) It is closesly integrated with web-based CRM and BW/APO

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

DIFFERENCE BETWEEN BAPI AND ALE

HI
COULD ANYBODY TEL ME
DIFFERENCE BETWEEN BAPI AND ALE

Hi Kalyan
ALE is a SAP specific method how to distribute data from and to SAP. It uses the asynchronous calls based on IDOC structures.
However in the distribution modell of ALE can also be used BAPIs. They will then automatically converted into IDOC structures. After creating the IDOCs they will be passed over to the receiver using the tRFC protocol.
Wheras the BAPIs are using the sRFC protocol.
fir more information please check this:
http://www.sap-img.com/abap/ale-bapi.htm
regards
Srinivas

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. 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.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

Difference Between Transport and message protocols in XI

Hi,
Can u please explain with some example , Difference Between Transport and message protocols in XI.
thanks
dhanush

Hi dhanush,
This two can have different attributes which were assigned in the adapter metadata. Please see this help for some info on this:
http://help.sap.com/saphelp_nw04/helpdata/en/79/e462405c910272e10000000a155106/content.htm
Go to SAP BASIS 6.40 or 7.00 software compoenent and open namespace http://sap.com/xi/XI/System. Go to Adapter objects and open Adapter metadata. Then open any adapter. Here you can see all the properties of your adapter which support.
Transport protocol gives information about outside of message details, kind of system, security details.
A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
Message protocol gives you an idea of message type XI payload
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm
Regards
Biplab

note:reward with points if helpful

Difference between model and metadata JCos

Similar Messages

Maybe you are looking for