DIFF. between Quick Viewer and Query Builder

Hi experts,
can any body explain the difference between Quick Viewer and Query Builder with examples and can u forward the related material( how to create Quick Viewer and Query Builder ) other than help.sap.com.
useful answers duly rewarded
thanks in advance
sai krishna

my mail id: was [email protected], please send me the material
i will assign the points
thanks in advance
sai krishna

Similar Messages

Diff between database view and inner join

Hello,
I need to select data from multiple tables. I need to choose between 2 options.
1) create a database view and use this view for select.
2) write an inner join in abap prorgam.
In which cases we should create a view and in which cases we should use a inner join?
What are the factors which decide these?
Pls advice.
Thanks,
Rupali.

Hi,
Both are same..
But if you use regulary and used view in Multiple programs then create view..
If inner join in abap prorgam between two or more table used in less Programs and do not want to
create View (Means not to create transport request) then go for JOin in Program.
Prabhudas

Diffrance between saved views and workbooks

Hello Friends,
Good Morning ..
Could any one please tell me what is the diff between saved view and Workbooks. .?
It will be nice help for me.
Thanks .

Hi Jain,
Do not know if your question is already answered. Let me give you my thoughts on this subject ... start with what is a query.
A query definition is saved on the server. Never anywhere else.
Although people say a workbook contains a query (or several queries); it does not. It contains a reference to a query. The workbook can be saved on the server; or anywhere else that you might save an Excel workbook.
What happens if someone changes the query definition on the server? Answer: the next time you refresh the query in the Excel workbook, the new query definition replaces the old query definition in the workbook. Maybe. It depends on what change was made.
For example, if someone added a Condition to the query definition, the workbook will be virtually invisible to this. The Condition is available; but, is not implemented in the workbook. (Until the user of the workbook manually adds the view of the Condition and then activates it.)
For example, if someone changed the definition of a KF in the query definition, the revised KF will show up in place of the old KF in the workbook.
But ... if, for example, someone deleted the old KF and added a new KF, we get a different story. Now the old KF no longer appears (it does not exist); but, the new KF does not appear (it was not marked to be visible in the workbook).
About workbooks as views ... OK, a workbook may very well have a certain "view" of the query (drilldown, filters, et cetera). And, if the workbook is saved to the server in a Role where everyone can access it, this is good. But, if the workbook is saved to one's favorites, then this "view" is only accessible to that individual. Which may be good. Or may not.
A "saved view", on the other hand is stored on the server. So, it is available to all.
If you navigate in a workbook you can back up. You can back up, though, only as far as you navigated in the current session. You cannot back up to where you were in the middle of last week's session. Unless you saved that navigation state as a "saved view". Then, you can jump to that view at any time.
The downside of saved views is that they are easy for anyone to set up and difficult for most to delete.
- Pete

What exactly is the diff between client dependant and client independant te

Hi gurus,
What is the diff between client independant and client dependant term.. I initially had a confusion related to client independant and client dependant Transport requests, where else are these words applicable, do they apply to data as well, if so how? any links to help me understand the difference..
regards,
kishore

Hi Kishore,
Client Independant: These objects are not specific to any client. And it is universal which can be viewed,changed across the clients.
Client Dependant: These are the objects can be viewed, changed for the client for which it has been assigned. Other clients do not have access on these objects.
In SAP, all objects are finally stored as tables. "Mandt" is key field which determines whether the object is client dependant or not.
Client Independant transport requests will make the transported objects available across the clients. and Client dependent transport request make the objects available only for the client mentioned by field "Mandt"
Regards,
Dinesh D

Diff bt Help view and Maintanence view

hi gem's
i need the diff bt Help view and Maintanence view with example...............

Hi
The followings are different types of views:
- Database View (SE11)
Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.
In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.
- Help View ( SE54)
Help views are used to output additional information when the online help system is called.
When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.
Go thru this link plzz
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
Difference between "Help View" and "Search Help"
- Projection View
Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.
A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.
- Maintenance View ( SE54 )
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
Please have a look at below link. It will help you.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
1.Go to se11
2. select view radiobutton and give a name
3. Create
4. select type of view you want to create. Such as database view.
5. give short description
6. give a table name such as mara
7. press the pushbutton relationship. here you will find all the tables which are allowed to create view with mara.
8. select one or mane tables.
8 copy
9.save , check and activate.
Regards
Anji

Diff between all views

hi all,
can any body tell me the diff between all views
projection view ,database view,maintance view,help view
plz tell me the difference with a example
hope for positive reponse

Maintenance views offer easy ways to maintain complex application objects.
Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.
A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
database view
Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.
Database views are defined in the ABAP Dictionary. A database view is automatically created in the underlying database when it is activated.
Application programs can access the data of a database view using the database interface. You can access the data in ABAP programs with both OPEN SQL and NATIVE SQL. However, the data is actually selected in the database. Since the join operation is executed in the database in this case, you can minimize the number of database accesses in this way. Database views implement an inner join
projection view
Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed.
A projection view contains exactly one table. You cannot define selection conditions for projection views.
There is no corresponding object in the database for a projection view. The R/3 System maps the access to a projection view to the corresponding access to its base table. You can also access pooled tables and cluster tables with a projection view.
help views
Help views are used if a view with an outer join is needed as selection method in a search help.
You have to create a help view if a view with outer join is needed as selection method of a search help.
The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.

Diff between ECC5.0 and ECC6.0

Hi,
This is Ramakrishna,can any one give proper explanation diff between ECC5.0 and ECC6.0
Regards
Ramakrishna

Hi,
Refer following link;
[SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
- Goods receipt
- Goods issue
- Transfer posting
- Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
- To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
- Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
- Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
- Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
- 107: Goods receipt to valuated goods receipt blocked stock
- 109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location

Diff between Solaris 8 and Solaris 9

Hello Experts,
Do we have a document which talks about the diff between Solaris 8 and Solaris 9
I need to know what are the new featured in Solaris 9 and etc....
Thanks in Advance.
Sunil.

Sadly, the difference between the early releases of Solaris 9 and the late releases of Solaris 8 isn't that big, since Sun backported a lot of the cool features in Solaris 9 to Solaris 8..
Hence; the answer to your question depends on which Solaris 8 and which Solaris 9 releases you are talking about.
However, a complete list of changes incoperated in the different Solaris 9 releases can be found here:
http://docs.sun.com/app/docs/doc/817-5770/6ml72d6k9?a=view
I guess there are similar lists for Solaris 10, which is even cooler than 8/9.
Enjoy!
//Magnus

Wrong position of objects / difference between editor view and browser view.

Dear Adobe
System info: Mac OS X 10.9, Muse 7.1 Build 329, Chrome, Safari and Firefox in the newest versions.
I use Muse since version 5 and this effect does exist 'til today (v7.1) without any changes.
Many times i have differences in the position of placed objects. But this missbehaviour is not realy logical. For example take a look to this illustration:
Left: Muse Editor, right: Browser (in this case its chrome, but the effect is identical in safari and firefox too)
Left you see one pixel space between the blue bar and the shadow (image-object). In the browser is the space bigger (2px). When i move the shadow-object in muse one pixel higher, then look this so:
The shadow is now within the bluebar. The position has changed in muse for 1 pixel, in browser around 7 pixels... i don't see, why.
Another example:
Left Muse Editor, right Browser... do you see the dramatic difference between?
I hope, this problem can be solved with a future version...
Best regards
Michael

This variation is due to the difference in the layout of text between Design view and Preview, which is representative of the variations that exist between browsers, OSes, devices and individual versions of each of those.
It's impossible to reverse engineer the structure of the objects from the screenshots, but how the objects or individual sized and positioned relative to one another is key to understanding (and explaining) what you're encountering.
If you provide the URL for this page I'll attempt take a look at it and provide some guidance for how to achieve the effect you're looking for within the constraints inherent in working with live text on the web.
(In case you're not already aware, you can Publish to a free trial site on Adobe Business Catalyst at any time using the Publish button. Using trial sites on BC is very convenient, even if you don't plan to host the finished site on BC.)

Difference between Database view and Table

Hi there,
Can anyone tell me the difference between Database view and Table.
Will the Database view query be more faster than a database table?

Tables and database views can be defined in the ABAP Dictionary.
These objects are created in the underlying database with this definition. Changes in the definition of a table or database view are also automatically made in the database.
Data from several tables can be combined in a meaningful way using a view (join).
You can also hide information that is of no interest to you (projection) or only display
those data records that satisfy certain conditions (selection).
Database views implement an inner join. You only get those records which have an
entry in all the tables included in the view.
in views db modifications are not possible
views only contain data at run time
when they consult the database
in case of views the join definitions are already sstored in the database itself
whereas join as open sql is a query to oracle database as similar select statements
Views are optimized by SAP and stored in the repository while Joins
are in reports that needs to be compiled at every execution
Reward if helps
Regards,
Senthil
Message was edited by: senthil kumar

Screen diff. between 4.7 and Ecc 6.0

Hi All,
Can you please provide the list of Transaction Code, where the Screens are diff.between 4.7 and ECC 6.0 in SD.
Means as per user View, they can find the diff. of the field for the screen. like Suppose in VA01 in ECC 6.0 might be add few more fields or modify the fields...compare to 4.7.
We need as per the Client requests..
regards
Pinal

There are so many differences between the version in different objects
I will explain in two or more objects the difference
1 in the customer master in 4.6 version there is no partner function tab in the customer in xd01 t-code
and also there is no CIN tab in that version
but it is there in the 4.7 EE version
This is the major change from the 4.6cc to 4.7EE
2. in 4.7EE there is some settings that are related for CIN
which cannot be done in 4.7EE that means they need some patches for doing the configuration setting for the CIN
But we can do the same in the 6.0 version
These are the some of the settings that are differed in the two versions and in that two objects
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prospective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences please refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
For Functionality Differences please refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Re: Difference Between SAP Version ECC 4.6, 4.7, SAP 5.0, 6.0 with SA
Re: SAP version differences 4.5b, 4.6c and ECC6.0
You can find the difference in release notes of each SAP version.
Here are the links.
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prospective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences please refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
rewards if it helps
siva

What is the diffrence between SAP View and CAD View ?

What is the diffrence between SAP View and CAD View ?
What is the main purpose of SAP View
and
What is the main purpose of CAD View
On SAP help i found
SAP View is used for :The SAP view displays the SAP structure (document-based structure) for the active CAD object, or another document info record (header document), with a single-level or multilevel document structure in a tree structure. You can variably configure the fields using the layout editor.
CAD View is used for :The CAD view displays the document-based structure of the currently active CAD object, such as the structure of an assembly. The CAD system determines the complete (multilevel) structure and copies it either completely or in stages to the SAP system, in accordance with the default explosion level.
BUT I did not understand it well
Can someone explain this with an example
THanks
Raj

Hello Raj,
SAP View can be further described as the view that is based on what is existing already in the SAP system. This view is generally used by SAP purchasing, MM people etc
CAD view is nothing but the replication of the model tree view in the SAP system. This is used by the design engineer and this view replicates only the parts that are actively displayed on the CAD tool window.
hope this helps. Let me know if you have further questions else please close the message.
regards
N K

In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

hello all
In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

Hi Swamy,
The differences between IDoc and BAPI are as follows:
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system.
Idocs are processed asynchronously and no information whatsoever is returned to the client.
The target system need not be always online. The IDOC would be created and would send the IDOC once the target system is available (tRFC concept). Hence supports guaranteed delivery.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later.
The disadvantage of asynchronous links is that the sub-process on the server cannot return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
IDOCs may be more changeable from release to release.
IDOCs are poorly documented.
BAPI
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.
BAPIs are called synchronously and (usually) return information.
For BAPIs the client code needs to do the appropriate error handling.
Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client cannot be finished (otherwise there would be data inconsistencies).
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link.
BAPIs are not totally immune to upgrades.
BAPIs are reasonably well documented.
Reward points if useful.
Best Regards,
Sekhar

Diff between Thin client and Rich client

Hi Everyone,
Can someone give me a clear picture of the what is the diff between Thin client and Rich client.
Thanks,
Krishna

Hi,
thick client (rich client) has/stores all the data inside itself
so it can do application processing without the server with data
thin client uses resources from host computer (from server)
and wihtout that you are not able to work with that kind of client
does that answer your question ?
Regards,
michal

Diff between Seeburger Adapter and File Adapter

Hi All,
My company needs to interact with some banks and the banks are particular that they want SFTP, which is not supported by File Adapter, so we have decided to go with Seeburger adapter.
Now what are the differences between File adapter and seeburger adapter?
I believe that Seeburger adapter does not support File Content Conversion, Archiving etc.
Could you all pls put some light on the diff between file adapter and seeburger adapter when it comes to dealing with files?
Xier

Hi
You are aware with working of File Adapter.
The most direct way of using the Seeburger adaptors is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to
1. Define or import the inbound message metadefinition in various formats ( edifact, xml,...)
2. Using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
3. Create a one to one mapping between input en output.
4. Export the metadata in xsd or sda format for import in XI
5. Generate an SDA which can be deployed in XI and used as a module.
Have a look here,
http://www.seeburger.com/fileadmin/com/pdf/SAP_Exchange_Infrastructure_Integratio_Strategy.pdf
Some Seeburger related information
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e2aeb02c-0601-0010-d680-c9be61ffa390
Go through this threads:
http://www.seeburger.com/fileadmin/com/pdf/SAP_Exchange_Infrastructure_Integratio_Strategy.pdf
Need Material on Seeburger Adapters.
Seeburger Adapter
Installing seeburger adapter
http://www.seeburger.com/xi-adapters/
Thanks

DIFF. between Quick Viewer and Query Builder

Similar Messages

Maybe you are looking for